SUSE Manager/NewFeatures2.1

From MicroFocusInternationalWiki
Revision as of 09:45, 25 October 2013 by SilvioMoioli (Talk | contribs) (Created page with "= New Features in SUSE Manager 2.1 = This beta test comes with the latest upcoming features that will be included in SUSE Manager 2.1, which includes support for: * Unattend...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

New Features in SUSE Manager 2.1

This beta test comes with the latest upcoming features that will be included in SUSE Manager 2.1, which includes support for:

  • Unattended bare-metal system provisioning
  • Power Management

Installation Instructions

Stop spacewalk services

 $> spacewalk-service stop

Update already installed packages

 $> zypper ar -f TODO: BETA ADDRESS HERE manager-beta
 $> zypper dup --from manager-beta

Schema upgrade

 $> spacewalk-schema-upgrade

Start spacewalk services

 $> spacewalk-service start

Unattended bare-metal system provisioning


SUSE Manager can be configured to automatically discover unprovisioned ("bare-metal") systems attached to the network and show them in the Systems list. Once a system appears in SUSE Manager, regular provisioning via autoinstallation is possible in a completely unattended fashion.


  • a fully patched SUSE Manager 2.1 server (see above for migration instructions from SUSE Manager 1.7);
  • one or more unprovisioned systems capable of PXE booting. Only x86_64 systems with at least 1 GB of RAM are supported.

Note that the SUSE Manager 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 this regard. In particular, a DHCP server must exist and have a next-server configuration parameter set to the SUSE Manager server IP address or hostname. See Cobbler Requirements for details.

Enabling bare-metal system discovery


Note that discovered systems will be added to the organization the current user belongs to. If you need to change it disable discovery, log in as an administrator of the organization you want new systems to be added to and enable discovery again TODO: CHECK THAT THESE INSTRUCTIONS ARE STILL CORRECT.

At this point, any bare-metal system connected to the SUSE Manager server will be automatically discovered as soon as it powers on. When discovery finishes, typically after a few minutes, the system will automatically shut down and will appear in the Systems list.

If this does not happen automatically, see the Troubleshooting section.

Inspecting discovered bare-metal systems

Discovered systems will appear in the Systems list with a special icon. Clicking on a system's name shows some basic information about the system, more details can be obtained or added manually via the Properties, Notes and Hardware tabs.

Bare-metal systems can be migrated to another organization like regular systems by using the Migrate tab.

Provisioning is also similar and can be initiated by clicking on the Provisioning tab. In case of bare-metal systems, though, provisioning cannot be scheduled: it will happen automatically as soon as it is completely configured and the system is powered on. Details about provisioning and autoinstallation configuration are available in the Autoinstallation section; to power on a system from SUSE Manager see Power Management.

System Set Manager and bare-metal systems

Although you can use System Set Manager with bare-metal systems, many features will not be available because those systems do not have an operating system installed. This limitation also applies to mixed sets with regular and bare-metal systems: you are advised to remove bare-metal systems from the set if you need all System Set Manager features.


If a bare-metal system is not automatically discovered, please do the following:

  1. check that network equipment connecting the system and the SUSE Manager server works correctly;
  2. check that those bare-metal systems have PXE booting enabled in their boot sequence, and that no operating system gets booted;
  3. check that the DHCP server responds to the DHCP request from the system during boot. In particular:
    1. check that it assigns the expected IP address. Typically you should see this address among PXE boot messages;
    2. check that it assigns the SUSE Manager server IP address as next-server for booting. This IP address should also be abe displayed among PXE boot messages;
  4. check that the SUSE Manager server IP address is actually reachable from the server;
  5. check that the SUSE Manager server has Cobbler running and the discovery feature is enabled;
  6. if you see a Cobbler blue menu shortly after booting, discovery has actually started. If it does not complete succesfully you can disable automatic shutdown for diagnosis purposes. To do that use the arrow keys to select "pxe-default-profile" in the Cobbler menu and press the Tab key before the 30 second timer expires. Then delete the kernel boot parameter spacewalk-finally=shutdown using the integrated editor and press Enter to continue booting. Then enter login root and password linux to get to a shell.

Known Issues

  • Due to technical limitation it is not possible to reliably distinguish a new bare-metal system from a system that has been discovered for the second time, it is thus recommended not to power on bare-metal systems multiple times. In case that happens, you can remove duplicate profiles by using the Duplicate systems page.

Power Management