Re: [openstack-dev] [Mistral]I think Mistral need K8S action

[홍선군]

Thanks for your reply.

 

I will refer to this Ansible action and developing  actions for K8S somewhere 
externally. 

 

Regards,

Xian Jun Hong

 

 

From: Dougal Matthews  
Sent: Saturday, April 14, 2018 1:00 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [Mistral]I think Mistral need K8S action

 

 

 

On 13 April 2018 at 05:47, Renat Akhmerov  > wrote:

Hi, 

 

I completely agree with you that having such an action would be useful. 
However, I don’t think this kind of action should be provided by Mistral out of 
the box. Actions and triggers are integration pieces for Mistral and are 
natively external to Mistral code base. In other words, this action can be 
implemented anywhere and plugged into a concrete Mistral installation where 
needed.

 

As a home for this action I’d propose 'mistral-extra’ repo where we are 
planning to move OpenStack actions and some more.

Also, if you’d like to contribute you’re very welcome.

 

I would recommend developing actions for K8s somewhere externally, then when 
mistral-extra is ready we can move them over. This is the approach that I took 
for the Ansible actions[1] and they will likely be one of the first additions 
to mistral-extra.

[1]: https://github.com/d0ugal/mistral-ansible-actions


 

 


Thanks

Renat Akhmerov
@Nokia


On 13 Apr 2018, 09:18 +0700,  >, wrote:

Hello  Mistral team.

I'm doing some work on the K8S but I observed that there is only Docker's 
action in Mistral.

I would like to ask Mistral Team, why there is no K8S action in the mistral.

I think it would be useful in Mistral.

If you feel it's necessary, could I add K8S action to mistral?

 

Regards,

Xian Jun Hong

 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [All][Election] Last Days for TC Nominations

[Kendall Nelson]

Hello Everyone,

A quick reminder that we are in the last hours for TC candidate
announcements. Nominations are open until Apr 17, 2018 23:45 UTC.

If you want to stand for TC, don't delay, follow the instructions at [1] to
make sure the community knows your intentions.

Make sure your nomination has been submitted to the openstack/election
repository and approved by election officials.

Thank you,

-Kendall Nelson (diablo_rojo)

[1] http://governance.openstack.org/election/#how-to-submit-your-candidacy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Mistral]I think Mistral need K8S action

[Renat Akhmerov]

On 13 Apr 2018, 23:01 +0700, Dougal Matthews , wrote:
> > I would recommend developing actions for K8s somewhere externally, then 
> > when mistral-extra is ready we can move them over. This is the approach 
> > that I took for the Ansible actions[1] and they will likely be one of the 
> > first additions to mistral-extra.
> >
> > [1]: https://github.com/d0ugal/mistral-ansible-actions
> >


Yes, I agree.

Renat Akhmerov
@Nokia
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] roadmap on containers workflow

[Emilien Macchi]

On Fri, Apr 13, 2018 at 5:58 PM, Emilien Macchi  wrote:

>
> A bit of progress today, I prototyped an Ansible role for that purpose:
> https://github.com/EmilienM/ansible-role-container-registry
>
> The next step is, I'm going to investigate if we can deploy Docker and
> Docker Distribution (to deploy the registry v2) via the existing composable
> services in THT by using external_deploy_tasks maybe (or another interface).
> The idea is really to have the registry ready before actually deploying
> the undercloud containers, so we can modify them in the middle (run
> container-check in our case).
>

This patch: https://review.openstack.org/#/c/561377 is deploying Docker and
Docker Registry v2 *before* containers deployment in the docker_steps.
It's using the external_deploy_tasks interface that runs right after the
host_prep_tasks, so still before starting containers.

It's using the Ansible role that was prototyped on Friday, please take a
look and raise any concern.
Now I would like to investigate how we can run container workflows between
the deployment and docker and containers deployments.
-- 
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][dynamic routing] RYU Breaks lower constraints

[IWAMOTO Toshihiro]

On Sun, 15 Apr 2018 21:02:42 +0900,
Gary Kotton wrote:
> 
> [1  ]
> [1.1  ]
> Hi,
> That sounds reasonable. I wonder if the RYU folk can chime in here.
> Thanks

I don't fully understand the recent g-r change yet, but
I guess neutron-dynamic-routing should  also have ryu>=4.24.
I'll check this tommorrow.

