- GCP Projects form the basis for creating, enabling and using all GCP Services including managing APIs, enabling billing, adding and removing collaborators, and managing permissions for GCP resources.
- Project are logical units which consumes a bunch of resources.
- The Project associated with account and accounts with organization.
- Project = Resource + Setting + Metadata
- The Project associated with or defined by 3 piecees of Metadata
- name, ID and the number.
- Project ID is unique & permement.
-
It is root node in GCP hierarchy (super node)
-
Organizational ID is unique identifier, automatically created.
- Message with certain amount of billed
- Can be on project or plan
- Who will pay for
- Access control to biling account is established by cloud IAM roles
- BA can be linked to one or more project
- Self Serve
- When billed , it will be charged
- cost are charged automatically
- by Credit or debit card
- Invoiced
- After month end
- Wire transfer or check
- Invoices are mailed.
- Monthly Billing
- cost are charged on regular Monthly cycle
- Threshold Billing
- Cost are charged when your account has accured a specific amount
- Invoiced billing account arre always billed monthly. =
- A BA includes a set of contract, defines on Google payments profile
- user can manage those contract through GCP console of the payment console
- Allows user to group charges from projects together on seprate section of Invoice
=
- Ownership refers to Cloud IAM permission inheritance.
- payment linkages define, which account pays for a given projetc.
- in diagram, the organizzation hsa owenership over the billing account & project 1,2,3 means it is cloud IAM permission parent of 3 Projects
- BA is linked to Projects 1,2 &3
- The billing account is connected to a google payment profile
- Although you can link billing account to project, billing account are not parents of Cloud IAM , so project dont inherit permissions form biling account they are linked to .
==========================