I tossed a few small things into my larger thread about getting Myriad running, so I am going to start separate threads to break them out.
When starting Myriad, it seems we now need to have at least one node manager specified at startup (based on the config file as seen below) nmInstances: # NMs to start with. Requires at least 1 NM with a non-zero profile. medium: 1 # <profile_name : instances> This is going to lead to task failures with mesos dns because the name won't be ready right away (potentially a 1 minute delay after kicking off Myriad) do we NEED to have a non-0 profile nodemanager startup with the resource manager? Can't we start Myriad with no nodemanagers, and then have automation (i.e. a startup procedure with a script to flex up after the myriad.marathon.mesos names begins to resolve) to flex up?
