Release Notes

v3.5.1

Release date: 9/21/2018

New Features

  • API: Services - Cypher added
  • API: User creation passwordConfirmation requirement removed
  • Appliance: Reduced memory database query overhead for agent comms
  • Backups: Avamar Integration added
  • Bluemix renamed to IBM Cloud
  • Infoblox: Variable support for ext attributes added
  • Instances: Metadata fields added to Edit Instance modal
  • Instances: Post-Provision Metadata and Tags editing
  • Morpheus Agent: Ubuntu 17.10 support added
  • Openstack: Additional support for versioned endpoints added
  • Openstack: Octavia Load Balancer Support added
  • Openstack: Queens support added
  • Option Lists: Authentication added for remote data providers
  • Policies - Policies section added to Administration for managing all Policies.
  • Policies: Budget Policy type Added
  • Policies: Global and User policy levels added
  • PXE: webHost in answer files now forced to http
  • Reports: Workload Summary Report added
  • Softlayer: Washington 6 region added
  • Storage: Storage Browser for NFS, Azure & Alibaba provider types added
  • Tenants: Disable option added for sub-tenants
  • VCD: support for vcd v9
  • VCD: Virtual Machine sync now includes undeployed VMs
  • vCloud Director: Support for v9.x added
  • Veeam: Service detail page added
  • VMware: API session management improvements
  • VMware: Massive cloud sync speed improvements

Fixes

  • Ansible Tower: Fix for Edit Integration
  • Ansible Tower: Fix for removing Ansible Tower Integration from Group or Cloud
  • Approvals: Fix for VM state updating on Instances list page after request is rejected or cancelled
  • Azure: Fix for price plans syncing
  • Backup: AWS backup shows in progress when snapshot limit exceeded
  • Backups: Default Backup Schedule not applied
  • Docker Hosts: Total Storage value fix
  • ESXi: Fix for file cleanup on failed provisions
  • Guidance: Fix for resize action
  • Guidance: Improved core count recommendations
  • Identity Sources: Fix for form reseting back to LDAP on unsuccessful save
  • Identity Sources: Fix for Required Group still applying after removal
  • Instances: Clone: Fix for Cloud selection not being respected
  • Instances: Fix for creating Instance with numbers-only names
  • KVM: Fix for Backup Restore for multi-disk VMs
  • KVM: Fix for Ubuntu 14 backups
  • LB: AVI - SSL shows ‘Select’ instead of ‘No SSL’
  • Library: Layouts: “Min Ram” not enforced when using custom plans
  • Library: Option Lists: Fix for option list with failed validation still creating records
  • Library: Scripts: Fix for WindowsFeature "$Feature$Number" causing scripts to be un-editable
  • Load Balancers: AVI: Fix for edit instance lb setup
  • Load Balancers: AVI: Fix for manually adding Virtual Server
  • Localizations - added message for Venafi delete
  • Networks: Fix for deleting an ACI Integration
  • Nutanix: Fix for automated Domain joins
  • OTC - Docker Host setup fails to complete
  • OTC: Fix for Reconfigures
  • Policies: Fix for issue with Power Schedule Tenant permissions
  • Policies: Fix for Max VMs Policy enforcement
  • Policies: Unable to edit policy assigned to tenant
  • Pricing: Fix for Azure price discrepancy
  • Provisioning: Fix for Cores per socket resetting back to 1 when going back in provisioning form
  • Provisioning: Fix for Price comparison modal for custom images
  • PXE: Fix for deleting kickstart files for subtenants
  • Reports: Fix for 500 error when report generated by deleted user exists
  • Scaling: Fix for NGINX autoscaling
  • Scaling: Fix for Scaling Schedules
  • Subtenants: Removed invalid link to Shared Clouds on Instance Details page
  • User Settings: Fix for unable to set user settings when connected to AD identity source.
  • User Settings: Username uniqueness now scoped to Tenants
  • vCloud Director: Fix for sync error when a vm has no disks
  • Veeam: Fix for Legacy referenceData causes backupServer dropdown to not load
  • Venafi: Fix for deleting integration
  • Venafi: Fix for incorrect subject set when applying cert during provisioning
  • Virtual Images: Removed “Convert” option for synced images

v3.4.2

Release date: 8/23/2018

New Features

  • Amazon: Additional service plans available
  • API & CLI: Instances metadata added
  • AWS: China cn-north-1/Beijing and cn-northwest-1/Ningxia regions added
  • Infoblox: Extended attributes for A and PTR records added
  • Infoblox: Script variable support added for extended attributes
  • Instances: Custom exposed ports are now globally available
  • KVM: VM Actions, MultiDisk, Reconfigure, Apps & Blueprints. Backups/Restore added
  • Morpheus Agent: Ubuntu 17.10 support added
  • PXE: Now force webHost to http for answer files
  • Xen: CUSTOM PORT option added to Xen Cloud Config

Fixes

  • ACI: Fix for deleting an ACI integration
  • Active Directory: Fix for removing Required Group after one is added
  • Approvals: VM status now moves from pending to cancelled/rejected on cancelled/rejected action from approval screen
  • AVI: multiple fixes and improvements
  • Azure: Fix for discrepancy in the prices shown in Morpheus for Azure prices
  • Evars: Fix for environment variables/deployment option values longer than 255 result in 500 error
  • Guidance: Fix for resize action on recommendations
  • Image builder: fix for config issue with plans when custom cpu is enabled
  • Instances: Cloning: Fix for cloud selection
  • LB: AVI: Create Pool - fix for blank monitors field
  • LB: AVI: Nodes: Fix for empty Monitor column
  • LB: Edit AVI - avi cloud field not populating
  • Load Balancers: Fix for Load Balancer for failing to save when multiple ports are available but only on 1 port is configured
  • Monitoring: Fix for updating existing App Checks causing a 500 error
  • Oracle Cloud: Fix for Virtual Image Icon missing
  • Provisioning: Fix for creating instances with names containing only numbers
  • Provisioning: Price comparisons: Fix for custom images not displaying Price comparisons
  • PXE: Fix for subtenant kickstart file deletion
  • Scale Schedules: Fix for schedule execution
  • Seed: Fix for hasNodeMonitors seed error
  • Subtenants: Removed hyperlink on Cloud Name for inaccessible clouds that would result in 500 error
  • Unmanaged VMs: Fix for cores not updated on refresh
  • User Settings: User name uniqueness now scoped to Tenant
  • VCD: Fix for Guest Customization for Windows failing to run.
  • Venafi: Fix for Add Integration from Administration section
  • Venafi: Fix for Details page error
  • Venafi: Fix for subject on certs added during provisioning
  • Venafi: Fix for viewing Certificates
  • Venafi: Instance Settings: Fix for edit cert
  • Virtual Images: Convert option removed for synced images
  • Virtual Images: Fix for deleting failed conversions

v3.5.0

Release date: 7/31/2018

New Features

  • Administration: Added support link white label
  • Analytics: Added Cost by Tenant report
  • Analytics: Added Cost by Group report
  • Analytics: Added Cost by Application report
  • Analytics: Added Cost by Instance report
  • Analytics: Added Cost by Cloud report
  • Analytics: Added Tenant Instance Usage report
  • Analytics: Added metadata filter to reports
  • Ansible: Added Ansible Tower integration
  • API/CLI: Workflows now support custom option types
  • API/CLI: DataStores added
  • API/CLI: Subtenant Groups added
  • API/CLI: Added “taskPhase” for workflow tasks
  • API/CLI: Added CLI login via token
  • API/CLI: Added optimization for virtual image upload
  • API/CLI: Added metadata for instances
  • Backups: Direct Stream to Storage Provider added for VMware, Xen and KVM backups and Image imports.
  • Backups refactored with Schedules, Job, Types, and Services
  • Backups: Zerto Integration added
  • Multicloud object storage backup and archival
  • Blueprints: Added ACI fields to Blueprint and App wizards
  • Cloud Foundry: Added inventory of applications during cloud sync
  • Cloud Foundry: Added support scaling
  • Cloud Foundry: Added sync for build packs
  • Cloud Foundry: Added custom route
  • Plans & Pricing: Prices: Datastore Price Type added
  • KVM: Added KVM migration workflow
  • KVM: Added CEPH storage support
  • KVM: Backup/restore is now possible for local datastores and LVM
  • Library: Debian 9.4 qcow2 image added
  • Instances: Backup type, provider, job, latest, next, added to instance detail page
  • Network: VMware NSX Integration added
  • Option Lists: Tenant visibility added to Option Lists
  • Option Lists: Added realtime sync option
  • Oracle: Added support for different storage types
  • Oracle: Added Oracle Cloud library nodes
  • Oracle: Added ability to upload a local image and provision to Oracle Cloud
  • phpIPAM: Added additional details (description, hostname, owner)
  • Variables: Added tenantSubdomain variable
  • Policies: Backup Creation policy type added
  • Policies: User Creation policy type added
  • Infrastructure: Hosts: Added host OS, Type and Status filters
  • Plans & Pricing: Added Custom Ranges to Service Plans for min/max storage, memory and cores
  • Provisioning: Added ability to toggle between MB and GB for memory settings in provisioning wizard
  • Roles: Added Global Access: Custom option to roles
  • SAML: Added response validation
  • ServiceNow: Added credential validation
  • Storage: Renamed “Object Stores” to “Providers”
  • Storage Providers: Added details page that allows you to browse, upload and delete files
  • Storage Providers: Verify permissions to path on save added
  • Storage Providers: Removed option for Tenants to create local storage providers
  • Storage Providers: Retention policy added
  • Storage Providers: Amazon S3: Added Create Bucket option
  • Users: Subtenant users will no longer be able to login from the main login page without specifying their subdomain
  • Users: Added API token generation for users via UI
  • Virtual Images: Default “force guest customizations” to “on”
  • VMware: Added VMware “Clone to Template” Action
  • VMware: Direct stream Backups added
  • XenServer: Backups don’t offload backup

Fixes

  • Fix for Chef detail section not displaying in app wizard
  • Fix for deployment failure with ARM template copies
  • Fix for Blueprints: broken image for library items with no custom icon
  • Fix for Analytics: Instance Count by Type and Cloud report: Cloud value
  • Fix for Instance Count by Cloud report
  • Fix for ServiceNow Plugin and API issue
  • Fix for web instance types
  • Fix for ServiceNow not listing datastores
  • Fix for issue deleting ServiceNow integration
  • Fix for OpenStack space issue
  • Fix for OpenStack floating IP issue
  • Fix for F5 destination port issue
  • Fix for VMware ServiceNow Plugin
  • Fix for manually deleting F5 pools and nodes
  • Fix for Nutanix VM taking multiple IP slots
  • Fix for PXE answer file
  • Fix for ENI records not being cleaned up in Amazon
  • Fix for tenant delete issues
  • Fix for Nutanix image endpoint
  • Fix for Install Agent flag for Nutanix
  • Fix for OTC missing icons
  • Fix for HCL parsing not saving
  • Fix for CentOS VM conversion issue
  • Fix for Blueprints resource pool
  • Fix for instance provisioning hanging at configure stage
  • Fix for Blueprints not connecting to Azure LB
  • Fix for Option List ignoring SSL errors
  • Fix for OTC duplicate images
  • Fix for changing roles via AD groups
  • Fix for user data in Windows Cloud
  • Fix for provisioning Windows into vCD
  • Fix for Custom Checks
  • Fix for local firewall not working for VM’s
  • Fix for Cloud Foundry and inventoried apps
  • Fix for Cloud Foundry API check type missing logo
  • Fix for Cloud Foundry cloud details
  • Fix for Cloud Foundry orphaned instances and hosts
  • Fix for Instance Inventory Summary
  • Fix for deployment versions not sorting
  • Fix for Archive Snapshots not saving
  • Fix for Alibaba CentOS 6.9 bad layouts
  • Fix for security groups
  • Fix for Hadoop Ports map error
  • Fix for modals not loading
  • Fix for price editing
  • Fix for multidisk component not using virtual image locations
  • Fix for instance name validation
  • Fix for instance type search limited to selected category
  • Fix for adding disks requiring logs
  • Fix for volume addition requiring infrastructure
  • Fix for private hosts visible to tenants
  • Fix for AD login when user OU changes
  • Fix for changing plan not updating volume
  • Fix for order of logs display
  • Fix for cloud not saving user data
  • Fix for network CRUD issues
  • Fix for VMware ‘Clone to Image’ not showing failures
  • Fix for API task ‘deleting’ failing
  • Fix for log parse error
  • Fix for creating app from existing template with no blueprint
  • Fix for Azure ARM parsing error
  • Fix for VMware ‘Clone to Image’ not working for stopped VM’s
  • Fix for billing API
  • Fix for App wizard naming issue
  • Fix for Oracle Cloud Virtual Image icon missing
  • Fix for Venafi integration details page
  • Fix for AVI LB monitors field being blank
  • Fix for Image Builder configuration issue
  • Fix for Veeam integration not being checked by default
  • Fix for Blueprints missing backup locks
  • Fix for error deleting Cloud Foundry service
  • Fix for i18n missing label

v3.4.1

Release date: 7/20/2018

New Features

  • API: Run workflow now allows arbitrary customOptions to be passed
  • API/CLI: Added CLI login via token. login -T <token> can be used instead of requiring a username and password.
  • API/CLI: Added optimizations for Virtual Image uploads
  • API/CLI: Added “taskPhase” for workflow tasks
  • Backups: Direct Stream to Storage Provider added for VMware, Xen and KVM backups and Image imports.
  • Blueprints: Added ACI fields to Blueprints and Apps wizards
  • phpIPAM: Added additional information including description, hostname and owner
  • Policies: Added variable <%= tenantSubdomain %> for Tenant SubDomain value in scripts and naming policies. The SubDomain is used for creating a direct login url in Identity Sources or as a login prefix to identify the tenant i.e. ‘subdomainusername’
  • Puppet: Expanded OS support for Puppet Agent install.
  • Users: User Settings: API Access section added for API & CLI user token generation
  • VMware: Added Clone to Image Instance Action to create new VMware Templates from Instances with corresponding Morpheus Virtual Image record.
  • VMware: Virtual Images: Switched “Force Guest Customizations” to on by default for Windows Virtual Images

Fixes

  • Fix for VMware ovf export timeouts for large images. Impacted offloaded backups, Import as Image actions.
  • Fix for Deployment versions not sorting
  • Fix for disabling ‘Archive Snapshots’ flag on Storage Providers not saving. When executing backups, the ‘Archive Snapshots’ flag enables ovf export of VMware snapshots to default or specified backup Storage Provider and removes the snapshot in VMware. If disabled, backup jobs will only trigger and leave snapshots in VMware.
  • Fix for Active Directory user login when users OU has been changed
  • Fix for duplicate Alibaba CentOS 6.9 layouts
  • Fix for Azure: ARM Templates copyIndex parsing errors
  • Fix for Security Groups with Source Type set to All
  • Fix for Actions: Reconfigure modal not loading in Infrastructure -> Hosts Section
  • Fix for Instance Name uniqueness validation in provisioning Wizard
  • Reverted Provision Wizard: Instance Type search being limited to selected category
  • Fix for adding disks requiring Logs: Read or Full Role permissions
  • Fix for volume addition requiring Infrastructure - Storage: Read or Full Role permissions
  • Fix for Master Tenant private KVM Host Subtenant visibility
  • Fix for changing plan not updating volume size for Nutanix Instance Type until image is selected
  • Fix for adding AVI load balancer integration.
  • Fix for API: /groups/:id/update-zones removal of zone not passed in the zones parameter
  • Fix for Apps wizard not loading when User Role permission set to Provisioning: Blueprints: None
  • Fix for Logs: Date parsing error when Windows Event logs are localized

v3.4.0

Release Date: 6/19/2018

Important

Morpheus v3.4.0 adds support for subtenant users to login via the main tenant url using subtenant id or subdomain prefix, ie subtentantId\username or subdomain\username. Subtenant local users will no longer be able to login from main login url without using subtenant id or subdomain prefix. Tenant subdomain can be defined by editing the Tenant settings and updating the SUBDOMAIN field.

New Features

  • API/CLI: DataStores added
  • API/CLI: Salt command options added
  • API/CLI: Subtenant Groups added
  • API/CLI: Workflows now support custom option types
  • Blueprints: ARM template Git integration added
  • Currency: Conversion settings added to Administration -> Settings.
  • Datastores: Storage > Datastores capacity column now hidden when “Hide Datastore Stats On Selection” is enabled
  • Identity Sources: Subtenant users can now login from the main login url using subtenant name or id prefix, including users created from Identity Source Integrations.
  • KVM: Added OnApp migration support
  • Library: CentOS 7.5 qcow2 image added
  • Library: Ubuntu 16.04, 18.04 qcow2 images added
  • Policies: User Creation Policy added
  • Provisioning: Added default datastore for additional disks to match first disk
  • Provisioning: Additional Network Interface types now default to match first Interface type
  • SAML: Validation configuration options added
  • Storage Providers: Verify permissions to path on save added

Note

In 3.4.0+ currency conversion data users will need to provide an open exchange or fixer.io api key under Administration -> Settings.

Fixes

  • Fix for Chef detail section hidden in UI
  • Fix for Cost by Cloud error
  • Fix for incorrect Instance provisioning status when using copies with ARM Templates
  • Fix for broken image issue for library items with no custom icon
  • Fix for Instance Type Count - By Clouds Value in Analytics
  • Fix for Instance Count by Cloud Group Count Value in Analytics
  • Fix for CLI Bad Request issue when creating a cloud
  • Fix for Web Instance Types to be scalable
  • Fix for Cost Month to Date report
  • Fix for ServiceNow listed Datastores
  • Fix for Cloud Init enabled in Images
  • Fix for KVM provisioning issue
  • Fix for i18n missing message
  • Fix for App Wizard Amazon validation issue
  • Fix for space issue with Openstack
  • Fix for postgreSQL issue with BluemixCF
  • Fix for Clouds stuck in deleting when removing
  • Fix for issue with adding/editing local storage objects
  • Fix for OpenStack Floating IP’s being required
  • Fix for F5 destination port issue
  • Fix for Storage Object issue with NFS
  • Fix for instance Wizard Issues
  • Fix for ServiceNow Plugin unable to provision VMware instance
  • Fix for ServiceNow Plugin Datastores duplicate options
  • Fix for F5 error deleting Pools and Nodes
  • Fix for missing scale tab for VCD Instances
  • Fix for KVM SSH fail after stop/start
  • Fix for App Wizard form update when changing cloud
  • Fix for ESXI Debian 8.8 failing to provision
  • Fix for KVM provision failing on self managed host
  • Fix for OEL build fail if more than 3 disks are requested during provisioning
  • Fix for Open Telekom Cloud provisioning issue
  • Fix for Cost by Cloud projected values
  • Fix for Nutanix duplicate IP’s when using IP Pools
  • Fix for PXE answer file not getting generated
  • Fix for ENI records not being cleaned up (Amazon)
  • Fix for Tenant delete issues
  • Fix for Nutanix sysprep unattend.xml passwords
  • Fix for “Install Agent” Flag for Nutanix Images
  • Fix for missing image icons
  • Fix Terraform HCL parsing
  • Fix for some converted-to-managed VM’s having docker check type
  • Fix for unnecessary resource pool request
  • Fix for vmToolsInstalled: no such property

Morpheus v3.4.0 is available in the Downloads section of morpheushub.com.

v3.3.2

Release Date 5/24/2018

Important

If upgrading from versions earlier than 3.2.0 please follow the 3.2.0+ upgrade instructions below the release notes.

Important

Appliance Elasticsearch communication in 3.3.1+ switches from transport protocol 9300 port to http 9200

