Currently the title for the octavia docs page is "Main".
This updates the title to be more descriptive.
This patch also updates the index for Anchor documentation and
our version 1.0 specs.
Change-Id: I1258503b7a778789b77c7ec6c4db1fbd310b6133
Octavia has no quota definitions, but needs them for parity with Neutron LBaaS.
This will provide an endpoint and support for retrieving, updating, and deleting
quotas for projects, as well as adding enforcement of those those quotas.
Adds scenario test that simply validates quotas in a lb graph.
Co-Authored-By: Michael Johnson <johnsomor@gmail.com>
Co-Authored-By: Phillip Toohill <phillip.toohill@rackspace.com>
Co-Authored-By: Adam Harwell <flux.adam@gmail.com>
Change-Id: Ia1d85dcd931a57a2fa3f6276d3fe6dabfeadd15e
Closes-Bug: #1596652
While Octavia is capable of doing many things, we presently lack a
simple, straight-forward guide for doing some of the simpler end-user
tasks with load balancing. This commit adds just such a guide.
Change-Id: I30628484893ae9c043e5833f480b99d185e4d362
Closes-Bug: #1558372
Octavia is currently missing any documentation designed to help
new developers and operators understand what we're doing with the project
or how to get started using and contributing to it. This patch set aims
to correct this problem.
Co-Authored-By: Michael Johnson <johnsomor@gmail.com>
Co-Authored-By: Leslie Lundquist <llundquist@us.ibm.com>
Closes-Bug: #1558368
Change-Id: Idaa37277bd342b644a463d4a0884ea40c2e8d4f5
This includes both an overall description of L7 load balancing as
implemented in Octavia, as well as a cookbook for common L7 usage.
Both of these documents are aimed at end-users.
Change-Id: I01c4484e2276257c97cfb6ba02d6224a25cdbc80
Closes-Bug: 1558377
This patch updates Octavia docs to use the oslo_config.sphinxext
integration to generate the configuration reference.
This patch also links in the "guru meditation report" document.
This document has been present, but was not linked.
I also reorganized the specs to reflect the correct release versions.
Change-Id: Icaf710c1c61277f3ca51efac45a3a80a0d3cce8f
Octavia extensively uses TaskFlow flows for orchestration.
To make it easier for developers to understand these flows,
this patch adds a mechanism for generating graphviz representations
of the key Octavia TaskFlow flows.
It also updates our tox docs task to generate this documentation.
This patch depends on a fix to the TaskFlow export_to_dot method.
Added into conf.py as first step of configuration
Closes-Bug: #1561063
Change-Id: I914e1c062b400148565def37ccf618b3d2ea2573
Depends-On: I99f87af0b2bed959fcb43ef611b3186e23bd9549
This patch moves the Octavia configuration option documentation
into the Octavia repository. The OpenStack docs team deleted
this documentation from the Mitaka release[1]. The Octavia
team finds value in this documentation so we are moving it into
our repository.
[1] https://review.openstack.org/#/c/259889/
Change-Id: I4fcc2a7dc8fa3ef343456d98202ea7d4f9cd1289
This restructuring should hopefully make better sense of the
documentation currently available. This is in preparation for
bringing the version 0.5 component documentation up to date and
adding a getting started and installation guide.
Change-Id: Ie1e27bab4d2b8d7d033f75750fda842dd9dd3de7
Contains the specification of the initial version of
the haproxy amphora RESTful API. Note that this is likely
to be expanded upon later as amphora lifecycle concerns and
network integration strategy become more concrete.
Implements: bp/appliance-api
Change-Id: Iecc2149c5c89fbdc98a3657f32940b30c8169fdb
Along with defining terms, this commit cleans up some of the documentation
structure so the auto-generated docs are a bit cleaner.
Change-Id: I6445f86a6746956d8227d2a587509fe08b27d26d
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
Every repo needs a first commit, eh? Most of this
is based on the neutron and neutron-specs project layouts.
Change-Id: I17a41fc30f8f8499c679afad14019c0755582bc6
