From 447ed4a394650ea597e29559600e668ccfa6e6fc Mon Sep 17 00:00:00 2001 From: gong yong sheng Date: Wed, 11 Nov 2015 16:56:09 +0800 Subject: [PATCH] Fix tacker doc reference links This fixes also the wrong MANO reference. Change-Id: Ib6eac344e9d48b33a1ebf45f1ddb68e5cf55ea49 Closes-bug: 1515147 --- doc/source/devref/mano_api.rst | 8 +++++++- doc/source/index.rst | 2 -- doc/source/policies/dev-process.rst | 16 ++++++++-------- 3 files changed, 15 insertions(+), 11 deletions(-) diff --git a/doc/source/devref/mano_api.rst b/doc/source/devref/mano_api.rst index 0a65be3b0..268a110ac 100644 --- a/doc/source/devref/mano_api.rst +++ b/doc/source/devref/mano_api.rst @@ -3,7 +3,8 @@ Tacker MANO API Overview ************************ Tacker MANO API introduces new REST API end-points based on ETSI NFV MANO -standards [1]. The two new resources introduced are 'vnfd' and 'vnf' for +standards[#]_. +The two new resources introduced are 'vnfd' and 'vnf' for describing the 'vnfm' extension. The resources request and response formats are described in below sections. @@ -277,3 +278,8 @@ Update vnf - Update a vnf based on user config file or data. **DELETE /v1.0/vnfs/{vnf_id}** Delete vnf - Deletes a specified vnf_id from the VNF list. + +References +========== + +.. [#] `ETSI NFV MANO `_ diff --git a/doc/source/index.rst b/doc/source/index.rst index 15450bff9..f3610404f 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -75,6 +75,4 @@ Developer Info Indices and tables ------------------ -* :ref:`genindex` -* :ref:`modindex` * :ref:`search` diff --git a/doc/source/policies/dev-process.rst b/doc/source/policies/dev-process.rst index 33caaeb84..fac79b6ca 100644 --- a/doc/source/policies/dev-process.rst +++ b/doc/source/policies/dev-process.rst @@ -9,7 +9,7 @@ Request for Enhancement (RFE) Process ===================================== The developer, or an operator, can write up the requested enhancement in a -Tacker launchpad [1] bug. +Tacker launchpad [#]_ bug. * The requester need to mark the bug with "RFE" tag. * The bug will be in the initial "New" state. @@ -32,11 +32,11 @@ Blueprint and Tacker-Specs process ================================== The developer, or an operator, can write up the requested enhancement by -submitting a patchset to the tacker-spec repository [2]. +submitting a patchset to the tacker-spec repository [#]_. -* The patchset should follow the template specified in [3] +* The patchset should follow the template specified in [#]_ * The requester should also create a corresponding blueprint for the - enhancement proposal in launchpad [4] + enhancement proposal in launchpad [#]_ * The requester and the team will have a discussion on the tacker-spec writeup using gerrit. * The patchset will be merged into the tackers-specs repository if the @@ -57,7 +57,7 @@ significant code-changes (LOC), community discussions and debates. References ========== -[1] https://bugs.launchpad.net/tacker -[2] https://github.com/openstack/tacker-specs -[3] https://github.com/openstack/tacker-specs/blob/master/specs/template.rst -[4] https://blueprints.launchpad.net/tacker/ +.. [#] https://bugs.launchpad.net/tacker +.. [#] https://github.com/openstack/tacker-specs +.. [#] https://github.com/openstack/tacker-specs/blob/master/specs/template.rst +.. [#] https://blueprints.launchpad.net/tacker/