# Linode Module

https://docs.wisecp.com/de/linode-module

Connect Linode to import compute plans, provision instances with backup and volume options, and provide customers with supported console, rescue, system, network and storage operations.

## Reaching the Screen

Go to **Products → Hosting Server → Linode**: `{admin}/linode`

> **Premium Feature**
> 
> This module is included with the **Business Plan** at no additional cost. On other WISECP license plans you can add it to your existing license.

> **The License Alone Does Not Open the Menu**
> 
> The **Linode** menu appears only after you create an active server record that uses this module. The module address is not available until the server-addition flow below is complete.

### Activate the Module Menu

1. Open **Products → Hosting Server** and click **Add New Server** below the page title. On a narrow screen, first open **Show Options** to reach this button.
2. Under **Server Automation Module**, choose the **Virtualization** category and then select **Linode**.
3. Under **Connection Details**, enter `linode.com` in **Address**, `root` in **Username**, and your Linode personal access token in **API Token**.
4. Click **Test Connection**. After the test succeeds, check the server name and required capacity fields, then click **Add New Server** at the bottom of the page.
5. The record is created as active. The **Products → Hosting Server → Linode** menu now appears and `{admin}/linode` becomes available.

## What the Module Does

| Area | Administrator capability | Customer result |
| --- | --- | --- |
| Compute catalogue | Reads Linode types and regions, creates WISECP products, tracks USD cost and builds compatible upgrades. | Reviewed plans are offered with automatic or fixed region selection. |
| Provisioning | Creates a Linode from plan, distribution, hostname, user data and SSH key, plus backup and volume options. | Linode ID, hostname and network information are stored on the service. |
| Lifecycle | Automates power, password, rebuild, console, rescue, backup, hostname, activity, firewall, reverse DNS and volume actions. | Customers operate the instance without receiving the provider token. |
| Commercial control | Synchronizes costs, margin, regions, stock visibility, Backup Service and Block Storage pricing. | Compute and optional services follow administrator-reviewed limits and prices. |

### Catalogue and product control

The plan grid joins Linode CPU, RAM, storage, transfer and regional data to the WISECP product. The public name, automatic/fixed region, category, monthly USD sale price and active status are editable. Import creates missing plans inactive, updates stored costs without replacing sale prices, resets removed pinned regions to automatic, synchronizes distributions and rebuilds upgrade paths.

### Customer service tools

Customers can start, stop and restart an instance; set a new root password; rebuild from a supported distribution; open the API-generated Glish/Lish console; enter/leave Finnix rescue; change hostname and view instance activity. Linode Backup Service supports listing automatic backups and the manual snapshot slot, taking a snapshot and restoring. Network tools provide an allow-list cloud firewall, reverse DNS and month-to-date transfer. Purchased Block Storage volumes are managed from the storage tool. CPU and bandwidth gauges are real; live guest RAM/disk usage is not available.

### Automation and lifecycle

Generated products receive distribution, hostname, user-data and SSH-key requirements and can attach backup and volume add-ons. Linode does not provide standalone ISO boot or a general snapshot service in this integration; the manual snapshot belongs to Backup Service. Additional public IPv4 is not sold because provider allocation requires a support request and justification. Linode ID links the service to all later actions and cancellation cleanup.

## Before You Configure It

1. Create a Linode personal access token for the account that will own instances, firewalls, Backup Service and volumes. Its scopes must cover every feature you enable.
2. Enable the Linode server module and create an active server record that stores the token.
3. Create and enable USD in WISECP; provider type costs and generated plan/add-on prices use USD.
4. Confirm the license, account limits and billing capacity for an instance, backup and volume test before provisioning.

## Settings and Product Controls

- **API Token**: Required on initial setup; blank on later saves keeps the stored token.
- **Default Profit Margin (%)**: Calculates new plan and add-on prices; applying it globally reprices all imported items.
- **Auto-Sync Cost Prices**: Keeps provider cost snapshots current without replacing sale prices.
- **Hide When Out of Stock**: Prevents sale when the selected type cannot be deployed.
- **Backup Service**: Adds the backup toggle so Linode Backup Service is enabled with provisioning.
- **Block Storage**: Sells volume capacity through a quantity add-on managed by the service.

## Installation and Operation

### Prepare the personal access token

1. Create a dedicated token in the Linode account that will own WISECP resources.
2. Give it access to instances, regions, images/distributions, Lish, events, networking, firewalls, backups and volumes used by enabled features.
3. Store it securely and plan rotation; the token is never shared with customers.

### Connect and test the module

1. On the module page, click the gear-shaped **Settings** button in the top action bar directly below the page title; on a narrow screen, reveal this bar with **Show Options** first. In the **Module Settings** window, enter the token, set margin, cost and stock behavior, choose backup/volume order steps and customer features.
2. Use **Test Connection** directly below the credential field; it can test the typed token before save and is not blocked by the license gate.
3. After success, click **Save Settings** in the window footer. The live plan/region data becomes available.

### Import and reconcile plans

1. In the top action bar below the page title, click the cloud-download **Import from API** button. In the window, select new plans, cost updates or region import.
2. After selecting at least one option, click **Start Import** in the window footer. Missing types become inactive margin-priced products; cost-only updates preserve current sale prices.
3. Review region fallbacks, synchronized distribution choices and rebuilt upgrade paths.

### Review plans, regions and pricing

1. Verify plan CPU, RAM, disk, transfer, USD cost and availability; choose public name, category and automatic/fixed region.
2. Set the monthly USD sale price and keep the product inactive until provisioning, service tools and cancellation pass.
3. Save rows. If bulk repricing is required, enter the rate in **Profit Rate (%)** on the right side of the top action bar and click **Update Prices**; this recalculates all Linode plan and generated add-on prices.

### Configure requirements, backup and volume

1. Review generated distribution, hostname, user-data and SSH-key requirements and remove unsupported customer choices.
2. Enable Backup Service and/or Block Storage order steps, then set their sale price and volume capacity limits.
3. Confirm generated add-ons are attached to intended products; do not add unsupported ISO, standalone snapshot or automatic extra-IPv4 promises.

### Verify with an inactive test product

1. Create a controlled service from an inactive plan in a supported region; include backup and a small volume if those will be sold.
2. Provision and confirm Linode ID/IP; test power, password reset, rebuild, Glish/Lish, rescue, backup, hostname, activity, firewall, reverse DNS, transfer and volume tools.
3. Cancel through WISECP and confirm the instance, volumes and module-managed paid resources are removed before activation.

### Maintain catalogue and service access

1. Import after type, region or cost changes; choose cost-only synchronization when sale prices are manually curated.
2. Review automatic-region fallbacks, stock visibility, distribution choices, backup price and volume limits.
3. Periodically test token scope, console/rescue access and cancellation cleanup before customer demand exposes drift.

## Things to Watch

> **Backups and volumes are separate provider services**
> 
> Both can continue generating cost. A test is complete only after the Linode and its module-managed paid resources are removed.

> **Provider limits shape the feature list**
> 
> Do not advertise ISO mounting, standalone snapshots or self-service extra public IPv4; those are not supported by this module’s Linode workflow.

> **Gauges are operational, not metered invoices**
> 
> CPU and month-to-date bandwidth are real provider data for the fixed plan. They do not generate usage-based invoice items; guest RAM/disk usage is unavailable.

## Privileges

**Product Operations** (`PRODUCTS_OPERATION`) is required for settings, import and pricing. Customer access follows feature switches and purchased backup/volume options.

## Related Screens

- [Servers](https://docs.wisecp.com/en/server-management)
- [Product Groups](https://docs.wisecp.com/en/product-groups)
- [Server Modules](https://docs.wisecp.com/en/module-management)