Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Well, zope is a cool thing I believe. We can consider to use it. I just don’t see what real advantage it’ll give us now. Essentially, what we’re trying to do now is pretty simple. We’re just defining one base class for all actions w/o talking about various modifications of this class yet. So if

[openstack-dev] [acceleration]Team Biweekly Meeting Agenda 2017.03.15

Hi Team, Please find the initial agenda at https://wiki.openstack.org/wiki/Meetings/ CyborgTeamMeeting#Agenda_for_next_meeting our IRC channel is #openstack-cyborg -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email: huangzhip...

[openstack-dev] [tricircle]weekly meeting of Mar. 15

Hello, team, New weekly meeting time slot is UTC 14:00~UTC 15:00 Agenda of Mar.15 weekly meeting: 1. Test coverage requirement : https://review.openstack.org/#/c/444394/ 2. Demo of VNF high availability across OpenStack with Tricircle in OPNFV Beijing summit 3. Pike-1 prioritized patc

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

Renat, I was talking to some friends that have more (and more recent) experience with standalone zope.interfaces inside other projects (last time I used it was inside zope and 10 years ago) and I think it might be just overcomplexity for our task at hand. Cheers, Adriano On Wed, Mar 15,

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Wed, Mar 15, 2017 at 12:05 AM, Joshua Harlow wrote: > * How does reloading work (does it)? No. There is nothing that we can do in oslo that will make services magically reload configuration. It's also unclear to me if that's something to do. In a containerized environment, wouldn't it be simp

Re: [openstack-dev] [neutron][gate] functional job busted

On 14/03, Ihar Hrachyshka wrote: > Hi all, > > the patch that started to produce log index file for logstash [1] and > the patch that switched metadata proxy to haproxy [2] landed and > together busted the functional job because the latter produces log > messages with null-bytes inside, while os-lo

Re: [openstack-dev] [mistral] Mistral Custom Actions API Design

> On 15 Mar 2017, at 15:32, Adriano Petrich wrote: > >I was talking to some friends that have more (and more recent) experience > with standalone zope.interfaces inside other projects (last time I used it > was inside zope and 10 years ago) and I think it might be just overcomplexity > fo

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

Mike Bayer wrote: > As mentioned previously, SQLAlchemy 1.1 has now been released for about > six months. My work now is on SQLAlchemy 1.2 which should hopefully > see initial releases in late spring.SQLAlchemy 1.1 includes tons of > features, bugfixes, and improvements, and in particular the

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

Colette Alexander wrote: > Currently the Stewardship Working Group meetings every other Thursday at > 1400 UTC. > > We've had a couple of pings from folks who are interested in joining us > for meetings that live in US Pacific Time, and that Thursday time isn't > terribly conducive to them being

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

On Tue, Mar 14 2017, Clint Byrum wrote: > +1 for just pulling it under the oslo umbrella but not renaming it. As > much as I like the uniformity oslo.keymanager would bring, I think it's > already adopted well enough we just want to make it clear that it is > blessed and ok to adopt. I don't even

[openstack-dev] [tripleo] Gating jobs are now running with Quickstart

As discussed previously in the CI Squad meeting summaries[1] and on the TripleO weekly meeting, the multinode gate jobs are now running with tripleo-quickstart. To signify the change, we added the -oooq suffix to them. The following jobs migrated yesterday evening, with more to come: - gate-t

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Joshua Harlow wrote: > Monty Taylor wrote: >> On 03/14/2017 06:04 PM, Davanum Srinivas wrote: >>> PS: Between this thread and the other one about Tooz/DLM and >>> os-lively, we can probably make a good case to add etcd as a base >>> always-on service. >> >> As I mentioned in the other thread, there

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Julien Danjou wrote: > On Tue, Mar 14 2017, Clint Byrum wrote: > >> +1 for just pulling it under the oslo umbrella but not renaming it. As >> much as I like the uniformity oslo.keymanager would bring, I think it's >> already adopted well enough we just want to make it clear that it is >> blessed a

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

