KR102524126B1 - Apparatus for providing design and deployment of distributed cloud system for establishing 5G infra and method thereof - Google Patents

Abstract

Disclosed is an apparatus and method in which a central cloud device provides design and installation of an edge cloud device in a distributed cloud system for building a 5G infrastructure. A central cloud device running a cloud manager that manages design, distribution, and installation of edge cloud infrastructure, the cloud manager comprising: a design registration unit receiving design information of edge cloud infrastructure; Template generation unit for generating an installation template according to the registered design information; When an installation request is received, an installation image generator for generating an installation image according to a corresponding template; A manager agent installation unit for installing a manager agent for installation and management of edge cloud infrastructure on an edge cloud device; and an installation information transmission unit that transmits installation information including a template for installing edge cloud infrastructure and an installation image to a manager agent.

Description

Apparatus for providing design and deployment of distributed cloud system for establishing 5G infra and method thereof}

The present invention is a technology for constructing a distributed cloud system, and more specifically, by designing and creating infrastructure optimized for services, characteristics, requirements, etc. required for a distributed cloud system, and distributing the created infrastructure to a distributed cloud system, Apparatus and method for providing automatic build.

Recently, standardization of 5G networks is progressing, and commercialization is about to begin. The 5G network accommodates services that can satisfy requirements such as high performance (Peak 20Gbps), low latency (1ms), and high computing (GPU) as well as current communication. There is a limit to supporting services that are sensitive to traffic response and delay. In order to solve this problem, network devices must be built in the form of NFC (Near Field Communication) based cloud infrastructure.

The actual construction of the cloud infrastructure will be a distributed deployment structure with a central cloud and multiple edge clouds. Accordingly, the need for distributed cloud infrastructure design and automatic installation technology to accommodate various 5G services in an optimized cloud infrastructure is increasing. Here, the distributed cloud infrastructure refers to an integrated HW and SW infrastructure for constructing a distributed cloud device.

Currently, in the case of most NFV (Network Function Virtualization) vendor products, even if the service is the same, each vendor's VNF (Virtual Network Function) has different requirements (number of interfaces, computing resource requirements, etc.). / Logical structure (the number of NICs (Network Interface Cards) in the physical server, and performance enhancement technologies (SR-IOV, DPDK, PCI-PassThrough, etc.) must be different. In other words, a standardized infrastructure is required to optimally accommodate various services. Independent cloud infrastructure must be provided for each service to satisfy the characteristics of each vendor's NFV or IT service.

For example, comparing the vEPC requirements of each vendor, each vendor has different requirements even though they are NFVs that provide the same vEPC service. Since each vendor has different NFV implementation element technologies and service structures, such as network structure, cloud platform, virtualization infrastructure manager (VIM), version, virtual network, and VNF deployment, each cloud infrastructure optimized for each NFV service must be built, and independent infrastructure service must be accepted.

However, current cloud platform vendors do not provide optimized infrastructure and cloud platforms for each service as above.

As can be seen from the conventional cloud installation procedure of FIG. 1 , most cloud platform vendors provide an automatic installation function, but provide a standardized cloud installation that does not consider service characteristics. By the automatic installation function, automatic installation of the standardized cloud proceeds (S100). After the automatic installation of the cloud, manual installation of infrastructure that requires optimization work is necessarily accompanied by server-specific requirements and service requirements (S110). After automatic installation of the cloud infrastructure with default settings applied, the administrator manually optimizes the service requirements to satisfy the service requirements, so agility and accuracy in accepting a specific service is reduced.

In addition, the cloud infrastructure structure is very complicated to quickly provide infrastructure suitable for the characteristics of each service while building the cloud infrastructure according to the existing cloud installation procedure. By bringing the infrastructure structure suitable for the characteristics of each service and at the same time bringing the cloud infrastructure's dual (or triple) structure for infrastructure stability, the hardware/software to be installed and set increases and the structure becomes more complex. . Due to the complexity of the structure and the increase in the number of installation targets, parameters not provided by existing installation templates or functions/settings not guaranteed by the cloud platform provider are manually installed through a cloud installation specialist or vendor after basic cloud installation. can only be set to

Referring to FIG. 2, in the case of a compute server 200 using an Open Virtual Switch (OVS), a service 221 and an interwork network 222 through which a Virtual Machine (VM) 211 can communicate according to service characteristics ), active/active bonding (231) considering infrastructure stability, storage switch (243) and server interface for object storage according to service requirements, SAN switch (244) and HBA card for block storage is designed to use In addition, in order to support the structure of Active/Active bonding 231, the service switch 241 and the interwork switch 242 accommodating each port are configured as MLAGs, and LACP for each port must be set. In order to provide an agile cloud infrastructure, the server 200, switches 241 to 244, and storage should all be able to be automatically configured, but automation technologies currently supported by vendors do not fully support this. In particular, most vendors do not support settings for the switches 241 to 244 at all.

Korean Patent Publication 2017-0052446 (2017.05.12.)

An object of the present invention is to exclude manual installation and setting according to the configuration environment and service characteristics of the edge cloud infrastructure in the structure design and system deployment of distributed cloud for building 5G infrastructure, improve the accuracy and agility of the installation, It is to provide a device and method for accommodating and providing 5G services to an edge cloud infrastructure optimized for requirements.

