Piste:
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
|
pages_it:provisioning:theforeman [2017/09/07 12:49] ebelhomme [Mirror a Yum repository] |
pages_it:provisioning:theforeman [2017/09/08 07:20] (Version actuelle) ebelhomme [The Foreman installation with Katello support] |
||
|---|---|---|---|
| Ligne 11: | Ligne 11: | ||
| More readings : | More readings : | ||
| + | * https:// | ||
| + | * https:// | ||
| * https:// | * https:// | ||
| * https:// | * https:// | ||
| Ligne 17: | Ligne 19: | ||
| === Software === | === Software === | ||
| + | |||
| Foreman/ | Foreman/ | ||
| === Hardware === | === Hardware === | ||
| + | |||
| 12GB are highly recommended. | 12GB are highly recommended. | ||
| Ligne 27: | Ligne 31: | ||
| === Storage === | === Storage === | ||
| - | ^ mountpoint | + | |
| Red Hat strongly recommends to use **LVM** for partitioning, | Red Hat strongly recommends to use **LVM** for partitioning, | ||
| + | ^ mountpoint | ||
| | / | 10GB | base system | | / | 10GB | base system | ||
| | / | | / | ||
| Ligne 162: | Ligne 167: | ||
| === GPG key === | === GPG key === | ||
| + | |||
| + | We need to import the GPG key used by the remote repository. In our case, the GPG key is accessible on | ||
| http:// | http:// | ||
| + | |||
| + | <columns - -> | ||
| + | On the Menu bar, click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Click on //**Create GPG Key**// Button | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Fill the form with the following informations : | ||
| + | * **Name** : a name for the GPG key to create, | ||
| + | * **GPG Key content** : you can copy & paste the content of the GPG key in the form, of you can use the // | ||
| + | |||
| + | Then click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| === Product === | === Product === | ||
| - | Dowbload policy | + | <columns - -> |
| - | * **On demand** : only repo's metadata are downloaded from the remote repository, then packages are fetched and stored on local FS only when clients request them, | + | On the Menu bar, click on // |
| - | * **Background** : repo's metadata are downloaded from the remote repository, then packages are downloaded as a background task after the initial | + | < |
| - | * **Immediate** : both repo's metadata and packages are downloaded. | + | {{ : |
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Click on //**Create Product**// Button | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Fill the form with the following informations : | ||
| + | * **Name** : the name for the product, | ||
| + | * **Label** : the label used internammy by Foreman, | ||
| + | * **GPG Key** : select with the drop-down list the relevant GPG key, | ||
| + | * **Sync Plan** : select with the drop-down list the relevant | ||
| + | * **Description** : put a description for this product. | ||
| - | === Environment | + | Then click on // |
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | One the product is created, the user is automatically directed to the // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - - -> | ||
| + | Fill the form with the following informations : | ||
| + | * **Name** : a name for the repository, | ||
| + | * **Label** : the label used internammy by Foreman, | ||
| + | * **Type** : select //**yum**// on the drop-down menu, | ||
| + | * **URL** : enter here the URL of the Yum repository to mirror | ||
| + | * **Dowbload policy** | ||
| + | * **On demand** : only repo's metadata are downloaded from the remote repository, then packages are fetched and stored on local FS only when clients request them, | ||
| + | * **Background** : repo's metadata are downloaded from the remote repository, then packages are downloaded as a background task after the initial sync, | ||
| + | * **Immediate** : both repo's metadata and packages are downloaded. | ||
| + | * **GPG Key** : Select with the drop-down menu the GPG key to use with this repository. | ||
| + | |||
| + | Then click on // | ||
| + | < | ||
| + | {{: | ||
| + | < | ||
| + | {{: | ||
| + | </ | ||
| + | ---- | ||
| + | |||
| + | === Lifecycle Environments | ||
| + | |||
| + | <columns - -> | ||
| + | On the Menu bar, click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Click on //**Create Environment Path**// Button | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Fill the form with the following informations : | ||
| + | * **Name** : a name for the environment, | ||
| + | * **Label** : the label used internammy by Foreman, | ||
| + | * **Description** : a description | ||
| + | |||
| + | Then click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| === Content View === | === Content View === | ||
| + | |||
| + | <columns - -> | ||
| + | On the Menu bar, click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Click on //**Create New View**// Button | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Fill the form with the following informations : | ||
| + | * **Name** : a name for the view, | ||
| + | * **Label** : the label used internammy by Foreman, | ||
| + | * **Description** : a description | ||
| + | Then click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Once the view is created, go on the //**Yum Content**// pane, then select the //**Add**// pane from the // | ||
| + | |||
| + | Then select the repositories to include into the view (in the example below, //base// and //updates// repositories from CentOS 7 Product are selected. | ||
| + | |||
| + | Finally, click on //**Add Repositories**// | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | go on the // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Fill the // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | The version is going to be published. This may take a while. | ||
| + | |||
| + | When the publshing procedure is completed, you can click on the // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Select the right //library// by clicking on the checkbox, then click on //**Promote Version**// | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| === Activation keys === | === Activation keys === | ||
| + | <columns - -> | ||
| + | On the Menu bar, click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Click on //**Create Activation Key**// Button | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Fill the form with the following informations : | ||
| + | * **Name** : The name of the activation key, | ||
| + | * **Unlimited Hosts** : check the box if you don't need to restrict the ammount of clients registered, | ||
| + | * **Description** : put a descriptive text, | ||
| + | * **Environment** : select the desired environments. | ||
| + | |||
| + | Then click on // | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| + | <columns - -> | ||
| + | Once the key is created, it can be used to register client hosts to this system by using the following command : | ||
| + | < | ||
| + | subscription-manager register --org=" | ||
| + | </ | ||
| + | < | ||
| + | {{ : | ||
| + | </ | ||
| + | ---- | ||
| ==== Configure client host ==== | ==== Configure client host ==== | ||
| - | | + | === Prerequisites === |
| + | |||
| + | The target system must have the required package installed prior registration : | ||
| + | | ||
| + | * **katello-ca-consumer-katello.xxx** must by downloaded from the Katello server itself. | ||
| + | |||
| + | In the following example, the Foreman/ | ||
| <code shell> | <code shell> | ||
| yum install -y subscription-manager | yum install -y subscription-manager | ||
| Ligne 185: | Ligne 383: | ||
| </ | </ | ||
| - | * register | + | === Client registration === |
| + | |||
| + | In order to register | ||
| + | * the **oraganization** name, in our example, the organization name is // | ||
| + | * the **activation key**. in our axample, | ||
| <code shell> | <code shell> | ||
| subscription-manager register --org=" | subscription-manager register --org=" | ||
| Ligne 193: | Ligne 395: | ||
| </ | </ | ||
| - | List available subscriptions | + | === List available subscriptions |
| < | < | ||
| Ligne 215: | Ligne 417: | ||
| </ | </ | ||
| - | Attach to a subscription | + | === Attach to a subscription |
| < | < | ||
| subscription-manager attach --pool=4028fa325e577a77015e5b0d989a0025 | subscription-manager attach --pool=4028fa325e577a77015e5b0d989a0025 | ||
| Successfully attached a subscription for: EPEL7 for CentOS/RHEL | Successfully attached a subscription for: EPEL7 for CentOS/RHEL | ||
| </ | </ | ||