ommon-openstack-ml-topics
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
l discuss such areas
that are a particularly good match for users to get involved.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
unity members to reach out on local social networks... But
I'm reluctant to pass an official resolution to recommend that TC
members engage on specific platforms because "everyone is there".
--
Thierry Carrez (ttx)
___
OpenSta
You mention Ildiko and Lance: they did that line of
work without being elected.
So I would definitely support having champions to drive SIG
cross-project priorities, and use the TC both to support them and as a
natural pool of champion candidate
d command).
For more information on the bot commands, please see:
https://git.openstack.org/cgit/openstack/ptgbot/tree/README.rst
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.o
.
[...]
Yes, the Freenode blacklist blocks most cloud providers IP blocks. My
own instance (running on an OpenStack public cloud) is also required to
use SASL.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
inconvenience this may cause.
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-July/132392.html
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
Thierry Carrez wrote:
Hi everyone,
Last month we published the tentative schedule layout for the 5 days of
PTG. There was no major complaint, so that was confirmed as the PTG
event schedule and published on the PTG website:
https://www.openstack.org/ptg#tab_schedule
The tab temporarily
enver_2018
See you there !
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
t:
https://openstackfoundation.formstack.com/forms/travelsupportptg_denver_2018
See you there !
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
ction data (what turbo-hipster did) and the challenges to
share deidentified data to that purpose.
Cheers,
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailma
ot;contributors" with various backgrounds but a single
objective, please add to it and join the session !
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailma
on Sunday, April 15,
at which point the Forum selection committee will take the entries and
make the final selection. So you have the whole week to enter your
selection of ideas on the website.
Thanks !
--
Thierry Carrez (ttx)
___
OpenStack-operators ma
Erik McCormick wrote:
> I'm a +1 too as long as the devs at large are cool with it and won't
> hate on us for crashing their party.
As a data point, in a recent survey 89% of surveyed developers supported
that the Ops meetup should happen at the same time and place. Amongst
past PTG attendees,
t it is possible for groups to book additional
meeting spots outside the pre-allocated time and space. If some work
groups realize they would like to meet on Monday to get work done,
that's definitely possible. It all appears on the dynamic event sched
the Forum can be found at:
https://wiki.openstack.org/wiki/Forum
Regards,
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
y calling it an ops event
co-located with a dev event. It's really a single "contributor" event.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
around. Anyone with the link can vote, nothing was sent to
each of the voters individually.
The "Already voted" error might be due to CIVS limiting public polling
to one entry per IP, and a colleague of yours already voted... Maybe try
from another IP address ?
--
Thierry Carrez
.html
Happy reading!
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
d at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
issues.
Thanks Sam for sharing! If you can clearly narrow it down to a specific
update (kernel or microcode), can you make sure the bug is reported back
to Ubuntu ?
Distros are struggling with the stability of the Meltdown/Spectre
workarounds (especially the opaque CPU microcode updates) and ca
I felt like
we were self-imposing too many deadlines, events and coordination
processes for limited gain. Maybe I'm wrong though :)
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.opens
ing ops-centric discussions around local OpenStack Days, and then use
Forums at Summits as the funnel to close the feedback loop in those
discussions. That would reduce the need for a "big" twice-a-year Ops
Meetup and let us piggyback on already organized events...
Just thinking
Rochelle Grober wrote:
> Thierry Carrez wrote:
>> One question I have is whether we'd need to keep the "QA" project team at
>> all. Personally I think it would create confusion to keep it around, for no
>> gain.
>> SIGs code contributors get voting rights
der turning other non-purely-upstream teams
(like I18n) in the future.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
vember/000149.html
Please continue the discussion there, to avoid the cross-posting.
If you haven't already, please subscribe at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
--
Thierry Carrez (ttx)
signature.asc
Description: OpenPGP
subscribe at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
istinfo/openstack-sigs
While I'm not sure that's the best name for it, as suggested by Rocky
let's use [lts] as a prefix there.
I'll start a couple of threads.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.opensta
ng OS/PyPI substrate) and enable whoever steps
up to maintain longer-lived branches to come up with a set of tests that
actually match their needs (tests that would be less likely to bitrot
due to changing OS/PyPI substrate).
A number of people from all backgrounds volunteered to flesh out a more
detaile
y help, even if there will be some pain setting them up and getting
the right readership to them :)
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
to coordinate their actions. Because if they try to affect upstream
separately, they won't go far, and we badly need them involved.
Yes, it's mostly a rebranding exercise, but perception matters.
Hope this clarifies,
--
Thierry Carrez (ttx)
___
Tim Bell wrote:
> Yes, I agree it is difficult… I was asking as there was an option ‘watch
> later’ on the summit schedule for the fishbowl sessions.
>
> The option should probably be removed from the summit schedule web page so
> people don’t get disappointed later if that is not too
ead for each
session, summarizing the outcome and opening up the discussion to
everyone who could not be present in person for one reason or another.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
h
ed in a
session, I encourage you to mention it in the description, for them to
pick it up at scheduling time. Also, once the schedule is up, if you see
a missing tag, feel free to reach out to them so that they add it.
--
Thierry Carrez (ttx)
___
OpenStack
ed this "mini-Forum" thread to
compensate while we transition to the new layout :)
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
mmunity (one release announce email
per cycle at the end of the release, urgent security advisories,
election announcements, etc...) and be very low-traffic again. You can
find it here:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce
Regards,
--
Thierry Carrez wrote:
> lebre.adr...@free.fr wrote:
>> After Thierry's cleaning, the possibilities are the following ones:
>>
>> Wednesday 14 UTC (odd week)
>> Wednesday 17 UTC
>> Thursday 14 UTC (odd week)
>> Thursday 16 UTC (even week)
>> Thu
an option.
Also note that Thursday 14 UTC is currently taken. Trying to free up the
slot with https://review.openstack.org/#/c/395509 but they may want to
keep it.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lis
Thierry Carrez wrote:
> [...]
> That said, it's a balancing act and we may be past the point when
> scheduling pain takes over the need to spread meetings out. I'll do a
> quick pass to try to free up slots taken by dead meetings, and if we
> can't free enough slots we'll likely ad
rc
That said, it's a balancing act and we may be past the point when
scheduling pain takes over the need to spread meetings out. I'll do a
quick pass to try to free up slots taken by dead meetings, and if we
can't free enough slots we'll likely add a new meeting channel.
--
very similar time.
I doubt there will be more value for you in the PTG, but to open options
for those who want to attend everything, I guess it wouldn't hurt to
place them on separate weeks.
--
Thierry Carrez (ttx)
___
OpenStack-operators mail
to this list ? Maybe we
> should unsubscribe these addresses. Who has admin rights ? Tom ?
Yes that's Tom, but he is off for the week, so that might take some
extra time to be handled.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing
ch potential tools for (3) and (4).
Thanks again for the feedback!
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
, make sure to
check if your use case is mentioned on the etherpad at:
https://etherpad.openstack.org/p/wiki-use-cases
If not, please add your use case, together with the URL of such a wiki
page to that etherpad.
Thanks in advance,
--
Thierry Carrez (ttx
d downstream contributors, because both aspects are
equally important.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
working, and it's too early (in terms of team results) to apply to be an
official team. Just setting up the git repo under the OpenStack
infrastructure sounds like a reasonable solution ?
--
Thierry Carrez (ttx)
___
OpenStack-operators mail
we need some excuse to
> publish the docs to the docs.openstack.org <http://docs.openstack.org> -
> like being now part of 'Rally' program.
OK, sounds good as a workaround solution :)
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing
oard of Directors. It's not trivial to
fix (since the election system is obviously pretty deeply embedded in
the bylaws).
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.or
- I
would expect operators to be fairly consensual candidates and get
elected. It's the cumulative voting system that is broken :)
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstac
by operators
rather than directly by the Rally project team ? If not, it's probably
fine to get that one defined as other upstream-maintained tags in the
same family.
Cheers,
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operato
to Afghans.
I think growing up is accepting the pain that comes with picking a
good name, rather than sidestepping the issue.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http
there is any reason not to converge into a single
framework where both types of data are accommodated.
Right, a single project metadata framework which provides tags and
structured data (open to suggestion on how to better call that) about
OpenStack projects.
Cheers,
--
Thierry Carrez (ttx
get why you want to reuse the exact same word for it.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
magically
the same. It will just confuse people.
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
picture. My
personal suggestion would be ops-data, but I don't really care which
color you paint that bikeshed (as long as it's not blue!).
Thanks for reading so far, hoping we can work within the same framework
to communicate the best information to all the consumers of our ecosystem.
--
Thierry
, the only interesting bit of
information is what is the first release cycle the packaging appeared
in, so you could actually have:
- repo: openstack/nova
tags:
- name: packaged:centos
since: diablo
I think it's easier and simpler to maintain.
--
Thierry Carrez (ttx
different things. That will open the door
to defining tags on top of it.
And if the ops WG is only interested in publishing the complex metadata,
I guess a workgroup around the TC could take up the work of turning that
data into a set of tags.
--
Thierry Carrez (ttx
-- the
discussion we had in Vancouver was that we should define subjectively
what well-packaged means, and than apply it objectively. Same for the
other ops tags. So I think we are actually on the same line...
--
Thierry Carrez (ttx)
___
OpenStack-operators mailing
of stable
updates for all projects though
In the spirit of avoiding cross-posting and broken threads, I invite you
to read the post at:
http://lists.openstack.org/pipermail/openstack-dev/2015-May/065144.html
You can either comment there or on the thread here. I'll follow both.
Cheers,
--
Thierry
59 matches
Mail list logo
