Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-24 Thread Akihiro Motoki
2017-07-24 23:44 GMT+09:00 Doug Hellmann : > Excerpts from Kevin Benton's message of 2017-07-23 14:19:51 -0700: >> Yeah, the networking guide does include configuration for some of the >> sub-projects (e.g. BGP is at [1]). For the remaining ones there is work >> that needs to be done because their

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-24 Thread Doug Hellmann
Excerpts from Kevin Benton's message of 2017-07-23 14:19:51 -0700: > Yeah, the networking guide does include configuration for some of the > sub-projects (e.g. BGP is at [1]). For the remaining ones there is work > that needs to be done because their docs live in wiki pages. > > 1. > https://docs.

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-23 Thread Kevin Benton
Yeah, the networking guide does include configuration for some of the sub-projects (e.g. BGP is at [1]). For the remaining ones there is work that needs to be done because their docs live in wiki pages. 1. https://docs.openstack.org/ocata/networking-guide/config-bgp-dynamic-routing.html On Sun,

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-23 Thread Anne Gentle
On Sat, Jul 22, 2017 at 12:13 PM, Akihiro Motoki wrote: > Hi, > > I have a question on admin/ document related to the networking guide > and would like to have advices from the documentation experts. > > It seems the check site by Doug expect all project have admin/ page. > In the case of neutron

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-23 Thread Doug Hellmann
Excerpts from Kevin Benton's message of 2017-07-23 01:31:25 -0700: > Yeah, I was just thinking it makes it more explicit that we haven't just > skipped doing an admin guide for a particular project. Sure, you can do that. I don't think we want to link to all of those pages from the list of admin g

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-23 Thread Kevin Benton
Yeah, I was just thinking it makes it more explicit that we haven't just skipped doing an admin guide for a particular project. On Sun, Jul 23, 2017 at 1:18 AM, Andreas Jaeger wrote: > On 07/22/2017 11:44 PM, Kevin Benton wrote: > >> Could we just put a placeholder in those subprojects /admin di

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-23 Thread Andreas Jaeger
On 07/22/2017 11:44 PM, Kevin Benton wrote: Could we just put a placeholder in those subprojects /admin directories that redirects to the networking guide? You mean a single page that basically says : All information is covered in the `Networking Guide

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-22 Thread Kevin Benton
Could we just put a placeholder in those subprojects /admin directories that redirects to the networking guide? On Sat, Jul 22, 2017 at 10:50 AM, Doug Hellmann wrote: > Excerpts from Akihiro Motoki's message of 2017-07-23 02:13:40 +0900: > > Hi, > > > > I have a question on admin/ document relat

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-22 Thread Doug Hellmann
Excerpts from Akihiro Motoki's message of 2017-07-23 02:13:40 +0900: > Hi, > > I have a question on admin/ document related to the networking guide > and would like to have advices from the documentation experts. > > It seems the check site by Doug expect all project have admin/ page. > In the ca

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-22 Thread Akihiro Motoki
Hi, I have a question on admin/ document related to the networking guide and would like to have advices from the documentation experts. It seems the check site by Doug expect all project have admin/ page. In the case of neutron the situation is a bit special. We have the networking guide as admin