DocsAbout projectsManage projects

Manage projects

Request a new project and understand project features, resource limits, restrictions, renaming, and deletion.

Creating, reconfiguring, and deleting projects are administrator actions. This page explains what a project's configuration controls so you know what to request, and documents the console flows for administrators.

Request a project

If you need a new project, contact your administrator. It helps to include:

  • The project name and a short description.
  • Which features should be isolated (see below).
  • The resource limits you expect to need (CPU, memory, disk, instance count).
  • The users who should get access — see Users and permissions.

Administrators create projects from the project selector (Create project, visible to administrators only) or through the Akasha API.

Project features

When a project is created, each of the following features is either isolated to the project or shared with the platform's default project:

FeatureWhen isolated
ImagesThe project has its own image store
ProfilesThe project has its own profiles, including its own default profile
NetworksNetworks are created and listed per project
Network zonesDNS zones are per project
Storage volumesCustom volumes are per project
Storage bucketsS3 buckets are per project

The Default feature preset isolates all of these. Feature isolation can only be changed while the project is empty, and the default project's features can never change.

The project form also sets a default instance storage pool (which becomes the root disk in the project's default profile) and a default profile network (which becomes the eth0 interface in the default profile) — see Profiles.

Resource limits

Administrators can set the following limits on a project:

LimitMeaning
limits.instancesMaximum number of instances
limits.containersMaximum number of containers
limits.virtual-machinesMaximum number of virtual machines
limits.cpuMaximum sum of CPU limits across all instances
limits.memoryMaximum sum of memory limits across all instances
limits.diskMaximum disk space used by all instances and volumes
limits.networksMaximum number of networks
limits.processesMaximum sum of processes across all instances

Current usage against these limits is shown on the project Summary page. If a limit blocks you, ask your administrator to raise it.

Restrictions

A project can additionally carry restrictions that constrain what its users can do:

GroupControls
ClustersWhether instances can target specific hosts or host groups directly
InstancesLow-level container and VM operations, container nesting and privilege, interception, backup creation, snapshot creation, and ID map ranges
Device usageWhich device types instances may use (disk, GPU, network, PCI, USB, InfiniBand, Unix devices), typically allow, block, or managed-only
NetworksWhich networks, subnets, uplinks, and zones the project may use

Restrictions surface in the console at the point of use — for example, when snapshot or backup creation is blocked, the corresponding buttons are disabled. See Instance snapshots and About networking.

View a project's configuration

Administrators open a project's Configuration page from the sidebar to see its features, limits, and restrictions; other users can reach it directly at /ui/project/<name>/configuration. Only administrators can change these values; changes by other users are rejected by the API.

Rename a project

Administrators rename a project by clicking its name in the header of the Configuration page. The default project cannot be renamed.

Delete a project

Deleting a project is an administrator action, and a project can only be deleted when it is empty. If the project still contains instances, profiles, images, or custom volumes, the delete button is blocked and a tooltip lists what remains. The default project can never be deleted.

Deletion asks you to type the project name to confirm — it permanently removes the project and cannot be undone.