CN113128909A

CN113128909A - Server management method based on power resources

Info

Publication number: CN113128909A
Application number: CN202110521177.6A
Authority: CN
Inventors: 陈玉麟
Original assignee: Ruilin World Energy Saving Technology Beijing Co ltd
Current assignee: Ruilin World Energy Saving Technology Beijing Co ltd
Priority date: 2021-05-13
Filing date: 2021-05-13
Publication date: 2021-07-16

Abstract

The invention relates to a server management method based on power resources, which operates in a server management system and comprises the following steps: a view representation layer, a business logic layer and a data processing layer; the method comprises the steps that Javascript and JQuery are adopted for development, a business logic layer is developed through SSH and MVC, after a request sent by a view representation layer is received, the authority of an operator is verified, then corresponding power resource architecture and cloud server management business processing are carried out, and when the business processing of cloud server management is carried out, an ORM framework adopted by a data processing layer is SSH. The invention has large data information processing capacity and wide data coverage area, can effectively collect the operation information of units such as power supply, power transformation and distribution of each level in the power system, and can read and edit the unified power information according to the identity of a specific operator, thereby effectively improving the working efficiency of information transmission and exchange work in the power system and the safety of information exchange on the one hand.

Description

Server management method based on power resources

Technical Field

The invention belongs to the field of power resource management, and particularly relates to a server management method based on power resources, which is operated in a server management system.

Background

With the booming development of computers and the internet, cloud computing gradually changes the working modes of people and influences the evolution and change of the business model of the whole society. Most businesses digitize information for business processing. Based on the reason of high cost performance, the flexible cloud computing service is the first choice of enterprises. However, most enterprises have a complicated organization structure, which determines that it is important to separate and uniformly manage cloud resources between the subordinate stations and between tasks. Meanwhile, in order to ensure the data security of the cloud resource pool of the enterprise, the authority management of various operator roles inside the enterprise is also required.

The timeliness and the accuracy of the electric power information interaction are one of the important guarantees for ensuring the normal operation of the current electric power system, but in the actual operation, the information communication and management mode in the current electric power system is mainly assisted by telephone communication and a computer network system, although the requirements of the electric power communication and management can be met to a certain extent, the defects of untimely information communication, incomplete data communication coverage, inconsistent data statistical standards, low data statistical accuracy, low working efficiency of data collection and management and the like exist at the same time, so that great potential safety hazards are formed for the daily operation and management work of the electric power system, meanwhile, the current electric power information communication and management mode is easy to cause serious information leakage, and the information resource management has serious security holes, so that a brand new electric power communication resource management mechanism is urgently required to be developed for the current situation, to meet the requirements of practical use.

Disclosure of Invention

The invention relates to a server management method based on power resources, which operates in a server management system and is characterized in that the server management system comprises: a view representation layer, a business logic layer and a data processing layer;

the view representation layer is a Web interface, is developed by adopting Javascript and JQuery, is responsible for filtering an operation entrance without authority of an operator, receives a request sent by the operator and verifies the legality of the input of the operator, finally sends the request to the service logic layer, and displays data on a page after the service logic layer processes and returns corresponding data;

the service logic layer is developed by adopting SSH and MVC, after a request sent by the view representation layer is received, the authority of an operator is verified, then a corresponding power resource architecture and cloud server management service processing are carried out, when the service processing of cloud server management is carried out, a cloud eSDK interface needs to be called, the cloud server is connected to the cloud server through an SDK and cloud resources are managed, the service logic layer and the data processing layer can carry out data transmission, and relevant processing results are returned to the view representation layer;

a control interface is also arranged between the view representation layer and the service logic layer;

the ORM framework adopted by the data processing layer is SSH, the used database is MongoDB, and the data processing layer is mainly responsible for persisting data and synchronizing cloud resource data into the database;

the business logic layer comprises a cloud server management module and a power resource architecture module.

The system is generally designed, a cloud server management module and a power resource framework module are described, then database analysis and design are carried out, then the system is designed in detail, the system comprises an operation environment, a class diagram, a timing diagram and a specific description, coding development is carried out, and finally, careful function test and non-function test are carried out on the system; the invention has the advantages of large data information processing capacity, wide data coverage area, strong fault resistance, flexible, various, convenient and reliable data reading, managing and updating modes, capability of effectively collecting the operation information of units such as power supply, power transformation and distribution of each level in the power system, and reading and editing unified power information according to the identity of a specific operator, thereby effectively improving the work efficiency of information transmission and exchange work in the power system and the safety of information exchange on the one hand, and effectively ensuring the uniformity, authenticity and timeliness of data among units in the power system on the other hand, thereby achieving the purposes of improving the communication information resource management level of the power system and improving the authenticity and reliability of information transmission.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a block diagram illustrating an operating system of a server management method based on power resources according to the present invention.

