Open Stack

Update on the Hypervisor Tuning Guide!

The plan mentioned earlier is still in effect and is in the midst of Step
2. All etherpad notes have been migrated to the OpenStack wiki and I've
recently finished cleaning them up. You can see the current work here[1].

For those who may be wondering "why yet another guide?", I guarantee that 9
out of 10 people who read the guide in its current state will learn
something new. Imagine how much you could learn if it was complete?

If you're interested in contributing, please see the How To Contribute
section[2]. In short: just add what you know to the wiki.

Here's a list of items that would be great to have:

* Information about Hypervisors other than libvirt/KVM.
* Information about operating systems other than Linux.
* Real options, settings, and values that you have found to be successful
in production.
* And ongoing: Continue to expand and elaborate on existing areas.

As mentioned before, there is no definitive timeline for this guide.
There's no plan to have formal meetings or anything like that at the
moment, either. Just an occasional poke to add what you know. However, if
you'd like to see this guide fall under a more formal schedule and would
like to lead that effort, please get in contact with me.

Thanks,
Joe

1: https://wiki.openstack.org/wiki/Documentation/HypervisorTuningGuide
2:
https://wiki.openstack.org/wiki/Documentation/HypervisorTuningGuide#How_to_Contribute


On Tue, Oct 27, 2015 at 9:02 PM, Joe Topjian <joe at topjian.net> wrote:

> We had a great Hypervisor Tuning Guide session yesterday!
>
> We agreed on an initial structure to the guide that will include four core
> sections (CPU, Memory, Network, and Disk) and common subsections to each.
> The etherpad[1] has this structure defined and during the session, we went
> through and added some brief notes about what should be included.
>
> Another agreement was that this guide should be detailed. It should have
> specific actions such as "change the following sysctl setting to nnn"
> rather than being more broad and generic such as "make sure you aren't
> swapping". One disadvantage of this is the guide might become out of date
> sooner than if it was more broad. We felt this was an acceptable tradeoff.
>
> Our current plan is the following:
>
> 1. We're going to leave the etherpad active for the next two weeks to
> allow people to continue adding notes at their leisure. I'll send a
> reminder about this a few days before the deadline.
>
> 2. We'll then transfer the etherpad notes to the OpenStack wiki and begin
> creating a rough draft of the guide. Brief notes will be elaborated on and
> supporting documentation will be added. Areas that have no information will
> be highlighted for help. Everyone is encouraged to edit the wiki during
> this time.
>
> 3. Once a decent rough draft has been created, we'll look into creating a
> formal OpenStack document.
>
> We're all very busy, so there are no definitive timelines for completing
> steps 2 and 3. At a minimum, we'll continue to touch base with this during
> the Summits and mid-cycles. If there's enough interest, we could try to
> schedule a large block of time to do a doc sprint during one of these
> events.
>
> Thanks,
> Joe
>
> 1: https://etherpad.openstack.org/p/TYO-ops-hypervisor-tuning-guide
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151208/0ec4eb2a/attachment.html>