[openstack-dev] [Docs] Changes for OpenStack API guides

Hello Anne, I'm working on "moving to Keystone v3 API" spec for Neutron [1]. HenryG mentioned, that in next release or so, there will be change how to describe changes connected to API [2]. In spec I'm mentioning, that some changes are required to Networking API v2 [3], so would like to know,

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Mondays 21UTC and Tuesdays 14UTC are OK for me, so personally I do not have problem to attend both meetings, but I know that for someone one or another can be in the middle of night. In this case, would be good to again have bi-weekly to allow attendance at least once per two weeks. +1 for

Re: [openstack-dev] changing in neutron code

Hey Atif, Welcome to the Community. If you do not know where to start, I'd suggest to read this wiki page [1]. Because you've mentioned Neutron, you can join #openstack-neutron channel on Freenode and talk to other people there. Kilo release is currently considered stable, so just bugfix are

Re: [openstack-dev] [Keystone][Neutron][Nova][devstack] Keystone v3 with "old" clients

r/python- > neutronclient/usage/cli.html#using-with-os-client-config > > Akihiro > > 2016-01-14 18:13 GMT+09:00 Michal Rostecki > <mroste...@mirantis.com <mailto:mroste...@mirantis.com> >: > > On 01/12/2016 02:10 PM, Smigiel, Darius

Re: [openstack-dev] [Neutron] Heads up for decomposed plugin break

> Doug Wiegley wrote: > > > > > >> On Jan 11, 2016, at 2:42 AM, Ihar Hrachyshka > wrote: > >> > >> Sean M. Collins wrote: > >> > On Fri, Jan 08, 2016 at 07:50:47AM PST, Chris Dent wrote: > > On Fri, 8 Jan 2016,

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

> On 2016/01/12 7:14, Armando M. wrote: > On 11 January 2016 at 13:54, Hirofumi Ichihara > > > wrote: > On 2016/01/12 5:14, Armando M. wrote: > On 11 January 2016 at 12:04, Carl

Re: [openstack-dev] [Neutron] Heads up for decomposed plugin break

ese as public methods. > Thanks > Gary > OK, get it. But just wanted to know, what is the outcome from email discussion. Do we need to match changed/removed private methods with deprecation warning, or just modify and tell plugins: "deal with it" :) BR, Dariusz (dasm) Smigiel &

[openstack-dev] [Keystone][Neutron][Nova] Keystone v3 with "old" clients

Hello, I'm trying to gather all the info necessary to migrate to keystone v3 in Neutron. When I've started to looking through possible problems with clients, it occurred that 'neutron' and 'nova' clients do not want to operate with Keystone v3. For keystone client, it's explicit written, that

Re: [openstack-dev] Fwd: [Neutron] Team meeting this Monday at 2100 UTC

> -Original Message- > From: Kevin Benton [mailto:blak...@gmail.com] > > I liked using the meeting for it because it was a nice way for everyone to get > a snapshot of where each thing was at. +1 The idea of discussing everything on meeting is very good. Everyone interested is on the

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

logic, seamlesslysomething > > worth investigating (zzzeek may be of help here). The sooner we start > > here, the sooner we catch and fix breakages > > > > 4) Tackle the codebase sweep. > > > > As for projects that use neutron and use the internal APIs, I can't

[openstack-dev] [Neutron] Rename tenant to project: discussion

Hey Neutrinos (thanks armax for this word :), Keystone is planning to deprecate V2 API (again :). This time in Mitaka [6], and probably forever. It will stay at least four releases, but we need to decide, how to conquer problem of renaming... And more important: consider if it's a problem for

Re: [openstack-dev] [Neutron] Bug deputy process

> From: Kyle Mestery [mailto:mest...@mestery.com] [...] > One concern I have is ensuring we rotate people, because it does take some > time, and if the same handful of rotate, they will burn out. So I actively > encourage more people to volunteer, you don't even have to be a Neutron core >

Re: [openstack-dev] [Neutron][Infra] "gate-neutron-lbaasv1-dsvm-api" blocking patch merge

> > On 04/11/15 12:48, Mohan Kumar wrote: > > Hi, > > > > Jenkins blocking patch merge due to " > > gate-neutron-lbaasv1-dsvm-api > > dsvm- > api/f631adf/>" > > > > > failures which is unrelated to patch-set changes . > > > >

Re: [openstack-dev] [kolla] Proposal for changing 1600UTC meeting to 1700 UTC

Folks, Several people have messaged me from EMEA timezones that 1600UTC fits right into the middle of their family life (ferrying kids from school and what-not) and 1700UTC while not perfect, would be a better fit time-wise. For all people that intend to attend the 1600 UTC, could I get

Re: [openstack-dev] [TripleO] Consistent variable documentation for diskimage-builder elements

Excerpts from Dan Prince's message of 2015-04-13 14:07:28 -0700: On Tue, 2015-04-07 at 21:06 +, Gregory Haynes wrote: Hello, Id like to propse a standard for consistently documenting our diskimage-builder elements. I have pushed a review which transforms the apt-sources

Re: [openstack-dev] [TripleO] Consistent variable documentation for diskimage-builder elements

Hello, Id like to propse a standard for consistently documenting our diskimage- builder elements. I have pushed a review which transforms the apt-sources element to this format[1][2]. Essentially, id like to move in the direction of making all our element README.rst's contain a sub section

Re: [openstack-dev] [TripleO] QuintupleO Overview

On 17 March 2015 at 09:30, Ben Nemec openst...@nemebean.com wrote: So I've successfully done a deployment to a QuintupleO environment. \o/ \o/ Great news! Congrats! @Ben, are you planning to keep it up-to-date or create repo with README? I would also like to be involved in TripleO

Re: [openstack-dev] [devstack] pip wheel' requires the 'wheel' package

From: yuntong [mailto:yuntong...@gmail.com] Sent: Monday, March 2, 2015 7:35 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [devstack] pip wheel' requires the 'wheel' package Hello, I got an error when try to ./stack.sh as: 2015-03-02 05:58:20.692 |