Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Excerpts from Doug Hellmann's message of 2016-06-23 08:37:04 -0400: > Excerpts from Doug Hellmann's message of 2016-06-13 15:11:17 -0400: > > I'm trying to pull together some information about contributions > > that OpenStack community members have made *upstream* of OpenStack, > > via code, docs,

[openstack-dev] [openstack-ansible] Change of default database collation

Hi all, OpenStack-Ansible has been configuring the default database collation as 'utf8_unicode_ci'. We've recently run into an issue with new deployments during cinder database migrations where a foreign key column had different a collation between the parent and child table[1]. That's since

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On 06/23/2016 Daniel Berrange wrote (lost attribution in thread): > Our long term goal is that 100% of all network storage will be connected > to directly by QEMU. We already have the ability to partially do this with > iSCSI, but it is lacking support for multipath. As & when that gap is >

[openstack-dev] What's Up, Doc? 24 June 2016

Hi everyone, We're starting to see a real rush of projects publishing their Install Guides this week, which is really exciting! We're also working on getting the index page on docs.openstack.org up and running, so we should have that ready to go up by the time I'm writing this newsletter next

[openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

Hi Team, As already discussed with some of teammates over irc and internally, thought of bringing discussionto ml for more opinions: My idea on repo structure is something similar to this: kuryr └── controller │ ├── api (running on controller node(cluster master or openstack controller node),

[openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

hi all, in openstack, we can use the pci passthrough feature now, refer to https://wiki.openstack.org/wiki/Pci_passthrough but we can't definitely specify the host pci driver is LEGACY_KVM or newer VFIO, new VFIO driver is more safer, and higher-performance user-space driver

Re: [openstack-dev] [oslo][monasca][requirements] Kafka 1.x for Oslo.Messaging and Monasca

On Wed, Jun 22, 2016 at 05:34:27AM +, Keen, Joe wrote: > Davanum, > We started work on getting Monasca into the global requirements with two > reviews [1] [2] that add gate jobs and check requirements jobs for the > Monasca repositories. Some repositories are being adapted to use versions >

Re: [openstack-dev] [keystone] [stable/mitaka] Error: Discovering versions from the identity service failed when creating the password plugin....

On Tue, Jun 21, 2016 at 10:27:28AM +0530, mohammad shahid wrote: > Hi, > > I am getting below error while starting openstack devstack with > stable/mitaka release. can someone look at this problem ? so I *think* you're trying to deploy stable/mitaka with the master version of devstack. Please

[openstack-dev] [cinder]restore method while ceph backup backend is used

Hi all, This is Liu Qing, new to this community. I have a question about the ceph backup backend. >From the cinder/backup/manager.py, the restore process is done by attach the original device(restore dest) to the cinder service host. And in the ceph driver the full_restore will discard the

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

On Wed, Jun 22, 2016 at 03:23:43PM +1000, Tony Breeds wrote: > On Wed, Jun 22, 2016 at 06:45:31AM +0200, Haïkel wrote: > > Hi, > > > > as a packager, I spend a lot of time to scrutinize the requirements > > repo, and I find it easier to read if specifiers are ordered. > > So in a quick glance,

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

Hey folks, I created the following sequence diagram to show my thinking on Ironic integration. I recognize some internals of the recently merged bifrost changes are not represented in this diagram. I would like to see a bootstrap action do all of the necessary things to bring up BiFrost in a

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

+1 on the idea of running function tests to see the fallout. Right now python-memcached is labelled as py3 compatible and in keystone our unit tests pass, but I'm skeptical about its behavior in functional and tempest tests. On Jun 23, 2016 1:14 PM, "Sean Dague" wrote: So, given

Re: [openstack-dev] [ironic] Gate troubleshooting howto

I dropped this Friday as an option based on the results. If you're interested this will still be happening, but in mid-July. Thanks, Jay Faulkner OSIC > On Jun 22, 2016, at 12:39 PM, Jay Faulkner wrote: > > There was a request at the mid-cycle for a presentation on >

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On 06/22/2016 01:56 PM, Paul Michali wrote: I did have a question about the current implementation as described by 292499, 324379, and 292500. Looking at the code, when a NUMAPagesTopology object is create, a new parameter is passed for the "reserved" pages. This reservation comes from a

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On 06/22/2016 01:56 PM, Paul Michali wrote: I did have a question about the current implementation as described by 292499, 324379, and 292500. Looking at the code, when a NUMAPagesTopology object is create, a new parameter is passed for the "reserved" pages. This reservation comes from a

[openstack-dev] [vitrage][aodh] Notifications about aodh alarm state changes

Hi Julien, Gordon, I understood that during Aodh-Vitrage design session in Austin, you had a discussion about Vitrage need for notifications about Aodh alarm state changes. Did you have a chance to think about it since, and to check how this can be done? Thanks, Ifat.

Re: [openstack-dev] [kolla] better solution for the non-ini format configure file

I looked more at this solution and am struggling to come up with a solution for: https://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/config.yml#L69-L85 That doesn't involve creating

Re: [openstack-dev] [lbaas]HA for lbaas v2 agent

As Assaf mentioned, namespace and octavia are two different lbaas drivers. But within those: - The lbaas plugin will schedule lbaas VIPs from all available lbaas-agents (I think it’s random.) No, you can’t move them later, or override the scheduler. - The lbaas agent is used by the octavia

Re: [openstack-dev] [lbaas]HA for lbaas v2 agent

On Thu, Jun 23, 2016 at 3:43 PM, Akshay Kumar Sanghai wrote: > Thanks Assaf. > I have few questions for lbaas: > - if i run agents on multiple nodes, will the request be ditrsibuted by > neutron-server? > - Does neutron lbaas agent forward the request to octavia-api

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: > Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: > > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > > I'd like for the community to set a goal for Ocata to have Python > > > 3 functional tests running for all projects.

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > I'd like for the community to set a goal for Ocata to have Python > > 3 functional tests running for all projects. > > > > As Tony points out, it's a bit late to have this as a

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On 06/23/2016 06:11 PM, Doug Hellmann wrote: > I'd like for the community to set a goal for Ocata to have Python > 3 functional tests running for all projects. > > As Tony points out, it's a bit late to have this as a priority for > Newton, though work can and should continue. But given how close

[openstack-dev] [release] Release countdown for week R-15, Jun 20-24

Focus - Teams should be working on new feature development and bug fixes in this period between the first and second milestones. General Notes - The members of the release team will all be traveling next week. This will result in delays in releases being processed, so please

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Wed, Jun 22, 2016, at 09:07 AM, Chris Dent wrote: > On Tue, 21 Jun 2016, Sylvain Bauza wrote: > > > To be honest, Chris and you were saying that you don't like Flask, and I'm > > a > > bit agreeing with you. Why now it's a good possibility ? > > As I said when I started the other version of

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Thu, Jun 23, 2016 at 12:07:43PM -0600, Chris Friesen wrote: > On 06/23/2016 10:09 AM, Walter A. Boring IV wrote: > > > >volumes connected to QEMU instances eventually become directly connected? > > > >>Our long term goal is that 100% of all network storage will be connected > >>to directly by

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Thu, Jun 23, 2016 at 09:50:11AM -0700, Preston L. Bannister wrote: > Daniel, Thanks. Looking for a sense of direction. > > Clearly there is some range of opinion, as Walter indicates. :) > > Not sure you are get to 100% direct connection to QEMU. When there is > dedicated hardware to do

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Thu, Jun 23, 2016 at 12:58:23PM -0400, Davanum Srinivas wrote: +1 from me as well. I get questions on support for these often enough. > +1 from me as well Doug! ("community to set a goal for Ocata to have Python > 3 functional tests running for all projects.") > > -- Dims > > On Thu, Jun

Re: [openstack-dev] [TripleO] CI package build issues

On 06/23/2016 02:56 PM, Dan Prince wrote: > After discovering some regressions today we found what we think is a > package build issue in our CI environment which might be the cause of > our issues: > > https://bugs.launchpad.net/tripleo/+bug/1595660 > > Specifically, there is a case where

Re: [openstack-dev] [lbaas]HA for lbaas v2 agent

Thanks Assaf. I have few questions for lbaas: - if i run agents on multiple nodes, will the request be ditrsibuted by neutron-server? - Does neutron lbaas agent forward the request to octavia-api or the neutron-server? Thanks Akshay On Thu, Jun 23, 2016 at 1:00 AM, Assaf Muller

[openstack-dev] [ironic] Ironic Newton midcycle sprint summary

Dear group, Please enjoy this midcycle sprint summary. You might have to put your Markdown glasses on for proper formatting :) The midcycle sprint lasted three days. It was virtually held over Infra's conference system and IRC. The event was split in two different time slots. The first

[openstack-dev] [TripleO] CI package build issues

After discovering some regressions today we found what we think is a package build issue in our CI environment which might be the cause of our issues: https://bugs.launchpad.net/tripleo/+bug/1595660 Specifically, there is a case where DLRN might not be giving an error code if build failures

[openstack-dev] [new][release] reno 1.8.0 release

We are satisfied to announce the release of: reno 1.8.0: RElease NOtes manager With source available at: http://git.openstack.org/cgit/openstack/reno Please report issues through launchpad: http://bugs.launchpad.net/reno For more details, please see below. Changes in reno

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On 06/23/2016 10:09 AM, Walter A. Boring IV wrote: volumes connected to QEMU instances eventually become directly connected? Our long term goal is that 100% of all network storage will be connected to directly by QEMU. We already have the ability to partially do this with iSCSI, but it is

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

So, given that everything in base iaas is over besides Nova, and there is some python 3 support in Devstack, before Newton is over one could get a python 3 (except Nova) job running, and start seeing the fallout of full stack testing. We could even prioritize functional changes in Nova to get full

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Excerpts from Ihor Dvoretskyi's message of 2016-06-23 19:47:32 +0300: > Doug, nice work, thank for collecting these items. > > I'd like to suggest adding Kubernetes as one of the container projects, > that is actively contributed by people from the OpenStack world. Within the > Kubernetes

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

+1 from me as well Doug! ("community to set a goal for Ocata to have Python 3 functional tests running for all projects.") -- Dims On Thu, Jun 23, 2016 at 12:11 PM, Doug Hellmann wrote: > Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: >> On

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On 06/23/2016 11:11 AM, Doug Hellmann wrote: > Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: >> On 06/22/2016 09:18 AM, Victor Stinner wrote: >>> Hi, >>> >>> Current status: only 3 projects are not ported yet to Python 3: >>> >>> * nova (76% done) >>> * trove (42%) >>> *

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

Daniel, Thanks. Looking for a sense of direction. Clearly there is some range of opinion, as Walter indicates. :) Not sure you are get to 100% direct connection to QEMU. When there is dedicated hardware to do off-board processing of the connection to storage, you might(?) be stuck routing

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Sean Dague wrote: > If we look at the iaas base layer: > > Keystone - custom WSGI with Routes / Paste > Glance - WSME + Routes / Paste > Cinder - custom WSGI with Routes / Paste > Neutron - pecan + Routes / Paste > Nova - custom WSGI with Routes / Paste Neutron's pecan code is still fairly new.

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Doug, nice work, thank for collecting these items. I'd like to suggest adding Kubernetes as one of the container projects, that is actively contributed by people from the OpenStack world. Within the Kubernetes Community we have an OpenStack Special Interest Group [0], where the most active

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

