![]() It can be used with multiple providers such as Oracle VirtualBox, VMware, Docker, and so on. Vagrant is a tool that will allow us to create a virtual environment easily and it eliminates pitfalls that cause the works-on-my-machine phenomenon. These benefits enable teams to resolve issues faster which make the more agile. For instance, Ops can reproduce an issue in a multi node cluster environment, Testers can deploy multiple versions of an application for executing test cases and verifying changes. Even though Minikube provides an excellent platform for getting started, it doesn't provide the opportunity to work with multi node clusters which can help solve problems or bugs that are related to application design and architecture. Multi node Kubernetes clusters offer a production-like environment which has various advantages. Why do we require multi node cluster setup? This setup provides a production-like cluster that can be setup on your local machine. Read here on how to suspend and resume your OpenStack Cookbook lab using Vagrant suspend and awk.This blog post describes the steps required to setup a multi node Kubernetes cluster for development purposes. I will be doing some other posts to show a few nifty ways to use the OpenStack Cookbook lab to learn about the various project features. You now have a two-node OpenStack on KVM lab running and you can dig around to see all of the various features and functionality available. Now you open up your browser to access the Horizon dashboard at using the default credentials for the lab which is a username of admin and a password of openstack to log in:Ĭlick on the Projects tab in the left hand pane and then the Instances menu option to see the active instance that was spun up with the demo script: Results will complete with the final command showing an associated floating IP: You will see a bunch of content roll by on the screen and you can scroll up to see all of the commands that were run and the results: The last step is to run the demo script which is located in the /vagrant/ folder that’s mapped to your local system with the /vagrant/demo.sh command. Next, we import the openrc file to put some environment variables together which will give us access to the endpoints to run the demo script. This is done from the console of the controller virtual machine.įirst, SSH into the machine from the command line using the vagrant ssh controller command: Now it’s time to start up the demo script which will build out the first Neutron router, some floating IP addresses, download a couple of guest instance images to Glance, and spark up a Nova instance. Once it’s all done building you will see a screen similar to this: The build takes about 20-30 minutes depending on your internet connection speed and the CPU, memory, and disk performance in your lab host. You will be prompted for credentials during the process of the build at least once as it needs to set up NFS shares to map the /vagrant/ directory from the guest virtual machines to your local host for access the build scripts on the shared folder: This is easily done thanks to the magic of automation by using the vagrant up -provider=virtualbox/command: Since you have the Vagrant and VirtualBox all set up on your system and the code is downloaded, it’s time to start up the build of the lab. Let’s change directory to the OpenStack Cookbook folder with the cd OpenStackCookbook and then we will want to ensure that we are on the stable Kilo branch of the cookbook using git checkout kilo to set the branch: ![]() I’ve documented that process here: Downloading the OpenStack Cookbook code NOTE: Once you’ve installed Vagrant, it is highly recommended to also install the vagrant-cachier plugin. The lab works great for me during testing when on the road and while disconnected, but we do run a live download of the code and base machines during the setup process. I highlight internet access because you can run the cookbook lab without internet access, but only once it is fully downloaded and built. ![]() You will need to have the following on your Mac in order to run the OpenStack Cookbook lab: Luckily, it doesn’t take much to run the OpenStack Cookbook lab, and most importantly, it is free! I’ve been lucky enough to have helped a little along the way as a reviewer for the 2nd edition of the book, and to have done some small code contributions as well. A great tool for that is the OpenStack Cookbook lab. As an advocate for OpenStack, I am always keen to help give newcomers to the open cloud ecosystem a chance to have a positive learning experience.
0 Comments
Leave a Reply. |