From d0de3044a449bbe818cdf8a074737d8381d46bb7 Mon Sep 17 00:00:00 2001 From: "Chris St. Pierre" Date: Thu, 17 May 2012 09:16:04 -0400 Subject: fixed doco bugs --- doc/server/plugins/generators/packages.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/server/plugins/generators/packages.txt b/doc/server/plugins/generators/packages.txt index 41e3925e5..76454b8f5 100644 --- a/doc/server/plugins/generators/packages.txt +++ b/doc/server/plugins/generators/packages.txt @@ -178,8 +178,8 @@ With the keys specified thusly, Packages will include the keys in the generated yum config file, and will ensure that the keys are imported on the client. -There is no need to specify ```` tags for :ref:``Pulp sources -``; that data is pulled directly from the Pulp +There is no need to specify ```` tags for :ref:`Pulp sources +`; that data is pulled directly from the Pulp REST API. .. _packages-exampleusage: @@ -243,7 +243,7 @@ Yum sources can be similarly specified:: For sources with a **URL** attribute, the **Version** attribute is also necessary. -:ref:``Pulp sources `` are very simple to specify +:ref:`Pulp sources ` are very simple to specify due to the amount of data that can be queried from Pulp itself:: -- cgit v1.2.3-1-g7c22 From cf1f4029b97f5e3100a7f9c31308a2e8b82657be Mon Sep 17 00:00:00 2001 From: "Chris St. Pierre" Date: Thu, 17 May 2012 16:17:56 -0400 Subject: fixed bug in FileProbes doco --- doc/server/plugins/probes/index.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/server/plugins/probes/index.txt b/doc/server/plugins/probes/index.txt index f22f405c1..33d6aa7d7 100644 --- a/doc/server/plugins/probes/index.txt +++ b/doc/server/plugins/probes/index.txt @@ -211,7 +211,7 @@ look something like: - + -- cgit v1.2.3-1-g7c22 From 4c4534c2302c869f5f8258eb7107dcf531e0edc7 Mon Sep 17 00:00:00 2001 From: "Chris St. Pierre" Date: Wed, 23 May 2012 10:47:13 -0400 Subject: added ability to specify arbitrary repository options to Packages --- doc/server/plugins/generators/packages.txt | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) (limited to 'doc') diff --git a/doc/server/plugins/generators/packages.txt b/doc/server/plugins/generators/packages.txt index 76454b8f5..54e92f1f6 100644 --- a/doc/server/plugins/generators/packages.txt +++ b/doc/server/plugins/generators/packages.txt @@ -182,6 +182,36 @@ There is no need to specify ```` tags for :ref:`Pulp sources `; that data is pulled directly from the Pulp REST API. +Arbitrary Repo Options +---------------------- + +.. versionadded:: 1.2.3 + +You can specify arbitrary options to be added to the repository config +on the server side, if you are using the native yum libraries, and on +the client side if you are using the ability of Packages to +automatically generate your Yum config. To do this, add an +```` tag to a Source; all of its attributes will be added +verbatim to the repository in the generated config. For instance:: + + + x86_64 + + + +If you are using native yum libraries and need to set options only on +the Bcfg2 server, you can set the ``serveronly`` attribute to "true"; +or, if you need to set options only on the client, you can set the +``clientonly`` attribute to "true". For instance, if your Bcfg2 +server needed to use a proxy to access a repo, and you wanted to +expire metadata caches very quickly on the client, you could do:: + + + x86_64 + + + + .. _packages-exampleusage: Example usage -- cgit v1.2.3-1-g7c22 From 19582d1e8a2bfd3131988b309b330ad01b2c803b Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Thu, 24 May 2012 14:29:41 -0500 Subject: doc: Fix client tool driver name (reported by m4z on IRC) Signed-off-by: Sol Jerome --- doc/development/client-driver.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/development/client-driver.txt b/doc/development/client-driver.txt index 32bb0aff4..c42d2b964 100644 --- a/doc/development/client-driver.txt +++ b/doc/development/client-driver.txt @@ -20,7 +20,7 @@ an existing driver, and the process that was used to create it. * Otherwise, subclass ``Bcfg2.Client.Tools.Tool`` (from here referenced as branch [T]) -#. Set ``__name__`` to "RPM" +#. Set ``name`` to "RPM" #. Add any required executable programs to ``__execs__`` #. Set ``__handles__`` to a list of (**entry.tag**, **entry.get('type')**) tuples. This determines which entries the Tool module can be used -- cgit v1.2.3-1-g7c22 From f379b0e43cfa0137379ad0f78f48223eba7db61a Mon Sep 17 00:00:00 2001 From: "Chris St. Pierre" Date: Wed, 13 Jun 2012 14:36:39 -0400 Subject: improved SSLCA verification routines and logging --- doc/server/plugins/generators/sslca.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/server/plugins/generators/sslca.txt b/doc/server/plugins/generators/sslca.txt index 8e33148cb..d2b051535 100644 --- a/doc/server/plugins/generators/sslca.txt +++ b/doc/server/plugins/generators/sslca.txt @@ -33,7 +33,7 @@ must contain full (not relative) paths. #. Add SSLCA to the **plugins** line in ``/etc/bcfg2.conf`` and restart the server -- This enabled the SSLCA plugin on the Bcfg2 server. -#. Add a section to your ``/etc/bcfg2.conf`` called sslca_foo, replacing foo +#. Add a section to your ``/etc/bcfg2.conf`` called ``sslca_foo``, replacing foo with the name you wish to give your CA so you can reference it in certificate definitions. @@ -51,6 +51,12 @@ must contain full (not relative) paths. specification. If you're using a self signing CA this would be the CA cert that you generated. +#. Optionally, add ``verify_certs = false`` if you don't wish to + perform certificate verification on the certs SSLCA generates. + Verification includes ``openssl verify`` to verify the CA chain, + and ensuring that both the key file and certificate file contain + the same key. + #. Once all this is done, you should have a section in your ``/etc/bcfg2.conf`` that looks similar to the following:: -- cgit v1.2.3-1-g7c22