On Wed, Mar 15 2017, Thierry Carrez wrote: > It's a governance problem. Basically if the abstraction layer is under > the control of the same group as one of the drivers, it's not really an > abstraction layer, and nobody will adopt it or develop another driver > for it. So we hope that by changi

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Monty, Team, Sorry for the top post: Support for etcd/tooz in devstack (with file driver as default) - https://review.openstack.org/#/c/445432/ As of right now both zookeeper driver and etcd driver is working fine: https://review.openstack.org/#/c/445630/ https://review.openstack.org/#/c/445629/

[openstack-dev] [neutron] [vpnaas] Contribution in order to bring VPNaaS back into the neutron governance

Hi everyone, As you know that the project neutron-vpnaas is no longer part of the neutron governance in Ocata [1][2]. I am planning/working to address the gaps identified in [2] in order to bring it back into the neutron governance. And according to the information from Kevin's email [3] (PTG su

Re: [openstack-dev] [all] Forum Brainstorming - Boston 2017

Emilien Macchi wrote: > [...] > Please let me know if any help is needed, we're likely going to > postpone the submission deadline to somewhere in April so we let more > time to people in organizing the topics. For clarity, the new deadlines are: March 20: end of brainstorming phase, opening of f

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

On Mon, Mar 13 2017, Clint Byrum wrote: > To me, Oslo is a bunch of libraries that encompass "the way OpenStack > does ". When is key management, projects are, AFAICT, universally > using Castellan at the moment. So I think it fits in Oslo > conceptually. It would be cool if it could rat

Re: [openstack-dev] [Neutron][LBaaS][heat] Removing LBaaS v1 - are weready?

Hello Michael, Thank you for the assurances regarding neutron-lbaas to octavia migration. Sometimes, i honestly feel that OpenStack needs somebody who can implement *a* rule something like "WE DO NOT BREAK USERSPACE!" rule from linux kernel community. Cheers, Syed On Fri, Mar 10, 2017 at 10:57

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

On 03/15/2017 05:32 AM, Thierry Carrez wrote: > Mike Bayer wrote: >> As mentioned previously, SQLAlchemy 1.1 has now been released for about >> six months. My work now is on SQLAlchemy 1.2 which should hopefully >> see initial releases in late spring.SQLAlchemy 1.1 includes tons of >> feature

Re: [openstack-dev] [neutron][gate] functional job busted

Thank you for the patches. I merged them, released 1.1.0 and proposed [1] Cheers!, [1] //review.openstack.org/445884 On Wed, Mar 15, 2017 at 10:14 AM, Gorka Eguileor wrote: > On 14/03, Ihar Hrachyshka wrote: > > Hi all, > > > > the patch that started to produce log index file for logstash [1]

Re: [openstack-dev] [keystone] slide deck

Thanks Lance, this is very useful. On Tue, Mar 14, 2017 at 11:07 PM, Lance Bragstad wrote: > Of course I would make changes to the template *right* after sending this > email. I'll just share the presentation that I have [0]. > > https://docs.google.com/presentation/d/1s9BNHI4aHs_ > fEcCYuekDCFw

Re: [openstack-dev] [tripleo][heat] Heat memory usage in the TripleO gate: Ocata edition

On Tue, Mar 14, 2017 at 10:21:54PM -0400, Emilien Macchi wrote: > On Tue, Mar 14, 2017 at 4:06 PM, Zane Bitter wrote: > > Following up on the previous thread: > > > > http://lists.openstack.org/pipermail/openstack-dev/2017-January/109748.html > > > > Here is the latest data, which includes the Oca

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

On 02/27/2017 12:34 PM, Andrea Frittoli wrote: Hello folks, TL;DR: if today you import manager,py from tempest.scenario please maintain a copy of [0] in tree until further notice. Hi! I hope it is pretty obvious, but just to be clear. Anything that this copied file uses should be treated mor

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/14/2017 11:00 PM, Monty Taylor wrote: > a) awesome. when the rest of this dips momentarily into words that might > sound negative, please hear it all wrapped in an "awesome" and know that > my personal desire is to see the thing you're working on be successful > without undue burden... > >

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

