DB access and marketplace control from master and slave zones:
* Client class is singleton as required by xmlrpc-c
* one_auth initialization moved to a comon location
* MarketPlaceApp and MarketPlace actions are performed in the same zone as
the associated marketplace.
* Adds three new api calls updateDB, dropDB and allocateDB to perform
low level DB operations. These methods are exposed for Market y
MarketApps
* Forward operations are abstarct by Pool classes
* Apps and markets now includes a ZONE_ID
is SYSTEM. Update quota update and snapshot survival after delete
--recreate according to:
+--------+-------------------------------------+
|LN/CLONE| PERSISTENT | NO PERSISTENT |
| |---------+---------+-----------------+
| TARGET | created | quota | created | quota |
+--------+---------+---------+-----------------+
| SYSTEM | system | VM + DS | system | VM |
| SELF | image | DS | image | DS |
| NONE | image | DS | image | DS |
+----------------------------------------------+
Snapshots created at system ds (LN_TARGET/TM_TARGET) will be deleted
after a recreate.
(cherry picked from commit c5ad05fc60680cda2763973f5079598c2bf166e7)
Datastore Quota management to deal with bulk updates. Hook on DM & LCM
resubmit and clean_up_vm to remove snapshots
(cherry picked from commit 6f02a240ec8f4be7ef232e8f8c584665e6747233)
UserChangePassword followed this strategy:
a1. Eventually encrypt user password if the users
auth_driver is CORE_AUTH
a2. Set (probably encrypted) password with
User::set_password
a3. User::set_password tries to validate (probably
encrypted) password instead of the raw password
UserChangeAuth did something similar:
b1. If password is given (not empty) do a1 through a3
b2. Set auth_driver
The change proposes the following:
* In set_password:
1. Validate the raw password
2. Do encryption if needed
* In UserChangePassword: simply call set_password
* In UserChangeAuth: set auth_driver *before* calling
set_password, such that set_password does the right thing
if the auth_driver changes
Note: I needed to move the implementation of set_password
from User.h to User.cc since it seems impossible to access
UserPool::CORE_AUTH from within User.h.