[RFC] should we allow to stop network when there are some templates linked to this network.
As we all know we should not stop network when are some running vms linked to this network. But what about only stop vms linked to this network? And what about only templates linked to this network? -- Thanks and best regards! Sheldon Feng(冯少合)<shaohef@linux.vnet.ibm.com> IBM Linux Technology Center
Sheldon, Would you elaborate? I am not sure what you are proposing. On 4/8/2014 10:51 AM, Sheldon wrote:
As we all know we should not stop network when are some running vms linked to this network.
But what about only stop vms linked to this network? And what about only templates linked to this network?
-- Adam King <rak@linux.vnet.ibm.com> IBM C&SI
Adam, I think Sheldon is talking about what the procedure to take when a user tries to remove/stop a network and it's being used (linked) only by guests that are not running and/or templates. IMO Sheldon, you must alert user which guests and templates have that network configured, and then stop/remove it. -- Paulo Ricardo Paz Vital <pvital@linux.vnet.ibm.com> IBM Linux Technology Center On Tue, 2014-04-08 at 11:59 -0400, Adam King wrote:
Sheldon,
Would you elaborate? I am not sure what you are proposing.
On 4/8/2014 10:51 AM, Sheldon wrote:
As we all know we should not stop network when are some running vms linked to this network.
But what about only stop vms linked to this network? And what about only templates linked to this network?
On 04/08/2014 04:54 PM, Paulo Ricardo Paz Vital wrote:
Adam,
I think Sheldon is talking about what the procedure to take when a user tries to remove/stop a network and it's being used (linked) only by guests that are not running and/or templates.
IMO Sheldon, you must alert user which guests and templates have that network configured, and then stop/remove it.
The network associated to a template or to *any* guest should not be removed or deleted - even if the guest is not running. If we allow user remove/stop a network associated with a stopped guest, the user will not be able to start the guest again which breaks Kimchi usability. And if we allow user remove/stop a network associate with a template, the user will not be able to create a guest from it (which also breaks Kimchi usability). I think it is already implemented that way and I don't see any reason to change it. Those kind of verifications were added to avoid users get inconsistent resources - templates or guests.
On 04/09/2014 03:54 AM, Paulo Ricardo Paz Vital wrote:
Adam,
I think Sheldon is talking about what the procedure to take when a user tries to remove/stop a network and it's being used (linked) only by guests that are not running and/or templates.
IMO Sheldon, you must alert user which guests and templates have that network configured, and then stop/remove it. Pvital, you know me. :-) Thanks.
-- Thanks and best regards! Sheldon Feng(冯少合)<shaohef@linux.vnet.ibm.com> IBM Linux Technology Center
on 2014/04/08 22:51, Sheldon wrote:
As we all know we should not stop network when are some running vms linked to this network.
But what about only stop vms linked to this network? And what about only templates linked to this network?
Here's my understanding of the relationship between template and network. It should be okay to create a template with a network that is not started, or stop a network when there is no running VM. The template is a static configuration, it should only check if a network exists. The live checks should only be performed just before a VM is actually started. -- Thanks and best regards! Zhou Zheng Sheng / 周征晟 E-mail: zhshzhou@linux.vnet.ibm.com Telephone: 86-10-82454397
participants (5)
-
Adam King -
Aline Manera -
Paulo Ricardo Paz Vital -
Sheldon -
Zhou Zheng Sheng