Re: [openstack-dev] [oslo.db]A proposal for DB read/write separation

, -amrith -- Amrith Kumar, CTO Tesora (www.tesora.com) Twitter: @amrithkumar IRC: amrith @freenode [1] http://www.tesora.com/solutions/database-virtualization-engine [2] http://www.tesora.com/solutions/downloads/products [3] http://www.mysqlperformanceblog.com/2014/06/24

Re: [openstack-dev] [Glance] IRC logging

I think logging the channel is a benefit even if, as Nikhil points out, it is not an official meeting. Trove logs both the #openstack-trove channel and the meetings when they occur. I have also had some conversations with other ATC's on #openstack-oslo and #openstack-security and have found that

Re: [openstack-dev] [Trove] Proposal to add Craig Vyvial to trove-core

+1 -- Amrith Kumar, CTO, Tesora | -Original Message- | From: Nikhil Manchanda [mailto:nik...@manchanda.me] | Sent: Tuesday, May 06, 2014 5:32 AM | To: OpenStack Development Mailing List (not for usage questions) | Subject: [openstack-dev] [Trove] Proposal to add Craig Vyvial to trove

Re: [openstack-dev] [nova][neutron][mysql] IMPORTANT: MySQL Galera does *not* support SELECT ... FOR UPDATE

So as another of the panelists on this panel that Jay organized some comments on Julien's reply below. | On Mon, May 19 2014, Jay Pipes wrote: | | > I think at that point I mentioned that there were a number of places | > that were using the SELECT ... FOR UPDATE construct in Nova (in | > SQLAlch

[openstack-dev] [trove] Blueprint Review: "Allow volume snapshot as another way for data backuping"

concerns as well and I'll let them contribute those to this mail thread if they so desire. -amrith -- Amrith Kumar, CTO, Tesora Twitter: @amrithkumar Email: amr...@tesora.com Skype: amrith.skype Web: http://www.tesora.com ___ OpenStack-dev m

Re: [openstack-dev] [OpenStack][Trove] Building new image for trove

Swapnil, If the default image being created by devstack gives you a timeout on launch, I don’t think your issue is with the image itself. Your best guide (for now) for creating a guest image is to follow the template that devstack uses. I’m on the hook for writing some documentation on how to

Re: [openstack-dev] [nova][cinder] (OperationalError) (1040, 'Too many connections') None None

What do you see if you run mysqladmin processlist I hope it doesn’t also give the same error (but that may be what you see). -amrith From: Nader Lahouti [mailto:nader.laho...@gmail.com] Sent: Monday, September 29, 2014 12:31 PM To: OpenStack Development Mailing List (not for usage questions) Su

Re: [openstack-dev] [nova][cinder] (OperationalError) (1040, 'Too many connections') None None

