Explore
For Enterprise
Join for Free
Log In

艺术与人文
商务
计算机科学
数据科学
信息技术
健康
数学和逻辑
个人发展
物理科学与工程
社会科学
语言学习
學位
證書

瀏覽 Coursera 的全部課程

瀏覽
搜索
企業版
登錄
免費加入

Hiérarchie des ressources de Google Cloud Platform

Loading...

Google Cloud Platform Fundamentals: Core Infrastructure en Français

Google 云端平台

4.7（15 個評分） | 755 名學生已註冊

課程 1（共 6 門，Architecting with Google Cloud Platform en Français 專項課程）

Les participants intéressés par Google Cloud Platform peuvent continuer leur apprentissage en suivant l'une de nos nouvelles spécialisations consacrées à l'infrastructure de GCP. Option 1 : La spécialisation Developing Applications with Google Cloud Platform est disponible depuis peu sur Coursera. Vous y apprendrez à créer des applications cloud natives sécurisées, évolutives et intelligentes. Rendez-vous sur https://www.coursera.org/specializations/developing-apps-gcp pour en savoir plus. Option 2 : La spécialisation Architecting with Google Cloud Platform est également disponible. Son contenu a été mis à jour et amélioré. Cette spécialisation vous aidera à préparer l'examen Google Certified Professional – Cloud Architect. Accédez à https://www.coursera.org/specializations/gcp-architecture pour explorer le contenu mis à jour. Le cours Google Cloud Platform Fundamentals: Core Infrastructure couvre les bases de Google Cloud Platform et constitue le premier cours de ces deux spécialisations. Il présente des concepts et termes importants de Google Cloud Platform (GCP). Vous y découvrirez et pourrez comparer de nombreux services de calcul et de stockage disponibles dans Google Cloud Platform, dont Google App Engine, Google Compute Engine et Google Container Engine. Remarques : • Vous avez besoin d'un compte Google/Gmail, et d'une carte de crédit ou d'un compte bancaire pour vous inscrire à l'essai gratuit de Google Cloud Platform. (Les services Google sont actuellement indisponibles en Chine.) • Si votre adresse de facturation pour les services GCP est située en Union européenne (UE) ou en Russie, lisez la documentation relative à la TVA à l'adresse suivante : https://cloud.google.com/billing/docs/resources/vat-overview. • Vous trouverez d'autres questions fréquentes relatives à l'essai gratuit de GCP à l'adresse suivante : https://cloud.google.com/free/?hl=fr.

查看授課大綱

審閱

4.7（15 個評分）

5 stars
11 ratings
4 stars
4 ratings

從本節課中

Premiers pas avec Google Cloud Platform

Les clients GCP utilisent des projets pour organiser leurs ressources. Ils font appel à la gestion de l'authentification et des accès de Google Cloud, également appelée "IAM", pour contrôler quels utilisateurs peuvent effectuer quelles actions sur ces ressources. Ils utilisent les différentes technologies à leur disposition pour se connecter à GCP. Ce module traite chacun de ces sujets, et présente un service appelé Cloud Launcher qui permet de faire ses premiers avec GCP en toute simplicité.

Hiérarchie des ressources de Google Cloud Platform5:51

教學方

Google Cloud Training

腳本

You may find it easiest to understand the GCP resource hierarchy from the bottom up.

All the resources you use,

whether they're virtual machines, cloud storage buckets,

tables and big query or anything else in GCP are organized into projects.

Optionally, these projects may be organized into folders.

Folders can contain other folders.

All the folders and projects used by

your organization can be brought together under an organization node.

Project folders and organization nodes are all places where the policies can be defined.

Some GCP resources, let you put policies on individual resources too.

Like those cloud storage buckets I mentioned.

We'll talk more about cloud storage later in the course.

In the meantime, remember that policies are inherited downwards in the hierarchy.

All Google Cloud platform resources belong to a project.

Projects are the basis for enabling and using GCP services like managing APIs,

enabling billing and adding and removing

collaborators and enabling other Google services.

Each project is a separate compartment and each resource belongs to exactly one.

Projects can have different owners and users,

they're built separately and they're managed separately.

Each GCP project has a name and a project ID that you assign.

The project ID is a permanent unchangeable identifier and it has to be unique across GCP.

You use project IDs in several contexts to tell GCP which project you want to work with.

On the other hand, project names are for your convenience and you can assign them.

GCP also assigns each of your projects a unique

project number and you'll see a display to you in various contexts.

But using it is mostly outside the scope of this course.

In general, project IDs are made to be

human readable strings and you'll use them frequently to refer to projects.

You can organize projects into folders although you don't have to.

They're tool at your disposal to make your life easier.

For example, you can use folders to represent different departments,

teams, applications or environments in your organization.

Folders let teams have the ability to delegate administrative rights,

so they can work independently.

The resources in a folder inherit I am policies from the folder.

So, if project three and four are administered by the same team by design,

you can put I am policies into folder B instead.

Doing it the other way,

putting duplicate copies of those policies on

project three and project four would be tedious and error prone.

One word of caution, to use folders,

you need an organization node at the top of the hierarchy.

So what's that? Let's talk about it now.

You probably want to organize all the projects in your company into a single structure.

Most companies want the ability to have centralized visibility

on how resources are being used and to apply policy centrally.

That's what the organization node is for.

It's the top of the hierarchy.

There are some special roles associated with it.

For example, you can designate

an organization policy administrator so that

only people with privilege can change policies.

You can also assign a project creator role,

which is a great way to control who can spend money.

So how do you get an organization node?

In part the answer depends on whether your company is also a Gswee customer.

If you have a Gswee domain,

GCP projects will automatically belong to your organization node.

Otherwise, you can use google cloud identity to create one.

Here's a tip, when you get a new organization node,

it lets anyone in the domain create

projects and billing accounts just as they could before.

That's to avoid surprises and disruption.

But it be a great first step with a new organization node to

decide who on your team should really be able to do those things.

Once you have an organization node,

you can create folders underneath it and put it in projects.

Here's an example of how you might organize your resources.

There are three projects each of which uses resources from several GCP services.

In this example, we haven't used

any folders although we could always move projects into folders.

Resources inherit the policies of their parent resource.

For instance, if you set a policy at the organization level,

it is automatically inherited by all its children projects.

And this inheritance is transitive,

which means that all the resources in those projects inherit the policy too.

There's one important rule to keep in mind.

The policies implemented at a higher level in

this hierarchy can't take away access that's granted at a lower level.

For example, suppose that a policy applied on

the bookshelf project gives user PAC the right to modify a cloud storage bucket,

but a policy at the organization level says that PAC can only

view cloud storage buckets not change them.

The more generous policy is the one that takes effect.

Keep this in mind as you design your policies.

探索我們的目錄

免費加入並獲得個性化推薦、更新和優惠。

Coursera 致力於普及全世界最好的教育，它與全球一流大學和機構合作提供在線課程。

© 2019 Coursera Inc. 保留所有權利。

通過 App Store 下載

通過 Google Play 獲取

Coursera
關於
管理團隊
工作機會
目錄
證書
MasterTrack™ 證書
學位
企業版
政府版

社區
Learners
Partners
Developers
Beta Testers
Translators

連接
博客
Facebook
領英
Twitter
Instagram
YouTube
技術博客

更多
條款
隱私
幫助
內容訪問
媒體
聯繫我們
目錄
附屬公司