Chapter 22. Using the rhc system role to register the system

Procedure

1. Store your sensitive variables in an encrypted file:

   1. Create the vault:

      $ ansible-vault create vault.yml
      New Vault password: <password>
      Confirm New Vault password: <vault_password>

   2. After the ansible-vault create command opens an editor, enter the sensitive data in the <key>: <value> format:

      activationKey: <activation_key>
      username: <username>
      password: <password>

   3. Save the changes, and close the editor. Ansible encrypts the data in the vault.

2. Create a playbook file, for example ~/playbook.yml, with the following content:

   • To register by using an activation key and organization ID (recommended), use the following playbook:

     ---
     - name: Registering system using activation key and organization ID
       hosts: managed-node-01.example.com
       vars_files:
         - vault.yml
       roles:
         - role: rhel-system-roles.rhc
       vars:
         rhc_auth:
           activation_keys:
             keys:
               -  "{{ activationKey }}"
         rhc_organization: organizationID

   • To register by using a username and password, use the following playbook:

     ---
     - name: Registering system with username and password
       hosts: managed-node-01.example.com
       vars_files:
         - vault.yml
       vars:
         rhc_auth:
           login:
             username: "{{ username }}"
             password: "{{ password }}"
       roles:
         - role: rhel-system-roles.rhc

3. Validate the playbook syntax:

   $ ansible-playbook --syntax-check --ask-vault-pass ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

4. Run the playbook:

   $ ansible-playbook --ask-vault-pass ~/playbook.yml

Procedure

1. Store your sensitive variables in an encrypted file:

   1. Create the vault:

      $ ansible-vault create vault.yml
      New Vault password: <password>
      Confirm New Vault password: <vault_password>

   2. After the ansible-vault create command opens an editor, enter the sensitive data in the <key>: <value> format:

      activationKey: <activation_key>

   3. Save the changes, and close the editor. Ansible encrypts the data in the vault.

2. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: Register to the custom registration server and CDN
     hosts: managed-node-01.example.com
     vars_files:
       - vault.yml
     roles:
       - role: rhel-system-roles.rhc
     vars:
       rhc_auth:
         login:
           activation_keys:
             keys:
               - "{{ activationKey }}"
           rhc_organization: organizationID
       rhc_server:
         hostname: example.com
           port: 443
           prefix: /rhsm
       rhc_baseurl: http://example.com/pulp/content

3. Validate the playbook syntax:

   $ ansible-playbook --syntax-check --ask-vault-pass ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

4. Run the playbook:

   $ ansible-playbook --ask-vault-pass ~/playbook.yml

Procedure

1. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: Disable Insights connection
     hosts: managed-node-01.example.com
     roles:
       - role: rhel-system-roles.rhc
     vars:
       rhc_insights:
         state: absent

2. Validate the playbook syntax:

   $ ansible-playbook --syntax-check ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

3. Run the playbook:

   $ ansible-playbook ~/playbook.yml

Procedure

1. Create a playbook file, for example ~/playbook.yml, with the following content:

   • To enable a repository:

     ---
     - name: Enable repository
       hosts: managed-node-01.example.com
       roles:
         - role: rhel-system-roles.rhc
       vars:
         rhc_repositories:
           - {name: "RepositoryName", state: enabled}

   • To disable a repository:

     ---
     - name: Disable repository
       hosts: managed-node-01.example.com
       vars:
         rhc_repositories:
           - {name: "RepositoryName", state: disabled}
       roles:
         - role: rhel-system-roles.rhc

2. Validate the playbook syntax:

   $ ansible-playbook --syntax-check ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

3. Run the playbook:

   $ ansible-playbook ~/playbook.yml

Procedure

1. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: Set Release
     hosts: managed-node-01.example.com
     roles:
       - role: rhel-system-roles.rhc
     vars:
       rhc_release: "8.6"

2. Validate the playbook syntax:

   $ ansible-playbook --syntax-check ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

3. Run the playbook:

   $ ansible-playbook ~/playbook.yml

Procedure

1. Store your sensitive variables in an encrypted file:

   1. Create the vault:

      $ ansible-vault create vault.yml
      New Vault password: <password>
      Confirm New Vault password: <vault_password>

   2. After the ansible-vault create command opens an editor, enter the sensitive data in the <key>: <value> format:

      username: <username>
      password: <password>
      proxy_username: <proxyusernme>
      proxy_password: <proxypassword>

   3. Save the changes, and close the editor. Ansible encrypts the data in the vault.

