From 54798b0134a53b4301fe9d04d5be58150a5b8c9f Mon Sep 17 00:00:00 2001 From: Dirk Mueller Date: Mon, 8 Sep 2014 13:27:55 +0000 Subject: [PATCH] Replace all references of Cloud3/4 with Cloud4/5 git-svn-id: http://svn.suse.de/svn/doc/trunk/cloud/en@59509 2463f871-af05-0410-bd21-ebfa852e3ce4 --- xml/depl_inst_admin.xml | 38 +++++++++++++++++++------------------- xml/depl_inst_nodes.xml | 4 ++-- xml/depl_maintenance.xml | 36 ++++++++++++++++++------------------ xml/depl_require.xml | 4 ++-- 4 files changed, 41 insertions(+), 41 deletions(-) diff --git a/xml/depl_inst_admin.xml b/xml/depl_inst_admin.xml index 6124bc82f..f670032c9 100644 --- a/xml/depl_inst_admin.xml +++ b/xml/depl_inst_admin.xml @@ -765,7 +765,7 @@ title="Profiling step"?> to have registered both products in &ncc;. Run the following commands as user &rootuser; on the ⪪ server: -for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-4-{Pool,Updates}; do +for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-5-{Pool,Updates}; do smt-repos $REPO sle-11-x86_64 -e done smt-mirror -L /var/log/smt/smt-mirror.log @@ -831,24 +831,24 @@ smt-mirror -L /var/log/smt/smt-mirror_ha.log - SUSE-Cloud-4-Pool + SUSE-Cloud-5-Pool - /srv/www/htdocs/repo/$RCE/SUSE-Cloud-4-Pool/sle-11-x86_64 + /srv/www/htdocs/repo/$RCE/SUSE-Cloud-5-Pool/sle-11-x86_64 - SUSE-Cloud-4-Updates + SUSE-Cloud-5-Updates - /srv/www/htdocs/repo/$RCE/SUSE-Cloud-4-Updates/sle-11-x86_64 + /srv/www/htdocs/repo/$RCE/SUSE-Cloud-5-Updates/sle-11-x86_64 @@ -982,7 +982,7 @@ smt-mirror -L /var/log/smt/smt-mirror_ha.log - Cloud 4 Product + Cloud 5 Product @@ -1051,7 +1051,7 @@ mount -t nfs nfs.&exampledomain;:/exports/SUSE-CLOU/DVD1/ mount -o loop /local/SLES-11-SP3-DVD-x86_64-DVD1.iso /srv/tftpboot/suse-11.3/install -mount -o loop /local/SUSE-CLOUD-4-DVD1.iso /srv/tftpboot/repos/Cloud +mount -o loop /local/SUSE-CLOUD-5-DVD1.iso /srv/tftpboot/repos/Cloud To automatically mount these directories either create entries in /etc/fstab or set up the automounter. @@ -1118,24 +1118,24 @@ mount -o loop /local/SUSE-CLOUD-4-DVD1.iso /srv/tftpb - SUSE-Cloud-4-Pool + SUSE-Cloud-5-Pool - /srv/tftpboot/repos/SUSE-Cloud-4-Pool + /srv/tftpboot/repos/SUSE-Cloud-5-Pool - SUSE-Cloud-4-Updates + SUSE-Cloud-5-Updates - /srv/tftpboot/repos/SUSE-Cloud-4-Updates + /srv/tftpboot/repos/SUSE-Cloud-5-Updates @@ -1209,7 +1209,7 @@ mount -o loop /local/SUSE-CLOUD-4-DVD1.iso /srv/tftpb In order to use repositories from a remote ⪪ server to deploy &cloud; you first need to make sure the products &sls; 11 SP3 and - Cloud 4 are registered and the corresponding channels are mirrored + Cloud 5 are registered and the corresponding channels are mirrored in ⪪. Now you need to enter the repository URLs on the Repositories tab in the &yast; &crow; module as described in /local/SUSE-CLOUD-4-DVD1.iso /srv/tftpb http://smt.&exampledomain;/repo/\$RCE/SLES11-SP3-Pool/sle-11-x86_64/ http://smt.&exampledomain;/repo/\$RCE/SLES11-SP3-Updates/sle-11-x86_64/ - http://smt.&exampledomain;/repo/\$RCE/SUSE-Cloud-4-Pool/sle-11-x86_64/ - http://smt.&exampledomain;/repo/\$RCE/SUSE-Cloud-4-Updates/sle-11-x86_64/ + http://smt.&exampledomain;/repo/\$RCE/SUSE-Cloud-5-Pool/sle-11-x86_64/ + http://smt.&exampledomain;/repo/\$RCE/SUSE-Cloud-5-Updates/sle-11-x86_64/ For the optional &hasetup; you also need the &ha; repositories: @@ -1251,7 +1251,7 @@ mount -o loop /local/SUSE-CLOUD-4-DVD1.iso /srv/tftpb Link the repositories mirrored by ⪪ to /srv/tftpboot: -for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-4-{Pool,Updates}; do +for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-5-{Pool,Updates}; do ln -s /srv/www/htdocs/repo/\$RCE/$REPO/sle-11-x86_64 /srv/tftpboot/repos/${REPO} done @@ -1309,7 +1309,7 @@ done - SUSE-Cloud-4-Pool + SUSE-Cloud-5-Pool http://manager.&exampledomain;/ks/dist/child/suse-cloud-4-pool-x86_64/sles11-sp3-x86_64/ @@ -1317,7 +1317,7 @@ done - SUSE-Cloud-4-Updates + SUSE-Cloud-5-Updates http://manager.&exampledomain;/ks/dist/child/suse-cloud-4-updates-x86_64/sles11-sp3-x86_64/ @@ -1386,7 +1386,7 @@ done &admserv;. This command will pull the files from a host named host.&exampledomain;: -for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-4-{Pool,Updates}; do +for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-5-{Pool,Updates}; do rsync -avPz host.&exampledomain;:/srv/www/htdocs/repo/\\\$RCE/$REPO/sle-11-x86_64/ \ /srv/tftpboot/repos/${REPO}/ done @@ -1403,7 +1403,7 @@ done address 192.168.124.10 in the following example): - for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-4-{Pool,Updates}; do + for REPO in SLES11-SP3-{Pool,Updates} SUSE-Cloud-5-{Pool,Updates}; do rsync -avPz /srv/www/htdocs/repo/\\\$RCE/$REPO/sle-11-x86_64/ \ 192.168.124.10:/srv/tftpboot/repos/${REPO}/ done diff --git a/xml/depl_inst_nodes.xml b/xml/depl_inst_nodes.xml index 12557b9ae..1fc170f5d 100644 --- a/xml/depl_inst_nodes.xml +++ b/xml/depl_inst_nodes.xml @@ -660,8 +660,8 @@ title="Profiling step"?> To enable the &susemgr; server to manage the &cloud; nodes, the - respective &productname; &productnumber; channels (SUSE-Cloud-4-Pool, - SUSE-Cloud-4-Updates) need to be available on the server. It also + respective &productname; &productnumber; channels (SUSE-Cloud-5-Pool, + SUSE-Cloud-5-Updates) need to be available on the server. It also requires to generate an Activation Key for &cloud;. diff --git a/xml/depl_maintenance.xml b/xml/depl_maintenance.xml index 60bd45712..4077013d0 100644 --- a/xml/depl_maintenance.xml +++ b/xml/depl_maintenance.xml @@ -117,10 +117,10 @@ - Upgrading from &productname; 3 to &productname; 4 + Upgrading from &productname; 5 to &productname; 5 - Upgrading from &productname; 3 to &productname; 4 is supported, with the + Upgrading from &productname; 4 to &productname; 5 is supported, with the following manual steps. However, note that it will turn off the &ostack; cloud during the upgrade and it is not possible to downgrade back to &productname; 3 in case of a regression or problem. It is highly @@ -155,7 +155,7 @@ Upgrade - As of &productname; 4, HyperV Nodes need to be re-installed after the + As of &productname; 5, HyperV Nodes need to be re-installed after the upgrade procedure. This re-installation will overwrite the instance's data and therefore they will be lost. &kvm;, VMWare and &xen; instances are not affected. @@ -163,10 +163,10 @@ - Upgrading &productname; 3 to 4 + Upgrading &productname; 4 to 5 - Make sure to subscribe to the SUSE Cloud 4 Pool and Update channels on + Make sure to subscribe to the SUSE Cloud 5 Pool and Update channels on the source that provides these channels for your &cloud; installation (for example an ⪪ or &susemgr; server). @@ -174,13 +174,13 @@ In case the channels are provided by an ⪪ server (either remote or on the &admserv; itself), refer to for instructions on - subscribing to the &cloud; 4 channels. + subscribing to the &cloud; 5 channels. Update the &productname; product repository on the &admserv;. To do so, - insert the &productname; 4 DVD and run the following commands: + insert the &productname; 5 DVD and run the following commands: mount /dev/dvd /mnt rsync -avP --delete /mnt/ /srv/tftpboot/repos/Cloud/ @@ -192,28 +192,28 @@ umount /mnt If you are using external URLs (for example from an external ⪪ or - &susemgr; server) for the SUSE Cloud 3 Pool and Update repositories, + &susemgr; server) for the SUSE Cloud 4 Pool and Update repositories, you need to update the file /etc/crowbar/provisioner.json. Open it in an editor and Search for the suse autoyast repos - entry. Replace the URLs pointing to the &productname; 3 Pool and Update - repositories with the ones pointing to version 4. Also change the name of - these repositories to SUSE-Cloud-4-Pool and SUSE-Cloud-4-Updates, + entry. Replace the URLs pointing to the &productname; 4 Pool and Update + repositories with the ones pointing to version 5. Also change the name of + these repositories to SUSE-Cloud-5-Pool and SUSE-Cloud-5-Updates, respectively. In case you are using an ⪪ server installed on the &admserv;, run the following commands to make the repositories available for &cloud;: - for REPO in SUSE-Cloud-4-{Pool,Updates}; do + for REPO in SUSE-Cloud-5-{Pool,Updates}; do ln -s /srv/www/htdocs/repo/\$RCE/$REPO/sle-11-x86_64 /srv/tftpboot/repos/${REPO} done - Now you need to replace the &productname; 3 Pool and Update - repositories used by the &admserv; with the ones for version 4. Modify + Now you need to replace the &productname; 4 Pool and Update + repositories used by the &admserv; with the ones for version 5. Modify the repository configuration by running &yast; Software Software Repositories on the &admserv;. @@ -235,14 +235,14 @@ zypper install suse-cloud-upgrade Web interface. In case the command fails, contact the &suse; support (see for more information). At this point of the upgrade workflow it is still possible - to go back to version 3. + to go back to version 4. Update all packages on the &admserv; by running zypper . During the update process you will need to - accept the &productname; 4 EULA. + accept the &productname; 5 EULA. @@ -252,7 +252,7 @@ zypper install suse-cloud-upgrade the command fails, contact the &suse; support (see for more information). From this point in the installation workflow on it is no longer possible to go back - to version 3. + to version 4. @@ -491,7 +491,7 @@ done Backing Up and Restoring the &admserv; As an example of how to back up and restore the data on the &admserv;, a crowbar-backup script is shipped with - &productname; 4. + &productname; 5. No Support for <filename>crowbar-backup</filename> The script serves as a functioning example of how diff --git a/xml/depl_require.xml b/xml/depl_require.xml index 62008fad6..921dbd38e 100644 --- a/xml/depl_require.xml +++ b/xml/depl_require.xml @@ -816,7 +816,7 @@ - SLES11-SP3-Pool and SUSE-Cloud-4-Pool + SLES11-SP3-Pool and SUSE-Cloud-5-Pool The &sls; and &productname; repositories containing all binary RPMs from @@ -830,7 +830,7 @@ - SLES11-SP3-Updates and SUSE-Cloud-4-Updates + SLES11-SP3-Updates and SUSE-Cloud-5-Updates These repositories contain maintenance updates to packages in the