3.3.2 New Features

  • Agent: Support for Ubuntu 18.04 LTS added
  • Alibaba: Docker Host support added
  • Alibaba: Virtual Image upload added
  • API: Virtual Image Upload via url added
  • API: Identity Source added
  • API: Instance config and volume details added
  • Apps: New default Blueprint logos
  • Auditing: Now support the ability to export the audit log from user interactions to a SIEM tool
  • Auditing: AuditLogService added to morpheus-ui logs
  • Azure: Scale Set threshold validation added
  • Bluecat: New method added for instant dns record deployments
  • Blueprints: Templates have been renamed to Blueprints
  • Blueprints: Default Blueprint type option added to Administration - Provisioning
  • Blueprints: ARM: Support for “concat” and “copies” added
  • Blueprints: Terraform: AWS support added
  • Blueprints: Terraform: Support for variable instance names added
  • Blueprints: Terraform: Oracle Cloud support added
  • Blueprints: Terraform failures surface on the app details page
  • Blueprints: Terraform: Variables now surface in App wizard
  • Global Search: Quick results added to header search
  • Infoblox: Support for custom extended attributes added
  • Instance Wizard: Code reworked for optimizations
  • Infrastructure: Updated delete dialog text
  • Keys & Certs: Services section added
  • Keys & Certs: Venafi service added
  • Keys & Certs: EC type public key support added
  • Keys & Certs: Upload keypair option added
  • Kubernetes: Ports no longer need to be defined on custom library items
  • Kubernetes: Added icon for Kubernetes instance type
  • KVM: Caching virtual machines now include metadata on network and storage volumes attached to a KVM VM
  • KVM: Re-factored LVM implementation of KVM to allocate a volume per disk instead of nested QCOW2 files
  • KVM: VM Inventory added
  • Network Services: phpIPAM integration added
  • Plans & Pricing: Max disk limit added to plans
  • Reports: Tenant filtering added to Usage Reports
  • Reports: Cost Reports added with Application, Cloud, Group, Instance and Tenant Cost Reports
  • Reports: Usage Reports: Tenant Usage Report Added
  • Roles: Trust Services permission added. Controls Infra > Keys & Certs > Services access and Admin > Integrations > Add (trust options)
  • ServiceNow: Kingston certification added for Morpheus SNOW Plugin
  • Users: Password confirmation fields added for Linux and Windows users
  • vCloud Director: Custom Plans support added
  • vCloud Director: Docker Host support added
  • vCloud Director: Reconfigure added
  • VMware: Instance Notes sync added

3.3.2 Fixes

  • Fix for tenant delete that fails if an app with custom tiers is used to create an app
  • Fix for Alibaba Cloud sync delay
  • Fix for Alibaba release EIP not respected when deleting VM
  • Fix for Alibaba network being recreated on sync
  • Fix for Alibaba instance validation not completing
  • Fix for Alibaba instance name validation
  • Fix for Xen snapshots not being cleaned up
  • Fix to show existing VM’s in Alibaba inventory
  • Fix for deleting SCVMM cloud
  • Fix for style issue with load balancer advanced options
  • Fix for Veeam Templates/Jobs not populating
  • Fix for Oracle Cloud VM. VM will restart after it is resized
  • Fix for VMware storage containers where adding a controller would clear the volume type
  • Fix for extra backup that’s created on an Azure Scale Set instance
  • Fix for Azure Scale Set instance data issues
  • Fix for MacStadium creating a duplicate VM after cloud sync
  • Fix for Alibaba cloud not cleaning security groups when deleted
  • Fix for Oracle Cloud users not being created for non-cloudinit images
  • Fix for Service Now incident level update
  • Fix for KVM multidisk provision
  • Fix for Bluemix Platform not cleaning up service library items
  • Fix for Alibaba not using available EIP
  • Fix for missing price component
  • Fix for Kubernetes host cert issue
  • Fix for Windows Cloudbase-init userdata and DNS client settings missing
  • Fix for wrong Ethernet adapter type being set on uploaded Windows images
  • Fix for Alibaba backups not getting deleted when instance is deleted
  • Fix for KVM provision not respecting host selection
  • Fix for Cloud Foundry user permissions
  • Fix for manual KVM host deletion error
  • Fix for permissions on default storage path
  • Fix for Openstack cloud service plans assigned to subtenants
  • Fix for default instance deployment
  • Fix for Alibaba ‘preserve volume’ not working on delete
  • Fix for system instance type: macOS
  • Fix for expired backup archived not deleting on S3
  • Fix for unintended firewall evaluation when using shared resource in an app
  • Fix for KVM App/Template issues
  • Fix for Last Deployment: Never Deployment phrasing
  • Fix for CentOS 7.2 Answer File in boot configurator for PXE

Important

If upgrading from versions earlier than 3.2.0 please follow the 3.2.0+ upgrade instructions below

3.2.0+ Upgrades

Overview

Upgrading from previous versions of Morpheus to 3.2.0 or later requires upgrading ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires an export and import of Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0 will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one or distributed high availability.

Morpheus All-In-One

This deployment configuration is the default mode for Morpheus and contains a single ElasticSearch instance on the appliance. The migration steps are as follows:

  1. Login to your appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
  2. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem
  3. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc
  4. Stop the Morpheus application by executing morpheus-ctl stop morpheus-ui, this will stop creating new documents in ElasticSearch.
  5. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://localhost:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.
  6. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.
  7. You can start Morpheus at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

Note

Make sure that Morpheus is fully started before moving on to the next step.

Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://localhost:9200 /root/es_backup, substitute the path you used during the backup if different from above.

Note

The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

Morpheus Distributed High Availability

This deployment configuration assumes that you manage an ElasticSearch cluster externally from Morpheus. The steps for upgrading ElasticSearch from 1.x to 5.x are located on the ElasticSearch website. Run the following from a “master” appliance, it has the required Ruby installed in the Morpheus full stack directory. Ensure that the appliance can reach at least one ElasticSearch node over port 9200 (http). Also, make sure thre is enough disk space to hold the exported data on the appliance.

  1. Login to the master appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory.

  2. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH

  3. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem

  4. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc

  5. Stop all the Morpheus application instances by executing morpheus-ctl stop morpheus-ui on each appliance node, this will stop creating new documents in ElasticSearch.

  6. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://xxx.xxx.xxx.xxx:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.

    Note

    The next steps are done on the ElasticSearch node(s).

  7. Stop ElasticSearch on each node.

  8. Backup the ElasticSearch config directory for each node, normally located at /etc/elasticsearch/.

  9. Since the index data between 1.x and 5.x is incompatible, delete the data from the data directory normally located at /var/lib/elasticsearch. To prepare for future upgrades make sure that you delete the cluster name directory as well, ie morpheus.

  10. Upgrade ElasticSearch, use the method that best fits your situation ie pkg, tar, or zip.

  11. Remove unsupported configuration from the existing ElasticSearch configuration

    • index.number_of_shards
    • index.number_of_replicas
    • discovery.zen.ping.multicast
  12. Replace or update the package installed configuration with your existing configuration if it was overwritten.

    • Set network.host or network.bind_ip and network.publish_ip accordingly to your network configuration.
  13. Start ElasticSearch on each node and form a new cluster.

  14. Verify you have a good cluster by executing: curl http://xxx.xxx.xxx.xxx:9200/_cluster/health?pretty, check for the number of nodes and that you have a green status.

    Note

    The next steps are done on the Morpheus “master” node.

  15. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  16. You can start Morpheus on the master node only at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

    Note

    Make sure that Morpheus is fully started before moving on to the next step.

  17. Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://xxx.xxx.xxx.xxx:9200 /root/es_backup, substitute the path you used during the backup if different from above.

    Note

    The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

  18. Move to the next Morpheus appliance and upgrade it by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  19. Start Morpheus by executing: morpheus-ctl start morpheus-ui.

  20. Upgrade the rest of the Morpheus appliances in your environment.

v3.3.1

Release Date 4/15/2018

Important

If upgrading from versions earlier than 3.2.0 please follow the 3.2.0+ upgrade instructions below the release notes.

Important

Appliance Elasticsearch communication in 3.3.1 switches from transport protocol 9300 port to http 9200

3.3.1 New Features

  • Azure Scale Sets support added
  • Azure: Network Security Group selection no longer required
  • Bluecat: Network filter option added to Integration settings
  • Cypher: TFvars added for Terraform. Allows variable files stored in cypher to be used with Terraform Templates.
  • Global Search: Apps & Library Items categories added
  • Infoblox: Host and Zone Record Sync added
  • Infoblox: Manual Host and Zone record creation, deletion and reservations added
  • Infrastructure- Hosts: Typing DELETE now required when removing infrastructure
  • Instances: Mute Checks option added on shutdown
  • Instance Details: Last Deployment Name and Version added
  • KeyPairs: Validation and conversion service added
  • Library: Morpheus Node Types for CentOS 7.3 for Nutanix and ESXi added
  • Load Balancers: F5 Pool Creation Validation, VIP Creation Validation, VIP Creation SSL Profile and Remove Policies Options added
  • Morpheus Appliance: Major Speed and resource utilization improvements. Please note Appliance Elasticsearch communication in 3.3.1 switches from transport protocol 9300 port to http 9200
  • Networks- IP Pools: Used and Total IPs progress bar added
  • Networks- IP Pools: IP Pool Detail Pages added
  • Networks - Services: IPAM Service Detail Pages added with Host Record Grids and List views.
  • Networks - IP Pools: Created date and created by user tracking added to IP assignments.
  • Networks: Domain Detail Pages added
  • Networks - Services: DNS Services Zone Record sync added
  • Oracle Cloud: Ability to provision by OCID added
  • Oracle Cloud: Multiple Compartment support and default Compartment selection added
  • Oracle Cloud: Provisioning improvements
  • Oracle Cloud: Reconfigure added
  • Plans: Cores Per Socket specification added to VMware type plans
  • Provisioning - Automation: Scale Thresholds section added. Scale Thresholds can be pre-defined and selected when scaling Instances.
  • Reports: Costs added to Virtual Machine Inventory Summary report
  • Reports: Provision Times added to exported Virtual Machine Inventory Summary reports
  • Templates: TFvars selection added
  • VCD: Custom Library Nodes added
  • VCD: Virtual Image upload added
  • Virtual Images: Minimum Ram Requirement field added. Limits which plans will be available for selection at provision time.

3.3.1 Fixes

  • Fix for Windows domain join guest user and password not being set
  • Fix for Error when setting custom group access on subtenant role
  • Fix for Favicon resetting to default on whitelabeling
  • Analytics Group and Cloud filter fix
  • Fix for API: groups list timing out in high usage environments
  • Fix for Nutanix Cloudbase-Init metadata
  • Fix for editing and saving Bluecat Integration creating duplicate networks
  • Fix for Baremetal: Convert to Managed - creating docker check
  • Fix for synced service plans remaining after some cloud deletions
  • Fix for KeyPairs 403 error when invalid KeyPair exists
  • Fix for Azure Managed Disk error when no Azure Storage Accounts exists
  • Fix for NetScaler: unable to add load balancer when using SSL
  • Fix for VMware and Nutanix duplicate VM records
  • Fix for VMware parent host record sync
  • Fix for error creating an App with Existing Instance
  • Fix for edit option shown in sub-tenant groups cloud tab on clouds owned by master tenant
  • Auto cleanup of Azure Deployment records added

