Now that https://pypi.python.org/pypi/jujubigdata is available, I'd like
to switch to that instead of updating charmhelpers, as it will allow us
to change our resources entry to this:
jujubigdata:
pypi: jujubigdata>=1.0.0,<2.0.0
This will give us the ability to make backwards compatible bug fixes and
improvements without updating all of the charms individually, and if we
need to make a change that would break the existing charms, we can still
do that by increasing the major version number, and then updating &
fixing the charms, so that deployments of the older versions will
continue to work with the older jujubigdata version.
IOW, it gives us much better control over our versioning and avoids
excessive churn on the charms.
--
You received this bug notification because you are a member of Juju Big
Data Development, which is a bug assignee.
https://bugs.launchpad.net/bugs/1453839
Title:
ip matching is too aggressive
Status in Juju Charms:
Fix Committed
Bug description:
In utils.py, we check for /etc/hosts entries and update them if found,
append them if not found. The ip matching re is too aggressive, and
will match if an ip is a subset of another (e.g. 10.0.0.123 will match
when scanning for 10.0.0.12).
This is an easy fix -- just add a whitespace char to the re, but all
apache-hadoop core charms will need an updated charmhelpers.tgz.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charms/+bug/1453839/+subscriptions
--
Mailing list: https://launchpad.net/~bigdata-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~bigdata-dev
More help : https://help.launchpad.net/ListHelp
