Upgrade Mesos Version #994

Merged
merged 3 commits into from May 17, 2016

Conversation

Projects
None yet
2 participants
@ssalinas
Member

ssalinas commented Apr 11, 2016

Currently built against 0.27.2, will bump to 0.28.1 if it is ready before we are ready to release.

Major changes:

  • .json endpoints no longer have the .json, however the deprecated versions of the endpoints are still in place, so no worries around the upgrade process
  • TaskStatus.Reason enum updated for memory limit
  • Bumped java version in docker image
  • Installing docker in slave image via apt
  • credential secret is now a String not a byte array

ssalinas added some commits Apr 11, 2016

@ssalinas

This comment has been minimized.

Show comment
Hide comment
@ssalinas

ssalinas Apr 14, 2016

Member

Bumped to 0.28.1 now that it has been released. Will not build currently beccause I am still investigating how closely mesos' new TASK_KILLING state maps to our TASK_CLEANING and how to handle the new one

Member

ssalinas commented Apr 14, 2016

Bumped to 0.28.1 now that it has been released. Will not build currently beccause I am still investigating how closely mesos' new TASK_KILLING state maps to our TASK_CLEANING and how to handle the new one

@ssalinas

This comment has been minimized.

Show comment
Hide comment
@ssalinas

ssalinas Apr 15, 2016

Member

So, it seems TASK_KILLING is triggered by the executor when it has received a request to kill and started the process of the kill. It doesn't quite map to our TASK_CLEANING state. However, reading through the PR comments, it seems that it's up to each executor to decide whether or not to send it, and up to each framework to decide whether or not to do anything with it. So, we can safely support but ignore usage of it for now

Member

ssalinas commented Apr 15, 2016

So, it seems TASK_KILLING is triggered by the executor when it has received a request to kill and started the process of the kill. It doesn't quite map to our TASK_CLEANING state. However, reading through the PR comments, it seems that it's up to each executor to decide whether or not to send it, and up to each framework to decide whether or not to do anything with it. So, we can safely support but ignore usage of it for now

@ssalinas ssalinas modified the milestone: 0.6.0 Apr 15, 2016

@jeffbyrnes jeffbyrnes referenced this pull request in evertrue/singularity-cookbook May 4, 2016

Merged

Upgrade to et_mesos cookbook ~> 5.0, update to Singularity v0.5.0 #16

@ssalinas ssalinas added the hs_stable label May 10, 2016

@ssalinas ssalinas modified the milestones: 0.6.0, 0.7.0 May 13, 2016

@ssalinas ssalinas merged commit d3a59f6 into master May 17, 2016

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@ssalinas ssalinas deleted the mesos_upgrade branch May 17, 2016

@tpetr

This comment has been minimized.

Show comment
Hide comment
@tpetr

tpetr May 20, 2016

Member

🚢

Member

tpetr commented on 30964a0 May 20, 2016

🚢

@tpetr

This comment has been minimized.

Show comment
Hide comment
@tpetr

tpetr May 20, 2016

Member

🚢

Member

tpetr commented on 373ecc2 May 20, 2016

🚢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment