Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

Qijing, As a simple example, let's assume that I use this schema. I realize that it does not provide the resource provider thing that Jay talked about in a previous (couple of weeks ago) email, but I believe that it serves to illustrate how the generations are used. create table resources (

Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

I'm not thrilled that there are two API's one for a quota check and one for a consumption, and where it is up to the caller to properly return the results of one to the other. I'd much rather have consume accept the quotas and the request and 'just do it'. With that approach, the generation id's

Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

Qijing, I don't believe that this is correct. I promised to send a description to the ML, I'll do that today. -amrith On Sun, 2016-05-15 at 01:16 -0700, Qijing Li wrote: > Hi Vilobh, > > Here is my thoughts on how Delimiter uses generation-id to guarantee > sequencing. Please correct me if

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

The interwebs must've been in need of some pluming work ... 2016-05-13 06:09:37.457 | git.exc.GitCommandError: 'git remote prune --dry-run origin' returned with exit code 128 2016-05-13 06:09:37.457 | stderr: 'fatal: unable to connect to git.openstack.org: 2016-05-13 06:09:37.457 |

[openstack-dev] Trove 2016-05-11 weekly meeting notes

Here are the notes from today's Trove weekly meeting: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-05-11-18.01.html Action Items: [amrith] update infra specs to point to new BP and WF +0: Done [tellesnobrega] abandon spec on CEPH (https://review.openstack.org/#/c/256057/):

Re: [openstack-dev] Team blogs

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Monday, May 09, 2016 7:46 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Team blogs > > On 05/09/2016 06:37 PM, Joshua Harlow wrote: > > After seeing the amount of summit recaps and the

Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db

timize it now that all the tests have moved over to the new paradigm). Peter From: Amrith Kumar [mailto:amr...@tesora.com] Sent: May-08-16 8:42 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [trove] timeouts in gate-trove-python34-db I'm seeing pyth

[openstack-dev] [trove] timeouts in gate-trove-python34-db

I'm seeing python34's gate job running very long and sometimes it is timing out at 40m. There is something amiss with this and I've let Victor and Abhishek know about it. In https://review.openstack.org/#/c/313941/ which is a dummy commit (just changed README.rst) it took 37m. 2016-05-08

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

0] https://review.openstack.org/#/c/295274/ 2016-05-04 23:20 GMT-03:00 Amrith Kumar <amr...@tesora.com<mailto:amr...@tesora.com>>: As we discussed at summit, (and consistent with all of the comments) we should move ahead with the project to advance the image builder for Trove and make

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

we need to push the code, we take it over from there. 2016-05-05 11:12 GMT-03:00 Amrith Kumar <amr...@tesora.com<mailto:amr...@tesora.com>>: From: Victoria Martínez de la Cruz [mailto:victo...@vmartinezdelacruz.com<mailto:victo...@vmartinezdelacruz.com>] Sent: Thursday,

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

s work to kick-off that repository. Best, Victoria [0] https://review.openstack.org/#/c/295274/ 2016-05-04 23:20 GMT-03:00 Amrith Kumar <amr...@tesora.com<mailto:amr...@tesora.com>>: As we discussed at summit, (and consistent with all of the comments) we should move ahead with the pr

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

se see line 220 of [0] for a detailed explanation of why I am making the repository. Best, Victoria [0] https://review.openstack.org/#/c/295274/ 2016-05-04 23:20 GMT-03:00 Amrith Kumar <amr...@tesora.com<mailto:amr...@tesora.com>>: As we discussed at summit, (and consistent with a

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

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 mos

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

> -Original Message- > From: Gregory Haynes [mailto:g...@greghaynes.net] > Sent: Wednesday, May 04, 2016 3:52 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] > discussion of image building in Trove > > On Wed, May 4,

Re: [openstack-dev] [dib][trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Adding [dib] to the subject line. -amrith > -Original Message- > From: Amrith Kumar [mailto:amr...@tesora.com] > Sent: Wednesday, May 04, 2016 11:05 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> >

[openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in 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.

[openstack-dev] FW: [trove] Cancel weekly Trove meeting this week?

The Trove weekly meeting on the 4th of May is canceled. We can pick up any conversations that we need on IRC as required. Thanks, -amrith > -Original Message- > From: Amrith Kumar [mailto:amr...@tesora.com] > Sent: Monday, May 02, 2016 11:14 AM > To: OpenStack Development

[openstack-dev] [trove] Cancel weekly Trove meeting this week?

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.

Re: [openstack-dev] [horizon][release] freeze timelines for horizon in newton

ething describing this expectation and I’ll make sure that we try and stay true to it. Rob On 29 Apr 2016, at 11:26, Amrith Kumar <amr...@tesora.com<mailto:amr...@tesora.com>> wrote: In the Trove review of the release schedule this morning, and in the retrospective of the mitaka re

[openstack-dev] [trove] final notes from Trove summit design summit sessions

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

[openstack-dev] [horizon][release] freeze timelines for horizon in newton

In the Trove review of the release schedule this morning, and in the retrospective of the mitaka release process, one question which was raised was the linkage between projects like Trove and Horizon. This came up in the specific context of the fact that projects like Trove (in the form of the

[openstack-dev] [trove] notes from first two days of Trove design summit sessions

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

Re: [openstack-dev] [stable][infra] request for reviews on two requirements changes

On Sat, 2016-04-23 at 12:53 -0500, Matt Riedemann wrote: > On 4/23/2016 8:20 AM, Amrith Kumar wrote: > > Folks, > > > > Changes [1] and [2] blacklist Routes 2.3 in Mitaka and Liberty. They've > > been cherry picked from a change that merged in master. > > > >

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On Sat, 2016-04-23 at 15:25 -0400, Jay Pipes wrote: > On 04/23/2016 03:18 PM, Mike Perez wrote: > > On 14:54 Apr 18, Jay Pipes wrote: > >> On 04/16/2016 05:51 PM, Amrith Kumar wrote: > >>> - update_resource(id or resource, newsize) > >> >

[openstack-dev] [stable][infra] request for reviews on two requirements changes

Folks, Changes [1] and [2] blacklist Routes 2.3 in Mitaka and Liberty. They've been cherry picked from a change that merged in master. I would like both changes merged so I can then make corresponding changes in Trove, and then make a Trove (Mitaka) bug fix release. Thanks, -amrith [1]

Re: [openstack-dev] Summit Core Party after Austin

Many thanks Tom! > -Original Message- > From: Tom Fifield [mailto:t...@openstack.org] > Sent: Friday, April 22, 2016 5:59 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Summit Core Party after Austin > > Hi all, > > On 22/04/16 16:40, Clint Byrum wrote: > >

[openstack-dev] [trove] No weekly Trove meeting next week

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]

Re: [openstack-dev] [trove][magnum][app-catalog][all] Build unified abstraction for all COEs

e spot on, and I > very much appreciate those features in Trove. It makes for a very nice way > of dealing with databases. Thanks to the trove team for all the hard work > put in to make it work. :) > > Kevin > > From: Amrith Kuma

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

num sessions, I would certainly like to attend as I think they will help to instruct us on how you are handling a similar class of challenges to ones that we face in Trove. > Thanks for all the input. The context helps. > > -Keith > > > > On 4/22/16, 6:40 AM, "

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

11:19 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] More on the topic of DELIMITER, the Quota > Management Library proposal > > On 04/22/2016 07:51 AM, Amrith Kumar wrote: > > If it doesn't make it harder, I would like to see if we can ma

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

