Reviewed: https://review.openstack.org/503052 Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=1b4ce7a7e3a5b1d0c46e629cc9f939ee318b1769 Submitter: Jenkins Branch: master
commit 1b4ce7a7e3a5b1d0c46e629cc9f939ee318b1769 Author: Boden R <[email protected]> Date: Tue Sep 12 09:54:33 2017 -0600 finish routes api ref Our API ref for 'routes' was missing some sample route objects in request/response JSON samples, as well as documenting the fact that routes can be updated with PUT requests on routers. Change-Id: I50f6d8193163586ab6f4f3bf61830fc9407ff7a2 Closes-Bug: #1564887 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1564887 Title: [api-ref]Neutron v2 Layer-3 extension - `routes` attribute not helpful Status in neutron: Fix Released Bug description: In all the router responses, you see a `routes` attribute. This is the explanation for it: routes plain xsd:list The extra routes configuration for L3 router. 1. What exactly is the structure of this value? "xsd:list" means nothing to me. Are there nested objects, nested strings? 2. The description doesn't explain how a route functions. Also, how do routes get set on routers? It's not included as an input param for POST or PUT operations. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1564887/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
