OpenStack Implementation Service
About the OpenStack Implementation Service
OpenStack is open source software for building cloud platforms. It provides administration
functions for networks, storage, and virtual machines in order to provide Infrastructure as a Service (IaaS)
and storage services, in combination with hypervisors like KVM, Xen, VMWareESXi, and Hyper-V. Users can build
cloud systems while selecting the optimum functions for their requirements, from PoC to commercial
applications. Functions are easily expandable due to its affinity to OSS,* allowing user
*OSS = Open Source Software.
OpenStack provides multi-tenant Infrastructure as a Service (IaaS). Independent tenants are assigned to OpenStack end users. Among tenants, end users can freely combine tools prepared in advance by OpenStack managers like virtual networks, virtual machines, and virtual storage, to flexibly build cloud environments. A single tenant can also be shared among multiple users.
Automation via linking to API tools
A program library is available to issue API requests, using Python and other programming languages, and allowing operation of variety environments. Multiple function settings exist in API, such as for virtual server control, network control, or storage control. Mutual API linking is possible inclusive of tools other than OpenStack, and automation is also possible using configuration management tools (e.g. Ansible or Chef).
Prevention of vendor lock-in
OpenStack uses publicly available API to freely combine other ecosystems, preventing lock-in by particular vendors or cloud. Cloud environments based on OpenStack not only prevent vendor lock-in, they also have the merit of allowing services and systems to be developed flexibly according to business circumstances.
Can build customized IaaS environments according to business circumstances
Builds IaaS environments via necessary Project Services and Core Services essential for IaaS cloud
Nova: component to build and manage virtual machines
Nova is the most vital core component of OpenStack, controlling the preparation and launch of virtual instances. Though it supports many hypervisors, it is primarily used with Linux KVM, which runs virtual machines on Linux. In addition to virtual machines, OpenStack also supports physical machines, Linux Containers (LXC), Docker containers and other components, but because it primarily works with virtual machines, Nova is given the greatest emphasis.
Glance: image control component
To make a virtual instance function, an image of the guest OS to be used is created, then uploaded and registered in an OpenStack environment with Glance, then the virtual instance is created in Nova. Glance has no function to create an image. The actual image and information relating to it (meta information) must both be saved. The meta information is saved in Glance's internal database, while the image itself is saved in an external system like Swift or Cinder.
Cinder: block storage component
Cinder provides a block storage function to permanently store various types of data. Unlike the temporary disk provided by Nova, Cinder offers a storage region to permanently keep data even after the virtual instance is completed.
Swift: object storing component
Swift is a storage function used as a place to store large volumes of data via dispersed object storage with high availability. The two main concepts of Swift are objects and containers. Objects link with Glance, which stores meta information, to store the actual image as the source for launching the virtual instance.
Neutron: network control component
Neutron links to external networks to provide L2/L3 and load balancers/VPN/firewall functions for virtual machines. Networks provided via Neutron when virtual instances are launched are internal networks, connectible externally according to specified external networks.
Keystone: identity component
Keystone provides functions for user management and authentication for the many components making up OpenStack. In addition to managing and authenticating users, it also allows creation or deletion of tenants, as well as token authentication. It can also connect to LDAP servers for flexible authentication management.
Configuration example implementing OpenStack
Use as an expandable infrastructure platform or for cost reductions by decreasing the number of physical servers
Monday - Friday, 9:00 am to 5:30 pm
(excluding national and business holidays)