Excerpts from Devananda van der Veen's message of 2014-06-06 12:04:08 -0700:
> I have just announced the Ironic mid-cycle in Beaverton, co-located
> with Nova. That's the "main one" for Ironic.
>
> However, there are many folks working on both TripleO and Ironic, so I
> wouldn't be surprised if th
On Tue, May 27, 2014 at 03:25:10PM +0530, abhishek jain wrote:
> Hi Daniel
>
> Thanks for the help.
> The end result of my setup is that the VM is stucking at Spawning state on
> my compute node whereas it is working fine on the controller node.
> Therefore I'm comparing nova-compute logs of both
On Sat, May 31, 2014 at 01:25:04AM +0800, Qin Zhao wrote:
> Hi all,
>
> When I run Icehouse code, I encountered a strange problem. The nova-compute
> service becomes stuck, when I boot instances. I report this bug in
> https://bugs.launchpad.net/nova/+bug/1313477.
>
> After thinking several days,
On 6/6/2014 1:40 AM, Joe Gordon wrote:
Hi All,
In the nova meeting this week, we discussed some of the shortcomings of
our recent bug day, one of the ideas that was brought up was to do a
better job of keeping track of stale bugs (assigned but not worked on)
[0]. To that end I put something to
On Jun 6, 2014, at 8:12 PM, Devananda van der Veen
wrote:
> I think some things are broken in the oslo-incubator db migration code.
>
> Ironic moved to this when Juno opened and things seemed fine, until recently
> when Lucas tried to add a DB migration and noticed that it didn't run... So I
My comments are inline below...
On Fri, Jun 6, 2014 at 8:47 AM, Jamie Hannaford <
jamie.hannaf...@rackspace.com> wrote:
>Whether the same one is used for each service or a new one is used for
> each service doesn't matter.
>
>
> Yes, it does matter IMO - and here are the reasons why:
>
> 1
Hi folks,
There was a small discussion about the better way of doing sql operations
for vni synchronization with the config.
Initial proposal was to handle those in chunks. Carl also suggested to
issue a single sql query.
I've did some testing with my sql and postgress.
I've tested the following s
+1 for #2.
In addition, I think it would be nice if barbican maintains versioned data
on updates. Which means consumer of barbican APIs can request for data
from older version if needed. This can address concerns expressed by
German. For example if certificates were updated on barbican but somehow
> If a user makes a change to a secret
Can we just disable that by making LBaaS a separate user so it would store
secrets under LBaaS 'fake' tenant id?
Eugene.
On Sun, Jun 8, 2014 at 7:29 AM, Jain, Vivek wrote:
> +1 for #2.
>
> In addition, I think it would be nice if barbican maintains versi
