This page explain how to install the Inmanta orchestrator software and setup an orchestration server. On any platform Inmanta requires at least the latest Python 3.6 or 3.7 and git.
When you use Inmanta modules that depend on python libraries with native code, python headers and a working compiler is required as well.
This guide goes through the steps to setup an Inmanta service orchestrator server. This guide assumes a RHEL 7 or CentOS 7 server. The rpm packages install the server configuration file in /etc/inmanta/server.cfg
Optional step 1: Setup SSL and authentication¶
Follow the instructions in Setup authentication to configure both SSL and authentication. It is not mandatory but still highly recommended.
Step 2: Install PostgreSQL 10¶
PostgreSQL 10 can be installed by following the installation guide for your platform.
If you are in the process of migrating an existing Inmanta server from MongoDB to PosgreSQL, you can use the following database migration procedure: Migrate from MongoDB to PostgreSQL.
Step 3: Setup a PostgreSQL database for the Inmanta server¶
Initialize the PostgreSQL server:
sudo /usr/pgsql-10/bin/postgresql-10-setup initdb
Start the PostgreSQL database
sudo systemctl start postgresql-10
Create a inmanta user and an inmanta database by executing the following command. This command will request you to choose a password for the inmanta database.
sudo -u postgres -i sh -c "createuser --pwprompt inmanta; createdb -O inmanta inmanta"
Change the authentication method for local connections to md5 by changing the following lines in the
# IPv4 local connections: host all all 127.0.0.1/32 ident # IPv6 local connections: host all all ::1/128 ident
# IPv4 local connections: host all all 127.0.0.1/32 md5 # IPv6 local connections: host all all ::1/128 md5
Restart the PostgreSQL server to apply the changes made in the
sudo systemctl restart postgresql-10
Step 4: Set the database connection details¶
/etc/inmanta/server.cfg file as such that it contains the correct database connection details. Add/Change the
database section of that file in the following way:
[database] name=inmanta username=inmanta password=<password>
Replace <password> in the above-mentioned snippet with the password of the inmanta database. By default Inmanta tries to
connect to the local server and uses the database inmanta. See the
database section in the
configfile for other options.
Step 5: Set the server address¶
When virtual machines are started by this server that install the inmanta agent, the correct
server.server-address needs to be
configured. This address is used to create the correct boot script for the virtual machine.
Set this value to the hostname or IP address that others systems use to connect to the server
in the configuration file stored at
If you deploy configuration models that modify resolver configuration it is recommended to use the IP address instead of the hostname.
Step 6: Configure ssh of the inmanta user¶
The inmanta user that runs the server needs a working ssh client. This client is required to checkout git repositories over ssh and if the remote agent is used.
- Provide the inmanta user with one or more private keys:
- Generate a new key with ssh-keygen as the inmanta user:
sudo -u inmanta ssh-keygen -N ""
- Install an exiting key in
- Make sure the permissions and ownership are set correctly.ls -l /var/lib/inmanta/.ssh/id_rsa -rw-------. 1 inmanta inmanta 1679 Mar 21 13:55 /var/lib/inmanta/.ssh/id_rsa
- Configure ssh to accept all host keys or white list the hosts that are allowed or use signed host keys
(depends on your security requirements). This guide configures ssh client for the inmanta user to accept all host keys.
/var/lib/inmanta/.ssh/configand create the following content:
Host * StrictHostKeyChecking no UserKnownHostsFile=/dev/null
Ensure the file belongs to the inmanta user:sudo chown inmanta:inmanta /var/lib/inmanta/.ssh/config
- Add the public key to any git repositories and save if to include in configuration models that require remote agents.
- Test if you can login into a machine that has the public key and make sure ssh does not show you any prompts to store the host key.
Step 7: Start the Inmanta server¶
Start the Inmanta server and make sure it is started at boot.
sudo systemctl enable inmanta-server sudo systemctl start inmanta-server
Step 8: Connect to the dashboard¶
The server dashboard is now available on port ‘8888’
Optional Step 8: Setup influxdb for collection of performance metrics¶
Follow the instructions in Performance Metering to send performance metrics to influxdb. This is only recommended for production deployments.