Type Alias PutLinodeConfigResponses

Type Declaration

• comments: string | null

  Optional field for arbitrary user comments on this configuration.

• devices: {
      sda: { disk_id: number; volume_id: number | null };
      sdb: { disk_id: number; volume_id: number | null };
      sdc: { disk_id: number; volume_id: number | null };
      sdd: { disk_id: number; volume_id: number | null };
      sde: { disk_id: number; volume_id: number | null };
      sdf: { disk_id: number; volume_id: number | null };
      sdg: { disk_id: number; volume_id: number | null };
      sdh: { disk_id: number; volume_id: number | null };
  }

  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.

  • sda: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

  • sdb: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

  • sdc: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

  • sdd: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

  • sde: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

  • sdf: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

  • sdg: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

  • sdh: { disk_id: number; volume_id: number | null }

    Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed. Can be null. Devices mapped from sde through sdh are unavailable in fullvirt virt_mode.

    • disk_id: number

      The Disk ID, or null if a Volume is assigned to this slot.

    • volume_id: number | null

      The Volume ID, or null if a Disk is assigned to this slot.

• helpers: {
      devtmpfs_automount: boolean;
      distro: boolean;
      modules_dep: boolean;
      network: boolean | null;
      updatedb_disabled: boolean;
  }

  Helpers enabled when booting to this Linode configuration.

  • devtmpfs_automount: boolean

    Populates the /dev directory early during boot without udev. Defaults to false.

  • distro: boolean

    Helps maintain correct inittab or upstart console device.

  • modules_dep: boolean

    Creates a modules dependency file for the kernel you run.

  • network: boolean | null

    Set to true to automatically configure static networking. The network option applies only to legacy configuration profile interfaces and does not apply to Linode interfaces.

  • updatedb_disabled: boolean

    Set to true to disable the updatedb cron job to avoid disk thrashing.

• Readonlyid: number

  Read-only The ID of this Config.

• interfaces: {
      active?: boolean;
      id?: number;
      ip_ranges?: string[] | null;
      ipam_address?: string | null;
      ipv4?: { nat_1_1: string | "any" | null; vpc: string | null };
      label?: string | null;
      primary?: boolean;
      purpose: "public" | "vlan" | "vpc";
      subnet_id?: number | null;
      vpc_id?: number | null;
  }[]

  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.

• kernel: string

  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.

• label: string

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

• memory_limit: number

  Defaults to the total RAM of the Linode.

• root_device: 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.

• run_level: "default" | "single" | "binbash"

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

• virt_mode: "paravirt" | "fullvirt"

  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.