nova-orchestration team mailing list archive

[Andrew Beekhof <andrew@xxxxxxxxxxx>]

On Thu, Nov 24, 2011 at 4:07 AM, Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx> wrote:
> Each provisioning operation is generally sequential (and perhaps even preferred to be for debugging). The only real parallel activity is, as you mentioned, creating many instances or mass migration/resize/backup/etc.

It also seems implicit in how scaling and compute instance failure is modelled.
Ie. that any instance could end up performing any given stage of the
provisioning process.

To get that you basically need to assume parallelism right?

>
> -S
>
> ________________________________________
> From: nova-orchestration-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx [nova-orchestration-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx] on behalf of Yun Mao [yunmao@xxxxxxxxx]
> Sent: Wednesday, November 23, 2011 10:32 AM
> To: nova-orchestration@xxxxxxxxxxxxxxxxxxx
> Subject: [Nova-orchestration] task parallelism in nova
>
> What's the use cases to run tasks in parallel? One that's quite
> obvious is to create many instances. The task to create a single
> instance seems quite sequential to me. Do we have other use cases? Is
> there a more complicated one, such as requiring parallel tasks to
> communicate? Thanks,
>
> Yun
>
> --
> Mailing list: https://launchpad.net/~nova-orchestration
> Post to     : nova-orchestration@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~nova-orchestration
> More help   : https://help.launchpad.net/ListHelp
>
> --
> Mailing list: https://launchpad.net/~nova-orchestration
> Post to     : nova-orchestration@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~nova-orchestration
> More help   : https://help.launchpad.net/ListHelp
>