Chapter 7. Your OpenStack Cloud in Action

Finally, we are at the chapter towards which we were inching gradually in the previous chapters. In this chapter, we will put together all that we have set up and see a real life scenario of us being a cloud provider to, say, our internal development team. We will stitch everything together and see all the services we have set up in action, so without any further ado let's dive in.

To be specific, we will cover the following topics in this chapter:

  • Gathering service requirements
  • Managing your network
  • Requesting services
  • Creating VM templates

Gathering service requirements

We hope that you are ready to start pointing, clicking and typing commands, but before we do just that, let's create a scenario for which we will be providing services.

So, we are a part of the IT wing of a company whose core business is software development. The company wants to make its processes agile and speed up the time to market the products it has been developing, and so we have been tasked with providing a private cloud environment to the various development and testing teams.

We have successfully done that by setting up our OpenStack environment and we have our first customer at our door, who is a project manager for a new product that has been conceptualized. They need an environment where the developers can freely spin instances up and down.

So, we have to ask the following questions:

  • What is the name of the project?
  • Project members – We will create individual accounts and will send the project to them as this is not yet Active Directory Integrated
  • Operating systems required – Please note that this can be predefined by us as a part of corporate standards
  • Networking configuration needed – We may choose to give the project members access to create their own networks, but in our case, we will set up everything for them for the first time
  • Quotas (The maximum number of instances, RAM, CPU, and so on) – This is required to set a quota, by default, and a tenant/project will be allowed a certain amount of resource that you can check out on the Horizon dashboard as shown in the following:
Gathering service requirements

Tip

If you need to change the defaults for every project, click on Update Defaults and change to the values you need.

Of course, the actual capacity also needs to be available in order to perform these actions. The ones shown in the preceding screenshot are merely limits that the system will enforce and not allow the users to request over these limits.

So our fictitious project manager gives us the following information:

  • Project/Tenant Name: TestingCloud
  • Users: John Doe ([email protected]), Jane Doe ([email protected])
  • Networking requirement: Single Layer 2 network with external access, DHCP IP addressing
  • Quotas: Defaults are fine

So, armed with the preceding information, we go on to take our cloud out for a spin.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset