[Starlingx-discuss] Delete snapshot and volume
Hi, The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from the Volume and finally an Instance should be launch from the Snapshot. The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot. Is this behavior correct? Those are the commands I used: openstack image create --disk-format qcow2 --file /home/wrsroot/cirros-0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility-zone nova vm-cirros 1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instructions Regards. Juan Carlos Alonso
Hello, Does anybody has faced the same behavior? I am wondering if it is possible to delete a snapshot, or not, when an instance is up and running. In my site, I could, but need to know if this is correct or not. Regards. Juan Carlos Alonso From: Alonso, Juan Carlos Sent: Tuesday, October 16, 2018 3:14 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Delete snapshot and volume Hi, The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from the Volume and finally an Instance should be launch from the Snapshot. The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot. Is this behavior correct? Those are the commands I used: openstack image create --disk-format qcow2 --file /home/wrsroot/cirros-0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility-zone nova vm-cirros 1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instructions Regards. Juan Carlos Alonso
Hi Juan Carlos, I had inquired internally at WR. My current understanding is that one does not "launch an instance from a volume snapshot", except in the form presented by Horizon interface. In that case, the behaviour of Horizon form is to create a volume from volume snapshot and launch the instance from the new volume. In your email you listed CLI commands and the command you listed showed that you launched the instance from volume, not from volume snapshot. So there's no reason to believe the volume snapshot should be locked from deletion. Moreover, it doesn't make sense for an instance to run from a volume snapshot - that's not what a snapshot is. The snapshot itself should be a static thing. You could probably have used the "openstack volume create --snapshot ..." command option to create a volume from volume snapshot, and then launch an instance from the new volume. The volume snapshot in this case would not be locked from deletion, neither the original volume from which the snapshot was based, but only the new volume you created. I hope this information is accurate and helpful :) I'll forward the response to the guys I inquired with, and they can correct me here if anything I wrote is amiss. M On 2018-10-17 11:47 a.m., Alonso, Juan Carlos wrote:
Hello,
Does anybody has faced the same behavior? I am wondering if it is possible to delete a snapshot, or not, when an instance is up and running. In my site, I could, but need to know if this is correct or not.
Regards. Juan Carlos Alonso
From: Alonso, Juan Carlos Sent: Tuesday, October 16, 2018 3:14 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Delete snapshot and volume
Hi,
The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from the Volume and finally an Instance should be launch from the Snapshot. The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot.
Is this behavior correct?
Those are the commands I used:
openstack image create --disk-format qcow2 --file /home/wrsroot/cirros-0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility-zone nova vm-cirros
1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instructions
Regards. Juan Carlos Alonso
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I was able to delete the snapshot even when 2 instances were launched from there following below steps: === $ openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros $ openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol $ openstack volume snapshot create --name cirros-snap cirros-vol $ nova boot --flavor <flavor> --snapshot <snapshot-id> --nic net-id=<net_id> <instance-name> $ openstack snapshot delete cirros-snap === So seems like the snapshot is not directly linked to the instance created. Regards, José
-----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 11:22 AM To: Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx- discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume
Hi Juan Carlos,
I had inquired internally at WR.
My current understanding is that one does not "launch an instance from a volume snapshot", except in the form presented by Horizon interface. In that case, the behaviour of Horizon form is to create a volume from volume snapshot and launch the instance from the new volume.
In your email you listed CLI commands and the command you listed showed that you launched the instance from volume, not from volume snapshot. So there's no reason to believe the volume snapshot should be locked from deletion.
Moreover, it doesn't make sense for an instance to run from a volume snapshot - that's not what a snapshot is. The snapshot itself should be a static thing. You could probably have used the "openstack volume create --snapshot ..." command option to create a volume from volume snapshot, and then launch an instance from the new volume. The volume snapshot in this case would not be locked from deletion, neither the original volume from which the snapshot was based, but only the new volume you created.
I hope this information is accurate and helpful :) I'll forward the response to the guys I inquired with, and they can correct me here if anything I wrote is amiss.
M
Hello,
Does anybody has faced the same behavior? I am wondering if it is possible to delete a snapshot, or not, when an instance is up and running. In my site, I could, but need to know if this is correct or not.
Regards. Juan Carlos Alonso
From: Alonso, Juan Carlos Sent: Tuesday, October 16, 2018 3:14 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Delete snapshot and volume
Hi,
The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from
On 2018-10-17 11:47 a.m., Alonso, Juan Carlos wrote: the Volume and finally an Instance should be launch from the Snapshot.
The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot.
Is this behavior correct?
Those are the commands I used:
openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility- zone nova vm-cirros
1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instructions
Regards. Juan Carlos Alonso
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi José, Thanks for the nova boot command. I see that "nova boot --snapshot" also creates a new volume and launches the instance from the new volume. I agree that the snapshot is not in use by the instance. The "openstack server show" and "nova show" commands list the new volume created. M On 2018-10-17 12:48 p.m., Perez Carranza, Jose wrote:
I was able to delete the snapshot even when 2 instances were launched from there following below steps:
=== $ openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros $ openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol $ openstack volume snapshot create --name cirros-snap cirros-vol $ nova boot --flavor <flavor> --snapshot <snapshot-id> --nic net-id=<net_id> <instance-name> $ openstack snapshot delete cirros-snap ===
So seems like the snapshot is not directly linked to the instance created.
Regards, José
-----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 11:22 AM To: Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx- discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume
Hi Juan Carlos,
I had inquired internally at WR.
My current understanding is that one does not "launch an instance from a volume snapshot", except in the form presented by Horizon interface. In that case, the behaviour of Horizon form is to create a volume from volume snapshot and launch the instance from the new volume.
In your email you listed CLI commands and the command you listed showed that you launched the instance from volume, not from volume snapshot. So there's no reason to believe the volume snapshot should be locked from deletion.
Moreover, it doesn't make sense for an instance to run from a volume snapshot - that's not what a snapshot is. The snapshot itself should be a static thing. You could probably have used the "openstack volume create --snapshot ..." command option to create a volume from volume snapshot, and then launch an instance from the new volume. The volume snapshot in this case would not be locked from deletion, neither the original volume from which the snapshot was based, but only the new volume you created.
I hope this information is accurate and helpful :) I'll forward the response to the guys I inquired with, and they can correct me here if anything I wrote is amiss.
M
Hello,
Does anybody has faced the same behavior? I am wondering if it is possible to delete a snapshot, or not, when an instance is up and running. In my site, I could, but need to know if this is correct or not.
Regards. Juan Carlos Alonso
From: Alonso, Juan Carlos Sent: Tuesday, October 16, 2018 3:14 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Delete snapshot and volume
Hi,
The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from
On 2018-10-17 11:47 a.m., Alonso, Juan Carlos wrote: the Volume and finally an Instance should be launch from the Snapshot.
The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot. Is this behavior correct?
Those are the commands I used:
openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility- zone nova vm-cirros
1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instructions Regards. Juan Carlos Alonso
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi, I tested again based on your feedback and I could check that the snapshot created from the volume, create another volume for each instance launched. Such new volume is used for the instance, so the original volume and snapshot can be deleted without no problems, as Jose said they are not linked to the instance. Thank you for your help. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 12:15 PM To: Perez Carranza, Jose <jose.perez.carranza@intel.com>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume Hi José, Thanks for the nova boot command. I see that "nova boot --snapshot" also creates a new volume and launches the instance from the new volume. I agree that the snapshot is not in use by the instance. The "openstack server show" and "nova show" commands list the new volume created. M On 2018-10-17 12:48 p.m., Perez Carranza, Jose wrote:
I was able to delete the snapshot even when 2 instances were launched from there following below steps:
=== $ openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros $ openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol $ openstack volume snapshot create --name cirros-snap cirros-vol $ nova boot --flavor <flavor> --snapshot <snapshot-id> --nic net-id=<net_id> <instance-name> $ openstack snapshot delete cirros-snap ===
So seems like the snapshot is not directly linked to the instance created.
Regards, José
-----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 11:22 AM To: Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx- discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume
Hi Juan Carlos,
I had inquired internally at WR.
My current understanding is that one does not "launch an instance from a volume snapshot", except in the form presented by Horizon interface. In that case, the behaviour of Horizon form is to create a volume from volume snapshot and launch the instance from the new volume.
In your email you listed CLI commands and the command you listed showed that you launched the instance from volume, not from volume snapshot. So there's no reason to believe the volume snapshot should be locked from deletion.
Moreover, it doesn't make sense for an instance to run from a volume snapshot - that's not what a snapshot is. The snapshot itself should be a static thing. You could probably have used the "openstack volume create --snapshot ..." command option to create a volume from volume snapshot, and then launch an instance from the new volume. The volume snapshot in this case would not be locked from deletion, neither the original volume from which the snapshot was based, but only the new volume you created.
I hope this information is accurate and helpful :) I'll forward the response to the guys I inquired with, and they can correct me here if anything I wrote is amiss.
M
On 2018-10-17 11:47 a.m., Alonso, Juan Carlos wrote:
Hello,
Does anybody has faced the same behavior? I am wondering if it is possible to delete a snapshot, or not, when an instance is up and running. In my site, I could, but need to know if this is correct or not.
Regards. Juan Carlos Alonso
From: Alonso, Juan Carlos Sent: Tuesday, October 16, 2018 3:14 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Delete snapshot and volume
Hi,
The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from the Volume and finally an Instance should be launch from the Snapshot. The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot. Is this behavior correct?
Those are the commands I used:
openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility- zone nova vm-cirros
1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instru ctions Regards. Juan Carlos Alonso
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Juan, openstack volume snapshot create does not have a --name parameter so your example will not run. It does have a --volume parameter but then the order of names is reversed: openstack volume snapshot create --volume cirros-vol cirros-snap Regards, Daniel Badea ________________________________________ From: Alonso, Juan Carlos [juan.carlos.alonso@intel.com] Sent: Wednesday, October 17, 2018 20:30 To: Thebeau, Michel; Perez Carranza, Jose; 'starlingx-discuss@lists.starlingx.io' Subject: Re: [Starlingx-discuss] Delete snapshot and volume Hi, I tested again based on your feedback and I could check that the snapshot created from the volume, create another volume for each instance launched. Such new volume is used for the instance, so the original volume and snapshot can be deleted without no problems, as Jose said they are not linked to the instance. Thank you for your help. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 12:15 PM To: Perez Carranza, Jose <jose.perez.carranza@intel.com>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume Hi José, Thanks for the nova boot command. I see that "nova boot --snapshot" also creates a new volume and launches the instance from the new volume. I agree that the snapshot is not in use by the instance. The "openstack server show" and "nova show" commands list the new volume created. M On 2018-10-17 12:48 p.m., Perez Carranza, Jose wrote:
I was able to delete the snapshot even when 2 instances were launched from there following below steps:
=== $ openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros $ openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol $ openstack volume snapshot create --name cirros-snap cirros-vol $ nova boot --flavor <flavor> --snapshot <snapshot-id> --nic net-id=<net_id> <instance-name> $ openstack snapshot delete cirros-snap ===
So seems like the snapshot is not directly linked to the instance created.
Regards, José
-----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 11:22 AM To: Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx- discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume
Hi Juan Carlos,
I had inquired internally at WR.
My current understanding is that one does not "launch an instance from a volume snapshot", except in the form presented by Horizon interface. In that case, the behaviour of Horizon form is to create a volume from volume snapshot and launch the instance from the new volume.
In your email you listed CLI commands and the command you listed showed that you launched the instance from volume, not from volume snapshot. So there's no reason to believe the volume snapshot should be locked from deletion.
Moreover, it doesn't make sense for an instance to run from a volume snapshot - that's not what a snapshot is. The snapshot itself should be a static thing. You could probably have used the "openstack volume create --snapshot ..." command option to create a volume from volume snapshot, and then launch an instance from the new volume. The volume snapshot in this case would not be locked from deletion, neither the original volume from which the snapshot was based, but only the new volume you created.
I hope this information is accurate and helpful :) I'll forward the response to the guys I inquired with, and they can correct me here if anything I wrote is amiss.
M
On 2018-10-17 11:47 a.m., Alonso, Juan Carlos wrote:
Hello,
Does anybody has faced the same behavior? I am wondering if it is possible to delete a snapshot, or not, when an instance is up and running. In my site, I could, but need to know if this is correct or not.
Regards. Juan Carlos Alonso
From: Alonso, Juan Carlos Sent: Tuesday, October 16, 2018 3:14 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Delete snapshot and volume
Hi,
The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from the Volume and finally an Instance should be launch from the Snapshot. The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot. Is this behavior correct?
Those are the commands I used:
openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility- zone nova vm-cirros
1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instru ctions Regards. Juan Carlos Alonso
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Daniel, Yes, you right, I made a mistake when write the commands on this email. The command I used was: "openstack snapshot create --name <snapshot_name> <volume_name>", but seems that such command has been deprecated or will be. Command you mention should be used now. Regards. Juan Carlos Alonso -----Original Message----- From: Badea, Daniel [mailto:Daniel.Badea@windriver.com] Sent: Wednesday, October 17, 2018 1:21 PM To: Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Thebeau, Michel <Michel.Thebeau@windriver.com>; Perez Carranza, Jose <jose.perez.carranza@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] Delete snapshot and volume Hi Juan, openstack volume snapshot create does not have a --name parameter so your example will not run. It does have a --volume parameter but then the order of names is reversed: openstack volume snapshot create --volume cirros-vol cirros-snap Regards, Daniel Badea ________________________________________ From: Alonso, Juan Carlos [juan.carlos.alonso@intel.com] Sent: Wednesday, October 17, 2018 20:30 To: Thebeau, Michel; Perez Carranza, Jose; 'starlingx-discuss@lists.starlingx.io' Subject: Re: [Starlingx-discuss] Delete snapshot and volume Hi, I tested again based on your feedback and I could check that the snapshot created from the volume, create another volume for each instance launched. Such new volume is used for the instance, so the original volume and snapshot can be deleted without no problems, as Jose said they are not linked to the instance. Thank you for your help. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 12:15 PM To: Perez Carranza, Jose <jose.perez.carranza@intel.com>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume Hi José, Thanks for the nova boot command. I see that "nova boot --snapshot" also creates a new volume and launches the instance from the new volume. I agree that the snapshot is not in use by the instance. The "openstack server show" and "nova show" commands list the new volume created. M On 2018-10-17 12:48 p.m., Perez Carranza, Jose wrote:
I was able to delete the snapshot even when 2 instances were launched from there following below steps:
=== $ openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros $ openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol $ openstack volume snapshot create --name cirros-snap cirros-vol $ nova boot --flavor <flavor> --snapshot <snapshot-id> --nic net-id=<net_id> <instance-name> $ openstack snapshot delete cirros-snap ===
So seems like the snapshot is not directly linked to the instance created.
Regards, José
-----Original Message----- From: Michel Thebeau [mailto:michel.thebeau@windriver.com] Sent: Wednesday, October 17, 2018 11:22 AM To: Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; 'starlingx- discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Delete snapshot and volume
Hi Juan Carlos,
I had inquired internally at WR.
My current understanding is that one does not "launch an instance from a volume snapshot", except in the form presented by Horizon interface. In that case, the behaviour of Horizon form is to create a volume from volume snapshot and launch the instance from the new volume.
In your email you listed CLI commands and the command you listed showed that you launched the instance from volume, not from volume snapshot. So there's no reason to believe the volume snapshot should be locked from deletion.
Moreover, it doesn't make sense for an instance to run from a volume snapshot - that's not what a snapshot is. The snapshot itself should be a static thing. You could probably have used the "openstack volume create --snapshot ..." command option to create a volume from volume snapshot, and then launch an instance from the new volume. The volume snapshot in this case would not be locked from deletion, neither the original volume from which the snapshot was based, but only the new volume you created.
I hope this information is accurate and helpful :) I'll forward the response to the guys I inquired with, and they can correct me here if anything I wrote is amiss.
M
On 2018-10-17 11:47 a.m., Alonso, Juan Carlos wrote:
Hello,
Does anybody has faced the same behavior? I am wondering if it is possible to delete a snapshot, or not, when an instance is up and running. In my site, I could, but need to know if this is correct or not.
Regards. Juan Carlos Alonso
From: Alonso, Juan Carlos Sent: Tuesday, October 16, 2018 3:14 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Delete snapshot and volume
Hi,
The test 211[1] indicates that an Image should be created, then a Volume should be created from the image, then a Snapshot should be created from the Volume and finally an Instance should be launch from the Snapshot. The test indicates that we try to delete the Snapshot and Volume while the Instance is running, Snapshot nor Volume cannot be deleted. But when tried found that the Snapshot can be deleted, but the Volume cannot. Is this behavior correct?
Those are the commands I used:
openstack image create --disk-format qcow2 --file /home/wrsroot/cirros- 0.4.0-x86_64-disk.img --public cirros openstack volume create --image cirros --availability-zone nova --size 1 cirros-vol openstack volume snapshot create --name cirros-snap cirros-vol openstack server create --volume cirros-vol --flavor m1.small --availibility- zone nova vm-cirros
1 https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan_Instru ctions Regards. Juan Carlos Alonso
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (4)
-
Alonso, Juan Carlos
-
Badea, Daniel
-
Michel Thebeau
-
Perez Carranza, Jose