KR102554198B1 - Test bed system and its control method - Google Patents

Abstract

The present invention relates to a test bed system capable of testing an IaaS system based on virtualization technology. More specifically, the present invention is a master node group; first and second worker node groups controlled by the master node group; and a switch group including at least one switch connected to the second worker node group, wherein the nodes included in the master node group and the first and second worker node groups are virtual machines (virtual machines, VM), the second worker node group includes at least one compute node for generating and running at least one virtual machine, and the first worker node group is configured to operate the at least one virtual machine. It relates to a cloud environment-based IaaS development test bed system configured to include at least one controller node.

Description

Test bed system and its control method {TEST BED SYSTEM AND ITS CONTROL METHOD}

The present invention relates to a system based on a virtualized computing infrastructure in a cloud-native environment, and more specifically, by supporting tests capable of developing IaaS (Infrastructure as a service) services, service/product development and testing. It is about a cloud-based computing test development environment (Testbed) system to make it easy to perform.

Cloud is a computer environment in which information is stored semi-permanently on servers on the Internet and temporarily stored on clients such as IT devices such as desktops, tablets, computers, laptops, netbooks, and smartphones. It refers to a computing environment in which data is stored on a server on the computer and this information is available anytime, anywhere through various IT devices. The cloud environment is expanding flexibility by gradually applying virtualization technology from the past physical server-based operation method.

In cloud operation, servers, storage, network resources, etc. are required, and software that can control each resource and further manage and operate them in an integrated manner is required. call

As the cloud computing environment becomes common, many software companies such as Microsoft, Amazon, and VMware are providing commercial cloud OS. However, on the other hand, as the center of gravity is focused on open source, open source cloud operating systems are supported by numerous open source-based software companies such as HP and RedHat.

As the cloud computing environment becomes more common and the development of IaaS services based on this environment becomes more active, the need for a system capable of testing the developed IaaS service in various environments and conditions is increasing.

Accordingly, research on a system that can easily test IaaS services under various environments and conditions is required.

The present invention configures virtual components by utilizing virtual execution elements operating in a cloud environment, and based on this, a network based on a virtualized cloud environment capable of testing various IaaS (Infrastructure-as-a-service) functions and developing new functions. It provides a computing development test bed system.

The present invention provides a cloud environment-based IaaS test bed system that can save a lot of time and money for preparing a new test development environment necessary for developing an IaaS system from the user's point of view.

The present invention provides a cloud environment-based IaaS test bed system that can support multi-tenants and can be easily implemented with only a small number of hardware devices.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

According to one aspect of the present invention to solve the above or other problems, the master node group; first and second worker node groups controlled by the master node group; and a switch group including at least one switch connected to the second worker node group, wherein the nodes included in the master node group and the first and second worker node groups are virtual machines (virtual machines, VM), the second worker node group includes at least one compute node for generating and running at least one virtual machine, and the first worker node group is configured to operate the at least one virtual machine. A cloud environment-based IaaS development test bed system configured to include at least one controller node is provided.

The system may be configured to include first and second PMs (Physical Machines).

The master node group and the first worker node group may be configured to be included in the first PM.

And, the second worker node group may be configured to be included in the second PM.

In addition, the first and second PMs may be connected through a first type network, and the master node group and the first and second worker node groups may be connected through a second type network, which is a container network.

The first type network,

It may include at least one of a wired network directly connected between the first and second PMs and a wireless network logically connected using an encapsulated protocol.

A third type network, which is a management network, may be connected between the first and second worker node groups.

The third type network,

The at least one virtual controller node may be a network used to operate the at least one user virtual machine created in the at least one compute node.

The first component required for the master node group is installed as a first container, the second component required for the first worker node group is installed as a second container, and the second component required for the second worker node group is installed. 3 components can be installed into a 3rd container.

A first component installed based on the first container may manage the second and third containers based on the second type network.

The first component installed based on the eighth container may further manage the first container.

The at least one virtual controller node may perform at least one of creation, modification, and deletion of the at least one virtual machine.

