Admin

The menu:Organization[Organization Details] page lists the details of the selected organization.

The following details are available:

List of all the users of an organization.

You can modify the user details if you belong to that organization and have organization administrator privileges.

Here establish trust between organizations.

Such a trust allows sharing contents and migrate systems between these two organizations. You may add a trust by checking the box next to an organization (or remove a trust by unchecking it) and clicking the btn:[Modify Trusts] button.

Allow the Organization Administrator to manage Organization configuration, configure the organization to use staged contents (“pre-fetching” packages, etc.), set up software crash reporting, and upload of SCAP files.

When settings are done, confirm with clicking the btn:[Update Organization] button.

For staging contents (“pre-fetching”), edit on the client /etc/sysconfig/rhn/up2date:

stagingContentWindow is a time value expressed in hours and determines when downloading will start. It is the number of hours before the scheduled installation or update time. In this case, it means 24 hours before the installation time. The start time for download depends on the selected contact method for a system. The assigned contact method sets the time for when the next rhn_check will be executed.

Next time an action is scheduled, packages will automatically be downloaded but not installed yet. When the scheduled time comes, the action will use the staged version.

Staging content for minions is affected by two parameters.

A value of salt_content_staging_advance equal to salt_content_staging_window results in the content staging window closing exactly when the installation/upgrade is scheduled to be executed. A larger value allows separating download time from the installation time.

These options are configured in /usr/share/rhn/config-defaults/rhn_java.conf and by default assume the following values:

From the menu:Admin[Organizations > States] page you can assign State to all systems in an organization. For example, this way it is possible to define a few global security policies or add a common admin user to all machines.

This page allows you to adjust basic {productname} administration settings.

When done, confirm with btn:[Update].

The menu:Manager Configuration[Bootstrap Script] page allows you to generate a bootstrap script that registers the client systems with {productname} and disconnects them from the remote {scc}.

This generated script will be placed within the /srv/www/htdocs/pub/bootstrap/ directory on your {productname} server. The bootstrap script will significantly reduce the effort involved in reconfiguring all systems, which by default obtain packages from the {scc}. The required fields are pre-populated with values derived from previous installation steps. Ensure this information is accurate.

When finished, click btn:[Update].

The menu:Manager Configuration[Organizations] page contains details about the organizations feature of {productname}, and links for creating and configuring organizations.

The menu:Manager Configuration[Restart] page comprises the final step in configuring {productname}.

Click the btn:[Restart] button to restart {productname} and incorporate all of the configuration options added on the previous screens. It will take between four and five minutes for a restart to finish.

On the menu:Manager Configuration[Cobbler] page you can run the Cobbler synchronization by clicking btn:[Update].

Cobbler synchronization is used to repair or rebuild the contents of /srv/tftpboot or /srv/www/cobbler when a manual modification of the cobbler setup has occurred.

Here you can add unprovisioned ("bare-metal") systems capable of booting using PXE to an organization.

First click btn:[Enable adding to this organization]. Those systems then will appear in the menu:Main Menu[Systems > All Systems] list, where regular provisioning via autoinstallation is possible in a completely unattended fashion.

Only AMD64/Intel 64 systems with at least 1 GB of RAM are supported. {productname} server will use its integrated Cobbler instance and will act as TFTP server for this feature to work, so the network segment that connects it to target systems must be properly configured. In particular, a DHCP server must exist and have a next-server configuration parameter set to the {productname} server IP address or hostname.

When enabled, any bare-metal system connected to the SUSE Manager server network will be automatically added to the organization when it powers on. The process typically takes a few minutes; when it finishes, the system will automatically shut down and then appear in the menu:Main Menu[Systems > All Systems] list.

Provisioning can be initiated by clicking the btn:[Provisioning] tab. In case of bare-metal systems, though, provisioning cannot be scheduled, it will happen automatically when it is completely configured and the system is powered on.

It is possible to use menu:Main Menu[Systems > System Set Manager] with bare-metal systems, although in that case some features will not be available as those systems do not have an operating system installed. This limitation also applies to mixed sets with regular and bare-metal systems: full features will be enabled again when all bare-metal systems are removed from the set.

The following will help you set up a master ISS server.

Click menu:Admin[>ISS Configuration > Master Setup]. In the top right-hand corner of this page, click btn:[Add New Slave]:

Fill in the following information:

Click btn:[Create]. Optionally, click any local organization to be exported to the slave {productname} then click btn:[Allow Orgs].

For synchronization timeout settings, see: [bp.troubleshooting.timeouts].

Slave servers receive content synchronized from the master server.

To securely transfer content to the slave servers, the ORG-SSL certificate from the master server is needed. Click menu:Admin[ISS Configuration > Slave Setup]. In the top right-hand corner, click btn:[Add New Master].

menu:ISS Configuration[Update Master > Master Setup] and fill in the following information:

Click btn:[Add New Master]. Once the master and slave servers are configured, start the synchronization on the Master server by executing mgr-inter-sync:

A mapping between organizational names on the master {productname} allows for channel access permissions being set on the master server and propagated when content is synchronized to a slave {productname}. Not all organization and channel details need to be mapped for all slaves. {productname} administrators can select which permissions and organizations can be synchronized by allowing or omitting mappings.

To complete the mapping, log in to the Slave {productname} as administrator. Click menu:Admin[ISS Configuration > Slave Setup] and select a master {productname} by clicking its name. Use the drop-down box to map the exported master organization name to a matching local organization in the slave {productname}, then click btn:[Update Mapping].

On the command line, issue the synchronization command on each of the custom channels to obtain the correct trust structure and channel permissions: