[openstack-dev] [trove] Weekly meeting canceled for Thanksgiving holiday week

As tomorrow (Wednesday) is a light day in the US at least, and given that other projects appear to be doing this as well, I'm going to cancel the Trove weekly meeting for tomorrow (23rd). I'm sure all of you will spend the extra hour doing reviews and preparing your Turkey. -amrith smime

Re: [openstack-dev] git review command authentication failed

Hi Raman, welcome. It would help immensely to look into this if you shared the exact error message(s) that you received. I suggest you copy and paste the error into something like gist.github.org or paste.openstack.org and share a link to that buffer in email. Please make sure you sanitize

Re: [openstack-dev] [Openstack-operators] [trove][nova][octavia][manila][sahara][designate][zaqar] Projects that use service VM's (Was: More file injection woes)

com] > Sent: Sunday, November 13, 2016 10:29 AM > To: Amrith Kumar ; OpenStack Development Mailing > List (not for usage questions) ; > openstack-operat...@lists.openstack.org > Subject: Re: [Openstack-operators] > [trove][nova][octavia][manila][sahara][designate][zaqar] Projects

Re: [openstack-dev] [Openstack-operators] [trove][nova][octavia][manila][sahara][designate][zaqar] Projects that use service VM's (Was: More file injection woes)

That's fine, I will take care of putting it in the devref but this is the only way in which I know to identify the "cats" involved :) -amrith > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Sunday, November 13, 2016 10:

Re: [openstack-dev] [Openstack-operators] [trove][nova][octavia][manila][sahara][designate][zaqar] Projects that use service VM's (Was: More file injection woes)

ovember 12, 2016 9:34 AM > To: Amrith Kumar ; OpenStack Development Mailing > List (not for usage questions) ; > openstack-operat...@lists.openstack.org > Subject: Re: [Openstack-operators] [trove][nova] More file injection woes > > On 11/12/2016 8:19 AM, Amrith Kumar wrote: > >

Re: [openstack-dev] [Openstack-operators] [trove][nova] More file injection woes

I'm adding [trove] to the subject as we're interested in where this ends up. Matt, it may make sense to include other projects that use service VM's if they are using file injection/configDrive/... -amrith -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent

[openstack-dev] [oslo][trove][dev] oslo_messaging.rpc message signing and verification

At the oslo-meeeting[1] on 11/7 we discussed a proposal[2] to enable message signing and verification for oslo_messaging.rpc. The use-case for this is to ensure that when RPC's are used with service VM's there is a possible attack vector that involves a compromised service VM. While there are sever

Re: [openstack-dev] [trove][requirements][kolla][security] pycrypto vs cryptography

Steve, I’m in the midst of doing something in this area for Trove and OSLO so I’m interested in this subject and have added [trove] to the subject so I don’t lose track of this thread. I was planning to use pycrypto. I’d prefer to continue with that; but thanks for the heads-up, I’ll plan on

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

ve.ca] > Sent: Friday, November 4, 2016 8:22 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all][dev][python] constructing a deterministic > representation of a python data structure > > > > On 04/11/16 08:02 AM, Amrith Kumar wrote: > > [Amrith

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

g. > > Step 3 would be signing. > > > > So, steps 2 and 3 are all set; just need step 1 :) And I'm marveling > > at the link that Morgan provided, it may have what I need. > > > > Please please please do not invent your own home rolled cryptographic >

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

On Thu, Nov 3, 2016 at 1:04 PM, Amrith Kumar mailto:amr...@tesora.com> > wrote: Gordon, You can see a very quick-and-dirty prototype of the kind of thing I'm looking to do in Trove at https://gist.github.com/amrith/6a89ff478f81c2910e84325923eddebe Uncommenting line 51 would simulate

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

ion that the message wasn't tampered with u probably at least want https://docs.python.org/2/library/hmac.html and then you need to start figuring out what to do about key distribution & management and rotation :-/ Amrith Kumar wrote: > Gordon, > > You can see a very quick-and-di

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

