Right now, a Server resource must define a cache volume for both tier1 and tier2, where used.
For better usability and a simpler interface, evaluate if this is needed in the first place.
If we want to retain the ability to dedicate different cache volumes, at least make it optional for tier1, with a fallback to a folder inside the tier1.data volume. The same applies to tier2.cache, only in those cases where tier1 is defined.
In both cases, provide a way to:
- Add the
cache on an existing tier1/tier2 of a server with a rolling restart, by moving the folder to the new volume
- Remove it from an existing server, implementing a similar behaviour as the previous entry
Right now, a
Serverresource must define acachevolume for bothtier1andtier2, where used.For better usability and a simpler interface, evaluate if this is needed in the first place.
If we want to retain the ability to dedicate different cache volumes, at least make it optional for
tier1, with a fallback to a folder inside thetier1.datavolume. The same applies totier2.cache, only in those cases wheretier1is defined.In both cases, provide a way to:
cacheon an existing tier1/tier2 of a server with a rolling restart, by moving the folder to the new volume