You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Sebastian Rieger 1445c54fa7 added some install documentation, added debug output for cron job 8 years ago
api added some install documentation, added debug output for cron job 8 years ago
app GER->ENG; better error messages, README update 8 years ago
css Paket-Verwaltung; Alert-Z-Index behoben 8 years ago
fonts Initial commit 8 years ago
js Initial commit 8 years ago
partials GER->ENG; better error messages, README update 8 years ago
.gitignore GER->ENG; better error messages, README update 8 years ago
README.md added some install documentation, added debug output for cron job 8 years ago
bower.json Paket-Verwaltung; Alert-Z-Index behoben 8 years ago
composer.json Initial commit 8 years ago
composer.lock GER->ENG; better error messages, README update 8 years ago
index.html Paket-Verwaltung; Alert-Z-Index behoben 8 years ago
package.json Paket-Verwaltung; Alert-Z-Index behoben 8 years ago

README.md

virl-scheduler

Setup instructions

  • make sure bower, composer and npm are available on command line

    • e.g. for Ubuntu 16.04 (VIRL 1.3.156 host):
      • "sudo apt-get install npm"
      • "sudo apt-get install nodejs-legacy"
      • "sudo npm install -g bower"
      • "sudo apt install libapache2-mod-php7.0 php7.0-sqlite3 php-xml php-curl"
      • "curl -sS https://getcomposer.org/installer | sudo php -- --install-dir=/usr/local/bin --filename=composer"
  • run npm update in virl-scheduler root directory (only if you want to test in devmodes, apache is enough otherwise)

  • run bower update in virl-scheduler root directory, afterwards verify bower_components directory was created

  • run composer update in virl-scheduler root directory, afterwards verify vendor directory was created

  • configure apache to use virl-scheduler and index.html as webroot (make sure rewrite engine is on and .htaccess files are parsed by apache)

    • e.g. for Ubuntu 16.04 (VIRL 1.3.156 host):
      • copy virl-scheduler to your webroot: "sudo cp -a virl-scheduler /var/www/html/"
      • add "ProxyPass /virl-scheduler !" to the ProxyPass directives in /etc/apache2/sites-available/000-default.conf
      • allow .htaccess in virl-scheduler api directory, e.g., by appending the following lines to /etc/apache2/sites-available/000-default.conf
        <Directory /var/www/html/virl-scheduler/api>
                AllowOverride All
        </Directory>
        
  • give the Apache2 process write permissions to the sqlite3 db by running "sudo chown www-data:www-data api/db.sqlite3" and "sudo chown www-data:www-data api" in the virl-scheduler directory

  • run service apache2 restart

  • Change hostname for VIRLRestangular factory in app/topologyManager.js and api/cron.php to your VIRL-API-Hostname or IP-Address.

  • Add a cron job to run the scheduler, e.g., every five minutes and start planned simulations

  • Have fun using the scheduler to start VIRL simulations automatically, by accessing /virl-scheduler on your VIRL host. Login using a VIRL username and password, be sure to add a Session name (simulation name) and a VIRL topology (XML source of a topology file)

  • output of the cron job can be seen in /var/log/virl-scheduler-cron.log or by accessing http:///virl-scheduler/api/cron.php" manually in your browser