In reality, this mapping has not been taken up. Instead, the 802.1p priority service assignment is negotiated locally between configurations and interpreters. An SLA is a written agreement that qualitatively and quantitatively specifies the service that a provider offers to a customer. It identifies the metrics used to measure service level and corrective actions or penalties resulting from non-compliance with promised service level expectations. An SLA is required to support the performance of operations that depend on the provider`s underlying services. Different levels of service can be offered at different price classes, and customers often make an optimal compromise between service level and costs. By defining SLA`s contractual obligations, suppliers manage expectations for all of their customers. Measured indicators and performance indicators allow both the supplier and the customer to identify, track, report and evaluate the actual indicators that define the actual business requirements and performance. Below the orchestration layer are dedicated controller software modules for servers, memory, and networks. These controllers translate orchestration layer commands into open APIs according to industry standards such as OpenStack for server virtualization and OpenFlow for networks. Controllers using open north and south walking APIs allow easy integration with orchestration layers and also allow the use of high-volume standard hardware by a large number of vendors that support the open API. In this example, the hypervisors and virtual switches on the servers must include the open VM controller commands, and the operating system for the top rack switch must include the open network controller commands. For memory, an open memory controller can be used to send commands to configure and monitor storage resources.
By communicating with the same orchestration layer, these controllers can ensure coordination between resources. In addition, these controllers help make available hardware resources and features available to the orchestration layer. In the following sections, we will provide more details about the OpenStack and OpenFlow standards. Working days with service providers (suppliers) at will, based on their performance and quality, have become contractual services and “preferred suppliers”, often based more on cost factors than on any other measure. A large part of them were due to certain incongruities that occurred in the sector, that bought stores or rely exclusively on relationships that did not necessarily lead to the best supplier to achieve the general organizational goals or those of their customers. The adoption of the request for proposal process by the majority of companies, regardless of their size, has unintentionally reinforced the need for this long-term contractual services mentality. . . .