Projects
Every resource belongs to a project, and a token's project decides which resources you see and change.
A project is the container your resources belong to, such as servers, volumes, networks and images. Every token is scoped to one project, and services show and change only that project's resources.
For example, with a token for the project a6f1c2d93b8e4f07b5d4e2c1a9f8e7d6, listing servers
returns that project's servers only. Another project's resources are not visible: services refuse
requests for them, usually with 403 Forbidden or 404 Not Found.
Your projects
A user can have roles in several projects. List them, and see which one your current token is for:
openstack project list --my-projects
openstack token issue -c project_idChoosing a project
The CLI and the OpenStack SDKs use the project set in your credentials. To work in another
project, choose it for one command, for a shell, or in a clouds.yaml entry:
openstack --os-project-id 7d3e9b1c5a2f4e8d9c6b0a1f3e5d7c9b server list
export OS_PROJECT_ID=7d3e9b1c5a2f4e8d9c6b0a1f3e5d7c9bAn application credential always acts on the project it was created in. To automate work in several projects, create one credential per project.