File: prerequisites.rst

package info (click to toggle)
murano 1%3A6.0.0-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 10,644 kB
  • sloc: python: 34,127; sh: 717; pascal: 269; makefile: 83
file content (178 lines) | stat: -rw-r--r-- 5,370 bytes parent folder | download | duplicates (2)
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
===================
System requirements
===================

This section provides basic information about the murano environment system
requirements. Additionally, it contains a description of the performance
test scenario, which you may use to check if your hardware fits
the requirements. To do this, run the test and compare the results with
the baseline data provided.

Software prerequisites
~~~~~~~~~~~~~~~~~~~~~~

Before you install murano, verify your system meets the following
prerequisites.

**Supported operating systems:**

* Ubuntu Server 14.04 LTS
* RHEL/CentOS
* Debian

**System packages for Ubuntu:**

* gcc
* python-pip
* python-dev
* libxml2-dev
* libxslt-dev
* libffi-dev
* libpq-dev
* python-openssl
* mysql-client

**System packages for CentOS:**

* gcc
* python-pip
* python-devel
* libxml2-devel
* libxslt-devel
* libffi-devel
* postgresql-devel
* pyOpenSSL
* mysql

Hardware requirements
~~~~~~~~~~~~~~~~~~~~~

We recommend that your system meets the following hardware 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 improves the read           |                      |
|            | performance almost twice)      |                      |
+------------+--------------------------------+----------------------+

Other possible storage configurations:

* 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 the directory where the virtual
  machines images are stored)

* 1x HDD (15000 rpm) 500+ GB

Testing the performance
~~~~~~~~~~~~~~~~~~~~~~~

We have measured the time required to boot 1 to 5 instances of the Windows
operating system simultaneously. You can use this data as the baseline
to check if your system is fast enough.

.. note::

   Use *sysprepped* images for this test to simulate an instance first boot.

To reproduce the performance test, proceed with the following steps:

#. Prepare a Windows 2012 Standard (with GUI) image in the ``QCOW2`` format.
   This example uses the ``ws-2012-std.qcow2`` image.

#. Verify that there are no KVM processes running on the host:

   .. code-block:: console

      ps aux | grep kvm

#. Make 5 copies of the Windows image file:

   .. code-block:: console

      for i in $(seq 5); do \
      cp ws-2012-std.qcow2 ws-2012-std-$i.qcow2; done

#. Create the ``start-vm.sh`` script in the directory with the ``.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 using the command below (as root) and measure time
   between the instance launch and the moment when the Server Manager window
   displays.

   .. code-block:: console

      sudo ./start-vm.sh 1

   To view the instance desktop, connect with VNC viewer to your host
   to VNC screen :1 (port 5901).

#. Turn off the instance. You may simply kill all KVM processes by running:

   .. code-block:: console

      sudo killall kvm

#. Start FIVE instances with the command below (as root) and measure time
   interval between ALL instances launch and the moment when the LAST
   Server Manager window displays.

   .. code-block:: console

      sudo ./start-vm.sh 5

   To view VM's desktops, connect with VNC viewer to your
   host to VNC screens :1 thru :5 (ports 5901-5905).

#. Turn off the instances. You may simply kill all KVM processes by running:

   .. code-block:: console

      sudo killall kvm

Baseline data
-------------

The table below provides the baseline data that was received in our test
murano environment.

+--------------------------+--------------------------+---------------------+
|                          | Boot ONE instance        | Boot FIVE instances |
+==========================+==========================+=====================+
| Avg. Time                | 3m:40s                   | 8m                  |
+--------------------------+--------------------------+---------------------+
| Max. Time                | 5m                       | 20m                 |
+--------------------------+--------------------------+---------------------+

**Avg. Time**
 Refers to the environment with the recommended hardware configuration

**Max. Time**
 Refers to the minimal hardware configuration

Host optimizations
------------------

You can improve your default KVM installation performance with the following
optimizations up to 30%:

* Change the default scheduler from **CFQ** to **Deadline**
* Use **ksm**
* Use **vhost-net**