Re: [openstack-dev] [Nova] Migration state machine proposal.

On 11/06/2015 03:47 AM, Tang Chen wrote: On 11/06/2015 12:45 PM, Chris Friesen wrote: To me, the external API would make more sense as: 1) resize 2) migrate (with option of cold or live, and with option to specify a destination, and with option to override the scheduler if the specified des

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 11/06/2015 12:45 PM, Chris Friesen wrote: On 11/05/2015 08:33 AM, Andrew Laski wrote: On 11/05/15 at 01:28pm, Murray, Paul (HP Cloud) wrote: Or more specifically, the migrate and resize API actions both call the resize function in the compute api. As Ed said, they are basically the same

Re: [openstack-dev] [Nova] Migration state machine proposal.

: [openstack-dev] [Nova] Migration state machine proposal. On 11/05/2015 08:33 AM, Andrew Laski wrote: > On 11/05/15 at 01:28pm, Murray, Paul (HP Cloud) wrote: >> Or more specifically, the migrate and resize API actions both call >> the resize function in the compute api. As Ed

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 11/05/2015 08:33 AM, Andrew Laski wrote: On 11/05/15 at 01:28pm, Murray, Paul (HP Cloud) wrote: Or more specifically, the migrate and resize API actions both call the resize function in the compute api. As Ed said, they are basically the same behind the scenes. (But the API difference is im

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 11/05/15 at 10:12am, Jonathan D. Proulx wrote: On Thu, Nov 05, 2015 at 09:33:37AM -0500, Andrew Laski wrote: :Can you be a little more specific on what API difference is important :to you? There are two differences currently between migrate and :resize in the API: : :1. There is a different

Re: [openstack-dev] [Nova] Migration state machine proposal.

On Thu, Nov 05, 2015 at 09:33:37AM -0500, Andrew Laski wrote: :Can you be a little more specific on what API difference is important :to you? There are two differences currently between migrate and :resize in the API: : :1. There is a different policy check, but this only really protects :the nex

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 11/05/15 at 01:28pm, Murray, Paul (HP Cloud) wrote: From: Ed Leafe [mailto:e...@leafe.com] On Nov 5, 2015, at 2:43 AM, Tang Chen wrote: > I'm sorry that I cannot understand why resize and migrate are the same thing behind. Resize is essentially a migration to the same host, rather than a

Re: [openstack-dev] [Nova] Migration state machine proposal.

> From: Ed Leafe [mailto:e...@leafe.com] > On Nov 5, 2015, at 2:43 AM, Tang Chen wrote: > > > I'm sorry that I cannot understand why resize and migrate are the same > thing behind. > > Resize is essentially a migration to the same host, rather than a different > host. The process is still taki

Re: [openstack-dev] [Nova] Migration state machine proposal.

On Nov 5, 2015, at 2:43 AM, Tang Chen wrote: > I'm sorry that I cannot understand why resize and migrate are the same thing > behind. Resize is essentially a migration to the same host, rather than a different host. The process is still taking an existing VM and using it to create another VM

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 11/05/2015 02:36 AM, Jonathan D. Proulx wrote: On Wed, Nov 04, 2015 at 06:17:17PM +, Murray, Paul (HP Cloud) wrote: :> From: Jay Pipes [mailto:jaypi...@gmail.com] :> A fair point. However, I think that a generic update VM API, which would :> allow changes to the resources consumed by the

Re: [openstack-dev] [Nova] Migration state machine proposal.

On Wed, Nov 04, 2015 at 06:17:17PM +, Murray, Paul (HP Cloud) wrote: :> From: Jay Pipes [mailto:jaypi...@gmail.com] :> A fair point. However, I think that a generic update VM API, which would :> allow changes to the resources consumed by the VM along with capabiities :> like CPU model or local

Re: [openstack-dev] [Nova] Migration state machine proposal.

> From: Jay Pipes [mailto:jaypi...@gmail.com] > On 10/27/2015 01:16 PM, Chris Friesen wrote: > > On 10/26/2015 06:02 PM, Jay Pipes wrote: > > > >> I believe strongly that we should deprecate the existing migrate, > >> resize, an live-migrate APIs in favor of a single consolidated, > >> consistent

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi all, Just FYI, the WIP patch-set is now available here: https://review.openstack.org/241476 https://review.openstack.org/241477 https://review.openstack.org/241478 https://review.openstack.org/241479 https://review.openstack.org/241480 Thanks. On 10/14/2015 10:05 AM, Tang Chen wrote: Hi, a

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/29/2015 09:26 AM, Tang Chen wrote: Hi Andrew, On 10/29/2015 12:53 AM, Andrew Laski wrote: On 10/27/15 at 09:02am, Jay Pipes wrote: On 10/22/2015 11:13 AM, Tang Chen wrote: On 10/22/2015 05:17 AM, Joshua Harlow wrote: Overall I'm very much inclined to have three state machines (one for

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi Andrew, On 10/29/2015 12:53 AM, Andrew Laski wrote: On 10/27/15 at 09:02am, Jay Pipes wrote: On 10/22/2015 11:13 AM, Tang Chen wrote: On 10/22/2015 05:17 AM, Joshua Harlow wrote: Overall I'm very much inclined to have three state machines (one for each type), vs the mix-mash of all three i

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/27/15 at 09:02am, Jay Pipes wrote: On 10/22/2015 11:13 AM, Tang Chen wrote: On 10/22/2015 05:17 AM, Joshua Harlow wrote: Overall I'm very much inclined to have three state machines (one for each type), vs the mix-mash of all three into one state machine (which causes the confusion around

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/27/2015 05:27 PM, Tang Chen wrote: On 10/27/2015 08:02 AM, Jay Pipes wrote: Evacuate does *not* migrate/move anything. Evacuate *rebuilds* VMs from their original source image. Well, I just dug into the source code. I think there could be some difference between evacuate in nova server s

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/27/2015 01:16 PM, Chris Friesen wrote: On 10/26/2015 06:02 PM, Jay Pipes wrote: I believe strongly that we should deprecate the existing migrate, resize, an live-migrate APIs in favor of a single consolidated, consistent "move" REST API that would have the following characteristics: * No

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi Chris, On 10/27/2015 12:16 PM, Chris Friesen wrote: On 10/26/2015 06:02 PM, Jay Pipes wrote: I believe strongly that we should deprecate the existing migrate, resize, an live-migrate APIs in favor of a single consolidated, consistent "move" REST API that would have the following character

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi Jay, Timofei, Thank you for the info. On 10/27/2015 08:02 AM, Jay Pipes wrote: On 10/22/2015 11:13 AM, Tang Chen wrote: On 10/22/2015 05:17 AM, Joshua Harlow wrote: Overall I'm very much inclined to have three state machines (one for each type), vs the mix-mash of all three into one state

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/26/2015 06:02 PM, Jay Pipes wrote: I believe strongly that we should deprecate the existing migrate, resize, an live-migrate APIs in favor of a single consolidated, consistent "move" REST API that would have the following characteristics: * No manual or wait-input states in any FSM graph

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/22/2015 11:13 AM, Tang Chen wrote: On 10/22/2015 05:17 AM, Joshua Harlow wrote: Overall I'm very much inclined to have three state machines (one for each type), vs the mix-mash of all three into one state machine (which causes the confusion around states in the first diagram in that paste)

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/22/2015 05:42 PM, Markus Zoeller wrote: Tang Chen wrote on 10/21/2015 10:22:15 AM: From: Tang Chen To: "OpenStack Development Mailing List (not for usage questions)" Date: 10/21/2015 10:24 AM Subject: Re: [openstack-dev] [Nova] Migration state machine proposal. Hi, Plea

Re: [openstack-dev] [Nova] Migration state machine proposal.

Nikola Đipanov wrote: On 10/21/2015 10:17 PM, Joshua Harlow wrote: Question on some things seen in the below paste. What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? Why does it jump over 'reverting' or 'confirming'? Should it? The other question is the difference between

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 22 October 2015 at 10:20, Nikola Đipanov wrote: > On 10/21/2015 10:17 PM, Joshua Harlow wrote: >> Question on some things seen in the below paste. >> >> What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? >> >> Why does it jump over 'reverting' or 'confirming'? Should it? >> >>

Re: [openstack-dev] [Nova] Migration state machine proposal.

Tang Chen wrote on 10/21/2015 10:22:15 AM: > From: Tang Chen > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 10/21/2015 10:24 AM > Subject: Re: [openstack-dev] [Nova] Migration state machine proposal. > > Hi, > > Please h

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/21/2015 10:17 PM, Joshua Harlow wrote: > Question on some things seen in the below paste. > > What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? > > Why does it jump over 'reverting' or 'confirming'? Should it? > > The other question is the difference between 'failed' and

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi Joshua, On 10/22/2015 05:17 AM, Joshua Harlow wrote: Question on some things seen in the below paste. What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? Let's take confirm as an example. Please refer to function confirm_resize(). Resize is one type of migration in the cur

Re: [openstack-dev] [Nova] Migration state machine proposal.

Question on some things seen in the below paste. What is with 'finished' -> 'reverted' and 'finished' -> 'confirmed'? Why does it jump over 'reverting' or 'confirming'? Should it? The other question is the difference between 'failed' and 'error' in the first diagram, any idea on why/how these

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi, Please help to take a look at this problem. I was trying to raise it in the spec discussion. But since we don't need a spec on this problem, so I want to discuss it here. It is about what the new state machine will be. http://paste.openstack.org/show/476954/ Thanks. _

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi Nikola, On 10/19/2015 06:52 PM, Nikola Đipanov wrote: On 10/19/2015 11:13 AM, Tang Chen wrote: Hi, all, If you don't mind, how about approve the BP, and I can start this work. This is IMHO the biggest drawback of the current spec process (as I've written before). There is no reason why y

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/19/2015 11:13 AM, Tang Chen wrote: > Hi, all, > > If you don't mind, how about approve the BP, and I can start this work. > This is IMHO the biggest drawback of the current spec process (as I've written before). There is no reason why you should doubt that this particular spec will get ap

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi, all, If you don't mind, how about approve the BP, and I can start this work. Thanks. On 10/15/2015 04:53 PM, Tang Chen wrote: Hi all, The spec is now available here: https://review.openstack.org/#/c/235169/ Please help to review. Thanks. On 10/14/2015 10:05 AM, Tang Chen wrote: Hi, a

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi all, The spec is now available here: https://review.openstack.org/#/c/235169/ Please help to review. Thanks. On 10/14/2015 10:05 AM, Tang Chen wrote: Hi, all, Please help to review this BP. https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine Currently, the migratio

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/14/2015 04:53 PM, Nikola Đipanov wrote: On 10/14/2015 04:29 AM, Tang Chen wrote: On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen mailto:tangc...@cn.fujitsu.com>> wrote: Hi, all, Please help to review this BP. https://blueprints.launchpad.net/nova/+spec/live-migration-state-m

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/14/2015 04:29 AM, Tang Chen wrote: >> >> On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen > > wrote: >> >> Hi, all, >> >> Please help to review this BP. >> >> https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine >> >> >> Currently

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/14/2015 11:14 AM, Zhenyu Zheng wrote: I think it will be better if you can submit a spec for your proposal, it will be easier for people to give comment. OK, will submit one soon. Thanks. On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen > wrote: Hi, a

Re: [openstack-dev] [Nova] Migration state machine proposal.

I think it will be better if you can submit a spec for your proposal, it will be easier for people to give comment. On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen wrote: > Hi, all, > > Please help to review this BP. > > https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine > > >

[openstack-dev] [Nova] Migration state machine proposal.

Hi, all, Please help to review this BP. https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine Currently, the migration_status field in Migration object is indicating the status of migration process. But in the current code, it is represented by pure string, like 'migrating',