Re: [openstack-dev] [Trove] Resource not found when creating db instances.

Hi Matt, Thanks for your kindly reply. I mispelled Newton in last email. I did not meet any problems with RabbitMQ, and the nova instances works well. From the error log I pasted, it seems something goes wrong when novaclient is trying to communicate with nova api. On Wed, Jan 18, 2017 at

Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] facing problem in devstack install - No Network found for private

Excellent! BTW, the following options are obsolete (as they became default in the meanwhile) disable_service n-net enable_service neutron enable_service q-svc enable_service q-agt enable_service q-dhcp enable_service q-meta enable_service q-l3 -- - Andreas IRC: andreas_s On Mi,

Re: [openstack-dev] [Trove] Resource not found when creating db instances.

Sorry Amrith, I mispelled Newton as neuton ... :( On Wed, Jan 18, 2017 at 10:59:06PM -0500, Amrith Kumar wrote: > Sorry Wang Sen, why do you say Trove is not ready for Neutron"? It has > worked with Neutron for some releases now. > > This does not appear to be at all related to Neutron. > >

[openstack-dev] [networking-sfc] Does SFC support chaining of Layer 2 devices?

All, I am exploring SFC for chaining an IDS device (strictly in L2 mode). As of now, it looks SFC default supports only L3 devices. SFC APIs doesn't have any way to specify the nature of device and without that, it seems there is no way an operator can spin any device/VNF except L3 mode VNFs.

Re: [openstack-dev] [Trove] Resource not found when creating db instances.

Trove works fine with neutron. I would look deeper into your logs. Do you have any errors about issues with Rabbit message timeouts? If so your guest may have issues talking to Rabbit. That seems to be a common issue. On Wed, Jan 18, 2017 at 8:59 PM, Amrith Kumar wrote:

Re: [openstack-dev] [Trove] Resource not found when creating db instances.

Sorry Wang Sen, why do you say Trove is not ready for Neutron"? It has worked with Neutron for some releases now. This does not appear to be at all related to Neutron. -amrith -- amrith.ku...@gmail.com On Jan 18, 2017 10:56 PM, "Wang Sen" wrote: > Hi all, > > I met

[openstack-dev] [Elections][PTL][Cinder] Sean McGinnis Candidacy for Pike

Hello everyone, I have been the Cinder PTL since the Mitaka release and I would love the opportunity to be the PTL one more time. I work for Dell EMC, working with storage for the last 14+ years. I am lucky enough that I have the support to focus on OpenStack for my job. I also have the support

[openstack-dev] [Trove] Resource not found when creating db instances.

Hi all, I met the resource not found error when I'm creating a database instance. The instance stays on build status and turns to error status after timeout. I know trove is not ready for neuton. Is there a work around for this issue ? Thanks in advance. Below is the detailed information.

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

On Thu, Jan 19, 2017 at 5:54 AM, Mikhail Fedosin wrote: > And here I want to ask the community - how exactly Glare may be useful in > OpenStack? Glare was developed as a repository for all possible data types, > and it has many possible applications. For example, it's a

[openstack-dev] [Gluon] F2F Meeting on Feb 6 and Feb 7 in Sunnyvale, CA to Complete Deliverables

Hello team, During the IRC meeting on January 11 [1] and today [2], the group agreed to have a face-to-face meeting on February 6th & 7th (Monday and Tuesday) in Silicon Valley to complete coding and testing before Ocata release schedule. The meeting logistics is available at [3], and

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On Wed, Jan 18, 2017 at 5:18 PM, Clint Byrum wrote: > Excerpts from Morgan Fainberg's message of 2017-01-18 15:33:00 -0800: > > On Wed, Jan 18, 2017 at 11:23 AM, Brant Knudson wrote: > > > > > > > > > > > On Wed, Jan 18, 2017 at 9:58 AM, Dave McCowan (dmccowan) <

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

Excerpts from Morgan Fainberg's message of 2017-01-18 15:33:00 -0800: > On Wed, Jan 18, 2017 at 11:23 AM, Brant Knudson wrote: > > > > > > > On Wed, Jan 18, 2017 at 9:58 AM, Dave McCowan (dmccowan) < > > dmcco...@cisco.com> wrote: > > > >> > >> On Mon, Jan 16, 2017 at 7:35 AM, Ian

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

gordon chung wrote: On 03/01/17 03:03 PM, Joshua Harlow wrote: Hi Oslo folks (and others), Happy new year! After serving for about a year I think it's a good opportunity for myself to let another qualified individual run for Oslo PTL (seems common to only go for two terms and hand-off to

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

On Thu, Jan 19, 2017 at 10:27 AM, Matt Riedemann wrote: > On 1/18/2017 4:53 AM, Jens Rosenboom wrote: > >> To me it looks like the times of 2G are long gone, Nova is using >> almost 2G all by itself. And 8G may be getting tight if additional >> stuff like Ceph is

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

On 01/14/2017 02:48 AM, Jakub Libosvar wrote: > recently I noticed we got oom-killer in action in one of our jobs [1]. > Any other ideas? I spent quite a while chasing down similar things with centos a while ago. I do have some ideas :) The symptom is probably that mysql gets chosen by the

[openstack-dev] [all][Elections] Nominations for OpenStack PTLs (Program Team Leads) are now open

Hello All! Nominations for OpenStack PTLs (Program Team Leads) are now open and will remain open until Jan 29, 2017 23:45 UTC. All candidates must be submitted as a text file to the openstack/election repository as explained at

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On Wed, Jan 18, 2017 at 11:23 AM, Brant Knudson wrote: > > > On Wed, Jan 18, 2017 at 9:58 AM, Dave McCowan (dmccowan) < > dmcco...@cisco.com> wrote: > >> >> On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco >> wrote: >> >>> Hi everyone, >>> >>> I've seen a few

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

On 1/18/2017 4:53 AM, Jens Rosenboom wrote: To me it looks like the times of 2G are long gone, Nova is using almost 2G all by itself. And 8G may be getting tight if additional stuff like Ceph is being added. I'm not really surprised at all about Nova being a memory hog with the versioned

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

On 1/13/2017 9:48 AM, Jakub Libosvar wrote: Hi, recently I noticed we got oom-killer in action in one of our jobs [1]. I saw it several times, so far only with linux bridge job. The consequence is that usually mysqld gets killed as a processes that consumes most of the memory, sometimes even

[openstack-dev] [all] Ubuntu 14.04 support in Newton and on

Hi all, Is there any community-wide policy on how long we strive to maintain compatibility with Ubuntu 14.04? For example by avoiding relying on MySQL 5.7 features. I¹ve had a hard time finding it on openstack.org and ML discussions. Thanks lots!

[openstack-dev] [tacker] Tacker PTL Non-candidacy

As I announced in the last Tacker weekly meeting, I'm not planning to run for Pike PTL position. Having served in this role for the last three cycles (including for the periods before it was a big-tent project), I think it is time for someone else to step in and take this forward. I'll continue to

[openstack-dev] [nova] Feature-related changes that need a final +2 (1/18)

Just to bring this to the awareness of other reviewers, here is a list of blueprint-related patches that have a +2 and need a final push: 1. https://blueprints.launchpad.net/nova/+spec/ironic-plug-unplug-vifs-update https://review.openstack.org/#/c/364413/ - don't miss the bug fix change

Re: [openstack-dev] [Congress][Fuel] Fuel plugin for installing Congress

Hi Serg, That¹s awesome news. Thanks all for the great work! Please do let us know how the Congress team can be helpful. On 1/16/17, 11:33 AM, "Serg Melikyan" wrote: >I'd like to introduce you fuel plugin for installing and configuring >Congress for Fuel [0]. > >This

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 We've also talked about fancier non-keystone-auth like x.509 certificate s. - - Douglas On 1/18/17 11:52 AM, Clint Byrum wrote: > Excerpts from Dave McCowan (dmccowan)'s message of 2017-01-18 > 15:58:19 +: >> >> On Mon, Jan 16, 2017 at 7:35

Re: [openstack-dev] [requirements] changing the order of values in upper-constraints.txt

