Difference between revisions of "PKI Components Collectively via Subversion"

From Dogtag
Jump to: navigation, search
(Building All PKI Components Collectively as a Group)
(Building All PKI Components Collectively as a Group)
Line 34: Line 34:
 
   
 
   
 
  (now encapsulated in a handy script entitled '''"pki/base/scripts/pkicheck"''')
 
  (now encapsulated in a handy script entitled '''"pki/base/scripts/pkicheck"''')
 +
 +
  NOTE:  With the renamed 'pki-symkey', the "\|symkey" can be dropped from the command
 
For example, building Dogtag Certificate System 1.0.0 on a Fedora 8 platform, you'll see output like this (where "{flavor}" equals "dogtag"):
 
For example, building Dogtag Certificate System 1.0.0 on a Fedora 8 platform, you'll see output like this (where "{flavor}" equals "dogtag"):
  
Line 64: Line 66:
 
     27  pki-util-1.0.0-8.fc8
 
     27  pki-util-1.0.0-8.fc8
 
     28  pki-util-javadoc-1.0.0-8.fc8
 
     28  pki-util-javadoc-1.0.0-8.fc8
     29  symkey-1.0.0-3.fc8
+
     29  symkey-1.0.0-3.fc8 (renamed to pki-symkey for 1.3.0)
  
 
In the event that all components have '''not''' been built successfully, please debug the problem using the '''typescript.build_pki''' file produced above, and make the appropriate changes.   
 
In the event that all components have '''not''' been built successfully, please debug the problem using the '''typescript.build_pki''' file produced above, and make the appropriate changes.   

Revision as of 01:12, 5 February 2010

Building PKI Components Collectively via Subversion

Checking out PKI Source Code via Subversion

Follow the instructions to checkout a read-only copy of the PKI source code using subversion:

Building All PKI Components Collectively as a Group

In order to build all PKI components collectively as a group, the sudo executable must be available on the development machine. If present, then all PKI components can be built collectively through the use of two scripts, prepare_pki and build_pki, by becoming the root user and adding the following two lines to the /etc/sudoers file:

{username}  ALL = NOPASSWD:       /bin/rpm
{username}  ALL = NOPASSWD:       /usr/bin/yum

First, become the desired {username}, and change directories into the scripts directory:

cd src/pki/{flavor}/scripts      where "{flavor}" equals "dogtag"

Next, invoke the preparation script to install all PKI support packages:

script -c ./prepare_pki typescript.prepare_pki

NOTE: While the script command is optional, the user may find it useful for debugging purposes.

Finally, issue the following command to build all PKI components:

script -c ./build_pki typescript.build_pki

NOTE: While the script command is optional, the user may find it useful for debugging purposes.

All non-UI PKI RPMs will be created in src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/{arch} and src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/noarch, while all PKI UI components will be created in src/pki/release/pki/{flavor}/{component}/dist/rpmpkg/RPMS/noarch. All PKI RPMs will also be automatically installed on the system.


When you have finished, make sure you have all the packages installed:

rpm -qa | egrep -i pki-\|osutil\|symkey | sort | cat -n

(now encapsulated in a handy script entitled "pki/base/scripts/pkicheck")
 NOTE:  With the renamed 'pki-symkey', the "\|symkey" can be dropped from the command

For example, building Dogtag Certificate System 1.0.0 on a Fedora 8 platform, you'll see output like this (where "{flavor}" equals "dogtag"):

    1  {flavor}-pki-ca-ui-1.0.0-7.fc8
    2  {flavor}-pki-common-ui-1.0.0-6.fc8
    3  {flavor}-pki-console-ui-1.0.0-3.fc8
    4  {flavor}-pki-kra-ui-1.0.0-4.fc8
    5  {flavor}-pki-ocsp-ui-1.0.0-3.fc8
    6  {flavor}-pki-ra-ui-1.0.0-4.fc8
    7  {flavor}-pki-tks-ui-1.0.0-3.fc8
    8  {flavor}-pki-tps-ui-1.0.0-4.fc8
    9  osutil-1.0.0-3.fc8
   10  pki-ca-1.0.0-17.fc8
   11  pki-common-1.0.0-28.fc8
   12  pki-common-javadoc-1.0.0-28.fc8
   13  pki-console-1.0.0-9.fc8
   14  pki-java-tools-1.0.0-3.fc8
   15  pki-java-tools-javadoc-1.0.0-3.fc8
   16  pki-kra-1.0.0-8.fc8
   17  pki-manage-1.0.0-3.fc8  (NOTE: The 'pki-manage' RPM has been 'deprecated' on Fedora platforms in favor of 'yum' and 'yum-utils'!) 
   18  pki-migrate-1.0.0-4.fc8
   19  pki-native-tools-1.0.0-3.fc8
   20  pki-ocsp-1.0.0-7.fc8
   21  pki-ra-1.0.0-7.fc8
   22  pki-selinux-1.0.0-1.fc8
   23  pki-setup-1.0.0-8.fc8
   24  pki-silent-1.0.0-4.fc8
   25  pki-tks-1.0.0-7.fc8
   26  pki-tps-1.0.0-7.fc8
   27  pki-util-1.0.0-8.fc8
   28  pki-util-javadoc-1.0.0-8.fc8
   29  symkey-1.0.0-3.fc8 (renamed to pki-symkey for 1.3.0)

In the event that all components have not been built successfully, please debug the problem using the typescript.build_pki file produced above, and make the appropriate changes.

If necessary, become the desired {username}, and change directories back into the scripts directory:

   cd src/pki/{flavor}/scripts      #where "{flavor}" equals "dogtag"

Next, run the following script to remove the default instances just built:

   ./remove_default_pki_instances   #answering "y" to remove all of the instances

Then, run the following script to remove the PKI components just built:

   ./remove_pki_components          #answering "n" to acknowledge that no existing instances need be removed

Optionally, run the following script to remove the DS instance that was just installed, and then run the second script to recreate it:

   ./remove_ds_instance -s <server_id>
   
   /usr/sbin/setup-ds.pl

Save a copy of the typescript.build_pki file to compare against the PKI packages that will be rebuilt.

   mv typescript.build_pki typescript.build_pki.`date +%Y%m%d%H%M%S`

Finally, re-issue the following command to re-build all PKI components and follow the instructions above until successful:

   script -c ./build_pki typescript.build_pki