Changes between Version 1 and Version 2 of StoryLinkWomToVm


Ignore:
Timestamp:
2011-11-25T21:52:30+01:00 (13 years ago)
Author:
Morris Swertz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • StoryLinkWomToVm

    v1 v2  
    1 As LL admin we want to connect each WOM to the proper VM
    2 
     1== As LL admin we want to connect each WOM to the proper VM ==
    32Scrum: ticket:1053
    43
    54Acceptance criteria:
     5* There is a WOM available to the MOLGENIS developers.
     6* When a browser is opened in the WOM accesses molgenis@VM at CIT (e.g. application32)
     7* When ssh is used in the WOM it can reach the VM (e.g. application32)
     8* When ssh is used in the WOM it can reach the cluster.gcc.rug.nl (future: cluster.lifelines.target.nl)
     9* When using the browser, no other websites can be reached
     10* When using ssh, no other servers can be reached
    611
    7 There is a WOM available to the MOLGENIS developers.
    8 When a browser is opened in the WOM accesses molgenis@VM at CIT (e.g. application32)
    9 When ssh is used in the WOM it can reach the VM (e.g. application32)
    10 When ssh is used in the WOM it can reach the cluster.gcc.rug.nl (future: cluster.lifelines.target.nl)
    11 When using the browser, no other websites can be reached
    12 When using ssh, no other servers can be reached
    1312Status:
     13* unknown!
    1414
    15 unknown!
    1615FAQ:
    17 
    18 WOM is a Windows 7 based virtual desktop hosted at UMCG. VM is a virtual Linux box living at CIT. There are several VPNs between UMCG and CIT.
     16* WOM is a Windows 7 based virtual desktop hosted at UMCG. VM is a virtual Linux box living at CIT. There are several VPNs between UMCG and CIT.
    1917How to link all of this together? Is someone working on this?