Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

I don't see much of a point in an OpenStack Technical blog. After all, those who want to blog likely already have blogs that are syndicated through the OpenStack digest mechanism. What problem or existing shortcoming is sought to be addressed by this blog? And is there some reason that existing

Re: [openstack-dev] [release][ptl] Improving the process for release marketing

Very cool, thanks Sean! -amrith On Mon, Nov 20, 2017 at 12:18 PM, Sean McGinnis wrote: > Hello PTL's, release liaisons, and all those interested. > > The changes on our side to support a release cycle highlights page have > been > completed, and things have settled a

Re: [openstack-dev] Building Openstack Trove Images

t; > > > > Can you throw some light or give us some guidance on this as it has halted > the implementation of our Production Openstack Pike. > > Your support and co-operation is highly appreciated. > > > FYI: Controller and compute node are running CentOS7. > > > &g

Re: [openstack-dev] Building Openstack Trove Images

b.com/openstack/trove/tree/master/ > integration/ however, it still throws me the same error. Please find the > log file attached. > > > Regards, > Ritesh > > On Wed, Nov 8, 2017 at 4:44 PM, Amrith Kumar <amrith.ku...@gmail.com> > wrote: > >> Please see inline

Re: [openstack-dev] Building Openstack Trove Images

t; >Please guide us where are going wrong on this. > > On Wed, Nov 8, 2017 at 12:11 PM, Ritesh Vishwakarma < > ritesh.vishwaka...@indusnet.co.in> wrote: > >> ++Looping my fellow engineer. >> >> On Wed, Nov 8, 2017 at 2:34 AM, Amrith Kumar <amrit

Re: [openstack-dev] Building Openstack Trove Images

I > came across the https://github.com/openstack/trove-integration which I am > going to try out today, kindly let me know if it is the right one or please > share any relevant reference on which we can work. > > > > Regards, > > Ritesh > > On Tue, Nov 7, 2017 at 8:16 AM, A

Re: [openstack-dev] Building Openstack Trove Images

Ha, it isn't often that I get called out by name in a mailing list thread. What are the issues that you are facing? Currently there are complete notes about how to build guest images but the issues you may be facing may not relate to the images you are building. So please provide some more

Re: [openstack-dev] [trove] retiring trove-integration?

Agreed, please also see[1]. -amrith [1] https://review.openstack.org/515084 On Wed, Oct 25, 2017 at 3:28 AM, Andreas Jaeger wrote: > Trove team, > > with the retirement of stable/newton, you can now retire > trove-integration AFAIU. > > For information on what to do, see: >

Re: [openstack-dev] [forum] Schedule Is Available

Mike, Thanks for sending this out. Long lines in descriptions of many events are not being wrapped, take Rochelle's session "Refstack: OpenStack to OPNFV, Vertical, Integrated, Interop" at 3:30pm on Wednesday. Any chance the descriptions could be wrapped? -amrith On Mon, Oct 16, 2017 at 7:43

Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

gt; On Sun, Oct 15, 2017 at 08:15:51AM -0400, Amrith Kumar wrote: >> Full disclosure, I'm running for election as well. I intend to also >> provide an answer to the question I pose here, one that I've posed >> before on #openstack-tc in an office hours session. >> >>

[openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

Full disclosure, I'm running for election as well. I intend to also provide an answer to the question I pose here, one that I've posed before on #openstack-tc in an office hours session. Question 1: "There are M open slots for the TC and there are N (>>M) candidates for those open slots. This is

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

Thanks Doug, I didn't know what caused the "Welcome New Contributor" thing show up in reviews, but that is exactly what I used to look for. -amrith On Fri, Oct 13, 2017 at 1:52 PM, Doug Hellmann wrote: > Excerpts from Amrith Kumar's message of 2017-10-13 13:32:54 -0400:

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

Flavio, Some months back I looked at a slide that Thierry showed at a meeting; it showed contributor statistics and it showed that there were a large number of contributors who made exactly 1 commit which sometimes got merged, but there was a huge drop off from 1 commit to 2 commits! So I got to

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

Zane, thanks for the question. Let me answer from the perspective of an OpenStack user (I work for Verizon) and from a developer (both now, and in the past as part of Tesora). OpenStack has multiple different users: - Deployers: People who deploy OpenStack and operate a cloud environment. -

Re: [openstack-dev] [tc][election] Question for the candidates

Clay, Great question and one that made me think quite a bit. I believe that while the commits in the Governance repo represent the visible actions of the TC, the real leadership ability of the TC is often in the actions that it inspires in people in the community. The TC is a body that has to

Re: [openstack-dev] [tc][election] TC non-candidacy

On Tue, Oct 10, 2017 at 7:40 PM, Monty Taylor wrote: > Hey everybody! > > I have decided not to seek reelection for the TC. > > I have had the honor and privilege of serving you on the TC and it's > predecessor the PPB since the fall of 2011 (with one six month absence that

Re: [openstack-dev] [tc] [kolla] [PTL] who can start the official meeting?

I agree with Jeremy that we shouldn't attempt to implement technical solutions for non-technical problems. But to that end, I'd be curious to know what the problem was with this. In my experience it has been an asset to have the meeting start on time even if the regular chair is for some reason

[openstack-dev] [election] [tc] TC Candidacy

I wish to submit my candidacy for election to the OpenStack Technical Committee. I have never been elected to the Technical Committee before but, I have never believed that being elected is a requirement to participate in the deliberations. I have therefore been a frequent participant and a

Re: [openstack-dev] [tc][election] non-candidacy for TC

Steve, thanks for all you've done on the TC, and for OpenStack. Looking forward to continuing to work with you, -amrith On Tue, Oct 3, 2017 at 11:05 PM, Steve Martinelli wrote: > Folks, due to changes in my day job I will not be running in the next TC > election. I

Re: [openstack-dev] Disk Image Builder for redhat 7.4

As Tony says, there's a base image that you can use for RHEL 7.4. Yes, you can install Oracle onto the image using dib. In saying that I only mean that it is possible. I make no statement about the supportability of that solution by any vendors involved. To do it, you would create elements (the

Re: [openstack-dev] patches for simple typo fixes

Sean, Each fix is a valid change, in and of itself. But what kind of lazy person would fix (in three patches) the exact same thing, in three places in a single project? Or which person would submit the exact same kind of patch multiple times to change URL's from http:// to https:// in places

Re: [openstack-dev] patches for simple typo fixes

Sean, I quantified it in 2016 for some of the patches that came in to Trove; approximately 130 hours of CI time per patch given the number of hacks that the person took before even getting pep8 to run. Close to a release boundary, that had very bad results on an already fragile Trove gate.

Re: [openstack-dev] Garbage patches for simple typo fixes

Thanks Matt for highlighting this (again). Please also see http://openstack.markmail.org/thread/iaqsha7hbiitwqe2 http://markmail.org/thread/k62gcehxg6gv5ep4 http://markmail.org/thread/n753w3wljii67yug When can we take some concrete action to stop these same kinds of things from coming up again

[openstack-dev] [trove] Please welcome Samuel Matzek, Luke Browning and Manoj Kumar to the Trove core team

​Pl​ ease join me in welcoming Samuel Matzek, Luke Browning and Manoj Kumar to the Trove core team. -amrith __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [trove]how to save time of creating instance?

The amount of time taken to create a trove instance (or cluster) is largely related to how long it takes to create a nova instance of the same size. So, how long does it take to create a nova instance of the same size on your system? Does your trove image install the database statically into the

Re: [openstack-dev] [trove][tc][all] Trove restart - next steps

out of the current ditch that we are in, multi-tenancy may not be the thing that would materially benefit the project. But, we shall discuss in a week or so at PTG. -- Amrith Kumar amrith.ku...@gmail.com <mailto:amrith.ku...@gmail.com> From: Tim Bell [mailto:tim.b...@c

Re: [openstack-dev] Future Trove development

Luke, please see inline below. -- Amrith Kumar mailto:amrith.ku...@gmail.com >From: Luke Browning [mailto:lukebrown...@us.ibm.com] >Sent: Thursday, August 31, 2017 1:00 PM >To: openstack-dev@lists.openstack.org >Subject: Re: [openstack-dev] Future Trove development > >Amrit

Re: [openstack-dev] [openstack][oslo][all] Clean up oslo deprecated stuff !

GCB, Ken, thanks for doing this. It will help immensely. -amrith On Wed, Aug 23, 2017 at 9:32 AM, Ken Giusti wrote: > > > On Tue, Aug 22, 2017 at 3:24 AM, ChangBo Guo wrote: > >> Hi ALL, >> >> We discussed a little about how to avoid breaking

Re: [openstack-dev] Future Trove development

​The email thread below is an one that I have been having with Luke and some others at IBM who have been working on Trove. I feel that these kind(s) of conversations are better had in the mailing list, and in replying to this email, I let the participants know that absent any objections, I would

Re: [openstack-dev] [trove][tc][all] Trove restart - next steps

; responsibility of the cloud provider rather than the end user. Some > quota/telemetry would be needed to allocate costs to the project. > > > > Tim > > > > *From: *Amrith Kumar <amrith.ku...@gmail.com> > *Reply-To: *"OpenStack Development Mailing List (not fo

[openstack-dev] [trove][tc][all] Trove restart - next steps

Now that we have successfully navigated the Pike release and branched the tree, I would like to restart the conversation about how to revive and restart the Trove project. Feedback from the last go around on this subject[1] resulted in a lively discussion which I summarized in [2]. The very quick

Re: [openstack-dev] [trove] Can we move some non-voting broken jobs to the experimental queue?

Matt, we're trying our best to and the reason they were (recently) moved back to NON-experimental is that in moving them to experimental, no one monitored them. Yes, I am trying to get them to voting and like everything else in Trove, we could use some help. Yes, I realize that there are no

[openstack-dev] [All][Trove] Adding Amrith candidacy for Trove.Queens

This email is to announce my candidacy for the PTL of Trove for the Queens cycle. My candidacy has been formally submitted in[1]. I have been the PTL for the Trove project since the Trove release (in March 2016). During this time, we've seen significant improvements during the Newton and Ocata

[openstack-dev] [tc][dev][trove] Request to consider applying the status:maintenance-mode tag to the Trove project for the Queens cycle

TC, Trove folks, I've submitted [1] a request to the TC to consider applying the status:maintenance-mode tag to the Trove project for the Queens cycle. If you would like to comment on this, I suggest that you do it on the review rather than this email thread. Thanks -amrith [1]

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

off > > instance. > > > > Don't reinvent the orchestration piece. > > > > Fewer DB's better support > > > > Clusters are first class citizens, not an afterthought > > > > Clusters spanning regions and openstack deployments > > > > Rest

[openstack-dev] [all][trove] Retiring the openstack/trove-integration repository

This is an early warning that the openstack/trove-integration repository was last used for Trove in the Newton release. Ocata, and now Pike use elements and things that are in the trove repository. This is a heads-up that when Newton goes EOL, the trove-integration repository will be retired. If

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Kevin, In interests of 'keeping it simple', I'm going to try and prioritize the use-cases and pick implementation strategies which target the higher priority ones without needlessly excluding other (lower priority) ones. Thanks, -amrith -- Amrith Kumar ​ P.S. Verizon is hiring ​OpenStack

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

tinue this conversation and hope you will all be able to attend. As soon as time slots for PTG are announced, I will try and pick this slot and request that you please attend. Thanks, -amrith On Sun, Jun 18, 2017 at 6:35 AM, Amrith Kumar <amrith.ku...@gmail.com> wrote: > Trove has evol

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

we believe > that it will cause people to walk away from the community and likely > OpenStack as well. > > - Manoj > > > > From:Amrith Kumar <amrith.ku...@gmail.com> > To:"OpenStack Development Mailing List (not for usage questions)" > <open

Re: [openstack-dev] [tc][swg] The future of the Stewardship Working Group

Colette, First of all, thank you for all that you have done in leading the charge around the SWG (since long before it got that name). I had the good fortune of being able to work with the first group of members of the TC who attended the training in Michigan at Zing Train and I think the

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On Thu, Jun 22, 2017 at 4:38 PM, Zane Bitter wrote: > (Top posting. Deal with it ;) > > ​Yes, please keep the conversation going; top posting is fine, the k8s issue isn't 'off topic'. ​ > You're both right! > > Making OpenStack monolithic is not the answer. In fact,

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

​Kevin, just one comment inline below. ​ ​ On Thu, Jun 22, 2017 at 3:33 PM, Fox, Kevin M wrote: > No, I'm not necessarily advocating a monolithic approach. > > I'm saying that they have decided to start with functionality and accept > whats needed to get the task done. Theres

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Thank you Kevin. Lots of container (specific?) goodness here. -amrith -amrith -- Amrith Kumar Phone: +1-978-563-9590 On Mon, Jun 19, 2017 at 2:34 PM, Fox, Kevin M <kevin@pnnl.gov> wrote: > Thanks for starting this difficult discussion. > > I think I agree with all the

[openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Trove has evolved rapidly over the past several years, since integration in IceHouse when it only supported single instances of a few databases. Today it supports a dozen databases including clusters and replication. The user survey [1] indicates that while there is strong interest in the

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

" with any more clarity than before. So I'm missing something and judging by the follow-up's I'm not the only one. And yes, "friends of OpenStack" only begs the question who are not friends of OpenStack :) -amrith -amrith -- Amrith Kumar Phone: +1-978-563-9590 On

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

I guess this mail thread and the questions asked here fell on deaf ears because I see https://review.openstack.org/#/c/472891/1 marching its way to merging. -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sen

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

Thanks, Sean. I will heartily second that request/proposal. -amrith -amrith -- Amrith Kumar Phone: +1-978-563-9590 On Fri, Jun 9, 2017 at 11:07 AM, Sean Dague <s...@dague.net> wrote: > On 06/08/2017 02:53 PM, Akihiro Motoki wrote: > > Hi all, > > > > Is your pro

Re: [openstack-dev] [all] Call for check: is your project ready for pylint 1.7.1?

down in flames with the new pylint and I'm wondering what benefit this has for projects in general. The notion of accumulating more technical debt (enable pylint 1.7.1 and disable the new tests, cleanup code later) strikes me as less than ideal. Thanks, -amrith​ -amrith -- Amrith Kumar Phone

Re: [openstack-dev] [qa][tc][all] Tempest to reject trademark tests

> -Original Message- > From: Sean McGinnis [mailto:sean.mcgin...@gmx.com] > Sent: Thursday, June 1, 2017 4:48 PM > To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org> > Subject: Re: [openstack-dev] [qa][tc][all] Tempest to reject trademark tests >

Re: [openstack-dev] [tc][ptls][all] Potential Queens Goal: Migrate Off Paste

for queens (which I still don't understand, I've been told). -amrith -- Amrith Kumar > -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Thursday, June 1, 2017 12:38 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev]

Re: [openstack-dev] [tc][ptls][all] Potential Queens Goal: Migrate Off Paste

Thierry, isn't the py35 goal continuing for Queens? -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Thursday, June 1, 2017 4:35 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack

Re: [openstack-dev] [tc][ptls][all] Potential Queens Goal: Migrate Off Paste

goal. My 2c worth. -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: Mike [mailto:thin...@gmail.com] > Sent: Wednesday, May 31, 2017 4:39 PM > To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org> > Cc: Sean Dag

Re: [openstack-dev] [qa][tc][all] Tempest to reject trademark tests

nstack-dev/%23openstack-dev.201 7-05-31.log.html#t2017-05-31T15:39:33 -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: Jeremy Stanley [mailto:fu...@yuggoth.org] > Sent: Wednesday, May 31, 2017 12:24 PM > To: OpenStack Development Mailing List (not f

Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master

rum wrote: > > Either way, it should be much simpler to manage slave lag than to deal > > with a Galera cluster that won't accept any writes at all because it > > can't get quorum. > > Would CockroachDB be any better at achieving quorum? > > Genuinely curious.

Re: [openstack-dev] Changing project schemas in patches; upgrade implications

Thx Monty, jroll, smcginnis, zzzeek_ ... -amrith -- Amrith Kumar Phone: +1-978-563-9590 On Wed, May 31, 2017 at 10:17 AM, Monty Taylor <mord...@inaugust.com> wrote: > On 05/31/2017 08:51 AM, Amrith Kumar wrote: > >> This email thread relates to[1], a change that aims to

[openstack-dev] Changing project schemas in patches; upgrade implications

​[2]https://etherpad.openstack.org/p/BOS-postgresql ​ ​​ -- Amrith Kumar Phone: +1-978-563-9590 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

for the project to get new contributors (update: if you are interested in contributing to an openstack project, trove is looking for new participants). It would have been nice to have them video taped. -amrith -amrith -- Amrith Kumar Phone: +1-978-563-9590 On Wed, May 24, 2017 at 6:20 PM

Re: [openstack-dev] [ptg] Strawman Queens PTG week slicing

(non cross project) topics to one of the days and give a preference to cross project things on another day. This may help with scheduling cross project participation. Thanks, -amrith -amrith -- Amrith Kumar Phone: +1-978-563-9590 On Wed, May 24, 2017 at 10:44 AM, Thierry Carrez <t

Re: [openstack-dev] on the subject of when we should be deprecating API's in a release cycle

gt; On 5/23/2017 7:50 PM, Amrith Kumar wrote: > > TL;DR > > > > When IaaS projects in OpenStack deprecate their API's after milestone > > 1, it puts PaaS projects in a pickle. I think it would be much better > > for PaaS projects if the IaaS projects could please

[openstack-dev] on the subject of when we should be deprecating API's in a release cycle

... -- Amrith Kumar amrith.ku...@gmail.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman

[openstack-dev] [trove][all] Weekly meeting time change - 1500UTC #openstack-meeting-alt

://review.openstack.org/#/c/466381/ [2] http://eavesdrop.openstack.org/#Trove_(DBaaS)_Team_Meeting [3] https://wiki.openstack.org/wiki/Meetings/TroveMeeting -- Amrith Kumar GPG: 0x5e48849a9d21a29b smime.p7s Description: S/MIME cryptographic signature

Re: [openstack-dev] [tc][all] Do we need a #openstack-tc IRC channel

In keeping with the brevity of the email below, YES Enough others have opined on the why, I have nothing new to add and I am happy to just say +1 ... -amrith > -Original Message- > From: Davanum Srinivas [mailto:dava...@gmail.com] > Sent: Tuesday, May 16, 2017 9:39 AM > To: OpenStack

Re: [openstack-dev] [trove] Trove meeting time update

Thanks for doing this Trevor, I am hoping that this patch merges soon so we can do the new meeting time on Wednesday. -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: MCCASLAND, TREVOR [mailto:tm2...@att.com] > Sent: Friday, May 19, 2017 2:49 PM > T

Re: [openstack-dev] contribute to the travel assistance program

That link again https://www.eventbrite.com/e/openstack-summit-may-2017-boston-tickets-283756 75409 Sorry for the duplication. -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: Amrith Kumar [mailto:amrith.ku...@gmail.com] > Sent: Friday, May 5, 2017

[openstack-dev] contribute to the travel assistance program

down to the last ticket type. Thanks, -amrith -- Amrith Kumar amrith.ku...@gmail.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [all][elections] Technical Committee Election Results

And thanks to the election officials, Kendall, Tristan, and Tony. -amrith -- Amrith Kumar amrith.ku...@gmail.com > -Original Message- > From: Tristan Cacqueray [mailto:tdeca...@redhat.com] > Sent: Thursday, April 20, 2017 8:35 PM > To: openstack-dev@lists.openstack.or

[openstack-dev] [nova][trove] deleted instances appearing in nova's server-group list

example (attached). [1] https://bugs.launchpad.net/bugs/1682845 -- Amrith Kumar amrith.ku...@gmail.com amrith@amrith-work:/opt/stack/trove$ openstack server group create affinity-policy --policy affinity +--+--+ | Field| Value

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

Hmm, all the cool kids didn’t receive the email but I did. Now I feel bad ☹ -amrith From: Morgan Fainberg [mailto:morgan.fainb...@gmail.com] Sent: Wednesday, April 12, 2017 9:53 AM To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [trove] weekly meeting canceled today

I've not seen anything new on the agenda and I have a late scheduling conflict today. Let's catch up on IRC if there is anything that needs discussing. -- Amrith Kumar amrith.ku...@gmail.com __ OpenStack Development

Re: [openstack-dev] [tc] [elections] Available time and top priority

parallel conversations going on > during a TC meeting and it's pretty frustrating to follow along, or get a > thought in the mix. That has to be much worse for a non-native English > speaker. > > So yeah, slow down folks. :) [Amrith Kumar] A huge +1000 to that. I have found it very hard

Re: [openstack-dev] [tc] [elections] Available time and top priority

be able to dedicate to Technical Committee affairs (reviewing proposed > changes and pushing your own) ? If there was ONE thing, one initiative, one > change you will actively push in the six months between this election round > and the next, what would it be ? > [Amrith Kumar] I have th

[openstack-dev] amrith candidacy for OpenStack Technical Committee

My name is Amrith Kumar, I've been around OpenStack since a little before the IceHouse release (about 3 years ago). During this time, I've worked mostly on Trove, and a little bit on other projects but mostly in service of Trove. I've also served as a member of the Stewardship Working Group

[openstack-dev] [trove] today weekly meeting canceled

There's nothing to discuss on the agenda today so I'm canceling the meeting for today. -amrith -- Amrith Kumar amrith.ku...@gmail.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

Re: [openstack-dev] [oslo]Introduction of new driver for oslo.messaging

Great idea, happy to try it out for Trove. We love o.m.rpc :) But it needs to be secure; other comment has been posed in review, I'm doing a talk about o.m use by trove in Boston anyway, maybe we can get Melissa to join me for that? -amrith -Original Message- From: Deja, Dawid

[openstack-dev] [trove] reminder, DST adjustment

Just a reminder that the Trove weekly meeting[1] is at 1800 UTC and with the DST correction, the meeting is now 1400EDT 1100PDT Thanks, -amrith [1] http://eavesdrop.openstack.org/#Trove_(DBaaS)_Team_Meeting -- Amrith Kumar amrith.ku...@gmail.com

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

Sounds like a good candidate for a cross-project release goal. A non-controversial situation, the work is a no-op for most, a specific deliverable for a few, and a mechanism to close the loop and make sure it gets done in a specific timeframe? Thanks for surfacing it Matthew. -amrith

[openstack-dev] [trove] today weekly meeting

While I try to schedule my life to not conflict with the weekly Trove meeting, it appears that Wednesday afternoon at 1pm is a particularly popular time for people to want to meet me. This week, and next week are no exception. While I'd tried to avoid these conflicts, I've managed to be unable

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

related, the #openstack-trove channel is your best bet. -amrith -- Amrith Kumar amrith.ku...@gmail.com +1-978-563-9590 GPG: 0x5e48849a9d21a29b smime.p7s Description: S/MIME cryptographic signature __ OpenStack Development

[openstack-dev] [trove] session schedule for Pike PTG

://etherpad.openstack.org/p/trove-pike-ptg-topics -- Amrith Kumar GPG: 0x5e48849a9d21a29b smime.p7s Description: S/MIME cryptographic signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

[openstack-dev] [trove] Trove logo files

Trove team members, Please see email below from the Openstack Foundation with a link to the Trove logo files. -amrith From: Heidi Joy Tretheway [mailto:heidi...@openstack.org] Sent: Tuesday, February 14, 2017 4:53 AM To: Amrith Kumar Subject: Trove logo files Hi Amrith

Re: [openstack-dev] [trove][Neutron] Towards better stability of gate jobs

I'd like to add the same call-to-action for Trove as well. When you see a gate failure, please don't simply recheck. Let's start tracking failure patterns in Launchpad and fix them. I know this is a change from what we've been doing a lot of in Trove of late so I realize that it will take some

Re: [openstack-dev] [trove] status of the gate

before we get to Ocata. But for the present, the gate is running again. -amrith [1] https://review.openstack.org/#/c/426535/ > -Original Message- > From: Amrith Kumar [mailto:amrith.ku...@gmail.com] > Sent: Sunday, January 29, 2017 12:06 PM > To: 'OpenStack Development

[openstack-dev] [trove][tc][stable] trove core team coverage this week

to you as soon as I can. For something urgent, please include a telephone number where I can call you. Thanks for understanding. -amrith -- Amrith Kumar GPG: 0x5e48849a9d21a29b smime.p7s Description: S/MIME cryptographic signature

[openstack-dev] [trove] status of the gate

] https://review.openstack.org/#/c/412497/ -- Amrith Kumar GPG: 0x5e48849a9d21a29b smime.p7s Description: S/MIME cryptographic signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

[openstack-dev] [trove] gate currently broken, rechecking is pointless

; it isn't going to do any good to warm the planet faster than it is already. -amrith [1] https://review.openstack.org/#/c/423086/ [2] https://review.openstack.org/#/c/412497/ -- Amrith Kumar GPG: 0x5e48849a9d21a29b smime.p7s Description: S/MIME cryptographic signature

[openstack-dev] [trove] self-nomination for Trove PTL

://review.openstack.org/422891 -- Amrith Kumar GPG: 0x5e48849a9d21a29b smime.p7s Description: S/MIME cryptographic signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [Trove] Resource not found when creating db instances.

Sorry Wang Sen, why do you say Trove is not ready for Neutron"? It has worked with Neutron for some releases now. This does not appear to be at all related to Neutron. -amrith -- amrith.ku...@gmail.com On Jan 18, 2017 10:56 PM, "Wang Sen" wrote: > Hi all, > > I met

Re: [openstack-dev] [ironic] [infra] Nested KVM + the gate

Jay, This is the Trove commit … I85364c6530058e964a8eba7fb515d7deadfd5d72 -amrith From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Wednesday, January 18, 2017 7:57 AM To: OpenStack

Re: [openstack-dev] [ironic] [infra] Nested KVM + the gate

Clark is right, trove does detect and try to use kvm where possible. The performance has been well worth the change (IMHO). -amrith On Jan 17, 2017 6:53 PM, "Clark Boylan" wrote: > On Tue, Jan 17, 2017, at 03:41 PM, Jay Faulkner wrote: > > Hi all, > > > > Back in late

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

