blob: 9891efecc85380e86a5262ca4c81558437dd45dd [file] [log] [blame]
Tony Macka717fb62015-11-16 22:34:33 +00001
21. Introduction
3
4 XOS is comprised of 3 core services:
5
6 * A database backend (postgres)
7 * A webserver front end (django)
8 * A synchronizer daemon that interacts with the openstack backend.
9
10 We have created separate dockerfiles for each of these services, making it easier to
11 build the services independently and also deploy and run them in isolated environments.
12
132. Database Container
14
15 To build and run the database container:
16
17 $ cd postgres; make build && make run;
18
193. XOS container
20
21 To build and run the xos webserver container:
22
23 $ cd xos; make build && make run;
24
25 You should now be able to access the login page by visiting http://localhost:80 and
26 log in using the default paadmin account. It may be helpful to bootstrap xos with
27 some sample data; deployment, controllers, sites, slices, etc. You can get started by
28 loading tosca configuration for the opencloud demo dataset:
29
30 $ cd xos; make runtosca;
31
32 Or you can create you own tosca configuraton file and customize the dataset however you
33 want. You can all load your own tosca configuration by setting the TOSCA_CONFIG_PATH
34 environment variable before executing the make command:
35
36 $ cd xos; TOSCA_CONFIG_PATH=/path/to/tosca/config.yaml make runtosca
37
384. Synchronizer container
39
40 The syncornonizer shares many of the same dependencies as the xos container. The synchronizer
41 container takes advantage of this by building itself on top of the xos image. This means
42 you must build the xos image before building the synchronizer image. The XOS and
43 synchronizer containers can run on separate hosts, but you must build the xos image
44 on the host that you plan to run the synchronizer container. Assuming you have already
45 built the xos container, executing the following will build and run the synchronizer container:
46
47 $ cd synchronizer; make build && make run
48
49
50
51