117117 </variablelist >
118118 </sect1 >
119119 <sect1 id =" sec.depl.maintenance.upgrade" >
120- <title >Upgrading from &productname; 3 to &productname; 4 </title >
120+ <title >Upgrading from &productname; 5 to &productname; 5 </title >
121121
122122 <para >
123- Upgrading from &productname; 3 to &productname; 4 is supported, with the
123+ Upgrading from &productname; 4 to &productname; 5 is supported, with the
124124 following manual steps. However, note that it will turn off the
125125 &ostack; cloud during the upgrade and it is not possible to downgrade back
126126 to &productname; 3 in case of a regression or problem. It is highly
155155 Upgrade
156156 </title >
157157 <para >
158- As of &productname; 4 , HyperV Nodes need to be re-installed after the
158+ As of &productname; 5 , HyperV Nodes need to be re-installed after the
159159 upgrade procedure. This re-installation will overwrite the instance's data
160160 and therefore they will be lost. &kvm; , VMWare and &xen; instances are not
161161 affected.
162162 </para >
163163 </important >
164164
165165 <procedure >
166- <title > Upgrading &productname; 3 to 4 </title >
166+ <title > Upgrading &productname; 4 to 5 </title >
167167 <step >
168168 <para >
169- Make sure to subscribe to the SUSE Cloud 4 Pool and Update channels on
169+ Make sure to subscribe to the SUSE Cloud 5 Pool and Update channels on
170170 the source that provides these channels for your &cloud; installation
171171 (for example an ⪪ or &susemgr; server).
172172 </para >
173173 <para >
174174 In case the channels are provided by an ⪪ server (either remote or on
175175 the &admserv; itself), refer to <xref
176176 linkend =" sec.depl.inst.admserv.post.smt_repos" /> for instructions on
177- subscribing to the &cloud; 4 channels.
177+ subscribing to the &cloud; 5 channels.
178178 </para >
179179 </step >
180180 <step >
181181 <para >
182182 Update the &productname; product repository on the &admserv; . To do so,
183- insert the &productname; 4 DVD and run the following commands:
183+ insert the &productname; 5 DVD and run the following commands:
184184 </para >
185185 <screen >mount /dev/dvd /mnt
186186rsync -avP --delete /mnt/ /srv/tftpboot/repos/Cloud/
@@ -192,28 +192,28 @@ umount /mnt</screen>
192192 </para >
193193 <para >
194194 If you are using external URLs (for example from an external ⪪ or
195- &susemgr; server) for the SUSE Cloud 3 Pool and Update repositories,
195+ &susemgr; server) for the SUSE Cloud 4 Pool and Update repositories,
196196 you need to update the file
197197 <filename >/etc/crowbar/provisioner.json</filename >. Open it in an editor
198198 and Search for the <menuchoice > <guimenu >suse</guimenu >
199199 <guimenu >autoyast</guimenu > <guimenu >repos</guimenu ></menuchoice >
200- entry. Replace the URLs pointing to the &productname; 3 Pool and Update
201- repositories with the ones pointing to version 4 . Also change the name of
202- these repositories to SUSE-Cloud-4 -Pool and SUSE-Cloud-4 -Updates,
200+ entry. Replace the URLs pointing to the &productname; 4 Pool and Update
201+ repositories with the ones pointing to version 5 . Also change the name of
202+ these repositories to SUSE-Cloud-5 -Pool and SUSE-Cloud-5 -Updates,
203203 respectively.
204204 </para >
205205 <para >
206206 In case you are using an ⪪ server installed on the &admserv; , run the
207207 following commands to make the repositories available for &cloud; :
208208 </para >
209- <screen >for REPO in SUSE-Cloud-4 -{Pool,Updates}; do
209+ <screen >for REPO in SUSE-Cloud-5 -{Pool,Updates}; do
210210ln -s /srv/www/htdocs/repo/\$RCE/$REPO/sle-11-x86_64 /srv/tftpboot/repos/${REPO}
211211done</screen >
212212 </step >
213213 <step >
214214 <para >
215- Now you need to replace the &productname; 3 Pool and Update
216- repositories used by the &admserv; with the ones for version 4 . Modify
215+ Now you need to replace the &productname; 4 Pool and Update
216+ repositories used by the &admserv; with the ones for version 5 . Modify
217217 the repository configuration by running <menuchoice >
218218 <guimenu >&yast; </guimenu > <guimenu >Software</guimenu > <guimenu >Software
219219 Repositories</guimenu ></menuchoice > on the &admserv; .
@@ -235,14 +235,14 @@ zypper install suse-cloud-upgrade</screen>
235235 Web interface. In case the command fails, contact the &suse;
236236 support (see <xref linkend =" sec.depl.trouble.support" /> for more
237237 information). At this point of the upgrade workflow it is still possible
238- to go back to version 3 .
238+ to go back to version 4 .
239239 </para >
240240 </step >
241241 <step >
242242 <para >
243243 Update all packages on the &admserv; by running <command >zypper
244244 <option >up</option ></command >. During the update process you will need to
245- accept the &productname; 4 EULA.
245+ accept the &productname; 5 EULA.
246246 </para >
247247 </step >
248248 <step >
@@ -252,7 +252,7 @@ zypper install suse-cloud-upgrade</screen>
252252 the command fails, contact the &suse; support (see <xref
253253 linkend =" sec.depl.trouble.support" /> for more information). From this
254254 point in the installation workflow on it is no longer possible to go back
255- to version 3 .
255+ to version 4 .
256256 </para >
257257 </step >
258258 <step >
@@ -491,7 +491,7 @@ done</screen>
491491 <title >Backing Up and Restoring the &admserv; </title >
492492 <para >As an example of how to back up and restore the data on the
493493 &admserv; , a <filename >crowbar-backup</filename > script is shipped with
494- &productname; 4 . </para >
494+ &productname; 5 . </para >
495495 <warning >
496496 <title >No Support for <filename >crowbar-backup</filename ></title >
497497 <para >The script serves as a functioning <emphasis >example</emphasis > of how
0 commit comments