kilo – Made by Mikal

Another Nova spec update

Post author:mikal
Post published:January 17, 2015
Post category:OpenStack

I started chasing down the list of spec freeze exceptions that had been requested, and that resulted in the list of specs for Kilo being updated. That updated list is below, but I'll do a separate post with the exception requests highlighted soon as well. API Add more detailed network information to the metadata server: review 85673 (approved). Add separated policy rule for each v2.1 api: review 127863 (requested a spec exception). Add user limits to the limits API (as well as project limits): review 127094. Allow all printable characters in resource names: review 126696 (approved). Consolidate all console access APIs into one: review 141065 (approved). Expose the lock status of an instance as a queryable item: review 127139 (abandoned); review 85928 (approved). Extend api to allow specifying vnic_type: review 138808 (requested a spec exception). Implement instance tagging: review 127281 (fast tracked, approved). Implement the v2.1 API: review 126452 (fast tracked, approved). Improve the return codes for the instance lock APIs: review 135506. Microversion support: review 127127 (approved). Move policy validation to just the API layer: review 127160 (approved). Nova Server Count API Extension: review 134279 (fast tracked). Provide a policy statement on the goals of our API policies: review…

How are we going with Nova Kilo specs after our review day?

Post author:mikal
Post published:December 15, 2014
Post category:OpenStack

Time for another summary I think, because announcing the review day seems to have caused a rush of new specs to be filed (which wasn't really my intention, but hey). We did approve a fair few specs on the review day, so I think overall it was a success. Here's an updated summary of the state of play: API 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. Consolidate all console access APIs into one: review 141065. Expose the lock status of an instance as a queryable item: review 127139 (abandoned); review 85928 (approved). Extend api to allow specifying vnic_type: review 138808. Implement instance tagging: review 127281 (fast tracked, approved). Implement the v2.1 API: review 126452 (fast tracked, approved). Improve the return codes for the instance lock APIs: review 135506. Microversion support: review 127127 (approved). Move policy validation to just the API layer: review 127160. Nova Server Count API Extension: review 134279 (fast tracked). Provide a policy statement on the goals of our API policies:…

Specs for Kilo, an update

Post author:mikal
Post published:December 3, 2014
Post category:OpenStack

We're now a few weeks away from the kilo-1 milestone, so I thought it was time to update my summary of the Nova specifications that have been proposed so far. So here we go... API 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. Expose the lock status of an instance as a queryable item: review 127139 (abandoned); review 85928 (approved). Implement instance tagging: review 127281 (fast tracked, approved). Implement the v2.1 API: review 126452 (fast tracked, approved). Improve the return codes for the instance lock APIs: review 135506. Microversion support: review 127127 (approved). Move policy validation to just the API layer: review 127160. Nova Server Count API Extension: review 134279 (fast tracked). Provide a policy statement on the goals of our API policies: review 128560. Sorting enhancements: review 131868 (fast tracked, approved). Support JSON-Home for API extension discovery: review 130715. Support X509 keypairs: review 105034 (approved). API (EC2) Expand support for volume filtering in the EC2 API: review 104450. Implement tags for volumes and…

Specs for Kilo

Post author:mikal
Post published:October 25, 2014
Post category:OpenStack

Here's an updated list of the specs currently proposed for Kilo. I wanted to produce this before I start travelling for the summit in the next couple of days because I think many of these will be required reading for the Nova track at the summit. API Add instance administrative lock status to the instance detail results: review 127139 (abandoned). 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. Expose the lock status of an instance as a queryable item: review 85928 (approved). Implement instance tagging: review 127281 (fast tracked, approved). Implement tags for volumes and snapshots with the EC2 API: review 126553 (fast tracked, approved). Implement the v2.1 API: review 126452 (fast tracked, approved). Microversion support: review 127127. Move policy validation to just the API layer: review 127160. Provide a policy statement on the goals of our API policies: review 128560. Support X509 keypairs: review 105034. Administrative Enable the nova metadata cache to be a shared resource to improve the hit rate: review 126705…

One week of Nova Kilo specifications

Post author:mikal
Post published:October 14, 2014
Post category:OpenStack

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…

Compute Kilo specs are open

Post author:mikal
Post published:October 13, 2014
Post category:OpenStack

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…

On layers

Post author:mikal
Post published:October 1, 2014
Post category:OpenStack

There's been a lot of talk recently about what we should include in OpenStack and what is out of scope. This is interesting, in that many of us used to believe that we should do ''everything''. I think what's changed is that we're learning that solving all the problems in the world is hard, and that we need to re-focus on our core products. In this post I want to talk through the various "layers" proposals that have been made in the last month or so. Layers don't directly address what we should include in OpenStack or not, but they are a useful mechanism for trying to break up OpenStack into simpler to examine chunks, and I think that makes them useful in their own right. I would address what I believe the scope of the OpenStack project should be, but I feel that it makes this post so long that no one will ever actually read it. Instead, I'll cover that in a later post in this series. For now, let's explore what people are proposing as a layering model for OpenStack. What are layers? Dean Troyer did a good job of describing a layers model for the OpenStack…

My candidacy for Kilo Compute PTL

Post author:mikal
Post published:September 30, 2014
Post category:OpenStack

This is mostly historical at this point, but I forgot to post it here when I emailed it a week or so ago. So, for future reference: I'd like another term as Compute PTL, if you'll have me. We live in interesting times. openstack has clearly gained a large amount of mind share in the open cloud marketplace, with Nova being a very commonly deployed component. Yet, we don't have a fantastic container solution, which is our biggest feature gap at this point. Worse -- we have a code base with a huge number of bugs filed against it, an unreliable gate because of subtle bugs in our code and interactions with other openstack code, and have a continued need to add features to stay relevant. These are hard problems to solve. Interestingly, I think the solution to these problems calls for a social approach, much like I argued for in my Juno PTL candidacy email. The problems we face aren't purely technical -- we need to work out how to pay down our technical debt without blocking all new features. We also need to ask for understanding and patience from those feature authors as we try and improve the…