Re: [Openstack] Lazy import of modules

2011-01-14 Thread Andy Smith
Thanks phone, that was a yup to separate repository generally. Small libraries could sneak in but usually best to separate repo in my opinion. On Jan 14, 2011 10:05 AM, "Jay Pipes" wrote: > On Fri, Jan 14, 2011 at 11:28 AM, John Purrier wrote: >> Another thought, as we envision moving OpenStack f

Re: [Openstack] Lazy import of modules

2011-01-14 Thread Andy Smith
Yup. On Jan 14, 2011 10:05 AM, "Jay Pipes" wrote: > On Fri, Jan 14, 2011 at 11:28 AM, John Purrier wrote: >> Another thought, as we envision moving OpenStack forward we will likely be including code and projects that are not written in Python. Being forward looking should we structure openstack-c

Re: [Openstack] Lazy import of modules

2011-01-14 Thread Jay Pipes
On Fri, Jan 14, 2011 at 11:28 AM, John Purrier wrote: > Another thought, as we envision moving OpenStack forward we will likely be > including code and projects that are not written in Python. Being forward > looking should we structure openstack-common to segment along language lines? That was

Re: [Openstack] Glance x-image-meta-type raw vs machine

2011-01-14 Thread Jay Pipes
2011/1/14 Diego Parrilla Santamaría : > Well... VMX is probably too VMware oriented. My only concern about this kind > of proprietary parameter file is you don't really have the chance to control > its lifecycle. New versions, changes... and developers lagging behind of > this changes. It can be a

Re: [Openstack] Lazy import of modules

2011-01-14 Thread John Purrier
Another thought, as we envision moving OpenStack forward we will likely be including code and projects that are not written in Python. Being forward looking should we structure openstack-common to segment along language lines? John -Original Message- From: openstack-bounces+john=opensta

Re: [Openstack] Lazy import of modules

2011-01-14 Thread Jay Pipes
All, To be clear, I wasn't stating that the LazyPluggable class and solution in Nova isn't good. Just that. *right now*, a few weeks before Bexar release, the best place to put this code is only in Nova. Let it bake nicely during Cactus, and we can consider really utilising the openstack-common p

Re: [Openstack] Glance x-image-meta-type raw vs machine

2011-01-14 Thread Diego Parrilla Santamaría
2011/1/13 Erik Carlin > I would just call it VMDK. That's what Vmware > (http://www.vmware.com/technical-resources/interfaces/vmdk.html) and > everyone else calls it, even though there may be extra files to support > it. We're just naming the disk format here. > > There are several subtypes of

Re: [Openstack] Glance x-image-meta-type raw vs machine

2011-01-14 Thread Diego Parrilla Santamaría
2011/1/13 Jay Pipes > 2011/1/13 Diego Parrilla Santamaría : > > An appliance is the combination of metadata describing the virtual > machine > > plus the virtual disks. The standard format in the virtualization > industry > > is OVF. Basically, differs from VMX+VMDK(s) because it has a XML format

[Openstack] Bexar FeatureFreeze now in effect

2011-01-14 Thread Thierry Carrez
Hello everyone, Now that only small islands can still claim it's Thursday, FeatureFreeze is in effect. This only affects branches that introduce new features or changes in expected behavior ("feature branches"), not branches fixing bugs ("bugfix branches"). You can still propose feature branches