Time
S
Nick
Message
01:09 axfelix joined #dataverse
04:54 axfelix joined #dataverse
07:07 metamattj joined #dataverse
08:08 jri joined #dataverse
08:21 bencomp joined #dataverse
09:12 jri joined #dataverse
09:39 jri_ joined #dataverse
09:46 jri joined #dataverse
10:07 jri joined #dataverse
13:58 jri joined #dataverse
14:29 jri_ joined #dataverse
15:17 bencomp
I just noticed that v8 of the Handle software has finally been released
15:18 bencomp
it seems it supports a JSON RESTful API
15:18 pdurbin
yummy
15:18 pdurbin
I'm fighting with XML as we speak :)
15:20 bencomp
you're not cooking it? ;)
15:21 pdurbin
:)
15:21 pdurbin
parsing it with rest-assured
15:24 pdurbin
basically I'm marching through http://guides.dataverse.org/en/4.2.1/api/sword.html#curl-examples and making sure each API call is exercised with rest-assured
15:25 pdurbin
which I execute with this job: https://build.hmdc.harvard.edu:8443/job/phoenix.dataverse.org-apitest-4.2.3/
16:25 axfelix joined #dataverse
17:14 axfelix joined #dataverse
17:35 donsizemore joined #dataverse
17:40 donsizemore
knock knock =)
17:42 pdurbin
who's there?
17:44 donsizemore
got a vanilla 4.2.1 install working in ansible. one step at a time
17:44 pdurbin
vanilla who?
17:44 donsizemore
everything is fine down to publishing the root dataverse, which we wouldn't want to do for a production install
17:44 pdurbin
donsizemore: that's great news. good work
17:45 donsizemore
next step is to stick in some snake oil ssl certs and work out shibboleth with say testshib.org
17:45 pdurbin
donsizemore: so you're testing this in Docker?
17:45 donsizemore
but, as i'm imagining an ansible workflow in particular would be for production stand-ups, do we want to grant auth users on root, populate dummy users, etc.?
17:46 donsizemore
i was just trying to iron out the ansible playbooks first. i've got a 4-line nuke_dataverse shell script that zaps the VM back where i need it
17:47 pdurbin
heh
17:47 pdurbin
you roll the VM back to a snapshot you mean?
17:48 donsizemore
don't need to. just nuke the glassfish, solr and postgres stuff the playbook installs and i'm back to square one
17:48 pdurbin
gotcha. makes sense
17:48 donsizemore
i was cribbing from your phoenix stuff, and in your "POST" script i think for a production deployment we'd want to stop at the reference_data.sql step
17:48 pdurbin
donsizemore: I'm just thinking ahead to when people open issues with your playbook and there isn't a common environment to test on :)
17:49 donsizemore
that's on my list, but next i want to get shib working, if you think i'm safe leaving off create-all-and-test, public-spruce1-and-test, etc.
17:50 pdurbin
absolutely. I'm actually wondering if I should retire those scripts once I have enough equivalent rest-assured tests in place
17:51 pdurbin
of course, it's kind of nice having those curl commands executed each time I rebuild phoenix so I know they still work
17:51 pdurbin
belt and suspenders
17:52 donsizemore
sweet. gonna push this stuff with those test scripts commented out, if it's cool, and switch to apache and shib.
17:52 pdurbin
donsizemore: ok. I agree that your playbook shouldn't publish the root dataverse
17:52 donsizemore
dataverse 4.2.1 installs (i believe) cleanly, running as a non-privileged user
17:53 pdurbin
donsizemore: will your playbook run the equivalent of https://github.com/IQSS/dataverse/blob/v4.2.1/scripts/search/tests/grant-authusers-add-on-root or not?
17:53 pdurbin
(probably it shouldn't... let the person installing decide)
17:54 donsizemore
it won't now =) this is why i'm coming to you with these questions
17:55 pdurbin
!
17:55 pdurbin
:)
17:55 pdurbin
donsizemore: is it the kind of thing you can make configurable via Ansible?
17:55 pdurbin
basically present what the GUI presents, I mean. the various options
17:56 donsizemore
we can configure whatever you'd like as long as we can do it in the group_vars file
17:56 pdurbin
on phoenix I let authenticated users create dataverses in the root but not datasets
17:56 pdurbin
because I think it's messy to let people create datasets in the root :)
17:56 pdurbin
but reasonable people disagree on such things :)
17:56 donsizemore
we could have both testing and production group_vars file to allow for such differences?
17:57 pdurbin
sorry, I don't follow. do you rely on a certain "add" configuration/permission for testing?
17:58 pdurbin
donsizemore: you should go ahead and push. We can worry about this stuff later :)
17:59 pdurbin
worry about it when you're about to tag it as 0.1 or whatever :)
17:59 donsizemore
so, i'm using group_vars for things like db_user and db_pass, but ansible can also use conditionals in deciding to run a task. a "test" setting or group_vars file would decide whether to make a bare-bones or fully-furnished dataverse installation.
17:59 pdurbin
what do I get with a fully furnished dataverse?
18:00 * pdurbin
dreams of a new couch that hasn't been destroyed by his cats
18:00 donsizemore
test users, test data, automatically published root dataverse, whatever you'd want in a demo, for instance
18:01 pdurbin
ah, gotcha. so phoenix is fully furnished. people can create accounts and start adding dataverses
18:01 pdurbin
donsizemore: I guess I would think about what your users would want. My guess is that they would be surprised to see test data in there but maybe I'm wrong.
18:01 donsizemore
a friend here at UNC adopted a stray and she's now in heat. yesterday his swedish ivy forsook its windowsill
18:02 pdurbin
:)
18:03 pdurbin
bencomp is one of your potential users :)
18:03 donsizemore
pdurbin: for my purposes, i want a "put it in production" playbook. but say a demo group_vars file could set options or run scripts to automate whatever the community thinks it should
18:04 * bencomp
is troubleshooting our DVN3 service
18:05 pdurbin
donsizemore: if your playbook worked on Ubuntu I'd be fine with bare bones. I'd tell Travis to do any additional setup I need with my own scripts.
18:06 donsizemore
i'm testing on CentOS7 but can fire it off on Ubuntu next
18:06 pdurbin
sweet
18:06 donsizemore
anything OS specific has an ansible_os_family switch in it
18:06 pdurbin
donsizemore: I thought you said shib was next :)
18:07 donsizemore
i have a Viking gas range with many burners. now if i could only learn to cook properly
18:07 pdurbin
bencomp: troubleshoot it in the head
18:08 metamattj joined #dataverse
18:10 bencomp
"Please be aware that files uploaded before the end of the maintenance window may be lost."
18:11 pdurbin
yikes
18:12 bencomp
they are likely not lost, because DVN doesn't clean up after itself
18:12 bencomp
:(
18:13 pdurbin
:(
18:13 pdurbin
hopefully Dataverse 4 is better about this but I don't know honestly
18:13 bencomp
one user got a strange call after 6PM... from me. "Are you uploading files right now?"
18:14 bencomp
we've seen similar mess with Dataverse 4
18:14 bencomp
but not necessarily related
18:15 bencomp
time to go home though
18:15 pdurbin
:(
18:15 pdurbin
bencomp: please open an issue with specifics when you have time
18:24 bencomp
added to to-do list
18:24 pdurbin
thanks
18:24 bencomp
now to go home before I'm kicked out
18:24 pdurbin
have a good night
18:37 cnk joined #dataverse
18:41 donsizemore joined #dataverse
19:12 balo joined #dataverse
19:12 donsizemore
what's the general level of interest in Dataverse http/https logs?
19:16 pdurbin
donsizemore: you mean analyzing them with logstash or whatever?
19:17 donsizemore
correct. how many folks do we think use Google Analytics, etc.
19:19 pdurbin
well
19:19 pdurbin
have you seen this? User usage statistic · Issue #2729 · IQSS/dataverse - https://github.com/IQSS/dataverse/issues/2729
19:29 donsizemore
excellent point; I just forwarded that on to Jon and Akio
19:30 pdurbin
pretty different than logstash though...
19:31 * pdurbin
wants logstash
19:31 pdurbin
I'm hearing that Splunk may be available to us some day in production. I hope so.
19:33 pdurbin
donsizemore: what is your use case for the http logs?
19:34 donsizemore
i'll cede to jon or akio for that. i was just deciding what, if anything, to do with the http/https logs in my ansible playbook
19:40 pdurbin
donsizemore: you mean apache logs, right? not "access" logs (when enabled) in glassfish
19:40 donsizemore
whoops yes
19:41 pdurbin
recently I was trying to crunch apache logs with awstats. old school, I know
19:43 pdurbin
donsizemore: I just forwarded an email to you if you're interested. has a screenshot
19:54 donsizemore
pdurbin: thank you =) I'm sending that to Jon and Akio as well.
20:21 bencomp joined #dataverse
20:51 axfelix joined #dataverse
22:12 pdurbin
cool
22:19 pdurbin
bencomp: you might like this computation stuff: http://irclog.greptilian.com/sourcefu/2015-12-09 :)
22:24 bencomp
pdurbin: you symlink the directory that holds temporary files to a place outside the Glassfish directory, right?
22:27 bencomp
which is a question not related to computation
22:34 axfelix joined #dataverse
