Browse Source

Remove valence-integration.rst

As we discussed during the Queens PTG, valence-integration spec
should be removed, as we changed to use rsd-lib for RSD server
support.

Change-Id: I7fb50a7777ecaa5288dacbcc51d41830c5bb483a
Zhenguo Niu 1 year ago
parent
commit
139f5a0fd1
1 changed files with 0 additions and 176 deletions
  1. 0
    176
      specs/pike/approved/valence-integration.rst

+ 0
- 176
specs/pike/approved/valence-integration.rst View File

@@ -1,176 +0,0 @@
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
-Valence Integration
9
-===================
10
-
11
-https://blueprints.launchpad.net/mogan/+spec/rsd-integration
12
-
13
-The current Mogan implementation only supports pre-set configuration servers.
14
-For custom servers, Mogan should to be able to compose bare metal through
15
-integration with Valence that leverages the Redfish API to compose nodes using
16
-disaggregated resources.
17
-
18
-
19
-Problem description
20
-===================
21
-
22
-Mogan currently can only provision pre-set configuration servers, but users may
23
-want to request a custom server with specific configurations like CPU, RAM, and
24
-DISK.
25
-
26
-Use Cases
27
----------
28
-
29
-* An enterprise user wants to manage the RSD and general servers in a
30
-unified manner.
31
-
32
-* An enterprise user wants to apply a custom server with CPU, RAM, and DISK
33
-specified himself.
34
-
35
-
36
-Proposed change
37
-===============
38
-
39
-First, we need to refactor our flavor to pass Valence required parameters when
40
-composing a node, need to align with Valence team. But for non-rack servers
41
-we can keep the current way of scheduling a node to provision.
42
-
43
-When a request come with the Valence specific flavor, We can invoke Valence to
44
-compose the node on the fly, then register the composed node into Ironic with
45
-Redfish driver(not supported yet). When nodes are enrolled in Ironic, there's
46
-no difference with non-rack nodes. And these works are all done before the
47
-current instance create workflow, so we can create a new taskflow [1]_ for
48
-Valence which includes compose and enroll tasks:
49
-
50
-ComposeNodeTask:
51
-* execute: Invoke Valence to compose a node according the specified flavor.
52
-* revert: Release the composed node if there's something wrong when enrolling.
53
-
54
-EnrollNodeTask:
55
-* execute: Enroll the composed node to Ironic.
56
-* revert: If some exception raised and the node has been enrolled, need to
57
-remove it from Ironic.
58
-
59
-For Valence node, we should skip the scheduling task in provison workflow.
60
-Currently there are ScheduleCreateInstanceTask and OnFailureRescheduleTask,
61
-we can get rid of these two tasks when initialize the task flow in Valence
62
-scenario. Or maybe can handle this like select which node instances are
63
-launched(not supported yet).
64
-
65
-Also, if there's some exception raised when provisioning, we should release the
66
-composed node to Valence pool and remove it from Ironic.
67
-
68
-When deleting a node we should remove it from ironic first, then release the
69
-resources to Valence pool. For this, we can add a new field to instance to
70
-indicate whether it's a valence instance or not.
71
-
72
-
73
-Alternatives
74
-------------
75
-
76
-It will automatically invoke valence to compose node if scheduling max attempts
77
-exceeds instead of using a specific flavor to indicate it's a Valence instance.
78
-
79
-Data model impact
80
------------------
81
-
82
-The proposed change will be add the following fields to the instance object
83
-with their data type and default value for migrations.
84
-
85
-+-----------------------+--------------+-----------------+
86
-| Field Name            | Field Type   | Migration Value |
87
-+=======================+==============+=================+
88
-| composed              | bool         | None            |
89
-+-----------------------+--------------+-----------------+
90
-
91
-
92
-REST API impact
93
----------------
94
-
95
-None
96
-
97
-Security impact
98
----------------
99
-
100
-None
101
-
102
-Notifications impact
103
---------------------
104
-
105
-None
106
-
107
-Other end user impact
108
----------------------
109
-
110
-None
111
-
112
-Performance Impact
113
-------------------
114
-
115
-There's one potential performance impact on the instance creating process,
116
-as we need to composing the node from Valence first.
117
-
118
-Other deployer impact
119
----------------------
120
-
121
-None
122
-
123
-Developer impact
124
-----------------
125
-
126
-* As Mogan plans to support not only Ironic driver but also CloudBoot, need
127
-to figure out whether CloudBoot has supported Redfish already or there's not
128
-a plan to support it.
129
-
130
-
131
-Implementation
132
-==============
133
-
134
-Assignee(s)
135
------------
136
-
137
-Primary assignee:
138
-  <niu-zglinux>
139
-
140
-Work Items
141
-----------
142
-
143
-* Refactor flavor(instance type) to meet Valence's requirements.
144
-* Add `composed` filed to instance object.
145
-* Add a new taskflow for node composing and enrolling.
146
-* Change delete instance process to handle composed node gracefully.
147
-* Add Valence installation in Mogan devstack plugin as an option
148
-
149
-Dependencies
150
-============
151
-
152
-* Need valence client to be ready to integrate.
153
-
154
-* Redfish driver landed in ironic.
155
-
156
-* Valence PodManager simulator need to be improved, maybe return a fake
157
-node(VM) and maybe we can test it with ssh driver before Redfish driver
158
-available.
159
-
160
-
161
-Testing
162
-=======
163
-
164
-Unit Testing will be added.
165
-
166
-Documentation Impact
167
-====================
168
-
169
-Docs about Valence integration will be added.
170
-
171
-References
172
-==========
173
-
174
-.. [1] https://wiki.openstack.org/wiki/TaskFlow
175
-
176
-* https://wiki.openstack.org/wiki/Valence

Loading…
Cancel
Save