Files
kubernetes/test/e2e_node
Francesco Romani d9d652e867 e2e: topomgr: initial negative tests
Negative tests is when we request a gu Pod we know the system cannot
fullfill - hence we expect rejection from the topology manager.

Unfortunately, besides the trivial case of excessive cores (request
more socket than a NUMA node provides) we cannot easily test the
devices, because crafting a proper pod will require detailed knowledge
of the hw topology.

Let's consider a hypotetical two-node NUMA system with two PCIe busses,
one per NUMA node, with a SRIOV device on each bus.
A proper negative test would require two SRIOV device, that the system
can provide but not on the same single NUMA node.
Requiring for example three devices (one more than the system provides)
will lead to a different, legitimate admission error.

For these reasons we bootstrap the testing infra for the negative tests,
but we add just the simplest one.

Signed-off-by: Francesco Romani <fromani@redhat.com>
2020-02-10 22:47:53 +01:00
..
2019-11-06 17:39:05 -05:00
2019-11-21 11:17:46 +08:00
2017-10-15 18:18:13 -07:00
2020-01-29 04:41:29 -05:00
2019-02-23 10:28:04 +08:00
2020-02-07 18:16:47 -08:00
2020-02-07 18:16:47 -08:00
2020-02-07 18:16:47 -08:00
2020-02-07 18:16:47 -08:00
2020-02-08 12:30:21 -05:00
2019-11-26 16:26:55 +08:00
2020-02-07 18:16:47 -08:00
2020-01-17 21:08:13 -05:00
2020-02-08 12:30:21 -05:00
2020-02-07 18:16:47 -08:00
2020-02-07 18:16:47 -08:00
2020-02-10 22:47:53 +01:00
2020-02-07 18:16:47 -08:00
2020-02-07 18:16:47 -08:00
2019-02-15 09:13:07 -05:00
2020-02-07 18:16:47 -08:00
2020-02-07 18:16:47 -08:00
2020-02-07 18:16:47 -08:00
2020-02-08 12:30:21 -05:00
2020-02-07 18:16:47 -08:00