Systems and methods for coordinating the deployment of components to defined user groups

    公开(公告)号:US11762652B2

    公开(公告)日:2023-09-19

    申请号:US17880362

    申请日:2022-08-03

    IPC分类号: G06F9/44 G06F8/65 G06F9/451

    CPC分类号: G06F8/65 G06F9/451

    摘要: Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.

    SYSTEMS AND METHODS FOR COORDINATING THE DEPLOYMENT OF COMPONENTS TO DEFINED USER GROUPS

    公开(公告)号:US20220374225A1

    公开(公告)日:2022-11-24

    申请号:US17880362

    申请日:2022-08-03

    IPC分类号: G06F8/65 G06F9/451

    摘要: Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.

    Systems and methods for coordinating the deployment of components to defined user groups

    公开(公告)号:US11042367B2

    公开(公告)日:2021-06-22

    申请号:US16730911

    申请日:2019-12-30

    IPC分类号: G06F9/44 G06F8/65 G06F9/451

    摘要: Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.

    Systems and methods for coordinating the deployment of components to defined user groups

    公开(公告)号:US11442719B2

    公开(公告)日:2022-09-13

    申请号:US17349439

    申请日:2021-06-16

    IPC分类号: G06F9/44 G06F8/65 G06F9/451

    摘要: Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.

    Systems and methods for coordinating the deployment of components to defined user groups

    公开(公告)号:US10521220B1

    公开(公告)日:2019-12-31

    申请号:US16365411

    申请日:2019-03-26

    IPC分类号: G06F9/44 G06F8/65 G06F9/451

    摘要: Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.

    CONSTRAINT-BASED UPGRADE AND DEPLOYMENT
    6.
    发明申请

    公开(公告)号:US20190369980A1

    公开(公告)日:2019-12-05

    申请号:US16269133

    申请日:2019-02-06

    IPC分类号: G06F8/65 H04L29/08

    摘要: One or more software products/services may be installed on a cloud deployment. Product versions of such services can be upgraded (or rolled back) based on a deployment plan comprising tasks adapted to reach a target deployment state. A central upgrade server can forward tasks to an upgrade agent for execution, the tasks being based on a current operational state of the cloud deployment (obtained by the upgrade agent) and one or more constraints. In multiple node deployments, some nodes may be upgraded to a new product version, while other nodes are kept at a current product version until stability of the new product version is determined. Traffic across nodes can be shaped to ensure a deployment is healthy before upgrading other nodes/deployments. If the health of a node/deployment does not meet specified criteria, an upgrade can be stopped, an alert can be triggered, and the node/deployment can be rolled back.

    Systems and methods for managing firewall rules and connections between different services

    公开(公告)号:US12081523B1

    公开(公告)日:2024-09-03

    申请号:US17592890

    申请日:2022-02-04

    IPC分类号: H04L9/40

    CPC分类号: H04L63/0263 H04L63/20

    摘要: A system for managing firewall rules between different services. In certain instances, the method includes receiving a discovery graph comprising a plurality of services and at least one application programming interface (API) dependency, wherein the plurality of services comprises a first service and a second service. In some instances, the method further includes determining whether the second service is permitted to receive an initial communication from the first service based upon the at least one API dependency included in the discovery graph. And, in response to determining the second service is permitted to receive the initial communication from the first service, the method can include establishing a first rule for a firewall between the first service and the second service, the first rule allowing the second service to receive the initial communication from the first service.

    Constraint-based upgrade and deployment

    公开(公告)号:US11586428B1

    公开(公告)日:2023-02-21

    申请号:US16779137

    申请日:2020-01-31

    IPC分类号: G06F8/65 H04L67/10 H04L67/00

    摘要: One or more software products/services may be installed on a cloud deployment. Product versions of such services can be upgraded (or rolled back) based on a deployment plan comprising tasks adapted to reach a target deployment state. A central upgrade server can forward tasks to an upgrade agent for execution, the tasks being based on a current operational state of the cloud deployment (obtained by the upgrade agent) and one or more constraints. In multiple node deployments, some nodes may be upgraded to a new product version, while other nodes are kept at a current product version until stability of the new product version is determined. Traffic across nodes can be shaped to ensure a deployment is healthy before upgrading other nodes/deployments. If the health of a node/deployment does not meet specified criteria, an upgrade can be stopped, an alert can be triggered, and the node/deployment can be rolled back.

    SYSTEMS AND METHODS FOR COORDINATING THE DEPLOYMENT OF COMPONENTS TO DEFINED USER GROUPS

    公开(公告)号:US20210311722A1

    公开(公告)日:2021-10-07

    申请号:US17349439

    申请日:2021-06-16

    IPC分类号: G06F8/65 G06F9/451

    摘要: Systems and methods are provided for coordinating the deployment of frontend assets to defined user groups. Individual groups of users may be assigned to a track comprising a set of frontend assets. Each set of frontend assets may comprise each of the individual components required to generate an entire frontend for an application. In some embodiments, different versions of a single component may be assigned within different tracks. As such, one set of users may be provided a first version of an application and a second set of users may be provided a second version of that application. By associating a new or updated version of a component to a given track, a new or updated version of a component not yet ready for widespread deployment may be provided to only a limited number of users.

    Constraint-based upgrade and deployment

    公开(公告)号:US10558454B2

    公开(公告)日:2020-02-11

    申请号:US16269133

    申请日:2019-02-06

    IPC分类号: G06F8/65 H04L29/08

    摘要: One or more software products/services may be installed on a cloud deployment. Product versions of such services can be upgraded (or rolled back) based on a deployment plan comprising tasks adapted to reach a target deployment state. A central upgrade server can forward tasks to an upgrade agent for execution, the tasks being based on a current operational state of the cloud deployment (obtained by the upgrade agent) and one or more constraints. In multiple node deployments, some nodes may be upgraded to a new product version, while other nodes are kept at a current product version until stability of the new product version is determined. Traffic across nodes can be shaped to ensure a deployment is healthy before upgrading other nodes/deployments. If the health of a node/deployment does not meet specified criteria, an upgrade can be stopped, an alert can be triggered, and the node/deployment can be rolled back.