• Russian
• 
  
• About
• 
  
• Screenshots
• 
  
• Version
• 
  
• Download
• 
  
• Rescuebsd LiveCD
• 
  
• Documentation
• 
  
• Bug report
• 
  
• Feedback

Attention! I apologize, but it is automatic machine translation of the text. You can improve it if will send to me more correct version of the text or fix html pages via GITHUB repository.

Cbsd represents an additional layer of abstraction over Jail framework and the part on FreeBSD functional

• vnet (VIMAGE)
• zfs
• racct/rctl
• ipfw
• pf
• carp
• hastd
• auditd
  

Many of these subsystems are not directly related to the jail, however, allow cbsd (which is the connecting link between these components) to provide a system administrator more advanced and integrated system solutions for the problems.

Below provides information useful to the system administrator and describes the architecture cbsd more detail.

First, the official articles about FreeBSD Jails required for the study to understand what is a jail in the usual way.

Secondly, it is useful to know about the file system hierarchy cbsd. Let us agree to use the following naming documentation and values:

• Node - physical server / resource unit.
• Jail - isolated environment with its own set of software/services. They can be a server-side components (DNS, Apache / nginx, postfix) and graphic environment.
• Cloud - Farm/cluster of interconnected nodes, a full-fledged peer network (each node can do other tasks through cbsd)
• cbsd - an entity that has control over the particular node(s) and certain subsystems of FreeBSD, is able to provide a simplified and unified action (API) on the nodes or jails and provides ACL and setting permissions for cbsd customers
• $workdir - working directory on cbsd node is initialized through cbsd initenv the first run. Usually /usr/jails.
• $jname - Name some jails, participate in the example.
  
  The most important data are located in $workdir/jails-data/$jname, as it is directly the root of the file system jails called $jname, if jail is created with the flag baserw=1, or contains the data of jail, which are superimposed on the standard $workdir/basejail/$basename in the directory ${workdir}/jails
  
  Given that the base you can always get through the building source code, or by downloading from the repository. The other words, cbsd jail to migrate to any other project management of jails or use the basic functionality FreeBSD jail, the main thing - is to have a consistent data in this directory. Notes: if you use a jails type md, then the directory $workdir/jails-data/$jname will contain the image of the jail.
  
  The second-largest in the directory hierarchy can act cbsd configuration files to create jail that are in the directory $workdir/jails-rcconf. In fact, every file is the configuration of a single jail for "jail -c" utility, but having additional cbsd-related parameters. These files can be edited with any editor when jail is stopped.
  
  Other directories are not critical to the jail themselves. For example, the directory $workdir/jails-system serves as an additional storage overhead information to jails, for example it may be configurators services, as well as statistics on the traffic and congestion, the description of the jails and so on.
  
  Inside information for the needs of the most cbsd resides in $workdir/db. For example, the information on the list of added nodes, inventory both the local and remote nodes, the database with the settings of the jails and so on.
  
  Important in terms of security, is the directories ${workdir}/.rssh and ${workdir}/.ssh, which contains the private RSA keys with remote user cbsd nodes and a local respectively. Make sure that the data of these directories were not available to other users of the system. By default, the key can be read only by a system user cbsd.
  
  

A brief summary of the hierarchy cbsd