We are excited to announce v6.1.0 with a complete overhaul for custom fields for a better UI and flow. This and other changes are discussed below.
- The default password for user ubuntu can now be changed from the console menu (previously the password could not be changed). That means you can now apply updates(or do other menu related work) using ssh. Implementation of this new functionality required us to remove the automated login to the menu and you will now need to login to see this menu. (Note: the username is ‘ubuntu’ and the default password is ‘adm!nd42’).
- Root login has been disabled via ssh
- The Traceroute and Ping commands in the appliance manager have been disabled for now as the implementation was not secure. This functionality (only used for support) should return in future versions.
Custom fields have been completely revamped with a much better flow. Previously, custom fields were defined object by object, For example, for device custom fields, you could create a custom field (e.g. Rating) in the Other tab while in the Edit View. This was convenient. However, many customers suggested that, once a custom field is defined, it should show up for all devices. Also, the distinction between the Value and the Value2 field was confusing to many customers.
As a result, we’ve made the following changes:
(1) Custom fields are defined in a separate menu and not in the device (or other object) edit mode.
(2) Once a custom field is defined for a device (or other object), it will appear in the Other tab for all devices and will appear in the view and edit pages for other objects.
Defining custom fields
Custom fields are now created from the Tools >> Custom fields menu. To create a custom field, choose a Type (Text, Numeric, or Date), and choose whether or not it should be Filterable and/or Mandatory. A Filterable custom field is one that can be used as a filter on the device (or other object) list page as shown below…
A Mandatory custom field is one that must have a value in order to save the device (or other object) record as shown below…
Please note that mandatory only applies when editing an object. This is not enforced it via the API or when adding a new device (or other object).
When editing the device or object, you can either pick a value from the dropdown list or you can type in a new value. You will see a date picker widget for fields with a Date type.
Pre-existing custom fields
Any pre-existing custom fields and value will be converted to the new scheme. We have taken away value2 capability as it was perceived as confusing. If you were using value2, the data will be merged into either the value or the notes, depending on the custom field type.
Getting a list of devices by building, room or rack was a bit slow in earlier versions. Those filters have been optimized in this report – but you will need to re-add buildings, rooms or racks in any of your existing reports. Apologies for the inconvenience with this required change.
As part of vServer discovery, you can now discover the KVM/Libvirt host with all the VMs on it.
- Dates were not being saved correctly in reports – now fixed.
- PDU port display order was not working correctly – now fixed.
- Juniper switches as chassis were not being discovered correctly – now fixed
- In network auto-discovery if you entered same End IP as Start IP – CDP/LLDP discovery was not being triggered when selected. Now fixed.
- We have added “re-importable exports” and add tags to bulk actions to all related objects.