Some days ago I released openstackcli, a new containerized tool to work with Openstack API.

The motivation of this project was driven by a missing feature from OVH’s Managed Kubernetes: Snapshots from in-use volumes.

If you are already working with Kubernetes, you would like to perform everything in a Kubernetes way, including volume’s snapshots, and this is possible as you can see in the docs.

That would be as easy as:

kind: VolumeSnapshot
  name: my-snapshot
    persistentVolumeClaimName: my-pvc

But, we should detach the volume before performing the snapshot due to OVH Infrastructure does not support yet to do it with an attached volume. Check the issue here.

The main purpose of performing a snapshot to a non-attached volume is to keep the consistency in the data. Otherwise, no every application is working 247. We know that there is some moments where the application is not actually used and we can apply some maintenance tasks, like back-ups. You can find applications which are used during office hours or during some sport events and we can easily detect time windows where they are not used. In this way, we would not need to detach and attach the volumes before and after the snapshots.

As we were working with OVH, we know that its Public Cloud is Openstack, why don’t we try to work directly against the API?


If we want to work against the Openstack’s API from Kubernetes, we need a container with the necessary software. In this case there are some available docker image, but I packaged mine in order to add some other useful tools like jq which will be very useful for the scripts. Now we can launch some Kubernetes Jobs or CronJobs in order to perform the snapshots or whatever other maintenance task, like clean them up.

Rememeber that the pod has to have access to the Openstack API

Cronjob example:

apiVersion: batch/v1beta1
kind: CronJob
  name: my-cronjob
  schedule: 0 0 * * *
          - name: snapshot
            image: mendrugory/openstackcli
            - /bin/sh
            - -c
            - openstack volume snapshot create --force --volume my-wonderful-data my-snapshot
            # Remember to give access to the Openstack API


I think that this is a temporary solution, but I expect that it is useful meanwhile.