Re: [openstack-dev] [puppet] Ubuntu problems + Help needed

> Just a note, the queens repo is not currently synced in the infra so > the queens repo patch is failing on Ubuntu jobs. I've proposed adding > queens to the infra configuration to resolve this: > https://review.openstack.org/529670 > As a follow up, the mirrors have landed and two of the four

Re: [openstack-dev] [release][PTL] Cycle highlights reminder

On 12/14/2017 2:24 PM, Sean McGinnis wrote: Hey all, As we get closer to Queens-3 and our final RCs, I wanted to remind everyone about the new 'cycle-highlights' we have added to our deliverable info. Background -- As a reminder on the background, we were finding that a lot of PTLs

Re: [openstack-dev] [all] Switching to longer development cycles

On 12/21/2017 4:37 PM, Joshua Harlow wrote: My 3 cents are that this isn't something that u get asked to put in from operators, it's something that is built in from the start. Just look at other workflow systems (which is really what nova/cinder/neutron... are); they don't try to add this

Re: [Openstack] Issues Understanding Neutron Networking Layout

Your description indicates you want something like this: +--+ | Compute | | | |/--\ |---> || VM1 | -|2x10G |\--/ |---> |

Re: [openstack-dev] [all] Switching to longer development cycles

My 3 cents are that this isn't something that u get asked to put in from operators, it's something that is built in from the start. Just look at other workflow systems (which is really what nova/cinder/neutron... are); they don't try to add this functionality in later (or they shouldn't at

[openstack-dev] [release] Release countdown for week R-9 and R-8, December 23 - January 5

Welcome to the extended Festivus edition of the countdown email. And now you're gonna hear about it. Development Focus - Teams should be focused on implementing planned work for the cycle. It is also a good time to review those plans and reprioritize anything if needed based on

Re: [Openstack] Issues Understanding Neutron Networking Layout

On Thu, Dec 21, 2017 at 11:11 AM, wrote: > Can you point me to any documentation to allow me to build to this kind of > layout? I'm afraid I do not have any good pointers for that sort of network setup, thus far my needs have been simple in that dept. dt -- Dean Troyer

Re: [openstack-dev] Race in FixedIP.associate_pool

On Fri, 15 Dec 2017 18:38:00 -0800, Arun Sag wrote: Here are the sequence of actions happen in nova-network 1. allocate_for_instance calls -> allocate_fixed_ips 2. FixedIPs are successfully associated (we can see this in the log) 3. allocate_for_instance calls get_instance_nw_info, which in

Re: [openstack-dev] [puppet] Ubuntu problems + Help needed

On Thu, Dec 21, 2017 at 10:40 AM, Alex Schultz wrote: > Currently they are all globally failing in master (we are using pike > still[0] which is probably the problem) in the tempest run[1] due to: > AttributeError: 'module' object has no attribute 'requires_ext' > > I've

Re: [openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

For the record, I added Lucas to the gerrit group. I assume he will mostly focus on OVN patches. You are still welcome to review other repo patches, and if you stick to it, I am happy to expand your role to cover all of them. As for OVN, you only have one +2, and existing stable reviewers may not

Re: [openstack-dev] [puppet] Ubuntu problems + Help needed

Currently they are all globally failing in master (we are using pike still[0] which is probably the problem) in the tempest run[1] due to: AttributeError: 'module' object has no attribute 'requires_ext' I've submit a patch[2] to switch UCA to queens. If history is any indication, it will probably

Re: [Openstack] Issues Understanding Neutron Networking Layout

Hi Dean I guessed this was the answer but I was afraid to admit it :-) Can you point me to any documentation to allow me to build to this kind of layout? I’ve struggled to find anything with blue-print/step-by-step installation which is why i fell back to DevStack... David Sent from my

Re: [openstack-dev] [requirements][mistral][vitrage][octavia][taskflow][watcher] Networkx version 2.0