According to an aspect, a central cloud device running a cloud manager managing design, distribution, and installation of an edge cloud infrastructure, the cloud manager comprising: a design registration unit receiving design information of an edge cloud infrastructure; Template generation unit for generating an installation template according to the registered design information; When an installation request is received, an installation image generator for generating an installation image according to the corresponding template; a manager agent installation unit for installing a manager agent for installation and management of the edge cloud infrastructure in an edge cloud device; and an installation information transmitter configured to transmit installation information including the template for installing the edge cloud infrastructure and the installation image to the manager agent.

The central client device is provided with a web server that registers design, installation, and installation state request information as the design information based on the web page.

The design registration unit provides hardware and software object information constituting the edge cloud infrastructure, and receives environment information and setting information of software objects corresponding to each hardware object as the design information.

The template generation unit refers to the design information including software package information corresponding to each hardware device including racks, servers, and switches, creates each template corresponding to the type information for each referenced device, and The installation template integrated with the execution script is created and stored.

The cloud manager receives registration information of a provisioning network for installation communication and an Intelligent Platform Management Interface (IPMI) network for remote control from the edge cloud device on which hardware infrastructure is installed, communicates installation data based on the registered provisioning network, and Based on the IPMI network, the edge cloud device is remotely controlled to install the manager agent and cloud infrastructure.

The installation image creation unit creates a temporary VM (Virtual Machine) for installation using a basic image of the operating system of the edge cloud device, and generates an image of a software package according to the template in which hardware infrastructure information installed in the edge cloud device is reflected. A script of installation information is executed and added to the VM, and the installation image is created and stored with a disk file remaining after the VM is deleted.

The manager agent installation unit refers to the address information in the template information, remotely accesses the edge cloud device, turns on the power, transmits the agent installation image, installs the agent in the edge cloud device, and Set network communication and address in

The central client device may further include a status checking unit for receiving and confirming an installation progress status of the edge cloud infrastructure from the manager agent.

In the central client device, the design registration unit receives a request for an additional design of the pre-built edge cloud device, the template creation unit creates an installation template according to the additional design information, the installation image creation unit receives an additional installation request, An installation image is created according to the corresponding template, and the installation information transmitter transmits additional installation information including the created template and image to the manager agent.

According to another aspect, in the edge cloud device receiving, installing, and executing a manager agent for installing and managing edge cloud infrastructure from a central cloud device, the manager agent is executed by the installed manager agent, the central cloud device. a receiving unit receiving installation information of the edge cloud infrastructure from; a parsing unit that analyzes the received installation information and parses template information; a preparation unit preparing for installation by checking whether hardware resources exist and software resources can be installed according to the installation information; and an installation unit that installs the edge cloud infrastructure by using the template and installation image of the installation information when it is confirmed as normal.

In the edge client device, each hardware device including a rack, a server, and a switch is installed, and a network for installation management and remote management with the central client device is set for creation of the installation image and installation of the agent. Afterwards, the edge cloud device characterized in that for registration by transmitting management information including the address and account of each of the installed hardware to the central client device.

The preparation unit checks data for each device including a server and a switch to see if the infrastructure information defined in the template is real, sets network and address information to receive a report on the installation progress from the checked device, and returns the set information. Perform a ping test with the identified devices to confirm existence.

The installation unit sets the network and virtual LAN information of the switch using the information of the template, installs a server based on the set information, sets an address to the installed server, boots the server with the installation image, and , A ping test is performed between each device including the installed switch and address, and if the ping test is successful, the software package is executed for each device to complete the installation.

According to another aspect, a method for a central cloud device to execute a cloud manager to manage design, distribution, and installation of an edge cloud infrastructure, comprising: receiving design information of the edge cloud infrastructure; Generating an installation template according to the registered design information; generating an installation image according to the corresponding template when an installation request is received; Installing a manager agent for installation and management of the edge cloud infrastructure in an edge cloud device; and transmitting installation information including the template for installing the edge cloud infrastructure and the installation image to the manager agent.

According to another aspect, a method of installing an edge cloud infrastructure by executing a manager agent by an edge cloud device includes receiving installation information of the edge cloud infrastructure from the central cloud device; Parsing template information by analyzing the received installation information; Preparing for installation by confirming whether hardware resources exist and software resources can be installed according to the installation information; and if it is confirmed as normal, installing the edge cloud infrastructure using the template and installation image of the installation information.

According to one aspect of the present invention, the central cloud manager provides a method for designing and installing an edge cloud, quickly and accurately automatically installs cloud infrastructure optimized for the unique requirements of an edge cloud, and eliminates manual setting by an administrator. , in preparation for existing installations, time and cost efficiency and system stability can be improved and differentiated customer service can be provided.

For the automatic installation, the cloud manager registers a provisioning network for data communication for installation and an IPMI network for data communication for remote control from an edge cloud device on which hardware infrastructure installation is completed, and communicates installation data based on the registered network. , remote control installation including power management and network booting.

In order to eliminate the administrator's manual setting, the cloud manager creates a VM, installs a basic image and a software package image by executing a script, creates an installation image with a disk file from which the VM is deleted, and the manager agent creates an installation image. to automatically install the cloud infrastructure.

