Projects

Creating Projects

If you want to divide your virtual resources among numerous users within each account, you need to create different projects within the account. It is possible to create either VPC-enabled projects, which is the default, or non-VPC-enabled, legacy projects.

The Admin user can create projects in any account, while the Tenant Admin can create projects only in the tenant admin’s own account.

To create a project:

  1. In the Identity & Access > Accounts > view for the specific account for which you wish to create a project, go to the Projects tab and click Create Project. The Create Project dialog box is displayed.

  2. Enter the following information:

    1. Project Name – Enter a name for the new project. The name must be unique within the account. Note: The names are not case-sensitive.

    2. Project Description [Optional] – Enter a description of the new project.

    3. IP Pool - Select one of the IP pools. If there is no available IP pool, request an Admin to create a shared edge network available in your Zadara Cloud Services  region.

    4. Legacy Mode - toggle on if you want to create a non-VPC-based legacy project.

  3. Click OK to create the new project. The new project is created and is displayed in the Projects tab of the specific account.

Using VPC-Enabled Projects

To VPC-enable a legacy project:

Note: Verify that there is a shared edge-network in your Zadara Cloud Services region.

  1. In the Identity & Access > Accounts > view, select the account in which the project you want to VPC-enable is found.

  2. Verify that the Projects tab is displayed.

  3. Highlight the project which you want to VPC-enable. The Enable VPC button is displayed on the Projects tab toolbar.

  4. Click Enable VPC. The Enable VPC for Project dialog box is displayed.

  5. Select an IP Pool. If there is no available IP pool, request an Admin to create a shared edge network available in your Zadara Cloud Services  region, or share an existing one.

  6. Click OK. A notice will pop-up informing you that a VPC has been provisioned for the legacy project.

Assigning a User to a Project

To assign a user to a project:

  1. In the Projects tab of the Identity & Access > Accounts > view for a specific account, highlight the row of the project to which you wish to assign a user. An Assign User button is displayed in the Projects tab toolbar.

  2. Click Assign User. The Assign User to Project: <name of selected project> dialog box is displayed.

  3. Do the following:

    1. Select a User to assign to the project.

    2. Select one of the three Project Roles, Member, Tenant Admin or Admin.

    3. Click OK.

  4. A new user will be created with the selected Zadara Cloud Services role and the default Zadara Cloud Services Policy ‘FullAccess’.

Disabling Projects

Note

The status of each project is indicated in the Enabled column of the Projects tab.

To disable a project:

  1. Go to the Projects tab of the Identity & Access > Accounts view of a specific account, and highlight the row of the project you wish to disable. Notice that the project is checked in the Enabled column. A Disable button appears in the toolbar.

    Note

    When the selected project is “Enabled”, the toolbar has a Disable button instead of an Enable button.

  2. Click Disable. A window pops-up informing you that the action has succeeded, and the project is no longer checked in the Enabled column.Note: The default project in the cloud_admin account cannot be disabled.

Enabling Projects

To enable a project:

  1. Go to the Projects tab of the Identity & Access > Accounts view of a specific account, and highlight the row of the project you wish to enable. Notice that the project is not checked in the Enabled column. An Enable button appears in the toolbar. Note: When the selected project is “Disabled”, the toolbar has a Enable button instead of a Disable button.

  2. Click Enable. A window pops-up informing you that the action has succeeded, and the project is now checked in the Enabled column.

Note

The default project in the cloud_admin account cannot be disabled.

Renaming Projects

To rename a project:

  1. Go to the Accounts Management > Accounts >  <name of specific account> view / Projects tab, and either

    1. Highlight the row of the project you wish to rename. A Rename button appears in the toolbar, -or-

    2. Click on the name of the project you want to rename. The view of the selected project will appear, with a Rename button in the toolbar,

  2. Click Rename. The Rename Project window is displayed.

  3. Make the necessary changes in the project name and its description.

  4. Click OK.

Configuring Default EC2 Networks

To configure the default EC2 networks:

  1. Go to the Accounts Management > Accounts >  <name of specific account> view / Projects tab, and either

    1. Highlight the row of the project you wish to rename. A EC2 Networks button appears in the toolbar, -or-

    2. Click on the name of the project you want to rename. The view of the selected project will appear, with a EC2 Networks button in the toolbar,

  2. Click EC2 Networks. The Configure EC2 Networks window is displayed.

  3. Select a ‘Private Network’ and an ‘Edge Network’.

  4. Click OK. A success message is displayed.

Deleting Projects

To delete a project:

  1. Go to the Accounts Management > Accounts >  <name of specific account> view / Projects tab, and either

    1. Highlight the row of the project you wish to delete A Delete button appears in the toolbar, -or-

    2. Click on the name of the project you want to delete. The view of the selected project will appear, with a Delete button in the toolbar,

  2. Click Delete. The Delete Project confirmation window is displayed.

  3. Click OK. A message confirming the deletion of the project will pop-up in the upper right-hand  corner of the screen.

    Note

    You cannot delete the ‘default’ project in the cloud_admin account.

Viewing Single Projects

Project Limits

Project Limits Overview

Zadara Cloud Services allows you to set  limits to the amount of virtual Compute, Service, Storage and Network resources each project can use. It is recommended that each account admin (tenant admin user) set the available resource limits for each of the projects within their account.

