Commit Graph

4 Commits

Author SHA1 Message Date
Andrey Pavlov 38b882d97d synchronize default vpc creation across threads
when two clients come for functions where check_default_vpc
is present then one goes to create default vpc and other fails.
it fails because vpc with is_default flag is already in DB
but children objects (like subnets) are not yet created.
For we will lock check_default_vpc function.

Another way is to rework _create_vpc. It can create VPC
without is_default flag. And at the end it can set the flag.
First thread will pass this. And second thread will fail at flag set
operation and will revert all created object. Then second thread
can check presence of default VPC again.
This way is better cause it can work across several controllers.

Change-Id: I5586fa234257b72721e328a9fa2375a56d1553c2
2018-03-24 00:49:01 +03:00
Andrey Pavlov d67adb7223 rework creating admin context - use keystoneauth1 lib
rather than own creator of session and auth_plugin from
keystoneclient library.

Change-Id: Id7f71e08de13e77586832f6d12cba1caff3772fe
2016-09-16 17:20:55 +03:00
Andrey Pavlov da6f97f291 rework certs stuff
remove ca_certs using for incoming requests
do small refactoring for keystone client using

Change-Id: I83dbb71248835cfc361eca691647deaa99023c8a
2015-11-12 11:19:06 +03:00
Andrey Pavlov 2f967d5ed4 add code for config generation
Change-Id: Ib86b949bb43ca6b5c386b7032a255f06b0f2eab9
2015-08-28 20:15:50 +03:00