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

[DEPR-2U] [Discovery] How do we want to handle devstack configuration without devstack.py files? #588

Open
dianakhuang opened this issue Mar 28, 2024 · 3 comments
Assignees
Labels
devstack Devstack fixes

Comments

@dianakhuang
Copy link
Member

dianakhuang commented Mar 28, 2024

Original DEPR:

We control the configuration for devstack in devstack.py files in the various repos. As part of the devstack deprecation, those files are slated to be removed from the openedx repos. We would like an alternative method for handling these configurations.

Acceptance Criteria

  • a plan for how to replicate the configuration in the devstack.py files from the devstack repo
  • attempt a proof of concept implementation this for edx-platform

Implementation Notes

  • Ideally, we probably want to see if we can use the production.py files and insert our own yaml files with devstack configuration via the devstack repo
  • We will need to understand how much python is in the current devstack.py files and if we can cut that down.
@robrap
Copy link
Contributor

robrap commented Jun 11, 2024

@dianakhuang: This needs a Due Date set. It may be for 6 months after announcement? We can discuss with DEPR or Maint WG.

@robrap robrap changed the title [Discovery] How do we want to handle devstack configuration without devstack.py files? [DEPR-2U] [Discovery] How do we want to handle devstack configuration without devstack.py files? Jun 11, 2024
@iamsobanjaved iamsobanjaved self-assigned this Aug 12, 2024
@jristau1984
Copy link

@dianakhuang @UsamaSadiq is there anything left for this discovery ticket, or can it be moved to Done now?

@UsamaSadiq
Copy link
Member

@dianakhuang @UsamaSadiq is there anything left for this discovery ticket, or can it be moved to Done now?

Just attempting the POC for the suggested solution. Once the POC PR has been reviewed internally, we'll update the discovery document and close this issue. Then follow up tickets will be created if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devstack Devstack fixes
Projects
Status: In Progress
Status: Backlog
Development

No branches or pull requests

6 participants