Product SiteDocumentation Site

6.2. Configuring Projects

Before CloudPlatform users start using projects, the CloudPlatform administrator must set up various systems to support them, including membership invitations, limits on project resources, and controls on who can create projects.

6.2.1. Setting Up Invitations

CloudStack can be set up either so that project administrators can add people directly to a project, or so that it is necessary to send an invitation which the recipient must accept. The invitation can be sent by email or through the user’s CloudStack account. If you want administrators to use invitations to add members to projects, turn on and set up the invitations feature in CloudStack.
  • Log in as administrator to the CloudStack UI.
  • In the left navigation, click Global Settings.
  • In the search box, type project and click the search button.
  • In the search box, type project and click the search button. searchbutton.png: Searches projects
  • In the search results, you will see a few other parameters you need to set to control how invitations behave. The table below shows global configuration parameters related to project invitations. Click the edit button to set each parameter
    Configuration Parameters
    Description
    project.invite.required
    Set to true to turn on the invitations feature.
    project.email.sender
    The email address to show in the From field of invitation emails.
    project.invite.timeout
    Amount of time to allow for a new member to respond to the invitation.
    project.smtp.host
    Name of the host that acts as an email server to handle invitations.
    project.smtp.password
    (Optional) Password required by the SMTP server. You must also set project.smtp.username and set project.smtp.useAuth to true.
    project.smtp.port
    SMTP server’s listening port.
    project.smtp.useAuth
    Set to true if the SMTP server requires a username and password.
    project.smtp.username
    (Optional) User name required by the SMTP server for authentication. You must also set project.smtp.password and set project.smtp.useAuth to true..
  • Restart the Management Server 
    service cloud-management restart

6.2.2. Setting Resource Limits for Projects

The CloudStack administrator can set global default limits to control the amount of resources that can be owned by each project in the cloud. This serves to prevent uncontrolled usage of resources such as snapshots, IP addresses, and virtual machine instances. Domain administrators can override these resource limits for individual projects with their domains, as long as the new limits are below the global defaults set by the CloudStack root administrator. The root administrator can also set lower resource limits for any project in the cloud

6.2.2.1. Setting Per-Project Resource Limits

The CloudStack root administrator or the domain administrator of the domain where the project resides can set new resource limits for an individual project. The project owner can set resource limits only if the owner is also a domain or root administrator.
The new limits must be below the global default limits set by the CloudStack administrator (as described in Section 6.2.2, “Setting Resource Limits for Projects”). If the project already owns more of a given type of resource than the new maximum, the resources are not affected; however, the project can not add any new resources of that type until the total drops below the new limit.
  1. Log in as administrator to the CloudStack UI.
  2. In the left navigation, click Projects.
  3. In Select View, choose Projects.
  4. Click the name of the project you want to work with.
  5. Click the Resources tab. This tab lists the current maximum amount that the project is allowed to own for each type of resource.
  6. Type new values for one or more resources.
  7. Click Apply.

6.2.2.2. Setting the Global Project Resource Limits

  1. Log in as administrator to the CloudStack UI.
  2. In the left navigation, click Global Settings.
  3. In the search box, type max.projects and click the search button.
  4. In the search results, you will see the parameters you can use to set per-project maximum resource amounts that apply to all projects in the cloud. No project can have more resources, but an individual project can have lower limits. Click the edit button to set each parameter. editbutton.png: Edits parameters
    max.project.public.ips
    Maximum number of public IP addresses that can be owned by any project in the cloud. See About Public IP Addresses.
    max.project.snapshots
    Maximum number of snapshots that can be owned by any project in the cloud. See Working with Snapshots.
    max.project.templates
    Maximum number of templates that can be owned by any project in the cloud. See Working with Templates.
    max.project.uservms
    Maximum number of guest virtual machines that can be owned by any project in the cloud. See Working With Virtual Machines.
    max.project.volumes
    Maximum number of data volumes that can be owned by any project in the cloud. See Working with Volumes.
  5. Restart the Management Server. 
    # service cloud-management restart

6.2.3. Setting Project Creator Permissions

You can configure CloudStack to allow any user to create a new project, or you can restrict that ability to just CloudStack administrators.
  1. Log in as administrator to the CloudStack UI.
  2. In the left navigation, click Global Settings.
  3. In the search box, type allow.user.create.projects.
  4. Click the edit button to set the parameter. editbutton.png: Edits parameters
    allow.user.create.projects
    Set to true to allow end users to create projects. Set to false if you want only the CloudStack root administrator and domain administrators to create projects.
  5. Restart the Management Server. 
    # service cloud-management restart