Merge pull request #64 from IBM/v5211-fixes

Storage Scale 5.2.1.1 support plus multiple fixes for open issues.

README.md

@@ -18,7 +18,7 @@ The creation of the Storage Scale cluster requires the Storage Scale
 self-extracting installation package. The developer edition can be downloaded
 from the [Storage Scale home page](https://www.ibm.com/products/storage-scale).
 
-Download the `Storage_Scale_Developer-5.2.1.0-x86_64-Linux-install` package and
+Download the `Storage_Scale_Developer-5.2.1.1-x86_64-Linux-install` package and
 save it to directory `StorageScaleVagrant/software` on the `host`.
 
 Please note that in case the Storage Scale Developer version you downloaded is
@@ -53,7 +53,7 @@ preferred provider to install and configure a virtual machine.
 
 Please note that for AWS you might want to prefer the new "Cloudkit" Storage
 Scale capability that is also available with the Storage Scale Developer Edition.
-For more details about Cloudkit, please refer to the [documentation](https://www.ibm.com/docs/en/storage-scale/5.1.9?topic=reference-cloudkit).
+For more details about Cloudkit, please refer to the [documentation](https://www.ibm.com/docs/en/storage-scale/5.2.1?topic=reference-cloudkit).
 
 Once the virtual environment is provided, Storage Scale Vagrant uses the same
 scripts to install and configure Storage Scale. Storage Scale Vagrant executes
@@ -72,6 +72,13 @@ Storage Scale Vagrant uses the Storage Scale CLI and the Storage Scale REST API
 to install and configure Storage Scale. In addition it configures the Storage
 Scale GUI to allow interested users to explore its capabilities.
 
+[!IMPORTANT]
+As per default setting, the Storage Scale GUI is mapped to port 8888 on the host.
+That might conflict with other software using that port (see issue #54).
+You can configure the port yourself [here](https://github.com/IBM/StorageScaleVagrant/blob/main/virtualbox/Vagrantfile#L58)
+for VirtualBox and [here](https://github.com/IBM/StorageScaleVagrant/blob/main/libvirt/Vagrantfile#L62) for libvirt.
+
+
 ### Storage Scale CLI
 
 Storage Scale Vagrant configures the shell `$PATH` variable and the sudo
@@ -160,6 +167,8 @@ To connect to the Storage Scale GUI, enter `https://localhost:8888` (AWS:
 `https://<AWS Public IP>`) in a browser. The GUI is configured with a
 self-signed certificate. The login screen shows, after accepting the
 certificate. The user `admin` has the default password `admin001`.
+To be able to use the GUI early in the installation process, a user
+`performance` with the default password `monitor` is created.
 
 ![](/doc/gui/gui_login.png)
 

aws/README.md

@@ -84,8 +84,8 @@ StorageScaleVagrant\aws\prep-ami>vagrant ssh
 [centos@ip-172-31-27-143 ~]$ ls -l software/
 total 931024
 -rw-r--r--. 1 centos centos        134 31. Mai 2023  README
--rw-r--r--. 1 centos centos 1162977306 15. Aug 13:24 Storage_Scale_Developer-5.2.1.0-x86_64-Linux-install
--rw-r--r--. 1 centos centos         87 15. Aug 13:24 Storage_Scale_Developer-5.2.1.0-x86_64-Linux-install.md5
+-rw-r--r--. 1 centos centos 1161789999 23. Sep 15:18 Storage_Scale_Developer-5.2.1.1-x86_64-Linux-install
+-rw-r--r--. 1 centos centos         87 23. Sep 15:18 Storage_Scale_Developer-5.2.1.1-x86_64-Linux-install.md5
 
 [centos@ip-172-31-27-143 ~]$ exit
 logout

libvirt/prep-box/Vagrantfile

@@ -13,11 +13,14 @@ steps are to create a Vagrant box file and to destroy the virtual machine.
 
 To create a Vagrant box file from virtual machine execute:
 vagrant package StorageScale_base --output StorageScale_base.box
-vagrant box add StorageScale_base.box --name StorageScale_base
+vagrant box add StorageScale_base.box --name StorageScale_base --force
 
 To destroy the virtual machine execute:
 vagrant destroy
 
+Finally cleanup the intermediate file:
+rm StorageScale_base.box
+
 --------------------------------------------------------------------------
 EOT
 

setup/demo/script-01.sh

@@ -32,6 +32,10 @@ mount | grep /ibm/
 echo "===> Show content of all Storage Scale filesystems"
 find /ibm/
 
+# Create the GUI Admin
+echo "==> Create the GUI admin user"
+sudo /usr/lpp/mmfs/gui/cli/mkuser admin -g SecurityAdmin -p admin001
+
 # Show all Storage Scale filesystems using the REST API
 echo "==> Show all Storage Scale filesystems using the REST API"
 curl -k -s -S -X GET --header 'Accept: application/json' -u admin:admin001 'https://localhost/scalemgmt/v2/filesystems/'

setup/demo/script-05.sh

@@ -55,8 +55,9 @@ sudo mkdir /ibm/fs1/pets/hamsters
 # Note: The algorithm creates files of varying sizes so that quota reports
 #       have varying sizes
 echo "===> Create some files in each user directory"
+set +x
 inc=3
-for dir in /ibm/fs1/*/* ; do
+for dir in /ibm/fs1/{pets,flowers}/* ; do
   inc=$(($inc+1))
   num_files=$((10+$inc))
   cur_file=$((0))
@@ -66,6 +67,7 @@ for dir in /ibm/fs1/*/* ; do
     sudo dd if=/dev/zero of=$dir/file$cur_file bs=100K count=$num_blocks 2>/dev/null
   done
 done
+set -x
 
 # Set owner of Storage Scale Filesets
 echo "===> Set owner of Storage Scale Filesets"

setup/demo/script-08.sh

@@ -107,6 +107,9 @@ sudo chown -R vagrant:vagrant aws-cert
 sudo mmces service stop s3
 sudo mmces service start s3
 
+# Wait some time for the service to get online. 10 seconds seem to be fine (issue #59)
+sleep 10
+
 # Test S3 interface
 echo "===> Test S3 API operations"
 AWS_CA_BUNDLE=/home/vagrant/aws-cert/tls.crt aws --profile s3user1 --endpoint https://cesip.example.com:6443 s3 mb s3://testbucket

setup/demo/script-80.sh

@@ -18,7 +18,6 @@ set -e
 
 # Authorize the default admin to manage ACLs
 echo "===> Authorize the default GUI admin to manage ACLs"
-sudo /usr/lpp/mmfs/gui/cli/mkuser admin -g SecurityAdmin -p admin001
 sudo /usr/lpp/mmfs/gui/cli/chuser admin -a DataAccess
 
 

setup/demo/script-81.sh

@@ -26,6 +26,7 @@ sudo mmlinkfileset fs1 exceed_warning_threshold -J /ibm/fs1/examples/exceed_warn
 sudo mmlinkfileset fs1 exceed_error_threshold   -J /ibm/fs1/examples/exceed_error_threshold
 
 # Create files to exceed warning threshold
+set +x
 echo "===> Create files to exceed warning threshold"
 for i in {1..850}; do
   sudo touch /ibm/fs1/examples/exceed_warning_threshold/file$i
@@ -36,7 +37,7 @@ echo "===> Create files to exceed error threshold"
 for i in {1..950}; do
   sudo touch /ibm/fs1/examples/exceed_error_threshold/file$i
 done
-
+set -x
 
 # Exit successfully
 echo "===> Script completed successfully!"

setup/install/common-preamble.sh

@@ -4,7 +4,7 @@ usage(){
   echo "  AWS"
   echo "  VirtualBox"
   echo "  libvirt"
-  echo "<spectrumscale-version> is the full version number like 5.2.1.0"
+  echo "<spectrumscale-version> is the full version number like 5.2.1.1"
 }
 
 # Improve readability of output

setup/install/script-05.sh

@@ -52,6 +52,9 @@ sudo systemctl status --no-pager pmsensors
 echo "==> Initialize Storage Scale GUI"
 sudo /usr/lpp/mmfs/gui/cli/initgui
 
+# Issue #58: Immediately create a GUI user
+echo "==> Create GUI user for monitoring purposes"
+sudo /usr/lpp/mmfs/gui/cli/mkuser performance -p monitor
 
 # Exit successfully
 echo "===> Script completed successfully!"

shared/Vagrantfile.common

@@ -6,7 +6,7 @@
 # This file should be included by the Vagrantfile of each cluster configuration
 #
 
-$StorageScale_version = "5.2.1.0"
+$StorageScale_version = "5.2.1.1"
 
 Vagrant.configure('2') do |config|
 

virtualbox/prep-box/Vagrantfile

@@ -13,10 +13,15 @@ steps are to create a Vagrant box file and to destroy the virtual machine.
 
 To create a Vagrant box file from virtual machine execute:
 vagrant package StorageScale_base --output StorageScale_base.box
+vagrant box add StorageScale_base.box --name StorageScale_base --force
 
 To destroy the virtual machine execute:
 vagrant destroy
 
+Finally cleanup the intermediate file:
+Linux or MacOS: rm StorageScale_base.box
+Windows: del StorageScale_base.box
+
 --------------------------------------------------------------------------
 EOT