[openstack-dev] [glance] Newton priorities, processes, dates, spec owners and reviewers

Hello all, Here are a few important announcements for the members involved in the Glance community. Priorities: === * The Glance priorities for Newton were discussed at the contributors' meetup at summit. * There are a few items that were carried forward from Mitaka that are still our

Re: [openstack-dev] [magnum] How to document 'labels'

Hi, +1 for option #2. Its ok to fetch help message from API server but a drawback is help message is supposed to work generally even if the actual services are not running. Thoughts? Regards, Madhuri -Original Message- From: taget [mailto:qiaoliy...@gmail.com] Sent: Thursday, May 12,

Re: [openstack-dev] Easing contributions to central documentation

Hi All, One reply inline: On 11/05/2016, 7:33 AM, "Lana Brindley" wrote: >On 10/05/16 20:08, Julien Danjou wrote: >> On Mon, May 09 2016, Matt Kassawara wrote: >> >>> So, before developer frustrations drive some or all projects to move >>> their documentation in-tree

Re: [openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the glance-coresec team

+1 :-) -Original Message- From: Nikhil Komawar [mailto:nik.koma...@gmail.com] Sent: Wednesday, May 11, 2016 8:40 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the

[openstack-dev] [zaqar] Zaqar weekly meeting time changed

Hi team, Based on our previous discussion, the weekly meeting time has been changed. The new meeting time is as below. Thanks. time: 18:00 UTC day: Monday irc: openstack-meeting-3 frequency: weekly start_date: 20160516 -- Cheers & Best regards, Fei

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

> -Original Message- > From: Mike Perez [mailto:m...@openstack.org] > Sent: May 11, 2016 23:52 > To: Ildikó Váncsa > Cc: 'D'Angelo, Scott (scott.dang...@hpe.com)'; > 'Walter A. Boring IV'; 'John Griffith > (john.griffi...@gmail.com)';

Re: [openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the glance-coresec team

+1 for Brian On 12/05/16 15:39, Nikhil Komawar wrote: > Hello all, > > I would like to propose adding add Brian to the team. He has been doing > great work on improving the Glance experience for user and operators and > tying the threads with the security aspects of the service. He also > brings

[openstack-dev] [glance] glance-registry deprecation: Request for feedback

Greetings, The Glance team is evaluating the needs and usefulness of the Glance Registry service and this email is a request for feedback from the overall community before the team moves forward with anything. Historically, there have been reasons to create this service. Some deployments use it

[openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the glance-coresec team

Hello all, I would like to propose adding add Brian to the team. He has been doing great work on improving the Glance experience for user and operators and tying the threads with the security aspects of the service. He also brings in good perspective of running large scale glance deployment and

[openstack-dev] [all] [glance] on contributing to projects/programs -- say glance

Hi all, I wanted to share with you that over the last week 5 (iirc) people have reached out to me asking of how they could contribute to Glance and have expressed interest in specific areas. The list of such individuals is longer (around 10) if I count those whom I had a chat with at the summit.

Re: [openstack-dev] [mistral] Promoting Hardik Parekh to core reviewers

Thank you all !!! I will try my best to justify this responsibility :) Thanks and Regards, Hardik Parekh > On May 10, 2016, at 4:34 PM, Lingxian Kong wrote: > > +1 to Hardik :-) > Regards! > --- > Lingxian Kong > > > On Tue, May 10, 2016

Re: [openstack-dev] [glance] Hiatus

Hi Stuart, This is a sad news indeed that you need to shift focus. I do hope that you come back very soon! (soon enough to run for PTL next cycle ;-) ) I do and am sure the entire Glance team appreciates all the effort you have put in the Import work and the great discussions between you Brian,

[openstack-dev] [magnum] Jinja2 for Heat template

Hi, all. Now, I’m trying to implement following bp. * https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips This bp requires to disable/enable “floating ip resource” in heat template dynamically. We have 3 options to implement this. 1. Use “conditions function” *

Re: [openstack-dev] [tc] supporting Go

On Mon, 9 May 2016 14:17:40 -0500 Edward Leafe wrote: > Whenever I hear claims that Python is “too slow for X”, I wonder > what’s so special about X that makes it so much more demanding than, > say, serving up YouTube. In case of Swift, the biggest issue was the scheduler. As

Re: [openstack-dev] [magnum] How to document 'labels'

+1 for #2, to keep help message in magnum API server, since we have an validation list in API Server, see https://review.openstack.org/#/c/312990/5/magnum/api/attr_validator.py@23 . But, if we chose #2 , CLI should add supporting to retrieve help message from API server. On 2016年05月12日

Re: [openstack-dev] [magnum] How to document 'labels'

Hi all, +1 for option #2. Yuanying drafted following blueprint. And I will follow up this. https://blueprints.launchpad.net/magnum/+spec/magnum-api-swagger-support I think, this will be satisfy Tom's comments. regards, Shu Muto

[openstack-dev] [nova][keystone] Austin summit nova/keystone cross-project session recap

On Thursday afternoon we had a nova/keystone cross-project design summit session. The session etherpad with full details is here [1]. This session was mostly about a nova spec [2] to fix a long-standing bug in Nova. We've actually had several duplicate bugs for this issue, which is why we're

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Thanks Josh about your reply. It's helpful. The attempt of this cross project work is to come up with a standard way of implementing quota logic that can be used by different services. Currently, different projects have their individual implementations and there are many learning lessons. The

Re: [openstack-dev] [TripleO][infra] HW upgrade for tripleo CI

On 11 May 2016 at 10:24, Derek Higgins wrote: > Hi All, > I'll be taking down the tripleo cloud today for the hardware > upgrade, The cloud will be take down at about 1PM UTC and I'll start > bringing it back up once dcops have finished installing the new HW. We > should

Re: [openstack-dev] [tc] supporting Go

On Wed, May 11, 2016, at 01:11 PM, Robert Collins wrote: > As a community, we decided long ago to silo our code: Nova and Swift > could have been in one tree, with multiple different artifacts - think > of all the cross-code-base-friction we would not have had if we'd done > that! The cultural

Re: [openstack-dev] [magnum] How to document 'labels'

Heat added a panel in horizon to describe all the resources they have. Not sure you would want to do it the same way, but there is at least one other project that ran into this issue and took a stab at solving it. Might be worth a look. Thanks, Kevin From:

Re: [openstack-dev] [tc] supporting Go