On 2017-01-18 16:34:56 -0500 (-0500), Doug Hellmann wrote: > When I tried to merge the upper-constraints updates for the library > releases we did today, I ran into quite a lot of merge conflicts > with the Oslo libraries. I'm exploring options for reducing the > likelihood that those sorts of

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

Looping this into the operator's list, too! On Wed, Jan 18, 2017 at 2:13 PM, Lance Bragstad wrote: > Thanks to Morgan in today's policy meeting [0], we were able to shed some > light on the reasons for keystone having two policy files. The main reason > a second policy file

[openstack-dev] [neutron] "Setup firewall filters only for required ports" bug

Hi neutrinos, I would like your feedback on the mentioned changeset in title[1] (yes, added since Liberty). With this patch, we (should) skip ports with port_security_enabled=False or with an empty list of security groups when processing added ports [2]. But we found multiple problems here *

Re: [openstack-dev] [requirements] changing the order of values in upper-constraints.txt

I actually like the last option (sha) the most, even as a packager I can just take the file and sort it if I want something more human readable. -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature

[openstack-dev] [requirements] changing the order of values in upper-constraints.txt

When I tried to merge the upper-constraints updates for the library releases we did today, I ran into quite a lot of merge conflicts with the Oslo libraries. I'm exploring options for reducing the likelihood that those sorts of conflicts will occur with a few patches that change how we generate

[openstack-dev] [validations][ui] resetting state of validations

Hi - Is there a way to reset the state of all the validations that have previously ran, back to the original state they were prior to running? Using the UI, for example, some validations (by design) run as soon as you log in. Others run after different actions are completed. But there's a

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I think that a Vault backend would only be valuable to folks who are already using Vault. For deployers who don't yet have a key management solution, a Vault backend would not solve the problem of having to deploy yet another service. In fact it

Re: [openstack-dev] [all] [goals] proposing a new goal: "Control Plane API endpoints deployment via WSGI"

On Thu, Jan 12, 2017 at 8:40 PM, Emilien Macchi wrote: > Greetings OpenStack community, > > I have been looking for a Community Goal [1] that would directly help > Operators and I found the "run API via WSGI" useful. > So I've decided to propose this one as a goal for Pike but

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

On 03/01/17 03:03 PM, Joshua Harlow wrote: > Hi Oslo folks (and others), > > Happy new year! > > After serving for about a year I think it's a good opportunity for > myself to let another qualified individual run for Oslo PTL (seems > common to only go for two terms and hand-off to another). > >

[openstack-dev] [nova] Reminder: 1/19 is non-client library release freeze

This is just a reminder that tomorrow (Thursday 1/19) is the non-client library release freeze for Ocata. This means if you have code that depends on something in a non-client library, like any of the oslo or os-* libraries, those changes have to be merged and released by EOD tomorrow or they

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

Thanks to Morgan in today's policy meeting [0], we were able to shed some light on the reasons for keystone having two policy files. The main reason a second policy file was introduced was to recenter RBAC around concepts introduced in the V3 API. The problem was that the policy file that came

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On Wed, Jan 18, 2017 at 9:58 AM, Dave McCowan (dmccowan) wrote: > > On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco > wrote: > >> Hi everyone, >> >> I've seen a few nascent projects wanting to implement their own secret >> storage to either replace

Re: [openstack-dev] [containers][magnum] Magnum team at Summit?

On Jan 18, 2017, at 10:48 AM, Mark Baker > wrote: Hi Adrian, Let me know if you have similar questions or concerns about Ubuntu Core with Magnum. Mark Thanks Mark! Is there any chance you, or an Ubuntu Core representative could join

Re: [openstack-dev] [containers][magnum] Magnum team at Summit?

Hi Adrian, Let me know if you have similar questions or concerns about Ubuntu Core with Magnum. Mark On 18 Jan 2017 8:36 p.m., "Adrian Otto" wrote: > Josh, > > > On Jan 18, 2017, at 10:18 AM, Josh Berkus wrote: > > > > Magnum Devs: > > > > Is

Re: [openstack-dev] [containers][magnum] Magnum team at Summit?

