Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

Hey Tony and all, I'm happy to take care of these retirements. However I probably can't get to it until Tuesday next week. So assuming no other infra root beats me to it I'll look at it then. Cheers, Josh On Thu, Dec 8, 2016 at 3:58 PM, Tony Breeds wrote: > On Tue,

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

On 5 December 2016 at 07:59, Bence Romsics wrote: > Hi, > > I measured how the new trunk API scales with lots of subports. You can > find the results here: > > https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling > > Hope you find it useful. There

Re: [openstack-dev] [heat] A question on creating Manila Share

Hi zengchen, Yeah, the constraint looks incorrect. Not sure if we got it wrong or manila has changed it afterwards. It would be good raise a bug/propose a fix. On Fri, Dec 9, 2016 at 8:26 AM, zengchen wrote: > Hi, Heat stackers: > May I ask a question about creating

Re: [openstack-dev] [heat] A question on creating Manila Share

Hi Zeng Geat observation! I think we need to fix it and make ACCESS_TYPE up to date. Feel free to file a bug and send out the fix patch or just file a bug if you would like others to fix it. Cheers :) __ OpenStack Development

Re: [openstack-dev] [TripleO] Network Configuration in TripleO UI

On 12/08/2016 05:28 PM, Dan Sneddon wrote: > On 12/08/2016 06:05 AM, Jiri Tomasek wrote: > > Hi all, > > > > I've been investigating how to implement TripleO network configuration > > in TripleO UI. Based on my findings I'd like to propose a solution. > > > > tl;dr proposal: Slightly refactor

Re: [openstack-dev] [Zun] Propose a change of Zun core membership

Thanks Hongbin and Zun Team, I will try my best to meet Zun team's expectations. Thanks, Pradeep Singh On Fri, Dec 9, 2016 at 12:20 AM, Hongbin Lu wrote: > Hi all, > > Thanks for the feedback. This proposal was approved. Pradeep has been > added to the core team. > >

Re: [openstack-dev] [Congress] Congress Dashboard and Containers

Hi Tim, Aimee, Yes, ideally only congress_dashboard is required on the same server as horizon for horizon to discover the plugin, but right now congress_dashboard is also part of congress repo, so congress needs to be installed on the same server. I'm thinking for a while to move the repo to

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Dec. 9 2016

1) Roll Call 2) Shanghai Telecom Support (Storage & Bare Metal) 3) OPNFV: Daisy CI Progress 4) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] will the release schedule be changed because of PTG?

Fred, See the diagram in the blog post from Thierry: https://ttx.re/splitting-out-design-summit.html Thanks, Dims On Thu, Dec 8, 2016 at 10:10 PM, Liyongle (Fred) wrote: > As we know, OpenStack were released in April and October. Because of the > first PTG, Ocata will be

[openstack-dev] will the release schedule be changed because of PTG?

As we know, OpenStack were released in April and October. Because of the first PTG, Ocata will be released in Feb. I checked [1] and it seems that in the future OpenStack will be released in Feb. and Aug. Is my understanding correct? If not, will it be still in April and October in the future?

[openstack-dev] [heat] A question on creating Manila Share

Hi, Heat stackers: May I ask a question about creating Manila Share. I see Heat define some constraints for property schema 'ACCESS_TYPE' at heat.engine.resources.openstack.manila.share.properties_schema[ACCESS_RULES]. I copy the codes as bellow. The allowed values for 'ACCESS_TYPE' are

Re: [openstack-dev] [neutron] broken rally gate

On 8 December 2016 at 16:40, Armando M. wrote: > Hi folks > > Chasing down why [1] accidentally broke rally. Please do not recheck, and > the failure is persistent. > > Thanks, > Armando > > [1] https://review.openstack.org/#/c/408020 >

[openstack-dev] [neutron] broken rally gate

Hi folks Chasing down why [1] accidentally broke rally. Please do not recheck, and the failure is persistent. Thanks, Armando [1] https://review.openstack.org/#/c/408020 __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [TripleO] Network Configuration in TripleO UI

On 12/08/2016 06:05 AM, Jiri Tomasek wrote: > Hi all, > > I've been investigating how to implement TripleO network configuration > in TripleO UI. Based on my findings I'd like to propose a solution. > > tl;dr proposal: Slightly refactor Network environment files to match > GUI usage, Use Jinja

Re: [openstack-dev] [all] stable/mitaka CI failures (ImportError: No module named vine.five)

On 2016-12-08 16:53:16 -0600 (-0600), Jason Johnson wrote: [...] > Further reading: > https://pip.pypa.io/en/stable/user_guide/#constraints-files Probably comes as no surprise, but Robert implemented that feature for pip specifically because we (the OpenStack community) had been struggling with

[openstack-dev] [cloudkitty] IRC Meeting

