1
edit
Changes
no edit summary
psql koji koji < /usr/share/doc/koji*/docs/schema.sql
exit
Authorize Koji-web and Koji-hub resources: In this example, Koji-web and Koji-hub are running on localhost.
/var/lib/pgsql/data/pg_hba.conf: These settings need to be valid and inline with other services configurations.
Please note, the first matching auth line is used so this line must be above any other potential matches. Add:
host koji koji 127.0.0.1/32 trust
local koji apache trust
local koji koji trust
To edit /var/lib/pgsql/data/pg_hba.conf
<code># TYPE DATABASE USER CIDR-ADDRESS METHOD
host koji koji 127.0.0.1/32 trust
host koji apache 127.0.0.1/32 trust
host koji koji ::1/128 trust
host koji apache ::1/128 trust
local koji apache trust
local koji koji trust</code>
'''TO enable auth changes live:'''
root@localhost$ su - postgres
postgres@localhost$ pg_ctl reload
postgres@localhost$ exit
Bootstrapping the initial koji admin user into the PostgreSQL database: The initial admin user must be manually added to the user database using sql commands. Once they are added and given admin privilege, they may add additional users and change privileges of those users via the koji command line tool's administrative commands. However, if you choose to use the simple user/pass method of authentication, then any password setting/changing must be done manually via sql commands as there is no password manipulation support exposed through the koji tools.
The sql commands you need to use vary by authentication mechanism.
SSL Certificate authentication: there is no need for either a password or a Kerberos principal, so this will suffice:
koji=> insert into users (name, status, usertype) values ('admin-user-name', 0, 0);
Give yourself admin permissions
koji=> insert into user_perms (user_id, perm_id, creator_id) values (<id of user inserted above>, 1, <id of user inserted above>);
you can get the ID of the new user by running the query:
koji=> select * from users;
So,Release 0.2-1 results here [http://ycshon.blogspot.com/2010/11/sbr-600-project-release-02-1.html in my blog]
So,Release 0.3-1 results here [http://ycshon.blogspot.com/2010/11/sbr-600-project-release-02-1.html in my blog]
'''Last stage'''
'''Setup Koji Web and web'''
* Koji Hub Configuration
,and add the following lines to ‘/etc/httpd/conf.d/ssl.conf’, under the section ‘VirtualHost _default_:443′:
SSLCertificateFile /etc/pki/koji/certs/kojihub.crt SSLCertificateKeyFile /etc/pki/koji/certs/kojihub.key
SSLCertificateChainFile /etc/pki/koji/koji_ca_cert.crt
SSLCACertificateFile /etc/pki/koji/koji_ca_cert.crt SSLVerifyClient require SSLVerifyDepth 10
First add the kojira account and grant repo privileges with the following command( this should be done before running kojira for the first time) :
su - kojiadmin
koji add-user kojira
koji grant-permission repo kojira
Then add as many builders as required using the following commands editing where required (this should also be done prior to running kojid on each host):
So,Release 0.2-2 results here [http://ycshon.blogspot.com/2010/11/sbr-600-project-release-02-2.html in my blog]
'''Last stage''' Authorize Koji-web and Koji-hub resources: In this example, Koji-web and Koji-hub are running on localhost. /var/lib/pgsql/data/pg_hba.conf: These settings need to be valid and inline with other services configurations. Please note, the first matching auth line is used so this line must be above any other potential matches. Add: host koji koji 127.0.0.1/32 trust local koji apache trust local koji koji trust'''TO enable auth changes live:''' root@localhost$ su - postgres postgres@localhost$ pg_ctl reload postgres@localhost$ exit Bootstrapping the initial koji admin user into the PostgreSQL database: The initial admin user must be manually added to the user database using sql commands. Once they are added and given admin privilege, they may add additional users and change privileges of those users via the koji command line tool's administrative commands. However, if you choose to use the simple user/pass method of authentication, then any password setting/changing must be done manually via sql commands as there is no password manipulation support exposed through the koji tools. The sql commands you need to use vary by authentication mechanism. SSL Certificate authentication: there is no need for either a password or a Kerberos principal, so this will suffice: koji=> insert into users (name, status, usertype) values ('admin-user-name', 0, 0); Give yourself admin permissions koji=> insert into user_perms (user_id, perm_id, creator_id) values (<id of user inserted above>, 1, <id of user inserted above>); you can get the ID of the new user by running the query: koji=> select * from users; So,Release 0.3-1 results here [http://ycshon.blogspot.com/2010/11/sbr-600-project-release-02-1.html in my blog] '''Setup Koji WebKojiweb'''
1.Introduction
