Difference between revisions of "SUSE Manager/SuseOpenstackCloud"

From MicroFocusInternationalWiki
Jump to: navigation, search
(written prerequisites)
(one section)
Line 13: Line 13:
  
 
The SUSE Manager Server must be reachable from the cloud's nodes, and its host name must match proper direct and reverse DNS entries (otherwise the SSL security will suspect a spoofing attempt).  
 
The SUSE Manager Server must be reachable from the cloud's nodes, and its host name must match proper direct and reverse DNS entries (otherwise the SSL security will suspect a spoofing attempt).  
 +
 +
== Steps on the SUSE Manager server ==
 +
Select '''Admin''' in the top menu and choose '''SUSE Products''' tab. Add '''SUSE Linux Enterprise Server 12 SP2''' channel for x86_64.
 +
# Press the cross on the left of this channel's name to show its child channels. Add '''SUSE OpenStack Cloud 7 x86_64''' child channel.
 +
# Wait for the synchronization of these two channels to end.
 +
# Select '''Systems''' on the top menu and choose '''Activation keys''' in left menu. If not done already, create a key for the SLES 12 SP2 channel by pressing "Create Key" on the top right. Name it '''1-sles-12-sp2'''.
 +
# Select the newly created activation key, and in the "Child Channels" tab, select all five channels (SLE-Manager-Tools12-Pool x86_64 SP2, SLE-Manager-Tools12-Updates x86_64 SP2, SLES12-SP2-Updates for x86_64, SUSE-OpenStack-Cloud-7-Pool for x86_64, and SUSE-OpenStack-Cloud-7-Updates for x86_64). Press '''Update Key''' button.
 +
# If not already done, create the tools repository for SLES12 SP2, by dropping to a command line and entering <tt>mgr-create-bootstrap-repo -c SLE-12-SP2-x86_64</tt> command.
 +
# If you have not created a bootstrap script template yet, do it now. Select '''Admin''' in the top menu, click '''SUSE Manager Configuration''' on left menu, and select '''Bootstrap Script''' tab. Press '''Update'''.
 +
# Drop to a command line and do <tt>cd /srv/www/htdocs/pub/bootstrap/</tt> then <tt>cp bootstrap.sh bootstrap-sles12-sp2.sh</tt>. Edit the newly created file to comment out line <tt>exit 1</tt> and to add the name of your activation key after <tt>ACTIVATION_KEYS=</tt>. At this point, you should have <tt># exit 1</tt> and <tt>ACTIVATION_KEYS=1-sles-12-sp2<tt> in that file.
 +
# Check that everything looks fine by opening in a web browser the URL '''<nowiki>https://yourserver.example.com/pub/</nowiki>''' (replace the server name by the hostname of your SUSE Manager server). You should see there two folders, '''bootstrap/''' and '''repositories/''', plus a file named '''rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm'''. When opening the '''bootstrap/''' folder, you should see the bootstrap script '''bootstrap-sles12-sp2.sh''' you just created.
  
  
 
(to be written)
 
(to be written)

Revision as of 17:06, 13 January 2017

SUSE Manager Main Page

Managing SUSE Openstack Cloud nodes with SUSE Manager

There is a barclamp for SUSE Openstack Cloud (SOC) that enables to register your cloud nodes (including the cloud's admin node!) inside SUSE Manager. This barclamp is called "SUSE Manager Client" and is part of the crowbar barclamps.

The instructions below have been tested with Cloud 7 development version (milestone 7) and SUSE Manager 3.0.3. SUSE Manager 3.0.3 is the minimal version for using Cloud 7. There are other valid version combinations of SUSE Openstack Cloud and SUSE Manager.

Prerequisites

You must have installed:

  • SUSE Openstack Cloud 7
  • SUSE Manager Server 3.0.3

The SUSE Manager Server must be reachable from the cloud's nodes, and its host name must match proper direct and reverse DNS entries (otherwise the SSL security will suspect a spoofing attempt).

Steps on the SUSE Manager server

Select Admin in the top menu and choose SUSE Products tab. Add SUSE Linux Enterprise Server 12 SP2 channel for x86_64.

  1. Press the cross on the left of this channel's name to show its child channels. Add SUSE OpenStack Cloud 7 x86_64 child channel.
  2. Wait for the synchronization of these two channels to end.
  3. Select Systems on the top menu and choose Activation keys in left menu. If not done already, create a key for the SLES 12 SP2 channel by pressing "Create Key" on the top right. Name it 1-sles-12-sp2.
  4. Select the newly created activation key, and in the "Child Channels" tab, select all five channels (SLE-Manager-Tools12-Pool x86_64 SP2, SLE-Manager-Tools12-Updates x86_64 SP2, SLES12-SP2-Updates for x86_64, SUSE-OpenStack-Cloud-7-Pool for x86_64, and SUSE-OpenStack-Cloud-7-Updates for x86_64). Press Update Key button.
  5. If not already done, create the tools repository for SLES12 SP2, by dropping to a command line and entering mgr-create-bootstrap-repo -c SLE-12-SP2-x86_64 command.
  6. If you have not created a bootstrap script template yet, do it now. Select Admin in the top menu, click SUSE Manager Configuration on left menu, and select Bootstrap Script tab. Press Update.
  7. Drop to a command line and do cd /srv/www/htdocs/pub/bootstrap/ then cp bootstrap.sh bootstrap-sles12-sp2.sh. Edit the newly created file to comment out line exit 1 and to add the name of your activation key after ACTIVATION_KEYS=. At this point, you should have # exit 1 and ACTIVATION_KEYS=1-sles-12-sp2<tt> in that file.
  8. Check that everything looks fine by opening in a web browser the URL https://yourserver.example.com/pub/ (replace the server name by the hostname of your SUSE Manager server). You should see there two folders, bootstrap/ and repositories/, plus a file named rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm. When opening the bootstrap/ folder, you should see the bootstrap script bootstrap-sles12-sp2.sh you just created.


(to be written)