+1000 Sean. Thanks, Dims On Wed, Mar 15, 2017 at 7:44 AM, Sean Dague wrote: > On 03/14/2017 11:00 PM, Monty Taylor wrote: > >> a) awesome. when the rest of this dips momentarily into words that might >> sound negative, please hear it all wrapped in an "awesome" and know that >> my personal desi

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 07:44 AM, Sean Dague wrote: On 03/14/2017 11:00 PM, Monty Taylor wrote: a) awesome. when the rest of this dips momentarily into words that might sound negative, please hear it all wrapped in an "awesome" and know that my personal desire is to see the thing you're working on be suc

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On 15 March 2017 at 03:23, Monty Taylor wrote: > On 03/15/2017 12:05 AM, Joshua Harlow wrote: >> So just fyi, this has been talked about before (but prob in context of >> zookeeper or various other pluggable config backends). >> >> Some links: >> >> - https://review.openstack.org/#/c/243114/ >> -

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 15 March 2017 at 11:58, Jay Pipes wrote: > On 03/15/2017 07:44 AM, Sean Dague wrote: >> >> On 03/14/2017 11:00 PM, Monty Taylor wrote: >> >>> >>> a) awesome. when the rest of this dips momentarily into words that might >>> sound negative, please hear it all wrapped in an "awesome" and know tha

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

On 15 March 2017 at 09:50, Thierry Carrez wrote: > Colette Alexander wrote: >> Currently the Stewardship Working Group meetings every other Thursday at >> 1400 UTC. >> >> We've had a couple of pings from folks who are interested in joining us >> for meetings that live in US Pacific Time, and that

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 13 March 2017 at 15:17, Jay Pipes wrote: > On 03/13/2017 11:13 AM, Dan Smith wrote: >> >> Interestingly, we just had a meeting about cells and the scheduler, >> which had quite a bit of overlap on this topic. >> >>> That said, as mentioned in the previous email, the priorities for Pike >>> (and

[openstack-dev] [all] [api] API stability and change guidelines

Short Version: Please review "Refactor and re-validate api change guidelines" https://review.openstack.org/#/c/421846/ this week because we intend to freeze it next week and I've heard a lot of people comment lots of places but not on the review. Long Version: At the PTG we had nearly a full d

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 08:10 AM, John Garbutt wrote: > On 15 March 2017 at 11:58, Jay Pipes wrote: >> On 03/15/2017 07:44 AM, Sean Dague wrote: >>> >>> On 03/14/2017 11:00 PM, Monty Taylor wrote: >>> a) awesome. when the rest of this dips momentarily into words that might sound negative, pl

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 13 March 2017 at 21:10, Zane Bitter wrote: > Yes. this is a problem with the default policy - if you have *any* role in a > project then you get write access to everything in that project. I don't > know how I can even call this role-based, since everybody has access to > everything regardless

Re: [openstack-dev] [nova] [notification] BlockDeviceMapping in InstancePayload

