Model-based artifact management

Patent metadata

Field	Value
Publication number	US-2017163518-A1
Application number	US-201514958988-A
Country	US
Kind code	A1
Filing date	Dec 4, 2015
Priority date	Dec 4, 2015
Publication date	Jun 8, 2017
Grant date	—

Abstract

The current document is directed to cloud-based cloud-management systems and subsystem components of the management systems that store, retrieve, use, and manipulate artifacts. In the described implementations, artifacts are represented by artifact descriptors, referred to as “artifact specs,” which are instantiated, at run time, as corresponding artifact models. The artifact models include full descriptions of the artifacts as well as references to locally stored instances of the artifacts that can be used to access the artifacts. In the case of automated-application-release-management subsystems, artifacts include executables, program code, files containing input and/or output data, and other stored data used in provisioning virtual machines, deploying application executables, testing application executables, and carrying out other subtasks of application development, testing, and release.

First claim

1 . A workflow-based cloud-management system incorporated within a cloud-computing facility having multiple servers, data-storage devices, and one or more internal networks, the workflow-based cloud-management system comprising:
an infrastructure-management-and-administration subsystem; a workflow-execution engine; an automated-application-deployment subsystem; and an automated-application-release-management subsystem that executes application-release-management pipelines that each comprises one or more stages, each having one of more tasks and that interfaces to one or more artifact repositories through a model-based artifact-management-subsystem interface to access artifacts on behalf of the executing executes application-release-management pipelines.

2 . The workflow-based cloud-management system of claim 1 wherein the automated-application-release-management subsystem comprises:
a dashboard user interface;
a management controller;
an interface to the workflow-execution engine; and
an artifact-management subsystem.

3 . The workflow-based cloud-management system of claim 2 wherein the automated-application-release-management subsystem and the infrastructure-management-and-administration subsystem include control logic at least partially implemented as workflows that are executed by the workflow-execution-engine subsystem.

4 . The workflow-based cloud-management system of claim 2 wherein an application-release-management pipeline stage or task within an application-release-management pipeline that accesses one or more artifacts managed by the artifact-management subsystem uses one or more search specs, stored in memory, as one or more handles for the one or more artifacts.

5 . The workflow-based cloud-management system of claim 4 wherein each search spec includes:
a name of the artifact or artifacts represented by the search spec;
an indication of one or more artifact repositories in which to search;
an indication of a search type; and
parameter values submitted in a call to an entrypoint corresponding to the search type.

6 . The workflow-based cloud-management system of claim 4 wherein the management controller resolves a search spec into a an artifact model by:
for each artifact repository indicated by artifact-repository indications in the search spec,
compiling a search request from the search-type indication and parameter values,
submitting the search request to the artifact repository, and
retrieving artifacts or references to artifacts returned in response to the search request;

generating an artifact model for each artifact retrieved from one or more of the artifact repositories; and
storing the artifact model in memory.

7 . The workflow-based cloud-management system of claim 6 wherein each artifact model includes:
a name for the artifact;
a reference to the artifact;
information that describes the repository from which the artifact was retrieved;
a size of the artifact;
a reference to a description of, or to a callable reference to, the search request used to retrieve the artifact; and
properties or attributes of the artifact.

8 . The workflow-based cloud-management system of claim 6 wherein each artifact model further includes:
check sums that can be used to verify the artifact.

9 . The workflow-based cloud-management system of claim 6 wherein the management controller downloads resolved artifacts to a computer system on which they are locally accessed by executing tasks of an application-release-management pipeline and wherein the reference to the artifact in the corresponding artifact model refers to the locally stored artifact.

10 . The workflow-based cloud-management system of claim 6 wherein an executing application-release-management pipeline downloads resolved artifacts to a computer system on which they are locally accessed by executing task and wherein the reference to the artifact in the corresponding artifact model refers to a remotely stored artifact.

11 . The workflow-based cloud-management system of claim 6 wherein the management controller maintains, in memory:
a storage-type table that lists each type of search, the parameter values supplied to invoke the search, and a list of artifact repositories that support the search type; and
a repository spec that provides connection information for each accessible artifact repository.

12 . A method that provides for execution of application-release-management pipelines, by an automated-application-release-management-subsystem component of a workflow-based cloud-management system that is incorporated within a cloud-computing facility having multiple servers, data-storage devices, and one or more internal networks and that that accesses artifacts through a model-based artifact-management-subsystem interface, the method comprising:
configuring an application-release-management pipeline to include one or more stages, each having one of more tasks, that include one or more search-spec handles for one or more artifacts; and launching, by a management controller, execution of the application-release-management pipeline, during which the management controller resolves the search specs into one or more artifact models.

13 . The method of claim 12 wherein the workflow-based cloud-management system comprises:
an infrastructure-management-and-administration subsystem;
a workflow-execution engine;
an automated-application-deployment subsystem; and
the automated-application-release-management subsystem that executes application-release-management pipelines.

14 . The method of claim 13 wherein the automated-application-release-management subsystem comprises:
a dashboard user interface;
the management controller;
an interface to the workflow-execution engine; and
an artifact-management subsystem.

15 . The method of claim 14 wherein each application-release-management pipeline task that accesses one or more artifacts managed by the artifact-management subsystem uses one or more search specs, stored in memory, as one or more handles to describe the one or more artifacts.

16 . The method of claim 15 wherein each search spec includes:
a name of the artifact or artifacts represented by the search spec;
an indication of one or more artifact repositories in which to search;
an indication of a search type; and
parameter values submitted in a call to an entrypoint corresponding to the search type.

17 . The method of claim 15 wherein the management controller resolves a search spec into a an artifact model by:
for each artifact repository indicated by artifact-repository indications in the search spec,
compiling a search request from the search-type indication and parameter values,
submitting the search request to the artifact repository, and
retrieving artifacts or references to artifacts returned in response to the search request; and

generating an artifact model for each artifact retrieved from one or more of the artifact repositories; and
storing the artifact model in memory.

18 . The method of claim 17 wherein each artifact model includes:
a name for the artifact;
a reference to the artifact;
information that describes the repository from which the artifact was retrieved;
a size of the artifact;
a reference to a description of, or to a callable reference to, the search request used to retrieve the artifact; and
properties or attributes of the artifact.

19 . The method of claim 6 wherein each artifact model further includes:
check sums that can be used to verif

Assignees

• Vmware Inc

Inventors

• Dube Arjun
• Sinha Rakesh
• Nagaraja Vishwas

Classifications

• H04L43/50 Primary

  Testing arrangements · CPC title

• G06F8/61

  Installation · CPC title

• H04L41/5054 Primary

  Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components · CPC title

• H04L41/5096

  wherein the managed service relates to distributed or central networked applications · CPC title