The testbed system is implemented based on the Kubernetes orchestration platform, and the master node group is configured to include a master node of the Kubernetes orchestration platform,

The first and second worker node groups may be configured to include worker nodes of the Kubernetes orchestration platform.

The test bed system,

It may be implemented based on OpenStack, the at least one controller node may be implemented as a controller node of the OpenStack, and the at least one compute node may be implemented as a compute node of the OpenStack.

According to the present invention, by configuring a virtual network using a virtual network device, a verification procedure for setting and operation of various network functional elements is provided, and based on this, it can be used as a tool for developing a new networking service.

In addition, it provides a more comfortable test and development environment through improved performance through the use of container technology compared to virtual machine-based virtual network test tools.

A further scope of the applicability of the present invention will become apparent from the detailed description that follows. However, since various changes and modifications within the spirit and scope of the present invention can be clearly understood by those skilled in the art, it should be understood that the detailed description and specific examples such as preferred embodiments of the present invention are given as examples only.

1 is a diagram illustrating a conventional cloud-based Infrastructure-as-a-Service (IaaS) system 10 configured in a general hardware form.
2 is a diagram showing a block diagram of an IaaS test system 100, which is a virtual test bed system according to an embodiment of the present invention. The virtualized configuration in FIG. 2 is indicated by a dotted line.
3 illustrates a block diagram implemented on at least two PMs of an IaaS test system 100 according to an embodiment of the present invention, according to one embodiment of the present invention.
4 is a diagram illustrating a second type network 410 required for the IaaS test system 100 implemented on at least two PMs 301 and 302 according to an embodiment of the present invention.
5 is a diagram explaining the role of the second type network 410 according to an embodiment of the present invention.
6 is a diagram illustrating a third type network 510 required for the IaaS test system 100 implemented on at least two PMs 301 and 302 according to an embodiment of the present invention.
7 is a diagram illustrating a fourth type network 710 required for the IaaS test system 100 implemented on at least two PMs 301 and 302 according to an embodiment of the present invention.

Hereinafter, the embodiments disclosed in this specification will be described in detail with reference to the accompanying drawings, but the same or similar elements are given the same reference numerals regardless of reference numerals, and redundant description thereof will be omitted. The suffixes "module" and "unit" for components used in the following description are given or used together in consideration of ease of writing the specification, and do not have meanings or roles that are distinct from each other by themselves. In addition, in describing the embodiments disclosed in this specification, if it is determined that a detailed description of a related known technology may obscure the gist of the embodiment disclosed in this specification, the detailed description thereof will be omitted. In addition, the accompanying drawings are only for easy understanding of the embodiments disclosed in this specification, the technical idea disclosed in this specification is not limited by the accompanying drawings, and all changes included in the spirit and technical scope of the present invention , it should be understood to include equivalents or substitutes.

Terms including ordinal numbers, such as first and second, may be used to describe various components, but the components are not limited by the terms. These terms are only used for the purpose of distinguishing one component from another.

It is understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle. It should be. On the other hand, when an element is referred to as “directly connected” or “directly connected” to another element, it should be understood that no other element exists in the middle.

Singular expressions include plural expressions unless the context clearly dictates otherwise.

In this application, terms such as "comprise" or "have" are intended to designate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, but one or more other features It should be understood that the presence or addition of numbers, steps, operations, components, parts, or combinations thereof is not precluded.

In the detailed description of this patent described below, it shows that a test bed is configured to control available resources for processing, storage space, and networking as an example by utilizing an IaaS-type cloud computing open source project called OpenStack. . Accordingly, the present invention is not limited to open source such as OpenStack, and various cloud computing platforms may be applied.

1 is a diagram illustrating a conventional cloud-based Infrastructure-as-a-Service (IaaS) system 10 configured in a general hardware form.

The conventional IaaS system 10 is configured to include at least one controller node 140-1 to 140-3, at least one PM (Physical Machine) 201-1 to 201-4, and a switch group 230. It can be. The IaaS system 10 may be configured based on a cloud management framework. For example, the IaaS system 10 may be configured based on OpenStack.

The PMs 201-1 to 201-4 refer to individual physical servers classified on the basis of hardware. The IaaS service provider may install an appropriate number of PMs 201-1 to 201-4 in the IaaS system 10 for smooth service provision. On this test-based IaaS system 10, each PM is imitated as a virtual machine and functions as a compute node.

A compute node refers to a node that provides compute resources to a virtual machine (VM). That is, the compute node refers to a node where a virtual machine is actually created and operated.

Each of the at least one PM 201-1 to 201-4 may create and manage a virtual machine according to a request of a service user (or service user). A plurality of virtual machines may be created in one PM.

The number of at least one controller node (140-1 to 140-3) may also be appropriately adjusted by the IaaS service provider. That is, the service provider may increase or decrease the number of controller nodes 140-1 to 140-3 as needed.

Each of the controller nodes 140-1 to 140-3 means a node for managing other shared services as well as the controller node itself and the compute node. If the IaaS system is based on OpenStack, each controller node (140-1 to 140-3) plays a role in controlling the overall functions of OpenStack. Controller nodes, for example, manage API services, coordinate requests from components, and serve as the primary interface.

The switch group 230 includes at least one component required for a switch fabric structure. At least one controller node (140-1 to 140-3) controls the switch group 203 constituting the switch fabric structure to connect so that data can be exchanged between virtual machines, or to connect an external network and virtual machines. so that data can be exchanged.

For example, in the IaaS system 10 shown in FIG. 1 , configurations required for a 2-layer leaf-spine fabric are included in the switch group 230 . The two-layer leaf-spine fabric includes a plurality of leaf switches, a plurality of spine switches, and a border leaf switch, and is formed in a hierarchical structure between the plurality of spine switches and the plurality of leaf switches.

In the illustrated example, a two-layer leaf-spine fabric structure is included, but not necessarily limited thereto, and various switch fabric structures may be applied to the IaaS system 10 shown in FIG. 1 .

According to the IaaS system 10 shown in FIG. 1, when a service user requests a virtual resource from a service provider, the service provider assigns an appropriate virtual machine to at least one compute node (first to fourth PMs in the illustrated example). ), and the created virtual machine can be provided for service users to use. That is, by optimizing the physical resources (first to fourth PMs in the illustrated example) of the service provider into virtual resources (virtual machines) to suit the usage purpose of the service user, the optimized virtual resources are used as a service can be provided to the user.

In the case of a service provider, in constructing the IaaS system 10 as shown in FIG. 1, it will be necessary to perform performance experiments for various settings and conditions. In the present invention, prior to constructing the actual IaaS system 10, a virtual test bed system structure capable of performing functional tests of such a system in a virtual space is proposed.

2 is a diagram showing a block diagram of an IaaS test system 100, which is a virtual test bed system according to an embodiment of the present invention. The virtualized configuration in FIG. 2 is indicated by a dotted line.

The IaaS test system 100 according to an embodiment of the present invention includes a master node group 110, first and second worker node groups 140 and 201 controlled by the master node group 110, and the th A switch group 230 including at least one switch connected to the 2 worker node group 201; and a switch controller group 240 for controlling the operation of the switch group 230 .

In particular, the nodes included in the master node group 110 and the first and second worker node groups 140 and 201 are composed of physical equipment in a real environment, not a test bed, but the present invention imitates the real environment Since it is a test bed, it is proposed to be configured as a Virtual Machine (VM).

IaaS is a service that provides virtual resources (for example, virtual machines) to users. When a user makes a request for creating a virtual machine, a virtual machine can be created and started in at least one node included in the second worker node group, which is a compute node group.

That is, a virtual machine requested by a user is created and operated in one node of the second worker node group, which is a compute node group implemented as a virtual machine.

And the first worker node group is configured to include at least one controller node for operating the virtual machines of the at least one user.

Referring to FIG. 2, the IaaS test system 100 according to an embodiment of the present invention includes a master node group 110, a first worker node group 140, a second worker node group 201, and a switch group ( 230) and a switch controller group 240.

