You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "David Liu (JIRA)" <ji...@apache.org> on 2012/05/18 17:23:08 UTC
[jira] [Created] (BIGTOP-594) Introduce git-style bigtop command
line and BIGTOP_HOME environment variable
David Liu created BIGTOP-594:
--------------------------------
Summary: Introduce git-style bigtop command line and BIGTOP_HOME environment variable
Key: BIGTOP-594
URL: https://issues.apache.org/jira/browse/BIGTOP-594
Project: Bigtop
Issue Type: New Feature
Components: General
Affects Versions: 0.4.0
Reporter: David Liu
A "git"-style shell script that allows a single point of entry to manage and monitor any of the bigtop upstream systems.
Something like mvn or git command. This will introduce something to
learn at first but it adds value to start/stop/access help for all systems in
a consistent way. It can also shield some changes that happens with
upstream systems. Instead of dealing with some many <XXX>_HOME, we can have one BIGTOP_HOME environment variable.
Proposed on bigtop email lists, and presented the attached slides during the hackathon.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-594) Introduce git-style bigtop command
line and BIGTOP_HOME environment variable
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279366#comment-13279366 ]
Roman Shaposhnik commented on BIGTOP-594:
-----------------------------------------
Great stuff! David, can you please take a look at this JIRA: BIGTOP-492 and let us know whether you think your work will take of the use case it talks about.
> Introduce git-style bigtop command line and BIGTOP_HOME environment variable
> ----------------------------------------------------------------------------
>
> Key: BIGTOP-594
> URL: https://issues.apache.org/jira/browse/BIGTOP-594
> Project: Bigtop
> Issue Type: New Feature
> Components: General
> Affects Versions: 0.4.0
> Reporter: David Liu
> Assignee: David Liu
> Attachments: Bigtop Wrapper.pptx
>
> Original Estimate: 1,008h
> Remaining Estimate: 1,008h
>
> A "git"-style shell script that allows a single point of entry to manage and monitor any of the bigtop upstream systems.
> Something like mvn or git command. This will introduce something to
> learn at first but it adds value to start/stop/access help for all systems in
> a consistent way. It can also shield some changes that happens with
> upstream systems. Instead of dealing with some many <XXX>_HOME, we can have one BIGTOP_HOME environment variable.
> Proposed on bigtop email lists, and presented the attached slides during the hackathon.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BIGTOP-594) Introduce git-style bigtop command
line and BIGTOP_HOME environment variable
Posted by "David Liu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Liu updated BIGTOP-594:
-----------------------------
Attachment: Bigtop Wrapper.pptx
Presented on 5/17/2012 Bigtop Hackathon.
> Introduce git-style bigtop command line and BIGTOP_HOME environment variable
> ----------------------------------------------------------------------------
>
> Key: BIGTOP-594
> URL: https://issues.apache.org/jira/browse/BIGTOP-594
> Project: Bigtop
> Issue Type: New Feature
> Components: General
> Affects Versions: 0.4.0
> Reporter: David Liu
> Attachments: Bigtop Wrapper.pptx
>
> Original Estimate: 1,008h
> Remaining Estimate: 1,008h
>
> A "git"-style shell script that allows a single point of entry to manage and monitor any of the bigtop upstream systems.
> Something like mvn or git command. This will introduce something to
> learn at first but it adds value to start/stop/access help for all systems in
> a consistent way. It can also shield some changes that happens with
> upstream systems. Instead of dealing with some many <XXX>_HOME, we can have one BIGTOP_HOME environment variable.
> Proposed on bigtop email lists, and presented the attached slides during the hackathon.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (BIGTOP-594) Introduce git-style bigtop command
line and BIGTOP_HOME environment variable
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik reassigned BIGTOP-594:
---------------------------------------
Assignee: David Liu
> Introduce git-style bigtop command line and BIGTOP_HOME environment variable
> ----------------------------------------------------------------------------
>
> Key: BIGTOP-594
> URL: https://issues.apache.org/jira/browse/BIGTOP-594
> Project: Bigtop
> Issue Type: New Feature
> Components: General
> Affects Versions: 0.4.0
> Reporter: David Liu
> Assignee: David Liu
> Attachments: Bigtop Wrapper.pptx
>
> Original Estimate: 1,008h
> Remaining Estimate: 1,008h
>
> A "git"-style shell script that allows a single point of entry to manage and monitor any of the bigtop upstream systems.
> Something like mvn or git command. This will introduce something to
> learn at first but it adds value to start/stop/access help for all systems in
> a consistent way. It can also shield some changes that happens with
> upstream systems. Instead of dealing with some many <XXX>_HOME, we can have one BIGTOP_HOME environment variable.
> Proposed on bigtop email lists, and presented the attached slides during the hackathon.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira