Commit f8938aca authored by Leonidas Poulopoulos's avatar Leonidas Poulopoulos

Release version 1.0.3

parent 552466bf
===========
1.0.3 RELEASE
Minor fixes. Check documentation for peers table handling
- Fix issue with altlogin redirection
- Switch peers primary key to AutoField
- Make peers tables management configurable
===========
1.0.2 RELEASE
Documentation enhancements
......
VERSION = '1.0.2'
VERSION = '1.0.3'
if __name__ == "__main__":
print VERSION
......@@ -45,9 +45,9 @@ copyright = u'2014, Leonidas Poulopoulos (@leopoul), GRNET S.A'
# built documents.
#
# The short X.Y version.
version = '1.0.2'
version = '1.0.3'
# The full version, including alpha/beta/rc tags.
release = '1.0.2'
release = '1.0.3'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
......
......@@ -37,10 +37,11 @@ If you are using mysql, you should create a database::
mysql -u root -p -e 'create database fod'
Required application packages
-----------------------------
Get the required packages and install them
Get the required packages and their dependencies and install them::
apt-get install libxml2-dev libxslt-dev gcc python-dev
- ncclient: NETCONF python client::
......@@ -113,17 +114,23 @@ If you have not installed an outgoing mail server you can always use your own ac
EMAIL_HOST_PASSWORD = 'yourpassword'
EMAIL_PORT = 587 #(outgoing)
It is strongly advised that you do not change the following to False values unless, you want to integrate FoD with you CRM or members database. This implies that you are able/have the rights to create database views between the two databases::
PEER_MANAGED_TABLE = True
PEER_RANGE_MANAGED_TABLE = True
PEER_TECHC_MANAGED_TABLE = True
By doing that the corresponding tables as defined in peers/models will not be created. As noted above, you have to create the views that the tables will rely on.
.. note::
Soon we will release a version with django-registration as a means to add users and Shibboleth will become an alternative
Let's move on with some copies and dir creations::
mkdir /var/log/fod
chown www-data.www-data /var/log/fod
cp urls.py.dist urls.py
cd ..
mkdir log
chown -R root:www-data log/
chmod -R g+w log
System configuration
====================
......@@ -171,7 +178,7 @@ FoD is served via gunicorn and is then proxied by Apache. If the above directory
'--worker-class=egg:gunicorn#gevent',
'--timeout=30',
'--log-level=debug',
'--log-file=/var/log/flowspy.log',
'--log-file=/var/log/gunicorn/fod.log',
),
}
......@@ -370,7 +377,7 @@ Again if the directory conventions have been followed the file is (pay attention
CELERY_CONFIG_MODULE="celeryconfig"
# %n will be replaced with the nodename.
CELERYD_LOG_FILE="/var/log/celery/%n.log"
CELERYD_LOG_FILE="/var/log/celery/fod_%n.log"
CELERYD_PID_FILE="/var/run/celery/%n.pid"
# Workers should run as an unprivileged user.
......@@ -482,7 +489,17 @@ You are not far away from deploying FoD. When asked for a super user, create one
cd /srv/flowspy
python manage.py syncdb
python manage.py migrate
python manage.py migrate flowspec
python manage.py migrate djcelery
python manage.py migrate accounts
If you have not changed the values of the PEER\_\*\_TABLE variables to False and thus you are going for a default installation (that is PEER\_\*\_TABLE variables are set to True) , then run::
python manage.py migrate peers
If however you have set the PEER\_\*\_TABLE variables to False and by accident you have ran the command above, then you have to cleanup you database manually by dropping the peer\* tables plus the techc_email table. For MySQL the command is::
DROP TABLE `peer`, `peer_networks`, `peer_range`, `peer_techc_emails`, techc_email;
Restart, gunicorn and apache::
......@@ -500,9 +517,9 @@ To import the flatpages, run from root folder::
Testing the platform
====================
Log in to the admin interface via https://<hostname>/admin. Go to Peer ranges and add a new range (part of/or a complete subnet), eg. 10.20.0.0/19
Go to Peers and add a new peer, eg. id: 1, name: Test, AS: 16503, tag: TEST and move the network you have crteated from Avalable to Chosen. From the admin front, go to User, and edit your user. From the bottom of the page, select the TEST peer and save.
Last but not least, modify as required the existing (example.com) Site instance (admin home->Sites). You are done. As you are logged-in via the admin, there is no need for Shibboleth. Go to https://<hostname>/ and create a new rule. Your rule should be applied on the flowspec capable device after aprox. 10 seconds.
Log in to the admin interface via https:\/\/<hostname>\/admin. Go to Peer ranges and add a new range (part of/or a complete subnet), eg. 10.20.0.0/19
Go to Peers and add a new peer, eg. id: 1, name: Test, AS: 16503, tag: TEST and move the network you have created from Avalable to Chosen. From the admin front, go to User, and edit your user. From the bottom of the page, select the TEST peer and save.
Last but not least, modify as required the existing (example.com) Site instance (admin home->Sites). You are done. As you are logged-in via the admin, there is no need to go through Shibboleth at this time. Go to https:\/\/<hostname>\/ and create a new rule. Your rule should be applied on the flowspec capable device after aprox. 10 seconds. If no Shibboleth authentication is available, a https:\/\/<hostname>\/altlogin is provided.
Branding
========
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment