Intel is planning to post a (very TPM-centric) blueprint and dedicate resources to building the Key Manager for the next (Havana) release. If no one challenges the write up it will most likely be the default implementation for Openstack and difficult to get changes (such as KMIP support) made. See https://wiki.openstack.org/wiki/KeyManager Now is the time for KMIP to make ourselves known (if we want to be a part of the OpenStack cloud offering). OpenStack is very code oriented (those who submit code get the most influence) but also requires socialization (wiki, blueprints, chat, and summit attendance) to get the job done. So, if anyone is interested in participating, here's what is needed: 1. someone (not necessarily one person) willing to commit resources to interact with OpenStack in order to get KMIP into the right place in the OpenStack design 2. a reference (open source) client implementation, with a mock-up server for testing. I'm willing to help socialize KMIP in OpenStack, but some vendor support would be great. Kelley |