The following is a list of actions regarding pending PRs and JIRA
tickets, some of them for discussing. Please comment if you consider
some change, or different action:

1. https://issues.apache.org/jira/browse/MYRIAD-86

"Consider an API for desired # instances, rather than flex up/down"

Comment: It looks the API /api/cluster/flexup and
/api/cluster/flexdown support the instance numbers yet.
Action: Close issue

2. https://github.com/apache/incubator-myriad/pull/103

"Remove maven central repository, use only jcenter"

Comment: Minor change. No problem for changing this resource IMHO.
Action: Merge PR

3. https://github.com/apache/incubator-myriad/pull/102

"Make links relative in index.html"

Comment; Minor change, however useful for DC/OS environments.
Action: Merge PR

4. https://github.com/apache/incubator-myriad/pull/99 and
https://issues.apache.org/jira/browse/MYRIAD-247

"MYRIAD-247 Fail to fetch yarnConfiguration from Resourcemanager"

Commnet: It looks good for me.
Action: Merge PR and Close Issue.

5 https://github.com/apache/incubator-myriad/pull/101 and
https://issues.apache.org/jira/browse/MYRIAD-250

"MYRIAD-250 Should shutdown mesos framework when stop resourcemanager"

Comment: PR ready but pending Unittest.
Action: Discuss

6. https://github.com/apache/incubator-myriad/pull/110 and
https://issues.apache.org/jira/browse/MYRIAD-263

"MYRIAD-263 Add HDFS as system service in DC/OS vagrant testbed"

Comment: PR ready and tested.
Action: Merge PR

7. https://issues.apache.org/jira/browse/MYRIAD-88

"Reduce verbose logging"

Comment: Proposal of changing from INFO to WARN in the JIRA ticket.
Action; Discuss.

8. https://issues.apache.org/jira/browse/MYRIAD-12

"Implement auto scaling"

Comment: Interesting feature for the new Myriad release
Action: Discuss.

9. https://issues.apache.org/jira/browse/MYRIAD-39

"Constraint-based scheduling"

Comment; Feature for the new Myriad release.
Action: Discuss.


--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info

Reply via email to