L7 capability extension implementation for lbaas v2

Bug #1551368 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Undecided
Unassigned
openstack-api-site
Invalid
Undecided
Unassigned
openstack-manuals
Invalid
Medium
Unassigned

Bug Description

https://review.openstack.org/148232
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.

commit 254190b3051453f823dbdf1826f1a6b984c57164
Author: Evgeny Fedoruk <email address hidden>
Date: Mon Jan 19 03:47:39 2015 -0800

    L7 capability extension implementation for lbaas v2

    Including extension modifications
    Including db model modifications
    Including alembic migration
    Including new driver managers for l7 rules and policies
    Inclufing logging_noop driver implementation
    Including unit testing
    Including Octavia driver updates

    DocImpact
    APIImpact
    Change-Id: I8f9535ebf28155adf43ebe046d2dbdfa86c4d81b
    Implements: blueprint lbaas-l7-rules
    Co-Authored-By: Evgeny Fedoruk <email address hidden>
    Co-Authored-By: Stephen Balukoff <email address hidden>

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Is there any operator/user documentation to be provided?

Revision history for this message
Stephen Balukoff (sbalukoff) wrote :

Yep, we plan on it!

Revision history for this message
Joseph Robinson (joseph-r-email) wrote :
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Medium
Chason Chan (chen-xing)
Changed in openstack-manuals:
assignee: nobody → Xing Chen (chen-xing)
Revision history for this message
Chason Chan (chen-xing) wrote :

@Joseph, can you give me more further information?

Revision history for this message
Stephen Balukoff (sbalukoff) wrote :

Xing-- are you going to work on updating this for the openstack manual then? If so, then as far as for more information:

The Octavia project also added this feature that works in essentially the same way (which makes sense given Octavia is the LBaaS v2 reference implementation). The updated API for Octavia describing all the L7 stuff is here: https://github.com/openstack/octavia/blob/master/doc/source/api/octaviaapi.rst

The Neutron API is exactly the same except for the fact that all the object interfaces are top-level interfaces in Neutron-LBaaS.

Further, for a description of how the L7 stuff is intended to work, there is this wiki page: https://wiki.openstack.org/wiki/Neutron/LBaaS/l7

I'm afraid as far as how to use the updated neutron CLI, we don't have any docs written-- your best bet here is to look at the following two files:
https://github.com/openstack/python-neutronclient/blob/master/neutronclient/neutron/v2_0/lb/v2/l7policy.py
https://github.com/openstack/python-neutronclient/blob/master/neutronclient/neutron/v2_0/lb/v2/l7rule.py

Please let me know whether you intend to write these docs, or whether I should do it (as a major contributor to the above code), eh!

Revision history for this message
Chason Chan (chen-xing) wrote :

 I find that I cannot complete these docs, Thanks, Stephen.

Changed in openstack-manuals:
assignee: Xing Chen (chen-xing) → Stephen Balukoff (sbalukoff)
Revision history for this message
Stephen Balukoff (sbalukoff) wrote :

Xing-- I have the knowledge of the new feature, but I have no idea how I go about updating the documentation for this. When I look in the neutron CLI reference in openstack-manual, as well as the API reference, I see a big notice at the top of these files that they are auto-generated. Does that mean I don't have to take any action to update these on my own, that they'll be updated by some automated process?

Also, I was told we are trying to move stuff that's in the wiki (like this: https://wiki.openstack.org/wiki/Neutron/LBaaS/l7 ) into the "official" openstack documentation. I understand that what's on that wiki page is for the most part a user guide... and I know we have several end-user guides. But I have no idea where I should go about inserting this information, especially given the fact that I can't seem to find anything else that is practical on neutron-lbaas in there either.

So if you're not going to do it, could you give me some pointers as to where I should insert this stuff into our OpenStack documentation structure, and how I go about doing it? (I'm very familiar with the gerrit review process, but totally unfamiliar with whatever tools are used to generate this documentation.)

Changed in neutron:
status: New → Invalid
Changed in openstack-api-site:
status: New → Confirmed
Changed in openstack-manuals:
assignee: Stephen Balukoff (sbalukoff) → nobody
Revision history for this message
Atsushi SAKAI (sakaia) wrote :

The API-Ref is changed from doc to each project (neutron)

Changed in neutron:
status: Invalid → Confirmed
Changed in openstack-api-site:
status: Confirmed → Invalid
Changed in openstack-manuals:
status: Confirmed → Invalid
Revision history for this message
Boden R (boden) wrote :

Marking this as incomplete with the following reasoning:
- The openstack-manuals team marked it as invalid and thus don't plan to update the docs/manuals.
- Unless we have someone willing to create/drive the change into the openstack-manuals, I don't see how this will get done.

If we have someone to work on it, please feel free to restore out of invalid state.

Changed in neutron:
status: Confirmed → Incomplete
status: Incomplete → Won't Fix
Revision history for this message
Boden R (boden) wrote :

Actually won't fix seems more fitting.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.