multi-tenancy-vmware-portal-managed-service-offering

When we started developing opvizor Health Analyzer as a SaaS offering we also thought about System Integrators or Consultants that want to use a single pane of glass across multiple customers (VMware landscape). 

Having an updated and direct view of the customers VMware environment is a great help to offer remote support and consulting. Just imagine a customer is adding a hundred more virtual machines but the environment was never planned for that. Before any performance complaints hitting your hotline you can already react and contact the customer with solutions before he falls into a trap.

Over time more and more consulting companies used opvizor as an enabler to offer remote managed services for VMware vSphere. In the beginning they just used multiple accounts in multiple browser windows. But we wanted to improve that, simplifying the way the managed service partner could see all his customers environments at once – the Partner View was born. A multi-tenancy VMware portal to remotely look over the customers shoulder, supporting him in the best possible way to run the perfect VMware.

About a week ago, when a VMware reseller sent us an email, we noticed that we need to promote the Partner View again. An excerpt of that email:

Here is the question.  If I install one instance of Opvizor for each of the customers above (6 instances), how will that data come across when viewing from the Opvizor web site.  I was dreaming last night that it might be some rudimentary form of single pane of glass (SPOG) viewing.  Or perhaps a set of links/tabs across the top of the dashboard – one for each program.  Once the tab is clicked, you would see a normal Opvizor dashboard for that program, but all the data is readily available without having to open up 6-7 instances of Opvizor.

[optin title="Get more Opvizor information!" text="Never miss VMware hints and recommendation" buttontext="Sign Up for news" successMessage="Message has been submitted successfully." errorMessage="Failed to send your message. Please try later." invalidEmailMessage="Your email address does not appear valid." border="false" collectfirstname="false" collectlastname="false" collectphone="false" collectcompany="false"]

Dear Partner, thanks for your email – and we´re more than glad to tell you and all others that are interested: It´s already in the product, we can easily enable it for you!

The customer just needs to add your "partner" type account and you can directly view it within the Partner View, Multi-Tenancy VMware Portal.

Multi-Tenancy VMware Partner View

When double-clicking the headline of the widget, your browser automatically opens another tab with the customers environment. There is no need of logging in again. And the customer still has total control to allow or deny the access!

Multi-Tenancy VMware Portal Single Customer View

If you´re interested in the Partner View, our Multi-Tenancy VMware Portal please let us know!

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.