[jira] [Commented] (MESOS-4440) Clean get/post/deleteRequest func and let the caller to use the general funcion.
[ https://issues.apache.org/jira/browse/MESOS-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15595073#comment-15595073 ] Yongqiao Wang commented on MESOS-4440: -- Thanks [~adam-mesos], I will fix your comments ASAP. > Clean get/post/deleteRequest func and let the caller to use the general > funcion. > > > Key: MESOS-4440 > URL: https://issues.apache.org/jira/browse/MESOS-4440 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: tech-debt > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4440) Clean get/post/deleteRequest func and let the caller to use the general funcion.
[ https://issues.apache.org/jira/browse/MESOS-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448166#comment-15448166 ] Yongqiao Wang commented on MESOS-4440: -- Append the related RR to clean up the http::internal::get function: https://reviews.apache.org/r/51493/ https://reviews.apache.org/r/51495/ https://reviews.apache.org/r/51505/ https://reviews.apache.org/r/51508/ > Clean get/post/deleteRequest func and let the caller to use the general > funcion. > > > Key: MESOS-4440 > URL: https://issues.apache.org/jira/browse/MESOS-4440 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: tech-debt > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4440) Clean get/post/deleteRequest func and let the caller to use the general funcion.
[ https://issues.apache.org/jira/browse/MESOS-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411362#comment-15411362 ] Yongqiao Wang commented on MESOS-4440: -- [~adam-mesos] I plan to clean up the code described in this ticket, do you have time and give me a review? I will submit patches later. > Clean get/post/deleteRequest func and let the caller to use the general > funcion. > > > Key: MESOS-4440 > URL: https://issues.apache.org/jira/browse/MESOS-4440 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: tech-debt > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5335) Add authorization to GET /weights
[ https://issues.apache.org/jira/browse/MESOS-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-5335: - Assignee: (was: Yongqiao Wang) > Add authorization to GET /weights > - > > Key: MESOS-5335 > URL: https://issues.apache.org/jira/browse/MESOS-5335 > Project: Mesos > Issue Type: Improvement > Components: master, security >Reporter: Adam B > Labels: mesosphere, security > Fix For: 0.29.0 > > > We already authorize which http users can update weights for particular > roles, but even knowing of the existence of these roles (let alone their > weights) may be sensitive information. We should add authz around GET > operations on /weights. > Easy option: GET_ENDPOINT_WITH_PATH /weights > - Pro: No new verb > - Con: All or nothing > Complex option: GET_WEIGHTS_WITH_ROLE > - Pro: Filters contents based on roles the user is authorized to see > - Con: More authorize calls (one per role in each /weights request) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5335) Add authorization to GET /weights
[ https://issues.apache.org/jira/browse/MESOS-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-5335: Assignee: Yongqiao Wang > Add authorization to GET /weights > - > > Key: MESOS-5335 > URL: https://issues.apache.org/jira/browse/MESOS-5335 > Project: Mesos > Issue Type: Improvement > Components: master, security >Reporter: Adam B >Assignee: Yongqiao Wang > Labels: mesosphere, security > Fix For: 0.29.0 > > > We already authorize which http users can update weights for particular > roles, but even knowing of the existence of these roles (let alone their > weights) may be sensitive information. We should add authz around GET > operations on /weights. > Easy option: GET_ENDPOINT_WITH_PATH /weights > - Pro: No new verb > - Con: All or nothing > Complex option: GET_WEIGHTS_WITH_ROLE > - Pro: Filters contents based on roles the user is authorized to see > - Con: More authorize calls (one per role in each /weights request) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4189) Dynamic weights
[ https://issues.apache.org/jira/browse/MESOS-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257262#comment-15257262 ] Yongqiao Wang commented on MESOS-4189: -- [~adam-mesos], also thanks a million for your guidance, I was very happy to work with you over the past few months. > Dynamic weights > --- > > Key: MESOS-4189 > URL: https://issues.apache.org/jira/browse/MESOS-4189 > Project: Mesos > Issue Type: Epic >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > Fix For: 0.29.0 > > > Mesos current uses a static list of weights that are configured when the > master startup(via the --weights flag), this place some limitation about > change the resource allocation priority for a role/frameworks(changing the > set of weights requires restarting all the masters). > This JIRA will add a new endpoint /weight to update/show weight of a role > with the authorized principles, and the non-default weights will be persisted > in registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4316) Support get non-default weights by /weights
[ https://issues.apache.org/jira/browse/MESOS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238672#comment-15238672 ] Yongqiao Wang commented on MESOS-4316: -- Append the RR for positive tests: https://reviews.apache.org/r/46139/ > Support get non-default weights by /weights > --- > > Key: MESOS-4316 > URL: https://issues.apache.org/jira/browse/MESOS-4316 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: mesosphere > Fix For: 0.29.0 > > > Like /quota, we should also add query logic for /weights to keep consistent. > Then /roles no longer needs to show weight information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5146) MasterAllocatorTest/1.RebalancedForUpdatedWeights is flaky
[
https://issues.apache.org/jira/browse/MESOS-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238522#comment-15238522
]
Yongqiao Wang commented on MESOS-5146:
--
Append the RR: https://reviews.apache.org/r/46135/
> MasterAllocatorTest/1.RebalancedForUpdatedWeights is flaky
> --
>
> Key: MESOS-5146
> URL: https://issues.apache.org/jira/browse/MESOS-5146
> Project: Mesos
> Issue Type: Bug
> Components: allocation, tests
>Affects Versions: 0.28.0
> Environment: Ubuntu 14.04 using clang, without libevent or SSL
>Reporter: Greg Mann
>Assignee: Yongqiao Wang
> Labels: mesosphere
> Fix For: 0.29.0
>
>
> Observed on the ASF CI:
> {code}
> [ RUN ] MasterAllocatorTest/1.RebalancedForUpdatedWeights
> I0407 22:34:10.330394 29278 cluster.cpp:149] Creating default 'local'
> authorizer
> I0407 22:34:10.466182 29278 leveldb.cpp:174] Opened db in 135.608207ms
> I0407 22:34:10.516398 29278 leveldb.cpp:181] Compacted db in 50.159558ms
> I0407 22:34:10.516464 29278 leveldb.cpp:196] Created db iterator in 34959ns
> I0407 22:34:10.516484 29278 leveldb.cpp:202] Seeked to beginning of db in
> 10195ns
> I0407 22:34:10.516496 29278 leveldb.cpp:271] Iterated through 0 keys in the
> db in 7324ns
> I0407 22:34:10.516547 29278 replica.cpp:779] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0407 22:34:10.517277 29298 recover.cpp:447] Starting replica recovery
> I0407 22:34:10.517693 29300 recover.cpp:473] Replica is in EMPTY status
> I0407 22:34:10.520251 29310 replica.cpp:673] Replica in EMPTY status received
> a broadcasted recover request from (4775)@172.17.0.3:35855
> I0407 22:34:10.520611 29311 recover.cpp:193] Received a recover response from
> a replica in EMPTY status
> I0407 22:34:10.521164 29299 recover.cpp:564] Updating replica status to
> STARTING
> I0407 22:34:10.523435 29298 master.cpp:382] Master
> f59f9057-a5c7-43e1-b129-96862e640a12 (129e11060069) started on
> 172.17.0.3:35855
> I0407 22:34:10.523473 29298 master.cpp:384] Flags at startup: --acls=""
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="true" --authenticate_http="true" --authenticate_slaves="true"
> --authenticators="crammd5" --authorizers="local"
> --credentials="/tmp/3rZY8C/credentials" --framework_sorter="drf"
> --help="false" --hostname_lookup="true" --http_authenticators="basic"
> --initialize_driver_logging="true" --log_auto_initialize="true"
> --logbufsecs="0" --logging_level="INFO" --max_completed_frameworks="50"
> --max_completed_tasks_per_framework="1000" --max_slave_ping_timeouts="5"
> --quiet="false" --recovery_slave_removal_limit="100%"
> --registry="replicated_log" --registry_fetch_timeout="1mins"
> --registry_store_timeout="100secs" --registry_strict="true"
> --root_submissions="true" --slave_ping_timeout="15secs"
> --slave_reregister_timeout="10mins" --user_sorter="drf" --version="false"
> --webui_dir="/mesos/mesos-0.29.0/_inst/share/mesos/webui"
> --work_dir="/tmp/3rZY8C/master" --zk_session_timeout="10secs"
> I0407 22:34:10.523885 29298 master.cpp:433] Master only allowing
> authenticated frameworks to register
> I0407 22:34:10.523901 29298 master.cpp:438] Master only allowing
> authenticated agents to register
> I0407 22:34:10.523913 29298 credentials.hpp:37] Loading credentials for
> authentication from '/tmp/3rZY8C/credentials'
> I0407 22:34:10.524298 29298 master.cpp:480] Using default 'crammd5'
> authenticator
> I0407 22:34:10.524441 29298 master.cpp:551] Using default 'basic' HTTP
> authenticator
> I0407 22:34:10.524564 29298 master.cpp:589] Authorization enabled
> I0407 22:34:10.525269 29305 hierarchical.cpp:145] Initialized hierarchical
> allocator process
> I0407 22:34:10.525333 29305 whitelist_watcher.cpp:77] No whitelist given
> I0407 22:34:10.527331 29298 master.cpp:1832] The newly elected leader is
> master@172.17.0.3:35855 with id f59f9057-a5c7-43e1-b129-96862e640a12
> I0407 22:34:10.527441 29298 master.cpp:1845] Elected as the leading master!
> I0407 22:34:10.527545 29298 master.cpp:1532] Recovering from registrar
> I0407 22:34:10.527889 29298 registrar.cpp:331] Recovering registrar
> I0407 22:34:10.549734 29299 leveldb.cpp:304] Persisting metadata (8 bytes) to
> leveldb took 28.25177ms
> I0407 22:34:10.549782 29299 replica.cpp:320] Persisted replica status to
> STARTING
> I0407 22:34:10.550010 29299 recover.cpp:473] Replica is in STARTING status
> I0407 22:34:10.551352 29299 replica.cpp:673] Replica in STARTING status
> received a broadcasted recover request from (4777)@172.17.0.3:35855
> I0407 22:34:10.551676 29299 recover.cpp:193] Received a recover response from
> a replica in STARTING status
> I0407 22:34:10.552315 29308 recover.cpp:564] Updating replica status to VOTING
[jira] [Assigned] (MESOS-5146) MasterAllocatorTest/1.RebalancedForUpdatedWeights is flaky
[
https://issues.apache.org/jira/browse/MESOS-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongqiao Wang reassigned MESOS-5146:
Assignee: Yongqiao Wang
> MasterAllocatorTest/1.RebalancedForUpdatedWeights is flaky
> --
>
> Key: MESOS-5146
> URL: https://issues.apache.org/jira/browse/MESOS-5146
> Project: Mesos
> Issue Type: Bug
> Components: allocation, tests
>Affects Versions: 0.28.0
> Environment: Ubuntu 14.04 using clang, without libevent or SSL
>Reporter: Greg Mann
>Assignee: Yongqiao Wang
> Labels: mesosphere
>
> Observed on the ASF CI:
> {code}
> [ RUN ] MasterAllocatorTest/1.RebalancedForUpdatedWeights
> I0407 22:34:10.330394 29278 cluster.cpp:149] Creating default 'local'
> authorizer
> I0407 22:34:10.466182 29278 leveldb.cpp:174] Opened db in 135.608207ms
> I0407 22:34:10.516398 29278 leveldb.cpp:181] Compacted db in 50.159558ms
> I0407 22:34:10.516464 29278 leveldb.cpp:196] Created db iterator in 34959ns
> I0407 22:34:10.516484 29278 leveldb.cpp:202] Seeked to beginning of db in
> 10195ns
> I0407 22:34:10.516496 29278 leveldb.cpp:271] Iterated through 0 keys in the
> db in 7324ns
> I0407 22:34:10.516547 29278 replica.cpp:779] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0407 22:34:10.517277 29298 recover.cpp:447] Starting replica recovery
> I0407 22:34:10.517693 29300 recover.cpp:473] Replica is in EMPTY status
> I0407 22:34:10.520251 29310 replica.cpp:673] Replica in EMPTY status received
> a broadcasted recover request from (4775)@172.17.0.3:35855
> I0407 22:34:10.520611 29311 recover.cpp:193] Received a recover response from
> a replica in EMPTY status
> I0407 22:34:10.521164 29299 recover.cpp:564] Updating replica status to
> STARTING
> I0407 22:34:10.523435 29298 master.cpp:382] Master
> f59f9057-a5c7-43e1-b129-96862e640a12 (129e11060069) started on
> 172.17.0.3:35855
> I0407 22:34:10.523473 29298 master.cpp:384] Flags at startup: --acls=""
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="true" --authenticate_http="true" --authenticate_slaves="true"
> --authenticators="crammd5" --authorizers="local"
> --credentials="/tmp/3rZY8C/credentials" --framework_sorter="drf"
> --help="false" --hostname_lookup="true" --http_authenticators="basic"
> --initialize_driver_logging="true" --log_auto_initialize="true"
> --logbufsecs="0" --logging_level="INFO" --max_completed_frameworks="50"
> --max_completed_tasks_per_framework="1000" --max_slave_ping_timeouts="5"
> --quiet="false" --recovery_slave_removal_limit="100%"
> --registry="replicated_log" --registry_fetch_timeout="1mins"
> --registry_store_timeout="100secs" --registry_strict="true"
> --root_submissions="true" --slave_ping_timeout="15secs"
> --slave_reregister_timeout="10mins" --user_sorter="drf" --version="false"
> --webui_dir="/mesos/mesos-0.29.0/_inst/share/mesos/webui"
> --work_dir="/tmp/3rZY8C/master" --zk_session_timeout="10secs"
> I0407 22:34:10.523885 29298 master.cpp:433] Master only allowing
> authenticated frameworks to register
> I0407 22:34:10.523901 29298 master.cpp:438] Master only allowing
> authenticated agents to register
> I0407 22:34:10.523913 29298 credentials.hpp:37] Loading credentials for
> authentication from '/tmp/3rZY8C/credentials'
> I0407 22:34:10.524298 29298 master.cpp:480] Using default 'crammd5'
> authenticator
> I0407 22:34:10.524441 29298 master.cpp:551] Using default 'basic' HTTP
> authenticator
> I0407 22:34:10.524564 29298 master.cpp:589] Authorization enabled
> I0407 22:34:10.525269 29305 hierarchical.cpp:145] Initialized hierarchical
> allocator process
> I0407 22:34:10.525333 29305 whitelist_watcher.cpp:77] No whitelist given
> I0407 22:34:10.527331 29298 master.cpp:1832] The newly elected leader is
> master@172.17.0.3:35855 with id f59f9057-a5c7-43e1-b129-96862e640a12
> I0407 22:34:10.527441 29298 master.cpp:1845] Elected as the leading master!
> I0407 22:34:10.527545 29298 master.cpp:1532] Recovering from registrar
> I0407 22:34:10.527889 29298 registrar.cpp:331] Recovering registrar
> I0407 22:34:10.549734 29299 leveldb.cpp:304] Persisting metadata (8 bytes) to
> leveldb took 28.25177ms
> I0407 22:34:10.549782 29299 replica.cpp:320] Persisted replica status to
> STARTING
> I0407 22:34:10.550010 29299 recover.cpp:473] Replica is in STARTING status
> I0407 22:34:10.551352 29299 replica.cpp:673] Replica in STARTING status
> received a broadcasted recover request from (4777)@172.17.0.3:35855
> I0407 22:34:10.551676 29299 recover.cpp:193] Received a recover response from
> a replica in STARTING status
> I0407 22:34:10.552315 29308 recover.cpp:564] Updating replica status to VOTING
> I0407 22:34:10.574865 29308 leveldb.cpp:304] Persisting metadata (8 bytes) to
>
[jira] [Commented] (MESOS-4316) Support get non-default weights by /weights
[ https://issues.apache.org/jira/browse/MESOS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208089#comment-15208089 ] Yongqiao Wang commented on MESOS-4316: -- Append test RR: https://reviews.apache.org/r/45203/ > Support get non-default weights by /weights > --- > > Key: MESOS-4316 > URL: https://issues.apache.org/jira/browse/MESOS-4316 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: mesosphere > > Like /quota, we should also add query logic for /weights to keep consistent. > Then /roles no longer needs to show weight information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4881) Rescind all outstanding offers after changing some weights.
[ https://issues.apache.org/jira/browse/MESOS-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208069#comment-15208069 ] Yongqiao Wang commented on MESOS-4881: -- Append the test RR: https://reviews.apache.org/r/45202/ > Rescind all outstanding offers after changing some weights. > --- > > Key: MESOS-4881 > URL: https://issues.apache.org/jira/browse/MESOS-4881 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4957) Typo in Mesos portal
[ https://issues.apache.org/jira/browse/MESOS-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197134#comment-15197134 ] Yongqiao Wang commented on MESOS-4957: -- [~adam-mesos], can you shepherd for this? > Typo in Mesos portal > > > Key: MESOS-4957 > URL: https://issues.apache.org/jira/browse/MESOS-4957 > Project: Mesos > Issue Type: Bug >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > Attachments: $3E85CFC7C5E68241.jpg > > > See the attachment for the details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4957) Typo in Mesos portal
[ https://issues.apache.org/jira/browse/MESOS-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4957: - Attachment: $3E85CFC7C5E68241.jpg > Typo in Mesos portal > > > Key: MESOS-4957 > URL: https://issues.apache.org/jira/browse/MESOS-4957 > Project: Mesos > Issue Type: Bug >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > Attachments: $3E85CFC7C5E68241.jpg > > > See the attachment for the details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4957) Typo in Mesos portal
[ https://issues.apache.org/jira/browse/MESOS-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4957: - Description: See the attachment for the detais. > Typo in Mesos portal > > > Key: MESOS-4957 > URL: https://issues.apache.org/jira/browse/MESOS-4957 > Project: Mesos > Issue Type: Bug >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > See the attachment for the detais. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4957) Typo in Mesos portal
[ https://issues.apache.org/jira/browse/MESOS-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4957: - Description: See the attachment for the details. (was: See the attachment for the detais.) > Typo in Mesos portal > > > Key: MESOS-4957 > URL: https://issues.apache.org/jira/browse/MESOS-4957 > Project: Mesos > Issue Type: Bug >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > See the attachment for the details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4957) Typo in Mesos portal
Yongqiao Wang created MESOS-4957: Summary: Typo in Mesos portal Key: MESOS-4957 URL: https://issues.apache.org/jira/browse/MESOS-4957 Project: Mesos Issue Type: Bug Reporter: Yongqiao Wang Assignee: Yongqiao Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4189) Dynamic weights
[ https://issues.apache.org/jira/browse/MESOS-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184205#comment-15184205 ] Yongqiao Wang commented on MESOS-4189: -- OK, Thanks Adam. I will follow up those tasks ASAP. Cloud you help to review the RR #41681, #41790 and #43863? and in order to reduce the conflicts, let us commit them firstly, then it will be easily to do the following tasks based on that code base. > Dynamic weights > --- > > Key: MESOS-4189 > URL: https://issues.apache.org/jira/browse/MESOS-4189 > Project: Mesos > Issue Type: Epic >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > Mesos current uses a static list of weights that are configured when the > master startup(via the --weights flag), this place some limitation about > change the resource allocation priority for a role/frameworks(changing the > set of weights requires restarting all the masters). > This JIRA will add a new endpoint /weight to update/show weight of a role > with the authorized principles, and the non-default weights will be persisted > in registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4881) Rescind all outstanding offers after changing some weights.
Yongqiao Wang created MESOS-4881: Summary: Rescind all outstanding offers after changing some weights. Key: MESOS-4881 URL: https://issues.apache.org/jira/browse/MESOS-4881 Project: Mesos Issue Type: Task Reporter: Yongqiao Wang Assignee: Yongqiao Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4316) Support get non-default weights by /weights
[ https://issues.apache.org/jira/browse/MESOS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4316: - Shepherd: Adam B > Support get non-default weights by /weights > --- > > Key: MESOS-4316 > URL: https://issues.apache.org/jira/browse/MESOS-4316 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > > Like /quota, we should also add query logic for /weights to keep consistent. > Then /roles no longer needs to show weight information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4316) Support get non-default weights by /weights
[ https://issues.apache.org/jira/browse/MESOS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182668#comment-15182668 ] Yongqiao Wang commented on MESOS-4316: -- Only add the GET for /weights in the same release as the PUT/POST. We can't change what's displayed in /roles without going through a deprecation cycle, but we can show the weights in both places for now. > Support get non-default weights by /weights > --- > > Key: MESOS-4316 > URL: https://issues.apache.org/jira/browse/MESOS-4316 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > > Like /quota, we should also add query logic for /weights to keep consistent. > Then /roles no longer needs to show weight information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4189) Dynamic weights
[ https://issues.apache.org/jira/browse/MESOS-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15179144#comment-15179144 ] Yongqiao Wang commented on MESOS-4189: -- [~adam-mesos], [~alexr], do you have time to speed up the review of the related patches? and can we release the dynamic weights feature in Mesos 0.28? > Dynamic weights > --- > > Key: MESOS-4189 > URL: https://issues.apache.org/jira/browse/MESOS-4189 > Project: Mesos > Issue Type: Epic >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > Mesos current uses a static list of weights that are configured when the > master startup(via the --weights flag), this place some limitation about > change the resource allocation priority for a role/frameworks(changing the > set of weights requires restarting all the masters). > This JIRA will add a new endpoint /weight to update/show weight of a role > with the authorized principles, and the non-default weights will be persisted > in registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4797) Add a couple of registrar tests for /weights endpoint
Yongqiao Wang created MESOS-4797: Summary: Add a couple of registrar tests for /weights endpoint Key: MESOS-4797 URL: https://issues.apache.org/jira/browse/MESOS-4797 Project: Mesos Issue Type: Task Reporter: Yongqiao Wang Assignee: Yongqiao Wang Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3945) Add operator documentation for /weight endpoint
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15149764#comment-15149764 ] Yongqiao Wang commented on MESOS-3945: -- Add a new doc for weights: https://reviews.apache.org/r/42719/ > Add operator documentation for /weight endpoint > --- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: James Wang >Assignee: Yongqiao Wang > > This JIRA ticket will update the related doc to apply to dynamic weights, and > add an new operator guide for dynamic weights which describes basic usage of > the /weights endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2646) Update Master to send revocable resources in separate offers
[ https://issues.apache.org/jira/browse/MESOS-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148270#comment-15148270 ] Yongqiao Wang commented on MESOS-2646: -- [~nnielsen] and [~vinodkone], could you help to review these patches? > Update Master to send revocable resources in separate offers > > > Key: MESOS-2646 > URL: https://issues.apache.org/jira/browse/MESOS-2646 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Yongqiao Wang > Labels: twitter > Attachments: code-diff.txt > > > Master will send separate offers for revocable and non-revocable/regular > resources. This allows master to rescind revocable offers (e.g, when a new > oversubscribed resources estimate comes from the slave) without impacting > regular offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2646) Update Master to send revocable resources in separate offers
[ https://issues.apache.org/jira/browse/MESOS-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148244#comment-15148244 ] Yongqiao Wang commented on MESOS-2646: -- Add the test: https://reviews.apache.org/r/43593/ > Update Master to send revocable resources in separate offers > > > Key: MESOS-2646 > URL: https://issues.apache.org/jira/browse/MESOS-2646 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Yongqiao Wang > Labels: twitter > Attachments: code-diff.txt > > > Master will send separate offers for revocable and non-revocable/regular > resources. This allows master to rescind revocable offers (e.g, when a new > oversubscribed resources estimate comes from the slave) without impacting > regular offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4189) Dynamic weights
[ https://issues.apache.org/jira/browse/MESOS-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148037#comment-15148037 ] Yongqiao Wang commented on MESOS-4189: -- [~hbogert], thank you in advance. Currently, the code has almost done, I am waiting for shepherd to review the related doc changes. If you are interesting in this feature, welcome you to verify it after all code committed. > Dynamic weights > --- > > Key: MESOS-4189 > URL: https://issues.apache.org/jira/browse/MESOS-4189 > Project: Mesos > Issue Type: Epic >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > Mesos current uses a static list of weights that are configured when the > master startup(via the --weights flag), this place some limitation about > change the resource allocation priority for a role/frameworks(changing the > set of weights requires restarting all the masters). > This JIRA will add a new endpoint /weight to update/show weight of a role > with the authorized principles, and the non-default weights will be persisted > in registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1719) Master should persist active frameworks information
[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148031#comment-15148031 ] Yongqiao Wang edited comment on MESOS-1719 at 2/16/16 2:48 AM: --- Thank you [~neilc] and [~kaysoky], I find that *state* object is an internal object of *RegistrarProcess*, if we want to use it directly in master.cpp to persist framework info, then we need to expose it firstly. Another question is why we should use *state abstraction* for framework info persistence? what is the benefit for it? My original idea is to use *registry* directly (Like the current implementation in above patches), then it can keep consistence with slave info persistence in master component. was (Author: gradywang): Thank you [~neilc] and [~kaysoky], I find that `state` object is an internal object of `RegistrarProcess`, if we want to use it directly in master.cpp to persist framework info, then we need to expose it firstly. Another question is why we should use 'state abstraction' for framework info persistence? what is the benefit for it? My original idea is to use `registry` directly (Like the current implementation in above patches), then it can keep consistence with slave info persistence in master component. > Master should persist active frameworks information > --- > > Key: MESOS-1719 > URL: https://issues.apache.org/jira/browse/MESOS-1719 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Vinod Kone >Assignee: Yongqiao Wang > > https://issues.apache.org/jira/browse/MESOS-1219 disallows completed > frameworks from re-registering with the same framework id, as long as the > master doesn't failover. > This ticket tracks the work for it work across the master failover using > registrar. > There are some open questions that need to be addressed: > --> Should registry contain framework ids only framework infos. > For disallowing completed frameworks from re-registering, persisting > framework ids is enough. But, if in the future, we want to disallow > frameworks from re-registering if some parts of framework info > changed then we need to persist the info too. > --> How to update the framework info. > Currently frameworks are allowed to update framework info while re- > registering, but it only takes effect on the master when the master > fails > over and on the slave when the slave fails over. How should things >change when persist framework info? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1719) Master should persist active frameworks information
[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15148031#comment-15148031 ] Yongqiao Wang commented on MESOS-1719: -- Thank you [~neilc] and [~kaysoky], I find that `state` object is an internal object of `RegistrarProcess`, if we want to use it directly in master.cpp to persist framework info, then we need to expose it firstly. Another question is why we should use 'state abstraction' for framework info persistence? what is the benefit for it? My original idea is to use `registry` directly (Like the current implementation in above patches), then it can keep consistence with slave info persistence in master component. > Master should persist active frameworks information > --- > > Key: MESOS-1719 > URL: https://issues.apache.org/jira/browse/MESOS-1719 > Project: Mesos > Issue Type: Task > Components: master >Reporter: Vinod Kone >Assignee: Yongqiao Wang > > https://issues.apache.org/jira/browse/MESOS-1219 disallows completed > frameworks from re-registering with the same framework id, as long as the > master doesn't failover. > This ticket tracks the work for it work across the master failover using > registrar. > There are some open questions that need to be addressed: > --> Should registry contain framework ids only framework infos. > For disallowing completed frameworks from re-registering, persisting > framework ids is enough. But, if in the future, we want to disallow > frameworks from re-registering if some parts of framework info > changed then we need to persist the info too. > --> How to update the framework info. > Currently frameworks are allowed to update framework info while re- > registering, but it only takes effect on the master when the master > fails > over and on the slave when the slave fails over. How should things >change when persist framework info? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1719) Master should persist active frameworks information
[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15146833#comment-15146833 ] Yongqiao Wang commented on MESOS-1719: -- [~kaysoky], Thanks for your reply. Is there some docs for "state abstraction"? I am not sure this function can address the problems referred as above of this ticket. > Master should persist active frameworks information > --- > > Key: MESOS-1719 > URL: https://issues.apache.org/jira/browse/MESOS-1719 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Yongqiao Wang > > https://issues.apache.org/jira/browse/MESOS-1219 disallows completed > frameworks from re-registering with the same framework id, as long as the > master doesn't failover. > This ticket tracks the work for it work across the master failover using > registrar. > There are some open questions that need to be addressed: > --> Should registry contain framework ids only framework infos. > For disallowing completed frameworks from re-registering, persisting > framework ids is enough. But, if in the future, we want to disallow > frameworks from re-registering if some parts of framework info > changed then we need to persist the info too. > --> How to update the framework info. > Currently frameworks are allowed to update framework info while re- > registering, but it only takes effect on the master when the master > fails > over and on the slave when the slave fails over. How should things >change when persist framework info? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2646) Update Master to send revocable resources in separate offers
[ https://issues.apache.org/jira/browse/MESOS-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126043#comment-15126043 ] Yongqiao Wang commented on MESOS-2646: -- Append the RR: https://reviews.apache.org/r/43041/ > Update Master to send revocable resources in separate offers > > > Key: MESOS-2646 > URL: https://issues.apache.org/jira/browse/MESOS-2646 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Yongqiao Wang > Labels: twitter > Attachments: code-diff.txt > > > Master will send separate offers for revocable and non-revocable/regular > resources. This allows master to rescind revocable offers (e.g, when a new > oversubscribed resources estimate comes from the slave) without impacting > regular offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3945) Add operator documentation for /weight endpoint
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-3945: Assignee: Yongqiao Wang > Add operator documentation for /weight endpoint > --- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: James Wang >Assignee: Yongqiao Wang > > This JIRA ticket will update the related doc to apply to dynamic weights, and > add an new operator guide for dynamic weights which describes basic usage of > the /weights endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3945) Add operator documentation for /weight endpoint
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114800#comment-15114800 ] Yongqiao Wang commented on MESOS-3945: -- Update docs for --weights flag and authorization: https://reviews.apache.org/r/42705/ > Add operator documentation for /weight endpoint > --- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: James Wang >Assignee: Yongqiao Wang > > This JIRA ticket will update the related doc to apply to dynamic weights, and > add an new operator guide for dynamic weights which describes basic usage of > the /weights endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1719) Master should persist active frameworks information
[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110343#comment-15110343 ] Yongqiao Wang commented on MESOS-1719: -- Patch for introducing framework registry operations: https://reviews.apache.org/r/42594/ [~bmahler], [~vinodkone], could you help to review those patches? > Master should persist active frameworks information > --- > > Key: MESOS-1719 > URL: https://issues.apache.org/jira/browse/MESOS-1719 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Yongqiao Wang > > https://issues.apache.org/jira/browse/MESOS-1219 disallows completed > frameworks from re-registering with the same framework id, as long as the > master doesn't failover. > This ticket tracks the work for it work across the master failover using > registrar. > There are some open questions that need to be addressed: > --> Should registry contain framework ids only framework infos. > For disallowing completed frameworks from re-registering, persisting > framework ids is enough. But, if in the future, we want to disallow > frameworks from re-registering if some parts of framework info > changed then we need to persist the info too. > --> How to update the framework info. > Currently frameworks are allowed to update framework info while re- > registering, but it only takes effect on the master when the master > fails > over and on the slave when the slave fails over. How should things >change when persist framework info? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1719) Master should persist active frameworks information
[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110167#comment-15110167 ] Yongqiao Wang edited comment on MESOS-1719 at 1/21/16 6:45 AM: --- Patch for adding the protobufs in registry to persist some framework informations which do not allow to change when framework re-register. https://reviews.apache.org/r/42591/ was (Author: gradywang): Patch for adding the protobufs in registry to persist some framework information which do not allowed to changed when framework re-register. https://reviews.apache.org/r/42591/ > Master should persist active frameworks information > --- > > Key: MESOS-1719 > URL: https://issues.apache.org/jira/browse/MESOS-1719 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Yongqiao Wang > > https://issues.apache.org/jira/browse/MESOS-1219 disallows completed > frameworks from re-registering with the same framework id, as long as the > master doesn't failover. > This ticket tracks the work for it work across the master failover using > registrar. > There are some open questions that need to be addressed: > --> Should registry contain framework ids only framework infos. > For disallowing completed frameworks from re-registering, persisting > framework ids is enough. But, if in the future, we want to disallow > frameworks from re-registering if some parts of framework info > changed then we need to persist the info too. > --> How to update the framework info. > Currently frameworks are allowed to update framework info while re- > registering, but it only takes effect on the master when the master > fails > over and on the slave when the slave fails over. How should things >change when persist framework info? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1719) Master should persist active frameworks information
[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110167#comment-15110167 ] Yongqiao Wang commented on MESOS-1719: -- Patch for adding the protobufs in registry to persist some framework information which do not allowed to changed when framework re-register. https://reviews.apache.org/r/42591/ > Master should persist active frameworks information > --- > > Key: MESOS-1719 > URL: https://issues.apache.org/jira/browse/MESOS-1719 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Yongqiao Wang > > https://issues.apache.org/jira/browse/MESOS-1219 disallows completed > frameworks from re-registering with the same framework id, as long as the > master doesn't failover. > This ticket tracks the work for it work across the master failover using > registrar. > There are some open questions that need to be addressed: > --> Should registry contain framework ids only framework infos. > For disallowing completed frameworks from re-registering, persisting > framework ids is enough. But, if in the future, we want to disallow > frameworks from re-registering if some parts of framework info > changed then we need to persist the info too. > --> How to update the framework info. > Currently frameworks are allowed to update framework info while re- > registering, but it only takes effect on the master when the master > fails > over and on the slave when the slave fails over. How should things >change when persist framework info? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2646) Update Master to send revocable resources in separate offers
[ https://issues.apache.org/jira/browse/MESOS-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106625#comment-15106625 ] Yongqiao Wang commented on MESOS-2646: -- [~nnielsen], yes, I think I have. and do you mean I can start to fix this ticker now? > Update Master to send revocable resources in separate offers > > > Key: MESOS-2646 > URL: https://issues.apache.org/jira/browse/MESOS-2646 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Yongqiao Wang > Labels: twitter > Attachments: code-diff.txt > > > Master will send separate offers for revocable and non-revocable/regular > resources. This allows master to rescind revocable offers (e.g, when a new > oversubscribed resources estimate comes from the slave) without impacting > regular offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4440) Clean get/post/deleteRequest func and let the caller to use the general funcion.
Yongqiao Wang created MESOS-4440: Summary: Clean get/post/deleteRequest func and let the caller to use the general funcion. Key: MESOS-4440 URL: https://issues.apache.org/jira/browse/MESOS-4440 Project: Mesos Issue Type: Bug Reporter: Yongqiao Wang Assignee: Yongqiao Wang Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4440) Clean get/post/deleteRequest func and let the caller to use the general funcion.
[ https://issues.apache.org/jira/browse/MESOS-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108162#comment-15108162 ] Yongqiao Wang commented on MESOS-4440: -- In MESOS-3763 ticket, we have exposed the internal::http::request function in the header, so it needs to clean the other instances of post/get to use the http::request method in this ticket. > Clean get/post/deleteRequest func and let the caller to use the general > funcion. > > > Key: MESOS-4440 > URL: https://issues.apache.org/jira/browse/MESOS-4440 > Project: Mesos > Issue Type: Bug >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-1719) Master should persist active frameworks information
[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-1719: Assignee: Yongqiao Wang (was: James Wang) > Master should persist active frameworks information > --- > > Key: MESOS-1719 > URL: https://issues.apache.org/jira/browse/MESOS-1719 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Yongqiao Wang > > https://issues.apache.org/jira/browse/MESOS-1219 disallows completed > frameworks from re-registering with the same framework id, as long as the > master doesn't failover. > This ticket tracks the work for it work across the master failover using > registrar. > There are some open questions that need to be addressed: > --> Should registry contain framework ids only framework infos. > For disallowing completed frameworks from re-registering, persisting > framework ids is enough. But, if in the future, we want to disallow > frameworks from re-registering if some parts of framework info > changed then we need to persist the info too. > --> How to update the framework info. > Currently frameworks are allowed to update framework info while re- > registering, but it only takes effect on the master when the master > fails > over and on the slave when the slave fails over. How should things >change when persist framework info? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4316) Support get non-default weights by /weights
Yongqiao Wang created MESOS-4316: Summary: Support get non-default weights by /weights Key: MESOS-4316 URL: https://issues.apache.org/jira/browse/MESOS-4316 Project: Mesos Issue Type: Task Reporter: Yongqiao Wang Assignee: Yongqiao Wang Priority: Minor Like /quota, we should also add query logic for /weights to keep consistent. Then /roles no longer needs to show weight information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-4143) Reserve/UnReserve Dynamic Reservation Endpoints allow reservations on non-existing roles
[ https://issues.apache.org/jira/browse/MESOS-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-4143: Assignee: Yongqiao Wang > Reserve/UnReserve Dynamic Reservation Endpoints allow reservations on > non-existing roles > > > Key: MESOS-4143 > URL: https://issues.apache.org/jira/browse/MESOS-4143 > Project: Mesos > Issue Type: Bug > Components: master >Affects Versions: 0.25.0, 0.26.0 >Reporter: John Omernik >Assignee: Yongqiao Wang >Priority: Minor > Labels: mesosphere, reservations > > When working with Dynamic reservations via the /reserve and /unreserve > endpoints, it is possible to reserve resources for roles that have not been > specified via the --roles flag on the master. However, these roles are not > usable because the roles have not been defined, nor are they added to the > list of roles available. > Per the mailing list, changing roles after the fact is not possible at this > time. (That may be another JIRA), more importantly, the /reserve and > /unreserve end points should not allow reservation of roles not specified by > --roles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-4214) Introduce HTTP endpoint /weights for updating weight
[ https://issues.apache.org/jira/browse/MESOS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074981#comment-15074981 ] Yongqiao Wang edited comment on MESOS-4214 at 1/5/16 1:44 PM: -- Append test RR: https://reviews.apache.org/r/41789/ https://reviews.apache.org/r/41790/ was (Author: gradywang): Append test RR: https://reviews.apache.org/r/41790/ > Introduce HTTP endpoint /weights for updating weight > > > Key: MESOS-4214 > URL: https://issues.apache.org/jira/browse/MESOS-4214 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3763) Need for http::put request method
[ https://issues.apache.org/jira/browse/MESOS-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084561#comment-15084561 ] Yongqiao Wang commented on MESOS-3763: -- Due to Dynamic Weights tests need this patch urgently, so I have post a patch (https://reviews.apache.org/r/41789/) to expose http::internal::request function. Feel free to review it. Thanks. > Need for http::put request method > - > > Key: MESOS-3763 > URL: https://issues.apache.org/jira/browse/MESOS-3763 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad >Priority: Minor > Labels: mesosphere > > As we decided to create a more restful api for managing Quota request. > Therefore we also want to use the HTTP put request and hence need to enable > the libprocess/http to send put request besides get and post requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3763) Need for http::put request method
[ https://issues.apache.org/jira/browse/MESOS-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15080721#comment-15080721 ] Yongqiao Wang commented on MESOS-3763: -- [~js84] and [~bmahler], I think we already have a function process::http::request(const Request& request, bool streamedResponse) to meet our requirement. Can we use it directly? > Need for http::put request method > - > > Key: MESOS-3763 > URL: https://issues.apache.org/jira/browse/MESOS-3763 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad >Priority: Minor > Labels: mesosphere > > As we decided to create a more restful api for managing Quota request. > Therefore we also want to use the HTTP put request and hence need to enable > the libprocess/http to send put request besides get and post requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4189) Dynamic weights
[ https://issues.apache.org/jira/browse/MESOS-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074784#comment-15074784 ] Yongqiao Wang commented on MESOS-4189: -- We need to commit this ticket then add the test for /weights endpoint. > Dynamic weights > --- > > Key: MESOS-4189 > URL: https://issues.apache.org/jira/browse/MESOS-4189 > Project: Mesos > Issue Type: Epic >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > Mesos current uses a static list of weights that are configured when the > master startup(via the --weights flag), this place some limitation about > change the resource allocation priority for a role/frameworks(changing the > set of weights requires restarting all the masters). > This JIRA will add a new endpoint /weight to update/show weight of a role > with the authorized principles, and the non-default weights will be persisted > in registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3763) Need for http::put request method
[ https://issues.apache.org/jira/browse/MESOS-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074979#comment-15074979 ] Yongqiao Wang commented on MESOS-3763: -- [~js84], the tests for Dynamic weights depends on this ticket, can you help to speed up this ticket? > Need for http::put request method > - > > Key: MESOS-3763 > URL: https://issues.apache.org/jira/browse/MESOS-3763 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad >Priority: Minor > Labels: mesosphere > > As we decided to create a more restful api for managing Quota request. > Therefore we also want to use the HTTP put request and hence need to enable > the libprocess/http to send put request besides get and post requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4214) Introduce HTTP endpoint /weights for updating weight
[ https://issues.apache.org/jira/browse/MESOS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074981#comment-15074981 ] Yongqiao Wang commented on MESOS-4214: -- Append test RR: https://reviews.apache.org/r/41790/ > Introduce HTTP endpoint /weights for updating weight > > > Key: MESOS-4214 > URL: https://issues.apache.org/jira/browse/MESOS-4214 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4214) Introduce HTTP endpoint /weights for updating weight
[ https://issues.apache.org/jira/browse/MESOS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069425#comment-15069425 ] Yongqiao Wang commented on MESOS-4214: -- Append RR: https://reviews.apache.org/r/41681/ > Introduce HTTP endpoint /weights for updating weight > > > Key: MESOS-4214 > URL: https://issues.apache.org/jira/browse/MESOS-4214 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4200) Test case(s) for weights + allocation behavior
[ https://issues.apache.org/jira/browse/MESOS-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15069176#comment-15069176 ] Yongqiao Wang commented on MESOS-4200: -- Append the RR: https://reviews.apache.org/r/41672/ > Test case(s) for weights + allocation behavior > -- > > Key: MESOS-4200 > URL: https://issues.apache.org/jira/browse/MESOS-4200 > Project: Mesos > Issue Type: Task > Components: allocation, test >Reporter: Neil Conway >Assignee: Yongqiao Wang > Labels: mesosphere, test, weight > > As far as I can see, we currently have NO test cases for behavior when > weights are defined. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-4200) Test case(s) for weights + allocation behavior
[ https://issues.apache.org/jira/browse/MESOS-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-4200: Assignee: Yongqiao Wang > Test case(s) for weights + allocation behavior > -- > > Key: MESOS-4200 > URL: https://issues.apache.org/jira/browse/MESOS-4200 > Project: Mesos > Issue Type: Task > Components: allocation, test >Reporter: Neil Conway >Assignee: Yongqiao Wang > Labels: mesosphere, test, weight > > As far as I can see, we currently have NO test cases for behavior when > weights are defined. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4214) Introduce HTTP endpoint /weights for updating weight
Yongqiao Wang created MESOS-4214: Summary: Introduce HTTP endpoint /weights for updating weight Key: MESOS-4214 URL: https://issues.apache.org/jira/browse/MESOS-4214 Project: Mesos Issue Type: Task Reporter: Yongqiao Wang Assignee: Yongqiao Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-2646) Update Master to send revocable resources in separate offers
[ https://issues.apache.org/jira/browse/MESOS-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-2646: Assignee: Yongqiao Wang (was: James Wang) > Update Master to send revocable resources in separate offers > > > Key: MESOS-2646 > URL: https://issues.apache.org/jira/browse/MESOS-2646 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Yongqiao Wang > Labels: twitter > Attachments: code-diff.txt > > > Master will send separate offers for revocable and non-revocable/regular > resources. This allows master to rescind revocable offers (e.g, when a new > oversubscribed resources estimate comes from the slave) without impacting > regular offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-2092) Make ACLs dynamic
[ https://issues.apache.org/jira/browse/MESOS-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-2092: Assignee: Yongqiao Wang (was: James Wang) > Make ACLs dynamic > - > > Key: MESOS-2092 > URL: https://issues.apache.org/jira/browse/MESOS-2092 > Project: Mesos > Issue Type: Task > Components: security >Reporter: Alexander Rukletsov >Assignee: Yongqiao Wang > Labels: mesosphere, newbie > > Master loads ACLs once during its launch and there is no way to update them > in a running master. Making them dynamic will allow for updating ACLs on the > fly, for example granting a new framework necessary rights. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3403) Add support for removing no re-registered slaves with timeout(--slave_reregister_timeout) from an external allocator
[ https://issues.apache.org/jira/browse/MESOS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-3403: Assignee: Yongqiao Wang (was: James Wang) > Add support for removing no re-registered slaves with > timeout(--slave_reregister_timeout) from an external allocator > > > Key: MESOS-3403 > URL: https://issues.apache.org/jira/browse/MESOS-3403 > Project: Mesos > Issue Type: Improvement > Components: master >Reporter: James Wang >Assignee: Yongqiao Wang > > For an external Mesos allocator which does not run with Mesos master in the > same OS process, and maybe this allocator can be deployed in the different > host with Mesos master, then the Mesos allocator module should be implemented > as a proxy, which delegates calls to an actual allocator. > For this external allocator, the total resources and allocated resources will > be stored in it. After Mesos master recovery (such as fail-over), it needs to > sync up with Mesos master. Under normal circumstances, all slaves will > reregister after Mesos master recovery, so we can sync up the total resources > and used resource of each slave in allocator->addSlave function call. But for > the abnormal case, a slave does not reregister after Mesos master recovery, > then master will call function Master::removeSlave(const Registry::Slave& > slave) to remove this slave from Registry after > timeout(slave_reregister_timeout), but this function does not call allocator > to remove the related resources. So in order to support the resources sync up > with the external allocator in this abnormal case, it needs to enhance > function Master::removeSlave(const Registry::Slave& slave) to call > allocator->removeSlave to remove the related resources from external > allocator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4213) Define a proper RESTful API to keep consistency among role-related configuration endpoints
[ https://issues.apache.org/jira/browse/MESOS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4213: - Description: Currently, Mesos uses the following ways to configure role-related objects: 1. For dynamic reserve resources for a role, /reserve endpoint is used to reserve, another /unreserve endpoint is used to unreserve, maybe the third endpoint should be added to show resource reservation of a role later due to someone has issue a requirement of this. 2. For configuring quota for a role, only one endpoint /quota is provided to set/remove/show quota information. 3. For dynamic weights, only one endpoint /weights will be provided to update weight; 4. For role information, /roles endpoint is only provided to show role information contains role name, non-default weight and the registered frameworks and their allocated resources, and any role will be allowed, subject to the ACL/authorization system. We can find that the design between above endpoints are different, so in the long-run, we like the idea of consistency among these types of endpoints, for example: 1. Add a new endpoint /reservations to follow the same PUT+DELETE pattern for reserve+unreserve. 2. Add a new endpoint /volumes to follow the same PUT+DELETE pattern for create+desgroy. 3. Improve /roles endpoints 4. etc. > Define a proper RESTful API to keep consistency among role-related > configuration endpoints > -- > > Key: MESOS-4213 > URL: https://issues.apache.org/jira/browse/MESOS-4213 > Project: Mesos > Issue Type: Epic >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > > Currently, Mesos uses the following ways to configure role-related objects: > 1. For dynamic reserve resources for a role, /reserve endpoint is used to > reserve, another /unreserve endpoint is used to unreserve, maybe the third > endpoint should be added to show resource reservation of a role later due to > someone has issue a requirement of this. > 2. For configuring quota for a role, only one endpoint /quota is provided to > set/remove/show quota information. > 3. For dynamic weights, only one endpoint /weights will be provided to update > weight; > 4. For role information, /roles endpoint is only provided to show role > information contains role name, non-default weight and the registered > frameworks and their allocated resources, and any role will be allowed, > subject to the ACL/authorization system. > We can find that the design between above endpoints are different, so in the > long-run, we like the idea of consistency among these types of endpoints, for > example: > 1. Add a new endpoint /reservations to follow the same PUT+DELETE pattern for > reserve+unreserve. > 2. Add a new endpoint /volumes to follow the same PUT+DELETE pattern for > create+desgroy. > 3. Improve /roles endpoints > 4. etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3943) Support dynamic weight in allocator
[ https://issues.apache.org/jira/browse/MESOS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066087#comment-15066087 ] Yongqiao Wang commented on MESOS-3943: -- Append the RR: https://reviews.apache.org/r/41597/ > Support dynamic weight in allocator > --- > > Key: MESOS-3943 > URL: https://issues.apache.org/jira/browse/MESOS-3943 > Project: Mesos > Issue Type: Task >Reporter: James Wang >Assignee: Yongqiao Wang > > This JIRA will focus on update the allocator API to support weight update of > a role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4213) Define a proper RESTful API to keep consistency among role-related configuration endpoints
Yongqiao Wang created MESOS-4213: Summary: Define a proper RESTful API to keep consistency among role-related configuration endpoints Key: MESOS-4213 URL: https://issues.apache.org/jira/browse/MESOS-4213 Project: Mesos Issue Type: Epic Reporter: Yongqiao Wang Assignee: Yongqiao Wang Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4189) Dynamic weights
Yongqiao Wang created MESOS-4189: Summary: Dynamic weights Key: MESOS-4189 URL: https://issues.apache.org/jira/browse/MESOS-4189 Project: Mesos Issue Type: Epic Reporter: Yongqiao Wang Assignee: Yongqiao Wang Mesos current uses a static list of weights that are configured when the master startup(via the --weights flag), this place some limitation about change the resource allocation priority for a role/frameworks(changing the set of weights requires restarting all the masters). This JIRA will add a new endpoint /weight to update/show weight of a role with the authorized principles, and the non-default weights will be persisted in registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4190) Design Doc
[ https://issues.apache.org/jira/browse/MESOS-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063625#comment-15063625 ] Yongqiao Wang commented on MESOS-4190: -- The design doc for dynamic weights can be found here: https://docs.google.com/document/d/1raTcwzq2Z2He2DIcbzm2g_Ym1YN6wLNP2tbGjUJyAgA/edit?usp=sharing > Design Doc > -- > > Key: MESOS-4190 > URL: https://issues.apache.org/jira/browse/MESOS-4190 > Project: Mesos > Issue Type: Documentation >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > A short design doc for dynamic weights, it will focus on /weights API and the > changes to the allocator API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-3943) Support dynamic weight in allocator
[ https://issues.apache.org/jira/browse/MESOS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3943: - Comment: was deleted (was: Append RR: https://reviews.apache.org/r/40469/) > Support dynamic weight in allocator > --- > > Key: MESOS-3943 > URL: https://issues.apache.org/jira/browse/MESOS-3943 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > This JIRA will focus on update the allocator API to support weight update of > a role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3177) Dynamic roles/weights configuration at runtime
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-3177: Assignee: Yongqiao Wang (was: Yongqiao Wang) > Dynamic roles/weights configuration at runtime > -- > > Key: MESOS-3177 > URL: https://issues.apache.org/jira/browse/MESOS-3177 > Project: Mesos > Issue Type: Epic > Components: master, slave >Reporter: Cody Maloney >Assignee: Yongqiao Wang > Labels: mesosphere > > All roles and weights must currently be specified up-front when starting > Mesos masters currently. In addition, they should be consistent on every > master, otherwise unexpected behavior could occur (You can have them be > inconsistent for some upgrade paths / changing the set). > This makes it hard to introduce new groups of machines under new roles > dynamically (Have to generate a new master configuration, deploy that, before > we can connect slaves with a new role to the cluster). > Ideally an administrator can manually add / remove / edit roles and have the > settings replicated / passed to all masters in the cluster by Mesos. > Effectively Mesos takes ownership of the setting, rather than requiring it to > be done externally. > In addition, if a new slave joins the cluster with an unexpected / new role > that should just work, making it much easier to introduce machines with new > roles. (Policy around whether or not a slave can cause creation of a new > role, a given slave can register with a given role, etc. is out of scope, and > would be controls in the general registration process). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4190) Design Doc
Yongqiao Wang created MESOS-4190: Summary: Design Doc Key: MESOS-4190 URL: https://issues.apache.org/jira/browse/MESOS-4190 Project: Mesos Issue Type: Documentation Reporter: Yongqiao Wang Assignee: Yongqiao Wang A short design doc for dynamic weights, it will focus on /weights API and the changes to the allocator API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3943) Support dynamic weight in allocator
[ https://issues.apache.org/jira/browse/MESOS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-3943: Assignee: Yongqiao Wang (was: Yongqiao Wang) > Support dynamic weight in allocator > --- > > Key: MESOS-3943 > URL: https://issues.apache.org/jira/browse/MESOS-3943 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > This JIRA will focus on update the allocator API to support weight update of > a role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3945) Add operator documentation for role management
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3945: - Assignee: (was: Yongqiao Wang) > Add operator documentation for role management > -- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang > > Add an operator guide for role management which describes basic usage of the > /roles endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3945) Add operator documentation for role management
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang reassigned MESOS-3945: Assignee: Yongqiao Wang (was: Yongqiao Wang) > Add operator documentation for role management > -- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > Add an operator guide for role management which describes basic usage of the > /roles endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3945) Add operator documentation for /weight endpoint
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3945: - Description: This JIRA ticket will update the related doc to apply to dynamic weights, and add an new operator guide for dynamic weights which describes basic usage of the /weights endpoint. (was: Add an operator guide for dynamic weights which describes basic usage of the /weights endpoint.) > Add operator documentation for /weight endpoint > --- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang > > This JIRA ticket will update the related doc to apply to dynamic weights, and > add an new operator guide for dynamic weights which describes basic usage of > the /weights endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3943) Support dynamic weight in allocator
[ https://issues.apache.org/jira/browse/MESOS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3943: - Description: This JIRA will focus on update the allocator API to support weight update of a role. (was: Currently, RoleInfo protobuf never be used for serialization, so I think we can remove it from allocator.proto, and define a struct to communicate between the allocator and master. But for role information display, then current serialization way(call modle(role*) in http.cpp) is not better, and we should define another RoleInfo protobuf for serialization. Refer to other components(such as quota), I propose to define role protobuf in a separated package rather than define it in mesos.proto.) > Support dynamic weight in allocator > --- > > Key: MESOS-3943 > URL: https://issues.apache.org/jira/browse/MESOS-3943 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > This JIRA will focus on update the allocator API to support weight update of > a role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3945) Add operator documentation for /weight endpoint
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3945: - Summary: Add operator documentation for /weight endpoint (was: Add operator documentation for role management) > Add operator documentation for /weight endpoint > --- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang > > Add an operator guide for role management which describes basic usage of the > /roles endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3945) Add operator documentation for /weight endpoint
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3945: - Description: Add an operator guide for dynamic weights which describes basic usage of the /weights endpoint. (was: Add an operator guide for role management which describes basic usage of the /roles endpoint.) > Add operator documentation for /weight endpoint > --- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang > > Add an operator guide for dynamic weights which describes basic usage of the > /weights endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3947) Authenticate /weight request
[ https://issues.apache.org/jira/browse/MESOS-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3947: - Assignee: Yongqiao Wang (was: Yongqiao Wang) Description: /weight endpoint needs to be authenticated. This ticket will authenticate /weight requests using credentials provided by the `Authorization` field of the HTTP request. This is similar to how authentication is implemented in `Master::Http`. was: /roles endpoint needs to be authenticated. This ticket will authenticate /roles requests using credentials provided by the `Authorization` field of the HTTP request. This is similar to how authentication is implemented in `Master::Http`. In addition, for the query request of /roles endpoint, considering that it would not change the status of roles/weights in Mesos master and for backward compatibility , so it will not be authenticated. Summary: Authenticate /weight request (was: Authenticate /roles request) > Authenticate /weight request > > > Key: MESOS-3947 > URL: https://issues.apache.org/jira/browse/MESOS-3947 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > /weight endpoint needs to be authenticated. > This ticket will authenticate /weight requests using credentials provided by > the `Authorization` field of the HTTP request. This is similar to how > authentication is implemented in `Master::Http`. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3948) Authorize /weight request
[ https://issues.apache.org/jira/browse/MESOS-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-3948: - Assignee: Yongqiao Wang (was: Yongqiao Wang) Description: This ticket will authorize /weight requests with ACLs. (was: When /roles are requested it should authorize the updated role. This ticket will authorize /roles requests with ACLs. ) Summary: Authorize /weight request (was: Authorize /roles request) > Authorize /weight request > - > > Key: MESOS-3948 > URL: https://issues.apache.org/jira/browse/MESOS-3948 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > This ticket will authorize /weight requests with ACLs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4007) Persist non-default weights information to registry
[ https://issues.apache.org/jira/browse/MESOS-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4007: - Assignee: Yongqiao Wang (was: Yongqiao Wang) Description: To consider the Mesos master recovery and failover case, Mesos master needs to persist the non-default weights information in registry: - In the first boot, the first leading master initialize the weights replicated log with the specified by command-line flags(--weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth. - At runtime, the weights replicated log can only be updated by /weight. - For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--weights), and also log a warning in Mesos master that the flags values are being ignored. The `--weights` flag is now considered deprecated and will be removed in a future. version of Mesos. was: To consider the Mesos master recovery and failover case, Mesos master needs to persist the roles and weights information in registry: - In the first boot, the first leading master initialize the replicated log with the roles/weights specified by command-line flags(--roles and --weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth. - At runtime, the replicated log can only be updated to add/remove/update entries by the operator REST API. - For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--roles/--weights), and also log a warning in Mesos master that the flags values are being ignored. - For the future works, we can educate end users to create the replicated log to initialize the supported roles/weights before Mesos cluster bootstrap, and reset roles/weights configurations by update the replicated log. Summary: Persist non-default weights information to registry (was: Persist role information to registry) > Persist non-default weights information to registry > --- > > Key: MESOS-4007 > URL: https://issues.apache.org/jira/browse/MESOS-4007 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > To consider the Mesos master recovery and failover case, Mesos master needs > to persist the non-default weights information in registry: > - In the first boot, the first leading master initialize the weights > replicated log with the specified by command-line flags(--weights). The flags > values are only useful to bootstrap the cluster, after which point the > registry becomes the source of truth. > - At runtime, the weights replicated log can only be updated by /weight. > - For Mesos master restart/failover case, if the replicated log for > roles/weights has exist, and then it prefers to use the registry values and > ignore the flags (--weights), and also log a warning in Mesos master that the > flags values are being ignored. > The `--weights` flag is now considered deprecated and will be removed in a > future. > version of Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4007) Persist non-default weights information to registry
[ https://issues.apache.org/jira/browse/MESOS-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4007: - Description: To consider the Mesos master recovery and failover case, Mesos master needs to persist the non-default weights information in registry: - In the first boot, the first leading master initialize the weights replicated log with the specified by command-line flags(--weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth. - At runtime, the weights replicated log can only be updated by /weight. - For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--weights), and also log a warning in Mesos master that the flags values are being ignored. The `--weights` flag is now considered deprecated and will be removed in a future version of Mesos. was: To consider the Mesos master recovery and failover case, Mesos master needs to persist the non-default weights information in registry: - In the first boot, the first leading master initialize the weights replicated log with the specified by command-line flags(--weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth. - At runtime, the weights replicated log can only be updated by /weight. - For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--weights), and also log a warning in Mesos master that the flags values are being ignored. The `--weights` flag is now considered deprecated and will be removed in a future. version of Mesos. > Persist non-default weights information to registry > --- > > Key: MESOS-4007 > URL: https://issues.apache.org/jira/browse/MESOS-4007 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > To consider the Mesos master recovery and failover case, Mesos master needs > to persist the non-default weights information in registry: > - In the first boot, the first leading master initialize the weights > replicated log with the specified by command-line flags(--weights). The flags > values are only useful to bootstrap the cluster, after which point the > registry becomes the source of truth. > - At runtime, the weights replicated log can only be updated by /weight. > - For Mesos master restart/failover case, if the replicated log for > roles/weights has exist, and then it prefers to use the registry values and > ignore the flags (--weights), and also log a warning in Mesos master that the > flags values are being ignored. > The `--weights` flag is now considered deprecated and will be removed in a > future version of Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-3791) Enhance the existing HTTP endpoint /roles
[ https://issues.apache.org/jira/browse/MESOS-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061946#comment-15061946 ] Yongqiao Wang edited comment on MESOS-3791 at 12/17/15 11:50 AM: - Implicit Roles epic MESOS-3988 has provided the similar enhancement for /roles, so close this JIRA directly. was (Author: gradywang): Implicit Roles epic MESOS-3988 has provided the similar fix for /roles. > Enhance the existing HTTP endpoint /roles > - > > Key: MESOS-3791 > URL: https://issues.apache.org/jira/browse/MESOS-3791 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > In this ticket, we will enhance the existing HTTP endpoint to query roles as > outlined in the Design Doc: > https://docs.google.com/document/d/1OIgceqpsjV3-_LGF83IMAFnrh1Ea3Zc16w9kWWPpUj4/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4008) Recovery the non-default weights from registry when master recovery.
[ https://issues.apache.org/jira/browse/MESOS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongqiao Wang updated MESOS-4008: - Assignee: Yongqiao Wang (was: Yongqiao Wang) Description: In Mesos master failover case, non-default weights should be recovered from registry. Note: if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--weights), and also log a warning in Mesos master that the flags values are being ignored. The `--weights` flag is now considered deprecated and will be removed in a future version of Mesos. was: To consider the Mesos master recovery and failover case, Mesos master needs to persist the roles and weights information in registry: - In the first boot, the first leading master initialize the replicated log with the roles/weights specified by command-line flags(--roles and --weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth. - At runtime, the replicated log can only be updated to add/remove/update entries by the operator REST API. - For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--roles/--weights), and also log a warning in Mesos master that the flags values are being ignored. - For the future works, we can educate end users to create the replicated log to initialize the supported roles/weights before Mesos cluster bootstrap, and reset roles/weights configurations by update the replicated log. Summary: Recovery the non-default weights from registry when master recovery. (was: Master recovery with the persisted roles in registry) > Recovery the non-default weights from registry when master recovery. > > > Key: MESOS-4008 > URL: https://issues.apache.org/jira/browse/MESOS-4008 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > > In Mesos master failover case, non-default weights should be recovered from > registry. > Note: if the replicated log for roles/weights has exist, and then it prefers > to use the registry values and ignore the flags (--weights), and also log a > warning in Mesos master that the flags values are being ignored. > The `--weights` flag is now considered deprecated and will be removed in a > future version of Mesos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
