Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.2.0
    • Component/s: deployment
    • Labels:

      Description

      This is a request to add the Juju Pig charm to the bigtop packaging source tree.

        Issue Links

          Activity

          Hide
          AndrewMcLeod Andrew McLeod added a comment -

          I am working on this, however I am unable to assign it to myself.

          Show
          AndrewMcLeod Andrew McLeod added a comment - I am working on this, however I am unable to assign it to myself.
          Hide
          githubbot ASF GitHub Bot added a comment -

          GitHub user andrewdmcleod opened a pull request:

          https://github.com/apache/bigtop/pull/121

          BIGTOP-2482: Adding Pig charm

          You can merge this pull request into a Git repository by running:

          $ git pull https://github.com/juju-solutions/bigtop PIG-BIGTOP-2482

          Alternatively you can review and apply these changes as the patch at:

          https://github.com/apache/bigtop/pull/121.patch

          To close this pull request, make a commit to your master/trunk branch
          with (at least) the following in the commit message:

          This closes #121


          commit 648ca7c6215d983ba3079d0fb3de7e9d41a483b8
          Author: Kevin W Monroe <kevin.monroe@canonical.com>
          Date: 2016-06-08T02:59:24Z

          BIGTOP-2482: Adding Pig charm


          Show
          githubbot ASF GitHub Bot added a comment - GitHub user andrewdmcleod opened a pull request: https://github.com/apache/bigtop/pull/121 BIGTOP-2482 : Adding Pig charm You can merge this pull request into a Git repository by running: $ git pull https://github.com/juju-solutions/bigtop PIG- BIGTOP-2482 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bigtop/pull/121.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #121 commit 648ca7c6215d983ba3079d0fb3de7e9d41a483b8 Author: Kevin W Monroe <kevin.monroe@canonical.com> Date: 2016-06-08T02:59:24Z BIGTOP-2482 : Adding Pig charm
          Hide
          rvs Roman Shaposhnik added a comment -

          I've added you to the contributor group. Please try assign it to yourself now. Also, is the patch (on PR) ready for review?

          Show
          rvs Roman Shaposhnik added a comment - I've added you to the contributor group. Please try assign it to yourself now. Also, is the patch (on PR) ready for review?
          Hide
          johnsca Cory Johns added a comment - - edited

          Yes, thanks, the patch available from GH is ready for review.

          Show
          johnsca Cory Johns added a comment - - edited Yes, thanks, the patch available from GH is ready for review.
          Hide
          rvs Roman Shaposhnik added a comment -

          Cory Johns could you please remind me how to run Juju unit tests? I'd like to see it work in my environment end-to-end.

          Show
          rvs Roman Shaposhnik added a comment - Cory Johns could you please remind me how to run Juju unit tests? I'd like to see it work in my environment end-to-end.
          Hide
          johnsca Cory Johns added a comment - - edited

          Roman,

          Apologies for the delayed response.

          The purpose of the Juju charms is to facilitate deployment / testing of Bigtop on clouds or cloud-like environments (such as bare-metal or container-based clusters). As such, the charms are not much more than metadata with some minimal code around the existing Puppet scripts and some minimal code to coordinate the connections to other services. We haven't found it practical so far to unit test that, so have focused on enabling the Bigtop smoke-tests.

          In order to test a charm like Pig, you’ll first need to setup Juju.  Once that’s done, you can build and test charms in your Juju environment as outlined in bigtop-packages/src/charm/README.  For convenience, we've published this charm to the charm store. This means you don’t need to build the Pig charm for yourself in order to test or use it – you can simply deploy directly from the store. For Pig, this means deploying the core hadoop-processing bundle and adding Pig to the deployment, as outlined in the “Usage” section of the Pig charm README.  Once deployed, you can see deployment status and run the smoke-test, again noted in the Pig charm README.

          I hope this is useful info – your question has us thinking about how to best present Juju Charms to the Bigtop community.  Our documentation is admittedly developer-centric, so we’ll be proposing an update to the bigtop-packages/src/charm/README that would be beneficial to people interested in using the charms versus people interested in developing charms. We also wanted to ask about adding this information to the Deployment section of the Wiki; what is the process for submitting changes to the Wiki?

          Show
          johnsca Cory Johns added a comment - - edited Roman, Apologies for the delayed response. The purpose of the Juju charms is to facilitate deployment / testing of Bigtop on clouds or cloud-like environments (such as bare-metal or container-based clusters). As such, the charms are not much more than metadata with some minimal code around the existing Puppet scripts and some minimal code to coordinate the connections to other services . We haven't found it practical so far to unit test that, so have focused on enabling the Bigtop smoke-tests . In order to test a charm like Pig, you’ll first need to setup Juju .  Once that’s done, you can build and test charms in your Juju environment as outlined in bigtop-packages/src/charm/README .  For convenience, we've published this charm to the charm store . This means you don’t need to build the Pig charm for yourself in order to test or use it – you can simply deploy directly from the store. For Pig, this means deploying the core hadoop-processing bundle and adding Pig to the deployment, as outlined in the “Usage” section of the Pig charm README .  Once deployed, you can see deployment status and run the smoke-test, again noted in the Pig charm README . I hope this is useful info – your question has us thinking about how to best present Juju Charms to the Bigtop community.  Our documentation is admittedly developer-centric, so we’ll be proposing an update to the bigtop-packages/src/charm/README that would be beneficial to people interested in using the charms versus people interested in developing charms. We also wanted to ask about adding this information to the Deployment section of the Wiki ; what is the process for submitting changes to the Wiki?
          Hide
          rvs Roman Shaposhnik added a comment -

          Cory Johns thanks for a very detailed explanations. I really think this (plus great answers on the mailing list http://markmail.org/message/amrsxixelq5i7xxy#query:+page:1+mid:amrsxixelq5i7xxy+state:results ) belong on the wiki. Do you need karma to update it?

          Show
          rvs Roman Shaposhnik added a comment - Cory Johns thanks for a very detailed explanations. I really think this (plus great answers on the mailing list http://markmail.org/message/amrsxixelq5i7xxy#query:+page:1+mid:amrsxixelq5i7xxy+state:results ) belong on the wiki. Do you need karma to update it?
          Hide
          johnsca Cory Johns added a comment -

          Roman Shaposhnik, I'm not sure what we need to be able to make changes to the wiki. I actually wasn't even able to use my normal Apache account to log in to https://cwiki.apache.org/ so had to register separately, and I still don't have access. Was re-registering the wrong thing to do, or is there something I need to do to link my account? Thanks.

          Show
          johnsca Cory Johns added a comment - Roman Shaposhnik , I'm not sure what we need to be able to make changes to the wiki. I actually wasn't even able to use my normal Apache account to log in to https://cwiki.apache.org/ so had to register separately, and I still don't have access. Was re-registering the wrong thing to do, or is there something I need to do to link my account? Thanks.
          Hide
          rvs Roman Shaposhnik added a comment -

          Cory Johns sadly, ASF doesn't have a single sign-on so various services require separate accounts. It helps, of course, to keep the names of those accounts the same. I take it that your CWIKI ID is johnsca I've granted persmissions to that account so please add the article to the wiki.

          Show
          rvs Roman Shaposhnik added a comment - Cory Johns sadly, ASF doesn't have a single sign-on so various services require separate accounts. It helps, of course, to keep the names of those accounts the same. I take it that your CWIKI ID is johnsca I've granted persmissions to that account so please add the article to the wiki.
          Hide
          kwmonroe Kevin W Monroe added a comment -

          Andrew McLeod, i made some changes to the readme and tests for juju 2.0 and xenial. Other than that, this looks good in both local and mapreduce mode. Thanks!

          Show
          kwmonroe Kevin W Monroe added a comment - Andrew McLeod , i made some changes to the readme and tests for juju 2.0 and xenial. Other than that, this looks good in both local and mapreduce mode. Thanks!
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user asfgit closed the pull request at:

          https://github.com/apache/bigtop/pull/121

          Show
          githubbot ASF GitHub Bot added a comment - Github user asfgit closed the pull request at: https://github.com/apache/bigtop/pull/121
          Hide
          kwmonroe Kevin W Monroe added a comment -

          Charm built from this source is available at:

          https://jujucharms.com/pig/

          Show
          kwmonroe Kevin W Monroe added a comment - Charm built from this source is available at: https://jujucharms.com/pig/

            People

            • Assignee:
              AndrewMcLeod Andrew McLeod
              Reporter:
              AndrewMcLeod Andrew McLeod
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development