Re: [Openstack] Federated Identity Management (bursting and zones)

Hi Jorge, Thanks for the detailed description, and sorry for the delayed response, I was at a conference this week. This clears up the terminology, but I guess I'm still not seeing what this really gives use (specifically resource groups). It seems overly complicated, but I'm probably just missing

Re: [Openstack] Floating IP in OpenStack API

Cool. Got it. Floating IPs or what Amazon calls Elastic IPs. How are you solving the cross L2 problem? Erik Sent from my iPhone On Apr 15, 2011, at 7:28 PM, "Eldar Nugaev" wrote: > Hi Erik > > Thank you for response! > Yes, you are absolutely right OpenStack API already support shared IP

Re: [Openstack] Floating IP in OpenStack API

Hi Erik Thank you for response! Yes, you are absolutely right OpenStack API already support shared IP groups. Suppose there are some misunderstanding, because I wrote about floating IPs. I want to have API for association IPs from floating IPs pool with particular VM. At this moment we have #1 i

Re: [Openstack] Floating IP in OpenStack API

Eldar - The OpenStack API already supports sharing IPs between instances (although this may be an extension?). What exact behavior are you after? More important than the way in which we expose via the API is how it's implemented. It's important to note that this is extremely network topology de

Re: [Openstack] Proposal for Ed Leafe to join Nova-Core

+1 On 4/15/11 2:55 PM, "Jay Pipes" wrote: >Hi all, > >Ed Leafe (dabo) has been one of those developers that has stepped up >to the plate in code reviews and mailing list discussions. I'd like to >propose he join nova-core. > >Cheers, >jay > >___ >Mail

Re: [Openstack] Proposal for Ed Leafe to join Nova-Core

+1 On Apr 15, 2011, at 12:55 PM, Jay Pipes wrote: > Hi all, > > Ed Leafe (dabo) has been one of those developers that has stepped up > to the plate in code reviews and mailing list discussions. I'd like to > propose he join nova-core. > > Cheers, > jay > > _

Re: [Openstack] Proposal for Ed Leafe to join Nova-Core

2011/4/15 Jay Pipes : > Hi all, > > Ed Leafe (dabo) has been one of those developers that has stepped up > to the plate in code reviews and mailing list discussions. I'd like to > propose he join nova-core. +1 for sure. I'm surprised he's not already nova-core, actually. -- Soren Hansen        |

Re: [Openstack] Proposal for Ed Leafe to join Nova-Core

+1 On 04/15/2011 02:55 PM, Jay Pipes wrote: > Hi all, > > Ed Leafe (dabo) has been one of those developers that has stepped up > to the plate in code reviews and mailing list discussions. I'd like to > propose he join nova-core. > > Cheers, > jay > >

Re: [Openstack] Proposal for Ed Leafe to join Nova-Core

+1 From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Jay Pipes [jaypi...@gmail.com] Sent: Friday, April 15, 2011 4:55 PM To: openstack@lists.launchpad.net Su

[Openstack] Proposal for Ed Leafe to join Nova-Core

Hi all, Ed Leafe (dabo) has been one of those developers that has stepped up to the plate in code reviews and mailing list discussions. I'd like to propose he join nova-core. Cheers, jay ___ Mailing list: https://launchpad.net/~openstack Post to :

Re: [Openstack] distributed and heterogeneous schedulers

Jagane, good question. There can be many schedulers running within a Zone (each with their own ZoneManager). They service scheduler requests round-robin thanks the AMQP. We can have them not listen for events until, let's say, 30 seconds has elapsed (the update interval). Thanks for the note a

Re: [Openstack] distributed and heterogeneous schedulers

What happens if a ZoneManager process dies? When the ZoneManager restarts, the compute nodes will send their attributes to the newly restarted ZoneManager and the in-memory list of attributes will be reconstructed, right? The only downside to this approach is the (probably short) time that it tak

Re: [Openstack] Proposal for Justin Santa Barbara to join Nova-Core

Why should they be secret? From: Sebastian Stadil mailto:sebast...@scalr.com>> Date: Fri, 15 Apr 2011 10:11:42 -0700 To: Soren Hansen mailto:so...@openstack.org>> Cc: "openstack@lists.launchpad.net" mailto:openstack@lists.launchpad.net>> Subject: Re: [Opensta

Re: [Openstack] distributed and heterogeneous schedulers

Each update from the services are atomic updates ... fully self contained. Why does this need to be in a persistent store? -S From: Jay Pipes [jaypi...@gmail.com] > you still need a persistent data store for attributes of the host. Just > because you > s

Re: [Openstack] distributed and heterogeneous schedulers

On Apr 15, 2011, at 12:02 PM, Jay Pipes wrote: > This is getting totally off-track :) Of course! Don't all email threads do that? :) > My point was that if you are going to put data in a database table, > the attributes that go into the main table should be the attributes > that are com

Re: [Openstack] Proposal for Justin Santa Barbara to join Nova-Core

