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.

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

Maestro-KCIDB bridge service migration to production #664

Closed
nuclearcat opened this issue Jun 28, 2024 · 2 comments
Closed

Maestro-KCIDB bridge service migration to production #664

nuclearcat opened this issue Jun 28, 2024 · 2 comments
Assignees

Comments

@nuclearcat
Copy link
Member

As KCIDB bridge service reached maturity, to make results more reliable we need to migrate it to Maestro production environment.
Following steps planned:

  • Disable KCIDB bridge service in Maestro staging environment
  • Enable KCIDB bridge service in Maestro production environment to submit data to playground KCIDB
  • Verify that data is submitted correctly to playground KCIDB
  • Disable KCIDB bridge service in Maestro staging environment
  • Enable KCIDB bridge service in Maestro production environment to submit data to production KCIDB
  • Verify that data is submitted correctly to production KCIDB
  • Enable KCIDB bridge service in Maestro staging environment to submit data to playground KCIDB
  • Verify that data is submitted correctly to playground KCIDB

We need to keep step 1 short as possible, if possible to do it in one day.

@JenySadadia
Copy link
Collaborator

We don't need to disable bridge service on staging environment.
The service running on production will submit data to KCIDB's production and will be distinguishable on the dashboard.

@nuclearcat
Copy link
Member Author

Production kcidb bridge is activated and should be sending data to kcidb production from now on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants