Hey folks:
There's not much to discuss on the Agenda for this week [1] and most
folks are still getting back from the Holidays, so let's cancel the
Trove meeting for this week.
We will have the Trove meeting next week on Wednesday, January 11th.
Thanks,
Nikhil
[1]
Hi Victoria:
Thanks for all your great work on Trove! Hope to see you around the
(OpenStack) block!
Cheers,
Nikhil
On Wed, Jun 8, 2016 at 4:19 PM, Peter Stachowski wrote:
> Hi Victoria,
>
>
>
> Thanks for all the help and good luck in your future work!
>
>
>
> Peter
>
>
>
>
Thanks for putting up that fix Matt.
The dependency on trunk python-troveclient (for stable/kilo) definitely
seems
screwy-- but I'm wondering if this was done for backwards compatibility
reasons?
(i.e. to ensure the latest version of python-troveclient should be able to
work
correctly against all
Hello all:
I'd like to announce that I will not be running for the position of
Trove PTL for Mitaka.
I've been PTL for 3 cycles now during which Trove has grown
immensely. We have added support for twelve different datastores --
enabling support for HA Trove instances through replication,
Hi Matt:
Yes, this is on my radar and something I'm actively looking at.
Hope to have a solution here for this pretty soon.
Appreciate the help with this and the review you put up to get the stable
branch unblocked!
Cheers,
Nikhil
On Wed, Aug 5, 2015 at 6:33 AM, Amrith Kumar amr...@tesora.com
Dear PTLs, cross-project liaisons and other interested parties:
We have a cross-project meeting tomorrow (June 23rd) at 21:00 UTC,
with the following agenda:
- Team announcements (horizontal, vertical, diagonal)
- Return request-id to caller (use thread local to store request-id)
- Main use
Hi Li:
Thanks for stepping up, and volunteering to dig into this. Your help
is much appreciated! We did talk about this at the Vancouver Summit,
but as far as I'm aware no one has started on this work for Liberty.
As I had mentioned in one of my previous emails, python-troveclient
does have the
prefer contribute.
I think you mean, we can add mgmt-cli directly into python-troveclient?
That is ok. what i should do? do i need to wirte a bp? or just write code,
push it to upstream?
--
Best
Li Tianqing
At 2015-06-12 16:52:46, Nikhil Manchanda nik...@manchanda.me wrote:
Hi Li
Hi Thomas:
I just checked and I don't see suds as a requirement for trove.
I don't think it should be a requirement for the trove debian package,
either.
Thanks,
Nikhil
On Thu, Jun 11, 2015 at 3:03 AM, Davanum Srinivas dava...@gmail.com wrote:
Thomas,
oslo.vmware (master) moved to
Thanks for all the hard work that you've put into Trove over the years.
I understand that with Cue you are going to have much less time to focus
on Trove reviews. However you are - and always will be - an integral
part of the Trove community.
Good luck on Cue!
Cheers,
-Nikhil
Vipul Sabhaya
Subject: Re:
[openstack-dev] [trove][zaqar] Trove and Zaqar integration.
Summit working session
On 11/05/15 05:49, Flavio Percoco wrote:
On 08/05/15 00:45 -0700, Nikhil Manchanda wrote:
3) The trove-guest-agent is in vm. it is connected by
taskmanager by rabbitmq. We designed
Comments inline.
Monty Taylor writes:
[...]
Might I suggest that if this is how people regularly deploy, that such a
class be included in trove proper, and that a config option be provided
like use_tenant='name_of_tenant_to_use' that would trigger the use of
the overridden novaclient class?
, 5:49 AM, Flavio Percoco fla...@redhat.com wrote:
|
| On 08/05/15 00:45 -0700, Nikhil Manchanda wrote:
| 3) The trove-guest-agent is in vm. it is connected by
taskmanager
| by rabbitmq. We designed it. But is there some prectise to do
| this?
| how to make the vm
Comments and answers inline.
Li Tianqing writes:
[...]
1) why we put the trove vm into user's tenant, not the trove's
tenant? User can login on that vm, and that vm must connect to
rabbitmq. It is quite insecure.
what's about put the tenant into trove tenant?
While the
Hi Li:
Thanks for contacting me about Trove. I'm still the PTL for Trove for
the Liberty cycle.
Looking at my inbox. I see that I have an email from you from late May
5th. Because of the volume of emails I get in my inbox, please
understand that it might sometimes take me 2-3 days to respond to
Hey folks:
There's not much to discuss on the agenda for this week [1] , so I'm
going to go ahead and cancel the Trove weekly meeting for this
week.
We will have the Trove meeting next week on Wednesday, May 6th.
Thanks,
Nikhil
[1] https://wiki.openstack.org/wiki/Meetings/TroveMeeting
Hi Benoit:
The rabbitmq server that the trove components use to communicate with
each other doesn't (and in fact _shouldn't_) necessarily be the same
rabbitmq server that the core openstack services are using for
communcation.
In most real-world deployments of OpenStack Trove that I am aware of,
Hey folks:
There's not much to discuss on the Agenda for this week [1] and most
folks are getting back from OpenStack Live, so I'd like to cancel the
Trove meeting for this week.
We will have the Trove meeting next week on Wednesday, April 22nd.
Thanks,
Nikhil
[1]
I'd like to announce my candidacy for the PTL role of the Database
(Trove) program for Liberty.
I have been the PTL for Trove for Juno, and Kilo. During this time
frame we made some really good progress on multiple fronts. In Kilo
specifically, we completed the oslo-messaging integration work
Looking back at the meeting eavesdrop, the primary reasons why we
deferred this work to Liberty was twofold:
- It wasn't a set plan based on information available to us at the time.
This being the case, we decided to wait until we had more information
regarding the requirements around this from
On Wed, Feb 11, 2015 at 1:55 AM, Flavio Percoco fla...@redhat.com wrote:
[...]
## Keep discussions open
I don't believe there's anything wrong about kicking off some
discussions in private channels about specs/bugs. I don't believe
there's anything wrong in having calls to speed up some
: Nikhil Manchanda slick...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Thursday, February 5, 2015 at 8:26 AM
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Trove] Core
Hello Trove folks:
Keeping in line with other OpenStack projects, and attempting to keep
the momentum of reviews in Trove going, we need to keep our core-team up
to date -- folks who are regularly doing good reviews on the code should
be brought in to core and folks whose involvement is dropping
Hello folks:
Since we are having the Trove Mid-Cycle meetup this week
(Feb 3-5), there will be no weekly Trove IRC meeting on Feb 4.
We'll resume our weekly IRC meeting next week, on Feb 11th.
Thanks,
Nikhil
__
OpenStack
Hi folks:
I've updated the schedule for the Trove Mid-Cycle Sprint at
https://wiki.openstack.org/wiki/Sprints/TroveKiloSprint#Schedule
and have linked the slots on the time-table to the etherpads that we're
planning on using to track the discussion.
I've also updated the page with some more
Hi Mark:
It's been a little while since I looked at this last, but as I recall these
values seem
to be used and needed only by the trove taskmanager. If you have support
for
metering messages turned on, this account gets used to look up instance
details
when sending periodic metering messages to
Hey folks:
Just a quick reminder that there will be no Weekly Trove Meeting
on Wednesday, Dec 31st. We will resume the weekly meeting next
year on January 7th.
See you in the new year!
Thanks,
Nikhil
___
OpenStack-dev mailing list
Thanks Robert!
Looks like it failed the Travis CI job due to an intermittent connectivity
issue
and I don't have the rights to kick-off the job again. I would appreciate it
if you could kick it off again when you get a chance.
Cheers,
Nikhil
On Sun, Nov 16, 2014 at 6:44 PM, Robert Collins
Thanks Sean and Amrith - for getting the patches lined up to unblock the
gate and
keep things moving.
I missed the action (just got off a plane). I'll follow up on IRC to get
the tests up and
running on python-troveclient, and on the next steps to rework the patch.
Thanks,
Nikhil
On Wed, Nov
Hey folks:
There's nothing to discuss on the BP Agenda for this week [1] as most
folks are just getting back from the summit, so I'd like to cancel the
Trove blueprint meeting for this week.
We will have the regular Trove meeting on Wednesday.
Thanks,
Nikhil
[1]
Hello folks:
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
numerous reviews. She has submitted quality code for multiple bug-fixes
in Trove, and most
Thanks everyone for the show of support.
Iccha: welcome to trove-core!
On Thu, Oct 30, 2014 at 8:41 AM, Vipul Sabhaya vip...@gmail.com wrote:
+1
On Oct 30, 2014, at 1:47 AM, Nikhil Manchanda nik...@manchanda.me
wrote:
Hello folks:
I'm proposing to add Iccha Sethi (iccha on IRC
Thanks for putting this together Doug!
I've opened https://bugs.launchpad.net/trove/+bug/1380789 to track the
changes that are needed here for Trove.
Cheers,
Nikhil
Doug Hellmann writes:
I’ve put together a little script to generate a report of the projects using
modules that used to be
Hey folks:
We have an empty agenda for the Trove Blueprint meeting tomorrow, so I'm
going to go ahead and cancel it.
We do have a few blueprints that are in-flight which need review
comments, so please take this time to review these blueprints and
provide feedback:
Hey folks:
There's nothing to discuss on the BP Agenda for this week so I'd like to
cancel the Trove blueprint meeting for this week.
There are a few blueprints that are in-flight and need reviews /
comments, so please take this time to review these blueprints and
provide feedback:
Hey folks:
There's nothing to discuss on the BP Agenda for this week and most folks
are busy with fixing and reviewing RC1 blocking bugs, so I'd like to
cancel the Trove blueprint meeting for this week.
See you guys at the regular Trove meeting on Wednesday.
Thanks,
Nikhil
Big +1 from me.
Anita has been super helpful, both with reviews and with discussions on IRC.
On Fri, Sep 26, 2014 at 8:34 AM, James E. Blair cor...@inaugust.com wrote:
I'm pleased to nominate Anito Kuno to the project-config core team.
The project-config repo is a constituent of the
I'd like to announce my candidacy for the PTL role of the Database
(Trove) program for Kilo.
I'm the current PTL for Trove for Juno, and during the Juno time frame
we made some really good progress on multiple fronts. We completed the
Neutron integration work that we had started in Icehouse.
Hello team:
Most folks are going to be out on Monday September 1st, on account of it
being Labor Day in the US. Consequently, I'd like to cancel the the
Trove blueprint meeting this week.
See you guys at the regular Trove meeting on Wednesday.
Thanks,
Nikhil
Hello folks:
I'm proposing to add Amrith Kumar (amrith on IRC) to trove-core.
Amrith has been working with Trove for a while now. He has been a
consistently active reviewer, and has provided insightful comments on
numerous reviews. He has submitted quality code for multiple bug-fixes
in Trove,
] [Trove] Proposal to add Amrith Kumar to
trove-core
Strong +1 from me!
-Original Message-
From: Nikhil Manchanda [mailto:nik...@manchanda.me]
Sent: August-26-14 3:48 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Trove] Proposal to add
Hello folks:
Just wanted to send out a quick reminder that we have the Trove Midcycle
Meetup this week (Aug 20 - 22) in Cambridge, MA. Details for the event
can be found at [1].
Since many of us will also be traveling on Aug 18th and 19th, and the
meeting agendas are light, I'm canceling the
Hey folks:
There's nothing to discuss on the BP Agenda for this week and most folks
are busy working on existing BPs and bugs, so I'd like to cancel the
Trove blueprint meeting for this week.
See you guys at the regular Trove meeting on Wednesday.
Thanks,
Nikhil
On Wed, Jul 23, 2014 at 7:28 AM, Denis Makogon dmako...@mirantis.com wrote:
[...]
Add Neutron-based configuration for DevStack to let folks try it
This makes sense to tackle; now that the neutron integration pieces have
merged in Trove (yahoo!).
However, it looks like the changes you
Tim Simpson writes:
To summarize, this is a conversation about the following LaunchPad
bug: https://launchpad.net/bugs/1325512
and Gerrit review: https://review.openstack.org/#/c/97194/6
You are saying the function _service_is_active in addition to
polling the datastore service status also
Anita Kuno writes:
[...]
Nik and I have talked. Since J2 is too far away to let a system run
without recheck capability (as Joe points out, this is not in compliance
with third party ci requirements), Nik is currently following up on
Sukdev's wiki page (if someone can help Sukdev learn
Joe Gordon writes:
[...]
This sounds very similar to the v3/v2.1 discussion happening in nova. All
OpenStack projects need to address these issues and it would be a shame if
each project chose a different solution, perhaps this is a good topic for
the TC to help tackle? As having different
Hey folks:
There's nothing to discuss on the BP Agenda for this week and most folks
are busy working on existing BPs and bugs, so I'd like to cancel the
Trove blueprint meeting for this week.
See you guys at the regular Trove meeting on Wednesday.
Thanks,
Nikhil
Denis Makogon writes:
On Mon, Jul 7, 2014 at 3:40 PM, Amrith Kumar amr...@tesora.com wrote:
Denis Makogon (dmako...@mirantis.com) writes:
[...]
I think it is totally ludicrous (and to all the technical writers who work
on OpenStack, downright offensive) to say the “docs are useless”. Not
:
On Jun 29, 2014 7:09 PM, Nikhil Manchanda nik...@manchanda.me wrote:
Long term, we're looking to move away from running the integration tests
in the third
party reddwarf-jenkins, so this should soon go away.
FWIW, in the short term, the re-trigger permissions are based on the
trove-developers
Hey folks:
There's nothing to discuss on the BP Agenda for this week and most folks
are busy working on existing BPs and bugs, so I'd like to cancel the
Trove blueprint meeting for this week.
See you guys at the regular Trove meeting on Wednesday.
Thanks,
Nikhil
Hi Anne:
Thanks for bringing this to our attention! This is definitely something
that we need to fix.
I've filed https://bugs.launchpad.net/trove/+bug/1334465 to track this
issue, and I'm hoping we'll be able to get to it during juno-2 (or
beginning of juno-3 at the latest).
Once we've got a
Denis Makogon writes:
Good day, Stackers, Trove community.
I'd like to start thread related to orchestration based resource
management. At current state Heat support in Trove is nothing else than
experimental. Trove should be able to fully support Trove as resource
management driver.
I
Isaku Yamahata writes:
[...]
2) Service Catalog - to accommodate multiple VNF services. Question: the
same problem exists with Trove which need a catalog for multiple concrete
DB implementations. Do you know which solution they will take for Juno?
Regarding to Trove, I don't know.
Any
Hello Team:
Just a quick reminder that the Trove Blueprint meeting on May 26th is
canceled since most folks will be unavailable on Memorial Day.
The next Blueprint meeting will be on Monday, June 2nd. The agenda can
be found at the usual location at:
Yes, this issue is fixed now that 94315 is merged.
On Tue, May 20, 2014 at 3:38 PM, Sergey Lukjanov slukja...@mirantis.comwrote:
As I see, the 94315 merged atm, is the issue fixed?
On Tuesday, May 20, 2014, Joe Gordon joe.gord...@gmail.com wrote:
Hi All,
If you hit an unknown error in a
Doug Shelley writes:
Very cool - thanks for providing. One question - for Trove, we have
Jenkins but also voting jobs on reddwarf - any way to change the No
Negative Feedback section to take into account reddwarf failures?
Hi Doug:
We're working on moving the reddwarf trove tests to
Just a quick reminder for the weekly Trove meeting.
https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting
Date/Time: Wednesday, 7 May - 1800 UTC / 1100 PDT / 1300 CDT
IRC channel: #openstack-meeting-alt
The Meeting Agenda can be found at
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 reviews. He has submitted quality code to multiple features in
Trove, and most
Thanks everyone for the show of support.
Craig: welcome to trove-core!
On Tue, May 6, 2014 at 1:17 PM, Vipul Sabhaya vip...@gmail.com wrote:
+1
On Tue, May 6, 2014 at 10:09 AM, McReynolds, Auston
amcreyno...@ebay.comwrote:
+1
On 5/6/14, 2:31 AM, Nikhil Manchanda nik...@manchanda.me
Hi Mat:
Some answers, and my perspective, are inline:
Lowery, Mathew writes:
As a non-core, I would like to understand the process by which core
prioritizes Gerrit changes.
I'm not aware of any standard process used by all core reviewers to
prioritize reviewing changes in Gerrit. My
Just a quick reminder for the weekly Trove meeting.
https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting
Date/Time: Wednesday, 16 April - 1800 UTC / 1100 PDT / 1300 CDT
IRC channel: #openstack-meeting-alt
The Meeting Agenda can be found at
Tim Bell writes:
From my understanding, Trove is due to graduate in the Juno release.
Is documentation for developers, operators and users not one of the
criteria
(http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements)
?
Hi Tim:
Just to
I'd like to announce my candidacy for the Database (Trove) PTL.
I'm currently a member of the Trove Core team, and have been working
on OpenStack and Trove for more than a year and a half now. I've
helped Trove grow from the tiny stackforge project that it was, to
the OpenStack Database project
Just a quick reminder for the weekly Trove meeting.
https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting
Date/Time: Wednesday 26 March - 1800 UTC / 1100 PDT / 1300 CDT
IRC channel: #openstack-meeting-alt
Meeting Agenda (https://wiki.openstack.org/wiki/Meetings/TroveMeeting):
1.
Sean Dague writes:
The Trove team said last week they could probably land the remove in
trove this week for mockito (it was on their roadmap anyway). So unless
they feel that's not doable, I think we're good.
-Sean
Yes, this was discussed at the trove IRC meeting last week, and is
Thomas Goirand writes:
On 03/18/2014 06:12 PM, Thierry Carrez wrote:
Thomas Goirand wrote:
[...]
Trove turned out to not be participating in global requirements, and
has 3 items outside of requirements.
Could you list them?
Hi Thomas:
There are 3 python packages that trove currently
Thomas Goirand writes:
[...]
All of these are in Debian already. Mockito and WSGI-Intercept, I'm the
one doing the packaging work. pexect is team maintained by the python
module team. No problem at all for the above changes.
[...]
Thanks for the confirmation on these packages, Thomas.
Much
in rdjenkins) down to the net-ssl-simple library. (This is all based
on the assumption that rdjenkins is running an older version of the
plugin.)
Thanks,
Mat
On 2/17/14, 10:13 PM, Nikhil Manchanda nik...@manchanda.me wrote:
Hi Mathew:
Nice work identifying these issues with the current Jenkins
The list of Etherpads for the design summit sessions for Trove is now
posted at:
https://wiki.openstack.org/wiki/Summit/Icehouse/Etherpads#Trove
Feel free to add any relevant notes to the Etherpads.
Thanks,
Cheers,
-Nikhil
___
OpenStack-dev mailing
It seems strange to me to treat both the datastore_type and version as
two separate entities, when they aren't really independent of each
other. (You can't really deploy a mysql type with a cassandra version,
and vice-versa, so why have separate datastore-list and version-list
calls?)
I think
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 classes to load. Hence the need
for having a datastore type API.
Just wanted to chime in that Trove also follows this approach and it's
worked pretty well for us.
+1 on Doug's suggestion to leave a comment on the patch so that two
reviewers don't end up doing the same work fixing it.
Cheers,
-Nikhil
On Fri, Oct 11, 2013 at 12:17 PM, Dolph Mathews
73 matches
Mail list logo