Google
  Web www.spinics.net

Re: P2P Packaging/Koji Cloud

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


2011/12/7 Nicolas Mailhot <nicolas.mailhot@xxxxxxxxxxx>
Concerning trust, the classic way it has been solved before (by seti…)
is to farm the same build to several independant nodes, cheksum results
and make sure they all agree

Again, we could use that P2P build system just to alleviate the centralised Koji servers from the scratch builds, on one hand, and from the failing builds on the other hand. That way, the centralised Koji servers would need no alteration.

As a side note, rather than using Snap (and Augeas, and...), we (in my department) tend to prefer Chef (http://www.opscode.com/chef/), which has got a broader scope, and allows much more complex configurations and automation tasks.

Denis
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud

[Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Deep Creek Hot Springs]     [Coolkey]     [Yum Users]     [Tux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux

Google
  Web www.spinics.net