For those interested in one aspect of this discussion (a common compute API for bare-metal, VM's and containers), there's a review of a spec in Trove [1], and a session at the summit [2]. Please join [2] if you are able Trove Container Support Thursday, April 28, 9:50am-10:30am

Re: [openstack-dev] [stable][Openstack-stable-maint] Stable check of openstack/trove failed

The links being referenced in this email for the UNSTABLE outcomes appear to be missing. Also, I notice that a whole bunch of stable jobs failed around the same time. Would someone on stable-maint please confirm whether there was something environmental going on at the time before teams start

Re: [openstack-dev] Summit Core Party after Austin

To all who have said the Core Party was a bad thing, let me echo Sean's feelings, and add that I actually liked the core parties more than any of the others, and actually found them to be a very good thing. I too got to meet people who I would normally not have had a chance to have a

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

t support any proposal for a complex > library that takes the resource claim process out of the hands of the > services that own those resources. The simpler the interface of this > library, the better. > [amrith] my proposal would not but this email thread has got too long. Yes, simple

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

As I was preparing some thoughts for the Board/TC meeting on Sunday that will discuss this topic, I made the notes below and was going to post them on a topic specific etherpad but I didn't find one. I want to represent the view point of a consumer of compute services in OpenStack. Trove is a

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

> -Original Message- > From: Keith Bray [mailto:keith.b...@rackspace.com] > Sent: Thursday, April 21, 2016 5:11 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [magnum][app-catalog][all] Build

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Boden, Are you thinking of implementing something which would perform exponentially backed off calls to some arbitrary function till that method returns with something other than a timeout? I think that would be very versatile, and useful in a wide variety of places. Thanks, -amrith >

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

ic of DELIMITER, the Quota > Management Library proposal > > On 04/16/2016 05:51 PM, Amrith Kumar wrote: > > If we therefore assume that this will be a Quota Management Library, > > it is safe to assume that quotas are going to be managed on a > > per-project basis, where pa

Re: [openstack-dev] [trove] Adding release notes to changes

release notes to changes > > 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,

[openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

First, let me thank Vilobh, Nikhil, Duncan and others who have been working on this quota management library/service issue. Recently there have been a number of threads [1], [2], [3] on the subject of quotas and quota management. This email is partially in response to [3] but since it is too long

[openstack-dev] [trove] Adding release notes to changes

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

[openstack-dev] [trove] review dashboard, review priorities for Newton

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

[openstack-dev] [trove] Trove weekly meeting notes

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

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

ilto:a...@suse.com] > Sent: Wednesday, April 13, 2016 1:46 PM > To: Amrith Kumar <amr...@tesora.com>; OpenStack Development Mailing List > (not for usage questions) <openstack-dev@lists.openstack.org> > Cc: mkassaw...@gmail.com; Lana Brindley <openst...@lanabrindley.com&g

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Andreas, Lana, Mike, Matt, and others who've been active on this thread, I've been following this conversation about installation documentation and core vs. non-core projects from afar and was under the impression that the changes being proposed would take effect for Newton and moving forward.

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

Subject: Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One > Platform – Containers/Bare Metal? (Re: Board of Directors Meeting) > > On 11/04/16 18:05 +, Amrith Kumar wrote: > >Adrian, thx for your detailed mail. > > > > > > > >Yes, I was ho

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

ainers), and the infrastructure on which they run (Nova instances). Regards, Adrian On Apr 11, 2016, at 8:47 AM, Amrith Kumar <amr...@tesora.com<mailto:amr...@tesora.com>> wrote: Monty, Dims, I read the notes and was similarly intrigued about the idea. In particular, from the perspective of projects

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

Monty, Dims, I read the notes and was similarly intrigued about the idea. In particular, from the perspective of projects like Trove, having a common Compute API is very valuable. It would allow the projects to have a single view of provisioning compute, as we can today with Nova and get the

[openstack-dev] [trove] call to action: blueprints awaiting review

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

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

alytics] Gaming the Stackalytics > stats > > Thanks Amrith! > > I am a big supporter on including +0s. > > On 4/9/16 6:31 PM, Amrith Kumar wrote: > > Thanks to Dims and Steve for bringing this up. > > > > It has long been my opinion that +0's are invaluable fo

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