Project Limits

  1. In the Accounts Management> Accounts> <name of specific account> > Projects > <name of specific project> view, click on the Limits tab. Lists of virtual Compute, Service, Storage and Network resource limits for the selected project, together with their current usage is displayed. Limits can be imposed on the following project resources:

    1. Compute:

      • Number of cores

      • Number of images

      • Number of instances

      • Number of key-pairs

      • RAM

    2. Services

      • Number of Kubernetes clusters

      • Number of MapReduce clusters

      • Number of database clusters

      • Number of database instances

      • Number of filesystems

      • Number of load balancers

      • Number of registries

    3. Storage Note: Storage limits are defined and displayed per storage pool, which are then aggregated to a Project limit.

      • Number of snapshots

      • Number of volumes

      • Volume capacity

    4. Network

      • Floating IPs

      • Networks

      • Routers

      • Security groups

      • Security group rules

      • Subnets

Adding Compute Resource Limits to Projects

Zadara Cloud Services allows you to limit the amount of compute resources each project can use. Compute limits affect the following resources:

  1. Number of cores

  2. Number of images

  3. Number of instances

  4. Number of key-pairs

  5. RAM

To limit one of these resources for a project:

  1. In the Accounts Management> Accounts> <name of specific account> > Projects > <name of specific project> view, click on the Limits tab. Lists of all Compute, Service, Storage and Networking limits of the selected project together with their current usage is displayed.

  2. Click on the Add button which is at the top-right of the Compute list. This pops-up the Add Compute Limit window.

  3. Do the following:

    1. Select the Resource to be limited,

    2. Note its current Usage, if any.

    3. Enter it’s Limit. Verify that the limit exceeds the current usage.

  4. Click OK. The selected resource limit will be updated on the list of Compute resource limits for the selected Project.

Adding a Service Resource Limit to a Project

Zadara Cloud Services allows you to limit the amount of Service resources each project can use. Service limits affect the following resources:

  1. Number of Kubernetes clusters

  2. Number of MapReduce clusters

  3. Number of database clusters

  4. Number of database instances

  5. Number of filesystems

  6. Number of load balancers

  7. Number of registries

To limit one of these resources for a project:

  1. In the Accounts Management> Accounts> <name of specific account> > Projects > <name of specific project> view, click on the Limits tab. Lists of all Compute, Service, Storage and Networking limits of the selected project together with their current usage is displayed.

  2. Click on the Add button which is at the top-right of the Services list. This pops-up the Add Service Limit window.

  3. Do the following:

    1. Select the Resource to be limited,

    2. Note its current Usage, if any.

    3. Enter it’s Limit. Verify that the limit exceeds the current usage.

  4. Click OK. The selected resource limit will be updated on the list of Service resource limits for the selected Project.

Adding Storage Resource Limits to Projects

Zadara Cloud Services allows you to limit the amount of storage resources each project can use, per storage pool. Storage limits affect the following resource

  1. Number of snapshots

  2. Number of volumes

  3. Volume capacity

To limit one of these resources for a project:

  1. In the Accounts Management> Accounts> <name of specific account> > Projects > <name of specific project> view, click on the Limits tab. Lists of all Compute, Services, Storage and Networking limits of the selected project together with their current usage is displayed.

  2. Click on the Add button which is at the top-right of the Storage list. This pops-up the Add Storage Limit win

  3. Do the following: #. Select the Resource to be limited, #. Select the Storage Pool, in which the resource will be located. #. Note its current Usage, if relevant. #. Enter it’s Limit. Verify that the limit exceeds the current usage.

  4. Click OK. The selected resource limit will be updated on the list of Storage resource limits per storage pool, and aggregated to the project level.

Managing Virtual Network Resource Limits of Projects

Zadara Cloud Services allows you to limit the amount of virtual Network resources each project can use. Network limits affect the following resources:

  1. Floating IPs

  2. Networks

  3. Routers

  4. Security Groups

  5. Security Group Rules

  6. Subnets

To limit one of these resources for a project:

  1. In the Accounts Management> Accounts> <name of specific account> > Projects > <name of specific project> view, click on the Limits tab. Lists of all Compute, Service, Storage and Network limits of the selected project together with their current usage is displayed.

  2. Click on the Edit button which is at the top-right of the Network list. This pops-up the Edit Limits window for all virtual Network resource limits.

  3. For each resource either check the Unlimited box, or uncheck it and enter a limit.

  4. Click OK. The selected resource limit(s) will be updated on the list of Network resource limits for the selected Project.

Editing a Compute, Service or Storage Resource Limit of a Project

  1. In the Accounts Management > Accounts > name of specific account > Projects > name of specific project view, click on the Limits tab. Lists of all Compute, Service, Storage and Networking limits of the selected project together with their current usage is displayed.

  2. Hover over the Compute, Service or Storage resource limit and click on its Edit icon. The Edit Limit window of the resource is displayed.

  3. Do the following: #. Note its current Usage, if relevant. #. Modify its Limit. Verify that the limit exceeds the current usage.

  4. Click OK. The selected resource limit will be updated in its respective list of resource limits for the selected Project.

Deleting a Compute, Service or Storage Resource Limit from a Project

To delete a Compute, Service or Storage resource limit from a project:

  1. In the Accounts Management> Accounts> <name of specific account> > Projects > <name of specific project> view, click on the Limits tab. Lists of all Compute, Service, Storage and Networking limits of the selected project together with their current usage is displayed.

  2. Hover over a Compute, Service or Storage resource limit and click on its Delete icon. The resource limit will be deleted from its respective list for the selected Project.