Statistics
| Branch: | Tag: | Revision:

root / README.deploy @ 50a48b39

History | View | Annotate | Download (16.6 kB)

1
README.deploy -- Instructions for a basic deployment of Synnefo v0.5.1
2

    
3
This document describes the basic steps to obtain a basic, working Synnefo
4
deployment. It begins by examining the different node roles, then moves to the
5
installation and setup of distinct software components.
6

    
7
It is current as of Synnefo v0.5.1.
8

    
9

    
10
Node types
11
===========
12

    
13
Nodes in a Synnefo deployment belong in one of the following types:
14

    
15
 * DB:
16
   A node [or more than one nodes, if using an HA configuration], running a DB
17
   engine supported by the Django ORM layer. The DB is the single source of
18
   truth for the servicing of API requests by Synnefo.
19
   Services: PostgreSQL / MySQL
20

    
21
 * APISERVER:
22
   A node running the implementation of the OpenStack API, in Django. Any number
23
   of APISERVERs can be used, in a load-balancing configuration, without any
24
   special consideration. Access to a common DB ensures consistency.
25
   Services: Web server, vncauthproxy
26

    
27
 * QUEUE:
28
   A node running the RabbitMQ software, which provides AMQP functionality. More
29
   than one QUEUE nodes may be deployed, in an HA configuration. Such
30
   deployments require shared storage, provided e.g., by DRBD.
31
   Services: RabbitMQ [rabbitmq-server]
32

    
33
 * LOGIC:
34
   A node running the business logic of Synnefo, in Django. It dequeues
35
   messages from QUEUE nodes, and provides the context in which business logic
36
   functions run. It uses Django ORM to connect to the common DB and update the
37
   state of the system, based on notifications received from the rest of the
38
   infrastructure, over AMQP.
39
   Services: the Synnefo logic dispatcher [/logic/dispatcher.py]
40

    
41
 * GANETI-MASTER and GANETI-NODE:
42
   A single GANETI-MASTER and a large number of GANETI-NODEs constitute the
43
   Ganeti backend for Synnefo, which undertakes all VM management functions.
44
   Any APISERVER can issue commands to the GANETI-MASTER, over RAPI, to effect
45
   changes in the state of the VMs. The GANETI-MASTER runs the Ganeti request
46
   queue.
47
   Services:
48
     only on GANETI-MASTER:
49
       the Synnefo Ganeti monitoring daemon [/ganeti/snf-ganeti-eventd]
50
       the Synnefo Ganeti hook [/ganeti/snf-ganeti-hook.py].
51
     on each GANETI_NODE:
52
       a deployment-specific KVM ifup script
53
       properly configured NFDHCPD
54

    
55

    
56
Installation Process
57
=====================
58

    
59
This section describes the installation process of the various node roles in a
60
Synnefo deployment.
61

    
62

    
63
0. Allocation of physical nodes:
64
   Determine the role of every physical node in your deployment.
65

    
66

    
67
1. Ganeti installation:
68
   Synnefo requires a working Ganeti installation at the backend. Installation
69
   of Ganeti is not covered by this document, please refer to
70
   http://docs.ganeti.org/ganeti/current/html for all the gory details. A
71
   successful Ganeti installation concludes with a working GANETI-MASTER and a
72
   number of GANETI-NODEs.
73

    
74

    
75
2. RabbitMQ installation:
76
   RabbitMQ is used as a generic message broker for the system. It should be
77
   installed on two seperate QUEUE nodes (VMs should be enough for the moment)
78
   in a high availability configuration as described here:
79

    
80
     http://www.rabbitmq.com/pacemaker.html
81

    
82
   After installation, create a user and set its permissions
83
     rabbitmqctl add_user okeanos 0k3@n0s
84
     rabbitmqctl set_permissions -p / okeanos  "^.*" ".*" ".*"
85

    
86
   The values set for the user and password must be mirrored in the
87
   RABBIT_* variables in settings.py (see step 6)
88

    
89

    
90
3. Web server installation:
91
   A Web Server (e.g., Apache) needs to be installed on the APISERVERs,
92
   and be configured to run the Synnefo Django project appropriately. Selection
93
   and configuration of a Web server is outside the scope of this document.
94

    
95
   For testing or development purposes, Django's own development server,
96
   `./manage.py runserver' can be used.
97

    
98

    
99
4. Installation of the Synnefo Django project:
100
   As of v0.5 the Synnefo Django project needs to be installed on nodes
101
   of type APISERVER, LOGIC and on the GANETI-MASTER, with a properly
102
   configured settings.py. In later revisions, the specific parts of the Django
103
   project which need to run on each node type will be identified.
104

    
105
   Synnefo is written in Python 2.6 and depends on the following Python modules:
106
   [package versions confirmed to be compatible are in braces]
107

    
108
    * django 1.2 [Django==1.2.4]
109
    * simplejson [simplejson==2.1.3]
110
    * pycurl [pycurl==7.19.0]
111
    * python-dateutil  [python-dateutil==1.4.1]
112
      WARNING: version python-dateutil==2.0 downloaded by pip known *not* to
113
               work with Python 2.6
114
    * python-ipy [IPy==0.75]
115
        also verified to work with python-ipy 0.70-1 as shipped with Squeeze
116
    * south [south==0.7.1]
117
      WARNING: might not work with Debian squeeze's default south-0.7-1 package.
118
    * amqplib [amqplib==0.6.1]
119
    * lockfile [lockfile==0.8]
120
    * python-daemon [python-daemon==1.5.5]
121

    
122
   also, depending on the database engine of choice, on one of the following:
123
    * MySQL-python [MySQL-python==1.2.3]
124
    * psycopg2 [psycopg2==2.4]
125

    
126
   if the invitations application is deployed, the following dependencies should
127
   be installed:
128
    * pycrypto==2.1.0
129

    
130
   To run the user interface tests, selenium must be installed
131
    * selenium [?]
132

    
133
   The easiest method for installation of the Django project is to setup a
134
   working environment through virtualenv. Alternatively, you can use your
135
   system's package manager to install the dependencies (e.g. Macports has them
136
   all).
137

    
138
   * On Snow Leopard and linux (64-bit), you have to set the following
139
     environment variable for pip to compile the dependencies correctly.
140

    
141
  	   $ export ARCHFLAGS="-arch x86_64"
142

    
143
   * On Ubuntu, a few more packages must be installed before installing the
144
     prerequisite Python libraries
145

    
146
	   $ sudo aptitude install libcurl3-gnutls libcurl3-gnutls-dev uuid-dev
147

    
148
   Checkout the code and install the Python prerequisites. This assumes that
149
   python is already installed on the host.
150

    
151
    $ sudo easy_install virtualenv
152
    $ git clone https://user@code.grnet.gr/git/synnefo synnefo
153
    $ virtualenv --python=python2.6 synnefo --no-site-packages
154
    ...
155
    $ cd synnefo
156
    $ ./bin/pip install <list_of_dependencies>
157

    
158
    [WARNING]: The software must be checked out in a directory named synnefo,
159
    otherwise python imports will not work. Therefore, do not change the
160
    or rename the checkout path.
161

    
162

    
163
5. Database installation:
164
   A database supported by the Django ORM layer must be installed on nodes
165
   of type DB. The choices are: SQLIte, MySQL, PostgreSQL.
166

    
167
   * SQLite:
168
     The python sqlite driver is available by default with Python so no
169
     additional configuration is required. Also, most self-respecting systems
170
     have the sqlite library installed by default.
171

    
172
   * MySQL:
173
      MySQL must be installed first:
174

    
175
      * Ubuntu - Debian
176
	      $ sudo apt-get install libmysqlclient-dev
177

    
178
      * MacPorts
179
	      $ sudo port install mysql5
180

    
181
      Install the MySQL python library on servers running the Django project:
182

    
183
	    $ bin/pip install MySQL-python
184

    
185
      Note: On MacOSX with Mysql install from MacPorts the above command will
186
            fail complaining that it cannot find the mysql_config command. Do
187
            the following and restart the installation
188
	        $ echo "mysql_config = /opt/local/bin/mysql_config5" >> \
189
                                         ./build/MySQL-python/site.cfg
190

    
191
      Configure a MySQL db/account for synnefo
192
	    $ mysql -u root -p
193

    
194
    	mysql> create database synnefo;
195
	    mysql> show databases;
196
	    mysql> GRANT ALL on synnefo.* TO username IDENTIFIED BY 'password';
197

    
198
   * PostgreSQL
199
     You need to install the PostgreSQL binaries:
200
     * Ubuntu - Debian
201
	     $ sudo apt-get install postgresql-8.4 libpq-dev
202

    
203
     * MacPorts
204
	     $ sudo port install postgresql84
205

    
206
     Install the postgres Python library
207
	    $ bin/pip install psycopg2
208

    
209
     Configure a postgres db/account for synnefo:
210

    
211
     Become the postgres user, connect to PostgreSQL:
212
       $ sudo su - postgres
213
       $ psql
214
	
215
	 Run the following commands:
216
	   DROP DATABASE synnefo;
217
	   DROP USER username;
218
	   CREATE USER username WITH PASSWORD 'password';
219
	   CREATE DATABASE synnefo;
220
	   GRANT ALL PRIVILEGES ON DATABASE synnefo TO username;
221
	   ALTER DATABASE synnefo OWNER TO username;
222
	   ALTER USER username CREATEDB;
223

    
224
     The last line enables the newly created user to create own databases. This
225
     is needed for Django to create and drop the test_synnefo database for unit
226
     testing.
227

    
228

    
229
6. Setting up the Django project:
230
   The settings.py file for Django may be derived by concatenating the
231
   settings.py.dist file contained in the Synnefo distribution with a file
232
   containing custom modifications, which shall override all settings deviating
233
   from the supplied settings.py.dist. This is recommended to minimize the load
234
   of reconstructing settings.py from scratch, since each release currently
235
   brings heavy changes to settings.py.dist.
236

    
237
   Add the following to your custom settings.py, depending on your choice
238
   of DB:
239
   * SQLite
240

    
241
	 PROJECT_PATH = os.path.dirname(os.path.abspath(__file__)) + '/'
242

    
243
	 DATABASES = {
244
	     'default': {
245
		     'ENGINE': 'django.db.backends.sqlite3',
246
		     'NAME': PROJECT_PATH + 'synnefo.db' # WARN: This must be an absolute path
247
	     }
248
	 }
249

    
250
   * MySQL
251

    
252
 	 DATABASES = {
253
	     'default': {
254
             'ENGINE': 'django.db.backends.mysql',
255
             'NAME': 'synnefo',
256
             'USER': 'USERNAME',
257
             'PASSWORD': 'PASSWORD',
258
             'HOST': 'HOST',
259
             'PORT': 'PORT',
260
             'OPTIONS': {
261
                 'init_command': 'SET storage_engine=INNODB',
262
             }
263
	    }
264
	}
265

    
266
   * PostgreSQL
267

    
268
     DATABASES = {
269
	     'default': {
270
             'ENGINE': 'django.db.backends.postgresql_psycopg2',
271
             'NAME': 'DATABASE',
272
             'USER': 'USERNAME',
273
             'PASSWORD': 'PASSWORD',
274
             'HOST': 'HOST',
275
             'PORT': 'PORT',
276
	     }
277
     }
278

    
279
    Try it out. The following command will attempt to connect to the DB and
280
    print out DDL statements. It should not fail.
281

    
282
	$ ./bin/python manage.py sql db
283

    
284

    
285
7. Initialization of Synnefo DB:
286
   You need to initialize the Synnefo DB and load fixtures
287
   db/fixtures/{flavors,images}.json, which make the API usable by end users by
288
   defining a sample set of hardware configurations (flavors) and OS images.
289

    
290
     $ ./bin/python manage.py syncdb
291
     $ ./bin/python manage.py migrate db
292
     $ ./bin/python manage.py loaddata db/fixtures/flavors.json
293
     $ ./bin/python manage.py loaddata db/fixtures/images.json
294

    
295

    
296
8. Finalization of settings.py:
297
   Set the BACKEND_PREFIX_ID variable to some unique prefix, e.g. your commit
298
   username in settings.py. Several functional conventions within the system
299
   require this variable to include a dash at its end (e.g. snf-)
300

    
301
   Fix the AMQP-specific settings based on the selected BACKEND_PREFIX_ID.
302
   The fix_amqp_settings() function is called once at the end of
303
   settings.py.dist, you must call it again if you change BACKEND_PREFIX_ID at
304
   some later point.
305

    
306

    
307
9. Installation of the Ganeti monitoring daemon, /ganeti/snf-ganeti-eventd:
308
   The Ganeti monitoring daemon must run on GANETI-MASTER.
309
   The Ganeti monitoring daemon has no dependency on Django.
310

    
311
   Override all relevant settings in settings.d/99-snf-ganeti-eventd.conf,
312
   GANETI_* variables.
313
   Then, make sure PYTHONPATH contains the parent of the Django project,
314
   and start the server on the Ganeti master as root.
315

    
316
     root:~# export PYTHONPATH=$PYTHONPATH:/opt
317
     root:~# /opt/synnefo/ganeti/snf-ganeti-eventd.py
318

    
319
   TBD: how to handle master migration.
320

    
321

    
322
10. Installation of the Synnefo dispatcher, /logic/dispatcher.py:
323
    The logic dispatcher is part of the Synnefo Django project and must run
324
    on LOGIC nodes.
325

    
326
    The dispatcher retrieves messages from the queue and calls the appropriate
327
    handler function as defined in the queue configuration in `setttings.py'.
