[jira] [Updated] (MESOS-8469) Mesos master might drop some events in the operator API stream

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8469:
--
Story Points: 3
  Sprint: Mesosphere Sprint 73

> Mesos master might drop some events in the operator API stream
> --
>
> Key: MESOS-8469
> URL: https://issues.apache.org/jira/browse/MESOS-8469
> Project: Mesos
>  Issue Type: Bug
>Reporter: Vinod Kone
>Assignee: Greg Mann
>Priority: Critical
>
> Inside `Master::updateTask`, we call `Subscribers::send` which asynchronously 
> calls `Subscribers::Subscriber::send` on each subscriber.
> But the problem is that inside `Subscribers:Subscriber::send` we are looking 
> up the state of the master (e.g., getting Task* and Framework*) which might 
> have changed between `Subscribers::send ` and `Subscribers::Subscriber::send`.
>  
> For example, if a terminal task received an acknowledgement the task might be 
> removed from master's state, causing us to drop the TASK_UPDATED event.
>  
> We noticed this in an internal cluster, where a TASK_KILLED update was sent 
> to one subscriber but not the other.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8462) Unit test for `Slave::detachFile` on removed frameworks.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8462:
--
Story Points: 2

> Unit test for `Slave::detachFile` on removed frameworks.
> 
>
> Key: MESOS-8462
> URL: https://issues.apache.org/jira/browse/MESOS-8462
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chun-Hung Hsiao
>Assignee: Qian Zhang
>Priority: Major
>  Labels: mesosphere
>
> We should add a unit test for MESOS-8460.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-7944) Implement jemalloc support for Mesos

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-7944:
--
Sprint: Mesosphere Sprint 63, Mesosphere Sprint 65, Mesosphere Sprint 66, 
Mesosphere Sprint 67, Mesosphere Sprint 68, Mesosphere Sprint 72, Mesosphere 
Sprint 73  (was: Mesosphere Sprint 63, Mesosphere Sprint 65, Mesosphere Sprint 
66, Mesosphere Sprint 67, Mesosphere Sprint 68, Mesosphere Sprint 72)

> Implement jemalloc support for Mesos
> 
>
> Key: MESOS-7944
> URL: https://issues.apache.org/jira/browse/MESOS-7944
> Project: Mesos
>  Issue Type: Bug
>Reporter: Benno Evers
>Assignee: Benno Evers
>Priority: Major
>  Labels: mesosphere
>
> After investigation in MESOS-7876 and discussion on the mailing list, this 
> task is for tracking progress on adding out-of-the-box memory profiling 
> support using jemalloc to Mesos.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8305) DefaultExecutorTest.ROOT_MultiTaskgroupSharePidNamespace is flaky.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8305:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> DefaultExecutorTest.ROOT_MultiTaskgroupSharePidNamespace is flaky.
> --
>
> Key: MESOS-8305
> URL: https://issues.apache.org/jira/browse/MESOS-8305
> Project: Mesos
>  Issue Type: Bug
> Environment: Ubuntu 16.04
> Fedora 23
>Reporter: Alexander Rukletsov
>Assignee: Qian Zhang
>Priority: Major
>  Labels: flaky-test
> Attachments: ROOT_MultiTaskgroupSharePidNamespace-badrun.txt
>
>
> On Ubuntu 16.04:
> {noformat}
> ../../src/tests/default_executor_tests.cpp:1877
>   Expected: strings::trim(pidNamespace1.get())
>   Which is: "4026532250"
> To be equal to: strings::trim(pidNamespace2.get())
>   Which is: ""
> {noformat}
> Full log attached.
> On Fedora 23:
> {noformat}
> ../../src/tests/default_executor_tests.cpp:1878
>   Expected: strings::trim(pidNamespace1.get())
>   Which is: "4026532233"
> To be equal to: strings::trim(pidNamespace2.get())
>   Which is: ""
> {noformat}
> The test became flaky shortly after MESOS-7306 has been committed and likely 
> related to it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8415) Add an SLRP test for agent reboot.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8415:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> Add an SLRP test for agent  reboot.
> ---
>
> Key: MESOS-8415
> URL: https://issues.apache.org/jira/browse/MESOS-8415
> Project: Mesos
>  Issue Type: Task
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
>Priority: Major
>  Labels: mesosphere, storage
>
> We should add a test for the following scenario: when an agent is rebooted, 
> all previously published CSI volumes would become unmounted. So SLRP should 
> remount them when a task is going to use the volumes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8409) Add an SLRP test for agent registered with a new ID.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8409:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> Add an SLRP test for agent registered with a new ID.
> 
>
> Key: MESOS-8409
> URL: https://issues.apache.org/jira/browse/MESOS-8409
> Project: Mesos
>  Issue Type: Task
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
>Priority: Major
>  Labels: mesosphere, storage
>
> When an agent is registered with a new ID, SLRP should be assigned with a 
> different ID, and all previously created volumes would become pre-existing 
> volumes without profile.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8291) Add documentation about fault domains

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8291:
--
Sprint: Mesosphere Sprint 70, Mesosphere Sprint 71, Mesosphere Sprint 72, 
Mesosphere Sprint 73  (was: Mesosphere Sprint 70, Mesosphere Sprint 71, 
Mesosphere Sprint 72)

> Add documentation about fault domains
> -
>
> Key: MESOS-8291
> URL: https://issues.apache.org/jira/browse/MESOS-8291
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Vinod Kone
>Assignee: Benno Evers
>Priority: Major
>
> We need some user docs for fault domains.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8428) SLRP recovery tests leak file descriptors.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8428:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> SLRP recovery tests leak file descriptors.
> --
>
> Key: MESOS-8428
> URL: https://issues.apache.org/jira/browse/MESOS-8428
> Project: Mesos
>  Issue Type: Bug
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
>Priority: Major
>  Labels: mesosphere, storage
>
> The {{CreateDestroyVolumeRecovery}} (formerly {{NewVolumeRecovery}}) and 
> {{PublishResourcesRecovery}} (formerly {{LaunchTaskRecovery}}) tests leak 
> fds. When running them in repetition, either the following error will 
> manifest:
> {noformat}
> rocess_posix.hpp:257] CHECK_SOME(pipe): Too many open files
> {noformat}
> or the plugin container will exit possibly due to no fd.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8462) Unit test for `Slave::detachFile` on removed frameworks.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8462:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> Unit test for `Slave::detachFile` on removed frameworks.
> 
>
> Key: MESOS-8462
> URL: https://issues.apache.org/jira/browse/MESOS-8462
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chun-Hung Hsiao
>Assignee: Qian Zhang
>Priority: Major
>  Labels: mesosphere
>
> We should add a unit test for MESOS-8460.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8382) Master should bookkeep local resource providers.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8382:
--
Sprint: Mesosphere Sprint 71, Mesosphere Sprint 72, Mesosphere Sprint 73  
(was: Mesosphere Sprint 71, Mesosphere Sprint 72)

> Master should bookkeep local resource providers.
> 
>
> Key: MESOS-8382
> URL: https://issues.apache.org/jira/browse/MESOS-8382
> Project: Mesos
>  Issue Type: Task
>Reporter: Jie Yu
>Assignee: Benjamin Bannier
>Priority: Major
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> This will simplify the handling of `UpdateSlaveMessage`. ALso, it'll simplify 
> the endpoint serving.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-7506) Multiple tests leave orphan containers.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-7506:
--
Sprint: Mesosphere Sprint 66, Mesosphere Sprint 67, Mesosphere Sprint 68, 
Mesosphere Sprint 69, Mesosphere Sprint 70, Mesosphere Sprint 72, Mesosphere 
Sprint 73  (was: Mesosphere Sprint 66, Mesosphere Sprint 67, Mesosphere Sprint 
68, Mesosphere Sprint 69, Mesosphere Sprint 70, Mesosphere Sprint 72)

> Multiple tests leave orphan containers.
> ---
>
> Key: MESOS-7506
> URL: https://issues.apache.org/jira/browse/MESOS-7506
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
> Environment: Ubuntu 16.04
> Fedora 23
> other Linux distros
>Reporter: Alexander Rukletsov
>Assignee: Andrei Budnik
>Priority: Major
>  Labels: containerizer, flaky-test, mesosphere
> Attachments: KillMultipleTasks-badrun.txt, 
> ROOT_IsolatorFlags-badrun.txt, ROOT_IsolatorFlags-badrun2.txt, 
> ROOT_IsolatorFlags-badrun3.txt, ReconcileTasksMissingFromSlave-badrun.txt, 
> ResourceLimitation-badrun.txt, ResourceLimitation-badrun2.txt, 
> RestartSlaveRequireExecutorAuthentication-badrun.txt, 
> TaskWithFileURI-badrun.txt
>
>
> I've observed a number of flaky tests that leave orphan containers upon 
> cleanup. A typical log looks like this:
> {noformat}
> ../../src/tests/cluster.cpp:580: Failure
> Value of: containers->empty()
>   Actual: false
> Expected: true
> Failed to destroy containers: { da3e8aa8-98e7-4e72-a8fd-5d0bae960014 }
> {noformat}
> All currently affected tests:
> {noformat}
> SlaveTest.RestartSlaveRequireExecutorAuthentication // cannot reproduce any 
> more
> ROOT_IsolatorFlags
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8357) Example frameworks have an inconsistent UX.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8357:
--
Sprint: Mesosphere Sprint 71, Mesosphere Sprint 72, Mesosphere Sprint 73  
(was: Mesosphere Sprint 71, Mesosphere Sprint 72)

> Example frameworks have an inconsistent UX.
> ---
>
> Key: MESOS-8357
> URL: https://issues.apache.org/jira/browse/MESOS-8357
> Project: Mesos
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Till Toenshoff
>Assignee: Till Toenshoff
>Priority: Minor
>  Labels: mesosphere
>
> Our example frameworks are a bit inconsistent when it comes to specifying 
> things like the framework principal / secret etc.. 
> Many of these examples have great value in testing a Mesos cluster. Unifying 
> the parameterizing would improve the user experience when testing Mesos.
> {{MESOS_AUTHENTICATE_FRAMEWORKS}} is being used by many examples for enabling 
> / disabling authentication. {{load_generator_framework}} as one example 
> however uses {{MESOS_AUTHENTICATE}} for that purpose. The credentials 
> themselves are most commonly expected in environment variables 
> {{DEFAULT_PRINCIPAL}} and {{DEFAULT_SECRET}} while in some cases we chose to 
> use {{MESOS_PRINCIPAL}}, {{MESOS_SECRET}} instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8411) Killing a queued task can lead to the command executor never terminating.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8411:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> Killing a queued task can lead to the command executor never terminating.
> -
>
> Key: MESOS-8411
> URL: https://issues.apache.org/jira/browse/MESOS-8411
> Project: Mesos
>  Issue Type: Bug
>  Components: agent
>Affects Versions: 1.3.0
>Reporter: Benjamin Mahler
>Assignee: Meng Zhu
>Priority: Critical
>
> If a task is killed while the executor is re-registering, we will remove it 
> from queued tasks and shut down the executor if all the its initial tasks 
> could not be delivered. However, there is a case (within {{Slave::___run}}) 
> where we leave the executor running, the race is:
> # Command-executor task launched.
> # Command executor sends registration message. Agent tells containerizer to 
> update the resources before it sends the tasks to the executor.
> # Kill arrives, and we synchronously remove the task from queued tasks.
> # Containerizer finishes updating the resources, and in {{Slave::___run}} the 
> killed task is ignored.
> # Command executor stays running!
> Executors could have a timeout to handle this case, but it's not clear that 
> all executors will implement this correctly. It would be better to have a 
> defensive policy that will shut down an executor if all of its initial batch 
> of tasks were killed prior to delivery.
> In order to implement this, one approach discussed with [~vinodkone] is to 
> look at the running + terminated but unacked + completed tasks, and if empty, 
> shut the executor down in the {{Slave::___run}} path. This will require us to 
> check that the completed task cache size is set to at least 1, and this also 
> assumes that the completed tasks are not cleared based on time or during 
> agent recovery.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8426) Speed up SLRP tests

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8426:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> Speed up SLRP tests
> ---
>
> Key: MESOS-8426
> URL: https://issues.apache.org/jira/browse/MESOS-8426
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
>Priority: Major
>  Labels: mesosphere, storage
>
> Each of the current SLRP unit tests takes seconds to run. This can be 
> improved by reducing the allocation interval and declining offers with 
> filters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-7742) ContentType/AgentAPIStreamingTest.AttachInputToNestedContainerSession is flaky

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-7742:
--
Sprint: Mesosphere Sprint 58, Mesosphere Sprint 72, Mesosphere Sprint 73  
(was: Mesosphere Sprint 58, Mesosphere Sprint 72)

> ContentType/AgentAPIStreamingTest.AttachInputToNestedContainerSession is flaky
> --
>
> Key: MESOS-7742
> URL: https://issues.apache.org/jira/browse/MESOS-7742
> Project: Mesos
>  Issue Type: Bug
>  Components: agent
>Affects Versions: 1.5.0
>Reporter: Vinod Kone
>Assignee: Andrei Budnik
>Priority: Major
>  Labels: flaky-test, mesosphere-oncall
> Fix For: 1.6.0
>
> Attachments: AgentAPITest.LaunchNestedContainerSession-badrun.txt, 
> LaunchNestedContainerSessionDisconnected-badrun.txt
>
>
> Observed this on ASF CI and internal Mesosphere CI. Affected tests:
> {noformat}
> AgentAPIStreamingTest.AttachInputToNestedContainerSession
> AgentAPITest.LaunchNestedContainerSession
> AgentAPITest.AttachContainerInputAuthorization/0
> AgentAPITest.LaunchNestedContainerSessionWithTTY/0
> AgentAPITest.LaunchNestedContainerSessionDisconnected/1
> {noformat}
> This issue comes at least in three different flavours. Take 
> {{AgentAPIStreamingTest.AttachInputToNestedContainerSession}} as an example.
> h5. Flavour 1
> {noformat}
> ../../src/tests/api_tests.cpp:6473
> Value of: (response).get().status
>   Actual: "503 Service Unavailable"
> Expected: http::OK().status
> Which is: "200 OK"
> Body: ""
> {noformat}
> h5. Flavour 2
> {noformat}
> ../../src/tests/api_tests.cpp:6473
> Value of: (response).get().status
>   Actual: "500 Internal Server Error"
> Expected: http::OK().status
> Which is: "200 OK"
> Body: "Disconnected"
> {noformat}
> h5. Flavour 3
> {noformat}
> /home/ubuntu/workspace/mesos/Mesos_CI-build/FLAG/CMake/label/mesos-ec2-ubuntu-16.04/mesos/src/tests/api_tests.cpp:6367
> Value of: (sessionResponse).get().status
>   Actual: "500 Internal Server Error"
> Expected: http::OK().status
> Which is: "200 OK"
> Body: ""
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-5333) GET /master/maintenance/schedule/ produces 404.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-5333:
--
Sprint: Mesosphere Sprint 70, Mesosphere Sprint 71, Mesosphere Sprint 72, 
Mesosphere Sprint 73  (was: Mesosphere Sprint 70, Mesosphere Sprint 71, 
Mesosphere Sprint 72)

> GET /master/maintenance/schedule/ produces 404.
> ---
>
> Key: MESOS-5333
> URL: https://issues.apache.org/jira/browse/MESOS-5333
> Project: Mesos
>  Issue Type: Bug
>  Components: HTTP API, libprocess
>Reporter: Nathan Handler
>Assignee: Alexander Rukletsov
>Priority: Minor
>  Labels: mesosphere
>
> Attempts to make a GET request to /master/maintenance/schedule/ result in a 
> 404. However, if I make a GET request to /master/maintenance/schedule 
> (without the trailing /), it works. My current (untested) theory is that this 
> might be related to the fact that there is also a 
> /master/maintenance/schedule/status endpoint (an endpoint built on top of a 
> functioning endpoint), as requests to /help and /help/ (with and without the 
> trailing slash) produce the same functioning result.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-5362) Add authentication to example frameworks

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-5362:
--
Sprint: Mesosphere Sprint 71, Mesosphere Sprint 72, Mesosphere Sprint 73  
(was: Mesosphere Sprint 71, Mesosphere Sprint 72)

> Add authentication to example frameworks
> 
>
> Key: MESOS-5362
> URL: https://issues.apache.org/jira/browse/MESOS-5362
> Project: Mesos
>  Issue Type: Improvement
>  Components: security
>Reporter: Greg Mann
>Assignee: Till Toenshoff
>Priority: Major
>  Labels: authentication, mesosphere, security
>
> Some example frameworks do not have the ability to authenticate with the 
> master. Adding authentication to the example frameworks that don't already 
> have it implemented would allow us to use these frameworks for testing in 
> authenticated/authorized scenarios.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8373) Test reconciliation after operation is dropped en route to agent

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8373:
--
Sprint: Mesosphere Sprint 71, Mesosphere Sprint 72, Mesosphere Sprint 73  
(was: Mesosphere Sprint 71, Mesosphere Sprint 72)

> Test reconciliation after operation is dropped en route to agent
> 
>
> Key: MESOS-8373
> URL: https://issues.apache.org/jira/browse/MESOS-8373
> Project: Mesos
>  Issue Type: Task
>  Components: agent, master
>Reporter: Greg Mann
>Assignee: Greg Mann
>Priority: Major
>  Labels: mesosphere
>
> Since new code paths were added to handle operations on resources in 1.5, we 
> should test that such operations are reconciled correctly after an operation 
> is dropped on the way from the master to the agent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8427) Clean up residual CSI endpoints for SLRP tests.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8427:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> Clean up residual CSI endpoints for SLRP tests.
> ---
>
> Key: MESOS-8427
> URL: https://issues.apache.org/jira/browse/MESOS-8427
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Chun-Hung Hsiao
>Assignee: Chun-Hung Hsiao
>Priority: Major
>  Labels: mesosphere, storage
>
> Since the CSI endpoints are not in the sandbox directory of the unit tests, 
> they need to be explicitly cleaned up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8424) Test that operations are correctly reported following a master failover

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8424:
--
Sprint: Mesosphere Sprint 72, Mesosphere Sprint 73  (was: Mesosphere Sprint 
72)

> Test that operations are correctly reported following a master failover
> ---
>
> Key: MESOS-8424
> URL: https://issues.apache.org/jira/browse/MESOS-8424
> Project: Mesos
>  Issue Type: Task
>  Components: master
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>Priority: Major
>  Labels: mesosphere
>
> As the master keeps track of operations running on a resource provider, it 
> needs to be updated on these operations when agents reregister after a master 
> failover. E.g., an operation that has finished during the failover should be 
> reported as finished by the master after the agent on which the resource 
> provider is running has reregistered.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (MESOS-8361) Example frameworks to support launching mesos-local.

2018-01-20 Thread Vinod Kone (JIRA)

 [ 
https://issues.apache.org/jira/browse/MESOS-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-8361:
--
Sprint: Mesosphere Sprint 71, Mesosphere Sprint 72, Mesosphere Sprint 73  
(was: Mesosphere Sprint 71, Mesosphere Sprint 72)

> Example frameworks to support launching mesos-local.
> 
>
> Key: MESOS-8361
> URL: https://issues.apache.org/jira/browse/MESOS-8361
> Project: Mesos
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: 1.5.0
>Reporter: Till Toenshoff
>Assignee: Till Toenshoff
>Priority: Minor
>  Labels: mesosphere
>
> The scheduler driver and library support implicit launching of mesos-local 
> for a convenient test setup. Some of our example frameworks account for this 
> in supporting implicit ACL rendering and more. 
> We should unify the experience by documenting this behaviour and adding it to 
> all example frameworks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MESOS-5827) Add example framework for using inverse offers

2018-01-20 Thread Till Toenshoff (JIRA)

[ 
https://issues.apache.org/jira/browse/MESOS-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16333266#comment-16333266
 ] 

Till Toenshoff commented on MESOS-5827:
---

Adds framework authentication to the inverse-offers-framework: 
https://reviews.apache.org/r/65255/

> Add example framework for using inverse offers
> --
>
> Key: MESOS-5827
> URL: https://issues.apache.org/jira/browse/MESOS-5827
> Project: Mesos
>  Issue Type: Task
>Reporter: Artem Harutyunyan
>Assignee: Joseph Wu
>Priority: Minor
>  Labels: mesosphere, newbie
>
> We should have an example framework (in src/examples) demonstrating how to 
> handle inverse offers. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)