[jira] [Commented] (MESOS-3011) Publish release documentation for major releases on website
[ https://issues.apache.org/jira/browse/MESOS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998975#comment-15998975 ] Tim Anderegg commented on MESOS-3011: - [~haosdent] [~neilc] Sorry again for the delay, but I believe all issues have been addressed here. Let me know if anything else is needed, and I'll address in a much shorter time frame! > Publish release documentation for major releases on website > --- > > Key: MESOS-3011 > URL: https://issues.apache.org/jira/browse/MESOS-3011 > Project: Mesos > Issue Type: Documentation > Components: documentation, project website >Reporter: Paul Brett >Assignee: Tim Anderegg > Labels: documentation, mesosphere > > Currently, the website only provides a single version of the documentation. > We should publish documentation for each release on the website independently > (for example as https://mesos.apache.org/documentation/0.22/index.html, > https://mesos.apache.org/documentation/0.23/index.html) and make latest > redirect to the current version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MESOS-3011) Publish release documentation for major releases on website
[ https://issues.apache.org/jira/browse/MESOS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15770649#comment-15770649 ] Tim Anderegg commented on MESOS-3011: - [~haosd...@gmail.com] [~vinodkone] Sorry for the delay in this, but I believe the patch is fully ready for merge, if you have a minute to give it another look. Thanks! https://reviews.apache.org/r/52064/ > Publish release documentation for major releases on website > --- > > Key: MESOS-3011 > URL: https://issues.apache.org/jira/browse/MESOS-3011 > Project: Mesos > Issue Type: Documentation > Components: documentation, project website >Reporter: Paul Brett >Assignee: Tim Anderegg > Labels: documentation, mesosphere > > Currently, the website only provides a single version of the documentation. > We should publish documentation for each release on the website independently > (for example as https://mesos.apache.org/documentation/0.22/index.html, > https://mesos.apache.org/documentation/0.23/index.html) and make latest > redirect to the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-907) Add Kerberos Authentication support
[ https://issues.apache.org/jira/browse/MESOS-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743234#comment-15743234 ] Tim Anderegg commented on MESOS-907: This was something I have had on the back burner for a while, but perhaps it does make sense to leave it as a separate module. Even if it starts out that way, it could always be integrated later if the Mesos core team desires. > Add Kerberos Authentication support > --- > > Key: MESOS-907 > URL: https://issues.apache.org/jira/browse/MESOS-907 > Project: Mesos > Issue Type: Story > Components: general >Reporter: Adam B >Assignee: Tim Anderegg > Labels: security, twitter > > MESOS-704 added basic authentication support using CRAM-MD5 through SASL. Now > we should integrate Kerberos authentication using GSS-API, which is already > supported by SASL. Kerberos is a widely-used industry standard authentication > service, and integration with Mesos will make it easier for customers to > integrate their existing security process with Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3011) Publish release documentation for major releases on website
[ https://issues.apache.org/jira/browse/MESOS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530079#comment-15530079 ] Tim Anderegg commented on MESOS-3011: - Thanks [~haosdent], I left some responses and will update the patch soon. > Publish release documentation for major releases on website > --- > > Key: MESOS-3011 > URL: https://issues.apache.org/jira/browse/MESOS-3011 > Project: Mesos > Issue Type: Documentation > Components: documentation, project website >Reporter: Paul Brett >Assignee: Tim Anderegg > Labels: documentation, mesosphere > > Currently, the website only provides a single version of the documentation. > We should publish documentation for each release on the website independently > (for example as https://mesos.apache.org/documentation/0.22/index.html, > https://mesos.apache.org/documentation/0.23/index.html) and make latest > redirect to the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3011) Publish release documentation for major releases on website
[ https://issues.apache.org/jira/browse/MESOS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504572#comment-15504572 ] Tim Anderegg commented on MESOS-3011: - Whoops, fixed :) Thanks! > Publish release documentation for major releases on website > --- > > Key: MESOS-3011 > URL: https://issues.apache.org/jira/browse/MESOS-3011 > Project: Mesos > Issue Type: Documentation > Components: documentation, project website >Reporter: Paul Brett >Assignee: Tim Anderegg > Labels: documentation, mesosphere > > Currently, the website only provides a single version of the documentation. > We should publish documentation for each release on the website independently > (for example as https://mesos.apache.org/documentation/0.22/index.html, > https://mesos.apache.org/documentation/0.23/index.html) and make latest > redirect to the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3011) Publish release documentation for major releases on website
[ https://issues.apache.org/jira/browse/MESOS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504544#comment-15504544 ] Tim Anderegg commented on MESOS-3011: - [~vinodkone] Sorry this took so long, if you remember you offered to shepherd this change a whlie back, here's the review: https://reviews.apache.org/r/52064/ Let me know if you have any questions! > Publish release documentation for major releases on website > --- > > Key: MESOS-3011 > URL: https://issues.apache.org/jira/browse/MESOS-3011 > Project: Mesos > Issue Type: Documentation > Components: documentation, project website >Reporter: Paul Brett >Assignee: Tim Anderegg > Labels: documentation, mesosphere > > Currently, the website only provides a single version of the documentation. > We should publish documentation for each release on the website independently > (for example as https://mesos.apache.org/documentation/0.22/index.html, > https://mesos.apache.org/documentation/0.23/index.html) and make latest > redirect to the current version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3402) mesos-execute does not support credentials
[ https://issues.apache.org/jira/browse/MESOS-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251106#comment-15251106 ] Tim Anderegg commented on MESOS-3402: - Patch draft completed, awaiting review: https://reviews.apache.org/r/46469/ > mesos-execute does not support credentials > -- > > Key: MESOS-3402 > URL: https://issues.apache.org/jira/browse/MESOS-3402 > Project: Mesos > Issue Type: Bug >Reporter: Evan Krall >Assignee: Tim Anderegg > > mesos-execute does not appear to support passing credentials. This makes it > impossible to use on a cluster where framework authentication is required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5148) Supporting Container Images in Mesos Containerizer doesn't work by using marathon api
[
https://issues.apache.org/jira/browse/MESOS-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234197#comment-15234197
]
Tim Anderegg commented on MESOS-5148:
-
[~wangqun] Sorry, I misled you since I thought Marathon did support the recent
updates to the Mesos containerzier (i.e. support for Docker images), as
[~kaysoky] points out it doesn't. The Marathon API theoretically supports
something like this, but the implementation isn't there.
> Supporting Container Images in Mesos Containerizer doesn't work by using
> marathon api
> -
>
> Key: MESOS-5148
> URL: https://issues.apache.org/jira/browse/MESOS-5148
> Project: Mesos
> Issue Type: Bug
>Reporter: wangqun
>
> Hi
> I use the marathon api to create tasks to test Supporting Container
> Images in Mesos Containerizer .
> My steps is the following:
> 1) to run the process in master node.
> sudo /usr/sbin/mesos-master --zk=zk://10.0.0.4:2181/mesos --port=5050
> --log_dir=/var/log/mesos --cluster=mesosbay --hostname=10.0.0.4 --ip=10.0.0.4
> --quorum=1 --work_dir=/var/lib/mesos
> 2) to run the process in slave node.
> sudo /usr/sbin/mesos-slave --master=zk://10.0.0.4:2181/mesos
> --log_dir=/var/log/mesos --containerizers=docker,mesos
> --executor_registration_timeout=5mins --hostname=10.0.0.5 --ip=10.0.0.5
> --isolation=docker/runtime,filesystem/linux --work_dir=/tmp/mesos/slave
> --image_providers=docker --executor_environment_variables="{}"
> 3) to create one json file to specify the container to be managed by mesos.
> sudo touch mesos.json
> sudo vim mesos.json
> {
> "container": {
> "type": "MESOS",
> "docker": {
> "image": "library/redis"
> }
> },
> "id": "ubuntumesos",
> "instances": 1,
> "cpus": 0.5,
> "mem": 512,
> "uris": [],
> "cmd": "ping 8.8.8.8"
> }
> 4)sudo curl -X POST -H "Content-Type: application/json"
> localhost:8080/v2/apps -d...@mesos.json
> 5)sudo curl http://localhost:8080/v2/tasks
> {"tasks":[{"id":"ubuntumesos.fc1879be-fc9f-11e5-81e0-024294de4967","host":"10.0.0.5","ipAddresses":[],"ports":[31597],"startedAt":"2016-04-07T09:06:24.900Z","stagedAt":"2016-04-07T09:06:16.611Z","version":"2016-04-07T09:06:14.354Z","slaveId":"058fb5a7-9273-4bfa-83bb-8cb091621e19-S1","appId":"/ubuntumesos","servicePorts":[1]}]}
> 6) sudo docker run -ti --net=host redis redis-cli
> Could not connect to Redis at 127.0.0.1:6379: Connection refused
> not connected>
> 7)
> I0409 01:43:48.774868 3492 slave.cpp:3886] Executor
> 'ubuntumesos.a0b45838-fdf0-11e5-8b4b-0242e2dedfce' of framework
> ffb72d7c-dd63-4c30-abea-bb746ab2c326- exited with status 0
> I0409 01:43:48.781307 3492 slave.cpp:3990] Cleaning up executor
> 'ubuntumesos.a0b45838-fdf0-11e5-8b4b-0242e2dedfce' of framework
> ffb72d7c-dd63-4c30-abea-bb746ab2c326- at executor(1)@10.0.0.5:60134
> I0409 01:43:48.808364 3492 slave.cpp:4078] Cleaning up framework
> ffb72d7c-dd63-4c30-abea-bb746ab2c326-
> I0409 01:43:48.811336 3493 gc.cpp:55] Scheduling
> '/tmp/mesos/slave/slaves/da0e09ff-d5b2-4680-bd7e-b58a2a206497-S0/frameworks/ffb72d7c-dd63-4c30-abea-bb746ab2c326-/executors/ubuntumesos.a0b45838-fdf0-11e5-8b4b-0242e2dedfce/runs/24d0872d-1ba1-4384-be11-a20c82893ea4'
> for gc 6.9070953778days in the future
> I0409 01:43:48.817401 3493 gc.cpp:55] Scheduling
> '/tmp/mesos/slave/slaves/da0e09ff-d5b2-4680-bd7e-b58a2a206497-S0/frameworks/ffb72d7c-dd63-4c30-abea-bb746ab2c326-/executors/ubuntumesos.a0b45838-fdf0-11e5-8b4b-0242e2dedfce'
> for gc 6.9065992889days in the future
> I0409 01:43:48.823158 3493 gc.cpp:55] Scheduling
> '/tmp/mesos/slave/meta/slaves/da0e09ff-d5b2-4680-bd7e-b58a2a206497-S0/frameworks/ffb72d7c-dd63-4c30-abea-bb746ab2c326-/executors/ubuntumesos.a0b45838-fdf0-11e5-8b4b-0242e2dedfce/runs/24d0872d-1ba1-4384-be11-a20c82893ea4'
> for gc 6.9065273185days in the future
> I0409 01:43:48.826216 3491 status_update_manager.cpp:282] Closing status
> update streams for framework ffb72d7c-dd63-4c30-abea-bb746ab2c326-
> I0409 01:43:48.835602 3493 gc.cpp:55] Scheduling
> '/tmp/mesos/slave/meta/slaves/da0e09ff-d5b2-4680-bd7e-b58a2a206497-S0/frameworks/ffb72d7c-dd63-4c30-abea-bb746ab2c326-/executors/ubuntumesos.a0b45838-fdf0-11e5-8b4b-0242e2dedfce'
> for gc 6.9064716444days in the future
> I0409 01:43:48.838580 3493 gc.cpp:55] Scheduling
> '/tmp/mesos/slave/slaves/da0e09ff-d5b2-4680-bd7e-b58a2a206497-S0/frameworks/ffb72d7c-dd63-4c30-abea-bb746ab2c326-'
> for gc 6.9041064889days in the future
> I0409 01:43:48.844699 3493 gc.cpp:55] Scheduling
> '/tmp/mesos/slave/meta/slaves/da0e09ff-d5b2-4680-bd7e-b58a2a206497-S0/frameworks/ffb72d7c-dd63-4c30-abea-bb746ab2c326-'
> for gc 6.902654163days in the future
> I0409 01:44:01.623440 3494 slave.cpp:4374] Current disk
[jira] [Commented] (MESOS-3402) mesos-execute does not support credentials
[ https://issues.apache.org/jira/browse/MESOS-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232567#comment-15232567 ] Tim Anderegg commented on MESOS-3402: - [~anandmazumdar] Ah, I should have looked into that first :) I'll watch MESOS-3923 and work on this once that is merged, thanks! > mesos-execute does not support credentials > -- > > Key: MESOS-3402 > URL: https://issues.apache.org/jira/browse/MESOS-3402 > Project: Mesos > Issue Type: Bug >Reporter: Evan Krall >Assignee: Tim Anderegg > > mesos-execute does not appear to support passing credentials. This makes it > impossible to use on a cluster where framework authentication is required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5148) Supporting Container Images in Mesos Containerizer doesn't work by using marathon api
[
https://issues.apache.org/jira/browse/MESOS-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232554#comment-15232554
]
Tim Anderegg commented on MESOS-5148:
-
According to the Marathon API docs
(https://mesosphere.github.io/marathon/docs/generated/api.html) there is no
"mesos" key in the "container" object. So if you specify "type": "MESOS", I
believe you would still need to use the "docker" key to set your container
image settings. The "type" parameter specifies which containerizer to use, not
necessarily which container image type to use. "appc" would be the other
container image type, but is not yet supported by Marathon.
> Supporting Container Images in Mesos Containerizer doesn't work by using
> marathon api
> -
>
> Key: MESOS-5148
> URL: https://issues.apache.org/jira/browse/MESOS-5148
> Project: Mesos
> Issue Type: Bug
>Reporter: wangqun
>
> Hi
> I use the marathon api to create tasks to test Supporting Container
> Images in Mesos Containerizer .
> My steps is the following:
> 1) to run the process in master node.
> sudo /usr/sbin/mesos-master --zk=zk://10.0.0.4:2181/mesos --port=5050
> --log_dir=/var/log/mesos --cluster=mesosbay --hostname=10.0.0.4 --ip=10.0.0.4
> --quorum=1 --work_dir=/var/lib/mesos
> 2) to run the process in slave node.
> sudo /usr/sbin/mesos-slave --master=zk://10.0.0.4:2181/mesos
> --log_dir=/var/log/mesos --containerizers=docker,mesos
> --executor_registration_timeout=5mins --hostname=10.0.0.5 --ip=10.0.0.5
> --isolation=docker/runtime,filesystem/linux --work_dir=/tmp/mesos/slave
> --image_providers=docker --executor_environment_variables="{}"
> 3) to create one json file to specify the container to be managed by mesos.
> sudo touch mesos.json
> sudo vim mesos.json
> {
> "container": {
> "type": "MESOS",
> "mesos": {
> "image": "library/redis"
> }
> },
> "id": "ubuntumesos",
> "instances": 1,
> "cpus": 0.5,
> "mem": 512,
> "uris": [],
> "cmd": "ping 8.8.8.8"
> }
> 4)sudo curl -X POST -H "Content-Type: application/json"
> localhost:8080/v2/apps -d...@mesos.json
> 5)sudo curl http://localhost:8080/v2/tasks
> {"tasks":[{"id":"ubuntumesos.fc1879be-fc9f-11e5-81e0-024294de4967","host":"10.0.0.5","ipAddresses":[],"ports":[31597],"startedAt":"2016-04-07T09:06:24.900Z","stagedAt":"2016-04-07T09:06:16.611Z","version":"2016-04-07T09:06:14.354Z","slaveId":"058fb5a7-9273-4bfa-83bb-8cb091621e19-S1","appId":"/ubuntumesos","servicePorts":[1]}]}
> 6) sudo docker run -ti --net=host redis redis-cli
> Could not connect to Redis at 127.0.0.1:6379: Connection refused
> not connected>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3402) mesos-execute does not support credentials
[ https://issues.apache.org/jira/browse/MESOS-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232510#comment-15232510 ] Tim Anderegg commented on MESOS-3402: - I'd like to take this one on, if no one else is interested, since I've been using mesos-execute to test out the new appc functionality. In addition to generally supporting credentials, I was going to add a "user" flag to specify which user to run as, in order to properly test authorization and containers that have predefined users as well. I can create a separate issue for that if folks consider it to be out of the scope of this issue. > mesos-execute does not support credentials > -- > > Key: MESOS-3402 > URL: https://issues.apache.org/jira/browse/MESOS-3402 > Project: Mesos > Issue Type: Bug >Reporter: Evan Krall >Assignee: Tim Anderegg > > mesos-execute does not appear to support passing credentials. This makes it > impossible to use on a cluster where framework authentication is required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1934) Tasks created with mesos-execute disappear from task list at termination
[ https://issues.apache.org/jira/browse/MESOS-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232488#comment-15232488 ] Tim Anderegg commented on MESOS-1934: - FWIW, I ran into this issue too but once I figured out the method Adam described, that worked fine for me, so I'd +1 closing this. > Tasks created with mesos-execute disappear from task list at termination > > > Key: MESOS-1934 > URL: https://issues.apache.org/jira/browse/MESOS-1934 > Project: Mesos > Issue Type: Bug > Components: cli >Affects Versions: 0.20.1 > Environment: Linux 3.13.0-34-generic kernel, Ubuntu 14.04 >Reporter: Ben Hardy >Priority: Minor > > We are noticing that when tasks created with mesos-execute terminate, either > normally or abnormally, the task disappears from the task list. They do not > appear in the "Completed" section as you would expect, or anywhere else in > the page. > This makes problem diagnosis a bit inconvenient since one has to go digging > around in the logs on slave nodes to find out what went wrong, rather than > just being able to look at logs in the UI as you can with tasks submitted by > Singularity or Marathon. > Not a big deal but would be a nice time saver, and make things more > consistent. > Thanks, > B -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3402) mesos-execute does not support credentials
[ https://issues.apache.org/jira/browse/MESOS-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Anderegg reassigned MESOS-3402: --- Assignee: Tim Anderegg > mesos-execute does not support credentials > -- > > Key: MESOS-3402 > URL: https://issues.apache.org/jira/browse/MESOS-3402 > Project: Mesos > Issue Type: Bug >Reporter: Evan Krall >Assignee: Tim Anderegg > > mesos-execute does not appear to support passing credentials. This makes it > impossible to use on a cluster where framework authentication is required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-907) Add Kerberos Authentication support
[ https://issues.apache.org/jira/browse/MESOS-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15219094#comment-15219094 ] Tim Anderegg commented on MESOS-907: Not yet, I've been distracted by other things, however I do intend to refocus on this soon. Partly I've been waiting for the new HTTP API implementation to make some progress, which it has. Are you interested in working on it? > Add Kerberos Authentication support > --- > > Key: MESOS-907 > URL: https://issues.apache.org/jira/browse/MESOS-907 > Project: Mesos > Issue Type: Story > Components: general >Reporter: Adam B >Assignee: Tim Anderegg > Labels: security, twitter > > MESOS-704 added basic authentication support using CRAM-MD5 through SASL. Now > we should integrate Kerberos authentication using GSS-API, which is already > supported by SASL. Kerberos is a widely-used industry standard authentication > service, and integration with Mesos will make it easier for customers to > integrate their existing security process with Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-907) Add Kerberos Authentication support
[ https://issues.apache.org/jira/browse/MESOS-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697198#comment-14697198 ] Tim Anderegg commented on MESOS-907: Hi folks - I was looking into taking a crack at this, but I'm wondering if the new (forthcoming) HTTP API and authentication system makes this no longer useful. I'm happy to work on it as a temporary feature enhancement until the new system lands though, and it might help a bit in integrating GSSAPI into HTTP auth down the road if there's some working code to use as reference. Any thoughts? Thanks! Add Kerberos Authentication support --- Key: MESOS-907 URL: https://issues.apache.org/jira/browse/MESOS-907 Project: Mesos Issue Type: Story Components: general Reporter: Adam B Labels: security, twitter MESOS-704 added basic authentication support using CRAM-MD5 through SASL. Now we should integrate Kerberos authentication using GSS-API, which is already supported by SASL. Kerberos is a widely-used industry standard authentication service, and integration with Mesos will make it easier for customers to integrate their existing security process with Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-907) Add Kerberos Authentication support
[ https://issues.apache.org/jira/browse/MESOS-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697569#comment-14697569 ] Tim Anderegg commented on MESOS-907: Cool, didn't realize the scheduler API was that far along. I might start with the sasl version anyways like you said, but I'll tackle HTTP soon after. Thanks Vinod! Tim Add Kerberos Authentication support --- Key: MESOS-907 URL: https://issues.apache.org/jira/browse/MESOS-907 Project: Mesos Issue Type: Story Components: general Reporter: Adam B Labels: security, twitter MESOS-704 added basic authentication support using CRAM-MD5 through SASL. Now we should integrate Kerberos authentication using GSS-API, which is already supported by SASL. Kerberos is a widely-used industry standard authentication service, and integration with Mesos will make it easier for customers to integrate their existing security process with Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-907) Add Kerberos Authentication support
[ https://issues.apache.org/jira/browse/MESOS-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Anderegg reassigned MESOS-907: -- Assignee: Tim Anderegg Add Kerberos Authentication support --- Key: MESOS-907 URL: https://issues.apache.org/jira/browse/MESOS-907 Project: Mesos Issue Type: Story Components: general Reporter: Adam B Assignee: Tim Anderegg Labels: security, twitter MESOS-704 added basic authentication support using CRAM-MD5 through SASL. Now we should integrate Kerberos authentication using GSS-API, which is already supported by SASL. Kerberos is a widely-used industry standard authentication service, and integration with Mesos will make it easier for customers to integrate their existing security process with Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1838) Add documentation for Authentication
[ https://issues.apache.org/jira/browse/MESOS-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680759#comment-14680759 ] Tim Anderegg commented on MESOS-1838: - Hello, I submitted a patch to the Review Board here: https://reviews.apache.org/r/37315/, thanks in advance to anyone who has the time to review my documentation. Add documentation for Authentication Key: MESOS-1838 URL: https://issues.apache.org/jira/browse/MESOS-1838 Project: Mesos Issue Type: Documentation Components: documentation Reporter: Vinod Kone Assignee: Tim Anderegg We need some documentation about how to enable framework and slave authentication. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-1838) Add documentation for Authentication
[ https://issues.apache.org/jira/browse/MESOS-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Anderegg reassigned MESOS-1838: --- Assignee: Tim Anderegg Add documentation for Authentication Key: MESOS-1838 URL: https://issues.apache.org/jira/browse/MESOS-1838 Project: Mesos Issue Type: Documentation Components: documentation Reporter: Vinod Kone Assignee: Tim Anderegg We need some documentation about how to enable framework and slave authentication. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
