The OneGate configuration file can be found at /etc/one/onegate-server.conf. It uses YAML syntax to define the following options:

This is the default file

################################################################################
# Server Configuration
################################################################################
 
# OpenNebula sever contact information
#
:one_xmlrpc: http://localhost:2633/RPC2
 
# Server Configuration
#
:host: 127.0.0.1
:port: 5030
 
################################################################################
# Log
################################################################################
 
# Log debug level
#   0 = ERROR, 1 = WARNING, 2 = INFO, 3 = DEBUG
#
:debug_level: 3
 
################################################################################
# Auth
################################################################################
 
# Authentication driver for incomming requests
#   onegate, based on token provided in the context
#
:auth: onegate
 
# Authentication driver to communicate with OpenNebula core
#   cipher, for symmetric cipher encryption of tokens
#   x509, for x509 certificate encryption of tokens
#
:core_auth: cipher

To start and stop the server, use the onegate-server start/stop command:

<xterm> $ onegate-server start onegate-server started </xterm>

By default, the server will only listen to requests coming from localhost. Change the :host attribute in /etc/one/onegate-server.conf to your server public IP, or 0.0.0.0 so onegate will listen on any interface.

Inside /var/log/one/ you will find new log files for the server:

/var/log/one/onegate.error
/var/log/one/onegate.log

Before your VMs can communicate with OneGate, you need to edit /etc/one/oned.conf and set the OneGate endpoint. This IP must be reachable from your VMs.

ONEGATE_ENDPOINT = "http://192.168.0.5:5030"

Continue to the OneGate usage guide.