On Wed, May 11, 2016, at 01:11 PM, Robert Collins wrote: > So, given that that is the model - why is language part of it? Yes, > there are minimum overheads to having a given language in CI - we need > to be able to do robust reliable builds [or accept periodic downtime > when the internet is not

[openstack-dev] [app-catalog] App Catalog IRC meeting Thursday May 12th

Join us Thursday for our weekly meeting, scheduled for May 12th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog It might be a short

Re: [openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

Anne Augustina Note. Sorry for duplicate posting for openstack-docs. Since I failed to post to openstack-dev. Thank you for description and help. I will clean up launchpad api-site within this week at first. Since just around 150 issues and many issues are tagged it already. I

Re: [openstack-dev] [tc] supporting Go

/me puts on his Operator hat. Operators do care about being able to debug issues with the stuff they have to deploy/manage. One of our complains about Java (and probably Erlang.. Not sure about go): In addition to the standard C like issues you hit, file descriptor limits, etc, the

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

So it was under my belief that at its current stage that this library would start off on its own, and not initially start of (just yet) in oslo (as I think the oslo group wants to not be the blocker/requirement for a library being a successful thing + the cost of it being in oslo may not be

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Since the review [1] to create the repo is up now, I have one question: This is a cross-project effort, so what is it's governance? The review stated it will be an independent project outside of the big tent - but seeing that this should become a common part for core projects and specific to

[openstack-dev] [Neutron][networking-sfc] meeting topics for 5/12/2016 networking-sfc project IRC meeting

Hi everyone, Here are some topics I have for this week's project meeting discussion(The meeting time is not changed, still UTC 1700 Thursday). Feel free to add more. You can also find the meeting topics in the project wiki page.

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

Can you move this documentation to the networking guide where operators/users can locate it more easily? On Wed, May 11, 2016 at 3:26 PM, Sukhdev Kapur wrote: > Hi Matt, > > If you look through the documentation, there are steps described to > install L2GW outside of

[openstack-dev] [ironic][nova][neutron][qa] Injecting code into grenade resource create phase

I've ran into a bit of a wedge working on ironic grenade tests. In a normal dsvm run, the ironic setup taps the control plane into the tenant network (as that's how it's currently intended to be deployed). That code is here[0]. However, in a grenade run, during the resource create phase, a new

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

On 14:38 May 11, Ildikó Váncsa wrote: > Hi All, > > We will continue the meeting series about the Cinder-Nova interaction changes > mostly from multiattach perspective. We have a new meeting slot, which is > __Thursday, 1700UTC__ on the #openstack-meeting-cp channel. > > Related etherpad:

Re: [openstack-dev] Wiki

On 05/11/2016 02:06 PM, Paul Belanger wrote: > On Wed, May 11, 2016 at 05:51:41PM +, Jeremy Stanley wrote: >> On 2016-05-11 10:04:26 -0400 (-0400), Sean Dague wrote: >> [...] >>> Before deciding that it's unsurmountable, maybe giving delete >>> permissions to a larger set of contributors might

Re: [openstack-dev] [third-party] Are you getting value from the 8:00 utc Tuesday meeting?

On 05/11/2016 02:22 PM, Mike Perez wrote: > On 14:30 May 10, Anita Kuno wrote: >> I've been chairing this meeting for about 3 releases now and in this >> last release it has mostly been myself and lennyb, who also attends the >> Monday 15:00 utc third-party meeting that I chair. >> >> Are you

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

Yes, dnsmasq is there as a simple solution for people that didn't want a separate DNS server specified in their subnet. Can you just enable DHCP on the subnet? Even though your containers don't use it for addressing, it will still work for resolving DNS. (it doesn't answer anonymous DHCP queries

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

Hi Matt, If you look through the documentation, there are steps described to install L2GW outside of devstack. -Sukhdev On Wed, May 11, 2016 at 1:54 PM, Matt Kassawara wrote: > Do you have any examples of how to implement L2GW outside of DevStack? > Operators do not

Re: [openstack-dev] [requirements] Bootstrapping new team for Requirements.

> That works for me. I'd prefer that meeting earlier in the week so perhaps > a UTC 11:00 Tuesday would be a good time to use until DST changes and then we > can re check based on who is active. Works for me. thanks for the writeup in the etherpad, that was very helpful. Lets meet on

Re: [openstack-dev] [neutron] Seeing db lockout issues in neutron add_router_interface

Thanks Kevin. Will take a look at the example. Thanks, Divya On Tue, May 10, 2016 at 11:41 PM, Kevin Benton wrote: > Unfortunately we didn't switch to the new sql driver until liberty so that > probably wouldn't be a safe switch in Kilo. > > Adding a retry will help, but

Re: [openstack-dev] [nova] api-ref sprint Wed status

On 05/11/2016 09:06 AM, Sean Dague wrote: > On 05/09/2016 08:23 AM, Sean Dague wrote: >> There is a lot of work to be done to get the api-ref into a final state. >> >> Review / fix existing patches - >> https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open >> shows

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

Do you have any examples of how to implement L2GW outside of DevStack? Operators do not deploy on DevStack. On Wed, May 11, 2016 at 2:47 PM, Sukhdev Kapur wrote: > Hi Matt, > > > Here is the wiki - https://wiki.openstack.org/wiki/Neutron/L2-GW > > This should provide you

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

Hi Matt, Here is the wiki - https://wiki.openstack.org/wiki/Neutron/L2-GW This should provide you all the information that you need. -Sukhdev On Wed, May 11, 2016 at 1:14 PM, Matt Kassawara wrote: > Can you point me to the documentation? > > On Wed, May 11, 2016 at

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/11/2016 12:37:40 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" , "OpenStack > Development Mailing List"

Re: [openstack-dev] [tc] supporting Go

On 11 May 2016, at 13:11, Robert Collins wrote: > > So, given that that is the model - why is language part of it? Yes, > there are minimum overheads to having a given language in CI - we need > to be able to do robust reliable builds [or accept periodic downtime > when the internet is not

Re: [openstack-dev] [tc] supporting Go

On 2016-05-12 08:11:46 +1200 (+1200), Robert Collins wrote: [...] > Right now we support Python, Java, Javascript, Ruby in CI (as I > understand it - infra focused folk please jump in here :)). [...] We also support boatloads of shell script! ;) -- Jeremy Stanley

Re: [openstack-dev] [OpenStack-Infra] [infra] Jobs failing : "No matching distribution found for "

On 2016-05-11 21:55:28 +1000 (+1000), Joshua Hesketh wrote: [...] > Once fixed properly we should undo the workaround so that our > mirror matches pypi. Donald's bandersnatch fix has merged and is now available in an updated release, but as James Blair pointed out in IRC we're currently running a

Re: [openstack-dev] [neutron][devstack] State of the refactor

More updates: https://review.openstack.org/#/q/status:open+project:openstack-dev/devstack+branch:master+topic:neutron-refactor Has the fixes for things I screwed up. Basically it looks like just the _configure_neutron_l3_agent got clobbered which could have broken people using neutron-legacy.

Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

Can you point me to the documentation? On Wed, May 11, 2016 at 2:05 PM, Sukhdev Kapur wrote: > > Folks, > > I am happy to announce that Mitaka release for L2 Gateway is released and > now available at https://pypi.python.org/pypi/networking-l2gw. > > You can install it

Re: [openstack-dev] [tc] supporting Go

I'm going to try arguing the pro case. The big tent has us bringing any *team* that want to work the way we do: in the open, collaboratively, in concert with other teams, into OpenStacks community. Why are we using implementation language as a gate here? I assert that most deployers don't

Re: [openstack-dev] [Infra] Newton Summit Infra Sessions Recap

On 2016-05-10 19:00:35 + (+), Jeremy Stanley wrote: [...] > Wiki Upgrades > - [...] > I'll be starting a thread on the openst...@lists.openstack.org > mailing list in the next few days to cover the situation in greater > detail and get the community-facing discussion going for

[openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

Folks, I am happy to announce that Mitaka release for L2 Gateway is released and now available at https://pypi.python.org/pypi/networking-l2gw. You can install it by using "pip install networking-l2gw" This release has several enhancements and fixes for issues discovered in liberty release.

Re: [openstack-dev] [Infra] Newton Summit Infra Sessions Recap

On 2016-05-11 12:27:13 -0700 (-0700), Elizabeth K. Joseph wrote: > Thanks for taking time to write these up for the list. As per my own > tradition, I've also written a blog post giving an overview of > Infrastructure sessions, according to my own recollection: >

Re: [openstack-dev] [tc] supporting Go

On 12 May 2016 at 02:35, Brant Knudson wrote: > > I'd be worried about bringing in a language that doesn't integrate well with > Python, since I'd expect the normal route would be to take advantage of as > much of the existing code as we have and only replace those parts that need >

Re: [openstack-dev] [tc] supporting Go

Jim Rollenhagen writes: On Wed, May 11, 2016 at 03:36:09PM +0200, Thomas Goirand wrote: On 05/11/2016 02:41 PM, Jim Rollenhagen wrote: >> Installing from $language manager instead of distro >> packages, be it in containers or not, will almost always >> make you download random blobs from

[openstack-dev] [magnum] How to document 'labels'

Hi all, This is a continued discussion from the last team meeting. For recap, 'labels' is a property in baymodel and is used by users to input additional key-pair pairs to configure the bay. In the last team meeting, we discussed what is the best way to document 'labels'. In general, I heard

Re: [openstack-dev] [neutron][devstack] State of the refactor

I'm seeing some mistakes I made when moving over the contents of neutron-legacy that were l3 related into the new file. It didn't trigger any failures in the gate, but it might impact some developer machines or third party systems. I'm putting together patches, but also considering reverting

Re: [openstack-dev] [tc] supporting Go

Flavio Percoco writes: On 11/05/16 09:47 -0500, Dean Troyer wrote: On Tue, May 10, 2016 at 5:54 PM, Flavio Percoco wrote: [language mixing bits were here] The above is my main concern with this proposal. I've mentioned this in the upstream review and I'm glad to

Re: [openstack-dev] [cross-project] The Future of Meetings

On 16:11 May 10, Matt Riedemann wrote: > On 5/9/2016 11:30 PM, Mike Perez wrote: > >Hey all, > > > >When we first discussed the future of cross-project meetings at the Tokyo > >summit, we walked out with the idea of beginning to have ad-hoc meetings > >instead of one big meeting with all big tent

Re: [openstack-dev] [tc] supporting Go

On Wed, May 11, 2016, at 03:24 AM, Thierry Carrez wrote: > > That said I know that the Swift team spent a lot of time in the past 6 > years optimizing their Python code, so I'm not sure we can generalize > this "everything to do with the algorithms" analysis to them ? > I agree. The swift

Re: [openstack-dev] [tc] supporting Go

On 05/11/2016 03:23 PM, Samuel Merritt wrote: > On 5/11/16 7:09 AM, Thomas Goirand wrote: >> On 05/10/2016 09:56 PM, Samuel Merritt wrote: >>> On 5/9/16 5:21 PM, Robert Collins wrote: On 10 May 2016 at 10:54, John Dickinson wrote: > On 9 May 2016, at 13:16, Gregory Haynes

Re: [openstack-dev] [Infra] Newton Summit Infra Sessions Recap

On Tue, May 10, 2016 at 12:00 PM, Jeremy Stanley wrote: > That concludes my recollection of these sessions over the course of > the week--thanks for reading this far--feel free to follow up (on > the openstack-dev ML please) with any corrections/additions! Thanks for taking

Re: [openstack-dev] [tc] supporting Go

On 5/11/16 7:09 AM, Thomas Goirand wrote: On 05/10/2016 09:56 PM, Samuel Merritt wrote: On 5/9/16 5:21 PM, Robert Collins wrote: On 10 May 2016 at 10:54, John Dickinson wrote: On 9 May 2016, at 13:16, Gregory Haynes wrote: This is a bit of an aside but I am sure others are

[openstack-dev] [javascript] [infra] NPM Mirrors (IMPORTANT)

Hello everyone! We've recently added NPM mirrors to our infrastructure, and are about to turn them on. Before that happens, however, we'd like to get a sanity check from impacted projects to make sure that we don't wedge your gate. If you are in charge of a project that invokes `npm install`

[openstack-dev] Trove 2016-05-11 weekly meeting notes

Here are the notes from today's Trove weekly meeting: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-05-11-18.01.html Action Items: [amrith] update infra specs to point to new BP and WF +0: Done [tellesnobrega] abandon spec on CEPH (https://review.openstack.org/#/c/256057/):

Re: [openstack-dev] [neutron][devstack] State of the refactor

On 05/11/2016 02:48 PM, Sean M. Collins wrote: > A quick update, https://review.openstack.org/168438 has landed. > > There is a lot of work that needs to be done, Armando and I spoke > yesterday about some of the hooks that are present in neutron-legacy > that both in-tree and out-of-tree

Re: [openstack-dev] [Neutron] Stale documentation on docs.o.o

Thank you. Carl On Wed, May 11, 2016 at 11:44 AM, Andreas Jaeger wrote: > On 05/11/2016 07:15 PM, Carl Baldwin wrote: >> Greetings all, >> >> This document [1] was superseded by this one [2] a while ago. It >> looks like the source for [1] no longer exists but the web server >>

Re: [openstack-dev] [neutron][devstack] State of the refactor

A quick update, https://review.openstack.org/168438 has landed. There is a lot of work that needs to be done, Armando and I spoke yesterday about some of the hooks that are present in neutron-legacy that both in-tree and out-of-tree consumers rely on being called. Doing a quick git grep - we

Re: [openstack-dev] [puppet] magnum module - fixes/improvements for Mitaka release

> -Original Message- > From: Emilien Macchi [mailto:emil...@redhat.com] > Sent: May-11-16 9:44 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [puppet] magnum module - > fixes/improvements for Mitaka release > > On Wed, May 11, 2016

Re: [openstack-dev] Wiki

On 2016-05-11 14:01:37 -0400 (-0400), Sean Dague wrote: > Well, part of the reason for the wiki over etherpads is that it is > findable in google. [...] Yep, also if we somehow found a way to get them to index our etherpads, those would be overrun with spam in short order. This was the case with

Re: [openstack-dev] [third-party] Are you getting value from the 8:00 utc Tuesday meeting?

On 14:30 May 10, Anita Kuno wrote: > I've been chairing this meeting for about 3 releases now and in this > last release it has mostly been myself and lennyb, who also attends the > Monday 15:00 utc third-party meeting that I chair. > > Are you getting value from the Tuesday 8:00 utc third-party

Re: [openstack-dev] [pbr] New release?

Excerpts from Julien Danjou's message of 2016-05-11 17:03:03 +0200: > Hey there, > > Would it be possible to push a new release out? > > I'd like to enjoy the fix for the --port option from Thomas for WSGI > scripts. > > Cheers, pbr is an Oslo library, so you should bring it up with the Oslo

Re: [openstack-dev] Wiki

On Wed, May 11, 2016 at 05:51:41PM +, Jeremy Stanley wrote: > On 2016-05-11 10:04:26 -0400 (-0400), Sean Dague wrote: > [...] > > Before deciding that it's unsurmountable, maybe giving delete > > permissions to a larger set of contributors might be a good idea. > [...] > > I have no objection

Re: [openstack-dev] Wiki

On 05/11/2016 01:51 PM, Jeremy Stanley wrote: > On 2016-05-11 10:04:26 -0400 (-0400), Sean Dague wrote: > [...] >> Before deciding that it's unsurmountable, maybe giving delete >> permissions to a larger set of contributors might be a good idea. > [...] > > I have no objection to granting delete

Re: [openstack-dev] [neutron] [designate] multi-tenancy in Neutron's DNS integration

On 11/05/2016 18:45, Mike Spreitzer wrote: >> On Tue, May 10, 2016 at 11:28 AM, Kevin Benton wrote: >> neutron subnet-show with the UUID of the subnet they have a port on >> will tell you. >> >> On Tue, May 10, 2016 at 6:40 AM, Mike Spreitzer > wrote: >>

[openstack-dev] [heat] RPC messaging issue and convergence

Hi, I have confirmed that the issue related to locally queueing of resource requests, which I highlighted at the design summit, exists currently. I have also confirmed that the issue is solved in oslo.messaging version 5.0.0. The issue is with oslo messaging library below version 5.0.0. The

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/11/2016 12:37:40 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" , "OpenStack > Development Mailing List"

Re: [openstack-dev] [Neutron] Stale documentation on docs.o.o

On 05/11/2016 07:15 PM, Carl Baldwin wrote: > Greetings all, > > This document [1] was superseded by this one [2] a while ago. It > looks like the source for [1] no longer exists but the web server > still has a copy that it continues to serve up. At least, that is the > situation as far as I

Re: [openstack-dev] Wiki

On 2016-05-11 10:04:26 -0400 (-0400), Sean Dague wrote: [...] > Before deciding that it's unsurmountable, maybe giving delete > permissions to a larger set of contributors might be a good idea. [...] I have no objection to granting delete (on non-locked articles) to all users immediately if

Re: [openstack-dev] [Neutron] Stale documentation on docs.o.o

All of the documentation on d.o.o suffers from the inability to easily delete files that search engines continue to reference. To delete specific files, I recommend opening a bug in openstack-manuals and someone on the documentation team (or infra?) can handle it. On Wed, May 11, 2016 at 11:15

Re: [openstack-dev] [tc] supporting Go

On Wed, May 11, 2016, at 05:09 AM, Hayes, Graham wrote: > On 10/05/2016 23:28, Gregory Haynes wrote: > > > > OK, I'll bite. > > > > I had a look at the code and there's a *ton* of low hanging fruit. I > > decided to hack in some fixes or emulation of fixes to see whether I > > could get any major

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/11/2016 12:06:55 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" , "OpenStack > Development Mailing List"

[openstack-dev] [Neutron] Stale documentation on docs.o.o

Greetings all, This document [1] was superseded by this one [2] a while ago. It looks like the source for [1] no longer exists but the web server still has a copy that it continues to serve up. At least, that is the situation as far as I can tell. Can anyone help here? Do we need to add

Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons

Cool. Just let me know if there is anything I can do. Have a nice day. :) Anthony. On Wed, May 11, 2016 at 9:05 AM, Hongbin Lu wrote: > Spyros, > > > > Thanks for taking this role. I have added your name to the Cross Project > Liaison wiki [1]. For Anthony and other

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Looks good apart from: networking_ovn/common/extensions.py There should be no changes to that file, I removed them as they are from an older prototype. Regards John From: Ryan Moats > Date: Wednesday, May 11, 2016 at 9:59 AM To: John

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/11/2016 11:30:07 AM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "disc...@openvswitch.org" , "OpenStack > Development Mailing List"

Re: [openstack-dev] [tc] supporting Go

On 11/05/16 09:47 -0500, Dean Troyer wrote: On Tue, May 10, 2016 at 5:54 PM, Flavio Percoco wrote: [language mixing bits were here] The above is my main concern with this proposal. I've mentioned this in the upstream review and I'm glad to have found it here as well.

Re: [openstack-dev] [TripleO][infra][puppet] HW upgrade for tripleo CI

On 2016-05-11 08:49:39 -0400 (-0400), Emilien Macchi wrote: [...] > TripleO Jobs are going to be red from Today 1 pm UTC until > tomorrow hopefully. [...] Note that the _probable_ outcome is that jobs will simply queue in Zuul, and then the TripleO test cloud will begin to churn through the

Re: [openstack-dev] [tc] supporting Go

On 11/05/16 12:09 +, Hayes, Graham wrote: On 10/05/2016 23:28, Gregory Haynes wrote: On Tue, May 10, 2016, at 11:10 AM, Hayes, Graham wrote: On 10/05/2016 01:01, Gregory Haynes wrote: On Mon, May 9, 2016, at 03:54 PM, John Dickinson wrote: On 9 May 2016, at 13:16, Gregory Haynes wrote:

Re: [openstack-dev] [requirements] Bootstrapping new team for Requirements.

Thanks Doug, Folks, Let's use #openstack-requirements channel -- Dims On Tue, May 10, 2016 at 11:46 AM, Doug Hellmann wrote: > Excerpts from Davanum Srinivas (dims)'s message of 2016-05-07 11:02:23 -0400: >> Dirk, Haïkel, Igor, Alan, Tony, Ghe, >> >> Please see brain

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Apologies for missing the _init_.py files – removed them and remerged. When I do a compare from my repo to main I see three files changed (which I think is correct): networking_ovn/ovsdb/commands.py networking_ovn/ovsdb/impl_idl_ovn.py networking_ovn/ovsdb/ovn_api.py I could be doing

[openstack-dev] [TripleO] Undercloud Configuration Wizard

Hi all, Just wanted to let everyone know that I've ported the undercloud configuration wizard to be a web app so it can be used by people without PyQt on their desktop. I've written a blog post about it here: http://blog.nemebean.com/content/undercloud-configuration-wizard and the tool itself is

Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons

Spyros, Thanks for taking this role. I have added your name to the Cross Project Liaison wiki [1]. For Anthony and other candidates, this role requires a basic understanding of Magnum and OpenStack documentation. I assigned this role to Spyros since his past work already showed his

Re: [openstack-dev] [nova][newton] Austin summit nova/newton cross-project session recap

On Sun, May 1, 2016 at 7:01 PM, Matt Riedemann wrote: > On Wednesday morning the Nova and Neutron teams got together for a design > summit session. The full etherpad is here [1]. > > We talked through three major items. > > 1. Neutron routed networks. > > Carl Baldwin

Re: [openstack-dev] [tc] supporting Go

On 2016-05-11 10:09:31 -0400 (-0400), Jim Rollenhagen wrote: [...] > Well, if we're talking about python, it all comes from PyPI. [...] That's not entirely true. Some projects listed on PyPI are simply index links to packages hosted elsewhere on the Web and that used to be a _lot_ more common

Re: [openstack-dev] [ironic] [OpenstackClient] deprecations

On Wed, May 11, 2016 at 02:35:12PM +, Loo, Ruby wrote: > Hi ironic’ers, > > I thought we had decided that we would follow the standard deprecation > process [1], but I see that ironic isn’t tagged with that [2]. > Although we have documented guidelines wrt deprecations [3]. But I am > not

Re: [openstack-dev] Wiki

>From the perspective of contributing documentation and providing support (mostly in #openstack) to a variety of consumers, the wiki tends to provide yet another location for varying levels of content without a specific audience and questionable relevance due to lack of maintenance. I find a

[openstack-dev] Collecting our wiki use cases

(posting as separate thread upon request) Hi everyone, At the beginning of OpenStack we have been using wiki.openstack.org as our default community lightweight information publication platform. There were/are lots of things in there, reference information that a couple people struggled to

[openstack-dev] [magnum][higgins][all] The first Higgins team meeting

Hi all, I am happy to announce that a new project (Higgins [1][2]) was created for providing container service on OpenStack. The Higgins team will hold the first team meeting at this Friday 0030 UTC [3]. At the first meeting, we plan to collect requirements from interested individuals and

Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons

Hi, since I work on the install docs (btw, I'll push in our repo in the next hour), I could do it. Spyros On 11 May 2016 at 00:35, Anthony Chow wrote: > HongBin, > > What is the skill requirement or credential for this documentation liaison > role? I am interested in

Re: [openstack-dev] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

On Wed, May 11, 2016 at 8:12 AM, Atsushi SAKAI wrote: > Anne > Augustina > > Thank you for description and help. > > I will clean up launchpad api-site within this week at first. > Since just around 150 issues and many issues are tagged it already. > I can manually

[openstack-dev] [pbr] New release?

Hey there, Would it be possible to push a new release out? I'd like to enjoy the fix for the --port option from Thomas for WSGI scripts. Cheers, -- Julien Danjou // Free Software hacker // https://julien.danjou.info signature.asc Description: PGP signature

[openstack-dev] [release][oslo] tooz 1.36.0 release (newton)

We are psyched to announce the release of: tooz 1.36.0: Coordination library for distributed systems. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/tooz With package available at: https://pypi.python.org/pypi/tooz

  1   2   >