framework
framework copied to clipboard
The Framework is a set of components and tools which brings the user an interface (GUI / API) to setup, extend and manage an Open vStorage platform.
### Problem description Specifically setting the framework logging to file, so that all components log to a file instead of stdout, causes a bug that backends can no longer be...
By default the logging for the framework components is set to 'info'. When you want to update the cluster, you need to manually change this to 'debug' if you want...
Tests have shown that the currently configured default settings on a vpool do not allow to guarantee a sustainable write throughput. In certain tests it quickly degrades over a time...
### Problem description The ABM config is only fetched once from a remote local backend. The OSD abm info might get out of date if the abm changes in the...
This is the Framework integration work for https://github.com/openvstorage/volumedriver/issues/251
Currently ABM and NSM clusters are only deployed to master nodes, this ticket is to include all nodes with a DB role for NSM and ABM clusters. Special attention is...
### Feature description The current scrubber does not allow the order of scrubbing to change. If a big scrub job was queued with all vdisks, you cannot ask for vDisk...
Logrotate does not work with the scrubber as it works behind its back (IOW the scrubber keeps on using the open file descriptor of a file that's been unlinked by...
A node can not be removed if there's vtemplate on it or owned by it let's say. Is there any workaround to remove this node? Related issue might be #2035...
As requested from @JeffreyDevloo . Take the ownership of all the ansible modules.