List view

• v0.1.8

  This is the second "heartbeat" milestone. Heartbeats occur every 2 weeks. During a heartbeat release all PRs that have been accepted into the release are formally merged into the release branch. Priorities:

  Due by June 17, 2016

  •19/20 issues closed
  95% complete1 open19 closed

• v0.1.7

  This is the first "heartbeat" milestone. Heartbeats occur every 2 weeks. During a heartbeat release all PRs that have been accepted into the release are formally merged into the release branch. Priorities: * support for clustering * support for ssl termination

  Due by June 3, 2016

  •14/14 issues closed
  100% complete0 open14 closed

• L2/3 Insertion

  No due date
  0% complete0 open0 closed

• Clustering Support

  No due date
  0% complete0 open0 closed

• LBaaSv2 HTTPS Support

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• v0.1.3

  Due by April 1, 2016

  •26/26 issues closed
  100% complete0 open26 closed

• v0.2.1

  Feature release for additional objects and clustering functionality.

  Due by April 15, 2016

  •2/2 issues closed
  100% complete0 open2 closed

• v0.1.2

  Maintenance release for v0.1 branch.

  Due by April 1, 2016

  •18/18 issues closed
  100% complete0 open18 closed

• Release 0.1.1-alpha3

  #### LBaaSv2 and Heat support * All LBaaSv2 and Heat objects * Refactor of the Cluster functionality * SOAP methods converted to REST

  Due by March 18, 2016

  •31/31 issues closed
  100% complete0 open31 closed

• Release 0.1.1-alpha2

  * dramatic expansion of unittest coverage * all functional tests pass, or marked as non-passing * tutorial draft complete * at least 1 more demoable use-case from 0.1.1-alpha1

  Due by February 4, 2016

  •1/1 issues closed
  100% complete0 open1 closed

• Release 0.1.1-alpha1

  * complete (auto-generated object representation of server URIs) * POC use case demonstration using this library

  Due by January 29, 2016

  •43/43 issues closed
  100% complete0 open43 closed

• v0.1.1

  Initial release of the common code * Dynamic attributes * Object/addtribute representation of the F5 iControl REST API

  Due by March 11, 2016

  •37/37 issues closed
  100% complete0 open37 closed

• Object Reprs of Resources

  I believe it's actually part of the definition of a RESTful interface for the client to represent the server provided resources as objects. In any event, we are prototyping an architecture that has that property. From PR #80 @swormke: "see if we can make something sane for a few more complex objects. I suggest this order: f5/bigip/ltm/nat.py f5/bigip/ltm/pool.py f5/bigip/ltm/virtual_server.py We also need to do something with objects that use the SOAP session as well."

  No due date

  •40/40 issues closed
  100% complete0 open40 closed

• Code Refactor

  Make the prototype code in the f5-common-python codebase into solid, high-quality, modular, tested, general, production-ready 0ssmness...

  No due date

  •2/2 issues closed
  100% complete0 open2 closed