328
    The default configuration should work directly without any modifications.
329

    
330
    For the time being The dispatcher must be run by hand:
331
      $ ./bin/python ./logic/dispatcher.py
332

    
333
    The dispatcher should run in at least 2 instances to ensure high
334
    (actually, increased) availability.
335

    
336

    
337
11. Installation of the Synnefo Ganeti hook:
338
    The bash wrapper ganeti/snf-ganeti-hook is the generic launcher for
339
    Synnefo hooks in Ganeti. It resides in the ganeti/ directory under the
340
    root of the Synnefo Django project.
341

    
342
    The hook needs to be enabled for phases post-{add,modify,reboot,start,stop}
343
    by *symlinking* in
344
    /etc/ganeti/hooks/instance-{add,modify,reboot,start,stop}-post.d on
345
    GANETI-MASTER, e.g.:
346

    
347
    root@ganeti-master:/etc/ganeti/hooks/instance-start-post.d# ls -l
348
    lrwxrwxrwx 1 root root 45 May   3 13:45 00-snf-ganeti-hook -> /home/devel/synnefo/ganeti/snf-ganeti-hook
349

    
350
    IMPORTANT: The link name may only contain "upper and lower case, digits,
351
    underscores and hyphens. In other words, the regexp ^[a-zA-Z0-9_-]+$."
