Time
S
Nick
Message
02:04 djbrooke joined #dataverse
12:58 donsizemore joined #dataverse
13:56 djbrooke joined #dataverse
14:07 djbrooke joined #dataverse
14:37 djbrooke joined #dataverse
14:56 djbrooke joined #dataverse
15:10 donsizemore joined #dataverse
15:33 djbrooke joined #dataverse
15:58 donsizemore joined #dataverse
17:51 djbrooke joined #dataverse
17:53 djbrooke joined #dataverse
18:00 donsizemore joined #dataverse
18:00 djbrooke joined #dataverse
18:05 djbrooke joined #dataverse
18:35 djbrooke joined #dataverse
18:36 yoh joined #dataverse
18:50 djbrooke joined #dataverse
18:55 djbrooke joined #dataverse
19:07 djbrooke joined #dataverse
19:18 djbrooke joined #dataverse
19:23 djbrooke joined #dataverse
19:36 djbrooke joined #dataverse
19:44 djbrooke joined #dataverse
19:56 bjonnh
alright
19:56 bjonnh
I'm at the maven package step
19:57 bjonnh
this is just incredible the number of pieces of software that we need now
19:57 axfelix joined #dataverse
19:57 bjonnh
I used to be able to compile an app without needing an internet connection ;)
20:14 djbrooke joined #dataverse
20:46 bjonnh
ok I can't get it to work :s
20:46 bjonnh
GlassFish Server
20:46 bjonnh
Your server is now running
20:46 bjonnh
I see that, but no dataverse
20:46 axfelix joined #dataverse
21:00 bjonnh
YAAY
21:04 pdurbin
bjonnh: does that "YAAY" mean you got it working after 15 more minutes of hacking (I hope!)? :)
21:04 bjonnh
yes
21:04 pdurbin
phew
21:04 bjonnh
is there a default account
21:05 pdurbin
yes: http://guides.dataverse.org/en/4.5.1/installation/installation-main.html#superuser-account
21:05 bjonnh
oh sorry didn't see that page
21:06 bjonnh
neat
21:07 pdurbin
:)
21:08 bjonnh
oh solr isn't set up
21:08 axfelix joined #dataverse
21:08 bjonnh
I see it uses /downloads
21:11 bjonnh
ok now I have to clean everything
21:18 bjonnh
there is quite a lot of stuff happening
21:21 djbrooke joined #dataverse
21:21 bjonnh
also it would be easier to not use the vagrant scripts
21:22 bjonnh
but that would mean having to maintain yet another set of setup files
21:32 axfelix joined #dataverse
21:35 axfelix joined #dataverse
21:42 bjonnh
docker run -p 8888:80 -p 9999:443 bjo/dataverse
21:42 bjonnh
lets see…
21:42 bjonnh
for now it is relying on me building the war
21:42 bjonnh
but I plan to make that change
21:43 bjonnh
yep login, solr etc works
21:47 axfelix joined #dataverse
21:57 bjonnh
pdurbin: would that be useful to have a docker that allows you to pull and build any branch?
21:57 bjonnh
pdurbin: (without redownloading/installing anything else)
22:06 axfelix joined #dataverse
22:10 djbrooke joined #dataverse
22:20 pdurbin
bjonnh: yes, that might be nice. I'm still new to Docker but I'm interested in any way to deploy an arbitrary branch (pull request) to AWS so that API tests can be run against the running Dataverse instance made from that branch.
22:21 bjonnh
I don't know how to aws
22:21 bjonnh
but the rest should work ok pretty soon
22:21 bjonnh
at least now it builds properly
22:21 bjonnh
the tests are failing inside docker
22:21 bjonnh
but not in a shell
22:22 bjonnh
the test of surefire (it seems)
22:22 pdurbin
bjonnh: ah, but telnoratti knows AWS and Docker. He created https://github.com/IQSS/dataverse-aws , which I've been meaning to test.
22:22 bjonnh
yeah
22:23 bjonnh
but I didn't got it to work on my machine without AWS
22:23 bjonnh
so I built mine
22:23 bjonnh
can probably merge the two together now
22:23 pdurbin
that would be awesome
22:23 pdurbin
bjonnh: would it be a pull request against https://github.com/IQSS/dataverse ?
22:23 pdurbin
(the main repo)
22:24 pdurbin
whatever makes sense is fine with me
22:26 bjonnh
for now yes
22:26 bjonnh
just a bunch of filesç
22:27 bjonnh
you get the repo locally
22:27 bjonnh
do ./build_docker.sh
22:27 bjonnh
wait a bit
22:27 bjonnh
docker run -p 8888:80 -p 9999:443 bjo/dataverse
22:27 bjonnh
and it is done
22:27 bjonnh
(and running)
22:28 pdurbin
nice
22:28 bjonnh
it is made using 2 dockers
22:28 bjonnh
one doing all the system prep (and predownloading the maven packages)
22:28 bjonnh
the other one getting the last update on git, packaging and redeploying
22:28 bjonnh
I was thinking breaking this last one in two
22:29 bjonnh
so the redeploying/start_services would be separated
22:29 bjonnh
that way you could run docker instances that just run the maven tests
22:29 bjonnh
and get the result back
22:29 bjonnh
(also meaning you can run them in parallel)
22:29 bjonnh
because they are isolated
22:30 bjonnh
I still have some tweaks to do to make things more universal (like custom git repo and custom branch)
22:30 bjonnh
I'll work on that next week
22:30 pdurbin
cool
22:31 pdurbin
I mean, it all sounds great and fancy. I hope I can get it working.
22:31 bjonnh
and then see with telnoratti how to integrate that with AWS
22:31 pdurbin
yeah
22:31 bjonnh
well I can push it to my repo if you want to try
22:32 pdurbin
the thing telnoratti made is awesome but it's hard coded to a specific release. This one the last time I checked: https://github.com/IQSS/dataverse/releases/download/v4.5/dataverse-4.5.war
22:32 pdurbin
it's great for kicking the tires on that release
22:32 pdurbin
but I'm interested in pre-release testing
22:32 pdurbin
pull request testing
22:32 bjonnh
wait I'm learning how to git… again…
22:32 pdurbin
automated testing of pull requests using API tests
22:33 pdurbin
whoops, I mean that it's hard coded to a specific *installer*, not a war file: https://github.com/IQSS/dataverse/releases/download/v4.5/dvinstall.zip
22:36 bjonnh
https://github.com/bjonnh/dataverse/commit/f7a82c9fc37aa1c901534d8a91f92ba18f3c3ce4
22:37 bjonnh
we can probably come up with a common setup system between vagrant and docker
22:37 bjonnh
that would avoid editing multiple files each time a version of a dependency is changed (thinking about solr, glassfish, schemaspy…)
22:38 pdurbin
that would be awesome
22:38 bjonnh
pdurbin: I don't get what you are talking about
22:38 bjonnh
(the installer thing)
22:39 bjonnh
pdurbin: well if nobody else is working on the vagrant part, I can maybe help
22:39 pdurbin
I added the Vagrant stuff. I just don't test it very often.
22:39 bjonnh
pdurbin: I will need to find a machine where I can run virtualbox, I think I have one that could do that
22:40 telnoratti
yeah the hardcoded release is something I want to get rid off
22:41 telnoratti
I wasn't sure the best way to build it and work wanted to see our instance move to production
22:41 pdurbin
telnoratti: cool. I owe bjonnh a better explanation of what I mean.
22:41 telnoratti
but any suggestions on how to build the release per docker would be good
22:42 telnoratti
my initial thoughts is that the dataverse build scripts have a docker image as a target
22:42 telnoratti
or something to that effect
22:43 bjonnh
ooh so you want to use the commit number as the version number?
22:47 telnoratti
yeah, then going by releases will be as simple as just building the image for a git tag and then using that as the docker tag
22:48 bjonnh
why not
22:49 bjonnh
we should probably rebuild everything though
22:49 bjonnh
which take some time
22:49 bjonnh
and bandwith
22:52 telnoratti
you mean a docker image per commit? I think for the dockerhub we really only care about an image existing for each tag, for pdurbin's development stuff he may be more interested in using a private docker registry for the QA process
22:57 bjonnh
oh tag≠commit
22:58 bjonnh
yeah
22:58 bjonnh
ok
22:58 bjonnh
I was thinking of tags as the IDs
23:05 pdurbin
telnoratti: sure, a docker image per commit would be fine. Every commit could have the API tests fired against a docker image running on AWS. Most of the commits happen in branches which eventually turn into pull requests.
23:05 pdurbin
I hope this is making sense.
23:06 pdurbin
If that's too expensive in terms of an AWS bill or too much noise or whatever, it could also be a somewhat manual decision. "I'd like to deploy this branch to AWS, have the API tests run against it, and then leave it up for a while so I can poke around in the GUI ."
23:07 telnoratti
well you may want to revise how it's deployed to aws, since the cloudformations we use is targeted for a production deployment
23:07 telnoratti
it includes autoscaling and some other featues that probably aren't necessary to test code releases
23:08 pdurbin
well, all that stuff is great for someone out there who wants to evaluate the latest release of Dataverse
23:08 telnoratti
though I haven't seen bills so I have no idea what pricing is like
23:08 pdurbin
there are different audiences to consider
23:09 pdurbin
right now we suggest that people who want to kick the tires can run Dataverse in Vagrant: http://guides.dataverse.org/en/4.5.1/installation/prep.html#vagrant-for-testing-only
23:36 pdurbin
bjonnh: here you can see how "dvinstall.zip" was changed from v4.4 to v4.5: https://github.com/IQSS/dataverse-aws/commit/ca90212
23:36 pdurbin
does that help?
