Questions & Answers: Maintenance and migration between the cloud.
Maintenance Freiburg: Do I have to do it myself?[faq_maintenance_1]
This entry cannot cover all user actions! The following important points have been worked out from the experience of the last bwCloud conversions.
Users are responsible for backing up their own data!
Please check and observe the following points:
- Before maintenance, users must back up their Openstack objects (VMs, volumes, SSH keys, ...) of the Productive-bwCloud themselves. There are corresponding entries in the FAQ.
- After maintenance, users can upload data to the new Productive-bwCloud again.
- It is NOT possible to "carry over" an IP address when switching to a new version. The IP networks provided in the bwCloud Freiburg (IPv4 in the three forms: public, internal, public-extended and in future IPv6) are strictly separated for both compute clusters (Productive and Experimental bwCloud).
CLI, Freiburg Region, Maintenance
Maintenance Freiburg: How can I migrate my instance during the migration period?[faq_maintenance_2]
It is best to (1) use storage that is located outside the bwCloud Freiburg and (2) keep your instance state less. This means that your services and data are independent of maintenance.
For the sake of completeness, the following describes how to transform your instance from the Inactive bwCloud (idm02) to the Productive bwCloud (idm01) after maintenance.
- Connect to the bwCloud via CLI.
-
Download the image of your instance provided by us as described here.
Compare the list of your images with your instances:
$ openstack server list $ openstack image list - Then follow these instructions to upload the image to the new bwCloud.
Now you can create a VM / server as usual. Make sure that you select your image as the source when creating it.
Freiburg Region, Maintenance
