From edca0b698637c3fd0a70af7e4752a46afca938d3 Mon Sep 17 00:00:00 2001 From: Narayan Desai Date: Mon, 23 Jan 2006 22:35:40 +0000 Subject: last step of repo switches git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@1716 ce84e21b-d406-0410-9b95-82705330c041 --- doc/deployment.xml | 214 +---------------------------------------------------- 1 file changed, 4 insertions(+), 210 deletions(-) (limited to 'doc/deployment.xml') diff --git a/doc/deployment.xml b/doc/deployment.xml index d687ea187..1114589d3 100644 --- a/doc/deployment.xml +++ b/doc/deployment.xml @@ -52,58 +52,6 @@ ports. - - - Package - - - A software package. This entity includes a package name - and version number. It may optionally include installation - information (such as a package source URL) if one is - needed. - - - - - ConfigFile - - - A configuration file. This entity includes a file path, - owner, group, permissions, and file contents. - - - - - SymLink - - - A symbolic link. This entity includes a source and - destination. - - - - - Service - - - A service (de)activation. This controls services, a la - chkconfig or update-rc.d. Services are restarted - whenever co-located configuration entities are - modified. This ensures that any configuration changes - are flushed out to all active processes. - - - - - Directory - - - A filesystem directory. This entity includes an owner, - group and permissions. - - - -
@@ -129,166 +77,12 @@
- Object Oriented Configs - - One of the most powerful and useful parts about bcfg2 metadata - system is the ability to have truely Object Oriented configs. I - have found that this has made me understand the machines I am - managing in a whole new light. Instead of focusing on what is - installed, I now focus on how machines relate to each other, or - what pieces of the metadata are similar in their configs. To - illistrate this think about the following example machines: - - - - A users desktop machine - A multiuser compute machine - A users home machine. (telecommuter) - - - These 3 machines have 3 distinct focuses for usage, but in reality - they can have a very similar metadata, depending on how the config is - broken up or the view that is taken of the config. If you focus first - on where the machines are the same it will help to build the common - metadata. below is what all 3 machines have in common: - - - users need to have the software they need to perform - there work. - - - let just encode this into metadata by creating a Class called - common-software that contains all the common software between all 3 - machines. - - - - - .... - - ]]> - - - now we need to find where they differ: - - - - Desktop machines - - - - need to have a GUI interface( Xwindows or what not ) - - - use NIS for authentification - - - use Autofs to mount home directories - - - - - - Multiuser compute machines - - - - only accessible by SSH, No GUI interface - - - use NIS for authentification - - - use Autofs to mount home directories - - - - - - Home machine - - - - need to have a GUI interface( Xwindows or what not ) - - - use static password file - - - use local disk for home directories - - - - - - - As you can see that there are common things pairwise in these configs - that can be further exploited by the object oriented system of bcfg2 - - - - - ... - - - - ... - - ]]> - - - now all that is left is to ensure that all needs are met and we find - we need to make one more class: - - - - - ... - - ]]> - - - Now we can mix and match these classes together to build the 3 - profiles or even build new profiles with these descrete entities. - - - - - - - - - - - - - - - - - - - - ]]> - - - The free form object oriented fashion in which metadata can be - constructed is truely a double edge sword. On one hand you can build - up a nice list of descrete entities that can compose even the most - complicated configs, but it also allows for the creation of entities - that could provide monolithic solutions to each machines config. It is - all in how one views the machines and how much they are willing to - harness the power of the OO based metadata system. - -
-
- Tips & Tricks + Bcfg2 Server Administration + +
+
An example application of bcfg2 -- cgit v1.2.3-1-g7c22