introducing-vmware-app-volumes-3-0-whats-new-cloud-volumes-vmware-monitoring-and-more

It’s an interesting time, indeed. The only time the buzz about one new device dies down is when the hullabaloo over another device cranks up. Developers are dealing with hodgepodge infrastructures that include a bit of legacy system here, a dabble of new application there, and a whole lot of in-between. 

VMware is trying to take some of the headaches out of managing, updating, delivering, and consuming applications across varied devices with VMware App Volumes 3.0. The new version was announced in February 2016 and will be available later this quarter. Here are some of the improvements you have to look forward to. 

  AppToggle

VMware App Volumes

VMware App Volumes 3.0 is designed to give you greater visibility and control across your environment, particularly in terms of the users and the devices that depend on your architecture. 

This new feature has a patent pending. It enables per-user entitlement and installation of apps inside a single AppStack, giving you greater flexibility. AppToggle helps IT lower the number of AppStacks necessary, eliminating a lot of the management duties, while improving performance. Instead of just hiding installed applications, AppToggle only installs those the user has access privileges to, so it also improves security. 

AppCapture With App Isolation 

This feature allows you to easily capture and update apps in order to simplify the app packing, delivery, and isolation processes with a command line interface. It allows IT to distribute the creation of AppStacks to various teams and to merge AppStacks to make the delivery and management processes simpler and easier. This feature integrates with ThinApp, enabling the delivery of native apps in a single, consistent format throughout the AppStacks. 

AppScaling With Multizones 

This feature empowers integrated app availability across data centers, so that it is no longer necessary to have separate software to replicate AppStacks across the various sites. All you have to do is add multiple file shares to the host AppStack, and then pair the host to instances in vCenter. Then an import service scans the file shares and populates the AppStacks.

Unified Administration Console

Unified Administration Console

If you like your legacy console, you can keep your legacy console. Unlike candidates on the campaign trail, App Volumes 3.0 delivers on the promises. 

This feature gives the IT administrator a holistic view of application management, the user environment, and monitoring. It recognizes patterns to deliver easy but powerful workflows for the delivery of applications, managing the user environment, and app monitoring. It takes the complexity out of managing multiple consoles, while still allowing customers to continue to use legacy consoles, if that’s what they prefer. 

Integrated App and User Management and Monitoring 

 This is the industry’s only solution that features both application and user environment management with a built-in monitoring solution. It is designed to deliver faster provisioning and context-aware user policy, and is a complete lifecycle management solution.These changes mark a lot of improvement in a relatively short time. It will be the fifth version within less than two years. 

VMware App Volumes 3.0 comes in three editions: Standard, Advanced, and Enterprise. 

Are you looking for a better way to keep up with the changes, updates, announcements, and other VMware news and information? 

Sign up for our newsletter at Opvizor today

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.