Important

If upgrading from versions earlier than 3.2.0 please follow the 3.2.0+ upgrade instructions below

3.2.0+ Upgrades

Overview

Upgrading from previous versions of Morpheus to 3.2.0 or later requires upgrading ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires an export and import of Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0 will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one or distributed high availability.

Morpheus All-In-One

This deployment configuration is the default mode for Morpheus and contains a single ElasticSearch instance on the appliance. The migration steps are as follows:

  1. Login to your appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
  2. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem
  3. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc
  4. Stop the Morpheus application by executing morpheus-ctl stop morpheus-ui, this will stop creating new documents in ElasticSearch.
  5. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://localhost:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.
  6. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.
  7. You can start Morpheus at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

Note

Make sure that Morpheus is fully started before moving on to the next step.

Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://localhost:9200 /root/es_backup, substitute the path you used during the backup if different from above.

Note

The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

Morpheus Distributed High Availability

This deployment configuration assumes that you manage an ElasticSearch cluster externally from Morpheus. The steps for upgrading ElasticSearch from 1.x to 5.x are located on the ElasticSearch website. Run the following from a “master” appliance, it has the required Ruby installed in the Morpheus full stack directory. Ensure that the appliance can reach at least one ElasticSearch node over port 9200 (http). Also, make sure thre is enough disk space to hold the exported data on the appliance.

  1. Login to the master appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory.

  2. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH

  3. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem

  4. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc

  5. Stop all the Morpheus application instances by executing morpheus-ctl stop morpheus-ui on each appliance node, this will stop creating new documents in ElasticSearch.

  6. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://xxx.xxx.xxx.xxx:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.

    Note

    The next steps are done on the ElasticSearch node(s).

  7. Stop ElasticSearch on each node.

  8. Backup the ElasticSearch config directory for each node, normally located at /etc/elasticsearch/.

  9. Since the index data between 1.x and 5.x is incompatible, delete the data from the data directory normally located at /var/lib/elasticsearch. To prepare for future upgrades make sure that you delete the cluster name directory as well, ie morpheus.

  10. Upgrade ElasticSearch, use the method that best fits your situation ie pkg, tar, or zip.

  11. Remove unsupported configuration from the existing ElasticSearch configuration

    • index.number_of_shards
    • index.number_of_replicas
    • discovery.zen.ping.multicast
  12. Replace or update the package installed configuration with your existing configuration if it was overwritten.

    • Set network.host or network.bind_ip and network.publish_ip accordingly to your network configuration.
  13. Start ElasticSearch on each node and form a new cluster.

  14. Verify you have a good cluster by executing: curl http://xxx.xxx.xxx.xxx:9200/_cluster/health?pretty, check for the number of nodes and that you have a green status.

    Note

    The next steps are done on the Morpheus “master” node.

  15. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  16. You can start Morpheus on the master node only at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

    Note

    Make sure that Morpheus is fully started before moving on to the next step.

  17. Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://xxx.xxx.xxx.xxx:9200 /root/es_backup, substitute the path you used during the backup if different from above.

    Note

    The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

  18. Move to the next Morpheus appliance and upgrade it by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  19. Start Morpheus by executing: morpheus-ctl start morpheus-ui.

  20. Upgrade the rest of the Morpheus appliances in your environment.

v3.3.0

Release Date 3/20/2018

Important

Morpheus v3.2.0+ introduces Global Search, which requires an Elasticsearch upgrade. Upgrading from previous versions of Morpheus to a 3.2.0 or later requires you to upgrade ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires you to export and import your Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0+ will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one, distributed high availability, or Morpheus clustered appliances.

Please refer to upgrade instructions below the release notes.

Note

Upgrading from 3.2.0 to 3.3.0 does not require an Elasticsearch upgrade.

New Features

  • Clouds: Oracle Cloud added
  • Apps & Blueprints: ARM Blueprints added
  • Apps & Blueprints: Teraform Blueprints
  • Localization: Spanish, French, German translations added
  • Azure: All provisioning now utilizes ARM Blueprints
  • Apps & Blueprints: Blueprint type and icons added
  • Hosts: RPC Port now configurable on Edit -> Host
  • API: Scheduling added
  • KeyPairs: Additional Keypair Validation added
  • Administration -> Provisioning -> Settings: Require Environment Selection Flag added
  • Administration -> Provisioning -> Environments: Actions - Hide added for Environments
  • Identity Sources: SAML error handling enhancements
  • VMware: Task customization domain join enhancements

Fixes

  • Fix for Static IP address filed losing focus in App Blueprints
  • Updates to UI Header for Localizations
  • Fix for error on searching for Cloud Foundry marketplace service
  • Fix for VMware 2 Disk Blueprints where 2nd disk is named *_2.vmdk
  • Fix for Instance Configuration dropdown sorted randomly
  • Fix for VMware Image sync duplications

Important

For upgrades to 3.2.0+ please follow the 3.2.0+ upgrade instructions below!

3.2.0+ Upgrades

Overview

Upgrading from previous versions of Morpheus to 3.2.0 or later requires upgrading ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires an export and import of Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0 will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one or distributed high availability.

Morpheus All-In-One

This deployment configuration is the default mode for Morpheus and contains a single ElasticSearch instance on the appliance. The migration steps are as follows:

  1. Login to your appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
  2. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem
  3. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc
  4. Stop the Morpheus application by executing morpheus-ctl stop morpheus-ui, this will stop creating new documents in ElasticSearch.
  5. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://localhost:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.
  6. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.
  7. You can start Morpheus at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

Note

Make sure that Morpheus is fully started before moving on to the next step.

Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://localhost:9200 /root/es_backup, substitute the path you used during the backup if different from above.

Note

The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

Morpheus Distributed High Availability

This deployment configuration assumes that you manage an ElasticSearch cluster externally from Morpheus. The steps for upgrading ElasticSearch from 1.x to 5.x are located on the ElasticSearch website. Run the following from a “master” appliance, it has the required Ruby installed in the Morpheus full stack directory. Ensure that the appliance can reach at least one ElasticSearch node over port 9200 (http). Also, make sure thre is enough disk space to hold the exported data on the appliance.

  1. Login to the master appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory.

  2. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH

  3. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem

  4. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc

  5. Stop all the Morpheus application instances by executing morpheus-ctl stop morpheus-ui on each appliance node, this will stop creating new documents in ElasticSearch.

  6. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://xxx.xxx.xxx.xxx:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.

    Note

    The next steps are done on the ElasticSearch node(s).

  7. Stop ElasticSearch on each node.

  8. Backup the ElasticSearch config directory for each node, normally located at /etc/elasticsearch/.

  9. Since the index data between 1.x and 5.x is incompatible, delete the data from the data directory normally located at /var/lib/elasticsearch. To prepare for future upgrades make sure that you delete the cluster name directory as well, ie morpheus.

  10. Upgrade ElasticSearch, use the method that best fits your situation ie pkg, tar, or zip.

  11. Remove unsupported configuration from the existing ElasticSearch configuration

    • index.number_of_shards
    • index.number_of_replicas
    • discovery.zen.ping.multicast
  12. Replace or update the package installed configuration with your existing configuration if it was overwritten.

    • Set network.host or network.bind_ip and network.publish_ip accordingly to your network configuration.
  13. Start ElasticSearch on each node and form a new cluster.

  14. Verify you have a good cluster by executing: curl http://xxx.xxx.xxx.xxx:9200/_cluster/health?pretty, check for the number of nodes and that you have a green status.

    Note

    The next steps are done on the Morpheus “master” node.

  15. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  16. You can start Morpheus on the master node only at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

    Note

    Make sure that Morpheus is fully started before moving on to the next step.

  17. Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://xxx.xxx.xxx.xxx:9200 /root/es_backup, substitute the path you used during the backup if different from above.

    Note

    The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

  18. Move to the next Morpheus appliance and upgrade it by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  19. Start Morpheus by executing: morpheus-ctl start morpheus-ui.

  20. Upgrade the rest of the Morpheus appliances in your environment.

v3.2.2

Release Date 5/2/2018

Important

Morpheus v3.2.0+ introduces Global Search, which requires an Elasticsearch upgrade. Upgrading from previous versions of Morpheus to a 3.2.0 or later requires you to upgrade ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires you to export and import your Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0+ will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one, distributed high availability, or Morpheus clustered appliances.

Please refer to upgrade instructions below the release notes.

New Features

  • Alibaba - Docker Host provisioning added
  • ServiceNow: Kingston support for SNOW Morpheus plug-in

Fixes

  • Apps: Fix for unintended firewall evaluation when using shared resource in an app
  • Backups: Fix for expired backup archives not deleting on S3 backup storage provider
  • Billing: Fix for billing API not returning usages for zones that no longer exist
  • Cloudbase-init: Fix for user data and DNS client settings missing
  • Cloud Foundry: Better handling when creating a space with a user that does not have the correct permissions
  • Deployments: Fix for deployment modal automatically selecting the last deployment used
  • F5 Load Balancer: Fix for syncing in duplicate unmanaged virtual servers
  • Load Balancers: Fix for edit modal typo & styling issue
  • MacStadium: Fix for duplicate Virtual Machines
  • NetScaler: Fix for adding load balancer when using SSL
  • Policies: Lifecycle extension message fixes
  • Pricing: Fix for platform price missing at provisioning stage
  • SCVMM: Fix for cloud deletion
  • Veeam: Fix for Templates/Jobs not populating
  • VMware: Fix for VM hypervisor host sync
  • Windows: Fix for wrong Ethernet adapter type for being set on uploaded windows images.
  • Xen: Fix for snapshots not being cleaned up

Important

For upgrades to 3.2.0 please follow the 3.2.0 upgrade instructions below!

3.2.0+ Upgrades

Overview

Upgrading from previous versions of Morpheus to 3.2.0 or later requires upgrading ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires an export and import of Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0 will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one or distributed high availability.

Morpheus All-In-One

This deployment configuration is the default mode for Morpheus and contains a single ElasticSearch instance on the appliance. The migration steps are as follows:

  1. Login to your appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
  2. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem
  3. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc
  4. Stop the Morpheus application by executing morpheus-ctl stop morpheus-ui, this will stop creating new documents in ElasticSearch.
  5. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://localhost:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.
  6. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.
  7. You can start Morpheus at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

