Re: [Openstack-operators] VPNaaS and FWaaS

2016-05-19 Thread Adam Lawson
We don't use FWaaS but we certainly are interested in LBaaS and VPNaaS. Chalk us up to a vendor trying to implement these. VPNaaS is huge as it allows customers to non-disruptively attach their organizations to a public cloud with the same IP space as is the case with AWS. I'd be open to letting th

Re: [Openstack-operators] VPNaaS and FWaaS

2016-05-19 Thread Joseph Bajin
We have actually started to look at VPNaaS as a way to tie two different region's Tenant Networks together.. This will hopefully allow us to not have to look at users using too many Floating IPs to just support tools and products that have issues with Floating IPs. On Tue, May 10, 2016 at 4:18 AM

Re: [Openstack-operators] Nova cells patches against Liberty

2016-05-19 Thread Sam Morrison
Ha, yeah have come across this too in our tempest runs. Haven’t had a chance to look into it yet. But I think you are on the right track. Just need to modify the tests. Cheers, Sam > On 20 May 2016, at 1:25 AM, Mike Dorman wrote: > > We are struggling a bit with the "Send up AZ and instance

Re: [Openstack-operators] [recognition] Non-ATC Recognition WG Meeting Today (5/12/2016)

2016-05-19 Thread Shamail
Hi Edgar, > On May 19, 2016, at 7:00 PM, Edgar Magana wrote: > > Shamail and Team, > > Where are we I defining the activities for recognizing OpenStack Users? In my > mind we have completed the definition and we agreed on: > AUC – Active User Contributor > We encourage the following activitie

Re: [Openstack-operators] [recognition] Non-ATC Recognition WG Meeting Today (5/12/2016)

2016-05-19 Thread Edgar Magana
Shamail and Team, Where are we I defining the activities for recognizing OpenStack Users? In my mind we have completed the definition and we agreed on: AUC – Active User Contributor We encourage the following activities: * Organizers of any of the groups.openstack.org * Active members an

Re: [Openstack-operators] Ops Meetups Team - Inagural meeting - Tuesday 1400 UTC

2016-05-19 Thread Shamail
> On May 19, 2016, at 6:23 PM, Edgar Magana wrote: > > This location sounds fantastic! I will go for Seattle! +1 > > Edgar > >> On 5/17/16, 8:13 AM, "Kingshott, Daniel" >> wrote: >> >> Just so we have this out there for the Seattle BestBuy location: >> >> 200 person theatre - Full A/V, V

Re: [Openstack-operators] Ops Meetups Team - Inagural meeting - Tuesday 1400 UTC

2016-05-19 Thread Edgar Magana
This location sounds fantastic! I will go for Seattle! Edgar On 5/17/16, 8:13 AM, "Kingshott, Daniel" wrote: >Just so we have this out there for the Seattle BestBuy location: > >200 person theatre - Full A/V, VC facilities. >6 breakout meeting rooms, one seats 5, the others seat 10+ - all have

Re: [Openstack-operators] Updated definition of 'users'

2016-05-19 Thread Edgar Magana
Awesome progress folks! So glad to see this well defined! I always wanted to have a “safe” environment for these discussions. Edgar From: Chris Morgan Date: Tuesday, May 17, 2016 at 9:34 AM To: Matt Jarvis Cc: OpenStack Operators Subject: Re: [Openstack-operators] Updated definition of 'users'

Re: [Openstack-operators] Neutron upgrade from Kilo to Mitaka

2016-05-19 Thread Kingshott, Daniel
+1 for Ihar¹s comments, the issue you will have is the deb packages will have dependencies that will be a huge pain, you would have to spin up a separate set of boxes for neutron and update the keystone endpoint. Daniel Kingshott Cloud Dude (425) 623 4359 - Cell Best Buy Co. Inc. Technology Dev

Re: [Openstack-operators] Neutron upgrade from Kilo to Mitaka

2016-05-19 Thread Ihar Hrachyshka
Akshik, please include the address of the original mailing list in your replies. > On 19 May 2016, at 22:17, Akshik dbk wrote: > > Hi Ihar, > > Thanks for the response, > > yes, Fuel does not run in containers > > correct me if I’m wrong, so upgrading neutron dependencies would have impact

Re: [Openstack-operators] Neutron upgrade from Kilo to Mitaka

2016-05-19 Thread Ihar Hrachyshka
> On 19 May 2016, at 21:43, Akshik dbk wrote: > >> Hi, >> >> I’m have a Fuel 7.0 based environment [kilo], wanted to upgrade the Neutron >> to Mitaka version. is it possible to upgrade Neutron alone to the Mitaka >> version. Developers don’t make any special effort to support mixed environme

[Openstack-operators] Neutron upgrade from Kilo to Mitaka

2016-05-19 Thread Akshik dbk
Hi, I’m have a Fuel 7.0 based environment [kilo], wanted to upgrade the Neutron to Mitaka version. is it possible to upgrade Neutron alone to the Mitaka version. if so can someone point me to right direction. ___ OpenStack-operators mailing list OpenSt

Re: [Openstack-operators] [Large Deployments Team] Meeting Reminder - 20-May-2016 03:00 UTC

2016-05-19 Thread Melvin Hillsman
Thanks for the reminder Matt! -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org From: Matt Van Winkle Date: Thursday, May 19, 2016 at 10:17 AM

Re: [Openstack-operators] Nova cells patches against Liberty

2016-05-19 Thread Mike Dorman
We are struggling a bit with the "Send up AZ and instance_name in system metadata” patch. It works fine under normal circumstances, but if there is a scheduler error (No valid host was found), then there is a failure when transitioning the instance to an error state, and the instance gets stuck

[Openstack-operators] [Large Deployments Team] Meeting Reminder - 20-May-2016 03:00 UTC

2016-05-19 Thread Matt Van Winkle
Hello LDT folks! Just a reminder that our May meeting is in a little less than 12 hours. This month is or APAC friendly time slot. See you all in #openstack-operators tonight/tomorrow morning! Thanks! VW ___ OpenStack-operators mailing list OpenStac

Re: [Openstack-operators] Problems (simple ones) at scale... Invisible VMs.

2016-05-19 Thread Kevin Bringard (kevinbri)
Sorry, my email client didn’t properly thread replies, so I just saw Simon’s reply. Seems that setting limit -1 is effectively telling it to paginate, so feel free to ignore that suggestion :-D We should perhaps still consider a better way to let people know that’s happening. At the very least

Re: [Openstack-operators] Problems (simple ones) at scale... Invisible VMs.

2016-05-19 Thread Kevin Bringard (kevinbri)
Given that there’s already the ability to start listing from a specific VM/UUID, it seems like we should add some pagination functionality in there. Maybe we need to add an “—all” flag or something which is non-admin and returns all VMs for the specific tenant. Then if someone really does want a

Re: [Openstack-operators] Problems (simple ones) at scale... Invisible VMs.

2016-05-19 Thread Simon Pasquier
In fact, both of you are correct. When passing '--limit -1' to the Nova client, it will issue multiple requests to the API using the --marker option until it receives no more data [1]. So the server-side limit (osapi_max_limit parameter) isn't by-passed, it's just the client that deals with it. BR,