344 | | To use Quattor, you need to deploy software repositories. Even if you |
345 | | want to customize it later, you are probably better to start with a |
346 | | configuration similar to what is provided in `repository` directory of |
347 | | `sites/example` directory. |
348 | | |
349 | | You can retrieve an initial directory content for each RPM repository by downloading the contents of the URL |
350 | | specified in comments at the beginning of each repository templates. A convenient way to do it is: |
351 | | {{{ |
352 | | src/utils/misc/rpmUpdates /your/dir/ectory URL_found_in_template_header > /dev/null |
353 | | }}} |
354 | | |
355 | | ''Note: this command produces a rather verbose output, just ignore it.'' |
356 | | |
357 | | You have to do it for the following repository templates: |
358 | | * OS: to start, you need only to download the OS version you plan to use. ''Note: there are several repositories per OS versions, be sure to download all of them.'' |
359 | | * gLite: to start download all the repositories related to the version you are planning to use, ignore others. |
360 | | * All the repositories not related to an OS or gLite version |
361 | | |
362 | | You are probably better to remove any template you think you will not use (you can always revert your change in case of mistakes). |
| 344 | In addition to the templates, you also need to mirror the YUM repositories used by the template library. You can find in the example part of the template library (from GitHub repository template-library-examples or from directory cfg/sites/examples/repository created by previous step) URLs of YUM repositories that you can use as upstream repositories to start. You may also want to look at how to use [http://quattor.org/documentation/2014/03/24/spma-yum-migration.html#toc_9 YUM repository snapshots] with Quattor. |