Browse Source

Merge "Added spec template, and refactored dir layout"

Jenkins 2 years ago
parent
commit
0cc158a9f6

+ 1
- 0
specs/ocata/ocata-template.rst View File

@@ -0,0 +1 @@
1
+../templates/ocata-template.rst

specs/implemented/async-container-operation.rst → specs/pre-ocata/implemented/async-container-operation.rst View File


specs/implemented/bay-drivers.rst → specs/pre-ocata/implemented/bay-drivers.rst View File


specs/implemented/container-networking-model.rst → specs/pre-ocata/implemented/container-networking-model.rst View File


specs/implemented/container-volume-integration-model.rst → specs/pre-ocata/implemented/container-volume-integration-model.rst View File


specs/implemented/containers-service.rst → specs/pre-ocata/implemented/containers-service.rst View File


specs/implemented/create-trustee-user-for-each-bay.rst → specs/pre-ocata/implemented/create-trustee-user-for-each-bay.rst View File


specs/implemented/magnum-horizon-plugin.rst → specs/pre-ocata/implemented/magnum-horizon-plugin.rst View File


specs/implemented/open-dcos.rst → specs/pre-ocata/implemented/open-dcos.rst View File


specs/implemented/resource-quotas.rst → specs/pre-ocata/implemented/resource-quotas.rst View File


specs/implemented/tls-support-magnum.rst → specs/pre-ocata/implemented/tls-support-magnum.rst View File


+ 101
- 0
specs/templates/ocata-template.rst View File

@@ -0,0 +1,101 @@
1
+..
2
+   This work is licensed under a Creative Commons Attribution 3.0 Unported
3
+ License.
4
+
5
+ http://creativecommons.org/licenses/by/3.0/legalcode
6
+
7
+..
8
+   This template should be in ReSTructured text. The filename in the git
9
+ repository should match the launchpad URL, for example a URL of
10
+ https://blueprints.launchpad.net/magnum/+spec/awesome-thing should be named
11
+ awesome-thing.rst .  Please do not delete any of the sections in this
12
+ template.  If you have nothing to say for a whole section, just write: None
13
+ For help with syntax, see http://sphinx-doc.org/rest.html
14
+ To test out your formatting, see http://www.tele3.cz/jbar/rest/rest.html
15
+
16
+===========================
17
+The title of your blueprint
18
+===========================
19
+
20
+Include the URL of your launchpad blueprint:
21
+
22
+https://blueprints.launchpad.net/magnum/+spec/example
23
+
24
+Introduction paragraph -- why are we doing anything?
25
+
26
+Problem description
27
+===================
28
+
29
+A detailed description of the problem.
30
+
31
+Proposed change
32
+===============
33
+
34
+Here is where you cover the change you propose to make in detail. How do you
35
+propose to solve this problem?
36
+
37
+If this is one part of a larger effort make it clear where this piece ends. In
38
+other words, what's the scope of this effort?
39
+
40
+Include where in the magnum tree hierarchy this will reside.
41
+
42
+If your specification proposes any changes to the Magnum REST API such
43
+as changing parameters which can be returned or accepted, or even
44
+the semantics of what happens when a client calls into the API, then
45
+you should add the APIImpact flag to the commit message. Specifications with
46
+the APIImpact flag can be found with the following query:
47
+
48
+https://review.openstack.org/#/q/status:open+project:openstack/magnum-specs+message:apiimpact,n,z
49
+
50
+Alternatives
51
+------------
52
+
53
+This is an optional section, where it does apply we'd just like a demonstration
54
+that some thought has been put into why the proposed approach is the best one.
55
+
56
+Implementation
57
+==============
58
+
59
+Assignee(s)
60
+-----------
61
+
62
+Who is leading the writing of the code? Or is this a blueprint where you're
63
+throwing it out there to see who picks it up?
64
+
65
+If more than one person is working on the implementation, please designate the
66
+primary author and contact.
67
+
68
+Primary assignee:
69
+  <launchpad-id or None>
70
+
71
+Can optionally can list additional ids if they intend on doing
72
+substantial implementation work on this blueprint.
73
+
74
+Milestones
75
+----------
76
+
77
+Target Milestone for completion:
78
+  ocata-1
79
+
80
+Work Items
81
+----------
82
+
83
+Work items or tasks -- break the feature up into the things that need to be
84
+done to implement it. Those parts might end up being done by different people,
85
+but we're mostly trying to understand the timeline for implementation.
86
+
87
+
88
+Dependencies
89
+============
90
+
91
+- Include specific references to specs and/or blueprints in magnum, or in other
92
+  projects, that this one either depends on or is related to.
93
+
94
+- Does this feature require any new library dependencies or code otherwise not
95
+  included in OpenStack? Or does it depend on a specific version of library?
96
+
97
+Security Impact
98
+===============
99
+
100
+- Include a description of how this change will affect the security posture of 
101
+  Magnum, or the configuration of the COE's it provides.

Loading…
Cancel
Save