In the context of the project STAMP, ActiveEon is a use case to explore several configuration notably for using different databases. This page explain show how to run camp for proactive worflows & schedulling.
All case-studies are located in a separate Git repository, namely
STAMP-project/camp-samples. You can fetch the case-study as follows:
$ git clone https://github.com/STAMP-project/camp-samples $ cd camp-samples/activeon
To build camp go to project root and use:
docker build . -t camp
To run camp within the created image use.
docker run -it camp bash
Work whithin the docker container has some drawbacks. The changes on the current drive are not seem or either presistent. Alternatively, you can also use a mounting point so camp container access an outside folder.
docker run -t -v $PWD:/campworkingdir camp camp -h
Now you can proceed to use camp. For instance for this example change current
directory to be
samples/stamp/activeeon and then run:
docker run -t -v $PWD:/campworkingdir camp camp generate -d /campworkingdir
CAMP then generates new Dockerfiles, properly chained together according to the configurations generated by camp generate. To do so, you can apply the following command:
docker run -t -v $PWD:/campworkingdir camp camp realize -d /campworkingdir
You can clean exited container and unlinked images using:
docker system prune
Now that the configurations are generated, you need to do some modifications to make it work:
You need to provide your host machine address to configure the
proactive server on docker. e.g., on mac or linux you can use
To get snapshot version of proactive from jenkins, you need to provide the
username and api-token first. Visit the jenkins site
http://<yourserver>/user/<username>/configure and then generate the token.
Now edit the scripts
get-last-proactive-do-not-commit.sh and replace
USERNAME and TOKEN by your credentials.
Finally to start the proactive server with go to the config folder generated
cd out/config_1 and run
to start both containers (proactive + database.)
Now it is time to run system-tests over generated configs.
The scheduling-system-tests project is a private repo on bitbucket. Access to the repo has to be requested (please contact us)
-Clone the project
git clone https://bitbucket.org/activeeon/scheduling-system-tests/src/master/
./gradlew clean -Plocal test
Proactive docker container to target system tests;