[jira] [Commented] (MESOS-2830) Add an endpoint to slaves to allow launching system administration tasks
[ https://issues.apache.org/jira/browse/MESOS-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011481#comment-15011481 ] John Pampuch commented on MESOS-2830: - Is there a ticket for the "external module" approach? > Add an endpoint to slaves to allow launching system administration tasks > > > Key: MESOS-2830 > URL: https://issues.apache.org/jira/browse/MESOS-2830 > Project: Mesos > Issue Type: Wish > Components: slave >Reporter: Cody Maloney >Assignee: Marco Massenzio >Priority: Minor > Labels: mesosphere > Attachments: Screen Shot 2015-07-10 at 2.52.52 PM.png, Screen Shot > 2015-07-10 at 2.58.34 PM.png, Screen Shot 2015-07-10 at 3.09.12 PM.png > > > As a System Administrator often times I need to run a organization-mandated > task on every machine in the cluster. Ideally I could do this within the > framework of mesos resources if it is a "cleanup" or auditing task, but > sometimes I just have to run something, and run it now, regardless if a > machine has un-accounted resources (Ex: Adding/removing a user). > Currently to do this I have to completely bypass Mesos and SSH to the box. > Ideally I could tell a mesos slave (With proper authentication) to run a > container with the limited special permissions needed to get the task done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2582) Create optional release step: update PyPi repositories
[ https://issues.apache.org/jira/browse/MESOS-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Pampuch updated MESOS-2582: Sprint: Mesosphere Q1 Sprint 7 - 4/17 (was: Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q1 Sprint 8 - 5/1) > Create optional release step: update PyPi repositories > -- > > Key: MESOS-2582 > URL: https://issues.apache.org/jira/browse/MESOS-2582 > Project: Mesos > Issue Type: Documentation >Reporter: Niklas Quarfot Nielsen > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2413) Create user doc for task labels
[ https://issues.apache.org/jira/browse/MESOS-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Pampuch updated MESOS-2413: Sprint: Mesosphere Q1 Sprint 7 - 4/17 (was: Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q1 Sprint 8 - 5/1) > Create user doc for task labels > --- > > Key: MESOS-2413 > URL: https://issues.apache.org/jira/browse/MESOS-2413 > Project: Mesos > Issue Type: Documentation >Reporter: Niklas Quarfot Nielsen >Priority: Trivial > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-905) Remove Framework.id in favor of FrameworkInfo.id
[ https://issues.apache.org/jira/browse/MESOS-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Pampuch updated MESOS-905: --- Sprint: Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17 (was: Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q1 Sprint 8 - 5/1) > Remove Framework.id in favor of FrameworkInfo.id > > > Key: MESOS-905 > URL: https://issues.apache.org/jira/browse/MESOS-905 > Project: Mesos > Issue Type: Improvement > Components: framework >Reporter: Adam B >Assignee: Kapil Arya > > Framework.id currently holds the correct FrameworkId, but Framework also > contains a FrameworkInfo, and the FrameworkInfo.id is not necessarily set. > I propose that we eliminate the Framework.id member variable and replace it > with a Framework.id() accessor that references Framework.FrameworkInfo.id and > ensure that it is correctly set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2500) Doxygen setup for libprocess
[ https://issues.apache.org/jira/browse/MESOS-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Pampuch updated MESOS-2500: Sprint: Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17 (was: Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q1 Sprint 8 - 5/1) > Doxygen setup for libprocess > > > Key: MESOS-2500 > URL: https://issues.apache.org/jira/browse/MESOS-2500 > Project: Mesos > Issue Type: Documentation > Components: libprocess >Reporter: Bernd Mathiske >Assignee: Joerg Schad > Original Estimate: 48h > Remaining Estimate: 48h > > Goals: > - Initial doxygen setup. > - Enable interested developers to generate already available doxygen content > locally in their workspace and view it. > - Form the basis for future contributions of more doxygen content. > 1. Devise a way to use Doxygen with Mesos source code. (For example, solve > this by adding optional brew/apt-get installation to the "Getting Started" > doc.) > 2. Create a make target for libprocess documentation that can be manually > triggered. > 3. Create initial library top level documentation. > 4. Enhance one header file with Doxygen. Make sure the generated output has > all necessary links to navigate from the lib to the file and back, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1806) Substituting etcd or ReplicatedLog for Zookeeper
[ https://issues.apache.org/jira/browse/MESOS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Pampuch updated MESOS-1806: Sprint: Mesosphere Sprint 4 - 1/16/15 > Substituting etcd or ReplicatedLog for Zookeeper > > > Key: MESOS-1806 > URL: https://issues.apache.org/jira/browse/MESOS-1806 > Project: Mesos > Issue Type: Task >Reporter: Ed Ropple >Assignee: Cody Maloney >Priority: Minor > >eropple: Could you also file a new JIRA for Mesos to drop ZK > in favor of etcd or ReplicatedLog? Would love to get some momentum going on > that one. > -- > Consider it filed. =) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1960) Silence symbolic link to pre-commit in bootstrap
[
https://issues.apache.org/jira/browse/MESOS-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Pampuch updated MESOS-1960:
Sprint: Mesosphere Q4 Sprint 3 - 12/7
This is complete, just getting it out of backlog and into a sprint.
> Silence symbolic link to pre-commit in bootstrap
>
>
> Key: MESOS-1960
> URL: https://issues.apache.org/jira/browse/MESOS-1960
> Project: Mesos
> Issue Type: Improvement
>Reporter: Niklas Quarfot Nielsen
>Assignee: Cody Maloney
>Priority: Trivial
> Fix For: 0.22.0
>
>
> Every time I run bootstrap, I see:
> {code}
> $ ./bootstrap
> ln: .git/hooks/pre-commit: File exists
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> ...
> {code}
> Should be pretty trivial to silence.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2124) state.json should report slave connection state
[
https://issues.apache.org/jira/browse/MESOS-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Pampuch updated MESOS-2124:
Sprint: Mesosphere Q4 Sprint 3 - 12/7
> state.json should report slave connection state
> ---
>
> Key: MESOS-2124
> URL: https://issues.apache.org/jira/browse/MESOS-2124
> Project: Mesos
> Issue Type: Bug
>Reporter: Thomas Rampelberg
>Assignee: Adam B
>Priority: Minor
> Labels: newbie
>
> Right now, Mesos is aware of whether a slave is activated or deactivated.
> Unfortunately, this only shows as a count in state.json. I would like to see
> a boolean on each slave in the list mentioning whether it is activated or not.
> Here's a snippet from state.json as it stands today:
> "slaves": [
> {
> "attributes": {},
> "hostname": "ubuntu-14.04-amd64-vmwarefusion",
> "id": "20141118-205755-16842879-5050-1617-0",
> "pid": "slave(1)@127.0.1.1:5051",
> "registered_time": 1416344284.37949,
> "resources": {
> "cpus": 2,
> "disk": 32297,
> "mem": 496,
> "ports": "[31000-32000]"
> }
> }
> ]
> I would like it to look like this:
> "slaves": [
> {
> "attributes": {},
> "activated": true,
> "hostname": "ubuntu-14.04-amd64-vmwarefusion",
> "id": "20141118-205755-16842879-5050-1617-0",
> "pid": "slave(1)@127.0.1.1:5051",
> "registered_time": 1416344284.37949,
> "resources": {
> "cpus": 2,
> "disk": 32297,
> "mem": 496,
> "ports": "[31000-32000]"
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2124) state.json should report slave connection state
[
https://issues.apache.org/jira/browse/MESOS-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Pampuch updated MESOS-2124:
Assignee: Adam B
> state.json should report slave connection state
> ---
>
> Key: MESOS-2124
> URL: https://issues.apache.org/jira/browse/MESOS-2124
> Project: Mesos
> Issue Type: Bug
>Reporter: Thomas Rampelberg
>Assignee: Adam B
>Priority: Minor
> Labels: newbie
>
> Right now, Mesos is aware of whether a slave is activated or deactivated.
> Unfortunately, this only shows as a count in state.json. I would like to see
> a boolean on each slave in the list mentioning whether it is activated or not.
> Here's a snippet from state.json as it stands today:
> "slaves": [
> {
> "attributes": {},
> "hostname": "ubuntu-14.04-amd64-vmwarefusion",
> "id": "20141118-205755-16842879-5050-1617-0",
> "pid": "slave(1)@127.0.1.1:5051",
> "registered_time": 1416344284.37949,
> "resources": {
> "cpus": 2,
> "disk": 32297,
> "mem": 496,
> "ports": "[31000-32000]"
> }
> }
> ]
> I would like it to look like this:
> "slaves": [
> {
> "attributes": {},
> "activated": true,
> "hostname": "ubuntu-14.04-amd64-vmwarefusion",
> "id": "20141118-205755-16842879-5050-1617-0",
> "pid": "slave(1)@127.0.1.1:5051",
> "registered_time": 1416344284.37949,
> "resources": {
> "cpus": 2,
> "disk": 32297,
> "mem": 496,
> "ports": "[31000-32000]"
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-1291) Use clang-format to automatically format code to style
[ https://issues.apache.org/jira/browse/MESOS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Pampuch updated MESOS-1291: Sprint: Mesosphere Q4 Sprint 2 - 11/14 > Use clang-format to automatically format code to style > -- > > Key: MESOS-1291 > URL: https://issues.apache.org/jira/browse/MESOS-1291 > Project: Mesos > Issue Type: Improvement > Components: technical debt >Reporter: Dominic Hamon >Assignee: Michael Park > Labels: style > > Instead of relying on a script to check and report style errors, we should > move to a workflow that allows people to write code how they feel comfortable > and then automatically format it to conform to our style guide. > The Chromium style from clang-format > (http://clang.llvm.org/docs/ClangFormat.html) is very close to our style > except for the dropped braces on class, struct, and function definitions, and > two lines of whitespace between method definitions outside a class. As such, > we should consider adopting clang-format and patching it to include a Mesos > style variant. > It can be run as part of post-reviews or as a git commit hook, or manually > from within editors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
