Changes from Infrastructure-API to IaaS-API
The IaaS-API defines its own set of features which are not compatible with the Infrastructure-API.
Most STACKIT resources however have a corresponding Infrastructure-API resource with similar features.
The following table shows terms and definitions of the STACKIT IaaS-API and how they map to the Infrastructure- /Openstack-API.
New STACKIT Features
Differences between Infrastructure/Openstack-API and IaaS-API Features
Most resources support the same features as the Infrastructure/Openstack-API did, the last column will describe important changes or new Feature additions.
Infrastructure / Openstack Term | IaaS-API Term | Iaas-API differences |
---|---|---|
Server or Instance | Server or Virtual Machine | Servers are similar to Openstack Servers. New Features
|
Image | Image | Images are similar to Openstack Images. New Features
|
Volume | Volume | Volumes are similar to Openstack Volumes. |
Flavor | Flavor/Server/Machine Type | IaaS-API uses the term Flavor more generically. Machine Types are similar to Openstack Flavors. |
Volume Type | Flavor/Volume/Performance Class | Performance Classes are similar to Openstack Volume Types. |
Floating IP | Public IP | Public IPs are similar to Openstack Floating IPs. |
Router | Network | The IaaS-API simplifies the process of a network creation by grouping and managing the router, gateway New Features
|
Gateway | ||
Subnet | ||
Network Port | Network Interface (nic) | Network Interfaces are similar to Openstack Network Ports. |
Tag | Label | A label is a key/value resource and can be attached to most Objects similar the Openstack Tags. New Features
|
Security Group | Security Group | Security Groups support the same features as Openstack Security Groups. |
Shelving/Unshelving | Deallocation/Starting | Deallocation is the same as Openstack Shelving. Explicit unshelving is now achieved by starting the Server. |
Server Groups | Affinity Groups | Affinity Groups are similar to Openstack Server Groups |
Volume/Server Backups | Backups | Backups have been consolidated into one Endpoint. The backup source can be a Volume or a Snapshot. |
Keypairs | Keypairs | IaaS-API only allows importing of public Keys. No private Keys will be created by the API for the user. Existing Keypairs can't be used in IAAS API. |
Openstack Project ID | - | Openstack Project IDs are not used anymore with the IaaS-API. The STACKIT Project ID has a different format (uuidv4) and must be used instead. |
Request Tracking
Creating or modifying a resource creates a unique request ID and returns it in the HTTP response as the X-Request-Id
Header. The IaaS-API provides an endpoint to retrieve the Status of a request and its associated Resources.
FAQ
Q: Why are we migrating from the Infrastructure-/Openstack-API to IaaS-API
A: Our goal was to have a standardized API across all infrastructure services and to simplify some currently unnecessarily complex steps. In addition, we now have the possibility to offer services like SNA that are outside the Openstack scope.