Help & DocumentationMaintenance Managing your Metric Insights InstanceWhitelist needed to Deploy or Upgrade Metric Insights - CentOS

Whitelist needed to Deploy or Upgrade Metric Insights - CentOS

Whether you host Metric Insights on VMware or install a CentOS version on bare metal, you will need access to various servers to update Metric Insights.

This applies to CentOS linux. This does not apply to Metric Insights hosted in Amazon EC2, running on Debian linux.

1. Deploy Metric Insights

To deploy a new version of Metric Insights you will need access some Metric Insights files that are pulled from Amazon S3, so you will need access to S3. (port 443)

2. Yum repositories

From time to time, it may also be necessary to update the basic components of the VM, e.g., Linux, Apache, etc. In these cases, the VM will need access to appropriate yum repositories. If you maintain your own repositories behind your firewall, you can add your own repo config file to the /etc/yum.repos.d directory. Otherwise, you might need to enable the VM to connect to one of the following external repositories:

3. Options

1) For all on-premise installs (vmware + bare-metal), you will need to access Amazon S3 (port 443)

2) For on-premise bare-metal installs, you will need ssh / https access to (or

3) For all on-premise installs, you will need https access to the official centos (or redhat) yum package repository for OS updates. This external access can be via a proxy server, or by external firewall rules for the MI server.  

If external access to the official repositories are not available, you will need an internal package repository for Redhat / CentOS rpms. If an internal package repository is still not available for OS updates, the final method for upgrades is to download a new, updated VMware instance and restore the data from a backup. This backup/restore method is as follows:

a) on current VMware instance, run mi-app-backup

b) download new VMware appliance from Metric Insights

c) start a new VMware instance from new VMware appliance

d) on new VMware instance, run mi-app-restore --convert <backup_location>

Here, <backup_location> can be a local file, remote file, s3 file, or location on an ftp server. See mi-app-restore -h and mi-app-backup -h for more info.

4. Check list

1) For install on-premise hardware (not VMWare image), access to adam

2) Access for OS package updates

 a) How to test if access is there

 b) Options for MI upgrades (to support MI upgrades)

     i) Open internet access

     ii) Proxy server

     iii) Internal package repository for OS upgrades

     vi) mi-deploy with upgrade in-place option (when ready)


Add your comment

E-Mail me when someone replies to this comment