Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

Steven Dake (stdake) wrote: If it does have some special meaning or requirements beyond the "we will freeze on the freeze deadline" could someone enumerate those? Short answer is: release:managed doesn't mean that much anymore (all official projects are "managed"), so we'll likely retire it

[openstack-dev] [neutron][taas] Taas can not capture the packet, if the two VM on the same host. Is it a Bug?

Hi , I found a limitation when use taas. My test case is descripped as follow: VM1 and VM2 is running on the same host and they are belong the vlan. The monitor VM is on the same host or the other host . I want to monitor the only INPUT flow to the VM1. So I configure the tap-flow

[openstack-dev] [openstack-ansible] When to purge the DB, and when not to purge the DB?

Hi everyone, In a recent conversation on the Operators list [1] there was a discussion about purging archived data in the database. It would seem to me an important step in maintaining an environment which should be done from time to time and perhaps at the very least prior to a major upgrade.

[openstack-dev] [Fuel][QA] fuel-devops bridge and interface names

Hi to all, This message is related to upcoming changes in fuel-devops project. Race condition issue was found in scenario where multiple environments are being created at the same time. Networks or node interfaces recive the same name in different environmens and this leads to error. This

[openstack-dev] [tripleo][infra] RH2 is up and running

Hi All, Yesterday the final patch merged to run CI jobs on RH2, and last night we merged the patch to tripleo-ci to support RH2 jobs. So we now have a new job (gate-tripleo-ci-centos-7-ovb-ha) running on all tripleo patch reviews. This job is running pacemaker HA with a 3 node controller and a

[openstack-dev] [tricircle]tricircle wiki update

Hello, team, The wiki page of Tricircle was updated in the architecture and value section, other sections also with minor update Please review and comment, and update accordingly for obvious error. If you have any question and topic to discuss, also let's discussion in the m-l. Thanks Sent

[openstack-dev] [osc][openstackclient][all] time to make the check-osc-plugins job voting?

There's a whole bunch of OpenStackClient plugins now (17 to be exact). With [1] now merged, we run a non-voting job (check-osc-plugins) on each plugin to check for commands that may conflict with each other. It tests the master branch of each plugin, so we'll catch errors before the release. The

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

Hi, talking about live-migration job. If you are OK to re-run tempest tests multiple times on single environment you could wrap this line: https://github.com/openstack/nova/blob/master/nova/tests/live_migration/hooks/run_tests.sh#L30 in for-cycle. Timofey. On Fri, Jul 1, 2016 at 10:31 AM,

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

Hi all, Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented we’ve requested a final tag [1]. Once that merges we are ready to have our kilo-eol tag implemented and the ‘kilo’ branch removed. Just to make life interesting, we still have leftover ‘juno’ and ‘icehouse’

Re: [openstack-dev] [neutron][calico] New networking-calico IRC meeting

The first networking-calico IRC meeting was planned for 28th June, but I'm afraid I was unwell - so it will now be 12th July. I've updated the agenda [2] accordingly. Neil On Mon, Jun 20, 2016 at 3:42 PM Neil Jerram wrote: > Calling everyone interested in networking-calico

Re: [openstack-dev] [ansible] Fail to install Openstack all in one

On Thu, Jun 23, 2016 at 8:47 AM, Alioune > wrote: I'm trying to install OpenStack all in one using ansible but I got the error bellow. Someone knows how to solve this error? Regards, ERROR: + openstack-ansible --forks 1 openstack-hosts-setup.yml

Re: [openstack-dev] [kolla][vote] Apply for release:managed tag

On 6/30/16, 8:26 PM, "Tony Breeds" wrote: >On Fri, Jul 01, 2016 at 12:56:09AM +, Steven Dake (stdake) wrote: >> Hey folks, >> >> I'd like the release management team to take on releases of Kolla. This >> means applying for the release:managed[1] tag. Please vote

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented we’ve requested a final tag [1]. Once that merges we are ready to have our kilo-eol tag implemented and the ‘kilo’ branch removed. Whoops – I forget to add the link to the final Kilo tag request. [1]

Re: [openstack-dev] [neutron][calico] New networking-calico IRC meeting