Note

Make sure that Morpheus is fully started before moving on to the next step.

Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://localhost:9200 /root/es_backup, substitute the path you used during the backup if different from above.

Note

The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

Morpheus Distributed High Availability

This deployment configuration assumes that you manage an ElasticSearch cluster externally from Morpheus. The steps for upgrading ElasticSearch from 1.x to 5.x are located on the ElasticSearch website. Run the following from a “master” appliance, it has the required Ruby installed in the Morpheus full stack directory. Ensure that the appliance can reach at least one ElasticSearch node over port 9200 (http). Also, make sure thre is enough disk space to hold the exported data on the appliance.

  1. Login to the master appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory.

  2. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH

  3. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem

  4. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc

  5. Stop all the Morpheus application instances by executing morpheus-ctl stop morpheus-ui on each appliance node, this will stop creating new documents in ElasticSearch.

  6. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://xxx.xxx.xxx.xxx:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.

    Note

    The next steps are done on the ElasticSearch node(s).

  7. Stop ElasticSearch on each node.

  8. Backup the ElasticSearch config directory for each node, normally located at /etc/elasticsearch/.

  9. Since the index data between 1.x and 5.x is incompatible, delete the data from the data directory normally located at /var/lib/elasticsearch. To prepare for future upgrades make sure that you delete the cluster name directory as well, ie morpheus.

  10. Upgrade ElasticSearch, use the method that best fits your situation ie pkg, tar, or zip.

  11. Remove unsupported configuration from the existing ElasticSearch configuration

    • index.number_of_shards
    • index.number_of_replicas
    • discovery.zen.ping.multicast
  12. Replace or update the package installed configuration with your existing configuration if it was overwritten.

    • Set network.host or network.bind_ip and network.publish_ip accordingly to your network configuration.
  13. Start ElasticSearch on each node and form a new cluster.

  14. Verify you have a good cluster by executing: curl http://xxx.xxx.xxx.xxx:9200/_cluster/health?pretty, check for the number of nodes and that you have a green status.

    Note

    The next steps are done on the Morpheus “master” node.

  15. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  16. You can start Morpheus on the master node only at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

    Note

    Make sure that Morpheus is fully started before moving on to the next step.

  17. Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://xxx.xxx.xxx.xxx:9200 /root/es_backup, substitute the path you used during the backup if different from above.

    Note

    The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

  18. Move to the next Morpheus appliance and upgrade it by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  19. Start Morpheus by executing: morpheus-ctl start morpheus-ui.

  20. Upgrade the rest of the Morpheus appliances in your environment.

v3.2.1

Release Date 3/23/2018

Important

Morpheus v3.2.0+ introduces Global Search, which requires an Elasticsearch upgrade. Upgrading from previous versions of Morpheus to a 3.2.0 or later requires you to upgrade ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires you to export and import your Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0+ will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one, distributed high availability, or Morpheus clustered appliances.

Please refer to upgrade instructions below the release notes.

New Features

  • Instances: Last Deployment Name/Version added to Instance list & details sections
  • Library: Minimum Memory field added to Layouts. Only the service plan options meeting this requirement will be displayed during provisioning.
  • Load Balancers: F5- VIP Creation Validation added
  • Load Balancers: F5- Pool Creation Validation added
  • Load Balancers: F5- SSL Profile Option during VIP Creation added
  • Load Balancers: F5- SSL Remove Policies Option during VIP Creation added
  • Networks: Network filter added to Bluecat Service.
  • Virtual Images: Minimum Memory field add to Virtual Images. Only the service plan options meeting this requirement will be displayed during provisioning. Note this will override any memory requirement set on the virtual image.
  • VMware: Cores per Socket Added to VMware type Service Plans
  • VMware: Sync time optimizations & memory utilization improvements

Fixes

  • Fix for VMware MV inventory issue when VM’s exist with same name in different resource pools
  • Fix for setting custom group access on legacy subtenant role.
  • Fix for white labeling favicon resetting to default
  • Fix for Analytics filter issues when filtering by Cloud or Group
  • Fix for API & CLI groups list timeouts in high usage environments
  • Fix for Nutanix Cloudbase-init metadata
  • Fix for Instance Removal from CLI not recording user
  • Fix for Bare metal: Convert to Managed creating Docker type check
  • Fix for Cloud Delete: service plan foreign key constraint prevents deleting of service plans during cloud delete
  • Fix for the global search HA replica count being set to 0 instead of 1

Important

For upgrades to 3.2.0 please follow the 3.2.0 upgrade instructions below!

3.2.0+ Upgrades

Overview

Upgrading from previous versions of Morpheus to 3.2.0 or later requires upgrading ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires an export and import of Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0 will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one or distributed high availability.

Morpheus All-In-One

This deployment configuration is the default mode for Morpheus and contains a single ElasticSearch instance on the appliance. The migration steps are as follows:

  1. Login to your appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
  2. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem
  3. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc
  4. Stop the Morpheus application by executing morpheus-ctl stop morpheus-ui, this will stop creating new documents in ElasticSearch.
  5. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://localhost:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.
  6. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.
  7. You can start Morpheus at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

Note

Make sure that Morpheus is fully started before moving on to the next step.

Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://localhost:9200 /root/es_backup, substitute the path you used during the backup if different from above.

Note

The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

Morpheus Distributed High Availability

This deployment configuration assumes that you manage an ElasticSearch cluster externally from Morpheus. The steps for upgrading ElasticSearch from 1.x to 5.x are located on the ElasticSearch website. Run the following from a “master” appliance, it has the required Ruby installed in the Morpheus full stack directory. Ensure that the appliance can reach at least one ElasticSearch node over port 9200 (http). Also, make sure thre is enough disk space to hold the exported data on the appliance.

  1. Login to the master appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory.

  2. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH

  3. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem

  4. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc

  5. Stop all the Morpheus application instances by executing morpheus-ctl stop morpheus-ui on each appliance node, this will stop creating new documents in ElasticSearch.

  6. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://xxx.xxx.xxx.xxx:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.

    Note

    The next steps are done on the ElasticSearch node(s).

  7. Stop ElasticSearch on each node.

  8. Backup the ElasticSearch config directory for each node, normally located at /etc/elasticsearch/.

  9. Since the index data between 1.x and 5.x is incompatible, delete the data from the data directory normally located at /var/lib/elasticsearch. To prepare for future upgrades make sure that you delete the cluster name directory as well, ie morpheus.

  10. Upgrade ElasticSearch, use the method that best fits your situation ie pkg, tar, or zip.

  11. Remove unsupported configuration from the existing ElasticSearch configuration

    • index.number_of_shards
    • index.number_of_replicas
    • discovery.zen.ping.multicast
  12. Replace or update the package installed configuration with your existing configuration if it was overwritten.

    • Set network.host or network.bind_ip and network.publish_ip accordingly to your network configuration.
  13. Start ElasticSearch on each node and form a new cluster.

  14. Verify you have a good cluster by executing: curl http://xxx.xxx.xxx.xxx:9200/_cluster/health?pretty, check for the number of nodes and that you have a green status.

    Note

    The next steps are done on the Morpheus “master” node.

  15. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  16. You can start Morpheus on the master node only at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

    Note

    Make sure that Morpheus is fully started before moving on to the next step.

  17. Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://xxx.xxx.xxx.xxx:9200 /root/es_backup, substitute the path you used during the backup if different from above.

    Note

    The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

  18. Move to the next Morpheus appliance and upgrade it by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  19. Start Morpheus by executing: morpheus-ctl start morpheus-ui.

  20. Upgrade the rest of the Morpheus appliances in your environment.

v3.2.0

Important

Morpheus v3.2.0+ introduces Global Search, which requires an Elasticsearch upgrade. Upgrading from previous versions of Morpheus to a 3.2.0 or later requires you to upgrade ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires you to export and import your Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0+ will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one, distributed high availability, or Morpheus clustered appliances.

Please refer to upgrade instructions below the release notes.

New Features

  • New Global Search: All of Morpheus can now be searched from the header or at /search.
  • UI: Updated header including Global Search, User Avatar, Morpheus Support/Documentation links
  • Active Directory: Nested Group Support added
  • AWS: GovCloud (West) Region added
  • Bluecat: Sync and DNS Improvements
  • Domains: Workflows added
  • Domains: Guest User setting added
  • Library: Morpheus CentOS 7.3 for Azure, Softlayer, Bluemix, DigitalOcean, Xen added
  • Library: Templates renamed File Templates
  • Policies: Sequence numbers no longer reused once freed
  • Power Schedule: Total number of hours saved per month added
  • Provisioning: Additional error messages surfaced
  • SCVMM: Support for static ip pools added
  • SCVMM : Inventory existing VMs added
  • VMware: Support for VMware 6.5 Hypervisor Console
  • Windows Agent: TLS 1.2 Support added
  • CLI: Monitoring - Apps added
  • CLI: Monitoring - Groups added
  • CLI: User Groups added

Fixes

  • Alibaba: Fix for Release Elastic IP
  • Alibaba: Fix for Edit Cloud not populating region/vpc
  • Alibaba: Fix for Networks recreated on sync
  • Alibaba: Fix for issue deleting VM that has backups
  • Alibaba: Fix for Elastic IP not surfaced in morpheus
  • Hosts: Fix for Add host modal in sub-tenant is not respecting user role group permissions
  • Hosts: Fix for bare metal convert to managed not displayed correctly.
  • Hosts: Fix for deleting orphaned vm’s
  • Infoblox: Fix for add integration not working with fqdn
  • Load Balancers: Fix for blank Settings tab for non-system admin roles
  • macOS: Fix for macOS User creation
  • User Groups: Fix for User Groups only available for master account
  • vCD : Fix for invalid instance/computer names

Important

For upgrades to 3.2.0 please follow the 3.2.0 upgrade instructions below!

3.2.0+ Upgrades

Overview

Upgrading from previous versions of Morpheus to 3.2.0 or later requires upgrading ElasticSerach to 5.4.1 or 5.x. We do not support ElasticSearch 6.x at this time. This upgrade requires an export and import of Morpheus ElasticSearch data if you want to retain logs, backup history, statistics, and check history of your instances. If you do not need to retain that data you can skip the ElasticSearch migration. Upgrading to 3.2.0 will create a blank ElasticSearch node with no data. Your Morpheus layout configuration will determine how to migrate your ElasticSearch data: all-in-one or distributed high availability.

