On 2017-11-15 00:37:26 + (+), Fox, Kevin M wrote:
[...]
> One idea is that at the root of chaos monkey. If something is
> hard, do it frequently. If upgrading is hard, we need to be doing
> it constantly so the pain gets largely eliminated. One idea would
> be to discourage the use of
John Dickinson wrote:
> What I heard from ops in the room is that they want (to start) one
> release a year who's branch isn't deleted after a year. What if that's
> exactly what we did? I propose that OpenStack only do one release a year
> instead of two. We still keep N-2 stable releases around.
Hello Guys,
after upgrading livirt to 3.2 version, ceilometer on compute gives some
erros, for example:
can not get info from libvirt: 'perf.cpu_cycles'
Must I modify some configuration on ceilometer or libvirt ?
After upgrading gnocchi does not how measures for instances.
Please, help me
I suggested by Rocky, I moved the discussion to the -sigs list by
posting my promised summary of the session at:
http://lists.openstack.org/pipermail/openstack-sigs/2017-November/000148.html
Please continue the discussion there, to avoid the cross-posting.
If you haven't already, please
Rochelle Grober wrote:
> Folks,
>
> This discussion and the people interested in it seem like a perfect
> application of the SIG process. By turning LTS into a SIG, everyone can
> discuss the issues on the SIG mailing list and the discussion shouldn't end
> up split. If it turns into a
