Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Story Points:4
-
Sprint:TSSW Sprint - Oct 12 - Oct 26
-
Team:Telescope and Site
-
Urgent?:No
Description
This task covers the time spent on the summit working on getting the M2 Server back online.
Attachments
Issue Links
- relates to
-
- Done
Activity
| Field | Original Value | New Value |
|---|---|---|
| Sprint | TSSW Sprint - Oct 12 - Oct 26 [ 1051 ] | |
| Team | Telescope and Site [ 13500 ] |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Link | This issue is blocked by IHS-4270 [ IHS-4270 ] |
| Labels | Summit |
| Story Points | 3 | 4 |
Both the M2 Servre and the Hexapod Rotator are on the summit and connected to the control network with some networking issues that need to be resolved. To better communicate our requirements to IT I am creating a ticket to represent a visual diagram on the elements we are working on and how we want them connected on the network.
Until October 19 we are blocked on two things. One is that the video output of the M2 sever is not working and so Franco is unable to do testing. The second is the I also requested to have a laptop connected to a private network to act as the VNC Client for the Hexapod / Rotator Server
These tickets cover some scopes of work that we need.
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
| Summary | M2 Server Startup | Summit Startup M2 & Rot/hex |
Andrew did a great job to support the summit activity!
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |
| Epic Link |
|
1st day completed. Te-Wei and I were able to get the GUI showing up on the servers and connected to the control network. Similiarly for the Hexapod Rotator server.
We are now waiting for IT to complete some work on their end so that the control network can be SSH'd to by someone on the VPN to be able to access the server computers.