Morpheus All-In-One

This deployment configuration is the default mode for Morpheus and contains a single ElasticSearch instance on the appliance. The migration steps are as follows:

  1. Login to your appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
  2. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem
  3. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc
  4. Stop the Morpheus application by executing morpheus-ctl stop morpheus-ui, this will stop creating new documents in ElasticSearch.
  5. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://localhost:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.
  6. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.
  7. You can start Morpheus at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

Note

Make sure that Morpheus is fully started before moving on to the next step.

Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://localhost:9200 /root/es_backup, substitute the path you used during the backup if different from above.

Note

The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

Morpheus Distributed High Availability

This deployment configuration assumes that you manage an ElasticSearch cluster externally from Morpheus. The steps for upgrading ElasticSearch from 1.x to 5.x are located on the ElasticSearch website. Run the following from a “master” appliance, it has the required Ruby installed in the Morpheus full stack directory. Ensure that the appliance can reach at least one ElasticSearch node over port 9200 (http). Also, make sure thre is enough disk space to hold the exported data on the appliance.

  1. Login to the master appliance as a user that has sudo privileges and can switch to the root user sudo su -. You can run the following commands under sudo, but you will need to pass the PATH to the Morpheus embedded directory.

  2. Export the Morpheus embedded path to your environment by executing: export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH

  3. Verify that you are using the Morpheus embedded gem by executing the command: which gem. You should see the path /opt/morpheus/embedded/bin/gem

  4. Install the elastic-util gem by executing: gem install elastic-util if you don’t want the documentation then execute gem install elastic-util --no-ri --no-rdoc

  5. Stop all the Morpheus application instances by executing morpheus-ctl stop morpheus-ui on each appliance node, this will stop creating new documents in ElasticSearch.

  6. Create a backup of the ElasticSearch indices by executing: elastic-util backup http://xxx.xxx.xxx.xxx:9200 /root/es_backup, you can change the location of the backup to any file location. You can also pass the --force argument to overwrite the existing location if you are repeating the backup.

    Note

    The next steps are done on the ElasticSearch node(s).

  7. Stop ElasticSearch on each node.

  8. Backup the ElasticSearch config directory for each node, normally located at /etc/elasticsearch/.

  9. Since the index data between 1.x and 5.x is incompatible, delete the data from the data directory normally located at /var/lib/elasticsearch. To prepare for future upgrades make sure that you delete the cluster name directory as well, ie morpheus.

  10. Upgrade ElasticSearch, use the method that best fits your situation ie pkg, tar, or zip.

  11. Remove unsupported configuration from the existing ElasticSearch configuration

    • index.number_of_shards
    • index.number_of_replicas
    • discovery.zen.ping.multicast
  12. Replace or update the package installed configuration with your existing configuration if it was overwritten.

    • Set network.host or network.bind_ip and network.publish_ip accordingly to your network configuration.
  13. Start ElasticSearch on each node and form a new cluster.

  14. Verify you have a good cluster by executing: curl http://xxx.xxx.xxx.xxx:9200/_cluster/health?pretty, check for the number of nodes and that you have a green status.

    Note

    The next steps are done on the Morpheus “master” node.

  15. Upgrade Morpheus as usual by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  16. You can start Morpheus on the master node only at this point to bring up the Morpheus application by executing: morpheus-ctl start morpheus-ui.

    Note

    Make sure that Morpheus is fully started before moving on to the next step.

  17. Once the application has started, a new ElasticSearch node is created with default data, to import your data from the backup execute: morpheus-ctl elastic-util restore http://xxx.xxx.xxx.xxx:9200 /root/es_backup, substitute the path you used during the backup if different from above.

    Note

    The restore may take several hours depending on the amount of data to restore. You can run this while running Morpheus.

  18. Move to the next Morpheus appliance and upgrade it by executing the package upgrade command dpkg -i morpheus-appliance_3.2.0-1_amd64.deb or rpm -U morpheus-appliance-3.2.0-1.el7.x86_64.rpm, and run morpheus-ctl reconfigure to complete the upgrade process.

  19. Start Morpheus by executing: morpheus-ctl start morpheus-ui.

  20. Upgrade the rest of the Morpheus appliances in your environment.

v3.1.5

New Features & Fixes

  • VMware: Cloud Sync Performance Improvements (10x)
  • Multiple Domain Join Improvements and Fixes
  • Alibaba: Technology Filter Type added
  • UI: Localization fixes
  • Fix for VMware Network and Folder Tenant Assignment
  • Windows Agent 1.4.3.0 with Agent Install and Chef Bootstrap Fixes

v3.1.4

New Features

  • Cisco ACI: Morpheus now integrates with Cisco ACI. Add ACI as a network and security integration. Inventory your existing ACI configurations, create networks, bridge domains, application profiles, tenants, endpoint groups, contexts, filters and contracts. Provision instances into new endpoint groups and define security groups that apply contracts on provision.
  • Load Balancers: F5 Improvements: Virtual Servers, Nodes and Pools can now be created, edited and deleted.
  • Openstack: Network Improvements including Multi-network, Static IP and IP Pool support
  • Hyper-V: Network Improvements including Multi-network, Static IP and IP Pool support
  • VMware Performance Improvements- 4x increase in VMware sync and performance
  • Clouds: New Alibaba Cloud Integration
  • UI- Localization support expanded
  • Morpheus Windows Agent 1.4.1 with script execution via agent command bus
  • Infrastructure: Instance Node Type added to VM detail pages
  • Library: New Search Filters
  • Library: Option Types can now be re-ordered
  • Plans & Pricing: Prices: INCUR CHARGES setting added with running, stopped, and always options.
  • vCloud Direct: IP Pools sync added
  • SCVMM- Generation option added to provisioning
  • Openstack: API token now cached to improve performance
  • Instance Details: App associations added
  • Amazon: Improved provisioning error details
  • XEN: XVA Import added
  • Containerized CLI: https://hub.docker.com/r/morpheusdata/morpheus-cli/

Fixes

  • Infrastructure: Fix for Hosts stop/start power indicator
  • Load Balancers: Fix for Default cloud selected when adding Load Balancer from cloud detail pages
  • AWS: Fix for AWS Docker Host service plan assignment
  • Networks: Fix for Assign Pool dropdown timeouts
  • Network Services: Consul - fix for name requirement not enforced
  • Virtual Images: Fix for Morpheus VMware Ubuntu 16.04 image
  • Tenancy: Assign to Tenant bulk action listing removed
  • Openstack: Keypairs are now removed on zone delete
  • vCloud Director: Fix for Provisioning - Datastore selection
  • vCloud Director: Fix for error on cloud sync
  • Provisioning: Fix for No host selection available for some System Instance types
  • Instances - fix for exported variables
  • Provisioning: Fix for 32-bit and macOS agent install

v3.1.3

New Features

  • Administration: Local user accounts can now be disabled
  • API: Storage Providers added
  • Cloud Foundry: Allow free form username input for space user management in Cloud Foundry
  • Cloud Foundry: Ability to create a space and add/remove users from a space
  • Google Cloud: Network Tagging support added
  • Instances: “Open Console” Action added
  • Instance Types: Morpheus Ubuntu 16.04 added for AWS, Hyper-V, Xen, ESXi and SCVMM
  • Library: Workflows added to Layouts

Fixes

  • Apps: Fix for broken image placeholder when creating a new app template in latest Chrome build.
  • AWS: Instances: Add Node: not propagating settings from original instance
  • Google: Provisioning: Fix for External IP list missing static IPs
  • High Availability: Implementation of the quartz lock handler
  • Image Builder: Fix for start time displayed in UTC
  • Instances: Provisioning: Fix for 500 error if disk size has decimal
  • Instances: Removed inaccessible links in sub-tenants for master tenant hosts and cloud
  • Library: Scripts: Fix for “Run as User”
  • Library: Scripts: Fix for sudo flag
  • OracleVM: Fix for Library: add OVM Node Type
  • Performance: WinRM Optimizations
  • PXE Boot: Fix for validation of Supermicro container and VM server mode boot mapping.

v3.1.2 & v2.12.5

New Features

3.1.2

  • Automation: Services section added
  • Cloud Foundry: Space deletion added
  • Cloud Foundry: Synced services provisioning added
  • Deployments: Services section added
Instances: Ubuntu 16.04 Added to Morpheus OpenStack, Google, Nutanix and Azure Instance Types
  • Load Balancers: LoadFortiADC Load Balancer Integration
  • Policies: “Remove Expiration” Action added to Instances for Users with Full Policies Role access
  • UI: Column Sorting added to multiple sections
  • vCenter: Cluster of Clusters- “All” option added to VMware cloud settings Cluster selection
  • vCloud Director: “Add User” option during provisioning added

3.1.2 & 2.12.5

  • API: Archives section added
  • API: Networks section added
  • OracleVM: Virtual Image disk count and sizes now auto-populate in provisioning wizard
  • Plans & Pricing: Additional decimal places allowed for in Prices and Costs
  • Policies: Lifecycle extension links in emails are now one-time use
  • Roles: System “User Admin” role is no longer multitenant

