> On May 6, 2014, at 2:31 AM, Nikhil Manchanda wrote:
>
>
> Hello folks:
>
> I'm proposing to add Craig Vyvial (cp16net) to trove-core.
>
> Craig has been working with Trove for a while now. He has been a
> consistently active reviewer, and has provided insightful comments on
> numerous revie
have had over the last 6mo (and before
when Trove was a wee little RedDwarf). Thanks to the other PTLs for helping
me shape my PTL role into something tangible. And of course a special shout
out to ttx for helping to keep me focused :) I will be still be working on
Trove full time.
--
Michael Bas
"Lowery, Mathew" writes:
> We have a need to support multiple versions of a single datastore with
> a single set of disk-image-builder elements. Let's take MySQL on
> Ubuntu as an example. 5.5 is already present in
> trove-integration. Let's say we want to add 5.6 to coexist. Let's also
> assume
Denis Makogon writes:
> Let me elaborate a bit.
>
> [...]
>
> Without storing static API contract capabilities gonna be 100% corrupted,
> because there's no API description inside Trove.
Im not sure i understand what you mean here.
> About reloading, file should not be reloaded, file is a stati
Giuseppe Galeota writes:
> Hi Michael,
> I'm using this unique guide: "
> http://docs.openstack.org/developer/trove/dev/manual_install.html";.
Thats developer guide uses virtualenv, but its by no means necessary.
> Can you help me with a more useful guide that makes trove working?
Id love to h
Daniel Salinas writes:
> https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API#REPLICATION
>
> I have updated the wiki page to reflect the current proposal for
> replication verbiage with some explanation of the choices. I would like to
> open discussion here regarding that verbia
Denis Makogon writes:
> Goodday, OpenStack DВaaS community.
>
>
> I'd like to start conversation about guestagent security issue related
> to backup/restore process. Trove guestagent service uses AES with 256 bit
> key (in CBC mode) [1] to encrypt backups which are stored at predefined
>
On Jan 23, 2014, at 5:10 PM, Mark McClain wrote:
>
> On Jan 23, 2014, at 5:02 PM, Russell Bryant wrote:
>
>> Greetings,
>>
>> Last cycle we had A "feature proposal deadline" across some projects.
>> This was the date that code associated with blueprints had to be posted
>> for review to make
On Jan 23, 2014, at 12:20 PM, Greg Hill wrote:
> The blueprint is here:
>
> https://wiki.openstack.org/wiki/Trove/scheduled-tasks
>
> So I have basically two questions:
>
> 1. Does anyone see a problem with defining the repeating options as a single
> field rather than multiple fields?
Im fin
On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote:
> My thoughts so far:
>
> /datastores//configuration/parameters (Option Three)
> + configuration set without an associated datastore is meaningless
> + a configuration set must be associated to exactly one datastore
> + each datastore must have
> On Dec 27, 2013, at 2:48 PM, Michael Basnight wrote:
>
> Howdy,
>
> Im proposing Auston McReynolds (amcrn) to trove-core.
The people have spoken. Welcome to trove core, Auston.
___
OpenStack-dev mailing list
OpenStack-dev@lists.ope
Howdy,
In the spirit of getting together to get stuff done, Trove is having a mid
cycle meetup in Austin, TX. We are having it Wednesday, February 19, 2014
to Friday, February 21, 2014, in downtown Austin at the Capital Factory,
which is a hip startup incubator. See [1] for more information.
The
> +1
> >
> > On Dec 30, 2013, at 1:13 PM, Vipul Sabhaya wrote:
> >
> >> +1
> >>
> >> Sent from my iPhone
> >>
> >> On Dec 30, 2013, at 10:50 AM, Craig Vyvial wrote:
> >>
> >>> +1
> >>>
> &g
Howdy,
Im proposing Auston McReynolds (amcrn) to trove-core.
Auston has been working with trove for a while now. He is a great reviewer.
He is incredibly thorough, and has caught more than one critical error with
reviews and helps connect large features that may overlap (config edits +
multi data
erver, and guest configurations are described at
> wiki page. [1]
>
> [1] https://wiki.openstack.org/wiki/TroveDBInstanceLogOperation
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.o
We are canceling our next two weekly meetings. They occur on Dec 25 and Jan
1. See you all on the 8th for our next regularly scheduled trove meeting.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailm
To accommodate a wider audience, Trove is changing our meeting time from
Wednesday, 2000 UTC to Wednesday, 1800 UTC. As always, we are in
#openstack-meeting-alt, and everyone is welcome to join!
How do i edit the iCal feed / google calendar on the main Meeting page?
signature.asc
Description:
> On Nov 11, 2013, at 11:27 AM, Joe Gordon wrote:
>
>
>> On Sun, Nov 10, 2013 at 3:50 PM, Sean Dague wrote:
>> Not that I know of. I've considered writing my own gerrit front end
>> mail service to do just that, because I agree, the current mail volume
>> and granularity is not very good. If I
On Oct 23, 2013, at 7:03 AM, Illia Khudoshyn wrote:
> Hi Denis, Michael, Vipul and all,
>
> I noticed a discussion in irc about adding a single entry point (sort of
> 'SuperManager') to the guestagent. Let me add my 5cent.
>
> I agree with that we would ultimately avoid code duplication. But f
On Oct 23, 2013, at 10:54 AM, Ilya Sviridov wrote:
> Besides the strategy of selecting the default behavior.
>
> Let me share with you my ideas of configuration management in Trove and how
> the datastore concept can help with that.
>
> Initially there was only one database and all configurati
On Oct 22, 2013, at 10:35 AM, Michael Basnight wrote:
> Top posting cuz im a baller. We will get this fixed today. PS clint i like
> the way you think ;)
>
> https://review.openstack.org/#/c/53176/
>
Now that this is merged, and there is no stable/havana for clients, Ive
this argument doesn't hold up.
>>
>> If the trove developers found some repo in the world and slapped an
>> apache license AND said:
>>
>> Copyright 2012 Michael Basnight
>>
>> in the header, and Thomas put that in debian/copyright, the Debian FTP
>
On Oct 22, 2013, at 9:34 AM, Tim Simpson wrote:
> > It's not intuitive to the User, if they are specifying a version alone.
> > You don't boot a 'version' of something, with specifying what that some
> > thing is. I would rather they only specified the datastore_type alone, and
> > not have
>>>
>>> Sure, we could also "improve clarity" by compiling a list of all the
>>> cities in the world where some OpenStack code has been authored ... but
>>> *why*?
>>>
>>
>> If you don't know who the copyright holders are,
On Oct 21, 2013, at 1:57 PM, Nikhil Manchanda wrote:
>
> The image approach works fine if Trove only supports deploying a single
> datastore type (mysql in your case). As soon as we support
> deploying more than 1 datastore type, Trove needs to have some knowledge
> of which guestagent manager c
On Oct 21, 2013, at 1:55 PM, Mark McLoughlin wrote:
> On Tue, 2013-10-22 at 01:45 +0800, Thomas Goirand wrote:
>> On 10/20/2013 09:00 PM, Jeremy Stanley wrote:
>>> On 2013-10-20 22:20:25 +1300 (+1300), Robert Collins wrote:
>>> [...]
OTOH registering one's nominated copyright holder on the f
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 discussed as being confusing. Id
>> like to use type and rely on having a def
On Oct 18, 2013, at 12:30 PM, Tim Simpson wrote:
> 1. I think since we have two fields in the instance object we should make a
> new object for datastore and avoid the name prefixing, like this:
I agree with this.
> 2. I also think a datastore_version alone should be sufficient since the
> as
On Oct 21, 2013, at 10:02 AM, Tim Simpson wrote:
> Can't we say that about nearly any feature though? In theory we could put a
> hold on any tests for feature work saying it
> will need to be redone when Tempest integrated is finished.
>
> Keep in mind what I'm suggesting here is a fairly triv
Top posting…
Id like to see these in the tempest tests. Im just getting started integrating
trove into tempest for testing, and there are some prerequisites that im
working thru with the infra team. Progress is being made though. Id rather not
see them go into 2 different test suites if we can
> On Oct 8, 2013, at 4:16 AM, Denis Makogon wrote:
>
> Hi, guys, i'd like to make few questions clear to all of us.
>
> First one is resource clean-up in Trove.
>
> According to few previous meetings we decided not to rollback each of
> resources which is under trove-quota-management controll.
On Oct 1, 2013, at 11:20 PM, McReynolds, Auston wrote:
> I have a few questions left unanswered by the blueprint/wiki:
>
> #1 - Should the true default configuration-group for a service-type be
>customizable by the cloud provider?
Yes
>
> #2 - Should a user be able to enumerate the ent
On Oct 2, 2013, at 9:21 AM, Craig Vyvial wrote:
> If a configuration is updated that is attached to N instances then those
> instances will be updated with the configuration overrides. This will keep
> the configuration n-sync[hah 90s boy band reference] with instances that have
> it attached.
On Oct 1, 2013, at 7:19 PM, Vipul Sabhaya wrote:
>
> So from this API, I see that a configuration is a standalone resource that
> could be applied to N number of instances. It's not clear to me what the API
> is for 'applying' a configuration to an existing instance.
https://wiki.openstack.o
On Oct 1, 2013, at 7:06 PM, Vipul Sabhaya wrote:
> On Oct 1, 2013, at 3:37 PM, Michael Basnight wrote:
>
>> On Oct 1, 2013, at 3:06 PM, Ilya Sviridov wrote:
>>
>>>
>>> On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson
>>> wrote:
>>> Hi
> On Oct 1, 2013, at 3:06 PM, Ilya Sviridov wrote:
>
>
>> On Tue, Oct 1, 2013 at 6:45 PM, Tim Simpson
>> wrote:
>> Hi fellow Trove devs,
>>
>> With the Designate project ramping up, its time to refactor the ancient DNS
>> code that's in Trove to work with Designate.
>>
>> The good news is s
Thx for getting this squared away zigo!!
On Oct 1, 2013, at 10:40 AM, Thomas Goirand wrote:
> Hi,
>
> First of all, before I reply, I'd like to tell that hopefully, I believe
> we're fine in this specific case (at least on the Debian side of
> things). Though it really shouldn't have happen, and
On Oct 1, 2013, at 8:00 AM, Nicholas Chase wrote:
>
>
> On 10/1/2013 10:53 AM, Michael Basnight wrote:
>
>> Well this sucks. Im not sure im a fan of renaming it because of the previous
>> existence of a package. Renaming is not fun. Ill let the more experienced
&
On Oct 1, 2013, at 6:45 AM, Thomas Goirand wrote:
> Hi,
>
> I have just found out that there's already a source package called
> "trove" in Debian:
>
> http://packages.debian.org/source/sid/trove
>
> Lucky, I don't think it will clash with OpenStack trove since it
> produces libtrove-java* .de
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.
>
> https://blueprints.launchpad.net/trove/+spec/configuration-management
>
> This is an overview of the API calls fo
On Sep 26, 2013, at 6:07 AM, Ilya Sviridov wrote:
> The blueprint https://blueprints.launchpad.net/trove/+spec/mysql-ha
>
> In order to become production ready DBaaS, Trove should provide ability to
> deploy and manage high available database.
>
> There are several approaches to achive HA in My
But I got suddenly full. Interesting thing that is.
Sent from my digital shackles
> On Sep 23, 2013, at 7:16 PM, Joshua Harlow wrote:
>
> I ran that but world peace didn't happen.
>
> Where can I get my refund?
>
> Sent from my really tiny device...
>
>> On Sep 23, 2013, at 6:47 PM, "Monty
Howdy,
Id like to self nominate for the Trove PTL.
Ive been the acting Trove PTL during the Havana incubation timeframe. During
this 6 month period I've learned a TON about what it takes to be a PTL, and I
know I will learn a lot more in the next 6mo if im elected. A bit of history;
before I
Lukjanov
> Savanna Technical Lead
> Mirantis Inc.
>
>> On Sep 13, 2013, at 22:35, Clint Byrum wrote:
>>
>> Excerpts from Michael Basnight's message of 2013-09-13 08:26:07 -0700:
>>>> On Sep 13, 2013, at 6:56 AM, Alexander Kuznetsov wrote:
>&g
On Sep 16, 2013, at 9:05 AM, Matthias Runge wrote:
> Signed PGP part
> On 16/09/13 17:51, Michael Basnight wrote:
>
> >> Currently, just the docs refer to reddwarf, resulting in build
> >> issues when building docs.
> >>
> >
> > Whew! Ill fix it
On Sep 16, 2013, at 12:24 AM, Matthias Runge wrote:
> On 16/09/13 05:30, Monty Taylor wrote:
>>
>>
>> On 09/15/2013 01:47 PM, Alex Gaynor wrote:
>>> Falcon was included as a result of Marconi moving from stackforge to
>>> being incubated. sphinxcontrib-programoutput doesn't appear to have been
On Sep 16, 2013, at 8:42 AM, Matthias Runge wrote:
> On 16/09/13 17:36, Michael Basnight wrote:
>
>>>
>>> Not to forget python-troveclient, which is currently a hard
>>> requirement for Horizon.
>>>
>>> During the review for python-tr
On Sep 13, 2013, at 10:00 AM, Alexander Kuznetsov wrote:
> Hadoop Ecosystem is not only datastore technologies. Hadoop has other
> components: Map Reduce framework, distributed coordinator - Zookepeer,
> workflow management - Oozie, runtime for scripting languages - Hive and Pig,
> scalable ma
On Sep 13, 2013, at 9:05 AM, Alexander Kuznetsov wrote:
>
>
>
> On Fri, Sep 13, 2013 at 7:26 PM, Michael Basnight wrote:
> On Sep 13, 2013, at 6:56 AM, Alexander Kuznetsov wrote:
> > On Thu, Sep 12, 2013 at 7:30 PM, Michael Basnight
> > wrote:
> > On
On Sep 13, 2013, at 6:56 AM, Alexander Kuznetsov wrote:
> On Thu, Sep 12, 2013 at 7:30 PM, Michael Basnight wrote:
> On Sep 12, 2013, at 2:39 AM, Thierry Carrez wrote:
>
> > Sergey Lukjanov wrote:
> >
> >> [...]
> >> As you can see, resources provision
Sent from my digital shackles
On Sep 12, 2013, at 10:20 PM, John Griffith wrote:
>
>
>
> On Thu, Sep 12, 2013 at 11:08 PM, Monty Taylor wrote:
>> Hey everybody!
>>
>> You know how, when you want to make a new project, you basically take an
>> existing one, like nova, copy files, and then
On Sep 12, 2013, at 2:39 AM, Thierry Carrez wrote:
> Sergey Lukjanov wrote:
>
>> [...]
>> As you can see, resources provisioning is just one of the features and the
>> implementation details are not critical for overall architecture. It
>> performs only the first step of the cluster setup. We’v
On Sep 11, 2013, at 8:42 AM, Andrei Savu wrote:
> +1
>
> I guess this will also clarify how Savanna relates to other projects like
> OpenStack Trove.
Yes the conversations around Trove+Savanna will be fun at the summit! I see
overlap between our missions ;)
>
> -- Andrei Savu
>
> On Wed,
On Sep 6, 2013, at 8:19 AM, Giuseppe Galeota wrote:
> Dear all,
> this is a technical question. I would try to modify the source code of Trove
> in order to create databases instances using Postgres engine. I think that it
> is necessary to modify the "create" method in the "InstanceController"
On Sep 6, 2013, at 8:30 AM, Giuseppe Galeota wrote:
> Dear all,
> I think that there is a poor documentation about Trove architecture and
> operation.
Thanks for your interest in trove. I agree. As ptl I will devote time (now that
the h3 madness has slowed for us) to doc'ing better information
On Aug 18, 2013, at 4:32 PM, Robert Collins wrote:
> Thanks to -infra folk over this weekend, we're now in the openstack/
> namespace for gerrit, git etc.
>
> Anyone consuming these from git - such as trove - will need to update
> to pull from the new repository, or you'll get stale code.
Thx f
On Aug 16, 2013, at 6:52 AM, Boris Pavlovic wrote:
> Hi all,
>
> We (OpenStack contributors) done a really huge and great work around DB code
> in Grizzly and Havana to unify it, put all common parts into oslo-incubator,
> fix bugs, improve handling of sqla exceptions, provide unique keys, an
Maybe sudo the 2nd cmd?
Sent from my digital shackles
On Aug 10, 2013, at 10:57 AM, Roman Gorodeckij wrote:
> ok.. nothing changes..
>
> stack@hp:~/devstack$ sudo pip install -I oslo.config==1.1.1
> Downloading/unpacking oslo.config==1.1.1
> Downloading oslo.config-1.1.1.tar.gz (75kB): 75kB do
tps://review.openstack.org/#/c/40239/
On Jul 29, 2013, at 4:02 PM, Jay Pipes wrote:
> On 07/29/2013 05:12 PM, Michael Basnight wrote:
>> Rackspace is interested in creating a redis implementation for Trove, as
>> well as haomai wang is looking to leverage Trove for leveldb integration.
>
Rackspace is interested in creating a redis implementation for Trove, as well
as haomai wang is looking to leverage Trove for leveldb integration. Ive done a
proof of concept for redis and it was ~200 lines of guest impl code and I had
to make one small change to the core create API, but one tha
Same bat time, same bat channel. Wed, 2000UTC in #openstack-meeting-alt. We
will be discussing clustering api if anyone is interested in following along.
https://wiki.openstack.org/wiki/Meetings/TroveMeeting
___
OpenStack-dev mailing list
OpenStack-dev@
On Jul 17, 2013, at 7:40 AM, Thierry Carrez wrote:
> Milestone-proposed branches were created for Keystone, Glance, Nova,
> Horizon, Neutron, Cinder, Ceilometer and Heat in preparation for the
> havana-2 milestone publication Thursday.
>
> You can find candidate tarballs at:
> http://tarballs.ope
On Jul 16, 2013, at 7:45 PM, Haomai Wang wrote:
>
> 在 2013-7-17，上午4:42，Michael Basnight 写道：
>
>> On Jul 16, 2013, at 12:49 PM, Mark McLoughlin wrote:
>>
>>> Hey,
>>>
>>> On Tue, 2013-07-16 at 10:37 -0700, Michael Basnight wrote:
>
Nachi, If/when you do pin it down to a particular version in
openstack/requirements, plz add me as a reviewer. Id like to make sure we dont
break trove. <3
On Jul 16, 2013, at 1:47 PM, Nachi Ueno wrote:
> Hi Folks
>
> Thanks
> I'll update code with Jinja2
>
>
On Jul 16, 2013, at 12:49 PM, Mark McLoughlin wrote:
> Hey,
>
> On Tue, 2013-07-16 at 10:37 -0700, Michael Basnight wrote:
>> Official Title: OpenStack Database as a Service
>> Initial PTL: Michael Basnight
>>
>> Mission Statement: To provide scalable an
Also, jinja2 is in requirements. We have no specific requirements on a
particular version so feel free to pin it to a specific. We (trove) use it to
generate config templates.
https://github.com/openstack/requirements/commit/96f38365ce94d2135f7744c93bae0ce92a747195
On Jul 16, 2013, at 1:10 PM,
Official Title: OpenStack Database as a Service
Initial PTL: Michael Basnight
Mission Statement: To provide scalable and reliable Cloud Database as a Service
functionality for both relational and non-relational database engines, and to
continue to improve its fully-featured and extensible open
On Jul 15, 2013, at 7:22 PM, Gareth wrote:
> Hi, all
>
> There are some common codes in most of projects, such as opnstack/common, db,
> and some else (?). I know a good way is using 'import oslo' is ok, instead of
> copy those codes here and there. And now we already have project oslo and
>
Meeting ended Wed Jul 10 20:59:26 2013 UTC. Information about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-07-10-20.00.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-07-10-
Same bat time, same bat channel. 2000 UTC in #openstack-meeting-alt
https://wiki.openstack.org/wiki/Meetings/TroveMeeting
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Jul 3, 2013, at 2:03 AM, Thierry Carrez wrote:
> Michael Basnight wrote:
>> 1) Companies who are looking at trove are not yet looking at heat, and a
>> hard dependency might stifle growth of the product initially
>
> Integration with other OpenStack 'integrate
On Jul 2, 2013, at 8:17 PM, Clint Byrum wrote:
> Excerpts from Michael Basnight's message of 2013-07-02 19:04:01 -0700:
>> On Jul 2, 2013, at 3:52 PM, Clint Byrum wrote:
>>
>>> Excerpts from Michael Basnight's message of 2013-07-02 15:17:09 -0700:
Howdy,
one of the TC requests fo
On Jul 2, 2013, at 3:52 PM, Clint Byrum wrote:
> Excerpts from Michael Basnight's message of 2013-07-02 15:17:09 -0700:
>> Howdy,
>>
>> one of the TC requests for integration of trove was to integrate heat. While
>> this is a small task for single instance installations, when we get into
>> clu
Howdy,
one of the TC requests for integration of trove was to integrate heat. While
this is a small task for single instance installations, when we get into
clustering it seems a bit more painful. Id like to submit the following as a
place to start the discussion for why we would/wouldnt integr
74 matches
Mail list logo
