Re: [openstack-dev] [Heat] as-update-policy implementation details

Zane, I tested FnGetRefId() in LaunchConfiguration to return unicode(self.physical_resource_name()). It doesn't work so well. When InstanceGroup resolve runtime data and resolve resource refs, the physical resource name (I.e.test_stack-JobServerConfig-jnzjnpomcxv5) replaced { 'Ref': 'JobServ

[openstack-dev] [State-Management] Meeting minutes.

Just wanted to ensure everyone is up to date and has the ability to chime-in on some of the discussion we had in the state-management team. Logs @ http://eavesdrop.openstack.org/meetings/state_management/2013/state_management.2013-08-08-20.00.html TLDR: 1. Cinder baby steps merged! *

Re: [openstack-dev] Motion to start using Gerrit for TC votes

On 2013-08-07 13:45:56 -0700 (-0700), James E. Blair wrote: > Actually, having a record outside of Gerrit doesn't require > cherry-pick mode. [...] Ah! Thanks. For some reason I'd gotten it into my head that git notes altered the commit itself, but that's quite clearly not the case. > So given th

Re: [openstack-dev] [Heat] event table is a ticking time bomb

On 08/08/13 13:16 -0700, Clint Byrum wrote: Last night while reviewing a feature which would add more events to the event table, it dawned on me that the event table really must be removed. https://bugs.launchpad.net/heat/+bug/1209492 tl;dr: users can write an infinite number of rows to the

Re: [openstack-dev] Nova config drive rebuilding

On 7 August 2013 11:53, John Garbutt wrote: > I have thought about a (slightly messy) alternative: > * use ConfigDrive only for basic networking config on the first nic > (i.e. just enough to get to the metadata service) > * get all other data from the metadata service, once the first nic is up T

Re: [openstack-dev] Blueprint review

On Thu, Aug 8, 2013 at 12:41 AM, Álvaro López García < alvaro.lopez.gar...@cern.ch> wrote: > Hi John. > > On Wed 07 Aug 2013 (15:56), Joe Gordon wrote: > > Can you provide more detail in the BP, there isn't very much to review > it > > on right now. > > Thanks for your interest, I've updated it a

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On Thu, Aug 08, 2013 at 10:10:09AM -0300, Monty Taylor wrote: > I don't think we will gain much by auto-generating packages. What really is the difference between devstack auto-generating a package and having a human basically doing the same thing and sticking it in a repo? It just seems unreliab

Re: [openstack-dev] Problem using Keystone split backend

On 08/08/2013 03:58 PM, Gaspareto, Otavio wrote: Hi all, I'm using the Keystone split backend code (H2) with both identity and assignment using SQL drivers. During the process of authentication thru Horizon, I'm getting the following error in the log: Traceback (most recent call last): F

[openstack-dev] [nova][vmware] VMwareAPI sub-team havana-3 do-or-die list!

Greetings stackers! tl;dr for core reviewers at the end... Because we're 2 weeks out on the first Havana-3 blueprint deadline I thought I would go ahead and list the blueprints in order of importance to the driver as a working whole... Sadly, not all of these are ready to go. That means as a t

Re: [openstack-dev] Keystone Split Backend LDAP Hang Problem

On 08/08/2013 01:20 PM, Miller, Mark M (EB SW Cloud - R&D - Corvallis) wrote: Adam, I want to thank for your responses as I am coming up to speed. If I don't get yanked off to fill some other project holes, Keystone knowledge and support will become my full time job here at HP. My pleasur

Re: [openstack-dev] Osl and dangerous code merging

On 08/08/2013 07:05 AM, Mark McLoughlin wrote: On Thu, 2013-08-08 at 11:49 +0100, Daniel P. Berrange wrote: On Thu, Aug 08, 2013 at 11:39:44AM +0100, Mark McLoughlin wrote: What do you mean by "dangerous code merging" in the subject? The body of your mail doesn't make any reference to whatever

Re: [openstack-dev] Change in openstack/keystone[master]: Implement domain specific Identity backends

Hi Henry, On Tue, 2013-08-06 at 22:10 +0100, Henry Nash wrote: > Hi Mark, > > Of particular interest are your views on the changes to > keystone/common/config.py. The requirement is that we need to be able to > instantiate multiple conf objects (built from different sets of config > files).

