V8.4

[Basa Benejan]

Withour upcoming VMware vRealize Log Insight v8.4 and vRealize Log Insight Cloud releases, we are excited to continuously improve and innovate centralized log management across your entire data center stack for better security, visibility, and troubleshooting.

The Arm Architecture is continually evolving, and this blog gives a high-level overview of some of the changes made in Armv8.4-A*. We develop these changes by listening to the Arm Ecosystem and working with them to provide new functionality that benefits everyone. These are incremental changes to the architecture and do not introduce any significant new features. Previous incremental versions of the architecture have been introduced for v8.3-A, v8.2-A, and v8.1-A.

Feedback from the Arm ecosystem demonstrates that there are multiple Secure Operating Systems (OS) that wish to make use of Secure EL1, including firmware, key management software, and secure OS services. These will have been developed independently of each other and are therefore unaware of the services provided by other functions, and compete for resources.

To help with this in Armv8.4-A, support has been added for Secure EL2. Together, with Arm Trusted Firmware, this will enable multiple Secure OS services to exist in the system alongside one another. Moving the world to the following diagram:

Armv8.4-A adds support for more cryptographic hashing algorithms, including SHA2-512, SHA3, and the Chinese Standards SM3, and SM4. This provides acceleration for more hashing algorithms than those available in earlier versions of Armv8-A.

Armv8-A has continually improved its support for virtualization and, in v8.4-A we add further improvements. One is an incremental improvement to how we handle nested-virtualization (that is running a Virtual Machine within a Virtual Machine), which provides significant performance benefits when the guests are not using para-virtualization. We believe this will be of benefit in enterprise server installations

One use case is enabling hypervisors to monitor and control how virtual machines are using the memory of a system and communicating with other system components. This means that the hypervisor can limit the memory system performance impact of one virtual machine on other virtual machines, just as it may limit the number of cores or amount of DRAM that can be allocated by a virtual machine.

This provides a short overview of some of the key features added to the Arm Architecture in Armv8.4-A. More information will be forthcoming over the next six months, as new versions of the Arm ARM and XML are released.

* The case of the Arm Architecture version numbering has changed to reflect the new Arm brand. Hence, the architecture version is now written as Armv8.4-A and not ARMv8.4-A. The architecture documentation will be updated over time to reflect this change.

Now, when you open a Workspace in GitKraken Client, you will see the new pull requests view option. This view shows a list of all open PRs associated with the repos in your Workspace, allowing you to quickly scroll through all open PRs. Users can also search to find a specific pull request.

Workspaces have always allowed you to create collections of repos for your personal work, or to be administered and shared by your whole organization. With GitKraken Client v8.4, users may now create their own teams, making it easy to share a workspace with select members of your organization. This is in addition to the other awesome benefits offered by the teams view in GitKraken Client!

Sharing Workspaces with teams lets the relevant team members work on the same repos and pull requests from a single view, helping keep everyone on task and in the developer flow. Sharing a workspace is also an easy way to onboard new team members who may need to Git clone many repos at once.

For example, when typing a Git command, you will now see the Git icon appear in the suggestion list, helping identify the best choice from the list of suggestions. This also works for shell commands, npm, and Yarn.

All GitKraken Client users can now create teams, composed of members of your organization. Teams can share a Workspace, get a view into what files other team members are working on, and give you a heads up about potential merge conflicts. You can start a new team either using the Teams View in the left panel or from Preferences by opening the menu from the Organization section.

We know that any mission is better solved with the right team using the right tools. The GitKraken Client v8.4 release is all about helping organizations of any size, especially those with multiple related repositories, get more done, easier, safer, and with better results.

This is the release note for the 8.4 release and details the issues resolved in all Program Temporary Fixes (PTFs) between 8.4.0.0 and 8.4.0.14.This document will be updated with additional information whenever a PTF is released.

The three site orchestrator is not compatible with the new SSH security level 4.This will be resolved in a future release of the orchestrator.8.4.0.13Customers planning to upgrade to v8.4.0 or later should be aware that an update to OpenSSH has terminated support forall DSA keys. An update to OpenSSL has also terminated support for 1024-bit RSA keys used in SSL certificates.

Customers currently using DSA public keys for SSH access will need to generate new keys using alternative ciphers, suchas RSA or ECDSA. If using RSA public keys for SSH access, it is recommended to use keys of 2048 bits or longer.

Customers currently using 1024-bit RSA keys in SSL certificates will need to generate new SSL certificates using2048-bit RSA keys or ECDSA keys. This applies not only to the system certificate, but also to any SSL certificates usedby external services such as LDAP servers.

There is an existing limit on the number of files that can be returned by the CLI of approximately 780 entries.In many configurations this limit is of no concern.However, due to a problem with hot-spare node I/O stats files, 8-node clusters with many hardware upgrades ormultiple spare nodes may see up to 900 I/O stats files.As a consequence the data collector for Storage Insights and Spectrum Control cannot list or downloadthe required set of performance statistics data.The result is that there are many gaps in the performance data, leading to errors with the performance monitoringtools and a lack of performance history.

Systems, with NPIV enabled, presenting storage to SUSE Linux Enterprise Server (SLES) or Red Hat Enterprise Linux(RHEL) hosts running the ibmvfc driveron IBM Power can experience path loss or read-only file system events.

For systems using remote copy without the 3-site functionality it is possible to trigger a resource leak whenopening the remote copy panel in the GUI.After the remote copy panel has been opened multiple times this resource leak can reach the point where the GUIbecomes unresponsive.

3a8082e126