Updated Spectrum Scale version to <IP_ADDRESS>

Changes

Updated Spectrum Scale version to <IP_ADDRESS>
Added python3 as new pre-required package for the installer
Increased the VirtualBox CPU cores from 1 to 2

Installation log
$ vagrant up
Bringing machine 'm1' up with 'virtualbox' provider...
==> m1: Importing base box 'SpectrumScale_base'...
==> m1: Matching MAC address for NAT networking...
==> m1: Setting the name of the VM: virtualbox_m1_1605091423985_210
==> m1: Clearing any previously set network interfaces...
==> m1: Preparing network interfaces based on configuration...
    m1: Adapter 1: nat
    m1: Adapter 2: hostonly
    m1: Adapter 3: hostonly
==> m1: Forwarding ports...
    m1: 443 (guest) => 8888 (host) (adapter 1)
    m1: 22 (guest) => 2222 (host) (adapter 1)
==> m1: Running 'pre-boot' VM customizations...
==> m1: Booting VM...
==> m1: Waiting for machine to boot. This may take a few minutes...
    m1: SSH address: <IP_ADDRESS>:2222
    m1: SSH username: vagrant
    m1: SSH auth method: private key
    m1: Warning: Connection reset. Retrying...
    m1: Warning: Connection aborted. Retrying...
    m1: Warning: Remote connection disconnect. Retrying...
    m1: Warning: Connection reset. Retrying...
    m1: Warning: Connection aborted. Retrying...
    m1: Warning: Connection reset. Retrying...
    m1: Warning: Connection aborted. Retrying...
    m1:
    m1: Vagrant insecure key detected. Vagrant will automatically replace
    m1: this with a newly generated keypair for better security.
    m1:
    m1: Inserting generated public key within guest...
    m1: Removing insecure key from the guest if it's present...
    m1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> m1: Machine booted and ready!
==> m1: Checking for guest additions in VM...
    m1: No guest additions were detected on the base box for this VM! Guest
    m1: additions are required for forwarded ports, shared folders, host only
    m1: networking, and more. If SSH fails on this machine, please install
    m1: the guest additions and repackage the box to continue.
    m1:
    m1: This is not an error message; everything may continue to work properly,
    m1: in which case you may ignore this message.
==> m1: Setting hostname...
==> m1: Configuring and enabling network interfaces...
==> m1: Rsyncing folder: /cygdrive/d/SpectrumScaleVagrant/setup/ => /vagrant
==> m1: Rsyncing folder: /cygdrive/d/SpectrumScaleVagrant/software/ => /software
==> m1: Running provisioner: Configure permissions for shell scripts (shell)...
    m1: Running: script: Configure permissions for shell scripts
==> m1: Running provisioner: Configure /etc/hosts for VirtualBox (shell)...
    m1: Running: script: Configure /etc/hosts for VirtualBox
==> m1: Running provisioner: Generate ssh keys for user root (shell)...
    m1: Running: script: Generate ssh keys for user root
==> m1: Running provisioner: Configure ssh host keys (shell)...
    m1: Running: script: Configure ssh host keys
    m1: # m1:22 SSH-2.0-OpenSSH_7.4
    m1: # m1:22 SSH-2.0-OpenSSH_7.4
    m1: # m1:22 SSH-2.0-OpenSSH_7.4
==> m1: Running provisioner: Get fingerprint for management IP address (shell)...
    m1: Running: script: Get fingerprint for management IP address
==> m1: Running provisioner: Add /usr/lpp/mmfs/bin to $PATH (shell)...
    m1: Running: script: Add /usr/lpp/mmfs/bin to $PATH
==> m1: Running provisioner: Add /usr/lpp/mmfs/bin to sudo secure_path (shell)...
    m1: Running: script: Add /usr/lpp/mmfs/bin to sudo secure_path
