Commit Graph

8 Commits

Author SHA1 Message Date
Takashi NATSUME 09d24e5ffa doc: Add links to novaclient contributor guide
Add links to the document for adding a new microversion support
in python-novaclient.

Depends-On: https://review.opendev.org/667002
Change-Id: Ic58afe401464a0da2b19306e7cc6ce412f177b16
2019-07-09 17:33:47 -04:00
zhufl 84afd12589 Change some URLs to point to better targets
This is to change some URLs to point to better or more accurate targets.

Change-Id: I1d450ba8bd2271a69f9380cc4d2b36ae3eefe09a
2019-05-13 00:52:23 +00:00
Jenkins 8a1a7c1531 Merge "Amend the code review guide for microversion API" 2017-09-08 18:12:20 +00:00
Takashi NATSUME fe933acfc8 Amend the code review guide for microversion API
A new patch for the microversion API change in python-novaclient side
should be submitted before the microversion change in Nova is merged.

Change-Id: Ie8868a2e767825e08ae4a2e1bfffa7b3fbfb7273
2017-08-16 20:18:29 +09:00
Matt Riedemann 8ab41c83a8 doc: code review considerations for online data migrations
Online data migrations that move something from the cell database
to the API database typically create new things in the API DB and
on a query, look in the API DB first and then fallback to the cell
database. We started supporting multiple cells in Pike, so any online
data migrations that move things to the API DB after that will need
to be multi-cell aware for the fallback lookup code.

This just adds a reminder in the code review guide.

Change-Id: If0d7d9b80e336b696aaf87ec13ac18daa1068357
2017-08-08 15:06:17 -04:00
Sean Dague 12c0a66657 Fix list rendering in code-review.rst
Sub lists have to be indented exactly 2 additional spaces from their
parent, otherwise it is treated as a blockquote, which isn't what we
want.

Part of bp: doc-migration

Change-Id: Iab46b5e39e4bd0d154f33dc795f24362c77a88a5
2017-08-03 07:45:25 -04:00
Stephen Finucane 83e7763518 doc: Populate the 'reference' section
Per the spec [1]:

  reference/ – any reference information associated with a project that
  is not covered by one of the above categories. Library projects should
  place their automatically generated class documentation here.

There are a couple of documents that focus on nova internals, but won't
necessarily be applicable to user. These are moved here.

[1] specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration

Change-Id: I94614c2383329e1fbed60d9c5aca3fab5170ef8f
2017-07-18 15:41:20 +01:00
Stephen Finucane a2165cf651 doc: Populate the 'contributor' section
Per the spec [1]:

  contributor/ – anything related to contributing to the project or how
  the team is managed. Applies to some of the current content under
  /developer, we are changing the name to emphasize that not all
  contributors are developers and sometimes developers are users but not
  contributors.

We currently have a handful of docs that focus on the "how to develop or
contribute" aspects of nova, and these are moved. Docs that focus on
architecture or design decisions for nova are not moved, as these will
go into 'reference'.

A TODO is added to the former 'api_plugins' document as it's mega
out-of-date and needs some serious work.

[1] specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration

Change-Id: Iad770688b4eafeb9caa710b4398b02d80a017a70
2017-07-18 15:41:19 +01:00