nickrenren / firmament-go Goto Github PK

TODOs:

Short term:

• network topology construction (slot model)
• cost model development
• think about how to control the rescheduling logic (both firmament and poseidon)
  • how to deal with the migration and eviction situations
• revisit all the panic logic (log.Panic(...))
• revisit all TODO comments among coding files
• add mutex for scheduler functions, just like Firmament does

Medium term:

• demo and benchmark

Long term:

• network topology optimization (non-slot model, depend on actual capacity and request in order to reduce resource fragmentation)
• take other factors into account (not only resource but also other restrictions, such as affinity/anti-affinity, label/selector, taint/toleration ...)
• network topology visualizations (memory display and website display)
• multiple cost model policies
• integrate solver code into flow scheduler
• MCMF algorithm optimization