# then we get the flavor and image ID's along with the security and network information from the previous instance | ID | Name | Status | Networks | Image | Flavor | We use the create server command, adding the –volume flag: From here we need to create our new instance. availability-zone NZ-WLG-2 -type b1.standardĪt this point, we now have a volume that contains all of the information from description volume-from-ephemeral-shelved -bootable -os-project-id eac679e489614xxxxxxce29d755fe289 \ $ openstack volume create persistent-volume-bootable -size 20 -image aa1e6f8d-0689-4eaf-9a13-xxxxxxxxxxxx \ # then we execute the following command, changing the -image to be the ID of your snapshot. | aa1e6f8d-0689-4eaf-9a13-xxxxxxxxxxxx | ephemeral-instance-shelved | active | # Find the correct snapshot (replace 'ephemeral' with your instance name) Old files and you will be able to shelve your instance without creating Once your new instance is up and running you should be able to see all of your Make sure the the other options for your instance match your previous Volume should already be selected by default, but double check that this is Source, you use the volume as your source type and not an image. Then create a new instance making sure that when you arrive at picking a Launch as instance from your selected volume. Next, navigate to the volume section of the dashboard and click For this example our snapshot is named ‘Ephemeral-snapshot’.Ĭlick create volume and follow the steps to creating a volume from this This isĪutomatically created for you when you shelve your instance:Īfter this, navigate to the Images section of the dashboard and locate your The first thing that you will need is the snapshot of your instance.
We detail how toĬomplete this action, using both the dashboard and the command line, below: The easiest solution to this is creating a new instance that does not containĪn ephemeral volume using a snapshot from the old instance. Your volume, the instance will still make snapshots of the ephemeral side.
You could add a persistent volume to the instance, but this means you now haveīoth ephemeral and persistent storage. This in turn slows the process of booting the instance from its shelved state. Over time these start to stack up if you consistently shelve your instance. New snapshot that contains the incremental changes from the previous snapshot. But each time you shelve your instance you create a You shelve your instance the system creates a snapshot to keep your data fromīeing flushed and deleted. If you chose an ephemeral volume, whenever When creating an instance you have the option to attach a persistent volume Replacing ephemeral storage with a persistent volume ¶
0 kommentar(er)
