2.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 deployment method is more likely to be needed in Cloud environments where OVA deployment may not be possible, as is the case with on-premise installations. Note that deployment playbooks will be required, as detailed later.

• From an OpenNAC OVA: When we already have an OVA deployed, most installation steps are already completed. Therefore, will primarily 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.

Keep in mind that the deployment playbooks already call the configuration playbooks. Therefore, if you use the deployment playbook, you should not call the configuration playbook separately.

Additionally, if you use a deployment playbook with an existing OVA deployment, you may encounter errors. To avoid any issues, please follow the proper guide and instructions before launching the automation.

• 2.1.1. From empty Rocky Linux
  • 2.1.1.1. Ansible first-time deployment
  • 2.1.1.2. Ansible node deployment
• 2.1.2. From OpenNAC OVA
  • 2.1.2.1. Giving the nodes an IP
  • 2.1.2.2. Creating and copying the SSH key pair
  • 2.1.2.3. Provisioning Ansible
  • 2.1.2.4. Configuration steps
  • 2.1.2.5. Launch the playbooks
  • 2.1.2.6. Launch the playbooks