On 22/03/17 21:00, Bill Peck wrote:
On Wed, 2017-03-22 at 14:04 -0500, Brian Stinson wrote:
On Mar 22 14:57, Ari LiVigni wrote:
Is artifacts.ci a good place to store ostree and image artifacts out of CentOS CI? If so what are the steps to hook that up?
Thanks,
-- -== @ri ==- My PGP fingerprint is F87F1EE7CD8BEE13 _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
I think one problem with artifacts.ci (as it currently exists) is that rsync is the only supported protocol. This makes managing files in the project spaces a little tricky.
I'd like to hear from you and the other projects there: If we were to expand the methods of accessing artifacts.ci from the duffy nodes and the workspaces, what would you like to see?
I can't make any promises at this point about what to support, but let's get some discussion going.
Cheers! --Brian
Hi Brian,
nfs or gluster mount would be much better for publishing ostree images. rsync is great for duplicating but if we have to pull/update/push to make changes it will be prone to race conditions and just messy. :-)
Thanks, Bill
NFS can be tricky as we can't restrict who can write where, as the only way to do that would be to have kerberos inside CI, which we haven't. And because some projects are pushing files directly from the duffy nodes (and so unpredictable) and not from slaves (and even for this, some projects are sharing the same VM, so same ip) we can't apply any IP ACL either
Either we can use - sshfs (reusing the pub key already known by duffy/CI env) - cifs (and maybe creating the same user/pass as credentials as the one already created for rsyncd on the artifacts node)
Just wild ideas :-)