In addition, if an additional service is required for an edge cloud device where cloud services are provided after the cloud infrastructure installation is completed, it flexibly provides cloud infrastructure design, deployment, and installation processing optimized for the added service to meet the requirements. We can provide customized automated installation services.

The following drawings attached to this specification illustrate preferred embodiments of the present invention, and together with the detailed description of the present invention serve to further understand the technical idea of the present invention, the present invention is the details described in such drawings should not be construed as limited to
1 is a schematic flowchart of a procedure of installing a conventional cloud system.
2 is a schematic structural diagram of a cloud server using an OVS requiring a conventional manual setting.
3 is a schematic structural diagram of a cloud system according to an embodiment of the present invention.
4 is a schematic configuration diagram of the cloud manager of FIG. 3 .
5 is a schematic configuration diagram of the manager agent of FIG. 4 .
6a and 6b are schematic configuration diagrams for installing an installer in the system of FIG. 3 .
7 and 8 are exemplary views of a user UI in which the cloud manager of FIG. 3 designs an edge cloud infrastructure.
9 is a schematic flowchart for designing, deploying, and installing an edge cloud infrastructure according to an embodiment of the present invention.
FIG. 10 is a schematic flowchart of generating an installation template of cloud infrastructure in FIG. 9 .
11 is a schematic flowchart of installing hardware in an edge cloud device for installation of cloud infrastructure in FIG. 9 .
12 is a schematic flowchart of generating an installation image of the cloud infrastructure in FIG. 9 .
13 is a schematic flowchart of installing a manager agent in the edge cloud device in FIG. 9 .
14 is a schematic flowchart in which the manager agent installed in step 13 installs cloud infrastructure.
FIG. 15 is a schematic flowchart in which the manager agent in FIG. 14 checks the infrastructure of the edge cloud device for cloud infrastructure installation.
16 is a schematic flowchart of the manager agent in FIG. 14 installing cloud infrastructure in the edge cloud device.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, the terms or words used in this specification and claims should not be construed as being limited to ordinary or dictionary meanings, and the inventors use the concept of terms appropriately to describe their invention in the best way. It should be interpreted as a meaning and concept consistent with the technical idea of the present invention based on the principle that it can be defined. Therefore, the embodiments described in this specification and the configurations shown in the drawings are only one of the most preferred embodiments of the present invention and do not represent all of the technical spirit of the present invention. It should be understood that there may be equivalents and variations.

3 is a schematic structural diagram of a distributed cloud system 300 according to an embodiment of the present invention.

The distributed cloud system 300 includes a central cloud device 310 and a plurality of edge cloud devices 330 . The central cloud device 310 and the edge cloud device 330 correspond to computing server devices for providing cloud services.

The central cloud device 310 executes the cloud manager 311, and the executed cloud manager manages cloud installation of the edge cloud device 300.

The edge cloud device 330 executes the cloud manager agent 331, and the executed manager agent 331 receives the installation installer corresponding to the installation file from the cloud manager 311, installs the edge cloud infrastructure, and installs The process is reported to the cloud manager 311.

In the present invention, the cloud manager 311 receives design information suitable for hardware, software, and service environments of the edge cloud device 330 from the manager, creates the installation installer according to the registered design information, and creates the installation The installer is sent to the manager agent 331. Then, the manager agent 331 executes the installation installer to automatically perform installation and setting tasks to suit the resource environment of the edge cloud device 330 . Here, the manual work of setting the service characteristics and execution environment previously performed by an administrator after cloud installation is eliminated by the installation installer, saving time and money and building a stable system 300 .

FIG. 4 is a schematic configuration diagram of the cloud manager 311 of FIG. 3 .

The cloud manager 311 according to an embodiment of the present invention includes a design registration unit 411, a template generator 413, an installation image generator 415, an agent installation unit 417, and an installation information transmission unit 419. consists of including

The design registration unit 411 receives design information of the edge cloud infrastructure from a manager. The design information includes various hardware and software resources constituting the edge cloud device 330, service characteristics, environment information, and the like. By pre-designing the infrastructure information, the manual work of the administrator after the automatic installation of the installer can be eliminated.

The template generator 413 creates a template based on registered design information. The created template corresponds to an aggregate of information referred to for installing the edge cloud device 3 .

The installation image generating unit 415 creates images of various software packages required to be installed according to set information of the template. A process of storing the created image in the edge cloud device 330 is a process of installing the edge cloud infrastructure.

Here, the image creation unit 415 creates a temporary VM for installation so that the installation image is installed as it is in the edge cloud device 330 and the manual setting operation of the administrator is excluded, and the basic image and the image of the software package are created in the VM. and delete the VM. The disk file of the deleted VM is created as the installation image.

The manager agent installation unit 417 transmits the installation file of the manager agent 331 to the edge cloud device 3 and installs the manager agent 331 in the edge cloud device 3 .

The installation information transmitter 419 creates an installer of installation information including a template and an installation image to the edge manager agent 331 installed in the edge cloud device 3, and transmits the created installer.

FIG. 5 is a schematic configuration diagram of the manager agent 331 of FIG. 4 .

The manager agent 331 according to an embodiment of the present invention includes an installation information receiving unit 531, a parsing unit 533, a preparation unit 535, and an installation unit 537.

