AFAIR, we created this restriction because VM instances may eat all CPUs and then there will be a lot of problems with DB performance. We just prohibited a user from doing such "shoot-in-leg" configuration. We suggest to use a number of virtual machines as a demo/playground environment instead.
On Mon, Sep 29, 2014 at 6:43 AM, Aleksandr Vorobiov <[email protected]> wrote: > Hello everyone, > > 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. > > The question is: is this behaviour expected and what issues could be > faced in such setup? > > Thank you in advance. > > -- > Mailing list: https://launchpad.net/~fuel-dev > Post to : [email protected] > Unsubscribe : https://launchpad.net/~fuel-dev > More help : https://help.launchpad.net/ListHelp > > -- Andrey Danin [email protected] skype: gcon.monolake
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
