[INSTRM-159] Develop software installation procedure using Ansible Created: 27/Jul/17  Updated: 18/Mar/23  Resolved: 18/Mar/23

Status: Won't Fix
Project: Instrument control development
Component/s: Summit infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: shimono Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: ICS-SETUP

 Description   

We are about to plan to use Ansible for PFS ICS host configuration works.
We need to develop plans on:

  • how wide we plan to execute host configuration using Ansible (at least actors are by eups)
  • define standard organization of configuration files following defacto-standard of Ansible
  • repository system definition and management

We may be better to have dedicated repository on this.

 Comments   
Comment by shimono [ 04/Apr/18 ]

for common roles required over system wide, we will have:

  • system-accounts
  • iptables
  • packages
  • cron-apt
  • ntp
  • rsyslog-client
  • exim4
  • (ldap: to be checked)

for CB2F physical hosts for infrastructure, we will have two category, one is VM host and another is FC/iSCSI mount with NFS export. so, it could be

  • fc-nfs: host to mount FC/iSCSI and exports via NFS
  • virt: VM host, with fc-nfs as virt:children
  • dell: physical computer from dell, with virt (and other device control computers) as dell:children

for each group, required roles are:

  • fc-nfs: iscsi, nfs-server
  • virt: virt
  • dell: hwraid
    but we need to omit /virt mount for fc-nfs (or just a special host which exports /virt?)
Comment by shimono [ 04/Apr/18 ]

considering not to make dependencies in inventory files messy,

  • groups in inventory files just contain hosts
  • define groups in playbook as a collection of groups in inventory with :children
    also,
  • add flag not to set nfs mount into virt role
Comment by arnaud.lefur [ 18/Mar/23 ]

need to discuss with yuki.moritani and Yoshida, Hiroshige

Comment by yuki.moritani [ 18/Mar/23 ]

No demand any more.

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