On 13 March 2017 at 17:14, Balazs Gibizer wrote: > Hi, > > As part of the Searchlight integration we need to extend our instance > notifications with BDM data [1]. As far as I understand the main goal is to > provide enough data about the instance to Searchlight so that Nova can use > Searchlight

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 03/13/2017 05:10 PM, Zane Bitter wrote: >> I'm not sure I agree. One can very simply inject needed credentials >> into a running VM and have it interact with the cloud APIs. > > Demo please! > > Most Keystone backends are read-only, you can't even create a new user > account yourself. It's an

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 15 March 2017 at 12:33, Sean Dague wrote: > On 03/15/2017 08:10 AM, John Garbutt wrote: >> On 15 March 2017 at 11:58, Jay Pipes wrote: >>> On 03/15/2017 07:44 AM, Sean Dague wrote: On 03/14/2017 11:00 PM, Monty Taylor wrote: > > a) awesome. when the rest of this dips mo

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On Wed, 2017-03-15 at 08:33 -0400, Sean Dague wrote: > On 03/15/2017 08:10 AM, John Garbutt wrote: > > On 15 March 2017 at 11:58, Jay Pipes wrote: > > > On 03/15/2017 07:44 AM, Sean Dague wrote: > > > > > > > > On 03/14/2017 11:00 PM, Monty Taylor wrote: > > > > > > > > > > > > > > a) awesome.

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On 03/15/2017 02:16 AM, Clint Byrum wrote: > Excerpts from Monty Taylor's message of 2017-03-15 04:36:24 +0100: >> On 03/14/2017 06:04 PM, Davanum Srinivas wrote: >>> Team, >>> >>> So one more thing popped up again on IRC: >>> https://etherpad.openstack.org/p/oslo.config_etcd_backend >>> >>> What d

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 11:37 AM, Davanum Srinivas wrote: > Monty, Team, > > Sorry for the top post: > > Support for etcd/tooz in devstack (with file driver as default) - > https://review.openstack.org/#/c/445432/ > > As of right now both zookeeper driver and etcd driver is working fine: > https://review.

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 01:48 PM, John Garbutt wrote: > On 15 March 2017 at 12:33, Sean Dague wrote: >> On 03/15/2017 08:10 AM, John Garbutt wrote: >>> On 15 March 2017 at 11:58, Jay Pipes wrote: On 03/15/2017 07:44 AM, Sean Dague wrote: > > On 03/14/2017 11:00 PM, Monty Taylor wrote: > >

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On Wed, Mar 15, 2017 at 9:19 AM, Monty Taylor wrote: > On 03/15/2017 11:37 AM, Davanum Srinivas wrote: >> Monty, Team, >> >> Sorry for the top post: >> >> Support for etcd/tooz in devstack (with file driver as default) - >> https://review.openstack.org/#/c/445432/ >> >> As of right now both zookee

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On Wed, Mar 15 2017, Davanum Srinivas wrote: > Yep, jd__ and i confirmed that things work with 3.x Though to be clear, what's used in tooz is the v2 HTTP API, not the new v3 gRPC API. -- Julien Danjou # Free Software hacker # https://julien.danjou.info signature.asc Description: PGP signature

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On Wed, Mar 15, 2017 at 1:44 PM, Julien Danjou wrote: > On Wed, Mar 15 2017, Davanum Srinivas wrote: > >> Yep, jd__ and i confirmed that things work with 3.x > > Though to be clear, what's used in tooz is the v2 HTTP API, not the new > v3 gRPC API. And just to be double clear: although etcd 3.x c

Re: [openstack-dev] [neutron][gate] functional job busted

That was quick folks. Thanks everyone for moving the patches forward. Ihar On Wed, Mar 15, 2017 at 4:32 AM, Miguel Angel Ajo Pelayo wrote: > Thank you for the patches. I merged them, released 1.1.0 and proposed [1] > > Cheers!, > > [1] //review.openstack.org/445884 > > > On Wed, Mar 15, 2017 at

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

