CN102789392A - Method for constructing power system distributed platform - Google Patents
Method for constructing power system distributed platform Download PDFInfo
- Publication number
- CN102789392A CN102789392A CN2012102124457A CN201210212445A CN102789392A CN 102789392 A CN102789392 A CN 102789392A CN 2012102124457 A CN2012102124457 A CN 2012102124457A CN 201210212445 A CN201210212445 A CN 201210212445A CN 102789392 A CN102789392 A CN 102789392A
- Authority
- CN
- China
- Prior art keywords
- lxc
- distributed platform
- file
- distributed
- operating system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Multi Processors (AREA)
Abstract
The invention provides a method for constructing a power system distributed platform. The method comprises the following steps of: constructing a virtual distributed assembly, arranging a distributed platform, and setting a distributed platform management subsystem. The method achieves all functions of the whole distributed platform with less resource consumption and achieves one-key completion of start-up and stop of the platform, so as to increase the operating speed; provides simple and practical functions of program updating, platform monitoring, task submission and viewing, so as to finally achieve the effect of space-saving and system easy-to-use properties of the distributed platform; and positions the mirror image on a notebook computer to complete development, test and demonstration of related programs and systems in the single computer environment by use of the distributed platform. The distributed platform is mobile.
Description
Technical field
The invention belongs to the electric system simulation technical field, be specifically related to a kind of electric system distributed platform construction method.
Background technology
Intel Virtualization Technology is popular in recent years computer technology, and it is meant to use and operates in the virtual hardware environment, can expand hardware capabilities through Intel Virtualization Technology, simplifies the configuration deployment process of software.Virtualized technology has a variety of, comprises that operating system is virtual, and application program is virtual; Desktop virtual; Storage Virtualization, network virtualization etc., the virtual operating system that is meant that we are often referred to is virtual; Promptly on a machine, fictionalize a plurality of operating systems (also can be server virtualization) because fictionalize the main frame of SOS.Operating system is virtual also divides multiplely, comprises fully virtualizedly, and half is virtual, and operating system grade is virtual.Fully virtualized is between hardware and client operating system, to have a middle layer (being called VMM, Virtual Machine Manager).The complete analog hardware of VMM, Guest OS need not do any change.It is fully virtualized that to be divided into traditional and hardware again auxiliary; Traditional is virtual fully, and virtual machine operates on the operating system, and the Virtual Machine Manager program itself operates in the Ring 0 of cpu; Virtual Guest OS then operates in Ring 1; But so the compatibility of Guest can be affected, and the instruction that will on Ring 0, carry out of original Guest OS all must pass through hypervisor and translate and could move, and speed can descend to some extent.And the auxiliary complete virtual cpu hardware supports that needs of hardware has two kinds of technology of AMD-V of VT and the AMD of intel, has only the cpu of these two kinds of technology of support just can use.Auxiliary virtual of hardware itself is put into the mode operation also lower than Ring 0 (such as Ring-1) to the Virtual Machine Manager program, and is put into Ring 0 to Guest OS, and compatibility is improved like this.Half virtual a kind of code of revising Guest OS part access privileges state is so that direct and the mutual technology of VMM; Need make amendment to the code of Guest OS; The part hardware interface offers Client OS with the form of software; This can provide through the mode of Hypercall (VMM offers directly calling of Guest OS, and is similar with system call), can improve the efficient of virtual machine like this.Virtual being meant of operating system grade fictionalizes the operating system that several are isolated fully on operating system, it is a kind of Intel Virtualization Technology of lightweight, and efficient is high, but can only simulate the operating system of the same type with Host os.
On unit, use a lot of of virtual machine at present; On unit, use the quite a few of several virtual machines,, also can constitute cluster through network configuration; But make up cluster like this; The one, it is bigger to take up room, because each operating system all is operating system independently, does not have the part of sharing between them.The 2nd, each operating system all needs to start separately, control respectively, and startup stops all can not accomplishing one-key operation.The 3rd, this Intel Virtualization Technology efficient is lower.Therefore, we adopt the virtual structure of realizing virtual distributed cluster of operating system grade.Usually distributed platform all is to run on the operating system of same type, and the virtual characteristics that can only simulate operating system of the same type of operating system grade have no influence to us.
(LXC) linux container is exactly a kind of Intel Virtualization Technology of operating system grade.Be based on the Intel Virtualization Technology of (SuSE) Linux OS.It can provide the virtual of lightweight, so that isolated process and resource, and instruction interpretation mechanism and other fully virtualized complicacy need be provided.Container effectively will be by the resource division of single operating management in isolated group, with better between isolated group balance the resource user demand of conflict is arranged.Compare with virtual, so neither need instruction level simulation, also do not need instant compiling.Container can instruct at the core CPU local runtime, and without any need for special explanation facility.In addition, also avoided complicacy in half virtual and the system call replacement.Through a kind of mode of creating and getting into container is provided, operating system lets application program just as operation on machine independently, but can share the resource of a lot of bottoms.For example, can share the caching of page of public documents (such as glibc) effectively, because all containers all use identical kernel, and all containers are also usually shared identical libc storehouse (depending on the container configuration).This share usually can expand to that other need not write the file of content in the catalogue.Container also through sharing these resource savings expenses, this means that container is much littler than real virtualized expense when isolation is provided.Linux Container provides and has supported that on single controlled host node the server container of a plurality of mutual isolation carries out simultaneously, and Linux Container is picture chroot a bit, and a virtual environment that has own process and cyberspace is provided.LXC provides the object of user's space through the new features (CGroup) of utilizing kernel, is used for guaranteeing the isolation of resource and for using or the resource control of system, through namespaces resource isolation is provided.
Come emulation electric system actual moving process to become the main flow of electric system simulation through computing machine, early stage model is simple owing to the electric system small scale, and therefore single user just can accomplish data maintenance and simulation analysis on unit.Along with the formation of transregional interconnected network and the continuous expansion of scale of power; The operational process of electrical network becomes increasingly complex; The simulation calculation amount is also increasing, and the simulation calculation of unit has been difficult to satisfy work requirements, therefore; Distributed Calculation is applied in the electric system simulation field, and many companies have developed distributed platform.Generally, distributed platform is deployed on many actual machine in the cluster, and actual distributed type assemblies can not arbitrarily move; For outside company, using developing of distributed platform, test, the staff of demonstration relative program and system; It is a very big problem; Some company particularly, intranet and extranet separate, and can only in company, use distributed platform.For the situation of the non-actual deployment distributed platform performance test relevant, need not dispose distributed platform through the cluster of reality with carrying out distributed platform.In actual use; Carry out the distributed platform development& testing, and the development& testing of the program (bottom core calculations program, interface) of relevant distributed system; Demonstrate the system that is with distributed platform to the user, this part work occupies the overwhelming majority that distributed platform uses.Therefore, design and research can realize movably distributed platform in the method for unit deploy distributed platform, can give exploitation, and the system of test and demonstration band distributed platform brings great convenience.
Summary of the invention
In order to overcome the deficiency of above-mentioned prior art; The present invention provides a kind of electric system distributed platform construction method; Make whole distributed platform dispose and consume minimum storage space, start and stop to realize robotization, one-key operation; And provide succinct easy-to-use program updates, platform monitoring, task to submit to and look facility, finally realize saving in space property and system's ease for use of distributed platform.
In order to realize the foregoing invention purpose, the present invention takes following technical scheme:
A kind of electric system distributed platform construction method said method comprising the steps of:
Step 1: make up virtual distributed cluster;
Step 2: the deployment of distributed platform;
Step 3: distributed platform ADMINISTRATION SUBSYSTEM.
In the said step 1, make up virtual distributed cluster through LXC.
Said step 1 may further comprise the steps:
Step 1-1: on the virtual machine unit, (SuSE) Linux OS is installed;
Step 1-2: the root file system that makes up LXC;
Step 1-3: host operating system is set;
Step 1-4: LXC is set;
Step 1-5: start LXC.
All connect between said host operating system and the LXC, between LXC and the LXC and realize communication through bridge.
Said step 1-2 may further comprise the steps:
Step 1-2-1: confirm the position of the root file system of LXC in the file system of host operating system;
Step 1-2-2: the root file system of copy host operating system.
Said step 1-3 may further comprise the steps:
Step 1-3-1: LXC user's attitude instrument is installed;
Step 1-3-2: the bridge between configuration host operating system and the LXC;
Step 1-3-3: the inspection host operating system /the etc/fstab file, guarantee in the host operating system carry/cgroup;
Step 1-3-4: the configuration file of writing LXC configuration file and LXC carry file system;
Step 1-3-5: the virtual unit of creating LXC.
Said step 1-4 may further comprise the steps:
Step 1-4-1: switch in the root file system of LXC;
Step 1-4-2: empty LXC /the etc/fstab file;
Step 1-4-3: deletion LXC network interface card configuration file;
Step 1-4-4: revise LXC and start the configuration file script;
Step 1-4-5: inspection/etc/inittab file;
Step 1-4-6: being provided with needs the service of startup simultaneously when LXC starts;
Step 1-4-7: revise host name and root password;
Step 1-4-8:LXC configuration finishes and withdraws from.
Said step 2 may further comprise the steps:
Step 2-1: create domestic consumer;
Step 2-2: copy the needed profile template of distributed platform, library file and executable file to corresponding catalogue;
Step 2-3: revise configuration, authority is set, write the startup script.
Said step 3 may further comprise the steps:
Step 3-1: submit to professional: calculation procedure is sent to computing node from this machine through scheduling node, and the frequency that the task of setting is then regularly submitted to is submitted to scheduling node with task;
Step 3-2: platform resource monitoring; The resource of checking distributed platform through scheduling node, and show return results at display interface;
Step 3-3: calculation task monitoring; Obtain the task that computing node is calculating through scheduling node, turn back to display interface and show;
Step 3-4: off-line results management; Finishing of task is calculated in inquiry on scheduling node, turns back to interface display, deletes unwanted task, the associated documents on the automatic deletion of node of distributed platform;
Step 3-5: check online result; After current task was calculated and finished, the automatic return results of distributed platform meeting turned back to display interface and shows.
Compared with prior art, beneficial effect of the present invention is:
1. the present invention realizes all functions of whole distributed platform with less resource consumption, and for the startup of platform with stop to realize one-key operation, speed speeds operations;
2. provide succinct easy-to-use program updates, platform monitoring, task to submit to and look facility, finally realize saving in space property and system's ease for use of distributed platform;
3. mirror image is placed on the notebook computer, can easily realizes utilizing developing of distributed platform at stand-alone environment, test, demonstration relative program and system realize the distributed platform that moves.
Description of drawings
Fig. 1 is a distributed platform ADMINISTRATION SUBSYSTEM structural drawing in the embodiment of the invention;
Fig. 2 is a distributed platform ADMINISTRATION SUBSYSTEM functional schematic in the embodiment of the invention;
Fig. 3 is that calculation task is submitted business process map in the embodiment of the invention;
Fig. 4 is platform resource monitoring business flowpath figure in the embodiment of the invention;
Fig. 5 calculates the Mission Monitor business process map in the embodiment of the invention;
Fig. 6 is an off-line results management business process map in the embodiment of the invention;
Fig. 7 checks online result set business process map in the embodiment of the invention.
Embodiment
Below in conjunction with accompanying drawing the present invention is done further explain.
Like Fig. 1, a kind of electric system distributed platform construction method said method comprising the steps of:
Step 1: make up virtual distributed cluster;
Step 2: the deployment of distributed platform;
Step 3: distributed platform ADMINISTRATION SUBSYSTEM.
In the said step 1, make up virtual distributed cluster through LXC.
Said step 1 may further comprise the steps:
Step 1-1: (SuSE) Linux OS centos 6 is installed on virtual machine unit VirtualBOX;
Step 1-2: the root file system that makes up LXC; Virtual root file system is an independently root file system of virtual opetrating system, and is isolated with other virtual root file systems.We adopt the file system of copy host main frame to realize;
Step 1-3: host operating system is set;
Step 1-4: LXC is set;
Step 1-5: start LXC.
All connect between said host operating system and the LXC, between LXC and the LXC and realize communication through bridge.
Said step 1-2 may further comprise the steps:
Step 1-2-1: confirm the position of the root file system of LXC in the file system of host operating system; Selection/lxc/${container_name}; Carry out mkdir-p/lxc/${container_name}, also can be placed on other catalogues such as (/var/lxc/${container_name}) in, LXC selects cpt; Container_name=cpt therefore, Actual path is/lxc/cpt.
Step 1-2-2: the root file system of copy host operating system; Close selinux, otherwise can report an error during copy/selinux catalogue.Editor/etc/selinux/config changes SELINUX=enforcing into SELINUX=disabled, restarts virtual machine then.With centos6 is example, following catalogue: bin is arranged, cgroup, etc, lib, lost+found, mnt, proc, sbin, srv, tmp, var, boot, dev, home, lib64, media, opt, root, selinux, sys, usr after centos minimal bag is installed.Do not copy sys, proc, the dev catalogue is only created sys, proc, the dev catalogue because these three catalogues do not exist on certain disk of disk, but is produced in internal memory by core.All the other catalogues are all copied over, do not copy the catalogue/lxc at container root file system place.
Said step 1-3 may further comprise the steps:
Step 1-3-1: LXC user's attitude instrument is installed; Comprise gcc, the software package of lxc-0.7.5 and dependence creaties directory: after mkdir-p/usr/local/var/lib/lxc/ is used to deposit the lxc-create command execution, and the configuration file that LXC generates.
Step 1-3-2: the bridge between configuration host operating system and the LXC; Communicate by letter the network interface card configuration file under the modification/etc/sysconfig/network-scripts/ catalogue through bridge between host operating system and LXC.Establishment/etc/sysconfig/network-scripts/ifcfg-br0; Corresponding D EVICE is set; Options such as IPADDR, modification/etc/sysconfig/network-scripts/ifcfg-eth0 file removes contents such as IPADDR; BRIDGE=br0 is set, restarts network/etc/init.d/network restart then.
Step 1-3-3: the inspection host operating system /the etc/fstab file, guarantee in the host operating system carry/cgroup; Guarantee in host's file system carry/cgroup, otherwise during with lxc-start order container, can report the spawn mistake.Will host operating system /add none/cgroup cgroup defaults 00 this delegation among the etc/fstab.
Step 1-3-4: the configuration file of writing LXC configuration file and LXC carry file system; The LXC title need be set, the network type of container, the ip address of container, the path of the fake root file system of container etc.
Need carry/lxc/cpt/proc, catalogues such as/lxc/cpt/sys can not carry { $rootfs}/var/lock/subsys; { $rootfs}/var/run; Otherwise when container started, these two catalogues can be hidden, and reported an error when container is started; But this type mistake is not a significant errors, and the major function that can not influence container is used.
If container has started the nfs related service, need carry/lxc/cpt/var/lib/nfs/rpc_pipefs, the carry statement is following: sunrpc/lxc/cpt/var/lib/nfs/rpc_pipefs rpc_pipefs defaults 00.
Step 1-3-5: the virtual unit of creating LXC; Because the container inoperative is on the hardware of reality, thus need to create virtual unit, through the mknod order at/lxc/cpt/dev/ establishment console down, pts, shm, equipment such as tty are like mknod-m 666/lxc/cpt/dev/null c 13.
Other system equipment comprises modification host name, modification/etc/hosts etc.
Said step 1-4 may further comprise the steps:
Step 1-4-1: switch in the root file system of LXC; Switch to chroot and to be easy to carry out in the fake root file system: chroot/lxc/cpt/bin/bash.
Step 1-4-2: empty LXC /the etc/fstab file; Because when container started, lxc-start can be according to configuration file/lxc/fstab.cpt carry.Carry out: rm-f/etc/fstab; Touch/etc/fstab.
Step 1-4-3: deletion LXC network interface card configuration file; Lxc-start can start Microsoft Loopback Adapter according to configuration file/lxc/cpt.conf.Carry out: rm-f/etc/sysconfig/network-scripts/ifcfg-eth0.
Step 1-4-4: revise LXC and start the configuration file script; Container starts and the practical OS's startup still has many difference.A lot of statements do not need to carry out, for centos, and modification/etc/rc.d/rc.sysinit.Generally be to remove original, write again, need that suffix is the file of pid under the deletion/var/run, and/ file under the var/lock/subsys/*, empty/the etc/mtab file, statement is following: rm-f$ (find/var/run-name'*pid'); Rm-f/var/lock/subsys/*; Rm-f/etc/mtab; Touch/etc/mtab.
Step 1-4-5: inspection/etc/inittab file; Guarantee to start from level 3, statement is following: id:3:initdefault:.
Step 1-4-6: being provided with needs the service of startup simultaneously when LXC starts; With chkconfig order opening and closing related service.
Step 1-4-7: revise host name and root password; Editor/etc/sysconfig/network revises value behind the HOSTNAME and be the host name of the container of oneself setting.Carry out the password order, revise the root password.Modification/etc/hosts file, the corresponding relation of configure host name and ip.
Step 1-4-8:LXC configuration finishes and withdraws from; Carry out exit.
Step 1-5 may further comprise the steps:
Step 1-5-1: create;
lxc-create?-n?cpt?-f/lxc/cpt.conf。Lxc-create must use-f parameter specified configuration file, otherwise the configuration file of the container of creating is empty (/usr/local/var/lxc/cpt/config is for empty); After creating successfully, can in/usr/local/var/lxc/, generate associative directory and file.
Step 1-5-2: start; Foreground initiation: lxc-start-n cpt.The backstage starts: lxc-start-n-d cpt.
Step 1-5-3: stop; Lxc-stop-n cpt.
Common distributed platform all is by one or more management node, and one or more computing node constitutes, and the distributed platform of our independent development minimizes and disposes is a scheduling node and a computing node; Be that minimum is two nodes; If be used for the test interface program, need a scheduling node, a computing node; With a computing node, i.e. three nodes.Each node need operate in independently on the operating system.Therefore our two containers are added host's node, constitute the cluster of three nodes.
Said step 2 may further comprise the steps:
Step 2-1: create domestic consumer;
Step 2-2: copy the needed profile template of distributed platform, library file and executable file to corresponding catalogue;
Step 2-3: revise configuration, authority is set, write the startup script.
Basic configuration step is following:
1) earlier with the login of root identity, and creating a ndsa group and ndsa user.
#groupadd?ndsa
#useradd-m?ndsa-g?ndsa
2) switch to ndsa user, decompress after compressed package is copied to root directory, this compressed package comprises the relevant configuration file of distributed platform, library file, executable file.
#su-ndsa
ndsa:~>tar?xvfz?dist2010.tgz
3) revise the platform relevant configuration, write startup and stop script.
System management subsystem accomplishes mainly that a key starts virtual distributed platform and related service on the unit, and the platform program update functions is provided, and the platform monitoring function is submitted calculation task to and checked function as a result.Whole ADMINISTRATION SUBSYSTEM mainly uses technology such as struts, spring, jni.
Like Fig. 1-2, through host's main frame of container /relevant startup command is set in the etc/rc.local file, in the time of can realizing starting virtual machine, start whole distributed platform, and relevant supervisory routine.Starting container and starting needs several seconds at interval between the distributed platform, because the startup of container needs spended time.
Like Fig. 3-7, said step 3 may further comprise the steps:
Step 3-1: submit to professional: calculation procedure is sent to computing node from this machine through scheduling node, and the frequency that the task of setting is then regularly submitted to is submitted to scheduling node with task;
Step 3-2: platform resource monitoring; The resource of checking distributed platform through scheduling node, and show return results at display interface;
Step 3-3: calculation task monitoring; Obtain the task that computing node is calculating through scheduling node, turn back to display interface and show;
Step 3-4: off-line results management; Finishing of task is calculated in inquiry on scheduling node, turns back to interface display, deletes unwanted task, the associated documents on the automatic deletion of node of distributed platform;
Step 3-5: check online result; After current task was calculated and finished, the automatic return results of distributed platform meeting turned back to display interface and shows.
Should be noted that at last: above embodiment is only in order to technical scheme of the present invention to be described but not to its restriction; Although the present invention has been carried out detailed explanation with reference to the foregoing description; Under the those of ordinary skill in field be to be understood that: still can specific embodiments of the invention make amendment or be equal to replacement; And do not break away from any modification of spirit and scope of the invention or be equal to replacement, it all should be encompassed in the middle of the claim scope of the present invention.
Claims (9)
1. electric system distributed platform construction method is characterized in that: said method comprising the steps of:
Step 1: make up virtual distributed cluster;
Step 2: the deployment of distributed platform;
Step 3: distributed platform ADMINISTRATION SUBSYSTEM.
2. electric system distributed platform construction method according to claim 1 is characterized in that: in the said step 1, make up virtual distributed cluster through LXC.
3. electric system distributed platform construction method according to claim 2, it is characterized in that: said step 1 may further comprise the steps:
Step 1-1: on the virtual machine unit, (SuSE) Linux OS is installed;
Step 1-2: the root file system that makes up LXC;
Step 1-3: host operating system is set;
Step 1-4: LXC is set;
Step 1-5: start LXC.
4. electric system distributed platform construction method according to claim 3 is characterized in that: all connect through bridge between said host operating system and the LXC, between LXC and the LXC and realize communication.
5. electric system distributed platform construction method according to claim 3, it is characterized in that: said step 1-2 may further comprise the steps:
Step 1-2-1: confirm the position of the root file system of LXC in the file system of host operating system;
Step 1-2-2: the root file system of copy host operating system.
6. electric system distributed platform construction method according to claim 3, it is characterized in that: said step 1-3 may further comprise the steps:
Step 1-3-1: LXC user's attitude instrument is installed;
Step 1-3-2: the bridge between configuration host operating system and the LXC;
Step 1-3-3: the inspection host operating system /the etc/fstab file, guarantee in the host operating system carry/cgroup;
Step 1-3-4: the configuration file of writing LXC configuration file and LXC carry file system;
Step 1-3-5: the virtual unit of creating LXC.
7. electric system distributed platform construction method according to claim 3, it is characterized in that: said step 1-4 may further comprise the steps:
Step 1-4-1: switch in the root file system of LXC;
Step 1-4-2: empty LXC /the etc/fstab file;
Step 1-4-3: deletion LXC network interface card configuration file;
Step 1-4-4: revise LXC and start the configuration file script;
Step 1-4-5: inspection/etc/inittab file;
Step 1-4-6: being provided with needs the service of startup simultaneously when LXC starts;
Step 1-4-7: revise host name and root password;
Step 1-4-8:LXC configuration finishes and withdraws from.
8. electric system distributed platform construction method according to claim 1, it is characterized in that: said step 2 may further comprise the steps:
Step 2-1: create domestic consumer;
Step 2-2: copy the needed profile template of distributed platform, library file and executable file to corresponding catalogue;
Step 2-3: revise configuration, authority is set, write the startup script.
9. electric system distributed platform construction method according to claim 1, it is characterized in that: said step 3 may further comprise the steps:
Step 3-1: submit to professional: calculation procedure is sent to computing node from this machine through scheduling node, and the frequency that the task of setting is then regularly submitted to is submitted to scheduling node with task;
Step 3-2: platform resource monitoring; The resource of checking distributed platform through scheduling node, and show return results at display interface;
Step 3-3: calculation task monitoring; Obtain the task that computing node is calculating through scheduling node, turn back to display interface and show;
Step 3-4: off-line results management; Finishing of task is calculated in inquiry on scheduling node, turns back to interface display, deletes unwanted task, the associated documents on the automatic deletion of node of distributed platform;
Step 3-5: check online result; After current task was calculated and finished, the automatic return results of distributed platform meeting turned back to display interface and shows.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102124457A CN102789392A (en) | 2012-06-21 | 2012-06-21 | Method for constructing power system distributed platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102124457A CN102789392A (en) | 2012-06-21 | 2012-06-21 | Method for constructing power system distributed platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102789392A true CN102789392A (en) | 2012-11-21 |
Family
ID=47154800
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012102124457A Pending CN102789392A (en) | 2012-06-21 | 2012-06-21 | Method for constructing power system distributed platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102789392A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105183558A (en) * | 2015-08-26 | 2015-12-23 | 北京元心科技有限公司 | Intelligent terminal and management method for container system thereof |
| CN106407101A (en) * | 2015-07-31 | 2017-02-15 | 三亚中兴软件有限责任公司 | LXC-based continuous integration method and apparatus |
| CN106686158A (en) * | 2017-02-19 | 2017-05-17 | 郑州云海信息技术有限公司 | Method and device of mutual trust communication among severs |
| CN107302475A (en) * | 2017-07-06 | 2017-10-27 | 郑州云海信息技术有限公司 | The method of testing and device of a kind of Based on Distributed storage cluster |
| CN109144526A (en) * | 2018-06-28 | 2019-01-04 | 国网山东省电力公司菏泽供电公司 | A kind of rapid deployment system and method for automation of transformation substations software |
| CN109977075A (en) * | 2019-03-19 | 2019-07-05 | 北京椒图科技有限公司 | A kind of file store path acquisition methods and device |
| CN110569043A (en) * | 2019-09-06 | 2019-12-13 | 程延辉 | Multi-user kbroker distributed operating system and multi-user management system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090044185A1 (en) * | 2007-08-08 | 2009-02-12 | Innopath Software, Inc. | Workflow-Based User Interface System for Mobile Devices Management |
| CN101789886A (en) * | 2009-01-23 | 2010-07-28 | 中兴通讯股份有限公司 | Environment setup automation system of distribution type environment and method |
-
2012
- 2012-06-21 CN CN2012102124457A patent/CN102789392A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090044185A1 (en) * | 2007-08-08 | 2009-02-12 | Innopath Software, Inc. | Workflow-Based User Interface System for Mobile Devices Management |
| CN101789886A (en) * | 2009-01-23 | 2010-07-28 | 中兴通讯股份有限公司 | Environment setup automation system of distribution type environment and method |
Non-Patent Citations (2)
| Title |
|---|
| LININGBO_LNB: "centos6 minimal版本下配置lxc", <HTTP://WENKU.BAIDU.COM/VIEW/EABC5647A8956BEC0975E34E.HTML> * |
| 弋瑞录等: "基于LSF集群系统的分布式并行计算", <测控技术> * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106407101A (en) * | 2015-07-31 | 2017-02-15 | 三亚中兴软件有限责任公司 | LXC-based continuous integration method and apparatus |
| CN105183558A (en) * | 2015-08-26 | 2015-12-23 | 北京元心科技有限公司 | Intelligent terminal and management method for container system thereof |
| CN105183558B (en) * | 2015-08-26 | 2018-11-16 | 北京元心科技有限公司 | The management method of intelligent terminal and its containment system |
| CN106686158A (en) * | 2017-02-19 | 2017-05-17 | 郑州云海信息技术有限公司 | Method and device of mutual trust communication among severs |
| CN107302475A (en) * | 2017-07-06 | 2017-10-27 | 郑州云海信息技术有限公司 | The method of testing and device of a kind of Based on Distributed storage cluster |
| CN109144526A (en) * | 2018-06-28 | 2019-01-04 | 国网山东省电力公司菏泽供电公司 | A kind of rapid deployment system and method for automation of transformation substations software |
| CN109144526B (en) * | 2018-06-28 | 2022-04-12 | 山东鲁软数字科技有限公司智慧能源分公司 | Rapid deployment system and method for substation automation software |
| CN109977075A (en) * | 2019-03-19 | 2019-07-05 | 北京椒图科技有限公司 | A kind of file store path acquisition methods and device |
| CN110569043A (en) * | 2019-09-06 | 2019-12-13 | 程延辉 | Multi-user kbroker distributed operating system and multi-user management system |
| CN110569043B (en) * | 2019-09-06 | 2023-04-25 | 程延辉 | Multi-user kbook distributed operating system and multi-user management system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190347127A1 (en) | Service provisioning and orchestration for virtual machine to container migration | |
| US11146620B2 (en) | Systems and methods for instantiating services on top of services | |
| CN102681899B (en) | Virtual computing resource dynamic management system of cloud computing service platform | |
| Williams | Virtualization with Xen (tm): Including XenEnterprise, XenServer, and XenExpress | |
| CN102789392A (en) | Method for constructing power system distributed platform | |
| US9086901B2 (en) | Migration of applications from physical machines to virtual machines | |
| US11537458B2 (en) | Reducing service disruptions in a micro-service environment | |
| CN109062655A (en) | A kind of containerization cloud platform and server | |
| US10922123B2 (en) | Container migration in computing systems | |
| Doherty | SDN and NFV simplified: a visual guide to understanding software defined networks and network function virtualization | |
| CA3095629A1 (en) | Method for managing application configuration state with cloud based application management techniques | |
| Liu et al. | Microservices: architecture, container, and challenges | |
| CN107632937B (en) | Method and device for testing virtual machine cluster and readable storage medium | |
| Dash | Getting started with oracle vm virtualbox | |
| US9678984B2 (en) | File access for applications deployed in a cloud environment | |
| KR101680702B1 (en) | System for web hosting based cloud service | |
| CN109309581B (en) | Container management system crossing hardware architecture | |
| Scott et al. | System-level virtualization research at oak ridge national laboratory | |
| Shah | Windows Server 2012 Hyper-V: Deploying the Hyper-V Enterprise Server Virtualization Platform | |
| Sun et al. | Performance Comparison of Multiple Containers Running Artificial Intelligence Applications | |
| CN112231725A (en) | Method for rapidly dividing software permission | |
| Finta | Mitigating the effects of vendor lock-in in edge cloud environments with open-source technologies | |
| Wu et al. | EVCS: An edge-assisted virtual computing and storage approach for heterogeneous desktop deployment | |
| Murhu | Containerization and Deployment of a Virtual Learning Environment | |
| CN202662000U (en) | Node virtualization deployment device of render farm |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: STATE ELECTRIC NET CROP. Effective date: 20130509 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20130509 Address after: 100192 Beijing city Haidian District Qinghe small Camp Road No. 15 Applicant after: China Electric Power Research Institute Applicant after: State Grid Corporation of China Address before: 100192 Beijing city Haidian District Qinghe small Camp Road No. 15 Applicant before: China Electric Power Research Institute |
|
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20121121 |