| 2014-08-25 18:55:04 |
Roman Alekseenkov |
bug |
|
|
added bug |
| 2014-08-25 18:55:29 |
Roman Alekseenkov |
description |
I believe we should define a set of supported scenarios for the VirtualBox, update our scripts, update release notes and also quick start on Mirantis portal. At least to tell the users what they CAN and CANNOT do under VirtualBox (e.g. having a full-blown HA with Ceph is unrealistic even on 32GB laptop)
My suggestions is to introduce something along the lines of:
config_4GB.sh - non-HA, 1 controller, 1 compute
config_8GB.sh - non-HA, 1 controller, 3 compute nodes
config_16GB.sh - HA, 3 controllers, 1 compute
This is actually triggered by the latest discussion on fuel-dev.
>> Digging the issue with Galera, I found that our environments have very high RAM utilization which leads to the problem during environment deployment. For instance "HA deployment + neutron/GRE" requires almost 2.6-2.7 GB during deployment (corosync+mysql+puppet++rabbit+neutron+ovs+openstack services). I found high swap in/swap out usage during deployment with very high load average. This creates many sporadic issues with some services. They time out in random place making our debugging very hard. I would like to review our policy for CI environment and increase RAM (at least for bvt tests) to 3 GB. |
I believe we should define a set of supported scenarios for the VirtualBox, update our scripts, update release notes and also quick start on Mirantis portal. At least to tell the users what they CAN and CANNOT do under VirtualBox (e.g. having a full-blown HA with Ceph is unrealistic even on 16GB laptop)
My suggestions is to introduce something along the lines of:
config_4GB.sh - non-HA, 1 controller, 1 compute
config_8GB.sh - non-HA, 1 controller, 3 compute nodes
config_16GB.sh - HA, 3 controllers, 1 compute
This is actually triggered by the latest discussion on fuel-dev.
>> Digging the issue with Galera, I found that our environments have very high RAM utilization which leads to the problem during environment deployment. For instance "HA deployment + neutron/GRE" requires almost 2.6-2.7 GB during deployment (corosync+mysql+puppet++rabbit+neutron+ovs+openstack services). I found high swap in/swap out usage during deployment with very high load average. This creates many sporadic issues with some services. They time out in random place making our debugging very hard. I would like to review our policy for CI environment and increase RAM (at least for bvt tests) to 3 GB. |
|
| 2014-08-25 18:55:37 |
Roman Alekseenkov |
description |
I believe we should define a set of supported scenarios for the VirtualBox, update our scripts, update release notes and also quick start on Mirantis portal. At least to tell the users what they CAN and CANNOT do under VirtualBox (e.g. having a full-blown HA with Ceph is unrealistic even on 16GB laptop)
My suggestions is to introduce something along the lines of:
config_4GB.sh - non-HA, 1 controller, 1 compute
config_8GB.sh - non-HA, 1 controller, 3 compute nodes
config_16GB.sh - HA, 3 controllers, 1 compute
This is actually triggered by the latest discussion on fuel-dev.
>> Digging the issue with Galera, I found that our environments have very high RAM utilization which leads to the problem during environment deployment. For instance "HA deployment + neutron/GRE" requires almost 2.6-2.7 GB during deployment (corosync+mysql+puppet++rabbit+neutron+ovs+openstack services). I found high swap in/swap out usage during deployment with very high load average. This creates many sporadic issues with some services. They time out in random place making our debugging very hard. I would like to review our policy for CI environment and increase RAM (at least for bvt tests) to 3 GB. |
I believe we should define a set of supported scenarios for the VirtualBox, update our scripts, update release notes and also quick start on Mirantis portal. At least to tell the users what they CAN and CANNOT do under VirtualBox (e.g. having a full-blown HA with Ceph is unrealistic even on 16GB laptop)
My suggestion is to introduce something along the lines of:
config_4GB.sh - non-HA, 1 controller, 1 compute
config_8GB.sh - non-HA, 1 controller, 3 compute nodes
config_16GB.sh - HA, 3 controllers, 1 compute
This is actually triggered by the latest discussion on fuel-dev.
>> Digging the issue with Galera, I found that our environments have very high RAM utilization which leads to the problem during environment deployment. For instance "HA deployment + neutron/GRE" requires almost 2.6-2.7 GB during deployment (corosync+mysql+puppet++rabbit+neutron+ovs+openstack services). I found high swap in/swap out usage during deployment with very high load average. This creates many sporadic issues with some services. They time out in random place making our debugging very hard. I would like to review our policy for CI environment and increase RAM (at least for bvt tests) to 3 GB. |
|
| 2014-08-25 18:56:22 |
Roman Alekseenkov |
fuel: importance |
Undecided |
High |
|
| 2014-08-25 19:34:08 |
Nastya Urlapova |
fuel: milestone |
|
5.1 |
|
| 2014-08-25 19:34:26 |
Nastya Urlapova |
fuel: assignee |
|
Miroslav Anashkin (manashkin) |
|
| 2014-08-25 20:02:02 |
Roman Alekseenkov |
fuel: importance |
High |
Medium |
|
| 2014-08-26 14:17:43 |
Miroslav Anashkin |
bug |
|
|
added subscriber Miroslav Anashkin |
| 2014-08-26 14:24:37 |
Miroslav Anashkin |
fuel: status |
New |
Confirmed |
|
| 2014-08-26 21:59:24 |
Andrew Woodward |
tags |
|
docs |
|
| 2014-09-24 00:09:55 |
Miroslav Anashkin |
fuel: status |
Confirmed |
Fix Committed |
|
