search

openshift / origin-metrics

78 stars 117 forks source link

Supported way to use external Cassandra? #348

Closed ksurent closed 3 years ago

ksurent commented 7 years ago

Hi,

I was wondering if there's an easy&supported way of making Hawkular use external Cassandra. By external I mean something that is not deployed using the scripts from this repo. It can still run inside the same OpenShift cluster, or a different cluster, or even just bare metal. I skimmed through the installation scripts and it appears that it's expected that Cassandra is available in the same cluster under a certain Service. Please correct me if I'm wrong.

If not, do you think it's something you'd want to support? Consider use cases where there's already a streamlined way of setting up Cassandra (either containerised or bare metal) and users prefer to use that instead of deploying it with Hawkular.

jsanda commented 7 years ago

I am not sure what changes would be required as I have not looked into it, but I think it is a good idea.

On Mon, Jun 12, 2017 at 11:26 AM, Alexey Surikov notifications@github.com wrote:

Hi,

I was wondering if there's an easy&supported way of making Hawkular use external Cassandra. By external I mean something that is not deployed using the scripts from this repo. It can still run inside the same OpenShift cluster, or a different cluster, or even just bare metal. I skimmed through the installation scripts and it appears that it's expected that Cassandra is available in the same cluster under a certain Service. Please correct me if I'm wrong.

If not, do you think it's something you'd want to support? Consider use cases where there's already a streamlined way of setting up Cassandra (either containerised or bare metal) and users prefer to use that instead of deploying it with Hawkular.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/openshift/origin-metrics/issues/348, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKQuaZ1CA0A38KMBpViwynigo_UHRI_ks5sDViRgaJpZM4N3RzF .

jpkrohling commented 7 years ago

This would require some work on the side of whoever is installing, specially to secure the communication between Hawkular and Cassandra. Those are the items I could think of, to use an external Cassandra:

Then, the admin installing Cassandra/Hawkular would need to:

These steps are currently being done here: (like this: https://github.com/openshift/origin-metrics/blob/master/deployer/scripts/hawkular.sh#L25-L68)

mwringe commented 7 years ago

Yeah, as mentioned, you can't really do it easily today. We could update our ansible playbooks to allow someone to specify an external Cassandra to connect to (eg URL + ca certificate). I don't think this would be too difficult to add.

We accept PRs if you would like to add in this feature :)

Otherwise it might be better to add a request via a bugzilla at https://bugzilla.redhat.com (against the 'OpenShift Container Platform' product and the 'metrics' component). There are more people monitoring the bugzillas than there are people who are monitoring these issues.

openshift-bot commented 4 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 4 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/origin-metrics/issues/348#issuecomment-706590549): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.