프로젝트의 상위 조직 리소스에 대해 resourcemanager.organizations.get 권한이 없으면 Google Cloud 콘솔의 실제 조직 아래에서 프로젝트가 예상한 대로 반영되지 않을 수 있습니다. 그 결과 프로젝트가 조직 리소스와 연결되지 않은 것으로 보일 수 있습니다.
프로젝트가 조직 리소스와 연결되었는지 확인하려면 다음을 수행합니다.
gcloud
다음 명령어를 실행합니다.
gcloud projects describe PROJECT_ID
PROJECT_ID를 마이그레이션하려는 프로젝트 ID로 바꿉니다.
상위 리소스가 출력에 표시되지 않으면 프로젝트가 조직 리소스와 연결되지 않은 것입니다.
상위 리소스(폴더 또는 조직 리소스)가 출력에 표시되면 프로젝트가 조직 리소스와 연결된 것입니다.
프로젝트 리소스는 Google Cloud 조직 리소스의 기본 수준 구성 항목입니다. 프로젝트는 조직 리소스 아래에 생성되며 리소스 계층 구조를 형성하는 폴더 또는 조직 리소스 자체에 배치될 수 있습니다.
무엇보다도 인수, 규제 요구사항, 비즈니스 단위 간 구분으로 인해 조직 리소스 간에 프로젝트를 마이그레이션해야 합니다.
Resource Manager API를 사용하여 조직 리소스 사이에 프로젝트를 마이그레이션할 수 있습니다.
또한 Resource Manager API를 사용하여 마이그레이션을 롤백하고, 리소스 계층 구조에서 원래 위치로 프로젝트를 되돌릴 수 있습니다.
할당량 영향
특정 리소스 수준에서 정의된 할당량이 있으면 마이그레이션 후에 다음 특성이 적용됩니다.
프로젝트 수준에서 정의된 할당량은 변경되지 않은 상태로 유지됩니다.
조직 리소스 수준에서 정의된 모든 할당량은 이전되지 않습니다. 조직에서 상속된 모든 할당량을 잃습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-21(UTC)"],[],[],null,["# Migrating projects between organization resources\n\nThis guide explains the following migration scenarios:\n\n- Migration of projects from one organization to another organization resource.\n- Migration of projects that were created with no associated organization resource into the hierarchy of an organization resource.\n\nIf you don't have the `resourcemanager.organizations.get` permission on the\nparent organization resource of the project, it's likely that your projects\ndon't reflect as expected under the actual organization in the\nGoogle Cloud console. This can make it seem like the project is not associated\nwith any organization resource.\n\nTo determine whether the project is associated with an organization resource, do\nthe following: \n\n### gcloud\n\nRun the following command: \n\n```\ngcloud projects describe PROJECT_ID\n```\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the ID of the project that you want to\nmigrate.\n\nIf the **parent** resource is *not* displayed in the output, it confirms\nthat the project is not associated with an organization resource.\n\nIf the **parent** resource (folder or organization resource) is displayed in\nthe output, it confirms that the project is associated with an organization\nresource.\n\nFor more details related to migrating projects, see the following:\n\n- If you want to migrate projects that were created with no associated organization, see [Migrate projects with no organization resource](/resource-manager/docs/handle-special-cases#migrating_projects_no_org).\n- If you want to migrate projects from one organization to another organization resource, see the detailed [project migration checklist](/resource-manager/docs/project-migration-checklist).\n\n| **Note:** If you want to transfer Google Workspace domains between organization resources, contact your Support representative.\n\nThe project resource is the base-level organizing entity in a\nGoogle Cloud organization resource. Projects are created under\norganization resources, and can be placed under folders or the organization\nresource itself, forming the\n[resource hierarchy](/resource-manager/docs/cloud-platform-resource-hierarchy).\nYou may need to migrate projects between organization resources due to\nacquisitions, regulatory requirements, and separation between business units,\namong other things.\n\nYou can use the Resource Manager API to migrate projects between organization resources.\nThe Resource Manager API also lets you roll back the migration, moving the\nproject back to its original place in the resource hierarchy.\n| **Note:** It generally takes less than a minute for the project migration to complete. After migrating a project between organization resources, it may take several minutes to reflect this change in the Google Cloud console. For information about finding the current details of a project, see [Creating and managing projects](/resource-manager/docs/creating-managing-projects#get_an_existing_project).\n\nQuota impact\n------------\n\nIf you have quotas defined at a certain resource level, the following aspects are applied after migration:\n\n- Any quotas defined at the project level remain unchanged.\n- Any quotas defined at the organization resource level are *not* transferred. The organization loses any inherited quotas.\n\nThe following pages can be used to determine what quotas are applied to an organization resource:\n\n- [View and manage quotas](/docs/quotas/view-manage)\n- [List quotas with gcloud](/sdk/gcloud/reference/alpha/services/quota/list)\n- [List quotas with RPC](/service-usage/docs/reference/rest/v1beta1/services.consumerQuotaMetrics/list)\n- [Example quota bucket](/service-usage/docs/reference/rest/v1beta1/services.consumerQuotaMetrics.limits#quotabucket)\n\n### Example\n\n $ gcloud alpha services quota list --service=compute.googleapis.com --consumer=projects/workloadyee --filter=\"metric: compute.googleapis.com/cpus\"\n\n ...\n - defaultLimit: '600'\n dimensions:\n region: us-central1\n effectiveLimit: '650'\n ...\n\nWhat's next\n-----------\n\nTo learn about the tasks involved in migrating projects, see the [project migration checklist](/resource-manager/docs/project-migration-checklist)."]]
