Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BIGTOP-2712: Juju CI driven updates #189

Closed
wants to merge 16 commits into from

Conversation

kwmonroe
Copy link
Member

The original point of this branch was to refresh the hbase charm (readme was out-of-date, needed lint love). However, as soon as ran CI on this and recent changes from #187, it was like I opened a filthy can of yarn (or however that saying goes).

None of these are show-stoppers, but all of them are issues that could affect the UX when deploying/testing bigtop charms:

  • Transient ganglia/rsyslog errors (e.g. websocket timeouts when trying to connect to http://ganglia-ip/ganglia). Since these are not directly related to bigtop, ignore test failures in these components.
  • hbase: this was neat. I just happened to run an hbase test and discovered the charm wasn't using the hbase-quorum interface to learn about hbase peers. Because of this, i'm adding a hadoop-hbase bundle that will surface issues in the HBase charm faster.
  • kafka, spark, and zookeeper: part of the tests for these charms alters the configuration. Ensure the charm-under-test does not actually alter the config of an existing deployment. This means deploy <charm>-test for testing, and destroy it when done.
  • mahout: the smoke test is hot garbage. Make it better (i.e. make it like the giraph smoke test).

As mentioned earlier, none of these issues affect charm functionality, but they do resolve test issues that might bite a user. This should be a trivial add and I am confident I can get good test runs before 1.2 goes RC.

@asfgit asfgit closed this in 4a24c4b Mar 28, 2017
@kwmonroe kwmonroe deleted the feature/hbase-refresh branch March 29, 2017 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant