nova-orchestration team mailing list archive

[Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx>]

Yeah, tricky. I'm hesitant to do a key/value table like InstanceTypeExtraSpecs since it makes it hard to query. I'd prefer something with a little more structure.

We may need to simply allow for custom join tables that work with the specific scheduler, but provide some hooks in the ZoneManager to allow the updates to get written when events arrive? Dunno.

I'm trying to get the base CapacityCache stuff finalized soon, so perhaps that'll be a better discussion point?

-S

________________________________
From: Lorin Hochstein [lorin@xxxxxxx]
Sent: Saturday, December 03, 2011 7:58 PM
To: Sandy Walsh
Cc: nova-orchestration@xxxxxxxxxxxxxxxxxxx; nova-scaling@xxxxxxxxxxxxxxxxxxx; dodcs list
Subject: Re: [Nova-orchestration] Tactical Scheduler/Scalability plan ...

Hi Sandy:

Just a note:  we want track usage of additional resources on the compute node(e.g., GPUs, or FPGAs), so we'd like to be able to extend the info tracked in the Capacity Cache to support arbitrary resources.

What do you think the best way is to support tracking this type of additional data within this scheme?

Lorin
--
Lorin Hochstein, Computer Scientist
USC Information Sciences Institute
703.812.3710
http://www.east.isi.edu/~lorin




On Dec 1, 2011, at 6:53 AM, Sandy Walsh wrote:

Hi y'all,

Attached are some notes from the whiteboard noodling myself, comstud and anotherjesse did last week:
http://wiki.openstack.org/EssexSchedulerImprovements

It addresses some tactical problems we're facing and, hopefully, sets up a pattern for further improvements and hooks for things like orchestration.

Look forward to your feedback!

Cheers,
Sandy

--
Mailing list: https://launchpad.net/~nova-orchestration
Post to     : nova-orchestration@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~nova-orchestration
More help   : https://help.launchpad.net/ListHelp