The content here was a test of transferring Contrail 5.0.1 docs over to=
Github/rst content.
It is essentially raw content (ie. real content but interlinking not es=
tablished, etc.) .. intent was to stitch it together, but effort was abando=
ned
See below for possible AI here
API guide - currently on OC site, moving over to TF site
Just FYI, Juniper will now also host a version of these pages on junipe=
r.net/documentation
This may need a total overhaul, but it's one of the most frequently hit=
pages on opencontrail.org so we should at least move it to tf/docs for now=
and add a "hey, out of date; stay tuned" warning to the tf/docs version an=
d a redirect from opencontrail.org to the new tf/docs version.
Moving forward - Some options to consider (not mutually exclusive=
)
Center around community-created docs
Parking this for today
Leverage and transfer Juniper/Contrail docs to TF/Github
It may be an option to reuse the content-transfer model described above=
The tooling to do this exists
Would require 1) coordinating with Juniper's DigiEng team to transfer c=
ontent, and 2) resources to (re-)thread the raw content together to make a =
full working doc set
Link/point to Juniper/Contrail docs on juniper.net/documentation
Instead of setting up around TF-created docs, simply point to existing =
Contrail doc set
Clearly would not provide a true 'TF doc set', and there would be some =
details to figure out, but it would provide an instant ful=
l-coverage doc set
The TF site already points liberally to github.com/Juniper; In at least=
one case, a github.com/tungstenfabric/docs page points to=
juniper/net.documentation, ie. this is not a fully new premise
Action items
Review/merge mi=
nutes above with previous week, continue conversations