OpenStack deployment troubles? Enter a couple validation tools
Whether you’re on your first or hundredth OpenStack deployment, any administrator will tell you that getting the initial deployment configuration correct is crucial. This gets easier with experience, but what can one do in the meantime to supplement that knowledge? Enter two tools: clapper, and the network isolation template generator.
Firstly: the network template generator. If you’ve read through any of the heat templates, or perused some of the upstream docs, you’ll know that configuring the networks you want in your OpenStack environment is a big part of the architecture. It’s also not easy to make changes to that once the environment is deployed. Typically, these configuration parameters are held in the network-environment.yaml template, as well as the nic-configs/
Secondly: clapper. It’s a suite of ansible playbooks that run both prior to and post deployment to validate the configuration of the environment. Within the tool are prepackaged validations (ansible playbooks) submitted by community members to check for things like adequate file descriptors, open file limits, network gateways, disk space, ip ranges, network templates, detecting rogue DHCP servers, and many more. You can git clone this tool to your undercloud server and run validations at any stage of your deployment. It’s handy in helping you implement best practices that come straight from the experience of the OpenStack community.
Got another tool to share? I’d love to hear from you. One that’s been picking up traction lately for ease of cloud deployments is the quickstart cloud installer. When I get some time, I’ll try it out and post a review.