Trouble installing WebMO on AWS CentOS - Unidentified Cloud Vendor

[dnl]

Hi team,

I have been following this guide: https://www.webmo.net/support/sitcAWS.html, but am getting the error: Unidentified Cloud Vendor! Exiting.

I have read the suggestions found here: https://www.webmo.net/forum/viewtopic.p ... Vendor#p83 but have not been able to resolve the issue.

Here is my SSH terminal output:

Code: Select all

[centos@euawsvdcpcapp01 ~]$ ls
GBDCVPMgtICA01.crt  GBDCVPMgtRCA01.crt         rds-ca-2019-root.pem
GBDCVPMgtICA02.crt  rds-ca-2019-eu-west-1.pem
[centos@euawsvdcpcapp01 ~]$ pwd
/home/centos
[centos@euawsvdcpcapp01 ~]$ whoami
centos
[centos@euawsvdcpcapp01 ~]$ curl -O https://www.webmo.net/cloud/sitc.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 18389  100 18389    0     0  16179      0  0:00:01  0:00:01 --:--:-- 16187
[centos@euawsvdcpcapp01 ~]$ ls
GBDCVPMgtICA01.crt  GBDCVPMgtRCA01.crt         rds-ca-2019-root.pem
GBDCVPMgtICA02.crt  rds-ca-2019-eu-west-1.pem  sitc.tar.gz
[centos@euawsvdcpcapp01 ~]$ tar xzf sitc.tar.gz
[centos@euawsvdcpcapp01 ~]$ ls
GBDCVPMgtICA01.crt  GBDCVPMgtRCA01.crt         rds-ca-2019-root.pem  sitc.tar.gz
GBDCVPMgtICA02.crt  rds-ca-2019-eu-west-1.pem  sitc
[centos@euawsvdcpcapp01 ~]$ ./sitc/install

Server In The Cloud version 0.6.03
Copyright (c) 2019, WebMO, LLC, all rights reserved.

This script automates the installation of software from several
third parties. Many of these have licenses that are agreed to
automatically by this script. Indicate your consent by pressing
ENTER, or press CTRL-c to exit.


Sanity check! You have selected to do the following:
 Update the operating system
 Install WebMO for user webmo
 Install mopac7 to /usr/local
Press ENTER to continue, or CTRL-c to exit.


Unidentified Cloud Vendor! Exiting.

At the moment I am just using the default values in install.conf as the instructions don't mention that I need to change.

Thanks in advance,
David

[dnl]

I had to modify the install script to identify the UUID: https://docs.aws.amazon.com/AWSEC2/late ... ances.html

FROM:

Code: Select all

#figure out whose cloud you're on
if [ -e "/sys/hypervisor/uuid" ]; then
        if [ -n "`cat /sys/hypervisor/uuid | grep -i ec2`" ]; then
                export SITC_CLOUD="EC2"
        fi

TO:

Code: Select all

#figure out whose cloud you're on
if [ -e "/sys/devices/virtual/dmi/id/product_uuid" ]; then
        if [ -n "`cat /sys/devices/virtual/dmi/id/product_uuid | grep -i EC2`" ]; then
                export SITC_CLOUD="EC2"
        fi

[polik]

Thanks for your feedback. It's a challenge to ensure that the sitc script works across all vendors (Google, Amazon, Microsoft) and all Linux distributions/versions (CentOS 6/7/8, Amazon linux (= CentOS), Debian 9/10, Ubuntu 16/18).

There is no need to change anything in sitc/install.conf, which sets default values for command line switches. It is the sitc/install script that is experiencing difficulty in determining which cloud vendor (Google, Amazon, Microsoft) you are running on.

Could you please reply with the specific Operating System and Instance Type that you selected in creating your Amazon Web Services (AWS) virtual machine, so that we can reproduce the situation?

Also, are you running the sitc script from the sudo-capable system account that you use to administer the virtual machine, or a different regular system account?

Thanks!

[dnl]

Hi there,

No problem, I appreciate it's not an easy job to accommodate for all distros. Here are the details of my instance:

AWS
Operating System: CentOS Linux 7 (Core)
Kernel: Linux 3.10.0-1062.18.1.el7.x86_64

The above change allows the install script to continue.

I was running all of the recommended commands as root.

Thanks in advance,
David

[campbell]

Thanks for the link about identifying EC2 Linux instances and the proposed sitc patch.

The existing code looks at the hypervisor for an indication that the instance is an EC2 virtual machine. But in some instances, one needs to look at the desktop management interface (dvi), which your patch accomplishes. So for portable code, one needs to look in both locations:

Code: Select all

#figure out whose cloud you're on
if [ -e "/sys/hypervisor/uuid" ]; then
        if [ -n "`cat /sys/hypervisor/uuid | grep -i ec2`" ]; then
                export SITC_CLOUD="EC2"
        fi
elif [ -e "/sys/devices/virtual/dmi/id/product_uuid" ]; then
        if [ -n "`cat /sys/devices/virtual/dmi/id/product_uuid | grep -i EC2`" ]; then
                export SITC_CLOUD="EC2"
        fi

We'll incorporate this in the next version of sitc!

[polik]

This issue stems from the CentOS linux 7 (Core) AMI not being one of the Quickstart AMI's distributed by Amazon.

The Quickstart AMI's are a set of Amazon Machine Images that have been created and vetted by Amazon to run in their cloud. They include:

• Amazon Linux 1 (based on CentOS 6)
• Amazon Linux 2 (based on CentOS 7)
• Ubuntu 16/18/20

The sitc script supports these common Quickstart AMI's. We will make this more clear in the AWS sitc documentation.

In contrast, the CentOS Linux 7 (Core) AMI disk image is one of the many disk images found on the AMI Marketplace, rather than in the Quickstart AMI collection. Although the sitc script strives to be as portable as possible, it's unlikely to support every distribution found on the AMI Marketplace.

We will be incorporating the above patch into sitc, so that CentOS Linux 7 (Core) disk image is supported in the future. But for new users deciding upon an AMI distribution to use with sitc, we recommend using a Quickstart AMI. In particular, CentOS 7 users should choose Amazon Linux 2.