1 CORTX VM on VirtualBox

Justin Woo edited this page 2021-03-08 09:15:37 -08:00

Unescape Escape

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

The following was done with VirtualBox 6.1 

File->Import Appliance
Navigate to OVA & import

Start VM
It will hang:

After several minutes:
 

Boot into rescue mode:

Login as cortx/opensource!

Sudo to root

Based on info found here, do the following to 
 

Wait approx. 30 seconds

Reboot (default boot option)
 

Network names won’t be what CORTX expects & configures:

CORTX seems to want the ens* names, so force udev to rename by getting hw addr from ifconfig and adding to ifcfg* files:
Get hw addresses for existing interfaces:

root@localhost ~

08:00:27:11:86:fb

root@localhost ~

08:00:27:c7:22:cb

root@localhost ~

08:00:27:cf:53:4e

Update network config scripts in /etc/init.d/network/scripts to add HWADDR lines to map the above to preferred names during udev rename_devices phase:

root@localhost ~

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=ens192
UUID=30b25b3b-7074-4b9e-b734-e0bae7788c15
DEVICE=ens192
ONBOOT=yes
ZONE=public
HWADDR=08:00:27:11:86:fb

(do the same with other two with corresponding MACs)

Reboot
Confirm interface names are all ens*

root@localhost ~

Configured devices:
lo ens192 ens224 ens256
Currently active devices:
lo ens192 ens224 ens256

set hostname

root@localhost ~

Bootstrap

root@localhost ~

Confirm all svcs running

root@localhost ~

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
   inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
   link/ether 08:00:27:11:86:fb brd ff:ff:ff:ff:ff:ff
   inet 192.168.86.35/24 brd 192.168.86.255 scope global noprefixroute dynamic ens192
      valid_lft 85919sec preferred_lft 85919sec
   inet6 fe80::e29:d50f:fa2:42de/64 scope link noprefixroute
      valid_lft forever preferred_lft forever
3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
   link/ether 08:00:27:c7:22:cb brd ff:ff:ff:ff:ff:ff
   inet 192.168.86.34/24 brd 192.168.86.255 scope global dynamic ens224
      valid_lft 85923sec preferred_lft 85923sec
   inet6 fe80::a00:27ff:fec7:22cb/64 scope link
      valid_lft forever preferred_lft forever
4: ens256: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
   link/ether 08:00:27:cf:53:4e brd ff:ff:ff:ff:ff:ff
   inet 192.168.86.36/24 brd 192.168.86.255 scope global dynamic ens256
      valid_lft 85925sec preferred_lft 85925sec
   inet6 fe80::a00:27ff:fecf:534e/64 scope link
      valid_lft forever preferred_lft forever

root@localhost ~

…
***** S3: SANITY TEST SUCCESSFULLY COMPLETED *****

In browser, go to https://192.168.86.35:28100/#/preboarding/welcome

follow steps and provide requested info

NOTE
S3 creds don’t have correct s3 url, but using system data IP works fine:
Account name S3 URL Access key Secret key
dolster http://None https://None xxxxxx xxxxx