structure On 03/11/16 02:24 PM, Amrith Kumar wrote: > > So, just before calling call() or cast(), I could compute the hash and > stuff it into the dictionary that is being sent over, and I can do the > same on the receiving side. But since I cannot guarantee that the > repres

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

e of your needs? http://www.slideshare.net/davanum/ovo-deep-dive https://gorka.eguileor.com/learning-something-new-about-oslo-versioned-objects/ http://www.danplanet.com/blog/2015/10/06/upgrades-in-nova-objects/ -- Dims On Thu, Nov 3, 2016 at 2:24 PM, Amrith Kumar wrote: > TL;DR > > >

Re: [openstack-dev] [oslo][oslo-messaging] [all][dev][python] constructing a deterministic representation of a python data structure

tion of a python data structure On 03/11/16 02:24 PM, Amrith Kumar wrote: > > So, just before calling call() or cast(), I could compute the hash and > stuff it into the dictionary that is being sent over, and I can do the > same on the receiving side. But since I cannot guarantee

[openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

TL;DR I want to take a python data structure (see later for details) and represent it in a format that will be stable across python versions, and platforms so that I can construct a stable hash. I'm looking for pointers to some best practices on how to do this. The longer version Assume

[openstack-dev] [trove] migration of trove-integration; ci changes

Unless you are actively working on Trove, this is something you wouldn't care about so here's the TL;DR The changes to the Trove CI (including trove, trove-integration, and python-troveclient) related to the project to get rid of trove-integration are now complete. Thanks to everyone in infra f

Re: [openstack-dev] [trove][octavia][tacker][designate][manila][sahara][magnum][infra] servicevm working group meetup

Ditto ... -Original Message- From: Hayes, Graham [mailto:graham.ha...@hpe.com] Sent: Tuesday, October 25, 2016 3:54 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [trove][octavia][tacker][designate][manila][sahara][magnum][infra] servicev

[openstack-dev] [all][tc] "production line" changes to multiple projects

Is there something we can do about the "production line" changes like https://review.openstack.org/#/q/Update+.gitignore+to+ignore+.idea+of+PyChar m These kinds of changes, and this is by no means the only one, are aimed at bringing 'standardization' to all OpenStack projects. Unfortunatel

[openstack-dev] [trove] FW: Your draft logo & a sneak peek

Sent: Wednesday, October 19, 2016 3:05 PM To: Amrith Kumar Subject: Your draft logo & a sneak peek Hi Amrith, We're excited to show you the draft version of your project logo, attached. We want to give you and your team a chance to see the mascot illustrations before we make the

[openstack-dev] [trove] no more commits to trove-integration please

As we work our way through the project to eliminate the trove-integration repository, there must come a point when we stop adding any more commits to the trove-integration repository. As described in the spec[1] for this project, everything in trove-integration repository (as of the current HEA

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

I've been interacting recently with several new contributors (to Trove) and I can certainly attest to the fact that people appear to browse the source repository and read the README's. Flavio makes a good point that it would be good to provide a short summary of the project's capabilities in so

Re: [openstack-dev] [Trove] trove core team

Craig, It’s been awesome working with you over these past years, and I look forward to doing it again (soon). All the very best to you with your new adventures. Thanks, -amrith P.S. You can be sure I’ll take you up on the offer to hang out when I’m in Austin, and my backyard-bbq is always ope

Re: [openstack-dev] [tc] open question to the candidates

ore robust way, and potentially not in a format that is squeezed for time. Thanks, -amrith [1] https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15243/stewardship-bringing-more-leadership-and-vision-to-openstack > -Original Message- > From: Amrith Kumar [mailto:amr..

Re: [openstack-dev] [tc] open question to the candidates

> -Original Message- > From: gordon chung [mailto:g...@live.ca] > Sent: Monday, October 03, 2016 11:31 AM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [tc] open question to the candidates > > hi, > > as there are many candidates this TC election, i figured i'd ask

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

FWIW, this does not appear to work for Trove. To confirm I've pushed up a trial balloon (https://review.openstack.org/#/c/381075/2). At least on a local sandbox it does not work ... -amrith > -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: Monday, October

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Also impacts Trove, see (for example) http://logs.openstack.org/85/380985/1/check/gate-trove-functional-dsvm-mysql/48ae79c/logs/devstacklog.txt.gz#_2016-10-03_09_04_15_199 I have updated https://bugs.launchpad.net/trove/+bug/1629726 and marked it as impacting Trove. -amrith From: Steven Dake (

[openstack-dev] [all] Why do we have project specific hacking rules?

It was my understanding that hacking rules were like the 'Ten Commandments', the 'Four Opens'; things that were universally true across all projects and an attempt to bring standardization to all OpenStack code. How come we then have extensive project specific hacking rules? Why not make these

[openstack-dev] TC Candidacy - amrith

I would like to announce my candidacy for election to the OpenStack Technical Committee. By way of introduction, I[1] have been working primarily on Trove since just before Icehouse. I was the PTL of the project for the Newton cycle, and was recently elected to a second term as the PTL for the O

Re: [openstack-dev] [neutron] clean up your git checkout!

ck.org/#/c/121044/ [3] https://review.openstack.org/#/c/121044/5/tox.ini > -Original Message- > From: John Villalovos [mailto:openstack@sodarock.com] > Sent: Friday, September 30, 2016 5:41 PM > To: OpenStack Development Mailing List (not for usage questions) > &g

Re: [openstack-dev] [neutron] clean up your git checkout!

e is still good. Your existing > virtualenvs already have .pycs in them so the easy way to clean that up > is to rebuild your tox venvs using tox -r. > > Clark > > On Fri, Sep 30, 2016, at 12:01 PM, Amrith Kumar wrote: > > Clark, > >

Re: [openstack-dev] [neutron] clean up your git checkout!

say this happens if .tox is in your gitignore list. Just run > tox with the -r flag which will rebuild the tox envs. > > Clark > > On Fri, Sep 30, 2016, at 11:22 AM, Amrith Kumar wrote: > > I tried that but even with it in place, a .tox directory with a ton of > > .pyc'

Re: [openstack-dev] [neutron] clean up your git checkout!

I tried that but even with it in place, a .tox directory with a ton of .pyc's was left around after the test. I'm assuming that this is OK? -amrith > -Original Message- > From: John Villalovos [mailto:openstack@sodarock.com] > Sent: Friday, September 30, 2016 1:57 PM > To: OpenStack

Re: [openstack-dev] [ptl] code churn and questionable changes

Joshua, I think Steve and you may be missing the point of my email. It *IS* because I want to be open and inviting that I even asked the question, and what I'm asking for is how to deal with it. All Steve says is " The fact that a new-to-openstack contributor would make such and error doesn’t

Re: [openstack-dev] [ptl] code churn and questionable changes

we cannot reach out to them > in this mailing list. There should be a way to limit this somewhere > in Launchpad. [amrith] Actually, not true. Some of the changes I'm seeing are from people who have a track record of these kinds of changes. And if there is a knob in Launchpad somewhere, I

[openstack-dev] [ptl] code churn and questionable changes

Of late I've been seeing a lot of rather questionable changes that appear to be getting blasted out across multiple projects; changes that cause considerable code churn, and don't (IMHO) materially improve the quality of OpenStack. I'd love to provide a list of the changes that triggered this em

Re: [openstack-dev] [band] OpenStack Summit - Barcelona - musicians please raise your hands

>> wrote: On Sat, Sep 17, 2016 at 1:35 PM, Amrith Kumar mailto:amr...@tesora.com>> wrote: > So, would y'all musicians who plan to bring your gear to Barcelona please > start a little thread here on the ML and let's get a band going? I would totally bring my gear if my cel

[openstack-dev] [band] OpenStack Summit - Barcelona - musicians please raise your hands

I had a chat with an openstack newbie on Thursday who has never posted a message on the mailing list. He's a musician and will be at summit in Barcelona, and I happened to mention that there were a bunch of other musicians who bring their gear along, and have a good time. I told him to post to

[openstack-dev] [trove] Newton RC1 tagged

As I type this email, the release team is tagging Trove and Trove Dashboard Newton RC1. Once this process is complete, master will be heading for Ocata and if you want something into Newton, you will have to explicitly chkin to the Newton branch. We will have an RC2 in a week or so to pick up a

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

> -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Tuesday, September 13, 2016 3:45 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all] governance proposal worth a visit: > Write down OpenStack principles > > Clay Gerrard wrote:

[openstack-dev] [trove] PTL candidacy

the project as well as members of the infra, release, stable, oslo, docs, dib, and other project teams who helped us on innumerable occasions. Thank you, and I appreciate your support in the election. I have Submitted this candidacy as review [4]. -amrith -- Amrith Kumar Email: amr...@tesora.com

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

> -Original Message- > From: Edward Leafe [mailto:e...@leafe.com] > Sent: Thursday, September 08, 2016 1:02 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [all] governance proposal worth a visit: > Write down OpenStack principles >

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

> -Original Message- > From: Chris Dent [mailto:cdent...@anticdent.org] > Sent: Thursday, September 08, 2016 7:19 AM > To: OpenStack-dev@lists.openstack.org > Subject: [openstack-dev] [all] governance proposal worth a visit: Write > down OpenStack principles > > > There's a governance p

Re: [openstack-dev] [puppet] Puppet OpenStack PTL non-candidacy

Emilien, Great work over the past 18 months, it was a pleasure to work with you. Thanks for all you've done! -amrith > -Original Message- > From: Emilien Macchi [mailto:emil...@redhat.com] > Sent: Friday, September 09, 2016 12:06 PM > To: OpenStack Development Mailing List > Subject: [

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

Thierry, thanks for writing this up. I think this is a great idea, and something that will help focus the release stewards on a specific release while the PTL can coordinate activities for all aspects of the project. Where appropriate, and where a project decides to take this route, it allows PT

Re: [openstack-dev] [release] proposing adding Tony Breeds to "Release Managers" team

Doug, This is a great addition; Tony's reviews are very helpful, he asks great questions and provides insightful feedback. And when you are in a bind, he has great suggestions. +1 Thanks, -amrith > -Original Message- > From: Doug Hellmann [mailto:] > Sent: Tuesday, September 06, 2016

[openstack-dev] [trove][release] Trove FFE's for Newton

Between some late breaking complications in the gate (on stable branches, now understood and fixes are on the way to being merged) and a desire to have more jobs running in our CI, there are some feature patches that have not landed in N-3. This email is to document that list of feature freez

Re: [openstack-dev] [OpenStack-docs] [cinder] [neutron] [ironic] [api] [doc][trove] API status report

This email managed to fall through the cracks in the couch cushions so my apologies for doing this late. I’ve added [trove] to the subject line now. Here’s the update from Trove: Anne’s original change[1] was abandoned and replaced by [2] which has now merged. The infra change [3] has also merg

Re: [openstack-dev] [devstack] How to start all OpenStack services after restarting system?

The attached script is something I’ve used for a while and it works pretty well. It does a little more than just the screen reconnection, it also gets you the swift/cinder volumes that you’ll need if you want to run, say Trove. -amrith From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]

Re: [openstack-dev] [all][infra] Constraints are ready to be used for tox.ini

> -Original Message- > From: John Dickinson [mailto:m...@not.mn] > Sent: Thursday, August 11, 2016 2:09 PM > To: OpenStack Development Mailing List > Subject: Re: [openstack-dev] [all][infra] Constraints are ready to be used > for tox.ini > > > > On 11 Aug 2016, at 10:03, Andreas Jaege

Re: [openstack-dev] [tc] persistently single-vendor projects

To Steven's specific question: > If PTLs can weigh in on this thread and commit to participation in such a > cross-project subgroup, I'd be happy to lead it. I would like to participate and help get this kind of a group going. -amrith > -Original Message- > From: Steven Dake (stdake) [

[openstack-dev] [trove] Weekly meeting today, canceled today

I'm going to cancel today's weekly trove meeting for a couple of reasons. We had our mid-cycle last week and went through a lot of the backlog of items, and there are a couple of people who are out today so attendance and agenda are kind-of thin. If there is something urgent that you would like

Re: [openstack-dev] [all][tc] establishing project-wide goals

Doug, Thanks for doing this. In the interests of transparency and full disclosure, I was at the leadership training and heard about this idea there (and was strongly in favor of it then, as I am now). I think it is very important that OpenStack not devolve into a loose confederation of bags of

Re: [openstack-dev] [oslo][nova][requirements] Getting oslo.context 2.6.0 into the gate

Jamie, I’ve updated your review re: u-c oslo.context==2.7.0 in Trove. It will fail but that is understood. I’ve manually tested o.c 2.7.0 and it appears to work. -amrith From: Jamie Lennox [mailto:jamielen...@gmail.com] Sent: Saturday, July 30, 2016 2:17 PM To: OpenStack Development Mailing Lis

[openstack-dev] [trove] Trove midcycle, July 26, 27 and 28

The Trove mid-cycle will be held over the next three days. Meeting information is available at [1]. We will not have our regular weekly meeting this week as a result. Thanks, -amrith [1] https://etherpad.openstack.org/p/newton-trove-midcycle ___

[openstack-dev] [trove] weekly meeting canceled this week

In view of the mid-cycle, the weekly meeting is canceled for this week. -amrith __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http:/

Re: [openstack-dev] [keystone][murano][trove][imm] Changing OpenStack LLC to OpenStack Foundation

ase.py > [ironic] > https://review.openstack.org/#/c/47451/2/ironic/common/image_service.py > > Do you think these changes needs to be reverted ? > > Thank you, > Dinesh Bhor > > -Original Message- > From: Amrith Kumar [mailto:amr...@tesora.com] > Sent:

[openstack-dev] [keystone][murano][trove][imm] Changing OpenStack LLC to OpenStack Foundation

Bug 1214176 seeks to "Fix copyright headers to be compliant with Foundation policies" and one of the changes being made is to substitute "OpenStack Foundation" in places where the code said "OpenStack LLC". Someone just pushed changes to Keystone, Murano and Trove today and I have some concerns

Re: [openstack-dev] Mascot/logo for your project

Heidi, The Trove team came up with several logo options. The result of a vote was decisive: 1. Stingray [1] 2. A Clam with a Pearl in it. [2] I have heard of no one else wanting to use the Stingray so I would like to request that the foundation consider that our preference. Among the opti

[openstack-dev] [trove] no weekly meeting next week

We won't have our weekly meeting next week as we are going to be meeting anyway for our virtual mid-cycle. Thanks, -amrith __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@l

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

> -Original Message- > From: Fox, Kevin M [mailto:kevin@pnnl.gov] > Sent: Friday, July 15, 2016 2:37 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for > all) > > Some specific things: > >

Re: [openstack-dev] [DIB] [TripleO] Should we have a DIB meeting?

Sounds like an excellent idea! +1 to a DIB meeting that includes office hours. I could've used this last week :) -amrith From: Gregory Haynes [mailto:g...@greghaynes.net] Sent: Friday, July 15, 2016 7:40 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [DIB] [TripleO] Shoul

Re: [openstack-dev] [release][documentation][telemetry][murano][trove] missing milestones

Doug, At this time it is highly unlikely that there will be a 0b2 tag on trove-image-builder. I may get to a 0b3 tag but per the proposed membership freeze[1], we have missed two of the milestones and therefore trove-image-builder will likely not be included in the newton release. Thanks, -a

[openstack-dev] kick-off meeting of openstack stewardship working group (SWG)

Today (July 14th) at 1800UTC in #openstack-meeting-cp, we will hold the kick-off meeting of the OpenStack Stewardship Working Group (SWG)[1]. The SWG was setup by the TC[2] with the stated purpose that this small group would review the leadership, communication, and decision making processes of

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

[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

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

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

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

[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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<    1   2   3   4   >