CN111381833B

CN111381833B - Initialization method for containerized opentack data

Info

Publication number: CN111381833B
Application number: CN202010146972.7A
Authority: CN
Inventors: 薛延滨; 唐晓东; 蔡卫卫; 高传集
Original assignee: Shandong Huimao Electronic Port Co Ltd
Current assignee: Shandong Huimao Electronic Port Co Ltd
Priority date: 2020-03-05
Filing date: 2020-03-05
Publication date: 2023-05-12
Anticipated expiration: 2040-03-05
Also published as: CN111381833A

Abstract

The invention provides a containerized opentack data initialization method, which belongs to the technical field of opentack data management and comprises the following steps: 1) A configuration parser to separate specific applications and configurations; 2) Distinguishing applications using annotations; 3) The deployment tool automatically refreshes the Values. The invention simplifies the deployment work, improves the application deployment efficiency and can adapt to different environments.

Description

Initialization method for containerized opentack data

Technical Field

The invention relates to an openstack data management technology, in particular to a containerized openstack data initialization method.

Background

More and more environments currently begin to use openstack, and applications that rely on openstack each use either public or independent openstack network configurations, flag configurations, mirroring, etc. Therefore, operation and maintenance personnel need to create opentack resources first and then refresh application configuration, the operation is complex, and the operation cannot be completed at one time.

Disclosure of Invention

In order to solve the technical problems, the invention provides a containerized openstack data initialization method, which provides repeatable refreshing operation for deployment of openstack related applications in a Kubernetes cluster, reduces manpower waste and saves deployment time.

The technical scheme of the invention is as follows:

a method for initializing containerized opentack data,

mainly comprises the following steps:

1) A configuration parser to separate specific applications and configurations;

2) Distinguishing applications using annotations;

3) The deployment tool automatically refreshes the Values.

Further, the method comprises the steps of,

pre-preparation should be made prior to operation, including:

adding comments in the application chart;

adding configuration with a specified format by using values in the chart;

plans in the environment planning table are treated by name.

Wherein, add notes in the application chart, the content is as follows:

annotations:

openstack_associated: t

openstack_networklist: [networkA, networkB]

openstack_flavorlist: [flavorA, flavorB]

the value in the application chart adds the configuration in the prescribed format, the content is as follows:

network:

id: 12345

subnet: 123123

still further, the method comprises the steps of,

the method comprises the following specific steps:

1) And uploading the environment planning table and the application list to a file server.

2) The file server pushes the application to the application deployment tool container.

3) In the deployment process, judging whether to call an opentack to initialize an application container according to whether the annotation opentack_associated in the application chart is true;

if not true, deploying the application;

if true, the opentack initialization application container acquires specific configuration information from the configuration parser container according to the name transmitted by the deployment tool container;

if the configuration information exists, directly inquiring the configuration;

if the configuration information is not available, creating configuration and feeding back to the deployment tool container;

the deployment tool container flushes the values file of the application and deploys the application.

a) The use of a configuration parser allows for separation of specific applications and configurations.

b) The use of annotations makes it easy to differentiate applications

c) Automated refreshing of Values by deployment tools simplifies the configuration of openstack

The invention has the beneficial effects that

The workload of configuration of operation and maintenance personnel is reduced, the admission standard of the operation and maintenance personnel is reduced, and the environment configuration time is saved. So that the deployment is changed from deployment opentack to manual reconfiguration to deployment application.

Drawings

FIG. 1 is a schematic diagram of a technical architecture of the present invention;

fig. 2 is a schematic of the workflow of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments, and all other embodiments obtained by those skilled in the art without making any inventive effort based on the embodiments of the present invention are within the scope of protection of the present invention.

1. Pre-preparation:

the append annotation in the application chart is exemplified as follows:

annotations:

openstack_associated: t

openstack_networklist: [networkA, networkB]

openstack_flavorlist: [flavorA, flavorB]

the configuration of adding a prescribed format to the values in the application chart is exemplified as follows:

network:

id: 12345

subnet: 123123

network etc. plans in an environment planning table are treated by name

2. The flow is as follows:

1) The operation and maintenance personnel upload the environment planning table and the application list to a designated file server

2) Pushing applications to application deployment tool container

3) In the deployment process, whether to call (openstack initialization application container) is judged according to whether the annotation openstack_associated in the application chart is true or not

4) The configuration of a specific network, mirror image and the like is acquired from the configuration parser container according to the deployment tool container incoming, and the configuration (if present, the configuration is directly queried) is created and fed back to the deployment tool container

5) Refreshing values file of application and deploying application

Keyword:

1. a container: kernel lightweight operating system layer virtualization technology

2. kubernetes: a distributed cluster management system in which a worker is run on each node to manage the life cycle of a container

3. git version control tool

4. Logical processor, which is responsible for processing database scripts

5. database client: integrating various versions of database clients into containers

The foregoing description is only illustrative of the preferred embodiments of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method for initializing containerized opentack data is characterized in that,

comprising the following steps:

step 1, configuring a parser to separate specific applications and configurations;

step 2, distinguishing applications by using notes;

step 3, the deployment tool automatically refreshes the Values;

pre-preparation should be made prior to operation, including:

adding comments in the application chart;

adding configuration with a specified format by using values in the chart;

the plans in the environment planning table are treated by names;

wherein, add notes in the application chart, the content is as follows:

annotations:

openstack_associated: t

openstack_networklist: [networkA, networkB]

openstack_flavorlist: [flavorA, flavorB]

network:

id: 12345

subnet: 123123

the step 3 is specifically as follows:

1) Uploading the environment planning table and the application list to a file server;

2) The file server pushes the application to the application deployment tool container;

3) In the deployment process, whether to call an opentack to initialize an application container is judged according to whether the annotation opentack_associated is true in the application chart.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

if not true, the application is deployed.

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

if true, the opentack initialization application container acquires specific configuration information from the configuration parser container according to the name transmitted by the deployment tool container, and if no configuration information exists, the configuration is created and then fed back to the deployment tool container;

4. The method of claim 1, wherein the step of determining the position of the substrate comprises,

if configuration information is present, the configuration is queried directly.