2 - Ordering a project on the container platform

Required information for the order:

1. Person in charge
   
   • Must have a contractual relation with the University.
2. Project owner
   
   • Must have a contractual relation with the University. Can be the same or a different person from "person in charge"
3. Technical contacts
   
   • One or more – it is recommended to have at least two! Technical contacts also must have a contractual relation with the University.
   • These technical contacts are the primary contacts for cluster administrators to reach out for when there are pressing technical issues regarding the project (such as serious security vulnerabilities etc.)
4. IAM-group, who are given administrative privileges for the OpenShift project
   
   • The group must exist when making the order, if the group does not exist the order will not be accepted.
   • The IAM-group will be added to a group for OpenShift users. This group can be used for emails regarding abnormalities in the container platform.
   •  Anyone with university user account can create and modify their own IAM groups with the https://idm.helsinki.fi tool, instructions at https://helpdesk.it.helsinki.fi/en/instructions/other-instructions/group-management-tool-iam
   • While not strictly required, we do in practice expect the "technical contacts" listed in point 3 to be members of this IAM group. This group membership is the one and only way for user to have access to the project in container platform.
5. Project name
   
   • Names assigned to existing projects are off-limits.
   • Forbidden phrases in the name include: "kube", "openshift" tai "default".
   • Allowed charactes:  small letters a-z, dash '-', numbers 0-9.
   • Container administration reserves the right to change the project name if/when necessary.
   • Words relating to the environment, such as "test" or "qa" are not necessary. The project will be initialized in both the test and production clusters, differentiation between production and staging should be done using these.
6. Project description
   • Your words here
7. WBS
8. Link to application porftolio (e.g sovellussalkku.it.helsinki.fi application, or if that does not exist, version.helsinki.fi repository)
   
   • If your project is in an application portfolio, link it here. If for some reason your project is not in a portfolio, you can give an explanation why you still need your project to run on the container platform. Smaller applications can be accepted with a less comprehensive process (without a portfolio).
   • Note 1: In the application portfolio you must reference the application. Do not copy the url from your browser, instead click the  -symbol from the basic information view, from there you can copy the correct link.
   • Note 2: If your project needs more services from the cluster administration, e.g egress IP, your project needs to be defined in a project portfolio.
9. Technical information which is the Quota for your project
   1. CPU
   2. RAM
   3. (If necessary) persistent storage.
      
      More detailed information can be found here: Tilauslomakkeen "teknisistä tiedoista" (Copy)