Re: [openstack-dev] [nova] Nominating Stephen Finucane for nova-core

On 12/2/2016 9:22 AM, Matt Riedemann wrote: I'm proposing that we add Stephen Finucane to the nova-core team. Stephen has been involved with nova for at least around a year now, maybe longer, my ability to tell time in nova has gotten fuzzy over the years. Regardless, he's always been eager to

[openstack-dev] [TripleO] "Spec review process" now exists as a policy

Hi folks, As discussed in the last couple of TripleO meeting, the information on the wiki about how to review specs [1] was migrated into a policy at [2]. Hopefully this will help make the information more visible, and new additions (like the one that came up at [3]) will be easier to consider

Re: [openstack-dev] [cinder] consistency groups in ceph

On Mon, Dec 05, 2016 at 04:13:44PM -0800, Victor Denisov wrote: > I just realized that probably we create images from individual > snapshots of that consistency group and add those images to the new > consistency group. > Am I correct? That is correct.

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

> > >> >> I'm surprised any AD administrator let Keystone write to it. I've always >> hear the inverse that AD admins never would allow keystone to write to it, >> therefore it was never used for Projects or Assignments. Users were >> likewise read-only when AD was involved. >> >> I have seen

[openstack-dev] [neutron] [classifier] Common Classifier / Classification Framework meeting

Hi all, Common Classification Framework developers and interested parties are invited for today's meeting. The agenda is below, feel free to add more topics. https://wiki.openstack.org/wiki/Neutron/CommonFlowClassifier#Discussion_Topic_6_December_2016 1700 UTC @ #openstack-meeting. Best

Re: [openstack-dev] [nova] placement/resource providers update 4

On Fri, 2 Dec 2016, Matt Riedemann wrote: Some responses within to clarify a few points. On 12/2/2016 12:04 PM, Chris Dent wrote: There are some things to consider as that work progresses: * The bit about aggregates in the previous section: the list of returned resource providers needs to

Re: [openstack-dev] [cinder] consistency groups in ceph

Hi Victor, Yes, you are right. Thanks, Xing From: Victor Denisov [vdeni...@mirantis.com] Sent: Monday, December 5, 2016 7:13 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Jason Dillaman Subject: Re: [openstack-dev] [cinder]

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

Bence, I had been meaning to go a little deeper with performance benchmarking, but I’ve been crunched for time. Thanks for doing this, this is some great analysis. As Armando mentioned, L2pop seemed to be the biggest impediment to control plane performance. If I were to use trunks heavily in

[openstack-dev] [Infra] Ocata Summit Infra Sessions Recap

I'm Cc'ing this to the openstack-infra ML but setting MFT to direct subsequent discussion to the openstack-dev ML so we can hopefully avoid further cross-posting as much as possible. If you're replying on a particular session topic, please update the Subject so that the subthreads are easier to

Re: [openstack-dev] [Infra][heat][QA] Tempest layer4 job failure due to heat devstack plugin switch.

2016-12-06 19:42 GMT-08:00 GHANSHYAM MANN : > Hi All, > > Recently all gate heat gate jobs were switched to use heat devstack plugin > and heat code was removed from devstack tree. > > During that tempest layer 4 job is missed and blocked the tempest gate[1]. > Also

Re: [openstack-dev] [OpenStack-Infra] [Infra] Ocata Summit Infra Sessions Recap

Thank you for the write up. Having missed being there in person it is much appreciated :-) On Wed, Dec 7, 2016 at 5:56 AM, Jeremy Stanley wrote: > I'm Cc'ing this to the openstack-infra ML but setting MFT to direct > subsequent discussion to the openstack-dev ML so we can

Re: [openstack-dev] [devstack]VersionConflict exception during stack.sh - resend with explanation.

Hi Wanjing, We had some similar issues in our CI, especially after we are running one of the stable branches. The current workaround we’d found is removing all pip packs after devstack ./clean.sh Thanks Lenny. -Original Message- From: Wanjing Xu (waxu) [mailto:w...@cisco.com] Sent:

[openstack-dev] [mistral][logo] Fwd: Mistral team draft logo

Please provide your feedback on the draft logo for Mistral. My opinion: I think it looks pretty nice and it has valid associations in my mind with what Mistral does. Looking forward to seeing it coloured. Renat Akhmerov @Nokia > Begin forwarded message: > > From: Heidi Joy Tretheway

