Abstract: Disclosed is an improved approach to process data and events from disparate ecosystems pertaining to products. An approach is provided to automatically cluster events from various ecosystems into noteworthy incidents and to correlate them with entities extracted from each system. Incidents are correlated between ecosystems to classify the type of incidents and to give a coherent converged picture of the event streams coming from the various ecosystems. Noteworthy incidents are automatically converted into tickets and their severity is ascertained from the associated incidents. Tickets that reference underlying defects with the product or service are converted into issues.

Abstract: Disclosed is an improved approach to process data and events from disparate ecosystems pertaining to products. An approach is provided to automatically cluster events from various ecosystems into noteworthy incidents and to correlate them with entities extracted from each system. Incidents are correlated between ecosystems to classify the type of incidents and to give a coherent converged picture of the event streams coming from the various ecosystems. Noteworthy incidents are automatically converted into tickets and their severity is ascertained from the associated incidents. Tickets that reference underlying defects with the product or service are converted into issues.

Abstract: The present subject matter discloses techniques to automatically cluster events generated by a plurality of distinct ecosystems deployed in a connected environment in relation to a product. In operation, the clustered events may be correlated, and one or more of the correlated events that trigger a response may be identified as an actionable item. Based on a correlation between the actionable items, a hierarchical product parameter responsible for the actionable item may be identified. The hierarchical product parameter is an operational factor in a hierarchy of operational factors associated with the product, where the hierarchy of operational factors span over the plurality of distinct ecosystems operating in relation to the product. Subsequently, one or more entities across the distinct ecosystems may be notified of the actionable item, to initiate a required action. Further, techniques to detect operational factors associated with the product deployed in the distinct ecosystems are disclosed.

Abstract: Disclosed is an approach for dynamically applying roles and access levels to an actor based at least in part upon a set of conditions an object should meet for the role to be assumed. The approach may dynamically determine privileges based at least in part upon API endpoints and operations. A multi-factor approach may be taken for determining authorization based at least in part upon conditions, attributes, and policy.

Abstract: Disclosed herein are related to a method, a system, and a non-transitory computer readable medium for providing a consolidated cloud system. The consolidated cloud system includes a plurality of cloud systems. A user request to access content in the consolidated cloud system is received, where the content is stored by a target cloud system of the plurality of cloud systems. The content from the target cloud system is retrieved, and the content is provided as part of the consolidated cloud system. The device generating the user request may be unaware of which cloud system stores the content.

Abstract: A system and method includes an orchestration engine to determine workloads associated with operations on cloud platforms. The orchestration engine can receive a request to a universal application programming interface (API) or a request to an API associated with a cloud platform. The orchestration engine can determine the workload associated with the operation, and select one or more cloud platforms to distribute the workload based at least on a policy. The system and method also includes a lifecycle management engine that can receive requests to implement lifecycle rules on an object stored at a cloud platform. The lifecycle management engine can translate received requests to one API into requests to an API associated with a target cloud platform. The lifecycle management engine can receive status of the object from the target cloud platform, and provide the status to the requesting client.

Abstract: Disclosed herein are related to a method, a system, and a non-transitory computer readable medium for providing a consolidated cloud system. The consolidated cloud system includes a plurality of cloud systems. A user request to access content in the consolidated cloud system is received, where the content is stored by a target cloud system of the plurality of cloud systems. The content from the target cloud system is retrieved, and the content is provided as part of the consolidated cloud system. The device generating the user request may be unaware of which cloud system stores the content.

Abstract: A method and system for implementing Multiple Endpoint Paths (MEP) for Point to Multipoint (P2MP) calls over Soft Permanent Virtual Connections (SPVC) are provided. When a condition is detected that requires a particular endpoint to be switched to an alternate endpoint, all calls of the P2MP group that used the particular endpoint are torn down in sequence, in accordance with SPVC procedures. Once all of the calls are torn down, any calls that are enabled for MEP are re-established using the alternate endpoint to replace the particular endpoint.