From 1ccdc403fd808c6e1bd7401c513ecf5478ec9abd Mon Sep 17 00:00:00 2001 From: Narayan Desai Date: Tue, 27 Sep 2005 20:10:03 +0000 Subject: add a section for the xml-rpc stuff (Logical change 1.322) git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@1313 ce84e21b-d406-0410-9b95-82705330c041 --- doc/install.xml | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/doc/install.xml b/doc/install.xml index ff7fd8156..48498a735 100644 --- a/doc/install.xml +++ b/doc/install.xml @@ -109,4 +109,55 @@ $ python setup.py install machine bcfgserver, port 8052, with the wire protocol "challenge". + + New-Style XML-RPC Deployments + + + A new version of the Bcfg2 software is in testing that will + provide simplified and standards compliant communications + facilities. Instead of the use of SSSlib for communication, the + server and clients can use HTTPS XML-RPC instead. This has + required reimplementing the server and providing XML-RPC support + for the client, but provides drastically simplified setup for + new installs. + + + + The prerequisite list now includes ElementTree, M2Crypto (for + SSL functions) and Python 2.2 or newer. ElementTree and M2Crypto + are both python modules that can be easily installed and are + already packaged for many Linux distributions. + + + + SSL Certificate Generation + + SSL is used for channel-level data encryption. The + requisite SSL certificates must be generated on the server + side. I need to figure out how to do this. + + + + + + Communication Bootstrapping + + + The Bcfg2 client must be able to find the server's + location. This is accomplished through the use of the + communication settings in /etc/bcfg2.conf + Two settings for the this section are required: protocol and + server url. + + + + Bcfg2 XML-RPC Communication Settings + + [communication] + protocol = xmlrpc/ssl + url = https://localhost:9443 + + + + \ No newline at end of file -- cgit v1.2.3-1-g7c22