Well deserved, Justin. You have been a great contributor to the project! John -Original Message- From: openstack-bounces+john=openstack@lists.launchpad.net [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf Of Justin Santa Barbara Sent: Friday, April 15, 2011

Re: [Openstack] Proposal for Justin Santa Barbara to join Nova-Core

Great news - thank you all! Justin On Fri, Apr 15, 2011 at 1:24 AM, Soren Hansen wrote: > 2011/4/12 Soren Hansen : >> +1 from me, too. >> >> As per the process, if no-one objects within 5 business (my >> interpretation) days, i.e. before Thursday, I'll get Justin added to >> the nova-core tea

Re: [Openstack] Proposal for Justin Santa Barbara to join Nova-Core

Question out of curiosity, should everyone's votes be public? On Fri, Apr 15, 2011 at 4:24 AM, Soren Hansen wrote: > 2011/4/12 Soren Hansen : > > +1 from me, too. > > > > As per the process, if no-one objects within 5 business (my > > interpretation) days, i.e. before Thursday, I'll get Justin a

Re: [Openstack] Enhancements to Glance in Diablo? Input welcomed

On Thu, Apr 14, 2011 at 4:09 AM, Ewan Mellor wrote: > How about QA?  Is this something that you'd want to consider specifically for > Glance?  It's the newest of our services, and the smallest team, so I think > that it's worthwhile explicitly blocking out some time to look at automated > testi

Re: [Openstack] Enhancements to Glance in Diablo? Input welcomed

On Thu, Apr 14, 2011 at 2:26 AM, Ziad Sawalha wrote: > Licensing - Has there been a conversation around licensing? Glance may not be > the place to manage licenses (issue, track, revoke, renew, register, etc...) > but one attribute of an image is whether it needs a license or not and if it > do

Re: [Openstack] distributed and heterogeneous schedulers

This is getting totally off-track :) My point was that if you are going to put data in a database table, the attributes that go into the main table should be the attributes that are common to all types of an entity, otherwise, use the table that stores the custom key/value pairs. -jay On Fri, Ap

Re: [Openstack] distributed and heterogeneous schedulers

On Apr 15, 2011, at 11:43 AM, Jay Pipes wrote: > Yes, I'm aware of how the Zone Manager works. But, you still need a > persistent data store for attributes of the host. Just because you > store a cached in-memory copy of instance attributes, doesn't mean you > don't need a persistent data store. Y

Re: [Openstack] distributed and heterogeneous schedulers

On Fri, Apr 15, 2011 at 11:19 AM, Ed Leafe wrote: > On Apr 15, 2011, at 10:37 AM, Jay Pipes wrote: > >> The extra data would be more for the compute_nodes table I think, or >> is it called hosts now? > > >        I'm not sure how useful the compute_nodes table is anymore, at least > not for sched

Re: [Openstack] distributed and heterogeneous schedulers

On Apr 15, 2011, at 10:37 AM, Jay Pipes wrote: > The extra data would be more for the compute_nodes table I think, or > is it called hosts now? I'm not sure how useful the compute_nodes table is anymore, at least not for scheduler. Currently only libvirt seems to populate it. I know it'

Re: [Openstack] OpenStack "Cactus" release is out

Thierry Carrez wrote: > Ten weeks after "Bexar", I'm proud to announce the new release of the > OpenStack project, codenamed "Cactus". Diablo is open for development. Let's get all those pending merge proposals in and break it :) -- Thierry Carrez (ttx) Release Manager, OpenStack __

Re: [Openstack] distributed and heterogeneous schedulers

On Fri, Apr 15, 2011 at 10:52 AM, Sandy Walsh wrote: > 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

Re: [Openstack] distributed and heterogeneous schedulers

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

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 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

Re: [Openstack] distributed and heterogeneous schedulers

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 t

Re: [Openstack] OpenStack "Cactus" release is out

Amazing work everyone! Special thanks to Thierry for keeping this vibrant community on track and always productive, yet never boring :) Hope to see everyone in 10 days!! Mark On Apr 15, 2011, at 4:37 AM, "Thierry Carrez" wrote: > Hello everyone, > > Ten weeks after "Bexar", I'm proud to ann

Re: [Openstack] Proposal for Justin Santa Barbara to join Nova-Core

2011/4/12 Soren Hansen : > +1 from me, too. > > As per the process, if no-one objects within 5 business (my > interpretation) days, i.e. before Thursday, I'll get Justin added to > the nova-core team. Noone objected, so this is now done. Congrats, Justin. Welcome to the team :) -- Soren Hansen U

[Openstack] OpenStack "Cactus" release is out

Hello everyone, Ten weeks after "Bexar", I'm proud to announce the new release of the OpenStack project, codenamed "Cactus". This release consists of the following deliverables: Nova 2011.2: https://launchpad.net/nova/cactus/2011.2 Glance 2011.2: https://launchpad.net/glance/cactus/2011.2 Swift