{"id":2188,"date":"2020-12-30T16:19:00","date_gmt":"2020-12-30T13:19:00","guid":{"rendered":"https:\/\/telcocloudbridge.com\/?p=2188"},"modified":"2026-09-21T19:38:12","modified_gmt":"2026-09-21T19:38:12","slug":"openstack-cheat-sheet","status":"publish","type":"post","link":"https:\/\/telecomlighthouse.com\/?p=2188","title":{"rendered":"Your Quick OpenStack Cheat Sheet!"},"content":{"rendered":"\n

For a while I thought to write about an OpenStack cheat sheet showing OpenStack components, so you can refer to it as an easy to use handy reference.<\/p>\n\n\n\n

If you are using NFV, you are using OpenStack for sure. OpenStack sits at the VIM layer inside NFV MANO and is the most important piece to manage the cloud infrastructure. For a quick refresher on NFV, click here, NFV Cheat Sheet.<\/a><\/p>\n\n\n\n

Openstack is very complex. You hear a lot of terms like Cinder, Glance, Nova, Horizon, etc. They are quite confusing to know and remember. So here I made a small OpenStack cheat sheet as a diagram\/infographic which you can keep as a reference. Just match the block colors with the colors of lines and you will easily know the role of each component\/block and how they interact with the other blocks.<\/p>\n\n\n\n

How about sticking a copy of the diagram on your desktop for easy reference !<\/p>\n\n\n\n

What is OpenStack?<\/h6>

“OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed and provisioned through APIs with common authentication mechanisms”. “https:\/\/www.openstack.org\/software\/<\/a>“<\/p><\/div><\/div>\n\n\n\n

So here is the cheat sheet\/infographic about Openstack services.<\/p>\n\n\n\n

Do take a note however that there are many more services in openStack<\/a>, here are the most important core ones that you must know <\/p>\n\n\n\n

\"\"
OpenStack Cheat sheet for Core Services-Simplified from openstack.org<\/a><\/figcaption><\/figure>\n\n\n\n

Description of OpenStack Cheat sheet<\/h2>\n\n\n\n

Horizon ( Dashboard)<\/h2>\n\n\n\n

This allows users to work on OpenStack using web GUI instead of CLI. This provides a user-friendly dashboard. This is part of common services<\/p>\n\n\n\n

Ceilometer ( Telemetry)<\/h2>\n\n\n\n

The ceilometer is a component of the Telemetry project. Its data can be used to provide customer billing, resource tracking, and alarming capabilities across all OpenStack core components.<\/p>\n\n\n\n

Keystone ( Identity)<\/h2>\n\n\n\n

keystone is the simplest service in OpenStack. it is a core service and provides authentication and authorization of tenants in OpenStack.<\/p>\n\n\n\n

Nova ( Compute)<\/h2>\n\n\n\n

Nova is the original core component of openstack and considered one of the most complicated components in openstack. It providess compute service in openstack.<\/p>\n\n\n\n

It has various components:<\/p>\n\n\n\n

\"\"
Nova components ( Ref: Openstack.org<\/a>)<\/figcaption><\/figure><\/div>\n\n\n\n

Nova-Compute<\/h4>\n\n\n\n

The nova-compute is responsible for creating and termination of VM instances via hypervisor APIs ( for example Libvirt KVM, VMWare API for VMware)<\/p>\n\n\n\n

Nova Conductor<\/h4>\n\n\n\n

The Nova conductor provides database access to compute nodes. The logic is to have all the database access pass through Nova conductor instead of compute nodes accessing DB directly thus reducing the risks in case of compute node gets compromised.<\/p>\n\n\n\n

Nova-api<\/h4>\n\n\n\n

The nova-api component accepts and responds to the end user and computes API calls.<\/p>\n\n\n\n

Nova-Scheduler<\/h4>\n\n\n\n

Compute uses the nova-scheduler service to determine how to dispatch compute requests. For example, the nova-scheduler service determines on which host a VM should launch.<\/p>\n\n\n\n

Neutron ( Networking)<\/h2>\n\n\n\n

Neutron is a service that provides networking service to other components of OpenStack<\/p>\n\n\n\n

Storage <\/h2>\n\n\n\n

There are various type of storages in openstack. It is important to understand the difference between them<\/p>\n\n\n\n

Cinder (Block Storage)<\/h2>\n\n\n\n

Cinder provides block storage in OpenStack. It provides raw volumes that can be used as a hard disk in virtual machines. It is called block storage because a large amount of data is chopped into blocks and stored with a unique identifier is attached which allows the data to be retrieved quickly and efficiently. <\/p>\n\n\n\n

Use Cases: <\/h4>\n\n\n\n
  • Databases-Block storage is common in databased and other mission-critical applications that demand high performance<\/li>
  • Volume snapshot management<\/li>
  • Attaching or detaching volumes from instances etc<\/li>
  • Creating and deleting of a snapshot of the volume.<\/li><\/ul>\n\n\n\n

    Swift (Object Storage)<\/h2>\n\n\n\n

    Swift provides an object-based storage service and accessible through Rest APIs. It can easily scale, making it a great choice for public cloud storage.<\/p>\n\n\n\n

    It has static nature and writing objects is a slow process, so does not work well with traditional databases. ( for which cinder works well). S3 from Amazon is a good example of object base storage.<\/p>\n\n\n\n

    Glance (Image Registry)<\/h2>\n\n\n\n

    Glance also provides storage but acts only as an image registry. It keeps track of virtual machines images, metadata such as the kernel, disk images, disk format, etc. This is available to OpenStack users through REST APIs.<\/p>\n\n\n\n

    Heat- Orchestration<\/h2>\n\n\n\n

    Heat manages and automate\/orchestrates entire life cycle of infrastructure that includes servers, IPs, volumes, security groups, users etc.<\/p>\n\n\n\n

    So thats it about the core services in OpenStack; let me know in the comments if you have any comments on this piece and if this cheat sheet helped you or not.<\/p>\n","protected":false},"excerpt":{"rendered":"

    For a while I thought to write about an OpenStack cheat sheet showing OpenStack components, so you can refer to it as an easy to use handy reference. If you are using NFV, you are using OpenStack for sure. OpenStack sits at the VIM layer inside NFV MANO and is the most important piece to […]<\/p>\n","protected":false},"author":2,"featured_media":2294,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-2188","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nfv"],"_links":{"self":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/2188","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2188"}],"version-history":[{"count":2,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/2188\/revisions"}],"predecessor-version":[{"id":3639,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/2188\/revisions\/3639"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/media\/2294"}],"wp:attachment":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}