The installation information receiver 531 receives the installer as installation information of the edge cloud infrastructure from the cloud manager 311 . The manager agent 331 stores installer information in a repository and database.

The parsing unit 533 parses and analyzes installation information in the storage and database.

The preparation unit 535 checks whether the hardware resources included in the installation information exist and whether software resources can be installed.

When it is confirmed that the check of the resource is normal, the installer 537 installs the edge cloud infrastructure by using the template and the installation image of the installation information.

6A and 6B are schematic configuration diagrams for installing an installer in the system 300 of FIG. 3 .

Referring to FIG. 6A , the central cloud device 310 further includes a web server 614 and a status checking unit 625 in addition to the configuration of the cloud manager 311 of FIG. 4 .

The web server 614 registers design request, installation request, and installation status request information of the manager based on user experiences of design user experience (UX) 611, installation UX 612, and status UX 613. . That is, the administrator may register information related to the design, installation, and installation state of the cloud infrastructure using the web page provided from the web server 614 . Meanwhile, the cloud manager 311 may upload or receive hardware unit data, component data and system data of the edge cloud as design information.

The design registration unit 411 registers the design information by providing the manager with information required to generate the design information. The template generator 413 parses registered design information to create a template, and the image generator 415 creates an installation image of a software package according to the template information. The created templates, installation images and installation scripts are stored in the repository 623 .

The installation information transmission unit 419 identifies installation resources by referring to design information of templates, images, and scripts stored in the storage 623, and when the resources are identified, the design information is parsed and an installer installation file is created (build). ), and transmits the generated installer to the manager agent 331 for installation.

Referring to FIG. 6B , the edge cloud device 330 is configured to further include a storage 641 , a database 642 , and a status transmission unit 651 in the manager agent 331 shown in FIG. 5 .

The storage 641 stores information of the storage 623 received by the manager agent 331 from the cloud manager 311 . In addition, the DB 642 stores template and image information stored in the storage 623 .

The parsing unit 533 parses the information stored in the storage 641 and the DB 642, the preparation unit 537 checks the existence and validity of resources according to the parsed information, and the installation unit 537 checks. Install the cloud infrastructure according to the provided information.

The status transmitter 651 checks the status of the installation process and transmits status information to the status check unit 624 . The status checking unit 625 may receive status information and record it as log information. If an installation error occurs during the installation process, the error information is recorded as log information, and the administrator redesigns the design unit 622 by referring to the recorded error information.

7 and 8 are exemplary views of a user UI in which the cloud manager 311 of FIG. 3 designs an edge cloud infrastructure.

Referring to FIG. 7 , each element of the physical infrastructure, software package, and logical infrastructure necessary for the cloud infrastructure is managed as a pool, and a cloud infrastructure design UI 700 is provided in a drag-and-drop format. The administrator selects the object 710 constituting the infrastructure and adds it to the configuration items of the cloud infrastructure 730 by drag and drop. Necessary devices (eg, racks, servers, and switches) are placed in the cloud infrastructure 730, and each object 710, such as computing technology, network information, and cloud logic information, required for each device is set.

Referring to FIG. 8 , when an input for detailed settings for each device object (eg, server, switch, NIC, etc.) 710 is required, a design UI 800 for inputting detailed settings for the object 710 is provided. .

Here, when infrastructure settings such as each server or switch are completed and the design data is saved, the cloud manager 311 extracts the data in json format and creates an installation template for each server and switch through parsing of the json data. can Unlike the existing standardized cloud installation, the cloud manager 311 graphically inputs/manages setting and installation information for each server and switch and automatically creates a template through the data, so cloud infrastructure design and template It is possible to generate an infrastructure installation template optimized for the service of the edge cloud device 330 and increasing the accuracy and efficiency of creation.

9 is a schematic flowchart for designing, deploying, and installing an edge cloud infrastructure according to an embodiment of the present invention.

The cloud manager 311 of the central cloud device 310 receives a cloud infrastructure design request from an administrator connected to the web server 614 (S911), and the web server 614 includes a design UX 611 and an installation UX ( 612) and the status UX 613, the design UIs 700 and 800 of FIGS. 7 and 8 are provided, and the cloud manager 311 creates a design list according to the design information and stores it in the database 621 ( S912). When the design is completed (S913), the cloud manager 311 parses the design data stored in the database 621 to create a cloud installation template, and stores the created template file in the storage 623 (S914).

Thereafter, when an installation request event occurs, the cloud manager 311 refers to the design list of the database 621 (S931), compares the design list with the design list, and checks the validity of the template created in the storage 623 (S932). . If validity is confirmed, the cloud manager 311 creates a new installation image in which software packages are added to the basic installation image according to the software package configuration details of the template and stores it in the storage 623 (S933). Next, the cloud manager 311 installs the manager agent 331 on the edge cloud device 330 (S934), and transmits an installer of installation information including templates, images, and scripts to the installed manager agent 331 to the edge cloud device 330. Installation of the cloud starts (S935).

FIG. 10 is a schematic flowchart of generating an installation template of cloud infrastructure in FIG. 9 .

In the steps S912 to S914, cloud infrastructure design and template generation are processed as follows. Design starts (S1001), and hardware such as racks, servers, and switches constituting the cloud infrastructure is arranged and types are designed based on the design UIs 700 and 800 of FIGS. 7 and 8 (S1002). An installation software package is selected for each designed hardware resource (S1003), and a NIC is placed (S1004). When the design is completed, the cloud manager 311 stores the completed design information in the database 621 (S1005).

The cloud manager 311 extracts design information from the database 621, classifies data by device, creates templates and scripts for each category (S1011), and stores the integrated templates and generated scripts in the storage 623. Do (S1012).

11 is a schematic flowchart of installing hardware in the edge cloud device 330 for installation of cloud infrastructure in FIG. 9 .

In order to install the cloud infrastructure in step S931, hardware infrastructure construction of the edge cloud device 300 is processed as follows. Hardware devices such as racks, servers, and switches are installed, and cables between devices are installed (S1101). Detailed items of servers and switches of the installed hardware are set (S1102 and S1103). Communication between the central cloud device 310 and the edge cloud device 330 is confirmed through the network connection (S1104). When communication is confirmed, information on the installed hardware is registered to the cloud manager 311, the template of the storage 623 is updated (S1105), and infrastructure installation is completed (S1106).

In the network connection, a provisioning network and an Intelligent Platform Management Interface (IPMI) network for center-to-edge installation work are tested. The provisioning network is used for general communication such as installation package transfer, template transfer, installation status check, etc., and the IPMI network is used for remote control such as power management and network booting of the remote edge cloud device 330. A network that can communicate with the central cloud manager 311 is tested, IPMI IP address and account information for each server, management IP of the switch, MAC address information of the PXE boot interface for network booting, CPU of each server, When RAM HDD information, switch product information, etc. are transmitted to the central cloud manager 311, the cloud manager 311 has an environment capable of controlling each device of the edge cloud device 330.

When the hardware installation is completed in the edge cloud device 330 as described above, a cloud installation request event occurs in step 931 and the installation process proceeds. The cloud manager 311 adds/updates hardware information installed in the edge cloud device 330 to the template previously created in step S914 in step S1106, and lists installed software packages for each server type defined in the template. Creates an image with the software installed. Here, the basic image in the existing storage 623 is a file in which only the OS for running the server is installed, and software packages for the cloud infrastructure are installed in the image file to install the corresponding image on the edge cloud device 330 later. After designing, an image must be created in order to automatically execute them.

12 is a schematic flowchart of generating an installation image of the cloud infrastructure in FIG. 9 .

As shown in FIG. 11 , when hardware installation in the edge cloud device 330 is completed, a cloud installation request event occurs in step 931 and the installation process proceeds. The cloud manager 311 adds/updates hardware information installed in the edge cloud device 330 to the template previously created in step S914 in step S1106, and lists installed software packages for each server type defined in the template. Creates an image with the software installed. Here, the basic image in the existing storage 623 is a file in which only the OS for running the server is installed, and software packages for the cloud infrastructure are installed in the image file to install the corresponding image on the edge cloud device 330 later. After designing, an image must be created in order to automatically execute them.

In the step (S933), the creation of the installation image of the cloud infrastructure is processed as follows. The cloud manager 311 refers to the database 621 and the storage 623 to load a basic image (S1201), loads a software package list in a template generated through design (S1202), and A script is automatically generated (S1203). The contents required for the script are the information of the software package repository to download the package from and the package list. The cloud manager 311 creates a temporary VM for installation using the base image (S1204), transmits and executes a script to the VM (S1205), installs each package in the disk file of the VM (S1206), and is deleted (S1209). The disk file of the deleted VM remains in RAW format. After converting the disk file to QCOW format, it is stored as an updated image in the storage 623, and the information of the newly uploaded image is created in the database 621 It does (S1209). Through this, when installing the edge cloud, the image in which all packages are installed using the VM is installed in the edge cloud device 330 as it is, such as software package storage required for conventional cloud installation, processing of communication network access for package download, etc. Manual setup work by administrators is eliminated.

FIG. 13 is a schematic flowchart of installing the manager agent 331 in the edge cloud device 330 in FIG. 9 .

In FIG. 11 , the manager agent 331 is installed in the edge cloud device 330 where the hardware infrastructure is installed in step S934 as follows. When both the template and the installation image are prepared, the cloud manager 311 starts installing the manager agent 331 on the edge cloud device 330 (S1301). In order to install the manager agent 331, the provisioning IP address and IPMI address of the manager agent 331 are checked from the template information (S1302). After checking the network information of the agent, the power of the target device 330 on which the agent 331 is installed is remotely controlled to be “on” through IPMI (S1303). When the device 330 is turned on, the image of the agent 331 is transmitted to the corresponding device 330 through IPMI to install the image, and when the installation is completed, the provisioning IP address of the agent 331 is changed to that of the agent 331. It is set in the edge cloud device 300 (S1304), and it is checked whether communication is established between the central manager 311 and the agent 331 through the provisioning network (S1305).

When communication through the central-edge provisioning network is activated, the central manager 311 performs detailed settings of the agent 331 through the provisioning network. The manager 311 activates the DHCP process of the network for management of the agent 331 . The network DHCP for management exists to use IP for the device 330 in the process of checking whether the servers defined as templates actually exist in the edge before installing the edge device 330 . After DHCP activation is completed, the remaining cloud installation processes are sequentially activated (S1306). The manager 311 transmits templates and images stored in the storage 623 to the agent 331 for cloud installation (S1307), and the agent 331 stores the transmitted data in the storage 641 within the agent 331. and registers related data and stored information in the agent database 642 (S1308). The cloud manager 311 registers information on the installed manager agent 331 in the database 621 (S1309).

