[OSSTEST PATCH 0/2] Test case for cpupools

[Dario Faggioli <dario.faggioli@citrix.com>]

Just the fact that we are not doing anything to smoke test cpupools, while I
think we should. :-)

This add something quite basic, but it's, IMO, already representative one
typically does with cpupools. We can add more pCPU related tricks (removing,
adding, etc), or we can add more domains and move them around more, of course.
If anyone has any suggestion about operations that should really be part of
Osstest's runs, let me know and I'll include them.

As it is right now, the test is super quick, to the point that I considered
whether it wouldn't have been better to add some similar cpupool operations in
one of the existing jobs. I ended up deciding for having a separate job,
because this is, after all, a rather specific operation, and a different enough
thing from basic VM lifecycle, so I think it deserves its own job.

Thanks and Regards, Dario

---

Dario Faggioli (2):
      ts-cpupools: new test script
      Testing cpupools: recipe for it and job definition


 make-flight |   11 +++++
 sg-run-job  |    6 +++
 ts-cpupools |  124 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 141 insertions(+)
 create mode 100755 ts-cpupools

--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)