Re: [openstack-dev] [Oslo] oslo.version and pbr

On Sun, 2013-08-04 at 13:41 -0400, Monty Taylor wrote: > Hey all! > > Currently, there is runtime version handling code in pbr. It's been a > cause of concern for some folks because it means that pbr becomes a > runtime rather than just a build time dependency - so the suggestion has > come across

[openstack-dev] [Heat] event table is a ticking time bomb

Last night while reviewing a feature which would add more events to the event table, it dawned on me that the event table really must be removed. https://bugs.launchpad.net/heat/+bug/1209492 tl;dr: users can write an infinite number of rows to the event table at a fairly alarming rate just by cre

Re: [openstack-dev] [openstack-announce] [OSSA 2013-018] Missing SSL certificate check in Python glance client (CVE-2013-4111)

On Tue, Jul 30, 2013 at 7:17 AM, Thierry Carrez wrote: > > OpenStack Security Advisory: 2013-018 > CVE: CVE-2013-4111 > Date: July 30, 2013 > Title: Missing SSL certificate check in Python glance client > Reporter: Thomas Leaman (HP) > Products: python-glanceclient > Affects: All versions > > Desc

[openstack-dev] Problem using Keystone split backend

Hi all, I'm using the Keystone split backend code (H2) with both identity and assignment using SQL drivers. During the process of authentication thru Horizon, I'm getting the following error in the log: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/keystone/common

Re: [openstack-dev] Oslo.exception being dropped??

+1 agreed. I should of looked at the wiki ;) From: Joe Gordon mailto:joe.gord...@gmail.com>> Date: Thursday, August 8, 2013 12:44 PM To: Joshua Harlow mailto:harlo...@yahoo-inc.com>> Cc: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] Osl

Re: [openstack-dev] Oslo.exception being dropped??

On Thu, Aug 8, 2013 at 12:41 PM, Joshua Harlow wrote: > Agreed. I'd at least like to have the bug referenced have at least more > context. > > The commit message links to the bug, so that’s a plus (but not ideal). > - *Do not assume the reviewer has access to external web services/site.* I

Re: [openstack-dev] Oslo.exception being dropped??

Agreed. I'd at least like to have the bug referenced have at least more context. The commit message links to the bug, so that’s a plus (but not ideal). From: Joe Gordon mailto:joe.gord...@gmail.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Th

Re: [openstack-dev] Oslo.exception being dropped??

This touches on one of my big pet peeves, in the commit message one should: "*Describe why a change is being made.* A common mistake is to just document how the code has been written, without describing /why/ the developer chose to do it that way. By all means describe the overall code structure,

[openstack-dev] [Swift] Swift hackathon in October in Austin

We (SwiftStack) are hosting a Swift Hackathon in Austin, Texas on October 15-17. We're bringing together Swift contributors to meet and hack for a few days. http://swifthackathon.eventbrite.com Our plan is to provide a few days of hacking together with just a few rules: 1) No slide decks and 2

Re: [openstack-dev] Blueprint for Nova native image building

Excerpts from Ian McLeod's message of 2013-08-08 07:29:14 -0700: > On Wed, 2013-08-07 at 11:00 -0700, Clint Byrum wrote: > > Flexibility can also be looked at as complexity. Complexity in Nova > > is expensive in many ways. But just poking a few more holes into > > Nova via the API would be a simpl

Re: [openstack-dev] Python overhead for rootwrap

Excerpts from Joshua Harlow's message of 2013-08-08 10:39:38 -0700: > A very neat option. I hadn't thought about tasks having policies on them. > > It does seem like a correct way to go, and a way that could help in some of > the rootwrap area. > > Good idea jay, the taskflow devs I think are st

Re: [openstack-dev] Oslo.exception being dropped??

Taking a total guess here... But, I reckon that it's usefulness now that oslo.* are being spun off into "real projects" means that the shared dependency is becoming a problem. e.g. oslo.config and oslo.messaging shouldn't both include it, so should a whole oslo.exception library be created for

[openstack-dev] [nova][vmware] a blueprint and bugs needing attention

