[jira] [Created] (AURORA-1776) Switch `launchTask` Mesos Driver call in favor of `acceptOffers` to support future dynamic reservation operations

Dmitriy Shirchenko created AURORA-1776: -- Summary: Switch `launchTask` Mesos Driver call in favor of `acceptOffers` to support future dynamic reservation operations Key: AURORA-1776 URL: https://issues.apache.

[jira] [Commented] (AURORA-1772) Do not resend TaskStateChange events every time a scheduler starts

[ https://issues.apache.org/jira/browse/AURORA-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15498106#comment-15498106 ] Dmitriy Shirchenko commented on AURORA-1772: https://reviews.apache.org/r/519

[jira] [Commented] (AURORA-1775) Updating pants to 1.1.0-rc7 breaks the make-pycharm-virtualenv script

[ https://issues.apache.org/jira/browse/AURORA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497746#comment-15497746 ] Zameer Manji commented on AURORA-1775: -- [~jsirois]: Any guidance here? It seems that

[jira] [Updated] (AURORA-1775) Updating pants to 1.1.0-rc7 breaks the make-pycharm-virtualenv script

[ https://issues.apache.org/jira/browse/AURORA-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Huang updated AURORA-1775: -- Description: When I run build-support/python/make-pycharm-virtualenv script locally, exceptions were t

[jira] [Created] (AURORA-1775) Updating pants to 1.1.0-rc7 breaks the make-pycharm-virtualenv script

Kai Huang created AURORA-1775: - Summary: Updating pants to 1.1.0-rc7 breaks the make-pycharm-virtualenv script Key: AURORA-1775 URL: https://issues.apache.org/jira/browse/AURORA-1775 Project: Aurora

[jira] [Commented] (AURORA-1739) createJob thrift api for golang consistenly failing with empty CronSchedule

[ https://issues.apache.org/jira/browse/AURORA-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497417#comment-15497417 ] Hudson commented on AURORA-1739: SUCCESS: Integrated in Jenkins build Aurora #1612 (See

[jira] [Resolved] (AURORA-1739) createJob thrift api for golang consistenly failing with empty CronSchedule

[ https://issues.apache.org/jira/browse/AURORA-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renan DelValle resolved AURORA-1739. Resolution: Fixed Fix Version/s: 0.16.0 https://reviews.apache.org/r/51973/ > creat

[jira] [Commented] (AURORA-1632) Investigate executor fixes when Mesos 0.30.0 stops passing along environment variables

[ https://issues.apache.org/jira/browse/AURORA-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496980#comment-15496980 ] Zameer Manji commented on AURORA-1632: -- I think this means Mesos 1.0 or 1.1. > Inve

[jira] [Assigned] (AURORA-1739) createJob thrift api for golang consistenly failing with empty CronSchedule

[ https://issues.apache.org/jira/browse/AURORA-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renan DelValle reassigned AURORA-1739: -- Assignee: Renan DelValle > createJob thrift api for golang consistenly failing with em

[jira] [Commented] (AURORA-327) Aurora shutdown blocks when attempting to abdicate leadership and zk ensemble is down

[ https://issues.apache.org/jira/browse/AURORA-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496537#comment-15496537 ] John Sirois commented on AURORA-327: Actually - it does make sense to resolve this now

[jira] [Commented] (AURORA-1661) Scheduler leader failed to re-announce itself after ZK name was changed

[ https://issues.apache.org/jira/browse/AURORA-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496532#comment-15496532 ] John Sirois commented on AURORA-1661: - That's silly - you're right. > Scheduler lead

[jira] [Commented] (AURORA-1661) Scheduler leader failed to re-announce itself after ZK name was changed

[ https://issues.apache.org/jira/browse/AURORA-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496522#comment-15496522 ] John Sirois commented on AURORA-1661: - I'd like to leave it as blocked on AURORA-1669

[jira] [Commented] (AURORA-327) Aurora shutdown blocks when attempting to abdicate leadership and zk ensemble is down

[ https://issues.apache.org/jira/browse/AURORA-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496520#comment-15496520 ] John Sirois commented on AURORA-327: It should be - yes. That said, I'd like to leave

[jira] [Updated] (AURORA-1286) Remove Locks for Crons

[ https://issues.apache.org/jira/browse/AURORA-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb updated AURORA-1286: Labels: tech-debt (was: ) > Remove Locks for Crons > -- > > Ke

[jira] [Updated] (AURORA-1689) Clean up usage of global checkpoint root by the observer

[ https://issues.apache.org/jira/browse/AURORA-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb updated AURORA-1689: Labels: tech-debt (was: ) > Clean up usage of global checkpoint root by the observer > ---

[jira] [Resolved] (AURORA-1542) Kill sequence delayed although HTTP teardown signal could not be dispatched

[ https://issues.apache.org/jira/browse/AURORA-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb resolved AURORA-1542. - Resolution: Not A Problem Talked to Andreas offline: We can close this as issue as life cycle met

[jira] [Closed] (AURORA-325) Scheduler shutdown commands should execute asynchronously

[ https://issues.apache.org/jira/browse/AURORA-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb closed AURORA-325. -- Resolution: Fixed > Scheduler shutdown commands should execute asynchronously >

[jira] [Commented] (AURORA-1599) HealthCheckerConfig should validate it has only 1 set field

[ https://issues.apache.org/jira/browse/AURORA-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496106#comment-15496106 ] Stephan Erb commented on AURORA-1599: - For reference: This is now possible since htt

[jira] [Updated] (AURORA-845) Document thermos

[ https://issues.apache.org/jira/browse/AURORA-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb updated AURORA-845: --- Issue Type: Story (was: Bug) > Document thermos > > > Key: AURORA-84

[jira] [Commented] (AURORA-1661) Scheduler leader failed to re-announce itself after ZK name was changed

[ https://issues.apache.org/jira/browse/AURORA-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496090#comment-15496090 ] Stephan Erb commented on AURORA-1661: - Given that curator has landed, I'd propose to

[jira] [Commented] (AURORA-327) Aurora shutdown blocks when attempting to abdicate leadership and zk ensemble is down

[ https://issues.apache.org/jira/browse/AURORA-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496088#comment-15496088 ] Stephan Erb commented on AURORA-327: [~jsirois] is this fixed with curator? > Aurora

[jira] [Commented] (AURORA-1274) auto create user in docker container, if user not exists

[ https://issues.apache.org/jira/browse/AURORA-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496082#comment-15496082 ] Stephan Erb commented on AURORA-1274: - For the new universal containerizer we create

[jira] [Closed] (AURORA-1140) Allow container mounts for non-docker containers (mesos filesystem isolator for example).

[ https://issues.apache.org/jira/browse/AURORA-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb closed AURORA-1140. --- Resolution: Fixed > Allow container mounts for non-docker containers (mesos filesystem isolator > fo

[jira] [Commented] (AURORA-1140) Allow container mounts for non-docker containers (mesos filesystem isolator for example).

[ https://issues.apache.org/jira/browse/AURORA-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496071#comment-15496071 ] Stephan Erb commented on AURORA-1140: - I have raised this issue originally and I am O

[jira] [Closed] (AURORA-866) Autogenerate TOC for documentation pages

[ https://issues.apache.org/jira/browse/AURORA-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb closed AURORA-866. -- Resolution: Works for Me I don't think this is really necessary any more given that I have splitted our

[jira] [Commented] (AURORA-1061) Scheduler cluster deadlock during leader election if zookeeper connectivity is interrupted

[ https://issues.apache.org/jira/browse/AURORA-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496042#comment-15496042 ] Stephan Erb commented on AURORA-1061: - [~jsirois] now that we are running on curator,

[jira] [Resolved] (AURORA-1434) Update Aurora Tutorial

[ https://issues.apache.org/jira/browse/AURORA-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb resolved AURORA-1434. - Resolution: Fixed This issue has been resolved some time ago. Apparently we forgot to close the

[jira] [Closed] (AURORA-526) UI flashes incomplete content

[ https://issues.apache.org/jira/browse/AURORA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb closed AURORA-526. -- Resolution: Fixed I haven't seen any problems since the last bunch of changes (see previous message). P

[jira] [Commented] (AURORA-1632) Investigate executor fixes when Mesos 0.30.0 stops passing along environment variables

[ https://issues.apache.org/jira/browse/AURORA-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495866#comment-15495866 ] Stephan Erb commented on AURORA-1632: - Does 0.30 correspond to Mesos 1.1 or Mesos 2.0