[Backport] Multiple devstack releases with one machine - #564
Conversation
|
Thanks for the pull request, @ztraboo! I've created OSPR-4854 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
37d9e35 to
9b5536b
Compare
|
@ztraboo Thank you for your contribution. Is this ready for edX to review? |
|
@natabene Yes ready for edX review. |
regisb
left a comment
There was a problem hiding this comment.
I really like the fact that we are replacing most docker commands by docker-compose. I'd just like to clarify some questions, as I didn't take the time to run this PR locally myself.
|
@regisb Made another update edx/devstack@037c229 to align with what we did in https://github.com/edx/devstack/pull/532 for the Also I provisioned this again and I didn't see any immediate errors. |
872dc53 to
1964d07
Compare
|
@regisb @kdmccormick @arbrandes Finally got around to adding documentation on how to use this multiple devstack same host here hhttps://github.com/edx/devstack/pull/564/commits/261bc6cefbfff33774cd08dabd1f1aab7a813fe5. I did this for the |
1964d07 to
261bc6c
Compare
|
@regisb Updated |
d96df35 to
f11bc36
Compare
|
@ztraboo I just need to understand the |
|
@regisb You are planning to review and merge this as a core committer, correct? |
0ae1c8a to
394df38
Compare
f2b4b87 to
b73a147
Compare
|
@regisb Just made this commit edx/devstack@b73a147 to update the
I rebased on top of
Instead of removing the |
|
This looks ready to merge! @ztraboo would you like to squash some of your commits or should I merge this as it is? |
I can squash all commits if needed. Would it be helpful to some to see what changes were done rather than all together as one commit? Does squashing commits make it easier to see what this PR changes were done in one commit rather than separated out? Please advise. |
|
Personnally, I prefer to squash together the commits that impact the same features or things. For instance, I would squash the commits that affect the README. If one particular commit fixes a bug that is not related to the other features from this PR, then this commit should stand on its own and not be squashed. Commits that all pertain to a single feature, such as "modify implementation according to regisb's bloody nitpickings" (:wink:) should be squashed in a single features. |
…tainers for multi-version devstack support https://discuss.openedx.org/t/docker-devstack-multiple-releases-one-machine/1902 Multiple devstack releases with one machine. This is in regards to this pull request https://github.com/edx/devstack/pull/532 Updating volumes for `themes` to work with the `ironwood` release. Applying these changes to get local devstack working for ironwood release. https://github.com/edx/devstack/pull/376 https://github.com/edx/devstack/pull/377 Moved `COMPOSE_PROJECT_NAME` update to `options.mk` file. Additional changes to get `devstack_docker` for Ironwood working multisite environment setup. Additional changes needed to make `docker` commands work making use of the `dev.print-container.%` target to get the container id. Reverting some of these commands back to `docker` type to align with what we did with edx/devstack@59f812e
…le isolated devstacks for same host. Make additional adjustments to the documentation for multiple releases one machine.
…commands for services outside of `docker-compose.yml`. Makes sure that other services (e.g. `xqueue`, etc) that are not defined in the docker-compose.yml file have the correct configuration passed to the `docker-compose exec` command to work properly.
…s one machine (regisb review). Comments came from `master` edx/devstack@c0b482d Fix issue with `docker-compose config` not outputting configuration information when `$(DOCKER_COMPOSE_FILES)` was excluded from the command. It appears that leaving out `$(DOCKER_COMPOSE_FILES)` caused the `docker-compose config` to not include the **volume** information for services within the `docker-compose.yml` file, as well as, excluding additional services like `docker-compose-{analytics-pipeline,watchers}.yml` to name a few. Update provision-ecommerce.sh with recommended changes from @morenol Co-authored-by: morenol <13-10934@usb.ve> Merging additional updates based on openedx-unsupported#569 changes for the `readme` file. - All changes from https://github.com/edx/devstack/pull/569 changes from this.
b73a147 to
35d197b
Compare
|
@regisb Thanks for that explanation. I squashed some commits. Ready to merge. |
|
@ztraboo 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
As discussed with @kdmccormick here edx/devstack@57455fe#commitcomment-41529836 we decided to remove `xqueue` since it is not needed by default devstack setup. This is a fix to recent PR https://github.com/edx/devstack/pull/564.
As discussed with @kdmccormick here edx/devstack@57455fe#commitcomment-41529836 we decided to remove `xqueue` since it is not needed by default devstack setup. This is a fix to recent PR https://github.com/edx/devstack/pull/564.
Committing this update for
juniperrelease since it didn't exist yet.@kdmccormick, @jmbowman, @arbrandes, @regisb
https://discuss.openedx.org/t/docker-devstack-multiple-releases-one-machine/1902
Multiple devstack releases with one machine.
This is in regards to this pull request
https://github.com/edx/devstack/pull/532
Updating volumes for
themesto work with theironwoodrelease.Applying these changes to get local devstack working for ironwood release.
https://github.com/edx/devstack/pull/376
https://github.com/edx/devstack/pull/377
Moved
COMPOSE_PROJECT_NAMEupdate tooptions.mkfile.Additional changes to get
devstack_dockerfor Ironwood working multisite environment setup.