://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-operators/2018-September/015919.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack
them
over the next week.
[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack
either might be resulting in
subscribers missing it.
[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
community SIG to cover it?
[...]
It may also be worthwhile to ask this on the openstack-sigs mailing
list.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openst
its initial location for crowd-sourcing/brainstorming, but
will get published to a more durable location like on
lists.openstack.org itself or perhaps the Project-Team Guide once
the list is in use.
--
Jeremy Stanley
signature.asc
Description: PGP signature
down for good).
[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack
] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
s/events, we discussed putting that here as well.
It seems a fine plan, just keep in mind that documenting and
publishing feedback doesn't magically translate into developers
acting on any of it (and this is far from the first time it's been
attempted).
--
Jeremy St
enstack.org/p/common-openstack-ml-topics
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
place and the measure doesn't make any
attempt to change that. We also don't regulate where unofficial
discussions are allowed to take place, and so it doesn't open up any
new possibilities which were previously disallowed.
--
Jeremy Stanley
signature.asc
Descr
ue to be missing from these
discussions.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
they shouldn't be the PTL. The same
> goes for TC members IMO.
Completely agree, I think we might just disagree on where to strike
the balance of purely technical priorities for the TC (as I
personally think the TC is somewhat incorrectly named).
--
Jeremy Stanley
signature.asc
Des
On 2018-09-12 16:03:12 -0600 (-0600), Zhipeng Huang wrote:
> On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> > On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> > [...]
> > > So I encourage all elected TC members to work directly with the
> >
hate to give the impression
that you must be on the TC to have such an impact.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mail
On 2018-09-06 15:03:52 -0500 (-0500), Matt Riedemann wrote:
> On 9/6/2018 2:56 PM, Jeremy Stanley wrote:
> > On 2018-09-06 14:31:01 -0500 (-0500), Matt Riedemann wrote:
> > > On 8/29/2018 1:08 PM, Jim Rollenhagen wrote:
> > > > On Wed, Aug 29, 2018 at 12:51 PM, Ji
> > // jim
>
> FYI for those that didn't see this on the other ML:
>
> http://lists.openstack.org/pipermail/foundation/2018-August/002617.html
[...]
While I agree that's a great post to point out to all corners of the
community, I don't see what it has to do with whether "
t usually tell them to take their questions elsewhere any more).
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/
IT's
listadmins have posted some so we don't need to:
http://web.mit.edu/lists/mailman/topics.html
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.op
me
message, or merely linked to a published document (and whether
that's best suited for the Infra Manual or New Contributor Guide or
somewhere else entirely is certainly up for debate), or even
potentially both.
--
Jeremy Stanley
signature.asc
Descr
and
become part of that process. Requiring them to have their
conversations elsewhere sends the opposite message.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.op
*lot*
of "black hole" subscribers who aren't actually following that list
but whose addresses aren't bouncing new posts we send them for any
of a number of possible reasons.
--
Jeremy Stanley
signature.asc
Description: PGP signature
__
upport in
Mailman unless we can somehow work with them to help in
reimplementing it.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/m
ling lists is not lost on me. ;)
[1] https://etherpad.openstack.org/p/YVR-ops-devs-one-community
[2] https://etherpad.openstack.org/p/common-openstack-ml-topics
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators ma
an also tell by looking at the general project properties:
https://review.openstack.org/#/admin/projects/openstack/operations-guide
"Require a valid contributor agreement to upload" there is "INHERIT
(false)" which indicates it's not set.
--
Jeremy Stanley
signatur
On 2018-08-09 09:56:47 +0200 (+0200), Thierry Carrez wrote:
> Jeremy Stanley wrote:
> > [...]
> > It does indeed sound like you might be caught up in the
> > aforementioned SASL-only network blacklist (I wasn't even aware of
> > it until this ML thread) which Free
ndependent
from the Infra team measure to require nick registration in official
OpenStack IRC channels, but certainly another symptom of the same
fundamental problem.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-
m connecting to
Freenode. You only need to be in a server buffer and connected to be
able to `/msg nickserv ...` but don't need to be in any channels at
all so shouldn't be a chicken-and-egg scenario.
--
Jeremy Stanley
signature.asc
Description: PGP signature
_
> >
> > Doug
> >
>
> We've been around 100ish so pretty light
How does it compare to respondent count from previous surveys about
organizing operations-focused gatherings?
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
oyers find the tag useful at all. If you or
your organization relies on this tag in any way, the OpenStack
Technical Committee would like to hear about it so they can know
whether continuing to track it is in any way an effective use of
time. Thanks!
--
Jeremy Stanley
signature.asc
Description: PGP
nStack Foundation and doesn't even require any
account on www.openstack.org for now, just login.ubuntu.com (this
will likely change in the future when we eventually switch OpenID
providers).
--
Jeremy Stanley
signature.asc
Description: PGP sig
l) to be
able to do so. Participation in the survey is not mandatory, but
still much appreciated as it helps the OpenStack project
contributors better determine where improvements are most needed.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenS
ligible to do so.
--
Jeremy Stanley
signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
are (and
vice versa). Having dedicated events and separate named identities
for these overlapping groups of people serves only to further divide
us, rather than bring us together where we can better draw on our
collective strengths to make something great.
--
Jeremy Stanley
signature.asc
Descript
ity risks exposed by DEBUG level
logging to be only hardening opportunities, and as such these often
linger unfixed or don't get backported to earlier releases (in other
words, we consider running in production with DEBUG level logging to
be a risky from an information security standpoint).
--
Jerem
to know how your deployments are. This is the area
> that deployment tools (like ansible, tripleo, fuel and so on)
> handle.
[...]
The burgeoning discussions about an etcd backend for oslo.config may
be relevant to this piece of the problem.
--
Jeremy Stanley
signature.asc
Description:
opic. Add "[horizon]" to the subject
line for more visibility within that team.
You can also sometimes find Horizon team regulars hanging out in the
#openstack-horizon channel on the Freenode IRC network if you need
to bounce ideas off someone in a more synchronous conversation.
ons (and expect other TC members feel the same).
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
oes not work ??
Perhaps not the answer you are looking for, but the metadata service
is far less reliable in most cases than using configdrive metadata
(which recent cloud-init releases should support fine).
--
Jeremy Stanley
signature.asc
Description: Digit
a database validation tool now? If we do,
is it deficient in some way? If we don't, what specifically should
it be checking? Seems like something we would also want to run at
the end of all our upgrade tests too.
--
Jeremy Stanley
signature.asc
Description: Digital signature
_
between
those two LTS releases will _also_ involve in-place upgrading of
Ubuntu.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Committee,
> not Thierry Carrez but I could be wrong.)
[...]
I never connected those before, but now I get why he was so keen to
replace the PPB with the TC. ;)
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-operators mailing li
e down to the
individual instance being targeted or used rather than knocking the
entire compute node offline (hopefully anyway), and is no substitute
for actual attack mitigation devices/services inline on the network.
--
Jeremy Stanley
signature.asc
Descri
bly helps, but I consider any public cloud which
doesn't give you some means of automatically setting reverse DNS
(either through an API or delegation to your own nameservers) to be
thoroughly broken, at least for Internet-facing use cases.
--
Jeremy Stanley
signature.asc
Description: Digital
y depended on this
service.
[1] https://review.openstack.org/452086
[2] https://apps.openstack.org/
[3] https://git.openstack.org/cgit/openstack/app-catalog/
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-operators mailing list
will queue at the senders' MTAs
until the server is back in service and so should not result in any
obvious disruption.
Apologies for cross-posting so widely, but we wanted to make sure
copies of this announcement went to most of our higher-traffic
lists.
--
Jeremy Stanley
signature.asc
messages bound for the server will
queue at the senders' MTAs until the server is back in service and
so should not result in any obvious disruption.
Apologies for cross-posting so widely, but we wanted to make sure
copies of this announcement went to most of our higher-traffic
lists.
--
Jeremy
tually
necessary?
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
. Lots of things, for example facter, like to beat on it heavily
which makes for a fun DDoS and so is a bit of a scaling challenge in
large deployments.
There are probably plenty more I don't know since I'm not steeped in
operating OpenStack deployments.
--
Jeremy S
le, "We're all in it together."
I understand you'll probably end up using whatever tools you're
familiar/comfortable with and which help you accomplish your goals,
I just ask that you keep in mind that publicly recommending non-free
tools in the service of free software development sets
n our community workflows and governance,
that might help us understand where to focus on improving so we can
better serve your needs in the future.
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
sticsearch filesystem).
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
https://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/elasticsearch_node.pp
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/li
or want additional information on
this maintenance.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
ase using our trademarked logo), so that we
hopefully don't need to resort to blocking their MTAs and reporting
them to spam blacklists.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.
On 2016-05-20 14:55:31 + (+), Jeremy Stanley wrote:
[...]
> The "users" being defined for AUC include a lot of roles orthogonal
> to software user personas
[...]
I also could have probably better phrased this as what's being
worked out in the context of AUC is not w
s: organizers of community user group
meetings, moderators on panels or track chairs at conferences,
members of board-appointed working groups, authors of articles,
people who answer questions in and police online forums... I don't
think the term "user" here is being employed in the
On 2016-05-17 16:42:43 + (+), Jeremy Stanley wrote:
> On 2016-05-17 17:30:31 +0100 (+0100), Matt Jarvis wrote:
> > We've noticed that as well, is everyone getting strange bounces from
> > openstack-private ? Any list admins lurking here ?
>
> I have a feeling that
On 2016-05-17 16:42:43 + (+), Jeremy Stanley wrote:
> On 2016-05-17 17:30:31 +0100 (+0100), Matt Jarvis wrote:
> > We've noticed that as well, is everyone getting strange bounces from
> > openstack-private ? Any list admins lurking here ?
>
> I have a feeling that
but I guess I'll find out when it
bounces back to my reply.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
wiki account and an interest in this topic could volunteer
to help them capture the details there for now.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listin
l
address match) are the most common reasons for the error you're
reporting. Also check out https://ask.openstack.org/question/56720
for some additional troubleshooting suggestions.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@list
tter involved in
these events, but making everyone an "ATC" isn't really the solution
to that problem.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
ortunately the original poster
cross-posted this thread to multiple mailing lists so the discussion
has rapidly bifurcated, but I addressed this particular topic in my
http://lists.openstack.org/pipermail/openstack-dev/2015-November/078735.html
reply.
--
Jeremy Stanley
___
come to collaborate on maintaining this (or any) resource on
which they depend. It's all a matter of individual priority.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
analysis answering this exact question. See page 22 (labeled 21) of
https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf
for a very appropriate graph.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack
-Project_Meeting
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-gratis participants:
http://debconf15.debconf.org/registration.xhtml#registration
But basically if you want to go and you or your employer can't/won't
cough up enough € for professional or corporate registration, then
you attend as a private participant for free.
--
Jeremy Stanley
-in-ubuntu and packaged-in-centos? Of course there's still
some ambiguity over details like how new is the packaged version?
and in what release(s) of the distro? but those are probably
things you could build tag-qualifying rules around.
--
Jeremy Stanley
://wiki.openstack.org/wiki/OSSN/OSSN-0027
--
Jeremy Stanley
signature.asc
Description: Digital signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
.
Anyway, this is just an attempt to level-set and spur the discussion
onward to actionable solutions rather than continuing to debate in
the abstract. Hopefully it takes us in a good direction.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack
On 2014-12-18 01:57:20 + (+), Jeremy Stanley wrote:
[...]
Anyway, this is just an attempt to level-set and spur the
discussion onward to actionable solutions rather than continuing
to debate in the abstract. Hopefully it takes us in a good
direction.
I meant to add that as an outcome
be a mark against
Debian's OpenStack packages.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
for packagers on a
variety of platforms, so any feedback like this is helpful to drive
future improvements on that front.
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin
RFC 2119? ;)
--
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
74 matches
Mail list logo
