[openstack-dev] [neutron][tap-as-a-service] pike branch/release

hi i'll create stable/pike (and probably a release) for tap-as-a-service in this week. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [horizon]when I access my website, there is '500 internal server error'

It looks to me like you're updating dependencies past those that are supported in Ocata. When installing / upgrading packages, you should make sure they are bound by upper-constraints in the global requirements repo. Does horizon work from your AIO *before* you modified it? Rob On 8 Aug 2017

Re: [openstack-dev] [all] New code contributors no longer forced to join the foundation

On 07/08/17 23:28 +, Jeremy Stanley wrote: Due to improvements in the OpenStack Foundation member directory and our technical election tooling, it is no longer necessary to join the foundation as an individual member just to be able to submit changes through Gerrit for official repositories.

Re: [openstack-dev] [all] New code contributors no longer forced to join the foundation

Thanks Jeremy! i know it took a lot of background work/effort by the team to get here. -- Dims On Mon, Aug 7, 2017 at 7:28 PM, Jeremy Stanley wrote: > Due to improvements in the OpenStack Foundation member directory and > our technical election tooling, it is no longer

[openstack-dev] [neutron][vpnaas] pike rc

hi, can anyone with an appropriate permission create a stable/pike and pike rc1 for neutron-vpnaas? stable/pike 11.0.0.0rc1 openstack/neutron-vpnaas 8278615c1f35f98447a3f9692a78ab45e90ee8c6 thank you. __ OpenStack

[openstack-dev] [neutron][networking-l2gw] pike

hi, who is planning to make stable/pike for networking-l2gw? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [all] New code contributors no longer forced to join the foundation

On Tue, Aug 8, 2017 at 4:58 AM, Jeremy Stanley wrote: > Due to improvements in the OpenStack Foundation member directory and > our technical election tooling, it is no longer necessary to join > the foundation as an individual member just to be able to submit > changes through

Re: [openstack-dev] [kolla][kolla-k8s] Installation in ubuntu 14.04

technically, it should work. But this is not tested, at least on kolla CI gate. On Tue, Aug 8, 2017 at 10:13 AM, ESWAR RAO wrote: > Hi All, > > I am trying to install openstack containers using kolla-k8s. > > I am following below link: >

[openstack-dev] [kolla][kolla-k8s] Installation in ubuntu 14.04

Hi All, I am trying to install openstack containers using kolla-k8s. I am following below link: https://docs.openstack.org/kolla-kubernetes/latest/deployment-guide.html# As per link, its only supported/validated for ubuntu 16.04. Please let me know if any version 0.6/0.5.0.4 is supported for

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron][nova] supporting resource extensions with our CLI

Excerpts from Matt Riedemann's message of 2017-08-07 14:33:22 -0500: > On 8/3/2017 1:39 PM, Boden Russell wrote: > > I think we have a gap in our OSC CLI for non-stadium plugin/driver > > projects (neutron plugin projects, nova driver projects) that implement > > RESTful resource API attribute

[openstack-dev] [horizon]when I access my website, there is '500 internal server error'

Hi: the log is here: http://paste.openstack.org/show/617722/ . I install Ocata in centos by all in one,then I copy Ironic-UI plugin to ‘enable’,I update some lib which is Ironic-UI based on,when I restart the httpd server, the error coming. how can I fix it except reinstall the env?

Re: [openstack-dev] [gnocchi][ceilometer] gnocchi-metricd error using redis as coordination

Thanks Along, finally I figure out that this is a bug and fixed by this commit commit e749b60f49a4a3b48cc5da67a797f717dd8cd01d Author: Julien Danjou Date: Tue Jun 20 16:36:14 2017 +0200 utils: use ASCII bytes as member id Tooz actually wants ASCII bytes and not

[openstack-dev] [tripleo] Screencast of the undercloud deploying mariadb

Hey Team, I took the time to record a small screencast[0] showing tripleo undercloud deplying mariadb on kubernetes. It's it's a *PoC*. It's very basic, some things are hard coded, but it highlights 3 things that I believe are critical for TripleO: * Unified configuration management * Re-use of