I have a couple things that need some action (they're becoming problems). This blueprint is not accepted... but the associated patch is merged already! Can we just get the paperwork on this one caught up? * https://blueprints.launchpad.net/nova/+spec/vmware-configuration-section ** https://review

[openstack-dev] Oslo.exception being dropped??

Hi recently I was working with some cinder code and noticed that oslo.exception is being dropped from it (and other projects). It seems connected back to this bug: https://bugs.launchpad.net/oslo/+bug/1208734 https://github.com/openstack/oslo-incubator/blob/master/MAINTAINERS#L118 I'm just won

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

Just an idea how this could go (without saying just use anvil). Taking from how anvil is doing it the following might work: 1. In devstack pass all the requirement files to multipip to get a unified list back. 2. Use yumfind (maybe a similar utility that integrates with apt-get/apt also?) to scan

Re: [openstack-dev] Python overhead for rootwrap

A very neat option. I hadn't thought about tasks having policies on them. It does seem like a correct way to go, and a way that could help in some of the rootwrap area. Good idea jay, the taskflow devs I think are starting to consider this idea and how it might be possible. There is as u said

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

Seems pretty similar. Has anyone been using that in production scenarios?? On 8/8/13 4:10 AM, "Pádraig Brady" wrote: >On 08/07/2013 06:54 PM, Monty Taylor wrote: >> >> >> On 08/07/2013 12:53 PM, Joshua Harlow wrote: >>> I agree triple-o will help a lot here although I would disagree that >>> p

Re: [openstack-dev] Keystone Split Backend LDAP Hang Problem

Adam, I want to thank for your responses as I am coming up to speed. If I don't get yanked off to fill some other project holes, Keystone knowledge and support will become my full time job here at HP. Mark From: Adam Young [mailto:ayo...@redhat.com] Sent: Wednesday, August 07, 2013 6:55 PM To:

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On Thu, Aug 8, 2013 at 11:34 AM, Monty Taylor wrote: > I'd be more happy about depending on RDO - we already said that we're ok > with depending on Ubuntu Cloud Archive for Ubuntu flavors. Basically, I > don't want devstack to depend on repos that we don't think is reasonable > to tell end users w

Re: [openstack-dev] Blueprint for Nova native image building

There is a current proposal in glance that is receiving development attention towards "importing" images asynchronously from a variety of sources. The import feature is plugin-based, so it would be easy to add on the ability and a plugin to do something like importing base os installs. The bluepri

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On 08/08/2013 12:58 PM, Pádraig Brady wrote: > On 08/08/2013 02:10 PM, Monty Taylor wrote: >> >> >> On 08/05/2013 02:03 PM, Dean Troyer wrote: >>> [Moving a discussion from https://review.openstack.org/40019 to the ML >>> to get a wider audience] >>> >>> We've been around this block more than onc

Re: [openstack-dev] [climate] Mirantis proposal to extend Climate to support virtual resources reservation

Hi Nikolay, Relying on Heat for orchestration is obviously the right thing to do. But there is still something in your design approach that I am having difficulties to comprehend since the beginning. Why do you keep thinking that orchestration and reservation should be treated together? That's

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On 08/08/2013 02:10 PM, Monty Taylor wrote: > > > On 08/05/2013 02:03 PM, Dean Troyer wrote: >> [Moving a discussion from https://review.openstack.org/40019 to the ML >> to get a wider audience] >> >> We've been around this block more than once so let's get it all >> documented in one place and s

Re: [openstack-dev] the plan the plan the havana doc plan

Anne Gentle wrote: > Let me know your input on "continuous release with bug tracking" for the > guides in the list above. If you have additional ideas, I'd love to hear > them. I'm definitely pondering the integrated programs doc strategies > and open to ideas. We've been discussing on openstack-do

Re: [openstack-dev] Blueprint for Nova native image building

On Thu, Aug 08, 2013 at 09:28:51AM -0500, Ian McLeod wrote: > On Wed, 2013-08-07 at 12:05 -0400, Russell Bryant wrote: > > On 08/07/2013 10:46 AM, Daniel P. Berrange wrote: > > > On Tue, Aug 06, 2013 at 12:20:00PM -0400, Russell Bryant wrote: > > >> On 08/06/2013 11:53 AM, Ian Mcleod wrote: > > >>>

Re: [openstack-dev] Blueprint for Nova native image building

On Wed, 2013-08-07 at 11:00 -0700, Clint Byrum wrote: > Excerpts from Ian McLeod's message of 2013-08-06 15:06:34 -0700: > > On Tue, 2013-08-06 at 16:02 -0300, Monty Taylor wrote: > > > > > > On 08/06/2013 03:46 PM, Russell Bryant wrote: > > > > On 08/06/2013 12:20 PM, Russell Bryant wrote: > > >

Re: [openstack-dev] Blueprint for Nova native image building

On Wed, 2013-08-07 at 15:53 +0100, Daniel P. Berrange wrote: > On Wed, Aug 07, 2013 at 10:34:57AM -0400, Russell Bryant wrote: > > On 08/06/2013 06:06 PM, Ian McLeod wrote: > > > On Tue, 2013-08-06 at 16:02 -0300, Monty Taylor wrote: > > > The proof of concept approach is limited to full-virt hyper

Re: [openstack-dev] Blueprint for Nova native image building

On Wed, 2013-08-07 at 12:05 -0400, Russell Bryant wrote: > On 08/07/2013 10:46 AM, Daniel P. Berrange wrote: > > On Tue, Aug 06, 2013 at 12:20:00PM -0400, Russell Bryant wrote: > >> On 08/06/2013 11:53 AM, Ian Mcleod wrote: > >>> Hello, > >>> > >>> A blueprint has been registered regarding API addi

[openstack-dev] the plan the plan the havana doc plan

Hi all, The doc team has been hard at work producing new titles and improving upon the existing. We all have a lot of work to do before the Oct. 17th release but I wanted to report on the doc plans and get your input. Where we are: there are now 9 core/integrated programs needing documentation [1]

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On 08/05/2013 02:03 PM, Dean Troyer wrote: > [Moving a discussion from https://review.openstack.org/40019 to the ML > to get a wider audience] > > We've been around this block more than once so let's get it all > documented in one place and see where to go next. Skip down to > # for

Re: [openstack-dev] Osl and dangerous code merging

On Thu, 2013-08-08 at 14:32 +0200, Flavio Percoco wrote: > On 08/08/13 11:49 +0100, Daniel P. Berrange wrote: > >On Thu, Aug 08, 2013 at 11:39:44AM +0100, Mark McLoughlin wrote: > >> What do you mean by "dangerous code merging" in the subject? The body of > >> your mail doesn't make any reference t

Re: [openstack-dev] Motion to start using Gerrit for TC votes

On 08/08/2013 09:30 AM, Thierry Carrez wrote: > Mark McLoughlin wrote: >> I think what Monty might be getting at is that TC decisions would no >> longer happen by default with people voting at a particular TC meeting. >> Rather a discussion would happen on the mailing list with people casting >>

Re: [openstack-dev] Osl and dangerous code merging

On 08/08/2013 09:04 AM, Sean Dague wrote: > On 08/08/2013 07:33 AM, Boris Pavlovic wrote: >> Hi Mark, >> Sounds good. Just needs someone willing to implement it. >> >> This is very interesting for us. >> What do you think if we create a fake project that use submodules as an >> example, and

Re: [openstack-dev] [openstack][ceilometer] About Grouping Meters

On Thu, Aug 08 2013, Guangyu Suo wrote: > Yeah, we can get the info from meter name by filtering prefix of meter > name, but I think this is a little weird, and further more, for the > user-defined meter, is it a good way to make people to add a specified > prefix of their meter name? And if peopl

Re: [openstack-dev] Osl and dangerous code merging

Mark McLoughlin wrote: > The idea of using submodules has come a few times. I don't have a > fundamental objection to it, except any time I've seen submodules used > in a project they've been extremely painful for everyone involved. Last time this was raised the conclusion was that there must be a

Re: [openstack-dev] Osl and dangerous code merging

On 08/08/13 11:49 +0100, Daniel P. Berrange wrote: On Thu, Aug 08, 2013 at 11:39:44AM +0100, Mark McLoughlin wrote: What do you mean by "dangerous code merging" in the subject? The body of your mail doesn't make any reference to whatever "danger" you're seeing. On Thu, 2013-08-08 at 14:16 +0400

Re: [openstack-dev] Motion to start using Gerrit for TC votes

Mark McLoughlin wrote: > I think what Monty might be getting at is that TC decisions would no > longer happen by default with people voting at a particular TC meeting. > Rather a discussion would happen on the mailing list with people casting > their votes in gerrit as the discussion evolves and, a

Re: [openstack-dev] Osl and dangerous code merging

On 08/08/2013 07:33 AM, Boris Pavlovic wrote: Hi Mark, Sounds good. Just needs someone willing to implement it. This is very interesting for us. What do you think if we create a fake project that use submodules as an example, and then just discuss it? How this is going to work in the gate i

Re: [openstack-dev] Osl and dangerous code merging

Hi Mark, >> Sounds good. Just needs someone willing to implement it. This is very interesting for us. What do you think if we create a fake project that use submodules as an example, and then just discuss it? Best regards, Boris Pavlovic -- Mirantis Inc. On Thu, Aug 8, 2013 at 3:21 PM, Mark

Re: [openstack-dev] Osl and dangerous code merging

On Thu, 2013-08-08 at 15:11 +0400, Boris Pavlovic wrote: > Mark, > > > >> What do you mean by "dangerous code merging" in the subject? The > body of > >> your mail doesn't make any reference to whatever "danger" you're > seeing. > > > > I mean that cut and paste approach is really unsafe. For

Re: [openstack-dev] Osl and dangerous code merging

Mark, >> What do you mean by "dangerous code merging" in the subject? The body of >> your mail doesn't make any reference to whatever "danger" you're seeing. I mean that cut and paste approach is really unsafe. For example some new member is able to change oslo code directly during syncing with s

Re: [openstack-dev] Osl and dangerous code merging

On 08/08/2013 06:49 AM, Daniel P. Berrange wrote: > On Thu, Aug 08, 2013 at 11:39:44AM +0100, Mark McLoughlin wrote: >> What do you mean by "dangerous code merging" in the subject? The body of >> your mail doesn't make any reference to whatever "danger" you're seeing. >> >> On Thu, 2013-08-08 at 14

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On 08/07/2013 06:54 PM, Monty Taylor wrote: > > > On 08/07/2013 12:53 PM, Joshua Harlow wrote: >> I agree triple-o will help a lot here although I would disagree that >> package rollback is an illusion. I would call it more of a hard >> problem instead since nothing is really impossible :) > > i

Re: [openstack-dev] Request for review - Change Ic98db496: Adding VIF Driver to support Mellanox Plugin

Hi, Jenkins is happy now.. Thanks, Itzik On 08/08/2013 12:30, Eugene Nikanorov wrote: Hi Itzik, Could you please fix your patch such that Jenkins would put +1? Thanks, Eugene. On Thu, Aug 8, 2013 at 1:18 PM, Itzik Brown > wrote: Hi, I have a pat

Re: [openstack-dev] Osl and dangerous code merging

On Thu, 2013-08-08 at 11:49 +0100, Daniel P. Berrange wrote: > On Thu, Aug 08, 2013 at 11:39:44AM +0100, Mark McLoughlin wrote: > > What do you mean by "dangerous code merging" in the subject? The body of > > your mail doesn't make any reference to whatever "danger" you're seeing. > > > > On Thu,

Re: [openstack-dev] Osl and dangerous code merging

On Thu, Aug 08, 2013 at 11:39:44AM +0100, Mark McLoughlin wrote: > What do you mean by "dangerous code merging" in the subject? The body of > your mail doesn't make any reference to whatever "danger" you're seeing. > > On Thu, 2013-08-08 at 14:16 +0400, Boris Pavlovic wrote: > > Hi All, > > > > C

Re: [openstack-dev] [Heat] as-update-policy implementation details

On 08/08/13 06:59, Chan, Winson C wrote: Proposal for the implementation is documented at https://wiki.openstack.org/wiki/Heat/Blueprints/as-update-policy. Please review and provide feedback. Looks pretty good to me. I think there's a simpler way to trigger updates to the instances based on

Re: [openstack-dev] Motion to start using Gerrit for TC votes

On Thu, 2013-08-08 at 10:55 +0200, Thierry Carrez wrote: > Monty Taylor wrote: > >> * How do we handle proxies ? Giving temporary +2 to a non-TC member > >> sounds like a bit of pain > > > > I do not think we'd need proxies anymore - as the vote wouldn't have to > > happen within the IRC meeting.

Re: [openstack-dev] Osl and dangerous code merging

What do you mean by "dangerous code merging" in the subject? The body of your mail doesn't make any reference to whatever "danger" you're seeing. On Thu, 2013-08-08 at 14:16 +0400, Boris Pavlovic wrote: > Hi All, > > Could somebody answer me, why we are merging oslo code in other projects > and d

[openstack-dev] Osl and dangerous code merging

Hi All, Could somebody answer me, why we are merging oslo code in other projects and don't use git submodules (http://git-scm.com/book/en/Git-Tools-Submodules) Best regards, Boris Pavlovic -- Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@l

Re: [openstack-dev] [openstack][ceilometer] About Grouping Meters

2013/8/8 Julien Danjou > On Thu, Aug 08 2013, Guangyu Suo wrote: > > > Any ideas ? > > The meter name should be sufficient to have such information, no? > Yeah, we can get the info from meter name by filtering prefix of meter name, but I think this is a little weird, and further more, for the us

Re: [openstack-dev] Request for review - Change Ic98db496: Adding VIF Driver to support Mellanox Plugin

Hi Itzik, Could you please fix your patch such that Jenkins would put +1? Thanks, Eugene. On Thu, Aug 8, 2013 at 1:18 PM, Itzik Brown wrote: > Hi, > > I have a patch waiting for review. > > https://review.openstack.org/#**/c/35189/- > Adding VIF Drive

[openstack-dev] Request for review - Change Ic98db496: Adding VIF Driver to support Mellanox Plugin

Hi, I have a patch waiting for review. https://review.openstack.org/#/c/35189/ - Adding VIF Driver to support Mellanox Plugin. I'll appreciate any comment/review. Thanks, Itzik ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http:/

Re: [openstack-dev] [openstack][ceilometer] About Grouping Meters

On Thu, Aug 08 2013, Guangyu Suo wrote: > Any ideas ? The meter name should be sufficient to have such information, no? -- Julien Danjou # Free Software hacker # freelance consultant # http://julien.danjou.info signature.asc Description: PGP signature _

Re: [openstack-dev] Motion to start using Gerrit for TC votes

Monty Taylor wrote: >> * How do we handle proxies ? Giving temporary +2 to a non-TC member >> sounds like a bit of pain > > I do not think we'd need proxies anymore - as the vote wouldn't have to > happen within the IRC meeting. Maybe it's just me, but I usually wait for the meeting to actually m

[openstack-dev] [openstack][ceilometer] About Grouping Meters

Hello, Ceilometer Team, For now, the results listing meters are not grouped, even we can filter the results by resource_id, project_id or meter_name, but I don't think this is a good way to group the meters. See an example: suo@ustack:~/devstack$ ceilometer meter-list +--

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On Tue, Aug 06, 2013 at 11:36:44PM -0300, Monty Taylor wrote: > > > On 08/06/2013 11:14 PM, Robert Collins wrote: > > On 7 August 2013 11:22, Jay Buffington wrote: > > > >> ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so > >> $(VENV)/lib/python2.6/site-packages/ > >> > >> Why is

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On Wed, Aug 07, 2013 at 05:43:19PM +, Joshua Harlow wrote: > Interesting, I should look into conary. > > I was hoping that DNF (the yum rewrite) would be a little better at this > stage, but it still seems a ways off. I don't know about what future plans the developers may have, but currently

Re: [openstack-dev] Blueprint review

Hi John. On Wed 07 Aug 2013 (15:56), Joe Gordon wrote: > Can you provide more detail in the BP, there isn't very much to review it > on right now. Thanks for your interest, I've updated it a bit [1]. [1] https://blueprints.launchpad.net/nova/+spec/multiple-image-cache-handlers > > On Wed, Aug