This commit is part of a series to retire the Packaging Deb
project. Step 2 is to remove all content from the project
repos, replacing it with a README notification where to find
ongoing work, and how to recover the repo if needed at some
future point (as in
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project).
Change-Id: Ie7dcd09d7c9bcb7a2a8990bab657e64ead021458
1. add config field in request and response.
2. add dependents field in response
Change-Id: I70a4fbbb360b6bf7f83b87712d0f50104771f7dd
Depends-On: Ibc2845633dc35e7c789578237bb219017f814c50
1. 'preview' is not necessary for adopt in API level, if need, we
can set it node_adopt function in senlin-engin level.
2. disk_config of server may be None, but AUTO_DISJ_CONFIG is
boolean.
3. bdm of server may be None, but BLOCK_DEVICE_MAPPING is list.
4. config_drive of server may be empty string or None, but
CONFIG_DRIVE is boolean.
Change-Id: I76c0d689d7124f70af915f1e3c14c737314fd47f
Closes-Bug: #1705168
this patch revises lb policy to handle node_recover action:
1. node is not member of lb pool, will add it to lb pool
2. node is already member of lb pool, but the recovery action is not
'RECREATE', do nothing
3. node is already member of lb pool, and the recovery action is
'RECREATE', need to remove it from lb pool and then add it to it
since the ip of the resource has already been changed.
Change-Id: I69fe9ca8e646682333b65f8c90dc1cf245153622
When do cluster operations, Cluster.load function given wrong
param 'db_cluster'.
Change-Id: I4b32165394fc24e0905f04dadc2b886150973bf1
Closes-Bug: #1704079
As part of the docs migration work[0] for Pike we need to switch to use
the openstackdocstheme.
[0]https://review.openstack.org/#/c/472275/
Change-Id: Ia8551b45c1d7b4d67368e493e143c3893d07df61
this patch revises node recovery logic which dumped data to action.outputs to help us
tell whether is had been recreated. Now we will dump it do node.data cause the logic is in engine node.
And for the nodes was in WARNING status, we will mark it as ACTIVE either if its physical status is fine,
and all these nodes will be handled in lb policy if needed.
Change-Id: I56234cb8d8e7d54bcd9a1f97f6d486318a332286
the problem is caused by the change of cluster's runtime, the nodes were node_eng obj,
then we could invoke node.do_check() directly.
Change-Id: Ied01597d72319bea9637c160583c59e3414154f4
Tony Breeds