Thanks to Dims and Steve for bringing this up. It has long been my opinion that +0's are invaluable for the question asking, and for getting to understand software, and unfortunately +0's are lost in the noise. So a while ago, I posted to the ML [1] asking about making +0's more

Re: [openstack-dev] [trove][stable] [Openstack-stable-maint] Stable check of openstack/trove failed

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

[openstack-dev] [trove] Trove weekly meeting minutes

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 __

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

Stable team, the reason for this failure of py27 in kilo is https://bugs.launchpad.net/trove/+bug/1437179 The bug was fixed in liberty in commit I92eaa1c98f5a58ce124210f2b6a2136dfc573a29 and therefore, at this time, only impacts Kilo. The issue is that the flavors are coming back in

Re: [openstack-dev] [all][trove] Trove bug scrub

ave so much of backlog. How about bug fixing days or bug squashing days? I’d love to do that as well and further trim the backlog. 2016-04-05 14:44 GMT-03:00 Flavio Percoco <fla...@redhat.com<mailto:fla...@redhat.com>>: On 05/04/16 15:15 +, Amrith Kumar wrote: If you are

[openstack-dev] [all][trove] Trove bug scrub

If you are subscribed to bug notifications from Trove, you'd have received a lot of email from me over the past couple of days as I've gone through the LP bug list for the project and attempted to do some spring cleaning. Here's (roughly) what I've tried to do: -many bugs that have been

[openstack-dev] minutes of the Trove meeting 2016-03-30

Meeting minutes can be found at http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-30-18.01.txt Thanks to all who attended. -amrith __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [magnum][magnum-ui] Have magnum jobs respect upper-constraints.txt

Thanks Hongbin, I've updated the bug summary to be more generic. -amrith > -Original Message- > From: Hongbin Lu [mailto:hongbin...@huawei.com] > Sent: Wednesday, March 30, 2016 11:32 AM > To: OpenStack Development Mailing List (not for usage questions) >

Re: [openstack-dev] [release][all] What is upper-constraints.txt?

> -Original Message- > From: Andreas Jaeger [mailto:a...@suse.com] > Sent: Wednesday, March 30, 2016 9:03 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [release][all] What is upper-constraints.txt?

Re: [openstack-dev] [release][all] What is upper-constraints.txt?

> -Original Message- > From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] > Sent: Wednesday, March 30, 2016 9:01 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [release][all] What is

Re: [openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

Also: https://review.openstack.org/298482 and it's children in stable/xyz Thanks to Henry for helping review the Trove changes for this issue. -amrith > -Original Message- > From: Henry Gessau [mailto:hen...@gessau.net] > Sent: Tuesday, March 29, 2016 9:05 PM > To: OpenStack

[openstack-dev] [trove] Trove team meeting today, 1800 UTC, #openstack-meeting-alt

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

Re: [openstack-dev] [Openstack-stable-maint][stable] Stable check of openstack/trove failed

Stable maintainers, I'm happy to fix in Kilo if required, the issue is Routes 2.3. It is a neat cherry-pick. Please advise. -amrith > -Original Message- > From: A mailing list for the OpenStack Stable Branch test reports. > [mailto:openstack-stable-ma...@lists.openstack.org] > Sent:

[openstack-dev] FW: [neutron] [Bug 1563028] Re: Routes version 2.3 broke the way we register routes

ith > -Original Message- > From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of > OpenStack Infra > Sent: Monday, March 28, 2016 4:12 PM > To: Amrith Kumar <amr...@tesora.com> > Subject: [Bug 1563028] Re: Routes version 2.3 broke the way we r

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

<openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Openstack-stable-maint] Stable check of > openstack/trove failed > > On 2016-03-28 11:52:12 + (+), Amrith Kumar wrote: > > I ran this manually on stable/mitaka and it succeeded. The errors > > being reporte

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

I ran this manually on stable/mitaka and it succeeded. The errors being reported are "database is locked". Is this something in the infrastructure or do you want me to investigate further? -amrith > -Original Message- > From: A mailing list for the OpenStack Stable Branch test reports.