> From: Akihiro MOTOKI 
> Reply-To: OpenStack List 
> Date: Sunday, April 15, 2018 at 12:43 PM
> To: OpenStack List 
> Subject: Re: [openstack-dev] [neutron][dynamic routing] RYU Breaks lower 
> constraints
> 
> Gary,
> 
> I think this is caused by the recent pip change and pip no longer cannot 
> import pip from code. The right solution seems to bump the minimum version of 
> ryu.
> 
> Thought?
> 
> http://lists.openstack.org/pipermail/openstack-dev/2018-March/128939.html
> 
> Akihiro
> 
> 2018/04/15 午後6:06 "Gary Kotton" 
> >:
> Hi,
> It seems like ther RYU import is breaking the project:
> 
> 
> 2018-04-15 
> 08:41:34.654681
>  | ubuntu-xenial | b'--- import errors ---\nFailed to import test module: 
> neutron_dynamic_routing.tests.unit.services.bgp.driver.ryu.test_driver\nTraceback
>  (most recent call last):\n  File 
> "/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
>  line 456, in _find_test_path\nmodule = 
> self._get_module_from_name(name)\n  File 
> "/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
>  line 395, in _get_modu
 le_from_name\n__import__(name)\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/neutron_dynamic_routing/tests/unit/services/bgp/driver/ryu/test_driver.py",
 line 21, in \nfrom ryu.services.protocols.bgp import bgpspeaker\n  
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/services/protocols/bgp/bgpspeaker.py",
 line 21, in \nfrom ryu.lib.packet.bgp import (\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/__init__.py", 
line 6, in \nfrom . import (ethernet, arp, icmp, icmpv6, ipv4, 
ipv6, lldp, mpls, packet,\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ethernet.py",
 line 18, in \nfrom . import vlan\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/vlan.py",
 line 21, in \nfrom . import ipv4\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ipv4.py",
 line 23, in \nfrom . import tcp\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/tcp.py",
 line 24, in \nfrom . import bgp\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/bgp.py",
 line 52, in \nfrom ryu.utils import binary_str\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/utils.py",
 line 23, in \nfrom pip import req as pip_req\nImportError: cannot 
import name \'req\'\n'
> 
> Any suggestions?

Re: [openstack-dev] PBR and Pipfile

[Gaetan]

Hello,

Thank you for this response. It took me quite some times to carefully read
it, it was far beyond my expectation! So thanks a lot, lot of thing to
understand.

>
>> There are actually three different relevant use cases here, with some
> patterns available to draw from. I'm going to spell them out to just make
> sure we're on the same page.
>
> * Library
> * Application
> * Suite of Coordinated Applications


[...]

Can we say packaging a python application for a linux distribution may fall
in this "Suite of Coordinate Applications" kind?

I really liked your way of describing these differences, I actually started
using it as basis for my internal Python courses I give in my company on a
regular basis :)

As maintainer of a small project (Guake), I am in contact with package
maintainers (Debian, arch, now, fedora,...) that relates me these kind of
issues (Guake mainly has system python dependencies such as pygtk). They
(the maintainers) has similar issues as OpenStack might have, in that they
need to sync all dependencies for a given version distribution. Of course
they do not use this upper-constraint requirements file as a way of fixing
the same dependencies for all apps.


>
>
For Pipfile, I believe we'd want to see is adding support for --constraints
> to pipenv install - so that we can update our Pipfile.lock file for each
> application in the context of the global constraints file. This can be
> simulated today without any support from pipenv directly like this:
>
>   pipenv install
>   $(pipenv --venv)/bin/pip install -U -c
> https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt
> -r requirements.txt
>   pipenv lock


the pipenv lock will not lock the dependencies added manually by pip,
unfortunately. What you can do it open a bug on pipenv project [1] on my
behalf, with your need and assign me on it. I am not sure how this would
need to be handled, but this worth notifying the pipenv projects of your
needs (never used the -c option of pip install)


> There is also works on PEP around pyproject.toml ([4]), which looks quite
>> similar to PBR's setup.cfg. What do you think about it?
>>
>
> It's a bit different. There is also a philosophical disagreement about the
> use of TOML that's not worth going in to here


we agree on TOML


> - but from a pbr perspecitve I'd like to minimize use of pyproject.toml to
> the bare minimm needed to bootstrap things into pbr's control. In the first
> phase I expect to replace our current setup.py boilerplate:
>
> setuptools.setup(
> setup_requires=['pbr'],
> pbr=True)
>
> with:
>
> setuptool.setup(pbr=True)
>
> and add pyproject.toml files with:
>
> [build-system]
> requires = ["setuptools", "wheel", "pbr"]


[...]
That would would indeed way beyond all what I wanted to work on for pbr.
Do you have a plan for this support for pbr?


> My opinion is this difference in behaviourbetween lib and app has
>> technical reasons, but as a community we would gain a lot of unifying both
>> workflows. I am using PBR + a few hacks [5], and I am pretty satisfied with
>> the overall result.
>>
>
> There are two topics your pbr patch opens up that need to be covered:
>
> * pbr behavior
> * dependencies
>
> ** pbr behavior **
>
> I appreciate what you're saying about unifying the lib and app workflow,
> but I think the general pattern across the language communities (javascript
> and rust both have similar patterns to Pipefile) is that the two different
> options are important.


We may just need to have a better document - rust has an excellent
> description:
>
> https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
>

There are lot of talks in the pipenv community at this moment, we ended up
with best practices for python:
- app: Pipfile and Pipfile.lock tracked in git
- library: do not track Pipfile*, but use ‘pipenv install -e .’

I am trying to amend it with pbr support for libs (and there are actually
several persons that uses pbr).

In any case, I think what pbr should do with pipfiles is:
>
> * If pbr discovers a Pipfile and no Pipfile.lock, it should treat the
> content in the packages section of Pipfile as it currently does with
> requirements.txt (and how you have done in the current patch)


That’s my goal in my patch. If I understand how it works (please tell me if
i am wrong), on a distribution package/wheel, pbr looks for
requirements.txt and inject as dependencies. The major change on my patch
is:
- having to vendor the basic toml parser.

* If pbr discoves a Pipfile.lock, it should treat the content in
> Pipfile.lock as it currently does requirements.txt.

This is actually the “normal” behavior of pipenv, and more generally, of
the Pipfile parser: prefer the lock file over the pipenv. The ultimate
source of truth is the lock file and the Pipfile is only a convinient way
of describing the dependencies, at least that is for apps.

Then, we either need to:
>
> * Add support to pipfile install for specifying a 

Re: [openstack-dev] [neutron][dynamic routing] RYU Breaks lower constraints

[Gary Kotton]

Hi,
That sounds reasonable. I wonder if the RYU folk can chime in here.
Thanks
Gary

From: Akihiro MOTOKI 
Reply-To: OpenStack List 
Date: Sunday, April 15, 2018 at 12:43 PM
To: OpenStack List 
Subject: Re: [openstack-dev] [neutron][dynamic routing] RYU Breaks lower 
constraints

Gary,

I think this is caused by the recent pip change and pip no longer cannot import 
pip from code. The right solution seems to bump the minimum version of ryu.

Thought?

http://lists.openstack.org/pipermail/openstack-dev/2018-March/128939.html

Akihiro

2018/04/15 午後6:06 "Gary Kotton" >:
Hi,
It seems like ther RYU import is breaking the project:


2018-04-15 
08:41:34.654681
 | ubuntu-xenial | b'--- import errors ---\nFailed to import test module: 
neutron_dynamic_routing.tests.unit.services.bgp.driver.ryu.test_driver\nTraceback
 (most recent call last):\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
 line 456, in _find_test_path\nmodule = self._get_module_from_name(name)\n  
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
 line 395, in _get_module_from_name\n__import__(name)\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/neutron_dynamic_routing/tests/unit/services/bgp/driver/ryu/test_driver.py",
 line 21, in \nfrom ryu.services.protocols.bgp import bgpspeaker\n  
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/services/protocols/bgp/bgpspeaker.py",
 line 21, in \nfrom ryu.lib.packet.bgp import (\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/__init__.py",
 line 6, in \nfrom . import (ethernet, arp, icmp, icmpv6, ipv4, 
ipv6, lldp, mpls, packet,\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ethernet.py",
 line 18, in \nfrom . import vlan\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/vlan.py",
 line 21, in \nfrom . import ipv4\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ipv4.py",
 line 23, in \nfrom . import tcp\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/tcp.py",
 line 24, in \nfrom . import bgp\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/bgp.py",
 line 52, in \nfrom ryu.utils import binary_str\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/utils.py",
 line 23, in \nfrom pip import req as pip_req\nImportError: cannot 
import name \'req\'\n'

Any suggestions?
Thanks
Gary

[openstack-dev] [devstack][infra] pip vs psutil

[Gary Kotton]

Hi,
The gate is currently broken with https://launchpad.net/bugs/1763966. 
https://review.openstack.org/#/c/561427/ Can unblock us in the short term. Any 
other ideas?
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][dynamic routing] RYU Breaks lower constraints

[Akihiro Motoki]

Gary,

I think this is caused by the recent pip change and pip no longer cannot
import pip from code. The right solution seems to bump the minimum version
of ryu.

Thought?

http://lists.openstack.org/pipermail/openstack-dev/2018-March/128939.html

Akihiro

2018/04/15 午後6:06 "Gary Kotton" :

Hi,

It seems like ther RYU import is breaking the project:



2018-04-15 08:41:34.654681

| ubuntu-xenial | b'--- import errors ---\nFailed to import test
module: 
neutron_dynamic_routing.tests.unit.services.bgp.driver.ryu.test_driver\nTraceback
(most recent call last):\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
line 456, in _find_test_path\nmodule =
self._get_module_from_name(name)\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
line 395, in _get_module_from_name\n__import__(name)\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/neutron_dynamic_routing/tests/unit/services/bgp/driver/ryu/test_driver.py",
line 21, in \nfrom ryu.services.protocols.bgp import
bgpspeaker\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/services/protocols/bgp/bgpspeaker.py",
line 21, in \nfrom ryu.lib.packet.bgp import (\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/__init__.py",
line 6, in \nfrom . import (ethernet, arp, icmp, icmpv6,
ipv4, ipv6, lldp, mpls, packet,\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ethernet.py",
line 18, in \nfrom . import vlan\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/vlan.py",
line 21, in \nfrom . import ipv4\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ipv4.py",
line 23, in \nfrom . import tcp\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/tcp.py",
line 24, in \nfrom . import bgp\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/bgp.py",
line 52, in \nfrom ryu.utils import binary_str\n  File
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/utils.py",
line 23, in \nfrom pip import req as pip_req\nImportError:
cannot import name \'req\'\n'



Any suggestions?

Thanks

Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron][dynamic routing] RYU Breaks lower constraints

[Gary Kotton]

Hi,
It seems like ther RYU import is breaking the project:


2018-04-15 
08:41:34.654681
 | ubuntu-xenial | b'--- import errors ---\nFailed to import test module: 
neutron_dynamic_routing.tests.unit.services.bgp.driver.ryu.test_driver\nTraceback
 (most recent call last):\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
 line 456, in _find_test_path\nmodule = self._get_module_from_name(name)\n  
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/unittest2/loader.py",
 line 395, in _get_module_from_name\n__import__(name)\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/neutron_dynamic_routing/tests/unit/services/bgp/driver/ryu/test_driver.py",
 line 21, in \nfrom ryu.services.protocols.bgp import bgpspeaker\n  
File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/services/protocols/bgp/bgpspeaker.py",
 line 21, in \nfrom ryu.lib.packet.bgp import (\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/__init__.py",
 line 6, in \nfrom . import (ethernet, arp, icmp, icmpv6, ipv4, 
ipv6, lldp, mpls, packet,\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ethernet.py",
 line 18, in \nfrom . import vlan\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/vlan.py",
 line 21, in \nfrom . import ipv4\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/ipv4.py",
 line 23, in \nfrom . import tcp\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/tcp.py",
 line 24, in \nfrom . import bgp\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/lib/packet/bgp.py",
 line 52, in \nfrom ryu.utils import binary_str\n  File 
"/home/zuul/src/git.openstack.org/openstack/neutron-dynamic-routing/.tox/lower-constraints/lib/python3.5/site-packages/ryu/utils.py",
 line 23, in \nfrom pip import req as pip_req\nImportError: cannot 
import name \'req\'\n'

Any suggestions?
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev