[INSTRM-112] Develop and fix configurations of ICS CB2F storage Created: 02/May/17  Updated: 05/Apr/19  Resolved: 05/Apr/19

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

Type: Epic Priority: Major
Reporter: shimono 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-22 [ICD] Standard configuration (uid/gid... Done
Relates
relates to INSTRM-33 BEE storage management document Won't Fix
Epic Name: ICS-Storage
Sprint: 2017-10A

 Description   

We need to fix configurations on:

  • Network connections including storage server, NFS server and related devices
  • SCSI LUN configuration and host mapping
  • Endpoint configuration for exporting resources (NFS server etc.)
  • NFS server mount point and permission (incl uid/gid) scheme

Permission and uid issue is filed and under discussion as INSTRM-22.

 Comments   
Comment by shimono [ 05/Oct/17 ]

As we have delivered storage to the production (summit), we need to define this. Total amount of available space is 108TB.
Current assumption by shimono and cloomis is:

  • keep assigning one LUN for DB, direct mount as iSCSI
  • temporary assume one LUN for all detector storage, CCD, IR, AG, MCS, etc.
  • assign one LUN for eups running output (logs etc.) and some of production
  • consider misc stroage, data backup etc. also

Possible allocation of space are:

  • 5TB for VM guest images (20GB each, capacity 250 for both active and backup)
  • 10TB for postgresql database storage (incl. WAL etc.)
  • 10TB for operational data incl. log, running output, etc.
  • 10TB for backup area
  • 70TB for production (FITS) data
Generated at Sat Feb 10 16:21:40 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.