Include keystone backend as available backend, Fixes #1983

[Itxaka]

Unable to use keystone as a backend on 0.13.x deb packages due to this issue.

[jvrplmlmn]

👍

[Kami]

Thanks.

The change looks good to me for v0.13 (v0.13.3), but it's also worth noting that the way auth backends work has changed in master and this change is not relevant there anymore.

In master we moved to "repo and Python package" per backend model (more flexible and easier to use custom backends) and by default we only ship flat_file backend. If you want to use a custom backend, you simply need to install a corresponding Python package from git.

Edit: I will check with others (/cc @manasdk @lakshmi-kannan @DoriftoShoes) and see if we have time to ship v0.13.3.

[Itxaka]

@Kami Yeah, I saw the change, but still at least for 0.13.x releases this is needed to make the backend actually work. Thats why I made the patch only against the 0.13 branch, afterwards it should not be longer of use. :)

[Kami]

Yep :)

We are pretty busy with working on the 1.0 beta release right now, but hopefully we will find some time this week to roll out v0.13.3.

Also, it would be great if you can re-open this PR against "v0.13.3" branch. The way out CI setup is currently set up, we first collect all the changes in the version branch and then we merge them into v0.13.

[Itxaka]

Will re-open against that branch.

when do usually new versions are build? we are now with the 0.13.2-5 debs installed :)

[Kami]

As far as ETA goes - we don't have any fixed time interval right now, but we tend to roll out a minor release every couple of weeks.

As far as our CI system is concerned - we build dev packages for master branch every time a new change is merged into master. As far as release branches go - we build new packages when a version branch is merged into a release branch (in this case when we finalize and merge changes from v0.13.3 branch into v0.13).