Re: [openstack-dev] [devstack]VersionConflict exception during stack.sh - resend with explanation.

Thanks Tony for reply This is Jenkins third party. So it is doing unstack and removing repo and stack again from master branch. It has been running OK and then it was disable for about a month. Now when we reenabled it, it has this versionconflict one-by-one. After I manually installed

[openstack-dev] [infra] Add support of different local.conf for subnodes

Hello, Very glad to know this patch "Add support of different local.conf for sub-nodes" https://review.openstack.org/#/c/407424/ Would like to know if each sub-node is allowed to use different local.conf, then can I customize the local.conf in primary-node and sub-node to setup multi-region

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

zhubingbing, Congratulations, the vote passed with ( 10 votes, without a veto ). I've added you to the appropriate group in Gerrit. I'll give you some training on the policies for core reviewers. PS: Since Michal is out on vacation recently, I will take the PTL duty for a while. On Fri, Dec

[openstack-dev] [nova] Is this a correct use of scheduler hints and nova-scheduler

Hi all, I want to ask a question about using scheduler-hints, could we add custom scheduler keys to work with our custom filters? Is it designed to allow vendors add own custom filters and keys? Another question is, as we have now persistent scheduler-hints in request spec, is it possible to

Re: [openstack-dev] [cinder] consistency groups in ceph

Does it mean that ceph as a backend for this feature is supposed to provide an API which allows to specify the name of each cloned image? V. On Tue, Dec 6, 2016 at 7:17 PM, yang, xing wrote: > The new image name should be volume-uuid if you don’t change >

Re: [openstack-dev] [nova] placement/resource providers update 4

On Tue, 6 Dec 2016 16:04:14 -0500, Jay Pipes wrote: We're discussing only doing: GET /resource_providers? Once we start doing claims in the scheduler, we'll have the ability to do: POST /allocations { } Thanks. FWIW, I'm not against simple non-JSON query params. The last time we

Re: [openstack-dev] [acceleration]Team Biweekly Meeting 2016.11.23 agenda

yup agree We have spent more time thinking through FPGA and GPU but certainly all devices are possible. Miroslav, you may recall in the isn examples I sent a while back I called them “programmable devices” ;-) We may need to think about defining a crips line however between these managed

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

I just saw this review [1] come in this afternoon. I'm starting to review and digest it, but it looks pretty slick. It looks like Ryu may have some test helpers that stand up Quagga in a container and allow you to interact with it natively in python. This gives us a clean way to set up a BGP

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

Hi Ryan, I was trying to add a scenario test for neutron-dynamic-routing since I have a conversation with Vikram about scenario test. And I pushed patches to gerrit as I have finished almost making it. Please check it. https://review.openstack.org/#/c/407779/ Thank you kakuma On Tue, 6 Dec

Re: [openstack-dev] [tripleo] [ci]

On Tue, Dec 6, 2016 at 9:34 PM, Ian Main wrote: > Wesley Hayutin wrote: > > Greetings, > > > > I wanted to send a status update on the quickstart based containerized > > compute ci. > > > > The work is here: > > https://review.openstack.org/#/c/393348/ > > > > I had two passes

[openstack-dev] [Zun] About k8s integration

Hi all, This is a continued discussion of the k8s integration blueprint [1]. Currently, Zun exposes a container-oriented APIs that provides service for end-users to operate on containers (i.e. CRUD). At the last team meeting, we discussed how to introduce k8s to Zun as an alternative to the

Re: [openstack-dev] [acceleration]Team Biweekly Meeting 2016.11.23 agenda

Hi Miroslav, GPU and NVMe devices are definitely in my understanding within the scope of Cyborg, however we need a road map for each type of accelerator devices :) On Wed, Dec 7, 2016 at 4:04 AM, Miroslav Halas wrote: > Hello Harm, > > > > Thank you for sharing. I was

Re: [openstack-dev] [cinder] consistency groups in ceph

How are the names chosen for those new cloned images? On Tue, Dec 6, 2016 at 10:04 AM, yang, xing wrote: > Hi Victor, > > Yes, you are right. > > Thanks, > Xing > > > From: Victor Denisov [vdeni...@mirantis.com] > Sent: Monday,

