Also for the sake of future googlers: we gave up on supporting keystone development in OS X a release or two ago due to the increasing number of workarounds like this that we had to track (a few of which impacted the code base itself, and were thus dropped).
On Tue, Jul 14, 2015 at 3:42 PM, Kirill Zaitsev <kzait...@mirantis.com> wrote: > Just for the sake of future googlers. I’ve encountered the same problem > (with horizon actually) and managed to solve it. > > 1) install and link latest openssl from homebrew: brew update && brew > install openssl && brew link --force openssl > 2) run tox, it fails. > 3) manually activate the environment you want: . .tox/venv/bin/activate > 4) build cryptography package with brew > ssl: LDFLAGS=-L/usr/local/opt/openssl/lib > CPPFLAGS=-I/usr/local/opt/openssl/include pip install --force-reinstall > --upgrade --no-binary cryptography cryptography > 5) deactivate > > that’s it — that should do the trick. Someone might be able to suggest a > better way to do this, but this variant works for me. (As long as I do not > rebuild venv too often =)) > > -- > Kirill Zaitsev > Murano team > Software Engineer > Mirantis, Inc > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