352
    See:
353
     http://docs.ganeti.org/ganeti/master/html/hooks.html?highlight=hooks#naming
354

    
355
    You need to set SYNNEFO_PROJECT_DIR in ganeti/snf-ganeti-hook. The bash
356
    script modifies PYTHONPATH accordingly, before passing control to the
357
    relevant Python code.
358

    
359

    
360
12. Installation of the VNC authentication proxy, vncauthproxy:
361
    To support OOB console access to the VMs over VNC, the vncauthproxy
362
    daemon must be running on every node of type APISERVER.
363

    
364
    Download and install vncauthproxy from its own repository,
365
    at https://code.grnet.gr/git/vncauthproxy (known good commit: tag v1.0).
366

    
367
    Download and install a specific repository commit:
368

    
369
    $ bin/pip install -e git+https://code.grnet.gr/git/vncauthproxy@INSERT_COMMIT_HERE#egg=vncauthproxy
370

    
371
    Create /var/log/vncauthproxy and set its permissions appropriately.
372

    
373
    Alternatively, you can build Debian packages. To do so,
374
    checkout the "debian" branch of the vncauthproxy repository
375
    (known good commit: tag debian/v1.0):
376

    
377
    $ git checkout debian
378

    
379
    Then build debian package, and install as root:
380

    
381
    $ dpkg-buildpackage -b -uc -us
