Allow port to be configured

[Chris Johnston]

Doing a deployment that doesn't allow access to 8443. The port used for ceph-dashboard should be able to be configured based on deployment requriements.

[Paul Goins (vultaire)]

We've also had a customer have problems because they needed it accessible on port 443 rather than 8443, necessitating us to deploy haproxy to redirect the traffic.

I know it's a simple change at the ceph level, e.g. "ceph config set mgr mgr/dashboard/$name/ssl_server_port $PORT", per https://docs.ceph.com/en/latest/mgr/dashboard/. I've reviewed the charm code and I see the status checks are hard-coded to expect port 8443, so that keeps me from doing that type of tweak by hand for fear of messing up the charm's status checks.

This seems like a relatively low hanging fruit here, maybe a good first bug for a new starter or similar?

[Luciano Lo Giudice (lmlogiudice)]

Yes, I agree this is good first bug for a newcomer (It's essentially a "find and replace" kind of task).