Fixes

  • API: Billing query optimizations
  • API: Costs removed from API billing when accessing from sub-tenant user
  • App Template: Fix for App Template wizard not loading local Amazon Images
  • AWS: Fix for “Assign EIP” flag when subnet not set to auto-assign Public IP by default.
  • AWS: Fix for Converted to managed Instances attaching service plans and pricing
  • Azure: Fix for US Gov pricing shown on EU Azure plans
  • Clouds: Fix for starting VM from Virtual Machine list tab within Cloud
  • Guidance: Fix when using multiple filters in
  • IBM Cloud (Bluemix Platform): Fix for cloud deletion and record cleanup
  • Instances: Fix for error on Actions -> Backup from main instances list on converted to managed Instances
  • Instances: Fix for inability to select a service plan when deploying HAProxy Instance Type in some environments
  • Instances: Fix for Virtual Machine link on Instance with Pending or Denied Approval status
  • Instances: Multiple regional Morpheus Virtual Image seed fixes
  • Library: Fix for Option Type variables not parsing when exported as Environment Variables
  • Monitoring: Fix for Incident re-open button
  • OracleVM: Fix for issue with multi-disk Virtual Images
  • OracleVM: Fix for Virtual Image dropdown showing unsupported Virtual Images
  • OracleVM: Fix for IP Assignment with Infoblox Integration
  • Plans and Pricing: Descriptions added for Volume Types
  • Reports: Fix for Analytics Report typos
  • Reports: Fixes for Sub-Tenants Cloud Reports
  • Reports: Tenant report removed from Sub-Tenants
  • Roles: Fix for Multitenant User Roles not propagating permission changes
  • UI: Fix for lower menu bar moving
  • Usage: Fix for multiple and duplicate records
  • vCenter: Fix for Hypervisor Console issue when multiple VMware clouds are sharing ESXi Hosts
  • vCenter: Fix for additional users not being created for Windows VMware instances when using static ip’s & Virtual Image credentials not populated
  • vCloud Director: Sync Status fix
  • vCloud Director: Security groups tab added
  • vCloud Director: Invalid Apache node type seed removed
  • vCloud Director: Fix for Virtual Image sync cleanup
  • vCloud Director: Fix for Custom Cores
  • vCloud Director: Fix for “Stop Server” Action not fully stopping VM
  • vCloud Director: Fix for host record when deleting VM
  • Virtual Images: Download option for Synced Virtual Images removed
  • Virtual Images: Fixes for error when adding Virtual Image with url with CIFS storage provider

v3.1.1

New Features

Scheduling Detail Pages
New detail pages for Operations -> Scheduling show schedule configurations and the resources schedules are applied to.
Azure Tags
Azure Tags can be created using metadata values, and existing Azure tags are now synced.

Other Improvements and Fixes

  • Fix for Library Template content edits
  • Currency symbol & other styling updates
  • VMware Multi-Disk Reconfigure fixes
  • Fix for HA Proxy Load Balancer deployment when using Firefox
  • Fix for Oracle VM Virtual Image list displaying unsupported Images
  • Oracle VM Multi-Disk fixes
  • Fix for Removing Azure Load Balancers
  • Morpheus Library CentOS AMI regional seed fixes
  • Updated vCloud Director artwork
  • VMware Hypervisor Console Improvements
  • Security improvements
  • Sub-tenant HA Proxy Load Balancer provisioning restrictions for Master Tenant Docker Hosts
  • Includes everything in v2.12.4

v3.1.0

New Features

Power Scheduling
New Operations: Power Scheduling Feature. Set weekly schedules for shutdown and startup times for Instances and VM’s, apply Power Schedules to Instances pre or post-provisioning, apply Power Schedule policies on Group or Clouds, or use Guidance to automatically recommend and apply optimized Power Schedules.
Currency Conversions
Pricing is now converted to the currency set on a Tenant with nightly currency conversions for pricing using exchange rates.
Datastore Group Permissions
Set which Groups can access a Datastore in the Datastore’s Group Access settings.
HP OneView Summary tab
Summary tab added to HP OneView Cloud Detail pages displaying Type, Name, Slot, Model, Serial Number, and Status of Chassis Blades
Network Groups - Round Robin per Instance support
Instance Networks now selected via round robin when using a Network Group, including multiple networks on the same VM, or multiple VMs in the same instance.
Legacy App Blueprint Conversion
App Blueprints from earlier Morpheus builds are converted to support v3.0+ App Blueprint features.
New Cloud Types
vCloud Director and IBM Bluemix Platform Cloud Types added (beta).

Other Additions

  • Reports -> Print added
  • Azure Multi-network Support added
  • VMware async provisioning
  • 32-bit Morpheus Agent
  • Ubuntu 16.04 added for SoftLayer, DigitalOcean, and Bluemix Morpheus Instance Types
  • API and CLI updates: Image Builder, Apps, Blueprints, Archives, –yaml support added.
  • Fix for java args in Apps Deployments

Important

There is a potential issue with application startup on fresh installs using Ubuntu 14.04 with Kernel 3.19.xx. If the Morpheus app does not start properly, please upgrade the Linux kernel and restart the morpheus-ui.

v3.0.1

New Features

New App & Blueprint wizard
Completely rebuilt Provisioning -> Apps and Blueprints sections with multi-config, raw json and yaml input/output, locking fields and boot order added.
New Analytics
Completely rebuilt Analytics section with Cost, Utilization, Instance and Instance Type analytic reports and data visualizations. Quickly analyze storage, cpu or ram usage across clouds or teams, or compare utilization vs cost per resource.
Guidance
The new Guidance feature can analyze your infrastructure and recommend actions to optimize resource utilization with projected cost savings. Morpheus can then act on those recommendations by resizing, shutting down or moving the resources to ensure money isn’t being wasted on underutilized assets.
Image Builder Service
Automate your image builds directly in Morpheus. Configure your builds, add scripts and run to generate vmdk ovf, qcow2, vhd templates from iso’s. *Requires VMware cloud with Hypervisor Console enabled.
Expanded User Settings
Users can now set default Group and Cloud Preferences, Linux and Windows User settings, add User Photos.
User Groups
User Groups can be created and then selected during provisioning to add each group members credentials to the Instance.
Kubernetes
Inventory and provision to existing Kubernetes clusters, or provision new Kubernetes clusters.
Expanded Reports
Provisioning, Infrastructure, and Tenant Inventory Reports Added to Operations -> Reports. JSON and CSV Exports added.
Container Mode
Container Mode option added to Cloud settings, can be set to Default Docker, Swarm or Kubernetes. Determines the type of Docker Host that will be provisioned into the Cloud. *Mode must be set before the first Docker Host is provisioned into a Cloud.

New Integrations

  • UpCloud
  • Cloud Foundry
  • IBM Bluemix
  • HP OneView
  • SCVMM
  • Kubernetes
  • Jenkins
  • Github

Other Additions

  • Support added for guest execution on VMware Windows Templates with renamed Administrator user.
  • USER CONFIG and DNS OPTIONS sections section added to Provisioning Wizard.
  • Disable Agent Based Firewall Management option added to Cloud Settings.
  • COST THIS MONTH and AVG MONTHLY COST data added to Cloud Detail pages.
  • Service Plans scoping added to Resource Pools and Folders.
  • EBS ENCRYPTION option added to Cloud settings
  • API & CLI Updates
  • Multiple other additions and Improvements.

v2.12.4

New Features

  • Performance Improvements including optimization of Monitoring Availability Service
  • Ansible Windows Support
  • Error handling and tracking of Ansible runs in Instance History
  • Forced sync on Identity Source logins such as Active Directory
  • Policies added to CLI
  • Optimizations for Tenant creation via API
  • HAProxy LoadBalancer restrictions for Tenants.
  • Identity Sources: Mapped Roles - Users now get default role & mapped role
  • <%=instance.createdByUsername%> variable added

Fixes

  • Ansible provision - Instance warning status no longer shown when Ansible is not enabled during provisioning.
  • API account creation optimizations
  • Fix for Active Directory Group Role removal
  • Fix for Trial Version setting on Virtual Image not saving
  • Network Services: Bind DNS - wont load
  • Fix for Policy: Fixed Host Name not being enforced
  • Fix for Delete Tenant nested error messages
  • Instance Shutdown: Extend Now styling fix
  • Usage host status fixes
  • Softlayer/Bluemix: Environment Variables IP Address fix
  • Fix for OVM Bug when base image contains more disks than are configured in provision wizard
  • Fix for Permissions: Instance Types not respected account level role

Morpheus v2.12.4 is available in the Downloads section of `morpheushub.com<https://morpheushub.com/>`_.

v2.12.3

v2.12.3 release date 10/24/2017

New Features

32-bit Agent Support
Morpheus Agent now supports 32-bit images
Cypher User Permission
New Roles Permission CYPHER -> USER allows user level decrypt permissions.
Improved VMware vCenter Session Management.
Connections pools significantly reduce vCenter API sessions from Morpheus.
Other Improvements
  • Parallel Instance Delete Improvements
  • Provisioning Status Task Improvements
  • Tenant Delete Improvements
  • Security Improvements

Fixes

  • Fix for VMware Datastore selection not populating during provisioning in certain circumstances
  • Fix for System AMI Virtual Image region sync
  • Approval and Workflow inputs restored on shutdown policy form.

Morpheus v2.12.3 is available in the Downloads section of `morpheushub.com<https://morpheushub.com/>`_.

v2.12.2

v2.12.2 release date 10/9/2017

Morpheus v2.12.2 adds the ServiceNow CMDB Integration, improvements to existing Features and Integrations, and bug fixes and enhancements.

  • ServiceNow CMDB Integration: The Morpheus ServiceNow CMDB integration creates a CMDB record upon Instance provision, updates the CMDB state when an instance is removed, and syncs changed Instance states nightly.
  • Additional ServiceNow Plugin Improvements
  • “Disable Management of Firewall by Agent” option added to Cloud settings.
  • Editing existing Environment Variables support added for Windows
  • VMware Folder support added to apps and templates
  • Nutanix Unmanaged Network Static IP support added
  • Script Variables added for Volumes: id: vol.id, name: vol.name, deviceName: vol.deviceName, maxStorage: vol.maxStorage, unitNumber: vol.unitNumber,displayOrder: vol.displayOrder, rootVolume: vol.rootVolume
  • vmxnet3 set as default VMware Network Adapter type.
  • Chef bootstrap process output added to Instance History
  • Improved Tenant Deletion
  • Improved VMware Folder and Resource Pool sync
  • Mobile layout improvements
  • Local Chef install url for windows msi added.
  • Email layout improvements for broader email client support.
  • Chef Integration now determines when FQDN should not be added.
  • Improved Provisioning error outputs
  • Improvements to User scoped permissions for monitoring, logs and backups.

Fixes:

  • Fix for Bulk Network Edit
  • Fix for DHCP flag being reset on Nutanix networks upon cloud sync.
  • Fix for Agent timestamp handling
  • Fix for Dashboard 500 error when user Role Permissions = Monitoring : User
  • Fix for Netscaler SSL cert upload
  • Fix for server stop/start when inventoried server is converted to managed and Instance Type is applied.
  • Additional character handling in Automation Scripts
  • Fix for Remove Shutdown Instance Action hanging
  • Fix for Instance History purge
  • Various other bug fixes and improvements

