Project

General

Profile

Bug #14224

[RFE] Have in the guy the possibility of limit Bandwith to syncronize Capsule server

Added by Mario Gamboa over 3 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Web UI
Target version:
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

At this moment is no exist any kind of option to limit the bandwidth in the sync of capsule would be great to have it at this moment we can do via

/lib/katello/engine.rb

initializer 'katello.load_default_settings', :before => :load_config_initializers do
default_settings = {
:use_pulp => true,
:use_cp => true,
:rest_client_timeout => 30,
:gpg_strict_validation => false,
:puppet_repo_root => '/etc/puppet/environments/',
:redhat_repository_url => 'https://cdn.redhat.com',
:post_sync_url => 'http://localhost:3000/katello/api/v2/repositories/sync_complete?token=katello',
:consumer_cert_rpm => 'katello-ca-consumer-latest.noarch.rpm',
:pulp => {
:default_login => 'admin',
:url => 'https://localhost/pulp/api/v2/',
:oauth_key => 'katello',
:oauth_secret => 'katello',
:bulk_load_size => 100,
:skip_checksum_validation => false,
:upload_chunk_size => 1_048_575, # upload size in bytes to pulp. see SSLRenegBufferSize in apache <--- here is really manual procedure
:sync_threads => 4,
:sync_KBlimit => nil

would be nice to have from the gui the option to put the limit and no mess up with the code.

History

#1 Updated by Eric Helms almost 3 years ago

  • Legacy Backlogs Release (now unused) changed from 144 to 168

#2 Updated by Eric Helms almost 3 years ago

  • Legacy Backlogs Release (now unused) changed from 168 to 171

#3 Updated by Eric Helms almost 3 years ago

  • Legacy Backlogs Release (now unused) deleted (171)

#4 Updated by Justin Sherrill almost 3 years ago

  • Legacy Backlogs Release (now unused) set to 114

Also available in: Atom PDF