Regigate requirements

From regify WIKI
Jump to navigation Jump to search

regigate VM requirements

The VM you are creating should be supplied with the following minimum configuration:

  • 1x 64 bit x86_64 CPU (AMD or Intel, single core will be sufficient, two cores is perfect)
  • 1GB RAM
  • 12GB of hard-disk space
  • 1 virtual network adapter
  • 1 virtual CD-ROM drive (for installation of the ISO image only)

After installation, the regigate appliance is managed and updated through SSH console. It offers Nagios compliant monitoring options.

Setup requirements

For a regigate

In order to quickly install and run regigate, you need to prepare some prerequisites before you install together with regify support:

  • A system with the requirements mentioned above on this page.
  • You need access to your email server administration (eg Exchange).
  • Please keep the following information on hand:
    • An IP address in the same network range as your existing e-mail gateway/mailserver.
    • IP address and network mask of your e-mail gateway (or e-mail server).
    • Internet-gateway IP address.
  • Prepare two passwords for the appliance:
    • One for the "root" user.
    • One for the regular "regify" user.
    • Passwords must be at least 8 characters, containing uppercase and lowercase letters and numbers (no special chars allowed!).
  • An administrative e-mail address where regigate will send messages to the admin.
  • You need the regigate activation code from your regify support contact.
  • regigate will have to contact the following internet domains:
    • Your regify provider to connect to (on port 900x, depending on the providers configuration)
    • updates.regify.com (port 80 and 443)
    • pkgs.regify.com (port 80 and 443)
    • www.regify.com (port 80)

For the connected regify provider

In order to allow regigates connecting to your regify provider, please respect the following prerequisites:

  • The regigates will connect using ports 9000 + sub-provider ID (eg port 9001 for the main provider and 9002 for the first sub-provider). You might need to enable the firewall/routing for this.
  • If you want to use regigate, the system does not work with SSL offloading.
    • The SSL termination needs to be done on the regify provider.
    • You still can use a loadbalancer on basis of HTTPS without SSL offloading (using IP based sticky sessions).
  • You need the regigate activation code from your regify support contact.

Redundancy

If you are planning to operate the regigate appliance on real hardware, you will get an offer for two hardware devices. The regigate appliance supports fully redundant operation and offers real-time fail-over using floating IP's.

If you plan to run the regigate appliance on a virtualized environment, please consider the following:

  • If your VM environment is fully redundant (eg Cluster based virtualization), it might be sufficient to run only one regigate instance.
  • If your VM is not redundant, you should consider running two regigate appliances on two different VM hosts. The two instances can get linked together to form a redundant solution using floating IP's (as if it was on real hardware).

We strongly advise to not run regigate without any redundancy as e-mail flow may become interrupted.

regigate performance

The performance highly depends on the speed of your internet connectivity and the amount of CPU in the regigate appliance environment. Here are some values for your information:

Test environment:

  • Single supermicro hardware appliance
  • CPU dual core Atom D525 w/HT 1.8GHz
  • 2GB RAM
  • 80GB Intel SSD
  • Direct provider and clearing connection (full speed 1GBit)

The appliance was able to encrypt and decrypt 210.200 messages/day with random sizes between 1Kb and 5Mb.

Please contact regify support if you need more transactions/day.