WO2020116223A1 - Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム - Google Patents
Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム Download PDFInfo
- Publication number
- WO2020116223A1 WO2020116223A1 PCT/JP2019/045934 JP2019045934W WO2020116223A1 WO 2020116223 A1 WO2020116223 A1 WO 2020116223A1 JP 2019045934 W JP2019045934 W JP 2019045934W WO 2020116223 A1 WO2020116223 A1 WO 2020116223A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- configuration information
- virtual
- resource management
- unit
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Definitions
- the present invention relates to an ICT (Information and Communication Technology) resource management device, an ICT resource management method, and an ICT resource management program.
- ICT Information and Communication Technology
- Patent Document 1 "one different communication service that is disclosed by a communication service API for each wholesale service provider in response to an order request for use of a communication service from a terminal that provides communication to a user" is disclosed.
- An inter-provider batch service construction device for collectively providing one or more of the above, which holds a catalog in which specifications of communication wholesale services are described and a cooperation rule which defines cooperation of various communication services,
- the communication service APIs corresponding to the plurality of communication services requested for the order are collectively cooperated based on the held catalog and the cooperation rule.
- a cooperative service is constructed, and a collective construction function unit for providing the constructed cooperative service to the terminal is provided.
- the cloud platform is a platform that provides devices such as servers and edges using virtualization technology.
- the cloud platform is a platform that provides devices such as servers and edges using virtualization technology.
- a technique of performing resource allocation from an orchestrator is known.
- selection of a cloud infrastructure and resource allocation involved human work, so there was a limit to the work efficiency for a service provider to be able to provide cloud services, and a system equipped with a cloud infrastructure was limited. There is a problem that it causes an increase in operating costs.
- an object of the present invention is to reduce operation costs by improving work efficiency when a service provider can provide a service.
- the invention according to claim 1 is an ICT resource management device that manages a physical node and a virtual node, which are ICT resources, and is configuration information regarding the physical node on a physical layer.
- a physical layer configuration information and a configuration information management unit that manages virtual layer configuration information that is configuration information regarding the virtual node on the virtual layer, and a request for configuration change regarding connection of a device using a service to the physical node.
- a cloud platform selection unit that selects a service platform that satisfies the conditions included in the request, and a layer mapping unit that performs mapping between the physical layer and the virtual layer.
- the infrastructure necessary for the configuration change In response to the configuration change request, based on the physical layer configuration information, the virtual layer configuration information, the selected service infrastructure, and the mapping information that is the result of the mapping, the infrastructure necessary for the configuration change
- a blueprint creating unit that creates a blueprint as design information, and an orchestrator that performs orchestration for the virtual layer by accessing and executing a program that can be operated through an API based on the blueprint. And a section.
- the invention according to claim 3 is an ICT resource management method in an ICT resource management device for managing physical nodes and virtual nodes, which are ICT resources, wherein the ICT resource management device is the physical layer on a physical layer.
- a step of collecting physical layer configuration information which is configuration information regarding a node and a virtual layer configuration information which is configuration information regarding the virtual node on a virtual layer, and a configuration change regarding connection of a device using a service to the physical node The plurality of service bases for realizing the service, the step of selecting a service base satisfying the conditions included in the request, the step of performing mapping with the physical layer and the virtual layer, In response to a configuration change request, based on the physical layer configuration information, the virtual layer configuration information, the selected service infrastructure, and the mapping information that is the result of the mapping, the design information of the infrastructure required for the configuration change.
- executing a orchestration for the virtual layer by accessing and executing a program that can be operated through an API based on the blueprint. It is characterized by
- the invention according to claim 2 is the ICT resource management device according to claim 1, wherein the service infrastructure selecting unit manages the service using a plurality of types of management items corresponding to the conditions. It is characterized in that the service infrastructure satisfying the condition is selected with reference to management information.
- the invention according to claim 4 is an ICT resource management program for causing a computer to function as the ICT resource management device according to claim 1 or claim 2.
- the construction of the ICT resource management device can be facilitated.
- the operation cost can be reduced by improving the work efficiency when the service provider can provide the service.
- the cloud service may be simply referred to as “service”.
- a distributed system 100 including the ICT resource management device 1 of the present embodiment is a system to which virtualization technology is applied, and includes the ICT resource management device 1, the service provider terminal 2, and the server 3. , Edges 4, 4-1 and devices 5, 5-1.
- the edge 4-1 is one of a plurality of edges 4 that exist, and the edges 4 and 4-1 may be collectively referred to as the edge 4.
- the device 5-1 is one of a plurality of devices 5 that exist, and the devices 5 and 5-1 may be collectively referred to as the device 5.
- the distributed system 100 can manage a physical layer that is an aggregate of physical nodes and a virtual layer that is an aggregate of virtual nodes configured and operating on the physical nodes.
- the server 3, the edge 4, and the device 5 are physical nodes forming a physical layer.
- a VM (Virtual Machine) 7 arranged on the virtual layer shown in FIG. 1 is a virtual node in which the server 3 or the edge 4 is virtualized.
- FIG. 1 illustrates cloud platforms A and B.
- Each of the cloud platforms A and B (which may include other cloud platforms (not shown)) has various services such as a charge, a quality, a service providing area, etc. even if the services are of the same type such as a computing service. It realizes similar services with different conditions.
- a virtual node corresponding to the cloud platform A is shown in the virtual layer of FIG. Although a virtual node corresponding to the cloud platform B exists in this virtual layer, it is omitted in FIG. 1 for convenience.
- the ICT resource management device 1 manages physical nodes and virtual nodes as ICT resources.
- the service provider terminal 2 is a terminal that requests configuration changes such as initial deployment and variable scale.
- the service provider terminal 2 makes the request through an API (Application Programming Interface).
- the API is a Northbound API between the ICT resource management device 1 and the service provider terminal 2.
- the service provider terminal 2 is used by the service provider.
- the server 3 is a computer that executes processes related to service provision.
- the server 3 shown in FIG. 1 is arranged on, for example, the cloud platforms A and B, and executes processes for cloud services.
- At least one of one or a plurality of applications (abbreviation of applications) 6-1 to 6-3 for executing a process related to service provision is arranged in the server 3.
- Each of the applications 6-1 to 6-3 is used when providing different services.
- Edge 4 is a relay device arranged on the NW (network), and corresponds to, for example, a router, a bridge, or a gateway. At the edge 4, at least one of one or a plurality of applications 6-1 to 6-3 for executing a process related to service provision is arranged. The server 3 and the edge 4 are communicably connected.
- the device 5 is a device that the end user uses the service, and corresponds to, for example, an IoT device.
- the device 5 can use the service by connecting to the edge 4.
- the ICT resource management device 1 can collect information about physical nodes and virtual nodes. Further, the ICT resource management device 1 can perform mapping between the physical layer and the virtual layer by using the collected information (see the broken double-headed arrow in FIG. 1). Further, the ICT resource management device 1 can execute orchestration on the virtual layer. Specifically, it is possible to deploy a service and allocate resources to the VM 7.
- the ICT resource management device 1 includes a request acquisition unit 11, a blueprint creation unit 12, a configuration information management unit 13, a layer mapping unit 14, a workflow execution unit 15, and an API adapter unit 16. And a functional unit such as the monitoring unit 17.
- the blueprint creation unit 12 includes a cloud infrastructure selection unit 12a.
- the ICT resource management device 1 stores the configuration information DB 21, the mapping information 22, the catalog group 23, the blueprint 24, and the service management information 25 in the storage unit.
- the storage unit included in the ICT resource management device 1 may be, for example, inside the ICT resource management device 1 or outside the ICT resource management device 1.
- the request acquisition unit 11 acquires a configuration change request from the service provider terminal 2.
- the request acquired by the request acquisition unit 11 may be called “order information”.
- the configuration change request can be made not only from the service provider terminal 2 but also from the terminal of the maintenance person of the distributed system 100, for example.
- the service provider terminal 2 and the maintenance person's terminal are examples of external devices.
- the blueprint creation unit 12 creates the blueprint 24 corresponding to the order information acquired by the request acquisition unit 11.
- the blueprint 24 is the design information of the infrastructure required for the requested configuration change.
- the infrastructure indicates the components of the operating environment of the service. For example, the ICT resource itself, ICT resource setting information (eg VM name, IP address, host name), allocated resources, LB (load balancer) set on the NW. ), FW (firewall), and containers.
- the configuration information management unit 13 manages information about ICT resources as configuration information.
- the configuration information management unit 13 can collect information about physical nodes and virtual nodes by accessing the API for collecting resource information, for example.
- the resource information collection API is an API for providing resource information prepared by the orchestration target.
- the API for collecting resource information is a southbound API between the ICT resource management device 1 and the orchestration target.
- the information to be collected can be, for example, a MIB (Management Information Base) based on Simple Network Management Protocol (SNMP), but is not limited to this.
- MIB Management Information Base
- SNMP Simple Network Management Protocol
- Orchestration targets include, but are not limited to, physical nodes and virtual nodes.
- the interface provided by the orchestration target can be provided by, for example, a controller (not shown) that controls the orchestration target, or can be provided by each of the physical node and the virtual node.
- the physical layer configuration information 21a is configuration information regarding physical nodes on the physical layer. As shown in FIG. 3, the physical layer configuration information 21a includes, for example, "node ID”, "state”, “host name”, “IP address”, “VMID”, "use service”, “user”, and “user”. It has a management item such as "cloud infrastructure ID”, and the value of each management item is stored for each physical node.
- the management item of “node ID” stores the identifier of the target physical node.
- the management item of "state” stores the operating state of the target physical node ("OK" for normal, "NG” for failure).
- the host name of the target physical node is stored in the management item of “host name”.
- the IP address assigned to the target physical node is stored in the management item of “IP address”.
- the “VMID” management item stores the identifier of the VM operating on the target physical node.
- the management item of "utilization service” stores the identifier of the service available in the target physical node.
- Utilization services include, for example, cloud services and edge computing services, but are not limited to these. Further, the service to be used can include a service that enables a plurality of physical nodes to provide the same service.
- the “user” management item stores the identifier of the user who uses the service indicated by the corresponding “use service”.
- the user may be, for example, a corporation or an individual. Further, for example, when the corresponding physical node is an edge device, only the owner of the edge device can be the user.
- the “cloud infrastructure ID” management item stores the identifier of the cloud infrastructure to which the target physical node belongs.
- the management items of the physical layer configuration information 21a shown in FIG. 3 are examples, and more can be set.
- the management items of the physical layer configuration information 21a it is possible to set the memory size of the VM operating on the target physical node, the CPU frequency, the power state, and the VM name.
- the name and ID of the resource pool used for the target physical node can be set.
- the management item of the physical layer configuration information 21a the type, ID, and name of the network in which the target physical node is arranged can be set.
- the ID, type, and name of the folder used by the target physical node can be set.
- the management items of the physical layer configuration information 21a the storage capacity, ID, type, and name of the data store used by the target physical node can be set. Further, as the management item of the physical layer configuration information 21a, the ID and name of the data center controlling the target physical node can be set. Further, as the management items of the physical layer configuration information 21a, it is possible to set a user name and a password which are authentication information of a user who accesses the target physical node.
- the virtual layer configuration information 21b is configuration information regarding virtual nodes on the virtual layer. As shown in FIG. 4, the virtual layer configuration information 21b has management items such as “node ID”, “state”, “VM name”, “IP address”, and “physical device ID”. The value of each management item is stored in.
- the management item of “node ID” stores the identifier of the target virtual node.
- the management item of "state” stores the operating state of the target operating node ("OK" for normal operation, "NG” for failure).
- the name of the target virtual node is stored in the management item of “VM name”.
- the IP address assigned to the target virtual node is stored in the management item of “IP address”.
- the management item of “physical device ID” stores the identifier of the physical node in which the target virtual node is arranged.
- the management items of the virtual layer configuration information 21b shown in FIG. 4 are examples, and more can be set.
- a VMID that is ID information of the target virtual node can be set.
- the management items of the virtual layer configuration information 21b it is possible to set the memory size and the CPU frequency that are resources of the target virtual node.
- the power state of the target virtual node can be set as a management item of the virtual layer configuration information 21b.
- the management items of the virtual layer configuration information 21b it is possible to set a user name and a password which are authentication information of a user who accesses the target virtual node.
- a gateway used by the target virtual node a VXLAN (Virtual eXtensible Local Area Network), and a static route can be set.
- the host name of the physical node in which the target virtual node is arranged can be set as the management item of the virtual layer configuration information 21b.
- the management item of the virtual layer configuration information 21b it is possible to set information regarding the hypervisor that generates the target virtual node.
- the management item of the container application can be set as the management item set in the virtual layer configuration information 21b.
- the management items of the virtual layer configuration information 21b the host name, label, state, and account ID of the container host registered for the container used by the target virtual node can be set.
- the management items of the virtual layer configuration information 21b it is possible to set the ID, name, state, and scale (the number of utilization servers) of the service provided by the container used by the target virtual node.
- the management items of the virtual layer configuration information 21b it is possible to set the volume mount, ID (only when using the Collinser NFS (Network File System)) and image ID of the storage device provided in the container used by the target virtual node. it can.
- the management items of the virtual layer configuration information 21b it is possible to set the stack group of the storage device provided in the container used by the target virtual node, the health state, the stack ID, and the ID of the service used.
- the cloud platform selecting unit 12a included in the blueprint creation unit 12 is a cloud platform that fulfills the conditions included in the configuration change request regarding the connection of the device that uses the cloud service to the physical node among the plurality of cloud platforms that implement the cloud service. Select the base.
- the selected cloud-based identifier constitutes a part of the physical layer configuration information 21a.
- the cloud platform selecting unit 12a is a partial function of the blueprint creating unit 12, and can access the API for collecting resource information and solve the collected information to specify the selected cloud platform. In the present embodiment, a case of selecting a cloud platform that realizes a cloud service will be described, but the present invention can also be applied to services that are not cloud services.
- the cloud platform selecting unit 12a of this embodiment is a specific example of a service platform selecting unit that selects a service platform.
- the cloud infrastructure selecting unit 12a may be provided anywhere in the ICT resource management device 1, but here, as an example, the blueprint creating unit 12 is provided.
- the layer mapping unit 14 performs mapping between the physical layer and the virtual layer. Specifically, based on the configuration information managed by the configuration information management unit 13, the layer mapping unit 14 determines which physical node on the physical layer the virtual node on the virtual layer is (or the application 6 on which the physical node is arranged). ) Is associated with.
- the ICT resource management device 1 stores, as the mapping information 22, the determination result of the association of the physical node and the virtual node by the layer mapping unit 14.
- the layer mapping unit 14 refers to the management item of “VMID” of the physical layer configuration information 21a (FIG. 3) and the management item of “Physical device ID” of the virtual layer configuration information 21b (FIG. 4), The association between the physical node and the virtual node can be determined.
- FIG. 5 is an explanatory diagram of a blueprint for initial deployment.
- the blueprint 24 can be configured as a set of a service template and parameters.
- the service template can be a collection of catalogs.
- the catalog is a template of processes used for providing services, and is an element of the catalog group 23 stored in the ICT resource management device 1.
- the catalog itself is well known, and detailed description thereof will be omitted.
- the parameter is input information for each catalog.
- the order information acquired by the request acquisition unit 11 is the order information related to the initial deployment.
- the blueprint creation unit 12 can configure a service template by selecting a catalog for VM creation, a catalog for NW setting, and a catalog for container setting from the catalog group 23, for example. ..
- the parameters input to the catalog for VM creation are, for example, the number and type of VMs created.
- parameters for designating three VMs that function as Web servers and two VMs that function as AP servers (application servers), that is, a total of five VMs are input to the catalog for VM creation.
- the parameter input to the catalog for VM creation can be input by the service provider terminal 2, for example.
- the parameter input to the NW setting catalog is, for example, IP address allocation (IP allocation).
- IP allocation IP allocation
- the parameter designating the IP address assigned to the created VM is input to the NW setting catalog.
- the parameters input to the NW setting catalog can be acquired from the distributed system 100, for example.
- the parameter input to the container setting catalog is, for example, the setting method of the container used by the created VM.
- a parameter indicating the setting method of copy execution by Collinser is input to the container setting catalog.
- the parameter input to the container setting catalog can be input by the service provider terminal 2, for example.
- the blueprint creation unit 12 selects a required catalog from the catalog group 23 according to the operation indicated by the order information acquired by the request acquisition unit 11, and forms a service template.
- the blueprint creating unit 12 can acquire the parameters input to the selected catalog from the order information and the distributed system 100.
- the blueprint creation unit 12 requests the parameters input to the selected catalog from the service provider terminal 2 or the like that has sent the order information, and receives the order information that is a response to the request again, thereby ordering the order. Parameters can be obtained from the information.
- the distributed system 100 itself can acquire the parameters such as the allocation of the IP address
- the blueprint creation unit 12 can acquire the parameters input to the selected catalog from the distributed system 100.
- the blueprint creating unit 12 refers to the configuration information managed by the configuration information managing unit 13 and the mapping information 22 stored by the layer mapping unit 14. That is, the blueprint creating unit 12 determines the current state of the physical node and the virtual node determined from the physical layer configuration information 21a, the virtual layer configuration information 21b, and the mapping information 22 and the service provider, which is indicated by the order information. It is possible to create the blueprint 24 by collating with the request such as.
- the workflow execution unit 15 executes the workflow according to the blueprint 24 created by the blueprint creation unit 12.
- the workflow is a process in which the steps indicated by the catalog included in the blueprint 24 are connected in a predetermined order.
- the workflow for initial deployment is such that the order is determined and linked, such as VM creation ⁇ NW setting ⁇ container setting.
- orchestration is executed and resources are assigned to the ICT resources.
- the API adapter unit 16 is an interface for accessing a program that can be operated through the API in response to a command from the workflow execution unit 15 that executes a workflow.
- the API is a southbound API between the API adapter unit 16 (or the ICT resource management device 1 including the API adapter unit 16) and the orchestration target.
- the API adapter unit 16 can be interface-connected for each orchestration target.
- a plurality of API adapter units 16 can be prepared for each program that can be operated through the API.
- the workflow execution unit 15 can execute a workflow by executing a program that can be operated through the API.
- the combination of the workflow execution unit 15 and the API adapter unit 16 functions as an orchestrator unit that executes orchestration.
- the monitoring unit 17 monitors the physical node on the physical layer and the virtual node on the virtual layer by, for example, SNMP.
- the monitoring result by the monitoring unit 17 indicates the usage status of the service which has been orchestrated and has become available.
- the monitoring result of the monitoring unit 17 can be transmitted to the configuration information management unit 13.
- the configuration information management unit 13 can collect information about physical nodes and virtual nodes based on the monitoring result of the monitoring unit 17.
- the service management information 25 is management information of services (network service, cloud service, etc.) used by the distributed system 100.
- the service management information 25 includes, for example, “service ID”, “cloud infrastructure ID”, “type”, “application used”, “charge”, “quality”, “providing area”, and “connection”. It has management items such as "service ID” and "operation ICT resource”, and the value of each management item is stored for each service.
- the above-described plurality of types of management items included in the service management information 25 correspond to a plurality of types of conditions included in the configuration change request regarding the connection of the device that uses the cloud service to the physical node. These conditions are the conditions required by the service provider.
- the management item of "service ID” stores the identifier of the target service.
- the management item of “cloud infrastructure ID” stores the identifier of the cloud infrastructure that realizes the target service.
- Information indicating the type of the target service is stored in the “type” management item.
- the stored information can be, for example, information indicating a computing service, a storage service, a big data service, a machine learning service, but is not limited to this.
- the management item of “used application” stores the identifiers of the applications 6-1 to 6-3 used for providing the target service. In other words, the used application is an application that constitutes the content of the target service.
- the “charge” management item stores information indicating the amount of money that is incurred when the device 5 uses the target service.
- the stored information can be, for example, information indicating the amount of money according to the communication amount per month, but is not limited to this.
- the “quality” management item stores information indicating the quality of the target service.
- the information stored can be, for example, information indicating an SLA (Service Level Agreement) set for the service, but is not limited to this.
- the management item of “providing area” stores information indicating an area where the target service is provided, that is, an area where the device 5 can use the service.
- the stored information can be, for example, information indicating an area within a radius of ⁇ kilometers centering on the edge 4 or the entire city, but is not limited to this.
- Services include services for connecting a plurality of services.
- the service provider desires to provide the first service, instead of selecting the first cloud platform that realizes the first service, the service provider realizes the second service connected to the first service. It is possible to provide the first service by selecting the second cloud platform that supports the above.
- the identifier of the ICT resource that operates when the target service is provided is stored in the management item of “operation ICT resource”.
- the operating ICT resource is a physical node in which the application to be used is arranged, or a virtual node operating on the physical node.
- the operating ICT resource is an ICT resource that is a target of resource allocation when a new application is received from a service provider.
- the operating ICT resource belongs to the cloud platform that realizes the target service, or to the ICT resource that belongs to the cloud platform via WAN (Wide Area Network) and CPE (Customer Premises Equipment), etc. Physically connected.
- WAN Wide Area Network
- CPE Customer Premises Equipment
- the cloud platform selecting unit 12a When a new device 5 is connected to a physical node forming a cloud platform by an application from the service provider, and there are a plurality of similar cloud platforms, the cloud platform selecting unit 12a notifies the service provider of An optimum cloud platform is selected for order information that requires a configuration change related to the connection of the device 5 to the physical node.
- similar cloud platforms means that the “type” (see FIG. 6) of each cloud service provided by each cloud platform is the same, and “charge”, “quality”, “providing area”, “connection service” It means that “ID” and “operating ICT resource” (see FIG. 6) are different.
- the order information includes conditions regarding the type of cloud service provided by the service provider, as requested by the service provider.
- the cloud platform selection unit 12a refers to the service management information 25 to identify a cloud service that matches the type indicated by the service provider's request from the “type” (FIG. 6) and realizes the identified cloud service.
- the cloud infrastructure (generally, a plurality of cloud infrastructures) to be used are identified from the “cloud infrastructure ID” (FIG. 6).
- the order information includes, for example, conditions regarding the charge, quality, and service area, as requested by the service provider.
- the condition regarding the charge can be, for example, an upper limit value of the usage charge of the cloud service per month.
- the quality conditions are, for example, the opening delay time, the network delay time, the network operation rate, the line operation rate, the failure recovery time, the failure notification time, and the minimum level of bandwidth guarantee set for the cloud service. You can
- the condition regarding the providing area can be a boundary between areas where the device 5 can use the cloud service.
- the cloud platform selecting unit 12a refers to the service management information 25 and selects one of the cloud platforms identified from the “type” and the “cloud platform ID” (FIG.
- the cloud platform selecting unit 12a can select the cloud platform as the optimum cloud platform.
- the cloud platform that is most advantageous to the service provider in terms of charges, quality, and service area, as the optimum cloud platform.
- the cloud platform selecting unit 12a If the selected cloud platform is a cloud platform to which the device 5 is connectable according to the “connection service ID” and “operation ICT resource” (FIG. 6) of the service management information 25, the cloud platform selecting unit 12a. Maintains the cloud infrastructure selection results. On the other hand, if the selected cloud platform is a cloud platform that the device 5 cannot connect to (for example, there is no connection between cloud services or physical connection between ICT resources), the cloud platform selecting unit 12a For example, it is possible to select, as the optimum cloud platform, the cloud platform that is the second most advantageous to the service provider in terms of price, quality, and service area. This kind of selection excludes the cloud platform that makes it possible to deploy the application from the perspective of the virtual layer, and even if it can meet the needs of the service provider, it cannot be physically connected from the perspective of the physical layer. Useful in.
- the blueprint creation unit 12 creates a blueprint 24 based on the configuration information managed by the configuration information management unit 13, the cloud platform selected by the cloud platform selection unit 12a, and the mapping information 22 stored by the layer mapping unit 14. To do.
- the workflow execution unit 15 can execute the workflow according to the blueprint 24 created by the blueprint creation unit 12. As a result, orchestration is performed and resources are assigned to ICT resources.
- the processing executed by the ICT resource management device 1 of this embodiment will be described with reference to FIG. 7. This process is started, for example, when there is a request from the service provider for an operation such as a configuration change regarding the connection of the device 5 that uses the cloud service to the physical node.
- the request acquisition unit 11 outputs order information indicating operations such as configuration change to the blueprint creation unit 12 (step S1).
- the blueprint creation unit 12 requests the configuration information from the configuration information management unit 13 (step S2).
- the configuration information management unit 13 outputs the configuration information stored in the configuration information DB 21, specifically, the physical layer configuration information 21a and the virtual layer configuration information 21b to the blueprint creation unit 12 (step S3). ..
- the cloud platform selection unit 12a of the blueprint creation unit 12 refers to the service management information 25 (FIG. 6) for the order information, selects a cloud platform that satisfies the conditions included in the order information, and selects the cloud platform.
- the result is output (step S3a).
- the blueprint creation unit 12 requests the mapping information 22 from the layer mapping unit 14 (step S4).
- the layer mapping unit 14 outputs the mapping information 22 to the blueprint creating unit 12 (step S5).
- the blueprint creating unit 12 creates a blueprint 24 for the order information based on the configuration information, the selected cloud platform, and the mapping information (step S6). At this time, the blueprint creating unit 12 selects a catalog required for the operation from the catalog group 23 according to the order information, and acquires the parameters to be input to the selected catalog from the order information or the distribution system 100.
- the blueprint creation unit 12 sends the created blueprint 24 to the service provider terminal 2 or the like that sent the order information via the request acquisition unit 11, and requests confirmation of the blueprint 24 (step S7). If there is no problem in confirming the blueprint 24, the request acquisition unit 11 transmits information indicating approval from the service provider terminal 2 or the like to the blueprint creation unit 12 (step S8). Steps S1 to S8 constitute an infrastructure design process in the entire process executed by the ICT resource management device 1. Note that steps S7 and S8 may be omitted in order to speed up the process.
- the blueprint creation unit 12 creates a script for executing orchestration based on the approved blueprint 24 (step S9). Techniques for creating scripts are well known, and detailed description thereof will be omitted.
- the blueprint creation unit 12 outputs the created script to the workflow execution unit 15 (step S10). Steps S9 to S10 constitute a script creation process in the entire process executed by the ICT resource management device 1.
- the workflow execution unit 15 interprets the script acquired from the blueprint creation unit 12 (step S11). Techniques for interpreting scripts are well known, and detailed description thereof will be omitted. Next, the workflow execution unit 15 instructs the API adapter unit 16 for each program that can be operated through the API (step S12) and executes the process.
- the API adapter unit 16 When the execution of the process is completed, the API adapter unit 16 notifies the workflow execution unit 15 of the completion of the process execution (step S13). Next, the workflow execution unit 15 notifies the blueprint creation unit 12 of the completion of the process execution (step S14).
- the completion of the process execution means the completion of the orchestration execution from the ICT resource management device 1 to the virtual layer, and the service after the configuration change is available. Steps S11 to S14 constitute an orchestration process in the entire process executed by the ICT resource management device 1.
- the monitoring unit 17 starts monitoring the physical nodes on the physical layer and the virtual nodes on the virtual layer.
- the monitoring unit 17 notifies the configuration information management unit 13 of the information collected by the monitoring (step S15).
- the configuration information management unit 13 notifies the layer mapping unit 14 of the information collected from the monitoring unit 17 (step S16).
- Steps S15 to S16 constitute a monitoring process in the entire process executed by the ICT resource management device 1.
- the configuration information management unit 13 generates configuration information from the information collected by the monitoring unit 17, and stores it in the configuration information DB 21.
- the layer mapping unit 14 also generates mapping information 22 from the information collected by the monitoring unit 17 via the configuration information management unit 13. The generated configuration information and mapping information 22 is used to create a new blueprint.
- the ICT resource management device 1 can hold the configuration information and the mapping information 22 in the latest state, so that the blueprint is created, the orchestration is executed, and the operation is performed without human intervention. Can be automated. In addition, it is possible to automate the selection of the optimum cloud infrastructure in response to operation requests such as configuration changes.
- the present embodiment it is possible to select an optimal cloud platform that meets the needs of a service provider without human work, and perform orchestration that is a resource allocation to ICT resources on the selected cloud platform. Can be executed. Therefore, the operating cost can be reduced by improving the work efficiency when the service provider can provide the cloud service.
- the service management information 25 it is possible to provide a concrete means for selecting a cloud infrastructure.
- program It is also possible to create a program in which the processing executed by the ICT resource management device 1 according to the above-described embodiment is described in a computer-executable language. In this case, the computer executes the program to obtain the same effect as that of the above embodiment. Furthermore, the same processing as that in the above-described embodiment may be realized by recording such a program in a computer-readable recording medium and causing the computer to read and execute the program recorded in the recording medium.
- An example of a computer that executes an ICT resource management program that realizes the same function as the ICT resource management device 1 will be described below.
- FIG. 8 is a diagram showing a computer that executes an ICT resource management program.
- the computer 1000 has, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.
- the memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM (Random Access Memory) 1012.
- the ROM 1011 stores, for example, a boot program such as BIOS (Basic Input Output System).
- BIOS Basic Input Output System
- the hard disk drive interface 1030 is connected to the hard disk drive 1090.
- the disk drive interface 1040 is connected to the disk drive 1100.
- a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1100.
- a mouse 1110 and a keyboard 1120 are connected to the serial port interface 1050, for example.
- a display 1130 is connected to the video adapter 1060, for example.
- the memory 1010, the hard disk drive 1090, the disk drive 1100, and the storage medium inserted into the disk drive 1100 are specific hardware resources of the storage unit included in the ICT resource management device 1.
- the hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094.
- Each table described in the above embodiment is stored in, for example, the hard disk drive 1090 or the memory 1010.
- the ICT resource management program is stored in the hard disk drive 1090 as a program module in which a command executed by the computer 1000 is described, for example.
- the program module in which each process executed by the ICT resource management device 1 described in the above embodiment is described is stored in the hard disk drive 1090.
- the data used for information processing by the ICT resource management program is stored as program data in, for example, the hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the hard disk drive 1090 into the RAM 1012 as necessary, and executes the above-described procedures.
- the program module 1093 and the program data 1094 related to the ICT resource management program are not limited to being stored in the hard disk drive 1090, and may be stored in a removable storage medium, for example, by the CPU 1020 via the disk drive 1100 or the like. It may be read.
- the program module 1093 and the program data 1094 related to the ICT resource management program are stored in another computer connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network), and the network interface 1070 It may be read by the CPU 1020 via the.
- the configuration information management unit 13 can manage the position information of the physical node.
- the configuration information management unit 13 can manage information regarding a user who uses the device 5 connected to the edge 4 as a physical node, or information regarding a tenant of the user. Therefore, the configuration information managed as the physical layer configuration information 21a can be the configuration information for each user or each tenant.
- the layer mapping unit 14 maps the physical layer and the virtual layer, the configuration information in units of users or units of tenants can be configuration information managed as the virtual layer configuration information 21b.
- a plurality of ICT resource management devices 1 of this embodiment may be provided for each cloud platform. In this case, the ICT resource management device for each cloud platform can be exchanged to select the optimal cloud platform.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Control Of Heat Treatment Processes (AREA)
Abstract
Description
したがって、サービス事業者がサービスを提供可能とする際の作業効率を向上させることで運用コストを低減することができる。
図1に示すように、本実施形態のICT資源管理装置1を含む分散システム100は、仮想化技術が適用されるシステムであり、ICT資源管理装置1と、サービス事業者端末2と、サーバ3と、エッジ4,4-1と、デバイス5,5-1とを備える。エッジ4-1は、複数存在するエッジ4の1つであり、エッジ4,4-1をまとめてエッジ4とする場合がある。また、デバイス5-1は、複数存在するデバイス5の1つであり、デバイス5,5-1をまとめてデバイス5とする場合がある。また、分散システム100は、物理ノードの集合体となる物理レイヤと、物理ノード上に構成されて稼働する仮想ノードの集合体となる仮想レイヤとを管理することができる。サーバ3と、エッジ4と、デバイス5は、物理レイヤを構成する物理ノードとなる。また、図1に示す、仮想レイヤ上に配置されているVM(Virtual Machine)7は、サーバ3またはエッジ4を仮想化した仮想ノードである。
サービス事業者端末2は、初期デプロイやスケール可変などの構成変更を要求する端末である。サービス事業者端末2は、当該要求をAPI(Application Programming Interface)を通じて行う。当該APIは、ICT資源管理装置1とサービス事業者端末2との間のNorthbound APIである。また、サービス事業者端末2は、サービス事業者が用いる。
また、ICT資源管理装置1は、仮想レイヤに対してオーケストレーションを実行することができる。具体的には、サービスのデプロイや、VM7へのリソース割り当てをすることができる。
図2に示すように、ICT資源管理装置1は、要求取得部11と、ブループリント作成部12と、構成情報管理部13と、レイヤマッピング部14と、ワークフロー実行部15と、APIアダプタ部16と、監視部17といった機能部を備える。ブループリント作成部12は、クラウド基盤選定部12aを備える。また、ICT資源管理装置1は、構成情報DB21と、マッピング情報22と、カタログ群23と、ブループリント24と、サービス管理情報25を記憶部で記憶する。ICT資源管理装置1が備える前記記憶部は、例えば、ICT資源管理装置1の内部にあってもよいし、ICT資源管理装置1の外部の装置にあってもよい。
要求取得部11は、サービス事業者端末2からの構成変更の要求を取得する。要求取得部11が取得した要求を「オーダ情報」と呼ぶ場合がある。また、構成変更の要求は、サービス事業者端末2に限らず、例えば、分散システム100の保守者の端末からも行うことができる。サービス事業者端末2、および、保守者の端末は、外部装置の例となる。
ブループリント作成部12は、要求取得部11が取得したオーダ情報に対応するブループリント24を作成する。ブループリント24は、要求された構成変更に必要となるインフラの設計情報である。インフラは、サービスの動作環境の構成要素を示し、例えば、ICT資源そのもの、ICT資源の設定情報(例:VM名、IPアドレス、ホスト名)や割当リソース、NW上に設定されるLB(ロードバランサ)、FW(ファイアウォール)、コンテナといったさまざまな要素を指す。
構成情報管理部13は、ICT資源に関する情報を構成情報として管理する。構成情報管理部13は、例えば、リソース情報収集のAPIにアクセスすることで、物理ノードおよび仮想ノードに関する情報を収集することができる。リソース情報収集のAPIとは、オーケストレーション対象がそれぞれに用意するリソース情報を提供するためのAPIである。リソース情報収集のAPIは、ICT資源管理装置1とオーケストレーション対象との間のsouthbound APIである。収集する情報は、例えば、SNMP(Simple Network Management Protocol)によるMIB(Management Information Base)とすることができるが、これに限定されない。構成情報管理部13が管理する構成情報は、構成情報DB21に格納されており、物理レイヤ構成情報21aと、仮想レイヤ構成情報21bに分類される。
オーケストレーション対象は、物理ノードおよび仮想ノードを含むが、これらに限定されない。オーケストレーション対象が提供するインタフェースは、例えば、当該オーケストレーション対象を制御するコントローラ(図示せず)が提供することもできるし、物理ノードおよび仮想ノードの各々が提供することもできる。
「状態」の管理項目には、対象の物理ノードの稼働状態が格納される(正常の場合「OK」、故障の場合「NG」)。
「ホスト名」の管理項目には、対象の物理ノードのホスト名が格納される。
「IPアドレス」の管理項目には、対象の物理ノードに割り当てられたIPアドレスが格納される。
「VMID」の管理項目には、対象の物理ノード上で稼働するVMの識別子が格納される。
「利用サービス」の管理項目には、対象の物理ノードで利用可能なサービスの識別子が格納される。利用サービスは、例えば、クラウドサービス、エッジコンピューティングサービスがあるが、これらに限定されない。また、利用サービスには、複数の物理ノードで同一のサービスを提供可能となるサービスを含めることができる。
「利用者」の管理項目には、対応の「利用サービス」に示すサービスを利用する利用者の識別子が格納される。利用者は、例えば、法人であってもよいし、個人であってもよい。また、例えば、該当の物理ノードがエッジ装置であった場合、当該エッジ装置の所有者のみを利用者とすることができる。
「クラウド基盤ID」の管理項目には、対象の物理ノードが属するクラウド基盤の識別子が格納される。
また、物理レイヤ構成情報21aの管理項目として、対象の物理ノードに用いるリソースプールの名称、IDを設定することができる。
また、物理レイヤ構成情報21aの管理項目として、対象の物理ノードが配置されるネットワークの型、ID、名称を設定することができる。
また、物理レイヤ構成情報21aの管理項目として、対象の物理ノードが用いるフォルダのID、型、名称を設定することができる。
また、物理レイヤ構成情報21aの管理項目として、対象の物理ノードが使用するデータストアの記憶容量、ID、型、名称を設定することができる。
また、物理レイヤ構成情報21aの管理項目として、対象の物理ノードを制御するデータセンタのID、名称を設定することができる。
また、物理レイヤ構成情報21aの管理項目として、対象の物理ノードにアクセスするユーザの認証情報となるユーザ名、パスワードを設定することができる。
「状態」の管理項目には、対象の稼働ノードの稼働状態が格納される(正常の場合「OK」、故障の場合「NG」)。
「VM名」の管理項目には、対象の仮想ノードの名称が格納される。
「IPアドレス」の管理項目には、対象の仮想ノードに割り当てられたIPアドレスが格納される。
「物理デバイスID」の管理項目には、対象の仮想ノードが配置される物理ノードの識別子が格納される。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードのリソースとなるメモリサイズ、CPU周波数を設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードの電源状態を設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードにアクセスするユーザの認証情報となるユーザ名、パスワードを設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードが使用するゲートウェイ、VXLAN(Virtual eXtensible Local Area Network)、スタティックルートを設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードが配置される物理ノードのホスト名を設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードを生成するハイパバイザに関する情報を設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードが用いるコンテナで提供されるサービスのID、名称、状態、スケール(利用サーバの台数)を設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードが用いるコンテナで提供されるストレージ装置のボリュームのマウント、ID(RancherNFS(Network File System)利用時のみ)、イメージIDを設定することができる。
また、仮想レイヤ構成情報21bの管理項目として、対象の仮想ノードが用いるコンテナで提供されるストレージ装置のスタックのグループ、ヘルス状態、スタックID、利用されるサービスのIDを設定することができる。
ブループリント作成部12が備えるクラウド基盤選定部12aは、クラウドサービスを実現する複数のクラウド基盤のうち、クラウドサービスを利用するデバイスの物理ノードへの接続に関する構成変更の要求に含まれる条件を満たすクラウド基盤を選定する。選定したクラウド基盤の識別子は、物理レイヤ構成情報21aの一部を構成する。クラウド基盤選定部12aは、ブループリント作成部12の一部機能であり、例えば、リソース情報収集のAPIにアクセスし、収集した情報を解決することで、選定したクラウド基盤を特定することができる。
なお、本実施形態では、クラウドサービスを実現するクラウド基盤を選定する場合について説明するが、本発明は、クラウドサービスではないサービスについても適用することができる。つまり、クラウド基盤に代えて、クラウドサービスではないサービスを実現するサービス基盤を選定する場合にも本発明はあてはまる。本実施形態のクラウド基盤選定部12aは、サービス基盤を選定するサービス基盤選定部の具体例となる。
また、クラウド基盤選定部12aは、ICT資源管理装置1のどこにあってもよいが、ここでは一例としてブループリント作成部12に備えることとする。
図2に戻って、レイヤマッピング部14は、物理レイヤと仮想レイヤとのマッピングを行う。具体的には、レイヤマッピング部14は、構成情報管理部13が管理する構成情報に基づいて、仮想レイヤ上の仮想ノードが物理レイヤ上のいずれの物理ノード(または当該物理ノード配置されたアプリ6)に紐付けられているかを判定する。ICT資源管理装置1は、レイヤマッピング部14による、物理ノードと仮想ノードとの紐付けの判定結果を、マッピング情報22として保存する。例えば、レイヤマッピング部14は、物理レイヤ構成情報21a(図3)の「VMID」の管理項目と、仮想レイヤ構成情報21b(図4)の「物理デバイスID」の管理項目を参照することで、物理ノードと仮想ノードとの紐付けを判定することができる。
ワークフロー実行部15は、ブループリント作成部12が作成したブループリント24に従って、ワークフローを実行する。ワークフローは、ブループリント24に含まれるカタログが示す工程を、順序を定めて連結したものである。図5に示す初期デプロイのブループリント24に対しては、初期デプロイのワークフローは、VM作成→NW設定→コンテナ設定、のように順序を定めて連結したものとなる。ワークフロー実行部15がワークフローを実行することで、オーケストレーションが実行され、ICT資源にリソースが割り当てられる。
APIアダプタ部16は、ワークフローを実行するワークフロー実行部15からの命令に対し、APIを通じ操作することができるプログラムにアクセスするためのインタフェースである。当該APIは、APIアダプタ部16(またはAPIアダプタ部16を備えるICT資源管理装置1)とオーケストレーション対象との間のsouthbound APIである。APIアダプタ部16は、オーケストレーション対象ごとにインタフェース接続することができる。APIアダプタ部16は、APIを通じ操作することができるプログラムごとに複数用意することができる。ワークフロー実行部15は、APIを通じ操作することができるプログラムを実行することで、ワークフローを実行することができる。
ワークフロー実行部15およびAPIアダプタ部16の組合せは、オーケストレーションを実行するオーケストレータ部として機能する。
監視部17は、物理レイヤ上の物理ノード、および、仮想レイヤ上の仮想ノードを、例えば、SNMPによって監視する。監視部17による監視結果は、オーケストレーションが実行され、利用可能となったサービスの使用状況を示している。監視部17による監視結果は、構成情報管理部13に送信することができる。構成情報管理部13は、監視部17の監視結果で、物理ノードおよび仮想ノードに関する情報を収集することができる。
サービス管理情報25は、分散システム100によって利用されているサービス(ネットワークサービス、クラウドサービス、など)の管理情報である。図6に示すように、サービス管理情報25は、例えば、「サービスID」、「クラウド基盤ID」、「種別」、「使用アプリ」、「料金」、「品質」、「提供エリア」、「接続サービスID」、「動作ICT資源」といった管理項目を有し、サービスごとに各管理項目の値が格納されている。サービス管理情報25が有する上記の複数種類の管理項目は、クラウドサービスを利用するデバイスの物理ノードへの接続に関する構成変更の要求に含まれる複数種類の条件に対応している。これらの条件は、サービス事業者が要望する条件となる。
「クラウド基盤ID」の管理項目には、対象のサービスを実現するクラウド基盤の識別子が格納される。
「種別」の管理項目には、対象のサービスの種別を示す情報が格納される。格納される情報は、例えば、コンピューティングサービス、ストレージサービス、ビッグデータサービス、機械学習サービスを示す情報とすることができるが、これに限定されない。
「使用アプリ」の管理項目には、対象のサービスが提供されるために使用されるアプリ6-1~6-3の識別子が格納される。換言すれば、使用アプリとは、対象のサービスの内容を構成するアプリケーションである。
「品質」の管理項目には、対象のサービスの品質を示す情報が格納される。格納される情報は、例えば、サービスに設定されたSLA(Service Level Agreement)を示す情報とすることができるが、これに限定されない。
「提供エリア」の管理項目には、対象のサービスが提供されるエリア、つまり、デバイス5が当該サービスを利用可能となるエリアを示す情報が格納される。格納される情報は、例えば、エッジ4を中心にして半径○キロメートル以内のエリア、都内全体を示す情報とすることができるが、これに限定されない。
本実施形態のICT資源管理装置1が実行する処理を、図7を参照して説明する。この処理は、例えば、サービス事業者からの申込みに対する、クラウドサービスを利用するデバイス5の物理ノードへの接続に関する構成変更等のオペレーションの要求があった場合に開始する。
ステップS1~ステップS8は、ICT資源管理装置1が実行する処理全体のうち、インフラ設計の処理を構成する。
なお、処理を迅速にするため、ステップS7、ステップS8は、省略してもよい。
ステップS9~ステップS10は、ICT資源管理装置1が実行する処理全体のうち、スクリプト作成の処理を構成する。
ステップS11~ステップS14は、ICT資源管理装置1が実行する処理全体のうち、オーケストレーションの処理を構成する。
ステップS15~ステップS16は、ICT資源管理装置1が実行する処理全体のうち、監視の処理を構成する。
また、構成変更等のオペレーションの要求に対し、最適なクラウド基盤の選定を自動化することができる。
したがって、サービス事業者がクラウドサービスを提供可能とする際の作業効率を向上させることで運用コストを低減することができる。
特に、サービス管理情報25を参照することで、クラウド基盤の選定の具体的手段を提供することができる。
また、上記実施形態に係るICT資源管理装置1が実行する処理をコンピュータが実行可能な言語で記述したプログラムを作成することもできる。この場合、コンピュータがプログラムを実行することにより、上記実施形態と同様の効果を得ることができる。さらに、かかるプログラムをコンピュータ読み取り可能な記録媒体に記録して、この記録媒体に記録されたプログラムをコンピュータに読み込ませて実行することにより上記実施形態と同様の処理を実現してもよい。以下に、ICT資源管理装置1と同様の機能を実現するICT資源管理プログラムを実行するコンピュータの一例を説明する。
(a)構成情報管理部13は、物理ノードの位置情報を管理することができる。
(b)構成情報管理部13は、物理ノードとしてのエッジ4に接続しているデバイス5を使用するユーザに関する情報、または、ユーザのテナントに関する情報を管理することができる。よって、物理レイヤ構成情報21aとして管理される構成情報は、ユーザ単位またはテナント単位の構成情報とすることができる。レイヤマッピング部14が、物理レイヤと仮想レイヤとのマッピングを行った場合、ユーザ単位またはテナント単位の構成情報は、仮想レイヤ構成情報21bとして管理される構成情報とすることができる。
(c)本実施形態のICT資源管理装置1は、クラウド基盤ごとに複数備えてもよい。この場合、クラウド基盤ごとのICT資源管理装置間でやりとりして、最適なクラウド基盤を選定することができる。
1 ICT資源管理装置
2 サービス事業者端末
3 サーバ
4 エッジ
5 デバイス
6 アプリ(アプリケーション)
7 VM
11 要求取得部
12 ブループリント作成部
12a クラウド基盤選定部(サービス基盤選定部の具体例)
13 構成情報管理部
14 レイヤマッピング部
15 ワークフロー実行部(オーケストレータ部)
16 APIアダプタ部(オーケストレータ部)
17 監視部
21 構成情報DB
21a 物理レイヤ構成情報
21b 仮想レイヤ構成情報
22 マッピング情報
23 カタログ群
24 ブループリント
25 サービス管理情報
Claims (4)
- ICT資源となる、物理ノードおよび仮想ノードを管理するICT資源管理装置であって、
物理レイヤ上の前記物理ノードに関する構成情報である物理レイヤ構成情報、および、仮想レイヤ上の前記仮想ノードに関する構成情報である仮想レイヤ構成情報を管理する構成情報管理部と、
サービスを利用するデバイスの前記物理ノードへの接続に関する構成変更の要求に対して、前記サービスを実現する複数のサービス基盤のうち、前記要求に含まれる条件を満たすサービス基盤を選定するサービス基盤選定部と、
前記物理レイヤおよび前記仮想レイヤとのマッピングを行うレイヤマッピング部と、
前記構成変更の要求に対して、前記物理レイヤ構成情報、前記仮想レイヤ構成情報、前記選定したサービス基盤、および、前記マッピングの結果であるマッピング情報に基づいて、前記構成変更に必要なインフラの設計情報となるブループリントを作成するブループリント作成部と、
前記ブループリントに基づいて、APIを通じ操作することができるプログラムにアクセスして実行することで、前記仮想レイヤに対するオーケストレーションを実行するオーケストレータ部と、を備える、
ことを特徴とするICT資源管理装置。 - 前記サービス基盤選定部は、前記条件に対応する複数種類の管理項目を用いてサービスを管理するサービス管理情報を参照して、前記条件を満たす前記サービス基盤を選定する、
ことを特徴とする請求項1に記載のICT資源管理装置。 - ICT資源となる、物理ノードおよび仮想ノードを管理するICT資源管理装置におけるICT資源管理方法であって、
前記ICT資源管理装置は、
物理レイヤ上の前記物理ノードに関する構成情報である物理レイヤ構成情報、および、仮想レイヤ上の前記仮想ノードに関する構成情報である仮想レイヤ構成情報を収集するステップと、
サービスを利用するデバイスの前記物理ノードへの接続に関する構成変更の要求に対して、前記サービスを実現する複数のサービス基盤のうち、前記要求に含まれる条件を満たすサービス基盤を選定するステップと、
前記物理レイヤおよび前記仮想レイヤとのマッピングを行うステップと、
前記構成変更の要求に対して、前記物理レイヤ構成情報、前記仮想レイヤ構成情報、前記選定したサービス基盤、および、前記マッピングの結果であるマッピング情報に基づいて、前記構成変更に必要なインフラの設計情報となるブループリントを作成するステップと、
前記ブループリントに基づいて、APIを通じ操作することができるプログラムにアクセスして実行することで、前記仮想レイヤに対するオーケストレーションを実行するステップと、を実行する、
ことを特徴とするICT資源管理方法。 - コンピュータを、請求項1または請求項2に記載のICT資源管理装置として機能させるためのICT資源管理プログラム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/299,652 US11886927B2 (en) | 2018-12-04 | 2019-11-25 | ICT resource management device, ICT resource management method and ICT resource management program |
AU2019393437A AU2019393437B2 (en) | 2018-12-04 | 2019-11-25 | ICT resource management device, ICT resource management method and ICT resource management program |
JP2020559062A JP7056760B2 (ja) | 2018-12-04 | 2019-11-25 | Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム |
SG11202105891XA SG11202105891XA (en) | 2018-12-04 | 2019-11-25 | Ict resource management device, ict resource management method and ict resource management program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2018-227540 | 2018-12-04 | ||
JP2018227540 | 2018-12-04 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020116223A1 true WO2020116223A1 (ja) | 2020-06-11 |
Family
ID=70973766
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2019/045934 WO2020116223A1 (ja) | 2018-12-04 | 2019-11-25 | Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム |
Country Status (6)
Country | Link |
---|---|
US (1) | US11886927B2 (ja) |
JP (1) | JP7056760B2 (ja) |
AU (1) | AU2019393437B2 (ja) |
SG (1) | SG11202105891XA (ja) |
TW (1) | TWI787562B (ja) |
WO (1) | WO2020116223A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111800506A (zh) * | 2020-07-06 | 2020-10-20 | 深圳市网心科技有限公司 | 一种边缘计算节点部署方法及相关装置 |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210117313A1 (en) * | 2019-10-16 | 2021-04-22 | Minnim Software | Language agnostic automation scripting tool |
CN117234882B (zh) * | 2023-09-28 | 2024-04-16 | 哈尔滨工业大学(威海) | 一种在线应用云资源供应软件定义模型构建方法及终端机 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015056182A (ja) * | 2013-09-13 | 2015-03-23 | 株式会社Nttドコモ | ネットワーク仮想化のための方法及び装置 |
JP2018032897A (ja) * | 2016-08-22 | 2018-03-01 | 日本電信電話株式会社 | 事業者間一括サービス構築装置及び事業者間一括サービス構築方法 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9052961B2 (en) | 2012-03-02 | 2015-06-09 | Vmware, Inc. | System to generate a deployment plan for a cloud infrastructure according to logical, multi-tier application blueprint |
US10949903B2 (en) | 2017-05-05 | 2021-03-16 | Servicenow, Inc. | System, computer-readable medium, and method for blueprint-based cloud management |
US10761871B2 (en) * | 2017-11-14 | 2020-09-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparratus for secrets injection into containers |
US11960940B2 (en) * | 2018-05-29 | 2024-04-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Performance of function as a service |
-
2019
- 2019-11-25 SG SG11202105891XA patent/SG11202105891XA/en unknown
- 2019-11-25 WO PCT/JP2019/045934 patent/WO2020116223A1/ja active Application Filing
- 2019-11-25 US US17/299,652 patent/US11886927B2/en active Active
- 2019-11-25 JP JP2020559062A patent/JP7056760B2/ja active Active
- 2019-11-25 AU AU2019393437A patent/AU2019393437B2/en active Active
- 2019-12-03 TW TW108144068A patent/TWI787562B/zh active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015056182A (ja) * | 2013-09-13 | 2015-03-23 | 株式会社Nttドコモ | ネットワーク仮想化のための方法及び装置 |
JP2018032897A (ja) * | 2016-08-22 | 2018-03-01 | 日本電信電話株式会社 | 事業者間一括サービス構築装置及び事業者間一括サービス構築方法 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111800506A (zh) * | 2020-07-06 | 2020-10-20 | 深圳市网心科技有限公司 | 一种边缘计算节点部署方法及相关装置 |
CN111800506B (zh) * | 2020-07-06 | 2023-09-19 | 深圳市网心科技有限公司 | 一种边缘计算节点部署方法及相关装置 |
Also Published As
Publication number | Publication date |
---|---|
AU2019393437A1 (en) | 2021-06-24 |
JP7056760B2 (ja) | 2022-04-19 |
TWI787562B (zh) | 2022-12-21 |
US20220035681A1 (en) | 2022-02-03 |
US11886927B2 (en) | 2024-01-30 |
AU2019393437B2 (en) | 2022-08-18 |
TW202037131A (zh) | 2020-10-01 |
JPWO2020116223A1 (ja) | 2021-09-27 |
SG11202105891XA (en) | 2021-07-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8370481B2 (en) | Inventory management in a computing-on-demand system | |
JP6819296B2 (ja) | 仮想化管理・オーケストレーション装置、仮想化管理・オーケストレーション方法、および、プログラム | |
US9152293B2 (en) | Server IP addressing in a computing-on-demand system | |
US10326668B2 (en) | Portable and flexible deployment of servers | |
US8271653B2 (en) | Methods and systems for cloud management using multiple cloud management schemes to allow communication between independently controlled clouds | |
JP7056759B2 (ja) | Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム | |
CN105379185B (zh) | 用于创建和管理网络群组的方法和系统 | |
WO2020116223A1 (ja) | Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム | |
US20120096149A1 (en) | Cloud federation in a cloud computing environment | |
JP2018519687A (ja) | クラウド・ネットワーキングのためのマルチテナント認識型動的ホスト構成プロトコル(dhcp)機構 | |
US20180004563A1 (en) | Orchestrator apparatus, system, virtual machine creation method, and computer-readable recording medium | |
EP3785424A1 (en) | Method and arrangement for licence management in nfv network environment | |
JP6393612B2 (ja) | システムのバックアップ装置及びバックアップ方法 | |
JP7115561B2 (ja) | Ict資源管理装置、ict資源管理方法、および、ict資源管理プログラム | |
US10992534B2 (en) | Forming groups of nodes for assignment to a system management server | |
US11423377B1 (en) | Lendable computing resources | |
WO2017022825A1 (ja) | 機能配置設計装置、方法、クラウドサービス仲介システム及びプログラム | |
US20230259405A1 (en) | Resource management device, resource managementmethod, and resource management program | |
CN115437728A (zh) | 一种云桌面设置方法、系统及设备 | |
Copeland et al. | Getting started with Azure virtual machines |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19894327 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2020559062 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019393437 Country of ref document: AU Date of ref document: 20191125 Kind code of ref document: A |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19894327 Country of ref document: EP Kind code of ref document: A1 |