Here, the installed agent 331 serves to install and manage the local edge cloud device 330 . The cloud manager 311 installs/manages each edge cloud device 330 by placing one agent 331 at each edge, and receives information such as the status/status of the edge cloud device 330, thereby centrally It is possible to manage all of the distributed edge cloud devices 330.

14 is a schematic flowchart of the manager agent 331 installed in FIG. 13 installing cloud infrastructure.

After the installation of the agent 331 is completed through FIG. 13 (S1401), detailed performance of the installed agent 331 is as follows. The agent 331 installed through the central manager 311 stores cloud installation templates and images received from the manager 311 in the edge local storage 641, creates templates and image information, and stores them in the database 642. Save (S1402). The agent 331 checks the validity of the template stored in the storage 641 (S1403), and checks whether the installation target servers and switches specified in the template are servers and switches that exist in the local edge or infrastructure that can normally be installed in the cloud (S1403). S1404). If the infrastructure check is normal, the agent 331 installs the cloud infrastructure on the switch and server at the edge based on the stored image and template (S1405). The agent 331 periodically collects information on the installation status of each edge infrastructure and reports it to the central cloud manager 311 so that the installation status of the entire edge cloud can be identified and managed from the center (S1406). When the installation is completed, the installed edge cloud is registered in the cloud manager 311, and the cloud service is provided to service users (S1407).

FIG. 15 is a schematic flowchart in which the manager agent 331 of FIG. 14 checks the infrastructure of the edge cloud device 330 for cloud infrastructure installation.

In the above step (S1404), the cloud infrastructure check is processed as follows. Infrastructure information was registered in the central manager 311 through infrastructure design and related data was created as a template. You need to check if it is spec. This is a procedure to minimize the possibility of installation failure by ensuring that the configuration is properly configured during the infrastructure installation process.

When the initial infrastructure check starts (S1501), the agent 331 parses the installation template, checks server/switch data (S1502), and logically creates a provisioning network for network communication for edge cloud infrastructure installation (S1503). Here, a TFTP server is configured and loaded with DHCP for allocating a provisioning network IP to the server and a low-capacity image to be used when checking the infrastructure. The low-capacity image is installed in the cloud server in the infrastructure confirmation step and has a function of automatically reporting information about the server, such as network, disk, and computing resources, to the agent 331 .

After configuring the network, the type and device information of each server and switch defined in the template is stored in the database (S1504, S1505). Here, the types of servers and switches to be installed are the roles of each server and switch in the cloud. In the case of a server, a controller that manages services provided by the cloud, a network server that serves as SNAT and DNAT for external communication, and a VM Compute servers and the like may be exemplified. Depending on the design outcome, this type can be further varied.

After completing the registration of the corresponding information, the agent 331 starts an infrastructure confirmation process for the registered device (S1506). First, by pinging the IPMI IP and management IP of each server and switch, it is confirmed whether each device exists at the edge (S1507). If it is determined that the device exists, in the case of a switch, it is checked whether login is possible by connecting to the switch management IP address defined in the template (S1509). If the login is successful, the switch is judged as an installable infrastructure and completes the verification process.

Next, in the case of servers, after powering on the server, setting the server to network boot mode (S1511, S1512), installing a low-specification image for infrastructure confirmation, and checking CPU, RAM, disk, and network port information of each server. It is searched and transmitted to the agent (S1513 to S1515). Upon receiving the information, the agent 331 determines whether each server is a device suitable for cloud infrastructure installation, and if there is no problem, updates the device status in the database 642 in an installable state (S1516), and proceeds to check the infrastructure. is completed (S1517). If a problem occurs during this process, you will have to go through the hardware infrastructure installation process again.

FIG. 16 is a schematic flowchart of the manager agent 331 installing cloud infrastructure in the edge cloud device 330 in FIG. 14 .

After the cloud infrastructure is confirmed through FIG. 15, the infrastructure installation is processed as follows in the above step (S1404). The agent 331 starts infrastructure installation (S1601) and parses the template stored in the storage 641 (S1602).

A switch is installed according to the parsed template information (S1603). The agent 331 sets a VLAN for each port of the switch through port mapping data between the server and the switch defined in the template, network type for each port of the server, and VLAN data for each network type. Here, the network type means a classification of networks according to the purpose used in the network device, and examples thereof include a network for management, a network for communication between virtual machines, and a provisioning network. After VLAN configuration, if additional switch settings are required for switch redundancy and server network port bonding, additional settings are made through the installation script of the template. The reason why the switch is set up before installing the server is that there is a network test procedure among the server installation procedures.

After completing the switch setting, the agent 331 creates a network for each purpose required for each device defined in the template (S1604). Here, network types are logically created and DHCP for the network is created. And according to the network used for each port of the server, IP addresses are generated for each port, and the corresponding information is notified to DHCP. If an IP address is generated in advance and notified to DHCP, when a server later requests an IP address from DHCP, DHCP assigns the previously informed address to the server. When the DHCP installation is completed, the server is turned on through IPMI (S1605), the network boot mode is set (S1606), and the cloud installation image created in the previous step is booted to install the image (S1607).

