Revision 2ca07643
b/docs/index.rst | ||
---|---|---|
65 | 65 |
Synnefo Guides |
66 | 66 |
============== |
67 | 67 |
|
68 |
There are 3 guides for Synnefo.
|
|
69 |
|
|
70 |
.. For the really impatient snf-deploy tool allows you to install all software
|
|
71 |
.. components from scratch (creating locally kvm based Virtual Machines) or to an
|
|
72 |
.. existing cluster (in the same network subnet and domain, same network
|
|
73 |
.. configuration, vanilla debian squeeze and installed ssh keys). Please note that
|
|
74 |
.. this should be used only for testing or demo installations because most of the
|
|
75 |
.. times the prerequisites cannot be satisfied due to the underlying
|
|
76 |
.. infrastructure complexity (especially as far as networks is concerned). |
|
77 |
|
|
78 |
The admin's installation guide describes how to install the whole Synnefo stack
|
|
79 |
in just two physical nodes, for testing purposes. This guide is useful to those
|
|
80 |
interested in deploying Synnefo in large scale, as a starting point that will
|
|
81 |
help them get familiar with the Synnefo components and overall architecture, as
|
|
82 |
well as the interconnection between different services. Such an installation,
|
|
83 |
also provides a quick preview of the basic Synnefo features, although we like to
|
|
84 |
think that Synnefo's real power unveils while scaling.
|
|
68 |
There are 4 guides for Synnefo.
|
|
69 |
|
|
70 |
The Quick Installation guide describes how to install Synnefo on a single node
|
|
71 |
in less than 10 minutes using the `snf-deploy` tool. This kind of installation
|
|
72 |
is targeted for testing and demo environments rather than production usage
|
|
73 |
deployments. It is the perfect way, even for an inexperienced user to have the
|
|
74 |
whole Synnefo stack up and running and allows for a quick preview of the basic
|
|
75 |
Synnefo features.
|
|
76 |
|
|
77 |
The Admin's installation guide describes how to install the whole Synnefo stack |
|
78 |
in just two physical nodes. This guide is useful to those interested in
|
|
79 |
deploying Synnefo in large scale, as a starting point that will help them get
|
|
80 |
familiar with the Synnefo components and overall architecture, as well as the
|
|
81 |
interconnection between different services. This guide explains the whole
|
|
82 |
procedure step by step, without the use of the `snf-deploy` tool. Anyone
|
|
83 |
familiar with this guide, will be able to easily install Synnefo in a larger
|
|
84 |
number of nodes too, or even expand the two node installation dynamically.
|
|
85 | 85 |
|
86 | 86 |
The Administrator's Guide targets system administrators, who want to dive into |
87 | 87 |
more details and common tasks regarding Synnefo. For the experienced Synnefo |
... | ... | |
101 | 101 |
.. toctree:: |
102 | 102 |
:maxdepth: 1 |
103 | 103 |
|
104 |
Quick Installation Guide (single node) <quick-install-guide> |
|
104 | 105 |
Installation Guide (on two nodes) <quick-install-admin-guide> |
105 | 106 |
|
106 | 107 |
.. toctree:: |
b/docs/quick-install-guide.rst | ||
---|---|---|
29 | 29 |
========================== |
30 | 30 |
|
31 | 31 |
First of all we need to install the snf-deploy tool. To do so please add the |
32 |
following line in your ``sources.list`` file: |
|
32 |
following line in your ``/etc/apt/sources.list`` file:
|
|
33 | 33 |
|
34 | 34 |
.. code-block:: console |
35 | 35 |
|
... | ... | |
61 | 61 |
Accessing the Synnefo installation |
62 | 62 |
================================== |
63 | 63 |
|
64 |
If you want to access the installation from the same machine it runs on, just |
|
65 |
open a browser and point to: |
|
66 |
|
|
67 |
`https://accounts.<domain>/im/` |
|
68 |
|
|
69 |
The <domain> is automatically set to ``hostname -d``. If this doesn't return |
|
70 |
anything, it is set to ``synnefo.deploy.local``. A local BIND is already set up |
|
71 |
by `snf-deploy` to serve all FQDNs. |
|
64 |
Remote access |
|
65 |
------------- |
|
72 | 66 |
|
73 | 67 |
If you want to access the Synnefo installation from a remote machine, please |
74 | 68 |
first set your nameservers accordingly by adding the following line as your |
... | ... | |
81 | 75 |
The <IP> is the public IP of the machine that you deployed Synnefo on, and want |
82 | 76 |
to access. |
83 | 77 |
|
78 |
Then open a browser and point to: |
|
79 |
|
|
80 |
`https://accounts.synnefo.live/im/` |
|
81 |
|
|
82 |
Local access |
|
83 |
------------ |
|
84 |
|
|
85 |
If you want to access the installation from the same machine it runs on, just |
|
86 |
open a browser and point to: |
|
87 |
|
|
88 |
`https://accounts.synnefo.live/im/` |
|
89 |
|
|
90 |
The <domain> is automatically set to ``synnefo.live``. A local BIND is already |
|
91 |
set up by `snf-deploy` to serve all FQDNs. |
|
92 |
|
|
93 |
Login |
|
94 |
----- |
|
95 |
|
|
84 | 96 |
Once you see the Login screen, go ahead and login using: |
85 | 97 |
|
86 |
| username: dimara@grnet.gr
|
|
87 |
| password: lala
|
|
98 |
| username: user@synnefo.org
|
|
99 |
| password: 12345
|
|
88 | 100 |
|
89 | 101 |
which is the default user. If you see the welcome screen, you have successfully |
90 | 102 |
installed Synnefo on a single node. |
... | ... | |
96 | 108 |
To be able to view all web pages make sure you have accepted all certificates |
97 | 109 |
for domains: |
98 | 110 |
|
99 |
* synnefo.deploy.local
|
|
100 |
* accounts.synnefo.deploy.local
|
|
101 |
* cyclades.synnefo.deploy.local
|
|
102 |
* pithos.synnefo.deploy.local
|
|
103 |
* cms.synnefo.deploy.local
|
|
111 |
* synnefo.live
|
|
112 |
* accounts.synnefo.live
|
|
113 |
* cyclades.synnefo.live
|
|
114 |
* pithos.synnefo.live
|
|
115 |
* cms.synnefo.live
|
|
104 | 116 |
|
105 | 117 |
|
106 | 118 |
Using the installation |
Also available in: Unified diff