Re: [openstack-dev] [neutron][tricircle]DVR issue in cross Neutron networking

Thank you Brian, some thoughts below : > So net3 is a shared private network, perhaps just a shared VLAN. And > something > makes sure IP address allocations don't overlap. Ok. Yes, Tricircle will make sure IP address allocation don't overlap, and currently shared VLAN was supported, next

[openstack-dev] [Infra][heat][QA] Tempest layer4 job failure due to heat devstack plugin switch.

Hi All, Recently all gate heat gate jobs were switched to use heat devstack plugin and heat code was removed from devstack tree. During that tempest layer 4 job is missed and blocked the tempest gate[1]. Also another heat job had issue for enabling plugin [2]. Fixes are up for both job fix,

Re: [openstack-dev] [cinder] consistency groups in ceph

No, the new cloned image (volume) will get this name (volume-uuid) automatically. The driver does not need to specify a name. Xing From: Victor Denisov [vdeni...@mirantis.com] Sent: Tuesday, December 6, 2016 10:37 PM To: OpenStack Development Mailing

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

On 6 December 2016 at 08:49, Vasyl Saienko wrote: > Hello Neutron Community, > > > I've found that nice feature vlan-aware-vms was implemented in Newton [0]. > However the usage of this feature for regular users is impossible, unless > I'm missing something. > > As I

[openstack-dev] [swift] Failed to restore swift from file backup

Hi all, I try to make a backup of swift cluster by stopping server and backup all files. Then I create one more cluster with absolutely the same settings and restore all files from backup on it. As result swift is working and 'swift glance list' gives the same correct list as before, but 'swift

Re: [openstack-dev] [Kuryr][Magnum] How stable is kuryr-kubernetes?

On Tue, Dec 6, 2016 at 9:10 AM, Mikhail Fedosin wrote: > Hi folks! > Hi Mikhail! > > We at Samsung are trying to integrate containers in OpenStack and at this > moment we are looking at Kubernetes deployed by Magnum, which works good > enough for now. > > One challenge we

[openstack-dev] [MassivelyDistributed] IRC meeting tomorrow 15:00 UTC

Dear all, Let me remind you that Massively Distributed Clouds WG meeting is scheduled tomorrow afternoon (15:00 UTC time) Agenda is available at : https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2016(line 77). Feel free to complete it. Best regards, ad_rien_

Re: [openstack-dev] [neutron][lbaas] New extensions for HAProxy driver based LBaaSv2

Hello Zhi, So currently we’re working on dropping LBasSv2 support. Octavia is a big-tent project providing lbass in OpenStack and after merging LBasS v2 API in Octavia we will deprecate that project and in next 2 releases we’re planning to completely wipe out that code repository. If you would

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

The segmentation type of the trunk (how the VM attached to the parent port sees the traffic) has nothing to do with the provider segmentation details (how the traffic will be encapsulated when it leaves the compute node). You're right that a normal user won't know the latter details, but they

[openstack-dev] [neutron] Vlan aware VMs or trunking

Hello Neutron Community, I've found that nice feature vlan-aware-vms was implemented in Newton [0]. However the usage of this feature for regular users is impossible, unless I'm missing something. As I understood correctly it should work in the following way: 1. It is possible to group

Re: [openstack-dev] [cinder] consistency groups in ceph

The new image name should be volume-uuid if you don’t change volume_name_template in cinder.conf. The display_name field will be None for the new volume. Xing From: Victor Denisov [vdeni...@mirantis.com] Sent: Tuesday, December 6, 2016 7:23 PM To:

Re: [openstack-dev] [all] Ocata Bugsmash

Hi Sean, Thanks again for your contribution to this Bug Smash in China. This was the 5th Smash in China and this activity will continue in each release cycle. Hope more and more engineers and companies could join the activities. If we can work in the same week, the activity will be more

Re: [openstack-dev] [cinder] consistency groups in ceph

Just want to clarify that when the driver gets a list of volume objects as an input parameter in create_group_from_src, volume.name will be in the format of volume-. If you look at the database, however, the display_name field is None. Xing From:

[openstack-dev] [Neutron][DVR] - No IRC Meeting this week

Hi Folks, We will not have a DVR sub-team meeting this week since neither Swami nor myself will be there to chair it. We will resume our meetings next week on December 14th. If you have any questions please ping us on IRC or send an email to the list.

Re: [openstack-dev] [nova] placement/resource providers update 4

On 12/06/2016 03:28 PM, Ed Leafe wrote: On Dec 6, 2016, at 2:16 PM, Jay Pipes wrote: I would prefer: GET /resource_providers?resources=DISK_GB:40,VCPU:2,MEMORY_MB:2048 to "group" the resources parameter together. When we add in trait lookups, we're going to want a way

Re: [openstack-dev] [Horizon] Draft team mascot

>> On 6 Dec 2016, at 20:19, Richard Jones wrote: >> Please let me know what you think (by December 12) of this draft for >> our Horizon team mascot. > On 7 December 2016 at 07:38, Rob Cresswell (rcresswe) wrote: > Are we missing an attachment / link ?

[openstack-dev] [all] Ocata Bugsmash

Last week was the Ocata Bugsmash in Shenzhen, China. Many developers from around China gathered to debug, test, and fix a large number of bugs across many of the most popular projects. I wanted to take an opportunity to thank Huawei, Intel, and everyone involved for making this event happen. It

Re: [openstack-dev] [devstack]VersionConflict exception during stack.sh

Try to manually uninstall it first: sudo pip uninstall python-heatclient Then launch devstack again. It will re-install the right version. /ludovic -Original Message- From: Wanjing Xu (waxu) [mailto:w...@cisco.com] Sent: December-06-16 2:43 PM To: OpenStack Development Mailing List

Re: [openstack-dev] [nova] placement/resource providers update 4

On 12/06/2016 02:02 PM, Ed Leafe wrote: On Dec 6, 2016, at 9:56 AM, Chris Dent wrote: * There is unresolved debate about the structure of the request being made to the API. Is it POST or a GET, does it have a body or use query strings? The plan is to resolve this

[openstack-dev] [Horizon] Draft team mascot

Hi folks, Please let me know what you think (by December 12) of this draft for our Horizon team mascot. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] placement/resource providers update 4

On Dec 6, 2016, at 2:16 PM, Jay Pipes wrote: > I would prefer: > > GET /resource_providers?resources=DISK_GB:40,VCPU:2,MEMORY_MB:2048 > > to "group" the resources parameter together. When we add in trait lookups, > we're going to want a way to clearly delineate between

Re: [openstack-dev] [nova] placement/resource providers update 4

On Dec 6, 2016, at 9:56 AM, Chris Dent wrote: >>> * There is unresolved debate about the structure of the request being >>> made to the API. Is it POST or a GET, does it have a body or use >>> query strings? The plan is to resolve this discussion in the review >>> of

[openstack-dev] [devstack]VersionConflict exception during stack.sh

Hi 2016-12-06 18:50:28.095 | +inc/python:setup_package:354  pip_install -e /opt/stack/horizon 2016-12-06 18:50:28.881 | +inc/python:pip_install:155  sudo -H http_proxy= https_proxy= no_proxy= PIP_FIND_LINKS= SETUPTOOLS_SYS_PATH_TECHNIQUE=rewrite

[openstack-dev] [devstack]VersionConflict exception during stack.sh - resend with explanation.

Hi, My devstack had been OK a month ago. But recently it keeps having this VersionConflict error. If I manually install the required module version, it will move on but then it will error out at some other module. I have manually installed and fixed about 8 such modules, still it is not

Re: [openstack-dev] [acceleration]Team Biweekly Meeting 2016.11.23 agenda

Hello Harm, Thank you for sharing. I was wondering if you have given any thoughts how other type of devices other than FPGAs would fit into this framework. For example, GPUs or block devices (such as NVMe drives) for exclusive access by the VMs. Could these type of devices be also managed by

Re: [openstack-dev] [devstack]VersionConflict exception during stack.sh

Thanks for replying . Sorry I did not write explanation in this email. So I sent another one. Basically, there are too many of this kind of conflicts, I already manually fixed about 8, still more. If I fix them all this time, it may still happen down the road if somebody update constrains

Re: [openstack-dev] [Horizon] Draft team mascot

Are we missing an attachment / link ? :) > On 6 Dec 2016, at 20:19, Richard Jones wrote: > > Hi folks, > > Please let me know what you think (by December 12) of this draft for > our Horizon team mascot. > >

