Hi Sandy and Jay,
I've checked in one graphviz VM state transition in this review patch 3:
https://review.openstack.org/#/c/8254/
However since it's very complicated, the graph is too big after it's
rendered. Ideas are welcome. Thanks,
Yun
On Thu, May 24, 2012 at 3:10 PM, Jay Pipes
I'd like to understand the difference between a soft and hard delete.
soft_delete is invoked when reclaim_instance_interval flag is set to non-zero.
In this case, when delete command is fired, only the VM is powered off, and
vm_state is set to SOFT_DELETE
Other resources (like network, volume,
] nova state machine simplification and clarification
I'd like to understand the difference between a soft and hard delete.
soft_delete is invoked when reclaim_instance_interval flag is set to non-zero.
In this case, when delete command is fired, only the VM is powered off, and
vm_state is set
state machine simplification and clarification
I'd like to understand the difference between a soft and hard delete.
soft_delete is invoked when reclaim_instance_interval flag is set to
non-zero.
In this case, when delete command is fired, only the VM is powered off, and
vm_state is set
)
I'd like to see more discussion on how reconciliation will be handled in the
event of a conflict.
Cheers!
-S
From: Yun Mao [yun...@gmail.com]
Sent: Thursday, May 17, 2012 10:16 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] nova state
On 05/24/2012 10:46 AM, Yun Mao wrote:
Sandy,
I like the suggestion of graphvis, although I haven't used it for a
while. Is there a dir in nova appropriate to put .dot files? I was
hoping to get the proposal discussed a few round, and while it's
getting stabilized, we can work on the graphvis
I love graphviz as a charting tool and sphinx support inline is great.
Used to use it all the time at nebula in the work wiki.
-Matt
On Thu, May 24, 2012 at 12:10 PM, Jay Pipes jaypi...@gmail.com wrote:
On 05/24/2012 10:46 AM, Yun Mao wrote:
Sandy,
I like the suggestion of graphvis,
in the
event of a conflict.
Cheers!
-S
From: Yun Mao [yun...@gmail.com]
Sent: Thursday, May 17, 2012 10:16 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] nova state machine simplification and clarification
Hi Yun,
This proposal looks very good to me. I am glad you included in it the
requirement that hard deletes can take place in any vm/task/power state.
I however feel that a similar requirement exists for revert resize. It should
be possible to issue a RevertResize command for any task_state
I agree, this looks much more clear compared to where we are now.
I'd like to understand the difference between a soft and hard delete.
Does an API user have to specify that in some way? I definitely agree
that you should be able to delete in any state, I would rather it not be a
requirement
Also, with this proposal I'd be a lot more interested in exposing task
state as a part of the API eventually. This is helpful to communicate
whether or not other actions would be allowed in certain states. For
example, right now we don't allow other actions when a server is
snapshotting, but
Hi Mark,
I haven't looked at resize related API calls very closely. But what
you are saying makes sense. revert_resize() should be able to preempt
an existing resize() call, which might get stuck. I'm not clear how
the leftovers will be garbage collected yet.
Yun
On Fri, May 18, 2012 at 10:20
Gabe,
There is a flag reclaim_instance_interval on API. If it's set to 0 (by
default), everything is hard_delete. Otherwise, it's soft_delete. and
will be automatically hard deleted after the configured interval.
There is also an API extension to as force_delete, which is hard
delete no matter
Hi,
There are vm_states, task_states, and power_states for each VM. The
use of them is complicated. Some states are confusing, and sometimes
ambiguous. There also lacks a guideline to extend/add new state. This
proposal aims to simplify things, explain and define precisely what
they mean, and why
14 matches
Mail list logo
