Next week is the OpenStack Summit conference. eNovance’s team will be present at the event. The convention is going to be awesome, I saw plenty of amazing sessions and I really look forward to attending those talks. Speaking about session, Emilien Macchi and I will give a talk about High Availability in OpenStack. You can check the talk page here. Hope to see you there!
Just started with Grizzly and already been through some minor issues :).
One of the most annoying thing is when the resolv.conf of your VM keeps changing because of the information sent by the DNSMASQ process. In this article, I assume that your setup has some conventions such as:
10.100.$ID.0/24
Availability zone in OpenStack. The main purpose of this article is to play a bit with availability zones.
Some tips for performing smooth maintenance in OpenStack.
Make consistent instance or volume snapshots.
I don’t want to see my logs poluted by INFO messages saying “hey, I’m running!”. No thanks, it burns my I/O cycles for nothing. If it doesn’t work I have a monitoring system for that and if it’s broken I simply change the log level to DEBUG. Of course it’s personal thoughts, however for those you who are interested just click ;-).
While waiting for the Ceilometer project to be ready, nova provides some facilities to retrieve simple statistics. A little overview about the available commands.
I couple of days ago I noticed that I never tested the overcommit capability in OpenStack
Short introduction to quota in OpenStack.