openstack/tacker
Code Issues Proposed changes

Fix tacker doc reference links

Browse Source 
This fixes also the wrong MANO reference.

Change-Id: Ib6eac344e9d48b33a1ebf45f1ddb68e5cf55ea49
Closes-bug: 1515147
This commit is contained in:
gong yong sheng 2015-11-11 16:56:09 +08:00
parent 351ca2b629
commit 447ed4a394
3 changed files with 15 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/devref/mano_api.rst
View File

@ -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 <http://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/01.01.01_60/gs_nfv-man001v010101p.pdf>`_

2
doc/source/index.rst
View File

@ -75,6 +75,4 @@ Developer Info
Indices and tables
------------------
* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`

16
doc/source/policies/dev-process.rst
View File

@ -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/