Member-oriented hybrid cloud operating system architecture and communication method thereof

Patent metadata

Field	Value
Publication number	US-9307017-B2
Application number	US-201414534735-A
Country	US
Kind code	B2
Filing date	Nov 6, 2014
Priority date	Aug 22, 2013
Publication date	Apr 5, 2016
Grant date	Apr 5, 2016

Abstract

A member-oriented hybrid cloud operating system architecture and a communication method thereof are provided. A hybrid architecture is established based on layer, object and message models, and a member-oriented idea is applied to manage constituent members and a processing environment thereof. On this basis, high-efficient routing, read-write separation and load balancing are performed on a member processing cluster, satisfying the requirements of being open and compatible, loosely coupled and extensible of a cloud operating system, and solving the self-management problem, the horizontal scaling problem of members and the high-availability problem of stateful members of the existing cloud operating system.

First claim

What claimed is:

1. A member-oriented hybrid cloud operating system, wherein the system establishing a hybrid architecture based on layer, object and message models, and applying a member-oriented idea to manage constituent members and a processing environment thereof, and on this basis, the system performing high-efficient routing, read-write separation and load balancing on a member processing cluster, satisfying the requirements of being open and compatible, loosely coupled and extensible for a cloud operating system, and solving the self-management problem, the horizontal scaling problem of members and the high availability problem of stateful members of an existing cloud operating system,
from the perspective of a layer model, the system being divided into a portal layer, a logic layer, an adaptation layer and an implementation layer from top to bottom, with each layer being relatively independent, the openness being enhanced by respectively defining a standard interface at each layer, and the compatibility being enhanced by adapting different functions at various layers;
from the perspective of an object model, the cloud operating system being composed of the functional modules of a cloud portal, cloud management portal, cloud resource management, monitoring management, metering and billing, service approval, and authorization and authentication, various functional components performing communication by Rest message-based calling, capable of being combined with each other freely, and being distributed and deployed as required, a new module being able to be developed in a value-added manner as required, and the extensibility of a platform being enhanced by realizing interoperation among different modules in the logic layer, the cloud operating system which is installed in a minimized manner comprising only the modules of a cloud portal, cloud management portal and cloud resource management, on this basis, monitoring, billing, approval or other modules being customized and extended as required, performing communication by Rest message-based calling, and being distributed, deployed and developed in a value-added manner as required, and the extensibility of the system being enhanced by realizing interoperation among different modules in the logic layer; and a message-based communication being introduced to support asynchronous calling, and a message communication interface JMS being used to transmit a Rest message, thus making the system architecture further decoupled, and on this basis, a construction-oriented design being applied, and a member management portal being responsible for managing metadata of members and monitoring operation states thereof;
despite being able to realize extension, distribution and deployment as required, an object architecture belonging to an RPC (remote process call) synchronization communication manner, a sending end is able to continue execution after waiting for the response from a receiving end, and the processes of the two parties are closely coupled, and with the magnification and complication of the system, an association relationship among the members being over-complicated, regarding this problem, a message-based communication being introduced on the basis of the object architecture, a message communication interface JMS being used to transmit the Rest information, making the life periods of the sending and receiving ends different, supporting asynchronous calling and making the system structure further decoupled, at least the operations of turning on, shutting down and suspending of a virtual machine between a portal and a cloud resource layer being realized in an asynchronous manner, and the portal being able to return without the need to wait for a response after sending out a command, thus improving user interaction effects;
the cloud operating system based on the above-mentioned hybrid architecture being able to satisfy the requirements of openness, compatibility and extension, and on this basis, based on a construction-oriented design idea, the member management portal being responsible for managing metadata information about the members, supporting at least the operations of registration, deletion, modification and querying, wherein,
a member is a triple, comprising: a name, a service set, an access address, and a description;
a service is a quadruple, comprising: a name, a type, a message protocol, a parameter list, a key name, a functional description, and a non-functional description;
in addition to describing and managing the members, a member management module further monitors a processing environment thereof, provides a basic service for ensuring the scalability and availability of the members, and perfects the self-management capability of the cloud operating system, and when a member is registered, the system allocates a username user, a password psw and a unique member id thereto, and then an access process of a member processing cluster comprises:
1) the processing cluster initiating an access request to a system bus with an address being url, the system bus verifying a username, password and id of an access node, and if the verification is passed, establishing a connection, the code being:
connection=ConnectionFactory.createConnection(user,psw,url);
2) establishing a write operation topic, and each processing node of the member subscribing to a write operation from the topic;
write _topic=session,createTopic(id+“WRITE_TOPIC”);
write_topic_consumer=session.createConsumer(write_topic);
3) the member realizing write processing in an onMessage method of a writeTopicListener, and registering to the system bus;
write_topic 13 consumer.setMessagetistener(writeTopicListener);
4) establishing a read operation queue group according to the number mum of processing nodes of the member, each processing node corresponding to one queue subscription read operation
read_queue=session.createMultiQueue(num,id+“READ_QUEUE”);
read_queue_consumer=session.createConsumer(read_queue); and
5) realizing a specific read processing function in an onMessage method of a read QueueListener, and registering to the system bus
read_queue_consumer.setMessageListener(readQueueListener);
on the basis of the above-mentioned read-write separation queue groups, service types of various members are distinguished in the member management module, setting the service types as idempotent or non-idempotent, an idempotent operation belonging to an unstateful operation, the result of each execution in the same state being the same, and a non-idempotent operation belonging to a stateful operation, the result of each execution in the same state being different, a router performing routing according to the service type, the non-idempotent operation being sent to a unique write queue, and the idempotent operation being sent to different read queues according to a load balancing strategy;
a read operation load balancing process comprises
1) calculating a processing capability of a node;
if a CPU frequency, memory capacity and I/O bandwidth of a node i are respectively C i , M i and B i , various resources of a cluster being the sums of various resources of nodes, i.e., C=ΣC i , M=ΣM i , B=ΣB i ;
then a CPU weight value of the node i is W i CPU =C i /C, the memory capacity W i RAM =M i /M, and the I/O bandwidth W i IO =B i /B; and
if the required resource proportions of the member service are respectively p CPU , p RAM and p IO , the processing capability of the node i being
W i =p CPU W i CPU +p RAM W i RAM +p IO W i IO ;

2) calculating a load of each node according to a read-write operation weight value;
if a read-write operation overhead ratio of a read queue L r to a write queue L w is a, a load of the node i being L i =L R i +aL W and
a load state of each node being S i =L i /W i and
3) selecting a node with the li

Assignees

• Inspur Electronic Information Industry Co Ltd

Inventors

• Wang Endong
• Zhang Dong
• Liu Zhengwei
• Qi kaiyuan
• Liu Junpeng
• Guo Feng
• Liu Chenping
• Gao Fei
• Zhu Bo

Classifications

• G06Q10/06

  Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling · CPC title

• H04L67/1034

  Reaction to server failures by a load balancer · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/1008 Primary

  based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30) · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title