ae74cd056e
Sometimes, trove image builds fail because of package authentication issues. This is often times related to the inability to get to a key server, and not indicative of anything more serious than that. The (strongly discouraged in production use cases) workaround for this is to pass the --allow-unauthenticated option to apt-get install. I say 'Closes-Bug' below but I realize that this is a white lie. What it fixes is only the Trove elements. The image build process uses elements from other places (triple-o, for example). These can still fail for the same reason. There is a much bigger hammer that we can use if we need it, and that is to throw the line 'APT::Get::AllowUnauthenticated "true";' into a conf file in /etc/apt/apt.conf.d/. If this hammer isn't big enough, we can revist later. Change-Id: I009697332bb2a8e1e60b17c10944faed5c311da3 Closes-Bug:#1646856
Trove
Trove is Database as a Service for OpenStack.
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone https://github.com/openstack/trove
- Wiki: https://wiki.openstack.org/wiki/Trove
- Developer Docs: http://docs.openstack.org/developer/trove
You can raise bugs here: https://bugs.launchpad.net/trove
Python client
https://git.openstack.org/cgit/openstack/python-troveclient
References
- Installation docs: http://docs.openstack.org/developer/trove/dev/install.html
- Manual installation docs: http://docs.openstack.org/developer/trove/dev/manual_install.html
- Build guest image: http://docs.openstack.org/developer/trove/dev/building_guest_images.html