Vmware, Inc.

Michael Toback

Hui Henry Li

David Ian Ferguson

Wenfeng Liu

Wit Riewrangboonya

David Byard

Nick Tenczar

Maria Del Carmen Hernandez-Villavicencio

Monty Ijzerman

In a computer-implemented method for validating interoperability of installed components of a computer system, site data identifying the installed components of the computer system and a version of each of the installed components is received, component dependency data identifying at least one component of the installed components requiring installation of another component of the installed components is received and component interoperability data identifying versions of a component of the installed components that are interoperable with versions of another component of the installed components is received. A version dependency compatibility acyclic graph is generated based at least on the installed components, the component dependency data and component interoperability data. It is determined whether the installed components are interoperable based on the version dependency compatibility acyclic graph.

Validating interoperability of installed components of a computer system

In a computer-implemented method for performing an upgrade analysis of a computer system, a version dependency compatibility acyclic graph defining component dependency and component version interoperability for a plurality of installed components of the computer system is accessed. Upgradable components of the installed components are determined based on the version dependency compatibility acyclic graph. An upgrade analysis request for an upgradable component of the plurality of installed components is received. Installed components of the plurality of installed components that are impacted by an upgrade of the upgradable component are determined based on the version dependency compatibility acyclic graph.

Upgrade analysis of a computer system

A method for managing a software package, including: accessing a request to process one or more package definitions in relation to a data repository which retains package definitions, wherein the one or more package definitions is associated with the software package; determining a status of an assertion that indicates either a completed assertion or an incomplete assertion; if the status is determined to be the incomplete assertion, then determining requirements for the software package to be configured for the hyper-converged appliance; attempting to find a match for the assertion in a pool of known resolvable assertions, wherein the match will allow the assertion to be resolved through accessible provisions and thereby fulfill the requirements; if the match is found, then using the accessible provisions to resolve and thereby complete the assertion; and if the assertion is completed, continuing an installation process of the software package.

System for managing software package configuration

Exemplary methods, apparatuses, and systems receive data describing a first software component used by a software product and vulnerability data describing a vulnerability in the first software component. A vulnerability score is calculated for the software product based upon the vulnerability data for the first software component. The vulnerability score is recalculated for the software product based upon receiving an updated status of the vulnerability in the first software component from bug tracking software, a waiver of the vulnerability of a software component, the addition of another software component, or another update to the software product or component(s). The task of remediation of the vulnerability in the first software component can be assigned to a user and tracked. A user interface is provided to enable users to monitor the vulnerabilities of software products or components.

Growing community of inventors

Saratoga, CA, United States of America

Michael Toback