Excerpts from Tim Bell's message of 2018-03-20 19:48:31 +:
>
> 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 summ
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 c
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 community
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.)
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 email
> thread about this
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-nam
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 contributing
> to OpenStack, wha
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, and
Hi there!
As discussions are underway for planning the Ops meetup during the
second half of the year, I wanted to reach out with some thoughts and to
see how the Foundation staff can help. We are committed to supporting
the Ops community and want you all to know that it continues to be a
majo
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, a
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
(https://
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
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 runni
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 a
14 matches
Mail list logo