probcomp / probcomp-stack

MIT Probabilistic Computing Project software stack
4 stars 5 forks source link

Stack release for 2017-07-19 meeting #36

Open jar600 opened 7 years ago

jar600 commented 7 years ago

A stack release is required for dissemination to participants in a meeting that starts 19 July. It is desirable that the release and its documentation by ready for internal review by 17 July.

We are assuming for this purpose that the user is providing a server (which could be AWS but that's not our worry).

jar600 commented 7 years ago

Also, where should the download/install/run documentation page reside (in this repo? what directory?) and what sort of markup should it use (html? what css?)? (adding to checklist)

jar600 commented 7 years ago

c3.8xlarge = 32 cores, 60Gb

jar600 commented 7 years ago

Deployment options:

  1. Recommended configuration: a workstation that has at least 32 cores, 60G RAM, and a display and keyboard.
  2. Compromise: fewer cores and/or less RAM, leading to significant limitations in what data sets can be analyzed.
  3. It is also possible to run in client/server mode, but that is "outside the scope of this document" (?? two ways to get secure the connection: https, requiring a certificate and some fussy initialization; and ssh, requiring an ssh client).
axch commented 7 years ago
jar600 commented 7 years ago

I think you've already done a good job of documenting options, and your comment here fills in some useful details. What we need for Wednesday is to decide what to tell participants at the PI meeting regarding release; this entails removing options (from the release documentation) so that the explanation is as simple as we can bear. For this audience we cannot / will not provide AWS instances, so docker it is. My first draft of release notes is here: https://github.com/probcomp/probcomp-stack/blob/20170713-jar-releasepage/web/release-page.html . The subtext is that they'll want to use an ssh tunnel, but for some reason we're not supposed to say that outright, thus the peculiar explanation that's currently there. I'm sure what I've written will require major revision.