The first worker node group 140 includes at least one virtual controller node 140-1' to 140-3'. The second worker node group 201 includes at least one virtual PM 201-1' to 201-4'.

Virtual machines (140-1' to 140-3', hereinafter referred to as virtual controller nodes) virtualizing at least one controller node are at least one controller node 140 in the conventional IaaS system 10 described above in FIG. -1 ~ 140-3) corresponding configuration. That is, a configuration in which at least one controller node (140-1 to 140-3), which is a physically independent configuration, is virtualized on the conventional IaaS system 10 as a virtual controller node (140-1' to 140-3'). can see.

Virtual machines (201-1' to 201-4', hereinafter referred to as virtual PMs) virtualizing at least one PM are at least one PM (201-1 to 201-4') in the conventional IaaS system 10 described above with reference to FIG. 201-4). That is, a configuration obtained by virtualizing at least one PM (201-1 to 201-4), which is a physically independent configuration, on the conventional IaaS system 10 can be regarded as a virtual PM (201-1' to 201-4'). there is.

The virtual PMs 201-1' to 201-4' will also serve as the aforementioned compute nodes. When serving as a compute node, virtual machines to be provided to service users may be created, managed, or deleted on the virtual PMs 201-1' to 201-4'. That is, a virtual machine within a virtual machine may be created by being double virtualized.

In order to distinguish the virtual PMs 201-1' to 201-4' and the virtual machines created therein, in the detailed description of the present invention, the virtual PMs 201-1' to 201-4' are created and In this case, a virtual machine provided to service users is referred to as a 'user virtual machine'.

Among the configurations of FIG. 2 , descriptions of components that perform the same function as those of FIG. 1 are omitted.

The switch controller group 240 includes first to third switch controller nodes 240-1 to 240-3. In the example of FIG. 2 , the number of switch controller nodes 240-1 to 240-3 is shown as three, but the number is not limited to this number and may be increased or decreased.

At least one of the plurality of switch controller nodes 240-1 to 240-3 may operate as a master mode. And, other than the master mode, the others may operate in the standby mode. Network settings are configured on switches in a switch group by a switch controller node operating in master mode. If a switch controller node operating in master mode fails, one of the switch controller nodes in standby mode can take over.

Among the API pods described below, the "Neutron" API, which is represented as a networking service, can be logically connected to a virtual spine switch or a virtual leaf switch through the switch controller. The “Neutron” API may be connected to a switch controller node of a switch controller group through a third type network (described later in FIG. 6), which is a management network. When a network creation/modification/deletion command is generated through the "Neutron" API, the switch controller node (set in master mode) receives the command and transmits the network settings to the related switch.

The IaaS test system 100 according to an embodiment of the present invention proposes to implement physically independent components included in the conventional IaaS system 10 described in FIG. 1 through a virtual machine. That is, for the purpose of testing, physical configurations are replaced with virtual machines. In the example of FIG. 1 , the physically independent components include the first to third controller nodes 140-1 to 140-3, the first to fourth PMs 201-1 to 201-4, and the switch group 230. It may mean at least one of included spine switches, leaf switches, and border leaf switches.

That is, the IaaS test system 100 according to an embodiment of the present invention includes first to third controller nodes 140-1 to 140-3, first to fourth PMs 201-1 to 201-4, At least one of each spine switch, leaf switch, and border leaf switch included in the switch group 230 is implemented as a virtual machine. A configuration implemented as a virtual machine is shown as a dotted line on FIG. 2 .

The first to third controller nodes 140-1 to 140-3 are the first to third virtual controller nodes 140-1' to 140-3' on the IaaS test system 100 according to an embodiment of the present invention. ) is virtualized and implemented.

The first to fourth PMs 201-1 to 201-4 are the first to fourth virtual PMs 201-1' to 201-4' on the IaaS test system 100 according to an embodiment of the present invention. It can be virtualized and implemented. As described above in FIG. 1 , the first to fourth virtual PMs 201-1' to 201-4' on the IaaS test system 100 may function as compute nodes.

