Table of Contents Previous Next



Use the RHEL Subscription Management section of the Admin tab to define and manage Red Hat Subscription Manager access for your Ark consoles that reside on Red Hat Linux instances (see Figure 4.33).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\1a34622b\Screen Shot 2017-05-09 at 10.32.21 AM.png
After creating a subscription definition, use options in the DB Engine Administration section of the Admin tab to associate the definition with database engines.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\b6dadd38\Screen Shot 2017-08-14 at 9.10.19 AM.png
Use fields on the Add RHEL Subscription dialog (see Figure 4.34) to describe a Red Hat subscription service:
Use the Subscription Id field to provide a user-friendly name for the subscription. The name will identify the subscription in the RHEL Subscription drop-down on the Add Engine Details dialog.
Use the Username field to provide the name of the user account registered with the Red Hat content server.
Use the Password field to provide the password associated with the user account.
Use the Server Url field to provide the host name of the subscription server used by the service; if left blank, the default value of subscription.rhn.redhat.com will be used.
Use the Base Url field to provide the host name of the content delivery server used by the service; if left blank, the default value of https://cdn.redhat.com will be used.
Use the Org field to provide the organization that will be registered with the Red Hat subscription system.
Use the Environment field to provide the name of the environment (within the organization that will be registered).
Use the Name field to provide the name of the system that will be registered.
Use the Activation Key field to provide the activation key of the Red Hat subscription.
If enabled, use the Auto-attach checkbox to instruct any node associated with the subscription to automatically attach to the service.
If applicable, use the Pool field to provide the pool identifier for the Red Hat subscription service.
If applicable, check the Auto checkbox to indicate that nodes provisioned with engines associated with the pool will automatically attach to the subscription service.
If applicable, use the Quantity field to provide the number of subscriptions in the subscription pool.
Use the Service Level field to provide the service level of the subscription.
Use the Release field to provide the operating system minor release that will be used when identifying updates to any nodes provisioned with the subscription.
Check the Force checkbox to indicate that the node should be registered, even if it is already registered.
Use the Type field to specify the type of consumer that is being registered; the default is system.
The Required Repos list is populated by the Ark console, and displays a list of the repositories required by the subscription definition.
Use the Additional Repos field to provide the names of any additional repositories that should be enabled on the cluster node(s).
Use the Disabled Repos field to provide the names of any repositories that should be disabled on the cluster node(s).
When you've completed the dialog, click the Save button to add the repository to the table in the RHEL Subscription Management section, or Cancel to exit without saving. If you choose to save the definition, the Ark console will display a popup that lists the subscription manager commands that were generated as a result of your selections (see Figure 4.35).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\1ab4630a\Screen Shot 2017-05-09 at 10.28.16 AM.png
After creating a subscription definition, use options in the DB Engine Administration section of the Admin tab to associate the definition with database engines; see Section 4.1.3 for detailed information.
To modify the description of a Red Hat Subscription Manager service, highlight the name of a subscription in the RHEL Subscription Management table, and click the Edit RHEL Subscription button. The Edit RHEL Subscription Details dialog opens, allowing you to modify the subscription definition.
After modifying the subscription definition, click Save to preserve your changes and exit the dialog; to exit without saving, click the Cancel button. Please note that changes made to a definition are applied only to those instances that are created after the changes are saved; changes are not propagated to existing instances.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\0f815dc3\Screen Shot 2017-05-10 at 1.00.34 PM.png
Click the Delete button to confirm that you wish to delete the subscription definition, or Cancel to exit without deleting the definition (see Figure 4.36).


Table of Contents Previous Next