When the image installation is completed, each server is assigned an IP through DHCP while configuring the network in the OS (S1611). After completing this process, the server is rebooted (S1612). After rebooting, a ping test is performed between each installation server (S1613). Through this, each server checks whether the network is normally set, and all servers confirm that booting is complete. Here, all servers must go through the same steps during installation. In order to prevent differences in installation steps due to different servers or problems such as network delay, a ping test is performed after rebooting. After the ping test, if there is a server that does not ping after a certain period of time, the cloud installation is terminated.

If the ping test is normally completed, the agent 331 creates configuration files for software packages based on the template data and activates each package (S1614). When the activated software packages operate normally, an installation operation through a subsequent installation script proceeds (S1615). Subsequent installation is performed differently for each server to optimize the server if there are specific settings for each server or software package settings that require a reboot. After the subsequent installation, if the server is rebooted (S1616), the cloud installation is completed (S1617). Then, cloud information such as an access URL of the corresponding cloud, a manager ID, and a password is registered in the database 621 of the central manager 311 through the agent 331 of the edge.

After the installation of cloud infrastructure in the edge cloud device 330 is completed, cloud services are provided to users. Then, when the addition of various services of 5G occurs, it may be required to add the service to the independently optimized infrastructure. When configuring the edge cloud device 330 for the first time, an edge cloud (Controller + Network node + IT Compute) capable of accommodating cloud operations and basic IT services is configured. In the case of most cloud providers, preparing infrastructure for services in advance can be a risk in terms of cost because it is impossible to determine the acceptance time and scale of a specific service.

If a service is added to a specific edge cloud device 330 after initial cloud configuration, the above-described installation procedure of FIGS. 9 to 16 is followed. When an additional service request is received, as shown in FIGS. 9 and 10 , the cloud manager 311 registers hardware and cloud infrastructure design information optimized for the corresponding service. Also, as shown in FIG. 11 , corresponding hardware is purchased and installed in the edge cloud device 330 through design information. After installation, as shown in FIGS. 12 and 14 to 16, cloud installation optimized for the service proceeds according to the above cloud installation procedure, and by grouping servers for the service, independent Cloud infrastructure can be added. Through this, the present invention can provide an independent optimal infrastructure for each service, unlike the conventional cloud installation, and can increase the economic and time efficiency for accepting various 5G services.

Although the present invention has been described with limited examples and drawings, the present invention is not limited thereto, and the technical idea of the present invention and claims to be described below are made by those skilled in the art to which the present invention belongs. Of course, various modifications and variations are possible within the equivalent range of the scope.

300: cloud system 310: central cloud device
311: cloud manager 330: edge cloud device
331: manager agent

Claims (26)

