18296288. NEGATIVE NUMBERING TO LOG WEB SERVICE UPDATE ATTEMPTS simplified abstract (Microsoft Technology Licensing, LLC)

From WikiPatents
Revision as of 02:57, 18 October 2024 by Wikipatents (talk | contribs) (Creating a new page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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 18296288 titled 'NEGATIVE NUMBERING TO LOG WEB SERVICE UPDATE ATTEMPTS

Simplified Explanation: The patent application describes a logging system for an orchestration system that deploys updates to a cloud service, allowing for the tracking of deployment activities and version changes.

  • The system includes an orchestrator service host computer, a service bus, and a database for recording deployment logs.
  • Each log entry corresponds to a subset of network components supporting the cloud service and the payload version deployed.
  • In case of deployment issues, the system retains records of previous payload versions by changing the version number to negative before rolling back to an earlier subset of network components.

Key Features and Innovation:

  • Logging system for tracking deployment activities in an orchestration system.
  • Records deployment of updates to a cloud service and changes in payload versions.
  • Ability to retain records of previous payload versions in case of deployment issues.

Potential Applications: The technology can be applied in various industries where cloud services are deployed and updated regularly, such as software development, IT infrastructure management, and network operations.

Problems Solved:

  • Tracking deployment activities and changes in payload versions.
  • Resolving deployment issues by rolling back to previous payload versions.
  • Ensuring transparency and accountability in the deployment process.

Benefits:

  • Improved visibility and control over deployment activities.
  • Faster resolution of deployment issues.
  • Enhanced reliability and stability of cloud services.

Commercial Applications: The technology can be utilized by cloud service providers, IT companies, and software development firms to streamline deployment processes, improve service quality, and minimize downtime for end-users.

Questions about Logging System for Orchestration System: 1. How does the logging system help in tracking deployment activities effectively? 2. What are the key benefits of retaining records of previous payload versions in the deployment process?

Frequently Updated Research: Stay updated on the latest advancements in cloud service deployment technologies and best practices to enhance the efficiency and effectiveness of deployment processes.


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.