Stored Profiles; Custom System Info; Kickstart - Red Hat NETWORK 3.1 - PROVISIONING Reference Manual

Chapter 4. Red Hat Network Website
Entitlement — The service level for the key, either Management or Provisioning. All systems
•
will be subscribed at this level with the key.
Universal default — Whether or not this key should be considered the primary activation
•
key for your organization.
Deploy configs — Select to have all stored configuration files installed upon registration.
•
Click Create Key.
After creating the unique key, it appears in the list of activation keys along with the number of times
it has been used. At this point, you may associate child channels and groups with the key so systems
registered with it will automatically be subscribed to them.
To change information about a key, such as the channels or groups, click its description in the key list,
make your modifications in the appropriate tabs, and click the Update Key button. To remove a key
entirely, click the delete key link in the top-right corner of the edit page.
If you do not want a key to be used to activate a system, you can disable it by unselecting the corre-
sponding checkbox under the Enabled column in the key list. The key can be re-enabled by selecting
the checkbox. After making these changes, click the Update Keys button on the bottom right-hand
corner of the page.
4.4.8. Stored Profiles
RHN Provisioning customers can create package profiles through the Profiles subtab of the Packages
tab within the System Details page. Those profiles end up here, on the Stored Profiles page, where
they may be edited and even deleted.
To edit a profile, click its name in the list, alter its name and description, and click the Update Profile.
To view software associated with the profile, click the Packages subtab. To remove the profile entirely,
click delete stored profile at the upper-right corner of the page.

4.4.9. Custom System Info

RHN Provisioning customers may include completely customizable information about systems. Un-
like notes, the information here is more formal and can be searched upon. For instance, you may
decide to identify the cubicle in which each system is located. To do this, you must create a cubicle
key within the Custom System Info page.
Click create new key at the upper-right corner of the page. Enter a descriptive label and description,
such as "Cubicle" and "Precise location of each system," and click the Create Key. The key will then
show up in the custom info keys list.
Once the key exists, you may assign a value to it through the Custom Info tab of the System Details
page. Refer to Section 4.4.2.6 System Details for instructions.

4.4.10. Kickstart

To satisfy the provisioning needs of customers, RHN provides this interface for developing kickstart
profiles by which new systems may be built. This enables systems to be installed to particular speci-
fications automatically.
Warning
Since RHN Proxy Servers direct files from the central RHN Servers, and those servers do not dis-
tribute the files necessary for kickstart, systems connected to a Proxy not being served by an RHN
61