Hello Fellow developers A few weeks ago we decided to drop the regular IRC meeting we had for cloudkitty and decided to held some when necessary. The next meeting will be on Monday 12th at 13:00 UTC on #cloudkitty. We'll be discussing the state of the various developments we are doing for

Re: [openstack-dev] [all] stable/mitaka CI failures (ImportError: No module named vine.five)

On Thu, Dec 8, 2016 at 4:27 PM, Matt Riedemann wrote: > On 12/8/2016 4:18 PM, Jason Johnson wrote: > >> >> On Thu, Dec 8, 2016 at 3:48 PM, Matt Riedemann >> > wrote: >> >> On 12/8/2016 1:03 PM, Ian

Re: [openstack-dev] [all] stable/mitaka CI failures (ImportError: No module named vine.five)

On 12/8/2016 4:18 PM, Jason Johnson wrote: On Thu, Dec 8, 2016 at 3:48 PM, Matt Riedemann > wrote: On 12/8/2016 1:03 PM, Ian Cordasco wrote: If your project were using constraints, you would not run into this

Re: [openstack-dev] [all] stable/mitaka CI failures (ImportError: No module named vine.five)

On Thu, Dec 8, 2016 at 3:48 PM, Matt Riedemann wrote: > On 12/8/2016 1:03 PM, Ian Cordasco wrote: > >> >> >> If your project were using constraints, you would not run into this >> problem. >> > > I'd like to stress this point. This was the solution for getting glance

[openstack-dev] [openstack-ansible][security] Need reviewers/testers for new STIG content

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey there, All of the patches for the 236 STIG controls in the RHEL 7 beta STIG are merged or under review in the openstack-ansible-security[0] role! Here's what you need to know: * The original RHEL6 STIG content is still in place. * The

Re: [openstack-dev] [nova] [Openstack-operators] How to expose the compute node local disks to instances

Hi Belmiro, In Cinder there is the "raw disk device" driver that has been used by some for Hadoop and similar applications. That may be something to look at, but with a big warning. That being that it is deprecated in the Ocata release and will be removed in Pike. The reason it is going to be

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On Mon, Nov 7, 2016, at 01:48 PM, Clark Boylan wrote: > Hello everyone, > > The infra team would really like to get the Ubuntu Xenial for testing > transition completed early this cycle. We are planning to switch any > jobs that remain on Ubuntu Trusty but should be on Ubuntu Xenial on > December

Re: [openstack-dev] [Congress] Congress Dashboard and Containers

I wouldn't expect Congress needs to be on the same server as Horizon. Anusha, do you know for sure? Tim On Thu, Dec 8, 2016 at 1:20 PM Aimee Ukasick wrote: > All - we are looking into deploying Congress in its own container, > separate from the container that

Re: [openstack-dev] [all] stable/mitaka CI failures (ImportError: No module named vine.five)

On 12/8/2016 1:03 PM, Ian Cordasco wrote: If your project were using constraints, you would not run into this problem. I'd like to stress this point. This was the solution for getting glance patches to land in stable/liberty today:

[openstack-dev] [Congress] Congress Dashboard and Containers

All - we are looking into deploying Congress in its own container, separate from the container that OpenStack is in. I know which Congress dashboard files need to be copied to Horizon, and from what I can tell, it looks like Congress and Horizon must be running on the same server for the Congress

[openstack-dev] [all] [interop] Name Change: Interop Working Group, formerly known as DefCore Committee

Hello Everyone, As you may have already heard, DefCore Committee is changing its name to Interop Working Group. Why the name change? At the Board of Directors meeting on April 24, 2016 the Board of Directors indicated that as DefCore has evolved it's focus on interoperability and it's working

Re: [openstack-dev] [kolla] balancing core team karma and collecting statements from kolla team.

Jeffrey, I think a better balance among the core reviewer teams for the 3 core reviewer teams we have for our 3 deliverables is warranted as you stated. To clarify my position, I am happy to train individuals on how to manage Launchpad, even one on one for our core reviewers that don’t know

Re: [openstack-dev] [all] stable/mitaka CI failures (ImportError: No module named vine.five)

-Original Message- From: Gary Kotton Reply: OpenStack Development Mailing List (not for usage questions) Date: December 8, 2016 at 12:59:07 To: OpenStack List Subject:  [openstack-dev] [all]

[openstack-dev] [all] stable/mitaka CI failures (ImportError: No module named vine.five)

Hi, Stable/mitaka is broken [1]. Any idea how to resolve this. Do the requiremets need to pin a specific oslo.messaging version? Thanks Gary [1] File "/home/jenkins/workspace/gate-vmware-nsx-python27-db-ubuntu-trusty/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py", line 1305, in

Re: [openstack-dev] [Zun] Propose a change of Zun core membership