2. Create a playbook file, for example ~/playbook.yml, with the following content:

   • To register to the Red Hat Customer Portal by using a proxy:

     ---
     - name: Register using proxy
       hosts: managed-node-01.example.com
       vars_files:
         - vault.yml
       roles:
         - role: rhel-system-roles.rhc
       vars:
         rhc_auth:
           login:
             username: "{{ username }}"
             password: "{{ password }}"
         rhc_proxy:
           hostname: proxy.example.com
           port: 3128
           username: "{{ proxy_username }}"
           password: "{{ proxy_password }}"

   • To remove the proxy server from the configuration of the Red Hat Subscription Manager service:

     ---
     - name: To stop using proxy server for registration
       hosts: managed-node-01.example.com
       vars_files:
         - vault.yml
       vars:
         rhc_auth:
           login:
             username: "{{ username }}"
             password: "{{ password }}"
         rhc_proxy: {"state":"absent"}
       roles:
         - role: rhel-system-roles.rhc

3. Validate the playbook syntax:

   $ ansible-playbook --syntax-check --ask-vault-pass ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

4. Run the playbook:

   $ ansible-playbook --ask-vault-pass ~/playbook.yml

Procedure

1. Store your sensitive variables in an encrypted file:

   1. Create the vault:

      $ ansible-vault create vault.yml
      New Vault password: <password>
      Confirm New Vault password: <vault_password>

   2. After the ansible-vault create command opens an editor, enter the sensitive data in the <key>: <value> format:

      username: <username>
      password: <password>

   3. Save the changes, and close the editor. Ansible encrypts the data in the vault.

2. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: Disable Red Hat Insights autoupdates
     hosts: managed-node-01.example.com
     vars_files:
       - vault.yml
     roles:
       - role: rhel-system-roles.rhc
     vars:
       rhc_auth:
         login:
           username: "{{ username }}"
           password: "{{ password }}"
       rhc_insights:
         autoupdate: false
         state: present

3. Validate the playbook syntax:

   $ ansible-playbook --syntax-check --ask-vault-pass ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

4. Run the playbook:

   $ ansible-playbook --ask-vault-pass ~/playbook.yml

Procedure

1. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: Disable remediation
     hosts: managed-node-01.example.com
     roles:
       - role: rhel-system-roles.rhc
     vars:
       rhc_insights:
         remediation: absent
         state: present

2. Validate the playbook syntax:

   $ ansible-playbook --syntax-check ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

3. Run the playbook:

   $ ansible-playbook ~/playbook.yml

Procedure

1. Store your sensitive variables in an encrypted file:

   1. Create the vault:

      $ ansible-vault create vault.yml
      New Vault password: <password>
      Confirm New Vault password: <vault_password>

   2. After the ansible-vault create command opens an editor, enter the sensitive data in the <key>: <value> format:

      username: <username>
      password: <password>

   3. Save the changes, and close the editor. Ansible encrypts the data in the vault.

2. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: Creating tags
     hosts: managed-node-01.example.com
     vars_files:
       - vault.yml
     roles:
       - role: rhel-system-roles.rhc
     vars:
       rhc_auth:
         login:
           username: "{{ username }}"
           password: "{{ password }}"
       rhc_insights:
         tags:
           group: group-name-value
           location: location-name-value
           description:
             - RHEL8
             - SAP
           sample_key:value
         state: present

3. Validate the playbook syntax:

   $ ansible-playbook --syntax-check --ask-vault-pass ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

4. Run the playbook:

   $ ansible-playbook --ask-vault-pass ~/playbook.yml

Procedure

1. Create a playbook file, for example ~/playbook.yml, with the following content:

   ---
   - name: Unregister the system
     hosts: managed-node-01.example.com
     roles:
       - role: rhel-system-roles.rhc
     vars:
       rhc_state: absent

2. Validate the playbook syntax:

   $ ansible-playbook --syntax-check ~/playbook.yml

   Note that this command only validates the syntax and does not protect against a wrong but valid configuration.

3. Run the playbook:

   $ ansible-playbook ~/playbook.yml