Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

Hi Marc, I am driving the ironic-ml2 integration and introduced baremetal type for vmic_type. You can very much use the same integration here - however, I am not completely clear about your use case. Do you want neutron/ML2 to plumb the network for Manila or do you want to find out what VLAN

Re: [openstack-dev] [oslo] oslo.messaging dispatching into private/protected methods?

So during this exploration of this code for the above review it made me wonder if this is a feature or bug, or if we should at least close the hole of allowing calling into nearly any endpoint method/attribute (even non-callable ones to?). ... Thoughts? I agree that doesn't make any sense to

Re: [openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

Thanks for this discussion and the agreement, it sounds good, I will upload related changes. -- Liu sheng 在 2016/3/7 23:42, gordon chung 写道: On 07/03/2016 8:05 AM, Julien Danjou wrote: On Mon, Mar 07 2016, gordon chung wrote: shall we drop 'alarm search' nomenclature and use just 'alarm

Re: [openstack-dev] [L2-Gateway] Install and Configuration issue

Hi Jason, According to the L2GW config, it should be set as in this line: https://github.com/openstack/networking-l2gw/blob/master/etc/l2gw_plugin.ini#L25 I think it should be working as default setting, but maybe you can try to set this explicitly. Hope it helps, Irena On Tue, Mar 8, 2016 at

Re: [openstack-dev] [Fuel] Nominate Maksim Malchuk for the fuel-virtualbox-core team

+1 Regards, Bulat Gaifullin Mirantis Inc. > On 03 Mar 2016, at 17:03, Dmitry Klenov wrote: > > Maksim, good job! +1 from my side though I am not a core. > > On Thu, Mar 3, 2016 at 4:10 PM, Aleksey Zvyagintsev >

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/08/2016 09:58 AM, Derek Higgins wrote: On 7 March 2016 at 18:22, Ben Nemec wrote: On 03/07/2016 11:33 AM, Derek Higgins wrote: On 7 March 2016 at 15:24, Derek Higgins wrote: On 6 March 2016 at 16:58, James Slagle

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

> > > I don't think your example is right: "PKI will validate that token > without going to any keystone server". How would it track revoked tokens? > I'm pretty sure that they still get validated, they are stored in the DB > even. > > I also disagree that there are different use cases. Just

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

From: Matt Fischer > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Tuesday 8 March 2016 at 20:35 To: "OpenStack Development Mailing

[Openstack] Kick Start

Just start to learn something about Openstack，any suggestion? Sent from Mail for Windows 10 ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to :

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

Henry, i think it's better to fix model vs migration mismatch issues [1] before tagging. how do you think? [1] https://review.openstack.org/#/c/287016/ On Tue, Mar 8, 2016 at 11:52 PM, Henry Gessau wrote: > By tomorrow we intend to tag the heads of all the neutron alembic

[Openstack] Fine-grained control of designate domain policy

Due to the weird public/private hybrid nature of my cloud, I'm frequently needing to abuse policy.conf files in unexpected ways. Today's challenge is the designate policy. Right now we're running a custom solution that maintains all public dns entries under a single domain: wmflabs.org.

Re: [Openstack-operators] Neutron doesn't start - was Neutron connection issue

Great! I had this working 4 hours ago. :) Thanks Chris. Sent from my iPhone > On Mar 8, 2016, at 6:57 PM, Kevin Benton wrote: > > Yes, if everything is on one box, you will only see one linux bridge agent. > >> On Mar 8, 2016 18:55, "Christopher Hull"

Re: [Openstack-operators] Neutron doesn't start - was Neutron connection issue

