OpenStack Developer Activity Weekly Review

 

January 7, 2011

Many people have asked for more insight into the developer activities for OpenStack as the large number of code changes and proposals make it difficult to monitor everything happening. In hopes of exposing more of the developer activities, I plan to post a weekly or biweekly blog post on the latest development activities. If you have any ideas for this blog post, please email me at [email protected]. I am always ready to listen to the community for new ideas.

Activitites

  • Branch Merge Proposal Freeze (January 6, 2011) – Only impacts branches introducing new features or changes in expected behavior; not branches fixing bugs. To submit a new feature you must follow the exception process found at http://wiki.openstack.org/BranchMergeProposalFreeze
  • Feature Freeze for Bexar scheduled for January 13th

Developer Mailing List (archive: https://lists.launchpad.net/openstack/)

  • BZR Plugin – Josh Kearney has created a plugin (https://github.com/jk0/bzr-pre-commit-hook) to ensure that PEP8 and unit tests are run automatically when submitting code
  • OpenStack Programming Model Framework – John Purrier has proposed (https://lists.launchpad.net/openstack/msg00225.html)  a model where developers will  interact with the OpenStack services will not interact directly with the service API’s, but rather will have a set of published language bindings that define the programming model. This does not preclude direct service calls, but this will be discouraged in favor of using the bindings. The bindings will be considered the “Nova API” for all intents and purposes. Further discussion on this issue led to the community not being in favor of the idea of only using language bindings for developers as there is no guarantee that a specific language binding would be available for a specific release.
  • OpenStack API Discussion – John Purrier has posted (https://lists.launchpad.net/openstack/msg00181.html) some comments on the OpenStack API discussing availability for Bexar and/0r Cactus release which also prompted the community focus on what the internal APIs are for OpenStack developers and what the external APIs are for  ecosystem developers to leverage. The current naming is devAPI for internal OpenStack development and OpenStack API for people creating solutions around OpenStack. Please note, naming of the internal devAPI is subject to change. Further details on OpenStack API for Bexar can be found at https://blueprints.launchpad.net/nova/+spec/openstack-api-parity.

For the latest on development activities on OpenStack please check these sites for more details:

Tags:

Leave a Reply

Your email address will not be published. Required fields are marked *