Yes, looks like MySQL was just configured with too low a max-connections value. -amrith | -Original Message- | From: Jay Pipes [mailto:jaypi...@gmail.com] | Sent: Monday, September 29, 2014 12:58 PM | To: openstack-dev@lists.openstack.org | Subject: Re: [openstack-dev] [nova][cinder] (Ope

Re: [openstack-dev] [Trove] Proposal to add Iccha Sethi to trove-core

+1 | -Original Message- | From: Nikhil Manchanda [mailto:nik...@manchanda.me] | Sent: Thursday, October 30, 2014 4:47 AM | To: OpenStack Development Mailing List (not for usage questions) | Subject: [openstack-dev] [Trove] Proposal to add Iccha Sethi to trove-core | | Hello folks: | | I'

Re: [openstack-dev] [all] python-troveclient keystone v3 support breaking the world

Sean, I'm looking into this and have proposed https://review.openstack.org/#/c/133958/ as an interim measure. As soon as the trove gate passes I'll try and get a couple of other votes and have that change merged. Dims and I had a short chat on IRC and weren't able to come up with a quick solut

[openstack-dev] [oslo] The right (and the wrong) way of handling module imports in oslo-incubator

At the suggestion of Doug Hellmann, and relative to a conversation with him and Flavio at Summit. Doug suggested that I pose this question on the dev mailing list so someone from OSLO can communicate the answer to the entire community (rather than just the private email exchange that we had). H

Re: [openstack-dev] [hacking] rules for removal

In addition to making changes to the hacking rules, why don't we mandate also that perceived problems in the commit message shall not be an acceptable reason to -1 a change. Would this improve the situation? -amrith -- Amrith Kumar, CTO Tesora (www.tesora.com) Twitter: @amrithkuma

[openstack-dev] Trove Juno mid-cycle meeting - confirmed dates and location

g for an all-day event on Trove and Database as a Service with OpenStack that we (Tesora, the company I work for) are organizing on August 19th. http://tesora.com/event/openstack-trove-day Thanks, -amrith -- Amrith Kumar, CTO Tesora ( <http://www.tesora.com> www

Re: [openstack-dev] [Glance][Trove] Metadata Catalog

Speaking as a ‘database guy’ and a ‘Trove guy’, I’ll say this; “Metadata” is a very generic term and the meaning of “metadata” in a database context is very different from the meaning of “metadata” in the context that Glance is providing. Furthermore the usage and access pattern for this me

[openstack-dev] Could we highlight +0 reviews in review.openstack.org

are any 0's there. Maybe in a different color. Otherwise, it is easy to miss a perfectly legitimate review with a 0 score. I think the UI would be more user friendly with that, maybe we could make it a user preference whether this is shown or not. Thanks, -amrith -- Amrith Kumar Tesor

Re: [openstack-dev] Could we highlight +0 reviews in review.openstack.org

ons) > > Subject: Re: [openstack-dev] Could we highlight +0 reviews in > review.openstack.org > > On 2015-11-12 16:33:52 + (+), Amrith Kumar wrote: > > When you look at a review on https://review.openstack.org, you see a > > section of the screen that shows +2&#

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo [imm]

Just catching up on this thread, have fixes been submitted for this already? Thanks, -amrith > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Wednesday, November 18, 2015 2:54 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev]

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo [imm]

rove unit tests failing on stable/kilo > [imm] > > > > On 11/19/2015 10:22 AM, Amrith Kumar wrote: > > Just catching up on this thread, have fixes been submitted for this already? > > > > Thanks, > > > > -amrith > > > >> -Origina

Re: [openstack-dev] How to add a periodic check for typos?