Yes, if everything is on one box, you will only see one linux bridge agent. On Mar 8, 2016 18:55, "Christopher Hull" wrote: > Oh. My bad. > I installed Neutron Controller and Compute on the same node. When I did > Compute, I commented out the DB connection (as it

Re: [Openstack-operators] Neutron doesn't start - was Neutron connection issue

Oh. My bad. I installed Neutron Controller and Compute on the same node. When I did Compute, I commented out the DB connection (as it said)... OOPS! Put it back. Now it works. I feel silly. NOW I'm wondering where my Neutron Compute agent is. I should see one Compute in this list.

Re: [openstack-dev] [app-catalog] Nominating Kirill Zaitsev to App Catalog Core

On Thu, Mar 3, 2016 at 1:10 PM, Christopher Aedo wrote: > I'd like to propose Kirill Zaitsev to the core team for app-catalog > and app-catalog-ui. > Kirill has been actively involved with the Community App Catalog since > nearly the beginning of the project, and more recently has

Re: [Openstack-operators] Neutron doesn't start - was Neutron connection issue

Once you get it configured with a normal db backend, you will have to run the neutron-db-manage command again to repopulate the schema. On Mar 8, 2016 18:43, "Kevin Benton" wrote: > Ah, it looks like neutron isn't configured to use a database so it's > defaulting to an

Re: [Openstack-operators] Neutron doesn't start - was Neutron connection issue

Ah, it looks like neutron isn't configured to use a database so it's defaulting to an in-memory sqlite server. Check your connection string in the neutron config. On Mar 8, 2016 18:39, "Christopher Hull" wrote: > Ah Neutron didn't start... > I see this issue mentioned

Re: [Openstack-operators] Neutron connection issue - Unable to establish connection to http://controller

For some reason the neutron agent thinks neutron is located at a hostname called 'controller'. I would check out your Keystone endpoint list to see if it needs to be updated with the correct hostname. If 'controller' is correct, it sounds like the neutron server didn't start correctly. Check the

Re: [Openstack-operators] Neutron doesn't start - was Neutron connection issue

That error is showing that the tables Neutron wants to access aren't in the database it is accessing. Did you change databases during the reboot? On Wed, 9 Mar 2016 at 13:39 Christopher Hull wrote: > Ah Neutron didn't start... > I see this issue mentioned elsewhere, but

[Openstack-operators] Neutron doesn't start - was Neutron connection issue

Ah Neutron didn't start... I see this issue mentioned elsewhere, but haven't dug up a solution yet. It was running before a reboot. Hmmm. neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations 2016-03-08 20:55:08.491 1664 ERROR neutron

Re: [OpenStack-Infra] Borrowing OpenStack Infrastructure tools

On 03/06/2016 12:10 PM, Noorul Islam K M wrote: I am a big fan of Openstack CI. I used it when I was contributing to Solum project. Currently at work we have a requirement to find a CI solution. Since I know Openstack CI is comprehensive and stable, I thought I would re-use it. Why to

[openstack-dev] [Horizon] Javascript linting and documentation

Hey all, I started looking into fixing the wall of "npm run lint" warnings today and quickly noticed that about 85% of the "linting" warnings were about jsdoc. We have significant issues around jsdoc anyway and we're supposed to be using Sphinx anyway[1]. Some Horizon folks will know that I've

[Openstack-operators] Neutron connection issue - Unable to establish connection to http://controller

Hi all; I was wondering if someone could tell me how to trace this down. I've got a single box installation that I'm trying to get working. Everything seems to run, but when I reboot, Neutron drops off. neutron agent-list Unable to establish connection to

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On 9 March 2016 at 09:51, Colette Alexander wrote: > > > On Tue, Mar 8, 2016 at 12:27 PM, Matt Riedemann > wrote: >>> >>> >> >> So is this for only current TC members? What about people that aren't on >> the TC? >> >> I asked in this in

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 9 March 2016 at 14:23, Jeremy Stanley wrote: > On 2016-03-09 13:57:45 +1300 (+1300), Robert Collins wrote: >> On 9 March 2016 at 13:07, Jeremy Stanley wrote: >> > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: >> > [...] >> >> SOLUTION 6 -

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 4:44 PM, Matt Riedemann wrote: On 3/8/2016 3:17 PM, Matt Riedemann wrote: On 3/8/2016 1:18 PM, Amrith Kumar wrote: Matt, See inline below. -amrith -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent: Tuesday, March 08, 2016 2:00 PM To:

Re: [openstack-dev] [nova][ceilometer] unable to see compute.node.cpu.* metrics in ceilometer

On Mar 8, 2016 02:15, Kapil wrote: > Hi > > > I enabled ComputeDriverCPUMonitor in nova.conf on one of the compute > nodes, restarted nova-compute, ceilometer-agent-compute on the compute > node and ceilometer-collector, ceilometer-api, > ceilometer-agent-central,

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 2016-03-09 13:57:45 +1300 (+1300), Robert Collins wrote: > On 9 March 2016 at 13:07, Jeremy Stanley wrote: > > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: > > [...] > >> SOLUTION 6 - make zuul capable of performing atomic cross-repository > >> commits. > > > >

Re: [openstack-dev] [release] mitaka-3 development milestone

On 2016-03-08 15:13:40 -0500 (-0500), Corey Bryant wrote: [...] > I'm only seeing neutron-vpnaas-8.0.0.0b3.dev1.tar.gz on > https://tarballs.openstack.org/neutron-vpnaas. Do we need an > update there? After some investigation, it appears your tarball jobs were broken up until

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 9 March 2016 at 13:07, Jeremy Stanley wrote: > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: > [...] >> SOLUTION 6 - make zuul capable of performing atomic cross-repository >> commits. > > This seems unlikely to happen, as it's very much counter to Zuul's >

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

But Jeremy: Atomic Zuul. How cool is that name. So I know I'm going to potentially get yelled at for voicing this, but what are the chances that app-catalog and Horizon are ever installed on the same system? That is, could it have its own xstatic constraints, with the promise that the two

Re: [openstack-dev] [keystone] [horizon] [qa] keystone versionless endpoints and v3

So with the merge of [1] the devstack change [2] to use unversioned endpoints passes gate. From previous experience this should not be considered an extensive test, however the only real way to find out what doesn't work is to merge it and see what fails. [1]

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: [...] > SOLUTION 6 - make zuul capable of performing atomic cross-repository > commits. This seems unlikely to happen, as it's very much counter to Zuul's designed-in reliance on serializing changes to test before merging them. -- Jeremy

[openstack-dev] [Neutron][DVR] No Meeting tomorrow

Sorry for the late notice, but I need to cancel the DVR meeting for tomorrow the 9th as a few of us have a conflict. We'll resume again next week on the 16th. -Brian __ OpenStack Development Mailing List (not for usage

[openstack-dev] [kolla] Mitaka release schedules and priorities - only 30 days left!

Hi Koala Bears! The release candidate schedules are as follows: We are in feature freeze. No new features in Kolla until after Mitaka is released on April 4th-April 8th. We may lag this date a little bit depending on the state of the tarballs repo for build from source, or we may just tag

Re: [openstack-dev] [Horizon][app-catalog] How do we move forward with xstatic releases?

fyi, we are planning on using the xstatic packages for the app catalog website so we can share as much code as possible with horizon and the app catalog horizon plugin. So it will affect the app catalog too, not just horizon. Thanks, Kevin From: David Lyle

Re: [Openstack-operators] [openstack-operators][neutron] use-case for multiple routers within a tenant

We use them all the time, and openstack in one version actually broke them on us. (I wrote and contributed a unit test so it shouldn't happen again.) Use case: You have two external networks. 1. Internet - One that's directly connected to the internet. 2. One that is a private network space and

Re: [Openstack] some error of install-openstack-from-source

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/03/16 08:56, Tony Breeds wrote: > On Tue, Mar 08, 2016 at 10:41:49AM +0800, yewgang wrote: >> Hi, >> >> I'm porting openstack from source into my environment, follows >> https://developer.rackspace.com/blog/install-openstack-from-source/ >> >>

Re: [openstack-dev] [keystone] [horizon] [qa] keystone versionless endpoints and v3

On Tue, Feb 23, 2016 at 8:49 PM, Jamie Lennox wrote: > > > On 18 February 2016 at 10:50, Matt Fischer wrote: > >> I've been having some issues with keystone v3 and versionless endpoints >> and I'd like to know what's expected to work exactly in

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

+1 we need Diana's perspective, knowledge and enthusiasm On 9 March 2016 at 10:03, Tripp, Travis S wrote: > +1, no questions asked. It is rare to find somebody with the passion that > Diana has shown. > > From: Lin Hua Cheng

Re: [Openstack-operators] [openstack-operators][neutron] use-case for multiple routers within a tenant

More than one multi-tier application avoiding broadcast domains. From: Rubab Syed > Date: Tuesday, March 8, 2016 at 2:20 PM To: "openstack-operators@lists.openstack.org"

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

+1, no questions asked. It is rare to find somebody with the passion that Diana has shown. From: Lin Hua Cheng > Reply-To: OpenStack List > Date: Tuesday, March 8, 2016 at

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

On 09/03/16 05:41, Johannes Grassler wrote: Hello, On 03/08/2016 04:57 PM, Zane Bitter wrote: On 08/03/16 10:40, Johannes Grassler wrote: On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins'

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

big +1 from me. She made a lot of contribution in making theming better for horizon and also prevented potential issues through reviews. Thanks for all the hard work, Diana. -Lin On Tue, Mar 8, 2016 at 2:06 PM, David Lyle wrote: > I propose adding Diana Whitten[1] to

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 3:17 PM, Matt Riedemann wrote: On 3/8/2016 1:18 PM, Amrith Kumar wrote: Matt, See inline below. -amrith -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent: Tuesday, March 08, 2016 2:00 PM To: openstack-dev@lists.openstack.org Subject:

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

On 8 March 2016 at 15:07, Doug Hellmann wrote: > Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > > Hi folks, > > > > There's a feature or two that are pending to be delivered in Mitaka > [1,2], > > and those involve changes to both the server and client

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On Mon, Mar 7, 2016 at 9:52 PM, Richard Jones wrote: > We've solved *most* of the issues around releasing new xstatic packages, > documented here[1] (and related documentation). > > We have one final issue that's blocking us, which is that during the > xstatic release

Re: [Openstack-operators] [openstack-operators][neutron] use-case for multiple routers within a tenant

Overlapping IPs. For a single tenant you might want to setup multiple copies of the exact same topology for testing, development, etc. On Tue, Mar 8, 2016 at 2:20 PM, Rubab Syed wrote: > Hi all, > > I am trying to get a general understanding of OpenStack networking. Can

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Tue, Mar 8, 2016 at 2:34 PM, Colette Alexander < colettealexan...@gmail.com> wrote: > So I laid out some of the questions I think the community could benefit > from alignment on in the etherpad I started already[0], but one of the > things that really struck me when talking to various members

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann wrote: > > > As I understood it when this course was originally proposed, the > idea was to have a few folks already in leadership positions go > take the training and evaluate it. Then, assuming the evaluation > was good, we

[openstack-dev] [neutron][taas] Proposal of Dashboard for TaaS

Thanks Soichi and Kaz for your work on implementing Horizon (dashboard) support for TaaS. The proposal (with screen shots) discussed in our recent IRC meeting look very nice. Here are some additional suggestions for improvement. 1. General a. When a port is being selected (for a

Re: [Openstack-operators] [openstack-operators][neutron] use-case for multiple routers within a tenant

Directing between different PCI environments. On March 8, 2016 5:20:46 PM EST, Rubab Syed wrote: >Hi all, > >I am trying to get a general understanding of OpenStack networking. Can >someone please point out a simple use-case for using multiple routers >within same tenant?

[Openstack-operators] [openstack-operators][neutron] use-case for multiple routers within a tenant

Hi all, I am trying to get a general understanding of OpenStack networking. Can someone please point out a simple use-case for using multiple routers within same tenant? Thanks, Rubab ___ OpenStack-operators mailing list

[openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

I propose adding Diana Whitten[1] to horizon-core. Diana is an active reviewer, contributor and community member. Over the past couple of releases, Diana has driven extensive changes around theme-ability in Horizon and drastically increased the standardization of our use of bootstrap. During this

[openstack-dev] [kolla][release] Announcing Kolla Mitaka-3 milestone release \o/

Fellow OpenStackers, The Kolla community is pleased to announce the release of Mitaka milestone #3. Angus Salkeld has agreed to be our release manager for the kolla-mesos repository. As an aside, we held our midcycle during mitaka-3 development, for which the notes can be found here:

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > Hi folks, > > There's a feature or two that are pending to be delivered in Mitaka [1,2], > and those involve changes to both the server and client sides. Ideally we'd > merge both sides in time for Mitaka RC and that implies that

Re: [Openstack] [openstack-announce] [OSSA 2016-007] Nova host data leak through resize/migration (CVE-2016-2140)

On 03/08/2016 08:16 PM, Tristan Cacqueray wrote: > === > OSSA-2016-007: Nova host data leak through resize/migration > === > > :Date: March 08, 2016 > :CVE: CVE-2016-2140 > > >

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

Excerpts from gordon chung's message of 2016-03-08 21:22:11 +: > > On 08/03/2016 6:25 AM, Chris Dent wrote: > > > > Last summer Lucas Gomes and I were press ganged into becoming core on > > WSME. Since then we've piecemeal been verifying bug fixes and generally > > trying to keep things

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

Thank you! I really appreciate being a part of Kolla project and now also core reviewers team! It is a pleasure to work with you guys. Thank you all for your support and help (especially for all -1 ;) ), wouldn't be here without you! Kind regards, Alicja PS best present for Women's Day ever!

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

Excerpts from Colette Alexander's message of 2016-03-01 14:41:01 -0800: > Hello Stackers, > > This is the continuation of an ongoing conversation within the TC about > encouraging the growth of leadership skills within the community that began > just after the Mitaka summit last year[1]. After

Re: [openstack-dev] [release] mitaka-3 development milestone

Corey Bryant wrote: neutron 8.0.0.0b3: https://tarballs.openstack.org/neutron/neutron-8.0.0.0b3.tar.gz https://tarballs.openstack.org/neutron-fwaas/neutron-fwaas-8.0.0.0b3.tar.gz https://tarballs.openstack.org/neutron-lbaas/neutron-lbaas-8.0.0.0b3.tar.gz

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

On 08/03/2016 6:25 AM, Chris Dent wrote: > > Last summer Lucas Gomes and I were press ganged into becoming core on > WSME. Since then we've piecemeal been verifying bug fixes and generally > trying to keep things moving. However, from the beginning we both agreed > that WSME is _not_ a web

[openstack-dev] [neutron] no upgrades meeting on March 14

Hi all, a lot of subteam folks will take part in the code sprint in Brno next Mon-Wed, so we’ll cancel the next meeting. Next meeting will occur March 21. Ihar __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 1:18 PM, Amrith Kumar wrote: Matt, See inline below. -amrith -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent: Tuesday, March 08, 2016 2:00 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [trove][stable] proboscis

Re: [openstack-dev] [TripleO] core members for tripleo-ui

On Mon, 2016-02-29 at 18:32 +0100, Ana Krivokapic wrote: > On Mon, Feb 29, 2016 at 4:27 PM, Dan Prince > wrote: > > > > There is a new projects for the ui called tripleo-ui. As most of > > the > > existing TripleO core members aren't going to be reviewing UI > > specific > >

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Tue, Mar 8, 2016 at 12:27 PM, Matt Riedemann wrote: > >> > So is this for only current TC members? What about people that aren't on > the TC? > > I asked in this in today's TC meeting but figured I'd ask here where it's > more global. Because of limited space in

[openstack-dev] [ceilometer] Could not get ceilometer events for instances running on demo tenant

I have a single node configuration for devstack liberty working and I want to record all the *ceilometer events* like compute.instance.start, compute.instance.end, compute.instance.update etc occurred recently. I am unable to get any event occurred for instances running for demo project i.e when I

[Openstack] [OSSA 2016-007] Nova host data leak through resize/migration (CVE-2016-2140)

=== OSSA-2016-007: Nova host data leak through resize/migration === :Date: March 08, 2016 :CVE: CVE-2016-2140 Affects ~~~ - Nova: <=2015.1.3, >=12.0.0 <=12.0.2 Description

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On 3/1/2016 4:41 PM, Colette Alexander wrote: Hello Stackers, This is the continuation of an ongoing conversation within the TC about encouraging the growth of leadership skills within the community that began just after the Mitaka summit last year[1]. After being asked by lifeless to do a

[openstack-dev] [magnum] SELinux is temporarily disabled due to bug 1551648

Hi team, FYI. In short, we have to temporarily disable SELinux [1] due to bug 1551648 [2]. SELinux is an important security features for Linux kernel. It improves isolation between neighboring containers in the same host. In before, Magnum had it turned on in each bay node. However, we have

[openstack-announce] [OSSA 2016-007] Nova host data leak through resize/migration (CVE-2016-2140)

=== OSSA-2016-007: Nova host data leak through resize/migration === :Date: March 08, 2016 :CVE: CVE-2016-2140 Affects ~~~ - Nova: <=2015.1.3, >=12.0.0 <=12.0.2 Description

Re: [openstack-dev] [release] mitaka-3 development milestone

On Fri, Mar 4, 2016 at 11:49 AM, Thierry Carrez wrote: > Hello everyone, > > The last milestone of the Mitaka development cycle, "mitaka-3", is now > reached. Some OpenStack projects following the milestone-based release > schedule took the opportunity to publish a

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

The vote was not exactly unanimous. I counted the following: 1.1.0 Steven Dake +1 Paul Bourke +1 Martin Andre +1 Michal Rostecki -1 Jeff Peeler +1 Ryan Hallisey +1 Michal Rosteki -1 Michal Jasterzebski -1 Since there are 6 votes in favor out of the 11 person core review team, 1.1.0 will

[openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

Hi folks, There's a feature or two that are pending to be delivered in Mitaka [1,2], and those involve changes to both the server and client sides. Ideally we'd merge both sides in time for Mitaka RC and that implies that we would be able to release a new version of the client including changes

Re: [openstack-dev] [qa] Tempest removal of tempest.api.compute.test_authorization

On 02/16/2016 03:38 PM, Matthew Treinish wrote: > On Tue, Feb 09, 2016 at 07:41:18PM -0500, Sean Dague wrote: >> As proposed in this patch - https://review.openstack.org/#/c/271467/ >> >> These tests do some manipulation of the request URI to attempt to >> request Nova resources owned by a

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

I don't think your example is right: "PKI will validate that token without going to any keystone server". How would it track revoked tokens? I'm pretty sure that they still get validated, they are stored in the DB even. I also disagree that there are different use cases. Just switch to fernet and

Re: [openstack-dev] [tripleo] CI jobs failures

On Tue, Mar 8, 2016 at 12:58 PM, Derek Higgins wrote: > We discussed this at today's meeting but never really came to a > conclusion except to say most people wanted to try it. The main > objection brought up was that we shouldn't go dropping the nonha job, > that isn't what I

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, See inline below. -amrith > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Tuesday, March 08, 2016 2:00 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly > failing in stable

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

See below. > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Tuesday, March 08, 2016 1:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly > failing in stable branches; bug 1538506 > >

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 12:52 PM, Matt Riedemann wrote: On 3/8/2016 12:35 PM, Amrith Kumar wrote: Matt, The correct solution for liberty is that we should fix the tests. Here's why I believe that this is the case. In pertinent part, the backtrace from your bug includes: 2016-01-27 07:02:06.777 |

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 12:35 PM, Amrith Kumar wrote: Matt, The correct solution for liberty is that we should fix the tests. Here's why I believe that this is the case. In pertinent part, the backtrace from your bug includes: 2016-01-27 07:02:06.777 | File

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Another tricky situation.. Given that changes to Docker were the cause of the first two backports I'd consider those to not be exceptions, but necessary adaptations that Kolla has to deal with. Unfortunately, this case seems more like an exception. But, I'm not opposed to a necessary

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Yes, it’s Database only — though we changed the agent driver in the DB from V1 to V2 — so if you bring up a V2 with that database it should reschedule all your load balancers on the V2 agent driver. German On 3/8/16, 3:13 AM, "Samuel Bercovici" wrote: >So this looks

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, The correct solution for liberty is that we should fix the tests. Here's why I believe that this is the case. In pertinent part, the backtrace from your bug includes: 2016-01-27 07:02:06.777 | File "/home/jenkins/workspace/periodic-trove-python27-liberty/trove/tests/api/replication.py",

[Openstack-operators] [openstacksummitaustin] Invite for OpenStack Operators Party, April 25

Hi there, Claire Massey from the OpenStack Foundation suggested that we circulate our Austin event here. Calling all operators. Join us at the OpenStack Operators Party hosted by Dell, Red Hat, Intel, Midokura and Cumulus Networks - Monday, April 25 in Austin Reserve your spot and forward to

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Exceptions can always be rationalized which is one reason exceptions are evil among many. The facts however speak for themselves. If we don't have a way to introduce new content in liberty when CVEs are fixed, stable/liberty is just as flawed as the data loss problem which was the original

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

The vote is unanimous. Welcome to the core reviewer team Alicja! Ping me when you get online next and our timezone overlaps, and I'll walk you through the differences in the gerrit interface you should know. I have made appropriate changes in gerrit. Regards -steve From: Steven Dake

[openstack-dev] [horizon] [searchlight] Horizon, Search, and Composability

Hello everybody, At the Horizon mid-cycle we had a lot of discussion on UI composability and searchability. Matt and Tyr provided a short presentation and demo at the mid-cycle. This morning I gave a more detailed presentation and demo via hangouts on air regarding Searchlight and Horizon. The

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/08/2016 11:58 AM, Derek Higgins wrote: > On 7 March 2016 at 18:22, Ben Nemec wrote: >> On 03/07/2016 11:33 AM, Derek Higgins wrote: >>> On 7 March 2016 at 15:24, Derek Higgins wrote: On 6 March 2016 at 16:58, James Slagle

Re: [openstack-dev] [tripleo] CI jobs failures

On 7 March 2016 at 18:22, Ben Nemec wrote: > On 03/07/2016 11:33 AM, Derek Higgins wrote: >> On 7 March 2016 at 15:24, Derek Higgins wrote: >>> On 6 March 2016 at 16:58, James Slagle wrote: On Sat, Mar 5, 2016 at 11:15 AM,

Re: [OpenStack-Infra] [Third-party-announce] Four Cisco CI systems are disabled

I had a consistent issue with zuul-merger failing to merge due to incorrect host keys set up by the community puppet modules. See https://review.openstack.org/#/c/266041/ for the fix, but note that we must have a newline at the end of the gerrit_ssh_host_key. You can easily confirm if you are

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are we ready?

Excerpts from Samuel Bercovici's message of 2016-03-02 07:06:30 -0800: > 2. HEAT Support - will it be ready in Mitaka? Side note, please remember, Heat is not an acronym. __ OpenStack Development Mailing List (not for

[openstack-dev] [oslo] oslo.messaging dispatching into private/protected methods?

Hi all, As I was working through https://review.openstack.org/#/c/288719/ for kevin benton to do some things with in neutron it came to my understanding that this code (the dispatcher code that is) can dispatch into nearly arbitrary callables of any object (or that is what it looks like it

Re: [OpenStack-Infra] [Third-party-announce] Four Cisco CI systems are disabled

The best way to determine why zuul is failing to merge changes is to check your zuul-merger debug log. If you are using the community puppet module these should end up in /var/log/zuul/merger-debug.log. When a merge fails the mergers should log the exact error from git in this log file. We run

Re: [Openstack-operators] What are you excited for in Mitaka?

Perhaps I was confused by the wording I found at http://docs.openstack.org/liberty/networking-guide/migration-classic-to-l3ha.html   I was looking for a way to do it on Kilo :( -jlk     - Original message -From: "Clayton O'Neill" To: Jesse Keating/Seattle/IBM@IBMUSCc:

Re: [OpenStack-Infra] InfraCloud Project, Weekly Status Update - March 7th 2016

On 03/07/2016 11:08 PM, Cody A.W. Somerville wrote: > InfraCloud Project, Weekly Status Update - March 7th 2016 > > Updates: > > 1. Relocation of HW: > a. All HW in "US East" was shipped as of today, March 7th. > b. Shipment of HW in "US West" is delayed. > > Risks: > > 1. "US West" HW now

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Does it work with DVR though? Probably would with Octavia since they are just vm's. Thanks, Kevin From: Eichberger, German [german.eichber...@hpe.com] Sent: Monday, March 07, 2016 4:11 PM To: OpenStack Development Mailing List (not for usage questions)

Re: [OpenStack-Infra] [Third-party-announce] Four Cisco CI systems are disabled

Moving this post to the openstack-infra mailing list thread for discussion. The third-party-announce thread is meant to be low traffic for contacting third party ci operators. Discussion of third party tools and systems are to take place on the openstack-infra mailing list.

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, As I just said in my earlier reply to you, Craig has been away for some time and I'll look into this. I don't know that we need to revert the change or take the route you propose. There may be a much simpler solution. I'll propose a change for your review. -amrith > -Original

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

On 08/03/16 08:03, Johannes Grassler wrote: Hello, On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins' add_dependencies() methods] Yes, you're right and this sucks. That's not the only problem we've had in

  1   2   >