[openstack-dev] [QA] Meeting Thursday Mar 9th at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, Mar 9th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_March_9th_2017_.280900_UTC.29

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

Hello, I'd like to start voting to include Duong (duonghq) in Kolla and Kolla-ansible core teams. Voting will be open for 2 weeks (ends at 21st of March). Consider this my +1 vote. Cheers, Michal __ OpenStack Development

Re: [openstack-dev] Disabling glance v1 by default in devstack

Thanks Matt. Yes please, lets all start getting rid of glance v1 in our tests and then on.. On 3/3/17 2:35 PM, Matt Riedemann wrote: > I've got a change proposed to disable glance v1 by default in devstack > for Pike [1]. > > The glance v1 API has been deprecated for awhile now. Nova started >

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

Hi Igor, This is weird. I just did a fresh clone and executed *"tox" *command. I am getting same error. Am I missing anything here ? There is no private change here. Below is the link for entire log. http://paste.openstack.org/show/601870/ On Tue, Mar 7, 2017 at 10:46 PM, Duarte

Re: [openstack-dev] Disabling glance v1 by default in devstack

On Sat, Mar 4, 2017 at 6:01 AM, Andrea Frittoli wrote: > > > On Fri, Mar 3, 2017 at 7:38 PM Matt Riedemann wrote: > >> I've got a change proposed to disable glance v1 by default in devstack >> for Pike [1]. >> >> The glance v1 API has been

Re: [openstack-dev] [telemetry][requirements] ceilometer grenade gate failure

On Wed, Mar 08, 2017 at 03:16:29AM +, gordon chung wrote: > hi, > > this is just an fyi but i've proposed a fix[1] for ceilometer grenade > gate failures we have. > > i've added reasoning in commit message but to re-iterate, > ceilometermiddleware never gets bumped to master

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

On Mon, Mar 6, 2017 at 3:26 AM, Thierry Carrez wrote: > Hello everyone, > > The App Catalog was created early 2015 as a marketplace of pre-packaged > applications that you can deploy using Murano. Initially a demo by > Mirantis, it was converted into an open upstream

[openstack-dev] [kolla][ubuntu][libvirt] Is libvirt 2.5.0 in ubuntu cloud archive ocata repo bust

Kolla deploy ubuntu gate is red now. here is the related bug[0]. libvirt failed to access the console.log file when booting instance. After made some debugging, i got following. # how console.log works nova create a empty console.log with nova:nova ( this is another bug workaround actually[1]),

[openstack-dev] [telemetry][requirements] ceilometer grenade gate failure

hi, this is just an fyi but i've proposed a fix[1] for ceilometer grenade gate failures we have. i've added reasoning in commit message but to re-iterate, ceilometermiddleware never gets bumped to master upper-constraint because it's not in any projects requirements and is conditionally

Re: [openstack-dev] [all] Some information about the Forum at the Summit in Boston

On 廿十七年三月七日 暮 11:26, Matt Riedemann wrote: On 3/7/2017 6:35 AM, Thierry Carrez wrote: Hi everyone, I recently got more information about the space dedicated to the "Forum" at the OpenStack Summit in Boston. We'll have three different types of spaces available. 1/ "Forum" proper There will be

Re: [openstack-dev] [glance] image import sync tomorrow CANCELLED

The Glance image import sync scheduled for 16:00 UTC on 8 March 2017 is postponed until next week. More details at the regular Glance weekly meeting on Thursday. cheers, brian On 3/7/17 9:49 AM, Brian Rosmaita wrote: > Sorry for the late notice, but we'll be having a one-hour image import >

