Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bring-your-own RabbitMQ #523

Open
BenGalewsky opened this issue Dec 15, 2022 · 2 comments · May be fixed by #565
Open

Bring-your-own RabbitMQ #523

BenGalewsky opened this issue Dec 15, 2022 · 2 comments · May be fixed by #565

Comments

@BenGalewsky
Copy link
Contributor

As a ServiceX admin I want to use an existing RabbitMQ instance so I don't have to deploy RabbitMQ specifically for a ServiceX deployment

Assumptions

  1. An optional secret can be included in the deployment that contains the RabbitMQ URI
  2. This value is used instead of attempting to construct a URI using the deployment name in:
    a. App deployment
    b. CERN OpenData DID Finder deployment
    c. Rucio DID finder deployment

Acceptance Criteria

  1. Deploy a RabbitMQ independently from the ServiceX chart
  2. Determine a URI that can be used inside and outside of the cluster
  3. Set the URI value
  4. The service should work
@BenGalewsky BenGalewsky moved this to Ready in ServiceX Dec 15, 2022
@BenGalewsky BenGalewsky moved this from Ready to Ready for Review in ServiceX Jan 24, 2023
@shriram192
Copy link
Member

We do not need to add our own rabbit MQ for running servicex on arm64 based processors. I have updated the versions of all the helm charts in the requirements.yaml and also suggested changes to the ncsa/checks chart. I have performed a local testing with the same and it works for both amd64 and arm64 based processors. There is a branch created on the serviceX repo called rabbitmq-rosetta-fix that has the helm chart changes.

In ncsa/checks, we have to change the base image to python3.10 in the docker file and also update the psychopg2-binary package to psychopg2>=2.9.3 < 3

@shriram192 shriram192 linked a pull request Mar 27, 2023 that will close this issue
Rabbitmq rosetta fix #565
Open
@BenGalewsky BenGalewsky removed this from ServiceX Sep 26, 2024
@ponyisi
Copy link
Collaborator

ponyisi commented Nov 13, 2024

@BenGalewsky sounds to me like you've decided to remove this from the roadmap?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rabbitmq rosetta fix ssl-hep/ServiceX
3 participants
@ponyisi @BenGalewsky @shriram192