Each spine switch may be virtualized and implemented as a virtual spine switch on the IaaS test system 100 according to an embodiment of the present invention.

Each leaf switch is configured on the IaaS test system 100 according to an embodiment of the present invention. It can be implemented by being virtualized as a virtual leased switch.

When physical configurations are replaced with virtual machines according to an embodiment of the present invention, a system for testing is constructed with only a smaller number of configurations than the number of basic hardware required to build an actual IaaS system 10 as shown in FIG. There are advantages to being able to do this.

In the following description of embodiments of the present invention, a system based on OpenStack is described as a representative example for convenience of explanation, but the present invention can be applied to various cloud management frameworks without necessarily being limited to OpenStack. .

In particular, in the case of the IaaS test system 100 according to an embodiment of the present invention, it is proposed to containerize at least one component in a container instead of installing components that must be complexly performed when constructing OpenStack.

Containerization refers to a virtualization method based on virtualization at the operating system level. Containers are characterized as lightweight, portable executables for applications that are isolated from each other or from the host.

Because containers are not tightly coupled to the host hardware computing environment, applications can be linked to container images and run as a single, lightweight package on any host or virtual host that supports the underlying container architecture. Because of these characteristics, containers can solve various problems that can arise when running software in different computing environments.

In addition, since containers are environments in which the operating system is virtualized, they are relatively lightweight compared to virtual machines, so they can support more container instances than existing virtual machines under the same conditions, and can be quickly created and removed. Often short-lived containers can be created and moved more efficiently than virtual machines. And containers can be managed as groups of logically related elements. In some orchestration platforms, for example Kubernetes, these elements are called "pods", and groups of these pods are called "clusters".

Hereinafter, the terms pod and cluster are used in the present invention, but these are only terms to refer to elements and their groups, and the present invention will not be limited to the Kubernetes platform.

A 'pod' can run on a node. A node is a worker machine on an orchestration platform and can be a virtual or physical machine depending on the cluster. Each node is managed by a master node. One node can have multiple pods, and the master node automatically handles scheduling of pods through the nodes in the cluster.

In one embodiment of the present invention, it is proposed to deploy or manage an IaaS test system in the form of a container that can be deployed and managed through an orchestration platform. In this way, using a container-based IaaS test system has the advantage of being able to properly deploy and manage cloud resources according to the request of service users, and creating a test bed environment with only a small number of PMs (about two). will be.

In addition, it is proposed that the controller node and the compute node of the IaaS test system 100 according to an embodiment of the present invention be implemented as worker nodes on an orchestration platform. In addition, the IaaS test system 100 may include a master node 110 to control the worker node.

Nodes where 'pods' are installed are divided into master nodes (or masters) and worker nodes (or workers) according to their roles. The master node plays a role in controlling the entire cluster.

Pods installed and operated on the master node are generally an API server that provides cluster functions in the form of an API, a database that stores cluster data, a scheduler that determines which nodes pods are assigned to, and cluster resources. There may be a controller that manages and allocates, and a Domain Name System (DNS) server. However, pods installed on the master node will not be limited to the listed functions.

Pods installed on worker nodes generally include an agent that executes commands delivered from the API server of the master node, a proxy that manages the network between pods, and a runtime that actually runs the pods. However, pods installed on worker nodes will not be limited to the listed functions.

Service API pods running on worker nodes are pods that run OpenStack API servers such as "Nova", "Neutron", "Keystone", "Cinder", "Glance", "Horizon", and "Octavia". Using the aforementioned OpenStack API is just one example, and it will be apparent that other APIs performing the same function can be substituted. For example, "Neutron" is an API for networking control, and it is obvious that other networking control APIs can be applied instead of "Neutron".

The first to third virtual controller nodes 140-1' to 140-3' are included in the first worker node group 140, and the first to third virtual controller nodes 140-1' to 140-3' ) Each operates as one worker node.

Similarly, the first to fourth virtual PMs 201-1' to 201-4' according to an embodiment of the present invention are included in the second worker node group 201, and the first to fourth virtual PMs 201-4' 1' to 201-4') can each operate as one worker node.

