Fleio 2022.05.2 stable was released on 31th of May, 2022. We’ve released the 2022.05.2 minor version due to unforeseen changes in relation to client email removal. You can see the updated changelog here.
Fleio 2022.05.1 stable was released today, 25th of May, 2022.
The latest version is marked as stable and can be used in production environment. You can read more about our release model here.
Multi region support for Swift Object store
With the release of the 2022.05 version, multi region support for Swift object store was added to Fleio.
As you may know, the Swift Object store containers are not saved in the Fleio database and they are directly pulled from OpenStack using the Swift API so the conventional way of having multi region support (as we have for Instances, Volumes, Networks and so on) could not be used for this type of OpenStack resources.
In order to be able to implement the multi region support we have added a new drop down in the top right corner, which will allow you to select the region for which you want to create, read, update and delete the swift object store containers:
Keep in mind that the Swift object store containers are still not cached inside the Fleio database and they are still being pulled directly from OpenStack using the Swift API.
Note that the drop down is disabled by default and you need to enable the openstack.object-store.show-region-select feature in your settings.py file.
If you don’t know how to enable or disable features, please head over to our docs:
Notifications and logs improvements
In the latest release we have also worked on improving the notifications and the user / clients related logs.
On the improvements part, we have added a color bar for the enabled or disabled notifications:
As you may notice in the picture from above, the first notification status bar is grey, which indicates that the
account.credit.low notifications is disabled. The green bar indicates that the notification is enabled.
One major addition to the notifications feature is the notification settings (user related), notification categories and the user defined notifications.
Each user that have the owner role for a client will now be able to configure what type of notification the users that are assigned to that client will get.
The notifications are split in 4 categories:
- account authorization notifications
- billing and service related notifications
- general announcements
- technical announcements
This will help the owners, to configure what type of notifications would an invited user (e.g. the accountant) should get.
Splitting the notifications in categories also allowed us to improve the mass message feature, by allowing staff users to set a message type (e.g. Technical announcement), and have a specific targeted audience for that message. These messages (be it by email, top line notification, or just panel notification) will be sent only to the users that have the category checked on their notification settings.
Two smaller improvements that were also added in the 2022.05 release are the addition of new order notification for upgrade and downgrade orders, and the possibility to filter the notifications templates by category and type.
On the logs side, we have added a new tab on user details and on client details, which are available only for Staff users:
Service welcome email
In the 2022.05 release we have also added a new service welcome email notification which will be send when a new service is created.
The notification needs to be configured on the product create/edit form, and it’s disabled by default (no notification will be sent when the service is created).
The Welcome email notification can also be changed by editing the service.welcome notification from Settings -> Notifications.
Additionally, if you want to have different notifications for each service, you can create a new notification which must have the Service notifications type in order to be available in the Welcome email drop down.
Client email removed
In the latest release we have also removed the client email address.
On sign up, a normal user would have to complete the email address twice: once on the user create form (login information) and once on the client create form (billing information).
With the improvements that we mentioned earlier, the client email became obsolete, since all the notifications were moved to the user’s email address.
Note that some clients may have been used different email addresses for user and client, so in order to be sure that all notifications are properly sent, these clients will get a new user which will have the client’s email address.
If you have custom scripts / workflow which you know that used the client’s email address, we highly recommend to test them in a staging environment, before upgrading to the 2022.05 release.
Keep in mind that in order to upgrade Fleio to the latest version you need to follow this guide.
Fleio 2022.05.1 includes many more improvements and bug fixes. For a full list, see the full 2022.05.1 changelog.