TO DO - Githubissues

jaymzh commented 8 years ago

[x] add deployment key to repo so we can pull automatically (and/or make repo public)
[ ] setup secrets repo and make chef pull from that for apache keys, db passwords, etc.
[x] mariadb chef support
[x] web deployment script
[x] handle static user generated content
[ ] share documentation for updating drupal code with scale-webdev
[x] instructions for bootstrapping nodes not managed by vagrant.

irabinovitch commented 8 years ago

7 days left on our hosting with ActUSA. Which of these do we need to address before cutover?

irabinovitch commented 8 years ago

For now we're using Rackspace's managed mysql setup, so I'm going to check off mariadb support and punt on it for now.

irabinovitch commented 8 years ago

@jaymzh I see the first item on this list is "add deployment key to repo so we can pull automatically (and/or make repo public)" . Thoughts on using chef server via hosted chef instead?

jaymzh commented 8 years ago

Naw... then you have to deliver them there too... (setting up grocery-delivery isn't any easier than making the repo public and it's just another moving part) and we've solved that problem once we make the repo public, which we should do anyway. it's only not public incase we leaked secrets into it while developing quickly. @davide125 and @odcinek and I, once the machines have been migrated and we can get a secondary 'test' set up where people can test new changes up, were going to tie together taste-tester into all that and make the repo public.

jaymzh commented 8 years ago

(despite some terrible hacks, that are a bit embarassing, I don't think there's anything stopping us from making the repo public now, fwiw)

irabinovitch commented 8 years ago

@jaymzh We already migrated the socallinuxexpo.{org,net,com} webserver although it took some hacks given the current workflow around keys for cloning this repo and scale-secrets. linuxfests.org was moved along time ago. mail was moved to gmail.

Things we still need to do in the next 4 days or sooner:

Migrate mailing lists ASAP. I might just end up doing this manually at this point because we only have 4 days left and all of those are travel days for me. (eg mailman, phplist, postfix+dkim, etc)
Deciding how we want servers to pull updates from these repos. Right now keys are needed to pull from this repo. If we're public I guess thats not needed. It doesn't solve scale-secrets being manual though.
Give Ron and scale-webdev a reasonable workflow for updating their PHP code. Right now the recipes only clone the repo on initial provisioning. Do we want him to manually run git pull any time he pushes changes? Something else?

jaymzh commented 8 years ago

Secrets can be deployed via a manually run script from someone with keys loaded, those don't exactly change often. The main repo will become public for sure. The development model for both Chef and PHP code are both first on my list for after I'm done with my traveling. I'll have a little time after ChefConf, but not a ton. My time will get much more available after DEFCON though. I had gotten the impression lists weren't required, feel free to hack it up as necessary and I can write chef for the lists stuff as long as I have access. Did we get (in whatever agreement we made with whoever is our new host) extra VMs for a dev env?

irabinovitch commented 8 years ago

Lists are required otherwise we lose all our ability to mail attendees, or to maintain discussions on scale-chairs and scale-planning. See #205, #209, #213

We have to shut down the VMs at ActUSA on 6/30. So 3 days left.

irabinovitch commented 5 years ago

I think we can close this out.

socallinuxexpo / scale-chef

TO DO #1