On 03/15/2017 07:30 AM, Sean Dague wrote: The problem was the original patch kept a cap on SQLA, just moved it up to the next pre-release, not realizing the caps in general are the concern by the requirements team. So instead of upping the cap, I just removed it entirely. (It also didn't help

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 02:26 PM, Davanum Srinivas wrote: > On Wed, Mar 15, 2017 at 9:19 AM, Monty Taylor wrote: >> On 03/15/2017 11:37 AM, Davanum Srinivas wrote: >>> Monty, Team, >>> >>> Sorry for the top post: >>> >>> Support for etcd/tooz in devstack (with file driver as default) - >>> https://review.op

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 02:44 PM, Julien Danjou wrote: > On Wed, Mar 15 2017, Davanum Srinivas wrote: > >> Yep, jd__ and i confirmed that things work with 3.x > > Though to be clear, what's used in tooz is the v2 HTTP API, not the new > v3 gRPC API. But if it conceptually works with v3 server using v2 htt

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 03/15/2017 02:52 PM, Louis Taylor wrote: > On Wed, Mar 15, 2017 at 1:44 PM, Julien Danjou wrote: >> On Wed, Mar 15 2017, Davanum Srinivas wrote: >> >>> Yep, jd__ and i confirmed that things work with 3.x >> >> Though to be clear, what's used in tooz is the v2 HTTP API, not the new >> v3 gRPC AP

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On Wed, Mar 8, 2017 at 8:09 PM Monty Taylor wrote: > On 03/08/2017 10:31 AM, Daniel P. Berrange wrote: > > On Wed, Mar 08, 2017 at 09:12:59AM -0600, Monty Taylor wrote: > >> Hey all, > >> > >> We have a set of old vanity redirect URLs from back when we made a URL > >> for each project: > >> > >>

[openstack-dev] [ironic] volunteers for cross project liaisons

Hi, The ironic community is looking for volunteers to be cross-project liaisons [1] for these projects: - oslo - logging working group - i18n The expectations are documented in [1] on a per-project basis. The amount of commitment varies depending on the project (and I don't know what that might

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Wed, Mar 15, 2017 at 04:23:09AM +0100, Monty Taylor wrote: > On 03/15/2017 12:05 AM, Joshua Harlow wrote: > > So just fyi, this has been talked about before (but prob in context of > > zookeeper or various other pluggable config backends). > > > > Some links: > > > > - https://review.openstack

Re: [openstack-dev] [ironic] volunteers for cross project liaisons

> On Mar 15, 2017, at 8:11 AM, Loo, Ruby wrote: > > Hi, > > The ironic community is looking for volunteers to be cross-project liaisons > [1] for these projects: > - oslo > - logging working group > - i18n The i18n and docs projects are closely related. I also don’t think they do a lot of tr

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On Wed, Mar 15 2017, Monty Taylor wrote: > On 03/15/2017 02:44 PM, Julien Danjou wrote: >> On Wed, Mar 15 2017, Davanum Srinivas wrote: >> >>> Yep, jd__ and i confirmed that things work with 3.x >> >> Though to be clear, what's used in tooz is the v2 HTTP API, not the new >> v3 gRPC API. > > But

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

On 03/15/2017 10:38 AM, Mike Bayer wrote: > > > On 03/15/2017 07:30 AM, Sean Dague wrote: >> >> The problem was the original patch kept a cap on SQLA, just moved it up >> to the next pre-release, not realizing the caps in general are the >> concern by the requirements team. So instead of upping t

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

Isn't the purpose of that specific job - gate-tempest-dsvm-neutron-src-oslo.db-ubuntu-xenial-ocata - to test a change to the library master branch with stable releases (i.e. Ocata) - of all other components? On Wed, Mar 15, 2017 at 5:20 PM, Sean Dague wrote: > On 03/15/2017 10:38 AM, Mike Bayer w

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

On Wed, Mar 15, 2017 at 5:18 AM, Thierry Carrez wrote: > Julien Danjou wrote: > > On Tue, Mar 14 2017, Clint Byrum wrote: > > > >> +1 for just pulling it under the oslo umbrella but not renaming it. As > >> much as I like the uniformity oslo.keymanager would bring, I think it's > >> already adopt

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

Perhaps, but in doing so oslo.db is going to get the pin and uc from stable/ocata, which is going to force it back to SQLA < 1.1, which will prevent oslo.db changes that require >= 1.1 to work. -Sean On 03/15/2017 11:26 AM, Roman Podoliaka wrote: > Isn't the purpose of that specific job -

[openstack-dev] [TripleO] Propose Attila Darazs and Gabriele Cerami for tripleo-ci core

Both Attila and Gabriele have been rockstars with the work to transition tripleo-ci to run via quickstart, and both have become extremely knowledgeable about how tripleo-ci works during that process. They are both very capable of providing thorough and thoughtful reviews of tripleo-ci patches. On

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

On Wed, Mar 15, 2017 at 11:38 AM Dmitry Tantsur wrote: > On 02/27/2017 12:34 PM, Andrea Frittoli wrote: > > Hello folks, > > > > TL;DR: if today you import manager,py from tempest.scenario please > maintain a > > copy of [0] in tree until further notice. > > Hi! > > I hope it is pretty obvious, b

[openstack-dev] [cinder] Additional Grenade jobs for Cinder patches

Hi, We now have two additional gate jobs which can be used to test patches that modify RPC API, objects or DB Schema for incompatibilities. These two jobs are non-voting and can be invoked on cinder patches by typing “check experimental” as a comment on that patch. The two-additional gate jobs

[openstack-dev] [QA] Forum Boston - Brainstorming

Hello folks, I set up an etherpad [0] for the QA team to track topic ideas / proposals for the Forum [1]. Please feel free to contribute ideas, we'll have a slot to discuss about this during our meetings starting tomorrow. Andrea [0] https://etherpad.openstack.org/p/BOS-QA-brainstorming [1] http

[openstack-dev] [infra][requirements] Does proposal bot also update foo-requirements.txt?

Hi, I wanted to understand which project requirement files get updated by the OpenStack proposal bot. Only requirements.txt and test-requirements.txt, or also foo-requirements.txt? Pointing me to the OpenStack proposal bot code would also help I guess... Thanks -- - Andreas IRC: andreas_s

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

This might be related to the current discussion. In one of the keystone PTG sessions we started to talk about API keys. [0] A spec is being written and discussed. [1] This would allow the user to provision API key credentials with a subset of roles for use inside of their applications. Removing

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 15/03/17 08:45, Sean Dague wrote: On 03/13/2017 05:10 PM, Zane Bitter wrote: I'm not sure I agree. One can very simply inject needed credentials into a running VM and have it interact with the cloud APIs. Demo please! Most Keystone backends are read-only, you can't even create a new user

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

On 03/15/2017 11:42 AM, Sean Dague wrote: Perhaps, but in doing so oslo.db is going to get the pin and uc from stable/ocata, which is going to force it back to SQLA < 1.1, which will prevent oslo.db changes that require >= 1.1 to work. so do we want to make that job non-voting or something

Re: [openstack-dev] [infra][requirements] Does proposal bot also update foo-requirements.txt?

On Wed, Mar 15, 2017, at 09:20 AM, Andreas Scheuring wrote: > Hi, > I wanted to understand which project requirement files get updated by > the OpenStack proposal bot. Only requirements.txt and > test-requirements.txt, or also foo-requirements.txt? > > Pointing me to the OpenStack proposal bot cod

Re: [openstack-dev] [TripleO] Propose Attila Darazs and Gabriele Cerami for tripleo-ci core

On Wed, Mar 15, 2017 at 11:44:22AM -0400, John Trowbridge wrote: > Both Attila and Gabriele have been rockstars with the work to transition > tripleo-ci to run via quickstart, and both have become extremely > knowledgeable about how tripleo-ci works during that process. They are > both very capable

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Sean Dague's message of 2017-03-15 08:45:54 -0400: > On 03/13/2017 05:10 PM, Zane Bitter wrote: > > >> I'm not sure I agree. One can very simply inject needed credentials > >> into a running VM and have it interact with the cloud APIs. > > > > Demo please! > > > > Most Keystone bac

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Kristi Nikolla's message of 2017-03-15 12:35:45 -0400: > This might be related to the current discussion. > > In one of the keystone PTG sessions we started to talk about API keys. [0] > A spec is being written and discussed. [1] > > This would allow the user to provision API key c

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On Wed, Mar 15, 2017, at 06:19 AM, Monty Taylor wrote: > On 03/15/2017 11:37 AM, Davanum Srinivas wrote: > > Monty, Team, > > > > Sorry for the top post: > > > > Support for etcd/tooz in devstack (with file driver as default) - > > https://review.openstack.org/#/c/445432/ > > > > As of right now

Re: [openstack-dev] [acceleration]Team Biweekly Meeting Agenda 2017.03.15

Hi Team, Please find the meeting minutes at https://docs.google.com/document/d/14Ab100zV0h_g2U0dhxYQ7hbzIU_6xH329hBv6cqDgWk/edit?usp=sharing . We had a great discussion todday and it was agreed that BP discussions will be carried on gerrit for spec review. Another agreement is that since we began

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Excerpts from Clark Boylan's message of 2017-03-15 09:50:49 -0700: > On Wed, Mar 15, 2017, at 06:19 AM, Monty Taylor wrote: > > On 03/15/2017 11:37 AM, Davanum Srinivas wrote: > > > Monty, Team, > > > > > > Sorry for the top post: > > > > > > Support for etcd/tooz in devstack (with file driver as

Re: [openstack-dev] [TripleO] Propose Attila Darazs and Gabriele Cerami for tripleo-ci core

On 03/15/2017 04:44 PM, John Trowbridge wrote: > Both Attila and Gabriele have been rockstars with the work to transition > tripleo-ci to run via quickstart, and both have become extremely > knowledgeable about how tripleo-ci works during that process. They are > both very capable of providing thor

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Other OpenStack subsystems (such as Heat) handle this with Trusts. A service account is made in a different, usually SQL backed Keystone Domain and a trust is created associating the service account with the User. This mostly works but does give the trusted account a lot of power, as the roles

Re: [openstack-dev] [all] Small steps for Go

Still, I’m intrigued by this apparent duplication of efforts... esp since the discussions at the committee level tended to go the ‘inclusive’ way toward other communities (http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/ section “Adjacent technologies”), can

Re: [openstack-dev] [all] Small steps for Go

Bruno, Here it is: https://etherpad.openstack.org/p/go-and-containers (it was on the first email of this thread) Thanks, Dims On Wed, Mar 15, 2017 at 1:46 PM, Bruno Morel wrote: > Still, I’m intrigued by this apparent duplication of efforts... > esp since the discussions at the committee level

[openstack-dev] [ptls] Project On-Boarding Rooms

Hello All! As you may have seen in a previous thread [1] the Forum will offer project on-boarding rooms! This idea is that these rooms will provide a place for new contributors to a given project to find out more about the project, people, and code base. The slots will be spread out throughout the

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

I'm interested in having a room for Swift. --John On 15 Mar 2017, at 11:20, Kendall Nelson wrote: > Hello All! > > As you may have seen in a previous thread [1] the Forum will offer project > on-boarding rooms! This idea is that these rooms will provide a place for > new contributors to a giv

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

+1 for Watcher Best Regards, _ Alexander Chadin OpenStack Developer Servionica LTD a.cha...@servionica.ru +7 (916) 693-58-81 On 15 Mar 2017, at 21:20, Kendall Nelson mailto:kennelso...@gmail.com>> wrote: Hello All! As you may have seen in

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 03/15/2017 01:21 PM, Fox, Kevin M wrote: Other OpenStack subsystems (such as Heat) handle this with Trusts. A service account is made in a different, usually SQL backed Keystone Domain and a trust is created associating the service account with the User. This mostly works but does give the

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

One for Kolla too please:) On 15 March 2017 at 11:35, Чадин Александр (Alexander Chadin) wrote: > +1 for Watcher > > Best Regards, > _ > Alexander Chadin > OpenStack Developer > Servionica LTD > a.cha...@servionica.ru > +7 (916) 693-58-81 > > On 15 Mar 2017, at 21:20, Kend

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

I would love to have one for on-boarding new identity developers. On Wed, Mar 15, 2017 at 1:43 PM, Michał Jastrzębski wrote: > One for Kolla too please:) > > On 15 March 2017 at 11:35, Чадин Александр (Alexander Chadin) > wrote: > > +1 for Watcher > > > > Best Regards, > > _

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

On Wed, Mar 15, 2017 at 8:15 AM, John Garbutt wrote: > On 15 March 2017 at 09:50, Thierry Carrez wrote: > > Colette Alexander wrote: > >> Currently the Stewardship Working Group meetings every other Thursday at > >> 1400 UTC. > >> > >> We've had a couple of pings from folks who are interested in

Re: [openstack-dev] [neutron][ml2] - driver capability/feature verification framework

RFE is at https://bugs.launchpad.net/neutron/+bug/1673142. -Bob On 3/13/17 2:37 PM, Robert Kukura wrote: Hi Kevin, I will file the RFE this week. -Bob On 3/13/17 2:05 PM, Kevin Benton wrote: Hi, At the PTG we briefly discussed a generic system for verifying that the appropriate drivers

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

I think they are. If they are not, things will break if federation is used for sure. If you know that it is please let me know. I want to deploy federation at some point but was waiting for dashboard support. Now that the dashboard supports it, I may try it soon. Its a no-go still though if heat

[openstack-dev] [nova] Pike summit attendance

I've added an "Attendance" section to the bottom of the Nova Forum Brainstorming etherpad [1]. If you are going to the summit, or are at least pretty sure you'll be going, please add your name to that list. This will help me get an idea of who is all going to be there so I can take that into ac

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

