OpenStack
You can connect your OpenStack environment to Txture using our preconfigured Data Source and Importer.
Data Source Configuration
To connect to your OpenStack environment:
- Navigate to the
Admin
section and select Data Sources. - Click the
+ Create
button and scroll down to the OpenStack Source. - Enter your credentials and save the data source.
- A connection status check will be performed automatically. If this check is successful, you can proceed to create the importers.
Authentication Credentials
- Username - Your OpenStack username
- Password - Your OpenStack password (or application credential secret)
- Project/Tenant Name - The specific project you want to work within
- Project/Tenant ID (Optional) - Often required as an alternative to project name
- Domain Name (Optional) - The domain your user belongs to (often "Default" for simple setups)
- Auth URL (Identity Service) - The Keystone authentication endpoint (e.g.,
https://openstack.example.com:5000/v3
)
Importer Configuration
You can enable and disable different importers from the preconfigured group depending on how your OpenStack environment is configured. You may also need to map the importers to adapt them to your Txture Structure.
- Create an importer by clicking the
Create Importer
button on the top right of your configured data source, or go toImporters
and click theCreate new importer
. - Since this is a auto-configured importer, an importer group will be created.
- Enable or disable the importers you need for your OpenStack import.
- Review the mapping for assets and links to ensure they fit your structure.
- Run your importers.
OpenStack Schema
The OpenStack importer uses a fixed schema with the following asset types and link types:
Asset Types
Asset Type | Description |
---|---|
FLAVOR | Flavor is an available hardware configuration for a server. It defines the size of a virtual server that can be launched. |
VIRTUAL_MACHINE | Virtual machines. You can choose "only running" to import only virtual machines that are currently running. |
IMAGE | All images available in your OpenStack environment. |
DNS | Domain Name System records for the given access data. |
SUPPORTED_SERVICES | Services supported by your OpenStack installation. |
LOADBALANCER | Load balancers (for detailed information, see the OpenStack documentation) |
LOADBALANCER_LISTENER | Listeners for load balancers. |
LOADBALANCER_POOL | Pools for load balancers. |
LOADBALANCER_MEMBER | Members of load balancer pools. |
LOADBALANCER_HEALTHMONITOR | Health monitors for load balancers. |
SECURITY_GROUP | Security groups for organizing and securing virtual machines. |
Link Types
Link Type | Description |
---|---|
VIRTUAL_MACHINE_TO_FLAVOR | Associates virtual machines with their flavors: which virtual machine uses which flavor configuration. |
VIRTUAL_MACHINE_TO_IMAGE | Associates virtual machines with their images: which virtual machine is based on which image. |
VIRTUAL_MACHINE_TO_SECURITY_GROUP | Associates virtual machines with security groups: which security groups are assigned to each virtual machine. |
LOADBALANCER_TO_LOADBALANCER_LISTENER | Associates load balancers with their listeners. |
LOADBALANCER_POOL_TO_LOADBALANCER_LISTENER | Associates listeners with load balancer pools. |
LOADBALANCER_POOL_TO_LOADBALANCER_MEMBER | Associates load balancer pools with their members. |
LOADBALANCER_HEALTHMONITOR_TO_LOADBALANCER_POOL | Associates load balancer pools with their health monitors. |
Understanding OpenStack Flavors
In OpenStack, a flavor defines the virtual hardware configuration for a server instance, specifying resources like vCPUs, RAM, and disk space. Essentially, it's a template that determines the size and capabilities of a virtual machine. Flavors are managed by administrative users and can be customized with metadata to further control instance behavior.
During the initial import, assets like Virtual Servers need to be linked manually to your specific flavor configurations. To transfer flavor information to asset properties, you'll need to configure additional mapping rules in the importer settings using Dynamic Columns.