A recent patch containing a pep8 error was merged without pep8
check since CI was down at that time. Do a quick fix here.
Change-Id: I8e9e5297c9e31d9f4089091274d59ec2e2bc96b0
Make client wrapper support create and delete operation so we
can create and delete aggregate in top OpenStack layer via DAL.
Change-Id: I13b7a0256e366f834965b817a6cd0237e52a6002
Implement client wrapper in DAL to access resources in top
OpenStack layer.
Partially implements: blueprint implement-dal
Change-Id: I8b6f5efdb49c87b6aeb4b7aad38f54c842c21d40
Base DAL implementation and DevStack integration. Our database
schema is under design so the models may be changed later.
Partially implements: blueprint implement-dal
Change-Id: I8b16b3217e6b72e04bd8886d01d638f2d5a5c388
This is the base implementation. It adds all the devstack boilerplate
and connects to the network plugins' requests.
Change-Id: Ibd61153e755e1c218503b0671c242ff50b5ebdc8
Initial implementation include option to use ML2 but it seem that it
will be better to use a core plugin (more control) over the process.
This just includes the Neutron side plugin. It replaces the ML2 plugin
with one that doesn't do any actual network changes, instead only
forwards it to the Cascade Service.
Change-Id: Ic63e7a3d0a1b171d43aff535b65c949e9e51ff4f
Add a link to poc code in project readme file; also remove readme
file in l2 proxy which is not needed.
Change-Id: Iebf3e552ab69c014dcd40bffe59dc44bb90c7d3f
Closes-Bug: #1469351#1469352
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
Jeremy Stanley