OneFlow orchestrates multi-VM services as a whole, interacts with the OpenNebula Daemon to manage the Virtual Machines (starts, stops), and can be controlled via the Sunstone GUI or over CLI. It’s a dedicated daemon installed by default as part of the Single Front-end Installation, but can be deployed independently on a different machine. The server is distributed as an operating system package
opennebula-flow with the system service
Read more in Multi-VM Service Management.
The OneFlow configuration file can be found in
/etc/one/oneflow-server.conf on your Front-end. It uses YAML syntax with following parameters:
After a configuration change, the OneFlow server must be restarted to take effect.
||Endpoint of OpenNebula XML-RPC API|
||Endpoint for ZeroMQ subscriptions|
||Time in seconds between each evaulation of elasticity rules|
||Host/IP where OneFlow will listen|
||Port where OneFlow will listen|
||Force deletion of VMs on terminate signal|
||Default cooldown period after a scale operation, in seconds|
||Default time to wait for VMs state changes, in seconds|
||Number of threads to make actions with flows|
||Default shutdown action. Values:
||Default number of virtual machines (
||Default name for the Virtual Machines created by Oneflow. You can use any of the following placeholders:
||Default page size when purging DONE services|
Authentication driver to communicate with OpenNebula core
For more information, visit the Cloud Server Authentication reference.
||Logging level. Values:
In the default configuration, the OneFlow server will only listen to requests coming from
localhost (which is enough to control OneFlow over Sunstone running on the same host). If you want to control OneFlow over API/CLI remotely, you need to change
:host parameter in
/etc/one/oneflow-server.conf to a public IP of your Front-end host or to
0.0.0.0 (to work on all IP addresses configured on Host).
Sunstone GUI enables end-users to access the OneFlow from the UI and it directly connects to OneFlow on their behalf. Sunstone has configured the OneFlow endpoint it connects to in
/etc/one/sunstone-server.conf in parameter
:oneflow_server. When OneFlow is running on a different host than Sunstone, the endpoint in Sunstone must be configured appropriately.
Sunstone tabs for OneFlow (Services and Service Templates) are enabled in Sunstone by default. To customize visibility for different types of users, follow the Sunstone Views documentation.
OneFlow CLI (
oneflow-template) uses same credentials as other command-line tools. The login and password are taken from the file referenced by environment variable
$ONE_AUTH (defaults to
$HOME/.one/one_auth). Remote endpoint and (optionally) distinct user/password access to the above is configured in environment variable
$ONEFLOW_URL (defaults to
ONEFLOW_URL=http://one.example.com:2474 oneflow list
See more in Managing Users documentation.
Service Control and Logs¶
Change the server running state by managing the operating system service
To start, restart or stop the server, execute one of:
systemctl start opennebula-flow systemctl restart opennebula-flow systemctl stop opennebula-flow
To enable or disable automatic start on Host boot, execute one of:
systemctl enable opennebula-flow systemctl disable opennebula-flow
Server logs are located in
/var/log/one in following files:
Logs of individual multi-VM Services managed by OneFlow can be found in
$IDidentifies the service
Other logs are also available in Journald. Use the following command to show:
journalctl -u opennebula-flow.service
Permission to Create Services¶
Documents are special types of resources in OpenNebula used by OneFlow to store Service Templates and information about Services. When a new user Group is created, you can decide if you want to allow/deny its users to create Documents (and also OneFlow Services). By default, new groups are allowed to create Document resources.