Klever

We have no time to implement these tasks in Klever 3.0.

Implemented in the improve-openstack-deployment branch using rsync. Now Klever sources, addons and build bases are deployed only if there are some changes in them. As a consequence, deployment speed during "update" action is considerably faster then before.

Let's include this into 3.0.

Branch improve-openstack-deployment avoids copying the same local build bases to instances, but it does not solve the problem in general. In general we need some means like for addons which are not updated (nothing is downloaded, extracted and so on) until their versions change within a deployment configuration file.

Implemented in the deploy-build-bases branch, which also contains other improvements regarding deployment of build bases:

• Now deployment scripts automatically extract build bases during deployment (previously they were simply copied)
• Now build bases are deployed during 'update' action only if they are changed
• Now deployment of build bases and Klever Addons uses the same code, which should simplify further improvements

Since it is solved, let's include it within Klever 3.0.

Likely resolved. Needs testing.

It works, but due to ill-formed archives (e.g. https://forge.ispras.ru/attachments/7328) users may meet very strange issues because of different build bases can be intermixed in the unpredictable way within the same directory.

1. A build base is placed within at least one top-level directory within an archive.
2. There is not most low-level directory that contains the build base at the deployment directory already.

Perhaps, some assistance from Clade will be necessary, since just Clade knows what is a build base.

I have added the following changes to the same deploy-build-bases branch:

• Now data transferred by rsync is compressed (unless the data itself is an archive)
• Now paths with spaces are handled correctly by rsync
• Now there is an optional ability to manually specify versions of build bases (but by default versions are calculated automatically)
• Now each build base has a unique name specified in the klever.json file. This name can be used in the job.json file to refer to the required build base.

We tested and fixed some additional related issues, after all everything seems to work perfect. I merged the branch to master in 4a52fad75. Everybody is welcome to deploy build bases within their Klever instances!

1. Edit /etc/default/klever. Change KLEVER_DATA_DIR="/home/debian/klever-inst/klever/build bases" to KLEVER_DATA_DIR="/home/debian/klever-inst/build bases".
2. Move directory /home/debian/klever-inst/klever/build bases to /home/debian/klever-inst/build bases.
3. Restart the scheduler: "sudo systemctl restart klever-native-scheduler.service".