According to uberj, we're about ready to try adding a real site to be deploy via Captain Shove, and careers.mozilla.org is the site to do it on. There's a few things that need to happen here: - Add command procfile to careers. - Install shove on the careers admin server. - Configure shove for the dev, stage, and prod environments as three separate projects. - Add entries to Captain to match those three projects. - Test! Will update shortly after a meeting to determine if any steps are missing from this.
Commit pushed to master at https://github.com/mozilla/lumbergh https://github.com/mozilla/lumbergh/commit/171145f6903f6529d2c98afeb5daf715f54f949a Bug 1075126: Add procfile for Captain Shove deployment.
Any news on when we can get to this?
Working on it. Need to get ports open for rabbit.
Looks like shove is not finding pika as being the version it wants. genericadm ~ $ hostname genericadm.private.phx1.mozilla.com genericadm ~ $ python -c "import pika;print pika.__version__" 0.9.12 genericadm ~ $ tail /var/log/shove-supervisor.log raise DistributionNotFound(req) pkg_resources.DistributionNotFound: pika==0.9.13 Traceback (most recent call last): File "/usr/bin/shove", line 5, in <module> from pkg_resources import load_entry_point File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 2659, in <module> parse_requirements(__requires__), Environment() File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 546, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: pika==0.9.13 The easiest path forward is to recompile the shove package to accept a different version of pika.
I've updated shove to be more lenient with version requirements: https://github.com/mozilla/shove/commit/2dc34585fcb48fea093b7e106c00c9daa98ebb0b
uberj: Based on the changes and deploys we ran today, would you call this resolved? I think I would.
We did it! Yay!