In case you're interested, there is another choice of 'workflow
engine' you can refer to: http://docs.openstack.org/developer/mistral/
Hope you'll find it interesting :-)
On Sat, Jan 9, 2016 at 10:33 AM, ESWAR RAO wrote:
> Thanks Joshua for the clear
A very Happy New Year 2016 !!
I have started a new group "Open Containers" on LinkedIn to provide a
common platform to all the Containers and Docker enthusiasts and passionate
people. In this group, we will be discussing about the Linux and Docker
containers runtimes as well as
On Sat, 2016-01-09 at 18:11 +0530, Nitin Agarwal wrote:
> Hello Everyone,
> A very Happy New Year 2016 !!
> I have started a new group "Open Containers" on LinkedIn to provide a
> common platform to all the Containers and Docker enthusiasts and
> people. In this group, we will
On 01/08/2016 08:34 AM, Amrith Kumar wrote:
As Kevin suggests, I'm adding [sahara] to the subject line.
Others in sahara who now see this thread, apologies for sending you a delayed
invitation to the party. There's still lots of food and beer so come on in!
thanks for reposting
When creating volume type, extra_specs is optional in body, as can be seen
from API document, http://developer.openstack.org/api-ref-blockstorage-v2.html
but I notice that in cinder-client, the method of create in
VolumeTypeManager dose not take extra_specs in body,
> From: Pradeep Kilambi [mailto:pkila...@redhat.com]
> Sent: Thursday, January 07, 2016 9:15 PM
> > > alternatively, it was discussed that maybe adding a zaqar notifier
> > > would be useful. that way, aodh-notifier would send alarm to zaqar and
> > > you could configure it to
I'm a bit confused. This thread started by liusheng asking to remove the
notifications to the bus, and I replied saying that we do want to use this
capability in Vitrage. What is the notifier plugin that you suggested? Is it
the same notifier that liusheng referred to, or
'os-initialize_connection' is a important API for Cinder to complete the volume
but there is no record in Cinder(Blockstorage) API Document(1).
Also some developers want to find the description for the
So should we add this API to the
During the Liberty release the OpenStackClient (OSC) team ran into an issue
that is documented here:  and here: . In short, commands were
clobbering each other because they had the same command name.
A longer example is this, OSC has a command for listing compute flavors (os