Microsoft technology licensing, llc (20240338196). NEGATIVE NUMBERING TO LOG WEB SERVICE UPDATE ATTEMPTS simplified abstract

From WikiPatents
Jump to navigation Jump to search

NEGATIVE NUMBERING TO LOG WEB SERVICE UPDATE ATTEMPTS

Organization Name

microsoft technology licensing, llc

Inventor(s)

Dmitry Valentinovich Kholodkov of Sammamish WA (US)

Rahul Nigam of Bothell WA (US)

Nidhi Verma of Bellevue WA (US)

NEGATIVE NUMBERING TO LOG WEB SERVICE UPDATE ATTEMPTS - A simplified explanation of the abstract

This abstract first appeared for US patent application 20240338196 titled 'NEGATIVE NUMBERING TO LOG WEB SERVICE UPDATE ATTEMPTS

The abstract describes a logging system for an orchestration system that deploys updates to a cloud service, including an orchestrator service host, a service bus, and a database for recording deployment logs.

  • The system records a log of each update deployment, with entries for subsets of network components supporting the cloud service.
  • Each log record refers to a specific payload version deployed to a corresponding subset of network components.
  • If an issue is detected with a deployment, the system retains records by changing the payload version number to negative before restarting the deployment with a new payload version.
  • This process helps avoid issues by reverting back to an earlier subset of network components with a new payload version.

Potential Applications: - Software deployment management - Cloud service updates - Network component monitoring

Problems Solved: - Efficiently managing and tracking updates in a cloud service environment - Addressing issues with deployment without losing deployment history

Benefits: - Improved update deployment process - Enhanced monitoring and tracking capabilities - Increased reliability and stability of cloud service updates

Commercial Applications: Title: "Efficient Cloud Service Update Deployment System" This technology can be used by cloud service providers, IT companies, and software development firms to streamline update deployment processes, improve system reliability, and enhance overall service quality.

Prior Art: Researchers can explore existing logging systems, orchestration tools, and cloud service deployment technologies to understand the evolution of similar concepts in the field.

Frequently Updated Research: Stay informed about advancements in cloud service deployment technologies, network monitoring tools, and update management systems to enhance the efficiency and effectiveness of the logging system described in the patent application.

Questions about the Logging System for Cloud Service Updates: 1. How does the system handle issues with deployment in specific subsets of network components? The system retains records by changing the payload version number to negative before restarting the deployment with a new payload version to avoid the issue.

2. What are the key components of the logging system for update deployments in a cloud service environment? The system includes an orchestrator service host, a service bus, and a database for recording deployment logs.


Original Abstract Submitted

a logging system for an orchestration system that implements a rollout service to deploy updates to a cloud service includes: an orchestrator service host computer hosting the rollout service; a service bus connecting the orchestrator service host computer with a network on which the cloud service is provided; and a database to which the rollout service records a log of a deployment of an update, the log comprising an entry for each of a number of subsets of network components supporting the cloud service. each record in the log refers to a payload version deployed to a corresponding subset of the network components supporting the cloud service. in response to detection of an issue with the deployment of the update in a particular subset of the network components, the rollout service retains a record in the log of each payload version deployed by changing a payload version number to be negative in each record of the log prior to a restart of the deployment back to an earlier subset of the network components with a new payload version to avoid the issue.