Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

Interesting debate, thanks for raising it. Would we still need the same style of summit forum if we have the OpenStack Community Working Gathering? One thing I have found with the forum running all week throughout the summit is that it tends to draw audience away from other talks so maybe we

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

On 2018-03-20 10:37:21 -0500 (-0500), Jimmy McArthur wrote: [...] > We have an opportunity to co-locate the Ops Meetup at the PTG. [...] To echo what others have said so far, I'm wholeheartedly in favor of this idea. It's no secret I'm not a fan of the seemingly artificial schism in our

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

Posting this from Dave Medberry (and with permission): While no longer technically an operator I'm 100% for colocating PTG and Ops Meetups. I know some folks don't want to feel like tagalongs but I think you are addressing that (and making a specific Ops invite and considering a name change.)

Re: [Openstack-operators] Ops Meetups team - minutes of team meeting 3/20/2018

On Tue, Mar 20, 2018 at 9:16 AM, Chris Morgan wrote: > > On that note, please stand by for some exciting news and discussion about > the future of Ops Meetups and OpenStack PTG, as there seems to be > increasing support for combining the two events into one. I expect an

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

I had jokingly called it the 'OpenStack Community Working Midcycle' during the UC meeting because I always wondered if the Gathering part of PTG had made it hard for people to get support to go. But I really do like the word contributor mentioned here and I think we should stress that in the

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

On Tue, Mar 20, 2018 at 10:03 AM, Thierry Carrez wrote: > > Personally, I'm not a big fan of separate branding (or "co-location"). > If the "PTG" name is seen as too developer-centric, I'd rather change > the event name (and clearly make it a work event for anyone

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

Jimmy McArthur wrote: > [...] > We've been meeting regularly with the User Committee to help establish > goals for the Committee as well as Operators and End Users.  There are > three critical things that we identified as immediate areas of concern: > > * How to involve operators, end users,

[Openstack-operators] Ops Meetups team - minutes of team meeting 3/20/2018

Hello Everyone, We had a good meeting today on IRC, links below for the minutes and log. We went over some lesson learned from the Tokyo event as well as plans for the future. On that note, please stand by for some exciting news and discussion about the future of Ops Meetups and OpenStack PTG,

[Openstack-operators] [scientific] IRC meeting 2100UTC

Hi all, Reminder there's a Scientific SIG meeting coming up in about 6.5 hours. All comers welcome. (https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_March_20th_2018) IRC Meeting March 20th 2018 2018-03-20 2100 UTC in channel #openstack-meeting # Forum brainstorming

Re: [Openstack-operators] tracking history of floating IP

Thanks, This seems to be a good track. I will check that --- Cedlerouge Le 2018-03-18 21:10, Jerome Pansanel a écrit : Hi, We have developed a simple MySQL trigger to register the floating ip usage: https://github.com/FranceGrilles/openstack-triggers (a recent modification has not been yet

Re: [Openstack-operators] sporadic missing vxlan-tunnel-port assignment

Hi Fabian, We are running Pike. We have DVR with centralized SNAT on L3-HA routers. We also have L2 population enabled which I think is responsible for the issue. We can reproduce the issue almost every time we are spawning 100 VMs at once. Usually 3-6 VMs have no connectivity to services

Re: [Openstack-operators] outstanding issues with GPU passthrough

I forgot to specifically address one of the questions that Belmiro raised, which is regarding device clean-up. I guess this would be relevant to Ironic bare-metal clouds too. If the hypervisor has blocked access to problematic areas of the PCI config space then this probably isn't necessary, but

[Openstack-operators] outstanding issues with GPU passthrough

Hi all, This has turned into a bit of a screed I'm afraid... Last week I had pings from both the folks at CERN and Catalyst Cloud about GPU-accelerated OpenStack instances with PCI passthrough, specifically asking about the security issues I've mentioned in community forums previously, and any