[MESOS-8357] Example frameworks have an inconsistent UX.

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Labels: mesosphere
• Target Version/s: 1.6.0
• Sprint: Mesosphere Sprint 71, Mesosphere Sprint 72, Mesosphere Sprint 73
• Story Points: 3
• Assignee: Till Toenshoff
• Reporter: Till Toenshoff
• Shepherd: Vinod Kone
• Created: 22/Dec/17 20:10
• Updated: 31/Jan/18 02:51
• Resolved: 31/Jan/18 02:51

Description

Our example frameworks are a bit inconsistent when it comes to specifying things like the framework principal / secret etc..
Many of these examples have great value in testing a Mesos cluster. Unifying the parameterizing would improve the user experience when testing Mesos.

MESOS_AUTHENTICATE_FRAMEWORKS is being used by many examples for enabling / disabling authentication. load_generator_framework as one example however uses MESOS_AUTHENTICATE for that purpose. The credentials themselves are most commonly expected in environment variables DEFAULT_PRINCIPAL and DEFAULT_SECRET while in some cases we chose to use MESOS_PRINCIPAL, MESOS_SECRET instead.

Issue Links

• incorporates: MESOS-8412 Example frameworks should support passing options via both command line flags or environment variables
• relates to: MESOS-8412 Example frameworks should support passing options via both command line flags or environment variables
• relates to: MESOS-5362 Add authentication to example frameworks
• relates to: MESOS-8361 Example frameworks to support launching mesos-local.