On behalf of the ManageIQ team, I’m happy to announce the release of ManageIQ Oparin! This release is named after the chess grandmaster Grigoriy Oparin. You can download the Oparin-1 release on our downloads page.

Here are the highlights of the Oparin release:

  • New Providers
    • Split oVirt Provider out of Red Hat Virtualization Provider [#21001]
    • Split AWX Provider out of Ansible Tower Provider [#21056]
  • Provider Enhancements
    • Google
      • Allow Enable/Disable external access when provisioning a VM [#231]
    • IBM Cloud PowerVS
      • Add support for clone-to-template on an instance [#374]
      • VM Native Console [#389], [#395]
      • VM Management Console access to open the VM’s page on IBM Cloud [#396]
      • Add volume clone [#390]
      • Add VM affinity for multi-VM create via server placement groups [#363]
      • Reporting Enhancements [#321]
    • IBM PowerVC
      • Metrics collection (inherited from base OpenStack provider)
      • Instance snapshots (inherited from base OpenStack provider)
      • Image import from IBM Cloud PowerVS [#38]
      • VM Console access [#69]
    • IBM Power HMC
      • Clone from Template to VM [#63]
      • Collect LPAR disks using VSCSI mappings [#91]
      • Collect Host Hardware/Guest Devices [#96]
      • Collect HMC shared processor pools to inventory as ‘resource pools’ [#100]
      • HMC console access [#83]
      • Add rename support for VMs [#99]
      • Add set_description support for VMs [#102]
    • Kyndryl AutoSDE
    • Oracle Cloud
      • Instance Provisioning Support [#79]
    • VMware
      • [Prototype] Add a pure-ruby event catcher [#522]
  • Core
    • Add lifecycle operation support for Cloud Databases [#21886]
    • Metrics Collection Performance and Scalability [#20071]
    • Add Kafka Configuration Option [#22132]
    • Run database with SSL as non-root user on appliances [#21722]
  • API
    • New endpoints
      • /physical_server_profiles collection [#1151]
      • /provider/#/cloud_volume_types sub-collection [#1170]
    • Additions
    • Fixes
      • /widgets Fixed generate_content to now return a task_id [#1165]
      • /volume_mappings Fixed issue where configuration button for volume mappings was missing [#1169]
  • Build
    • Default to PostgreSQL 13 [#20662]
    • [Podified] operator-sdk 1.x support [#624]
    • Remove the need to deliver NodeJS in production [#8300]
    • Move ansible python module installation from post script to a standalone rpm [#423]
  • Developer
    • Complete Transition from AvailabilityMixin to SupportsFeatureMixin [#21179]
    • [UI] Continue conversion of HAML tables to react Carbon tables [#8124]
    • [UI] Continue to replace angular code [#8417]
    • [UI] Continue conversion of forms to React [#8441]
    • Support Ruby 3.0 [#21536]
    • Upgrade to Rails 6.1 [#21516]
    • Upgrade ansible-runner to 2.3.x [#21734]

IMPORTANT: The following are potentially breaking changes and deprecations.

  • **BREAKING**
    • Stop logging to files in production deployments [#21177]
      • Logs will go to journald on appliances and to STDOUT on podified deployments
      • This change is potentially breaking if you have any automation that relies on collecting the logs from the /var/www/miq/vmdb/log location.
    • Don’t automatically initialize appliances on first-boot [#21878]
      • On first-boot an appliance can be configured as a database appliance or a worker appliance using appliance_console.
      • Worker appliances do not need a second disk and so can be connected directly to the database appliance without need for “un-initialization”.
      • This change is potentially breaking if you have any automation for deploying appliances.
  • Deprecations (to be removed in Petrosian release)
    • Microsoft SCVMM Provider
    • OpenShift 3.x support
    • VMware 5.x and below support
    • PostgreSQL 10 support
      • While PostgreSQL 10 support will continue to work for the Oparin release, we recommend upgrading to PostgreSQL 13 now, as it will be required for the Petrosian release.

There are many more changes that would be impossible to detail in a single blog post. Many thanks goes to all of the community members for their contributions! We are already well underway on the next release of ManageIQ - Petrosian. If you’re interested in getting involved, check out our roadmap, check out our community page, ask questions in our discussions forum, and chat with us in Gitter. We look forward to hearing from you!