Akasha.
DocsAbout projectsProfiles

Profiles

Define reusable instance configuration with profiles and understand how the default profile applies to new instances.

A profile is a reusable set of instance configuration: devices, resource limits, security policies, cloud-init data, and more. Profiles belong to a project, and instances pick up their configuration from the profiles applied to them.

The default profile

Every project has a profile named default. It is applied to new instances automatically and typically provides the essentials an instance needs to boot: a root disk on a storage pool and an eth0 network interface. The default profile cannot be deleted, but you can edit it to change the baseline configuration for new instances in the project.

In projects that do not have isolated profiles, the profiles you see (including default) come from the platform's default project and are shared — see About projects.

Create a profile

  1. Go to Profiles → Create profile.

  2. Enter a name and optional description under Main configuration.

  3. Fill in any of the configuration sections (all optional):

    SectionContents
    DevicesDisk, Network, GPU, Proxy, and other devices
    Resource limitsCPU, memory, and related limits
    Security policiesPrivilege, protection, and isolation settings
    SnapshotsAutomatic snapshot naming, expiry, and schedule
    MigrationLive-migration behavior
    BootBoot order and autostart settings
    Cloud initcloud-init user, vendor, and network data

  4. Click the create button to save the profile.

These are the same sections you see when configuring an instance — a profile is an instance configuration template. You can also switch the form to a YAML view to edit the profile as text. For what the individual options mean, see Configure instances and Use cloud-init.

How profiles apply to instances

When you create or edit an instance, values that come from a profile appear in the form as inherited values, marked with their source. Each inherited value has an override control: overriding it writes an instance-specific value that takes precedence over the profile.

Changes to a profile affect the instances that use it, except where an instance has overridden the value.

Edit, rename, or delete a profile

Open a profile from the Profiles list to see its Overview tab (including the instances that use it) and its Configuration tab.

  • To edit, change values on the Configuration tab and save.
  • To rename, click the profile name in the page header.
  • To delete, use the Delete button. The default profile cannot be deleted.