Morpheus v2.12.2 is available in the Downloads section of `morpheushub.com<https://morpheushub.com/>`_.

v2.12.1

Morpheus v2.12.1 adds Console Copy & Paste, VMware Folders, expanded User Scoping Permissions, Nutanix additions, Infoblox additions, and many other Improvements and Fixes.

New Features

Console Copy & Paste
  • Copy button added to copy selected text to local Clipboard.
  • Paste field added to paste text from local Clipboard. Right click in console to then paste to target.
Additional User Scoping
  • Role permissions can now be set to User for Monitoring, Backup, and Logs sections.
  • Users will only see information related to their Instances in the corresponding sections, as well as on the Dashboard, when Role permission is set to User
VMware
  • VMware Folders now sync and can be targeted for VM and Image destinations, set to active/inactive, and assigned Tenant permissions.
  • Storage Type can now be set to Thick or Thin in VMware Cloud settings.
  • Boot from ISO support added. ISO’s can now be selected to boot from for VMware provisioning, and can fully be installed using the Hypervisor Console.
  • Eject Disk Action also added for VMware technology Instance Types.
Nutanix
  • Instances can now be converted to Images in Nutanix using the Import as Image Action. A Virtual Image record with matching meta-data will also be automatically created.
  • Disk and Network type selection added to Nutanix technology Instance Types.
  • Network Interface Type Selection can be enabled in Nutanix Cloud settings.
Infoblox
  • Display Name column added to IP Pools to better identify IP Pools synced from Nutanix.
  • Network Filter field added to Infoblox settings. Allows for filtering by field, exact match or regular expression, as well as searching on extended attributes. EX: [ network_view=default&*Building=work ]
  • Tenant Match Attribute field added to Infoblox settings. Allow for auto-assignment of IP pool Groups and individual IP Pools to a tenant.

Other Additions and Improvements

  • Trial Version flag added under Virtual Images -> Edit Virtual Image -> Advanced Options. Flagging a Windows Image as Trial Version will re-arm the trial during provisioning.
  • F5 Load Balancer improvements
  • HA Proxy Load Balancer improvements
  • Citrix Load Balancer improvements
  • Chef improvements
  • Provisioning: Allow Force Delete
  • UI/API/CLI Security Improvements
  • Process Service Improvements
  • Add Node Action will now only show compatible clouds as target options.
  • Windows 2012 R2 AMI System Image improvements.
  • Redis System Images improvements.
  • New Role Permission: Provisioning: Allow Force Delete

Fixes

  • Fix for browser language settings adding commas in Plans & Pricing -> Pricing.
  • Fix for Hyper-V and Openstack technology types in Library -> Node Type -> Image dropdown.
  • Fix for File Upload in Virtual Images and Archives when using NFSv3 Storage Provider target.
  • Fixes for synced Image Record duplication.
  • Fix for extra Sub-Tenant Groups automatically being created during Sub-Tenant creation.
  • Fix for Nutanix - Windows- Create Additional user.
  • Fix for respecting Xen Custom Cores value.
  • Fix fir CentOS 6 agent install when using multiple LVM based volumes.
  • Fix for Infrastructure -> Network -> Services -> Add Service -> Consul modal.
  • Fix for Morpheus Wordpress Images: Load Balancer - no port available.
  • Fix for Dual name fields in Networks -> Services -> add Microsoft DNS

v2.12.0

2.12.0 Release Notes

Contains everything from 2.11.4 release, plus:

  • Azure Custom Image Support: Morpheus users can now upload private images into Morpheus , and then provision those onto an Azure cloud.
  • User Provisioning Notifications: Provisioning e-mail notifications are configurable in user settings.
  • Fix for removing Clouds from Groups
  • Fix for Puppet agent install for Tasks and Group/Cloud integrations
  • Fix for Nutanix backup and restore when using custom library items
  • Additional Openstack ssl support

v2.11.4

New Features

Network IP Override
Networks can now be configured to allow overriding IP configuration and selecting between DHCP, Static IP entry, or IP Pools at provision time.
Windows License Management
Windows license can now be assigned to virtual images a applied during provisioning. License can be managed in the new Licenses section under Admin - Provisioning.
Salt Windows Support
Salt Minions can now be installed on Windows Operating Systems via the Automation Engine. The source repo can also be customized and the minions can be successfully registered to both syndic master layouts as well as standard master layouts
Xen Reconfigure
Memory, Cores, Disk Size, Disks, and Networks can now be reconfigure on Xen instances and Hosts.
Debian 8 OS Support
Support for Debian 8 and 9 added to Agent. Debian 8.8 vmdk added to Morpheus Catalog.
Cloud Sync Update
90%+ reduction in VMware cloud sync time. Last Sync date and Sync Duration added to cloud detail pages.
Agent time normalization
Logging and stats data is now converted to appliance time in the cases VM time is offset.
Added support for querying ESXi hosts for Virtual Switch UUID::
vCenter user used for VMware cloud integration no longer requires propagating datacenter permissions for provisioning.
Hostname routing added for Amazon ALB’s
Allows multiple hosts to share the same port
Shutdown renewals
Shutdown policy extension lease timeframe now begins at the time of extension approval for instances already shut down by the policy, rather than from the end of the previous lease.

Additional updates:

  • Source column added to Virtual Images list page
  • Tenants columns added to Networks list view
  • Cloud Status column added to Cloud list view
  • Improvements to host cpu, power and memory statistics.
  • SEK currency support added
  • Asynchronous cloud delete added

Fixes

  • Fix for agent install and stop/start in inventoried AWS instances that are converted to Managed.
  • Fix for Openstack disabled forced SSL validation
  • Fix for Nutanix image sync issue with region codes
  • Scaling improvements
  • Windows agent install improvements
  • Fix for editing Appliance Backup settings
  • Fix for Role Permissions: Apps = User
  • Fix for Max Storage policy enforcement
  • Fix for uploaded OVA’s Virtual Image type
  • Linux ssh console aspect ratio change in 2.11.3 reverted
  • Network Groups improvements
  • Security Improvements

v2.11.3 & 2.10.8

Important

ACCOUNTS has been renamed to TENANTS in v2.11.3

New Features

Task phase execution
Set phase and execution order for tasks in Workflows. Workflow detail pages added. Drag n’ drop reordering added to scripts in node types. Restart task type added.
Load Balancer improvements
New Balance mode, sticky mode, shared VIP address options, Load Balancer Detail Pages
ServiceNow Plugin
Add Morpheus clouds and Instance types for complete provisioning within Service now
Archives Service
Archives provides a way to store your files and make them available for download by your Scripts and Users.
Network Groups
Network Groups provide round robin network pooling capabilities when provisioning instances. These are most useful when scaling multiple vms across various subnets or availability zones.
Groups Access added to Networks
Networks can now be assigned to individual Groups and set as the default choice for a group.
Featured Instance Types
Instance types in the Library can now be flagged as Featured to be added to the new Featured Instance Types filter in the Provisioning wizard. Please note once at least one Instance Type is featured, the provisioning wizard will default to the Featured filter. Simply click the All Instance Types filter to see your entire catalog.
Group Lifecycle Policies
Now apply to instances that are converted from unmanaged to managed
New Reports section
Completely rebuilt reports section. Customizable capacity and usage reports with versioning.
Cost Tracking
Instance and host cost reporting available via UI and API. Prices added to instance and host detail pages.
Refreshed Instances Section
Instance list makeover with new charts, cloud, group and health info added.
Instance Locking
Instances can now be locked to prevent deletion.
Move Instances
Instances can now be moved between groups by editing the instance and selecting the group dropdown to assign the instance to a new group.
“User” Provisioning permission added to Roles
Allows permitting a user to only see their own instances.
“Remote Console Auto-Login” permission added to Roles
Please note NLA must be disabled in Windows RPD settings if auto-login is set to “no”. This permission does not apply when using VMware hypervisor console option.
New storage Provider types
NFSv3 and CIFS (Windows Samba File Sharing) added
Expanded variable support
Custom variables can now be used in Naming policies, including variables from options types.
Process output added to instance history
See process output per action in new Instance History detail modal.
Instance notes section
Add custom notes to instances, with markdown support.
Expanded Inventorying
Inventory Existing Instance option added to Softlayer and VMware fusion cloud types
Salt, Ansible and Chef improvements
Includes Ansible and Salt integration detail pages.
Integration detail page
Detail pages added for all integration with added functionality per integration.
Timezone option added to cloud settings
Users can now specify which timezone to set during guest customization.
Force guest customization added
Flag added for vmdk Virtual Images configuration (Advanced Settings- Force Guest Customization)
Enable Settings Flag on library items configuration
This setting exposes the Settings tab for appropriate instance types in the Instance Detail page.
  • Deployment option added to Provisioning wizard
  • IBMid support added to Softlayer*
  • Windows 2012 AMI option added to default Windows Instance Type*
  • Starting, stopping phases added to Instance status
  • Manage Network Interfaces from Instance and Host detail pages
  • Advanced Options- Status selection for Instances
  • White Label mobile formatting improvements
  • Source Image info and link added to Instance and Host detail pages
  • Restart task type added (restarts target)
  • API Allowed Origins support added
  • Accounts renamed to tenants
  • Multi-select added for tenant network assignment*
  • Inventory Level setting added for Azure clouds with Basic and Full (API Heavy)
  • Xen NFS, Multi-network support added
  • KVM Multi-Network support added, Multi-network driver
  • ESXi Multi-Network support added

2.11.3 and 2.10.8 Fixes

  • Fixed issue with deleted Tenants stuck in removing due to Openstack cloud security groups not flushing
  • Fixed Nutanix- Virtual Image duplication and cleanup
  • Fixed Nutanix images not available in Node Type image dropdown
  • Fixed Hostname field in Apps and Templates not applying to Windows instances.
  • Fixed fields Apps Wizard Layout section not saving when custom Service Plan was selected.
  • Fix for Chef bootstrap on Windows instances in Azure
  • Instance list layout fixes.
  • Xen Image sync fix
  • Fix for instance list for sub-accounts
  • Fix for Bluecat network query
  • Dashboard- Recent Activity now only shows activity from Groups the user has access to
  • User permission fixes
  • Stopping an Azure instance now deallocates it in Azure
  • Fix for Group user permission when Clouds permission is set to “none”
  • Digital Ocean Naming Fixes
  • Fix for duplicate price entries on public cloud price sync