Commit 507ff77b authored by Brandon Logan's avatar Brandon Logan

Hacking fixes in CONSTITUTION, ROADMAP, & HACKING

Change-Id: I6f075284731139cd9611938178ee998ad3a075c0
parent 3324e121
......@@ -30,9 +30,9 @@ Octavia VM images might be replaced by a vendor's proprietary VM image.)
Rather, it means that:
* The reference implementation should always be open source and unencumbered.
* We are typically not interested in making design compromises in order to work
with a vendor's proprietary product. If a vendor wants to develop a component
for Octavia, then the vendor should bend to Octavia's needs, not the other
way around.
with a vendor's proprietary product. If a vendor wants to develop a component
for Octavia, then the vendor should bend to Octavia's needs, not the other
way around.
Octavia is a load balancer for large operators
----------------------------------------------
......
Octavia Style Commandments
=======================
==========================
This project was ultimately spawned from work done on the Neutron project.
As such, we tend to follow Neutron conventions regarding coding style.
......@@ -7,7 +7,7 @@ As such, we tend to follow Neutron conventions regarding coding style.
http://docs.openstack.org/developer/hacking/
Octavia Specific Commandments
--------------------------
-----------------------------
- [N320] Validate that LOG messages, except debug ones, have translations
......
......@@ -32,10 +32,10 @@ Neutron LBaaS progress:
Octavia progress:
* Consensus on:
* Constitution
* Road map
* Component design
* APIs
** Constitution
** Road map
** Component design
** APIs
* Initial code underway (perhaps alpha release?)
......@@ -59,12 +59,12 @@ Octavia progress:
* Horizon UI for operators
* Neutron LBaaS driver interface for Octavia
* Non-voting Neutron third-party CI for Octavia to ensure Neutron code changes
don't break Octavia
don't break Octavia
* Command-and-control layer handles:
* Octavia VM lifecycle maangement
* Octavia VM monitoring
* Octavia VM command and control
* Neutron LBaaS service deployment
** Octavia VM lifecycle maangement
** Octavia VM monitoring
** Octavia VM command and control
** Neutron LBaaS service deployment
* Resilient topologies for Octavia VMs (ie. HA for the VMs)
* "Experimental" project status
......@@ -93,7 +93,7 @@ OpenStack release target: ???
Octavia progress:
* "Two layer" load balancing topology implemented where layers 1-4 handled by
routing infrastructure, and 4-7 handled by Octavia VMs acting in parallel.
routing infrastructure, and 4-7 handled by Octavia VMs acting in parallel.
* Improvements to Horizon UI for operators
......@@ -104,13 +104,13 @@ Short-term timeline
Highest priority:
* See Neutron LBaaS work scheduled for Juno through to completion.
* Import google docs describing v0.5, v1.0 and v2.0 Octavia into specs folder
of this repository
of this repository
* Get reviews and consensus on the same
Medium priority:
* Define and document Octavia VM <=> Controller RESTful APIs
* Define best practices for credential management between Octavia VM and
controllers (suggested: bi-direction server / client certificat verification)
controllers (suggested: bi-direction server / client certificat verification)
* Collect requirements for Operator API
* Start work on Octavia VM image
* Start work on Octavia VM agent
......@@ -118,12 +118,12 @@ Medium priority:
* Create Neutron LBaaS driver for Octavia
* Get Octavia to work in devstack
* Flesh out the above items with more detailed checklists as work commences on
them
them
Lower priority:
* Create mock-ups of and start coding Horizon UI for Octavia operators
* Create non-voting CI interface for testing changes relating to Octavia in
gerrit
gerrit
============================
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment