This global settings are needed for fsi portal to run:

• deploy server name and ip
• portal user roles
• db settings

Some other section optional:

• domain settings for login
• xenserver add default template

The sections for servers operating system to install are documented in three other wiki pages.

Every rzenv.xml has at least following section:

<rz Develop>
  # config content
</rz>

Develop is the name of the data center and is shown in the browser tab heading.

   vitemp      "template.example.com"   # global parameter for deploy server hostname with dns suffix
   vitempip    "192.168.1.1"            # deploy server main network ip

   <userrole Admin>          # Role Admin can do all
   </userrole>
   <userrole Install>        # Role Install is for start/abort installations
   </userrole>
   <userrole XenAdmin>       # Role XenAdmin is for alle XenServer/Xen Pool Actions
   </userrole>
   <userrole ESXiAdmin>      # Role ESXiAdmin is for alle ESXi/VC Actions
   </userrole>
   <userrole LXAdmin>        # Role LXAdmin is for alle Linux/Model Actions
   </userrole>
   <userrole AddServer>      # Role Add Server can add new Server
   </userrole>

The fsi portal creates a postgresql database from the server config files. The following section is the config to this db:

   <db>
      port              5432                         # database port
      name              fsidb                        # db name
      usr               dbuser                       # db user
      pw                password                     # db user password
      host              localhost                    # db server
   </db>

You can define the xenserver default template for add server with the following xml structure:

   <templdefault>             # Default Template config hash
      <xen650>                # Xenserver Add Version
         <2bond_lacp>         # Template name as dir name
            default true
         </2bond_lacp>
      </xen650>
   </templdefault>

The fsi portal access configuration can use a MS Windows or LDAP domain. Both a single user or a group are supported.

   <windom labdom>                                   # PRE Win2000 Netbios Domain Name
      dns   labdom.lab.local                         # dns Windows Domain Name
      dc    labdc.labdom.lab.local                   # if dns domain name not usable or other dc for login
      <search domainbase>                            # user search base (multiple possible)
         base "dc=labdom, dc=lab, dc=local"
      </search>
      <search users>
         base "CN=Users,DC=labdom,DC=lab,DC=local"
      </search>
      <search labor>
         base "OU=User,OU=Labor,DC=labdom,DC=lab,DC=local"
      </search>
   </windom>

   daemonsleep 10    # fsi check all daemon rescan sleep time