| ao_server_daemon_hosts | 3 | 1.0a100 | ao_server_daemon_hosts stores which hosts may connect to the AOServ Daemon on a server. |
| ao_servers | 25 | 1.0a100 | The ao_servers table keeps track of all the servers that are running the AOServ distribution. |
| aoserv_permissions | 2 | 1.21 | aoserv_permissions lists all of the possible permissions in the AOServ Platform. |
| aoserv_protocols | 4 | 1.0a101 | aoserv_protocols keeps track of the different versions of the protocol
and what is available in that protocol. |
| aosh_commands | 6 | 1.0a100 | aosh_commands stores the details about each command that may be used in the AO shell. |
| architectures | 2 | 1.0a100 | The architectures table provides all the possible computer architectures for the servers table. |
| backup_partitions | 4 | 1.0a100 | The backup_partitions table stores the details of each backup location. |
| backup_reports | 6 | 1.0a101 | The backup_reports table stores the daily summary of backup system usage. |
| backup_retentions | 2 | 1.0a100 | backup_retentions stores all of the possible backup retention times. |
| bank_accounts | 5 | 1.0a100 | The bank_accounts table stores all the bank accounts we operate. |
| bank_transaction_types | 4 | 1.0a100 | The bank_transaction_types table stores all the possible types of transactions for bank_transactions. |
| bank_transactions | 11 | 1.0a100 | The bank_transactions table stores all the the transactions that have occured on a bank account. |
| banks | 2 | 1.0a100 | The banks table stores information about each bank we deal with |
| blackhole_email_addresses | 1 | 1.0a100 | The blackhole_email_addresses is a list of email addresses in which all email sent
to them is immediately discarded via /dev/null. |
| brands | 39 | 1.44 | Each brand has separate website, packages, nameservers, and support |
| business_administrators | 22 | 1.0a100 | The business_administrators table stores details about the people who are allowed
to access the aoserv and aoweb utilities. |
| business_administrator_permissions | 3 | 1.21 | Grants administrative permissions. |
| business_profiles | 21 | 1.0a100 | The business_profiles stores all the old profile data for a business.
This is done so that old contacts may be used in case of an emergency. |
| businesses | 13 | 1.0a100 | The businesses table stores details about businesses |
| business_servers | 12 | 1.0a100 | The business_servers table stores which servers may be accessed by which business.
A child business can only access a subset of the parent business' servers.
Only one entry per business is flagged as default. |
| country_codes | 4 | 1.0a100 | The country_codes table contains all of the valid country codes.
This data was obtained from http://digitalid.verisign.com/ccodes.html |
| credit_card_processors | 12 | 1.29 | The credit_card_processors table stores all of the different credit card processing merchant accounts. |
| credit_card_transactions | 90 | 1.29 | The credit_card_transactions table stores the complete history of credit card processor transactions. |
| credit_cards | 33 | 1.0a100 | The credit_cards table stores all of the client credit card information in an encrypted format. |
| Currency | 3 | 1.83.0 | The supported currencies. |
| cvs_repositories | 7 | 1.0a100 | The cvs_repositories table stores the details of each CVSROOT |
| cyrus_imapd_binds | 5 | 1.81.10 | The cyrus_imapd_binds table represents all the ip_address port binding combinations.
The app_protocol of the bind should always be POP3, IMAP2, SIMAP, or SPOP3. |
| cyrus_imapd_servers | 11 | 1.81.10 | The cyrus_imapd_servers table contains a list of all the Cyrus IMAPD servers. |
| disable_log | 5 | 1.0a100 | The disable_log logs all the times things are disabled. |
| distro_file_types | 2 | 1.0a100 | The distro_file_types stores all of the possible file types. |
| distro_files | 14 | 1.0a100 | The distro_files stores all of the file attributes in the templates. |
| distro_report_types | 2 | 1.70 | The distro_report_types stores all of the possible report types. |
| dns_forbidden_zones | 1 | 1.0a100 | dns_forbidden_zones stores all of the DNS zones that may not be hosted by the name servers |
| dns_records | 12 | 1.0a100 | dns_records stores all of individual records of the name server. |
| dns_tlds | 2 | 1.0a100 | dns_tlds stores all of the domains that are considered to be "top level domains". |
| dns_types | 8 | 1.0a100 | dns_types stores all of the types of entries that may be placed in a line of a zone file. |
| dns_zones | 6 | 1.0a100 | dns_zones stores all of the DNS zones. |
| email_addresses | 3 | 1.0a100 | The email_addresses table stores a central pool of all email addresses. |
| email_attachment_blocks | 3 | 1.0a116 | The email_attachment_blocks table stores all attachment types that are currently blocked. |
| email_attachment_types | 3 | 1.0a116 | email_attachment_types stores all of the possible attachment extensions that may be blocked. |
| email_domains | 4 | 1.0a100 | The email_domains table stores all the domains that the MTA responds to. |
| email_forwarding | 3 | 1.0a100 | The email_forwarding sends email addresssed to email_addresses to another address. |
| email_list_addresses | 3 | 1.0a100 | The email_list_addresses attaches the email_addresses to the email lists. |
| email_lists | 5 | 1.0a100 | The email_lists table stores pointers to all the list files that are used for email. |
| email_pipe_addresses | 3 | 1.0a100 | The email_pipe_addresses attaches the email_addresses to the email pipes. |
| email_pipes | 5 | 1.0a100 | The email_pipes table stores pointers to all the processes that are used for direct delivery of email. |
| email_smtp_relay_types | 3 | 1.0a100 | The email_smtp_relay_types table stores all the different types of SMTP rules. |
| email_smtp_relays | 10 | 1.0a100 | The email_smtp_relays table stores the SMTP server access rules. |
| email_smtp_smart_host_domains | 5 | 1.57 | The email_smtp_smart_host_domains table stores optional per-domain settings for email_smtp_smart_hosts. |
| email_smtp_smart_hosts | 5 | 1.57 | The email_smtp_smart_hosts table indicates a SMTP port is configured as a SmartHost for one or more servers. |
| email_sa_integration_modes | 3 | 1.0a120 | The email_sa_integration_modes tables provides all the possible spam assassin itegration modes supported. |
| encryption_keys | 3 | 1.23 | The encryption_keys table stores the list of GPG key ids on a per-business basis. |
| expense_categories | 1 | 1.0a100 | The expense_categories table is a lookup for bank_transactions, and is used to
organize expenditures for accounting purposes. |
| failover_file_log | 8 | 1.0a100 | The failover_file_log records statistics about each finished failover file replication. |
| failover_file_replications | 10 | 1.0a100 | The failover_file_replications configures the replication of files from servers to failover servers. |
| failover_file_schedule | 5 | 1.0a100 | The failover_file_schedule controls when replications occur. |
| failover_mysql_replications | 9 | 1.28 | The failover_mysql_replications indicates a failover replication is using MySQL replication
for /var/lib/mysql/... instead of file-based replication. |
| file_backup_settings | 5 | 1.0a100 | The file_backup_settings table overrides everything in the backup
system except file_backup_devices. |
| firewalld_zones | 6 | 1.81.0 | The firewalld_zones table defines all Firewall zones used on an AOServer. |
| ftp_guest_users | 1 | 1.0a100 | Each linux_account may optionally be a guest FTP user. A guest FTP user is restricted
to FTP access in their home directory. The passwd and group files are created such that any username
or group in the same business resolve to the correct text names. |
| httpd_binds | 2 | 1.0a100 | The httpd_binds table represents all the ip_address port binding combinations.
The app_protocol of the bind should always be HTTP or HTTPS. |
| httpd_jboss_sites | 7 | 1.0a100 | httpd_jboss_sites ties httpd_sites to a jboss version to its httpd_shared_tomcat JVM. |
| httpd_jboss_versions | 3 | 1.0a100 | httpd_jboss_versions is a lookup table containing information about different jboss versions. |
| httpd_jk_codes | 1 | 1.0a100 | The httpd_jk_codes table contains all the possible mod_jk codes.
The codes must be unique for one httpd_sites when the site is used
in multiple httpd_servers. |
| httpd_jk_protocols | 1 | 1.0a100 | The httpd_jk_protocols table contains all of the possible protocols used by the mod_jk Apache module. |
| httpd_servers | 47 | 1.0a100 | The httpd_servers table contains a list of all the Apache servers. |
| httpd_shared_tomcats | 17 | 1.0a100 | httpd_shared_tomcats stores information about the JVM shared by httpd_tomcat_shared_sites. |
| httpd_site_authenticated_locations | 9 | 1.18 | The httpd_site_authenticated_locations configured Apache basic
authentication using Location directives. |
| httpd_site_bind_headers | 11 | 1.81.15 | The httpd_site_bind_headers configures headers on httpd_site_binds. |
| RewriteRule | 7 | 1.81.21 | The per-VirtualHost set of RewriteRule. |
| httpd_site_binds | 12 | 1.0a100 | The httpd_site_binds attaches httpd_sites to httpd_binds. |
| httpd_site_urls | 4 | 1.0a100 | The httpd_site_urls stores the hostnames that a site will respond to. |
| httpd_sites | 22 | 1.0a100 | The httpd_sites table stores all of the site names used in the
/www directory on servers. Each site name must be unique per
server. Also, for site portability, it is preferred that sites
remain unique between one set of servers. Such as AO Industries
will use unique names across all of its virtual servers, while
resellers may also choose to use unique names across their sets
of dedicated machines. |
| httpd_static_sites | 1 | 1.0a100 | The httpd_static_sites stores the details of all sites that simply host static content only. |
| httpd_tomcat_contexts | 15 | 1.0a100 | The httpd_tomcat_contexts stores the details of all contexts for all Tomcat sites. |
| httpd_tomcat_data_sources | 11 | 1.5 | The httpd_tomcat_data_sources stores the data sources on a per-context basis. |
| httpd_tomcat_parameters | 6 | 1.5 | The httpd_tomcat_parameters stores the parameters on a per-context basis. |
| httpd_tomcat_site_jk_mounts | 4 | 1.81.6 | The httpd_tomcat_site_jk_mounts stores the JkMount and JkUnMount settings for each Tomcat-based site. |
| httpd_tomcat_sites | 3 | 1.0a100 | The httpd_tomcat_sites stores the details of all sites based on the Tomcat servlet engine.
This includes JBoss, single instance Tomcats, and a Tomcat that runs in a shared Java VM. |
| httpd_tomcat_shared_sites | 2 | 1.0a100 | httpd_tomcat_shared_sites ties the httpd_tomcat_site to its httpd_shared_tomcat JVM. |
| httpd_tomcat_std_sites | 9 | 1.0a100 | The httpd_tomcat_std_sites table stores the details for each site that
is self contained in its /www directory. |
| httpd_tomcat_versions | 3 | 1.0a100 | The httpd_tomcat_versions is a lookup of all the available versions of Tomcat. |
| httpd_workers | 3 | 1.0a100 | The httpd_workers table contains all of the workers that are registered on each server. |
| ip_addresses | 12 | 1.0a100 | The ip_addresses table has an entry for every IP address hosted on our machines. |
| IpAddressMonitoring | 6 | 1.81.18 | The monitoring configuration for ip_addresses |
| ip_reputation_limiter_limits | 17 | 1.66 | The per-class limits for each IP Reputation Limiter. |
| ip_reputation_limiter_sets | 4 | 1.66 | The sets for each IP Reputation Limiter. |
| ip_reputation_limiters | 4 | 1.66 | A network traffic limiter based established IP reputation. |
| ip_reputation_set_hosts | 5 | 1.65 | The per-host reputation for each IP Reputation Set. |
| ip_reputation_set_networks | 4 | 1.65 | The per-network reputation for each IP Reputation Set. |
| ip_reputation_sets | 14 | 1.65 | A set of IP reputation on a per-host and per-network basis. |
| languages | 1 | 1.44 | The languages table provides all the possible languages for brands. |
| linux_acc_addresses | 3 | 1.0a100 | The linux_acc_addresses table links email addresses to linux accounts. |
| linux_account_types | 3 | 1.0a100 | The linux_account_types table stores all the different types of linux accounts. |
| linux_accounts | 9 | 1.0a100 | The linux_accounts table stores all of the linux account info that is common to all machines. |
| linux_group_accounts | 5 | 1.0a100 | The linux_group_accounts stores the alternate users for linux groups. |
| linux_group_types | 2 | 1.0a100 | The linux_group_types table stores all the different types of linux groups. |
| linux_groups | 3 | 1.0a100 | The linux_groups table stores the details of each linux group that are common to every server. |
| linux_server_accounts | 19 | 1.0a100 | The linux_server_accounts table contains the user configuration that is unique to each server. |
| linux_server_groups | 5 | 1.0a100 | The linux_server_groups table stores the details about the groups that exist on the servers. |
| majordomo_lists | 9 | 1.0a100 | The majordomo_lists table stores the details of each list in a majordomo_server. |
| majordomo_servers | 7 | 1.0a100 | The majordomo_servers table stores all the details for one domain of Majordomo hosting. |
| majordomo_versions | 2 | 1.0a100 | The majordomo_versions table contains a list of all the supported versions of the
Majordomo manages email list server. |
| master_hosts | 3 | 1.0a100 | master_hosts stores which hosts each user may connect from. |
| master_processes | 16 | 1.0a100 | |
| master_server_stats | 3 | 1.0a100 | |
| master_servers | 3 | 1.0a100 | master_servers stores which servers each user may control. |
| master_users | 9 | 1.0a100 | master_users stores the authorization information for people that may access the master controller. |
| monthly_charges | 10 | 1.0a100 | The monthly_charges table contains an entry for each transaction that is automatically charged each month. |
| mysql_databases | 5 | 1.0a100 | The mysql_databases table stores the information about each MySQL database in the system. |
| mysql_db_users | 22 | 1.0a100 | The mysql_db_users table stores which mysql_server_users can access
which mysql_databases. The user permissions are also contained in each row. |
| mysql_server_users | 10 | 1.0a100 | The mysql_server_users table contains all the server-specific information about a mysql_user |
| mysql_servers | 5 | 1.4 | The mysql_servers table stores the information about each MySQL instance in the system. |
| mysql_users | 30 | 1.0a100 | The mysql_users table stores all of the user info that is common for every MySQL server a user has
a MySQL user account on. The server specifics are stored in the mysql_server_users table. |
| net_bind_firewalld_zones | 3 | 1.81.0 | Each port may be independently associated with a specific set of Firewalld Zones. |
| net_binds | 8 | 1.0a100 | net_binds stores all of ports that should be bound to
by processes running on the servers. If any ports is bound to that
is not listed here, it may indicate a security violation. This
data is also used to open firewall ports. Each port may also be
periodically monitored for process reliability.
Four types of IP addresses exist:
- wildcard - Processes bind to all available IP addresses on
the server. Monitoring may be performed from
anywhere, depending on firewall flags.
- public - Processes bind to a public IP address. Monitoring
may be performed from the localhost or public
network, depending on firewall rules.
- private - Processes bind to a private IP address. Monitoring
may be performed from the localhost or private
network, depending on firewall rules.
- loopback - Processes bind internally in the server. Monitoring
may only be performed from localhost.
|
| net_device_ids | 2 | 1.0a100 | The net_device_ids contains all the network devices used on Linux servers. |
| net_devices | 15 | 1.0a100 | The net_devices table contains each device used by Linux servers. |
| net_tcp_redirects | 5 | 1.0a111 | The net_tcp_redirects table stores all of the xinetd redirect configurations. |
| notice_log | 7 | 1.0a100 | The table notice_log contains information about any late or non-payment notices. |
| NoticeLog.balance | 3 | 1.83.0 | The per-currency balances for a NoticeLog. |
| notice_types | 2 | 1.0a100 | The table notice_types provides lookup information for the notice_log table |
| operating_system_versions | 8 | 1.0a100 | The operating_system_versions table provides all the supported versions of operating_systems. |
| operating_systems | 3 | 1.0a100 | The operating_systems table stores represents each type of operating system. |
| package_categories | 1 | 1.0a123 | The various categories for package_definitions. |
| package_definition_limits | 7 | 1.0a123 | The package_definition_limits table defines the limits for each package_definition and resource combination. |
| package_definitions | 13 | 1.0a123 | The package_definitions table stores a list of supported services. |
| packages | 13 | 1.0a100 | The packages table stores information about each package that businesses have signed up for. |
| payment_types | 4 | 1.0a100 | The payment_types table stores all the acceptable payment forms |
| physical_servers | 10 | 1.36 | The physical servers consume rack space and electricity and optionally provide cluster resources. |
| postgres_databases | 8 | 1.0a100 | The postgres_databases table stores the information about each PostgreSQL database in the system. |
| postgres_encodings | 3 | 1.0a100 | The postgres_encodings table stores the information about each PostgreSQL database encoding supported. |
| postgres_server_users | 5 | 1.0a100 | The postgres_server_users table stores the specific attributes of postgres_users for one server. |
| postgres_servers | 8 | 1.0a100 | The postgres_servers table stores the information about each PostgreSQL instance in the system. |
| postgres_users | 6 | 1.0a100 | The postgres_users table stores all the users for PostgreSQL.
Because a single person may have access to multiple PostgreSQL
servers, this table represents what is common to them across all
machines. The machine specific details are in the
postgres_server_users table. |
| postgres_versions | 3 | 1.0a100 | The postgres_versions is a lookup of all the available versions of PostgreSQL. |
| private_ftp_servers | 7 | 1.0a100 | The private_ftp_servers table contains an entry for each private FTP server hosted. |
| processor_types | 2 | 1.36 | The possible types of processors for cluster QoS management. |
| protocols | 4 | 1.0a100 | The protocols table has an entry for each service protocol along with the default port numbers. |
| racks | 5 | 1.36 | Each server farm may manage cluster resources on a per-rack basis. |
| resellers | 2 | 1.44 | A reseller may provide ticket-based support |
| resources | 1 | 1.0a100 | The resources table stores a list of resources that may be charged |
| schema_columns | 11 | 1.0a100 | schema_columns stores the details about the data contained in each column. |
| schema_foreign_keys | 5 | 1.0a100 | schema_foreign_keys tables stores all the foreign key info for the database. |
| schema_tables | 7 | 1.0a100 | schema_tables stores table names, display names, and descriptions for each table. |
| schema_types | 4 | 1.0a100 | schema_types stores names and unique numbers for each type. |
| sendmail_binds | 3 | 1.81.10 | The sendmail_binds table represents all the ip_address port binding combinations.
The app_protocol of the bind should always be SMTP, SMTPS, or submission. |
| sendmail_servers | 20 | 1.81.10 | The sendmail_servers table contains a list of all the Sendmail servers. |
| server_farms | 4 | 1.0a100 | The server_farms table stores the details about each unique server farm (or location) that exists. |
| servers | 7 | 1.0a100 | The servers table keeps track of all the servers that are referenced in the database |
| shells | 3 | 1.0a100 | The shells table stores all the shells that may be used in a linux account. |
| signup_request_options | 4 | 1.23 | The options for each specific sign-up type. |
| signup_requests | 37 | 1.23 | One sign-up request for any time of service. |
| spam_email_messages | 4 | 1.0a100 | The spam_email_messages table stores all of the reported spam. |
| ssl_certificate_names | 5 | 1.81.10 | The ssl_certificate_names contains all of the names associated with SSL certificates. |
| ssl_certificate_other_uses | 5 | 1.81.16 | The ssl_certificate_other_uses contains additional descriptions of how SSL certificates are used. |
| ssl_certificates | 8 | 1.81.10 | The ssl_certificates contains all of the names and paths of managed SSL certificates. |
| system_email_aliases | 4 | 1.0a100 | The system_email_aliases is a list of all entries that are placed in /etc/aliases
but are not part of the other tables. |
| technologies | 3 | 1.0a100 | The technologies table contains the list of all software packages and the classes they belong to. |
| technology_classes | 2 | 1.0a100 | The technology_classes table defines the classes that may be used in the technologies table |
| technology_names | 6 | 1.0a100 | The technology_names table contains all of the unique names of software packages
that are installed in the servers. |
| technology_versions | 8 | 1.0a100 | The technology_versions table contains the list of all software packages, owners, and versions. |
| ticket_action_types | 2 | 1.44 | Table ticket_action_types is a lookup for all of the possible actions that may be made to a ticket |
| ticket_actions | 23 | 1.44 | The ticket_actions table represent a complete history of the changes that have been made to a ticket.
When a ticket is initially created it has no actions. Any change from its initial state will cause
an action to be logged. |
| ticket_assignments | 4 | 1.44 | Tickets may be assigned to specific administrators at each reseller level. |
| ticket_brand_categories | 4 | 1.44 | Each brand may select which categories will be visible for ticket support. |
| ticket_categories | 3 | 1.44 | Each ticket may be associated with one of these hierichical categories. |
| ticket_priorities | 1 | 1.0a100 | Table ticket_priorities is a lookup table for tickets |
| ticket_stati | 2 | 1.0a100 | Table ticket_stati is a lookup table for tickets |
| ticket_types | 1 | 1.0a100 | Table ticket_types is a lookup for tickets showing types of service requests |
| tickets | 20 | 1.0a100 | Table tickets contains information on service requests |
| time_zones | 1 | 1.2 | The allowed time zones for a server |
| transaction_types | 2 | 1.0a123 | The transaction_types table stores all the types of transactions. |
| transactions | 14 | 1.0a100 | The transactions table keeps track of all transactions that have occured with the businesses |
| us_states | 2 | 1.0a100 | The us_states table contains an entry for each state in the United States. |
| usernames | 3 | 1.0a100 | The usernames table stores information about each username.
Every username is unique across the system, and may be used
for multiple services. Regardless of the system, the username
always belongs to one business, and preferrably one actual
person or system. |
| virtual_disks | 10 | 1.36 | The virtual disk configurations for cluster QoS management. |
| virtual_servers | 17 | 1.36 | A virtual server is any server that is a guest in the virtualized clustering. |
| WhoisHistory | 6 | 1.81.19 | Logs the whois history for each registrable domain. |
| WhoisHistoryAccount | 3 | 1.81.19 | Logs which accounts were associated with a registrable domain at the time of whois lookup. |
