Monday, April 15 • 3:40pm - 4:20pm
Concurrent Resource Scheduling in Heat

Sign up or log in to save this to your schedule and see who's attending!

Heat currently uses a strategy of only creating/deleting/updating one resource per stack at a time. It does this in in dependency-topology order which keeps the code simple and guarantees things happen in the intended order. With large stacks, this will mean a significant amount of time spent waiting unnecessarily. We should discuss the problem space and various strategies to reduce waiting.

(Session proposed by Clint Byrum)

Monday April 15, 2013 3:40pm - 4:20pm

Attendees (0)