The first to third virtual controller nodes 140-1′ to 140-3′ and the first to fourth virtual PMs 201-3, which are worker nodes included in the first and second worker node groups 140 and 201, 1' to 201-4') can be controlled by virtual master nodes 110-1 to 110-3. For example, the virtual master nodes 110-1 to 110-3 may perform monitoring, scheduling, or management of containers included in the first and second worker node groups 140 and 201.

Meanwhile, in one embodiment of the present invention, it is proposed that the above-described virtual machines be implemented on at least two PMs.

3 illustrates a block diagram implemented on at least two PMs of an IaaS test system 100 according to an embodiment of the present invention, according to one embodiment of the present invention.

According to the illustrated diagram, the master node group 110 and the first worker node group 140 are configured on the first PM 301 . A switch group 230 and a second worker node group 201 are configured on the second PM 302 .

The first PM 301 and the second PM 302 are connected to each other based on a first type network 310 .

The first type network 310 includes a wireless connection network to which the first PM 301 and the second PM 302 are directly connected. In addition, the first type network 310 may include an encrypted virtual private network (VPN), for example, a 'wireguard' protocol. That is, various networks that can be logically connected using an encapsulated protocol such as VXLAN may be included in the first type network 310 .

The first PM 301 and the second PM 302 presented in this patent will not necessarily be limited to being configured as physical machines.

The first PM 301 and the second PM 302 presented in this patent may also be configured as virtual machines (VMs), and the virtual machines may be configured and connected to the first type network 310, In this case, the first type network 310 may use a tunneling protocol for logical connection.

Therefore, if the first PM 301 and the second PM 302 are composed of virtual machines, the test bed proposed in this patent can be operated on a cloud (AWS or GCP) where virtual machines are provided.

Referring to FIGS. 4 to 6 , network connections required for the IaaS test system 100 to be implemented on at least two PMs 301 and 302 according to an embodiment of the present invention will be described.

4 is a diagram illustrating a second type network 410 required for the IaaS test system 100 implemented on at least two PMs 301 and 302 according to an embodiment of the present invention.

The second type network 410 shown in FIG. 4 means a network for exchanging data between containers. For example, it can be a network for exchanging data between Kubernetes containers, an orchestration platform.

In FIG. 4, the first to third virtual master nodes 110-1 to 110-3 belonging to the master node group 110 are worker nodes, and the first to third virtual controller nodes 140-1' to 140-3 ') or the first to fourth virtual PMs 201-1' to 201-4', the second type network 410 may be used.

For example, the second type network 410 is used to create, maintain, and manage a container in which at least one master node 110-1 to 110-3 is installed in the first worker node group 140. available.

Hereinafter, a more specific role of the second type network 410 will be described with reference to FIG. 5 .

5 is a diagram explaining the role of the second type network 410 according to an embodiment of the present invention.

When using an orchestration platform (eg Kubernetes), containerized and installed components that need to be installed on at least one virtual controller node (140-1' to 140-3') or at least one compute node described above , management, etc.

A component means a set of functions required by at least one virtual controller node (140-1' to 140-3') or at least one compute node. For example, in the case of OpenStack, there may be 'Nova' in charge of compute function and 'Neutron' in charge of networking function.

The above-mentioned 'Nova' or 'Neutron' is just one example, and will not necessarily be limited to components having these names. That is, it is obvious that other types or types of components responsible for networking functions can be applied to the present invention instead of 'Neutron'.

Table 1 below shows an example of components for OpenStack.