So, just for grins, I took this approach out for a spin on Trove and noticed this as part of the change proposed by topy. - "hebrew": ["hebrew_general_ci", "hebrew_bin"], + "Hebrew": ["hebrew_general_ci", "hebrew_bin"], - "greek": ["greek_general_ci", "g

Re: [openstack-dev] [oslo] A special thank you to Davanum (Dims)

Yes, let's talk about dims while he isn't here. I'll second what Michael and Steve have to say. Dims has been a great guy to work with and he's been a great resource. On one occasion, I needed some openstack folks to help (in person) at very short notice. Dims (and Kamesh, also of Mirantis) dro

Re: [openstack-dev] Licenses

I believe that Swapnil Kulkarni took over that role. -amrith From: Armando Dominguez [mailto:armando.doming...@rackspace.com] Sent: Monday, November 23, 2015 12:46 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Licenses Hey All, Sorry for hitting the entire list, I'm just try

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 | git.openstack

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 I

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 a

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 ( r

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

-+ | 3 | 4096 | ++---+ 1 row in set (0.00 sec) By adding consumer_id to the resources table, the hotspot/scalability-issue/problem that Jay described has been addressed. Hope this helps, Thanks, -amrith From: Amrith Kumar Sent: Sunday, May 15,

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

> > Le 09/05/2016 16:38, Amrith Kumar a écrit : > > So I'm able to run the py34 tests in about 10s if I run the dangling > > mock detector with a depth of 0 or 1. > > IMHO the strange mock detector code must be removed. It is very slow and > I don't understand

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

Thanks Victor, I see your question on Infra. I'm going to restate it here just in case someone who reads the ML notices it. hi. i'm investigating "Random timeout on gate-trove-python34-db" https://bugs.launchpad.net/trove/+bug/1582257 : i noticed that python 2 has many precompiled wheel packag

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

> -Original Message- > From: Victor Stinner [mailto:vstin...@redhat.com] > Sent: Monday, May 16, 2016 12:10 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [trove] timeouts in gate-trove-python34-db > > Le 16/05/2016 16:12, Peter St

[openstack-dev] Weekly Trove meeting minutes 2016-05-18

Minutes of the weekly Trove meeting held today can be found at http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-05-18-18.00.html Meeting summary Action items from last week's meeting (amrith, 18:03:03) Trove pulse update (amrith, 18:03:28) http://bit.ly/1VQyg00 (amri

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

Emily, Is this mentoring program in any way related to Outreachy[1] or is that a different program altogether? Your email says, "people to the guidelines (here and here

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

Auggy, This is a great wiki page and would love to see a high level "OpenStack Mentoring" page with links to projects that have this kind of "beginners guide". I'll try and do something similar for Trove but you've set the bar very high. -amrith > -Original Message- > From: Augustina R

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

From: Augustina Ragwitz [mailto:aragwitz.li...@pobox.com] Sent: Tuesday, May 24, 2016 10:12 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas On 12:54 May 24, Augustina Ragwitz wrote: Hi Emily, I'm the Nova M

Re: [openstack-dev] [devstack] let's give a different warning message for different OS_PROJECT_NAME ?

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Wednesday, May 25, 2016 6:06 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [devstack] let's give a different warning > message for different OS_PROJECT_NAME ? > > On 05/25/2016 04:05 AM, li.

[openstack-dev] Trove Meeting notes

Here are the notes from the (just concluded) Trove meeting. http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-05-25-18.00.html Two actions: ACTION: pmalik and stewie925 to look into the rebase issue (amrith, 18:41:32) ACTION: amrith pmackinn cp16net to see what this mysql issue is (a

Re: [openstack-dev] [oslo][all] oslo.log `verbose` and $your project

Ihar, I entered 1586066[1] for Trove and the Trove change is 321585. Thanks, -amrith [1] https://bugs.launchpad.net/trove/+bug/1586066 [2] https://review.openstack.org/#/c/321585/ > -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: Thursday, May 26, 2016

Re: [openstack-dev] [tc] Leadership training - ideas to include those not in the room?

Anita, Colette, I too was wondering how effective my own participation in the training would be there was an implied expectation that I was to be taking notes for a live relay to others on the internet who were following along on an etherpad, not to mention what it would to the dynamics in the r

[openstack-dev] [trove] Reminder: Trove meeting this afternoon

A reminder to everyone that there's a Trove meeting scheduled for 2pm Eastern Time today. Currently there is nothing on the agenda. If there's nothing on the agenda by ~ 60m before the meeting, I propose that we cancel the meeting. Agenda is at https://wiki.openstack.org/wiki/Meetings/TroveMeet

[openstack-dev] [trove] Today's Trove meeting is canceled

Nothing new has been added to the agenda. Today's meeting is canceled. If anything urgent comes up, use #openstack-trove. Thanks, -amrith > -Original Message- > From: Amrith Kumar > Sent: Wednesday, June 01, 2016 9:17 AM > To: OpenStack Development Mailing List (not fo

[openstack-dev] [trove] trove-image-builder project

We've had some lengthy discussions over the past couple of release cycles, most recently in Austin, and on the ML on the subject of the trove-image-builder project[1]. Subsequently the trove spec [2] has been merged and yesterday the infra and governance changes [3] and [4] have also merged. Th

[openstack-dev] [trove] Trove Newton spec proposal deadline

This week, June 6-10 is R-17 for Newton and marks the deadline for the proposal of any specs for features to be considered for the Newton cycle. Please get all specs into the trove-specs repository as soon as possible. The following specs [1] are currently proposed and in need of review. 315079

[openstack-dev] [oslo][trove][keystone][glance][nova] on the deprecation of isotime() in oslo.utils

TL;DR Oslo deprecated isotime() and some other functions in oslo_utils.timeutils a while back. The recommended route was to just use datetime.isoformat() instead. In researching this for Trove, I found that several projects instead handled the situation by cloning the code into their own projec

Re: [openstack-dev] Reasoning behind my vote on the Go topic

Well put Monty. It is a tough choice and neither choice was inexpensive. -amrith > -Original Message- > From: Monty Taylor [mailto:mord...@inaugust.com] > Sent: Tuesday, June 07, 2016 3:00 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev]

[openstack-dev] Trove weekly meeting minutes

The summary of the Trove weekly meeting held just now. Action Items: - prepare for next weeks meeting; things that we can get into Newton Full transcript at http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-06-08-18.00.html Thanks, -amrith _

Re: [openstack-dev] [Trove] Stepping down from Trove Core

Victoria, Thank you very much for your contribution to Trove. All the very best to you and the projects you will be working on. -amrith From: Victoria Martínez de la Cruz [mailto:victo...@vmartinezdelacruz.com] Sent: Tuesday, June 07, 2016 2:34 PM To: OpenStack Development Mailing List Subjec

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Thierry, Thanks for writing this up and for the interesting discussion that has come up in this ML thread. While I think I get the general idea of the motivation, I think the verbiage doesn't quite do justice to your intent. One area which I would like to highlight is the situation with the un

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

aying field for > OpenStack projects > > Amrith Kumar wrote: > > Thanks for writing this up and for the interesting discussion that has > come up in this ML thread. > > > > While I think I get the general idea of the motivation, I think the > verbiage doesn't quit

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Steve, this was exactly the point I wanted to make and the reason I chose the verbiage of "reasonably accessible" since I believe that this would classify as such. However, as Thierry pointed out in his response to the review that wasn't his primary focus. Rather, he didn't want a project to be

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Clint, In your original email, you proposed "So, with that, I'd like to propose the creation of an Architecture Working Group. This group's charge would not be design by committee, but a place for architects to share their designs and gain support across projects to move forward with and ratify

[openstack-dev] OpenStack Trove Ocata Midcycle, NYC, August 25 and 26.

The Trove midcycle will be held in midtown NYC, thanks to IBM for hosting the event, on August 25th and 26th. If you are interested in attending, please join the Trove meeting today, 2pm Eastern Time (#openstack-meeting-alt) and register at http://www.eventbrite.com/e/openstack-trove-ocata-midc

Re: [openstack-dev] [all] Proposal: Architecture Working Group

> -Original Message- > From: Clint Byrum [mailto:cl...@fewbar.com] > Sent: Wednesday, June 22, 2016 2:25 PM > To: openstack-dev > Subject: Re: [openstack-dev] [all] Proposal: Architecture Working Group > > Excerpts from Amrith Kumar's message of 2016-06-22 13:15:03 +: > > Clint, > > >

[openstack-dev] Notes from Trove weekly meeting

Notes from the Trove weekly meeting are at: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-06-22-18.00.html A significant amount of the discussion related to https://review.openstack.org/#/c/332933/ [Document house rules for approving changes] The summary of the change pro

[openstack-dev] [trove] RE: [all] Status of the OpenStack port to Python 3

Victor, To echo what Sylvain is saying, I think Trove has talked about python 3 for a while now and while it isn’t listed as a blueprint for Newton, I think we’re far enough along that we should see if we can get this completed for the Newton cycle. Thanks for all your work on this, and also t

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Thursday, June 23, 2016 5:16 PM > To: openstack-dev > Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3 > [... snip ...] > > Let's see what PTLs have to say about planning, but I

[openstack-dev] [trove] OpenStack Trove Ocata Virtual Midcycle,

hanks, -amrith > -Original Message- > From: Amrith Kumar > Sent: Wednesday, June 22, 2016 9:54 AM > To: openstack-dev > Subject: OpenStack Trove Ocata Midcycle, NYC, August 25 and 26. > > The Trove midcycle will be held in midtown NYC, thanks to IBM for hosting >

[openstack-dev] [trove] Trove meeting today (June 29th) is canceled

I'm canceling today's Trove meeting as there is nothing on the agenda and several people are either traveling or otherwise unable to make it to the meeting. We will meet again on July 6th. -amrith __ OpenStack Development

Re: [openstack-dev] [tc] Leadership training recap & steps forward

A huge "THANK YOU" to Colette for all the time and effort that went into making this a reality. What she doesn't mention is that this training (which lasted just a couple of days) was a year in the making! In addition to the great sandwiches and BBQ (and beer), I think it was great to have so m

[openstack-dev] trove weekly meeting notes

Notes from today's trove meeting are at[1] Action items 1. [done] vgnbkr to figure some way of updating the spec to get the check/gate jobs to pass; maybe simplify the script 2. [all, esp amrith] watch https://www.youtube.com/watch?v=-5wpm-gesOY 3. [amrith] review logstash to see how the

Re: [openstack-dev] [tc] Leadership training recap & steps forward

> Subject: Re: [openstack-dev] [tc] Leadership training recap & steps > forward > > That's great news! > Congrats to Colette for the organization and to the people who dare to > join the training! > > On Wed, Jul 6, 2016 at 6:45 PM, Amrith Kumar wrote: > > A huge &

Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project

Does it make sense that this conversation about the merits of nova-docker be had before the retirement is actually initiated. It seems odd that in the face of empirical evidence of actual use (user survey) we merely hypothesize that people are likely using their own forks and therefore it is fin

Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project

cient notice: > http://markmail.org/message/geijiljch4yxfcvq > > I really really want this to go away. Every time this comes up, > example it came up in Austin too, a few people raise their hands and > then do not show up. (Not saying you will do the same!). > > -- Dims >

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: We

[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] [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 Developmen

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 upper-constraints.txt? > > On Wed, Mar 30, 201

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? > > On 2016-03-30 14:33, Davanum S

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) > > Subject: [openstack-dev] [magn

[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: o

[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 in

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

t 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 mailto:fla...@redhat.com>>: On 05/04/16 15:15 +0000, Amrith Kumar wrote: If you are subscribed to bug notifications from Trove, you’d have received a lot of

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 a

[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] [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 to

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 visible

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

ics] 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 invaluab

[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 o

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 b

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

instances). Regards, Adrian On Apr 11, 2016, at 8:47 AM, Amrith Kumar 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 like Trove, having a common Compute API is very valuable. It would

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

tion] [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 hopeful of a silver bullet and as we’ve discussed be

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] [docs] Our Install Guides Only Cover Defcore - What about big tent?

reas Jaeger [mailto:a...@suse.com] > Sent: Wednesday, April 13, 2016 1:46 PM > To: Amrith Kumar ; OpenStack Development Mailing List > (not for usage questions) > Cc: mkassaw...@gmail.com; Lana Brindley ; Mike > Perez ; openstack-d...@lists.openstack.org > Subject: Re: [openstack-de

[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

[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 timefr

[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 rep

[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 f

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

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

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

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] [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 > -O

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 unified > abstraction for all COEs > >

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 c

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

t. > > Bottom line for me: I really won'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 wo

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 conversatio

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 di

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] 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 make

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

y 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, "Amrith Kumar" wrote: >

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

preciate 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 Kumar [amr...@tesora.com] > Sent: Frid

[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] https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#T

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: > > But

[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] https:/

  1   2   3   4   >