Just using cascading neutron object(net, subnet, port) uuid as name
of cascaded neutron object when creating these objects in nova.
Change-Id: I627d482c62e5f8c552623030104790f89da70533
Before, the cascading don't know the aggregates and resource info of
the cascadeds managed by proxys, so we cannot using the most filters
to choose the proper host with nova scheduler.
By updating the aggregates(includes hosts and metadata) and resource
used info in cascaded to the cascading periodically, this problem can
be solved.
Change-Id: If369f0023130c24544bbdbb3c1afbef05527d783
when cinderClient being generated, b/c this will be helpful to break
out from recursion when cinderclient being constructed from invalid
user/password
Change-Id: Id179b03b5d60af0af8cccfb64a7fad1ca709bf83
Add re-check logic when create network faild with the Conflict Exception
whose status_code is 409, it's means another task of creating the same
network is happend and done. So there is no need to create it again, instead
we query if the network exists(by name). If we can not find the network,
then the exception raised.
Change-Id: I44a6909b3119be748d4445a0f560454c19687276
When creating cascading port in nova proxy, add the 'name' field which
contains a cascading network_name and port uuid.
Change-Id: I730a0ca953513b9f965155141d04b90b39963432
When creating cascading port in nova proxy, add the 'name' field which
contains a cascading network_name and port uuid.
Change-Id: I40418f24f4f4813b90add46fe11457819c2bf6ec
add flag to cinder-proxy for volume status sync based on timestamp between cascading and cascaded OpenStack
Change-Id: I0d396a729df7d9d1265012b6052405181e3d7531
rebuild operation of nova may change the name of the instance, this
patch support update the name to cascaded.
Change-Id: I52fe578e80e52d8f465f92eefdf1eec8e36e5de3
The mapping relationships of network/subnet were saved into a json
file, now we use a dict to store them. It is decrease the IO operations
for promoting perforance.
Change-Id: I5786f3b27320cf870a85a0ea9db1a15f74819dfd
Add func to get cascaded instace uuid when not in the uuid_mapping,
which is using cascading instance's display_name and uuid based on
the cascaded instance's naming rule.
Change-Id: I210ad28fc09ff6c279ceed31fb104ba6ef523b35
We make the python novaclient as a memeber of ComputeManager, each
time used, we create it only if it's None. This avoids creating the
token for every request.
Note that the python-novaclient can re-auth when the token is expired,
so we need not to do it in application level.
Change-Id: I4a5644264383ffdf863759245086f2a6889152bf
Because of the change in mapping relationship between cascading and
cascaded, the instance_mapping_uuid_patch is no need exists.
Change-Id: I72606bb8f1d7238a53e0e5caae0671fa4ed105fa
When launching, reboot or resize a instance, if the flavor's accesses
is changed in cascading, then the modification will be synced to the
cascaded.
Change-Id: I54f0496c9841417966537faeee071ac309b8042d
Cache subnet mapping info between cascaded and cascading and support
multiple subnets exists in single network.
Change-Id: Id70cafe058685ea27b848d7c52a2a3c9db4a521e