Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
synnefo
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
itminedu
synnefo
Commits
ddb51ce5
Commit
ddb51ce5
authored
10 years ago
by
Stratos Psomadakis
Browse files
Options
Downloads
Patches
Plain Diff
docs: Update 0.16 upgrade guide
parent
d59e4f94
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
docs/install-guide-centos.rst
+16
-0
16 additions, 0 deletions
docs/install-guide-centos.rst
docs/install-guide-debian.rst
+16
-0
16 additions, 0 deletions
docs/install-guide-debian.rst
docs/upgrade/upgrade-0.16.rst
+58
-11
58 additions, 11 deletions
docs/upgrade/upgrade-0.16.rst
with
90 additions
and
11 deletions
docs/install-guide-centos.rst
+
16
−
0
View file @
ddb51ce5
...
...
@@ -2096,6 +2096,22 @@ settings. Check the `documentation
<http://www.synnefo.org/docs/snf-vncauthproxy/latest/index.html>`_ of
snf-vncauthproxy for more information.
You should also provide snf-vncauthproxy with SSL certificates signed by a
trusted CA. You can either copy them to `/var/lib/vncauthproxy/{cert,key}.pem`
or inform vncauthproxy about the location of the certificates (via the
`DAEMON_OPTS` setting in `/etc/default/vncauthproxy`).
::
DAEMON_OPTS="--pid-file=$PIDFILE --cert-file=<path_to_cert> --key-file=<path_to_key>"
Both files should be readable by the `vncauthproxy` user or group.
.. note::
At the moment, the certificates should be issued to the FQDN of the
Cyclades worker.
We have now finished with the basic Cyclades configuration.
Database Initialization
...
...
This diff is collapsed.
Click to expand it.
docs/install-guide-debian.rst
+
16
−
0
View file @
ddb51ce5
...
...
@@ -2136,6 +2136,22 @@ settings. Check the `documentation
<http://www.synnefo.org/docs/snf-vncauthproxy/latest/index.html>`_ of
snf-vncauthproxy for more information.
You should also provide snf-vncauthproxy with SSL certificates signed by a
trusted CA. You can either copy them to `/var/lib/vncauthproxy/{cert,key}.pem`
or inform vncauthproxy about the location of the certificates (via the
`DAEMON_OPTS` setting in `/etc/default/vncauthproxy`).
::
DAEMON_OPTS="--pid-file=$PIDFILE --cert-file=<path_to_cert> --key-file=<path_to_key>"
Both files should be readable by the `vncauthproxy` user or group.
.. note::
At the moment, the certificates should be issued to the FQDN of the
Cyclades worker.
We have now finished with the basic Cyclades configuration.
Database Initialization
...
...
This diff is collapsed.
Click to expand it.
docs/upgrade/upgrade-0.16.rst
+
58
−
11
View file @
ddb51ce5
...
...
@@ -6,16 +6,16 @@ Introduction
Starting with version 0.16, we introduce Archipelago as the new storage backend
for the Pithos Service. Archipelago will act as a storage abstraction layer
between Pithos and NFS, RADOS or any other storage backend driver that
Archipelago
supports. In order to use the Pithos Service you must install
Archipelago on the
node that runs the Pithos
workers. Additionally, you must install snf-image
version 0.16 on the Ganeti nodes since this is the first version that supports
Archipelago.
between Pithos and NFS, RADOS or any other storage backend driver that
Archipelago
supports. In order to use the Pithos Service you must install
Archipelago on the
node that runs the Pithos
and Cyclades workers.
Additionally, you must install snf-image version 0.16 on the Ganeti nodes since
this is the first version that supports
Archipelago.
Until now the Pithos mapfile was a simple file containing a list of hashes that
make up the stored file in a Pithos container. After this consolidation the
Pithos
mapfile had to be converted to an Archipelago mapfile. An Archipelago
mapfile
is an updated version of the Pithos mapfile, intended to supersede it.
make up the stored file in a Pithos container. After this consolidation the
Pithos
mapfile had to be converted to an Archipelago mapfile. An Archipelago
mapfile
is an updated version of the Pithos mapfile, intended to supersede it.
More info about the new mapfile you can find in Archipelago documentation.
...
...
@@ -23,7 +23,9 @@ More info about the new mapfile you can find in Archipelago documentation.
Upgrade Steps
=============
The upgrade to v0.16 consists in the following steps:
The upgrade to v0.16 consists of the following steps:
0. Upgrade / Install Archipelago and snf-image.
1. Bring down services and backup databases.
...
...
@@ -43,6 +45,24 @@ The upgrade to v0.16 consists in the following steps:
It is strongly suggested that you keep separate database backups
for each service after the completion of each step.
0. Upgrade / Install Archipelago and snf-image
==============================================
If you have never used Archipelago before, make sure to install Archipelago 0.4
on all Ganeti VM-capable nodes.
If you're upgrading from Archipelago 0.3.5, make sure to upgrade Archipelago
on all Ganeti nodes before starting the upgrade process. For more
information, check the Archipelago
`upgrade notes <https://www.synnefo.org/docs/archipelago/latest/upgrades/archipelago_upgrade_v04.rst>`_.
Once you have Archipelago 0.4 up and running, you can install snf-image 0.16.
At this point, you should also install Archipelago 0.4 on the Pithos and
Cyclades workers.
1. Bring web services down, backup databases
============================================
...
...
@@ -143,6 +163,33 @@ The upgrade to v0.16 consists in the following steps:
pithos-host$ pithos-migrate upgrade head
2.3 Configure snf-vncauthproxy
------------------------------
Synnefo 0.16 replaces the Java VNC client with an HTML5 Websocket client and
the Cyclades UI will always request secure Websocket connections. You should,
therefore, provide snf-vncauthproxy with SSL certificates signed by a trusted
CA. You can either copy them to `/var/lib/vncauthproxy/{cert,key}.pem` or
inform vncauthproxy about the location of the certificates (via the
`DAEMON_OPTS` setting in `/etc/default/vncauthproxy`).
::
DAEMON_OPTS="--pid-file=$PIDFILE --cert-file=<path_to_cert> --key-file=<path_to_key>"
Both files should be readable by the `vncauthproxy` user or group.
.. note::
At the moment, the certificates should be issued to the FQDN of the
Cyclades worker.
For more information on how to setup snf-vncauthproxy check the
snf-vncauthproxy `documentation <https://www.synnefo.org/docs/snf-vncauthproxy/latest/index.html#usage-with-synnefo>`_
and `upgrade notes <https://www.synnefo.org/docs/snf-vncauthproxy/latest/upgrade/upgrade-1.6.html>`_.
3. Inspect and adjust resource limits
=====================================
...
...
@@ -198,8 +245,8 @@ another project in order to overcome this restriction.
4. Tweak Archipelago and Gunicorn settings on Pithos node
=========================================================
After installing Archipelago on Pithos node we need to adjust the
configuration
files according to our deployment needs.
After installing Archipelago on
the
Pithos node we need to adjust the
configuration
files according to our deployment needs.
For Archipelago the configuration file is located on
``/etc/archipelago/archipelago.conf``, where we need to adjust carefully at
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment