API

Create a configuration profile

post
https://api.linode.com//linode/instances//configs

Adds a new configuration profile to a Linode. Configuration profiles define the kernel, devices, and how much memory a Linode boots with.

📘

This operation is for legacy configuration profiles only, and not Linode interfaces.

Permissions and scopes

To call this operation, you need the following:

  • Identity and access permissions. Your user needs a role with these permissions assigned. Learn more.

    • Permissions: create_linode_config_profile

  • OAuth scopes. Your user needs these scopes assigned. Learn more.

    • Scopes: linodes:read_write

CLI

linode-cli linodes config-create 7590910 \
  --label "My Config" \
  --devices.sda.disk_id 123456 \
  --devices.sdb.disk_id 123457

Learn more

Path Params
string
enum
required

Enum Call either the v4 URL, or v4beta for operations still in Beta.

Allowed:
integer
required

ID of the Linode to look up Configuration profiles for.

Body Params
string | null

Optional field for arbitrary user comments on this configuration.

devices
object
required

A dictionary of device disks to use as a device map in a Linode's configuration profile.

  • An empty device disk dictionary or a dictionary with empty values for device slots is allowed.
  • If no devices are specified, booting from this configuration will hold until a device exists that allows the boot process to start.
helpers
object

Helpers enabled when booting to this Linode configuration.

interfaces
array of objects
length between 1 and 3

interfaces is applicable only to legacy configuration profiles and does not apply to Linode interfaces.

From one to three network interfaces to add to this Linode's configuration profile. The position in the array determines which of the Linode's network interfaces is configured:

  • First [0]: eth0
  • Second [1]: eth1
  • Third [2]: eth2

When updating a Linode's legacy interfaces, each interface must be redefined. An empty interfaces array results in a default public type interface configuration only.

If no public Interface is configured, public IP addresses are still assigned to the Linode but will not be usable without manual configuration.

📘

Changes to Linode Interface configurations can be enabled by rebooting the Linode.

vpc details

See the VPC documentation guide for its specifications and limitations.

vlan details

  • Only Next Generation Network (NGN) data centers support VLANs. Run the List regions operation to view the capabilities of data center regions. If a VLAN is attached to your Linode and you attempt to migrate or clone it to a non-NGN data center, the migration or cloning will not initiate. If a Linode cannot be migrated or cloned because of an incompatibility, you will be prompted to select a different data center or contact support.
  • See the VLANs Overview guide to view additional specifications and limitations.
interfaces
string
Defaults to linode/latest-64bit

The ID of the kernel used to boot a Linode. Run the List kernels operation to see all available kernels. Here are some commonly used kernels:

  • linode/latest-64bit. This is the default, our latest kernel at the time of an instance boot or reboot.

  • linode/grub2. The upstream distribution-supplied kernel that's installed on the primary disk, or a custom kernel if installed.

  • linode/direct-disk. The master boot record (MBR) of the primary disk or root device. Use this in place of a Linux kernel.

string
required
length between 1 and 48

Filterable The name of the configuration for display in Akamai Cloud Manager.

integer

Defaults to the total RAM of the Linode.

string

The root device to boot.

📘

  • If you leave this empty or set an invalid value, the root device defaults to /dev/sda.

  • If you specify a device at the root device location and it's not mounted, the Linode won't boot until a device is mounted.

string
enum

Defines the state of your Linode after booting. Defaults to default.

Allowed:
string
enum

Controls the virtualization mode. Defaults to paravirt.

  • paravirt is suitable for most cases. Linodes running in paravirt mode share some qualities with the host, ultimately making it run faster since there is less transition between it and the host.

  • fullvirt affords more customization, but is slower because 100% of the VM is virtualized.

Allowed:
Responses

Updated about 1 month ago

Language
Credentials
LoadingLoading…
Response
Choose an example:
application/json

Updated about 1 month ago