24a825848c
Definition of "Day-2": User can perform the operation post
the initial deployment.
Definition of "secondary": A secondary subcloud is just in the
DB, will not do any other operations like management/sync.
Update DB of subclouds add rehome_data column.
Update "dcmanager subcloud add --secondary" to save data for
day-2's rehome/migrate purpose.
Update "dcmanager subcloud update --bootstrap-address
--bootstrap-values" to save data for day-2's
rehome/migrate purpose.
Add "dcmanager subcloud migrate" for day-2's rehome/migrate
Example of usage:
dcmanager subcloud add --secondary --bootstrap-address \
128.224.115.15 --bootstrap-values ./sub1-bootsrapvalues.yml
dcmanager subcloud migrate sub1 --sysadmin-password PASSWORD
EQUALS TO:
dcmanager subcloud add --migrate --bootstrap-address \
123.123.123.123 --bootstrap-values ./sub1-bootsrapvalues.yml \
--sysadmin-password password
This commit updates the 'subcloud add' implementation to use
the 'secondary' subcloud deployment operations.
It saves rehome necessary data as JSON format into the
'subclouds' table's 'rehome_data' column in the DB.
Additionally, it adds the 'migrate' subcommand for
subcloud day-2's migration abilities.
Test Plan:
1. PASS - Verify that 'secondary' option works for 'subcloud add'
successfully.
2. PASS - Verify that 'bootstrap-values' could update
subclouds' rehome_data through api.
successfully.
3. PASS - Verify that 'bootstrap-address' could update
subclouds' rehome_data through api.
successfully.
4. PASS - Verify that 'migrate' command can migrate a 'secondary'
subclouds successfully.
5. PASS - Verify original subcloud add/update functionalities
successfully.
6. PASS - Verify 'subcloud add --secondary' can handle error
And set secondary-failed successfully.
7. PASS - Verify delete a 'secondary-failed' subcloud
successfully
CLI example:
dcmanager subcloud add --secondary --bootstrap-address 128.224.119.55 \
--bootstrap-values ./testsub.yml
dcmanager subcloud update testsub --bootstrap-address 128.224.119.55 \
--bootstrap-values ./testsub.yml
dcmanager subcloud migrate testsub --sysadmin-password PASSWORD
API use case:
PATCH /v1.0/subclouds/testsub/migrate
Story: 2010852
Task: 48503
Task: 48484
Change-Id: I9a308a4e2cc5057091ba195c4d05e9d1eb4a950c
Signed-off-by: Wang Tao <tao.wang@windriver.com>
|
||
|---|---|---|
| .. | ||
| controllers | ||
| policies | ||
| __init__.py | ||
| api_config.py | ||
| app.py | ||
| policy.py | ||
| README.rst | ||
api
DC Manager API is Web Server Gateway Interface (WSGI) application to receive and process API calls, including keystonemiddleware to do the authentication, parameter check and validation, convert API calls to job rpc message, and then send the job to DC Manager Manager through the queue. If the job will be processed by DC Manager Manager in synchronous way, the DC Manager API will wait for the response from the DC Manager Manager. Otherwise, the DC Manager API will send response to the API caller first, and then send the job to DC Manager Manager in asynchronous way.
Multiple DC Manager API could run in parallel, and also can work in multi-worker mode.
Multiple DC Manager API will be designed and run in stateless mode, persistent data will be accessed (read and write) from the DC Manager Database through the DAL module.
Setup and encapsulate the API WSGI app
- app.py:
-
Setup and encapsulate the API WSGI app, including integrate the keystonemiddleware app
- api_config.py:
-
API configuration loading and init
- enforcer.py
-
Enforces policies on the version2 APIs