openstack team mailing list archive

[Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx>]

Hmm, kind of a duplication of efforts wrt tracking services:

1. the previous "availability zones" code (flat partitioning/tagging within a single nova deployment). I believe this was done for EC2 compatibility. I'll call this AZ. 
2. the Zone stuff I've been working on. I'll just call this Zones

* AZ updates the Services table when a new Service is spun up. Other periodic calls update the related tables (libvirt only currently I think).
* Zones updates the ZoneManager in the Schedulers via rabbitmq calls (no db). Call scheduler.api.get_zone_capabilities("service") to get that info.
* ZoneManager holds the capabilities for each service. Handling AZ-like functionality can be done with capabilities.

As mentioned before, each service reports their capabilities to the ZoneManager via a rabbit call. There is no need to update any tables since this is all ephemeral and are raw python data structures. ie. make them as rich as you like.

We could replace the AZ stuff with the scheduler/zone manager approach to lessen confusion?

-S

________________________________________
From: Jay Pipes [jaypipes@xxxxxxxxx]
Sent: Friday, April 15, 2011 11:37 AM
To: Sandy Walsh
Cc: Mark Washenberger; openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] distributed and heterogeneous schedulers

The extra data would be more for the compute_nodes table I think, or
is it called hosts now?

-jay

On Fri, Apr 15, 2011 at 10:06 AM, Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx> wrote:
> Hey guys,
>
> I don't understand how adding more data to the *instances* table will be used for scheduling?
>
> Perhaps what you're talking about is metadata in Glance on the source images?
>
> If so, that data would simply be added to the required-capabilities that get passed into the scheduler during the run_instance() call and would be extracted from the Flavor/OS pair passed into boot().
>
> What I missing something here? Feel free to talk to me like I'm a five year old :)
>
> -S
>
>
>
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>