Difference between revisions of "Groovix Net Control"
| Line 15: | Line 15: | ||
GNC updates are contained to their own directory <font class="code">/var/www/groovix/gnc/updates/[customer]</font> where [customer] is the name of your Groovix site found in <font class="code">/etc/groovix/version</font>. Each GNC update has a file at the root of the directory called gnc; the gnc file is written in bash script as a series of commands listed in the order they should be run. Groovix provides parameters and commands that customize how and when GNC updates are run and to which workstations run them, these are described in detail below. Each workstation downloads and executes the script individually after downloading it from Open Sense servers or your local Groovix Server. GNC updates that have been downloaded and executed can be found locally on each workstation in the <font class="code">/var/lib/groovix/updates/master.bash</font> file. | GNC updates are contained to their own directory <font class="code">/var/www/groovix/gnc/updates/[customer]</font> where [customer] is the name of your Groovix site found in <font class="code">/etc/groovix/version</font>. Each GNC update has a file at the root of the directory called gnc; the gnc file is written in bash script as a series of commands listed in the order they should be run. Groovix provides parameters and commands that customize how and when GNC updates are run and to which workstations run them, these are described in detail below. Each workstation downloads and executes the script individually after downloading it from Open Sense servers or your local Groovix Server. GNC updates that have been downloaded and executed can be found locally on each workstation in the <font class="code">/var/lib/groovix/updates/master.bash</font> file. | ||
| − | + | The <font class="code">/var/www/groovix/gnc/updates/[customer]</font> directory contains separate directories for the different types, sites, and labels for your deployment. GNC updates that will only apply to a specific workstation type (/etc/groovix/type1,2,etc) should be placed in the directory for that type. Updates placed in the default directory are applied to all workstations. | |
=== Script Structure === | === Script Structure === | ||
Revision as of 20:35, 13 November 2011
Contents
!!UnderConstruction!!
The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix NetCustomization or GNC. It queries updates, fixes and system changes from the Groovix Server and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.
Normally, this process is performed on boot up or customized to your specific update schedule; however, this process can be run manually at any time by typing /etc/init.d/groovix-netcustomization start in an xterm window. Every time Groovix NetCustomization is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at /var/log/groovix/netcustomization.log.
Setting up Groovix Server for GNC
!!Coming Soon!!
GNC Scripts
GNC updates are contained to their own directory /var/www/groovix/gnc/updates/[customer] where [customer] is the name of your Groovix site found in /etc/groovix/version. Each GNC update has a file at the root of the directory called gnc; the gnc file is written in bash script as a series of commands listed in the order they should be run. Groovix provides parameters and commands that customize how and when GNC updates are run and to which workstations run them, these are described in detail below. Each workstation downloads and executes the script individually after downloading it from Open Sense servers or your local Groovix Server. GNC updates that have been downloaded and executed can be found locally on each workstation in the /var/lib/groovix/updates/master.bash file.
The /var/www/groovix/gnc/updates/[customer] directory contains separate directories for the different types, sites, and labels for your deployment. GNC updates that will only apply to a specific workstation type (/etc/groovix/type1,2,etc) should be placed in the directory for that type. Updates placed in the default directory are applied to all workstations.
Script Structure
The directory structure inside each GNC update should be treated like it is the / (root) directory (ex. replacing the /etc/network/interfaces file, the interfaces file would be put in a /etc/network/ directory instead of just having the interfaces file in the root of the update directory).
All GNC updates start with a number, this number is significant. When a Groovix workstation downloads multiple updates, it runs them in sequential order. 0-1000 is reserved for GNC updates that need to be run first, 2000's are run next followed by 9000 for GNC updates that need to be run last. Most customer made updates will be named with the date, essentially putting them in the 2000's; only use 1000 or 9000 if your GNC update is required to be run before or after all other updates. If an update has changed it's purpose, add a -1, -2, etc. to the end of the update name; this ensures that this update is applied after the older version and that workstations that already ran this update, run it again with the latest change.