Re: [openstack-dev] [nova] placement/resource providers update 4

Le 06/12/2016 22:02, Ed Leafe a écrit : > On Dec 6, 2016, at 2:42 PM, Jay Pipes wrote: > >> Oh, absolutely, I wasn't arguing about length of URI or anything. >> >> To be clear, I could either go the above route or even do a POST >> /resource_providers that returns a list

Re: [openstack-dev] [devstack]VersionConflict exception during stack.sh - resend with explanation.

On Tue, Dec 06, 2016 at 08:02:23PM +, Wanjing Xu (waxu) wrote: > > Hi, > My devstack had been OK a month ago. But recently it keeps having this > VersionConflict error. If I manually install the required module version, > it will move on but then it will error out at some other module. I

[openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

Hi all, General query - Is there anyone in the Dynamic Routing community that is planning on contributing a scenario test? As far as I could tell, none of the current API tests would fail if, for example, the BGP agent was not running. Please correct me if I'm wrong. Thank you.

[openstack-dev] [Kuryr][Magnum] How stable is kuryr-kubernetes?

Hi folks! We at Samsung are trying to integrate containers in OpenStack and at this moment we are looking at Kubernetes deployed by Magnum, which works good enough for now. One challenge we have faced recently is making containers able to communicate with Nova VM instances (in other words we

Re: [openstack-dev] [devstack] About installing devstack on Ubuntu

Try: apt-get install python-dev BTW, this list is about openstack developers. For questions about installation and usage, please post to openst...@lists.openstack.org or try ask.openstack.org Regards, Qiming On Tue, Dec 06, 2016 at 02:07:58PM +0800, Yipei Niu wrote: > Hi, All, > > I

[openstack-dev] [neutron][lbaas] New extensions for HAProxy driver based LBaaSv2

Hi, all I am considering add some new extensions for HAProxy driver based Neutron LBaaSv2. Extension 1, multi subprocesses supported. By following this document[1], I think we can let our HAProxy based LBaaSv2 support this feature. By adding this feature, we can enhance loadbalancers

Re: [openstack-dev] [neutron] Is it possible that creating a port and binding it with 2 IPs

Hi Vincent,Your initial observation is correct: each port is associated with a Neutron network, and will get one IPv4 and one IPv6 address from the subnets associated with that network.To add additional IPs to a

Re: [openstack-dev] [neutron] Is it possible that creating a port and binding it with 2 IPs

+1. Also, if you just need an additional IP for the instance that isn't used by other instances, you can do a port update and add additional IPs to the fixed_ips field. On Tue, Dec 6, 2016 at 1:09 AM, Neil Jerram wrote: > Hi Vincent, > > Your initial observation is correct: each

Re: [openstack-dev] [devstack][neutron-lbaas][octavia] About installing Devstack on Ubuntu

On 6 December 2016 at 13:12, Jens Rosenboom wrote: > 2016-12-06 7:16 GMT+01:00 Yipei Niu : >> Hi, All, >> >> I failed installing devstack on Ubuntu. The detailed info of local.conf and >> error is pasted in http://paste.openstack.org/show/591493/. >> >>

Re: [openstack-dev] [devstack][neutron-lbaas][octavia] About installing Devstack on Ubuntu

2016-12-06 7:16 GMT+01:00 Yipei Niu : > Hi, All, > > I failed installing devstack on Ubuntu. The detailed info of local.conf and > error is pasted in http://paste.openstack.org/show/591493/. > > BTW, python2.7 is installed in Ubuntu, and Python.h can be found under >

Re: [openstack-dev] [nova] Nominating Stephen Finucane for nova-core

+1 from me. He will be a great add. I really enjoyed working with him as part of OSIC early on in his Nova journey, and I trust him to a great job as part of the core team. John On Sun, 4 Dec 2016 at 00:00, Michael Still wrote: > +1, I'd value him on the team. > > Michael >

Re: [openstack-dev] [neutron][lbaas] New extensions for HAProxy driver based LBaaSv2

Hi, I think that there is a move to Octavia. I suggest reaching out to that community and see how these changes can be added. Sounds like a nice addition Thanks Gary From: zhi Reply-To: OpenStack List Date: Tuesday, December 6, 2016 at

Re: [openstack-dev] [Performance][shaker] Triangular topology

Hi Matt, I would suggest to let users specify custom topology in Shaker scenario via graphs (e.g. directed triangle would look like: A -> B, B -> C, C -> A), where every pair of nodes is pair of VMs and every edge corresponds to the traffic flow. The above example will be deployed as 6 VMs, 2 per

[openstack-dev] [puppet] Virtual midcycle/sprint - Jan 11/12

Hey everyone, We're going to be running a small midcycle/sprint on January 11-12, 2017 in #puppet-openstack on freenode. We will be reviewing the work items for Ocata and doing some bug triage. Feel free to add additional topics to the etherpad[0]. Thanks, -Alex [0]

Re: [openstack-dev] [Horizon] Draft team mascot

On 12/06/2016 01:48 PM, Richard Jones wrote: > >> On 6 Dec 2016, at 20:19, Richard Jones wrote: > >> Please let me know what you think (by December 12) of this draft for > >> our Horizon team mascot. > > > On 7 December 2016 at 07:38, Rob Cresswell (rcresswe) >

Re: [openstack-dev] [neutron][tricircle]DVR issue in cross Neutron networking

On 12/05/2016 10:38 PM, joehuang wrote: Hello, Brian, Thank you for your comment, see inline comments marked with [joehuang]. The ASCII figure is not good in the plain text mail, you can check it at the browser: http://lists.openstack.org/pipermail/openstack-dev/2016-December/108447.html

Re: [openstack-dev] [nova] placement/resource providers update 4

On Dec 6, 2016, at 2:42 PM, Jay Pipes wrote: > Oh, absolutely, I wasn't arguing about length of URI or anything. > > To be clear, I could either go the above route or even do a POST > /resource_providers that returns a list of resource providers instead of > creating a

Re: [openstack-dev] [nova] placement/resource providers update 4

On 12/06/2016 04:00 PM, melanie witt wrote: On Tue, 6 Dec 2016 15:42:18 -0500, Jay Pipes wrote: On 12/06/2016 03:28 PM, Ed Leafe wrote: On Dec 6, 2016, at 2:16 PM, Jay Pipes wrote: I would prefer: GET /resource_providers?resources=DISK_GB:40,VCPU:2,MEMORY_MB:2048 to

Re: [openstack-dev] [nova] placement/resource providers update 4

On Tue, 6 Dec 2016 15:42:18 -0500, Jay Pipes wrote: On 12/06/2016 03:28 PM, Ed Leafe wrote: On Dec 6, 2016, at 2:16 PM, Jay Pipes wrote: I would prefer: GET /resource_providers?resources=DISK_GB:40,VCPU:2,MEMORY_MB:2048 to "group" the resources parameter together. When

Re: [openstack-dev] [nova] placement/resource providers update 4

On Dec 6, 2016, at 3:00 PM, melanie witt wrote: > > Last time I was aware of the discussion, I thought that sophisticated queries > for a list of resource providers would involve specifying a structured JSON > payload. That is where I don't tend to think a query string in

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

On 6 December 2016 at 14:36, Assaf Muller wrote: > Hi all, > > General query - Is there anyone in the Dynamic Routing community that > is planning on contributing a scenario test? As far as I could tell, > none of the current API tests would fail if, for example, the BGP >

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

This is at the top of my list to look at. I've been thinking a lot about how to implement some tests. For instance, do we need to actually stand up a BGP peer of some sort to peer neutron with and assert the announcements somehow? Or should we assume that Ryu works properly and make sure we

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

On 6 December 2016 at 14:44, Tidwell, Ryan wrote: > This is at the top of my list to look at. I've been thinking a lot about > how to implement some tests. For instance, do we need to actually stand up > a BGP peer of some sort to peer neutron with and assert the

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

Thanks for the pointer. I'll take a look and see what can be leveraged. -Ryan _ From: Armando M. > Sent: Tuesday, December 6, 2016 2:57 PM Subject: Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

Re: [openstack-dev] [Neutron][Dynamic Routing] Plans for scenario testing?

On Tue, Dec 6, 2016 at 5:44 PM, Tidwell, Ryan wrote: > This is at the top of my list to look at. Thanks Ryan that's good to know. I think that gating on some tests that demonstrates that the project works end to end is a signal of maturity and will help adoption. > I've