aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sweeney (JIRA)" <>
Subject [jira] [Created] (AURORA-1498) aurora task run doesn't accept aliased port names
Date Tue, 22 Sep 2015 22:38:04 GMT
Kevin Sweeney created AURORA-1498:

             Summary: aurora task run doesn't accept aliased port names
                 Key: AURORA-1498
             Project: Aurora
          Issue Type: Bug
            Reporter: Kevin Sweeney

Aurora task run allows you to specify a port name and have it expanded, e.g.

aurora task run us-west-1/mesos/prod/labrat/0 'curl -s http://localhost:{{thermos.ports[admin]}}/vars
| grep jvm_uptime'

However, only the canonical name works here, any ports aliased with {{portmap}} do not. This
is because the client uses the list of ports on the scheduler and does not take into account
the portmap during template substitution. [1] This is confusing, as aliased port names work
fine in the aurora config file.

I see a couple ways forward:
(1) Populate the portmap as metadata in the config sent to the scheduler and use that in addition
to {{assignedPorts}}.
(2) Parse {{the portmap}} from the task JSON in the Thrift {{executorConfig}} field and merge
it with {{assignedPorts}}.
(3) Improve the error message to note that {{aurora task run}} requires the canonical port

(3) is the easiest but least user-friendly. (1) is backwards-incompatible but allows the portmap
data to be used by the aurora UI too. (2) is backwards-compatible, but would require knowledge
of the Thermos Task schema to be usable on the UI. My preference is for (2).


This message was sent by Atlassian JIRA

View raw message