Cloud computing, Google Cloud Platform Understanding of Project, Folder and Organization in Google Cloud Platform (GCP)

So here you can see any google cloud resources that you allocate and use must belong to a project. That means lets say if you want to create any kind of services or if you want to use any vm instances or want to create bigquery table, big data, etc. So, whatever the service that you want to use that must belong to any project without the project. Google cloud will not allow to create or use any services because that how it works, but from this a project is made up of settings permission and other metadata that describe your application. Resource within a single project can work together easily, for example, by communicating through a internal network subject to the regions and zone through what it means lets say. You have selected one project and you want to create multiple networks which can be vpc network, for example, and lets say if you have created multiple vpc network and you want them to communicate with each other. So you dont have to use any external services like vbs appearing or sharing pc. Instead, you can grab the internal ip and with those internal light you can communicate with them. So that will you know, decrease your extra efforts for communicating with the vpc. So this this is one advantage that you will get by using the project. Now project has some, you know, uh format, so lets say this is c project name my first project. This is project number and this is project id.

So, in our case, uh project name and project id will be used will be useful in most of the scenarios like. If you want to uh set any particular resource or any uh region, then we have to use project id in in that particular thing that we will see in upcoming videos. So if you want to uh check the list of the project, then you can just go here and select the drop down and you will see the list of project right now. I only have one project which is created by default when we set up our account. So this is the project name, and this is the project id and if you want to create new project, then you can select from here just click on new project and you will get a project name lets say if i want to create demo demo project – and Here you can see it is sticking automatically project id sunny a misery. So this is basically decided by these uh system itself, but we can change it. You can go to edit and um lets say if i want to give a demo project one two three. So you can give it like this, but this is not available because maybe in past someone has used it and this cannot be reused in the future. So maybe i have to give something unit that has not been used in the past, so demo trade project, one two three projected you can have lowercase stitch its an iphone.

It must start with a lowercase letter and with the electron number it should be. Okay, yeah number one, two three, so this project is available. You can define um as per your convenience, so this is how it looks like and here organization. So basically, if you browse it, then you will see here no organization, because my account is not linked with any particular organization. So lets say if we are working for any particular xyz company, then that company has purchased some google suit. Uh g suite account for which they will have an email id, something like lets say. My name is uh through in so through it at the rate um or at the So if youre accessing from that email id, then you will definitely see an organization here, because you know they have purchased the google suit and youre accessing from that particular id. So right now i dont have uh. I have a personal id so um, you will not see anything here, but thats, fine, okay, this is it created and it is trying to create a project okay. So if you just click here – okay, maybe yeah – it is here demo project all right. Okay, so one thing is very important that we have to learn about uh the resource hierarchy, so lets just quickly go to the diagram and see uh. What is it so here? On top, you can see the organization and that organization can be your company, and your company has multiple folders like department um, you can have different teams, you have a products and that particular product can have different projects like development, taste, production and that particular project can Contain the different resources like, as we discussed earlier, that uh all of the resources that you create, that must belong to any project right, so this is how the hierarchy will look like, and you can definitely modify your own hierarchy depending on your requirement.

Okay, so now lets try to understand about access policy, so you can define policy on organization level, on folders level and on the project levels and itself on particular resources level as well. So what do i mean is lets say if i am giving any policy on the organization, so all the child loads? So this is basically a parent and this all are joined. So if i assign any policy here, then all the child components or nodes will automatically access that particular policy. So this is how, when uh policy will work and here to define an example um. So let me just quickly explain you what it is it so lets say if you have defined any policy here on department y to any person called bob at the which is working for this company. So if i am giving a project editor to bob at, then he can access all the child hierarchy, like uh team, a team b product one product two and this all the project and with this resistance as well. So he can access all this stuff because we have provided the permission is at this level. So this is basically a parent and this basically a child right now. The second example they have provided is lets say, if you assign instance, admin role on this test project to a lightsaber, so alice is basically another person who is looking for the same organization, but im assigning the instance.

Admin role for this particular project. Only and instant advantage. Basically, it means that you can only access this compute engine instances. You will not uh this allies version cannot access app engine or cloud storage bucket or any other projects or any other product or organization itself. So this is how the hierarchy will follow and you can, you know, learn more uh from this particular link. I will provide you the link in the description, so you can all go through it. Okay, so now let me go back to the console and we will create few instances um in the demo project and my first project and lets see how it works. So lets go back to compute engine select the vm instances so remember to use any services. You have to enable apis without enabling api you cant use any service, so thats how it works, lets wait for it, okay, so we are done with the enabling api like okay. Here we are so after enabling api. You can see this page as in vm instance. So now lets create one instance uh. We dont have to worry about this configuration that we will see in my upcoming videos so now lets just uh, accept it uh by default and read it okay, so it is not creating here in this demo project. Now let me also create one more instance in the different project. My first project. Okay, so here lets create it and i will give one any different name: demo accept it as default.

Lets create it okay, so maybe one thing you have noticed that when we selected this project um from demo project, so whatever the instance we have created in the demo project is not visible here right because uh, it implies that particular definition that whatever the resource you Create that will belong to a single project so for demo it is belonging to. It is belonging to this my first project, and if you go to the demo project, then you will see the instance one that we have created. So there would be no overlapping uh of your resources from one project to another, so it will be very easy to like if you, if you want to manage your resources, so this is kind of useful okay. Now, if you want to delete your project, then you can go to manage resources. Okay, here you can see we have a demo project and we have my first project so lets say. If i want to delete this demo project, you can click on delete and you will notice something here that the project will be scheduled to be deleted after 30 days. However, some resource may be deleted much earlier, so what it means when you uh proceed with the deletion, it will not delete immediately. It will delete after the 30 days from now, so that is uh beneficial because lets say. If you want to restore uh that particular project, then you can definitely distribute in 30 days uh.

So this have one one advantage, but now lets proceed to shutdown and well see what happens next. Okay, so now you can see this demo project is now shut down and scheduled to be deleted after fab seven. So this particular demo project will not visible now in your particular gcp platform and will be deleted after fab seven, so you can check it from resource pending deletion. If you go here, okay, you can see this demo project, which i have deleted and even you can restore from here. So if you restore it, it will just simply restore back to its uh uh. You know the project list, but we dont need it right now. So thats fine! So if you go back to home and if you click here so it is not gone, that means the page is not refreshed. Just refresh the page click one more time and its gone: okay, so thats how it work.

What do you think?

Written by freotech


Leave a Reply

Your email address will not be published. Required fields are marked *



Cloud computing, Google Cloud Platform Solvers Solving with Google Cloud: Featuring

Cloud computing, Google Cloud Platform – Dataproc