I don't expect it to be a big thing for taskflow, I'll mess around this weekend; afaik most of the changes in networkx 2.0 were around making all the things iterators. Matthew Thode wrote: On 17-12-20 15:51:17, Afek, Ifat (Nokia - IL/Kfar Sava) wrote: Hi, There is an open bug in launchpad

[Openstack] single openstack deployment across datacenters

Hi All, Would just like to know if this is possible, currently i have 2 openstack deployment at 2 DCs. I also have ceph cluster at each DC. I'm looking at changing this deployment with a single Openstack across DCs, e.g. i will deploy: 2x controller at DC1 3x controller at DC2 8x compute at DC1

Re: [Openstack] Issues Understanding Neutron Networking Layout

On Thu, Dec 21, 2017 at 4:23 AM, wrote: > Controller in one location with a single IP connection (1 GE) > Compute node in a remote location with 4 10GE connections for public > networking and 1GE IP connection to the Controller > > The VMs on the Compute node will each have

Re: [openstack-dev] [sahara] [api] [sdks] [keystone] Sahara APIv2: service discovery

I've been delayed in actually starting the grunt work on this. If anyone else besides Monty is also able to chime in, feel free. I'm a bit lost in trying to find examples of clients doing version discovery + endpoint manipulation the "right way". If I could find a good example life would be

[openstack-dev] [nova] Overview of local disk serial numbers series for reviewers

This series is ready for review. As normal I've done my best to break it up into logically separate changes, so it's currently 15 patches long. I've also done my best to write commit messages with the reviewer in mind. If something looks weird, please check if I called it out in the commit

Re: [openstack-dev] [neutron] Stepping down from core

On Fri, Dec 15, 2017 at 2:01 PM, Armando M. wrote: > Hi neutrinos, > > To some of you this email may not come as a surprise. > > During the past few months my upstream community engagements have been more > and more sporadic. While I tried hard to stay committed and fulfill my

[openstack-dev] [etsinfv][gap-03][blazar]: Network resources to be reserved

Hi, During the Forum session about the ETSI NFV Gaps I received a request to clarify what network resources should be reserved. According to the feedback from the IFA group the most important network resources to be reserved are bandwith and public IP addresses. Any comments are welcome, also

Re: [Openstack-operators] [publiccloud] Improvement for Horizon performance

Sure, thanks. I'll push it to my colleagues. We'll come back if it's match our issues. Thank you. Jean-Daniel Bonnetot ovh.com | @pilgrimstack On 20 Dec 2017, at 23:47, Mathieu Gagné > wrote: Thank you very much for sharing this

Re: [Openstack] Issues Understanding Neutron Networking Layout

Hello OpenStack and NetVirt I'd really appreciate some guidance here because I am a confused as to how I should be building this. To explain what I want to do: * Controller in one location with a single IP connection (1 GE) * Compute node in a remote location with 4 10GE connections

[openstack-dev] [qa] Office Hours Report 2017-12-21

Hello, Thanks everyone for attending QA office hour. The IRC report [0] and full log [1] are available through meetbot. We have triaged 3 bugs and talks about some reviews, As below is the report. * Bug #1736988 in devstack: "using long-deprecated keystonemiddleware options"

Re: [openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

Hi, > Please tell me who from the OVN group is ready to take the burden, and > I will make you part of neutron-stable-maint. I think it's ok to be > more laissez faire with backports for subprojects than we were used > to, with the recent drop in core team membership and reduced capacity. Great!

Re: [openstack-dev] [nova] question on , quience use call and unquience use cast

Hi, @jichen: Something I found, FYI: The commit history in here: https://review.openstack.org/#/c/138795 I noticed that the unquience change call to cast in PS5 and PS6: https://review.openstack.org/#/c/138795/5..6/nova/compute/rpcapi.py and some comments on

[openstack-dev] [nova] question on , quience use call and unquience use cast

During review https://review.openstack.org/#/c/529278/2 ,some question on the method for quience/unquience https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L1140 use call for quience https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L1146 use cast for