On 06/23/2016 08:37 AM, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2016-06-13 15:11:17 -0400: >> I'm trying to pull together some information about contributions >> that OpenStack community members have made *upstream* of OpenStack, >> via code, docs, bug reports, or anything

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

volumes connected to QEMU instances eventually become directly connected? Our long term goal is that 100% of all network storage will be connected to directly by QEMU. We already have the ability to partially do this with iSCSI, but it is lacking support for multipath. As & when that gap is

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: > On 06/22/2016 09:18 AM, Victor Stinner wrote: > > Hi, > > > > Current status: only 3 projects are not ported yet to Python 3: > > > > * nova (76% done) > > * trove (42%) > > * swift (0%) > > > >

Re: [openstack-dev] Openstack Neutron lbaas question

Hi, LBaaS is installed automatically if neutron is present. Then you just need to install a driver and get everything configured. I’d start here: http://docs.openstack.org/liberty/networking-guide/adv-config-lbaas.html

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

Hi all, 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 Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e

[openstack-dev] Openstack Neutron lbaas question

Dear Openstack Team: I have some questions regarding to openstack Mitaka Neutron lbaas For Neutron-lbaas installation, should I just follow this LINKhttps://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRunbut my openstack has controller and compute nodes. is not installed by Devstack, it is

Re: [openstack-dev] [Fuel] Deprecation of fuel-mirror tool

