Any GCP resources that you allocate and use must belong to a project. You can think of a project as the organizing entity for what you're building. A project is made up of the settings, permissions, and other metadata that describe your applications. Resources within a single project can work together easily, for example by communicating through an internal network, subject to the regions-and-zones rules. The resources that each project contains remain separate across project boundaries; you can only interconnect them through an external network connection.
Each GCP project has:
A project name, which you provide.
A project ID, which you can provide or GCP can provide for you.
A project number, which GCP provides.
As you work with GCP, you'll use these identifiers in certain command lines and API calls. The following screenshot shows a project name, its ID, and number:
Each project ID is unique across GCP. Once you have created a project, you can delete the project but its ID can never be used again.
When billing is enabled, each project is associated with one billing account. Multiple projects can have their resource usage billed to the same account.
A project serves as a namespace. This means every resource within each project must have a unique name, but you can usually reuse resource names if they are in separate projects. Some resource names must be globally unique. Refer to the documentation for the resource for details.
References:
https://cloud.google.com/docs/overview/
No comments:
Post a Comment