Abstract:
A hybrid cloud management system in a cloud environment having a more than one cloud platforms is described. The system includes a management interface, a cloud broker including cloud connectors, and a resource broker. The management interface facilitates user-selection of services including service models and deployment models for an internal cloud and an external cloud. The cloud broker is coupled to the management interface to provision and automate lifecycle use of selected services. The cloud connector enables interaction of the management interface with the external cloud through the cloud broker. The resource broker operably coupled to the cloud broker to manage a resource inventory of the internal cloud.
Abstract:
In example implementations, a non-vendor specific input is received for an enterprise resource planning (ERP) system. At least one vendor specific ERP system for applying the non-vendor specific input is identified. The non-vendor specific input is translated to a vendor specific input of the at least one vendor specific ERP system. The vendor specific input is used to cause at least one device in the at least one vendor specific ERP system to be modified.
Abstract:
Examples include cloud access rule translation for a hybrid cloud computing environment. Some examples include translation of a cloud access rule in a cloud-specific format to a canonical format and a determination of whether to allow an application programming interface (API) request for a cloud computing service based on the translated cloud access rule.
Abstract translation:示例包括用于混合云计算环境的云访问规则转换。 一些示例包括将云特定格式的云访问规则翻译成规范格式,以及基于翻译后的云访问规则确定是否允许针对云计算服务的应用程序编程接口(API)请求。 p >
Abstract:
Service scaling for batch processing. Examples include receipt of transaction requests for business services hosted on a network, as each transaction request is received, parsing of metadata of the transaction request to determine whether the transaction request is a batch request, and when the transaction request is a batch request, generation, based on the metadata, of a batch profile of the batch request comprising processing parameters of the batch request, including business services targeted by the batch request, monitoring of ongoing capacities of the network, including each of the business services; and scaling of targeted business services based at least on the monitored capacities, the batch profile, and processing policies.
Abstract:
Example implementations relate to a provider offer. For example, computing device may include a processor. The processor may receive a request for a particular product or service, wherein the request is associated with an account of a user. The processor may identify providers of the particular product or service located within a particular distance from a location of the user, wherein the providers are identified according to preferences specified by the user in the account. The processor may send the request to the providers and notify the user of at least one offer from at least one of the providers, wherein the at least one offer specifies a price offered by the at least one of the providers. The processor may receive, from the user, an acceptance of one of the at least one offer.
Abstract:
A system includes a marketplace portal to allow a user to order a business service, and a cloud controller to deploy an instance of the ordered business service to a cloud environment. The system includes an application programming interface (API) scanner to discover API information including at least one API exposed by the deployed instance of the ordered business service, and publish the discovered API information to another service.
Abstract:
A network system having a pool of network resources including aggregation routers in communication with a wide area network, aggregation switches in communication with the aggregation routers, and groups of servers, each group having a corresponding switch. The network system includes a cloud provisioning system to receive a cloud provisioning request from and end user, the cloud provisioning system including an orchestrator to form, from the pool of network resources, a plurality of overlay networks which together form the cloud, to form each overlay network, the orchestrator, for one or more groups of servers, to logically assign, in a one-to-one fashion, ports of servers to ports of the corresponding switch, and to logically assign the corresponding switch of the one or more groups of servers to ports of a same aggregation switch, and an internet protocol address management (IPAM) module to assign an IP address to each overlay network at the aggregation routers.
Abstract:
Orchestration template generation for a computer network such as cloud environment is described. A platform-independent intermediary model is generated from an enterprise architecture model. The intermediary model is applied to a selected platform-specific deployment configuration template associated with a selected deployment format.
Abstract:
Examples disclosed herein relate to control of a drone. In one example, aerial movement of the drone is controlled. In the example, it is determined, based on a plurality of devices, whether the drone is within a line- of-sight with at least a respective one of a plurality of humans within a physical proximity to a respective one of a the devices.. In the example, the devices are used by the drone to track the humans. In the example, when the drone is determined to lack the !ine-of-sight, aerial movement of the drone is controlled to move the drone to become within the line-of-sight.
Abstract:
A system includes a policy manger that includes a policy to describe policy attributes of an application that define whether the application can be deployed as a container server or as a non-container server. An application analyzer analyzes a given application with respect to the policy attributes to classify the given application as a container model or a non-container model. A deployment controller generates a corresponding container server for the given application if the given application is classified as a container model or generates a corresponding non-container server for the given application if the given application is classified as a non-container model.