Document the all-in-one deployment option

[Meg McRoberts]

Document how to deploy bare-metal MOSt on a single server. This will be a section in the Operations Guide, with a link
from the Planning Guide section about hardware requirements.

Include appropriate warnings about the risks of doing this and point out that deploying MOSt on VirtualBox may be
a more reliable method to demonstrate MOSt on minimal hardware.

Include a list of configuration options that increase the odds of problems -- probably Ceilometer/MongoDB, Ceph,
Zabbix...

[Meg McRoberts (dreidellhasa)]

From Aleksandr Vorobiov:
Recently I've been playing and trying to install MOS in "all in one" mode, i.e. all services should be setup in one node. To accomplish this I've edited the file /usr/lib/python2.6/site-packages/nailgun/fixtures/openstack.yaml in nailgun docker container. I've removed instructions which describe conflicts between roles:

----------------------------------------------------------------
controller:
name: "Controller"
description: "The controller initiates orchestration activities and provides an external API. Other components like Glance (image storage), Keystone (identity management), Horizon (OpenStack dashboard) and Nova-Scheduler are installed on the controller as well."
conflicts:
- compute
---------------------------------------------------------------------------------------------------

Strings in red were removed.

After that I was able to assign controller, cinder and compute roles on a single node. After finishing deployment I was able to complete OSTF tests and checked installation manually, at first glance everything works well.

[Manikandan R (maniram477)]

I am trying to deploy an AIO node using Fuel 7.0. I removed the conflict section as mentioned by Meg McRoberts. Is there anything else to be done ...
Can anyone explain the process briefly ???

[TeYen Liu (teyen-liu)]

Recently I tried to deploy an all_in_one node ( controller + compute ) using Fuel 7.0 with DVR enabled. It is done. But, I found that the centralised SNAT didn't work, which means the VM without a floating IP cannot access to Internet via external network. Is any suggestion about this issue? Thanks.