Consider charming cos-alerter

[dstathis]

Enhancement Proposal

I have seen some interest in a cos-alerter charm. We should consider the possibility.

Note: This issue is complete when a decision has been made.

Abridged discussion from chat:

> user
Can we get a charm for the COS Alerter in order to deploy it with juju ?

> dylanstathis
We intentionally did not make a charm so that people would not put this in the same location as their infrastructure. One simple cloud container is our recommendation.

> user
We plan to deploy it as recommended, using docker. We will deploy a cs:ubuntu unit in a different cloud, to monitor remotely.

which brings to 2. why not use juju to deploy in a different location ? Deploying cs:ubuntu, manually installing docker, and then running the image in it feels very anachronic :wink:

> dylanstathis
The idea is to be outside of juju entirely. As in just click buttons on aws or whatever since you only need to deploy one. That being said, I can discuss charming it with the team.

> user
the point of juju is to avoid clicking in aws (also, deploying with juju means we have the asset in our inventories) (oh, and for avoidance of doubt, we will deploy in a different cloud, managed by a different juju controller)

[sajoupa]

I was just thinking (as I'm manually deploying a cos-alerter at the moment), that having it charmed also should give us an easy way to expose the dashboard (through juju expose), whereas a manual deployment will require configuring an ingress.
Ideally, the charm would relate to a reverse proxy (which will handle tls termination, and access management).

[lucabello]

Closing this in favor of #78.