382
    # dpkg -i ../vncauthproxy_1.0-1_all.deb
383

    
384

    
385
13. Installation of the customized Ganeti Instance Image for image deployment:
386
    For Synnefo to be able to launch VMs from specified Images, you need
387
    the gnt-instance-image OS Provider installed on the Ganeti backend.
388

    
389
    Download and install gnt-instance-image in all Ganeti nodes from its own
390
    repository, at https://code.grnet.gr/git/gnt-instance-image. It's
391
    recommended to use the win-support branch (known good commit:
392
    aa661a7ea6da9c11a05a3587ee61d10348eb7422).
393

    
394
    After installing gnt-instance-image do the following:
395
    1. root@ganeti-master$ cd /path-to-repo
396
       root@ganeti-master$ cp ./defaults /etc/default/ganeti-instance-image
397
    2. Uncomment the following in /etc/default/ganeti-instance-image:
398
         SWAP=no
399
         ARCH="x86_64"
400
    3. In /etc/ganeti/instance-image/hooks, make sure the hooks you want to
401
       run during instance creation process have execute permission.
402
       For linux you will need at lease `grub' and `root_passwd' to make the
403
       instance usable:
404
         chmod +x /etc/ganeti/instance-image/hooks/linux/{grub,root_passwd}
405
       For security reasons make sure `ssh' hook is also enabled.
406
       For windows you will need `mbr' and `admin_passwd':
407
         chmod +x /etc/ganeti/instance-image/hooks/windows/{mbr,admin_passwd}
408
       For both architectures it is also highly recommended to enable
409
       `hostname' hook too:
410
         chmod +x /et/ganeti/instance-image/hooks/{linux,windows}/hostname
411

    
412
    Your Custom Images should be stored in a dump format under
413
    /var/cache/ganeti-instance-image and their filenames should have the
414
    following format:
415
      {backend_id}-x86_64-root.dump
416
    e.g., debian-6.0.1a-x86_64-root.dump (backend_id = "debian-6.0.1a")
417

    
418
14. Setup Synnefo-specific networking on the Ganeti backend:
419
    This part is deployment-specific and must be customized based on the
420
    specific needs of the system administrators.
421

    
422
    A reference installation will use a Synnefo-specific KVM ifup script,
423
    NFDHCPD and pre-provisioned Linux bridges to support public and private
424
    network functionality. For this:
425

    
426
    Grab NFDHCPD from its own repository (https://code.grnet.gr/git/nfdhcpd),
427
    install it, modify /etc/nfdhcpd/nfdhcpd.conf to reflect your network
428
    configuration.
429

    
430
    Install a custom KVM ifup script for use by Ganeti, as
431
    /etc/ganeti/kvm-vif-bridge, on GANETI-NODEs. A sample implementation is
432
    provided under /contrib/ganeti-hooks. Set NFDHCPD_STATE_DIR to point
433
    to NFDHCPD's state directory, usually /var/lib/nfdhcpd.
434

    
435

    
436
15. Create log file directories for Synnefo components, set appropriate
437
    permissions. By default logic/dispatcher.py and ganeti/snf-ganeti-eventd.py
438
    use /var/log/synnefo.
439

    
440

    
441
16. (Hopefully) Done
442