Introduction to OpenStack, Why and deployment models of OpenStack.

Introduction to OpenStack, Why and deployment models of OpenStack.

OpenStack is a type of cloud service that is included in the category of infrastructure and service that makes the site open. Gives you all the components to configure your cloud infrastructure. It provides you with a set of tools and different components and services, It was created in 2010 by Rackspace. It is a large cloud hosting company and NASA. the open side community is really huge, there are contributors like the Giants in the world of technology. Everyone is contributing to it such as IBM, VMware, Red Hat, Dell, HP and Cisco. Each one of them is in the community. They contribute almost occasionally to develop it. The best part of it is that it is open source. You can get it for free and you can modify anything you need depending on the infrastructure you want to create.

Click on this website for more details- https://www.cloudologic.com/post/introduction-anddeployment-models-of-openstack It is the future of cloud computing because it is backed by the giant technology giants in the current era. So what can you to make it an infrastructure as a service type of a cloud service and can you really add and run instances in it? You want if you can configure different types of nodes for different purposes. Let's say you can build all your infrastructure, if you need some kind of instances in the development environment. You need a large test environment and you want the instances to run in each type of environment. You can configure everything in it. It also provides a platform as an infrastructure service in the end, what it will take advantage of is that it will give you a platform on which you can really build your own application and your infrastructure.

Why OpenStack?

Control Flexible architecture and vibrant ecosystem allow you to customize the platform for your business needs and control your own destiny. The modular design allows you to integrate third-party technologies, so you don't have to extract and replace your existing infrastructure and you can continue using your favorite tool. You can directly influence the roadmap through the open design process and a strong user community.

Click on this website for more details- https://www.cloudologic.com/post/introduction-anddeployment-models-of-openstack Agility It is self-service dashboard and rapid resource provisioning support internal engineering equipment, agile business processes and faster product delivery. Get operational efficiency and a competitive advantage by optimizing your infrastructure on the OpenStack cloud platform.

Cost savings With expensive and complex licensing schemes, some programs force you to make architectural decisions just to contain the licensing costs. The software is freely available under the Apache 2 license, which means you have the freedom to use this, according to your unique requirements, either from free open source repositories or with a turnkey business

solution. Many companies in the ecosystem offer professional services to provide experience regardless of the path you choose.

Ecosystem.

More than 400 leading technology companies worldwide are developing and building tools for it. With so many options in the commercial ecosystem, it is never blocked by a supplier.

So now let's move on to the cloud deployment models you can have with it.

There are 5 kind of deployment models.

1 The first is in the distribution of permits now, since the name says on the premises means that your data center is in your company. They are your servers and then you can design a layer over your data centers. That is what it means that we have a public cloud based on it and a private cloud hosted on it in the third. You can make your infrastructure public or private or it can even be a hybrid cloud. Which is a part of this is public and another part is private. As it is based on services and devices. The first is local distribution, so what happens here is that your data centers are located in your own company in your own facilities and, sometimes, they are also known as local. So this means the same thing that prem means here, the facilities for your data centers to be there, so just download and install all OpenStack services on your own to create that cloud infrastructure. These reside only in your internal network. So this is basically a DIY, a DIY cloud infrastructure. So you only have your data centers, just download the software, install all the services, put them into operation and then you have your OpenStack cloud infrastructure.

2 The next model is a public cloud based on OpenStack, so what happens here is that a provider provides a public cloud computing system based on the OpenStack project.

Therefore, there is a cloud provider that is responsible for creating the infrastructure and designing all the services it needs so that it only goes to the provider to which it requests

some services and it provides all the services and all the data. Everything is stored on your servers in the service of the cloud provider. So this is a very good example of a public cloud that is AWS, but if you want it at night, let's say it is based on OpenStack so you can ask your cloud provider or Intel provider what kind of services really You need to design your application or for your project your cloud will handle better and provide all the services.

3 The following is a private OpenStack cloud hosted. Let's say you have some confidential data that you want to keep, that you don't want to expose to an outside world, or that you can't rely on other people's servers to store your data. Therefore, you can ask a cloud provider to design all the services for you in your internal network on your hardware and all administration will be done by the cloud provider. Actually, the person received all the opposite services for you, so that it will be done for them, will be fully compatible with them and they will only charge you for the support. If something goes wrong, otherwise, the other data and the application that you will actually implement in the infrastructure will be handled by you.

Click on this website for more details- https://www.cloudologic.com/post/introduction-anddeployment-models-of-openstack 4 The following is OpenStack as a service, so in this type of implementation model. Your service provider will install OpenStack on your system. In reality, they will have all the services established in their own cloud and if you want to take advantage of any type of services. Let's say you want the computer service for the development of your application. So you can only request service from your trunk provider. That offers OpenStack services to be charged for the services it provides.

5 Finally in OpenStack there is a final implementation model. Suppose there is a cloud provider called a nebula and they are selling devices and the devices are software that does not require our operating system to work. So this can be a service that is like a plug-in service that you can take advantage of when you really buy the service or that plug-in service. Which is known as a device and you can use it in your implementation or in your infrastructure that you just configured.