[Openstack] python-novaclient vs. python-openstack.compute

2011-05-17 Thread Soren Hansen
python-novaclient[0] is the client for Nova that we maintain ourselves. It is a fork of jacobian's python-cloudservers. python-openstack.compute is jacobian's new branch of python-cloudservers. I wonder if there's any point in having two distinct, but very similar libraries to do same thing. If n

[Openstack] Discussion of network service flows

2011-05-17 Thread Troy Toman
As was mentioned in the networks meeting this afternoon, we need to open up a discussion around flows between Nova, Melange(IPAM), Quantum and Donabe. As we are refactoring Nova for networking and designing IP and Network services in parallel, it will be important to reach some agreement as to h

[Openstack] testing and deploying swift?

2011-05-17 Thread Jon Slenk
hi, So what are people's processes for tracking Swift releases, on production systems? I'm guessing Rackspace is probably the most serious deployment to date. If anybody there could comment on what release of Swift is being run and how you expect to deploy newer versions, that would be fun and ed

Re: [Openstack] Global deployment of Glance

2011-05-17 Thread Eric Day
Assuming you are using Swift for storage, the Swift ring configuration can specify zones and minimum number of replicas, which could handle all this logic and bit pushing for you. -Eric On Tue, May 17, 2011 at 06:36:38PM +, Glen Campbell wrote: > That's probably the easiest to implement. This

Re: [Openstack] Global deployment of Glance

2011-05-17 Thread Glen Campbell
That's probably the easiest to implement. This would mean that each deployment of new images would need to be installed in each region. On 5/17/11 12:47 PM, "Chris Behrens" wrote: > >Ignoring how it is actually implemented, I think we do want copies of >base images in reach region. We do

Re: [Openstack] Global deployment of Glance

2011-05-17 Thread Chris Behrens
Ignoring how it is actually implemented, I think we do want copies of base images in reach region. We don't want any sort of outage in one region to adversely affect another region. - Chris On May 17, 2011, at 9:36 AM, Jay Pipes wrote: > On Tue, May 17, 2011 at 11:59 AM, Glen Campbell > wr

Re: [Openstack] Global deployment of Glance

2011-05-17 Thread Chris Behrens
Each zone should definitely have glance instances, IMO. At least two per zone for redundancy and networking reasons in large OpenStack installations. There's some work to do to support this, though. - Chris On May 17, 2011, at 8:59 AM, Glen Campbell wrote: > If we are going to deploy Glance

Re: [Openstack] Global deployment of Glance

2011-05-17 Thread Jay Pipes
On Tue, May 17, 2011 at 11:59 AM, Glen Campbell wrote: > If we are going to deploy Glance to support a global deployment of Nova, > would it make sense to have replicas in different regions for better > performance? > Or, to put it another way, is there a recommended way to keep multiple Glance

[Openstack] Global deployment of Glance

2011-05-17 Thread Glen Campbell
If we are going to deploy Glance to support a global deployment of Nova, would it make sense to have replicas in different regions for better performance? Or, to put it another way, is there a recommended way to keep multiple Glance installations in sync? Users doing snapshots/backups, etc., wo

[Openstack] Reminder: OpenStack team meeting - 21:00 UTC

2011-05-17 Thread Thierry Carrez
Hello everyone, Our weekly team meeting will take place at 21:00 UTC this Tuesday in #openstack-meeting on IRC. Check out how that time translates for *your* timezone: http://www.timeanddate.com/worldclock/fixedtime.html?iso=20110517T21 See the meeting agenda, edit the wiki to add new topics for

[Openstack] Keystone API versioning

2011-05-17 Thread Ziad Sawalha
Gholt brings up a good point in https://github.com/khussein/keystone/issues/36. In order to support the existing ecosystem of clients out there designed to work against swift and the Rackspace auth 1.0 API (as documented here http://docs.rackspacecloud.com/files/api/v1/cfdevguide_d5/content/ch03