Once the installer has completed successfully, ansible sites.yml playbook completes without errors, and we have integrated ceph we can start verification and configuration.
Note: For anyone who suffers from OCD, yes this is a slightly different build than the environment that was used for the previous 1-6 blog posts – that has been rebuilt many times since I’ve had the chance to write this post. The process is the same.
Locate Login Account Details
- On the HLM deployer node get the user account passwords
- Add the hlm alias to the /etc/hosts file on the deployer node
- Quickly verify the network by pinging all the hostnames in the /etc/hosts file on one of the controller nodes.
Configure Cinder Volume Type
- Add a volume type for the ceph storage (this can also be achieved using Horizon rather than the cli)
- create a test volume and then delete it
Configure the External Network (floating ips)
- You can either run the HLM playbook to perform this action or use the CLi as detailed below. The playbook does not give you the flexibility to set the gateway ip address at present.
Add a private network
- As demo user, add a private network with router to the external network.
- Try the following one of the controller nodes
Upload a test image
- Use the ansible playbook to upload a demo image for testing from the deployer node
Tempest Verification Tests Setup
- Configure the environment for for tempest using the supplied playbooks and then run the tests
- Execute the default tests as follows
- Beware of false failures – not all the tests run as expected which usually results in approximately 4 failures out of 246 tests
- Get the portal details from the /etc/hosts file.
- Default users are admin and demo. Password locations are detailed at top of this post.
Access Operations Console
- The operations console is available at port 9095 on the management vip identified above
- Default user is admin. Same password as above.
ELK – Centralised Logging Access
- Default user is kibana. Password locations are detailed at top of this post.
That’s it for now. The final blogpost in this series covers some of the errors encountered during the installation process.