AND fixing remaining bits of our apps which aren't docker-friendly
this is something we can plan, as well the migration to full cloud
it is an effort of the whole team, a bit like the one we did to move from dwni to hetzner (with the dockerization of our apps), but it is definitively the way to go.
daksh joined the channel
but being familiar with docker is a pre-requisite, so, imho, it is too soon. My idea is to setup services we currently have on gcloud vms (grafana/influx/nbagios/wiki/etc..) on kubernetes at gcloud, we need to study pricing etc... though
it could be a starting point, before trying to migrate critical stuff
ruaok
great summary, thanks.
in the new year, lets make a list of things that need to be done in order to make our containers docker friendly.
then, once we get there, we should as a team all work to nuke consul and to go to pod.
then we can do a gcloud test deploy
how does that sound like a plan?
iliekcomputers: as I suspected: > fatal: Not a git repository (or any of the parent directories): .git
when the meb container starts. the commit hash needs to be captured at container build time.
samj1912
we generally do it by patching a __version__ variable in the __init__ or setup file
not sure what amazon account those came from...I tried logging into the one in syswiki and the password was incorrect:)
ruaok
yeah, I found it to be incorrect today too. I updated to what I had on record, let me make sure that matches what have in syswiki
iliekcomputers: tests passing now.
oh I see part of the problem
AWS != amazon associates.
let me make sure both are up to date.
bitmap
that's why I was a bit confused, since it was saying "Your $AWS_PUBLIC is not registered as an Amazon Associate." so I thought they were somehow linked
ruaok
associates updated.
oh, I see where the confusion is.
they are two different concepts but have the same login credentials.
bitmap: AmazonAffiliateProgram.md
use that to log into AWS and associates. I've made a note in the AWS file as well.
let me know if that works.
bitmap
thanks
UmkaDK joined the channel
UmkaDK_ has quit
it sent a login code to the meb email, don't think I have access
ruaok
539453
bitmap
thx
working
ruaok
great
bitmap
I guess I should just have MB be using the keys in AmazonAWSAccessKeys.md
I don't know where these other ones came from, for security reasons they don't show you your active keys... but apparently you can have up to two at a time
ruaok
or just generate new ones, just in case?
bitmap
sure, I'll try that instead
ah, they show you the public codes for your active keys. I guess there weren't any generated before. so the current MB ones weren't on this account
I'll switch out the codes and see if it works
ruaok
I also thought those were two separate things, so I guess I broke the old keys when I cleaned up the associates stuff
bitmap
not sure, it was working until very recently
ruaok
huh, yeah not sure. it was a few months ago that I cleaned up
samj1912
bitmap: the docker file for solr was always there in the mb-solrquerywriter repo, it just wasn't updated, gentlecat started using docker-solr, but git submodules are a massive PITA, especially when there are 2 layers of them so I simply updated the solrquerywriter repo with the latest docker file
I pushed the config, but got nothing in the logs indicating that it was restarted.
would it fully start the service from scratch? if so, it doesn't look like it worked.
bitmap
hmm, I think it would send a HUP signal
ruaok
oh, it took longer than expected.
bitmap
I don't know what uwsgi does in that case
ruaok
30 seconds.
bitmap
ah
ruaok
yep, seems to work fine.
anything we should test?
bitmap
making sure it handles config updates is the only thing I can think of
I think it shouldn't change anything else
ruaok
ok, I'll merge both PRs and deploy the updated stuff to production.
phew. finally deployed cleanly into production.
bitmap
nice
samj1912: ok, thanks. I think it's confusing, but maybe the mb-solrquerywriter repo just needs to be renamed
the name of the repo and the README suggest it's for a very specific part/module to our Solr setup, so I just wouldn't expect it to be the "main" Solr repo
samj1912 totally forgot we are back to normal times
Freso
samj1912: :p
chhavi_
totally forgot too
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | Google Code-In https://goo.gl/8xSZem | Meeting agenda: Reviews, Consolidated contributing guidelines video (naiveai)
yvanzo
bitmap: Yes. Can we deploy gh:MBS#580 on test.mb.o?
ruaok: about https://github.com/metabrainz/metabrainz.org/pu... i'm not sure to understand: you write current git version to .gitversion in the top dir of the repo but where is it copied to the image ?