A big +1 > 23 черв. 2016 р. о 14:59 Bulat Gaifullin > написав(ла): > > Totally agree with this decision. > > Vladimir, thank you for driving this activity. > > Regards, > Bulat Gaifullin > Mirantis Inc. > > > >> On 23 Jun 2016, at 13:31, Vladimir Kozhukalov

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

On 2016-06-23 13:44:36 +0200 (+0200), Markus Zoeller wrote: > Interesting, I didn't know that. It runs without warnings in Nova too, > so hopefully everything's in a good shape for the pbr release. :) Note that there has been at least one past proposal[1] to add a "docs" tox environment as

[openstack-dev] [fuel] Weekly meeting for today canceled.

There is nothing in the agenda for the meeting today, so the meeting is canceled https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda . -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Community __

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

On 06/23/2016 10:07 AM, Sean McGinnis wrote: > On Thu, Jun 23, 2016 at 12:19:34AM +, Angus Lees wrote: >> So how does rootwrap fit into the "theory of upgrade"? >> >> The doc talks about deprecating config, but is silent on when new required >> config (rootwrap filters) should be installed.

Re: [openstack-dev] [tripleo] [bigswitch] question about neutron bigswitch agent

for the record: https://review.openstack.org/#/c/73/ On Wed, Jun 22, 2016 at 11:50 PM, Emilien Macchi wrote: > Ok I found what I wanted, for the record, only > python-networking-bigswitch is required on the compute node, and not > the restproxy options in neutron. > > On

[openstack-dev] [javascript] remove IIFE in js-generator-openstack

Hi, JavaScript Ninjas, Currently, all scripts in js-generator-openstack is written in IIFE form which is not necessary for nodejs project but introduce some trouble to jsdoc. What do you think we remove all the IIFE wrapper? A partial

[openstack-dev] [new][oslo] oslo.concurrency 2.6.1 release (liberty)

We are gleeful to announce the release of: oslo.concurrency 2.6.1: Oslo Concurrency library This release is part of the liberty stable release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.concurrency Please report issues through launchpad:

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

On Thu, Jun 23, 2016 at 12:19:34AM +, Angus Lees wrote: > So how does rootwrap fit into the "theory of upgrade"? > > The doc talks about deprecating config, but is silent on when new required > config (rootwrap filters) should be installed. By virtue of the way the > grenade code works

[openstack-dev] [storlets]Brand new documentation

Brand new documentation for storlets is now available. Compiled HTML format can be found here: http://storlets.readthedocs.io/en/latest/ Major new sections are: 1. A use cases section 2. A detailed dev env installation instructions (a-la SAIO), as well as deployment instructions. Thanks,

[openstack-dev] [api] Today's API-WG meeting is headless

All three of the usual chairs of the API-WG meeting (at 1600 UTC in #openstack-meeting-3) are travelling today and will not be in attendance. Apologies for the late notice. If you were hoping to bring an issue up at the meeting today please instead start an email thread tagged "[api]" so we can

Re: [openstack-dev] [kolla] better solution for the non-ini format configure file

Looks like a really cool feature, and possibly a way to non-ini files, such as policy.json files which we just want to copy rather then override. Kolla already has ini merging for ini files though and the example you provide is an ini file. I like Kolla's ini merging, and it is sort of an

Re: [openstack-dev] [Fuel] Deprecation of fuel-mirror tool

Totally agree with this decision. Vladimir, thank you for driving this activity. Regards, Bulat Gaifullin Mirantis Inc. > On 23 Jun 2016, at 13:31, Vladimir Kozhukalov > wrote: > > Dear colleagues. > > I'd like to announce that fuel-mirror tool is not going to be

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Excerpts from Doug Hellmann's message of 2016-06-13 15:11:17 -0400: > I'm trying to pull together some information about contributions > that OpenStack community members have made *upstream* of OpenStack, > via code, docs, bug reports, or anything else to dependencies that > we have. > > If

Re: [openstack-dev] [nova] libvirt driver: who should create the libvirt.xml file?

On 23.06.2016 11:50, Daniel P. Berrange wrote: > On Mon, Jun 20, 2016 at 05:47:57PM +0200, Markus Zoeller wrote: >> White working on the change series to implement the virtlogd feature I >> got feedback [1] to move code which creates parts of the libvirt.xml >> file from the "driver" module into

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

On 23.06.2016 12:21, Andreas Jaeger wrote: > On 06/23/2016 10:43 AM, Markus Zoeller wrote: >> On 21.06.2016 15:01, Doug Hellmann wrote: >>> A while back pbr had a feature that let projects pass "warnerror" >>> through to Sphinx during documentation builds, causing any warnings in >>> that build to

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

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 here and I’d like to ask the community if what we would like to do makes sense.

[openstack-dev] [Fuel] Deprecation of fuel-mirror tool

Dear colleagues. I'd like to announce that fuel-mirror tool is not going to be a part of Fuel any more. Its functionality is to build/clone rpm/deb repos and modify Fuel releases repository lists (metadata). Since Fuel 10.0 it is recommended to use other available tools for managing local

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

On 06/23/2016 10:43 AM, Markus Zoeller wrote: On 21.06.2016 15:01, Doug Hellmann wrote: A while back pbr had a feature that let projects pass "warnerror" through to Sphinx during documentation builds, causing any warnings in that build to be treated as an error and fail the build. This lets us

Re: [openstack-dev] [nova] libvirt driver: who should create the libvirt.xml file?

On Mon, Jun 20, 2016 at 05:47:57PM +0200, Markus Zoeller wrote: > White working on the change series to implement the virtlogd feature I > got feedback [1] to move code which creates parts of the libvirt.xml > file from the "driver" module into the "guest" module. I'm a bit > hesitant to do so as

[openstack-dev] [bilean] Bilean Team IRC Meeting

Hello everyone, The first IRC meeting of Bilean team will be Thursday, June 23th at 14:00 UTC in the #openstack-meeting-3 channel, everybody is welcome to join. The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/BileanAgenda And you can figure out the time in your

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote: > > > Le 23/06/2016 02:42, Tony Breeds a écrit : > > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > > > Do you think it looks like possible to have Nova

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Wed, Jun 15, 2016 at 04:59:39PM -0700, Preston L. Bannister wrote: > QEMU has the ability to directly connect to iSCSI volumes. Running the > iSCSI connections through the nova-compute host *seems* somewhat > inefficient. > > There is a spec/blueprint and implementation that landed in Kilo: >

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

On 21.06.2016 15:01, Doug Hellmann wrote: > A while back pbr had a feature that let projects pass "warnerror" > through to Sphinx during documentation builds, causing any warnings in > that build to be treated as an error and fail the build. This lets us > avoid things like links to places that

Re: [openstack-dev] [neutron][general] Multiple implementation of /usr/bin/foo stored at the same location, leading to conflicts

On 06/22/2016 06:36 PM, Nate Johnston wrote: > On Wed, Jun 22, 2016 at 05:55:48PM +0200, Thomas Goirand wrote: > >> Does neutron-fwaas also use "neutron" as launchpad package for bug report? > > Yes we do, just add the 'fwaas' tag to the bug. Thanks! > > --N. Here's the neutron-fwaas bug

[openstack-dev] [trove] RE: [all] Status of the OpenStack port to Python 3

Victor, To echo what Sylvain is saying, I think Trove has talked about python 3 for a while now and while it isn’t listed as a blueprint for Newton, I think we’re far enough along that we should see if we can get this completed for the Newton cycle. Thanks for all your work on this, and also

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Le 23/06/2016 02:42, Tony Breeds a écrit : On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: Le 22/06/2016 à 10:49, Thomas Goirand a écrit : Do you think it looks like possible to have Nova ported to Py3 during the Newton cycle? It doesn't depend on me: I'm sending patches,

Re: [openstack-dev] [openstack-ansible] L3HA problem

Version 1.2.13 is reliable. On Wed, Jun 22, 2016 at 8:40 PM, Assaf Muller wrote: > On Wed, Jun 22, 2016 at 12:02 PM, fabrice grelaud > wrote: > > > > Le 22 juin 2016 à 17:35, fabrice grelaud > a > > écrit : > > >