![Lead Image © Tom Wang, Fotolia.com Lead Image © Tom Wang, Fotolia.com](/var/ezflow_site/storage/images/archive/2018/46/openstack-installation-with-the-packstack-installer/po-23898-fotolia-tom_wang_fotolia-mann_liest_buch_auf_wolke_resized.png/154123-1-eng-US/PO-23898-Fotolia-Tom_Wang_Fotolia-Mann_liest_Buch_auf_Wolke_resized.png_medium.png)
Lead Image © Tom Wang, Fotolia.com
OpenStack installation with the Packstack installer
Living in the Clouds
For several years, cloud computing in the global IT market has become common, both in corporate infrastructure and among private users. In medium and large companies, it replaces a not very flexible, poorly scalable, and often expensive computer infrastructure, whereas it allows small businesses, startups, and private users to transfer the entire burden of providing IT services to an external supplier.
In addition to the division into private and public clouds, you can divide cloud computing according to the types of services offered. In this category, two types of clouds lead: Infrastructure as a Service (IaaS; e.g., OpenStack and Amazon Web Services), which provides the entire virtual infrastructure, including servers, mass storage, and virtual networks, and Storage as a Service (SaaS; e.g., Dropbox, Hightail), which delivers storage space to clients.
The ways to install an OpenStack cloud range from a tedious step-by-step installation of individual OpenStack services to the use of automated installation scripts, such as Packstack or TripleO (OpenStack on OpenStack), which significantly accelerates cloud installations. Whereas TripleO is used mainly in installations for production environments, Packstack [1] is used for quickly setting up development or demonstration cloud environments.
In this article, I present an example of an IaaS-type RDO [2] OpenStack Pike [3] installation using the Packstack installer.
OpenStack
A typical OpenStack environment comprises a cloud controller (Controller node) that runs most of the cloud services, including network services (Neutron), and at least one Compute node (hypervisor) controlling the operation of virtual machines, called instances. The most common reason for integrating
...Buy this article as PDF
(incl. VAT)