3.1. Automated deployments

OpenNAC Enterprise provides automation tools to ease node deployments with Ansible. Ansible is a software tool that provides simple but powerful automation for cross-platform computer support. In the OpenNAC Enterprise case, it automates the deployment of the Core Principal, Core Worker, Core Proxy, Analytics, and Sensor.

Following this guide, you will be able to use the basic Ansible commands to deploy your OpenNAC Enterprise infrastructure

There are two scenarios where we can launch the automation:

• From an empty Rocky Linux: This is more likely to be needed on Cloud environments where we can’t deploy an OVA as in On-Premise. As will be detailed later, keep in mind that we will need the deployment playbooks.

• From an OpenNAC OVA: When we already have an OVA deployed, most of the installation steps are already done, so we will need the configuration playbooks.

Note

A playbook is a YAML automation script that connects by SSH with one or more servers to execute commands or modules.

It is important to remember that the deployment playbooks call the configuration playbooks, so if you use the deployment one, you should not call again the configuration playbook.

Also, if you use a deployment playbook when you have an OVA already deployed, you might find some errors, so please follow the proper guide before launching the automation.

• 3.1.1. Ansible deployment from empty Rocky Linux
  • 3.1.1.1. Giving the nodes an IP
  • 3.1.1.2. Creating and copying the ssh key pair
  • 3.1.1.3. Provisioning Ansible
  • 3.1.1.4. Configuration steps
  • 3.1.1.5. Launching the playbooks
• 3.1.2. Ansible configuration from OpenNAC OVA
  • 3.1.2.1. Giving the nodes an IP
  • 3.1.2.2. Creating and copying the ssh key pair
  • 3.1.2.3. Locating the playbooks
  • 3.1.2.4. Repository configuration and corporate proxy
  • 3.1.2.5. Configuration steps
  • 3.1.2.6. Launching the playbooks