So nova has a massive .mailmap that maps multiple addresses for one
person together. I'm wondering if a) it's still needed, and b) if it
is, should we push it into all the repositories - e.g. have a single
global copy and an automated job to push updates around.
-Rob
--
Robert Collins
Distingui
Excerpts from Steven Dake's message of 2013-10-25 12:12:54 -0700:
> Hi,
>
> I would like to propose Randall Burt for Heat Core. He has shown
> interest in Heat by participating in IRC and providing high quality
> reviews. The most important aspect in my mind of joining Heat Core is
> output a
+1
Regards,
Alex
Joshua Harlow wrote on 26/10/2013 09:29:03 AM:
>
> An idea that others and I are having for a similar use case in
> cinder (or it appears to be similar).
>
> If there was a well defined state machine/s in nova with well
> defined and managed transitions between states then
Hi Drew,
Unfortunately there's not much up to date documentation on how to write an
api extension (its on the TODO list), but as Phil mentioned looking at
existing extensions like scheduler_hints is a good place to start.
You'll need to decide whether you want to write a V2 and V3 API version of
Hi,
I am trying to set up a deployment via neutron ryu plugin, but it seems
there is no way to set up it right with the latest neutron code and the
latest ryu code . And the document about ryu with openstack is not updated
for a long time. https://github.com/osrg/ryu/wiki/OpenStack
Who is maintai
I think I will try to have a unconference at the HK summit about ideas the
cinder developers (and the taskflow developers, since it's not a concept that
is unique /applicable to just cinder) are having about said state machine (and
it's potential usage).
So look out for that, be interesting to
Deletes should only be allowed when the vm is in a power off state. This will
allow consistent state transition.
Thanks
Al
On Oct 26, 2013, at 8:55 AM, Joshua Harlow wrote:
> I think I will try to have a unconference at the HK summit about ideas the
> cinder developers (and the taskflow deve
Potentially,
Although I think the lack of formalization and visibility (and the ability to
easily change its transitions) into the state machine is at this point causing
part of this pain.
If the state machine was well defined (and adjustable - to a degree...) then
you could imagine only allow
This is a bit off topic , but in general it seems to me that the state
transitions as you said are not clearly defined for many openstack components.
Is there any effort underway to define these? As the software gets bigger and
bigger this will help both developers and operators.
Thanks & Regar
There is at least 1 such effort being discussed in cinder, other projects I can
not say. I am hoping to gain more traction there as taskflow[1] I think can
provide (or help provide) a foundation to help here. Taskflow itself has a well
defined state machine [2]. But it's in the end up to the pro
If someone takes effort to learn Vim to the point when he/she develops code
in it, they most definitely have their preferred settings already, why
overwrite them? If those settings conflict with the style guide -- it has
been said, pep8 and hacking check will notify.
I always thought that leaving
11 matches
Mail list logo
