The official documentation would greatly benefit from more practical information such as tuning... most likely in the administration or operations guide, at least for now. Ideally, I would like to see a operators contribute documentation for complete production deployments that others can use as a reference for new deployments and avoid reinventing the wheel.
On Wed, Nov 4, 2015 at 4:27 PM, Leslie-Alexandre DENIS <cont...@ladenis.fr> wrote: > Hello there, > > Very interesting initiative ! I'm currently working on the performance > side too on our (french astrophysics cloud) OpenStack deployment but to say > so currently I'm just following what CERN did regarding to Nova/CPU > configuration. > It's essentially around KSM, NUMA, CPU pinning, EPT and performance > measures are compared through Spec 06 benchmarks, which is standard for > HPC/HTC computing. > > You can take a look at the very interesting blog from CERN here > http://openstack-in-production.blogspot.fr/ and if you want I have few > slides from various meetings like HEPIX on these subjects. > > Following the etherpad ! > > Regards, > > > Le 05/11/2015 00:11, Donald Talton a écrit : > >> Awesome start. Rabbit fd tweaks are the bane of every install...including >> some of my own... >> >> -----Original Message----- >> From: Kevin Bringard (kevinbri) [mailto:kevin...@cisco.com] >> Sent: Wednesday, November 04, 2015 3:56 PM >> To: OpenStack Operators >> Subject: [Openstack-operators] OpenStack Tuning Guide >> >> Hey all! >> >> Something that jumped out at me in Tokyo was how much it seemed that >> "basic" tuning stuff wasn't common knowledge. This was especially prevalent >> in the couple of rabbit talks I went to. So, in order to pool our >> resources, I started an Etherpad titled the "OpenStack Tuning Guide" ( >> https://etherpad.openstack.org/p/OpenStack_Tuning_Guide). Eventually I >> expect this should go into the documentation project, and much of it may >> already exist in the operators manual (or elsewhere), but I thought that >> getting us all together to drop in our hints, tweaks, and best practices >> for tuning our systems to run OpenStack well, in real production, would be >> time well spent. >> >> It's a work in progress at the moment, and we've only just started, but >> please feel free to check it out. Feedback and community involvement is >> super welcome, so please don't hesitate to modify it as you see fit. >> >> Finally, I hate diverging resources, so if something like this already >> exists please speak up so we can focus our efforts on making sure that's up >> to date and well publicized. >> >> Thanks everyone! >> >> -- Kevin >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> This email and any files transmitted with it are confidential, >> proprietary and intended solely for the individual or entity to whom they >> are addressed. If you have received this email in error please delete it >> immediately. >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
