TBA-cloud-provider: logos of OpenNebula and the Cloud Provider

Deploying OpenNebula on Ampere Hardware

This repository contains the needed code and documentation to perform an OpenNebula deployment and configuration on Ampere hardware. It extends the one-deploy-validation repository, which is added as a git submodule.

• Requirements
• Hardware Specifications
• Required Parameters
• Deployment and Validation

Requirements

1. Install hatch

   pip install hatch

2. Initialize the dependent one-deploy-validation and one-deploy submodule

   git submodule update --init --remote --merge

3. Install the opennebula.deploy collection with dependencies using the submodule's tooling:

   make submodule-requirements

Hardware Specifications

See the details of the Ampere servers that has been used to certify the hardware platform for OpenNebula deployment: Ampere OpenNebula. After the servers have been provisioned, take note of the required parameters that are required for automation of OpenNebula deployment and validation.

Required Parameters

Update the inventory values to match the provisioned infrastructure.

Description	Variable Names	Files/Location
Frontend Host IP	ansible_host	inventory/ampere.yml
KVM Host IPs	ansible_host	inventory/ampere.yml
VXLAN PHYDEV	vn.vxlan.template.PHYDEV	inventory/ampere.yml
GUI password of oneadmin	one_pass	inventory/ampere.yml

Optional customization parameters:

Description	Variable Names	Files/Location
VXLAN Starting IP	vn.vxlan.template.AR.IP	inventory/ampere.yml
VXLAN IP range size	vn.vxlan.template.AR.SIZE	inventory/ampere.yml

Deployment and Validation

Use the provided Makefile commands to automate deployment and testing:

1. Review the inventory and playbooks directories, following Ansible design guidelines.

2. Deploy OpenNebula:

   make deployment

3. Configure the deployment for the specifics of ARM64 architecture of Ampere servers:

   make specifics

4. Verify the deployment:

   make validation

For more information about the submodule's tooling, refer to its README.md and for detailed documentation on the deployment automation refer to the one-deploy repo.