+1
On Feb 2, 2016 4:07 PM, "James Y. Li" wrote:
> +1
>
>
> On Tue, Feb 2, 2016 at 1:33 PM, Devdatta Kulkarni <
> devdatta.kulka...@rackspace.com> wrote:
>
>> Hi team,
>>
>> I would like to propose Vijendar Komalla for our core team. Vijendar has
>> been actively
>>
The problem was caused by references to stackforge/python-mistralclient.git in
contrib/devstack/lib/mistral; our devstack job in Jenkins was failing because
it could not clone the client [1].
Merging [2] updated those references to their new openstack-owned locations.
Our issues are
The app-resource spec [1] is as much documentation as we have on the new
resources at present. It does illustrate some imagined healthy interactions
with the proposed API, though looking at the mentioned Glance example I can see
several ways we can improve our specs, for example by explaining
the following addition to the solum-core group[1]:
+ Ed Cranford (ed--cranford)
Please reply to this email to indicate your votes.
Thanks,
Adrian Otto
[1] https://review.openstack.org/#/admin/groups/229,members Current
Members
___
OpenStack
Happy Corethday to the both of you!
On 10/1/14, 1:10 PM, Adrian Otto adrian.o...@rackspace.com wrote:
Thanks everyone for your feedback on this. The adjustments have been made.
Regards,
Adrian
On Sep 30, 2014, at 10:03 AM, Adrian Otto adrian.o...@rackspace.com
wrote:
Solum Core Reviewer
through MuranoPL class(es) and generated temporary file which
contains Plant UML definitions for the entire graph
* Plant UML is called with that file as input
* Plant UML processes input file somehow and uses GraphViz to build output image
On Tue, Apr 1, 2014 at 11:25 PM, Ed Cranford
ed.cranf
What about Graphviz?
On 4/1/14, 1:34 PM, Timur Sufiev tsuf...@mirantis.com wrote:
Hello!
Recently we've made an attempt to make MuranoPL class definitions more
conceivable for everyone, and decided to use UML diagrams for that
purpose. The most obvious (and quick) solution was to use a
Conductor was the first phase of
https://wiki.openstack.org/wiki/Trove/guest_agent_communication whose
proposed future phases include turning conductor into a source of truth for
trove to ask about instances, and then using its own datastore separate
from the host db anyway.
The purpose of the
done by Trove
code which has access to that database anyway. Moving root history to
Conductor will complicate things without giving us any benefit.
Thanks,
Tim
--
*From:* Ed Cranford [ed.cranf...@gmail.com]
*Sent:* Friday, December 20, 2013 10:13 AM