The purpose of this project is to automatically install the desired operating system on HPE Proliant servers using ansible and maas software, without human intervention.
Canonical Maas software was used for operating system installation in the project. Ansible software was used to run the installation processes in a specific order and to make the necessary settings on the HPE Server and MAAS software for the operating system installation.
The following system requirements are needed in order for the written codes to work properly.
- Maas Server (Region & Rack Controller)
- You can find detailed information about Maas server setup from the link below.
- Ansible Core
- You can find detailed information installing ansible core from the link below. You can install ansible where located on Maas servers operating system.
- HPE Proliant Servers Gen10 & Gen10+
- You can download the github repository to the server with ansible installed with the following command.
- git clone [email protected]:emrbaykal/maas-hpe.git
-
Before start working, infrastructure-specific and host-spesific variables must be filled .
The variables defined under this directory contain the connection and protocol information of the systems in the infrastructure.
The following variable define Connection protocol, username and password information that ansible will use to access the server where maas cli is installed.
ansible_connection: ssh ansible_user: hpe ansible_ssh_pass: xxxxxx
The following variable define maas cli ip address & maas server api url, username and api key information that ansible will use to access the server where maas rack controller and cli is installed.
# maas user maas_user: admin # maas api url maas_url: http:https://00:00:00:00:5240/MAAS # maas API Key maas_apikey: admin-api-key-sample # maas cli delegation server maas_cli_srv: maas-cli-server maas_cli_srv_ip: 00:00:00:00
If there is vmware vcenter in your environment and virtual host deployment will be made on vmware, the following VMware virtual center connection information must be filled. The following variable define VMware vcenter hostname, username , password and datacenter name informations.
# Vmware Virtual Center Info vcenter_hostname: 00:00:00:00 vcenter_username: [email protected] vcenter_password: xxxxxxx datacenter_name: VMware-Datacenter
If there is vmware vcenter in your environment and virtual host deployment will be made on vmware, the following esxi host whose deployment is planned host connection information must be filled. The following variable esxi username , password informations.
# Planing to Deploy ESXI Host username & password Informations esxi_username: root esxi_password: xxxxx
-
The host specific information of the target servers to be installed is filled into this csv file. Then the information in this csv file is read by ansible and host variable files are created. After the target server is customized using the information in the host variable files, then operating system is installed.
-
The fields in the csv file should be filled in the following format.
hostname: Target Server hostname. server_state: If the target server is virtual, the "virtual" parameter should be entered, If the target server is physical, the "physical" parameter should be entered. ilo_address: If the target server is physical, ilo ip address should be entered, If the target server is virtual, keep blank. ilo_username: If the target server is physical, ilo username (admin rights) should be entered, If the target server is virtual, keep blank. ilo_password: If the target server is physical, ilo password should be entered, If the target server is virtual, keep blank. public_net_interface_ip: Target Server public network interface ipaddress. public_net_interface_subnet: Target Server public network interface subnet. public_net_interface_mac: Target Server public network interface mac address. deployment_net_interface_mac: Target Server deployment network interface mac address. Maas will use this mac address during commissioning state. domain_name: Target Server domain name. maas_zone_name: Target Server zone information. motherboard_firmware: If target Server bios firmware type legacy , the "bios" parameter should be entered. If target Server bios firmware type efi , the "efi" parameter should be entered. distro: If Red Hat Enterprise Linux will be installed on the target server, the "rhel" parameter should be entered. If VMware ESXI Host will be installed on the target server, the "vmware" parameter should be entered. distro_version: If Red Hat Enterprise Linux will be installed on the target server, the "7.5" or "6.9" parameter should be entered. If VMware ESXI Host will be installed on the target server, the "7.0" parameter should be entered. server_role: If a database will be installed on the target server, the "database" parameter should be entered. If a ESXI Host will be installed on the target server, the "virtualization" parameter should be entered. If it is not clear which application will be installed on the target server, keep blank. os_disc_raid: If the target server is physical, the "RaidX" parameter should be entered. If the target server is virtual, keep blank. os_disc_capacity_gb: If the target server is physical, the "xx" GB parameter should be entered. If the target server is virtual, keep blank. boot_partition_size_gb: If Red Hat Enterprise Linux will be installed on the target server, the "xx" GB parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. boot_partition_fs: If Red Hat Enterprise Linux will be installed on the target server, the "fat32" parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. swap_partition_size_gb: If Red Hat Enterprise Linux will be installed on the target server, the "xx" GB parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. swap_partition_fs: If Red Hat Enterprise Linux will be installed on the target server, the "swap" parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. root_partition_size_gb: If Red Hat Enterprise Linux will be installed on the target server, the "xx" GB parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. root_partition_fs: If Red Hat Enterprise Linux will be installed on the target server, the "ext4" or "xfs" parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. var_partition_size_gb: If Red Hat Enterprise Linux will be installed on the target server, the "xx" GB parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. var_partition_fs: If Red Hat Enterprise Linux will be installed on the target server, the "ext4" or "xfs" parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. home_partition_size_gb: If Red Hat Enterprise Linux will be installed on the target server, the "xx" GB parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. home_partition_fs: If Red Hat Enterprise Linux will be installed on the target server, the "ext4" or "xfs" parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. tmp_partition_size_gb: If Red Hat Enterprise Linux will be installed on the target server, the "xx" GB parameter should be entered. If a ESXI Host will be installed on the target server, keep blank. tmp_partition_fs: If Red Hat Enterprise Linux will be installed on the target server, the "ext4" or "xfs" parameter should be entered. If a ESXI Host will be installed on the target server, keep blank.
-
-
After entering the infrastructure-specific and host-specific variables, you can run the following command to setup the target servers.
-
When the following yml file is execute:
anssible-playbook site.yml -
The jobs summarized below are executed, also the following steps can be run independently using tags:
- The host variables are created by reading the data on the csv file created by the user.
anssible-playbook site.yml --tags role::host-variable - Login to MAAS Server via using Maas CLI.
- Checking whether the server is registered to maas.
- If the server is registered to maas, the status of the server is checked.
- If the server is registered to maas and its state is Deployed main plays will not be run for that server.
- If the target server is HPE proliant Gen10 server, necessary configurations for bios and local disks are made.
anssible-playbook site.yml --tags role::maas-configure-physical-server - Ansible registers the target server to the maas server, then the commissioning process is started.
anssible-playbook site.yml --tags role::maas-add-device - Network configuration is done with the information filled in the csv file of the target server.
anssible-playbook site.yml --tags role::maas-configure-net-int - Storage configuration is done with the information filled in the csv file of the target server.
anssible-playbook site.yml --tags role::maas-configure-storage-layout - Operating system deployment perform to the target server.
anssible-playbook site.yml --tags role::maas-deploy-machine - If the target server is desired to be set up as vmware host, after the operating system installation, the registration process is performed in the Vmware Virtual Center.
anssible-playbook site.yml --tags role::maas-add-esxi-vcenter
- The host variables are created by reading the data on the csv file created by the user.
-
- Host Variable Role Tasks {{ role: host-variable }}
- Using this role, the host variables are created by reading the data on the csv file created by the user.
- Create host variable file
- 01-host-var.yml
- Convigure ansible hosts file
- 02-hosts.yml
- Pre Tasks
- Pretask is a conditional execution block that runs before running main plays. These tasks do some prerequisite checks and validations.
- Login to MAAS Server via using Maas CLI
- Checking whether the server is registered to maas.
- If the server is registered to maas, the status of the server is checked.
- If the server is registered to maas and its state is Deployed,
main plays will not be run for that server.
- Main Role Tasks:
- HPE Proliant Server Preconfigure Role Tasks {{ maas-configure-physical-server }}
- If the target server is HPE proliant Gen10 server, the following tasks are run before the operating system installation.
- HPE Proliant Server Preconfigure Role Tasks {{ maas-configure-physical-server }}
- Check Proliant Server power state, powered on server if needed.
- 01-power-state.yml
- Disk raid configuration is made to the server in the desired config.
- 02-logical-drives.yml
- Bios settings are made according to the application to be installed on the server.
- 03-bios-settings.yml
- Tasks used to register target servers to the maas server {{ maas-add-device }}
- It registers the target server to the maas server, then the commissioning process is started.
- If the target server is a virtual server running in vmware environment,
connect to Vmware Vcenter and UUID information of the related virtual server is pulled.
- 01-query-vm.yml
- If the target server is a virtual server running in vmware environment,
it is registered to the maas server together with the UUID information obtained in the previous task.
After the registration process, the commissioning state is started automatically.
- 02-add-virtual-device.yml
- if target server is HPE Proliant Server, it is registered to the maas server together with the server ILO informations.
After the registration process, the commissioning state is started automatically.
- 03-add-physical-device.yml
- Network configuration of target server. {{ maas-configure-physical-server }}
- Network configuration is done with the information filled in the csv file of the target server.
- Checking whether the server is registered to maas.
- If the server is registered to maas, the status of the server is checked.
- 01-query-machine-id-net.yml
- The settings of the public network interface are made.
- 02-conf-public-insterface.yml
- Storage configuration of target server. {{ maas-configure-storage-layout }}
- Storage configuration is done with the information filled in the csv file of the target server.
- Checking whether the server is registered to maas.
- If the server is registered to maas, the status of the server is checked.
- 01-query-machine-storage.yml
- Clean current storage layout
- 02-clean-storage-layout.yml
- If the target server is desired to be set up as vmware host, to create vmfs storage layout.
- 03-set-vmfs-storage-layout.yml
- If the target server is desired to be set up as Redhat Linux OS, to crate boot partition.
- 04-create-boot-partition.yml
- If the target server is desired to be set up as Redhat Linux OS, to crate LVM Layout
- 05-create-volume-group.yml
- If the target server is desired to be set up as Redhat Linux OS, to crate SWAP Partition
- 06-create-swap-logical-volume.yml
- If the target server is desired to be set up as Redhat Linux OS, to crate / Partition
- 07-create-root-logical-volume.yml
- If the target server is desired to be set up as Redhat Linux OS, to crate /var Partition
- 08-create-var-logical-volume.yml
- If the target server is desired to be set up as Redhat Linux OS, to crate /home Partition
- 09-create-home-logical-volume.yml
- If the target server is desired to be set up as Redhat Linux OS, to crate /tmp Partition
- 10-create-tmp-logical-volume.yml- Operating system deployment perform to the target server. {{ maas-deploy-machine }}
- The installation is started according to the operating system version desired to be installed on the target server.
- Checking whether the server is registered to maas.
- If the server is registered to maas, the status of the server is checked.
- 01-query-machine-deploy.yml
- Operating System Deployment
- 02-deploy-machine.yml- Vmware Host Vcenter Registration. {{ maas-add-esxi-vcenter }}
- If the target server is desired to be set up as vmware host, after the operating system installation, the registration process is performed in the Vmware Virtual Center.
- Add ESXi Host to vCenter.
- 01-add-host-to-vcenter.yml- Post Tasks
- Post is a conditional execution block that runs after running main plays.
- Logout to MAAS Server via using Maas CLIApache License 2.0, check LICENSE file for more information
WARNING: Despite the modules are used by the Author regularly they are tested only manually
To get in touch with author you can use email [email protected] or create a issue on github when requesting some feature.