+Boris B On 03/15/2017 02:55 PM, Fox, Kevin M wrote: I think they are. If they are not, things will break if federation is used for sure. If you know that it is please let me know. I want to deploy federation at some point but was waiting for dashboard support. Now that the dashboard supports

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Jay Pipes's message of 2017-03-15 15:06:26 -0400: > +Boris B > > On 03/15/2017 02:55 PM, Fox, Kevin M wrote: > > I think they are. If they are not, things will break if federation is used > > for sure. If you know that it is please let me know. I want to deploy > > federation at so

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

Excerpts from Brant Knudson's message of 2017-03-15 10:27:49 -0500: > On Wed, Mar 15, 2017 at 5:18 AM, Thierry Carrez > wrote: > > > Julien Danjou wrote: > > > On Tue, Mar 14 2017, Clint Byrum wrote: > > > > > >> +1 for just pulling it under the oslo umbrella but not renaming it. As > > >> much a

Re: [openstack-dev] [oslo][requirements][all] requesting assistance to unblock SQLAlchemy 1.1 from requirements

Excerpts from Mike Bayer's message of 2017-03-15 12:39:48 -0400: > > On 03/15/2017 11:42 AM, Sean Dague wrote: > > Perhaps, but in doing so oslo.db is going to get the pin and uc from > > stable/ocata, which is going to force it back to SQLA < 1.1, which will > > prevent oslo.db changes that requi

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Thomas Herve's message of 2017-03-15 09:41:16 +0100: > On Wed, Mar 15, 2017 at 12:05 AM, Joshua Harlow wrote: > > > * How does reloading work (does it)? > > No. There is nothing that we can do in oslo that will make services > magically reload configuration. It's also unclear to me

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

