Re: [Review Queue] New charm: trusty/cassandra
Thanks for sharing Tim. I want to add that Datastax has recently joined our Charm Partner Programme. This charm will be the base of their work. They will support it and port it to support the upcoming DSE 4.7 due this month. Feel free to ask any question about this, Thanks, Samuel Best, Samuel -- Samuel Cozannet Cloud, Big Data and IoT Strategy Team Business Development - Cloud and ISV Ecosystem Changing the Future of Cloud Ubuntu http://ubuntu.com / Canonical UK LTD http://canonical.com / Juju https://jujucharms.com samuel.cozan...@canonical.com mob: +33 616 702 389 skype: samnco Twitter: @SaMnCo_23 On Mon, May 18, 2015 at 2:51 PM, Tim Van Steenburgh tim.van.steenbu...@canonical.com wrote: This is a total rewrite of the Cassandra charm. It supports Apache Cassandra 2.0, 2.1 and DataStax Enterprise 4.6. It is not backwards compatible with the old precise/cassandra charm that only supported earlier versions of Cassandra. Many thanks to Stuart Bishop for his work on this charm! -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Running CI tests locally.
Hi All, tl;dr bash script to run CI deploy job locally: https://github.com/waigani/juju-scripts/blob/master/ci.sh During the last sprint I showed a script which checks out the CI tools and runs the tests locally. The link to the script and slides have been in the sprint notes doc. As a few have asked for it, I'm sharing the link here. I've updated the script to make use of new flags and features added to the CI tools. The script comments give instructions on how to use it. I'll just give one example here: $ ci.sh --provider=amazon --current-juju-bin=/custom/version/juju/bin --keep-env --upload-tools --upgrade This uses my custom built Juju to bootstrap using my amazon config. It uploads and uses the local tools for bootstraping, deploys two services, adds a relation, then upgrades (incrementing the patch version by 1) - all on ec2. The environment is keep for inspection. ci.sh currently only runs the deploy job (bootstrap, deploy two services, add relation, destroy environment). From what I can see, this is the only job currently in the juju-ci-tools repository. I have been writing a JES deploy job (testing multiple environments). When this is ready*, ci.sh will be updated to run different jobs. * The JES deploy job script is all but done. Along the way, it has revealed bugs with JES which take priority over finishing the script. I do not want to push the JES job up until we get at least one clean pass. Cheers, Jess -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Juju devel 1.24-beta4 is available for testing
# juju-core 1.24-beta4 A new development release of Juju, juju-core 1.24-beta4, is now available. This release replaces version 1.24-beta3. ## Getting Juju juju-core 1.24-beta4 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24-beta4 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.24-beta4. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Agents see too many open files errors after many failed api attempts Lp 1420057 * Container destruction doesn't mark ip addresses as dead Lp 1441206 * Debug-hooks not working with manually provisioned machines Lp 1429790 * Joyent machines get stuck in provisioning Lp 1446264 * Cannot process charms: finding charm revision info: cannot get metadata from the charm store: verification failed: no macaroon cookies in request Lp 1453238 * Juju log spams error juju.worker.diskmanager lsblk.go:111 error checking if sr0 is in use: open /dev/sr0: no medium found Lp 1454481 * Failed to retrieve the template to clone - 500 internal server error - error creating container juju-trusty-lxc-template - Lp 1454676 * 1.20.x client cannot communicate with 1.22.x env Lp 1454829 * Received disconnect from ...: 2: too many authentication failures for ubuntu Lp 1456315 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Juju devel 1.24-beta4 is available for testing
# juju-core 1.24-beta4 A new development release of Juju, juju-core 1.24-beta4, is now available. This release replaces version 1.24-beta3. ## Getting Juju juju-core 1.24-beta4 is available for vivid and backported to earlier series in the following PPA: https://launchpad.net/~juju/+archive/devel Windows and OS X users will find installers at: https://launchpad.net/juju-core/+milestone/1.24-beta4 Development releases use the devel simple-streams. You must configure the `agent-stream` option in your environments.yaml to use the matching juju agents. Upgrading from stable releases to development releases is not supported. You can upgrade test environments to development releases to test new features and fixes, but it is not advised to upgrade production environments to 1.24-beta4. ## Notable Changes This releases addresses stability and performance issues. ## Resolved issues * Agents see too many open files errors after many failed api attempts Lp 1420057 * Container destruction doesn't mark ip addresses as dead Lp 1441206 * Debug-hooks not working with manually provisioned machines Lp 1429790 * Joyent machines get stuck in provisioning Lp 1446264 * Cannot process charms: finding charm revision info: cannot get metadata from the charm store: verification failed: no macaroon cookies in request Lp 1453238 * Juju log spams error juju.worker.diskmanager lsblk.go:111 error checking if sr0 is in use: open /dev/sr0: no medium found Lp 1454481 * Failed to retrieve the template to clone - 500 internal server error - error creating container juju-trusty-lxc-template - Lp 1454676 * 1.20.x client cannot communicate with 1.22.x env Lp 1454829 * Received disconnect from ...: 2: too many authentication failures for ubuntu Lp 1456315 Finally We encourage everyone to subscribe the mailing list at juju-...@lists.canonical.com, or join us on #juju-dev on freenode. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
