Core development is all about development on any component of the OneOps application stack itself.
All source code for the various components is available on GitHub.
The OneOps build relies on Unix scripts and should work on OSX and Linux operating systems versions.
The following tools are required to build and run OneOps on a local developer machine.
- Java Development Kit 8 from Oracle
- Apache Maven 3.5.0 (unless included Maven wrapper is used)
- PostgreSQL 9.2 development file (libpg)
- Virtual Box
Nice to have:
- Favorite IDE like EclipseIDE or STS
- Some Git UI
- And so on …
Fork and clone the oneops source repository
and run a build with the Maven wrapper in the created
cd oneops ./mvnw clean install
or directly with Maven, if you have it installed already.
cd oneops mvn clean install
The build compiles, tests and builds all packages.
If you want to run OneOps after a build, you can use the
during a build. It creates all necessary configuration for Vagrant to spin up
the newly built OneOps in a VirtualBox virtual machine.
mvn install -P vagrant
After a successful build with the profile you can find the necessary files for
starting a VM with OneOps running in the
~/.oneops/vagrant directory and start
the VM from there.
cd ~/.oneops/vagrant/ vagrant up
Once the VM is up and running, you can access the OneOps user interface at http://localhost:9090.
Subsequently you can
halt the VM with vagrant or use the
VirtualBox user interface as desired. Refer to the Vagrant and VirtualBox
documentation for further information.
OneOps uses a PostgreSQL database for model storage. Some information about the model is available in the relations documentation.