Thanks, Carl. I had the same observation, so would also be interested in the answer. Neil On Thu, Jun 30, 2016 at 9:15 PM Carl Baldwin wrote: > On Mon, Jun 20, 2016 at 8:42 AM, Neil Jerram wrote: > > Calling everyone interested in networking-calico

Re: [openstack-dev] [keystone][openid][mistral] Enabling OpenID Connect authentication w/o federation

On 23 June 2016 at 21:30, Renat Akhmerov wrote: > Hi, > > I’m looking for some hints on how to enable authentication via OpenID > Connect protocol, particularly in Mistral. Actually, specific protocol is > not so important. I’m mostly interested in conceptional vision

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

> On 30 Jun 2016, at 16:07, Steven Dake (stdake) wrote: > > Hey folks, > > I am keen on tagging Kolla in the governance repository with every tag that > is applicable to our project. One of these is release:managed. I've been > working as PTL the last 3 cycles to get

Re: [openstack-dev] [keystone][openid][mistral] Enabling OpenID Connect authentication w/o federation

Jamie, Thanks a lot for your detailed answer. We’ll think again about all that taking your comments into account. Renat Akhmerov @Nokia > On 01 Jul 2016, at 13:10, Jamie Lennox wrote: > > > > On 23 June 2016 at 21:30, Renat Akhmerov

Re: [openstack-dev] [swift] Support for unicode filename in tempurl middleware

Hi, at the end I figured the problem out. It was the very same bug of the python-swiftclient, missing encoding for utf-8. I encoded the hmac_body with utf8 (but not URI encoding) and the tempURL is now valid! Thank you for the support! Best Antonio On Wed, Jun 29, 2016 at 9:40 PM, Antonio

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

This is some neat work. I like it. We have a graph of nodepool nodes in use in grafana[1]. Looking at a 30 day window, its pretty easy to tell that the weekends are low activity. Running big tests like this on a Saturday would be great. Of course, there won't be much infra support on that day.

Re: [openstack-dev] [FUEL]Network verification failed.

Hi I guess, this doc[1] will be more useful - since Samer use fuel 8.0 [1] https://community.mellanox.com/docs/DOC-2435 On Thu, Jun 30, 2016 at 6:18 PM, Yuki Nishiwaki wrote: > Hello Samer > > Did you read this reference (https://community.mellanox.com/docs/DOC-2036) > ?

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

On Thu, Jun 30, 2016 at 02:44:36PM +0100, Daniel P. Berrange wrote: [Snip description of some nice debugging.] > I'd really love it if there was > > 1. the ability to request checking of just specific jobs eg > > "recheck gate-tempest-dsvm-multinode-full" Yes, this would really be

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

Have you considered just writing a throwaway devstack-gate change which overrides the gate_hook to run that one suspect Tempest test, say, a thousand times in a loop? Would be far more efficient if you don't need to be concerned with all the environment setup/teardown overhead. -- Jeremy Stanley

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

On Fri, Jul 1, 2016 at 3:26 PM, Monty Taylor wrote: > On 07/01/2016 08:10 AM, Antoni Segura Puimedon wrote: > > Hi fellow kuryrs! > > > > In order to proceed with the split of kuryr into a main lib and it's > kuryr > > libnetwork component, we've cloned the contents of

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

On 06/30/2016 01:55 PM, HU, BIN wrote: > I see, and thank you very much Dan. Also thank you Markus for unreleased > release notes. > > Now I understand that it is not a plugin and unstable interface. And there is > a new "use_neutron" option for configuring Nova to use Neutron as its network >

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

On Fri, Jul 1, 2016 at 3:10 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > Hi fellow kuryrs! > > In order to proceed with the split of kuryr into a main lib and it's kuryr > libnetwork component, we've cloned the contents of openstack/kuryr over to >

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

On 07/01/2016 08:10 AM, Antoni Segura Puimedon wrote: > Hi fellow kuryrs! > > In order to proceed with the split of kuryr into a main lib and it's kuryr > libnetwork component, we've cloned the contents of openstack/kuryr over to > openstack/kuryr-libnetwork. > > The idea is that after this, the

Re: [openstack-dev] [manila] nfs-ganesha export modification issue

On Thu, Jun 30, 2016 at 1:37 PM, Alexey Ovchinnikov wrote: > Hello everyone, > > here I will briefly summarize an export update problem one will encounter > when using nfs-ganesha. > > While working on a driver that relies on nfs-ganesha I have discovered that > it > is

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

