On Mon, Dec 19, 2016 at 10:57 PM, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > In the past I have always seen this sort of problem handled as a > property to the scheduler, and a declaration that a certain job needs > certain properties. Indeed, we have discussed this as a property of the scheduler in kubernetes. - Nodes are given attributes (i.e. THP=never) - Users declare their requirements (i.e. THP=never) - User submits job, scheduler does matching to node - Node executes job This allows for shared control plane, serving disparate workloads on hybrid infra. THP=never is just another node attribute, as could be things like - Does a DPDK-capable NIC or GPU or FPGA exist, and is unused - What kernel version is it running - Is the node tuned correctly ...myriad other possibilities, in a rapidly evolving space. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
