Awesome, thanks a lot! This'll be tremendously useful. Makes sense on the Ginkgo issues. Very glad we'll have a working docker-based devstack for Hawthorn, though.
-- Uman @OpenCraft <http://opencraft.com> On Tue, Apr 17, 2018 at 4:38 PM, Jeremy Bowman <[email protected]> wrote: > We do plan to create Hawthorn-tagged Docker images for all the Open edX > services, built from the appropriate branch in each repository. We hope to > have that done for the upcoming Hawthorn beta release, here's the JIRA > ticket for tracking that: https://openedx.atlassian.net/browse/OPEN-2219 . > > One of the things that makes it difficult to use Ginkgo with the Docker > devstack repo is that each of the services needed a number of configuration > changes made after the Ginkgo release to work correctly in that > environment, which was beyond the scope of changes we normally consider > appropriate for an already released version of Open edX. Moving forward, > each release should have everything needed to launch and maintain a > Docker-based devstack for it, including a release-specific branch of the > devstack repo. > > Jeremy > > On Mon, Apr 16, 2018 at 3:22 AM, Uman Shahzad <[email protected]> wrote: > >> Hi, >> >> I'm wondering if edX has plans to support a separate Hawthorn branch for >> the docker devstack repo? >> >> Right now doing development for Ginkgo instances with the docker devstack >> is basically impossible unless you had saved images for all services when >> they were on or close to the Ginkgo branch, and probably other things >> besides the images like the commit in the devstack repo itself. >> >> Going forward, it'd be lovely if we can have a Hawthorn branch on the >> devstack repo where the images downloaded from Docker Hub are tagged for >> Hawthorn separately from the latest master images. >> >> If this won't be done upstream, I'm willing to do it on my own and share >> that with the community, but that could lead to some unnecessary >> fragmentation. >> >> Thanks, >> -- >> Uman >> @OpenCraft <http://opencraft.com> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "General Open edX discussion" group. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/edx-code/CA%2B_6%3DJ6-7TeQ3bNTbQUPX%2B%3DFGYC5-BUaemKCE_ >> 3vp8R7U7kQPQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/edx-code/CA%2B_6%3DJ6-7TeQ3bNTbQUPX%2B%3DFGYC5-BUaemKCE_3vp8R7U7kQPQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > > -- > Jeremy Bowman > Principal Software Engineer > edX > 141 Portland St. > <https://maps.google.com/?q=141+Portland+St.+Cambridge,+MA+02139&entry=gmail&source=g> > Cambridge, MA 02139 > <https://maps.google.com/?q=141+Portland+St.+Cambridge,+MA+02139&entry=gmail&source=g> > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "General Open edX discussion" group. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/edx-code/CABQueNm_w7hr5W1D-eoi4AA1RsYyvL%3Dkw0NKO0%2Bkcf-deBf%2B-w% > 40mail.gmail.com > <https://groups.google.com/d/msgid/edx-code/CABQueNm_w7hr5W1D-eoi4AA1RsYyvL%3Dkw0NKO0%2Bkcf-deBf%2B-w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CA%2B_6%3DJ5ZmHgh9yVxu7AqBxeBiU%3DLd1P-U_z5%2BUcDOzfkLzm8hw%40mail.gmail.com.
