This spec is being created to track the work required to get a minimum
viable deployment of kilo. Because the Kilo release of OpenStack has not
yet been released the work done within this blueprint will pull from the
head of master and stabilize on the a given sha for the time being.

In order to have a minimally functional Kilo stack there are several issues
that need to be resolved which have been raised within Launchpad. Once
the following issues are resolved Kilo should be a functional deployment
from the stand point of gating. The point of this Spec is to introduce the
least amount of changes into the stack in an effort to enable a Kilo code
base. The changes should pass gating from the a commit basis. Once this
spec is complete other work can follow to make Kilo a production ready
product.

This change will impact upgrades. The change will introduce new code which
will allow the system to upgrade inplace. That said, this is a transitional
spec which will translate into future work to make Kilo a production ready
product. Upgrades are out of the scope of this spec and it is expected that
Juno to Kilo upgrades will be broken at this point.

Because the Kilo code base is not tested and released the performance of
the stack will not be in scope at this time. As future work develops to
finalize the roles used in Kilo work will be done on a per role basis to
ensure performance.

The spec will introduce a number of new dependencies. At this time not all are
exactly known. However, we can safely say that all new clients will be used
throughout the stack as well as various middlewares.