Per the discussion in the 12-Nov-2014 openstack octavia meeting, remove
the definition of start(), stop(), suspend(), resume(), and backup().
Change-Id: Iefc9c295ec5188b871681ff1804b563ac4feff32
Here we define the overall strategy for dealing with secure TLS data
in Octavia. There are several areas that need attention, and they are
detailed in this spec. Barbican will be our default secure storage and
certificate signing service, but the interfaces should remain generic.
Sequence diagrams now included.
Change-Id: Icbbea8e37af0ce13fd959543403f2b01b8c7d17b
Implements: blueprint tls-data-security
This design represents the overall layout of components that will
make up the first major milestone release of Octavia (v0.5). The
intent here is to have a scalable service delivery layer, to get
communication with external components right, and not yet worry
about making the command and control layer scalable.
Change-Id: I09ab7185683b66ec2567119616bc54cf9d8cc000
This commit adds documentation around project direction and conventions.
Additionally, I've added doc8 checks to make sure or .rst and .txt files
in this repository follow good conventions, and fixed a check related to
graphviz external .dot files.
Change-Id: I1b73b3839b86198f3d56587ca3fb2644dc231f00
Every repo needs a first commit, eh? Most of this
is based on the neutron and neutron-specs project layouts.
Change-Id: I17a41fc30f8f8499c679afad14019c0755582bc6