[
https://issues.apache.org/jira/browse/MESOS-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001225#comment-15001225
]
Greg Mann commented on MESOS-3064:
----------------------------------
Also, [~adam-mesos] raised the question of whether or not this {{principal}}
field really should be changed to 'required' in the future. He said that it led
to some confusion for framework developers, who thought that the 'required'
{{principal}} field in {{DiskInfo}} implied that authorization had to be
enabled in order for persistent volumes to be used. I'd say that is perhaps an
issue that can be addressed with better documentation, but I wonder if there
are other good arguments for/against making it 'required'? We can always just
fail authorizations when there is no {{principal}} found, so I'm not sure why
it would strictly need to be 'required'.
> Add 'principal' field to 'Resource.DiskInfo.Persistence'
> --------------------------------------------------------
>
> Key: MESOS-3064
> URL: https://issues.apache.org/jira/browse/MESOS-3064
> Project: Mesos
> Issue Type: Task
> Reporter: Michael Park
> Assignee: Greg Mann
> Labels: mesosphere, persistent-volumes
>
> In order to support authorization for persistent volumes, we should add the
> {{principal}} to {{Resource.DiskInfo}}, analogous to
> {{Resource.ReservationInfo.principal}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
