8 Debian Wheezy (x64) - Django 1.4.x
9 ==================================
10 This guide assumes that installation is carried out in /srv/flowspy directory. If other directory is to be used, please change the corresponding configuration files. It is also assumed that the root user will perform every action.
12 Upgrading from v<1.0.x
13 ----------------------
14 If upgrading from flowspy version <1.0.x pay attention to settings.py changes. Also, do not forget to run::
18 to catch-up with latest database changes.
20 Required system packages
21 ------------------------
22 Update and install the required packages::
26 apt-get install mysql-server apache2 memcached libapache2-mod-proxy-html gunicorn beanstalkd python-django python-django-south python-django-tinymce tinymce python-mysqldb python-yaml python-memcache python-django-registration python-ipaddr python-lxml mysql-client git python-django-celery python-paramiko python-gevent vim
29 Set username and password for mysql if used
32 If you wish to deploy an outgoing mail server, now it is time to do it. Otherwise you could set FoD to send out mails via a third party account
36 If you are using mysql, you should create a database::
38 mysql -u root -p -e 'create database fod'
40 Required application packages
41 -----------------------------
42 Get the required packages and their dependencies and install them::
44 apt-get install libxml2-dev libxslt-dev gcc python-dev
46 - ncclient: NETCONF python client::
49 git clone https://github.com/leopoul/ncclient.git
51 python setup.py install
53 - nxpy: Python Objects from/to XML proxy::
56 git clone https://code.grnet.gr/git/nxpy
58 python setup.py install
60 - flowspy: core application. Installation is done at /srv/flowspy::
63 git clone https://code.grnet.gr/git/flowspy
66 Application configuration
67 =========================
68 Copy settings.py.dist to settings.py::
71 cp settings.py.dist settings.py
73 Edit settings.py file and set the following according to your configuration::
75 ADMINS: set your admin name and email (assuming that your server can send notifications)
76 DATABASES (to point to your local database). You could use views instead of tables for models: peer, peercontacts, peernetworks. For this to work we suggest MySQL with MyISAM db engine
77 SECRET_KEY : Make this unique, and don't share it with anybody
78 STATIC_ROOT: /srv/flowspy/static (or your installation directory)
79 STATIC_URL (static media directory) . If you have followed the above this should be: /srv/flowspy/static
80 TEMPLATE_DIRS : If you have followed the above this should be: /srv/flowspy/templates
81 CACHE_BACKEND: Enable Memcached for production or leave to DummyCache for development environments
82 Alternatively you could go for redis with the corresponding Django client lib.
83 NETCONF_DEVICE (tested with Juniper EX4200 but any BGP enabled Juniper should work). This is the flowspec capable device
84 NETCONF_USER (enable ssh and netconf on device)
86 If beanstalk is selected the following should be left intact.
87 BROKER_HOST (beanstalk host)
88 BROKER_PORT (beanstalk port)
91 If beanstalk is selected the following should be left intact.
92 BROKER_URL (beanstalk url)
93 SHIB_AUTH_ENTITLEMENT (if you go for Shibboleth authentication)
94 NOTIFY_ADMIN_MAILS (bcc mail addresses)
95 PROTECTED_SUBNETS (subnets for which source or destination address will prevent rule creation and notify the NOTIFY_ADMIN_MAILS)
96 The whois client is meant to be used in case you have inserted peers with their ASes in the peers table and wish to get network info for each one in an automated manner.
99 If you wish to deploy FoD with Shibboleth change the following attributes according to your setup:
100 SHIB_AUTH_ENTITLEMENT = 'urn:mace'
101 SHIB_ADMIN_DOMAIN = 'example.com'
102 SHIB_LOGOUT_URL = 'https://example.com/Shibboleth.sso/Logout'
103 SHIB_USERNAME = ['HTTP_EPPN']
104 SHIB_MAIL = ['mail', 'HTTP_MAIL', 'HTTP_SHIB_INETORGPERSON_MAIL']
105 SHIB_FIRSTNAME = ['HTTP_SHIB_INETORGPERSON_GIVENNAME']
106 SHIB_LASTNAME = ['HTTP_SHIB_PERSON_SURNAME']
107 SHIB_ENTITLEMENT = ['HTTP_SHIB_EP_ENTITLEMENT']
109 If you have not installed an outgoing mail server you can always use your own account (either corporate or gmail, hotmail ,etc) by adding the following lines in settings.py::
111 EMAIL_USE_TLS = True #(or False)
112 EMAIL_HOST = 'smtp.example.com'
113 EMAIL_HOST_USER = 'username'
114 EMAIL_HOST_PASSWORD = 'yourpassword'
115 EMAIL_PORT = 587 #(outgoing)
117 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::
119 PEER_MANAGED_TABLE = True
120 PEER_RANGE_MANAGED_TABLE = True
121 PEER_TECHC_MANAGED_TABLE = True
123 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.
126 Soon we will release a version with django-registration as a means to add users and Shibboleth will become an alternative
128 Let's move on with some copies and dir creations::
131 chown www-data.www-data /var/log/fod
132 cp urls.py.dist urls.py
137 Apache operates as a gunicorn Proxy with WSGI and Shibboleth modules enabled.
138 Depending on the setup the apache configuration may vary::
145 If shibboleth is to be used::
147 apt-get install libapache2-mod-shib2
150 Now it is time to configure beanstalk, gunicorn, celery and apache.
154 Enable beanstalk by editting /etc/default/beanstalkd::
156 vim /etc/default/beanstalkd
158 Uncomment the line **START=yes** to enable beanstalk
162 service beanstalkd start
166 Create and edit /etc/gunicorn.d/fod::
168 vim /etc/gunicorn.d/fod
170 FoD is served via gunicorn and is then proxied by Apache. If the above directory conventions have been followed so far, then your configuration should be::
174 'working_dir': '/srv/flowspy',
176 '--bind=127.0.0.1:8081',
178 '--worker-class=egg:gunicorn#gevent',
181 '--log-file=/var/log/gunicorn/fod.log',
188 Celery is used over beanstalkd to apply firewall rules in a serial manner so that locks are avoided on the flowspec capable device. In our setup celery runs via django. That is why the python-django-celery package was installed.
190 Create the celeryd daemon at /etc/init.d/celeryd **if it does not already exist**::
192 vim /etc/init.d/celeryd
194 The configuration should be::
197 # ============================================
198 # celeryd - Starts the Celery worker daemon.
199 # ============================================
201 # :Usage: /etc/init.d/celeryd {start|stop|force-reload|restart|try-restart|status}
202 # :Configuration file: /etc/default/celeryd
204 # See http://docs.celeryq.org/en/latest/cookbook/daemonizing.html#init-script-celeryd
209 # Required-Start: $network $local_fs $remote_fs
210 # Required-Stop: $network $local_fs $remote_fs
211 # Default-Start: 2 3 4 5
212 # Default-Stop: 0 1 6
213 # Short-Description: celery task worker daemon
214 # Description: Starts the Celery worker daemon for a single project.
219 DEFAULT_PID_FILE="/var/run/celery/%n.pid"
220 DEFAULT_LOG_FILE="/var/log/celery/%n.log"
221 DEFAULT_LOG_LEVEL="INFO"
222 DEFAULT_NODES="celery"
223 DEFAULT_CELERYD="-m celery.bin.celeryd_detach"
226 [ -r "$CELERY_DEFAULTS" ] && . "$CELERY_DEFAULTS"
228 [ -r /etc/default/celeryd ] && . /etc/default/celeryd
230 if [ "$ENABLED" != "true" ]; then
231 echo "celery daemon disabled - see /etc/default/celeryd."
236 CELERYD_PID_FILE=${CELERYD_PID_FILE:-${CELERYD_PIDFILE:-$DEFAULT_PID_FILE}}
237 CELERYD_LOG_FILE=${CELERYD_LOG_FILE:-${CELERYD_LOGFILE:-$DEFAULT_LOG_FILE}}
238 CELERYD_LOG_LEVEL=${CELERYD_LOG_LEVEL:-${CELERYD_LOGLEVEL:-$DEFAULT_LOG_LEVEL}}
239 CELERYD_MULTI=${CELERYD_MULTI:-"celeryd-multi"}
240 CELERYD=${CELERYD:-$DEFAULT_CELERYD}
241 CELERYCTL=${CELERYCTL:="celeryctl"}
242 CELERYD_NODES=${CELERYD_NODES:-$DEFAULT_NODES}
247 CELERYD_OPTS="$CELERYD_OPTS $2"
250 CELERYD_LOG_DIR=`dirname $CELERYD_LOG_FILE`
251 CELERYD_PID_DIR=`dirname $CELERYD_PID_FILE`
252 if [ ! -d "$CELERYD_LOG_DIR" ]; then
253 mkdir -p $CELERYD_LOG_DIR
255 if [ ! -d "$CELERYD_PID_DIR" ]; then
256 mkdir -p $CELERYD_PID_DIR
259 # Extra start-stop-daemon options, like user/group.
260 if [ -n "$CELERYD_USER" ]; then
261 DAEMON_OPTS="$DAEMON_OPTS --uid=$CELERYD_USER"
262 chown "$CELERYD_USER" $CELERYD_LOG_DIR $CELERYD_PID_DIR
264 if [ -n "$CELERYD_GROUP" ]; then
265 DAEMON_OPTS="$DAEMON_OPTS --gid=$CELERYD_GROUP"
266 chgrp "$CELERYD_GROUP" $CELERYD_LOG_DIR $CELERYD_PID_DIR
269 if [ -n "$CELERYD_CHDIR" ]; then
270 DAEMON_OPTS="$DAEMON_OPTS --workdir=\"$CELERYD_CHDIR\""
275 if [ ! -c /dev/null ]; then
276 echo "/dev/null is not a character device!"
282 export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"
286 $CELERYD_MULTI stop $CELERYD_NODES --pidfile="$CELERYD_PID_FILE"
291 $CELERYD_MULTI start $CELERYD_NODES $DAEMON_OPTS \
292 --pidfile="$CELERYD_PID_FILE" \
293 --logfile="$CELERYD_LOG_FILE" \
294 --loglevel="$CELERYD_LOG_LEVEL" \
301 $CELERYD_MULTI restart $CELERYD_NODES $DAEMON_OPTS \
302 --pidfile="$CELERYD_PID_FILE" \
303 --logfile="$CELERYD_LOG_FILE" \
304 --loglevel="$CELERYD_LOG_LEVEL" \
327 $CELERYCTL status $CELERYCTL_OPTS
341 echo "Usage: /etc/init.d/celeryd {start|stop|restart|try-restart|kill}"
348 celeryd configuration
349 ---------------------
350 celeryd requires a /etc/default/celeryd file to be in place.
351 Thus we are going to create this file (/etc/default/celeryd)::
353 vim /etc/default/celeryd
355 Again if the directory conventions have been followed the file is (pay attention to the CELERYD_USER, CELERYD_GROUP and change accordingly) ::
360 # Name of nodes to start, here we have a single node
362 # or we could have three nodes:
363 #CELERYD_NODES="w1 w2 w3"
365 # Where to chdir at start.
366 CELERYD_CHDIR="/srv/flowspy"
367 # How to call "manage.py celeryd_multi"
368 CELERYD_MULTI="python $CELERYD_CHDIR/manage.py celeryd_multi"
370 # How to call "manage.py celeryctl"
371 CELERYCTL="python $CELERYD_CHDIR/manage.py celeryctl"
373 # Extra arguments to celeryd
374 #CELERYD_OPTS="--time-limit=300 --concurrency=8"
375 CELERYD_OPTS="-E -B --schedule=/var/run/celery/celerybeat-schedule"
376 # Name of the celery config module.
377 CELERY_CONFIG_MODULE="celeryconfig"
379 # %n will be replaced with the nodename.
380 CELERYD_LOG_FILE="/var/log/celery/fod_%n.log"
381 CELERYD_PID_FILE="/var/run/celery/%n.pid"
383 # Workers should run as an unprivileged user.
384 CELERYD_USER="celery"
385 CELERYD_GROUP="celery"
387 # Name of the projects settings module.
388 export DJANGO_SETTINGS_MODULE="flowspy.settings"
392 Apache proxies gunicorn. Things are more flexible here as you may follow your own configuration and conventions. Create and edit /etc/apache2/sites-available/fod. You should set <server_name> and <admin_mail> along with your certificates. If under testing environment, you can use the provided snakeoil certs. If you do not intent to use Shibboleth delete or comment the corresponding configuration parts inside **Shibboleth configuration** ::
394 vim /etc/apache2/sites-available/fod
396 Again if the directory conventions have been followed the file should be::
399 ServerAdmin webmaster@localhost
400 ServerName fod.example.com
401 DocumentRoot /var/www
403 ErrorLog ${APACHE_LOG_DIR}/fod_error.log
405 # Possible values include: debug, info, notice, warn, error, crit,
409 CustomLog ${APACHE_LOG_DIR}/fod_access.log combined
411 Alias /static /srv/flowspy/static
413 RewriteCond %{HTTPS} off
414 RewriteRule ^/(.*) https://fod.example.com/$1 [L,R]
418 ServerName fod.example.com
419 ServerAdmin webmaster@localhost
423 SSLCertificateFile /etc/ssl/certs/fod.example.com.crt
424 SSLCertificateChainFile /etc/ssl/certs/example-chain.pem
425 SSLCertificateKeyFile /etc/ssl/private/fod.example.com.key
427 AddDefaultCharset UTF-8
428 IndexOptions +Charset=UTF-8
430 ShibConfig /etc/shibboleth/shibboleth2.xml
431 Alias /shibboleth-sp /usr/share/shibboleth
436 ShibRequireSession On
438 ShibRequestSetting entityID https://idp.example.com/idp/shibboleth
442 # Shibboleth debugging CGI script
443 ScriptAlias /shibboleth/test /usr/lib/cgi-bin/shibtest.cgi
444 <Location /shibboleth/test>
446 ShibRequireSession On
451 <Location /Shibboleth.sso>
455 # Shibboleth SP configuration
457 #SetEnv proxy-sendchunked
465 ProxyErrorOverride off
468 ProxyPass /shibboleth !
469 ProxyPass /Shibboleth.sso !
471 ProxyPass / http://localhost:8081/ retry=0
472 ProxyPassReverse / http://localhost:8081/
474 Alias /static /srv/flowspy/static
478 ErrorLog ${APACHE_LOG_DIR}/fod_error.log
479 CustomLog ${APACHE_LOG_DIR}/fod_access.log combined
483 Now, enable your site. You might want to disable the default site if fod is the only site you host on your server::
488 You are not far away from deploying FoD. When asked for a super user, create one::
491 python manage.py syncdb
492 python manage.py migrate flowspec
493 python manage.py migrate djcelery
494 python manage.py migrate accounts
496 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::
498 python manage.py migrate peers
500 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::
502 DROP TABLE `peer`, `peer_networks`, `peer_range`, `peer_techc_emails`, techc_email;
504 Restart, gunicorn and apache::
506 service gunicorn restart && service apache2 restart
509 Propagate the flatpages
510 =======================
511 Inside the initial_data/fixtures_manual.xml file we have placed 4 flatpages (2 for Greek, 2 for English) with Information and Terms of Service about the service.
512 To import the flatpages, run from root folder::
514 python manage.py loaddata initial_data/fixtures_manual.xml
520 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
521 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.
522 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.
526 Via the admin interface you can modify flatpages to suit your needs
530 Under the templates folder (templates), you can alter the footer.html file to include your own footer messages, badges, etc.
534 Under the templates folder (templates), you can alter the welcome page - welcome.html with your own images, carousel, videos, etc.