Re: [openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

On 07/03/17 14:34, James Slagle wrote: I've been working on this spec for TripleO: https://review.openstack.org/#/c/431745/ which allows users to selectively disable Heat deployment resources for a given server (or server in the case of a *DeloymentGroup resource). I'm not completely clear on

[openstack-dev] [congress] meeting topics

Hi all, Proposed topics for the next congress irc meeting are tracked in this etherpad: https://etherpad.openstack.org/p/congress-meeting-topics Feel free to add additional topics and/or comment on existing ones. Thanks!

Re: [openstack-dev] A Summary of Atlanta PTG Summaries (!)

On Mon, Mar 6, 2017 at 10:45 PM, Hugh Blemings wrote: > Hiya, > > As has been done for the last few Summits/PTGs in Lwood[1] I've pulled > together a list of the various posts to openstack-dev that summarise things > at the PTG - projects, videos, anecdotes etc. > > The

[openstack-dev] [congress] Pike tasks

Hi all, Based on our discussions at the PTG, I have set up some tasks for Pike. https://bugs.launchpad.net/congress/+bugs?field.tag=pike-goal Feel free to adjust them (text, priority, target, assignee, etc.) or suggest changes as you see fit.

Re: [openstack-dev] [release][tripleo][fuel][kolla][ansible] Ocata Release countdown for R+2 Week, 6-10 March

Doug I have proposed the change for Fuel RC2 [0], but it has W-1 set as I am waiting for the final tests result. If everything goes alright, I will check the Worfklow off and this RC2 can be the cut as the release. [0] https://review.openstack.org/#/c/442775/ On Tue, Mar 7, 2017 at 3:39 AM,

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

On Tue, Mar 07, 2017 at 04:04:55PM +0800, Sam wrote: > Is this? > > https://pypi.python.org/pypi/neutron-lib Make sure you're installing with upper-constratints otehrwise you'll get components that rely on features for newer releases Assuming you're installing with pip something like[1] wget

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

Hi, an update on this. It's about 10days since the original message, and the current status is: - 3 patches merged, 1 approved (recheck) - 5 patches submitted, pending approval - 2 patches with a -1 (need more work) - 7 patches submitted by me today (draft) - review needed Thank you for your

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

Hi Pavlo, thank you for your suggestion. See my comments inline. andrea On Thu, Mar 2, 2017 at 9:19 AM Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com> wrote: > Hi Andrea, > > I am not sure why the new tempest.scenario.manager has to be developed > that way. May I humbly suggest another

Re: [openstack-dev] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

On Mon, Feb 27, 2017 at 11:02 AM, Steven Hardy wrote: > Hi all, > > Over the recent PTG, and previously at the design summit in Barcelona, > we've had some productive cross-project discussions amongst the various > deployment teams. > > It's clear that we share many common

[openstack-dev] [puppet][tripleo][release] puppet module versioning

Ahoy folks, I would like to bring attention to deriving version numbers for puppet modules (for packaging) as part of the release process. Today we uncovered an issue[0] in the way that version numbers were being derived for packages which ultimately broke the TripleO CI upgrade jobs because the

[openstack-dev] [ironic] [neutron] Should the ironic-neutron meeting start back up for pike?

Hey all, So at yesterday's ironic IRC meeting the question of whether or not the ironic neutron integration meeting should start back up. My understanding is that this meeting died down as it became more status oriented. I'm wondering if it'd be worthwhile to kick it off again as 4 of

[openstack-dev] [nova] Question to clarify versioned notifications

While digging through nova code today to compare versioned and unversioned notifications, and reading specs and seeing how seachlight handles nova notifications, I noticed that the unversioned notifications have a "compute." prefix in the name. The versioned notifications do not. It also took

[openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

I've been working on this spec for TripleO: https://review.openstack.org/#/c/431745/ which allows users to selectively disable Heat deployment resources for a given server (or server in the case of a *DeloymentGroup resource). Some of the main use cases in TripleO for such a feature are scaling

Re: [openstack-dev] [Murano] ERROR murano.common.engine [-] yaql.language.exceptions.NoMatchingMethodException: No method "values" for receiver None matches supplied arguments

HOWEVER … for future reference … how do I go about seeing the internal HEAT STACK that Murano builds based on the Murano Application / Packaging ? You can do it be ether 1) Obtaining from the Heat since the stack is accessible and there is an API and UI to get the template 2) Grep

Re: [openstack-dev] [qa][keystone] Tempest will use Keystone v3 API as the default

On 03/07/2017 01:02 PM, Ken'ichi Ohmichi wrote: > Hi, > > This is a kind of notification as the mail title. > > Now QA-team is trying to test most recent stable APIs which are marked > as CURRENT in most components. > The investigation is written on >

[openstack-dev] [Murano] Newton version of Murano fails trying to auto-import a Liberty version of io.murano.applications.zip

I am running a NEWTON version of Murano. When I try to import a package that is using io.murano.applications classes (e.g. SingleServerApplication), it seems to try to auto-import the liberty version of io.murano.applications.zip … and fails. Is this a bug ? Is it suppose to be using NEWTON

[openstack-dev] [qa][keystone] Tempest will use Keystone v3 API as the default

Hi, This is a kind of notification as the mail title. Now QA-team is trying to test most recent stable APIs which are marked as CURRENT in most components. The investigation is written on https://etherpad.openstack.org/p/tempest-api-versions-in-pike On Keystone side, the V3 API is CURRENT and

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

Saverio, Unfortunately back when LBaaS v1 was deprecated (liberty) no automated migration path was developed to move from LBaaS v1 to v2. Some manual database migration scripts were contributed, but you may still have incompatible v1 load balancers that require manual intervention. There is a

Re: [openstack-dev] [Murano] Errors on $.instance.deploy() ... WHEN RUNNING WITHOUT MURANO-AGENT RABBIT

Stan, Success … this worked. thank you very much for your help. Greg. ( got another question but I’ll ask it in another thread ) From: Stan Lagun Date: Monday, March 6, 2017 at 6:10 PM To: "openstack-dev@lists.openstack.org" , Greg

Re: [openstack-dev] [Sahara] Cross Project Liaisons

Great Vitaly. I will update that. On Tue, Mar 7, 2017 at 12:02 PM Vitaly Gridnev wrote: > I can continue to work with Stable branches and with infra, I think. > > Best regards, > Vitaly Gridnev > > > On Mar 7, 2017, at 12:31 AM, Telles Nobrega wrote:

Re: [openstack-dev] [cross-project][nova][cinder][designate][neutron] Common support-matrix.py

On Mon, Mar 6, 2017, at 08:42 PM, Sean Dague wrote: > On 03/06/2017 06:27 PM, Mike Perez wrote: > > On 15:55 Mar 02, Morales, Victor wrote: > >> I got this link[11] from Ankur, apparently Nova and Neutron has already > >> started a common effort > >> > >> [11]

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

Hello Michael, thanks. Using your email I read this page: https://docs.openstack.org/ocata/networking-guide/config-lbaas.html It is still not clear to me if the command: neutron-db-manage --subproject neutron-lbaas upgrade head Will make the necessary database migrations from LBaaS v1 to v2 ?

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

Excerpts from Hayes, Graham's message of 2017-03-07 14:19:02 +: > On 07/03/2017 13:22, Davanum Srinivas wrote: > > Folks, > > > > Anyone interested? https://etherpad.openstack.org/p/go-and-containers > > > > Thanks, > > Dims > > > > The first thing that is required (according to the new

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

Hi Vikash, Please stick to pastebin for complete logs. Check your migration files: FAILED: Contract HEAD file does not match migration timeline head, expected: 48072cb59133 Best regards, Igor. From: Vikash Kumar [mailto:vikash.ku...@oneconvergence.com] Sent: Tuesday, March 7, 2017 5:03 PM To:

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

Complete log: py35 create: /home/vikash/guess_vk/python-dev/networking-sfc/.tox/py35 py35 installdeps: -r/home/vikash/guess_vk/python-dev/networking-sfc/requirements.txt, -r/home/vikash/guess_vk/python-dev/networking-sfc/test-requirements.txt py35 develop-inst:

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

On 03/07/2017 01:34 AM, zengchen wrote: Hi, guys: I find a non-coincidence definition in Oslo, oslo_utils.timeutils.utcnow is defined like this: def utcnow(with_timezone=False): oslo_versonedobjects.fields.DateTimeField is defined like this

Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

Hi Saverio, I think the confusion is coming from neutron/neutron-lbaas/octavia. Neutron-lbaas, prior to the Ocata series was a sub-project of neutron and as such has it's own release notes: https://docs.openstack.org/releasenotes/neutron-lbaas/ As of Ocata, neutron-lbaas is part of the Octavia

[openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

Hi, I was testing patch on master branch, but the test is failing because of the import error. http://paste.openstack.org/show/601794/ -- Regards, Vikash __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On 2017-03-06, 3:46 PM, "Mario Villaplana" wrote: Hi ironic, At the PTG, an issue regarding the default version of the ironic API used in our python-openstackclient plugin was discussed. [0] In short, the issue is that we default to a very old API

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On 07/03/17 12:14, Jim Rollenhagen wrote: I'm also good with the standard deprecation period for this. +1 to "standard deprecation period" - sorry, I'd misremembered what that was. Miles __ OpenStack Development

Re: [openstack-dev] [all] Some information about the Forum at the Summit in Boston

On 3/7/2017 6:35 AM, Thierry Carrez wrote: Hi everyone, I recently got more information about the space dedicated to the "Forum" at the OpenStack Summit in Boston. We'll have three different types of spaces available. 1/ "Forum" proper There will be 3 medium-sized fishbowl rooms for

Re: [openstack-dev] [puppet] puppet-cep beaker test

Hey Stefan, On Tue, Mar 7, 2017 at 7:09 AM, Scheglmann, Stefan wrote: > Hi, > > currently got some problems running the beaker test for the puppet-cep > module. Working on OSX using Vagrant version 1.8.6 and VirtualBox version > 5.1.14. Call is 'BEAKER_destroy=no

[openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

Greetings, The TripleO team would like to initiate a conversation about the possibility of creating a new pipeline in Openstack Infra to allow a set of jobs to run periodically every four hours [2]. The background and context of why such a pipeline is required is as follows. TripleO CI executes

[openstack-dev] [glance] image import sync tomorrow

Sorry for the late notice, but we'll be having a one-hour image import sync via video conference at 16:00 UTC tomorrow (8 March 2017). Watch the ML for more details later today, plus connection info will be posted in #openstack-glance around 15:45 UTC tomorrow. cheers, brian

Re: [openstack-dev] [cross-project][nova][cinder][designate][neutron] Common support-matrix.py

On 01/03/2017 23:53, Mike Perez wrote: > Hey all, > > I kicked off a thread [1] to start talking about approaches with improving > vendor discoveribility by improving our Market Place [2]. In order to improve > our market place, having the projects be more part of the process would allow > the

Re: [openstack-dev] [cinder] Create backup with snapshots

Excellent! Review comments added to your patch. Thanks! Xing From: 王玺源 [wangxiyuan1...@gmail.com] Sent: Monday, March 6, 2017 8:08 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [cinder] Create backup

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

On 07/03/2017 13:22, Davanum Srinivas wrote: > Folks, > > Anyone interested? https://etherpad.openstack.org/p/go-and-containers > > Thanks, > Dims > The first thing that is required (according to the new guidelines) is for there to be a technical reason we need to use go, and cannot use python.

Re: [openstack-dev] [Sahara] Cross Project Liaisons

I can continue to work with Stable branches and with infra, I think. Best regards, Vitaly Gridnev > On Mar 7, 2017, at 12:31 AM, Telles Nobrega wrote: > > Hello Saharans, in the last two or three cycles our team has undergone some > changes and we need to update our

[openstack-dev] [puppet] puppet-cep beaker test

Hi, currently got some problems running the beaker test for the puppet-cep module. Working on OSX using Vagrant version 1.8.6 and VirtualBox version 5.1.14. Call is 'BEAKER_destroy=no BEAKER_debug=1 bundle exec --verbose rspec spec/acceptance’ output in http://pastebin.com/w5ifgrvd Trace:

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

+1 , please add me. /Trinath Get Outlook for iOS From: Davanum Srinivas Sent: Tuesday, March 7, 2017 6:47:49 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [all] Small steps

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

Folks, Anyone interested? https://etherpad.openstack.org/p/go-and-containers Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

On Mon, Mar 06, 2017 at 09:06:18AM -0500, Sean Dague wrote: > On 03/06/2017 08:43 AM, Andreas Jaeger wrote: > > On 2017-03-06 14:03, Sean Dague wrote: > >> I'm trying to understand the implications of > >> https://review.openstack.org/#/c/439500. And the comment in the linked > >> email: > >> >

Re: [openstack-dev] [tricircle]reschedule the weekly meeting

Hello, The patch was merged, the weekly meeting will be held on UTC 1400 ~ UTC 1500 every Wednesday from this week. Best Regards Chaoyi Huang(joehuang) 发件人：黄朝意 收件人：openstack-dev,Morales, Victor,sindhu.dev...@intel.com,prince.a.owusu.boat...@intel.com 时间：2017-03-06 10:07:14 主题:RE:

Re: [openstack-dev] [all] Discount codes for ATCs

On 2017-03-07 09:54:25 +0100 (+0100), j.kl...@cloudbau.de wrote: [...] > So how should i take this? ATCs who can afford to travel to the > PTG receive more discount/funding from the foundation than ATCs > who can not afford to go there? I am pretty sad about the > direction we seem to move with

[openstack-dev] [all] Some information about the Forum at the Summit in Boston

Hi everyone, I recently got more information about the space dedicated to the "Forum" at the OpenStack Summit in Boston. We'll have three different types of spaces available. 1/ "Forum" proper There will be 3 medium-sized fishbowl rooms for cross-community discussions. Topics for the

Re: [openstack-dev] ask.openstack.org site is down!

On 2017-03-07 09:46:12 +0200 (+0200), Abed Abu-Dbai wrote: [blank message body] The site seems up to me at this point, but we've been tracking periodic outages of the service which come some days around the same timeframe you sent your message today. At this point those of us investigating still

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On Tue, Mar 7, 2017 at 6:36 AM, Dmitry Tantsur wrote: > On 03/07/2017 12:32 PM, Miles Gould wrote: > >> On 06/03/17 20:46, Mario Villaplana wrote: >> >>> We also still have yet to decide what a suitable deprecation period is >>> for this change, as far as I'm aware. Please

Re: [openstack-dev] [all] [api] API-WG PTG recap

On Fri, 2017-03-03 at 17:12 +, Chris Dent wrote: > > # Capabilities Discovery > > https://etherpad.openstack.org/p/capabilities-pike > > This began as an effort to refine a proposed guideline for > expressing what a cloud can do: > >  https://review.openstack.org/#/c/386555/ > >

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On 03/07/2017 12:32 PM, Miles Gould wrote: On 06/03/17 20:46, Mario Villaplana wrote: We also still have yet to decide what a suitable deprecation period is for this change, as far as I'm aware. Please respond to this email with any suggestions on the deprecation period. One cycle? I'd go

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On 06/03/17 20:46, Mario Villaplana wrote: We also still have yet to decide what a suitable deprecation period is for this change, as far as I'm aware. Please respond to this email with any suggestions on the deprecation period. One cycle? Miles

Re: [openstack-dev] [Sahara][infra] Jenkins based 3rd party CIs

On Monday, 6 March 2017 20:05:18 CET James E. Blair wrote: > Telles Nobrega writes: > > Hello, > > > > we from Sahara use the compatibility layer with Zuulv2.5 and we are > > wondering if with the change to Zuulv3 this compatibility layer will still > > be maintained. > > If

[openstack-dev] [TripleO][Containers] Containers work tracking, updates and schedule

Greetings, We've been organizing the containers work for TripleO in a more consumable way that will hopefully ease the engagement from different squads and teams in OpenStack. The result of this work is all in this etherpad[0], which we'll use as a central place to keep providing updates and

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

Hi Sam, On Tue, Mar 7, 2017 at 8:05 AM Sam wrote: > Is this? > > https://pypi.python.org/pypi/neutron-lib > Yes, that is one of the ways that neutron-lib is packaged. The 'upstream' is at http://git.openstack.org/cgit/openstack/neutron-lib. Exactly how are you using the

Re: [openstack-dev] [oslo_reports]Does GMR work for uwsgi mode service?

Hi, My understanding is that it's not recommended for WSGI apps to set up custom signal handlers. The reason for that is that a WSGI server (i.e. uwsgi in your case or Apache+mod_wsgi) will most likely have its own handlers for the very same set of signals [1]. There is an alternative way to

Re: [openstack-dev] Stepping down from Neutron roles

Nate, it was a pleasure working with you, you and your team made great contributions to OpenStack and neutron. I'll be very happy if we ever have the chance to work again together. Best regards, and very good luck, my friend. On Tue, Mar 7, 2017 at 4:55 AM, Kevin Benton wrote:

[openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2

Hello, I am upgrading from Mitaka to Newton. our Openstack cloud has in production LBaaSv1. I read all the following release notes: https://docs.openstack.org/releasenotes/neutron/liberty.html https://docs.openstack.org/releasenotes/neutron/mitaka.html

[openstack-dev] [all] Discount codes for ATCs

Hi, i just received a discount code for the Boston summit as an ATC for 300$ (while the ticket price is currently at 600$). As far as i know every ATC who went to the PTG received a discount code of 600$ (also stated here  https://www.openstack.org/summit/boston-2017/faq/). So how should i

Re: [openstack-dev] [picasso] First meeting on 7th of March

Good morning / afternoon / evening, Not sure if you have seen the agenda etherpad posted in the Slack channel - https://etherpad.openstack.org/p/picasso-first-meeting. Might be worth putting our thoughts in there, I already had a few questions about integration with the OpenStack community and

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

Is this? https://pypi.python.org/pypi/neutron-lib 2017-03-07 15:48 GMT+08:00 Sam : > Hi, > > I'm using neutron mitaka version, I found lots of files include this: > "from neutron_lib import exceptions as e" > But I don't find where is neutron_lib, and I got error as