X

      Submit A Request

      Release Notes 4.0.0.0c

      • by Leslie Lundquist ● June 30, 2017

      • Tags:

        • commontech

        • release

        • features

        • gettingstarted

      IBM Bluemix Private Cloud Customer

      Release Notes 4.0.0.0c Community Edition (Ubuntu)

      June 30, 2017

      This document offers a basic description of the 4.0.0.0c IBM Bluemix Private Cloud offering, commonly called Dedicated. The Community Edition offering is based on Ubuntu. Links to further documentation can be found in each section.

      Summary of the Latest Release

      Release 4.0.0.0c of IBM Bluemix Private Cloud includes some new capabilities and performance improvements.

      Every IBM Bluemix Private Cloud has these new features in 4.0.0.0c:

      • Upgrade to OpenStack Newton version
      • Live Migration (available to cloud_admin role only)
      • Federated ID service with W3ID using SAML 2.0
      • Network Performance Tuning for Dedicated Controllers
      • ILMT/BigFix agent support on Compute nodes
      • Language switching is now available in Horizon

      For more information about OpenStack Newton, please refer to the OpenStack Newton Release Notes

      To maintain continuity with our earlier releases, the customer documentation now reflects Mitaka and Newton differences in features and it can be searched by those keywords.

      General Enhancements

      You may notice expansion, performance, and monitoring improvements. Here are some highlights:

      • We now allow expansion to more than 2 pods.
      • We’ve enabled the Cinder V3 endpoint.
      • Monitoring and logging support enhancements.
      • Improved Ceph automation, with performance improvements.
      • Volume cloning, with a few known limitations.

      Here is a document to give you more details.

      #### Known Limitations of this Release

      [1] Error message when updating a network with a subnet https://bugs.launchpad.net/horizon/+bug/1694380 There is a defect in the community on this issue, it is purely a Horizon display issue. When a user makes an update on a network with a subnet, a message is displayed: “Danger: there was an error submitting the form.” The updated network information is not reflected in Horizon. The error does not have any functionality impact. The workaround is to refresh the browser, so that the correct information will be displayed.

      [2] Full clone feature: A known limitation is that you can only create 3 clones concurrently. It is a feature flag, which means that, by default, full clone is NOT enabled. A defect is open in the community pending core review.

      [3] member and project_admin role cannot create an image with Image Sharing Visibility as Public Information about this limitation has been added to our customer documentation here.

      [4] Not all roles can create Ports using Horizon The Neutron policy lets all roles create ports on the network. However, from the Horizon dashboard only users with admin or cloud_admin roles are allowed to create ports on a network from the “Admin” tab. If you try to create a port as a user with admin or cloud_admin roles via the Horizon dashboard, after you click the submit button, nothing happens. There is an upstream bug https://bugs.launchpad.net/horizon/+bug/1645708 for this issue. Users can use the OpenStack CLI or the API to create the port on a network as an alternative.

      [5] “Unable to connect to neutron” error when viewing Admin > System > Instances page in Horizon A few customer clouds may see a display/cosmetic bug in Horizon when viewing the Admin > System > Instances page. The problem occurs when retrieving data for ports that are owned by other projects. Our engineering team continues to investigate exactly which circumstances lead to this display error, but please be assured it is a non-impacting bug. Horizon operates normally and instances spawn successfully despite this message being on screen.