This will be the first official PTL election for Cue, and I would be
honored to serve another term leading the project for the M Cycle.
Cue is a relatively new project in Openstack, and was approved into the Big
Tent during Liberty. I have been involved with Cue from the beginning,
Thanks for starting this thread Josh.
On Fri, Sep 11, 2015 at 12:26 PM, Joshua Harlow
> Hi all,
> I was reading over the TC IRC logs for this week (my weekly reading) and I
> just wanted to let my thoughts and comments be known on:
Hello OpenStack TC and stackers!
We’ve submitted a patch to add Cue to the OpenStack project list.
For those not familiar, Cue is a Message Broker Provisioning and Lifecycle
Management service for OpenStack. We’ve focused initially on RabbitMQ, and
Having not been very active in Trove for the past few months, it’s time to
step down from the core team.
I’ll be focusing primarily on Cue going forward, getting it included into
the Big Tent, and making it production worthy.
From RedDwarf to Trove to Onwards and Upwards!
The Cue team will be crashing the Designate contributors meetup Friday at
1:20pm, in room 214.
Come find us there!
OpenStack Development Mailing List (not for usage questions)
Cue is holding a design session to talk about some of the priorities for
Liberty, Thursday from 3:20pm to 4:00pm at the couches outside of room 220.
Come and join us to learn more!
On Mon, Apr 20, 2015 at 12:07 PM, Fox, Kevin M firstname.lastname@example.org wrote:
Another parallel is Manilla vs Swift. Both provides something like a share
for users to store files.
The former is a multitenant api to provision non multitenant file shares.
The latter is a multitenant api to provide
On Wed, Apr 8, 2015 at 4:45 PM, Min Pae sputni...@gmail.com wrote:
an under-the-clould service ? - That is not what I am after here.
I think the thread went off on a tangent and this point got lost. A user
facing notification system absolutely should be a web centric protocol, as
On Mon, Mar 23, 2015 at 10:40 AM, Joshua Harlow harlo...@outlook.com
Greetings all stackers,
I propose that we add Min Pae to the taskflow-core team.
Min has been actively contributing to taskflow for a while now, both in
helping prove taskflow out (by being
+1 to all the nominations. Many thanks to the departing cores for their
contributions and bringing Trove to where it is today.
On Feb 5, 2015, at 9:02 AM, Craig Vyvial cp16...@gmail.com wrote:
+1 +1 +1
I think these nominations will help grow the trove community.
On Thu, Feb
Thanks to those who I met personally at the Summit for your feedback on the
For those that don’t know what Cue is, we’re building a Message Broker
Provisioning service for Openstack. More info can be found here:
Since the summit, we’re
We will be meeting folks that are interested in discussing Cue at *10 AM on
Friday at the Trove Pod* in the “Program Pods” section of the Design Summit.
Looking forward to seeing folks there!
On Tue, Nov 4, 2014 at 10:26 AM, Vipul Sabhaya vip...@gmail.com wrote:
vision, I plan to host a meetup in the design summit
area of the Le Meridien on *Friday morning*. More details to come.
OpenStack-dev mailing list
On Oct 30, 2014, at 1:47 AM, Nikhil Manchanda nik...@manchanda.me wrote:
I'm proposing to add Iccha Sethi (iccha on IRC) to trove-core.
Iccha has been working with Trove for a while now. She has been a
very active reviewer, and has provided insightful comments on
On Fri, Sep 19, 2014 at 4:23 AM, Eoghan Glynn egl...@redhat.com wrote:
My understanding of Zaqar is that it's like SQS. SQS uses distributed
which have a few unusual properties :
Amazon SQS makes a best effort to preserve order in messages, but
On Tue, Aug 26, 2014 at 11:43 AM, Robert Myers myer0...@gmail.com wrote:
On Tue, Aug 26, 2014 at 8:54 AM, Tim Simpson tim.simp...@rackspace.com
From: Sergey Gotliv [sgot...@redhat.com]
Sent: Tuesday, August 26, 2014 8:11 AM
On Tue, May 6, 2014 at 10:09 AM, McReynolds, Auston amcreyno...@ebay.comwrote:
On 5/6/14, 2:31 AM, Nikhil Manchanda nik...@manchanda.me wrote:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has
On Sun, Apr 6, 2014 at 9:36 AM, Russell Bryant rbry...@redhat.com wrote:
On 04/06/2014 09:02 AM, Christopher Yeoh wrote:
On Sun, Apr 6, 2014 at 10:06 AM, Hopper, Justin justin.hop...@hp.com
At this point the guard that Nova needs to
On Mon, Jan 27, 2014 at 1:43 PM, Don Kehn dek...@gmail.com wrote:
check with the trove folks they might be testing percona.
We don’t test Nova or other Openstack pieces against Percona. We do test
Percona as a underlying datastore within Trove though.
On Mon, Jan 27, 2014 at 2:34 PM,
Sent from my iPhone
On Dec 30, 2013, at 10:50 AM, Craig Vyvial cp16...@gmail.com wrote:
On Mon, Dec 30, 2013 at 12:00 PM, Greg Hill greg.h...@rackspace.com wrote:
On Dec 27, 2013, at 4:48 PM, Michael Basnight mbasni...@gmail.com wrote:
Im proposing Auston
they don’t need the logs, they can perform the
delete directly in Swift.
From: Vipul Sabhaya vip...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
Date: Friday, December 20, 2013 2:14 AM
I am fine with requiring the deployer to update default values, if they
don’t make sense for their given deployment. However, not having any value
for older/existing instances, when the code requires it is not good. So
let’s create a default datastore of mysql, with a default version, and set
Yep agreed, this is a great idea.
We really only need two API calls to get this going:
- List available logs to ‘save’
- Save a log (to swift)
Some additional points to consider:
- We don’t need to create a record of every Log ‘saved’ in Trove. These
entries, treated as a Trove resource aren’t
On Sun, Oct 27, 2013 at 4:29 PM, Ilya Sviridov isviri...@mirantis.comwrote:
Totally agree, however current concept supposes working with type and
version as different entities, even if it is the attributes on one thing -
The reason for storing it as separate models can be
On Mon, Oct 21, 2013 at 2:04 PM, Michael Basnight mbasni...@gmail.comwrote:
On Oct 21, 2013, at 1:40 PM, Tim Simpson wrote:
2. I also think a datastore_version alone should be sufficient since
the associated datastore type will be implied:
When i brought this up it was generally
On Oct 1, 2013, at 3:37 PM, Michael Basnight mbasni...@gmail.com wrote:
On Oct 1, 2013, at 3:06 PM, Ilya Sviridov isviri...@mirantis.com wrote:
On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson tim.simp...@rackspace.com
Hi fellow Trove devs,
With the Designate project ramping up,
On Sep 26, 2013, at 8:49 AM, Michael Basnight mbasni...@gmail.com wrote:
On Sep 25, 2013, at 7:16 PM, Craig Vyvial wrote:
So we have a blueprint for this and there are a couple things to point out
that have changed since the inception of this BP.
Mail list logo