Difference between revisions of "Koji Testbed"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 377: | Line 377: | ||
Before the RPMs that Koji produces are distributed, they should be signed. The YUM configuration can then be configured to use GPG to verify the origin of the RPMs upon installing. | Before the RPMs that Koji produces are distributed, they should be signed. The YUM configuration can then be configured to use GPG to verify the origin of the RPMs upon installing. | ||
| − | Sigul integrates well with Koji, but unfortunately comes with little documentation. | + | Sigul integrates well with Koji, but unfortunately comes with little documentation. There is some [https://fedoraproject.org/wiki/Create_release_signing_key here]. |
The architecture of sigul is as follows: | The architecture of sigul is as follows: | ||
| Line 384: | Line 384: | ||
The sigul server node holds the secret key(s) and must be secured very tightly. The sigul bridge node only allows connections from the client and the server, it will make no outgoing connections. | The sigul server node holds the secret key(s) and must be secured very tightly. The sigul bridge node only allows connections from the client and the server, it will make no outgoing connections. | ||
| + | |||
| + | Sigul is available as a package in CentOS 6, and hold all three components. The client is installed on koji-hub.testbed; the bridge on koji-bridge.testbed and the server on sigul.testbed. The latter two cannot be accessed through ssh, only console access (wich 'virsh console' or on the virtual video console). | ||
= Generating distribution repos from koji = | = Generating distribution repos from koji = | ||
