GitHub user bhaisaab opened a pull request:
https://github.com/apache/cloudstack/pull/106
CLOUDSTACK-8272: Python based file-lock free password server implementat...
Major changes:
- VRs are single CPU, so Threading based implementation favoured than
Forking based
- Implements a Python based password server that does not use file based
locks
- Saving password mechanism is provided by using secure token only to VR
(localhost)
- Old serve_password implementation is removed
- Runs with Python 2.6+ with no external dependencies
- Locks used within threads for extra safety
The aim for this is to improve password server by relying on a threading
based approach to minimize RAM usage and at the same time avoid using file
based lock. For 4.5.1 and 4.6.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/cloudstack concurrent-password-server
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/106.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #106
----
commit 3951ab00e25458c9c804b190ae7c7758f57985a3
Author: Rohit Yadav <rohit.ya...@shapeblue.com>
Date: 2015-03-10T10:05:31Z
CLOUDSTACK-8272: Python based file-lock free password server implementation
- VRs are single CPU, so Threading based implementation favoured than
Forking based
- Implements a Python based password server that does not use file based
locks
- Saving password mechanism is provided by using secure token only to VR
(localhost)
- Old serve_password implementation is removed
- Runs with Python 2.6+ with no external dependencies
- Locks used within threads for extra safety
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
