Difference between revisions of "Fedora-ARM,Dogfood - koji Hub"
| Line 64: | Line 64: | ||
The next steps is to create a user named “koji”, set up Postgresql and populate the schema: | The next steps is to create a user named “koji”, set up Postgresql and populate the schema: | ||
| − | + | useradd koji | |
| − | + | passwd -d koji | |
| − | + | su - postgres | |
| − | + | createuser koji | |
| − | + | Shall the new role be a superuser? (y/n) n | |
| − | + | Shall the new role be allowed to create databases? (y/n) n | |
| − | + | Shall the new role be allowed to create more new roles?(y/n) n | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
createdb -O koji koji | createdb -O koji koji | ||
Revision as of 21:56, 24 November 2010
Contents
Project Name
Fedora-ARM Dogfood -Koji Hub
Project Description
The Fedora-ARM koji system uese HongKong,an x86_64 system, as the Koji hub.
The Fedora-ARM project to use ARM system as the Koji hub(this is called "Eating own dogfood" in the industry)
The project involves configuring the OpenRD-Client system as koji hub.
The Fedora ARM Koji system is running. It is currently building F13 under the supervision of Whalen and Chris Tyler. Koji have 22 hardware ARM builders. I am in the progress of building Fedora 13 under IRAQ.
Project Leader(s)
Project Contributor(s)
No one contributed to this project
Project Details
First stage
- Koji Authentication Selection
Koji primarily supports Kerberos and SSL Certificate authentication. For basic koji command line access,
plain user/pass combinations are possible. However, kojiweb does not support plain user/pass authentication.
Furthermore, once either Kerberos or SSL Certificate authentication is enabled so that kojiweb will work,
the plain user/pass method will stop working entirely.
As such plain user/pass authentication is a stop gap measure at best unless you intend to never setup
a fully functional kojiweb instance.
The Kerberos credentials of the initial admin user will be necessary to bootstrap the user database.
For SSL authentication, SSL certificates for the xmlrpc server, for the various koji components,
and one for the admin user will need to be setup
1.Setting up SSL Certificates for authentication
2.Setting up Kerberos for authentication
So,Release 0.1 results here in my blog
Second stage
Koji Database
1.Create Database
yum install postgresql-server
2. Once installed you will then need to initialize the Database with the following command:
service postgresql initdb
3.Start the Postgresql service with:
service postgresql start
4. At this point the Postgresql server is installed and operational provided no errors were reported with the database initialized.
The next steps is to create a user named “koji”, set up Postgresql and populate the schema:
useradd koji passwd -d koji su - postgres createuser koji Shall the new role be a superuser? (y/n) n Shall the new role be allowed to create databases? (y/n) n Shall the new role be allowed to create more new roles?(y/n) n
createdb -O koji koji logout
su - koji
psql koji koji < /usr/share/doc/koji*/docs/schema.sql
exit
Project Plan
Goals for each release:
- 0.1 - Koji Certificates
Koji Hub setup - Certificates/security
- 0.2 - Koji Hub setup and Koji Database
Koji Hub Setup- Configuration
To setup PostgreSQL for use with Koji
- 0.3 - Koji Web
Build software with koji hub
Project News
1,November I will do Project Plan 0.1- I set up Koji Certificates
5,November I did build and create Koji Certifacation on IRAQ server.
9,Novenber I set up Koji Database.
Resources
Configuration of CDOT_Development system
