4-things-to-consider-when-planning-a-vmware-vsphere-deployment

VMware vSphere is one of the most stable, reliable platforms available for building cloud infrastructures. Are you ready to get started? Great! Just take a few minutes first to consider some important deployment factors. First and foremost is hardware. No, really, you have to get the right hardware.

1. Get the Right Hardware

VMware vSphere Deployment - right hardware

Don’t assume that just any server, CPU, or other hardware component is compatible with vSphere, because only a few are. Incompatible hardware means some or all of the features won’t work, such as Fault Tolerance and Direct Path I/O.

Without the right hardware, vSphere just won’t work. At best, there will be a whole lot of really important features that don’t work. There is an extremely narrow set of hardware components that are certified to work with vSphere. You have to be sure you have one of the certified:

  • Servers
  • CPU
  • Storage adapters
  • Network adapters
  • Storage

Bear in mind that the latest VMware vSphere versions are only compatible with 64-bit hardware, so customers still using 32-bit hardware are out of luck. Though the approved hardware components are manufactured by popular makers like Intel and AMD, you can’t assume that all Intel and AMD products are certified, because they aren’t. 

Check the Compatibility Guide before buying or prepare to get your feelings hurt.

2. Get the Right Software Licenses

Software vendors have started cracking down on software licensing infringements with a vengeance in recent years. Some of the most aggressive are the big guys like Microsoft, Oracle, and SAP. IBM and AutoDesk are also getting a bad rep for knocking on doors and demanding software audits. Don’t let this simple oversight cost you (and it will: potentially tens of thousands of dollars). Get the software licenses you need and set up some kind of SAM to keep yourself out of hot water in the future.

3. Size the Host Correctly

Each host has to be set up for the appropriate size in order to properly mange the apps that are installed and operated in that environment. You don’t have to guess at it, because there are tools to help you determine what size to set up the host in a given scenario for optimal performance (and profits). Use one of the available tools to determine the right host size in your environment(s).

4. Monitor Your Clients More Than a Few Hours or Days

VMware vSphere Deployment - monitor your clients

You won’t be able to get a good read on each client’s metrics during the first day or first few days. Monitor your customers over the course of a whole month to get a clear picture of the average and peak workloads you’re dealing with.

Another common deployment mistake is to monitor clients for just a day or less to determine their needs. Average and peak usage can’t really be measured unless you monitor the situation for a full month. By then, you should have collected adequate metrics to properly address the average and peak workloads of each customer.

A little planning now can save you a lot of trouble, expense, and frustration in the long run. For a near-time monitoring solution to improve your VMware performance and free up as much as 60% of your time, visit 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.