Detailed Description

The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings and specific embodiments of the present invention, and it is to be understood that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The invention relates to a server management method based on power resources, which operates in a server management system, and is characterized in that the server management system comprises: a view representation layer, a business logic layer and a data processing layer;

Further, the cloud server management module provides an operation function of an operator on the cloud server, and the operation function at least includes adding a cloud server, releasing cloud server resources, checking cloud server information, changing cloud server settings, starting up, shutting down, restarting, adding a new cloud snapshot, recovering a new cloud snapshot, and deleting a cloud snapshot;

the power resource architecture module is provided with four management submodules, namely an operator management submodule, a role management submodule, a subordinate post management submodule and a task management submodule, which are used for managing the enterprise organization architecture and personnel and providing different operation authorities for different operator roles. The method comprises the following steps of inquiring information of operators, modifying information of the operators, adding the operators, deleting the operators, recovering the deleted operators, inquiring information of roles, modifying information of roles, adding roles, deleting roles, inquiring information of subordinate stations, changing names of the subordinate stations, adding the subordinate stations, deleting the subordinate stations, obtaining information of tasks, changing names of the tasks, adding the tasks, deleting the tasks, adding the members of the tasks and deleting the members of the tasks.

Furthermore, in the power resource architecture module, the relationship between roles and operators is many-to-many, wherein one operator can simultaneously select different role identities, and different operators can exist under one role identity. The relation between roles and authorities is many-to-many, wherein a contact set of setting authorities exists between the roles, different authorities can be set for a certain role, and a certain authority can also be set to different roles. The relationship between the membership post and the operators is one-to-many, i.e. there can be different operators for a certain membership post, and for a certain operator it can only belong to a certain membership post. The relationship between the membership post and the task is also one-to-many, that is, for a certain membership post, it can have different tasks under it, and for a certain task, it can only belong to a certain membership post. Task-to-task member group relationships are one-to-one in that a task has a particular one of the member groups. The relation between the task member group and the operators is many-to-many, wherein a contact set of setting members exists between the task member group and the operators, and for different operators in a certain member group, a certain operator can join in different member groups.

In the cloud server management module, the relationship between the membership posts and the cloud servers is one-to-many, wherein one membership post can own different cloud servers, and one cloud server can only belong to a specific membership post. The relationship between the tasks and the cloud servers is also one-to-many, namely, a certain task can own different cloud servers, and a certain cloud server can only belong to a certain specific task. The relation stored between the cloud server and the cloud snapshots is one-to-many, wherein a certain cloud server can have different snapshots, and a certain snapshot only belongs to a certain specific cloud server.

And obtaining a plurality of main database tables at least comprising a cloud server information table, a cloud snapshot information table, a membership post information table, a role information table, a permission information table, an operator and role relation table, a task information table and a task member group table based on the database structure of the entity contact model.

Furthermore, JSON is adopted between the view representation layer and the control interface for data transmission. The control interface is responsible for receiving a request sent by the front end, and the naming mode of the □ is according to a certain specification, usually in a module name + Controller form, and the control interface receives parameters transmitted by the front end and performs specific service processing;

the naming mode of the interface between the control interface and the business logic layer is usually the form of module name + Operator, module name + Service, module name + Driver, in the cloud server management module, after the Operator layer receives the parameters transmitted by the control interface, the business logic layer and the driving layer are called to respectively process,

the service logic layer is responsible for performing service processing, the driving layer is responsible for calling the eSDK interface to operate cloud server resources, and the service logic layer performs service processing after receiving parameters transmitted by the control interface in the power resource architecture module;

the naming mode of the interface between the business logic layer and the data processing layer is usually in a form of module name + Dao, the business logic layer calls the Dao layer to process data, and the Dao layer performs database operation through SSH.

Further, the server management system comprises a plurality of interfaces, and the plurality of interfaces are at least used for inquiring information of a certain operator, inquiring information of a certain cloud server and acquiring cloud snapshot information.

Furthermore, the power resource architecture module comprises an operator management function, a membership post management function, a role management function and a task management function;

the operator management function comprises inquiring operator information, adding operators, modifying the operator information, deleting the operators and recovering the deleted operators;

the query of the operator information is to display brief information of the operator in a list according to different query conditions, and then to obtain specific information of the operator by clicking a 'view details' button;

the OperatoComroller is a class for receiving operator-related requests sent by the front end and is responsible for interacting with the front end, and each method in the class corresponds to a different front end request. The method in the OperatorController class checks the legality of operation (if it has authority, whether the deletion meets the requirement, etc.), then calls the OperatorService class to process the request specifically, and finally returns the processing result, the OperatorService class is responsible for the operation related to the operator, after receiving the Model parameter transmitted by the Operatontroller class, it can call other Service classes, such as RoleService class, and call the OperatorDato class, the OperatDato class is responsible for the database operation related to the operator, after receiving the Entity transmitted by the OperatorService, the database is operated, the OperatorEntity is the operator Entity class corresponding to the database operator table, the OperatorModel is used to transmit the parameter between layers, and the attribute is basically the same as the OperatorEntity. Because the operator is planned under the membership position, when deleting the membership position, it needs to first confirm that no normal operator exists in the membership position and the subordinate membership position thereof, so the OperaterDao class needs to realize a method of determining whether a normal operator exists in the membership position in the interface IDeptResourceCock.

When the operator information is modified, whether the operator information has the operation authority is checked, whether the parameters transmitted by the foreground are legal is checked, then, the operator service is called to change the data of the operator, and finally, the change result is returned to the foreground;

the adding of the operators is to automatically add the mapping of the operators and the roles in the middle table operator _ role;

the deletion operator modifies the attribute is _ deleted in the operator table and sets the mapping data of the operator, the task member group and the role to be null;

based on the safety consideration of data, the function does not directly delete the operator data in the database, but changes the operator into a historical operator, essentially modifies the attribute is _ deleted in the operator table, and nulls the mapping data of the operator and the task member group and role. Thus, if the misoperation of the operator is reduced, the reduced operator can be recovered to save. The timing diagram shows the message interaction between the operator and the system. The back end part code is as follows:

v/check whether it has the authority to delete the operator

boolean hasPrivilege = operatorPrivilegeCheck.checkOperatorDel(delId， curOperator);

V/checking whether the deleted operator is an operator

if(!hasPrivilege || curOperator.getId() == delld){

If the operator without operation authority or deleted operator is the same as the current operator, returning error information

}

V/checking whether the operator is on task

List<TaskModel> p = taskService.getTaskListByOperatorld(delld);

if(!p.isEmpty()){

// return to the task group where the operator exists and print the log

}

Delector, delete operator

Invoking OperatorDao, OperatorGroupService in the deleerator method to change the operator's associated data;

the recovery deleted operators reinsert the mapping data of the operators and the roles, change part of data in an operator table and change historical operators into normal operators;

the role management function comprises the steps of inquiring role information, adding roles, modifying role information and deleting roles;

the RoleController is a class for receiving role-related requests sent by the front end and is responsible for interacting with the front end. The method in RoleController class checks the legality of operation (such as if it has authority, whether deletion meets the requirement or not), calls RoleService class to process the request specifically, and returns the processing result, RoleService class is responsible for processing role-related Service, after receiving the Model parameter transferred by RoleController class, it can call other Service classes such as OptorService class, etc. and call RoleDao class, RoleDao class is responsible for operating database, after receiving the entity parameter transferred by RoleService, it can operate database through SSH, PrivilegeService mainly responsible for authority query Service, PrivigeDao class is responsible for authority-related database query, RoleEntity is the entity class of role, corresponding to the role information table in database, PrivigeEntity is the entity class of authority, corresponding to the authority table ege in database, RoleEntity class has members in RoleType class, the RoleType is used for transferring the RoyleEntity layer parameter with the same as the Model parameter, the latter property is substantially the same as the PrivilegeEntity.

The adding of the role inserts the relationship between the authority and the role, and if the number of the authority is large, the adding of the role takes some time. In order to improve the experience of operators, the method is designed to be asynchronous, and the same-name role can be added only one at any time and can be modified after the addition is finished. The rollercontroller can check whether the authority and the parameters transmitted by the foreground are legal, then the rollervice can call an external interface (task management interface) to check whether the unfinished task exists, so as to judge whether the role is newly added or modified, and finally the external interface is called to create the asynchronous task.