Josh, > On Jan 18, 2017, at 10:18 AM, Josh Berkus wrote: > > Magnum Devs: > > Is there going to be a magnum team meeting around OpenStack Summit in > Boston? > > I'm the community manager for Atomic Host, so if you're going to have > Magnum meetings, I'd like to send you

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'm very much interested in an out-of-the-box software-only backend driver for Barbican. I think that one of the reasons people have been hesitant to deploy Barbican is that we claim that our Simple Crypto software-only driver is "not secure in any

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Excerpts from Mikhail Fedosin's message of 2017-01-18 19:54:01 +0300: > Hello! > > In this letter I want to tell you the current status of Glare project and > discuss its future development within the entire OpenStack community. > > In the beginning I have to say a few words about myself - my

Re: [openstack-dev] [requirements][nova][horizon][release] unable to update constraint for python-novaclient to 7.0.0

Nice work tracking that down, thanks! Excerpts from Diana Clarke's message of 2017-01-18 12:19:35 -0500: > Fixed. I'm a big girl now, lol. > > Cheers, > > --diana > > On Wed, Jan 18, 2017 at 9:42 AM, Doug Hellmann wrote: > > The automatically produced patch to update

[openstack-dev] [containers][magnum] Magnum team at Summit?

Magnum Devs: Is there going to be a magnum team meeting around OpenStack Summit in Boston? I'm the community manager for Atomic Host, so if you're going to have Magnum meetings, I'd like to send you some Atomic engineers to field any questions/issues at the Summit. -- -- Josh Berkus Project

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

Excerpts from Dave McCowan (dmccowan)'s message of 2017-01-18 15:58:19 +: > > On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco > > wrote: > Hi everyone, > > I've seen a few nascent projects wanting to implement their own secret > storage to

Re: [openstack-dev] [all] Improving Vendor Driver Discoverability

Just a FYI, Ankur have been working on have a Feature Classification Matrix in Neutron[1] which collects some of this information [1] https://review.openstack.org/#/c/318192/ Regards/Saludos Victor Morales Irc: electrocucaracha On 1/13/17, 10:29 PM, "Mike Perez" wrote:

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Wed, Jan 18 2017, Mehdi Abaakouk wrote: > So, I agree with gordc, perhaps you should stay with the old and > unsupported lib. And let other to use the supported one. The best option would be for the Monasca folks to actually participate upstream to the Kafka driver development and help

Re: [openstack-dev] [requirements][nova][horizon][release] unable to update constraint for python-novaclient to 7.0.0

On 1/18/2017 11:19 AM, Diana Clarke wrote: Fixed. I'm a big girl now, lol. Cheers, --diana Nice, thanks for jumping on that. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

On 1/18/2017 10:54 AM, Mikhail Fedosin wrote: Hello! In this letter I want to tell you the current status of Glare project and discuss its future development within the entire OpenStack community. In the beginning I have to say a few words about myself - my name is Mike and I am the PTL of

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Thanks Joe for all these details, I can see that Monasca is still not able to switch to the new lib for new very good reasons. But according your comment on https://review.openstack.org/#/c/420579/ : I don't think that anyone currently using Monasca wants to accept either of those options so

Re: [openstack-dev] [requirements][nova][horizon][release] unable to update constraint for python-novaclient to 7.0.0

Fixed. I'm a big girl now, lol. Cheers, --diana On Wed, Jan 18, 2017 at 9:42 AM, Doug Hellmann wrote: > The automatically produced patch to update the constraints to include > python-novaclient 7.0.0 are failing on the horizon test job. Can someone > please look into

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On 17/01/17 06:58 PM, Keen, Joe wrote: > > I also see additional problems with the use of the deprecated > SimpleConsumer and SimpleProducer clients. We really do need to > investigate migrating to the new async only Producer objects while still > maintaining the reliability guarantees that

[openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Hello! In this letter I want to tell you the current status of Glare project and discuss its future development within the entire OpenStack community. In the beginning I have to say a few words about myself - my name is Mike and I am the PTL of Glare. Currently I work as a consultant at Nokia,

Re: [openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.01.18 Agenda

Hi Team, Thanks for attending today's meeting, please find the minutes at https://docs.google.com/document/d/18Dw90FFNv4n0_y1JSg8k3_Duk7zBXE_lbr8wlhksBkY/pub On Wed, Jan 18, 2017 at 10:43 PM, Harm Sluiman wrote: > I am afraid I am stuck in an alternate reality meeting

Re: [openstack-dev] [cinder] Problem with lvm thin provisioning and snapshots

Ok, problem solved (it seems) in /etc/lvm/lvm.conf I need to set auto_set_activation_skip = 0 and, in my case, I set the same in /etc/cinder/lvm.conf (because I'm using a cluster configuration for lvm) Thank you 2017-01-18 16:38 GMT+01:00 Marco Marino : > Hi, I'm trying

Re: [openstack-dev] [tripleo] short term roadmap (actions required)

On Wed, Jan 18, 2017 at 9:57 AM, John Trowbridge wrote: > > > On 01/17/2017 04:36 PM, Emilien Macchi wrote: >> I'm trying to dress a list of things important to know so we can >> successfully deliver Ocata release, please take some time to read and >> comment if needed. >> >> ==

[openstack-dev] [charms] monitoring interface

Hi all, We're looking at adding the monitor interface to the openstack charms to enable us to use the nagios charm, rather than via an external nagios using nrpe-external-master. I believe this will just be a matter of adding in the interface, adding an appropriate monitor.yaml that defines

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco > wrote: Hi everyone, I've seen a few nascent projects wanting to implement their own secret storage to either replace Barbican or avoid adding a dependency on it. When I've pressed the

[openstack-dev] [cinder] Problem with lvm thin provisioning and snapshots

Hi, I'm trying to use lvm thin provisioning with openstack cinder (mitaka) but I have a problem with snapshots. I'm trying to create a snapshot from a volume (detached) and then create a new volume from the snapshot. 1) Snapshot creation works well and I have (with lvs) LV

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco wrote: > Hi everyone, > > I've seen a few nascent projects wanting to implement their own secret > storage to either replace Barbican or avoid adding a dependency on it. > When I've pressed the developers on this point, the

Re: [openstack-dev] [congress][oslo.config][keystone] NoSuchOptError: no such option project_domain_name in group [keystone_authtoken]

On Thu, Jan 12, 2017 at 4:31 PM, Eric K wrote: > On a freshly stacked devstack (Jan 12), attempting to access > `cfg.CONF.keystone_authtoken.project_domain_name` gave the > error: NoSuchOptError: no such option project_domain_name in group > [keystone_authtoken] > > I’m

[openstack-dev] [Cinder] Ocata Priority Sprint

Just to raise awareness - we've discussed this in channel and in the weekly meeting. Today and tomorrow we will be doing a short sprint to focus on getting the Active/Active HA and new Attach/Detach API work reviewed and merged. Lists of patches for both efforts can be found in our review

Re: [openstack-dev] [tripleo] short term roadmap (actions required)

On 01/17/2017 04:36 PM, Emilien Macchi wrote: > I'm trying to dress a list of things important to know so we can > successfully deliver Ocata release, please take some time to read and > comment if needed. > > == Triaging Ocata & Pike bugs > > As we discussed in our weekly meeting, we decided

Re: [openstack-dev] [release][stable] nominating Alan Pevec (apevec) for stable release core

+1 from me. welcome Alan On Wed, Jan 18, 2017 at 9:16 AM, Doug Hellmann wrote: > Based on Tony's recommendation, and Alan's recent review work, I > am nominating Alan Pevec (apevec) to have core reviewer rights on > stable releases in the openstack/releases repository. > >

Re: [openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.01.18 Agenda

I am afraid I am stuck in an alternate reality meeting this week. my apologies I will work to get the other meeting moved in the future On Tue, Jan 17, 2017 at 10:26 PM, Zhipeng Huang wrote: > Hi Team, > > Please find the agenda at https://wiki.openstack.org/ >

[openstack-dev] [requirements][nova][horizon][release] unable to update constraint for python-novaclient to 7.0.0

The automatically produced patch to update the constraints to include python-novaclient 7.0.0 are failing on the horizon test job. Can someone please look into whether that is still actually an issue so we can be sure of including the client release in Ocata? Thanks, Doug

[openstack-dev] [architecture] Base services

Hi everyone, In OpenStack all components can assume that a number of external services will be present and available for them to use (think: a message queue), but we never had a clear name to describe them or a clear list. Work has started[0] within the Architecture working group[1] to prepare a

Re: [openstack-dev] [keystone] webob 1.7

With the release targeted for 5 weeks out - https://releases.openstack.org/ I agree with Ian that this is a distraction at this point. It should be a Pike priority, but I think chasing and validating this for Ocata is the wrong call, as it is likely to impact a bunch of projects. -Sean

[openstack-dev] [octavia] IRC weekly meeting of Jan.18

Hi, Active Active Topology discussion items: 1. Merging commits up to "Distributor image creation" https://review.openstack.org/#/c/403594 Updated etherpad doc: https://etherpad.openstack.org/p/Active-_Active_Topology_commits 2. Bug #1655656:

[openstack-dev] [release][stable] nominating Alan Pevec (apevec) for stable release core

Based on Tony's recommendation, and Alan's recent review work, I am nominating Alan Pevec (apevec) to have core reviewer rights on stable releases in the openstack/releases repository. Release team, please either +1 or raise any concerns you have. Doug

Re: [openstack-dev] [keystone] webob 1.7

Hi Ian, I just read the bug report and I don't think the correct fix for this issue is to blacklist webob 1.7.0. The reason for this is that multiple distros are already using webob 1.7. Also projects like keystonemiddleware have made backwards compatible changes to accomodate newer versions of

Re: [openstack-dev] [keystone] webob 1.7

On 18-Jan 08:59, Chuck Short wrote: > Hi > > We have been expericing problems with newer versions of webob (webob 1.7). > Reading the changelog, it seems that the upstream developers have > introduced some backwards incompatibility with previous versions of webob > that seems to be hitting

Re: [openstack-dev] [keystone] webob 1.7

-Original Message- From: Chuck Short Reply: OpenStack Development Mailing List (not for usage questions) Date: January 18, 2017 at 08:01:46 To: OpenStack Development Mailing List Subject: 

[openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

Last night in the TC meeting a topic[1] was a review[2] to introduce a new tag 'assert:supports-api-compatibility' which: defines the base expectations and requirements for a stable REST API provided by a service The tag document uses an API guideline, "Evaluating API Changes"[3], as

[openstack-dev] [ironic] release timelines

Hi all, As you probably know, ironic is a cycle-with-intermediary project that doesn't strictly follow the OpenStack feature freeze. Ocata is finishing up and we need to define some deadlines/goals around a final release. Please refer to the schedule here:

[openstack-dev] [keystone] webob 1.7

Hi We have been expericing problems with newer versions of webob (webob 1.7). Reading the changelog, it seems that the upstream developers have introduced some backwards incompatibility with previous versions of webob that seems to be hitting keystone and possibly other projects as well

[openstack-dev] [nova][dpm] multiple nova-compute services on *one* host?

TL;DR: Is it advisable to run multiple nova-compute services within the same operating system while each nova-compute service manages a different (remote) hypervisor? The longer version: Co-workers and I are working on a new (out-of-tree [1]) driver for a system z hypervisor [2]. A model of what

Re: [openstack-dev] [ironic] [infra] Nested KVM + the gate

Jay, This is the Trove commit … I85364c6530058e964a8eba7fb515d7deadfd5d72 -amrith From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Wednesday, January 18, 2017 7:57 AM To: OpenStack

Re: [openstack-dev] [ironic] [infra] Nested KVM + the gate

On Tue, Jan 17, 2017 at 6:41 PM, Jay Faulkner wrote: > Hi all, > > Back in late October, Vasyl wrote support for devstack to auto detect, and > when possible, use kvm to power Ironic gate jobs ( > 0036d83b330d98e64d656b156001dd2209ab1903). This has lowered some job time > when it

Re: [openstack-dev] [TripleO][Mistral][Ansible] Calling Ansible from Mistral workflows

Ok to both answers. Renat Akhmerov @Nokia > On 18 Jan 2017, at 16:37, Dougal Matthews wrote: > > > > On 17 January 2017 at 03:28, Renat Akhmerov > wrote: > Dougal, I looked at the source code. Seems like it’s

Re: [openstack-dev] [tripleo][ui] FYI, the tripleo-ui package is currently broken

Hi all, I'm sorry to report we're finding ourselves in the same situation again - CI will fail on all the UI patches, please don't recheck until we have a new dependencies package available. On the plus side, with the help of amoralej on #rdo we figured out why this is happening: the tripleo-ui

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

2017-01-13 17:56 GMT+01:00 Clark Boylan : > On Fri, Jan 13, 2017, at 07:48 AM, Jakub Libosvar wrote: >> Does anybody know whether we can bump memory on nodes in the gate >> without losing resources for running other jobs? >> Has anybody experience with memory consumption

[openstack-dev] [kuryr] Project Virtual Gathering (PVG)

Hi Kuryrs! Due to traveling restrictions, we opted not to take part in the Atlanta PTG. However, the design work sessions won't disappear :-) Please go through its etherpad[0] and propose, vote, comment about sessions, format and scheduling. Regards, Toni [0]

Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] facing problem in devstack install - No Network found for private

Hi Andreas, As in between you suggested to try with default devstack neutron config params. I tried that i set no config option for neutron part all default. This local.conf is working well.. for others who are facing problem pasting working local.conf here

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

From: Yujun Zhang Date: Tuesday, 17 January 2017 at 02:41 Sounds good. Have you created an etherpad page for collecting topics, Ifat? Here: https://etherpad.openstack.org/p/vitrage-pike-design-sessions

Re: [openstack-dev] [TripleO][Mistral][Ansible] Calling Ansible from Mistral workflows

On 17 January 2017 at 03:28, Renat Akhmerov wrote: > Dougal, I looked at the source code. Seems like it’s already usable enough. > Do you think we need to put a section about Ansible actions into Mistral > docs? > I’m also thinking if we need to move this code into the

Re: [openstack-dev] Attempting to proxy websockets through Apache or HAProxy for Zaqar

On Tue, Jan 17, 2017 at 6:23 PM, Dan Trainor wrote: > Hi - > > In an attempt to work on [0], I've been playing around with proxying all the > service API endpoints that the UI needs to communicate with, through either > haproxy or Apache to avoid a bug[1] around how

Re: [openstack-dev] [yaql] Yaql validating performance

Hi Kirill, Do you have any information related to the performance of Jinja and Yaql validating. With the big size of input, yaql runs quite so slow in our case therefore we have plan to switch to jinja. Br, @Nokia/Tuan On Tue, Jan 17, 2017 at 3:02 PM, lương hữu tuấn

Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] facing problem in devstack install - No Network found for private

Andreas, I require nothing specific from neutron side. Just a basic working setup from neutron side because my work is mostly on storage side of OpenStack. Can you please suggest a working configuration if tried recently. Thanks nidhi From: Nidhi

[openstack-dev] [tripleo] [zaqar] Re: Attempting to proxy websockets through Apache or HAProxy for Zaqar

(Just adding a couple of topic tags for visibility) On 17 January 2017 at 17:23, Dan Trainor wrote: > Hi - > > In an attempt to work on [0], I've been playing around with proxying all the > service API endpoints that the UI needs to communicate with, through either > haproxy

Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] facing problem in devstack install - No Network found for private

HI Andreas, Thanks for your reply. I have no specific reason for using this network configuration in local.conf. I have only basic knowledge of these config options even. This local.conf network configurations used to work well with earlier devstack openstack versions. So i did not change

[openstack-dev] [acceleration]Team Bi-weekly Meeting 2017.01.18 Agenda

Hi Team, Please find the agenda at https://wiki.openstack.org/wiki/Meetings/ CyborgTeamMeeting#Agenda_for_next_meeting our IRC channel is #openstack-cyborg -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email:

[openstack-dev] [tricircle]weekly meeting of Jan.18

Hello, team, Agenda of Jan.18 weekly meeting: 1. Ocata release preparation 2. Pike planning and design topics: https://etherpad.openstack.org/p/tricircle-pike-design-topics 3. QoS and LBaaS feature support 4. Open Discussion How to join: # IRC meeting: