Reviewed: https://review.openstack.org/458763 Committed: https://git.openstack.org/cgit/openstack/charm-lxd/commit/?id=6df877339c55435a3e87774d7232f4cc0f51bd35 Submitter: Jenkins Branch: master
commit 6df877339c55435a3e87774d7232f4cc0f51bd35 Author: Chris MacNaughton <[email protected]> Date: Fri Apr 21 10:15:14 2017 +0200 Migrate to LXD storage pools We need to continue with the previous style of managing storage until zesty or a specified -updates channel LXD This additionally reinforces our suggested deployment with ZFS for a deployment, rather than using LVM as the defualt in testing. Closes-Bug: 1676742 Related-Bug: 1573681 Depends-On: I5c38766c4be66d63ef4a07eccc780fcab5973d49 Change-Id: I3ddbd11382c34ff9200e721fa3c90fe67bdce534 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573681 Title: conflict when managing LXD storage with Juju 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-lxd/+bug/1573681/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
