Re: [Openstack] using objects returned from DB layer

For me, it's not one particular notation versus the other, I'd be happy with either--it's having both. It just needlessly complicates things. > Now we're complaining that the ORM we likely aren't using > correctly isn't working for us I don't think anyone is complaining that the *ORM* is at faul

Re: [Openstack] using objects returned from DB layer

s., fixing those last things. Hm... although, I guess I really do > like the ability to turn something off if it's broken. :) > > - Chris > > > > On Dec 15, 2011, at 12:29 AM, Rick Harris wrote: > >> ++ on moving to a consistent dict-style syntax. >> &

Re: [Openstack] using objects returned from DB layer

++ on moving to a consistent dict-style syntax. We could attempt to rip the Band-Aid off here by: 1. Rejecting any new patches which use the dot-notation 2. Trying to switch out to using dot-notation access all at once in one big 'fix-it-up' patch. I'm not convinced 2) is possible. Separating

Re: [Openstack] Proposal to add Kevin Mitchell to nova-core

+1 as well. On Nov 9, 2011, at 11:24 AM, Chris Behrens wrote: > Yep... +1 > > > On Nov 9, 2011, at 5:59 AM, Brian Waldon wrote: > >> Vek has absolutely stepped up and started doing quite few reviews, so I'd >> like to nominate him to be added to nova-core. >> >> Waldon >> >> >> __

Re: [Openstack] Proposal to add Johannes Erdfelt to nova-core

Definite +1 On Nov 9, 2011, at 11:05 AM, Trey Morris wrote: +1 On Wed, Nov 9, 2011 at 9:35 AM, Sandy Walsh mailto:sandy.wa...@rackspace.com>> wrote: 9 * 3 - 26 From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net

Re: [Openstack] Proposal to add Chris Behrens to nova-core

Definite +1 On Sep 15, 2011, at 4:13 PM, Brian Waldon wrote: > Chris (comstud) has been a great help with reviews lately and has quite a bit > of knowledge of the system overall. I think he would add a great amount to > the team, so I'm proposing we add him to nova-core. > > Brian Waldon > >

Re: [Openstack] [NEW DEPENDENCY] Nova will depend on Tempo

The agreement is missing in trunk, but this pull-request adds it: https://github.com/rackspace/Tempo/pull/8 On Sep 8, 2011, at 5:40 PM, Ben McGraw wrote: Am I missing a licensing agreement in the Tempo project? -Ben (Grue) On Thu, Sep 8, 2011 at 3:15 PM, Rick Harris mailto:rick.har

[Openstack] [NEW DEPENDENCY] Nova will depend on Tempo

Just a quick announcement so no one is caught by surprise: Once https://code.launchpad.net/~rconradharris/nova/backup_schedule_extension/+merge/74665 merges, Nova will have a new dependency on the Tempo project (https://github.com/rackspace/Tempo). Tempo is included in the pip-require and the

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

+1 From: openstack-bounces+rick.harris=rackspace@lists.launchpad.net [openstack-bounces+rick.harris=rackspace@lists.launchpad.net] on behalf of Vishvananda Ishaya [vishvana...@gmail.com] Sent: Thursday, April 07, 2011 2:19 PM To: Jay Pipes Cc: open

Re: [Openstack] core dev

Sprinklin' on a +1 From: openstack-bounces+rick.harris=rackspace@lists.launchpad.net [openstack-bounces+rick.harris=rackspace@lists.launchpad.net] on behalf of Sandy Walsh [sandy.wa...@rackspace.com] Sent: Friday, March 25, 2011 10:26 AM To: Trey Morris; o

[Openstack] Nova-core membership request

Throwing my hat into the ring for nova-core membership. Eager to help knock down that merge-prop backlog we have at the moment :-) Obligatory plug: While I have your attention, checkout https://code.launchpad.net/~rconradharris/nova/xs-unified-images/+merge/50102 -Rick (sirp) Confidentialit

Re: [Openstack] Glance, libvirt/kvm snapshots

Hey Ahmed, TL;DR Glance doesn't appear to be supported with libvirt driver yet. Judging by the stack trace, it looks like the code is taking an S3 code path even though you've selected the GlanceImageService. Looking through the code, it doesn't appear that the libvirt/Glance code is there ye

Re: [Openstack] Deprecating nova-objectstore

>What's the difference between an image and an object? They're all just blobs >of bits as far as I > thought. I think of an image as data+metadata. The data is stored as objects where the image can span multiple objects. The metadata maybe stored in the form of a manifest-file, or, as with Gla

Re: [Openstack] Glance streaming [was RE: Use of IANA-registered port]

> I'm expecting precisely one compute node per XS host You're right. In that case, I agree, moving the code into nova-compute should be fine. From: Ewan Mellor [ewan.mel...@eu.citrix.com] Sent: Monday, January 03, 2011 11:55 AM To: Rick Harr

Re: [Openstack] Use of IANA-registered ports

> streaming should be done inside nova-compute, rather than in a xapi plugin... do you _need_ the code inside a plugin for xs-snapshots, or will it be OK if we move it? If we moved the code into nova-compute, wouldn't that mean we're directing all image-download/image-snapshot traffic through the

[Openstack] Glance/Nova Snapshot Changes

In developing Nova's instance snapshots, I've run into a little snag revolving around somed design decisions in both Nova and Glance. I have a plan that I'd like to move forward with ASAP, so please, if you see any problems or have any objections, raise them now. Problem === OpenStack's API