Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Oct 26, 2011
  1. @bkearney
  2. @bkearney
  3. @bkearney
  4. @bkearney
  5. @bkearney

    Add in a headpin cli package

    bkearney committed
  6. @bkearney

    Break up the cli spec file

    bkearney committed
Commits on Oct 25, 2011
  1. @thomasmckay

    merge master

    thomasmckay committed
  2. @lzap
  3. @lzap
  4. @iNecas

    734517 - puppet - set pulp.conf server_name to fqdn

    iNecas committed
    It's used to generate download url for rpms
  5. @tstrachota
  6. @tstrachota
  7. @tstrachota
  8. @tstrachota
  9. @tstrachota
  10. @tstrachota

    dep calc - refactoring and performance improvement

    tstrachota committed
    - not calculating dependencies for packages that are included in any product or repository in the changeset
  11. @tstrachota
  12. @tstrachota
Commits on Oct 24, 2011
  1. @parthaa
  2. @thomasmckay
  3. @thomasmckay
  4. @adelton @cliffy94


    adelton committed with cliffy94
    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
    -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat
  5. @swarmingbee
  6. @bkearney
  7. @bkearney
  8. @knowncitizen
  9. @lzap

    improving python code style checker

    lzap committed
  10. @lzap

    improving python code style

    lzap committed
  11. @lzap

    pools - one more unit test

    lzap committed
    Finally providing proper unit test.
  12. @lzap

    pools - list of available unit test

    lzap committed
  13. @iNecas
  14. @iNecas
Commits on Oct 21, 2011
  1. @tstrachota
  2. @bbuckingham

    Systems - minor change to view to address warning during render...

    bbuckingham committed
    prior to this change, rendering the _new partial would generate an
    error similar to:
    /git/katello/src/app/views/systems/_new.html.haml:15: warning: multiple values for a block parameter (0 for 1)
      from /usr/lib/ruby/gems/1.8/gems/haml-3.1.2/lib/haml/helpers/action_view_mods.rb:160
Something went wrong with that request. Please try again.