[
https://issues.apache.org/jira/browse/AURORA-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717677#comment-14717677
]
Kevin Sweeney commented on AURORA-1448:
---------------------------------------
[~wfarner] The terminology shift was underway at MesosCon, with most of the
speakers using the "Agent" term. The proposed patches here are to standardize
Aurora's internal usage of the term (only using the old term when
backwards-compatibility or an external library has not yet updated). I agree
with not getting ahead too far ahead of upstream's changes here, but I can't
imagine the time horizon is especially long, given the ease at which I was able
to produce the Aurora patches over the course of half a day. Given that our
next release is probably a month out it seems fine to get ahead of upstream a
bit on this.
[~benjaminhindman], [~vinodkone]: do you know a rough ETA of when upstream
documentation will be updated?
> Refer to Mesos Agent instead of Mesos Slave
> -------------------------------------------
>
> Key: AURORA-1448
> URL: https://issues.apache.org/jira/browse/AURORA-1448
> Project: Aurora
> Issue Type: Epic
> Reporter: Kevin Sweeney
>
> Upstream has decided to use the terminology "Mesos Agent" in place of "Mesos
> Slave"; we should update any Aurora references to match, keeping
> backwards-compatibility considerations in mind (in most cases few exist since
> Thrift defines binary compatibility in terms of field numbering and not
> naming).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
