Hi,
We'd like to place Gluster-Swift in the Storage SIG. Users can install (OpenStack) Swift as a pretty much stand-alone (without OpenStack) environment. It is possible to use Gluster in the backend, and the project that enables this is called gluster-swift.
The difficulty is that gluster-swift depends on the Swift packages from OpenStack. And of course these packages have yet an other set of dependencies... The way I think is most practical for users that want to install Gluster-Swift, is the following:
- create a (Storage SIG) repository that contains glusterfs-swift - create a new centos-release-gluster-swift package (crgs) - have crgs depend on centos-release-gluster for a recent glusterfs-fuse - have crgs depend on centos-release-openstack for other swift bits
Currently gluster-swift only works with OpenStack Kilo. Additional work is needed to have it work with more current OpenStack versions.
Do others see this as a good way forward? Alternative solutions are most welcome too :)
Thanks, Niels
- have crgs depend on centos-release-openstack for other swift bits
Currently gluster-swift only works with OpenStack Kilo. Additional work is needed to have it work with more current OpenStack versions.
OpenStack Kilo is EOL upstream and we are overdue to retire it in CloudSIG i.e. move to vault.centos.org. so I would highly recommend to update to OpenStack Newton first!
Cheers, Alan
On Wed, Sep 21, 2016 at 01:18:55AM +0200, Alan Pevec wrote:
- have crgs depend on centos-release-openstack for other swift bits
Currently gluster-swift only works with OpenStack Kilo. Additional work is needed to have it work with more current OpenStack versions.
OpenStack Kilo is EOL upstream and we are overdue to retire it in CloudSIG i.e. move to vault.centos.org. so I would highly recommend to update to OpenStack Newton first!
Thanks! That is an interesting detail that I was not aware of as non-OpenStack user/developer :)
Obviously it makes sense to only package Gluster-Swift for versions that are supported by the Cloud SIG.
Niels