On 3/15/17, 6:51 AM, "Julien Danjou" wrote: >On Mon, Mar 13 2017, Clint Byrum wrote: > >> To me, Oslo is a bunch of libraries that encompass "the way OpenStack >> does ". When is key management, projects are, AFAICT, >>universally >> using Castellan at the moment. So I think it fits in

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Monty Taylor's message of 2017-03-15 04:36:24 +0100: > On 03/14/2017 06:04 PM, Davanum Srinivas wrote: > > Team, > > > > So one more thing popped up again on IRC: > > https://etherpad.openstack.org/p/oslo.config_etcd_backend > > > > What do you think? interested in this work? > > >

Re: [openstack-dev] [kolla] Proposing duonghq for core

+1 Great job Duong! Regards, Vikram Hosakote IRC: vhosakot From: Michał Jastrzębski mailto:inc...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, March 08, 2017 at 11:21 PM To: "OpenStack Developme

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 15/03/17 14:41, Jay Pipes wrote: On 03/15/2017 01:21 PM, Fox, Kevin M wrote: Other OpenStack subsystems (such as Heat) handle this with Trusts. A service account is made in a different, usually SQL backed Keystone Domain and a trust is created associating the service account with the User. T

Re: [openstack-dev] [tripleo][heat] Heat memory usage in the TripleO gate: Ocata edition

On Tue, Mar 14, 2017 at 4:06 PM, Zane Bitter wrote: > Following up on the previous thread: > > http://lists.openstack.org/pipermail/openstack-dev/2017-January/109748.html > > Here is the latest data, which includes the Ocata release: > > https://fedorapeople.org/~zaneb/tripleo-memory/20170314/heat

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Wed, Mar 15, 2017 at 09:41:16AM +0100, Thomas Herve wrote: > On Wed, Mar 15, 2017 at 12:05 AM, Joshua Harlow wrote: > > > * How does reloading work (does it)? > > No. There is nothing that we can do in oslo that will make services > magically reload configuration. It's also unclear to me if t

[openstack-dev] [openstack-ansible] Choosing a name for the OSA Python package

Hello, I'm working on making the OpenStack-Ansible inventory code available within a Python package, rather than simply living in the git repository. While initially I used 'openstack_ansible' as a name in my patch [1], I'm open to suggestions for something slightly less confusing, if others a

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

Horizon would love the opportunity to baffle newcomers. This could also be useful for the many plugins that are managed by their respective service teams. Rob On 15 Mar 2017, at 18:20, Kendall Nelson mailto:kennelso...@gmail.com>> wrote: Hello All! As you may have seen in a previous thread [1

  1   2   >