Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive a traffic descriptor that includes a character string corresponding to an application of the UE. In some cases, the character string may be encoded to represent a sequence of characters in the character string to index or match applications to different network slices for communications for the UE. For example, the character string may be encoded using American Standard Code for Information Interchange (ASCII) encoding. After receiving and decoding the encoded traffic descriptor, the UE may identify a matching network slice for the application corresponding to the character string of the traffic descriptor. Subsequently, the UE may attempt to establish a connection with the matching network slice for communications for the application and may communicate with the matching network slice for the application based on a successful establishment of the connection.

This disclosure describes techniques that include adding information to a network service header in packets being processed by a set of compute nodes in a service chain. The information added to the network service header can be used during selection of the next hop in a service chain, and may be used to help ensure that service level agreements (SLA) are met with respect to one or more metrics. In one example, this disclosure describes a method that includes receiving, by a service complex having a plurality of service nodes, a packet associated with a service chain representing a series of services to be performed on the packet by one or more of the plurality of service nodes; identifying, by the service complex, one or more service chain constraints associated with the service chain; and modifying the packet, by the service complex, to include information about the service chain constraints.

A service provider may apply customer-selected or customer-defined auto-scaling policies to a cluster of resources (e.g., virtualized computing resource instances or storage resource instances in a MapReduce cluster). Different policies may be applied to different subsets of cluster resources (e.g., different instance groups containing nodes of different types or having different roles). Each policy may define an expression to be evaluated during execution of a distributed application, a scaling action to take if the expression evaluates true, and an amount by which capacity should be increased or decreased. The expression may be dependent on metrics emitted by the application, cluster, or resource instances by default, metrics defined by the client and emitted by the application, or metrics created through aggregation. Metric collection, aggregation and rules evaluation may be performed by a separate service or by cluster components. An API may support auto-scaling policy definition.

Systems and methods for ticket-based provisioning of cloud infrastructure from one or more cloud providers to build one or more computing workspaces of an enterprise. A provisioning platform provides a module catalog having one or more infrastructure-as-code (IAC) modules, each including code that is executable to provision cloud computing resources for the cloud infrastructure from the cloud providers to build the computing workspaces of the enterprise. A service catalog has one or more electronic entries mapped to and corresponding with the IAC modules of the module catalog. The service catalog receives one or more tickets that each specify at least one of the electronic entries in the service catalog, to bind each specified electronic entry with a corresponding IAC module, causing the provisioning platform to instantiate on the more cloud providers the computing resources for the cloud infrastructure corresponding to the ticket.

A network slice managing entity, comprising means configured to obtain a service request for a network slice, the service request defining service requirements; request network slice descriptions from a database and selecting at least one network slice which support said service requirements according to the descriptions; generate a resource graph comprising nodes representing infrastructure resources and links representing connections between the nodes, the resource graph depicting resources needed for providing the service, wherein the generating is carried out based on a network slice description of the selected at least one network slice; transmit the resource graph to an infrastructure manager for mapping a topology of said network infrastructure onto said resource graph and determining at least one subset of said network infrastructure; and, receive a mapping result from said infrastructure manager containing said at least one subset of said network infrastructure.

Processing devices receive a file having entries having data items separated by delimiters. Each data item has an ordinal position. The processing device(s) cause display of a table, having rows and columns, in a graphical user interface. Each data items of a particular entry appears in a respective column of the same row. Each column corresponds to the ordinal position of its respective data item. User input is received designating, for each respective column, a field name and an entity definition component type to which the respective column pertains, and stores for each of the data items of the particular entry a value of an element of an entity definition. The element has the element name designated for the respective column in which the data item appeared, and is associated with an entity definition component having the type designated for the respective column in which the data item appeared.

Systems and methods are described for network service pricing and service resource management, implemented by a server communicatively coupled to a Software Defined Networking (SDN) network configured to provide the network service. The systems and methods includes receiving a service request for a network service in the SDN network; determining one or more price categories and one or more network resources for the service request, wherein the network resources are selected to instantiate the network service; adjusting a price of the network resources by adjusting the price within a range of the price categories based on current and known future network information of the SDN network; and responsive to acceptance of the price, instantiating the network service through the network resources in the SDN network.

A method implemented in a data center management node including obtaining, from memory, a physical stack describing a configuration of platform components across multiple operating platforms on a data center infrastructure, generating, by a processor, a graph describing correlations between the operating platforms and the data center infrastructure based on a platform library, wherein the platform library describes configurations of the platform components for each of the operating platforms separately, generating, by the processor, one or more logical stacks based on the graph, wherein the one or more logical stacks indicate deployable configurations of the operating platforms without depicting the platform components, and representing the logic stack to a user.

Methods, apparatus, systems and articles of manufacture are disclosed to improve cluster efficiency. An example apparatus includes a cluster manager to identify cluster resource details to execute a workload, a workload manager to parse the workload to identify services to be executed by cluster resources, and an optimization formula manager to identify service optimization formulas associated with respective ones of the identified services, and improve cluster resource efficiency by generating a cluster formula configuration to calculate cluster parameter values for the cluster resources.

A network management architecture referred to as the Control/Orchestration/Management/Policy/Analytics (COMPA) architecture (or COMPA for short). The COMPA architecture functions to simplify and automate the operations (both management and business process) of a network. In one aspect, the COMPA architecture addresses four use case categories: (1) Resource/Service Onboarding; (2) Automated Product Offerings; (3) Automated Management; and (4) Service Exposure. COMPA enables rapid service introduction into the network and lifecycle management; dynamic network governance via policy; and controlled access to functionality provided by different responsibility domains.