On 05/04/2016 11:46 AM, Clark Boylan wrote:
On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote:
On 04/05/16 15:05 +, Amrith Kumar wrote:
I'm emailing the ML on the subject of a review ongoing in the Trove project
regarding image building[1].
TL;DR
One of the most frequent questions t
On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote:
> On 04/05/16 15:05 +, Amrith Kumar wrote:
> >I'm emailing the ML on the subject of a review ongoing in the Trove project
> >regarding image building[1].
> >
> >TL;DR
> >
> >One of the most frequent questions that new users of Trove ask i
On Wed, May 4, 2016, at 08:55 AM, Flavio Percoco wrote:
> On 04/05/16 15:05 +, Amrith Kumar wrote:
> >I'm emailing the ML on the subject of a review ongoing in the Trove project
> >regarding image building[1].
> >
> >TL;DR
> >
> >One of the most frequent questions that new users of Trove ask i
On 04/05/16 15:05 +, Amrith Kumar wrote:
I'm emailing the ML on the subject of a review ongoing in the Trove project
regarding image building[1].
TL;DR
One of the most frequent questions that new users of Trove ask is how and where
to get guest images with which to experiment with Trove,
I'm emailing the ML on the subject of a review ongoing in the Trove project
regarding image building[1].
TL;DR
One of the most frequent questions that new users of Trove ask is how and where
to get guest images with which to experiment with Trove, and how to build these
images for themselves.
We all had a week full of meetings last week and I'm not sure that we have
anything significantly new on the agenda for the weekly meeting on the 4th.
So, if I don't hear anyone object, I'll send an email out by 4pm Eastern Time
today canceling the Trove weekly meeting for the 4th of May.
Thank
Here is the updated (final) notes from the Trove design summit in
Austin, TX.
Some changes from yesterday's email are highlighted.
Changes are marked with "::NOTE::"
-amrith
Python3 support
- make python34 a voting test in the gate (was already done, so no
action required)
- peterstac to
Here are my notes from the first two days of the Trove design summit
sessions. I will send another tomorrow after we finish the contributor
meetup.
Action items will follow tomorrow.
Thanks,
-amrith
Python3 support
- make python34 a voting test in the gate (was already done, so no
action r
As several of us will be at summit next week, there will be no weekly
Trove meeting.
The complete list of Trove design summit sessions can be found at [1].
There are also several talks about Trove [2] ... [5].
Thanks,
-amrith
[1] https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#T
Thanks Kevin, much appreciated.
I've added [trove] to the subject so it shows up on their mail filters.
-amrith
> -Original Message-
> From: Fox, Kevin M [mailto:kevin@pnnl.gov]
> Sent: Friday, April 22, 2016 1:11 PM
> To: OpenStack Development Mailing List (not for usage questions)
Thanks Amrith, this looks great!
Just added the new dashboard to my Gerrit dashboard.
Cannot think on anything else we could need.
2016-04-16 10:45 GMT-03:00 Amrith Kumar :
> At the Trove meeting last week, I agreed to send out a simple way in
> which we can all view the patches that are in nee
: [openstack-dev] [trove] Adding release notes to changes
On 2016-04-17 19:04, Amrith Kumar wrote:
>> -Original Message-
>> > From: Andreas Jaeger [mailto:a...@suse.com]
>> > Sent: Sunday, April 17, 2016 4:31 AM
>> > To: OpenStack Development Mail
On 2016-04-17 19:04, Amrith Kumar wrote:
>> -Original Message-
>> > From: Andreas Jaeger [mailto:a...@suse.com]
>> > Sent: Sunday, April 17, 2016 4:31 AM
>> > To: OpenStack Development Mailing List (not for usage questions)
>> >
>> >
> -Original Message-
> From: Andreas Jaeger [mailto:a...@suse.com]
> Sent: Sunday, April 17, 2016 4:31 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [trove] Adding release notes to changes
>
> On 04/16/201
On 04/16/2016 05:07 PM, Amrith Kumar wrote:
> Folks,
>
> We are now using reno[1] for release notes in trove, trove-dashboard,
> and python-troveclient.
Note that the trove-dashboard changes are not published and tested at
all, you do not have set it up in project-config yet,
Andreas
> [...]
--
ntire text in quotes. For bug numbers, it's
probably easiest just to use a format like 'Bug 1234567' to avoid this issue.
Thanks,
Peter
-Original Message-
From: Amrith Kumar [mailto:amr...@tesora.com]
Sent: April-16-16 11:07 AM
To: openstack-dev@lists.openstack.org
Subj
Folks,
We are now using reno[1] for release notes in trove, trove-dashboard,
and python-troveclient.
If you submit a change to any one of these repositories, that is going
to be visible to a user (i.e. not changes that only impact tests, or are
procedural changes relating to management of the rep
At the Trove meeting last week, I agreed to send out a simple way in
which we can all view the patches that are in need of review.
In the past, as we got closer to release milestones, we have used the
starredby: method. I first remember using this when Nikhil
proposed it in the Juno/Liberty timefr
The minutes of the Trove weekly meeting are at
http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-04-13-18.00.html
AGREED:
We decided that changes from the proposal bot (requirements, translations) can
be approved on master by a single +2.
The python34 gate jobs can be changed from
There are several blueprints for Trove that are awaiting review [1]. Many of
these are targeted for Newton, some were originally started for Mitaka but
missed the deadlines and are still being considered for Newton.
Would all reviewers please take a look at these and provide feedback. Several
o
On Thu, Apr 07, 2016 at 12:24:07PM +, Amrith Kumar wrote:
> The trove failure is [1], same as described in email yesterday[2].
>
> We have a gracious volunteer who offered to help with stable management
> changes, and I've emailed him a request to have this and some other changes
> proposed
On 07/04/16 12:24 +, Amrith Kumar wrote:
The trove failure is [1], same as described in email yesterday[2].
We have a gracious volunteer who offered to help with stable management
changes, and I've emailed him a request to have this and some other changes
proposed into other stable branche
The trove failure is [1], same as described in email yesterday[2].
We have a gracious volunteer who offered to help with stable management
changes, and I've emailed him a request to have this and some other changes
proposed into other stable branches. That request is below:
> You had offered to
Minutes from today's weekly Trove meeting are at
http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-04-06-18.00.html
Detailed session schedule for summit is at
http://bit.ly/trove-newton-design-summit
-amrith
__
Due to one release-critical issue spotted in Trove during RC1 testing, a
new release candidate was created for Mitaka. You can find the RC2
source code tarball at:
https://tarballs.openstack.org/trove/trove-5.0.0.0rc2.tar.gz
Unless new release-critical issues are found that warrant a last-minu
We have weekly team meetings on Wednesdays at 18:00 UTC in
#openstack-meeting-alt
Meeting agenda is at https://wiki.openstack.org/wiki/Meetings/TroveMeeting
We have a lengthy agenda for today so please review ahead of time.
-amrith
___
- Original Message -
> On Wed, Mar 23, 2016 at 07:52:10PM +, Amrith Kumar wrote:
> > The meeting bot died during the meeting and therefore the logs on eavesdrop
> > are useless. So I've had to get "Old-Fashioned-Logs(tm)".
> >
> > Action Items:
> >
> > #action [all] If you have a p
On Wed, Mar 23, 2016 at 07:52:10PM +, Amrith Kumar wrote:
> The meeting bot died during the meeting and therefore the logs on eavesdrop
> are useless. So I've had to get "Old-Fashioned-Logs(tm)".
>
> Action Items:
>
> #action [all] If you have a patch set that you intend to resume work
> o
The meeting bot died during the meeting and therefore the logs on eavesdrop are
useless. So I've had to get "Old-Fashioned-Logs(tm)".
Action Items:
#action [all] If you have a patch set that you intend to resume work
on, please put an update in it to that effect so we don't go abandon it under
This morning, Craig tagged RC1 on trove[1] and a short while ago I tagged RC1
on trove-dashboard[2]. The python-troveclient for Mitaka was tagged some days
ago[3].
At this point, changes merged into master will be headed for Newton.
Any changes that are required for Mitaka RC2 will have to be b
Excerpts from Amrith Kumar's message of 2016-03-18 13:44:34 +:
> Folks on the Trove team,
>
> I've certainly learnt a lot of things going through the Mitaka release
> process thus far, and I'm sure there are more things that I will learn as
> well. But, I want to send this to all so that we
Minutes of the OpenStack Trove meeting held today are at:
http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-16-18.00.html
If there are topics you would like to suggest for the summit, please do
that soon so we can start consolidating and making a schedule that will
accommodate as m
Folks on the Trove team,
I've certainly learnt a lot of things going through the Mitaka release process
thus far, and I'm sure there are more things that I will learn as well. But, I
want to send this to all so that we don't 'learn' the same things again in
Newton.
1. The release calendar is
And.. we now have Trove ready and producing a release candidate for the
end of the Mitaka cycle! You can find the RC1 source code tarball at:
https://tarballs.openstack.org/trove/trove-5.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this RC1
we can have
some of that this Thursday when I’m in your stomping grounds.
Thanks,
-amrith
From: Craig Vyvial [mailto:cp16...@gmail.com]
Sent: Tuesday, March 15, 2016 12:22 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [trove] PTL non-candidacy
All,
I've decided to no
All,
I've decided to not run for Trove PTL for the upcoming Newton cycle.
I've enjoyed working with everyone in the Trove community. We've
accomplished many features over the last cycle. I am positive with the
roadmap we've talked about that Trove will continue to grow with the next
leadership. I
Please propose sessions that you would like to include at the design summit in
Austin.
I will fill in the items that were agreed to at the mid-cycle over the next
couple of days.
An etherpad is available for this at:
https://etherpad.openstack.org/p/trove-newton-proposed-sessions
-amrith
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It is that time of the year ... The weekly Trove meeting is held at 1800
UTC each Wednesday in #openstack-meeting-alt[1]. This weekend, people
will be going through the twice annual ritual of readjusting their
clocks and changing batteries in smoke
Minutes of the OpenStack Trove meeting held today are at:
http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-09-18.00.html
--
Amrith Kumar, CTO | amr...@tesora.com
Tesora, Inc | @amrithkumar
125 CambridgePark Drive, Suite 400 | http://www.t
rote:
On 3/8/2016 3:17 PM, Matt Riedemann wrote:
On 3/8/2016 1:18 PM, Amrith Kumar wrote:
Matt,
See inline below.
-amrith
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent: Tuesday, March 08, 2016 2:00 PM
To: openstack-dev@lists.openstack.org
Subject: R
>>>>> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
>>>>> Sent: Tuesday, March 08, 2016 2:00 PM
>>>>> To: openstack-dev@lists.openstack.org
>>>>> Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
>>>>
: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
failing in stable branches; bug 1538506
On 3/8/2016 12:52 PM, Matt Riedemann wrote:
On 3/8/2016 12:35 PM, Amrith Kumar wrote:
Matt,
The correct solution for liberty is that we should fix
: [openstack-dev] [trove][stable] proboscis tests randomly
failing in stable branches; bug 1538506
On 3/8/2016 12:52 PM, Matt Riedemann wrote:
On 3/8/2016 12:35 PM, Amrith Kumar wrote:
Matt,
The correct solution for liberty is that we should fix the tests.
Here's why I believe that th
On 3/8/2016 1:18 PM, Amrith Kumar wrote:
Matt,
See inline below.
-amrith
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent: Tuesday, March 08, 2016 2:00 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [trove][stable] proboscis
Matt,
See inline below.
-amrith
> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Tuesday, March 08, 2016 2:00 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
>
See below.
> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Tuesday, March 08, 2016 1:53 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
> failing in stable bra
mann [mailto:mrie...@linux.vnet.ibm.com]
Sent: Tuesday, March 08, 2016 12:11 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
failing in stable branches; bug 1538506
On 3/8/2016 10:17 AM, Matt Riedemann wrote:
This is a call for help on
rd to hearing your feedback on this.
Thanks,
-amrith
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
Sent: Tuesday, March 08, 2016 12:11 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
failing in stable b
dev@lists.openstack.org
> Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
> failing in stable branches; bug 1538506
>
>
>
> On 3/8/2016 10:17 AM, Matt Riedemann wrote:
> > This is a call for help on resolving bug 1538506 [1] where the
> > probosc
> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Tuesday, March 08, 2016 12:11 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly
> failing in stable branches; bug 1538506
>
On 3/8/2016 10:17 AM, Matt Riedemann wrote:
This is a call for help on resolving bug 1538506 [1] where the proboscis
tests randomly fail on the stable branches with something like:
TypeError: create() got an unexpected keyword argument 'slave_of'
Craig Vyvial has a proposed stable/kilo change
This is a call for help on resolving bug 1538506 [1] where the proboscis
tests randomly fail on the stable branches with something like:
TypeError: create() got an unexpected keyword argument 'slave_of'
Craig Vyvial has a proposed stable/kilo change [2] but it has some
issues, at least from me
Members of the Trove team,
Earlier today I tagged Trove release 5.0.0.0b3[1] and python-troveclient
version 2.1.0[2]. A request has also been submitted to update constraints to
reflect the new client version[3].
Thanks to all who submitted code for features in this release. I know that
there a
Hello,
I would like to request a feature freeze for the following feature: Add
support for CouchDB backup & restore [1]. The code for this feature is
complete and up for review [2]. The integration tests requires a new
library which was added to global-requirements [3]. Unit tests and
integra
I'd like to request a feature freeze exception for "Implement backup and restore functionality for db2 express c" [1] and "Implement database and user functions for CouchDB" [2]
The patch implementing db2 backup and restore is up for review [3] and has covered unit tests.
CouchDB user and database
I'd like to request a feature freeze exception for "CouchDB Configuration
Groups". [1]
The code/tests for this feature are complete and have been in review [2]
since Feb 17. The FFE is being requested so that Sonali (or myself) address
the nits reviewers left and to have more time to review/test e
I'd like to request a feature freeze exception for "Vertica Cluster Grow
and Shrink". [1]
The code/tests for this feature are complete and have been in review [2]
since Feb 17. The FFE is being requested so that the reviewers have more
time to review/test etc. Hopefully the review process can
I'd like to request a feature freeze exception for "Vertica
configuration groups". [1]
The code/tests for this feature are complete and have been in review [2]
since Feb 23. The FFE is being requested so that the reviewers have more
time to review/test etc. Hopefully the review process can be
I'd like to request a feature freeze exception for "Add support for adding and
applying module configuration to an instance" [1]
The work was split up and several parts of this have already merged in Mitaka.
[2][3][4]. I have one more troveclient commit and a commit for the remainder of
the ser
tl;dr
-
The Trove team held its mid-cycle sprint in Raleigh, NC last week. My
thanks to Red Hat and Pete MacKinnon (IRC: pmackinn) who hosted us for
this mid-cycle meeting. Several attendees from companies active in the
project (HP, Tesora, IBM and Red Hat) attended the meeting in person and
r
On 02/18/2016 08:20 PM, Victor Stinner wrote:
> I discussed with some Trove developers who are interested to start the
> Python 3 port right now. What do you think?
Mitaka b3 is just around the corner (in less than 10 days now), so at
the end, it doesn't change things much, unless all of your patc
Message-
> From: Victor Stinner [mailto:vstin...@redhat.com]
> Sent: Thursday, February 18, 2016 9:42 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [trove] Start to port Trove to Python 3 in
> Mitaka cycle?
>
> Le
Le 18/02/2016 14:15, Amrith Kumar a écrit :
Let's definitely discuss this again once you have all the changes that you feel
should be merged for Mitaka ready.
I don't like working on long patch series. In my experience, after more
than 4 patches, it's more expensive to maintain the patch seri
16
[2] https://review.openstack.org/#/c/256057/
-Original Message-
From: Victor Stinner [mailto:vstin...@redhat.com]
Sent: Thursday, February 18, 2016 7:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [trove] Start to port Trove to Python
6 7:20 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka
> cycle?
>
> Hi,
>
> When I began to work on porting Trove to Python 3, I was blocked by MySQL-
> Python which is no
Hi,
When I began to work on porting Trove to Python 3, I was blocked by
MySQL-Python which is not compatible with Python 3. I tried a big change
replacing MySQL-Python with PyMySQL, since other OpenStack services also
moved to PyMySQL. But tests fail and I'm unable to fix them :-/
https://rev
openstack.org
> Subject: Re: [openstack-dev]
> [trove][neutron][cinder][swift][ceilometer][nova][keystone][sahara][glance
> ][neutron-lbaas][imm] stylistic changes to code, how do we handle them?
>
> On 01/12/2016 06:13 AM, Amrith Kumar wrote:
> [...]
> > I did not exhaustiv
On 01/12/2016 06:13 AM, Amrith Kumar wrote:
[...]
> I did not exhaustively verify this but
[...]
A fair question to ask then is, why are you proposing these patches?
> I created a quick poll to tally results
oh no, not another survey! :) Sometimes I feel that survey-itis[1] is a
consequence of
I see that https://review.openstack.org/264253 merged in Trove. Do you feel
that the exposure is sufficient that we should go and revert these kind(s) of
changes wholesale across the projects?
-amrith
> -Original Message-
> From: Eric Harney [mailto:ehar...@redhat.com]
> Sent: Tuesday,
On 01/12/2016 08:51 AM, Amrith Kumar wrote:
My question to the ML is this, should stylistic changes of this kind be handled
in a consistent way across all projects, maybe with a hacking rule and some
discussion on the ML first? After all, if this change is worthwhile, it is
worth ensuring that
On 12/01/16 15:01 +0100, Ihar Hrachyshka wrote:
Amrith Kumar wrote:
I've tagged this message with the projects impacted by a series of
change sets:
[trove] https://review.openstack.org/#/c/266220/
[neutron] https://review.openstack.org/#/c/266156/1
[cinder] https://re
On Tue, Jan 12, 2016 at 9:13 AM, Amrith Kumar wrote:
> Chris, Ihar,
>
> I assumed that this was stylistic based on the fact that in the places
> where I was seeing it, it seemed to be the case that the LHS was
> intuitively positive (a length, for example). I did not exhaustively verify
> this bu
Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev]
> [trove][neutron][cinder][swift][ceilometer][nova][keystone][sahara][glance
> ][neutron-lbaas][imm] stylistic changes to code, how do we handle them?
>
> On Tue, 12 Jan 2016, Amrith Kumar wrote:
>
>
On Tue, Jan 12, 2016 at 8:51 AM, Amrith Kumar wrote:
> I've tagged this message with the projects impacted by a series of change
> sets:
>
> [trove] https://review.openstack.org/#/c/266220/
> [neutron] https://review.openstack.org/#/c/266156/1
> [cinder] https://review.ope
not a fan of these changes since it messes up git blame and it becomes
harder to track down author if you have questions relating to bug/code.
that said, "if var > 0" is not the same as "if var". in the latter, var
can be any number (negative or positive) or any other datatype and it'll
evalua
On 01/12/2016 03:02 PM, Chris Dent wrote:
> On Tue, 12 Jan 2016, Amrith Kumar wrote:
>
>> if var > 0:
>> ... something ...
>>
>> To
>>
>> if var:
>> ... something ...
>
> I may be missing something but the above is not a stylistic change
> if var can ever be negative. In one of the ceilomet
Hi,
IMO if you want to do the stylistic changes - make the hacking rule for it
first. Not all of this particular changes are useful and even correct. The
explicit comparison with zero in Python where we have number of implicit
casts to bool is much better in such cases.
Thanks.
On Tue, Jan 12, 2
On Tue, 12 Jan 2016, Amrith Kumar wrote:
if var > 0:
... something ...
To
if var:
... something ...
I may be missing something but the above is not a stylistic change
if var can ever be negative. In one of the ceilometer changes[1] for
example, this change will change the flo
Amrith Kumar wrote:
I've tagged this message with the projects impacted by a series of change
sets:
[trove] https://review.openstack.org/#/c/266220/
[neutron] https://review.openstack.org/#/c/266156/1
[cinder] https://review.openstack.org/#/c/266099/2
[swift]
I've tagged this message with the projects impacted by a series of change sets:
[trove] https://review.openstack.org/#/c/266220/
[neutron] https://review.openstack.org/#/c/266156/1
[cinder] https://review.openstack.org/#/c/266099/2
[swift] https://review.openstack.o
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!
Amrith,
thanks for reposting this,
> Subject: Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core
>
> Looks like we have a consensus from the team and I’d like to welcome
> Mariam John to the Trove Core Team!
>
> I look forward to continuing to work with Mariam!
>
> Thanks,
> -Craig
&
usage questions)"
Date: 01/08/2016 03:30 PM
Subject: Re: [openstack-dev] [trove] Nominating Mariam John to Trove
Core
Looks like we have a consensus from the team and I’d like to welcome Mariam
John to the Trove Core Team!
I look forward to continuing to work
evelopment Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core
Thanks for the nomination Amrith and I think Mariam will be a great addition to
the core team.
+1
-Craig
On Jan 6, 2016, at 12:39 PM, Amrith Kumar
mailto:amr...
.openstack.org>>
Subject: [openstack-dev] [Trove][Outreachy] Add configuration groups for CouchDB
Hi all,
For those who are not aware, we have 7 Outreachy interns [0] working on
different projects on OpenStack since last Dec 7th.
Sonali (sonali5) will be working with us on Trove and we have been tr
M [mailto:kevin@pnnl.gov]
> Sent: Thursday, January 07, 2016 7:32 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
>
> While I applaud raising the issue on the mailing list to get more fo
ur project choice.
>>
>>
>>
>> -amrith
>>
>>
>>
>> *From:* Victoria Martínez de la Cruz [mailto:
>> victo...@vmartinezdelacruz.com]
>> *Sent:* Tuesday, December 22, 2015 9:21 AM
>> *To:* OpenStack Development Mailing List <
>> openstack-dev@
.
Thanks,
Kevin
From: Amrith Kumar [amr...@tesora.com]
Sent: Thursday, January 07, 2016 1:59 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
> -Original Mess
> -Original Message-
> From: michael mccune [mailto:m...@redhat.com]
> Sent: Thursday, January 07, 2016 3:12 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
>
> On 01/07/2016 11:59 AM, Amrith Kumar
>From: Fox, Kevin M
>Sent: Thursday, January 07, 2016 9:44 AM
>To: OpenStack Development Mailing List (not for usage questions)
>Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
>
>the whole hadoopish stack is unusual though. I suspect users often w
usage questions)
Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
the whole hadoopish stack is unusual though. I suspect users often want to
slice and dice all the components that run together on the cluster, where HBase
is just one component of the shared cluster. I can to
t; -Original Message-
> From: michael mccune [mailto:m...@redhat.com]
> Sent: Thursday, January 07, 2016 11:18 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
>
> thanks for bringing this up Amrith,
>
&
OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
just my 2 cents... I think you can do both. The great thing about Trove is that
its providing an abstract api so users just deal with provisioning db's, sc
t;>
Subject: Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core
A big +1.
Thanks Amrith and Mariam!
2016-01-06 17:03 GMT-03:00 Peter Stachowski
mailto:pe...@tesora.com>>:
I agree!
+1
Peter
-Original Message-
From: Vyvial, Craig [mailto:craig.vyv...@hpe.com<
List (not for usage questions)
> Subject: Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core
>
> Thanks for the nomination Amrith and I think Mariam will be a great
> addition to the core team.
>
> +1
>
> -Craig
>
> On Jan 6, 2016, at 12:39 PM, Amrith Kumar amr
Message-
> From: Fox, Kevin M [mailto:kevin@pnnl.gov]
> Sent: Wednesday, January 06, 2016 7:32 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [trove] Adding support for HBase in Trove
>
> just my 2 cents... I think you can
ting a whole cluster
management system for Trove that already exists.
Thanks,
Kevin
From: Amrith Kumar [amr...@tesora.com]
Sent: Wednesday, January 06, 2016 3:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [t
TL;DR Should Trove treat HBase as a special database because one use case is as
part of a large multi-node Hadoop cluster, and therefore either not support it
at all, or necessarily use Sahara to provision and manage a cluster? There are
pro's and con's and it is argued that the con's outweigh t
I agree!
+1
Peter
-Original Message-
From: Vyvial, Craig [mailto:craig.vyv...@hpe.com]
Sent: January-06-16 2:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Nominating Mariam John to Trove Core
Thanks for the nomination
Thanks for the nomination Amrith and I think Mariam will be a great addition to
the core team.
+1
-Craig
On Jan 6, 2016, at 12:39 PM, Amrith Kumar
mailto:amr...@tesora.com>> wrote:
Members of the Trove team,
I would like to nominate Mariam John (johnma on IRC) to the Trove core review
team.
201 - 300 of 851 matches
Mail list logo
