mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kone (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-8357) Example frameworks have an inconsistent UX.
Date Sun, 21 Jan 2018 01:12:04 GMT

     [ https://issues.apache.org/jira/browse/MESOS-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kone updated MESOS-8357:
------------------------------
    Sprint: Mesosphere Sprint 71, Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere
Sprint 71, Mesosphere Sprint 72)

> Example frameworks have an inconsistent UX.
> -------------------------------------------
>
>                 Key: MESOS-8357
>                 URL: https://issues.apache.org/jira/browse/MESOS-8357
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 1.5.0
>            Reporter: Till Toenshoff
>            Assignee: Till Toenshoff
>            Priority: Minor
>              Labels: mesosphere
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message