- 1 New Features in SUSE Manager 1.7
- 1.1 Installation Instructions (Server)
- 1.2 Installation Instructions (Proxy)
- 1.3 Installation Instructions (Client)
- 1.4 New spacewalk-schema-upgrade
- 1.5 Tool to create bootstrap repositories
- 1.6 SSH Server Push
- 1.7 TFTP Sync
New Features in SUSE Manager 1.7
This betatest comes with the latest upcoming features for SUSE Manager 1.7, which includes support for managing clients via a server push mechanism (SSH Server Push) as well as the TFTP Sync feature to support PXE booting via SUSE Manager proxies. Additionally we improved the spacewalk-schema-upgrade script.
Installation Instructions (Server)
Stop spacewalk services
$> spacewalk-service stop
Update already installed packages
$> zypper ar -f http://beta.suse.com/private/SUSE-Manager-beta/features/server-push/server manager-beta $> zypper dup --from manager-beta
Start spacewalk services
$> spacewalk-service start
Installation Instructions (Proxy)
Update the packages on a proxy
$> zypper ar -f http://beta.suse.com/private/SUSE-Manager-beta/features/server-push/proxy proxy-beta $> zypper dup --from proxy-beta
Restart the proxy
$> mgr-proxy restart
Installation Instructions (Client)
The beta test provides packages from an internal development build, not signed with a SUSE build key and marked with a non-SUSE vendor. This is why updated packages have to be installed via 'zypper dup'.
Execute the following commands to upgrade packages on a managed client or a system that you want to register for being managed (example shows a SLES 11 SP2 system, see below for other client repositories):
$> zypper ar -f http://beta.suse.com/private/SUSE-Manager-beta/features/server-push/client-sles-11-sp2 manager-beta $> zypper dup --from manager-beta
The following client repositories with updated packages are available:
SLES 10 SP1-SP3 (noarch)
SLES 11 SP2 (noarch)
For SLES 11 SP1, the server push feature can be used with the regular (unpatched) client tools, but there is a bug leading to the client's hostname showing up as 'unknown' on the server (see Known Issues below).
We modified spacewalk-schema-upgrade in order to make it easier to fix failed schema upgrades.
The original idea was:
- search the upgrade path
- cat all migration files in the correct order into one big migration script
- run the script
If this script failed somewhere in the middle, the customer had to search for place where it failed, remove all statements before this point, fix the failing statement and run the script again.
The new script has a different approach:
- search the upgrade path
- create a migration directory and create symlinks in the correct order to the migration scripts
- run script by script. In case of a migration script run successfull, remove the symlink.
If the migration now failes, you can execute spacewalk-schema-upgrade again. It will find the unfinished migration and try to execute the missing scripts.
To fix a statement, you can go into the migration directory and change the first script (this was the one which failed).
The new spacewalk-schema-upgrade tells you how many migration scripts needs to be executed and the current number.
Tool to create bootstrap repositories
This beta has a new tool to create bootstrap repositories.
If you want to register a SLE client with SUSE Manager, but the required packages are not installed on the client, you need a repository that provides these packages.
Up until now, we used to deliver these repositories as RPMs on the SUSE Manager Server for the following distributions:
- SLE10 SP3/SP4
- SLE11 SP1
The bootstrap script then tries to add these repositories depending on a special structured path and installs the required tools automatically before the registration starts.
The new mgr-create-bootstrap-repo script should now replace the special RPMs. The mgr-create-bootstrap-repo script creates the repositories on the SUSE Manager server using the current RPMs from the synced channels.
#> mgr-create-bootstrap-repo -h Usage: mgr-create-bootstrap-repo [options] Options: -h, --help show this help message and exit -n, --dryrun Dry run. Show only changes - do not execute them -i, --interactive Interactive mode (default) -l, --list list available distributions -c CREATE, --create=CREATE create bootstrap repo for for given distribution label --datamodule=DATAMODULE Use an own datamodule (Default: mgr_bootstrap_data)
It enforces to uninstall the RPMs that currently provide these repositories, because it writes to the same paths.
This tool uses the official RPMs synced with mgr-ncc-sync. This means that you can only create repositories for distributions you have synced in SUSE Manager.
For compatibility reasons you should create a symlink susemanager-client-setup pointing to sle/11/1/bootstrap with:
$> cd /srv/www/htdocs/pub/repositories $> ln -s sle/11/1/bootstrap susemanager-client-setup
SSH Server Push
Please see the SSH Push page.
This feature is about syncing cobbler generated TFTP contents to SUSE Manager Proxies, to be able to perform PXE boot via these proxies.
On the SUSE Manager Server, install the package susemanager-tftpsync.
$> zypper install susemanager-tftpsync
On the SUSE Manager Proxy, install the package susemanager-tftpsync-recv.
$> zypper install susemanager-tftpsync-recv
Configure SUSE Manager Proxy
Execute configure-tftpsync.sh on SUSE Manager Proxy.
This setup script asks for hostnames and IP addresses of the SUSE Manager Server and of the proxy itself. Additionally, it asks for the tftpboot directory on the proxy.
See also the output of configure-tftpsync.sh --help.
Configure SUSE Manager Server
Execute configure-tftpsync.sh on SUSE Manager Server.
$> configure-tftpsync.sh proxy1.domain.top proxy2.domain.top
Finally execute "cobbler sync" to initially push the files to the proxies. This will succeed, if all listed proxies are correctly configured.
Note: You can call configure-tftpsync.sh to change the list of proxies. You always have to provide the full list of proxies.
Note: In case you reinstall an already configured proxy and want to push all files again you need to remove the cache file /var/lib/cobbler/pxe_cache.json before you call "cobbler sync" again.