CN115729610A - Operation and maintenance management method and system for components in cloud native environment - Google Patents
Operation and maintenance management method and system for components in cloud native environment Download PDFInfo
- Publication number
- CN115729610A CN115729610A CN202211581516.0A CN202211581516A CN115729610A CN 115729610 A CN115729610 A CN 115729610A CN 202211581516 A CN202211581516 A CN 202211581516A CN 115729610 A CN115729610 A CN 115729610A
- Authority
- CN
- China
- Prior art keywords
- resource
- binary data
- maintenance management
- cloud native
- components
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses an operation and maintenance management method of a component in a cloud native environment, which comprises the following steps: acquiring a helmchart packet; compressing and encoding the helmchart packet into binary data, and storing the binary data into a configmap resource of the cluster; extracting partial binary data from the configmap resource to create a custom resource; acquiring a dynamic link library according to the user-defined resources; decoding binary data in the user-defined resources through a helm template to obtain a yaml resource file; deploying the cloud native components according to the yaml resource file; and carrying out operation and maintenance management on the cloud native component through the dynamic link library. The invention also discloses an operation and maintenance management system of the components in the cloud native environment. The method saves the chart package through the configmap resource, can avoid using a chart package warehouse, reduces external dependent components, and improves the availability of the system. The native helm template is installed in one step, and resources are analyzed and created through the chart package, so that the flexibility of deployment is improved.
Description
Technical Field
The invention relates to the technical field of cloud native application, in particular to an operation and maintenance management method and system for a component in a cloud native environment.
Background
The helm in the cloud native environment is the package manager of the main process. For compiling, slightly complicated deployment engineering adopts a helminstall mode to deploy the application. The helm official provides a warehouse https:// artifacthub. Io/, contains a large number of reusable and mature application packages, and is convenient for rapid deployment and application in a cloud native environment.
The helm uses a packing format called chart. A graph is a collection of files that describes a set of related kubernets resources. Wherein the templates folder is followed by a series of yaml deployment files, but contains various variable templates, which cannot be directly used. Where the values.yaml file is used as a configuration file to replace specific variables at the time of final deployment. However, the software package is deployed in the cloud native environment in a chart package hellinstall mode, only the deployment capability is provided, and the capability of expanding custom operation and maintenance is lacked; meanwhile, certain standardized operations are troublesome to implement, for example, information of a unified company/team/responsible person needs to be added to the resource, and subsequent operation and maintenance can be managed more easily, so that only the resource file in each chart package can be modified at present.
A controller schema efficient extension cloud-native platform is provided in kubernets. However, the management of the cloud native components can be realized through the cloud native controller written in the controller mode, but only corresponding API capabilities are provided, and specific implementation methods, deployment, operation and maintenance capabilities are not provided. For example, the deployment of resources also needs to be realized by coding, a large amount of codes and logic judgment are needed, and the capacity can be completely replaced by a chart packet, which is more standard. While reducing meaningless encoding and bugs.
The method can realize the palm operator constructed by the framework, and has the effects of generating the custom resource without coding and calling the palm pilot to create the resource by using the custom resource. However, only the helmchart package deployed by using the custom resource is packaged, the function is single, the expansion cannot be performed, and the complexity of the system is increased by depending on an external component.
Meanwhile, when the cloud native environment management component is used daily, since the version needs to be updated frequently, different versions (including the custom resource attribute format and the controller code logic) are inconsistent, and controllers of different versions and custom resources of different versions cannot be compatible.
Disclosure of Invention
The invention aims to provide a method and a system for operation and maintenance management of components in a cloud native environment, which are rapid and convenient to deploy.
In order to solve the technical problem, the invention provides an operation and maintenance management method for components in a cloud native environment, which comprises the following steps:
acquiring a helmchart packet;
compressing and encoding the helmchart packet into binary data, and storing the binary data into a configmap resource of the cluster;
extracting partial binary data from the configmap resource to create a custom resource;
acquiring a dynamic link library according to the user-defined resources;
decoding binary data in the user-defined resources through a helm template to obtain a yaml resource file;
deploying the cloud native components according to the yaml resource file;
and carrying out operation and maintenance management on the cloud native component through the dynamic link library.
Preferably, the method further comprises the following steps:
calculating a hash value of binary data in the user-defined resource;
and updating the self-defined resource when the hash value of the binary data in the self-defined resource changes.
Preferably, the computing the hash value of the binary data in the user-defined resource specifically includes the following steps:
when the configuration of the binary data in the custom resource is modified, a hash value of the binary data in the custom resource is calculated.
Preferably, the obtaining of the helmchart packet specifically comprises the following steps:
the helmchart package is downloaded from an open source community or written.
The invention also provides an operation and maintenance management system of the components in the cloud native environment, which comprises the following components:
the acquisition module is used for acquiring the helmchart packet;
the compression coding module is used for compressing and coding the helmchart packet into binary data and storing the binary data into a configmap resource of the cluster;
the custom resource management module is used for extracting part of binary data from the configmap resource to create a custom resource;
the version management module is used for acquiring the dynamic link library according to the user-defined resources;
the decoding module is used for decoding binary data in the user-defined resources through the palm template to obtain a yaml resource file;
the deployment module is used for deploying the cloud native components according to the yaml resource file;
and the operation and maintenance management module is used for performing operation and maintenance management on the cloud native component through the dynamic link library.
Compared with the prior art, the invention has the following beneficial effects:
1: the Chart package is stored through the configmap resource, so that a Chart package warehouse can be avoided, external dependent components are reduced, and the availability of the system is improved.
2: from native helm one-step installation to analysis through a chat packet, custom attribute modification and resource creation, the custom attribute modification can be expanded, and the deployment flexibility is increased.
3: and by adding a plug-in mode, the operation and maintenance logic can be modified without changing the basic code. The system is decoupled, and the complexity of system management is reduced.
4: the active operation and maintenance, the passive operation and maintenance and the health check are standardized, and plug-ins can be provided for expansion, so that the expansibility and the standardization of the operation and maintenance are increased.
5: after the version is upgraded, a new chart package and a plug-in can be added and are compatible with the old operation and maintenance logic, so that the compatibility of multiple versions is realized.
Drawings
The following describes embodiments of the present invention in further detail with reference to the accompanying drawings.
FIG. 1 is a schematic flow chart of a method for managing operation and maintenance of a component in a cloud native environment according to the present invention;
FIG. 2 is a schematic view of an operation and maintenance management process;
FIG. 3 is a schematic diagram of an intelligent operation and maintenance flow;
FIG. 4 is a schematic diagram of a multi-version management architecture;
FIG. 5 is a multi-version management flow diagram;
fig. 6 is a deployment flow diagram.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, but rather construed as limited to the embodiments set forth herein.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if," as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination," depending on the context.
The invention is described in further detail below with reference to figures 1-6:
as shown in fig. 1, the present invention provides an operation and maintenance management method for components in a cloud native environment, including the following steps:
acquiring a helmchart packet;
compressing and coding the helmchart packet into binary data, and storing the binary data into a configmap resource of a cluster;
extracting partial binary data from the configmap resource to create a custom resource;
acquiring a dynamic link library according to the user-defined resources;
decoding binary data in the user-defined resources through a helm template to obtain a yaml resource file;
deploying the cloud native components according to the yaml resource file;
and carrying out operation and maintenance management on the cloud native component through the dynamic link library.
In a preferred embodiment, the step of extracting part of binary data from the configmap resource to create the custom resource further comprises the following steps:
calculating the hash value of binary data in the user-defined resource;
and updating the self-defined resource when the hash value of the binary data in the self-defined resource changes.
In a preferred embodiment, the calculating the hash value of the binary data in the user-defined resource specifically includes the following steps:
when the configuration of the binary data in the custom resource is modified, a hash value of the binary data in the custom resource is calculated.
In a preferred embodiment, the obtaining of the helmchart packet specifically includes the following steps:
the helmchart package is downloaded from an open source community or written.
The invention also provides an operation and maintenance management system of the components in the cloud native environment, which comprises the following components:
the acquisition module is used for acquiring the helmchart packet;
the compression coding module is used for compressing and coding the helmchart packet into binary data and storing the binary data into a configmap resource of the cluster;
the custom resource management module is used for extracting part of binary data from the configmap resource to create a custom resource;
the version management module is used for acquiring the dynamic link library according to the user-defined resources;
the decoding module is used for decoding binary data in the user-defined resources through the helm template to obtain a yaml resource file;
the deployment module is used for deploying the cloud native components according to the yaml resource file;
and the operation and maintenance management module is used for performing operation and maintenance management on the cloud native component through the dynamic link library.
In order to better illustrate the technical effects of the invention, the invention provides the following specific examples to illustrate the technical process:
a deployment, operation and maintenance management method of a component under a cloud native component is provided. The method mainly comprises three parts of rapid deployment, intelligent operation and maintenance in annotation of metadata information and multi-version management.
The deployment needs to depend on self-defined resources, and the designed structure also comprises two parts of deployment and operation and maintenance. Wherein the attributes of the deployment section include configuration attributes in the corresponding chart package value.
Before deployment, chart packages need to be integrated into a cluster, and the steps are as follows:
(1): and downloading a corresponding component helmchart package from the open source community or writing a chart package for the component.
(2): compressing and encoding the chart packet into binary data, storing the binary data into a configmap resource of the cluster, and if a plurality of chart packets exist, designating different keys as the name of the chart packet.
The specific deployment process is as shown in fig. 6:
1: the deployment application needs to create a corresponding custom resource, and the resource attribute needs to include the configmap resource name created in the previous step (or adopt a default value), the key of the chart package, and the configuration of the chart package (which may cover the configuration information in the values.
The deployment controller inquires corresponding configmap resources from the cluster according to the attributes in the custom resources, decodes the encoded binary data according to the key value, restores the encoded binary data into a chart packet, and places the chart packet in the temporary directory.
2: reading the chart package by the deployment controller, covering the configuration in value. Yaml with the configuration value in the self-defined resource as the configuration with high priority, decoding the chart through the palm template engine, converting the chart into a standard resource format in a cloud native platform in a memory, namely a series of yaml resource files (the files can be directly used for creating resources through a command line client side)
3: the deployment controller also needs to convert resources in the format of yaml, and adds description information related to some projects and organizations, so that filtering is convenient in the operation and maintenance process; and identifying metadata information such as resource groups, version numbers, resource names and the like of each resource in the yaml resource file.
4: and checking whether the resource type exists in the cluster or not through metadata information (resource group, version number and resource name), and if not, creating. And performing md5hash calculation on the configuration information in the custom resource and storing the configuration information in the annotation. The hash value is calculated before each update, and the deployment update/upgrade is carried out only if the configuration is inconsistent, so that the repeated execution of the flow is avoided. When the resource is created/updated, a mark attribute is added in the annotation to mark that the update is completed.
Each time, the configuration (i.e., config attribute) md5 in the custom resource is hash-operated, and the result is recorded, such as the result abcdef. And when the configuration in the custom resource is manually modified, performing md5hash calculation again, when the result is abcsee and is inconsistent with the last recorded result, representing that the configuration is changed, and comparing the hash value to judge whether the configuration is changed without comparing all configuration contents.
Through the above steps, the deployment controller deploys the cloud native components according to the yaml resource file and the corresponding resource type.
In the operation and maintenance flow, a pluggable mode is provided in a dynamic link library mode for facilitating code management and decoupling, and the code of a basic controller does not need to be modified. The plug-in provides an interface for 4 operations, as shown in fig. 2;
health examination: the health check is to check the health status of the application itself.
And (3) state acquisition: acquiring state information of a cluster component; the state information includes internal configuration, roles, and the like.
Active operation and maintenance: and the active operation and maintenance executes the corresponding operation and maintenance state according to the user-defined resource attribute state. Such as updating configuration, upgrading, etc.
Passive operation and maintenance: passive operation and maintenance is the operation and maintenance performed when the health check fails. The attributes of the custom resource and the running state of the current component need to be passed.
The operation and maintenance controller may obtain metadata information according to the deployment controller, as shown in fig. 3;
and filtering the current container list to obtain. And sequentially traverse the containers, first performing a health check.
The health check defines several general health check modes in advance, and the plug-in can directly use the following modes to carry out the health check and can also be realized in a self-defining mode.
1. Detection of the icmp protocol: i.e. to try to ping the container ip several times.
2. tcp port probing mode: the container ip and the port are probed.
3. http request probing: and carrying out survival detection by configuring an http interface.
4. Self-defining detection mode: user input is required by way of shell scripts.
When the health check fails, a passive operation and maintenance interface needs to be called to realize the user-defined operation and maintenance operation. And the user-defined active operation and maintenance interface is called only when the health check is successful. And finally, storing the state of the current component into the state of the user-defined resource through a state acquisition interface.
Incompatible multi-version simultaneous management of components is to be achieved. In the invention, deployment and operation and maintenance are already decomposed into a chart package and a dynamic link library plug-in, and the two parts can be decoupled. The simultaneous management of multiple versions is realized, and only one version attribute version needs to be added to the custom resource, so that the controller loads the chart package and the plug-ins containing suffixes of different version attributes according to different version attributes, and then executes corresponding processes in the main deployment and operation and maintenance processes, as shown in fig. 4 and 5.
Take the management of a redis cluster in a cloud native cluster as an example.
The chart package needs to be pre-selected. Wherein the template file contains necessary resources, such as stateful, configmap, service, and the like. And after the creation, storing the chat packet in the configmap resource in a two-step mode.
Secondly, a main operation and maintenance method in a corresponding dynamic link library plug-in is needed to be realized, the plug-in expands the operation and maintenance capability in a dynamic link library mode, and provides a specific operation and maintenance interface to realize the operation and maintenance of the application, and the method comprises the following steps:
and (3) state acquisition: and accessing each redis component to execute a clusterinfo/clusterinodeCommand to acquire the states of the redis cluster and the node according to the information for providing the redis.
Health examination: and connecting the redis and judging whether the cluster state is normal and whether the node number is consistent in the set state.
Passive operation and maintenance: the passive operation and maintenance operation can be added according to the actual requirement, such as the following 2 operation and maintenance operations. If the cluster is not initialized, executing cluster initializing operation; if a cluster node is lost, a rejoin of the cluster is attempted.
Active operation and maintenance: under normal conditions, actively trigger commands, such as the following 2 operation and maintenance operations. A command attribute, if the attribute is not null, executing the command of the attribute for all instances; the fragment rebalancing operation is carried out, if the attribute is not null, the data is re-evenly distributed for all the data fragments, and the uneven distribution caused by excessive data of part of the fragments is prevented;
after the operation and maintenance capabilities are completed, the operation and maintenance capabilities are compiled into a dynamic link library. And loading the resource into a controller, and creating a self-defined resource to complete the deployment, operation and maintenance of the redis cluster by the controller.
If there are incompatible versions to release, the chart package and plug-in code are modified and a version suffix is added. The method manages programs of multiple versions, and adds corresponding version attributes to the created custom resources.
The invention utilizes the Chart package mechanism and the dynamic link library capability, and can simultaneously manage when a plurality of versions exist simultaneously. Multiple versions of the chart package and multiple versions of the dynamically linked library are provided.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules, or units is only one type of division of logical functions, and there may be other divisions in actual implementation, for example, multiple units, modules, or components may be combined or integrated into another device, or some features may be omitted, or not executed.
The units may or may not be physically separate, and components displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed to a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
In particular, according to embodiments of the present disclosure, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section, and/or installed from a removable medium. The computer program performs the above-described functions defined in the method of the present invention when executed by a Central Processing Unit (CPU). It should be noted that the computer readable medium of the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (5)
1. An operation and maintenance management method for components in a cloud native environment is characterized by comprising the following steps:
acquiring a helmchart packet;
compressing and encoding the helmchart packet into binary data, and storing the binary data into a configmap resource of the cluster;
extracting partial binary data from the configmap resource to create a custom resource;
acquiring a dynamic link library according to the user-defined resources;
decoding binary data in the user-defined resources through a helm template to obtain a yaml resource file;
deploying cloud native components according to the yaml resource file;
and carrying out operation and maintenance management on the cloud native component through the dynamic link library.
2. The method for operation and maintenance management of components in cloud native environment according to claim 1, wherein the step of extracting partial binary data from the configmap resource to create the custom resource further comprises the following steps:
calculating a hash value of binary data in the user-defined resource;
and updating the self-defined resource when the hash value of the binary data in the self-defined resource changes.
3. The operation and maintenance management method for the components in the cloud native environment according to claim 2, wherein calculating a hash value of binary data in the custom resource specifically includes the following steps:
when the configuration of the binary data in the custom resource is modified, a hash value of the binary data in the custom resource is calculated.
4. The method for operation and maintenance management of components in the cloud-native environment according to claim 1, wherein acquiring the helmcart package specifically includes the following steps:
the helmchart package is downloaded from an open source community or written.
5. An operation and maintenance management system for a component in a cloud native environment, which implements the operation and maintenance management method for the component in the cloud native environment according to any one of claims 1 to 4, comprising:
the acquisition module is used for acquiring the helmchart packet;
the compression coding module is used for compressing and coding the helmchart packet into binary data and storing the binary data into a configmap resource of the cluster;
the custom resource management module is used for extracting part of binary data from the configmap resource to create a custom resource;
the version management module is used for acquiring the dynamic link library according to the user-defined resource;
the decoding module is used for decoding binary data in the user-defined resources through the palm template to obtain a yaml resource file;
the deployment module is used for deploying the cloud native components according to the yaml resource file;
and the operation and maintenance management module is used for performing operation and maintenance management on the cloud native component through the dynamic link library.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211581516.0A CN115729610A (en) | 2022-12-07 | 2022-12-07 | Operation and maintenance management method and system for components in cloud native environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211581516.0A CN115729610A (en) | 2022-12-07 | 2022-12-07 | Operation and maintenance management method and system for components in cloud native environment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115729610A true CN115729610A (en) | 2023-03-03 |
Family
ID=85300961
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211581516.0A Pending CN115729610A (en) | 2022-12-07 | 2022-12-07 | Operation and maintenance management method and system for components in cloud native environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115729610A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117827233A (en) * | 2024-03-05 | 2024-04-05 | 成都华栖云科技有限公司 | Simplified installation and deployment method based on rancher platform |
-
2022
- 2022-12-07 CN CN202211581516.0A patent/CN115729610A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117827233A (en) * | 2024-03-05 | 2024-04-05 | 成都华栖云科技有限公司 | Simplified installation and deployment method based on rancher platform |
| CN117827233B (en) * | 2024-03-05 | 2024-04-30 | 成都华栖云科技有限公司 | Rancher platform-based simplified installation and deployment method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8296758B2 (en) | Deployment and versioning of applications | |
| US9858044B2 (en) | Application for builder for industrial automation | |
| US8352905B2 (en) | Application builder for industrial automation | |
| US20100082133A1 (en) | Application builder for industrial automation | |
| EP2177986A1 (en) | Application builder for industrial automation | |
| US20040088397A1 (en) | System and method for management of software applications | |
| WO2021022713A1 (en) | Distributed module update method, device, and storage medium | |
| WO2020015191A1 (en) | Business rule releasing and managing method, electronic device and readable storage medium | |
| CN111897570A (en) | Multi-dependency file extraction method and device based on Maven plug-in | |
| CN113094164A (en) | Task processing device and method, computer equipment and storage medium | |
| CN111897548A (en) | Front-end resource publishing method and device, electronic equipment and computer storage medium | |
| US8359573B2 (en) | Application builder for industrial automation | |
| CN115729610A (en) | Operation and maintenance management method and system for components in cloud native environment | |
| CN115080060A (en) | Application program distribution method, device, equipment, storage medium and program product | |
| KR102432807B1 (en) | Apparatus and method for reconfiguring microservice architecture | |
| CN114528085A (en) | Resource scheduling method, device, computer equipment, storage medium and program product | |
| CN114912897A (en) | Workflow execution method, workflow arrangement method and electronic equipment | |
| CN113741954A (en) | System software generation method and device, electronic equipment and storage medium | |
| US20130297755A1 (en) | Network element configuration management | |
| CN111159142B (en) | Data processing method and device | |
| CN115544518A (en) | Vulnerability scanning engine implementation method and device, vulnerability scanning method and electronic equipment | |
| CN113254040A (en) | Front-end framework updating method, device, equipment and storage medium | |
| CN114064213A (en) | Kubernets container environment-based rapid arranging service method and system | |
| CN116257841B (en) | Function processing method and device based on Kubernetes | |
| CN114021723B (en) | Rule management method and device for medical knowledge base and computer readable storage medium |
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 |