In the previous blog: “Concept of OpenStack” we have discussed what is OpenStack, and then we also discussed about two components i.e., Compute (Nova) & Networking (Neutron) of OpenStack. In today’s blog, we are going to discuss the remaining components of OpenStack.
So let’s start the discussion:
1. Block storage (Cinder)
The OpenStack Block Storage (Cinder) offers constant block-level storage devices for use in OpenStack evaluation cases. The creation, connecting and disconnecting of the block devices to the server is managed by the Block Storage system. For giving permission to the users of the cloud for managing their personal storage requirements, the volumes of Block Storage are fully merged into OpenStack account and its dashboard.
The OpenStack can also use other platforms for storage including storage of native Linux server like GlusterFS, Linux LIO. NetApp etc. The Block Storage is suitable for accomplishing delicate situations like storage of database, scalable file systems, or allowing a server to access the natural block-level storage.
Whatever functionality of backed up data that is stored on the block storage is managed by snapshot. If you want to construct a new block storage proportions you can use snapshots or if you want to restore the backed up data then also you can use the snapshot.
2. Image (Glance)
The OpenStack Image (Glance) offers services like detecting, enrolling and releasing the images of disk and server. Templates can be used as stored images. The OpenStack Image (Glace) can be used for storing and classifying the backups which are unlimited. The back ends like Swift can be used for storing the disk and images of the server. This is also an API service which offers standard REST interface for questioning information related to images of disk and makes the users pass those images to the new servers.
The OpenStack (Glance) service includes many improvements in the current bestowal infrastructures. For example: When the OpenStack (Glance) service is merged with the VMware, then it can insert features which are advanced to the vSphere family like vMotion which is a existing transfer of a working VM, from one physical server to another physical server that too without any service disruption, large availability, and also the DRS i.e. Dynamic Resource Scheduling.
Like this, the OpenStack Image (Glance) facilitates an active and automatic self oriented data center, providing maintenance of hardware for the drifting servers with no downtime.
When other modules of OpenStack require communicating with images, like Heat, at that time they must interact with the metadata of those images via Image (Glance). At the same time, Nova can also represent information related to the images, and design an image modification as per the demand.
3. Object storage (Swift)
The Object Storage (Swift) component of OpenStack is accessible through an extra system for storage. There are many disk drives which are distributed across all the servers present in the data center on which the files and objects are written. With the help of OpenStack software which is important for assuring the duplication of data and also the merging of the data throughout the cluster. Suppose any server or hard drive fails, then OpenStack uses the software analytics for making it sure that the duplication of data and the allotment of the data throughout various devices, cheap resources like hard drives and servers can also be used.
4. Dashboard (Horizon)
The OpenStack Dashboard (Horizon) component offers to both administrators as well as users an interface which is graphical and it is also used for accessing, provisioning and automating the installment of resources which are cloud based. Its design includes intermediate services as well as products like Billing, controlling and other extra tools of management.
This component is also branded for the various proprietary vendors those who desire to use it. The users can communicate with the various resources of the OpenStack using the Dashboard (Horizon) component of OpenStack in different ways. The developers can automatically access or construct tools for controlling the various resources with the help of local OpenStack API or using the EC2 uniformity API.
5. Orchestration (Heat)
Heat which is an Image service is used for organizing many complex applications of the cloud with the help of templates, via both the local OpenStack REST API (Representational State Transfer application Program Interface) as well as by a Query API which is in accordance with the Cloud formation.
6. Telemetry (Ceilometer)
The Telemetry (Ceilometer) component of OpenStack offers a single platform for billing systems, allowing each and every counter which requires incorporating client billing throughout all the recent and following OpenStack components. The release of counters is track able and audible and all the counters should be easily scalable for supporting new projects and also supporting representatives for performing the collection of data independent of the entire system.
7. Workflow (Mistral)
The Workflow (Mistral) component of the OpenStack is a service which controls workflows. The clients generally write the workflow with the help of a workflow language on the basis of YAML and then send this explanation of the workflow to the Mistral through the REST API. After that the user can begin this workflow physically through the REST API(Representational State Transfer Application Program Interface) or build a stimulus for beginning the workflow on the basis of some kind of event.
8. Elastic map reduce (Sahara)
The Sahara or the Elastic map reduce component of OpenStack is a component which can smoothly and quickly supply Hadoop troupes. Different guidelines can be specified by the users such as version number of Hadoop, the type of the troupe features, also describing disk space, settings of RAM and CPU and so on. Once the user supplies all the guidelines then the Sahara installs the troupe immediately. It can also offer various ways to calibrate already existing Hadoop cluster by accumulating and deleting the worker nodes as per requirement.
9. Bare metal (Ironic)
Bare metal (Ironic) is a project of an OpenStack which caters the machines of the Bare metal rather than the machines which are virtual. It is best considered as a Bare metal API and also a group of plugins which communicates with it.
10. Messaging (Zaqar)
Zaqar is a multi-tasker cloud messaging service for the web developers. This service emphasizes completely on the RESTful API that can be used by developers for sending messages between different components of the SaaS and the various applications of the mobile by using different patterns of the interaction. The basic element of this API is a systematic messaging engine which is designed by keeping in the mind the adjustability and security. The Other components of the OpenStack can communicate with Zaqar to supply to the end users and to interact with the guest representatives which executes the overcharging cloud layer.
11. Shared file system (Manila)
The Shared file system (Manila) component of the OpenStack offers an open API for managing portions in a dealer cynical framework. Usual locals involve the capabilities of creating, removing and giving or declining permission to a part and can be used as an independent or in a different variety of network settings. The corporate storage devices from EMC, NetApp, and Oracle and so on are also supported and at the same time the file system techniques like Red Hat GlusterFS also.
12. DNS (Designate)
The DNS (Designate) component of the OpenStack is a multi-tasker REST API (Representational State Transfer Application Program Interface) which is used for controlling and managing DNS. This component offers DNS as a kind of service and it is in accordance with current DNS servers to control the DNS zones on the basis of the per visitor.
13. Database (Trove)
Database (Trove) component of the OpenStack is a service as a database which is catering to the related and non related database engine.
14. Search (Searchlight)
The Search (Searchlight) component of the OpenStack offers a modern state of the art and steady search abilities throughout the different OpenStack cloud services. It attains this by depositing the queries related to the user search from some different OpenStack API (Application Program Interface) servers by listing their data into ElasticSearch. This component can be merged with Horizon and it can also offer a command line interaction.
15. Key manager (Barbican)
It is a REST API which is built for safe storage, implementing and managing secrets. Its main aim is to become useful for all settings involving big transient clouds.
16. container orchestration (Magnum)
Container orchestration (Magnum) is a component of OpenStack which is an API service designed and developed by the OpenStack containers team allowing the container balance such as Docker Swarm, Kubernetes, etc. which are available as best resources in OpenStack. Magnum takes help of Heat for balancing the operating system image which consists of Docker and Kubernetes and passes that image either in virtual machines or in bare metal which is present in a cluster configuration.
17. root Cause Analysis (Vitrage)
The next component of OpenStack is Root Cause analysis (Vitrage) which is a service for managing, checking and extending the strains and measures, resulting into the perceptions related to the root cause of the issues and removing them before they can be spotted.
18. Rule-based alarm actions (Aodh)
This component is a concerning service which allows the capabilities to prompt actions on the basis of exact rules opposite to data measures which are gathered by Ceilometer.
Ceilometer: It is a service of data collection which offers the capability to standardize and convert data throughout the latest OpenStack components to accomplish the work undertaken to provide a platform for the future OpenStack components.
19. Identity (Keystone)
The other component of the OpenStack is Identity (Keystone) which offers a major Directory of users mapped out with the OpenStack services which they can be able to access. It appears as a common authority system throughout the cloud operating system and merges with the current backend directory services like LDAP i.e. Lightweight Directory Access Protocol.
It provides platform to the many forms of verification involving local username and password, Amazon Web Series (AWS) style logins. Further it offers a listing of all of the services which can be installed in an OpenStack cloud using only one catalogue. The users and the inermediator devices can decide which features they can fetch.
That’s all for today! I hope you find this blog helpful! If yes, please mention your opinion in the comment section below.