On 2016-07-01 11:24:27 +0200 (+0200), Thierry Carrez wrote: > Short answer is: release:managed doesn't mean that much anymore (all > official projects are "managed"), so we'll likely retire it ASAP. [...] If the meaning has been reduced to "this project is allowed to request tagging by the

[openstack-dev] [kuryr] kuryr-libnetwork split

Hi fellow kuryrs! In order to proceed with the split of kuryr into a main lib and it's kuryr libnetwork component, we've cloned the contents of openstack/kuryr over to openstack/kuryr-libnetwork. The idea is that after this, the patches that will go to openstack/kuryr will be to trim out the

[openstack-dev] [fuel][nailgun-agent] Announcement of massive changes in fuel-nailgun-agent

Greetings! Today we did a big change which might be invasive. We replaced ohai with facter in fuel-nailgun-agent [1]. There were a couple reasons why we did that: 1. Fuel project uses facter very intensively. However, ohai and facter have similar purpose and functionality. We were lack of some

Re: [openstack-dev] [Nova][Neutron][Live-Migration] Cross l2 agent migration and solving Nova-Neutron live migration bugs

> -Original Message- > From: Carl Baldwin [mailto:c...@ecbaldwin.net] > Sent: 29 June 2016 22:20 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Nova][Neutron][Live-Migration] Cross l2 agent >

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

On 2016-07-01 15:39:10 +0200 (+0200), Kashyap Chamarthy wrote: > [Snip description of some nice debugging.] > > > I'd really love it if there was > > > > 1. the ability to request checking of just specific jobs eg > > > > "recheck gate-tempest-dsvm-multinode-full" > > Yes, this would

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 6/30/2016 11:10 AM, Chris Friesen wrote: For what it's worth, this is how the timestamps work for POSIX filesystems. When you create a file it sets the access/modify/change timestamps to the file creation time. Chris

[openstack-dev] [nova][scheduler] No meeting this Monday, July 4

Due to the US Independence Day holiday, we will be skipping the Nova Scheduler subteam meeting on this upcoming Monday, July 4. The next meeting will be July 11 at 1400 UTC [0]. [0] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160711T14 -- Ed Leafe

Re: [openstack-dev] [Zaqar] Nominate Thomas Herve for Zaqar core

Thomas contributions have been very useful to Zaqar. Big +1! 2016-07-01 1:17 GMT-03:00 王玺源 : > +1, Thomas did a great job on Zaqar. As we can see, many important feature > are done by him. > > Welcome, thomas. > > 2016-07-01 6:33 GMT+08:00 Emilien Macchi

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

On Fri, Jul 01, 2016 at 02:35:34PM +, Jeremy Stanley wrote: > On 2016-07-01 15:39:10 +0200 (+0200), Kashyap Chamarthy wrote: > > [Snip description of some nice debugging.] > > > > > I'd really love it if there was > > > > > > 1. the ability to request checking of just specific jobs eg > > >

[openstack-dev] [Bilean][CloudKitty][Telemetry] Open discussion around Bilean and existing OpenStack components

Hi, I would like to continue the discussion that started in the [review][1] for the Big-Tent integration of the project Bilean. In the [review][1] the Bilean team stated that a new project was needed to overcome limitations of existing components. In this thread, I would like to have an open

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

On 07/01/2016 12:05 PM, Jeremy Stanley wrote: > On 2016-07-01 20:59:06 +0530 (+0530), Vikas Choudhary wrote: >> There seems to be some problem with. I cloned kuryr-libnetwork: >> >>> git clone http://github.com/openstack/kuryr-libnetwork.git >> >> >> But when pushed patch, on gerrit its showing

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

Hi Toni, There seems to be some problem with. I cloned kuryr-libnetwork: > git clone http://github.com/openstack/kuryr-libnetwork.git But when pushed patch, on gerrit its showing project "openstack/kuryr" PTAL, https://review.openstack.org/#/c/336617/ -Vikas On Fri, Jul 1, 2016 at 6:40

Re: [openstack-dev] Gerrit downtime on 1 July 2016 at 20:00 UTC

On Tue, Jun 21, 2016 at 1:11 PM, Elizabeth K. Joseph wrote: > Hi everybody, > > On 1 July 2016 at 20:00 UTC Gerrit will be unavailable for > approximately 120 minutes (2 hours) while we upgrade > zuul.openstack.org and static.openstack.org to Ubuntu Trusty. > > During this

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

This option is already available for live-migration job, as it's hooks are under nova project. On Fri, Jul 1, 2016 at 5:13 PM, Jeremy Stanley wrote: > Have you considered just writing a throwaway devstack-gate change > which overrides the gate_hook to run that one suspect

Re: [openstack-dev] [Nova][Neutron][Live-Migration] Cross l2 agent migration and solving Nova-Neutron live migration bugs

On Fri, Jul 1, 2016 at 8:34 AM, Murray, Paul (HP Cloud) wrote: >> -Original Message- >> From: Carl Baldwin [mailto:c...@ecbaldwin.net] >> Sent: 29 June 2016 22:20 >> To: OpenStack Development Mailing List (not for usage questions) >> >>

[openstack-dev] [designate][charms] Synchronising domains with new bind9 server

Hi, I'm trying to add a new bind9 pool_target to an existing pool. The problem is that the new bind server has no knowledge of the existing zones as it missed the addzone commands when the domains where created. It seems to me I have 3 options: 1) To sync the zone + nzf files from an existing

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

On 2016-07-01 20:59:06 +0530 (+0530), Vikas Choudhary wrote: > There seems to be some problem with. I cloned kuryr-libnetwork: > > > git clone http://github.com/openstack/kuryr-libnetwork.git > > > But when pushed patch, on gerrit its showing project "openstack/kuryr" > > PTAL,

Re: [openstack-dev] [security] [horizon] Security implications of exposing a keystone token to a JS client

