fully-featured-vsphere-client-in-vsphere-6-7-update-1

One of the best updates of the vSphere 6.7 Update 1 is the full featured vSphere Client. Finally, the days are gone, switching between different the HTML5 and the Web Client.

Here comes the full list of the new HTML5 client.

From the VMware vSphere client product managers:

We’ve ported all remaining features into the vSphere Client, including Auto Deploy, Host Profiles, VMware vSphere Update Manager (VUM), vCenter High Availability (VCHA), network topology diagrams, overview performance charts, and more. Read about all the features released in this version of the vSphere Client by visiting Functionality Updates for the vSphere Client site.

Feature highlights

As part of our drive towards tailoring the vSphere Client to serve your needs, we’ve improved workflow usability and overall performance. You’ll notice some changes how you work with the vSphere Client compared to earlier clients. Here are some of the areas that have changed significantly.

  • vCenter High Availability (VCHA)
    • We redesigned VCHA workflows to combine the Basic and Advanced configuration workflows. This streamlines the user experience and eliminates the need for manual intervention of some deployments.
  • Search Experience
    • We revamped the search experience. In this version of the vSphere Client, you can now search for objects with a string and filter the search results based on Tags/Custom attributes. You can also filter the object lists in the search even further. For instance, you can filter on the power state of the VMs etc., You can save your searches and revisit them later.
  • Performance Charts
    • You can pop the performance charts into a separate tab and zoom in on a specific time in the chart. We also added overview performance charts for datacenters and clusters.
  • Dark Theme
    • Dark theme has been one of the most requested features for the vSphere Client so we’re introducing a Dark mode setting. Support for the Dark theme is available for all core vSphere Client functionality and implementation for vSphere Client plugins is in progress.
  • Alarm Definitions
    • We greatly simplified the way you define new alarms, particularly in how you create rules for trigger conditions.

Let’s highlight a couple of features which are available only in the vSphere Client.

  • In-product Feedback Tool
    • We wanted to make it very easy for you to give us feedback so we included an In-product feedback tool in the vSphere Client. After you login to the vSphere Client, notice the smile icon on the top right corner. You can click the icon to send feedback as a free-form text. You also have an option to capture a screenshot to include in the feedback, annotate, and obfuscate any private information in the captured screenshot. Optionally, you can include your email address so that we can reach out to you to follow-up on your feedback.
  • Dashboard
    • The home page of vSphere Client is a dashboard that displays resource utilization information (CPU, Memory and Storage), the number of VMs, hosts, a list of objects with critical alerts, and a list of installed plugins that vCenter finds in the environment.

To get familiar with modified workflows and new features in the vSphere Client, take a look at this series of short videos on YouTube.

vSphere Client Plugins

vSphere Client Plugins are UI components built by VMware and our partners to enable you to manage the additional suite of products that work with vSphere. We provided our plugin partners with SDK tools to migrate their plugins to the vSphere Client in advance of this release and client plugins for the following solutions are now available:

  • VMware plugins: VMware vSphere Update Manager (VUM), vSAN, NSX, vRealize Operations (vROPs), Site Recovery Manager (SRM), vSphere Replication (VR), vSphere Integrated Containers (VIC).
  • Partner plugins certified for the vSphere Client: IBM Spectrum Protect, IBM Storage Enhancements, Veeam, StorMagic, INFINIDAT, HPE OneVIew, Fujitsu Software ServerView, Fujitsu ETERNUS, ATTO vconfigutoolui. Please refer to VMware Compatibility Guide for the latest set of certified plugins.

We are actively engaging with the additional partners to migrate the remaining plugins. You could refer vSphere 6.7 Client Plugin Readiness blog post to get tentative schedules of additional partner plugins.

vSphere Client flings

We continue to release vSphere Client flings. We often use flings for early feature validation so some features are first released in a fling and later released as part of a standard vSphere release. vSphere Client code in a fling gets the same quality and performance testing as the code in the official supported vSphere releases. Please continue using flings and giving us feedback on how we can make our new features better for you.

To take advantage of all features in the vSphere Client, upgrade to vSphere 6.7 U1 as soon as you can. Until you’re ready to upgrade, you can continue using the vSphere Client flings for vCenter Server 6.5 and vCenter Server 6.0 to get some of the features that are missing in these versions. Please take a moment to fill out this short 2-minute survey about your experience using the vSphere Client so-far.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.