==> m1: Running provisioner: Install and configure single node Spectrum Scale cluster (shell)...
    m1: Running: script: Install and configure single node Spectrum Scale cluster
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script.sh
    m1: ===> Perform all steps to provision a Spectrum Scale cluster
    m1: ===>
    m1: =========================================================================================
    m1: + set -e
    m1: + '[' 1 -ne 1 ']'
    m1: + case $1 in
    m1: + PROVIDER=VirtualBox
    m1: + /vagrant/install/script-01.sh VirtualBox
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script-01.sh
    m1: ===> Check that Spectrum Scale self-extracting install package exists
    m1: ===>
    m1: =========================================================================================
    m1: + set -e
    m1: + install=/software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install
    m1: ===> Check for Spectrum Scale self-extracting installation package
    m1: + echo '===> Check for Spectrum Scale self-extracting installation package'
    m1: + '[' '!' -f /software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install ']'
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/install/script-02.sh VirtualBox
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script-02.sh
    m1: ===> Extract Spectrum Scale RPMs
    m1: ===>
    m1: =========================================================================================
    m1: + set -e
    m1: + install=/software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install
    m1: ===> Check for Spectrum Scale directrory
    m1: + echo '===> Check for Spectrum Scale directrory'
    m1: + '[' -d /usr/lpp/mmfs ']'
    m1: + chmod 555 /software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install
    m1: ===> Extract Spectrum Scale PRMs
    m1: + echo '===> Extract Spectrum Scale PRMs'
    m1: + sudo /software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install --silent
    m1:
    m1: Extracting License Acceptance Process Tool to /usr/lpp/mmfs/<IP_ADDRESS> ...
    m1: tail -n +641 /software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install | tar -C /usr/lpp/mmfs/<IP_ADDRESS> -xvz --exclude=installer --exclude=*_rpms --exclude=*_debs --exclude=*rpm  --exclude=*tgz --exclude=*deb --exclude=*tools* 1> /dev/null
    m1:
    m1: Installing JRE ...
    m1:
    m1: If directory /usr/lpp/mmfs/<IP_ADDRESS> has been created or was previously created during another extraction,
    m1: .rpm, .deb, and repository related files in it (if there were) will be removed to avoid conflicts with the ones being extracted.
    m1: tail -n +641 /software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install | tar -C /usr/lpp/mmfs/<IP_ADDRESS> --wildcards -xvz  ibm-java*tgz 1> /dev/null
    m1: tar -C /usr/lpp/mmfs/<IP_ADDRESS>/ -xzf /usr/lpp/mmfs/<IP_ADDRESS>/ibm-java*tgz
    m1:
    m1: Invoking License Acceptance Process Tool ...
    m1: /usr/lpp/mmfs/<IP_ADDRESS>/ibm-java-x86_64-80/jre/bin/java -cp /usr/lpp/mmfs/<IP_ADDRESS>/LAP_HOME/LAPApp.jar com.ibm.lex.lapapp.LAP -l /usr/lpp/mmfs/<IP_ADDRESS>/LA_HOME -m /usr/lpp/mmfs/<IP_ADDRESS> -s /usr/lpp/mmfs/<IP_ADDRESS> -t 5
    m1:
    m1: License Agreement Terms accepted.
    m1: Extracting Product RPMs to /usr/lpp/mmfs/<IP_ADDRESS> ...
    m1: tail -n +641 /software/Spectrum_Scale_Data_Management-<IP_ADDRESS>-x86_64-Linux-install | tar -C /usr/lpp/mmfs/<IP_ADDRESS> --wildcards -xvz  Public_Keys installer hdfs_debs/ubuntu/hdfs_3.1.0.x hdfs_debs/ubuntu/hdfs_3.1.1.x hdfs_rpms/rhel7/hdfs_3.1.0.x hdfs_rpms/rhel7/hdfs_3.1.1.x ganesha_debs/ubuntu ganesha_rpms/rhel7 ganesha_rpms/rhel8 ganesha_rpms/sles15 gpfs_debs/ubuntu gpfs_rpms/rhel object_rpms/rhel8 smb_debs/ubuntu smb_rpms/rhel7 smb_rpms/rhel8 smb_rpms/sles15 tools/repo zimon_debs/ubuntu zimon_rpms/rhel7 zimon_rpms/rhel8 zimon_rpms/sles15 gpfs_debs gpfs_rpms manifest 1> /dev/null
    m1:    - Public_Keys
    m1:    - installer
    m1:    - hdfs_debs/ubuntu/hdfs_3.1.0.x
    m1:    - hdfs_debs/ubuntu/hdfs_3.1.1.x
    m1:    - hdfs_rpms/rhel7/hdfs_3.1.0.x
    m1:    - hdfs_rpms/rhel7/hdfs_3.1.1.x
    m1:    - ganesha_debs/ubuntu
    m1:    - ganesha_rpms/rhel7
    m1:    - ganesha_rpms/rhel8
    m1:    - ganesha_rpms/sles15
    m1:    - gpfs_debs/ubuntu
    m1:    - gpfs_rpms/rhel
    m1:    - object_rpms/rhel8
    m1:    - smb_debs/ubuntu
    m1:    - smb_rpms/rhel7
    m1:    - smb_rpms/rhel8
    m1:    - smb_rpms/sles15
    m1:    - tools/repo
    m1:    - zimon_debs/ubuntu
    m1:    - zimon_rpms/rhel7
    m1:    - zimon_rpms/rhel8
    m1:    - zimon_rpms/sles15
    m1:    - gpfs_debs
    m1:    - gpfs_rpms
    m1:    - manifest
    m1: Removing License Acceptance Process Tool from /usr/lpp/mmfs/<IP_ADDRESS> ...
    m1: rm -rf  /usr/lpp/mmfs/<IP_ADDRESS>/LAP_HOME /usr/lpp/mmfs/<IP_ADDRESS>/LA_HOME
    m1:
    m1: Removing JRE from /usr/lpp/mmfs/<IP_ADDRESS> ...
    m1: rm -rf /usr/lpp/mmfs/<IP_ADDRESS>/ibm-java*tgz
    m1: ==================================================================
    m1: Product packages successfully extracted to /usr/lpp/mmfs/<IP_ADDRESS>
    m1:
    m1:    Cluster installation and protocol deployment
    m1:       To install a cluster or deploy protocols with the Spectrum Scale Install Toolkit:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale -h
    m1:       To install a cluster manually:  Use the gpfs packages located within /usr/lpp/mmfs/<IP_ADDRESS>/gpfs_<rpms/debs>
    m1:
    m1:       To upgrade an existing cluster using the Spectrum Scale Install Toolkit:
    m1:       1) Copy your old clusterdefinition.txt file to the new /usr/lpp/mmfs/<IP_ADDRESS>/installer/configuration/ location
    m1:       2) Review and update the config:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale config update
    m1:       3) (Optional) Update the toolkit to reflect the current cluster config:
    m1:          /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale config populate -N <node>
    m1:       4) Run the upgrade:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale upgrade -h
    m1:
    m1:       To add nodes to an existing cluster using the Spectrum Scale Install Toolkit:
    m1:       1) Add nodes to the clusterdefinition.txt file:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale node add -h
    m1:       2) Install GPFS on the new nodes:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale install -h
    m1:       3) Deploy protocols on the new nodes:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale deploy -h
    m1:
    m1:       To add NSDs or file systems to an existing cluster using the Spectrum Scale Install Toolkit:
    m1:       1) Add nsds and/or filesystems with:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale nsd add -h
    m1:       2) Install the NSDs:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale install -h
    m1:       3) Deploy the new file system:  /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale deploy -h
    m1:
    m1:       To update the toolkit to reflect the current cluster config examples:
    m1:          /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale config populate -N <node>
    m1:       1) Manual updates outside of the install toolkit
    m1:       2) Sync the current cluster state to the install toolkit prior to upgrade
    m1:       3) Switching from a manually managed cluster to the install toolkit
    m1:
    m1: ==================================================================================
    m1: To get up and running quickly, consult the IBM Spectrum Scale Protocols Quick Overview:
    m1: https://www.ibm.com/support/knowledgecenter/STXKQY_5.1.0/com.ibm.spectrum.scale.v5r10.doc/pdf/scale_povr.pdf
    m1: ===================================================================================
    m1: + echo '===> Script completed successfully!'
    m1: ===> Script completed successfully!
    m1: + exit 0
    m1: + /vagrant/install/script-03.sh VirtualBox
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script-03.sh
    m1: ===> Setup management node (m1) as Spectrum Scale Install Node
    m1: ===>
    m1: =========================================================================================
    m1: + set -e
    m1: + '[' 1 -ne 1 ']'
    m1: + case $1 in
    m1: + PROVIDER=VirtualBox
    m1: + '[' VirtualBox = AWS ']'
    m1: + '[' VirtualBox = VirtualBox ']'
    m1: + INSTALL_NODE=<IP_ADDRESS>
    m1: ===> Setup management node (m1) as Spectrum Scale Install Node
    m1: + echo '===> Setup management node (m1) as Spectrum Scale Install Node'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale setup -s <IP_ADDRESS>
    m1: [ INFO  ] Installing prerequisites for install node
    m1: [ INFO  ] Chef successfully installed and configured
    m1: [ INFO  ] Your control node has been configured to use the IP <IP_ADDRESS> to communicate with other nodes.
    m1: [ INFO  ] Port 8889 will be used for chef communication.
    m1: [ INFO  ] Port 10080 will be used for package distribution.
    m1: [ INFO  ] Install Toolkit setup type is set to Spectrum Scale (default). If an ESS is in the cluster, run this command to set ESS mode: ./spectrumscale setup -s server_ip -st ess
    m1: [ INFO  ] SUCCESS
    m1: [ INFO  ] Tip : Designate protocol, nsd and admin nodes in your environment to use during install:./spectrumscale -v node add <node> -p  -a -n
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale node list
    m1: [ INFO  ] List of nodes in current configuration:
    m1: [ INFO  ] [Installer Node]
    m1: [ INFO  ] <IP_ADDRESS>
    m1: [ INFO  ]
    m1: [ INFO  ] [Cluster Details]
    m1: [ INFO  ] No cluster name configured
    m1: [ INFO  ] Setup Type: Spectrum Scale
    m1: [ INFO  ]
    m1: [ INFO  ] [Extended Features]
    m1: [ INFO  ] File Audit logging     : Disabled
    m1: [ INFO  ] Watch folder           : Disabled
    m1: [ INFO  ] Management GUI         : Disabled
    m1: [ INFO  ] Performance Monitoring : Enabled
    m1: [ INFO  ] Callhome               : Enabled
    m1: [ INFO  ]
    m1: [ INFO  ] No nodes configured. Use 'spectrumscale node add' to add nodes.
    m1: [ INFO  ] If a cluster already exists use 'spectrumscale config populate -N node_in_cluster' to sync toolkit with existing cluster.
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/install/script-04.sh VirtualBox
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script-04.sh
    m1: ===> Specify Spectrum Scale Cluster
    m1: ===> Target configuration: Single Node Cluster
    m1: ===>
    m1: =========================================================================================
    m1: + set -e
    m1: + '[' 1 -ne 1 ']'
    m1: + case $1 in
    m1: + PROVIDER=VirtualBox
    m1: ===> Specify cluster name
    m1: + echo '===> Specify cluster name'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale config gpfs -c demo
    m1: [ INFO  ] Setting GPFS cluster name to demo
    m1: ===> Specify to disable call home
    m1: + echo '===> Specify to disable call home'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale callhome disable
    m1: [ INFO  ] Disabling the callhome.
    m1: [ INFO  ] Configuration updated.
    m1: ===> Specify nodes and their roles
    m1: + echo '===> Specify nodes and their roles'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale node add -a -g -q -m -n m1
    m1: [ INFO  ] Adding node m1.example.com as a GPFS node.
    m1: [ INFO  ] Adding node m1.example.com as a quorum node.
    m1: [ INFO  ] Adding node m1.example.com as a manager node.
    m1: [ INFO  ] Adding node m1.example.com as an NSD server.
    m1: [ INFO  ] Configuration updated.
    m1: [ INFO  ] Tip :If all node designations are complete, add NSDs to your cluster definition and define required filessytems:./spectrumscale nsd add <device> -p <primary node> -s <secondary node> -fs <file system>
    m1: [ INFO  ] Setting m1.example.com as an admin node.
    m1: [ INFO  ] Configuration updated.
    m1: [ INFO  ] Tip : Designate protocol or nsd nodes in your environment to use during install:./spectrumscale node add <node> -p -n
    m1: [ INFO  ] Setting m1.example.com as a GUI server.
    m1: ===> Show cluster specification
    m1: + echo '===> Show cluster specification'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale node list
    m1: [ INFO  ] List of nodes in current configuration:
    m1: [ INFO  ] [Installer Node]
    m1: [ INFO  ] <IP_ADDRESS>
    m1: [ INFO  ]
    m1: [ INFO  ] [Cluster Details]
    m1: [ INFO  ] Name: demo
    m1: [ INFO  ] Setup Type: Spectrum Scale
    m1: [ INFO  ]
    m1: [ INFO  ] [Extended Features]
    m1: [ INFO  ] File Audit logging     : Disabled
    m1: [ INFO  ] Watch folder           : Disabled
    m1: [ INFO  ] Management GUI         : Enabled
    m1: [ INFO  ] Performance Monitoring : Enabled
    m1: [ INFO  ] Callhome               : Disabled
    m1: [ INFO  ]
    m1: [ INFO  ] GPFS           Admin  Quorum  Manager   NSD   Protocol   GUI     OS   Arch
    m1: [ INFO  ] Node            Node   Node     Node   Server   Node    Server
    m1: [ INFO  ] m1.example.com   X       X       X       X                X    rhel7  x86_64
    m1: [ INFO  ]
    m1: [ INFO  ] [Export IP address]
    m1: [ INFO  ] No export IP addresses configured
    m1: + '[' VirtualBox = AWS ']'
    m1: + '[' VirtualBox = VirtualBox ']'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale nsd add -p m1.example.com -fs fs1 /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf
    m1: [ INFO  ] Connecting to m1.example.com to check devices and expand wildcards.
    m1: [ INFO  ] Looking up details of /dev/sdb.
    m1: [ INFO  ] The installer will create the new file system fs1 if it does not exist.
    m1: [ INFO  ] Adding NSD None on m1.example.com using device /dev/sdb.
    m1: [ INFO  ] Looking up details of /dev/sdc.
    m1: [ INFO  ] Adding NSD None on m1.example.com using device /dev/sdc.
    m1: [ INFO  ] Looking up details of /dev/sdd.
    m1: [ INFO  ] Adding NSD None on m1.example.com using device /dev/sdd.
    m1: [ INFO  ] Looking up details of /dev/sde.
    m1: [ INFO  ] Adding NSD None on m1.example.com using device /dev/sde.
    m1: [ INFO  ] Looking up details of /dev/sdf.
    m1: [ INFO  ] Adding NSD None on m1.example.com using device /dev/sdf.
    m1: [ INFO  ] Configuration updated
    m1: [ INFO  ] Tip : If all node designations and any required protocol configurations are complete, proceed to check the installation configuration: ./spectrumscale install --precheck
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale nsd add -p m1.example.com /dev/sdg /dev/sdh
    m1: [ INFO  ] Connecting to m1.example.com to check devices and expand wildcards.
    m1: [ INFO  ] Looking up details of /dev/sdg.
    m1: [ INFO  ] No filesystem has been specified for this NSD. The installer may create a default filesystem to assign this NSD if there is no filesystem specified in the cluster. For more information, see 'Creating file systems' under 'Defining configuration options for the spectrumscale installation toolkit'in IBM Spectrum Scale documentation on Knowledge Center.
    m1: [ INFO  ] Adding NSD None on m1.example.com using device /dev/sdg.
    m1: [ INFO  ] Looking up details of /dev/sdh.
    m1: [ INFO  ] No filesystem has been specified for this NSD. The installer may create a default filesystem to assign this NSD if there is no filesystem specified in the cluster. For more information, see 'Creating file systems' under 'Defining configuration options for the spectrumscale installation toolkit'in IBM Spectrum Scale documentation on Knowledge Center.
    m1: [ INFO  ] Adding NSD None on m1.example.com using device /dev/sdh.
    m1: [ INFO  ] Configuration updated
    m1: [ INFO  ] Tip : If all node designations and any required protocol configurations are complete, proceed to check the installation configuration: ./spectrumscale install --precheck
    m1: ===> Show NSD specification
    m1: + echo '===> Show NSD specification'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale nsd list
    m1: [ INFO  ] Name FS      Size(GB) Usage   FG Pool    Device   Servers
    m1: [ INFO  ] nsd1 fs1     2.0      Default 1  Default /dev/sdb [m1.example.com]
    m1: [ INFO  ] nsd2 fs1     2.0      Default 1  Default /dev/sdc [m1.example.com]
    m1: [ INFO  ] nsd3 fs1     2.0      Default 1  Default /dev/sdd [m1.example.com]
    m1: [ INFO  ] nsd4 fs1     2.0      Default 1  Default /dev/sde [m1.example.com]
    m1: [ INFO  ] nsd5 fs1     2.0      Default 1  Default /dev/sdf [m1.example.com]
    m1: [ INFO  ] nsd6 Default 10.0     Default 1  Default /dev/sdg [m1.example.com]
    m1: [ INFO  ] nsd7 Default 10.0     Default 1  Default /dev/sdh [m1.example.com]
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/install/script-05.sh VirtualBox
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script-05.sh
    m1: ===> Install Spectrum Scale and create a Spectrum Scale cluster
    m1: ===>
    m1: =========================================================================================
    m1: ===> Install Spectrum Scale and create Spectrum Scale cluster
    m1: + set -e
    m1: + echo '===> Install Spectrum Scale and create Spectrum Scale cluster'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale install
    m1: [ WARN  ] On fresh installations, you might get Chef related errors during installation toolkit deployment. To work around this problem, on fresh installations, before the installation toolkit prechecks, you must create passwordless SSH keys by using the 'ssh-keygen -m PEM' command.
    m1: [ INFO  ] Logging to file: /usr/lpp/mmfs/<IP_ADDRESS>/installer/logs/INSTALL-11-11-2020_10:48:48.log
    m1: [ INFO  ] Validating configuration
    m1: [ WARN  ] NTP is not set to be configured with the install toolkit.See './spectrumscale config ntp -h' to setup.
    m1: [ WARN  ] Only one GUI server specified. The Graphical User Interface will not be highly available.
    m1: [ INFO  ] Install toolkit will not configure file audit logging as it has been disabled.
    m1: [ INFO  ] Checking for knife bootstrap configuration...
    m1: [ INFO  ] Running pre-install checks
    m1: [ INFO  ] Running environment checks
    m1: [ INFO  ] Skipping license validation as no existing GPFS cluster detected.
    m1: [ WARN  ] With 1 node specified functionality will be limited
    m1: [ INFO  ] Checking pre-requisites for portability layer.
    m1: [ INFO  ] GPFS precheck OK
    m1: [ WARN  ] The NSD nsd1 only has one server configured. This may affect the ability to run concurrent maintenance on this cluster.
    m1: [ WARN  ] The NSD nsd2 only has one server configured. This may affect the ability to run concurrent maintenance on this cluster.
    m1: [ WARN  ] The NSD nsd3 only has one server configured. This may affect the ability to run concurrent maintenance on this cluster.
    m1: [ WARN  ] The NSD nsd4 only has one server configured. This may affect the ability to run concurrent maintenance on this cluster.
    m1: [ WARN  ] The NSD nsd5 only has one server configured. This may affect the ability to run concurrent maintenance on this cluster.
    m1: [ WARN  ] The NSD nsd6 only has one server configured. This may affect the ability to run concurrent maintenance on this cluster.
    m1: [ WARN  ] The NSD nsd7 only has one server configured. This may affect the ability to run concurrent maintenance on this cluster.
    m1: [ INFO  ] Running environment checks for Performance Monitoring
    m1: [ INFO  ] Running environment checks for file  Audit logging
    m1: [ INFO  ] Network check from admin node m1.example.com to all other nodes in the cluster passed
    m1: [ WARN  ] Ephemeral port range is not set. Please set valid ephemeral port range using the command ./spectrumscale config gpfs --ephemeral_port_range . You may set the default values as 60000-61000
    m1: [ INFO  ] The install toolkit will not configure call home as it is disabled. To enable call home, use the following CLI command: ./spectrumscale callhome enable
    m1: [ WARN  ] On the nodes: [['m1.example.com with OS RHEL7']], the Portmapper service (rpcbind) is found running and it is advised to disable it or verify with the operating system's administrator.
    m1: [ INFO  ] Preparing nodes for install
    m1: [ INFO  ] Installing Chef (deploy tool)
    m1: [ INFO  ] Installing Chef Client on nodes
    m1: [ INFO  ] Checking for chef-client and installing if required on m1.example.com
    m1: [ INFO  ] Chef Client 13.6.4 is on node m1.example.com
    m1: [ INFO  ] Installing GPFS
    m1: [ INFO  ] GPFS Packages to be installed: gpfs.base, gpfs.gpl, gpfs.msg.en_US, gpfs.docs, and gpfs.gskit
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:20] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:20] IBM SPECTRUM SCALE: Creating core gpfs repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:21] IBM SPECTRUM SCALE: Creating gpfs librdkafka repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:22] IBM SPECTRUM SCALE: Configuring GPFS performance monitoring repository (SS31)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:22] IBM SPECTRUM SCALE: Installing core GPFS packages (SS01)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:41] IBM SPECTRUM SCALE: Installing gpfs afm cos package (SS265)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:45] IBM SPECTRUM SCALE: Installing GPFS license package (SS230)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:47] IBM SPECTRUM SCALE: Installing performance monitoring packages (SS70)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:49:52] IBM SPECTRUM SCALE: Building portability layer (SS02)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:14] IBM SPECTRUM SCALE: Generating node description file for cluster configuration (SS03)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:14] IBM SPECTRUM SCALE: Creating GPFS cluster with default profile (SS04)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:20] IBM SPECTRUM SCALE: Setting client licenses (SS09)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:20] IBM SPECTRUM SCALE: Setting server licenses on manager nodes (SS12)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:22] IBM SPECTRUM SCALE: Setting server licenses on quorum nodes (SS11)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:22] IBM SPECTRUM SCALE: Setting server licenses on server nodes (SS11)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:23] IBM SPECTRUM SCALE: Setting server licenses on protocol nodes (SS11)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:23] IBM SPECTRUM SCALE: Setting server licenses on nsd nodes (SS11)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:23] IBM SPECTRUM SCALE: Setting ephemeral ports for GPFS daemon communication (SS13)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:24] IBM SPECTRUM SCALE: Starting GPFS (SS05)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:50:25] IBM SPECTRUM SCALE: Checking state of GPFS (SS103)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:07] IBM SPECTRUM SCALE: Tearing down core gpfs repository (SS06)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:08] IBM SPECTRUM SCALE: Tearing down GPFS performance monitoring repository (SS35)
    m1: [ INFO  ] Installing NSDs
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:24] IBM SPECTRUM SCALE: Generating stanza file for NSD creation (SS14)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:24] IBM SPECTRUM SCALE: Setting server licenses on NSD servers (SS15)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:25] IBM SPECTRUM SCALE: Creating NSDs (SS16)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:33] IBM SPECTRUM SCALE: Generating stanza file for NSD settings (SS17)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:33] IBM SPECTRUM SCALE: Updating NSD settings (SS18)
    m1: [ INFO  ] Installing Performance Monitoring
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:39] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:39] IBM SPECTRUM SCALE: Creating core gpfs repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:39] IBM SPECTRUM SCALE: Creating gpfs librdkafka repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:40] IBM SPECTRUM SCALE: Configuring GPFS performance monitoring repository (SS31)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:41] IBM SPECTRUM SCALE: Installing performance monitoring packages (SS70)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:48] IBM SPECTRUM SCALE: Tearing down core gpfs repository (SS06)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:49] IBM SPECTRUM SCALE: Tearing down GPFS performance monitoring repository (SS35)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:54] IBM SPECTRUM SCALE: Starting performance monitoring collector (SS73)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:58] IBM SPECTRUM SCALE: Generating configuration for performance monitoring tools (SS83)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:52:58] IBM SPECTRUM SCALE: Modifying sensor configuration for performance monitoring tools (SS85)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:01] IBM SPECTRUM SCALE: Enabling GPFS Disk Capacity sensors (SS90)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:06] IBM SPECTRUM SCALE: Enabling performance monitoring sensors (SS84)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:11] IBM SPECTRUM SCALE: Restarting performance monitoring sensors (SS74)
    m1: [ INFO  ] Installing GUI
    m1: [ INFO  ] GUI packages to be installed: gpfs.gui
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:15] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:15] IBM SPECTRUM SCALE: Creating core gpfs repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:16] IBM SPECTRUM SCALE: Creating gpfs librdkafka repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:17] IBM SPECTRUM SCALE: Configuring GPFS performance monitoring repository (SS31)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:17] IBM SPECTRUM SCALE: Installing GPFS GUI package (SS19)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:53:27] IBM SPECTRUM SCALE: Starting the Graphical User Interface service (SS23)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:54:12] IBM SPECTRUM SCALE: Tearing down core gpfs repository (SS06)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:54:15] IBM SPECTRUM SCALE: Tearing down GPFS performance monitoring repository (SS35)
    m1: [ INFO  ] Installing FILE AUDIT LOGGING
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:54:25] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:54:25] IBM SPECTRUM SCALE: Creating core gpfs repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:54:26] IBM SPECTRUM SCALE: Creating gpfs librdkafka repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:54:27] IBM SPECTRUM SCALE: Configuring GPFS performance monitoring repository (SS31)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:54:30] IBM SPECTRUM SCALE: Installing gpfs librdkafka packages (SS265)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:55:23] IBM SPECTRUM SCALE: Installing gpfs librdkafka packages (SS265)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:55:27] IBM SPECTRUM SCALE: Tearing down core gpfs repository (SS06)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:55:28] IBM SPECTRUM SCALE: Tearing down GPFS performance monitoring repository (SS35)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:55:35] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] Checking for a successful install
    m1: [ INFO  ] Checking state of Chef (deploy tool)
    m1: [ INFO  ] Chef (deploy tool) ACTIVE
    m1: [ INFO  ] Checking state of GPFS
    m1: [ INFO  ] Checking state of GPFS on all nodes
    m1: [ INFO  ] GPFS active on all nodes
    m1: [ INFO  ] GPFS ACTIVE
    m1: [ INFO  ] Checking state of NSDs
    m1: [ INFO  ] NSDs ACTIVE
    m1: [ INFO  ] Checking state of Performance Monitoring
    m1: [ INFO  ] Running Performance Monitoring post-install checks
    m1: [ INFO  ] pmcollector running on all nodes
    m1: [ INFO  ] pmsensors running on all nodes
    m1: [ INFO  ] Performance Monitoring ACTIVE
    m1: [ INFO  ] Checking state of GUI
    m1: [ INFO  ] Running Graphical User Interface  post-install checks
    m1: [ INFO  ] Graphical User Interface running on all GUI servers
    m1: [ INFO  ] Enter one of the following addresses into a web browser to access the Graphical User Interface: <IP_ADDRESS>, <IP_ADDRESS>, m1.example.com
    m1: [ INFO  ] GUI ACTIVE
    m1: [ INFO  ] SUCCESS
    m1: [ INFO  ] All services running
    m1: [ INFO  ] StanzaFile and NodeDesc file for NSD, filesystem, and cluster setup have been saved to /usr/lpp/mmfs folder on node: m1.example.com
    m1: [ INFO  ] Installation successful. 1 GPFS node active in cluster demo.example.com. Completed in 6 minutes 53 seconds.
    m1: [ INFO  ] Tip :If all node designations and any required protocol configurations are complete, proceed to check the deploy configuration:./spectrumscale deploy --precheck
    m1: ===> Show cluster configuration
    m1: + echo '===> Show cluster configuration'
    m1: + sudo mmlscluster
    m1:
    m1: GPFS cluster information
    m1: ========================
    m1:   GPFS cluster name:         demo.example.com
    m1:   GPFS cluster id:<PHONE_NUMBER>496948200
    m1:   GPFS UID domain:           demo.example.com
    m1:   Remote shell command:      /usr/bin/ssh
    m1:   Remote file copy command:  /usr/bin/scp
    m1:   Repository type:           CCR
    m1:
    m1:  Node  Daemon node name  IP address  Admin node name  Designation
    m1: ------------------------------------------------------------------
    m1:    1   m1.example.com    <IP_ADDRESS>   m1.example.com   quorum-manager-perfmon
    m1: ===> Show node state
    m1: + echo '===> Show node state'
    m1: + sudo mmgetstate -a
    m1:
    m1:  Node number  Node name        GPFS state
    m1: -------------------------------------------
    m1:        1      m1               active
    m1: ===> Show cluster health
    m1: + echo '===> Show cluster health'
    m1: + sudo mmhealth cluster show
    m1:
    m1: Component           Total         Failed       Degraded        Healthy          Other
    m1: -------------------------------------------------------------------------------------
    m1: NODE                    1              0              0              0              1
    m1: GPFS                    1              0              0              0              1
    m1: NETWORK                 1              0              0              1              0
    m1: FILESYSTEM              0              0              0              0              0
    m1: DISK                    0              0              0              0              0
    m1: GUI                     1              0              0              1              0
    m1: PERFMON                 1              0              0              1              0
    m1: THRESHOLD               1              0              0              1              0
    m1: ===> Show node health
    m1: + echo '===> Show node health'
    m1: + sudo mmhealth node show
    m1:
    m1: Node name:      m1.example.com
    m1: Node status:    TIPS
    m1: Status Change:  3 min. ago
    m1:
    m1: Component      Status        Status Change     Reasons
    m1: ----------------------------------------------------------------------------------------
    m1: GPFS           TIPS          3 min. ago        callhome_not_enabled, gpfs_pagepool_small
    m1: NETWORK        HEALTHY       4 min. ago        -
    m1: FILESYSTEM     HEALTHY       4 min. ago        -
    m1: DISK           HEALTHY       2 min. ago        -
    m1: GUI            HEALTHY       1 min. ago        -
    m1: PERFMON        HEALTHY       2 min. ago        -
    m1: THRESHOLD      HEALTHY       Now               -
    m1: ===> Show NSDs
    m1: + echo '===> Show NSDs'
    m1: + sudo mmlsnsd
    m1:
    m1:  File system   Disk name       NSD servers
    m1: ------------------------------------------------------------------------------
    m1:  (free disk)   nsd1            m1.example.com
    m1:  (free disk)   nsd2            m1.example.com
    m1:  (free disk)   nsd3            m1.example.com
    m1:  (free disk)   nsd4            m1.example.com
    m1:  (free disk)   nsd5            m1.example.com
    m1:  (free disk)   nsd6            m1.example.com
    m1:  (free disk)   nsd7            m1.example.com
    m1: ===> Show GUI service
    m1: + echo '===> Show GUI service'
    m1: + service gpfsgui.service status
    m1: Redirecting to /bin/systemctl status gpfsgui.service
    m1: ● gpfsgui.service - IBM_Spectrum_Scale Administration GUI
    m1:    Loaded: loaded (/usr/lib/systemd/system/gpfsgui.service; enabled; vendor preset: disabled)
    m1:    Active: active (running) since Wed 2020-11-11 10:54:02 UTC; 1min 40s ago
    m1:  Main PID: 29297 (java)
    m1:    Status: "GSS/GPFS GUI started"
    m1:    Memory: 261.7M (limit: 2.0G)
    m1:    CGroup: /system.slice/gpfsgui.service
    m1:            ├─17767 /bin/bash -c set -m; grep -q -E 'ccrEnabled\s+no' /var/mmfs/gen/mmfs.cfg || sudo mmccr 'fget' '_gui.keystore_settings' '/var/lib/mmfs/gui/keystore_settings.json.e292af06-c217-4081-a309-add4e821b385'
    m1:            └─29297 /usr/lpp/mmfs/java/jre/bin/java -XX:+HeapDumpOnOutOfMemoryError -Dhttps.protocols=TLSv1.2,TLSv1.3 -Djava.library.path=/opt/ibm/wlp/usr/servers/gpfsgui/lib/ -javaagent:/opt/ibm/wlp/bin/tools/ws-javaagent.jar -jar /opt/ibm/wlp/bin/tools/ws-server.jar gpfsgui --clean
    m1:
    m1: Nov 11 10:55:13 m1 sudo[17306]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmccr fget mmsdrfs /var/lib/mmfs/gui/mmsdrfs.cct
    m1: Nov 11 10:55:13 m1 sudo[17311]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/gui/bin-sudo/chown_ccr_fget_file.sh mmsdrfs.cct
    m1: Nov 11 10:55:13 m1 sudo[17344]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmauth show
    m1: Nov 11 10:55:14 m1 sudo[17427]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/gui/bin-sudo/tsstatus.sh
    m1: Nov 11 10:55:14 m1 sudo[17448]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmhealth thresholds list -Y
    m1: Nov 11 10:55:14 m1 sudo[17463]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmcallhome capability list -Y
    m1: Nov 11 10:55:14 m1 sudo[17482]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmhealth node show --verbose -N m1 -Y
    m1: Nov 11 10:55:15 m1 sudo[17522]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmperfmon config show
    m1: Nov 11 10:55:16 m1 sudo[17724]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmhealth node eventlog -N m1 -Y
    m1: Nov 11 10:55:18 m1 sudo[17771]: scalemgmt : TTY=unknown ; PWD=/opt/ibm/wlp ; USER=root ; COMMAND=/usr/lpp/mmfs/bin/mmccr fget _gui.keystore_settings /var/lib/mmfs/gui/keystore_settings.json.e292af06-c217-4081-a309-add4e821b385
    m1: ===> Show Zimon Collector service
    m1: + echo '===> Show Zimon Collector service'
    m1: + service pmcollector status
    m1: Redirecting to /bin/systemctl status pmcollector.service
    m1: ● pmcollector.service - zimon collector daemon
    m1:    Loaded: loaded (/usr/lib/systemd/system/pmcollector.service; enabled; vendor preset: disabled)
    m1:    Active: active (running) since Wed 2020-11-11 10:53:01 UTC; 2min 42s ago
    m1:  Main PID: 25060 (pmcollector)
    m1:    Memory: 852.0K
    m1:    CGroup: /system.slice/pmcollector.service
    m1:            └─25060 /opt/IBM/zimon/sbin/pmcollector -C /opt/IBM/zimon/ZIMonCollector.cfg -R /var/run/perfmon
    m1:
    m1: Nov 11 10:53:01 m1 systemd[1]: Stopped zimon collector daemon.
    m1: Nov 11 10:53:01 m1 systemd[1]: Started zimon collector daemon.
    m1: ===> Show Zimon Sensors service
    m1: + echo '===> Show Zimon Sensors service'
    m1: + service pmsensors status
    m1: Redirecting to /bin/systemctl status pmsensors.service
    m1: ● pmsensors.service - zimon sensor daemon
    m1:    Loaded: loaded (/usr/lib/systemd/system/pmsensors.service; enabled; vendor preset: disabled)
    m1:    Active: active (running) since Wed 2020-11-11 10:53:07 UTC; 2min 35s ago
    m1:  Main PID: 27207 (pmsensors)
    m1:    Memory: 8.8M
    m1:    CGroup: /system.slice/pmsensors.service
    m1:            ├─27207 /opt/IBM/zimon/sbin/pmsensors -C /opt/IBM/zimon/ZIMonSensors.cfg -R /var/run/perfmon
    m1:            ├─27247 /opt/IBM/zimon/MMDFProxy
    m1:            ├─27249 /opt/IBM/zimon/MmpmonSockProxy
    m1:            └─27265 /opt/IBM/zimon/MMCmdProxy
    m1:
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSFileset registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSPool registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSWaiters registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSEventProducer registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSBufMgr registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSOpenFile registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSQoS registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: GPFSVFSX registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: SensorFactory: Blaster registered
    m1: Nov 11 10:53:07 m1 pmsensors[27207]: Nov-11 10:53:07  [Info   ]: Successfully read configuration from file /opt/IBM/zimon/ZIMonSensors.cfg
    m1: ==> Initialize Spectrum Scale GUI
    m1: + echo '==> Initialize Spectrum Scale GUI'
    m1: + sudo /usr/lpp/mmfs/gui/cli/initgui
    m1: EFSSA0634I The cluster demo.example.com has already been added as managed cluster.
    m1: EFSSG1000I The command completed successfully.
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/install/script-06.sh VirtualBox
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script-06.sh
    m1: ===> Create Spectrum Scale filesystems
    m1: ===>
    m1: =========================================================================================
    m1: ===> Show filesystem specification
    m1: + set -e
    m1: + echo '===> Show filesystem specification'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale filesystem list
    m1: [ INFO  ] Name   BlockSize   Mountpoint   NSDs Assigned  Default Data Replicas     Max Data Replicas     Default Metadata Replicas     Max Metadata Replicas
    m1: [ INFO  ] fs1    Default (4M)/ibm/fs1     5              1                         2                     1                             2
    m1: [ INFO  ]
    m1: ===> Create Spectrum Scale filesystems
    m1: + echo '===> Create Spectrum Scale filesystems'
    m1: + sudo /usr/lpp/mmfs/<IP_ADDRESS>/installer/spectrumscale deploy
    m1: [ WARN  ] On fresh installations, you might get Chef related errors during installation toolkit deployment. To work around this problem, on fresh installations, before the installation toolkit prechecks, you must create passwordless SSH keys by using the 'ssh-keygen -m PEM' command.
    m1: [ INFO  ] Logging to file: /usr/lpp/mmfs/<IP_ADDRESS>/installer/logs/DEPLOY-11-11-2020_10:55:47.log
    m1: [ INFO  ] Validating configuration
    m1: [ WARN  ] Only one GUI server specified. The Graphical User Interface will not be highly available.
    m1: [ INFO  ] Install toolkit will not configure file audit logging as it has been disabled.
    m1: [ INFO  ] Checking for knife bootstrap configuration...
    m1: [ INFO  ] Running pre-install checks
    m1: [ INFO  ] NSDs are in a valid state
    m1: [ INFO  ] Running environment checks for Performance Monitoring
    m1: [ INFO  ] Running environment checks for file  Audit logging
    m1: [ INFO  ] Network check from admin node m1.example.com to all other nodes in the cluster passed
    m1: [ WARN  ] Ephemeral port range is not set. Please set valid ephemeral port range using the command ./spectrumscale config gpfs --ephemeral_port_range . You may set the default values as 60000-61000
    m1: [ INFO  ] The install toolkit will not configure call home as it is disabled. To enable call home, use the following CLI command: ./spectrumscale callhome enable
    m1: [ WARN  ] On the nodes: [['m1.example.com with OS RHEL7']], the Portmapper service (rpcbind) is found running and it is advised to disable it or verify with the operating system's administrator.
    m1: [ INFO  ] Preparing nodes for install
    m1: [ INFO  ] Installing Chef (deploy tool)
    m1: [ INFO  ] Installing Chef Client on nodes
    m1: [ INFO  ] Checking for chef-client and installing if required on m1.example.com
    m1: [ INFO  ] Chef Client 13.6.4 is on node m1.example.com
    m1: [ INFO  ] Installing Filesystem
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:13] IBM SPECTRUM SCALE: Creating GPFS filesystem fs1 (SS17)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:25] IBM SPECTRUM SCALE: Mounting GPFS filesystem fs1 (SS18)
    m1: [ INFO  ] Installing Performance Monitoring
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:37] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:37] IBM SPECTRUM SCALE: Creating core gpfs repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:38] IBM SPECTRUM SCALE: Creating gpfs librdkafka repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:39] IBM SPECTRUM SCALE: Configuring GPFS performance monitoring repository (SS31)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:40] IBM SPECTRUM SCALE: Installing performance monitoring packages (SS70)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:47] IBM SPECTRUM SCALE: Tearing down core gpfs repository (SS06)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:48] IBM SPECTRUM SCALE: Tearing down GPFS performance monitoring repository (SS35)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:54] IBM SPECTRUM SCALE: Starting performance monitoring collector (SS73)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:58] IBM SPECTRUM SCALE: Generating configuration for performance monitoring tools (SS83)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:59] IBM SPECTRUM SCALE: Modifying sensor configuration for performance monitoring tools (SS85)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:56:59] IBM SPECTRUM SCALE: Enabling GPFS Disk Capacity sensors (SS90)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:04] IBM SPECTRUM SCALE: Enabling performance monitoring sensors (SS84)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:13] IBM SPECTRUM SCALE: Restarting performance monitoring sensors (SS74)
    m1: [ INFO  ] Installing GUI
    m1: [ INFO  ] GUI packages to be installed: gpfs.gui
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:19] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:19] IBM SPECTRUM SCALE: Creating core gpfs repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:20] IBM SPECTRUM SCALE: Creating gpfs librdkafka repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:20] IBM SPECTRUM SCALE: Configuring GPFS performance monitoring repository (SS31)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:21] IBM SPECTRUM SCALE: Installing GPFS GUI package (SS19)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:24] IBM SPECTRUM SCALE: Starting the Graphical User Interface service (SS23)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:28] IBM SPECTRUM SCALE: Tearing down core gpfs repository (SS06)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:29] IBM SPECTRUM SCALE: Tearing down GPFS performance monitoring repository (SS35)
    m1: [ INFO  ] Installing FILE AUDIT LOGGING
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:35] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:35] IBM SPECTRUM SCALE: Creating core gpfs repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:36] IBM SPECTRUM SCALE: Creating gpfs librdkafka repository (SS00)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:37] IBM SPECTRUM SCALE: Configuring GPFS performance monitoring repository (SS31)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:39] IBM SPECTRUM SCALE: Installing gpfs librdkafka packages (SS265)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:39] IBM SPECTRUM SCALE: Installing gpfs librdkafka packages (SS265)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:43] IBM SPECTRUM SCALE: Tearing down core gpfs repository (SS06)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:44] IBM SPECTRUM SCALE: Tearing down GPFS performance monitoring repository (SS35)
    m1: [ INFO  ] [m1.example.com 11-11-2020 10:57:51] IBM SPECTRUM SCALE: Removing Yum cache repository (SS229)
    m1: [ INFO  ] Checking for a successful install
    m1: [ INFO  ] Checking state of Chef (deploy tool)
    m1: [ INFO  ] Chef (deploy tool) ACTIVE
    m1: [ INFO  ] Checking state of Filesystem
    m1: [ INFO  ] File systems have been created successfully
    m1: [ INFO  ] Filesystem ACTIVE
    m1: [ INFO  ] Checking state of Performance Monitoring
    m1: [ INFO  ] Running Performance Monitoring post-install checks
    m1: [ INFO  ] pmcollector running on all nodes
    m1: [ INFO  ] pmsensors running on all nodes
    m1: [ INFO  ] Performance Monitoring ACTIVE
    m1: [ INFO  ] Checking state of GUI
    m1: [ INFO  ] Running Graphical User Interface  post-install checks
    m1: [ INFO  ] Graphical User Interface running on all GUI servers
    m1: [ INFO  ] Enter one of the following addresses into a web browser to access the Graphical User Interface: <IP_ADDRESS>, <IP_ADDRESS>, m1.example.com
    m1: [ INFO  ] GUI ACTIVE
    m1: [ INFO  ] SUCCESS
    m1: [ INFO  ] All services running
    m1: [ INFO  ] StanzaFile and NodeDesc file for NSD, filesystem, and cluster setup have been saved to /usr/lpp/mmfs folder on node: m1.example.com
    m1: [ INFO  ] Successfully installed protocol packages on 0 protocol nodes. Components installed: Chef (deploy tool), Filesystem, Performance Monitoring, GUI, FILE AUDIT LOGGING. it took 2 minutes and 9 seconds.
    m1: ===> Enable quotas
    m1: ===> Note: Capacity reports in the GUI depend on enabled quotas
    m1: + echo '===> Enable quotas'
    m1: + echo '===> Note: Capacity reports in the GUI depend on enabled quotas'
    m1: + sudo mmchfs fs1 -Q yes
    m1: mmchfs: mmsdrfs propagation completed.
    m1: ===> Show Spectrum Scale filesystem configuration
    m1: + echo '===> Show Spectrum Scale filesystem configuration'
    m1: + sudo mmlsfs all
    m1:
    m1: File system attributes for /dev/fs1:
    m1: ====================================
    m1: flag                value                    description
    m1: ------------------- ------------------------ -----------------------------------
    m1:  -f                 8192                     Minimum fragment (subblock) size in bytes
    m1:  -i                 4096                     Inode size in bytes
    m1:  -I                 32768                    Indirect block size in bytes
    m1:  -m                 1                        Default number of metadata replicas
    m1:  -M                 2                        Maximum number of metadata replicas
    m1:  -r                 1                        Default number of data replicas
    m1:  -R                 2                        Maximum number of data replicas
    m1:  -j                 scatter                  Block allocation type
    m1:  -D                 nfs4                     File locking semantics in effect
    m1:  -k                 nfs4                     ACL semantics in effect
    m1:  -n                 100                      Estimated number of nodes that will mount file system
    m1:  -B                 4194304                  Block size
    m1:  -Q                 user;group;fileset       Quotas accounting enabled
    m1:                     user;group;fileset       Quotas enforced
    m1:                     none                     Default quotas enabled
    m1:  --perfileset-quota No                       Per-fileset quota enforcement
    m1:  --filesetdf        No                       Fileset df enabled?
    m1:  -V                 24.00 (<IP_ADDRESS>)          File system version
    m1:  --create-time      Wed Nov 11 10:56:25 2020 File system creation time
    m1:  -z                 No                       Is DMAPI enabled?
    m1:  -L                 33554432                 Logfile size
    m1:  -E                 Yes                      Exact mtime mount option
    m1:  -S                 relatime                 Suppress atime mount option
    m1:  -K                 whenpossible             Strict replica allocation option
    m1:  --fastea           Yes                      Fast external attributes enabled?
    m1:  --encryption       No                       Encryption enabled?
    m1:  --inode-limit      107520                   Maximum number of inodes
    m1:  --log-replicas     0                        Number of log replicas
    m1:  --is4KAligned      Yes                      is4KAligned?
    m1:  --rapid-repair     Yes                      rapidRepair enabled?
    m1:  --write-cache-threshold 0                   HAWC Threshold (max 65536)
    m1:  --subblocks-per-full-block 512              Number of subblocks per full block
    m1:  -P                 system                   Disk storage pools in file system
    m1:  --file-audit-log   No                       File Audit Logging enabled?
    m1:  --maintenance-mode No                       Maintenance Mode enabled?
    m1:  -d                 nsd1;nsd2;nsd3;nsd4;nsd5  Disks in file system
    m1:  -A                 yes
    m1: Automatic mount option
    m1:  -o                 none
    m1: Additional mount options
    m1:  -T                 /ibm/fs1
    m1: Default mount point
    m1:  --mount-priority   0
    m1: Mount priority
    m1: ===> Show Spectrum Scale filesystem usage
    m1: + echo '===> Show Spectrum Scale filesystem usage'
    m1: + sudo mmdf fs1
    m1: disk                disk size  failure holds    holds           free in KB          free in KB
    m1: name                    in KB    group metadata data        in full blocks        in fragments
    m1: --------------- ------------- -------- -------- ----- -------------------- -------------------
    m1: Disks in storage pool: system (Maximum disk size allowed is 29.12 GB)
    m1: nsd1                  2097152        1 Yes      Yes         1273856 ( 61%)         11384 ( 1%)
    m1: nsd2                  2097152        1 Yes      Yes         1269760 ( 61%)         11128 ( 1%)
    m1: nsd3                  2097152        1 Yes      Yes         1290240 ( 62%)         11128 ( 1%)
    m1: nsd4                  2097152        1 Yes      Yes         1286144 ( 61%)         11640 ( 1%)
    m1: nsd5                  2097152        1 Yes      Yes         1241088 ( 59%)         11640 ( 1%)
    m1:                 -------------                         -------------------- -------------------
    m1: (pool total)         10485760                               6361088 ( 61%)         56920 ( 1%)
    m1:
    m1:                 =============                         ==================== ===================
    m1: (total)              10485760                               6361088 ( 61%)         56920 ( 1%)
    m1:
    m1: Inode Information
    m1: -----------------
    m1: Number of used inodes:            4106
    m1: Number of free inodes:          103414
    m1: Number of allocated inodes:     107520
    m1: Maximum number of inodes:       107520
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/install/script-07.sh VirtualBox
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/install/script-07.sh
    m1: ===> Tune sensors for demo environment
    m1: ===>
    m1: =========================================================================================
    m1: ===> Tune sensors for demo environment
    m1: + set -e
    m1: + echo '===> Tune sensors for demo environment'
    m1: + sudo mmperfmon config update GPFSPool.restrict=m1.example.com GPFSFileset.restrict=m1.example.com DiskFree.period=300 GPFSFilesetQuota.period=300 GPFSDiskCap.period=300
    m1: mmperfmon: mmsdrfs propagation completed.
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
==> m1: Running provisioner: Configure Spectrum Scale for demo purposes (shell)...
    m1: Running: script: Configure Spectrum Scale for demo purposes
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/demo/script.sh
    m1: ===> Perform all steps to configure Spectrum Scale for demo purposes
    m1: ===>
    m1: =========================================================================================
    m1: + set -e
    m1: + /vagrant/demo/script-01.sh
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/demo/script-01.sh
    m1: ===> Show Spectrum Scale filesystems
    m1: ===>
    m1: =========================================================================================
    m1: ===> Show the global mount status for the whole Spectrum Scale cluster
    m1: + set -e
    m1: + echo '===> Show the global mount status for the whole Spectrum Scale cluster'
    m1: + mmlsmount all
    m1: File system fs1 is mounted on 1 nodes.
    m1: ==> Show the default mount point managed by Spectrum Scale
    m1: + echo '==> Show the default mount point managed by Spectrum Scale'
    m1: + mmlsfs fs1 -T
    m1: flag                value                    description
    m1: ------------------- ------------------------ -----------------------------------
    m1:  -T                 /ibm/fs1
    m1: Default mount point
    m1: ===> Show the local mount status on the current node
    m1: + echo '===> Show the local mount status on the current node'
    m1: fs1 on /ibm/fs1 type gpfs (rw,relatime,seclabel)
    m1: ===> Show content of all Spectrum Scale filesystems
    m1: + mount
    m1: + grep /ibm/
    m1: + echo '===> Show content of all Spectrum Scale filesystems'
    m1: + find /ibm/
    m1: /ibm/
    m1: /ibm/fs1
    m1: /ibm/fs1/.snapshots
    m1: ==> Show all Spectrum Scale filesystems using the REST API
    m1: + echo '==> Show all Spectrum Scale filesystems using the REST API'
    m1: + curl -k -s -S -X GET --header 'Accept: application/json' -u admin:admin001 https://localhost/scalemgmt/v2/filesystems/
    m1: Error 401: SRVE0295E: Error reported: 401
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/demo/script-02.sh
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/demo/script-02.sh
    m1: ===> Add second storage pool to filesystem fs1
    m1: ===>
    m1: =========================================================================================
    m1: ===> Show storage pools of filesystem fs1
    m1: + set -e
    m1: + echo '===> Show storage pools of filesystem fs1'
    m1: + mmlspool fs1
    m1: Storage pools in file system at '/ibm/fs1':
    m1: Name                    Id   BlkSize Data Meta Total Data in (KB)   Free Data in (KB)   Total Meta in (KB)    Free Meta in (KB)
    m1: system                   0      4 MB  yes  yes       10485760        6361088 ( 61%)       10485760        6414336 ( 61%)
    m1: ===> Show usage of filesystem fs1
    m1: + echo '===> Show usage of filesystem fs1'
    m1: + mmdf fs1
    m1: disk                disk size  failure holds    holds           free in KB          free in KB
    m1: name                    in KB    group metadata data        in full blocks        in fragments
    m1: --------------- ------------- -------- -------- ----- -------------------- -------------------
    m1: Disks in storage pool: system (Maximum disk size allowed is 29.12 GB)
    m1: nsd1                  2097152        1 Yes      Yes         1273856 ( 61%)         11384 ( 1%)
    m1: nsd2                  2097152        1 Yes      Yes         1269760 ( 61%)         11128 ( 1%)
    m1: nsd3                  2097152        1 Yes      Yes         1290240 ( 62%)         11128 ( 1%)
    m1: nsd4                  2097152        1 Yes      Yes         1286144 ( 61%)         11640 ( 1%)
    m1: nsd5                  2097152        1 Yes      Yes         1241088 ( 59%)         11640 ( 1%)
    m1:                 -------------                         -------------------- -------------------
    m1: (pool total)         10485760                               6361088 ( 61%)         56920 ( 1%)
    m1:
    m1:                 =============                         ==================== ===================
    m1: (total)              10485760                               6361088 ( 61%)         56920 ( 1%)
    m1:
    m1: Inode Information
    m1: -----------------
    m1: Number of used inodes:            4106
    m1: Number of free inodes:          103414
    m1: Number of allocated inodes:     107520
    m1: Maximum number of inodes:       107520
    m1: ===> Show the stanza file that describe the new disks
    m1: + echo '===> Show the stanza file that describe the new disks'
    m1: + cat /vagrant/files/spectrumscale/stanza-fs1-capacity
    m1: %nsd: device=/dev/sdg
    m1: nsd=nsd6
    m1: servers=m1
    m1: usage=dataOnly
    m1: failureGroup=1
    m1: pool=capacity
    m1:
    m1: %nsd: device=/dev/sdh
    m1: nsd=nsd7
    m1: servers=m1
    m1: usage=dataOnly
    m1: failureGroup=1
    m1: pool=capacity
    m1: ===> Add NSDs to new capacity storage pool
    m1: + echo '===> Add NSDs to new capacity storage pool'
    m1: + sudo mmadddisk fs1 -F /vagrant/files/spectrumscale/stanza-fs1-capacity
    m1:
    m1: The following disks of fs1 will be formatted on node m1:
    m1:     nsd6: size 10240 MB
    m1:     nsd7: size 10240 MB
    m1: Extending Allocation Map
    m1: Creating Allocation Map for storage pool capacity
    m1: Flushing Allocation Map for storage pool capacity
    m1: Disks up to size 322.37 GB can be added to storage pool capacity.
    m1: Checking Allocation Map for storage pool capacity
    m1: Completed adding disks to file system fs1.
    m1: mmadddisk: mmsdrfs propagation completed.
    m1: ===> Show storage pools of filesystem fs1
    m1: + echo '===> Show storage pools of filesystem fs1'
    m1: + mmlspool fs1
    m1: Storage pools in file system at '/ibm/fs1':
    m1: Name                    Id   BlkSize Data Meta Total Data in (KB)   Free Data in (KB)   Total Meta in (KB)    Free Meta in (KB)
    m1: system                   0      4 MB  yes  yes       10485760        6348800 ( 61%)       10485760        6402048 ( 61%)
    m1: capacity             65537      4 MB  yes   no       20971520              0 (  0%)              0              0 (  0%)
    m1: ===> Show usage of filesystem fs1
    m1: + echo '===> Show usage of filesystem fs1'
    m1: + mmdf fs1
    m1: disk                disk size  failure holds    holds           free in KB          free in KB
    m1: name                    in KB    group metadata data        in full blocks        in fragments
    m1: --------------- ------------- -------- -------- ----- -------------------- -------------------
    m1: Disks in storage pool: system (Maximum disk size allowed is 29.12 GB)
    m1: nsd1                  2097152        1 Yes      Yes         1273856 ( 61%)         11384 ( 1%)
    m1: nsd2                  2097152        1 Yes      Yes         1269760 ( 61%)         11128 ( 1%)
    m1: nsd3                  2097152        1 Yes      Yes         1286144 ( 61%)         11128 ( 1%)
    m1: nsd4                  2097152        1 Yes      Yes         1282048 ( 61%)         11640 ( 1%)
    m1: nsd5                  2097152        1 Yes      Yes         1236992 ( 59%)         11640 ( 1%)
    m1:                 -------------                         -------------------- -------------------
    m1: (pool total)         10485760                               6348800 ( 61%)         56920 ( 1%)
    m1:
    m1: Disks in storage pool: capacity (Maximum disk size allowed is 322.37 GB)
    m1: nsd6                 10485760        1 No       Yes        10412032 ( 99%)          8056 ( 0%)
    m1: nsd7                 10485760        1 No       Yes        10412032 ( 99%)          8056 ( 0%)
    m1:                 -------------                         -------------------- -------------------
    m1: (pool total)         20971520                              20824064 ( 99%)         16112 ( 0%)
    m1:
    m1:                 =============                         ==================== ===================
    m1: (data)               31457280                              27172864 ( 86%)         73032 ( 0%)
    m1: (metadata)           10485760                               6348800 ( 61%)         56920 ( 1%)
    m1:                 =============                         ==================== ===================
    m1: (total)              31457280                              27172864 ( 86%)         73032 ( 0%)
    m1:
    m1: Inode Information
    m1: -----------------
    m1: Number of used inodes:            4106
    m1: Number of free inodes:          103414
    m1: Number of allocated inodes:     107520
    m1: Maximum number of inodes:       107520
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/demo/script-03.sh
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/demo/script-03.sh
    m1: ===> Create placement policy for filesystem fs1
    m1: ===>
    m1: =========================================================================================
    m1: ===> Show file that contains the placement rules
    m1: + set -e
    m1: + echo '===> Show file that contains the placement rules'
    m1: + cat /vagrant/files/spectrumscale/fs1-placement-policy
    m1: RULE 'Files ending with .hot to system pool'
    m1:     SET POOL 'system'
    m1:         WHERE (LOWER(NAME) LIKE '%.hot')
    m1:
    m1: RULE 'All other files to capacity pool'
    m1:     SET POOL 'capacity'
    m1: ===> Activate placement rules
    m1: + echo '===> Activate placement rules'
    m1: + sudo mmchpolicy fs1 /vagrant/files/spectrumscale/fs1-placement-policy
    m1: Validated policy 'fs1-placement-policy': Parsed 2 policy rules.
    m1: Policy `fs1-placement-policy' installed and broadcast to all nodes.
    m1: ===> Show all active rules
    m1: + echo '===> Show all active rules'
    m1: + mmlspolicy fs1
    m1: Policy for file system '/dev/fs1':
    m1:    Installed by vagrant@m1 on Wed Nov 11 10:58:22 2020.
    m1:    First line of policy 'fs1-placement-policy' is:
    m1: RULE 'Files ending with .hot to system pool'
    m1: ===> Create example directory to demonstrate placement rules
    m1: + echo '===> Create example directory to demonstrate placement rules'
    m1: + sudo mkdir -p /ibm/fs1/examples/placement_policy
    m1: ===> Create file that will be placed in the system storage pool
    m1: + echo '===> Create file that will be placed in the system storage pool'
    m1: + sudo bash -c 'echo "This file will be placed in the system storage pool" > /ibm/fs1/examples/placement_policy/file.hot'
    m1: ===> Create file that will be placed in the capacity storage pool
    m1: + echo '===> Create file that will be placed in the capacity storage pool'
    m1: + sudo bash -c 'echo "This file will be placed in the capacity storage pool" > /ibm/fs1/examples/placement_policy/file.txt'
    m1: ===> Show that hot file is placed in the system storage pool
    m1: + echo '===> Show that hot file is placed in the system storage pool'
    m1: + grep 'storage pool name'
    m1: + mmlsattr -L /ibm/fs1/examples/placement_policy/file.hot
    m1: storage pool name:    system
    m1: ===> Show that default file is placed in the capacity storage pool
    m1: + echo '===> Show that default file is placed in the capacity storage pool'
    m1: + grep 'storage pool name'
    m1: + mmlsattr -L /ibm/fs1/examples/placement_policy/file.txt
    m1: storage pool name:    capacity
    m1: ===> Show that Spectrum Scale storage pools are not visible to end users
    m1: + echo '===> Show that Spectrum Scale storage pools are not visible to end users'
    m1: + ls -la /ibm/fs1/examples/placement_policy
    m1: total 2
    m1: drwxr-xr-x. 2 root root 4096 Nov 11 10:58 .
    m1: drwxr-xr-x. 3 root root 4096 Nov 11 10:58 ..
    m1: -rw-r--r--. 1 root root   52 Nov 11 10:58 file.hot
    m1: -rw-r--r--. 1 root root   54 Nov 11 10:58 file.txt
    m1: + wc -l /ibm/fs1/examples/placement_policy/file.hot /ibm/fs1/examples/placement_policy/file.txt
    m1:   1 /ibm/fs1/examples/placement_policy/file.hot
    m1:   1 /ibm/fs1/examples/placement_policy/file.txt
    m1:   2 total
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/demo/script-05.sh
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/demo/script-05.sh
    m1: ===> Create filesets and some example data
    m1: ===>
    m1: =========================================================================================
    m1: ===> Create example groups
    m1: + set -e
    m1: + echo '===> Create example groups'
    m1: + sudo groupadd flowers
    m1: + sudo groupadd pets
    m1: ===> Creating example users
    m1: + echo '===> Creating example users'
    m1: + sudo useradd admin_flowers -g flowers
    m1: + sudo useradd daffodils -g flowers
    m1: + sudo useradd roses -g flowers
    m1: + sudo useradd tulips -g flowers
    m1: + sudo useradd admin_pets -g pets
    m1: + sudo useradd cats -g pets
    m1: + sudo useradd dogs -g pets
    m1: + sudo useradd hamsters -g pets
    m1: ===> Create Spectrum Scale Filesets
    m1: + echo '===> Create Spectrum Scale Filesets'
    m1: + sudo mmcrfileset fs1 pets -t 'Cute Pets'
    m1: Fileset pets created with id 1 root inode 76547.
    m1: + sudo mmcrfileset fs1 flowers -t 'Lovely Flowers'
    m1: Fileset flowers created with id 2 root inode 76548.
    m1: ===> Link Spectrum Scale Filesets
    m1: + echo '===> Link Spectrum Scale Filesets'
    m1: + sudo mmlinkfileset fs1 pets -J /ibm/fs1/pets
    m1: Fileset pets linked at /ibm/fs1/pets
    m1: + sudo mmlinkfileset fs1 flowers -J /ibm/fs1/flowers
    m1: Fileset flowers linked at /ibm/fs1/flowers
    m1: ===> Create directories for users
    m1: + echo '===> Create directories for users'
    m1: + sudo mkdir /ibm/fs1/flowers/daffodils
    m1: + sudo mkdir /ibm/fs1/flowers/roses
    m1: + sudo mkdir /ibm/fs1/flowers/tulips
    m1: + sudo mkdir /ibm/fs1/pets/cats
    m1: + sudo mkdir /ibm/fs1/pets/dogs
    m1: + sudo mkdir /ibm/fs1/pets/hamsters
    m1: ===> Create some files in each user directory
    m1: + echo '===> Create some files in each user directory'
    m1: + inc=3
    m1: + for dir in '/ibm/fs1/*/*'
    m1: + inc=4
    m1: + num_files=14
    m1: + cur_file=0
    m1: + '[' 0 -lt 14 ']'
    m1: + cur_file=1
    m1: + num_blocks=27
    m1: + sudo dd if=/dev/zero of=/ibm/fs1/examples/placement_policy/file1 bs=100K count=27
    m1: + '[' 1 -lt 14 ']'
    m1: + cur_file=2
    m1: + num_blocks=44
    m1: + sudo dd if=/dev/zero of=/ibm/fs1/examples/placement_policy/file2 bs=100K count=44
...
    m1: + sudo touch /ibm/fs1/examples/exceed_error_threshold/file950
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: + /vagrant/demo/script-99.sh
    m1: =========================================================================================
    m1: ===>
    m1: ===> Running /vagrant/demo/script-99.sh
    m1: ===> Update the capacitiy reports
    m1: ===>
    m1: =========================================================================================
    m1: + set -e
    m1: ===> Initialize quota database
    m1: + echo '===> Initialize quota database'
    m1: + sudo mmcheckquota fs1
    m1: fs1: Start quota check
    m1:   12 % complete on Wed Nov 11 11:21:41 2020
    m1:   24 % complete on Wed Nov 11 11:21:42 2020
    m1:   36 % complete on Wed Nov 11 11:21:42 2020
    m1:   68 % complete on Wed Nov 11 11:21:42 2020
    m1:  100 % complete on Wed Nov 11 11:21:42 2020
    m1: Finished scanning the inodes for fs1.
    m1: Merging results from scan.
    m1: mmcheckquota: Command completed.
    m1: ===> Update capacity reports
    m1: + echo '===> Update capacity reports'
    m1: + sudo /usr/lpp/mmfs/gui/cli/runtask QUOTA
    m1: EFSSG1000I The command completed successfully.
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0
    m1: ===> Script completed successfully!
    m1: + echo '===> Script completed successfully!'
    m1: + exit 0

==> m1: Machine 'm1' has a post `vagrant up` message. This is a message
==> m1: from the creator of the Vagrantfile, and not from Vagrant itself:
==> m1:
==> m1: --------------------------------------------------------------------------
==> m1:
==> m1: Created virtual environment for IBM Spectrum Scale.
==> m1:
==> m1: User Guide:
==> m1: https://github.com/IBM/SpectrumScaleVagrant/blob/master/README.md
==> m1:
==> m1: To logon on the management node execute:
==> m1: vagrant ssh
==> m1:
==> m1: To connect to the Spectrum Scale GUI, in a web browser:
==> m1: https://localhost:8888
==> m1:
==> m1: --------------------------------------------------------------------------
==> m1:

@neikei - Thanks for providing this enhancement!


WIP: Feature/extra template context

This PR introduces a new pre-defined label variable, namely extra, which contains the entire JSON object parsed from the input, when using input type webhook with format being either json_single or json_bulk.
It is flexible enough to be utilized by any input, which may want to provide a map as extra context for the label templating step.
The majority of changes has been made in the initial commit 6ee14ae, and simply involves changing the type of additionalFields from map[string]string to map[string]interface{} in order to support proper recursive data structures as extra context.
An argument could have been made to go all the way to data interface{} as this is the type utilized for the Execute method's data argument on the Template type, however map[string]interface{} seemed like a good compromise.

I have tested the change using:
global:
  config_version: 3
input:
  type: webhook
  webhook_path: /webhook
  webhook_format: json_single
  webhook_json_selector: .message
  webhook_text_bulk_separator: "\n\n"
metrics:
- type: counter
  name: user_logins
  help: Total number of user logins, by user and ip.
  match: 'Login occured'
  labels:
    user: '{{ index .extra "user" }}'
    ip: '{{ index .extra "ip" }}'
server:
  host: "[::]"
  port: 9144

Started as:
go run grok_exporter.go -config example/config_context_json.yml

With the following log messages being posted:
curl localhost:9144/webhook --data '{"message": "Login occured", "user": "Skeen", "ip": "<IP_ADDRESS>"}'

And this as output:
# HELP user_logins Total number of user logins, by user and ip.
# TYPE user_logins counter
user_logins{ip="<IP_ADDRESS>",user="Skeen"} 1

Assuming this is something you'll consider merging, I will fix the broken tests, get the build to succeed, and then remove the WIP: prefix on the PR.

Thanks a lot for this! I'll look into this in the next couple of days and get back to you.

Thanks a lot, this sounds like a useful feature for users of the webhook users. I'm happy to merge it once it's finalized.

I don't seem to be able to reproduce the failing test in the appveyor/pr check.
skeen@ibuprofen ~/p/grok_exporter (feature/extra_template_context)> go clean -testcache
skeen@ibuprofen ~/p/grok_exporter (feature/extra_template_context)> go test ./...
?   	github.com/fstab/grok_exporter	[no test files]
ok  	github.com/fstab/grok_exporter/config	0.003s
ok  	github.com/fstab/grok_exporter/config/v2	0.011s
ok  	github.com/fstab/grok_exporter/config/v3	0.015s
ok  	github.com/fstab/grok_exporter/exporter	0.681s
ok  	github.com/fstab/grok_exporter/oniguruma	0.010s
ok  	github.com/fstab/grok_exporter/tailer	23.284s
?   	github.com/fstab/grok_exporter/tailer/fswatcher	[no test files]
ok  	github.com/fstab/grok_exporter/tailer/glob	0.003s
ok  	github.com/fstab/grok_exporter/template	0.004s

Can you assist me with finding out what is going afoul here?

Coverage increased (+0.01%) to 67.231% when pulling e4e0cccc306ce0a74573507378fc429d9e7d1067 on magenta-aps:feature/extra_template_context into 58c93fb4a788051679a908b77646ba3e385a5db6 on fstab:master.

Unfortunately, the Windows file tailor tests are flaky:
fswatcher_test.go:652: C:\Users\appveyor\AppData\Local\Temp\1\grok_exporter807922133\logdir still contains file logfile.log after mv.

The test is simulating logrotate moving the logfile away, but after the mv operation the file is still in the directory. I have no idea why this happens, because the os.Rename(...) call does not return an error. You can ignore this. Re-running the test manually in Appveyor helps, but I think you need to log in to do that. As it is test code that fails and not production code, I don't think it's a big risk to ignore this.
If you have any idea how os.Rename(...) can be successful but the file is still there after that, I'd be grateful, but this has nothing to do with your changes.

Thanks a lot!!!

P.S.: After the merge Appveyor built without error again without any code change https://ci.appveyor.com/project/fstab/grok-exporter/builds/32644306

Unfortunately, the Windows file tailor tests are flaky:
fswatcher_test.go:652: C:\Users\appveyor\AppData\Local\Temp\1\grok_exporter807922133\logdir still contains file logfile.log after mv.

The test is simulating logrotate moving the logfile away, but after the mv operation the file is still in the directory. I have no idea why this happens, because the os.Rename(...) call does not return an error. You can ignore this. Re-running the test manually in Appveyor helps, but I think you need to log in to do that. As it is test code that fails and not production code, I don't think it's a big risk to ignore this.
If you have any idea how os.Rename(...) can be successful but the file is still there after that, I'd be grateful, but this has nothing to do with your changes.

Are we sure that os.rename(...) is indeed atomic on Windows?
I don't believe that is the case in general, as Python calls MoveFileW() on Windows, which is atomic in specific cases, but not as a general case (such as with network mounted file-systems).
On Windows to ensure atomic renaming, you'd have to create a transaction with CreateTransaction() followed by a call to MoveFileTransacted(), and finally a commit.
So in general, I would not assume a os.rename call to be atomic on Windows.
Potential solutions:

Find a library which does transactional file-moves, and accept that the tests will only pass on Windows Vista and higher.
Add a sleep / busy wait loop, continuously checking whether the file has actually been moved yet, and leaving the loop after that happens.


No need to use zepto, merging problems

Thanks.
Did you check if there is no side effect of removing the onReady event on iOS and Android ?


feat: add WRROC models, validators & unit tests

This PR introduces several key changes related to the WRROC models and their corresponding validators. Below is a summary of the changes:
1) Addition of WRROC Models:
TES Models:
Executor: Represents an executor in the Task Execution Service (TES).
TESInputs & TESOutputs: Models representing input and output files in TES.
TESLogs: Represents logs associated with TES tasks.
TESData: Represents a TES task, including all relevant attributes such as executors, inputs, outputs, logs, etc.
WES Models:
WESRunLog: This represents a run log in the Workflow Execution Service (WES).
WESOutputs: Represents output files in WES.
WESRequest: Represents a workflow request in WES.
WESData: Represents a WES run, including request, run log, state, task logs, and outputs.
WRROC Models:
WRROCInputs & WRROCOutputs: Models representing inputs and outputs in WRROC.
WRROCData: Represents a general WRROC entity with attributes like id, name, description, instrument, object, result, startTime, and endTime.
WRROCDataTES & WRROCDataWES: Models specifically designed for TES and WES conversion, inheriting from WRROCData.
WRROCProcess, WRROCWorkflow, WRROCProvenance: Hierarchical models representing different profiles (Process Run, Workflow Run, and Provenance Run) in WRROC.
2) Validators:

I added functions to validate WRROC data and determine the specific profile (Process, Workflow, or Provenance).
We implemented validators to check WRROC data for TES and WES conversions, ensuring the presence of required fields for each conversion type.

3) Unit Tests:

Comprehensive unit tests have been added for the WRROC models and validators to ensure they work as expected.
Tests include validation for correct data, incorrect data, and missing required fields.

Note:
Test cases for TES and WES converters are not included in this PR. They will be addressed in a subsequent PR to keep the changes manageable and focused.

Summary by Sourcery
Add WRROC, TES, and WES models along with corresponding validators and unit tests. Enhance CI workflow to run tests.
New Features:

Introduce WRROC models including WRROCInputs, WRROCOutputs, WRROCData, WRROCDataTES, WRROCDataWES, WRROCProcess, WRROCWorkflow, and WRROCProvenance.
Add TES models such as Executor, TESInputs, TESOutputs, TESLogs, and TESData.
Add WES models including WESRunLog, WESOutputs, WESRequest, and WESData.

Enhancements:

Implement validators for WRROC data to determine specific profiles (Process, Workflow, or Provenance) and ensure required fields for TES and WES conversions.

CI:

Enable running tests in the CI workflow by uncommenting the relevant lines in the CI configuration.

Tests:

Add comprehensive unit tests for WRROC models and validators, covering correct data validation, incorrect data handling, and missing required fields.

Hi @uniqueg and @SalihuDickson,
Summary
This PR introduces several key improvements and fixes based on recent feedback:

Refactor WRROC Models:

Created a base class WRROCDataBase to hold common fields and methods.
Refactored WRROCData, WRROCDataTES, and WRROCDataWES to inherit from WRROCDataBase to reduce code duplication and enhance maintainability.

Stricter Validation:

Replaced extra = "allow" with extra = "forbid" in all WRROC models (WRROCProcess, WRROCWorkflow, WRROCProvenance) to enforce stricter validation.

Enhanced Validation and Error Collection:

Modified validation functions to collect and report all errors found during validation, ensuring comprehensive feedback.
Simplified field validation by removing manual checks for extra fields and leveraging Pydantic's extra = "forbid" configuration.

Expanded Unit Tests:

Added test cases for edge scenarios such as empty object or result lists, missing optional fields, and incorrect data types.
Implemented tests for invalid URLs and other edge cases.
Fixed existing tests by allowing empty lists and adding URL validation in the WES conversion validation.

@Karanjot786, you are currently trying to merge to the models branch which is owned by you (it requires no extra permissions to merge).  If this was by accident please change the base branch.
Alternatively you can merge to the models branch and create a new PR to the main branch.

@SalihuDickson, I noticed the base branch issue. I’ll merge to the models branch and then create a new PR targeting the main branch.


Add zh-tw translation

Add traditional chinese for Taiwan users

@budparr Thanks for merged, I want to add this PR to hacktoberfest (Which event improve open source participate, https://hacktoberfest.digitalocean.com/)
Wolud you add "hacktoberfest-accepted" label for this PR? Thanks :)


Investigate new U15 events

[x] #113
[ ] #111

https://hosting.zaonce.net/community/journal/v37/Journal_Manual_v37.pdf

Investigation complete. Separate issues raised, closing.


Fuzzy matching?

I really miss the fuzzy matching that nvim-compe had...is there a way to enable that in nvim-cmp?

Ah, you're right, my mistake.


grunt: not found

I am trying to run this project.I am getting this error.
sh: 1: grunt: not found
npm ERR! Linux 4.2.0-c9
npm ERR! argv "/home/ubuntu/.nvm/versions/node/v5.5.0/bin/node" "/home/ubuntu/.nvm/versions/node/v5.5.0/bin/npm" "start"
npm ERR! node v5.5.0
npm ERR! npm  v3.3.12
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>start: grunt start
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'grunt start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sails-angular-electron package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     grunt start
npm ERR! You can get their info via:
npm ERR!     npm owner ls sails-angular-electron
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/workspace/npm-debug.log
}).flatten().uniq().value();
^
TypeError: _(...).map(...).flatten is not a function
at Object.module.exports as findup
at Task.task.init (/home/ubuntu/workspace/node_modules/grunt/lib/grunt/task.js:427:16)
at Object.grunt.tasks (/home/ubuntu/workspace/node_modules/grunt/lib/grunt.js:120:8)
at Object.module.exports as cli
at Object. (/home/ubuntu/.nvm/versions/node/v5.5.0/lib/node_modules/grunt-cli/bin/grunt:44:20)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Function.Module.runMain (module.js:447:10)

@HaiderMalik12 Did you managed to make it works ? I need to make a sailsjs api with electronjs inside.


Update ssh_config provider

If there is more than one entry for SendEnv, it didn't remove the extra entries.

Changes Unknown when pulling f8d9de78323b365c60b6d42fe8177370fbdc8dc8 on jamesmwestover:master into ** on hercules-team:master**.

Changes Unknown when pulling f8d9de78323b365c60b6d42fe8177370fbdc8dc8 on jamesmwestover:master into ** on hercules-team:master**.

Changes Unknown when pulling f8d9de78323b365c60b6d42fe8177370fbdc8dc8 on jamesmwestover:master into ** on hercules-team:master**.

Changes Unknown when pulling f8d9de78323b365c60b6d42fe8177370fbdc8dc8 on jamesmwestover:master into ** on hercules-team:master**.

Thank you for this. Could you squash the commits and add some documentation about this behavior in README.md please?


Skaffold a Task's project

Feature request
Have you considered part of the Tekton project to propose a tool or a UI screen on the hub able to skaffold a Task like also to generate the README.md from the Task definition such as:

name,
description,
parameters,
workspaces,
result,
etc

Use case

As a user/contributor, I would like to easily create a new task's project from a skeleton and containing a README file + needed files and folder(s)
As a user/contributor, I would like when I create a new task to encode the name, description, parameter(s), workspace(s) and that a project is generated

Probably not suited for tektoncd/pipeline

Should we then move this ticket under https://github.com/tektoncd/cli ? What about having too this option offered on https://hub.tekton.dev/ as by example operator hub proposes too https://operatorhub.io/packages ?

I made a poc of a auto generation tool https://github.com/chmouel/tkn-autogenerate, this output pac templates but that can be modified to use tekton resolvers instead

Remark: Your POC makes the job from an existing project and do not generate using a skeleton a project to create a task, pipeline, etc

I also implemented a poc of using LLM to 1) create a task from user's prompt 2) generate readme/docs from the task yaml.
Do you think that's something useful?

Certainly. How users will then been able to consume such AI/LLM feature ?


Regex response type is not respected

System Info
Using TGI through Inference Endpoints with this endpoint.
Reproduction
This is the example from the doc.
from huggingface_hub import InferenceClient

client = InferenceClient("https://o9blasawqn0vtw5b.us-east-1.aws.endpoints.huggingface.cloud")

regexp = "((25[0-5]|2[0-4]\\d|[01]?\\d\\d?)\\.){3}(25[0-5]|2[0-4]\\d|[01]?\\d\\d?)"

resp = client.text_generation(
    f"What is Googles DNS? Please use the following regex: {regexp}",
    seed=42,
    grammar={
        "type": "regex",
        "value": regexp,
    },
)

print(resp)

I get output:
<IP_ADDRESS>1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
Expected behavior
I would expect to get a matching regex, so the last number should be between 0 and 255 and not a long sequence of 1s.

Thanks for reporting @aymeric-roucher 🙌
I wonder if it's technically respecting the grammar 🤔 my hypothesis:

every token respects the grammar since the token is a "1", so thats between 0 and 255
at the end, instead of ending the sequence, the model just continues adding the "1" token until max tokens is reached

I've seen similar behavior with e.g "\n", especially on 8B and smaller models.
I'll ping @drbh for this one as well 👍

Hey @aymeric-roucher thanks for pointing this out, I believe there was a couple issues with the regex expression I originally added to the docs. I think the \\d? notion may have caused subtle issues with the grammar compilation. A similar yet more simple and valid IP grammar would be (((25[0-5]|2[0-4]|[01])\.){3}(25[0-5]|2[0-4]|[01])) and that would match <IP_ADDRESS>, the final 1 should only appear once. Apologies for any confusion!
I've just opened a PR to update the docs to use a different (easier to read and re use) regex expression here: https://github.com/huggingface/text-generation-inference/pull/2468

closing as https://github.com/huggingface/text-generation-inference/pull/2468 was merged and is available here https://huggingface.co/docs/text-generation-inference/en/basic_tutorials/using_guidance#constrain-with-pydantic


Agency table location maintenance

Context
Related to https://github.com/Police-Data-Accessibility-Project/data-source-map/pull/6
Most of our agencies have lat/lng, but a few do not.

Requirements

A script to batch-create location data (latitude and longitude) for all agencies for which it is blank.

If we can find a maps record for the agency that seems to have a specific lat/lng inside the bounds of the database's jurisdiction, we can use that
If we can't find a google maps record, we can use the lat/lng of the center of the county/city, or use another clever abstraction.

Add that data to the db for each record.
Create a mechanism to automatically do this, maybe monthly, when agencies have lat/lng blank. (This would be infrequent enough that it would place us in the free tier for most geocoding APIs)

Open questions

when we put data sources and agencies on a map, we might not need to put them in exact locations—when zoomed in on a county, a user may just see a list of agencies which appear there.

duplicate of https://github.com/Police-Data-Accessibility-Project/data-sources-app/issues/246


Missing Content and Broken links

URL for relevant page?
https://docs.influxdata.com/influxdb/v1.6/tools/shell/#import-data-from-a-file-with-import
doesn't look like it migrated across to 1.7 and 1.8
https://docs.influxdata.com/influxdb/v1.7/guides/writing_data/
is missing in the 1.8 release.
https://docs.influxdata.com/influxdb/v1.7/guides
broken header.

fix broken header https://github.com/influxdata/docs.influxdata.com/commit/35c256fff99ec5a608fed79872acfb81d3740795

Thanks @timhallinflux, resolved


map search enhancements

As a new user I find the experience of using map search could have been a lot smoother. I have a few ideas for enhancements here. I’d be keen to work on any/all of them.

Remove duplicates for the search results. Currently if I search for “Toronto” I get two identical results that display as “Toronto, Ontario, Canada”. When multiple results from OSM have the same computed display name we could drop the one(s) with the lower importance score.
Autocomplete/debounce inputs. It’s a little annoying/confusing that you have to hit enter to search. So instead we could execute the search after some delay with a debounce instead of doing it when the user hits enter.
Remove low quality search results. Currently if I search for “Toronto” one of the results is “Luka pod Medníkem, Jílové u Prahy, Luka pod Medníkem, Central Bohemia, Czechia”. If we set a threshold for OSM’s importance score to at least 0.5 we could remove results like this. To be a little safer we do something like only filtering when there are at least 3 results.

I think that's a great idea, but I believe 2 is against the TOS of Nominatim? Been a while since I checked that though.

According ot their usage policy you aren't allowed to do "auto-complete search": https://operations.osmfoundation.org/policies/nominatim/
We might get away with it at least for a while if the de-bounce time is long enough, but then users will be frustrated if it's too long.

Hmm their usage policy also says no more than 1 request per second :P
So maybe it's still too risky but I wonder about debouncing 300ms and also throttling 1s
i.e. the request to nominatim is fired 300ms after the user stops typing. If they start and stop multiple times there is at least 1000ms between each request.


:user-invalid pseudoclass not recognized

Which package(s) are affected?
Lit Core (lit / lit-html / lit-element / reactive-element)
Description
When using the (relatively new) :user-invalid (link to MDN) pseudoclass in lit-CSS, it looks like this is not supported and/or properly typed. When using it inside a regular <style> -tag (so without using Lit) in the same editor (VSCode), it is supported and recognized properly. This is not the case when using it inside Lit CSS.
Reproduction
Apply the following style in a lit-component that renders a <input required /> element (note the required attribute) :
static styles = [
    css`
      input:user-invalid {
        border-color: red;
      }
    `,
];

The red border should not apply initially after rendering. Then, apply focus to the input field, without entering a value. Then, when giving focus to another element, the red border should be applied.
Workaround
I have manually worked around this problem by using other classes.
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
Failing in Lit 3.2.0
Browser/OS/Node environment
Tested in both Edge 128 and Chrome 128.

Lit doesn't do anything with the styles - they're attached to your component as-is. So there's nothing for us to do to support new CSS features.
I made an example in the lit.dev playground that shows it working for me.

Closing this one, since Lit doesn't modify styles. It's likely a browser support issue.


Tracing: Fixed TraceRecorder inclusion problem

Moved conditional inclusion of tracing_tracerecorder.h
from the start of tracing.h to the bottom. This was the
initial placement of this include but it was moved as
part of PR #40126. If this file is included at the
start of tracing.h the TraceRecorder module hooks
will not map correctly and completely breaks
that module.
Signed-off-by: Torbjörn Leksell<EMAIL_ADDRESS>

@tleksell-pe  is this still relevant, I have not noticed it before.

@nashif yes, I just tried it out and verified to problem still exists in v2.7.99 when using the Trace Recorder module.
There is also a compilation error due to the updated syscall hooks which I will sort out by submitting an updated Trace Recorder version that v2.7.99 should pull from. If you want I can amend this PR with such an update so that the Trace Recorder module works again.

@teburd  can you look into this?

This does seem to fix some include ordering that broke in the previous change


Reset Scans

Source information
Reset Scans 1.4.41
Source language
English
Source new URL
https://rspro.xyz/
Other details
Moved from old domain reset-scans.co to new domain rspro.xyz
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

This is not duplicate!, Domain change reset-scans.co to new domain rspro.xyz

By the way, some of their series like Dungeon Reset are only present in their sub-site Reset-Scans.xyz!.


New documentation page contains a link for the wrong Github issue

The following page : http://docs.asp.net/en/latest/mvc/views/dynamic-vs-static.html
contains a link that links to #134 when it should be about Dynamic vs Strongly typed views

Fixed in 9b30420c1aef5e4970e95bbea1131392760546e1.
Thanks for pointing it out

Is this blog post I wrote a while ago relevant?
https://www.jamietech.com/2015/10/14/mvc-view-models-or-viewdata/