[INSTRM-291] Provide development computer(s) at Subaru Created: 08/Feb/18  Updated: 05/Apr/19  Resolved: 05/Apr/19

Status: Done
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: cloomis Assignee: shimono
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by INSTRM-70 Define procedure of configuration and... Done
is blocked by INSTRM-76 Develop way to monitor/manage VM inst... Won't Fix
is blocked by INSTRM-71 organization of dnsmasq configuration... Done
is blocked by INSTRM-149 Choose between NTP and PTP Done
is blocked by INSTRM-163 Allocation of CIDRs for subsystems on... Done
is blocked by INSTRM-183 Define hostname naming convention Done
is blocked by INSTRM-192 Assign MAC address for VMs Done
is blocked by INSTRM-204 Move unorganized configurations in ma... Done
is blocked by INSTRM-221 Add gateway VM guest at production Done

 Description   

Can we get to a computer at Hilo or the summit now for software development? It needn't be administered the same way as the final PFS machines. Something which has access to:

  • the tron hub
  • the STS server (sts.subaru.nao.ac.jp, I think).
  • some real OCS server
  • the PFS postgresql server
  • some /data directory

and on which we can run VNC servers. Obviously a VM would be fine.

The immediate need is to have a place to test the STS feed for MCS delivery, with full MHS machinery (tron, postgresql, alertsActor).

Certainly for development we need proper user accounts, with the usual shared group semantics.

If we already have an NFS /data server, can we get two development computers? If there will be any issues with synchronization between data writers and data readers we should discover those as soon as possible.

 Comments   
Comment by cloomis [ 04/Jul/18 ]

From my point of view this is done. We could open other tickets on the distribution of services, but shell-ics solved this ticket.

Generated at Sat Feb 10 16:23:28 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.