I am not sure if this is a valid concern. If I am using a CLI and someone gets access to my computer, they can do whatever they well please. If I am using Horizon and someone gets access, its going to be the same story, they can still do damage even without knowing the token (at least until the

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

Did this resolve the problem? https://review.openstack.org/#/c/336549/ From: Vikas Choudhary To: Antoni Segura Puimedon Cc: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

Excerpts from Jeremy Stanley's message of 2016-07-01 15:05:30 +: > On 2016-07-01 08:26:13 -0500 (-0500), Monty Taylor wrote: > [...] > > Check with Doug Hellman about namespaces. We used to use them in some > > oslo things and had to step away from them because of some pretty weird > > and

Re: [openstack-dev] [kolla][ironic] My thoughts on Kolla + BiFrost integration

Maybe I missed it - but is there a way to provide site specific configurations? Things we will run into in the wild include: Configuring multiple non-openstack nics IPMI configuration Password integration with Corporate LDAP etc. Integration with existing SANs Integration

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

On 7/1/16, 11:18 AM, "Doug Hellmann" wrote: >Excerpts from Jeremy Stanley's message of 2016-07-01 13:50:30 +: >> On 2016-07-01 11:24:27 +0200 (+0200), Thierry Carrez wrote: >> > Short answer is: release:managed doesn't mean that much anymore (all >> > official

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

Excerpts from Steven Dake (stdake)'s message of 2016-07-01 18:42:47 +: > > On 7/1/16, 11:18 AM, "Doug Hellmann" wrote: > > >Excerpts from Jeremy Stanley's message of 2016-07-01 13:50:30 +: > >> On 2016-07-01 11:24:27 +0200 (+0200), Thierry Carrez wrote: > >> >

Re: [openstack-dev] [all][Python 3.4-3.5] Async python clients

Excerpts from Denis Makogon's message of 2016-06-26 15:56:14 +0300: > Hello stackers. > > > I know that some work in progress to bring Python 3.4 compatibility to > backend services and it is kinda hard question to answer, but i'd like to > know if there are any plans to support asynchronous

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

On 2016-07-01 14:18:13 -0400 (-0400), Doug Hellmann wrote: [...] > The "release:managed" tag used to convey information about how much > the release team did for the project team in a way that was (we > hoped) useful to consumers of the project. That included things we > no longer do at all for

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 07/01/2016 10:37 AM, Matt Riedemann wrote: > On 6/30/2016 11:10 AM, Chris Friesen wrote: >> >> For what it's worth, this is how the timestamps work for POSIX >> filesystems. When you create a file it sets the access/modify/change >> timestamps to the file creation time. >> >> Chris >> >>

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

Excerpts from Jeremy Stanley's message of 2016-07-01 13:50:30 +: > On 2016-07-01 11:24:27 +0200 (+0200), Thierry Carrez wrote: > > Short answer is: release:managed doesn't mean that much anymore (all > > official projects are "managed"), so we'll likely retire it ASAP. > [...] > > If the

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On 6/28/2016 4:56 PM, Sean Dague wrote: On 06/28/2016 01:46 AM, Angus Lees wrote: Ok, thanks for the in-depth explanation. My take away is that we need to file any rootwrap updates as exceptions for now (so releasenotes and grenade scripts). That is definitely the fall back if there is no

Re: [openstack-dev] [neutron][calico] New networking-calico IRC meeting

Sorry I missed it. I will plan to listen in on the 12th. It will be nice to have the ICS available by then. You should probably check with the @openstack-infra channel to see what the issue is. Carl On Fri, Jul 1, 2016 at 5:31 AM, Neil Jerram wrote: > The first

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

On Fri, Jul 01, 2016 at 02:13:46PM +, Jeremy Stanley wrote: > Have you considered just writing a throwaway devstack-gate change > which overrides the gate_hook to run that one suspect Tempest test, > say, a thousand times in a loop? Would be far more efficient if you > don't need to be

Re: [openstack-dev] [ovs-dev] The QoS feature minimum guaranteed bandwidth of OpenvSwitch not work

On Fri, Jul 01, 2016 at 03:40:30AM +, Xiao Ma (xima2) wrote: > I want to use the QoS feature of OpenvSwitch to control the bandwidth based > on the vlan id(Scene 1) or port id(Scene 2). > So I deployed it as showed bellow,and configured the qos rules,the flows,and > used iperf tool to test

Re: [openstack-dev] [trove] OpenStack Trove Ocata Virtual Midcycle,

Hello Amrith, Just wanted to confirm that I can attend the virtual midcycle during the proposed dates: July 26th-28th. Thank you. Regards, Mariam. From: Amrith Kumar To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] Openstack Mitaka Neutron LBaaS Question

Dear OpenStack Dev member: May I ask you some question about neutron lbaaS? How to install the neutron LBaaS with Octavia in Mitaka?I followed these two guide ,but which one I should use? (My openstack is Mitaka , 1 controller, 2 compute nodes)

Re: [openstack-dev] [Nova] Deprecated Configuration Option in Nova Mitaka Release

On 30 June 2016 at 10:55, HU, BIN wrote: > I see, and thank you very much Dan. Also thank you Markus for unreleased > release notes. > > Now I understand that it is not a plugin and unstable interface. And there > is a new "use_neutron" option for configuring Nova to use Neutron

Re: [openstack-dev] [designate][charms] Synchronising domains with new bind9 server

On 01/07/2016 18:04, Liam Young wrote: > Hi, > > I'm trying to add a new bind9 pool_target to an existing pool. The > problem is that the new bind server has no knowledge of the existing > zones as it missed the addzone commands when the domains where created. > It seems to me I have 3 options: >

Re: [openstack-dev] [security] [horizon] Security implications of exposing a keystone token to a JS client

On 06/29 at 21:10, Timur Sufiev wrote: > Hello, vigilant folks of OpenStack Security team! > > The commit(s) I'd like you to take a look at introduces a new Horizon > feature, Create (Glance) Image using CORS (AKA Cross-Origin Resource > Sharing) [1]. > > The main idea is to bypass Horizon

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 06/30/2016 08:31 AM, Andrew Laski wrote: > > > On Wed, Jun 29, 2016, at 11:11 PM, Matt Riedemann wrote: >> On 6/29/2016 10:10 PM, Matt Riedemann wrote: >>> On 6/29/2016 6:40 AM, Andrew Laski wrote: On Tue, Jun 28, 2016, at 09:27 PM, Zhenyu Zheng wrote: > How about I

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 7/1/2016 1:32 PM, Sean Dague wrote: On 06/30/2016 08:31 AM, Andrew Laski wrote: On Wed, Jun 29, 2016, at 11:11 PM, Matt Riedemann wrote: On 6/29/2016 10:10 PM, Matt Riedemann wrote: On 6/29/2016 6:40 AM, Andrew Laski wrote: On Tue, Jun 28, 2016, at 09:27 PM, Zhenyu Zheng wrote: How

[openstack-dev] [nova] Non-priority feature freeze and FFEs

We're now past non-priority feature freeze. I've started going through some blueprints and -2ing them if they still have outstanding changes. I haven't gone through the full list yet (we started with 100). I'm also building a list of potential FFE candidates based on: 1. How far along the

[openstack-dev] [manila][stable] liberty periodic bitrot jobs have been failing more than a week

The manila periodic stable/liberty jobs have been failing for at least a week. It looks like manila isn't using upper-constraints when running unit tests, not even on stable/mitaka or master. So in liberty it's pulling in uncapped oslo.utils even though the upper constraint for oslo.utils in

[openstack-dev] [searchlight] Mid Cycle Hangout

At our last IRC meeting, we discussed that there were a few topics which could use some high bandwidth conversation, in particular the pipeline architecture [0] as well as reviewing progress for the release. Since we are not having a face to face meetup which would exclude people unable to

Re: [openstack-dev] [openstack-ansible] When to purge the DB, and when not to purge the DB?

-Original Message- From: Jesse Pretorius Reply: OpenStack Development Mailing List (not for usage questions) Date: July 1, 2016 at 04:45:17 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] New Python35 Jobs coming

The infra team is working on taking advantage of the new Ubuntu Xenial release including running unittests on python35. The current plan is to get https://review.openstack.org/#/c/336272/ merged next Tuesday (July 5, 2016). This will add non voting python35 tests restricted to >= master/Newton on

[openstack-dev] [Neutron][L2 Gateway] No meeting on July 4th

Folks, Due the US holiday on 4th of July, there will be no meeting for L2 Gateway. The channel will be available for anybody to use, should you need to discuss anything during the meeting's time slot. Happy 4th.. -Sukhdev

[openstack-dev] [Ironic][Neutron] No Ironic-Neutron Integration meeting on July 4th

Folks, Due the US holiday on 4th of July, there will be no meeting on Ironic-Neutron Integration. The channel will be available for anybody to use, should you need to discuss anything during the meeting's time slot. Happy 4th.. -Sukhdev

Re: [openstack-dev] New Python35 Jobs coming

Excerpts from Clark Boylan's message of 2016-07-01 12:51:52 -0700: > The infra team is working on taking advantage of the new Ubuntu Xenial > release including running unittests on python35. The current plan is to > get https://review.openstack.org/#/c/336272/ merged next Tuesday (July > 5, 2016).

Re: [openstack-dev] [manila][stable] liberty periodic bitrot jobs have been failing more than a week

Thanks Matt. https://review.openstack.org/#/c/334220 adds the upper constraints. -- Goutham On 7/1/16, 5:08 PM, "Matt Riedemann" wrote: The manila periodic stable/liberty jobs have been failing for at least a week. It looks like manila isn't using

Re: [openstack-dev] [kolla] Build the docker images in a graceful way

Hi all, the spec is here[0] [0] https://review.openstack.org/336757 On Wed, Jun 29, 2016 at 9:44 PM, Jeffrey Zhang wrote: > > On Wed, Jun 29, 2016 at 9:26 PM, Gerard Braad wrote: > >> Although I saw the Ansible Container repo, I wasn't that excited

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

On 2016-07-01 08:26:13 -0500 (-0500), Monty Taylor wrote: [...] > Check with Doug Hellman about namespaces. We used to use them in some > oslo things and had to step away from them because of some pretty weird > and horrible breakage issues. [...] Or read the associated Oslo spec from when that

Re: [openstack-dev] [security] [horizon] Security implications of exposing a keystone token to a JS client

Hi David, How do you feel about the approach here: https://review.openstack.org/#/c/311189/ Its lets the existing angular js module: horizon.app.core.openstack-service-api.keystone access the current token via getCurrentUserSession().token Thanks, Kevin

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

Thanks Banix, Actually after noticing this patch i pushed my changes on top this, linked with dependency and that worked. On Fri, Jul 1, 2016 at 11:14 PM, Mohammad Banikazemi wrote: > Did this resolve the problem? https://review.openstack.org/#/c/336549/ > > [image: Inactive