<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Make an environment that can be accessed by the public?</title>
  <link rel="alternate" href="https://conferences.xsede.org/c/message_boards/find_thread?p_l_id=&amp;threadId=2506917" />
  <subtitle>Make an environment that can be accessed by the public?</subtitle>
  <entry>
    <title>RE: Make an environment that can be accessed by the public?</title>
    <link rel="alternate" href="https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=2507419" />
    <author>
      <name>Brian Wayne Beck</name>
    </author>
    <id>https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=2507419</id>
    <updated>2020-07-07T03:49:08Z</updated>
    <published>2020-07-07T03:49:08Z</published>
    <summary type="html">Yes. You could use a Jetstream VM.&lt;br /&gt;You’d have to:&lt;br /&gt;* get an allocation&lt;br /&gt;* request enough service units (cores * hours) to cover a server running during the window of time the reviewers would use it. It would likely need to be 24/7 since you wouldn’t know when the reviewers would access the VM.&lt;br /&gt;* request API access because standard access does not include a static IP&lt;br /&gt;* deploy a VM and customize it with your software stack&lt;br /&gt;* create one or more custom user accounts unique to your VM, the credentials of which could be shared with reviewers&lt;br /&gt;&lt;br /&gt;The only problematic part would be making sure the VM was deployed during a window you KNEW the reviewers would use it. You could of course request 8760 x cores to run 24/7/365 but that’s brute force.&lt;br /&gt;&lt;br /&gt;There are smarter more elegant ways to do this that I’d be happy to talk to you about. I also recommend you consider talking to the folks at https://sciencegateways.org to get advice.&lt;br /&gt;&lt;br /&gt; -Brian Beck&lt;br /&gt;&lt;br /&gt;help@jetstream-cloud.org</summary>
    <dc:creator>Brian Wayne Beck</dc:creator>
    <dc:date>2020-07-07T03:49:08Z</dc:date>
  </entry>
  <entry>
    <title>Make an environment that can be accessed by the public?</title>
    <link rel="alternate" href="https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=2506916" />
    <author>
      <name>John F B</name>
    </author>
    <id>https://conferences.xsede.org/c/message_boards/find_message?p_l_id=&amp;messageId=2506916</id>
    <updated>2020-07-06T19:42:43Z</updated>
    <published>2020-07-06T19:41:27Z</published>
    <summary type="html">Dear all,&lt;br /&gt;I&amp;#039;m new to the Jetstream/XSEDE environment.  I was pointed in this direction because I have developed some programs that are used for interpreting mass spectrometry data.  I want to publish those programs but to do so I need to make them readily accessible to reviewers.  So someone suggested that I create a virtual machine on Jetstream and share it with the reviewers.  &lt;br /&gt;&lt;br /&gt;In discussion with the journal though, I was told that for anonymity&amp;#039;s sake the reviewers need to be able to access the system *without registration or login*.  So they must not create an XSEDE account in order to access the system. &lt;br /&gt;&lt;br /&gt;I was wondering if it was still possible to use this avenue though, by creating a virtual machine that would be publicly accessible without registration or login.  Again I&amp;#039;m very new to this system so I don&amp;#039;t know if what I&amp;#039;m asking for is impossible or what, but I&amp;#039;m wondering if it can be done on Jetstream.  I did a search for this both on https://portal.xsede.org/jetstream and on these forums and didn&amp;#039;t think I found an answer, which is why I&amp;#039;m asking here.&lt;br /&gt;&lt;br /&gt;Thank you for your time</summary>
    <dc:creator>John F B</dc:creator>
    <dc:date>2020-07-06T19:41:27Z</dc:date>
  </entry>
</feed>

