On Wed, 27 Jun 2018 10:19:17 +0900 Ghanshyam Mann
wrote
> ++ operator ML
>
> On Wed, 27 Jun 2018 10:17:33 +0900 Ghanshyam Mann
> wrote
> >
> >
> >
> > On Tue, 26 Jun 2018 23:12:30 +0900 Doug Hellmann
> wrote
> > > Excerpts from
++ operator ML
On Wed, 27 Jun 2018 10:17:33 +0900 Ghanshyam Mann
wrote
>
>
>
> On Tue, 26 Jun 2018 23:12:30 +0900 Doug Hellmann
> wrote
> > Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400:
> > > On Tue, Jun 26, 2018 at 08:53:21AM
Sean put together some really great things here and I do think the SiG
might be the way to go as far as ownership for the repos and the plan looks
pretty complete. I've offered to do the Git and Gerrit Lunch and Learn at
the OPS mmetup if needed to help get folks set up and going.
Amy (spotz)
On
On Tue, 26 Jun 2018 12:36:52 -0500
Sean McGinnis wrote:
> >
> > Plan
> >
> > So to recap above, I would propose the following actions be taken:
> >
> > 1. Create sig-operators as a group to manage operator efforts at least
> > related
> >to what needs to be done in repos.
> > 2.
In diagnosing a situation where a Pike deployment was intermittently
slower (in general), I discovered that it was (sometimes) exceeding
memcached's maximum connection limit, which is set to 4096.
Looking closer, ~2750 of the connections are from 8 neutron-server
process. neutron-server is
>
> Plan
>
> So to recap above, I would propose the following actions be taken:
>
> 1. Create sig-operators as a group to manage operator efforts at least related
>to what needs to be done in repos.
> 2. Create an openstack/operations-guide repo to be the new home of the
>operations
This sounds great. As I understand it Sean can set up a skeleton for us to
work on ops docs (and maybe other things later) with a minimum of
initiation energy. Count me in.
Chris
On Tue, Jun 26, 2018 at 12:42 PM Sean McGinnis
wrote:
> Reviving this thread with a fresh start. See below for the
Reviving this thread with a fresh start. See below for the original.
To recap, the ops community is willing to take over some of the operator
documentation that is no longer available due to the loss of documentation team
resources. From discussions, there needs to be some official governance
