Permalink
Switch branches/tags
rubygem-katello-2.4.0-2 rubygem-katello-2.4.0-1 rubygem-katello-2.3.1-2 rubygem-katello-2.3.1-1 rubygem-katello-2.3.0-7 rubygem-katello-2.3.0-6 rubygem-katello-2.3.0-5 rubygem-katello-2.3.0-4 rubygem-katello-2.3.0-3 rubygem-katello-2.3.0-2 rubygem-katello-2.3.0-1 rubygem-katello-2.2.4-1 rubygem-katello-2.2.3-2 rubygem-katello-2.2.3-1 rubygem-katello-2.2.2-2 rubygem-katello-2.2.2-1 rubygem-katello-2.2.1-1 rubygem-katello-2.2.1-0 rubygem-katello-2.2.0-11 rubygem-katello-2.2.0-10 rubygem-katello-2.2.0-9 rubygem-katello-2.2.0-8 rubygem-katello-2.2.0-7 rubygem-katello-2.2.0-6 rubygem-katello-2.2.0-5 rubygem-katello-2.2.0-4 rubygem-katello-2.2.0-3 rubygem-katello-2.2.0-2 rubygem-katello-2.2.0-1 rubygem-katello-2.1.2-3 rubygem-katello-2.1.2-2 rubygem-katello-2.1.1-2 rubygem-katello-2.1.1-1 rubygem-katello-2.1.0-5 rubygem-katello-2.1.0-4 rubygem-katello-2.1.0-3 rubygem-katello-2.1.0-2 rubygem-katello-2.1.0-1 rubygem-katello-2.0.0-6 rubygem-katello-2.0.0-5 rubygem-katello-2.0.0-4 rubygem-katello-2.0.0-3 rubygem-katello-2.0.0-2 rubygem-katello-2.0.0-1 rubygem-katello-1.5.0-12 rubygem-katello-1.5.0-11 rubygem-katello-1.5.0-10 rubygem-katello-1.5.0-9 katello-utils-1.4.1-1 katello-utils-1.3.2-1 katello-utils-1.3.1-1 katello-utils-1.2.1-1 katello-utils-1.1.2-1 katello-utils-1.1.1-1 katello-selinux-1.4.1-1 katello-selinux-1.3.2-1 katello-selinux-1.3.1-1 katello-selinux-1.1.2-1 katello-selinux-1.1.1-1 katello-selinux-1.0.1-1 katello-selinux-0.2.7-1 katello-selinux-0.2.6-1 katello-selinux-0.2.5-1 katello-selinux-0.2.4-1 katello-selinux-0.2.3-1 katello-selinux-0.2.2-1 katello-selinux-0.2.1-1 katello-selinux-0.1.10-1 katello-selinux-0.1.9-1 katello-selinux-0.1.8-1 katello-selinux-0.1.7-1 katello-selinux-0.1.6-1 katello-selinux-0.1.5-3 katello-selinux-0.1.5-2 katello-selinux-0.1.5-1 katello-selinux-0.1.4-1 katello-selinux-0.1.3-1 katello-selinux-0.1.2-1 katello-repos-1.4.1-1 katello-repos-1.3.4-1 katello-repos-1.3.3-1 katello-repos-1.3.2-1 katello-repos-1.3.1-1 katello-repos-1.2.4-1 katello-repos-1.2.3-1 katello-repos-1.2.2-1 katello-repos-1.2.1-1 katello-repos-1.1.3-1 katello-repos-1.1.2-1 katello-repos-1.1.1-1 katello-repos-1.0.3-1 katello-repos-1.0.2-1 katello-repos-1.0.1-1 katello-repos-0.2.10-1 katello-repos-0.2.9-1 katello-repos-0.2.8-1 katello-repos-0.2.7-1 katello-repos-0.2.6-1 katello-repos-0.2.5-1 katello-repos-0.2.4-1
Nothing to show
Commits on Oct 26, 2011
  1. Add in a headpin cli package

    bkearney committed Oct 24, 2011
  2. Break up the cli spec file

    bkearney committed Oct 24, 2011
Commits on Oct 25, 2011
  1. merge master

    thomasmckay committed Oct 25, 2011
  2. 734517 - puppet - set pulp.conf server_name to fqdn

    iNecas committed Oct 25, 2011
    It's used to generate download url for rpms
  3. dep calc - refactoring and performance improvement

    tstrachota committed Oct 24, 2011
    - not calculating dependencies for packages that are included in any product or repository in the changeset
Commits on Oct 24, 2011
  1. Hello,

    adelton committed with cliffy94 Oct 24, 2011
    attached please find a series of three patches that hide the puppet
    output and instead shows progress for some long-running operations.
    
    Which operations are they?
    
    Starting Katello configuration
    The top-level log file is [/var/log/katello/katello-configure-20111013-091200/main.log]
    Creating Katello database user
    Creating Katello database
    Creating Candlepin database user
    Creating Candlepin database
    Candlepin setup
    Populating Katello database schema
    
    How do we know the progress of these?
    
    We stat the length of log files that these operations generate.
    
    Why doesn't it show the progress of (for example) service katello
    start or service katello-jobs start?
    
    These are started using
    
    	service {["katello", "katello-jobs"]:
    		ensure  => running, ... }
    
    and I did not find a way to redirect the stdout of those commands
    (initiated by service) to a log file to be able to check its length.
    Please let me know if you have any hints.
    
    Also, there are many other operations that puppet does between
    the steps above -- so you will have "... OK" on the previous line
    but no additional step listed as running. Again, I welcome any
    suggestion how to improve the situation (or better yet, just fix it
    in git once these patches are reviewed and applied) without
    rewriting to English all the output lines that puppet generates.
    
    How do you add other steps to have the progress shown?
    
    You redirect their output to a log file and you add the log file
    entry to the commands_by_logfiles hash, with a message to print
    when the command starts, and the expected "success" length of the
    file.
    
    -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat
  2. improving python code style checker

    lzap committed Oct 24, 2011
  3. improving python code style

    lzap committed Oct 24, 2011
  4. pools - one more unit test

    lzap committed Oct 24, 2011
    Finally providing proper unit test.
  5. pools - list of available unit test

    lzap committed Oct 24, 2011
Commits on Oct 21, 2011