[jira] [Assigned] (MESOS-10141) CSI External Volume Support
[ https://issues.apache.org/jira/browse/MESOS-10141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Dary reassigned MESOS-10141: Assignee: Qian Zhang > CSI External Volume Support > --- > > Key: MESOS-10141 > URL: https://issues.apache.org/jira/browse/MESOS-10141 > Project: Mesos > Issue Type: Epic >Reporter: Greg Mann >Assignee: Qian Zhang >Priority: Major > Labels: csi, external-volumes, storage > > This epic tracks work for our MVP of external volume support in Mesos using > the CSI standard. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MESOS-6568) JSON serialization should not omit empty arrays in HTTP APIs
[
https://issues.apache.org/jira/browse/MESOS-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089641#comment-17089641
]
Dominik Dary commented on MESOS-6568:
-
[~bmahler] this is done, right?
> JSON serialization should not omit empty arrays in HTTP APIs
>
>
> Key: MESOS-6568
> URL: https://issues.apache.org/jira/browse/MESOS-6568
> Project: Mesos
> Issue Type: Improvement
> Components: HTTP API
>Reporter: Neil Conway
>Assignee: Benjamin Mahler
>Priority: Major
> Labels: mesosphere
>
> When using the JSON content type with the HTTP APIs, a {{repeated}} protobuf
> field is omitted entirely from the JSON serialization of the message. For
> example, this is a response to the {{GetTasks}} call:
> {noformat}
> {
> "get_tasks": {
> "tasks": [{...}]
> },
> "type": "GET_TASKS"
> }
> {noformat}
> I think it would be better to include empty arrays for the other fields of
> the message ({{pending_tasks}}, {{completed_tasks}}, etc.). Advantages:
> # Consistency with the old HTTP endpoints, e.g., /state
> # Semantically, an empty array is more accurate. The master's response should
> be interpreted as saying it doesn't know about any pending/completed tasks;
> that is more accurately conveyed by explicitly including an empty array, not
> by omitting the key entirely.
> *NOTE: The
> [asV1Protobuf|https://github.com/apache/mesos/blob/d10a33acc426dda9e34db995f16450faf898bb3b/src/common/http.cpp#L172-L423]
> copy needs to also be updated.*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MESOS-10004) Enable SSL on Windows
[ https://issues.apache.org/jira/browse/MESOS-10004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073672#comment-17073672 ] Dominik Dary commented on MESOS-10004: -- [~greggomann] can this be closed? /cc [~bmahler] [~asekretenko] > Enable SSL on Windows > - > > Key: MESOS-10004 > URL: https://issues.apache.org/jira/browse/MESOS-10004 > Project: Mesos > Issue Type: Epic >Reporter: Greg Mann >Assignee: Joseph Wu >Priority: Major > Labels: foundations > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MESOS-10072) Windows: Curl requires zlib when built with SSL support on Windows
[
https://issues.apache.org/jira/browse/MESOS-10072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049317#comment-17049317
]
Dominik Dary commented on MESOS-10072:
--
[~greggomann] what is the priority of this task? blocker for GA?
> Windows: Curl requires zlib when built with SSL support on Windows
> --
>
> Key: MESOS-10072
> URL: https://issues.apache.org/jira/browse/MESOS-10072
> Project: Mesos
> Issue Type: Task
>Reporter: Joseph Wu
>Priority: Major
> Labels: curl, foundations, windows
> Attachments: Screen Shot 2019-12-17 at 1.38.43 PM.png
>
>
> After building Windows with --enable-ssl, some curl-related tests, like
> health check tests, start failing with the odd exit code {{-1073741515}}.
> Running curl directly with the Visual Studio debugger yields this error:
> !Screen Shot 2019-12-17 at 1.38.43 PM.png|width=343,height=164!
> Some documentation online seems to support this additional requirement:
> [https://wiki.dlang.org/Curl_on_Windows]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