[openstack-dev] [nova] [docs] Ideal landing page

The integration of all the manual docs, plus all of our native docs trying to get restructured a bit, has left us with a first order mess when it comes to our front page (and the Table of Contents in the sidebar) - https://docs.openstack.org/nova/latest/ I started trying to pull things out of the

Re: [openstack-dev] [nova] placement/resource providers update 29

On Jul 24, 2017, at 5:05 AM, Chris Dent wrote: > > I guess the code that Ed's working on at > >https://review.openstack.org/#/c/484949 > > need to zero out VCPU etc in the extra specs so that the eventual > allocation record is created in 484935 is correct? That’s

Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

On Mon, Aug 7, 2017 at 9:15 AM, Doug Hellmann wrote: > Kendall & Thierry, what do we need to do to reserve that room if we > can't find space in another team room? Worst case, we can use a slot from TripleO - this topic is also critical to us and I think we can make our

Re: [openstack-dev] [kolla][PTL][elections] Candidacy for Kolla PTL

+1 Rich Wellum On Wed, Aug 2, 2017 at 2:44 PM Michał Jastrzębski wrote: > Hello everyone, > > Once more unto the breach dear friends! I would like to run for PTL again > for > Queens. Pike was very exciting release for Kolla. With strong focus on > Kolla-Kubernetes,

Re: [openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

On Mon, Aug 07, 2017 at 10:34:59AM -0700, Emilien Macchi wrote: > On Mon, Aug 7, 2017 at 9:18 AM, Paul Belanger wrote: > > I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs > > regex for elastic-recheck to start tracking tripleo. What this means,

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron][nova] supporting resource extensions with our CLI

On 8/3/2017 1:39 PM, Boden Russell wrote: I think we have a gap in our OSC CLI for non-stadium plugin/driver projects (neutron plugin projects, nova driver projects) that implement RESTful resource API attribute extensions. For details, go directly to [1]. For a summary read on... For

Re: [openstack-dev] [python-openstacksdk] Status of python-openstacksdk project

On 08/07/2017 11:55 AM, Boden Russell wrote: On 8/4/17 1:26 PM, Boris Pavlovic wrote: That's not going to work for dozens of OpenStack projects. It's just won't scale. Every project should maintain plugin for their project. And it should be enough to say "pip install python-client" that

[openstack-dev] [all][barbican][freezer][horizon][karbor][keystone][mistral][nova][pack-deb][refstack][solum][storlets][swift][tacker][telemetry][watcher][zaqar] Last days for PTL candidate announceme

Hello Everyone :) A quick reminder that we are in the last days for PTL candidate announcements. If you want to stand for PTL, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your candidacy has been submitted to the openstack/election

[openstack-dev] [all] ETSI NFV - OpenStack workshop in Denver

Hi All, I would like to draw your attention to a co-located event during the upcoming OpenStack PTG in Denver. The event will take place in the OpenStack PTG venue (Renaissance Hotel, Denver) at 2pm - 5pm on Tuesday (Sept. 12). The workshop intends to provide a forum to identify and discuss

Re: [openstack-dev] [nova][docs] Concerns with docs migration

On Wed, Aug 2, 2017, at 01:44 PM, Clark Boylan wrote: > On Wed, Aug 2, 2017, at 11:37 AM, Sean Dague wrote: > > On 08/02/2017 12:28 PM, Clark Boylan wrote: > > > On Wed, Aug 2, 2017, at 07:55 AM, Matt Riedemann wrote: > > >> Now that Stephen Finucane is back from enjoying his youth and > > >>

Re: [openstack-dev] [neutron][FFE]Allow DVR for E/W while leaving N/S centralized Edit

Based on feedback from Brian, this patch is close to ready so we should be able to land it. It also proposes a limited risk to existing deployments not using the new agent mode. On Thu, Aug 3, 2017 at 4:26 PM, Swaminathan Vasudevan wrote: > > > > Hi PTL/all, > I would like

Re: [openstack-dev] [neutron][FFE] DVR support for Allowed_address_pair port that are bound to multiple ACTIVE VM ports

I think this is okay. It's been a long standing bug and the patch has is very close to ready. On Thu, Aug 3, 2017 at 4:26 PM, Swaminathan Vasudevan wrote: > > Hi PTL/all,I would like to request an exception for inclusion of >

[openstack-dev] [all] New code contributors no longer forced to join the foundation

Due to improvements in the OpenStack Foundation member directory and our technical election tooling, it is no longer necessary to join the foundation as an individual member just to be able to submit changes through Gerrit for official repositories. You do, however, still eventually need to join

Re: [openstack-dev] [nova][docs] Concerns with docs migration

Excerpts from Clark Boylan's message of 2017-08-07 14:04:33 -0700: > On Wed, Aug 2, 2017, at 01:44 PM, Clark Boylan wrote: > > On Wed, Aug 2, 2017, at 11:37 AM, Sean Dague wrote: > > > On 08/02/2017 12:28 PM, Clark Boylan wrote: > > > > On Wed, Aug 2, 2017, at 07:55 AM, Matt Riedemann wrote: > > >

[openstack-dev] Is shade (and os_client_config) thread safe?

Hi there folks, I'm doing various scans of our clouds here at godaddy and using shade to do some of the calls. Though when I do stuff like the following sometimes it has issues... http://paste.openstack.org/show/617712/ Typically this causes the following error: Traceback (most recent call

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. Docs due to the

Re: [openstack-dev] [all][barbican][freezer][horizon][karbor][keystone][mistral][nova][pack-deb][refstack][solum][storlets][swift][tacker][telemetry][watcher][zaqar] Last days for PTL candidate announ

On 8/7/2017 2:50 PM, Kendall Nelson wrote: Hello Everyone :) A quick reminder that we are in the last days for PTL candidate announcements. If you want to stand for PTL, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your

Re: [openstack-dev] [nova] [docs] Ideal landing page

Excerpts from Sean Dague's message of 2017-08-07 17:07:37 -0400: > The integration of all the manual docs, plus all of our native docs > trying to get restructured a bit, has left us with a first order mess > when it comes to our front page (and the Table of Contents in the > sidebar) -

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

On Mon, Aug 7, 2017 at 4:00 AM, Chris Dent wrote: > Many deployments are several months behind. If _all_ (or even many) > deployments are that far behind, maybe we could consider saving ourselves > some pain? I would agree with this when we get some solid feedback on the

[openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

Hi all, currently our GlanceImageService seems to support several ways of defining a reference to glance image: 1) simple image UUID [0] 2) image UUID prefixed with 'glance://' protocol [1] (well, actually anything starting with 'glance://' and ending with '/') 3) full REST path to the image (as

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

On Mon, Aug 07, 2017 at 07:33:04AM -0500, Dean Troyer wrote: > On Mon, Aug 7, 2017 at 4:00 AM, Chris Dent wrote: > > Many deployments are several months behind. If _all_ (or even many) > > deployments are that far behind, maybe we could consider saving ourselves > > some

Re: [openstack-dev] Tracing (all the places)

> -Original Message- > From: Joshua Harlow [mailto:harlo...@fastmail.com] > Sent: Friday, 04 August, 2017 11:12 > To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org> > Subject: Re: [openstack-dev] Tracing (all the places) > > vin...@vn.fujitsu.com

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

On Fri, 4 Aug 2017, Joshua Harlow wrote: Any idea of who are these deployers? I think I knew once who they might have been but I'm not really sure anymore. Are they still doing this (and can afford doing it)? Why don't we hear more about them? I'd expect that deployers (and there associated

[openstack-dev] [neutron] Functional job failure rate at 100%

Hi all, as per grafana [1] the functional job is broken. Looking at logstash [2] it started happening consistently since 2017-08-03 16:27. I didn't find any particular patch in Neutron that could cause it. The culprit is that ovsdb starts misbehaving [3] and then we retry calls indefinitely. We

[openstack-dev] [elections][shade] PTL candidacy for Queens

I would like to be the PTL of the shade project for another cycle. Over the past few years the shade project has grown from a utility library containing some logic needed by the Infrastructure team and Ansible for interacting with OpenStack clouds to a rich SDK that serves the general needs

[openstack-dev] [neutron] Bug deputy report

Hi all, I was bug deputy for the last week and as I'm not gonna attend meeting today, I'm sending a report here: There weren't that many urgent things reported last week. Here are some bugs that needs more eyes: - https://bugs.launchpad.net/neutron/+bug/1708030 - failure in functional tests,

Re: [openstack-dev] [nova][searchlight] status of an instance on the REST API and in the instance notifications

> -Original Message- > From: Matt Riedemann [mailto:mriede...@gmail.com] > Sent: July 26, 2017 03:23 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova][searchlight] status of an instance on the > REST API and in the instance notifications > > On 7/19/2017 10:54

[openstack-dev] [nova]notification update week 32

Hi, Here is the status update / focus setting mail about notification work for week 32. Bugs [Low] https://bugs.launchpad.net/nova/+bug/1696152 nova notifications use nova-api as binary name instead of nova-osapi_compute Agreed not to change the binary name in the notifications. Instead we

Re: [openstack-dev] [Horizon][Nova] Editing flavor causing instance flavor display error

I’m planning on putting up a patch for this today. My proposal is to add a setting that disables it by default, then add a big warning side on the setting documentation and release notes. Anyone who then explicitly enables it will see the warning. Beyond that, we can deprecate it this cycle,

Re: [openstack-dev] [ceilometer]The principle of restrict the scope of returned events

OK，thanks @gord Look forward to other people's suggestion. On Sat, Aug 5, 2017 at 12:12 AM, gordon chung wrote: > hi, > > i think this is best to ask this on mailing list. to be honest, i do not > work on Panko much anymore. feel free to propose something if it doesn't > meet

Re: [openstack-dev] [gnocchi][ceilometer] gnocchi-metricd error using redis as coordination

>From the log info,It shows that your 'node' maybe is not the valid str. You can show the node name via 'print node' and try to call str(node).encode('utf-8') , identify does it can goes well. 2017-08-05 18:14:19.100 1329257 ERROR cotyledon._utils key = str(node).encode('utf-8') 2017-08-05

[openstack-dev] [kuryr] No weekly IRC meeting today

HI Kuryrs! Since most of the people are on PTO today, we'll skip the weekly IRC meeting and hold it next week. I don't have PTO, so if there's anything you want to discuss, you are very welcome to come to #openstack-kuryr Regards, Toni

Re: [openstack-dev] [tripleo][tripleo-heat-template] how to get interface name from network name in service profile

Thanks for the pointer Saravanan! @Dan, would you mind if I continue the patch work at https://review.openstack.org/#/c/383516/? Cheers! zenghui On Wed, Aug 2, 2017 at 1:33 PM, Saravanan KR wrote: > On Wed, Aug 2, 2017 at 5:21 AM, Zenghui Shi wrote: > > >

Re: [openstack-dev] [requirements][ptls] HELP! Thawing the requirements repo

2017-08-07 11:59 GMT+09:00 Tony Breeds : > Hi All, > So as you all know we've frozen the requirements repo and it will > stay frozen until after all the cycle-with-milestones projects have > stable/pike branches. That's pretty normal. > > The last couple of cycles

[openstack-dev] [Docs][Elections] PTL candidacy for Queens

Hello everyone, I would like to announce my candidacy for Documentation PTL (Queens). First of all, I wish to introduce myself briefly. I have been working on the bugs of openstack-manuals project since the Liberty release. And the most I fixed is the bugs of the Install Guide. In my opinion,

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

On Fri, 4 Aug 2017, Lance Bragstad wrote: On 08/04/2017 03:45 PM, Kristi Nikolla wrote: Therefore the call which now returns a 403 in master, returned a 2xx in Ocata. So we would be fixing something which is broken on master rather than changing a ‘contract’. Good call - with that in mind I

[openstack-dev] [mistral] No meeting today - 08/7/2017

Hi, We decided to cancel today’s Mistral meeting. Thanks Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [ironic][bifrost] Unable to Enroll Inventory

Hi Aimee, I suspect the reason that ansible is owned by root in your setup is that you ran scripts/env-setup.sh using sudo. Could you paste the errors seen when running without sudo? Mark On 3 August 2017 at 23:09, Aimee Ukasick wrote: > Thanks Mark for pointing

Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

Excerpts from Raildo Mascena de Sousa Filho's message of 2017-08-04 19:34:25 +: > Hi all, > > We had a couple of discussions with the Oslo team related to implement > Pluggable drivers for oslo.config[0] and use those feature to implement > support to protect plaintext secret on

[openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

Greetings, I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs regex for elastic-recheck to start tracking tripleo. What this means, is now the elasticRecheck bot will start leaving comments on reviews once it matches a failure in knows about. The goal here is to better

[openstack-dev] [docs] Updating the docs team mission statement

Hi all, With the core docs suite moving from openstack-manuals to individual project repos as per http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html, it's also time to update the docs team mission statement from

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

It sounds like there isn't any major objection to moving forward with a fix and getting this into Pike. I would be inclined to say the discussion here has elevated that priority since missing Pike would expose the 204 -> 403 in an official release. On 08/07/2017 03:54 AM, Chris Dent wrote: > On

Re: [openstack-dev] [neutron] Functional job failure rate at 100%

On Mon, Aug 7, 2017 at 2:52 AM, Jakub Libosvar wrote: > Hi all, > > as per grafana [1] the functional job is broken. Looking at logstash [2] > it started happening consistently since 2017-08-03 16:27. I didn't find > any particular patch in Neutron that could cause it. > >

Re: [openstack-dev] [all][ptl][tc] IMPORTANT upcoming change to technical elections

Hi Clark, Thanks for your support, that works for me :-) Thanks --- 2017-08-07 10:10 GMT-07:00 Clark Boylan : > On Mon, Aug 7, 2017, at 10:01 AM, Ken'ichi Ohmichi wrote: >> Hi >> >> My name is on the nonmembers list and I guess that could be because of >> "Current Member

Re: [openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

On Mon, Aug 7, 2017 at 9:18 AM, Paul Belanger wrote: > I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs > regex for elastic-recheck to start tracking tripleo. What this means, is now > the elasticRecheck bot will start leaving comments on

[openstack-dev] [neutron] RC1 week

Hi neutrinos, Today RC week starts [0] and I have prepared release patch [1]. For the project you're liasion, please review the patch for accuracy and make sure we tag RC1/create a stable branch with the git commit hash you are OK with. Many thanks, Armando [0]

Re: [openstack-dev] [all][ptl][tc] IMPORTANT upcoming change to technical elections

On Mon, Aug 7, 2017, at 10:01 AM, Ken'ichi Ohmichi wrote: > Hi > > My name is on the nonmembers list and I guess that could be because of > "Current Member Level: Speaker", not "Current Member Level: Foundation > Member". > Can I know how to change this member level? > > Thanks > Ken'ichi

[openstack-dev] [neutron] no CI and upgrades meetings this week

Hi, we are in pre-release mode, and some of active participants will not be able to join those meetings, so we will cancel them this week. Thanks, and see you all next week. Ihar __ OpenStack Development Mailing List (not

Re: [openstack-dev] [python-openstacksdk] Status of python-openstacksdk project

On 8/4/17 1:26 PM, Boris Pavlovic wrote: > > That's not going to work for dozens of OpenStack projects. It's just > won't scale. Every project should maintain plugin for their project. And > it should be enough to say "pip install python-client" that > extend the Core OpenStack python client and

Re: [openstack-dev] [all][ptl][tc] IMPORTANT upcoming change to technical elections

Hi My name is on the nonmembers list and I guess that could be because of "Current Member Level: Speaker", not "Current Member Level: Foundation Member". Can I know how to change this member level? Thanks Ken'ichi Ohmichi --- 2017-08-03 8:07 GMT-07:00 Doug Hellmann : >

Re: [openstack-dev] [requirements][ptls] HELP! Thawing the requirements repo

On 6 August 2017 at 23:33, Akihiro Motoki wrote: > 2017-08-07 11:59 GMT+09:00 Tony Breeds : > > Hi All, > > So as you all know we've frozen the requirements repo and it will > > stay frozen until after all the cycle-with-milestones projects have >