Features
- Added full dynamic config for application setup allowing configuration to be set up and modified by Bionics without new Virtual Rack software releases
- With dynamic config the extra environment variables and settings for each application are now shown in the Application create screen
- Virtual Rack and Virtual Rack Technician have been moved to their own services, completely independent on each other. A failure of either service will auto-restart, but will not bring down each other.
- New last line of defence that should Virtual Rack software shutdown but applications are still running, communication with replicated nodes can get status information about the applications (and not fail over if they are still running) while the Virtual Rack software is restarting.
- Ability to set a application “description” which is on top of the application name allowing a description of the service
- Added an ability for 2nd Pairing network. Replication checks are handled via the pairing networks (Pairing Network 1, Pairing Network 2, AOIP network)
- Added the option for each application to set the display order (and thereby LWRP GPIO application) to allow the custom ordering of applications on the screen and logic flows.
- Virtual Rack failover improvements to understand if the pairing network is available but the AOIP (applications) network has failed over and thereby not available, but the host is.
- PTP Domain Clock option can be set (default is 0)
- LWRP shows each application uptime, memory and CPU usage on the APP command
- LWRP shows health as STOPPED when the app is stopped, rather than UNKNOWN
- LWRP shows system uptime and VR uptime in the SYS command
- LWRP shows system overall memory and CPU usage
- Option to enable on the UI the App Health Status to be displayed
- Version number for each application is shown under the application logo
- Improved the Pairing interface to include all elements regarding pairing on the one area, resilance pairing code is also on this page.
- Made clearer the “Restart Virtual Rack Software” button to define that the button only restarts the Virtual Rack rather than the entire appliance
- Added a “All Applications” backup option on the System tab
- Improved the layout of the Network setup screen
- Added an “Application State” which allows API querying of the state of each application on each node, separate to the configuration provided back from the basic running/stopped.
- Added a timeout (15 seconds) to stop applications failing back when failing over if they are slower to start on the starting node
- Added a force shutdown after 20 seconds if the application has been requested to shutdown and it does not shutdown.
- Added new ContainerBasics API call on “ShowContainerSummary” which displays the basic name and application states
- Handle error states for new applications better allowing a cancel option should an application have invalid configuration and allow for re-creating.
- UI fixes on network buttons on the configuration which were not correctly aligned
- Application version updates show the % of download when downloading the version to the local machine
- Backup files now include the application name in the filename of the zip file
- Pairing network(s) can be changed after installation and setup (with pairing active)
- Application stats shows Mbps/Kbps in the last 10-15 seconds on the statistics for the application
- Improved the valid IP address ranges in the application automatic IP suggestions when an application IP range is defined
Fixes (from 1.4.0.37)
- Fix – Application Specific Routes not stored in the backup consistently
- Improvement – Replication was showing as “good” when there was no replication set up. When no replication is set up, this is not shown.
- Fix – Ethernet Subnet value was not consistently saving to the database
- Improvement – LWRP enable / disable no longer requires a restart of Virtual Rack
- Improvement – Improved laggy display when entering IP addresses on new applications
- Fix – restoring of applications and IP addresses at times not displaying correctly against new host adapters (if the host being restored to was not the same as the backup)
- Fix – Backup Application was not showing IP address of the application (even thought it was stopped)
- Fix – Version changing after a restore could cause a re-install of the application.
- Fix – when adding new applications the IP check was not checking IP of the replicated node
- Fix – from the main page sometimes the application “web interface” window would not launch and had to be launched from the application properties window
- Fix – Removing a parked backup application (non primary) would remove the primary.
- Fix – if removing a parked backup application, starting the primary would not consistently work due to the missing backup.
- Fix – ability to force remove a broken mirror server