748806 - vagrant updates

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Setup / Install, defect)

Description

[Luke Crouch [:groovecoder]]

vagrant and puppet need some more TLC to bring them up to date with the latest code for wiki. Especially:

* error installing tmux during vagrant up/provision - related to sphinx & openjdk?
* schematic migration error trying to fix constance config table records that don't exist (they are in a south migration)
* south migration error in migration 13 - running twice seems to work though

Comment 1

[Les Orchard [:lorchard]]

FWIW, I didn't get any tmux errors after a `vagrant destroy && vagrant up`. I did get the migration errors, which were fixed after a second `vagrant provision` as you mentioned. 

We should debug that, but FWIW I packaged and uploaded a new kuma.box to people.mozilla.org which should get future vagrant setups over the hump.

Some more things that might be handy to take care of in spring cleaning:

* Once bug 746636 is fixed, get a new anonymized DB dump produced and uploaded to people.mozilla.org for future vagrant DB imports

* "kumawiki" waffle flag on by default in the DB. Any other waffle flags that should be enabled? (eg. something about html5? apps?) We should add those to vagrant as they're created

* Might be nice to have an easier way to get an initial admin user enabled.

Comment 2

[Les Orchard [:lorchard]]

We might also want to get the events page working in vagrant instances out of the box:

https://github.com/mozilla/kuma/pull/185#issuecomment-5389619

It seems to be unconfigured / broken on first spin-up, right now

Comment 3

[Les Orchard [:lorchard]]

This is a developer environment thing, not necessary for July launch

Comment 4

[Les Orchard [:lorchard]]

This will probably turn into "Fall" cleaning at this rate, but another thing maybe worth considering:

We now have developer-dev.allizom.org. Maybe we should consider changing the host name of the VM to developer-local.allizom.org, since developer-dev.mozilla.org is easy to confuse with the other.

Comment 5

[Les Orchard [:lorchard]]

Also: Set up HTTPS in vagrant. It seems to be working already, as far as apache is concerned, but nothing's configured to get served up

Comment 6

[Luke Crouch [:groovecoder]]

when dropping tables in postimport.sql, reset the schematic and/or south versions to the appropriate numbers.

Comment 7

[Les Orchard [:lorchard]]

Alternatively, don't drop the tables, figure out why the south migrations failed. Someday soon, they'll have real data in them.

Comment 8

[Luke Crouch [:groovecoder]]

Change the vm host to 'developer-local.mozilla.org'

Comment 9

[Les Orchard [:lorchard]]

(In reply to Luke Crouch [:groovecoder] from comment #8)
> Change the vm host to 'developer-local.mozilla.org'

See also: https://bugzilla.mozilla.org/show_bug.cgi?id=748806#c4

Should probalby stick to the allizom.org convention

Comment 10

[[github robot]]

Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/c7dd8bfca7dff74ef5416bbab73232caed609c10
bug 748806: Switch to https://developer-local.allizom.org

* Change hostname to developer-local.allizom.org

* Enable SSL in Apache / Kuma config

* Redirect all http:// to https://

* Switch to non-mindtouch htaccess config

https://github.com/mozilla/kuma/commit/23d9446aa9ef36accc8b83cfeff95e8ca83efd23
Merge pull request #354 from lmorchard/https-in-vagrant

bug 748806: Switch to https://developer-local.allizom.org

Comment 11

[Les Orchard [:lorchard]]

There's actually still more to be done here. This should probably be a tracking bug for more tasks

Comment 12

[Les Orchard [:lorchard]]

That, or resolved invalid and a better bug (or bugs) filed for vagrant issues

Comment 13

[Les Orchard [:lorchard]]

New needful thing: Remove MindTouch from the vagrant box, since we finally migrated away from it

Comment 14

[[github robot]]

Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/24ebf27b1d16b18bf58797e540c72bff48f8f146
bug 748806: Symlink bugfix for the non-Mindtouch .htaccess

https://github.com/mozilla/kuma/commit/8ef592dd53b212eb32f84ea761414541eab4429a
Merge pull request #608 from lmorchard/vagrant-htaccess

bug 748806: Symlink bugfix for the non-Mindtouch .htaccess

Comment 15

[Luke Crouch [:groovecoder]]

GFLJay helped us clean this up!

Comment 16

[John Karahalis [:openjck]]

See https://bugzilla.mozilla.org/show_bug.cgi?id=789511#c5

Comment 17

[Justin Crawford [:hoosteeno] [:jcrawford]]

:groovecoder thought this was resolved in comment 15.

But comment 16 links to this mysterious message:

"Additionally, I suspect bug 748806 is not entirely finished, either."

:lorchard, as the author of that message, can you say what you think is still keeping this bug from being resolved?

Comment 18

[Les Orchard [:lorchard]]

(In reply to Justin Crawford [:hoosteeno] [:jcrawford] from comment #17)

> :lorchard, as the author of that message, can you say what you think is
> still keeping this bug from being resolved?

Well, it's been over a year, and lots of things have been done to Vagrant in the meantime. Probably worth closing and opening a specific bug about known Vagrant issues

Comment 19

[Justin Crawford [:hoosteeno] [:jcrawford]]

That sounds good to me. Let's open new bugs for vagrant clean up as needed.