Fleio 2021.02.1 was released today, 9th of February.
The latest version is marked as stable and can be used in production environment (read more about our release model here).
New fleio commands
In the latest release we have worked on improving the new fleio bash command (which is available only when using Fleio deployed with docker).
As of 2021.02.1 we now have some new arguments, such as:
fleio edit bash command you will now be able to directly edit the configuration files, using your preferred file editor:
Before 2021.02.1, you would have to access the utils container using
fleio utils command, then change the directory to
/var/webapps/fleio/scripts and then you would be able to run the
Now you can just run the
fleio sync command, as you would run any other fleio related command (status, restart, updates and so on).
fleio edit and
fleio sync we have changed the
utils flag to
bash, so now you can run commands inside utils container, directly from the server host, using
fleio bash $command.
Url uploads in memory streams
On 2021.01.1 release, we have changed the way on how files and images were uploaded to Openstack. Prior to this change, the files were first uploaded to the Fleio host, in a tmp file, and just after that it was uploaded to Openstack.
This opened some vulnerabilities, where someone could make use of this vulnerability and start uploading images until your server ran out of space.
We are happy to announce that with 2021.02.1 release, we have fully mitigated this, by sending the files and images (including URL uploads) directly to Openstack.
Besides the URL uploads, we also added some more checks when an enduser uploads an image from URL, for cases where the requested url was not working, had authentication, etc.
With 2021.02.1 release we have also made changes to how Fleio computes client’s credit on resource create. This should result in a big performance boost
Prior to this change, Fleio would compute all the client’s data on each cloud resource create (instance, volume, network, etc) with all pricing rules, to see if the client does have enough credit at that given point.
If he has enough credit, the instance is deployed. If not, he receives a warning that he does not have enough credit even though he has positive credit (basically on next process clients cron he would get into negative credit).
We have now implemented a new settings.py feature that will allow you to enable/disable the credit check on cloud resource deploy:
COLLECT_USAGE_ON_CHECK_CREDIT = True
This new feature is enabled by default (basically, you will have no changes in Fleio if you let this feature enabled).
Fleio deployed with docker ready for production
With 2021.02.1 we are happy to let you know that Fleio deployed with docker is now ready for production.
We do recommend you to start testing the docker deployment in your staging environment as soon as possible.
More details about Fleio – Docker will come in a separate blog post.
As a reminder, when upgrading Fleio, we recommend you to use the safe upgrade procedure.
Fleio 2021.02.1 includes many more improvements and bug fixes. For a full list see the full 2021.02 changelog.