blueprints

Its been one week of specifications for Nova in Kilo. What are we seeing proposed so far? Here's a summary... API Add instance administrative lock status to the instance detail results: review 127139. Add more detailed network information to the metadata server: review 85673. Add separated policy rule for each v2.1 api: review 127863. Add user limits to the limits API (as well as project limits): review 127094. Allow all printable characters in resource names: review 126696. Implement instance tagging: review 127281. Implement tags for volumes and snapshots with the EC2 API: review 126553 (spec approved). Implement the v2.1 API: review 126452 (spec approved). Microversion support: review 127127. Move policy validation to just the API layer: review 127160. Support X509 keypairs: review 105034. Administrative Enable the nova metadata cache to be a shared resource to improve the hit rate: review 126705. Containers Service Initial specification: review 114044. Hypervisor: FreeBSD Implement support for FreeBSD networking in nova-network: review 127827. Hypervisor: Hyper-V Allow volumes to be stored on SMB shares instead of just iSCSI: review 102190. Hypervisor: VMWare Add ephemeral disk support to the VMware driver: review 126527 (spec approved). Add support for the HTML5 console: review 127283. Allow Nova to access…

From my email last week on the topic: I am pleased to announce that the specs process for nova in kilo is now open. There are some tweaks to the previous process, so please read this entire email before uploading your spec! Blueprints approved in Juno =========================== For specs approved in Juno, there is a fast track approval process for Kilo. The steps to get your spec re-approved are: - Copy your spec from the specs/juno/approved directory to the specs/kilo/approved directory. Note that if we declared your spec to be a "partial" implementation in Juno, it might be in the implemented directory. This was rare however. - Update the spec to match the new template - Commit, with the "Previously-approved: juno" commit message tag - Upload using git review as normal Reviewers will still do a full review of the spec, we are not offering a rubber stamp of previously approved specs. However, we are requiring only one +2 to merge these previously approved specs, so the process should be a lot faster. A note for core reviewers here -- please include a short note on why you're doing a single +2 approval on the spec so future generations remember…