Hi all, Thanks for the feedback. This proposal was approved. Pradeep has been added to the core team. Best regards, Hongbin > -Original Message- > From: Sudipta Biswas [mailto:sbisw...@linux.vnet.ibm.com] > Sent: December-04-16 11:29 PM > To: openstack-dev@lists.openstack.org >

[openstack-dev] [nova] [Openstack-operators] How to expose the compute node local disks to instances

Hi, we have a set of disk servers (JBOD) that we would like to integrate into our cloud to run applications like Hadoop and Spark. Using file disks for storage and a huge "/var/lib/nova" is not an option for these use cases so we would like to expose the local drives directly to the VMs as

Re: [openstack-dev] [ironic] unsupported drivers and their future

Hi all, On Thu, Dec 8, 2016 at 6:58 PM, Jim Rollenhagen wrote: > On Wed, Dec 7, 2016 at 1:52 PM, Pavlo Shchelokovskyy < > pshchelokovs...@mirantis.com> wrote: > >> HI all, >> >> we (ironic community) some time ago decided [0] to require third-party CI >> for any driver

Re: [openstack-dev] [ironic] unsupported drivers and their future

On Wed, Dec 7, 2016 at 1:52 PM, Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com> wrote: > HI all, > > we (ironic community) some time ago decided [0] to require third-party CI > for any driver that is present in the main ironic code tree. I'd like to > discuss the state of currently

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, A new guideline merged this week, describing the "not in" operator for query strings, and some clarification of when to use 400 vs 404 is ready for wider review. See below for links to both. Other than that, not a lot going on. If you're aware of a missing,

[openstack-dev] [glance] [stable] Liberty Periodic Failures (Was: [Openstack-stable-maint] Stable check of openstack/glance failed)

This failure is caused by the fact Glance isn't using constraints on stable/liberty. Matt is backporting those changes via: https://review.openstack.org/#/q/topic:liberty-constraints -Original Message- From: A mailing list for the OpenStack Stable Branch test reports.

Re: [openstack-dev] [heat] On allowing null as a parameter default

On 08/12/16 08:40, Steven Hardy wrote: On Mon, Dec 05, 2016 at 04:27:50PM -0500, Zane Bitter wrote: Any parameter in a Heat template that has a default other than None is considered optional, so the user is not required to pass a value. Otherwise, however, the parameter is required and creating

Re: [openstack-dev] [swg][tc] An attempt to clarify/discuss: what exactly is the Stewardship Working Group, anyhow?

Colette Alexander wrote: > [...] > So, what do we do exactly? > [...] Thanks a lot for this thorough introduction ! > [...] > What are the sorts of things you'd like to see tackled? John Garbutt recently proposed that the TC works on defining visions for itself[1] and OpenStack in general[2]

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

No but I will now, ty! -- Brian Stajkowski Manager, Software Development ­ US m: 702.575.7890 irc: ski e: brian.stajkow...@rackspace.com On 12/8/16, 12:06 AM, "Ihar Hrachyshka" wrote: >Do you test with https://review.openstack.org/#/c/271830/ included? Would > >be nice

Re: [openstack-dev] [kolla] balancing core team karma and collecting statements from kolla team.

Right now I try to attack the bug list whenever I get time, admittedly it's not a regular activity though. I actually wasn't aware kolla and kolla-ansible had separate bug trackers, so far I've just been following the kolla one so this is good to know. One issue I have is the fact that a

[openstack-dev] [nova] remote debugging hangs nova-compute

Hi, I've been trying to get nova-compute (devstack, Newton, all-in-one) to work with the remote debugger in eclipse/pydev. (I've also tried pyCharm with the same results.) Following instructions here: http://docs.openstack.org/developer/nova/development.environment.html I see the message in

Re: [openstack-dev] [Openstack] [OpenStack][Release] Migration problem from icehouse to newton

Hi Mohamed, Thanks you. Can you share links with me that explain the version migration procedures? 2016-12-08 14:04 GMT+00:00 Mohammed Naser : > Hi Thierno, > > There is not, the supported upgrade path is going version by version till > the one you want (in your case,

[openstack-dev] [kolla] balancing core team karma and collecting statements from kolla team.

First of all, kolla team != kolla core reviewer members. everyone is welcome to reply this email. Kolla ( including kolla, kolla-ansible and kolla-kubernetes projects ) is using launchpad for bug track and blueprint management as other OpenStack projects. As kolla become more mature, we have more

[openstack-dev] [TripleO] Network Configuration in TripleO UI

Hi all, I've been investigating how to implement TripleO network configuration in TripleO UI. Based on my findings I'd like to propose a solution. tl;dr proposal: Slightly refactor Network environment files to match GUI usage, Use Jinja Templating to generate dynamic parts of the

Re: [openstack-dev] [Openstack] [OpenStack][Release] Migration problem from icehouse to newton

Hi Thierno, There is not, the supported upgrade path is going version by version till the one you want (in your case, Icehouse -> Juno -> Kilo - > Liberty -> Mitaka -> Newton).. Good luck! Mohammed > On Dec 8, 2016, at 8:44 AM, Thierno Diop wrote: > > Hello

[openstack-dev] [OpenStack][Release] Migration problem from icehouse to newton

Hello guys, I have installed the icehouse version of openstack and I would like to migrate to the newton version to exploit the cloudkitty billing component. I would like to know if there is a direct migration procedure from the icehouse version to the newton version. I have documented but I can

Re: [openstack-dev] [heat] On allowing null as a parameter default

On Mon, Dec 05, 2016 at 04:27:50PM -0500, Zane Bitter wrote: > Any parameter in a Heat template that has a default other than None is > considered optional, so the user is not required to pass a value. Otherwise, > however, the parameter is required and creating the stack will fail pretty >

Re: [openstack-dev] [kolla] Kolla-Kubernetes tagging -> on the road to 1.0.0

thanks Steve for making this clear. btw, could we have an expected release date for next minor version? On Thu, Dec 8, 2016 at 10:36 AM, Steven Dake (stdake) wrote: > Hey folks, > > > > Jeffrey delegated to me to determine the tagging structure for > kolla-kubernetes. I was

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On Thu, Dec 01, 2016 at 05:26:31PM -0500, Emilien Macchi wrote: > Team, > > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few > months now. While he's very active in different areas of TripleO, his > reviews and contributions on puppet-tripleo have been very useful. > Alex is

Re: [openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh Integration

On Thu, Dec 08 2016, Weyl, Alexey (Nokia - IL) wrote: > From Vitrages' point of view "manual" the action is not manual because > it is all done automatically. How about "generic"? "custom"? > "external"? Yeah I like generic and external as names too. > I am trying to understand where exactly in

Re: [openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh Integration

Hi Julien, Thank you for your response. > > We are starting to work on the following BP proposal: > > https://review.openstack.org/#/c/408060/ > > > > In this regard, I have two questions: > > 1. What should this new alarm be called? > > Ah naming things, the biggest problem in CS. Well I'd

Re: [openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh Integration

On Wed, Dec 07 2016, Weyl, Alexey (Nokia - IL) wrote: Hi Alexey, > We are starting to work on the following BP proposal: > https://review.openstack.org/#/c/408060/ > > In this regard, I have two questions: > 1. What should this new alarm be called? Ah naming things, the biggest problem in CS.

Re: [openstack-dev] [ironic] unsupported drivers and their future

On 12/07/2016 07:52 PM, Pavlo Shchelokovskyy wrote: HI all, we (ironic community) some time ago decided [0] to require third-party CI for any driver that is present in the main ironic code tree. I'd like to discuss the state of currently unsupported drivers and how to proceed with them. Here

Re: [openstack-dev] [cinder] [ceilometer]

On Thu, Dec 08 2016, Jiong Liu wrote: Hi Jeremy, If I'm not mistaken, there's a new pollster in Ocata that uses the Cinder API to get the metrics now, so I think the volume usage audit is getting useless. > Hello Cinder/Ceilometer community, > > > > Is there any guideline on using

[openstack-dev] [all] Deadline for PTG Travel Support Program

Hi everyone, The PTG Travel Support Program helps contributors that are not otherwise funded to join their team gathering at the Project Teams Gathering. As explained on http://www.openstack.org/ptg#tab_travel , the deadline for applying to the Atlanta PTG travel support program is this week !

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

Le 08/12/2016 02:28, Jay Pipes a écrit : > On 12/07/2016 07:06 PM, Matt Riedemann wrote: >> On 12/7/2016 2:40 AM, Sylvain Bauza wrote: >>> >>> FWIW, I think POST is not that complex and allows us to have room for >>> further request information like traits, without defeating the purpose >>> to

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

Do you test with https://review.openstack.org/#/c/271830/ included? Would be nice to use a setup with the patch included as our new base. Brian Stajkowski wrote: Yes, this actually has to do with the policy check on any list of objects, including ports. The

[openstack-dev] [neutron-lbaas][octavia] New time proposal for weekly meeting

Hi, As some project members are based outside of the US, I’d like to propose time change for the weekly meeting, which will more friendly to non-US based members. Please post your preferences/info in the etherpad below. https://etherpad.openstack.org/p/octavia-weekly-meeting-time

[openstack-dev] [cinder] [ceilometer]

Hello Cinder/Ceilometer community, Is there any guideline on using `cinder-volume-usage-audit` command? Search through cinder/ceilometer logs, I find some messages are sent to ceilometer-collector. How do I check the output of this command in ceilometer? Do you have any suggestion?