Creating a new ROC

Infrastructure needed

• If relevant, the registration of a new DNS domain name
• The name of the new ROC, the ROC manager, the ROC manager's deputies, the ROC security contact.
• mailing list to contact the ROC, for ROC management purposes
• mailing list to contact the ROC for security purposes
• mailing list to contact the ROC for user support purposes
• Web site for the new ROC as a reference point for the public and maybe the administrators of the sites belonging to the ROC
• Internal twiki or other means of communication targeted at the members of the ROC team
• Certification infrastructure
  • A ROC bdii, containing the entries that are available in production, plus the services run at the site(s) to be certified
  • A WMS able to submit to the CE(s) belonging to the sites to be certified
  • A ROC Nagios (to double check, maybe the Standard ROC NAgios can also be used for certification)

A non-functional requirement for the infrastructure to be set up is that the ROC services be instantiated in site(s) with good proven network connection. This requirement won't be object of technical testing by the incubator, however it is strongly advised that the relevant servers be located at a site with good overall reliability (as documented by operational reports)

Security contacts

• The ROC security contact and mailing list must be communicated to OSCT

Servers needed

• ROC Nagios
• (Optional) Ticketing system
• ROC level copy of the top level BDII
• ROC certification BDII
• (Optional as SAMAP can be used) WMS for certification

Requests to central services

• Set up a (unique) date for the switch over with GOCDB, CIC portal, GGUS, SAM.

GOCDB

• Creation of ROC entry in the GOCDB
• Communication of the ROC management mailing list addresses
• Registration of people
• Request of relevant roles: ROC manager, ROC deputies, ROD.
• List of sites to be moved/created under the new ROC

CIC portal

• Notification to CIC portal of new entry in GOCDB
• Communication of the ROC mailing list address
• Registration of people
• Request of relevant roles: ROC manager, ROC deputies, ROD

SAM

• A modification has to be made into the SAM central database.

SAMAP

• Notify SAMAP of the new ROC creation
• Contact the administrator(s) of the WMS used by SAMAP so that the new ROC will be authorized to use it.

GGUS

• Notification to GGUS:
• Communication of the ROC user support mailing list address and FAQ
• Registration of people involved in the support team as supporters in GGUS

Operations Manual

• People in charge of the Operations Manual currently need to be informed

VOMS

• deciding on the name of the new VOMS group owner.
• Creation of the VOMS group under /dteam, for instance /dteam/la
• (Optional) creation of subgroups (e.g. /dteam/la/brazil), each with their owner
• Registration of people involved in the dteam VO

Checks after the creation

• Check that all the new ROC mailing lists work.

GOCDB

• Check that the new ROC is present
• Check that the ROC mailing lists are inserted correctly

CIC portal

• Check that the new ROC is present
• Check that all the sites belonging to the new ROC appear in the regional dashboard

SAM

• Check that the new ROC is present

GGUS

• Check that the new ROC appears on the submission form
• Check that all the sites belonging to the new ROC appears on the submission form
• Check that the new ROC appears on the search engine
• Open one ticket per site to check the correct work-flow is followed (direct notification to the site, ticket assigned to the new ROC)

Gridview

• Check that the new ROC is present

Gridmap

• Check that the new ROC is present

Accounting portal

• Check that the new ROC is present

-- DianaBosio - 2009-10-01