1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
|
========================
Prepare a lab for murano
========================
This section provides basic information about lab's system requirements.
It also contains a description of a test which you may use to check if
your hardware fits the requirements. To do this, run the test and
compare the results with baseline data provided.
.. _system_prerequisites:
System prerequisites
~~~~~~~~~~~~~~~~~~~~
Supported operating systems
---------------------------
* Ubuntu Server 12.04 LTS
* RHEL/CentOS 6.4
**System packages are required for Murano**
*Ubuntu*
* gcc
* python-pip
* python-dev
* libxml2-dev
* libxslt-dev
* libffi-dev
* libpq-dev
* python-openssl
* mysql-client
Install all the requirements on Ubuntu by running::
sudo apt-get install gcc python-pip python-dev \
libxml2-dev libxslt-dev libffi-dev \
libpq-dev python-openssl mysql-client
*CentOS*
* gcc
* python-pip
* python-devel
* libxml2-devel
* libxslt-devel
* libffi-devel
* postgresql-devel
* pyOpenSSL
* mysql
Install all the requirements on CentOS by running::
sudo yum install gcc python-pip python-devel libxml2-devel \
libxslt-devel libffi-devel postgresql-devel pyOpenSSL \
mysql
.. _lab_requirements:
Lab requirements
----------------
+------------+--------------------------------+-----------------------+
| Criteria | Minimal | Recommended |
+============+================================+=======================+
| CPU | 4 core @ 2.4 GHz | 24 core @ 2.67 GHz |
+------------+--------------------------------+-----------------------+
| RAM | 8 GB | 24 GB or more |
+------------+--------------------------------+-----------------------+
| HDD | 2 x 500 GB (7200 rpm) | 4 x 500 GB (7200 rpm) |
+------------+--------------------------------+-----------------------+
| RAID | Software RAID-1 (use mdadm as | Hardware RAID-10 |
| | it will improve read | |
| | performance almost two times) | |
+------------+--------------------------------+-----------------------+
`Table: Hardware requirements`
There are a few possible storage configurations except the shown above.
All of them were tested and were working well.
* 1x SSD 500+ GB
* 1x HDD (7200 rpm) 500+ GB and 1x SSD 250+ GB (install the system onto
the HDD and mount the SSD drive to folder where VM images are)
* 1x HDD (15000 rpm) 500+ GB
Test your lab host performance
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We have measured time required to boot 1 to 5 instances of Windows
system simultaneously. You can use this data as the baseline to check if
your system is fast enough.
You should use sysprepped images for this test, to simulate VM first
boot.
Steps to reproduce test:
#. Prepare Windows 2012 Standard (with GUI) image in QCOW2 format. Let's
assume that its name is ws-2012-std.qcow2
#. Ensure that there is NO KVM PROCESSES on the host. To do this, run
command:
.. code-block:: console
ps aux | grep kvm
#. Make 5 copies of Windows image file:
.. code-block:: console
for i in $(seq 5); do \
cp ws-2012-std.qcow2 ws-2012-std-$i.qcow2; done
#. Create script start-vm.sh in the folder with .qcow2 files:
.. code-block:: console
#!/bin/bash
[ -z $1 ] || echo "VM count not provided!"; exit 1
for i in $(seq $1); do
echo "Starting VM $i ..."
kvm -m 1024 -drive file=ws-2012-std-$i.qcow2,if=virtio -net user -net nic,model=virtio -nographic -usbdevice tablet -vnc :$i & done
#. Start ONE instance with command below (as root) and measure time
between VM's launch and the moment when Server Manager window
appears. To view VM's desktop, connect with VNC viewer to your host
to VNC screen :1 (port 5901):
.. code-block:: console
sudo ./start-vm.sh 1
#. Turn VM off. You may simply kill all KVM processes by
.. code-block:: console
sudo killall kvm
#. Start FIVE instances with command below (as root) and measure time
interval between ALL VM's launch and the moment when LAST Server Manager
window appears. To view VM's desktops, connect with VNC viewer to your
host to VNC screens :1 thru :5 (ports 5901-5905):
.. code-block:: console
sudo ./start-vm.sh 5
#. Turn VMs off. You may simply kill all KVM processes by
.. code-block:: console
sudo killall kvm
Baseline data
~~~~~~~~~~~~~
The table below provides baseline data which we've got in our
environment.
+----------------+--------------------------+---------------------+
| | Boot 1 instance | Boot 5 instances |
+================+==========================+=====================+
| Avg. Time | 3m:40s | 8m |
+----------------+--------------------------+---------------------+
| Max. Time | 5m | 20m |
+----------------+--------------------------+---------------------+
``Avg. Time`` refers to the lab with recommended hardware configuration,
while ``Max. Time`` refers to minimal hardware configuration.
Host optimizations
~~~~~~~~~~~~~~~~~~
Default KVM installation could be improved to provide better
performance.
The following optimizations may improve host performance up to 30%:
* change default scheduler from ``CFQ`` to ``Deadline``
* use ``ksm``
* use ``vhost-net``
|
