Month: April 2015

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 …

multi-tenancy-vmware-portal-managed-service-offering Read More »

not-a-search-engine-opvizor-is-the-find-engine-for-vmware-vsphere-2

Not a Search engine, opvizor is the Find engine for VMware vSphere Why comparing management software with search engines like google? Isn´t it annoying that all these tools and software products you are using to optimize and stabilize your VMware vSphere environment are build as some kind of query framework. Of course they do an …

not-a-search-engine-opvizor-is-the-find-engine-for-vmware-vsphere-2 Read More »

virtualizeplanet-com-with-vrops-you-still-need-something-like-opvizor

Ricky from virtualizeplanet.com asked himself after attending a local VMUG in London, how VMware competes with his Eco-system especially looking at the new vROPs release. Photo courtesy of Ricky El-Qasem His great question and our response is definitely worth sharing as more people think and ask the same. “What we receive from customers is that …

virtualizeplanet-com-with-vrops-you-still-need-something-like-opvizor Read More »

solving-vmware-tools-outdated-or-not-installed

Virtualizationsoftware.com about VMware Tools outdated or not installed David Davis at http://www.virtualizationsoftware.com/ published another article about the bad situation of having VMware Tools outdated or not installed at all. Photo courtesy of VMware Tools outdated article by David Davis Every VMware administrator should be well aware of the negative impact to virtual machines when living with that …

solving-vmware-tools-outdated-or-not-installed Read More »

installing-vsphere-6-0-esxi-hosts-nested-preconfiguration

Introduction After covering the installing of the vCSA in the last article, we now care about the ESXi 6.0 Hosts installation and integration. I need to run the ESXi hosts nested as virtual machines themselves as this will be a testing environment. All systems installed are based on an existing physical environment running vSphere 5.5. …

installing-vsphere-6-0-esxi-hosts-nested-preconfiguration Read More »

installing-vsphere-6-vcsa-vcenter-server-appliance

Introduction During my daily work as a Systems Engineer at opvizor I’m frequently facing scenarios where customers or developers are asking for things that have to be reproduced in a vSphere environment. As I don’t want to use (and wouldn’t recommend to anyone) the productive infrastructure for testing, I needed something else. Since I cannot …

installing-vsphere-6-vcsa-vcenter-server-appliance Read More »

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.

Subscribe to our newsletter