(openstack-multi-service-feature)=

# OpenStack multi-service per client feature

```{contents}
:depth: 4
:backlinks: none
```

Fleio works with multiple OpenStack services/projects per client when the end-user feature "openstack.multi-service" 
is enabled in the [settings.py file](#edit_settings-py). The documentation below describes Fleio behavior when using 
this feature.

## Service-project-resource relation

An OpenStack project corresponds to a service in Fleio. A client with multiple active OpenStack services has a different 
OpenStack project for each one.

End-users can change the default OpenStack service from **Services** page. This preselects the service on the resource
creation forms. An alias can also be set for OpenStack services to differentiate them.

When creating a new OpenStack resource from Fleio and the client has multiple OpenStack services, a service selector
appears on the form. The resource will be deployed in the project assigned to the selected service. Similarly, in the
staff panel, the client selector will change the client entry into a header and show services underneath it when
there is more than one service for a client.

Resources that are synchronized in Fleio from OpenStack are displayed from all the client's active services on resource
list pages. End-users can filter them by the service record. In the case of resources that are not synchronized and 
are retrieved directly from OpenStack (e.g., load balancers at the current moment), a service selector appears on the 
list page and resources are shown from the selected service's project.

## Creating new OpenStack services

Before this feature, a client was limited to a single active OpenStack service. When the feature is active,  
administrators can set the OpenStack product and cycles as public and users will be able to order more 
services/projects. Alternatively, staff users can create a new OpenStack service from the client's detail page.

## Billing multiple OpenStack services per client

There is no difference when billing multiple OpenStack services per client than when the client only has one. Each
service is billed individually, and the client can check the cost and usage in the **Billing history** page, where a
service selector allows switching between multiple services data.

## External billing support

If you're using an external billing system alongside Fleio, ensure it is compatible with this functionality. When using
**fleio-whmcs**, ensure the module version you are using supports multiple OpenStack services per client.