turn Component name explanation One Compute Compute is the main part of the IaaS system, the cloud computing fabric controller. It is designed to manage and automate pools of computer resources and can work with widely available virtualization technologies as well as bare metal, high-performance computing (HPC) configurations.
As a hypervisor technology (virtual machine monitor), you have a choice of KVM, VMware, or Xen, which can be used in conjunction with Linux container technologies such as Hyper-V and LXC. In OpenStack, Nova is responsible for that function. 2 Networking Networking (Neutron) A system for managing networks and IP addresses. OpenStack Networking ensures that the network is not bottlenecked, and even provides self-service capabilities to users through network configuration. Networking provides a networking model for different applications or groups of users. Most basically, it includes a VLAN/VXLAN network that logically separates the network by supporting flat or multi-tenant corresponding to a single tenant. Networking manages IP addresses, allowing for dedicated static IP addresses or DHCP. Floating IP addresses allow traffic to be dynamically routed to any resource within the IT infrastructure, allowing users to redirect traffic in the event of maintenance or failure. In OpenStack, Neutron is in charge of that function. 3 Block Storage Block storage provides persistent block-level storage devices for use with compute instances. The block storage system manages the creation, attachment, and removal of block devices to servers. In OpenStack, Cinder is responsible for that function. 4 Identity Identity provides a central directory of users that are mapped to the services they can access. It acts as a common authentication system through cloud operating systems and can integrate with existing backend directory services such as LDAP.
In OpenStack, Keystone is responsible for that function. 5 Image Image provides discovery, registration, and distribution services for disk and server images. Saved images can be used as templates. It can also be used to store and catalog an unlimited number of backup copies. Image services can store disk and server images on various backends. The Image Service API provides a standard REST interface for querying information about disk images and allows clients to stream images to a new server.
In OpenStack, Glance is responsible for that function. 6 Dashboard The dashboard provides administrators and users a graphical interface for accessing, provisioning, and automating cloud-based resource deployment. The design accommodates third-party products and services such as billing, monitoring, and additional management tools.
In OpenStack, Horizon is responsible for that function. 7 Provisioning Provisioning is a service that prepares a bare metal machine instead of a virtual machine. You can think of it as a bare metal hypervisor API and a collection of plug-ins that interact with the bare metal hypervisor. Basically, it uses PXE and IPMI to reserve and turn on/off machines, but vendor-specific plug-ins can be supported and extended to implement additional functions.
In OpenStack, Ironic is responsible for that function.

Referring to FIG. 5 , components required for the master node group 110 may be created, managed, and deleted in the form of a first container 501-1.

Similarly, components required for the first worker node group 140 can be created, managed, and deleted in the form of the second container 501-2.

In addition, components required for the second worker node group 201 can be created, managed, and deleted in the form of a third container 501-3.

The above-described second type network 510 is used so that at least one master node belonging to the master node group 110 manages the above-described first to third containers 501-1 to 501-3. That is, the second type network 510 is used to exchange data between the container(s) 501-1 to 501-3.

6 is a diagram illustrating a third type network 510 required for the IaaS test system 100 implemented on at least two PMs 301 and 302 according to an embodiment of the present invention.

The third type network 510 described in FIG. 6 refers to a network required when an administrator controls or controls each other between OpenStack components (between a controller node and a compute node).

In an embodiment of the present invention, the third type network 510 may serve as a 'manage network'. A 'manage network' is a network in which all nodes existing in the first and second PMs 301 and 302 are connected and control traffic flows therebetween. It may refer to a network for managing (setting) virtual machine(s) created in at least one compute node.

In a real environment, access to at least one virtual PM (201-1' ~ 201-4') or user virtual machine to check settings, enter configuration parameters, or send and receive data between the OpenStack controller and the computer. Type network 510 is used.

In addition, the third type network 510 is used to transfer data between the controller node and the switch and between the switch controller and the switch.

7 is a diagram illustrating a fourth type network 710 required for the IaaS test system 100 implemented on at least two PMs 301 and 302 according to an embodiment of the present invention.

The fourth type network 710 may be a network for communication between user virtual machines created in the second worker node group 201 or for external communication with a user virtual machine.

The configuration of the switch group shown in FIG. 7 is composed of a Leaf switch and a Spine switch, and a connection setting is configured with VXLAN-EVPN, but this is an example and is not limited to this configuration.

In the fourth type network 710 , traffic may move from a leaf switch to a spine switch to a leaf switch along a switch fabric structure in order to communicate between a first user virtual machine and a second user virtual machine.

Connection 710-1 between at least one virtual leaf switch and at least one virtual PM 201-1' to 201-4', as well as connection 710 between at least one virtual leaf switch and at least one virtual spine switch -2) may be made of the fourth type network 710 .

For example, settings for the fourth type network 710 can be made by the above-described Neutron API of OpenStack. The Neutron API can be performed through the switch controllers 240-1 to 240-3 included in the aforementioned switch controller group in order to control switch configurations included in the switch group or apply settings. That is, in order to establish a connection between the first user virtual machine and the second user virtual machine, the Neutron API may control the switch controller (240-1 in the example of FIG. 2) set to the master mode.

Initially, when there is no user virtual machine, there is no network setting. When the user virtual machine is created, VLAN information, IP information, port information, etc. corresponding to the created user virtual machine may be registered in the virtual leaf switch.

Above, the embodiment of the IaaS test system 100 according to the present invention has been described, but this is described as at least one embodiment, and thereby the technical spirit of the present invention and its configuration and operation are not limited. The scope of the technical idea of the invention is not limited / limited by the drawings or the description referring to the drawings. In addition, the concepts and embodiments of the present invention presented in the present invention can be used by those skilled in the art as a basis for modifying or designing other structures to achieve the same purpose of the present invention. , Modified or changed equivalent structure by a person of ordinary skill in the art to which the present invention belongs is bound by the technical scope of the present invention described in the claims, and does not depart from the spirit or scope of the invention described in the claims. Various changes, substitutions and modifications are possible within the limits.

Claims (12)

In the IaaS development test bed system configured to include the first and second PMs (Physical Machines),
master node group;
first and second worker node groups controlled by the master node group; and
A switch group including at least one switch connected to the second worker node group,
The master node group and the first worker node group are configured to be included in the first PM,
The second worker node group is configured to be included in the second PM,
Nodes included in the master node group and the first and second worker node groups are composed of virtual machines (VMs),
The second worker node group includes at least one compute node that creates and runs at least one user virtual machine,
The first worker node group includes at least one controller node for operating the at least one user virtual machine,
The first and second PMs are connected to a first type network;
The master node group and the first and second worker node groups are configured to be connected by a second type network,
wherein the first and second type networks are networks of different types;
Cloud environment based IaaS development test bed system.
delete delete According to claim 1,
The first type network,
At least one of a wired network directly connected between the first and second PMs and a wireless network logically connected using an encapsulated protocol,
Cloud environment based IaaS development test bed system.
According to claim 1,
A third type network is connected between the first and second worker node groups,
Cloud environment based IaaS development test bed system.
According to claim 5,
The third type network,
The at least one virtual controller node is a network used to operate the at least one user virtual machine created in the at least one compute node.
Cloud environment based IaaS development test bed system.
According to claim 1,
The first component required for the master node group is installed as a first container, the second component required for the first worker node group is installed as a second container, and the second component required for the second worker node group is installed. 3 components are installed into the 3rd container,
Cloud environment based IaaS development test bed system.
According to claim 7,
A first component installed based on the first container manages the second and third containers based on the second type network.
Cloud environment based IaaS development test bed system.
According to claim 8,
The first component installed based on the first container further manages the first container,
Cloud environment based IaaS development test bed system.
According to claim 1,
The at least one virtual controller node performs at least one of creation, modification, and deletion of the at least one virtual machine,
Cloud environment based IaaS development test bed system.
According to claim 1,
The test bed system,
Implemented on top of the Kubernetes orchestration platform,
The master node group is configured to include a master node of the Kubernetes orchestration platform,
The first and second worker node groups are configured to include worker nodes of the Kubernetes orchestration platform,
Cloud environment based IaaS development test bed system.
According to claim 11,
The test bed system,
It is implemented based on OpenStack,
The at least one controller node is implemented as a controller node of the OpenStack,
Characterized in that the at least one compute node is implemented as a compute node of the OpenStack,
Cloud environment based IaaS development test bed system.

Images