A central cloud device running a cloud manager that manages the design, distribution, and installation of edge cloud infrastructure, wherein the cloud manager:
A design registration unit that receives design information of edge cloud infrastructure;
Template generation unit for generating an installation template according to the registered design information;
When an installation request is received, an installation image generator for generating an installation image according to the corresponding template;
a manager agent installation unit for installing a manager agent for installation and management of the edge cloud infrastructure in an edge cloud device; and
Installation information transmission unit for transmitting installation information including the template for installing the edge cloud infrastructure and the installation image to the manager agent
A central cloud device that includes. According to claim 1,
A central cloud device characterized in that a web server is installed that receives request information of design, installation, and installation status as the design information based on a web page. According to claim 1,
The design register,
A central cloud device characterized in that it provides object information of hardware and software constituting the edge cloud infrastructure, and receives environment information and setting information of software objects corresponding to each hardware object as the design information. According to claim 1,
The template generator,
The design information including software package information corresponding to each hardware device including racks, servers, and switches is referred to, each template corresponding to the type information for each referenced device is created, and the created template and execution script are integrated. A central cloud device characterized in that for generating and storing the installation template. According to claim 1,
The cloud manager,
Receives registration of information of the provisioning network for installation communication and IPMI (Intelligent Platform Management Interface) network for remote control from the edge cloud device on which the hardware infrastructure is installed, communicates installation data based on the registered provisioning network, and communicates data for installation based on the registered IPMI network. The central cloud device, characterized in that for remotely controlling the edge cloud device to install the manager agent and cloud infrastructure. According to claim 1,
The installation image generating unit,
A temporary VM (Virtual Machine) for installation is created using the basic image of the operating system of the edge cloud device, and the software package image according to the template reflecting the hardware infrastructure information installed in the edge cloud device is executed with the script of the installation information. and adding it to the VM, and generating and storing the installation image with a disk file remaining after deleting the VM. According to claim 1,
The manager agent installation unit,
Remote access to the edge cloud device by referring to the address information in the information of the template to turn on the power, transmit the installation image of the agent to install the agent in the edge cloud device, network communication and address in the edge cloud device Central cloud device, characterized in that for setting. According to claim 1,
Status checking unit for receiving and confirming the installation progress of the edge cloud infrastructure from the manager agent
A central cloud device further comprising a. According to claim 1,
The design registration unit receives a request for additional design of the pre-built edge cloud device,
The template generation unit generates an installation template according to the additional design information,
The installation image generating unit receives an additional installation request and creates an installation image according to the corresponding template;
The central cloud device, characterized in that the installation information transmitter transmits additional installation information including the generated template and image to the manager agent. In an edge cloud device that receives, installs, and executes a manager agent for installation and management of edge cloud infrastructure from a central cloud device
The manager agent,
a receiving unit receiving installation information of the edge cloud infrastructure from the central cloud device by execution of an installed manager agent;
a parsing unit that analyzes the received installation information and parses template information;
a preparation unit preparing for installation by checking whether hardware resources exist and software resources can be installed according to the installation information; and
If it is confirmed as normal, the installation unit that installs the edge cloud infrastructure using the template and installation image of the installation information.
Edge cloud device that includes. According to claim 10,
For the creation of the installation image and the installation of the agent, after each hardware device including a rack, server, and switch is installed, and a network for installation management and remote management is set, each of the installed hardware devices is connected to the central cloud device. An edge cloud device characterized by transmitting and registering management information including hardware addresses and accounts. According to claim 10,
The preparation part,
Check data for each device including servers and switches to see if the infrastructure information defined in the template is real, set network and address information to receive installation progress reports from the checked devices, and use the set information to confirm An edge cloud device, characterized in that it checks existence by performing a ping test with devices. According to claim 10,
The installation part,
Using the information of the template, set the network and virtual LAN information of the switch, install the server based on the set information, set the address to the installed server, boot the server with the installation image, and install the switch and An edge cloud device characterized by performing a ping test between each device including an address and, if the ping test is successful, executing a software package for each device to complete installation. A method in which a central cloud device runs a cloud manager to manage the design, distribution, and installation of edge cloud infrastructure,
Receiving design information of edge cloud infrastructure;
Generating an installation template according to the registered design information;
generating an installation image according to the corresponding template when an installation request is received;
Installing a manager agent for installation and management of the edge cloud infrastructure in an edge cloud device; and
Transmitting installation information including the template for installing the edge cloud infrastructure and the installation image to the manager agent
How to include. According to claim 14,
The registration step is
A method characterized in that a web server provides a web page and registers design, installation, and installation state request information as the design information. According to claim 14,
The registration step is
The method characterized in that the step of providing object information of hardware and software constituting the edge cloud infrastructure, and selecting environment information and setting information of software objects corresponding to each hardware object as the design information. According to claim 14,
The step of creating the installation template,
The design information including software package information corresponding to each hardware device including racks, servers, and switches is referred to, each template corresponding to the type information for each referenced device is created, and the created template and execution script are integrated. and generating and storing the installation template. According to claim 14,
Before generating the installation image,
Further comprising registering information on a provisioning network for installation communication and an Intelligent Platform Management Interface (IPMI) network for remote control from the edge cloud device on which hardware infrastructure is installed,
Wherein the cloud manager communicates installation data based on a registered provisioning network and remotely controls the edge cloud device based on a registered IPMI network to install the manager agent and cloud infrastructure. According to claim 14,
The step of creating the installation image is,
A temporary VM (Virtual Machine) for installation is created using the basic image of the operating system of the edge cloud device, and the software package image according to the template reflecting the hardware infrastructure information installed in the edge cloud device is executed with the script of the installation information. and adding the VM to the VM, and generating and storing the installation image with a disk file remaining after deleting the VM. According to claim 14,
The installation step is
Remote access to the edge cloud device by referring to the address information in the information of the template to turn on the power, transmit the installation image of the agent to install the agent in the edge cloud device, network communication and address in the edge cloud device A method characterized in that the step of setting. According to claim 14,
After the sending step,
Receiving and confirming the installation progress of the edge cloud infrastructure from the manager agent
A method characterized in that it further comprises. According to claim 14,
By the transmitting step, after the cloud infrastructure is installed in the edge cloud device, the cloud manager,
Receiving a request for additional design of a pre-built edge cloud device from the manager agent;
generating an installation template according to the additional design information;
generating an installation image according to the template corresponding to the additional installation request; and
Additional installation by transmitting additional installation information including the generated template and image to the manager agent
A method characterized in that for executing. In the method for the edge cloud device to run the manager agent to install the edge cloud infrastructure,
Receiving installation information of the edge cloud infrastructure from a central cloud device;
Parsing template information by analyzing the received installation information;
Preparing for installation by confirming whether hardware resources exist and software resources can be installed according to the installation information; and
If confirmed normally, installing the edge cloud infrastructure using the template and installation image of the installation information
How to include. 24. The method of claim 23,
Before the receiving step, for generating the installation image and installing the agent, the manager agent,
After installing each hardware device including racks, servers, and switches and setting up a network for installation management and remote management, management information including the address and account of each installed hardware is transmitted to the central cloud device, A method characterized by registering. 24. The method of claim 23,
The preparation step is
Check data for each device including servers and switches to see if the infrastructure information defined in the template is real, set network and address information to receive installation progress reports from the checked devices, and use the set information to confirm A method characterized in that the step of confirming existence by performing a ping test with devices. 24. The method of claim 23,
The installation step is
Using the information of the template, set the network and virtual LAN information of the switch, install the server based on the set information, set the address to the installed server, boot the server with the installation image, and install the switch and and performing a ping test between each device including the address, and if the ping test is successful, executing the software package for each device to complete the installation.

Images