Hmm. I wonder if we could use "MesosSlave" to encapsulate the slave specific attributes and pass that along to the scheduler. Currently it is a bit weird because "master" and "frameworkName" are directly passed even though they are part of MesosCloud. I am ok passing MesosCloud to the scheduler if we clean up the scheduler's constructor to not take redundant information. Makes sense?