N-tier workload and data placement and orchestration
One example method includes creating a manifest that specifies one or more requirements concerning execution of an application that resides at an end device in an N-tier configuration, identifying a workload that is associated with the application and executable at one or more edge stations of the N-tier configuration, gathering and evaluating network telemetry, orchestrating the workload based on the network telemetry and the manifest, scheduling performance of the workload at the one or more edge stations, and performing the workload at the one or more edge stations in accordance with the scheduling.
1. A method, comprising:
creating a manifest that specifies one or more requirements concerning a workload that is defined as execution of a group of containers associated with an application;
based on the requirements in the manifest, defining a tier topology of an N-tier configuration that includes multiple tiers;
gathering network telemetry and evaluating the network telemetry to determine if a system performance parameter, as indicated by the telemetry, meets one of the requirements specified in the manifest and, when the system performance parameter does not meet the requirement, modifying the number of tiers in the N-tier configuration;
orchestrating the workload across multiple tiers of the N-tier configuration, wherein the orchestrating is based on the network telemetry and the manifest and the orchestrating includes positioning each of the containers at one of the tiers of the N-tier configuration;
scheduling performance of the workload; and
performing the workload at one or more edge stations in accordance with the scheduling, wherein one of the edge stations is located on one tier of the N-tier configuration, and another of the edge stations is located on another tier of the N-tier configuration.
2. The method as recited in claim 1 , wherein the manifest specifies a startup strategy concerning the group of containers, weights for network performance expectations, and hardware requirements associated with performance of the workload.
3. The method as recited in claim 1 , wherein orchestrating the workload comprises defining an optimal placement of containers and data across N-tiers of the N-tier configuration.
4. The method as recited in claim 3 , wherein the optimal placement is determined using IPv6 extension headers and/or flow labels of the IPv6 extension headers.
5. The method as recited in claim 1 , further comprising receiving an opt in, or opt out, communication from a user indicating whether or not the user will participate in orchestrating the workload.
6. The method as recited in claim 5 , further comprising sharing opt in, and/or opt out, information among a set of end devices and edge stations.
7. The method as recited in claim 1 , further comprising protecting any personally identifiable information, included in the network telemetry, from unauthorized access.
8. The method as recited in claim 1 , further comprising receiving additional network telemetry, and migrating the workload from the one or more edge stations based on the additional network telemetry.
9. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
creating a manifest that specifies one or more requirements concerning a workload that is defined as execution of a group of containers associated with an application;
based on the requirements in the manifest, defining a tier topology of an N-tier configuration that includes multiple tiers;
gathering network telemetry and evaluating the network telemetry to determine if a system performance parameter, as indicated by the telemetry, meets one of the requirements specified in the manifest and, when the system performance parameter does not meet the requirement, modifying the number of tiers in the N-tier configuration;
orchestrating the workload across multiple tiers of the N-tier configuration, wherein the orchestrating is based on the network telemetry and the manifest and the orchestrating includes positioning each of the containers at one of the tiers of the N-tier configuration;
scheduling performance of the workload; and
performing the workload at one or more edge stations in accordance with the scheduling, wherein one of the edge stations is located on one tier of the N-tier configuration, and another of the edge stations is located on another tier of the N-tier configuration.
10. The non-transitory storage medium as recited in claim 9 , wherein the manifest specifies a startup strategy concerning the group of containers, weights for network performance expectations, and hardware requirements associated with performance of the workload.
11. The non-transitory storage medium as recited in claim 9 , wherein orchestrating the workload comprises defining an optimal placement of containers and data across N-tiers of the N-tier configuration.
12. The non-transitory storage medium as recited in claim 11 , wherein the optimal placement is determined using IPv6 extension headers and/or flow labels of the IPv6 extension headers.
13. The non-transitory storage medium as recited in claim 9 , wherein the operations further comprise receiving an opt in, or opt out, communication from a user indicating whether or not the user will participate in orchestrating the workload.
14. The non-transitory storage medium as recited in claim 13 , wherein the operations further comprise sharing opt in, and/or opt out, information among a set of end devices and edge stations.
15. The non-transitory storage medium as recited in claim 9 , wherein the operations further comprise protecting any personally identifiable information, included in the network telemetry, from unauthorized access.
16. The non-transitory storage medium as recited in claim 9 , wherein the operations further comprise receiving additional network telemetry, and migrating the workload from the one or more edge stations based on the additional network telemetry.