Ian, This is a fascinating conversation. Let me offer two observations. First, Trove has long debated the ideal solution for storing secrets. There have been many conversations, and Barbican has been considered many times. We sought input from people who were deploying and operating Trove at

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

Josh, It has been great working with you as the PTL of Oslo. Thanks for your leadership. -amrith > -Original Message- > From: Joshua Harlow [mailto:harlo...@fastmail.com] > Sent: Tuesday, January 3, 2017 3:04 PM > To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [trove] A question for the user survey

or more), or short answer. Please send suggestions before Wednesday so I can respond to the team assembling the survey in sufficient time. Thanks, -amrith -- Amrith Kumar <mailto:amr...@amrith.org> amr...@tesora.com +1-978-563-9590 GPG: 0x5e48849a9d21a29b smi

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

So Jeremy, that's great. so all someone has to do is pick this file and blast it out to 150 projects :) Merry Christmas, Happy Hanukah, Happy Festivus and best wishes for the feats of strenght, Happy Holidays, Have a good weekend ... (pick as many as you'd like) -amrith > -Original

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

For those who would like to know exactly what this set of changes cost in the CI, the answer is approximately 1050 jobs which consumed 190 compute hours of CI time. -amrith -Original Message- From: Amrith Kumar [mailto:amr...@tesora.com] Sent: Wednesday, December 21, 2016 11:13 AM

Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects

Ian, Andreas, Emilien, My sentiments on the subject of these kinds of "production line" changes is unchanged from [1] and [2]. A complete list of these changes is at [3]. I've updated all of the changes in this thread with a block comment and a -1. My apologies to other reviewers (and active

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

Clark, for Trove, I'm in the process of finishing this and there is a change [1] that is currently up for review (I have to incorporate changes to reflect Andreas' comments). If you find something amiss with the Trove jobs (trove, trove client, trove-integration or dashboard), please let me know

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

Thierry, when we were adding the #openstack-swg group, we had this conversation and I observed that my own preference would be for a project's meetings to be in that projects room. It makes it easier to then search for logs for something (say SWG related) in the SWG room, and I do this regularly

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

at.com] > Sent: Friday, November 25, 2016 9:00 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in > README files > > On 25/11/16 13:46 +00

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

Flavio, I see a number of patches[1] which have been landed on this project but I find that at least the ones that were landed for Trove, and a random sampling of the others all to be different from what you proposed below[2] in one important aspect. In [2] you proposed a structure where the

[openstack-dev] [all][ptls] A request: using the cross-project release goals process for openstack wide change

In the last week I've been dealing with two [1][2] cross project efforts that I believe would have been great candidates for the cross-project goals process. I think the cross project goals process is lightweight, and it is a closed-loop process which ensures that we don't have escapes. The use of

  1   2   3   4   >