CN113835715A - Case board card, cluster system, software deployment method and storage medium - Google Patents
Case board card, cluster system, software deployment method and storage medium Download PDFInfo
- Publication number
- CN113835715A CN113835715A CN202010592519.9A CN202010592519A CN113835715A CN 113835715 A CN113835715 A CN 113835715A CN 202010592519 A CN202010592519 A CN 202010592519A CN 113835715 A CN113835715 A CN 113835715A
- Authority
- CN
- China
- Prior art keywords
- software
- deployment
- cluster system
- chassis
- software deployment
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
In the embodiment of the invention, because at least two software deployment servers capable of providing services simultaneously exist in the cluster system, each chassis board can select one of the software deployment servers to acquire a software version file corresponding to a target software group in the starting stage of the cluster system, so that the request objects of each chassis board are dispersed, the pressure of a single main control board is reduced, more importantly, the efficiency of acquiring the software version file by each chassis board is improved, and the starting time of the cluster system is shortened. On the other hand, for one main control board, it is not necessary to provide corresponding software version files to all chassis boards in the cluster system, so the main control board can have more time to synchronously forward the table data to the previously started chassis board, and the time for the cluster system to reach a serviceable state is further shortened.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to but not limited to a chassis board card, a cluster system, a software deployment method and a storage medium.
Background
With the explosion of internet services, traffic data traffic to be processed by communication networks such as a backbone network of a telecommunication operator, a mobile core network, a metropolitan area network and the like is rapidly increased, and a high-throughput and high-availability carrier-grade forwarding and switching device is required to be used. A physical cluster system (also referred to as a physical cluster system device) composed of multiple chassis, such as a carrier class cluster router and a switch, has a high throughput and a high availability, and is a core component of the above important communication network.
Disclosure of Invention
The chassis board card, the cluster system, the software deployment method and the storage medium provided by the embodiment of the invention mainly solve the technical problems that: in the related art, the physical cluster system needs a long time to reach a serviceable state when being started, and the starting speed is slow.
To solve the foregoing technical problem, an embodiment of the present invention provides a cluster system software deployment method, including:
the method comprises the steps that a chassis board card sends a software version request containing software group information in a cluster system to which the chassis board card belongs, wherein the software group information is used for indicating a target software group which needs to be deployed by the chassis board card, at least two software deployment servers capable of providing services simultaneously exist in the cluster system, and different software deployment servers are respectively deployed on different main control boards of the cluster system;
the chassis board card receives download indication messages sent by at least two software deployment servers in the cluster system according to the software version request, wherein the download indication messages are used for indicating how to acquire the software version files of the target software group from the corresponding software deployment servers;
the chassis board card selects one software deployment server as a target software deployment server according to the downloading indication message;
and the case board card downloads the software version file from the target software deployment server and deploys the software according to the software version file.
The embodiment of the invention also provides a cluster system software deployment method, which comprises the following steps:
the method comprises the steps that a main control board receives a software version request containing software group information sent by a chassis board card in a cluster system, wherein the software group information is used for indicating a target software group which needs to be deployed by the chassis board card; the cluster system comprises at least two software deployment servers capable of providing services simultaneously, and different software deployment servers are respectively deployed on different main control boards of the cluster system;
the main control board sends a downloading indication message to the chassis board card according to the software version request, wherein the downloading indication message is used for indicating the chassis board card how to acquire the software version file of the target software group from the corresponding software deployment server;
after receiving the download request of the case board card, the main control board controls the software deployment server to send the software version file of the target software group to the case board card, so that the case board card deploys software according to the software version file.
The embodiment of the invention also provides a chassis board card, which comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is used for executing a first cluster system software deployment program stored in the memory so as to realize the steps of the first cluster system software deployment method; or the processor is used for executing a second cluster system software deployment program stored in the memory to realize the steps of the second cluster system software deployment method.
The embodiment of the invention also provides a cluster system which is characterized by comprising a plurality of chassis board cards, wherein the chassis board cards are in communication connection with each other, and each chassis board card is a chassis board card of which the processor can execute a first cluster system software deployment program; the main control boards with the software deployment servers are chassis boards, and the processor can execute a second cluster system software deployment program.
The embodiment of the present invention further provides a storage medium, where the storage medium stores at least one of a first cluster system software deployment program and a second cluster system software deployment program, and the first cluster system software deployment program can be executed by one or more processors to implement the steps of the first cluster system software deployment method; and the second cluster is used for deploying the second cluster system software.
According to the chassis board card, the cluster system, the software deployment method and the storage medium provided by the embodiment of the invention, when the cluster system is started, one chassis board card can send a software version request containing software group information in the cluster system, and a target software group required to be deployed by the board card is indicated through the software group information. And then, the chassis board receives download instruction messages sent by at least two software deployment servers in the cluster system according to the software version requests, wherein the download instruction messages can be used for instructing how to acquire the software version files of the target software group from the corresponding software deployment servers. The chassis board card can select a software deployment server as a target software deployment server of the board card according to the received download instruction messages, then download the software version file from the target software deployment server, and perform software deployment according to the acquired software version file. In the embodiment of the invention, at least two software deployment servers capable of providing services simultaneously exist in the cluster system, and each software deployment server is respectively deployed on different main control boards of the cluster system, so that in the starting stage of the cluster system, each chassis board card in the cluster system can select one of the software deployment servers to acquire the software version file corresponding to the target software group, thereby avoiding the problems that the pressure for deploying the software deployment server is large and the software version request of each chassis board card cannot be responded for a long time because all chassis board cards in the cluster system acquire the software version file from one software deployment server. At least two software deployment servers capable of providing services simultaneously are arranged in the cluster system, so that the request objects of all chassis board cards are dispersed, the pressure of a single main control board is reduced, more importantly, the efficiency of acquiring software version files by all chassis board cards is improved, and the starting time of the cluster system is shortened. On the other hand, because more than one main control board is used for deploying the software deployment server capable of providing the service, for one main control board, the corresponding software version files do not need to be provided for all the chassis boards in the cluster system, so that the main control board can have more time for synchronously forwarding the table entry data to the previously started chassis board, and the time for the cluster system to reach the service-capable state is further shortened.
Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a flowchart of a cluster system software deployment method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a star cluster system shown in the first embodiment of the present invention;
fig. 3 is a schematic diagram of a linear cluster system according to a first embodiment of the present invention;
fig. 4 is a flowchart illustrating that a chassis board sends a software version request and selects a target software deployment server according to a first embodiment of the present invention;
fig. 5 is a flowchart illustrating a main control board negotiating to create a primary deployment software group in the cluster system according to the second embodiment of the present invention;
fig. 6 is an optional flowchart of an upgrade process of a software deployment server in a cluster system according to a second embodiment of the present invention;
fig. 7 is a schematic diagram of a hardware structure of a chassis board card according to a third embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The first embodiment is as follows:
the cluster system in this embodiment mainly refers to a physical cluster system, each chassis of the physical cluster system usually includes two main control boards and multiple forwarding boards, and an auxiliary management board may be further included in a part of the chassis. The main control board is mainly used for deploying software service with a service control function, server software with an equipment management function and client software with the equipment management function, wherein the server software with the equipment management function comprises a software deployment server and the like, and the client software comprises software deployment client software and the like. And the local storage device of the main control unit board card stores software versions to be executed by the main control board, the forwarding board and other board cards. The forwarding board is mainly used for deploying software service with a service forwarding function and client software with an equipment management function, and the client software comprises software deployment client software and the like.
The software running in the cluster system has a plurality of software processes which are classified according to functions and can be divided into a plurality of software groups. Each software group has a plurality of attributes, one of which is whether the software group is active or standby. In general, only the active software group provides services, and the standby software group does not provide services to the outside during the period that the active software group normally provides services. Some software groups may be configured in units of chassis according to deployment requirements of each chassis on the software group, for example, for a software group with a function, one active a software group and one standby a software group may be configured in one chassis, in this case, a plurality of active a software groups may exist in the cluster system at the same time, and each active a software group is used to provide services to the chassis board card of the chassis where it is located. However, some software groups are set in a cluster system unit, for example, for a software group with b functions, only one active software group b and one standby software group b are set in one cluster system, and in this case, the active software group b needs to provide services for the cluster system. For a software group, such as a software group b, which is set in a cluster system unit, the software group may be referred to as a "software group in a unique software master state", and for a software group, such as a software group a, which is set in a chassis unit, the software group may be referred to as a "software group in a non-unique software master state".
In the related art, the software group to which the corresponding process of the software deployment server belongs is the only software group in the software master state, so that only one software deployment server provides services in the cluster system at the same time. This severely restricts the starting speed of the cluster system after the equipment is down and the system is upgraded, and affects the service experience of the user. In this embodiment, software deployment servers are deployed on at least two main control boards in the cluster system, and the at least two software deployment servers in the cluster system can provide services simultaneously. Therefore, a software deployment server for providing services is deployed on at least two main control boards of the cluster system. It can be understood that, although there are two main control boards in the cluster system in the related art to deploy the software deployment servers, the software deployment servers on the two main control boards cannot provide services at the same time, and only the software deployment server of the currently owned software group in the active state can provide services to the outside at the same time.
Please refer to an interactive flowchart of the cluster system software deployment method shown in fig. 1:
s102: the chassis board card sends a software version request containing software group information in the cluster system to which the board card belongs.
The chassis board card may send a software version request to the software deployment server in the process of deploying the software group, where the software version request includes software group information, and the software group information may indicate which software group or groups the chassis board card needs to deploy. In this embodiment, the software group that one chassis board needs to be deployed is referred to as a target software group of the chassis board, so that the software group information carried in the software version request actually indicates the target software group of the chassis board that sends the software version request to the software deployment server. Typically, a chassis board needs to deploy a resource management software group, which is a base software group. In addition, some main control boards need to deploy additional software groups besides the resource management software group, but these additional software groups are not deployed for each chassis board or even for each main control board. Which software groups need to be deployed by a chassis board card is determined by the software deployment server.
It can be understood that, because at least two software deployment servers providing services exist in the cluster system of this embodiment at the same time, the chassis board card is not specifically sent to one of the software deployment servers when sending the software version request. The chassis board card may send a software version request within a range of the cluster system in which the chassis board card is located, that is, the software version request may be sent to all software deployment servers in the cluster system, where the provisioning servers are deployed. In fig. 1, the software version request sent by the chassis board card is transmitted to the first software deployment server and the second software deployment server. It can be understood that, because the software deployment server is deployed on the main control board, the chassis board sends the software version request to the software deployment server, which is actually sending the software version request to the main control board on which the software deployment server is deployed. It is assumed in fig. 1 that a first main control board is deployed for the first software deployment server, and a second main control board is deployed for the second software deployment server. It should be understood that, although only the interaction between the chassis board and the first software deployment server and the second software deployment server is shown in fig. 1, in practice, if more software deployment servers capable of providing services to the outside at the same time are deployed in the cluster system, the chassis board may also interact with more software deployment servers, that is, more main control boards for deploying the software deployment servers.
Generally, a physical cluster system can be divided into a star cluster system and a line cluster system according to different connection modes, wherein the connection mode of each chassis in the star cluster system is a star topology structure, and the connection mode of each chassis in the line cluster system is a line topology structure. The star-type cluster system comprises a central switch case and a forwarding case, wherein the forwarding case is used for realizing a message forwarding function, and the central switch case can realize the intercommunication among the forwarding cases. In some examples of this embodiment, a star cluster system may include at least two central switch chassis and a plurality of repeater chassis, for example, please refer to fig. 2, which shows a connection diagram of the star cluster system: in fig. 2, the star cluster system 2 includes a first central switch chassis 21, a second central switch chassis 22, and four repeater chassis (a first repeater chassis 23a, a second repeater chassis 23b, a third repeater chassis 23c, and a fourth repeater chassis 23d, respectively). The first central switch chassis 21 is communicatively connected to the second central switch chassis 22, and the repeater chassis are connected to the two central switch chassis, respectively. Fig. 3 shows a line type cluster system 3, where the line type cluster system includes a plurality of forwarding chassis (for example, a first forwarding chassis 30a, a second forwarding chassis 30b, and a third forwarding chassis 30c in fig. 3) for forwarding a message, and each forwarding chassis is connected in pairs to implement an intercommunication function between the forwarding chassis. In this embodiment, whether in a star cluster system or a line cluster system, the chassis are connected by a hardware connection line, which may be a network cable, an optical fiber, or another hardware connection line.
S104: and at least two software deployment servers in the cluster system send a downloading indication message to the chassis board card according to the software version request.
After receiving the software version request, the software deployment server in the cluster system may send a download instruction message to the chassis board card that sent the software version request as a response, where the download instruction message is used to instruct the chassis board card how to download the software version file corresponding to the target software group from the software deployment server. In this embodiment, the download instruction message includes a download address when the software version file corresponding to the target software group is downloaded from the corresponding software deployment server. In this way, after the boxboard card receives the response corresponding to the software version request, if the software version file is selected to be downloaded from the corresponding software deployment server, the boxboard card can acquire the software version file of the target software group according to the download address in the download instruction message.
In some examples of this embodiment, each software deployment server providing services in the cluster system responds after receiving a software version request, and thus, after one chassis board sends one software version request, at least two download indication messages may be received.
S106: and the chassis board card selects one software deployment server as a target software deployment server of the board card according to each downloading indication message.
In this embodiment, after receiving the download instruction message fed back by each software deployment server, the chassis board may select one software deployment server from the software deployment servers as a target software deployment server according to the download instruction message, where the target software deployment server is a software deployment server for the chassis board to subsequently obtain a target software group software version file.
In some examples of this embodiment, the chassis board may randomly select one of the software deployment servers as the target software deployment server according to the download instruction message. In some other examples of this embodiment, the chassis board may select the target software deployment server according to the deployment location of the software deployment server: for example, the chassis card may determine the chassis where the software deployment server is located, and then preferentially select the software deployment server in the same chassis as the local card as the target software deployment server. In some other examples, the chassis board may determine a slot of a main control board where the software deployment server is located, and then preferentially select the software deployment server deployed on the board card as the target software deployment server. If one chassis board card determines that the chassis in which the chassis board card is located does not have the software deployment server, the chassis board card can randomly select the target software deployment server from the software deployment servers.
FIG. 4 is a flowchart illustrating the chassis board sending a software version request and selecting a target software deployment server:
s402: and the case board card sends a software version request and starts a receiving timer.
It can be understood that, because the chassis board does not have a specific sending object when sending the software version request, and is a generalized sending behavior, it is difficult for the chassis board to accurately predict how many responses will be received and when the responses of all software deployment servers in the cluster system will be received, but the chassis board cannot wait without limitation. Therefore, the start of the receiving timer by the chassis board actually sets a time window for the process of receiving the download instruction message, and the chassis board can continue to receive the download instruction message within the time window, and the chassis board will not download the download instruction message after the time window is exceeded.
S404: and the chassis board card judges whether the current message receiving timer finishes timing.
If the determination result is negative, S406 is executed, otherwise S420 is executed.
S406: and the chassis board card receives the downloading indication information.
S408: and the chassis board card determines whether the downloading indication message is valid.
If yes, go to step S410, otherwise discard the download indication message, and continue to step S404.
S410: and the chassis board card determines the deployment position information of the software deployment server which sends the downloading indication message.
S412: and the case board card determines whether the software deployment server is positioned on the case board card according to the deployment position information.
If yes, go to step S414, otherwise go to step S416.
S414: the software deploying server is selected as a target software server.
S416: and the case board card determines whether the software deployment server is positioned in the case or not according to the deployment position information.
If yes, go to step S414, otherwise go to step S418.
S418: and recording the information of the software deployment server.
S420: and randomly selecting one from the recorded software deployment servers as a target software deployment server.
In some examples of this embodiment, the download indication message sent by the software deployment server to the chassis board carries deployment position information of the software deployment server, where the deployment position information may include at least one of chassis identification information of a chassis where the software deployment server is located and slot identification information of the board where the software deployment server is located, and it is understood that the chassis identification information may be a chassis number and the slot identification information may be a slot number. In some examples of the present embodiment, the download indication message includes information content including specific deployment location information; for example, the download instruction message is a software version response message that is sent by the software deployment server to the chassis board according to the software version request, and the message content of the response message includes deployment location information.
In some other examples of this embodiment, the download instruction message does not include specific deployment location information, but after receiving the download instruction message, the chassis board card may determine the deployment location information of the software deployment server according to the source IP address and/or the source MAC address in the download instruction message. For example, in an example of this embodiment, the last three bits of the IP address of each chassis board in the cluster system may represent the chassis number, and the first three bits may represent the slot number corresponding to the chassis board. Therefore, after the chassis board card receives a software version response message sent by a software deployment server, information extraction can be carried out from the corresponding position of the message header of the response message, so that the deployment position information of the software deployment server is determined according to the preset rule. It should be understood that, if the deployment position information of the chassis board is to be embodied by using the content of at least one of the source IP address, the source MAC address, and the like of the chassis board, when the IP address or the MAC address is allocated to each chassis board in the cluster system, the IP address or the MAC address is generated for each chassis board according to the chassis number (or the slot number) of each chassis board in combination with a preset rule, where the preset rule is a rule agreed with other chassis boards in the cluster system in advance, and after receiving the download instruction message, the cluster system determines the chassis number (or the slot number) where the software deployment server is located according to the source IP address, the source MAC address determination chassis number carried in the download instruction message in combination with the same preset rule.
In other examples of this embodiment, the download indication message sent by the software deployment server to the chassis board card does not carry information that can represent the deployment location information, but in the cluster system, each chassis board card can store a mapping relationship between the deployment location information of each chassis board card and an IP address (or MAC address) of each chassis board card in the cluster system, so that, when one chassis board card receives the download indication message fed back by the software deployment server, the IP address (or MAC address) in the download indication message can be extracted, and then the deployment location information of the software deployment server that sends the download indication message is determined according to the pre-stored mapping relationship.
It can be understood that the second and third manners for determining the deployment location information of the software deployment server are similar and are determined according to the mapping relationship between the IP address (or MAC address) of the chassis board where the software deployment server is located and the deployment location information of the software deployment server, but in the second manner, the mapping relationship stored by each chassis board is a preset rule, while in the third manner, a specific corresponding relationship needs to be stored, and generally, there are many chassis boards in the cluster system, so that the second manner occupies less storage resources of the chassis boards.
S108: and the case board card downloads the software version file from the target software deployment server and deploys the software according to the software version file.
After the chassis board determines the target software deployment server, a software version downloading request may be sent to the target software deployment server according to the downloading indication information sent by the target software deployment server, and then a software version file of the target software group sent by the target software deployment server is received. In this embodiment, it is assumed that the target software deployment server determined by the chassis board in fig. 1 is the first software deployment server. And the software version file can indicate each software process corresponding to the target software group and the storage position of each software process in the cluster system, so that after the chassis board card acquires the software version file of the target software group, the corresponding software process can be downloaded to the corresponding position according to the indication of the software version file, the deployment and the starting of the software process are completed, and the deployment and the starting of the target software group are realized.
In some examples of the embodiment, there are at least six software deployment servers that are deployed on at least one main control board in each chassis of a cluster system, for example, there are six chassis in the star cluster system 2 shown in fig. 2, and there are at least six software deployment servers that are deployed on at least one main control board in each of the six chassis, so there are at least six software deployment servers that can simultaneously provide services in the star cluster system 2. In fig. 3, the wire star type cluster system 3 has a total of three chassis, and in the wire star type cluster system 3, at least three software deployment servers capable of providing services simultaneously exist. In other examples of this embodiment, for the star-type cluster system, it is required that each main control board in the central switch box is deployed with a software deployment server capable of providing services, and continuing to take the star-type cluster system 2 in fig. 2 as an example, in this star-type cluster system 2, because there are two central switch chassis and there are two main control boards in each central switch box, there should be at least four software deployment servers capable of providing services simultaneously in the star-type cluster system 2 shown in fig. 2.
In some examples of this embodiment, each main control board in the cluster system is deployed with a software deployment server that can provide a service, in which case, there are how many software deployment servers that can provide servers to the outside simultaneously for how many main control boards in the cluster system. The main control board of the cluster system can directly acquire the software version file of the target software group from the software deployment server where the main control board is located, and the non-main control board can acquire the software version file of the target software group from the software deployment server in the local box. Therefore, when the cluster system is restarted due to downtime or upgrading, the pressure of a single main control board can be greatly reduced, the efficiency of acquiring software version files by all chassis board cards is improved, the main control boards can complete synchronization of forwarded item data more quickly, the whole cluster system can reach a serviceable state in a shorter time, and the service experience of users is enhanced.
Example two:
in order to make the advantages and details of the cluster system software deployment method provided by the embodiment of the present invention clearer for those skilled in the art, the present embodiment will continue to explain the cluster system software deployment method on the basis of the foregoing embodiment:
it can be understood that the software deployment server is actually also a software process, the software process may also be divided into a certain software group according to functions, and a software deployment server to be deployed on a main control board is actually to create a software group where the software deployment server is to be deployed. Generally, in the process of starting a cluster system, after each main control board in the cluster system needs to negotiate for a period of time, it is determined on which main control boards software groups to which a software deployment server belongs are created, and main/standby state attributes of the software groups on each main control board. After a software group to which the software deployment server belongs is created on a main control board, a process corresponding to the software deployment server is started in the software group, and the software deployment service is started.
In the related art, the software group to which the software deployment server belongs (for convenience of introduction, the software group to which the software deployment server belongs is referred to as "deployment software group" for short) includes not only the software deployment server process but also other processes, so when each main control board negotiates creation and main/standby state attributes of the deployment software group, the negotiation content is large, and the negotiation time is naturally relatively long. However, in this embodiment, the deployment software group only includes the process corresponding to the software deployment server, and for other processes in the original deployment software group, the software group is additionally set. In this case, when the cluster system is restarted, when each main control board negotiates for the deployment software group, the negotiation may be performed only for the content related to the software deployment server, so that the negotiation for the deployment software group and the deployment of the software deployment server are completed as early as possible, and the software deployment server can be put into application as soon as possible.
It should be understood that the deployment software group includes only the process corresponding to the software deployment server, which is only an optional implementation manner in this embodiment, and this is not necessary, and in some other examples, the deployment software group may be the same as the deployment software group in the related art, and may also include other processes besides the software deployment server process.
In some examples of this embodiment, when negotiating about the deployment software group, each main control board negotiates about one active deployment software group and at least one standby deployment software group. It should be noted that, although each main control board in the related art may also negotiate one active deployment software group and one standby deployment software group for the deployment software group, the software deployment server in the standby deployment software group in the related art cannot provide services to the outside during the period that the software deployment server in the active deployment software group normally provides services. In this embodiment, the software deploying server in the active deploying software group and the software deploying server in the standby deploying software group may provide services to the outside at the same time.
It can be understood that, when negotiating about the deployment software group, each main control board may negotiate based on some rules, for example, in some examples, each main control board pre-agrees to elect the main control board with the smallest chassis number and the smallest slot number to deploy the active deployment software group, in this case, each main control board may send its own chassis number and slot number in the cluster system in a broadcast manner, then compare the chassis number and slot number in the received broadcast message with its own chassis number and slot number, and determine whether it is qualified to continue election according to the comparison result. For another example, in some other examples, each master control board in the star cluster system makes the agreement that the active deployment software group should be deployed on the master control board of the central switch chassis.
The negotiation process of each master control board for a deployment software group is described below with reference to the example given in fig. 5:
s502: the main control board judges whether the chassis is the central exchange chassis.
If yes, go to step S504, otherwise go to step S514.
In this embodiment, the cluster system is a star cluster system, and each main control board in the star cluster system makes an agreement that only the main control board in the central switch box can deploy the active deployment software group.
S504: the main control board issues own election information in the cluster system through broadcast messages.
In this embodiment, the selection information includes a chassis number and a slot number of the main control board, and software version information of software running on the main control board. Each main control board in the star cluster system agrees that only the main control board with the largest case number and the largest slot number can deploy the main deployment software group, and if the software version information of one main control board is not the latest, the main control board cannot create the deployment software group.
S506: and the main control board receives election information sent by other main control boards.
S508: the main control board judges whether the number of the case is smaller than that in the received election information.
If the determination result is yes, it indicates that the main control board is not necessarily the main control board with the largest box number in the cluster system, so the main control board performs S514, otherwise the main control board performs S510.
S510: the master control board judges whether the slot number of the master control board is smaller than the slot number in the received election information.
If the determination result is yes, it indicates that the main control board is not necessarily the main control board with the largest slot number in the cluster system, and the main control board performs S514, otherwise the main control board performs S512.
S512: the main control board judges whether the software version information of the main control board is smaller than the software version information in the received election information.
If the result of the determination is yes, it indicates that the main control board is not qualified to create a deployment software group, let alone to create a primary deployment software group, so that the main control board executes S514 to quit the election, otherwise, the main control board executes S516.
It is understood that the timing of the three determination processes in S508-S512 can be arbitrarily exchanged, and is not limited to the one in fig. 5.
S514: and the master control board quits the establishment and election of the main deployment software group.
S516: the main control board determines whether other election information is received.
If so, continuing to execute step S508, otherwise, indicating that the main control board has compared with all other main control boards in the cluster system, and as a result, the main control board has the largest case number and the largest slot number and runs with the latest software version.
S518: and the main control board determines that the main control board is the main control board for deploying the main deployment software group and informs each chassis board card in the cluster system.
After a master control board determines that it is the master control board that can create the active deployment software group, it can notify each chassis board card in the cluster system that it has become the master control board of the active deployment software group.
In some other examples of this embodiment, after the active deployment software group is created, the software deployment server in the software group notifies each main control board in the cluster system of an additional software group that needs to be deployed.
In some examples of this embodiment, although both the standby deployment software group and the software deployment server in the active deployment software group can provide services, the software deployment servers in the active deployment software group and the standby deployment software group may have a slight difference in function: for example, in some examples of this embodiment, when a manager needs to upgrade a software deployment server, the manager may upgrade only the software deployment server in the primary deployment software group, and for other software deployment servers in the cluster system, the manager may synchronously upgrade the software deployment servers in the primary deployment software group after completing upgrading themselves, please refer to an optional flowchart of an upgrade process of the software deployment server in the cluster system shown in fig. 6:
s602: the main control board receives a software upgrading instruction aiming at a software deployment server on the chassis board card.
In this embodiment, the software upgrading instruction received by the main control board may be manually issued by a manager, where the software upgrading instruction is used to instruct to upgrade the software deployment server deployed on the main control board. It should be understood that the main control board executing the flow in fig. 6 should be the main control board on which the deployment software is in the active state.
S604: and the main control board upgrades the software deployment server on the local box board card according to the software upgrading instruction.
The main control board can upgrade the software deployment server on the local card after receiving the software upgrading instruction. In the software upgrading instruction, the manager can indicate a first mapping relation between each case board card and the target software unit after upgrading, a second mapping relation between each software group and the software process and a third mapping relation between each software process and the storage position to the main control board.
S606: and the master control board synchronously updates information to the master control boards where other software deployment servers are located in the cluster system.
After the master control board finishes upgrading the software deployment server on the own edition card, the master control board can synchronously upgrade information to the master control board where other software deployment servers are located in the cluster system, and as can be understood, the upgrade information synchronized by the main control board to other main control boards may include all information in the software upgrade instruction, or may only include the second mapping relationship and the third mapping relationship in the software upgrade instruction, because only the software deployment server in the active deployment software group needs to indicate the software group which needs to be deployed to other main control boards according to the first mapping relation, after the software deployment server in each standby software group receives the software version request of each chassis board card, the download indication information may be generated only according to the second mapping relationship and the third mapping relationship, so the main control board deploying the spare deployment software group may not need the first mapping relationship.
Of course, it can be understood by those skilled in the art that, under the condition that the number of software deployment servers in the cluster system is not large, the administrator may also manually upgrade these software deployment servers respectively, without depending on the synchronous upgrade of the software deployment servers in the active deployment software group to the software deployment servers in the standby deployment software group, but, relatively speaking, the upgrade scheme shown in fig. 6 can significantly reduce the upgrade burden of the administrator.
In the cluster system software deployment method provided by this embodiment, on one hand, the efficiency of acquiring software version files by each chassis board is improved by arranging two or more software deployment servers which provide services at the same time in the cluster system, and the load of a single main control board is reduced, so that the main control board deploying the software deployment servers can complete synchronization of forwarding table data to the chassis board which is started in advance, and further the whole cluster system can complete startup as soon as possible, and a serviceable state is achieved. On the other hand, the cluster system is independently arranged in one deployment software group aiming at the process corresponding to the software deployment server, so that the negotiation content of each main control board in the negotiation of the deployment software group is reduced, the deployment of the software deployment server is accelerated, and the time length from the start of the cluster system to the service-available state is further shortened.
Moreover, when the software deployment servers in the cluster system need to be upgraded, the administrator can only send a software upgrading instruction to the software deployment servers in the primary deployment software group to complete the upgrading of the software deployment servers in the primary deployment software group, and the upgrading of other software deployment servers in the cluster system can be automatically completed by the software deployment servers in the primary deployment software group, so that the burden of the administrator is reduced.
Example three:
the present embodiments provide a storage medium including volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact disk Read-Only Memory), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
The embodiment further provides two computer programs (or called computer software), which are a first cluster system software deployment program and a second cluster system software deployment program, respectively, where the first cluster system software deployment program and the second cluster system software deployment program may be distributed on the storage medium and executed by a computing device to implement at least one step of the method for deploying cluster system software on the side of a chassis board card (hereinafter referred to as a "request-side chassis board card") requesting a software version file in each of the foregoing embodiments; the second cluster system software deployment program may be distributed on the storage medium and executed by the computing device to implement at least one step of the cluster system software deployment method on the master control board (hereinafter referred to as "response-side master control board") side of the software deployment server in the foregoing embodiments. Also, in some cases, at least one of the steps shown or described may be performed in a different order than described in the above embodiments.
The present embodiments also provide a computer program product comprising a computer readable means on which a computer program as shown above is stored. The computer readable means in this embodiment may include a computer readable storage medium as shown above.
In some examples of this embodiment, the computer readable device is a chassis board, and the chassis board may be a main control board, a forwarding board or an auxiliary management board in a chassis of the cluster system. In this embodiment, software deployment servers are deployed on at least two main control boards in the cluster system, and the at least two software deployment servers in the cluster system can provide services simultaneously. Therefore, a software deployment server for providing services is deployed on at least two main control boards of the cluster system. Please refer to fig. 7, which illustrates a hardware structure diagram of the chassis board card: the chassis board 70 includes a processor 71, a memory 72, and a communication bus 73, wherein the communication bus 73 is used for realizing connection communication between the processor 71 and the memory 72. In some examples of this embodiment, the memory 72 stores at least one of the first cluster system software deployment program and the second cluster system software deployment program described above. For example, in some examples, the chassis board 70 may execute the first cluster system software deployment program stored in the memory 72 for the requesting chassis board processor 71 to implement the steps of the requesting chassis board side cluster system software deployment method in the foregoing embodiments:
the processor 71 sends a software version request containing software group information in the cluster system to which the chassis board 70 belongs, where the software group information is used to indicate a target software group that the chassis board 70 needs to deploy. Subsequently, the processor 71 receives a download instruction message sent by at least two software deployment servers in the cluster system according to the software version request, where the download instruction message is used to instruct how to obtain the software version file of the target software group from the corresponding software deployment server. Then, the processor 71 selects one software deployment server as a target software deployment server of the chassis board 70 according to each download instruction message, downloads the software version file from the target software deployment server, and deploys software according to the software version file.
In some examples of this embodiment, the download instruction message includes deployment location information of the software deployment server, which is used to indicate a deployment location of the software deployment server that sent the download instruction message; when the processor 71 selects one software deployment server as the target software deployment server of the chassis board 70 according to each download instruction message, the processor 71 may obtain the deployment position information of each software deployment server from each download instruction message, and then the processor 71 selects the target software deployment server according to the deployment position information of each software deployment server.
In some examples of this embodiment, the deployment location information includes chassis identification information of a chassis in which the software deployment server is located, and when the processor 71 selects the target software deployment server according to the location information of each software deployment server, the software deployment server in the same chassis as the chassis board 70 may be preferentially selected as the target software deployment server according to the chassis identification information corresponding to each software deployment server;
in other examples of this embodiment, the deployment position information includes slot identification information of a board where the software deployment server is located, and when the processor 71 selects the target software deployment server according to the position information of each software deployment server, the software deployment server on the same board as the chassis board 70 may be preferentially selected as the target software deployment server according to the slot identification information corresponding to each software deployment server.
Optionally, each main control board in the cluster system is deployed with a software deployment server, and the software deployment servers on each main control board can provide services at the same time.
In some examples of this embodiment, the chassis board 70 is a response side main control board, and the processor 71 may execute the second cluster system software deployment program stored in the memory 72 to implement the steps of the response side main control board side cluster system software deployment method in the foregoing embodiments:
the processor 71 receives a software version request containing software group information sent by a request-end chassis board card in the cluster system, where the software group information is used to indicate a target software group that the request-end chassis board card needs to deploy. Then, the processor 71 sends a download instruction message to the requesting chassis board according to the software version request, where the download instruction message is used to instruct the requesting chassis board how to obtain the software version file of the target software group from the software deployment server on the chassis board 70. If the processor 71 receives the download request of the request-side chassis board card, the processor 71 controls the software deployment server on the chassis board card 70 to send the software version file of the target software group to the request-side chassis board card, so that the request-side chassis board card deploys software according to the software version file.
In some examples of this embodiment, the download indication message includes deployment position information, where the deployment position information includes chassis identification information and/or slot identification information corresponding to the chassis board 70, and the deployment position information is used to request the end chassis board to determine whether to download the software version file of the target software group from the software deployment server on the chassis board 70.
If the deployment software group to which the process corresponding to the software deployment server on the chassis board 70 belongs is in the active state, the processor 71 may further receive a software upgrade instruction for the software deployment server on the chassis board 70, and then upgrade the software deployment server on the chassis board 70 according to the software upgrade instruction. After the software deployment server on the chassis board card 70 is upgraded, the processor 71 synchronizes upgrade information to the main control board where the other software deployment servers in the cluster system are located, so as to upgrade the other software deployment servers in the cluster system.
In some examples of this embodiment, the process corresponding to the software deployment server belongs to the deployment software group, and only the process corresponding to the software deployment server is included in the deployment software group; before receiving the software version request containing the software group information sent by the board card in the cluster system, the processor 71 may also negotiate with each main control board in the cluster system to determine one main control board for deploying the active deployment software group and at least one main control board for deploying the standby deployment software group, where the software deployment server in the active deployment software group and the software deployment server in the standby deployment software group can provide services simultaneously.
In addition, this embodiment further provides a cluster system, where the cluster system includes a plurality of chassis boards, and the chassis boards may be divided into a main control board and a forwarding board. The chassis boards can be in direct or indirect communication connection, and the indirect communication connection means that the two chassis boards are in communication connection through other chassis boards.
In this embodiment, the processor of each chassis board in the cluster system can execute the first cluster system software deployment program to implement the steps of the cluster system software deployment method on the side of the request-side chassis board in each embodiment. In addition, at least two main control boards in the cluster system are all deployed with software deployment servers capable of providing services simultaneously, that is, there are at least two response end main control boards in the cluster system, and a processor of the response end main control board can execute a second cluster system software deployment program, so as to implement the steps of the cluster system software deployment method on the response end main control board side in the foregoing embodiments. In some examples of this embodiment, a software deployment server is deployed on each main control board in the cluster system, and the software deployment servers on each main control board can provide services at the same time.
In the enclosure board card, the cluster system, and the storage medium provided in this embodiment, because at least two software deployment servers capable of providing services simultaneously exist in the cluster system, and each software deployment server is respectively deployed on different main control boards of the cluster system, each enclosure board card in the cluster system can select one of the software deployment servers to obtain a software version file corresponding to a target software group in a start-up stage of the cluster system, so that a problem that the software deployment server is under high pressure when all enclosure board cards in the cluster system obtain the software version file from one software deployment server, and a software version request of each enclosure board card cannot be responded for a long time is solved. At least two software deployment servers capable of providing services simultaneously are arranged in the cluster system, so that the request objects of all chassis board cards are dispersed, the pressure of a single main control board is reduced, more importantly, the efficiency of acquiring software version files by all chassis board cards is improved, and the starting time of the cluster system is shortened. On the other hand, because more than one main control board is used for deploying the software deployment server capable of providing the service, for one main control board, the corresponding software version files do not need to be provided for all the chassis boards in the cluster system, so that the main control board can have more time for synchronously forwarding the table entry data to the previously started chassis board, and the time for the cluster system to reach the service-capable state is further shortened.
It will be apparent to those skilled in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software (which may be implemented in computer program code executable by a computing device), firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit.
In addition, communication media typically embodies computer readable instructions, data structures, computer program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to one of ordinary skill in the art. Thus, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (12)
1. A cluster system software deployment method comprises the following steps:
the method comprises the steps that a chassis board card sends a software version request containing software group information in a cluster system to which the chassis board card belongs, wherein the software group information is used for indicating a target software group which needs to be deployed by the chassis board card, at least two software deployment servers capable of providing services simultaneously exist in the cluster system, and different software deployment servers are respectively deployed on different main control boards of the cluster system;
the chassis board card receives download indication messages sent by at least two software deployment servers in the cluster system according to the software version request, wherein the download indication messages are used for indicating how to acquire the software version files of the target software group from the corresponding software deployment servers;
the chassis board card selects one software deployment server as a target software deployment server according to the downloading indication message;
and the case board card downloads the software version file from the target software deployment server and deploys the software according to the software version file.
2. The cluster system software deployment method of claim 1, wherein the download instruction message includes deployment location information, and the deployment location information is used to indicate a deployment location of a software deployment server that sends the download instruction message; the case board card selecting one software deployment server as a target software deployment server according to the download indication message comprises:
the chassis board card acquires deployment position information corresponding to the software deployment server from the received download indication message;
and the chassis board card selects a target software deployment server according to the acquired deployment position information.
3. The cluster system software deployment method of claim 2, wherein the deployment location information includes chassis identification information of a chassis in which the software deployment server is located, and the chassis board selecting the target software deployment server according to the acquired deployment location information includes: the case board card preferentially selects a software deployment server in the same case as the case board card as a target software deployment server according to the acquired case identification information corresponding to the software deployment server;
or the like, or, alternatively,
the deployment position information includes slot position identification information of a board where the software deployment server is located, and the selecting, by the chassis board, the target software deployment server according to the acquired deployment position information of the software deployment server includes: and the chassis board card preferentially selects a software deployment server on the same board card as a target software deployment server according to the acquired slot position identification information corresponding to the software deployment server.
4. The cluster system software deployment method of any one of claims 1 to 3, wherein a software deployment server is deployed on each main control board in the cluster system, and the software deployment servers on each main control board can provide services simultaneously.
5. A cluster system software deployment method comprises the following steps:
the method comprises the steps that a main control board receives a software version request containing software group information sent by a chassis board card in a cluster system, wherein the software group information is used for indicating a target software group which needs to be deployed by the chassis board card; the cluster system comprises at least two software deployment servers capable of providing services simultaneously, and different software deployment servers are respectively deployed on different main control boards of the cluster system;
the main control board sends a downloading indication message to the chassis board card according to the software version request, wherein the downloading indication message is used for indicating the chassis board card how to acquire the software version file of the target software group from the corresponding software deployment server;
after receiving the download request of the case board card, the main control board controls the software deployment server to send the software version file of the target software group to the case board card, so that the case board card deploys software according to the software version file.
6. The cluster system software deployment method of claim 5, wherein the download indication message includes deployment location information, the deployment location information includes chassis identification information and/or slot identification information of the main control board, and the deployment location information is used for enabling the chassis board to determine whether to download the software version file of the target software group from the software deployment server on the main control board.
7. The cluster system software deployment method of claim 5 or 6, wherein a software deployment server is deployed on each main control board in the cluster system, and the software deployment servers on each main control board can provide services simultaneously.
8. The cluster system software deployment method according to claim 5 or 6, wherein the process corresponding to the software deployment server belongs to a deployment software group, and if the deployment software group on the main control board is in the active state, the cluster system software deployment method further includes:
the main control board receives a software upgrading instruction aiming at the software deployment server;
the main control board upgrades the software deployment server according to the software upgrading instruction;
and the master control board synchronizes upgrading information to the master control boards where other software deployment servers in the cluster system are located so as to upgrade the other software deployment servers in the cluster system.
9. The cluster system software deployment method of claim 5 or 6, wherein the process corresponding to the software deployment server belongs to a deployment software group, and the deployment software group only includes the process corresponding to the software deployment server; before the main control board receives a software version request containing software group information sent by a chassis board card in the cluster system, the method further comprises the following steps:
the main control board negotiates with other main control boards in the cluster system to determine one main control board for deploying the active deployment software group and at least one main control board for deploying the standby deployment software group, and the software deployment server in the active deployment software group and the software deployment server in the standby deployment software group can provide services at the same time.
10. A chassis board card comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute a first cluster system software deployment program stored in the memory to implement the steps of the cluster system software deployment method according to any one of claims 1 to 4; or the processor is configured to execute a second cluster system software deployment program stored in the memory to implement the steps of the cluster system software deployment method according to any one of claims 5 to 9.
11. A cluster system, comprising a plurality of chassis boards, wherein the chassis boards are communicatively connected to each other, and the chassis boards are the chassis boards of claim 10 in which the processor is capable of executing a first cluster system software deployment program; the plurality of chassis board cards are partially main control boards, at least two main control boards in the cluster system are respectively provided with a software deployment server capable of providing services at the same time, and the main control board provided with the software deployment server is the chassis board card of which the processor can execute the second cluster system software deployment program in claim 10.
12. A storage medium storing at least one of a first cluster system software deployment program executable by one or more processors to implement the steps of the cluster system software deployment method as claimed in any one of claims 1 to 4 and a second cluster system software deployment program; the second cluster system software deployment program is executable by one or more processors to implement the steps of the cluster system software deployment method as claimed in any one of claims 5 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010592519.9A CN113835715A (en) | 2020-06-24 | 2020-06-24 | Case board card, cluster system, software deployment method and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010592519.9A CN113835715A (en) | 2020-06-24 | 2020-06-24 | Case board card, cluster system, software deployment method and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113835715A true CN113835715A (en) | 2021-12-24 |
Family
ID=78964953
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010592519.9A Pending CN113835715A (en) | 2020-06-24 | 2020-06-24 | Case board card, cluster system, software deployment method and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113835715A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115150317A (en) * | 2022-06-22 | 2022-10-04 | 杭州迪普科技股份有限公司 | Routing table item issuing method and device, electronic equipment and computer readable medium |
-
2020
- 2020-06-24 CN CN202010592519.9A patent/CN113835715A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115150317A (en) * | 2022-06-22 | 2022-10-04 | 杭州迪普科技股份有限公司 | Routing table item issuing method and device, electronic equipment and computer readable medium |
| CN115150317B (en) * | 2022-06-22 | 2023-09-12 | 杭州迪普科技股份有限公司 | Routing table entry issuing method and device, electronic equipment and computer readable medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109104318B (en) | Method for realizing cluster self-adaptive deployment | |
| US9999030B2 (en) | Resource provisioning method | |
| WO2019237588A1 (en) | Linux virtual server creation method, device, computer device and storage medium | |
| WO2014169870A1 (en) | Virtual network element automatic loading and virtual machine ip address acquisition method and system, and storage medium | |
| CN108958742A (en) | A kind of method of batch installing operating system, relevant device and system | |
| CN106549789B (en) | Method and system for realizing server installation | |
| CN111880902A (en) | Pod creation method, device, equipment and readable storage medium | |
| CN101478429A (en) | Method, system and equipment for version upgrade | |
| CN112328262A (en) | Deployment method, system and device of operating system and electronic equipment | |
| CN112583712B (en) | Block chain router and block chain network system | |
| CN110716787A (en) | Container address setting method, apparatus, and computer-readable storage medium | |
| CN112187958A (en) | Method and device for registering, discovering and forwarding microservice | |
| CN108549542A (en) | A kind of file dispositions method, device and equipment | |
| CN112783646A (en) | Stateful application containerization deployment method and device | |
| CN110933036A (en) | Cloud game service system and server | |
| US10289402B2 (en) | Collaborative maintenance of software programs | |
| CN111049682B (en) | Method, system and central network equipment for realizing uninterrupted service upgrade | |
| CN113835715A (en) | Case board card, cluster system, software deployment method and storage medium | |
| CN110768812A (en) | Server management system and method | |
| CN112667293B (en) | Method, device and storage medium for deploying operating system | |
| CN113268254A (en) | Cluster system installation method and device, electronic equipment and storage medium | |
| US10592221B2 (en) | Parallel distribution of application services to virtual nodes | |
| CN111752576A (en) | Forwarding system deployment method based on 5G data, terminal and storage medium | |
| CN115333933B (en) | Automatic management method, medium and equipment for servers on machine room | |
| JP2015099547A (en) | Software update method, software update apparatus, software update program, and software update system |
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 |