When the asynchronous task is executed, whether the asynchronous task is newly added or modified is judged, then a permission set List < PrivilegeEntity > of the role is constructed according to the parameters, and finally the role data is persisted into a database. When the back-end executes the task, the front-end page sends a request for checking the uncompleted role task every 2 seconds, and a success prompt window is popped up until the role is successfully added. After the role page pops "role in the middle" the next events in the two timing diagrams are concurrent. The back end part code is as follows:

v/determining whether a role is being added or modified by task name

String taskName = "createOrUpadateRoIe"+rModel.getName〇;

if(! (tasklteml nterface. getTaskLi stByName(taskName). isEmpty ())) {

// Return to "role is being added or modified" to the front desk and print an error log

}

CreateOrUpdateRoleParam param = new CreateOrUpdateRoleParam(rModel，

pModel)// constructing parameters for asynchronous tasks

Creation and scheduling of asynchronous tasks by task factory

createOrUpdateRoleFactory.scheduleCommandCreateOrUpdateRoIe(param);

Part of the code for the asynchronous task is as follows:

list < PrivilegeEntity > privList = new ArrayList < > (),/construct the set of permissions

for(PrivilegeModel priviModel: pModel){

PrivilegeEntity p = priviService.getByEnLabel(priviModel.getEnLabel〇);

if (null! = pM// pass the English string of the privilege to verify whether the privilege exists in the database

priviList.add(p);

Else {// setting the state of the asynchronous task to fail }

}

if (null = rolemodel. getid ()) {// judges whether to add or modify, if no Id, it is added

RoleEntity rEntity = new RoleEntity();

// some set () method of rEntity is omitted here, and the attribute of rEntity is populated according to roleModel

rEntity.setPrivilege(priviList);

Createneentity (rEntity)// inserting data in a database

// set asynchronous task status to success

} else {// Modify role }

In order to ensure the system safety, the authority information table privilege in the system is only used as inquiry authority data, and the functions of adding, deleting and modifying the data in the privilege table through a front-end page by an operator do not exist, so that a Controller class does not need to be created for the authority.

The membership post management function comprises inquiring membership post information, newly adding membership posts, changing names of the membership posts and deleting the membership posts;

the task management function comprises the steps of acquiring task information, adding a task, changing a task name, deleting a task, adding a task member and deleting a task member.

The newly added task member function can newly add a plurality of members at one time, so that some time can be spent, the newly added task member function is designed to be asynchronous operation, a member group can only be operated by one operator at any time, and other operators cannot newly add the members before the newly added operation is not completed. The TaskController checks whether the authority and the parameters transferred by the foreground are legal, and then the TaskService calls a method of an external interface (task management interface) to judge whether the member group is being newly added, and finally, an asynchronous task is created. When the asynchronous task is executed, whether the added members and the added task are under the same primary membership position needs to be judged one by one, and then an addOperators method of the operator group service is called to add the members. Here, 2 sequence diagrams of the function are shown, and the backend inserts member data into the database in an asynchronous manner. Meanwhile, the front-end page sends a request for inquiring about uncompleted tasks every 2 seconds until the member is successfully added, and a success prompt window is popped up. After the task member page pops "new addition", the next events in the two timing diagrams occur at the same time. The back end part code is as follows:

i/check if the task group is adding a member

String taskName = "addTaskOperators"+pId;

if(!(taskItemInterface.getTaskListByName(taskName).isEmpty())){

// return "newly added Member" to the foreground and print error Log

}

V/constructing parameters of asynchronous task

AddProOperatorTaskParam taskParam = new AddProOperatorTaskParam(operators， task);

Creation and scheduling of asynchronous tasks by task factory

addProOperatorsFactory.scheduleCommandAddProOperators( taskParam);

The back-end portion code of the asynchronous task is as follows:

StringBuffer error Msg = new StringBuffer (), the variable is used for recording error information

OccupationModel root = departimentservice. getroot (),/get root belonging to post

// find task's first-level membership post

OccupationModel levelOne = root.findLevelOne(task.getOccupationId〇);

List < Long > List = new ArrayList good component (),/find all subordinate posts under the subordinate post

list = OccupationService.getAllIdsByLevelOne(levelOne.getId〇);

for(OperatorModel operator : operators) {

if (null | = operator service. getoperator byid (operator. getid ()) {// the operator presence {/operator

V/checking whether the operator and the task belong to the same first-class membership post

if (| list. contacts (). getId ()) {// recording error information

Aprengd (operator. getId good + "operator and task non-identical first level membership position #") }

Else { error msg. ap pend (operator. getid () + "operator does not exist #") ]// record error information

}// end cycle

if(errorMsg.length〇!=0){

Set the result of the asynchronous task to fail and save the contents of errorMsg into the task result

}else{

operator group personal services addoperators, tasks, operators, new task members

Setting the result of the asynchronous task to success

}

Further, the newly-added cloud server adopts asynchronous operation, polls the generation state of the cloud server, updates related data into a database, sends a request for inquiring uncompleted tasks at preset time intervals on a front-end page until the cloud server is successfully added, pops up a success prompt window, and pops up 'the cloud server is being newly added' on the cloud server page;

the cloud server is released, the releasing progress of the cloud server is polled by adopting asynchronous operation, relevant data are updated into a database, a front-end page sends a request for inquiring uncompleted tasks at preset time intervals until the cloud server is successfully released, a successful prompt is popped up, and a 'releasing in progress' is popped up on the cloud server page;

the starting, the shutdown and the restart are used for circularly inquiring whether the cloud server is operated successfully or not;

the examination query cloud server information can be examined according to the name and ID conditions, and by clicking an examination query information button, the inquiry jumps to a detail page, namely the query can firstly examine the current data of the cloud server, the examination query does not need to generate a remote task, the data is directly returned, then the database is updated, and finally the data is returned to the foreground;

and the cloud server setting change comprises changing the size of a cloud server memory and a CPU (central processing unit), polling whether the task is successful, and then modifying the database.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. The manager management system includes: a view representation layer, a business logic layer and a data processing layer;

2. A method for power resource based server management as claimed in claim 1, wherein:

the cloud server management module provides an operation function of an operator on the cloud server, and at least comprises cloud server adding, cloud server resource releasing, cloud server information examination and query, cloud server setting changing, starting, shutdown, restart, new cloud snapshot adding, cloud snapshot restoring and cloud snapshot deleting;

the power resource architecture module is provided with four management submodules, namely an operator management submodule, a role management submodule, a subordinate post management submodule and a task management submodule, which are used for managing the enterprise organization architecture and personnel and providing different operation authorities for different operator roles.

3. The method comprises the following steps of inquiring information of operators, modifying information of the operators, adding the operators, deleting the operators, recovering the deleted operators, inquiring information of roles, modifying information of roles, adding roles, deleting roles, inquiring information of subordinate stations, changing names of the subordinate stations, adding the subordinate stations, deleting the subordinate stations, obtaining information of tasks, changing names of the tasks, adding the tasks, deleting the tasks, adding the members of the tasks and deleting the members of the tasks.

4. A method for power resource based server management as claimed in claim 1, wherein:

the power resource architecture module and the cloud server management module adopt a database structure of an entity contact model, and the relationship between roles and operators in the power resource architecture module is many-to-many; the relationship between the membership post and the operator is one-to-many; the relationship between the membership posts and the tasks is one-to-many; the task and task member group relationship is one-to-one; the relationship between the task member group and the operator is many-to-many;

in the cloud server management module, the relationship between the membership posts and the cloud servers is one-to-many; the relationship between the tasks and the cloud servers is also one-to-many; the relation stored between the cloud server and the cloud snapshot is one-to-many;

5. A method for power resource based server management as claimed in claim 1, wherein:

JSON is adopted between the view representation layer and the control interface for data transmission.

6. The control interface is responsible for receiving a request sent by the front end, and the naming mode of the □ is according to a certain specification, usually in a module name + Controller form, and the control interface receives parameters transmitted by the front end and performs specific service processing;

7. A method for power resource based server management as claimed in claim 1, wherein:

the server management system comprises a plurality of interfaces, and the plurality of interfaces are at least used for inquiring information of a certain operator, inquiring information of a certain cloud server and acquiring cloud snapshot information.

8. A method for power resource based server management as claimed in claim 1, wherein:

the power resource architecture module comprises an operator management function, a subordinate post management function, a role management function and a task management function;

9. A method for power resource based server management as claimed in claim 2, wherein:

and the newly-added cloud server adopts asynchronous operation, polls the generation state of the cloud server, updates related data into a database, and sends a request for inquiring uncompleted tasks at preset time intervals on a front-end page until the cloud server is successfully added and pops up a success prompt window.

10. Popping up a cloud server page that the cloud server is in the process of being newly added;