Open Stack

Hi all

We are still experiencing some issues with master node bootstrapping after
moving to container-based installation.

First of all, these issues are related to our system tests. We have rather
small nodes running as master node - only 1 GB of RAM and 1 virtual CPU. As
we are using strongly lrzipped archive, this seems quite not enough and
leads to timeouts during deployment of the master node.

I have several suggestions:

1) Increase amount of RAM for  master node to at least 8 Gigabytes (or do
some pci virtual memory hotplug during master node bootstrapping) and add
additional vCPU for the master node.
2) Run system tests with non-containerized environment (env variable
PRODUCTION=prod set)
3) Split our system tests in that way not allowing more than 2 master nodes
to bootstrap simulteneously on the single hardware node.
4) do lrzipping as weak as possible during the development phase and lrzip
it strongly only when we do release
5) increase bootstrap timeout for the master node in system tests


Any input would be appreciated.

-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
45bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin at mirantis.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140510/21323b2a/attachment.html>