vscheduler 2.0.0

Full Changelog: v1.0.0...v2.0.0
Full Changelog: v1.0...v2.0.0

1. a module to check for zombie nodes to replace pool node if it’s not in service and flag it to in db be skipped when allocating to pool
2. add db table for nodes' status marking ones not in service to be skipped when allocating to pool
3. add vinfo giving overview of node’s status
4. add vset to set status of nodes in local db
5. separate logs for ldap-guaca sync script, nebula, setonix, etc
6. not checking booked db when it’s off in config, so, vscheduler could be deployed without booking partition and having booked installed
7. develop initial ansible playbook for automatic scheduler deployment
8. 8. Logging
9. ldap-guaca sync (pawsey specific)
10. email notification for db disconnections or any fatal error like socket communication failure
11. Modules:
12. vsync → booked-guaca sync
13. vmanage → windows machine management
14. vreport → report module
15. vkill → end a session
16. vquota → report on quota for specific group or node
17. valooc → allocates a node to user
18. read config from dedicated config file
19. load balance
20. socket communication between management and vis nodes
21. developed wrapper for CLI mode
22. ssh communication for session management in Windows only
23. record login/out events in local db on management instance
24. wall-time set to 8 hrs using atd daemon in client side
25. client side socket server to send usage back to management instance for load balance
26. no re-allocation of same node to same user after log out or hitting wall-time
27. all modules to be capable of parallel multithread running

vscheduler 1.0.0

Refer to release notes for more info on change log specific to this release.

Following features are included in current release:

1. Logging
2. email notification for db disconnections and socket communication failure
3. In-built modules:
4. vsync → booked-guacamole sync
5. vmanage → windows machines management
6. vreport → report module
7. vkill → end a session
8. vquota → report on quota for specific group or node
9. valloc → allocates a node to user
10. read config from dedicated config file
11. load balance
12. socket communication between management and visualisation nodes
13. CLI wrapper
14. session management through ssh
15. record login/out events in local db on management instance
16. client side socket server to send usage back to management instance for load balance
17. no re-allocation of same node to same user after log out
18. multithread modules