[
https://issues.apache.org/jira/browse/MESOS-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043042#comment-16043042
]
Neil Conway commented on MESOS-7636:
------------------------------------
Per offline discussion with [~vinodkone] and [~jieyu], the plan is to avoid
tackling this for now. The {{domain}} in {{Offer}} will just be the agent's
domain, which we make available as a convenience mechanism for frameworks.
Depending on exactly how the ERP message flow works, we'll need some way to
describe the domain of a resource provided by an ERP, but that can be solved
later.
> Add DomainInfo to Resource
> --------------------------
>
> Key: MESOS-7636
> URL: https://issues.apache.org/jira/browse/MESOS-7636
> Project: Mesos
> Issue Type: Bug
> Reporter: Neil Conway
> Assignee: Neil Conway
> Labels: mesosphere
>
> Add a new {{domain}} field to {{Resource}}, which identifies the domain where
> the resources are located.
> It would be nice to add this to a higher-level message, like {{Offer}}, but
> we need to account for the possibility that different resources in a single
> offer come from different domains -- e.g., when support for external resource
> providers is introduced.
> It will now be possible for an agent's checkpointed resources to change when
> the agent is drained and restarted. Combined with the change to preserve
> AgentID across agent drains (MESOS-6223), this will mean that if an agent
> re-registers, its resources might have changed; previous copies of the
> resource in the master's in-memory state will need to be updated.
> This also means that if a framework has cached the properties of a persistent
> volume it created, subsequently attempting to destroy that volume with the
> old persistent volume JSON may not succeed, because the PV's properties have
> changed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
