Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-2703

refresh juju charms/bundles with metric and CI support

    Details

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

      Description

      Given the upcoming code freeze for 1.2, this is a refresh for all the Juju charms/bundles that are currently based on bigtop-1.1. Notable mentions:

      • include basic metric collection (e.g.: node count, useful to help application scale decisions)
      • include ci-info.yaml to help Juju CI systems determine what to test
      • make readmes consistent
      • missing hadoop-kafka bundle source, which was made generally available in the juju charm store months ago

        Issue Links

          Activity

          Hide
          cos Konstantin Boudnik added a comment -

          Shall it be marked against 1.2 then?

          Show
          cos Konstantin Boudnik added a comment - Shall it be marked against 1.2 then?
          Hide
          githubbot ASF GitHub Bot added a comment -

          GitHub user kwmonroe opened a pull request:

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

          BIGTOP-2703: refresh juju charms/bundles with metric and CI support

          While this looks like a large PR, the majority is simply bumping charm revisions/locations in yaml files and updating READMEs to be consistent. Other notable mentions include:

          • include basic metric collection for NN/RM/ZK (e.g.: node count, useful to help application scale decisions)
          • include ci-info.yaml to help Juju CI systems determine what to test in a bundle
          • include hadoop-kafka bundle source, which was made generally available in the juju charm store months ago (yet missing from upstream repo)
          • move bundle machine constraints to the application (else, scaling an application would get default cloud constraints)

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

          $ git pull https://github.com/juju-solutions/bigtop feature/metrics

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

          https://github.com/apache/bigtop/pull/187.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 #187



          Show
          githubbot ASF GitHub Bot added a comment - GitHub user kwmonroe opened a pull request: https://github.com/apache/bigtop/pull/187 BIGTOP-2703 : refresh juju charms/bundles with metric and CI support While this looks like a large PR, the majority is simply bumping charm revisions/locations in yaml files and updating READMEs to be consistent. Other notable mentions include: include basic metric collection for NN/RM/ZK (e.g.: node count, useful to help application scale decisions) include ci-info.yaml to help Juju CI systems determine what to test in a bundle include hadoop-kafka bundle source, which was made generally available in the juju charm store months ago (yet missing from upstream repo) move bundle machine constraints to the application (else, scaling an application would get default cloud constraints) You can merge this pull request into a Git repository by running: $ git pull https://github.com/juju-solutions/bigtop feature/metrics Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bigtop/pull/187.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 #187
          Hide
          kwmonroe Kevin W Monroe added a comment -

          Konstantin Boudnik, yup, I just updated to target 1.2 – I'll have this closed out after the Juju CI runs tonight. What could possibly go wrong, amirite?

          Show
          kwmonroe Kevin W Monroe added a comment - Konstantin Boudnik , yup, I just updated to target 1.2 – I'll have this closed out after the Juju CI runs tonight. What could possibly go wrong, amirite?
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user c0s commented on the issue:

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

          If it is all working and look good for other Juju's team guys - please go and commit this, perhaps after squashing them together. Thanks!

          Show
          githubbot ASF GitHub Bot added a comment - Github user c0s commented on the issue: https://github.com/apache/bigtop/pull/187 If it is all working and look good for other Juju's team guys - please go and commit this, perhaps after squashing them together. Thanks!
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user asfgit closed the pull request at:

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

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

          Of course I jinxed myself. Tests uncovered issues with HBase and Mahout charms. I'll open jiras to resolve those (simple rebuilds should be all that's needed).

          This patch, however, is g2g. QA was green for containers and AWS:

          http://bigtop.charm.qa/cwr_bundle_hadoop_processing/6/report.html

          Note the lack of runs on gce/azure were do to timeouts and personal account limits being exceeded – I am confident aws+lxd proves this safe for merging.

          Show
          kwmonroe Kevin W Monroe added a comment - Of course I jinxed myself. Tests uncovered issues with HBase and Mahout charms. I'll open jiras to resolve those (simple rebuilds should be all that's needed). This patch, however, is g2g. QA was green for containers and AWS: http://bigtop.charm.qa/cwr_bundle_hadoop_processing/6/report.html Note the lack of runs on gce/azure were do to timeouts and personal account limits being exceeded – I am confident aws+lxd proves this safe for merging.

            People

            • Assignee:
              kwmonroe Kevin W Monroe
              Reporter:
              kwmonroe Kevin W Monroe
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 24h
                24h
                Remaining:
                Remaining Estimate - 24h
                24h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Development