Method and system for providing customized rollout of features
US-11829743-B2 · Nov 28, 2023 · US
US12236233B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12236233-B2 |
| Application number | US-202318360840-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 28, 2023 |
| Priority date | Jul 29, 2022 |
| Publication date | Feb 25, 2025 |
| Grant date | Feb 25, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure discloses a method and system for automatically and quickly deploying a front-end processor based on gray release. The system includes a user management module, a front-end processor engineering configuration module, a version iteration module and an engineering code version management repository, where the version iteration module is connected with the engineering code version management repository, the user management module and the front-end processor engineering configuration module, a code is obtained through the engineering code version management repository to perform updating or rollback of a current code, an operating permission of the front-end processor is obtained by using the user management module, an engineering configuration parameter is obtained from the front-end processor engineering configuration module for engineering gray release of a plurality of front-end processors, and a task scheduling function therein is called.
Opening claim text (preview).
What is claimed is: 1. A method for automatically and quickly deploying a front-end processor based on gray release, comprising steps of: step S 1 : performing version management on to-be-deployed engineering by using an engineering code version management repository, the engineering code version management repository being deployed on a remote server; step S 2 : logging in a user management module for identity identification, and verification of an operating permission for a plurality of front-end processors and an operating permission for engineering configurations of the plurality of front-end processors; step S 3 : performing parameter extraction on the front-end processors, arranging all the front-end processors in a sequence according to the extracted parameters, and performing gray release deployment on the top front-end processors in the sequence; step S 4 : when the gray release deployment is to be performed on 10% of the front-end processors, sequentially deploying the top 10% of the front-end processors in a total front-end processor queue and performing a gray scale test after deployment is completed, and when a number of front-end processors meeting smoothness of new and old function ports and overall running stability of a system accounts for greater than or equal to 90% of a number of deployed front-end processors, continuing gray release; and otherwise, performing version rollback on the deployed front-end processors until the engineering on all front-end processors returns to a previous version, and finishing the gray release; step S 5 : when the gray release deployment is to be performed on 10% to 40% of the front-end processors, reordering a last 90% of the front-end processors in the total front-end processor queue according to step S 3 , sequentially deploying a first one-third of the front-end processors in the reordered front-end processor queue, performing a gray scale test after deployment is completed, and when the number of the front-end processors meeting smoothness of new and old function ports and overall running stability of the system accounts for greater than or equal to 90% of the number of deployed front-end processors, continuing the gray release; and otherwise, performing version rollback on the deployed front-end processors until the engineering on all front-end processors returns to a previous version, and finishing the gray release; and step S 6 : when the gray release deployment is to be performed on a last-two-thirds of the front-end processors in the reordered front-end processor queue, reordering the last two-thirds of the front-end processors in the reordered front-end processor queue according to step S 3 , sequentially deploying all front-end processors in a front-end processor queue that has been reordered again, performing a gray scale test after deployment is completed, and when the number of the front-end processors meeting smoothness of new and old function ports and overall running stability of the system accounts for greater than or equal to 90% of the number of deployed front-end processors, performing troubleshooting manually on unsuccessfully deployed front-end processors for manually updating deployment; and otherwise, performing version rollback on the deployed front-end processors until the engineering on all front-end processors returns to a previous version. 2. The method for automatically and quickly deploying the front-end processor based on the gray release according to claim 1 , wherein step S 3 comprises sub-steps of: step S 31 : performing parameter extraction on each front-end processor; step S 32 : performing classification by using a decision-making tree according to a current CPU load situation of the front-end processor to sequentially obtain a plurality of initial sequences; step S 33 : performing in-sequence ordering in each initial sequence in combination with a remaining amount of an internal memory of the front-end processor, a size of an update package and expected transmission time to obtain a sequence; and step S 34 : determining a sequence number of each front-end processor in each sequence, arranging all front-end processors in the sequence and according to positions within the sequence, and performing gray release deployment in order of sequence numbers from front to back. 3. The method for automatically and quickly deploying the front-end processor based on gray release according to claim 2 , wherein step S 31 comprises sub-steps of: step S 311 : extracting a remaining amount of an internal memory of a current front-end processor; step S 312 : extracting a network bandwidth; step S 313 : extracting the size of the update package; and step S 314 : calculating the expected transmission time of the update package according to the network bandwidth and the size of the update package. 4. The method for automatically and quickly deploying the front-end processor based on gray release according to claim 2 , wherein step S 32 is performing sequence dividing on to-be-deployed front-end processors according to a CPU load average and a number of CPU cores, and four dividing conditions are as follows: dividing the front-end processors where a load average of one minute is smaller than the number of the CPU cores into a first sequence; dividing the front-end processors where a load average of one minute is greater than or equal to the number of the CPU cores and the front-end processors where a load average of five minutes is smaller than the number of the CPU cores into a second sequence; dividing the front-end processors where a load average of one minute is greater than or equal to the number of the CPU cores, the front-end processors where a load average of five minutes is greater or equal to the number of the CPU cores and the front-end processors where a load average of fifteen minutes is smaller than the number of the CPU cores into a third sequence; and dividing the rest of the front-end processors into a fourth sequence. 5. The method for automatically and quickly deploying the front-end processor based on gray release according to claim 2 , wherein step S 33 comprises sub-steps of: step S 331 : composing the remaining amount of the internal memory of the front-end processor, the size of the update package and the expected transmission time into a matrix; step S 332 : performing zero-mean normalization on each row of the matrix; step S 333 : obtaining a covariance matrix; step S 334 : obtaining an eigenvalue and a corresponding eigenvector of the covariance matrix; step S 335 : arranging eigenvectors by row, from top to bottom, according to sizes of corresponding eigenvalues to form a new matrix; step S 336 : taking data which is one-dimension through dimensionality reduction to obtain a feature component, and calculating expected total deployment time of each front-end processor; and step S 337 : arranging the front-end processors in a positive sequence according to the expected total deployment time, wherein the shorter the total deployment time, the more front the sequence numbers of the front-end processors. 6. The method for automatically and quickly deploying the front-end processor based on gray release according to claim 1 , wherein the method further comprises steps of: step 1 : sending, by a user, an automatic deployment request of front-end processor engineering to a central computer by using a version iteration module, downloading, by the central computer, a version code corresponding to the to-be-deployed engineering from the engineering code version management repository, generating an engineering update package in combination with an engineering version of a current front-end processor, and compressing the engineering update package by using a ssh agent; step 2 : transmittin
Updates (security arrangements therefor G06F21/57) · CPC title
Test management · CPC title
for test version control, e.g. updating test cases to a new software version · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
Software deployment · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.