Hi, This mail to start a discussion about the integration of a SAIO within SF. I believe it can help for: - Adapt or internal tooling to "only" the swift API (for storage related stuff) - Be able to use the internal Swift instance when an SF operator can't access to a Swift cluster - Be able to have some cool stuffs working by default if the internal installation is used: - log files/build artifacts export thanks to "zuul-swift-upload" - Each project can inherit a container or account ? to store data/final artifacts / rpm repo / images / ... - Each project can in the future stores a static website accessible through http://sfdomain/pages/<project-name>/
We can easily use a pre-existing Ansible playbook to deploy swift SAIO so the integration can be straightforward and quickly done. In a first step we can have by default the swift proxy service and object/container servers/replicators deactivated if in sfconfig.yaml set SAIO -> disabled: true. It will also ease a lot the development for us of features related to Swift into SF as a SF installation can be easily reconfigured by sfconfig.sh to start SAIO. Cheers, Fabien _______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