Re: [openstack-dev] Bots and Their Effects: Gerrit, IRC, other

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: Thursday, March 24, 2016 9:13 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] Bots and Their Effects: Gerrit, IRC, other

Re: [openstack-dev] Bots and Their Effects: Gerrit, IRC, other

Thanks for the posting because it tells me that there is a way to have bots contributed to infra (which I didn't know). I have experimented with some bots, mostly against gerrit and trying to use the rather lightweight Launchpad API. The one bot that I still operate looks at gerrit and

[openstack-dev] [trove] OpenStack Trove meeting minutes (2016-03-23)

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

Re: [openstack-dev] [keystone][ptls] Newton summit planning etherpad

I've added Keystone to the subject line. Keystone folks, please see email below from Steve! -amrith > -Original Message- > From: Anita Kuno [mailto:ante...@anteaya.info] > Sent: Tuesday, March 22, 2016 6:08 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Newton

[openstack-dev] [trove] We're open for business on Newton

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

Re: [openstack-dev] [all][infra][ptls] tagging reviews, making tags searchable

, 2016 10:37 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [all][infra][ptls] tagging reviews, making > tags searchable > > On 18/03/2016 14:19, Amrith Kumar wrote: >

[openstack-dev] [all][infra][ptls] tagging reviews, making tags searchable

As we were working through reviews for the Mitaka release, the Trove team was trying to track groups of reviews that were needed for a specific milestone, like m-1, or m-3 or in the recent days for rc1. The only way we could find was to have someone (in this instance, me) 'star' the reviews

Re: [openstack-dev] [Openstack-stable-maint][stable/liberty][trove] stable/liberty changes in Trove that are ready for merge

On 03/19/2016 01:43 AM, Tony Breeds wrote: > On Sun, Mar 13, 2016 at 12:15:23PM +0000, Amrith Kumar wrote: >> Hi, >> >> Sorry for the blast mail, this is targeted at the stable-maint team. The >> following five changes are now ready to merge. Two of them are cha

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On 03/16/2016 08:42 AM, Sean Dague wrote: > On 03/16/2016 08:27 AM, Amrith Kumar wrote: >> Nikhil, thank you for the very timely posting. This is a topic that has >> been discussed quite a bit recently within the Trove team. I've read the >> document you reference as [1] and

[openstack-dev] [trove] OpenStack Trove meeting minutes (2016-03-16)

as many of them as possible. Thanks! -amrith -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125 CambridgePark Drive, Suite 400 | http://www.tesora.com Cambridge, MA. 02140| GPG: 0x5e48849a9d21a29b signature.asc

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

into implementations, so if there are any descriptions of those requirements, I'd appreciate getting pointers to that. Thanks, -amrith [1] https://review.openstack.org/#/c/284454/ -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125

[openstack-dev] [trove] notes for Newton about the release process, learnings from Mitaka thus far

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

Re: [openstack-dev] [all][infra][ptls] tagging reviews, making tags searchable

t: Re: [openstack-dev] [all][infra][ptls] tagging reviews, making > tags searchable > > > > On 18 Mar 2016, at 7:15, Amrith Kumar wrote: > > > As we were working through reviews for the Mitaka release, the Trove > team was trying to track groups of reviews that were nee

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

I just ran stable/liberty through these tests on a sandbox and they passed. I'm not sure what caused this failure but if it persists, I'll take another look. Some changes are coming soon on master and I'll backport them to mitaka and liberty. They'll make debugging these tests a whole lot

Re: [openstack-dev] [all][infra][ptls] tagging reviews, making tags searchable

Jim, Maybe we could collaborate and build something that'd work for multiple projects? Happy to help with this. It is clearly a problem that some projects seem to be facing and there aren't any good solutions there. Thanks, -amrith > -Original Message- > From: Jim Rollenhagen

Re: [openstack-dev] [trove] PTL non-candidacy

Craig, You’ve done a ton for Trove (your first commit on the project that is visible in git is March 2012!) and it was the 25th commit in the project! It has been a pleasure and a honor working with you, with Nikhil and Michael before that. I look forward to some good backyard-bbq, and maybe

[openstack-dev] [election][trove] Trove PTL Candidacy

. -amrith -- Amrith Kumar Email: amr...@tesora.com IRC: amrith GPG: 0x5e48849a9d21a29b [1] http://stackalytics.com/?user_id=amrith=all=commits [2] http://stackalytics.com/?user_id=amrith=all=marks [3] http://www.apress.com/9781484212226 signature.asc Description: OpenPGP digital signature

[openstack-dev] [Openstack-stable-maint][stable/liberty][trove] stable/liberty changes in Trove that are ready for merge

Hi, Sorry for the blast mail, this is targeted at the stable-maint team. The following five changes are now ready to merge. Two of them are changes proposed by the bot and three of them are clearly identified as cherry-picks from changes that went into master.

[openstack-dev] [trove] Trove Newton summit planning

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

[openstack-dev] [trove] Weekly meeting time change

- -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125 CambridgePark Drive, Suite 400 | http://www.tesora.com Cambridge, MA. 02140| GPG: 0x5e48849a9d21a29b -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux

Re: [openstack-dev] [tc] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

age- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Wednesday, March 09, 2016 2:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [tc] [trove][stable] proboscis tests randomly > failing in stable branches; bug 1538506 > > > > On

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

es for libraries > > On 09/03/16 13:41 -0500, Amrith Kumar wrote: > >Doug, > > > >>> openstack/python-troveclient 2.1.0 > > > >Trove isn't there yet. You are aware of the conversation(s) we're having > about this, and there are two. > > >

Re: [openstack-dev] [tc] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly > failing in stable branches; bug 1538506 > > > > On 3/9/2016 8:54 AM, Amrith Kumar wrote: > > Matt, > > > > As I understand it, you have 4 changes up

[openstack-dev] [trove] OpenStack Trove meeting minutes (2016-03-09)

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

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

amrith -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125 CambridgePark Drive, Suite 400 | http://www.tesora.com Cambridge, MA. 02140| GPG: 0x5e48849a9d21a29b On 03/09/2016 12:26 PM, Doug Hellmann wrote: > It's time

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

17 PM, Matt Riedemann wrote: >>> >>> >>> On 3/8/2016 1:18 PM, Amrith Kumar wrote: >>>> Matt, >>>> >>>> See inline below. >>>> >>>> -amrith >>>> >>>>> -Original Message- >>&

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

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. &

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

nches; bug 1538506 > > > > 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 this is the case. > > > > In pertinent part, the backtrace from your

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, The correct solution for liberty is that we should fix the tests. Here's why I believe that this is the case. In pertinent part, the backtrace from your bug includes: 2016-01-27 07:02:06.777 | File "/home/jenkins/workspace/periodic-trove-python27-liberty/trove/tests/api/replication.py",

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, As I just said in my earlier reply to you, Craig has been away for some time and I'll look into this. I don't know that we need to revert the change or take the route you propose. There may be a much simpler solution. I'll propose a change for your review. -amrith > -Original

[openstack-dev] [trove][release] Releases for Trove and python-troveclient

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

[openstack-dev] [trove] Trove Mitaka mid-cycle sprint summary

le, a good time was had by all (to the best of my knowledge, no one told me otherwise ;)). My thanks again to Red Hat, and to Pete who hosted us at the Red Hat offices in Raleigh, and those who participated in the meeting. Thanks, -amrith [1] https://wiki.openstack.org/wiki/Sprints/TroveMita

Re: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka cycle?

> Mitaka cycle? > > 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

Re: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka cycle?

reasonable to take all of these changes in one set. -amrith -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125 CambridgePark Drive, Suite 400 | http://www.tesora.com Cambridge, MA. 02140| GPG: 0x5e48849a9

<    1   2   3   4   >