+ Reply to Thread
Results 1 to 1 of 1

Thread: kitops Tool

  1. #1
    vbseo's Avatar
    vbseo is offline Member
    Join Date
    March 16th, 2008
    Posts
    79
    Blog Entries
    2
    Downloads
    114
    Uploads
    37

    Default kitops Tool

    A more detailed description will follow. In the meantime, below is the kitops usage information and an excerpt from the man page.

    Code:
    options:
      -h, --help            show this help message and exit
      -a, --add             add the kit specified with -m
      -l, --list            list all the kits available on the system
      -e, --remove          remove the specified kit
      -m MEDIA              specify the media iso or mountpoint for the kit
      -k KIT, --kit=KIT     kit
      -o KITVERSION, --kitversion=KITVERSION
                            kitversion
      -c KITARCH, --kitarch=KITARCH
                            kitarch
      --dbdriver=DBDRIVER   Database driver (sqlite, mysql)
      --dbdatabase=DBDATABASE
                            Database
      --dbuser=DBUSER       Database username
      --dbpassword=DBPASSWORD
                            Database password
      -y, --yes             Assume the answer to any question is Yes
      -v, --version         Display version
    
    Code:
    NAME
           kitops - Kusu/OCS kit management tool.
    
    SYNTAX
           kitops [-h|-v|-l]    - Kit information
    
           kitops  [-a  -m  Media  [{-k Kitname | --kit=Kitname}  [-o KitVersion |
           --kitversion=KitVersion] [-c  KitArch  |  --kitarch=KitArch]]]        -
           Adding a Kit
    
           kitops  [-e  {-k  Kitname  | --kit=Kitname}  [-o KitVersion | --kitver-
           sion=KitVersion] [-c KitArch | --kitarch=KitArch]                 - Kit
           removal
    
    DESCRIPTION
           Kitops is the kit operations tool.  It is for adding and removing kits.
           Once a kit is added with kitops is must be associated with one or  more
           repositories with the repoman before the kit can be used.
    
           Adding  a  kit  to the installer cause the packages to be copied to the
           /depot/kits directory.  The kit is not yet available  for  installation
           on  the  nodes.   The kit then needs to be associated with a repository
           using repoman.
    
           Kits can be deleted from the installer, however the  kit  must  not  be
           associated with any repository prior to it's removal.  Removing the kit
           from the repository may also require  de-selecting  any  components  of
           that  kit  that  are in use.  A kit cannot be removed if the components
           are in use.
    
           Upgrading a kit is performed by deleting the old kit and adding the new
           one.   However  this  is  not  desirable.  The repository using the kit
           should be snapshoted so that it can be reverted back to in the event of
           a problem.
    
    OPTIONS
           -a, --add
                  Add a kit.
    
           -e, --remove
                  Remove a kit.  The kit must not be associated with any reposito-
                  ries, and the components provided by that kit should not be used
                  in  any  nodegroups.   If this condition is not met the kit will
                  not be removed.
    
           -h, --help
                  Print the help information and exit.
    
           -k, --kit=<Kit Name>
                  Specifies the name of the kit to add or remove.
    
           -o, --kitversion=<Kit Version>
                  Specifies the kit version to add or remove.
    
           -c, --kitarch=<Kit Arch>
                  Specifies the kit architecture to add or remove.
    
           -m <Media>
                  Specifies the kit ISO file, or the mount point of the media con-
                  taining the kit to add.
    
           --dbdriver=<Driver>
                  Connect  to  an  alternate  database using the driver specified.
                  Currently mysql and/or sqlite.  This option is  not  needed  for
                  normal use.
    
           --dbdatabase=<Database>
                  Connect to an alternate database to read information from.  This
                  option is not needed for normal use.
    
           --dbuser=<User>
                  Connect to an alternate database as user <User> to read informa-
                  tion from.  This option is not needed for normal use.
    
           --dbpassword=<Password>
                  Connect to an alternate database using the password provided  to
                  read information from.  This option is  not  needed  for  normal
                  use.
    
           -v, --version
                  Print the version information and exit.
    
           -y, --yes
                  Skip the confirmation when deleting a kit.
    
    FILES
           /depot/kits/*
    
    Last edited by vbseo; September 30th, 2008 at 08:28 AM.

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts