Shulou(Shulou.com)06/01 Report--

This article is about how to build an OpenStack experimental environment, the editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Before we learn about the OpenStack services, let's set up an experimental environment.

There is no doubt that an OpenStack that can be seen and touched and allows us to mess around casually can improve our learning efficiency.

DevStack's rich options give us the flexibility to select and deploy the OpenStack services we want, which is very suitable for learning and research.

Deployment Topology

First, let's design the deployment topology of OpenStack.

OpenStack is a distributed system consisting of several nodes (Node) with different functions:

The control node (Controller Node) manages the OpenStack, and the services running on it are Keystone, Glance, Horizon, and management-related components in Nova and Neutron. The control node also runs services that support OpenStack, such as SQL databases (usually MySQL), message queues (usually RabbitMQ), and network time service NTP.

The service running on the network node (Network Node) is Neutron. Provide L2 and L3 networks for OpenStack. Including virtual machine network, DHCP, routing, NAT and so on.

The storage node (Storage Node) provides block storage (Cinder) or object storage (Swift) services.

The compute node (Compute Node) runs Hypervisor on it (the default is KVM). Agent running Neutron service at the same time to provide network support for virtual machines.

These types of nodes are logically divided in terms of functions, and can be flexibly configured according to requirements during actual deployment, such as:

In a large-scale OpenStack production environment, each type of node is deployed on several physical servers, performing their own duties and cooperating with each other.

Such an environment has good performance, scalability, and high availability.

In the smallest experimental environment, four types of nodes can be deployed to a physical or even virtual server.

Although the sparrow is well-equipped, it is often referred to as All-in-One deployment.

In our experimental environment, in order to make the topology simple and fully functional, we used two virtual machines:

Devstack-controller: control node + network node + block storage node + compute node

Devstack-compute: compute nod

Physical resource requirements

CPU and memory are for reference.

If you are creating a virtual deployment on your own PC machine, the resources may not be available and can be adjusted appropriately.

Network planning

Three networks are planned on the network:

Management Network: used for internal management of OpenStack, such as communication between services. Eth0 is used here

The network used by virtual machines deployed by VM (Tenant) Network:OpenStack. OpenStack supports multi-tenancy (Tenant). Virtual machines are placed under Tenant, so they are called Tenant Network. Eth2 is used here

External Network: generally speaking, Tenant Network is an internal private network, which is only used for communication between VM and is isolated from other non-VM networks. Here we plan an external network (External Network) that connects through devstak-controller 's eth3. Neutron enables VM to access External Network through L3 services. For public clouds, External Network generally refers to Internet. For the enterprise private cloud, External Network can be a network in Intranet.

The above is how to build the OpenStack experimental environment, the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.