Change fragment/block cache backend on a vpool

[jeroenmaelbrancke]

Is there an option to change the fragment/block cache backend via the gui?
If one cache backend is broken, can we move the vpool to another cache backend without removing the vpool?

[JeffreyDevloo]

No option to reconfigure as of yet.
The only fwk supported action would be: shrinking, extending via api with the new params

[wimpers]

In case we allow to update the fragment/block cache for a Storage Router, please check mockups as part of https://docs.google.com/document/d/1A5atdDML4W5Oao7G7L0Jhh7PfRx6i911LWGIqiuJHEA/edit#

[wimpers]

After discussion with @JeffreyDevloo following items will be picked up:
On the vPool details page:

• Make the Storage Drivers collapsable (http://fontawesome.io/icon/plus-square-o/)
• Replace the Nr. of proxies by a view which displays the status of the different proxies
• Add Edge port and IP info
• Add restart all proxies (http://fontawesome.io/icon/bullseye/)
• Add edit wizard (http://fontawesome.io/icon/pencil-square-o/) which goes through extend vPool wizard to change fragment/block cache
• When Storage router view is expanded (http://fontawesome.io/icon/minus-square-o/) show the port info, + current info (block/fragment cache)
• Underneath all Storage Drivers add form to update proxy config of all proxies in the vpool

[wimpers]

To be on the same page, following items are out of scope and will not be tackled:

• Individually restart proxies
• edit voldrv config
• set maintenance mode

[domsj]

FYI adding/removing block/fragment cache may (besides restarting the proxies) currently also require a restart of the volumedriver for the reads to happen via the fast path there