Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

On 8/22/16, 7:24 PM, "duon...@vn.fujitsu.com" wrote: >Hello Kollish, > >I am working on bp ansible-specific-task-become so I need community opinion >about Kolla configuration files owner and permissions. > >For files in "/var/lib/kolla", it's quite clear that the

[openstack-dev] [Fuel] Need Help in adding multiple External networks in Fuel 9.0

Hi All, I think this is right platform to ask my question. i will be thankful if someone can help me in below mentioned use-case. Here is my cloud setup: I have 4 Nodes: Controller Node : 1 No Compute + Ceph Node : 2 No Fuel Node : 1 No My Interfaces are as below : All 4 Nodes has *3 NIC

Re: [openstack-dev] [oslo] support keymirror/valuemirror dict in olso

So question I have is how would this work in python? Any example anywhere? Reason I am asking is that in the example: > search_opts = { > > 'all_tenants': all_tenants, > > 'status': args.status, > > 'filter':filter, > > ……. > > } There is nothing really built-in to python afaik (besides

[openstack-dev] [meghdwar] use case for meghdwar API - Continuing email discussions (CANCELLED-Meeting 24th Aug)

Hi all, CANCELLED: Meeting Wednesday 24th August      (14 Hr-15 Hr UTC )   [7AM-8AM PDT] Follow up on same points with updates aslast meeting. 1 Megdwar Gateway API discussions based on use case Focus is what APIs needed for minimum use case of two cloudlets on two edges running 1 app

[openstack-dev] [charms] tests/charmhelpers in venv and use bindep for bzr

Hi OpenStack Charmers, In prep for a move to a global requirements for OpenStack Charms, I'd like to hit the master branches with a batch of cleanups. This nets -2300 LoC in the example Charm repo. ;-) First, a pre-requisite charm-helpers merge proposal re: missing setup.py entries for

[openstack-dev] [new][horizon] XStatic-smart-table 1.4.13.0 release

We are ecstatic to announce the release of: XStatic-smart-table 1.4.13.0: Installed /home/jenkins/workspace /xstatic-angular-smart-table-announce- release/.eggs/setuptools_scm-1.11.1-py2.7.egg XStatic-smart-table --- smart-table javascript library packaged for setuptools

[openstack-dev] [oslo] support keymirror/valuemirror dict in olso

Hi all, I have an idea about adding common function which creating an dictionary with key equal to its values in OSLO. This is inspired by Key mirror in node js(https://www.npmjs.com/package/keymirror).This is very useful when we create dictionary like below: search_opts = {

[openstack-dev] [nova] Fixing race condition with server groups and affinity policy

According to [1]: """ 1) It's possible to hit a similar race condition for server groups with the "affinity" policy. Suppose we create a new group and then create two instances simultaneously. The scheduler sees an empty group for each, assigns them to different compute nodes, and the policy

[openstack-dev] [kolla] Kolla configuration files owner and permission

Hello Kollish, I am working on bp ansible-specific-task-become so I need community opinion about Kolla configuration files owner and permissions. For files in "/var/lib/kolla", it's quite clear that the owner should be 'root' as currently. For files in "/etc/kolla": After discussion with

[openstack-dev] [Infra] Meeting Tuesday August 23rd at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday August 23rd, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

Re: [openstack-dev] [vitrage] entity graph layout

I'm considering to use Cytoscape.js [1] to improve the layout for entity graph view. Cytoscape.js is a graph theory (a.k.a. network) library for analysis and visualisation which under active maintenance (latest release 2.7.8 on Aug 18, 2016) [2], while the current library d3-dagre [3] is declared

Re: [openstack-dev] [Neutron] Intermittent gate failures

On 22 August 2016 at 09:51, Armando M. wrote: > Neutrinos, > > Since the merge of test [1], a race has surfaced, which leads to failure > as reported in [2]. A number of Neutron's jobs are affected, and even > though the failure is only intermittent, it is particularly bad for

[openstack-dev] [new][openstack] os-client-config 1.20.1 release (newton)

We are grateful to announce the release of: os-client-config 1.20.1: OpenStack Client Configuation Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/os-client-config With package available at:

Re: [openstack-dev] [nova] Hold off on pushing new patches for config option cleanup

Its a shame so many are -2'ed. There is a lot there I could have merged yesterday if it wasn't for that. Michael On Mon, Aug 22, 2016 at 9:00 PM, Sean Dague wrote: > On 08/22/2016 12:10 AM, Michael Still wrote: > >> So, if this is about preserving CI time, then its cool for me

Re: [openstack-dev] Upcoming OpenStackClient 3.0 Release (Monday)

Yes, known bug, try with version 3.0.1 On Aug 22, 2016 3:46 PM, "Andrey Pavlov" wrote: > I have an issue with new openstack client - > > openstack client is installed in new virtual env. it version is 3.0.0 > os-client-config!=1.19.0,>=1.13.1 (from osc-lib>=0.4.0->python- >

Re: [openstack-dev] [tc] persistently single-vendor projects

Let me toss out my perspective (FWIW) from a cloud planning perspective as relates to single-vendor projects: As an established OpenStack and cloud SDN architect and by extension a working owner, I do design work for lots of the companies who read this list. Let me just say that from where I sit,

[openstack-dev] [new][oslo] oslo.messaging 5.9.0 release (newton)

We are glad to announce the release of: oslo.messaging 5.9.0: Oslo Messaging API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.messaging With package available at: https://pypi.python.org/pypi/oslo.messaging

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

Hi All, On Fri, May 13, 2016 at 12:28 PM, Michal Adamczyk wrote: > On Fri, May 13, 2016 at 9:42 AM, Michal Adamczyk > wrote: > >> >> >> On Thu, May 12, 2016 at 2:14 PM, Michal Adamczyk >> wrote: >> >>> >>> On Wed, May 11, 2016

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

What is the logic for that? It's a massive duplication of effort, and it leads to defacto forks and inconsistencies between clouds - exactly what the OpenStack mission is against. Many/most of the clouds actually in production are already out of upstream stable policy. The more convergence we can

Re: [openstack-dev] Upcoming OpenStackClient 3.0 Release (Monday)

I have an issue with new openstack client - openstack client is installed in new virtual env. it version is 3.0.0 os-client-config!=1.19.0,>=1.13.1 (from osc-lib>=0.4.0->python-openstackclient) I set credentials via environment OS_PROJECT_NAME, OS_USERNAME, OS_PASSWORD, OS_AUTH_URL. and

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

In my opinion, we have to be careful about the "supported" label. Saying that third-party tested drivers are community supported implies a commitment that may have not been intended. Personally, I see no problem with leaving everything just as planned. Drivers that are in tree are either tested

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

I’ll have a look. From: Timofei Durakov [mailto:tdura...@mirantis.com] Sent: Monday, August 22, 2016 8:03 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission Hi

[openstack-dev] [ironic] ideas for Ocata summit sessions

Hi, Start getting those ironic juices flowing! We've got an etherpad [1] ready to capture your ideas for the Ocata summit sessions. As discussed in today's meeting [2], in next Monday's ironic meeting [3] we will decide on the number of fishbowl and workroom sessions, and the ideas submitted

[openstack-dev] [ironic] weekly subteam status report

Hi, Here is this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff between 15 Aug 2016 and 22 Aug 2016) - Ironic: 223 bugs (-9) + 211 wishlist items (+12). 26 new (-10), 164 in progress

Re: [openstack-dev] [Openstack-operators] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

Matt, originally this started as an experiment - try to collect information about OpenStack scalability and performance and publish it to the community - and we started this experiment under Rally (OpenStack Benchmarking) umbrella, that's having its documentation space under

[openstack-dev] [puppet] weekly meeting #91

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4 Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160823 Feel free to add topics, and any outstanding bug and patch. See you tomorrow! Thanks,

Re: [openstack-dev] [Openstack-operators] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

Kaustubh, thanks for the comment. Usually if testing scenario require VM booting, its flavor is set in the Rally scenario configuration (e.g. here or here

Re: [openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

Ok, let's keep current (16:00 UTC) time slot for tomorrow meeting, until we'll find a better option. Cheers, Dina On Mon, Aug 22, 2016 at 9:05 AM, Augie Mena III wrote: > Hi Dina/Adrien, > > Not a great slot here in Austin (that would be noon). Would prefer a > 30-minute slot

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

Hi everyone, got a question on that Intel NFV CI: has statistics for stable branches been checked either? I have a patch to stable/liberty [1] that failed on all Intel NFV CI jobs 2 times in a row. Who could help me to figure out the root cause for that? Thanks in advance, Timofey. [1] -

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

I like this approach more than the current "you're in or you're out". +1 --deva On Mon, Aug 22, 2016 at 7:02 AM Vladyslav Drok wrote: > +1 from me then :) > > On Mon, Aug 22, 2016 at 4:52 PM, Jim Rollenhagen > wrote: > >> On Mon, Aug 22, 2016 at

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

Hi, I admit, I didn't read the entire thread [0], but did read the summary [1]. I like this, except that I'm not sure about #3. What's the rationale of adding a new config option 'enable_unsupported_drivers' that defaults to False. Versus not having it, and "just" logging a warning if they are

Re: [openstack-dev] [Group-based-policy] Question on GBP installation

Hi Yuki, Thanks for your email. We are currently in the process of updating the packages, and will update this webpage once that happens. Thanks, ~Sumit. On Mon, Aug 22, 2016 at 2:17 AM, Yuki Miyahara wrote: > Hi GBP Team, > > Now I'm trying to install OpenStack

[openstack-dev] [lbaas][flavor]Using flavor framework in Mitaka

Hi, We have a few questions regarding using flavor support in Mitaka- * We are trying to setup 3 flavors which can be used by LBaaS users during Loadbalancer creation. All of the 3 flavours will point to the same provider/driver. The driver should be able to understand which flavour

Re: [openstack-dev] [TripleO] Easier way of trying TripleO

On Fri, 2016-08-19 at 15:31 -0400, Dan Prince wrote: > On Tue, 2013-11-19 at 16:40 -0500, James Slagle wrote: > > > > I'd like to propose an idea around a simplified and complimentary > > version of > > devtest that makes it easier for someone to get started and try > > TripleO.   > > > > The

[openstack-dev] [Neutron] Intermittent gate failures

Neutrinos, Since the merge of test [1], a race has surfaced, which leads to failure as reported in [2]. A number of Neutron's jobs are affected, and even though the failure is only intermittent, it is particularly bad for the linux bridge job. If I can ask you to hold your +2/+W until [3] puts

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

Sorry if touch 3rd rail. But should backport bug fixes to older releases be done in distros and not upstream? -Original Message- From: Walter A. Boring IV [mailto:walter.bor...@hpe.com] Sent: Tuesday, August 09, 2016 12:34 PM To: openstack-dev@lists.openstack.org Subject: Re:

Re: [openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

Adrien, this looks good to me. Let's see what Joshua and Augie will think about it. Cheers, Dina On Mon, Aug 22, 2016 at 7:44 AM, wrote: > Hi Dina, > > 17:30 UTC means 19:30 in France (Summer time). > Considering that the meeting lasts in average 30/45 min, it would be

Re: [openstack-dev] [nova][keystone] auth for new metadata plugins

Adam Young wrote: On 08/15/2016 05:10 PM, Rob Crittenden wrote: Review https://review.openstack.org/#/c/317739/ added a new dynamic metadata handler to nova. The basic jist is that rather than serving metadata statically, it can be done dyamically, so that certain values aren't provided until

[openstack-dev] [api] Example HTTP status codes for review

Hi all, To give projects a head start and a path to copy/paste to success, I've got a sample HTTP status code YAML file that you can use with the os-api-ref Sphinx extension to make nicely-styled HTML tables. Please take a look at https://review.openstack.org/#/c/351835/ The idea here isn't to

Re: [openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

Hi Dina, 17:30 UTC means 19:30 in France (Summer time). Considering that the meeting lasts in average 30/45 min, it would be great if we could find a trade off a bit sooner. What's about 17:00 UTC ? Thanks, Adrien - Mail original - > De: "Dina Belova" > À:

[openstack-dev] [all] Generating python API signature + diff reports

Do any projects have an interest in generating python API signature reports capable of showing "what's new/changed/removed" in a release (ex: [2])? If so, read on. We recently developed a tool in neutron-lib [1] capable of inspecting + generating python API signature and diff reports. Its

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

+1 from me then :) On Mon, Aug 22, 2016 at 4:52 PM, Jim Rollenhagen wrote: > On Mon, Aug 22, 2016 at 8:01 AM, Vladyslav Drok > wrote: > > On Fri, Aug 19, 2016 at 5:15 PM, Jim Rollenhagen > > > wrote: > >> > >> Hi

Re: [openstack-dev] [LBaaS][Octavia] Health manager does not create standby amphora VM

Hi Koteswara, This is not normal behavior, but there was a reported bug that was recent fixed. Please see: https://bugs.launchpad.net/octavia/+bug/1577963 If you are still seeing an issue after using a patched version, please open a bug for the issue. Michael On Mon, Aug 22, 2016 at 6:10 AM,

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

On Mon, Aug 22, 2016 at 8:01 AM, Vladyslav Drok wrote: > On Fri, Aug 19, 2016 at 5:15 PM, Jim Rollenhagen > wrote: >> >> Hi Ironickers, >> >> There was a big thread here[0] about Cinder, driver removal, and standard >> deprecation policy. If you

Re: [openstack-dev] [TripleO] Improving Swift deployments with TripleO

On 04.08.16 15:39, Giulio Fidente wrote: > On 08/04/2016 01:26 PM, Christian Schwede wrote: >> On 04.08.16 10:27, Giulio Fidente wrote: >>> On 08/02/2016 09:36 PM, Christian Schwede wrote: Hello everyone, >>> >>> thanks Christian, >>> I'd like to improve the Swift deployments done by

[openstack-dev] [new][glance] glance_store 0.18.0 release (newton)

We are high-spirited to announce the release of: glance_store 0.18.0: OpenStack Image Service Store Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/glance_store With package available at:

[openstack-dev] [new][openstack] os-client-config 1.20.0 release (newton)

We are high-spirited to announce the release of: os-client-config 1.20.0: OpenStack Client Configuation Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/os-client-config With package available at:

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

On Fri, Aug 19, 2016 at 5:15 PM, Jim Rollenhagen wrote: > Hi Ironickers, > > There was a big thread here[0] about Cinder, driver removal, and standard > deprecation policy. If you haven't read through it yet, please do before > continuing here. :) > > The outcome of that

Re: [openstack-dev] [Openstack-operators] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

Why isn't this content in the openstack-manuals repository? On Sun, Aug 21, 2016 at 4:38 PM, Kaustubh Kelkar wrote: > I might have missed it entirely, but I wasn't able to find virtual > resources used by the instances. IMO, it'd be great if one could see > instance

[openstack-dev] [LBaaS][Octavia] Health manager does not create standby amphora VM

Hi All, I followed these steps and health manager does not create standby amphora VM in step 6. Is this a defect or working as per design? 0. Spare pool =2 1. Create LB 2. Two amphora VMs got created ( One is active , second is standby ) 3. Shutdown the Active amphora VM 4. Standby takes

Re: [openstack-dev] [nova] Hold off on pushing new patches for config option cleanup

On 08/22/2016 12:10 AM, Michael Still wrote: So, if this is about preserving CI time, then its cool for me to merge these on a US Sunday when the gate is otherwise idle, right? yes. Michael On Fri, Aug 19, 2016 at 7:02 AM, Sean Dague > wrote: On

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

On 19/08/2016 18:44, "Villalovos, John L" wrote: >> -Original Message- >> From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] >> Sent: Friday, August 19, 2016 7:15 AM >> To: OpenStack Development Mailing List (not for usage questions) >>

Re: [openstack-dev] [NOVA] How boot an instance on specific compute with provider-network: physnet1

With tags we can boot instances to a specified host aggregate. But in case when we need boot instances to a specified host, available zone is a good approach. Otherwise, we need to provide tagged flavors for each host. In real use I think it's quite impossible. Best regards, Leehom Li From:

[openstack-dev] [Fuel] Ocata design summit planning

Dear colleagues, We are two months from Ocata summit. Let's start planning topics we would like to discuss during design sessions. Here is etherpad [1]. Please put your topics under backlog section and we will disscuss later which of them will be brought out to design sessions. [1]

Re: [openstack-dev] mod_wsgi: what services are people using with it?

Just small note about mod_wsgi for Glance, You need mod_wsgi v.4.4.0 or older to work with Glance in daemon mode. Otherwise, glance should fail when uploading images. Best regards, Kairat Kushaev On Sat, Aug 20, 2016 at 4:00 AM, Nick Papadonis wrote: > > > On Fri, Aug 19,

[openstack-dev] [Group-based-policy] Question on GBP installation

Hi GBP Team, Now I'm trying to install OpenStack (Liberty) with GBP on RHEL7.2[1], but I can't find following packages from https://www.rdoproject.org/repos/rdo-release.rpm. - openstack-neutron-gbp - python-gbpclient - openstack-dashboard-gbp Do you know where it is? [1]

Re: [openstack-dev] [NOVA] How boot an instance on specific compute with provider-network: physnet1

Cloud admin can add the necessary tags in the tenant flavors. On Aug 22, 2016 12:00 AM, "Jay Pipes" wrote: > On 08/21/2016 03:24 PM, Fawaz Mohammed wrote: > >> I belive utilizing host aggregate is better than availability zone in >> this case. >> > > Users don't know

[openstack-dev] ?????? [devstack] How to start all OpenStack servicesafter restarting system?

my scripts, runs ok: /usr/bin/python /usr/bin/glance-registry --config-file=/etc/glance/glance-registry.conf &> glance-registry.log & /usr/bin/python /usr//bin/glance-api --config-file=/etc/glance/glance-api.conf &> glance-api.log & /usr/bin/python /usr/bin/nova-conductor &>

Re: [openstack-dev] [TripleO][UI] Port number for frontend app

On Mon, Aug 22, 2016 at 7:08 AM, Honza Pokorny wrote: > Hello folks, > > We've been using port 3000 for the GUI during development and testing. > Now that we're working on packaging and shipping our code, we're > wondering if port 3000 is still the best choice. > > Would 3000

Re: [openstack-dev] [TripleO][UI] Port number for frontend app

On 22/08/16 08:08, Honza Pokorny wrote: > Hello folks, > > We've been using port 3000 for the GUI during development and testing. > Now that we're working on packaging and shipping our code, we're > wondering if port 3000 is still the best choice. > > Would 3000 conflict with any other services?

Re: [openstack-dev] [neutron] Update port status to error from l2 agent

The use-case is similar to the spec[1]. [1]: https://review.openstack.org/#/c/351675/ On 2016/08/22 15:48, Edan David wrote: Hi all, It seems today that the ml2 rpc API only supports reporting that a port is up\down, There may be situations when the l2 agent can fail, For example SR-IOV

[openstack-dev] [neutron] Update port status to error from l2 agent

Hi all, It seems today that the ml2 rpc API only supports reporting that a port is up\down, There may be situations when the l2 agent can fail, For example SR-IOV agent can report failure when configuring a port on the wrong physnet. In these cases we should how would one report port failed

[openstack-dev] [TripleO][UI] Port number for frontend app

Hello folks, We've been using port 3000 for the GUI during development and testing. Now that we're working on packaging and shipping our code, we're wondering if port 3000 is still the best choice. Would 3000 conflict with any other services? Is there a better option? Thanks Honza Pokorny