mattAndruff commented on pull request #555: URL: https://github.com/apache/bigtop/pull/555#issuecomment-628238520
@guyuqi I'm new to this world of bigtop/Mpacks. But It's my definite understanding that Mpacks are supposed to be deployable without deploying a new version of Ambari. (which your current proposal kind of goes against.) So they should be in fact separate entities that exist outside an ambari install. Perhaps you don't need to push this upstream but instead add a new structure to this project and host all the code changes here as a management pack? (They're just supposed to be tarballs that you can throw into other ambari's, not tied to a release.) I know there are other management packs included with Ambari already so their is totally a precedent set in terms of what other have done. I still believe it goes against the spirit of the whole thing. If they are to be shipped with ambari then it's supposed to be a stack and not a management pack. (I have to say I prefer management stacks as at this time it seems they're cleaner/self contained. So if that's why you did it I get it, still feel like it should be a releasable artifact.) I mean all this to say "this looks amazing" I want it. Can I have it without having to download a patched Ambari? (I totally will if it comes to that. Just again kind of feels against the intent of what a mpack is.) Also I totally want to see more services included and I"m totally willing to help. Like for instances writing up how to make this work. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
