CN106936636A - A kind of implementation method of the cloud computing test platform of rapid deployment containerization - Google Patents
A kind of implementation method of the cloud computing test platform of rapid deployment containerization Download PDFInfo
- Publication number
- CN106936636A CN106936636A CN201710152454.4A CN201710152454A CN106936636A CN 106936636 A CN106936636 A CN 106936636A CN 201710152454 A CN201710152454 A CN 201710152454A CN 106936636 A CN106936636 A CN 106936636A
- Authority
- CN
- China
- Prior art keywords
- deployment
- docker
- node
- container
- cloud computing
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0889—Techniques to speed-up the configuration process
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
- H04L41/0886—Fully automatic configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- 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/45562—Creating, deleting, cloning virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a kind of implementation method of the cloud computing test platform of rapid deployment containerization, comprise the following steps：S1, the essential information that file configuration deployment node is described using the virtual machine of Vagrant, operation vagrant up orders pull the (SuSE) Linux OS of prepackage from Public Warehouse, and are run in Virtual Box；Docker is installed in node is disposed and privately owned container warehouse is created using Docker；The container image file of each service of Openstack is made using Kolla, is preserved into the privately owned container warehouse；S2, traversal perform the process of step S1, and the container image file is deployed into destination node.In the present invention, simplify the deploying step of cloud computing test platform, the flexibility of deployment efficiency and deployment process is improve, the (SuSE) Linux OS compatibility of the different editions that Openstack is issued with different vendor is improve, deployment can also as desired carry out flexible dilatation after terminating.
Description
Technical field
The present invention relates to field of cloud computer technology, more particularly to a kind of cloud computing test platform of rapid deployment containerization
Implementation method.
Background technology
Private clound (Private Clouds) is built for a client is used alone, thus is provided to data, peace
The most effective control of full property and service quality.The said firm possesses infrastructure, it is possible to which deployment should in this infrastructure for control
With the mode of program.Private clound can be deployed in the fire wall of enterprise data center, it is also possible to which they are deployed in into a safety
Hosting place, the core attribute of private clound is specific resource.
With the fast development of cloud computing technology, increasing company attempts oneself deployment cloud computing platform, and upper
Face carries out functional verification and test, in addition, also there is the substantial amounts of exploitation tester to need a set of cloud computing platform of rapid deployment to use
Tested in exploitation.
Openstack as the very privately owned cloud platform of main flow at present, by many organizations portion, lifting in the inner
Its internal IT infrastructure operation and the efficiency of management.Openstack deployment be always one it is comparatively laborious and it is easy error but
Extremely important step, is a preposition link for component private clound again.In the prior art, the scheme of deployment Openstack is non-
Chang Duo, but due to the complexity of Openstack itself, and deployed environment varies, and causes deployment to be got up very tired
It is difficult.
At present, the private clound based on Openstack carries out the method for rapid deployment and is typically based on configuration management framework
Puppet manages the software installation of Openstack components, configuration file modification and treatment of Resource Dependence etc..The prior art
Defect：Config option is excessive and many configuration needs to be manually adjusted according to the difference of system environments, so as to cause error
Probability is greatly increased；Simultaneously as the prior art cannot automatically install (SuSE) Linux OS.At present, it is compatible and run
The (SuSE) Linux OS of Openstack needs to install in advance, and relevant information (such as Hostname, IP address) is write
Enter in configuration file, to be read out when Openstack is disposed, deployer is still needed in the process and enters pedestrian
Work participate in intervene and carry out the adjustment of config option, therefore also result in error probability greatly increase.
The Chinese invention patent application of Publication No. CN104580519A discloses a kind of " rapid deployment openstack clouds
The method of calculating platform ".The main technological route of the prior art is by each of (SuSE) Linux OS and Openstack platforms
Plant service, component and make mirror image template, then started by PXE, DHCP and TFTP.The defect of the prior art：Configuration process
Operation it is excessively complicated；Additionally, when certain node in deployed Openstack needs to reconfigure, it is necessary to again
Redeployed after making mirror image template, the maintenance in later stage and lacking for performance upgrade are unfavorable for so as to cause the prior art to exist
Fall into；Importantly, the prior art cannot adapt to the (SuSE) Linux OS of the different editions of different vendor's issue,
The (SuSE) Linux OS of the different editions that Openstack is issued with different vendor is coupled seriously, therefore the prior art there is also
Problem Openstack not good with the (SuSE) Linux OS compatibility of the different editions that different vendor issues.
In view of this, it is necessary to which the dispositions method based on Openstack cloud platforms of the prior art is improved, with
Solve the above problems.
The content of the invention
It is an object of the invention to disclose a kind of implementation method of the cloud computing test platform of rapid deployment containerization, it is used to
Simplify the deploying step of cloud computing test platform, improve the flexibility of deployment efficiency and deployment process, improve Openstack with not
The (SuSE) Linux OS compatibility of the different editions issued with manufacturer.
To achieve the above object, the invention provides a kind of realization side of the cloud computing test platform of rapid deployment containerization
Method, comprises the following steps：
S1, the essential information that file configuration deployment node is described using the virtual machine of Vagrant, operation vagrant up lives
Order pulls the (SuSE) Linux OS of prepackage from Public Warehouse, and is run in Virtual Box；Installed in node is disposed
Docker simultaneously creates privately owned container warehouse using Docker；The container mirror image text of each service of Openstack is made using Kolla
Part, preserves into the privately owned container warehouse；
S2, traversal perform the process of step S1, and the container image file is deployed into destination node.
As a further improvement on the present invention, described in step S1 " is installed in node is disposed and Docker and uses
Docker creates privately owned container warehouse " also include：After the configuration file configuration of ansible is finished, file is described in virtual machine
It is middle to add the order for calling ansible, after after deployment node normally operation, by calling ansible to install Docker automatically.
As a further improvement on the present invention, also including to describing file to the virtual machine in deployment node and destination node
In the operations that make an amendment of config option Config.vm.box.
As a further improvement on the present invention, the cloud computing test platform is the Openstack cloud meters based on containerization
Calculate test platform.
As a further improvement on the present invention, during the cloud computing test platform runs on a physics host.
As a further improvement on the present invention, the step S2 also loses including current container image file deployment operation
When losing, the container to remaining Docker volume described in the residual Docker volume and carry in destination node is made clear manually
Division operation or automatic clear operation, and the container image file is redeployed to destination node.
Compared with prior art, the beneficial effects of the invention are as follows：By the present invention, the portion of cloud computing test platform is simplified
Administration's step, improves the flexibility of deployment efficiency and deployment process, improves the different versions that Openstack is issued from different vendor
This (SuSE) Linux OS compatibility.
Brief description of the drawings
Fig. 1 is the topological diagram of the cloud computing test platform based on a kind of rapid deployment containerization shown by the present invention；
Fig. 2 be a kind of cloud computing test platform of the rapid deployment containerization shown by the present invention implementation method in first
The deployment process flow diagram flow chart in stage；
Fig. 3 be a kind of cloud computing test platform of the rapid deployment containerization shown by the present invention implementation method in second
The deployment process flow diagram flow chart in stage.
Specific embodiment
The present invention is described in detail for shown each implementation method below in conjunction with the accompanying drawings, but it should explanation, these
Implementation method not limitation of the present invention, those of ordinary skill in the art according to these implementation method institutes works energy, method,
Or equivalent transformation or replacement in structure, belong within protection scope of the present invention.
Before the present invention is elaborated, the major technique noun being related to specification is defined as follows and explains：
1、OpenStack：Based on the cloud computing management platform project increased income, target be to provide implementation it is simple, can be extensive
The unified cloud computing management platform of extension, abundant, standard.
2、VirtualBox：Increase income software virtual machine.
3、Vagrant：Cross-platform virtual machine the build tool, can describe virtual machine, so by a configuration file
The VirtualBox of bottom is called to create virtual machine afterwards.
4、Ansible：Automatically dispose operation and maintenance tools, feature：It is distributed, without client, lightweight.
5、Kolla：Openstack each service is carried out the project of containerization, including two parts：Make Openstack
Each corresponding container image file of service；Use ansible deployment container image files.
6、Docker：The application container engine increased income, allow developer can pack they application and rely on bag to one
In individual transplantable container, then it is published on the computer of the (SuSE) Linux OS of any prevalence, it is also possible to realize virtual
Change.Container is to use sandbox mechanism completely, does not have any interface each other.
7th, Public Warehouse：Docker companies build and towards the warehouse of all users.
Next to a kind of specific embodiment of the implementation method of the cloud computing platform of rapid deployment containerization of the invention
It is elaborated.
Shown in ginseng Fig. 1, many virtual machines (VM), and wherein one virtual machine conduct are created on a physics host 10
Deployment node 4, other virtual machines are used as destination node.Deployment node 4 is of coupled connections multiple target sections by managing network 20
Point (i.e. destination node 1, destination node 2, destination node 3 ... destination node N in Fig. 1), for deposit Openstack each
The container image file of service；, used as the destination node disposed, these destination nodes are used as final deployment for other virtual machines
The feature node of Openstack.Wherein, destination node N refers to any one feature node in above-mentioned destination node 1~3.
A kind of implementation method of the cloud computing test platform of the rapid deployment containerization shown by present embodiment is disposed
Cloud computing test platform run on a physics host 10, with deployment process by the beneficial effect of ectocine
Really.
Shown in ginseng Fig. 1, the Fig. 1 shows multiple destination nodes, is respectively destination node 1 (as control node), target section
Point 2 (as calculate nodes) and destination node 3 (as network node).Furthermore it is possible to accordingly increase with hardware configuration as needed
Plus the number of destination node, and define different types of destination node.During deployment Openstack, according to the arrow side in Fig. 1
To, will dispose node 4 on Openstack each service container image file be deployed to each destination node up, with complete
Into the deployment of the whole cloud computing test platform based on OpenStack frameworks.
Preliminary examination can be carried out to deployed environment using kolla-ansible prechecks orders during deployment,
To reduce the risk of deployment failure；Once other deployment process makes a mistake, it is possible to use kolla-ansible
Destroy--yes-i-really-really-mean-it orders come remove deployment during residual data, solving out
When wrong problem lays equal stress on newly deployed, it is ensured that possess clean deployed environment in physics host 10, deployment is so just ensure that
The idempotence of process, can greatly reduce the failure probability of deployment.
In the present embodiment, the implementation method of the cloud computing test platform of the rapid deployment containerization mainly includes two
Stage.
Shown in ginseng Fig. 2, the first stage：Make the container image file of each service of OpenStack, and specially following the
Shown in 1 step to the 3rd step.
1st step：Prepare for deployment node.
File (Vagrantfile) is described using the virtual machine of Vagrant to configure the essential information of deployment node 4, it is main
Want code as follows：
Then vagrant up orders are run.Vagrant can pull the Linux operations system being pre-installed from its Public Warehouse
System.Be simplify statement, in this manual, (SuSE) Linux OS from version number for CentOS7 (SuSE) Linux OS (with
Lower abbreviation " CentOS7 ").CentOS7 is run in Virtual Box, while setting CentOS7 is in Virtual Box
Title, CentOS7 operation after can also perform the operation for automatically configuring Hostname and IP address.
Can be with by whether can be in SSH to deployment node 4 and verifying whether IP address and Hostname are correct and determine
Whether this step is done properly；If wrong, can first check that the virtual machine of deployment node 4 describes file
(Vagrantfile) connectedness of present physical host 10 and outer net etc., is checked to be solved.Specifically, can pass through
The TTL of ping 114.114.114.114 (address of disclosed dns server) carries out the judgement connective with outer net, as long as
There is the packet of return and without packet loss, can assert that physics host 10 has built up with outer net and be connected.
2nd step：Docker is installed in node is disposed, and a privately owned container warehouse (Docker is created using Docker
registry)。
Preferably, in the present embodiment, it is described Docker to be installed in node is disposed and creates privately owned using Docker
Container warehouse also includes：After the configuration file configuration of ansible is finished, in virtual machine describes file (Vagrantfile)
The order of ansible is called in addition, after after deployment node normally operation, by calling ansible to install Docker automatically.From
And in causing that the content for installing Docker writes on the configuration file of ansible.The main code of the 2nd step is as follows.
Wherein, playbook.yml contents are as follows：
Then a privately owned container warehouse (Docker registry), the main generation of establishment operation correspondence order are created
Code is as follows：
mkdir-p/root/image_repo
docker run-d-p 4000:5000-v/root/image_repo:/var/lib/registry--restart
=always--name registry registry:2
Meanwhile, in the present embodiment, in addition it is also necessary to configure Docker finger daemons, it is used the private for creating just now
There is container warehouse, can be by adding start-up parameter in/lib/systemd/system/docker.service.
ExecStart=/usr/bin/dockerd--insecure-registry 192.168.0.10:4000...
Then Docker is restarted, code is：systemctl restart docker.
Can be by the way that can be pushed to any one container image file in the privately owned container warehouse of firm establishment by this step
To verify whether correctly to perform；If wrong, Docker configurations and the configuration in privately owned container warehouse can be checked, checking is
It is no correctly to enable this privately owned container warehouse.
3rd step：Dispose node 4 in using Kolla make Openstack each service container image file and preserve
To in privately owned container warehouse.
Specifically, downloading first and installing Kolla, operation makes all of mirror image to issue orders and pushes to privately owned appearance
Device warehouse：
kolla-build--type source--registry 192.168.0.10:4000–push
After this step is complete, can check whether all of container image file has all been made in privately owned container warehouse
Determine whether successful execution.Due to needing that various software kits and source code are downloaded from network (specially outer net), network and soft
The factor such as unstable in part source can cause to perform failure, can be retried after stabilization, if the configuration file of Kolla in addition
In it is wrong, will also result in create container image file failure.
Specifically, using order：curl 192.168.0.10:4000/v2/_catalog checks privately owned container warehouse
In all container image files.If the container image file one that result is listed with kolla-build--list-images orders
Cause, it is possible to think that all of container image file has all made and finish.
Shown in ginseng Fig. 1 and Fig. 3, second stage, the container image file that will be made are deployed on destination node.
4th step, preparation destination node.
This three configurations of destination node defined in file (Vagrantfile) are described in the virtual machine of vagrant, mainly
Code is as follows：
It can be seen that defining three network segments：Management network 20：192.168.0.0/24, calculating network 30：
And external network 40 192.168.1.0/24：192.168.2.0/24.It is Openstack test wrappers that the effect of external network 40 is
Virtual machine in border provides the approach for accessing outer net.
In addition, in the 1st step, in the range of management network 20, deployment node 4 just can be with for the IP of the deployment node 4 of definition
This destination node, destination node 2 and destination node 3 are accessed by managing network 20.
Virtual machine describes operation vagrant up orders after file (Vagrantfile) is ready to, with the 1st step one
Sample, Vagrant can pull the CentOS 7 being pre-installed from Public Warehouse, and run CentOS 7 in Virtual Box
Get up, while titles of the CentOS 7 in Virtual Box can be set, CentOS 7 can also automatically configure host name after running
Claim and IP address.
With the same in the 1st step, can be with by whether with SSH to disposing in node 4, and can verify whether are IP and Hostname
Correctly, so that it is determined that whether this step is correctly completed, if wrong, can first check that the virtual machine of deployment node describes file
(Vagrantfile) connectedness of present physical machine and outer net etc., is checked to be solved.
5th step, Docker is installed in destination node 1, destination node 2 and destination node 3, and changes default configuration, make
Above three destination node can use the privately owned container warehouse being created in deployment node 4.By configuring Docker
Finger daemon, making to state three destination nodes can be using the privately owned container warehouse being created, can be by in/lib/
Start-up parameter is added in systemd/system/docker.service, specific code is as follows：
ExecStart=/usr/bin/dockerd--insecure-registry 192.168.0.10:4000...
Then Docker is restarted, code is：systemctl restart docker.
Whether the container mirror for creating in the first phase can be correctly downloaded by this several destination nodes of deployment
As file, just can verify whether current this step runs succeeded.If wrong, the Docker configurations of present node are checked,
Determine whether correctly to enable the privately owned container warehouse for preserving mirror image.
If specifically, container mirror image can be pulled from the privately owned container warehouse (Docker registry) described in the 2nd step
File, then prove whether the verification operation in the 5th step succeeds.Specific code is：
docker pull 192.168.0.10:4000/kolla/centos-source-nova-api,
Wherein, during " kolla/centos-source-nova-api " is privately owned container warehouse (Docker registry)
A container image file.
6th step：Disposed using Kolla in node 4 is disposed.
This step needs to do some preparation, will 3 management network ip address of destination node and each node pair
The role's (such as control node, calculate node and network node) for answering writes the configuration file of Kolla, to be existed using Kolla
These different destination nodes just can be recognized during deployment Openstack.Equally, this step can also be by calling ansible
Order to be automatically performed.
By this method will install CentOS 7 with dispose Openstack the two isolate the step of be fused together,
Just a large amount of manual configurations that other deployment way must be carried out can be solved the problems, such as, the cloud computing test of containerization had both been simplified
The deployment flow of platform, also effectively reduces the risk of the deployment failure caused by configuration error, so as to greatly improve
The deployment efficiency of the cloud computing test platform of containerization.
Configuration file be can be carried out after changing it is formal deploy, run following order：
kolla-ansible deploy
The privately owned cloud platform of the Openstack of the containerization of complete set is ready and deployment is finished after the completion of execution.
Can by test Openstack each function whether can be used to judge this step whether successful execution, if
Any problem, can check that each Openstack services corresponding container running status and configuration file, checks Kolla configuration texts
Part, reruns order and is disposed after pinpointing the problems.
Specifically, in how verifying the 6th step, whether successful execution is specially：
Perform nova service-list and neutron agent-list；If run succeeded, and can be with result
List calculate node (i.e. destination node 2) and network node (i.e. destination node 3) respectively, and be all active states and can
Prove to be disposed using Kolla whether install successfully to create the resources such as virtual machine and network.
After the completion of deployment, if demands such as dilatations, for example, increase calculate node or network node, can be according to this hair
Bright middle second stage identical step carries out dilatation, due to being already prepared to privately owned container warehouse and container in the first stage
Image file, thus the first stage need not re-execute；Other this mode is for deployed good destination node
Do not influence completely, so just can easily carry out resource capacity expansion.
The present invention can support different editions number, the (SuSE) Linux OS of different releases, and what we were used above is
The (SuSE) Linux OS of CentOS 7, it is also possible to support the (SuSE) Linux OS of other manufacturers or different editions, such as lead
Ubuntu/Debian, SUSE of stream etc..What our needs made only needs to simply change each virtual machine configuration
(Vagrantfile) config.vm.box configuration items are to be capable of achieving self adaptation in, and specific code is as follows：
Config.vm.box=" ubuntu/trusty64 ", represents and uses the 64bit of Ubuntu 14.04；
Config.vm.box=" ubuntu/xenial64 ", represents and uses the 64bit of Ubuntu 16.04；
Config.vm.box=" debian/jessie64 ", represents and uses the 64bit of Debian 8；
Config.vm.box=" suse/sles11sp3 ", represents and uses SUSE enterprises
Version SLES 11 SP3.
In the 6th step, the problem of the deployment failure being likely to occur when being disposed using Kolla to first time, the present invention
Corresponding solution is it is also proposed, it is specific as follows shown.
The situation of deployment failure is likely encountered during deployment, mariadb databases occur cannot log in：
TASK[mariadb:Creating haproxy mysql user]
FAILED-RETRYING:TASK:mariadb:Creating haproxy mysql user(10 retries
left).
……
FAILED-RETRYING:TASK:mariadb:Creating haproxy mysql user(2 retries
left).
FAILED-RETRYING:TASK:mariadb:Creating haproxy mysql user(1 retries
left).
NO MORE HOSTS LEFT
to retry,use:--limit@/usr/share/kolla/ansible/site.retry
PLAY RECAP
controller1:Ok=49 changed=22 unreachable=0 failed=1
Include database as the destination node 1 of control node, and preferentially select mariadb databases.When for the first time
During deployment failure, because preceding first use Kolla carries out error when deployment is installed, cause to have remained one in control node
Docker volume, and there is bug in code.Therefore, carry out once being examined when deployment is installed using Kolla at second
Measured this residual Docker volume, then the step of can skip initialization data storehouse (i.e. mariadb databases), so that
Cause that caused by the difference of set database password in configuration process twice mariadb data cannot be logged on to forever
The problem in storehouse, and ultimately result in cannot successful deployment problem.
Therefore, in the present embodiment, in the 6th step, also failing including current container image file deployment operation
When, the container to remaining Docker volume described in the residual Docker volume and carry in destination node is made to remove manually
Operation or automatic clear operation, and the container image file is redeployed to destination node.Accordingly, it would be desirable to remove
The Docker (container) of Docker volume and correlation in mariadb, then re-starts deployment.Docker now is
It is mounted with the container of Docker volume.For this can be by changing kolla bug in itself or before deployment using script clear
Solved the above problems except all residual datas (including Docker Volume and be mounted with the Docker of Docker Volume).
It should be noted that container signified herein refers to the container that control node is currently running.Delete Docker
The order of Volume is that docker volume rm mariadb, wherein mariadb are the titles of Docker Volume, comprising
The data of each component database in Openstack.
Specifically, removing the container operation of residual Docker volume described in residual Docker volume and carry manually
Scheme be specially：
Run to order the container removed Docker volume and be currently running in all of control node：
First, the mariadb containers being currently running are stopped in all control nodes, is ordered as follows：
docker stop mariadb；
Then, container is deleted in all control nodes, is ordered as follows：
docker stop mariadb；
Finally, docker volume are removed in all control nodes, is ordered as follows：
docker volume rm mariadb。
The automatic scheme for removing the container operation of residual Docker volume described in residual Docker volume and carry
Specially：
By herein below write-in ansible configuration file in, by running ansible to remove in control node automatically
Residual Docker volume and residual Docker volume described in carry container, its order is as follows：
By above-mentioned technical proposal, can avoid due to it is front and rear twice using Kolla carry out deployment install when, it is to avoid due to two
Asking for mariadb databases cannot be logged on to forever caused by the difference of set database password in secondary configuration process
Topic, so as to significantly improve the success rate and simplicity of deployment, prevents error.
In the present embodiment, using the assembled scheme of Vagrant and Virtual Box come unified plan Openstack
The cloud computing test platform of framework, Openstack is deployed in the virtual machine of physics host 10, and is configured to have difference
The destination node of function, solves the problems, such as the deployment failure caused by environment is inconsistent.Meanwhile, using Vagrant with
The combination of Ansible, can support (SuSE) Linux OS and the two independent deployment ranks of deployment Openstack of different editions
Duan Shixian organic combinations, reduce user's deployment difficulty.Finally, due to using privately owned container warehouse and container image file, from
And greatly reduce the mortality of deployment cloud computing test platform.
Those listed above is a series of to be described in detail only for feasibility implementation method of the invention specifically
Bright, they simultaneously are not used to limit the scope of the invention, all equivalent implementations made without departing from skill spirit of the present invention
Or change should be included within the scope of the present invention.
It is obvious to a person skilled in the art that the invention is not restricted to the details of above-mentioned one exemplary embodiment, Er Qie
In the case of without departing substantially from spirit or essential attributes of the invention, the present invention can be in other specific forms realized.Therefore, no matter
From the point of view of which point, embodiment all should be regarded as exemplary, and be nonrestrictive, the scope of the present invention is by appended power
Profit requires to be limited rather than described above, it is intended that all in the implication and scope of the equivalency of claim by falling
Change is included in the present invention.Any reference in claim should not be considered as the claim involved by limitation.
Moreover, it will be appreciated that although the present specification is described in terms of embodiments, not each implementation method is only wrapped
Containing an independent technical scheme, this narrating mode of specification is only that for clarity, those skilled in the art should
Specification an as entirety, the technical scheme in each embodiment can also be formed into those skilled in the art through appropriately combined
May be appreciated other embodiment.
Claims (6)
1. a kind of implementation method of the cloud computing test platform of rapid deployment containerization, it is characterised in that comprise the following steps：
S1, described using the virtual machine of Vagrant file configuration dispose node essential information, operation vagrant up orders from
The (SuSE) Linux OS of prepackage is pulled in Public Warehouse, and is run in Virtual Box；Installed in node is disposed
Docker simultaneously creates privately owned container warehouse using Docker；The container mirror image text of each service of Openstack is made using Kolla
Part, preserves into the privately owned container warehouse；
S2, traversal perform the process of step S1, and the container image file is deployed into destination node.
2. implementation method according to claim 1, it is characterised in that described in step S1 " is installed in node is disposed
Docker simultaneously creates privately owned container warehouse using Docker " also include：After the configuration file configuration of ansible is finished, in void
Plan machine describes to add the order for calling ansible in file, after after deployment node normally operation, by calling ansible with certainly
It is dynamic that Docker is installed.
3. implementation method according to claim 1, it is characterised in that also including to in deployment node and destination node
Virtual machine describes the operation that the config option Config.vm.box in file makes an amendment.
4. implementation method according to claim 1, it is characterised in that the cloud computing test platform is based on containerization
Openstack cloud computing test platforms.
5. implementation according to claim 1, it is characterised in that the cloud computing test platform runs on a physics
In host.
6. implementation method according to claim 1, it is characterised in that the step S2 also includes a current container mirror image
During file deployment operation failure, to remaining Docker volume described in the residual Docker volume and carry in destination node
Container make manual clear operation or automatic clear operation, and the container image file is redeployed to destination node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710152454.4A CN106936636B (en) | 2017-03-15 | 2017-03-15 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710152454.4A CN106936636B (en) | 2017-03-15 | 2017-03-15 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106936636A true CN106936636A (en) | 2017-07-07 |
| CN106936636B CN106936636B (en) | 2019-08-30 |
Family
ID=59432472
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710152454.4A Active CN106936636B (en) | 2017-03-15 | 2017-03-15 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106936636B (en) |
Cited By (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107463432A (en) * | 2017-08-17 | 2017-12-12 | 福建中金在线信息科技有限公司 | Server production environment dispositions method, device, electronic equipment and storage medium |
| CN107835093A (en) * | 2017-10-26 | 2018-03-23 | 郑州云海信息技术有限公司 | A kind of memory management method and device |
| CN108462746A (en) * | 2018-03-14 | 2018-08-28 | 广州西麦科技股份有限公司 | A kind of container dispositions method and framework based on openstack |
| CN108809733A (en) * | 2018-07-11 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of system of multinode deployment docking OpenStack cloud management platforms |
| CN108829399A (en) * | 2018-04-13 | 2018-11-16 | 杭州朗和科技有限公司 | A kind of test method of application, test device, medium and calculate equipment |
| CN108829409A (en) * | 2018-06-20 | 2018-11-16 | 泰华智慧产业集团股份有限公司 | A kind of distributed system quick deployment method and system |
| CN108984165A (en) * | 2018-07-16 | 2018-12-11 | 郑州云海信息技术有限公司 | A kind of building customizes the method and system of mirror image |
| CN109065111A (en) * | 2018-08-06 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of cloud platform health check system and method based on docker |
| CN109359033A (en) * | 2018-09-05 | 2019-02-19 | 广州神马移动信息科技有限公司 | Method for testing pressure, testing service device, management server and system |
| CN109412887A (en) * | 2018-10-08 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of collection system of the container monitors data based on OpenStack |
| CN109495298A (en) * | 2018-11-06 | 2019-03-19 | 郑州云海信息技术有限公司 | The method and apparatus of management node in OpenStack system |
| CN109756533A (en) * | 2017-11-02 | 2019-05-14 | 阿里巴巴集团控股有限公司 | A kind of mirror image accelerated method, device and server |
| CN109799998A (en) * | 2018-12-18 | 2019-05-24 | 深圳先进技术研究院 | OpenStack cluster configuration and batch dispositions method and system |
| CN109871213A (en) * | 2018-12-25 | 2019-06-11 | 武汉烽火信息集成技术有限公司 | OpenStack containerization system and method based on Domestic Platform |
| CN110233817A (en) * | 2018-03-06 | 2019-09-13 | 广州西麦科技股份有限公司 | A kind of vessel safety system based on cloud computing |
| WO2019218463A1 (en) * | 2018-05-14 | 2019-11-21 | 平安科技（深圳）有限公司 | Method and apparatus for automatically building kubernetes master node on basis of ansible tool, terminal device, and readable storage medium |
| CN111181953A (en) * | 2019-12-26 | 2020-05-19 | 山东乾云启创信息科技股份有限公司 | Method and device for supporting spice protocol through Roc virtualization |
| CN111198696A (en) * | 2019-12-30 | 2020-05-26 | 湖南大学 | OpenStack large-scale deployment method and system based on bare computer server |
| CN111198695A (en) * | 2019-12-25 | 2020-05-26 | 航天信息股份有限公司 | Automatic deployment method of micro-service administration management platform and electronic equipment |
| CN111324356A (en) * | 2018-12-17 | 2020-06-23 | 北京数安鑫云信息技术有限公司 | Software automation deployment method and system |
| CN111343144A (en) * | 2020-01-23 | 2020-06-26 | 奇安信科技集团股份有限公司 | OPC (optical proximity correction) network gate system based on Linux and data processing method |
| CN111427600A (en) * | 2020-03-20 | 2020-07-17 | 成都千立网络科技有限公司 | Docker-based platform system deployment and upgrade method and system |
| CN111984366A (en) * | 2020-07-24 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method and system for deploying disaster recovery mechanism in containerization manner |
| WO2020253079A1 (en) * | 2019-06-17 | 2020-12-24 | 平安科技（深圳）有限公司 | Jmeter-based distributed performance test method and apparatus, device, and storage medium |
| CN112187567A (en) * | 2020-09-11 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Containerized agent-free private cloud management method and system |
| CN112543109A (en) * | 2019-09-20 | 2021-03-23 | 上海数荃数据科技有限公司 | Cloud host creation method, system, server and storage medium |
| CN112667256A (en) * | 2020-12-22 | 2021-04-16 | 北京浪潮数据技术有限公司 | OpenStack cross-version upgrading method based on kolla-allowed |
| CN112887352A (en) * | 2019-11-29 | 2021-06-01 | 北京神州泰岳软件股份有限公司 | Image file uploading method and device for Docker container |
| CN112925609A (en) * | 2021-03-01 | 2021-06-08 | 浪潮云信息技术股份公司 | OpenStack cloud platform upgrading method and device |
| CN113064827A (en) * | 2021-04-12 | 2021-07-02 | 京东数科海益信息科技有限公司 | Test platform deployment method, device, equipment and storage medium |
| CN113127150A (en) * | 2021-03-18 | 2021-07-16 | 同盾控股有限公司 | Rapid deployment method and device of cloud native system, electronic equipment and storage medium |
| CN113572619A (en) * | 2021-09-22 | 2021-10-29 | 银河麒麟软件(长沙)有限公司 | Container cloud mirror image credible implementation method and system based on nottry |
| US11171824B2 (en) | 2018-03-01 | 2021-11-09 | Red Hat, Inc. | Configuration of computing devices via containers |
| CN114489693A (en) * | 2021-12-27 | 2022-05-13 | 国网冀北电力有限公司 | Comprehensive transformer state monitoring system based on edge application |
| US11336588B2 (en) | 2020-06-26 | 2022-05-17 | Red Hat, Inc. | Metadata driven static determination of controller availability |
| US11366683B2 (en) | 2020-01-03 | 2022-06-21 | International Business Machines Corporation | Images deployment system across multiple architectures |
| CN115102965A (en) * | 2022-05-25 | 2022-09-23 | 弥费实业(上海)有限公司 | SECSGEM communication conversion system and method for semiconductor material storage equipment |
| CN112667256B (en) * | 2020-12-22 | 2024-07-02 | 北京浪潮数据技术有限公司 | Kolla-stable-based OpenStack cross-version upgrading method |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105871988A (en) * | 2015-12-14 | 2016-08-17 | 乐视云计算有限公司 | Service deployment method and device |
| US20160366233A1 (en) * | 2015-06-10 | 2016-12-15 | Platform9, Inc. | Private Cloud as a service |
-
2017
- 2017-03-15 CN CN201710152454.4A patent/CN106936636B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160366233A1 (en) * | 2015-06-10 | 2016-12-15 | Platform9, Inc. | Private Cloud as a service |
| CN105871988A (en) * | 2015-12-14 | 2016-08-17 | 乐视云计算有限公司 | Service deployment method and device |
Non-Patent Citations (2)
| Title |
|---|
| LSC: "OpenStack Kolla之部署", 《HTTPS://BBS.ICHUNQIU.COM/THREAD-3985-1-1.HTML》 * |
| PMLPML: "用vagrant快速部署docker虚拟机集群", 《HTTPS://BLOG.CSDN.NET/PMLPML/ARTICLE/DETAILS/53925542》 * |
Cited By (53)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107463432A (en) * | 2017-08-17 | 2017-12-12 | 福建中金在线信息科技有限公司 | Server production environment dispositions method, device, electronic equipment and storage medium |
| CN107835093A (en) * | 2017-10-26 | 2018-03-23 | 郑州云海信息技术有限公司 | A kind of memory management method and device |
| CN109756533A (en) * | 2017-11-02 | 2019-05-14 | 阿里巴巴集团控股有限公司 | A kind of mirror image accelerated method, device and server |
| CN109756533B (en) * | 2017-11-02 | 2021-11-30 | 阿里巴巴集团控股有限公司 | Mirror image acceleration method and device and server |
| US11171824B2 (en) | 2018-03-01 | 2021-11-09 | Red Hat, Inc. | Configuration of computing devices via containers |
| CN110233817A (en) * | 2018-03-06 | 2019-09-13 | 广州西麦科技股份有限公司 | A kind of vessel safety system based on cloud computing |
| CN110233817B (en) * | 2018-03-06 | 2021-12-28 | 广州西麦科技股份有限公司 | Container safety system based on cloud computing |
| CN108462746B (en) * | 2018-03-14 | 2021-11-16 | 广州西麦科技股份有限公司 | Container deployment method and framework based on openstack |
| CN108462746A (en) * | 2018-03-14 | 2018-08-28 | 广州西麦科技股份有限公司 | A kind of container dispositions method and framework based on openstack |
| CN108829399A (en) * | 2018-04-13 | 2018-11-16 | 杭州朗和科技有限公司 | A kind of test method of application, test device, medium and calculate equipment |
| WO2019218463A1 (en) * | 2018-05-14 | 2019-11-21 | 平安科技（深圳）有限公司 | Method and apparatus for automatically building kubernetes master node on basis of ansible tool, terminal device, and readable storage medium |
| CN108829409A (en) * | 2018-06-20 | 2018-11-16 | 泰华智慧产业集团股份有限公司 | A kind of distributed system quick deployment method and system |
| CN108829409B (en) * | 2018-06-20 | 2022-03-04 | 泰华智慧产业集团股份有限公司 | Distributed system rapid deployment method and system |
| CN108809733B (en) * | 2018-07-11 | 2021-10-22 | 郑州云海信息技术有限公司 | System for multi-node deployment docking OpenStack cloud management platform |
| CN108809733A (en) * | 2018-07-11 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of system of multinode deployment docking OpenStack cloud management platforms |
| CN108984165A (en) * | 2018-07-16 | 2018-12-11 | 郑州云海信息技术有限公司 | A kind of building customizes the method and system of mirror image |
| CN109065111A (en) * | 2018-08-06 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of cloud platform health check system and method based on docker |
| CN109359033A (en) * | 2018-09-05 | 2019-02-19 | 广州神马移动信息科技有限公司 | Method for testing pressure, testing service device, management server and system |
| CN109412887A (en) * | 2018-10-08 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of collection system of the container monitors data based on OpenStack |
| CN109495298B (en) * | 2018-11-06 | 2022-06-07 | 郑州云海信息技术有限公司 | Method and device for managing nodes in OpenStack system |
| CN109495298A (en) * | 2018-11-06 | 2019-03-19 | 郑州云海信息技术有限公司 | The method and apparatus of management node in OpenStack system |
| CN111324356A (en) * | 2018-12-17 | 2020-06-23 | 北京数安鑫云信息技术有限公司 | Software automation deployment method and system |
| CN109799998A (en) * | 2018-12-18 | 2019-05-24 | 深圳先进技术研究院 | OpenStack cluster configuration and batch dispositions method and system |
| CN109871213A (en) * | 2018-12-25 | 2019-06-11 | 武汉烽火信息集成技术有限公司 | OpenStack containerization system and method based on Domestic Platform |
| WO2020253079A1 (en) * | 2019-06-17 | 2020-12-24 | 平安科技（深圳）有限公司 | Jmeter-based distributed performance test method and apparatus, device, and storage medium |
| CN112543109B (en) * | 2019-09-20 | 2023-08-15 | 上海数荃数据科技有限公司 | Cloud host creation method, cloud host creation system, server and storage medium |
| CN112543109A (en) * | 2019-09-20 | 2021-03-23 | 上海数荃数据科技有限公司 | Cloud host creation method, system, server and storage medium |
| CN112887352A (en) * | 2019-11-29 | 2021-06-01 | 北京神州泰岳软件股份有限公司 | Image file uploading method and device for Docker container |
| CN112887352B (en) * | 2019-11-29 | 2023-04-18 | 北京神州泰岳软件股份有限公司 | Image file uploading method and device for Docker container |
| CN111198695A (en) * | 2019-12-25 | 2020-05-26 | 航天信息股份有限公司 | Automatic deployment method of micro-service administration management platform and electronic equipment |
| CN111181953A (en) * | 2019-12-26 | 2020-05-19 | 山东乾云启创信息科技股份有限公司 | Method and device for supporting spice protocol through Roc virtualization |
| CN111198696A (en) * | 2019-12-30 | 2020-05-26 | 湖南大学 | OpenStack large-scale deployment method and system based on bare computer server |
| CN111198696B (en) * | 2019-12-30 | 2021-06-29 | 湖南大学 | OpenStack large-scale deployment method and system based on bare computer server |
| US11366683B2 (en) | 2020-01-03 | 2022-06-21 | International Business Machines Corporation | Images deployment system across multiple architectures |
| CN111343144A (en) * | 2020-01-23 | 2020-06-26 | 奇安信科技集团股份有限公司 | OPC (optical proximity correction) network gate system based on Linux and data processing method |
| CN111343144B (en) * | 2020-01-23 | 2022-09-02 | 奇安信科技集团股份有限公司 | OPC (optical proximity correction) network gate system based on Linux and data processing method |
| CN111427600A (en) * | 2020-03-20 | 2020-07-17 | 成都千立网络科技有限公司 | Docker-based platform system deployment and upgrade method and system |
| CN111427600B (en) * | 2020-03-20 | 2023-04-21 | 成都千立网络科技有限公司 | Platform system deployment upgrading method and system based on dock |
| US11991094B2 (en) | 2020-06-26 | 2024-05-21 | Red Hat, Inc. | Metadata driven static determination of controller availability |
| US11336588B2 (en) | 2020-06-26 | 2022-05-17 | Red Hat, Inc. | Metadata driven static determination of controller availability |
| CN111984366A (en) * | 2020-07-24 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method and system for deploying disaster recovery mechanism in containerization manner |
| CN111984366B (en) * | 2020-07-24 | 2023-01-06 | 苏州浪潮智能科技有限公司 | Method and system for containerized deployment of disaster recovery mechanism |
| CN112187567A (en) * | 2020-09-11 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Containerized agent-free private cloud management method and system |
| CN112667256A (en) * | 2020-12-22 | 2021-04-16 | 北京浪潮数据技术有限公司 | OpenStack cross-version upgrading method based on kolla-allowed |
| CN112667256B (en) * | 2020-12-22 | 2024-07-02 | 北京浪潮数据技术有限公司 | Kolla-stable-based OpenStack cross-version upgrading method |
| CN112925609B (en) * | 2021-03-01 | 2022-03-15 | 浪潮云信息技术股份公司 | OpenStack cloud platform upgrading method and device |
| CN112925609A (en) * | 2021-03-01 | 2021-06-08 | 浪潮云信息技术股份公司 | OpenStack cloud platform upgrading method and device |
| CN113127150A (en) * | 2021-03-18 | 2021-07-16 | 同盾控股有限公司 | Rapid deployment method and device of cloud native system, electronic equipment and storage medium |
| CN113127150B (en) * | 2021-03-18 | 2023-10-17 | 同盾控股有限公司 | Rapid deployment method and device of cloud primary system, electronic equipment and storage medium |
| CN113064827A (en) * | 2021-04-12 | 2021-07-02 | 京东数科海益信息科技有限公司 | Test platform deployment method, device, equipment and storage medium |
| CN113572619A (en) * | 2021-09-22 | 2021-10-29 | 银河麒麟软件(长沙)有限公司 | Container cloud mirror image credible implementation method and system based on nottry |
| CN114489693A (en) * | 2021-12-27 | 2022-05-13 | 国网冀北电力有限公司 | Comprehensive transformer state monitoring system based on edge application |
| CN115102965A (en) * | 2022-05-25 | 2022-09-23 | 弥费实业(上海)有限公司 | SECSGEM communication conversion system and method for semiconductor material storage equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106936636B (en) | 2019-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106936636B (en) | A kind of implementation method of the cloud computing test platform of rapid deployment containerization | |
| CN106325951B (en) | It is a kind of to support multiple database, the application system Automation arranging method of more middleware types | |
| KR102443172B1 (en) | System and method for supporting patching in a multitenant application server environment | |
| US8719782B2 (en) | Integrated package development and machine configuration management | |
| US9043767B2 (en) | Release management system for a multi-node application | |
| Lowe | Mastering vmware vsphere 5 | |
| US20090150885A1 (en) | Appliances in virtual computing environments | |
| CN112084008A (en) | Method for rapidly deploying cloud pipe system based on container technology | |
| US20070044077A1 (en) | Infrastructure for verifying configuration and health of a multi-node computer system | |
| US9830177B1 (en) | Computer implemented method and system, and computer program product, for determining compliance with a configuration parameter before deployment of a virtual appliance into a network appliance | |
| Chen et al. | MORE: A model-driven operation service for cloud-based IT systems | |
| CN109710281A (en) | The installation method and device of big data platform | |
| Blaas et al. | Stateless provisioning: Modern practice in hpc | |
| CN117472785B (en) | Openstack test method and system under Linux system | |
| CN116909584B (en) | Deployment method, device, equipment and storage medium of space-time big data engine | |
| Murhu | Containerization and Deployment of a Virtual Learning Environment | |
| Kollárová | Fault injection testing of openstack | |
| Dolstra et al. | Charon: Declarative provisioning and deployment | |
| Jadhav | Configuration and automation of OpenStack deployment | |
| US9239870B1 (en) | Multiple instance database auto-configuration for high availability | |
| Kulkarni | Openstack Installation and Automation: Victoria | |
| Ghonsikar | Openstack cloud installation and uninstallation automation | |
| Team | HIL Documentation | |
| Allison et al. | Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide, 10g Release 2 (10.2) for Linux B14203-01 | |
| Dyke et al. | Adding and Deleting Nodes and Instances |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 214125 Wuxi science and Technology Park, Jiangsu Binhu District No. 6 Patentee after: Huayun data holding group Co., Ltd Address before: 214125 Wuxi science and Technology Park, Jiangsu Binhu District No. 6 Patentee before: WUXI CHINAC DATA TECHNICAL SERVICE Co.,Ltd. |