Dell EMC VxBlock 1000: Some history and What’s New
Wed, 01 Apr 2020 18:40:24 -0000|
Read Time: 0 minutes
First for the “some history” part! Converged Infrastructure (CI) is not a new concept – it’s been with us for more than 10 years. Hey, one could even consider that we were the “inventors” of CI back in the days when we publicly announced it on November 03, 2009 (Press Release).
Figure 1. EMC Joe Tucci (center) unveils the Virtual Computing Environment coalition with VMware's Paul Maritz (left) and Cisco's John Chambers (right).
Nowadays the CI concept is well understood, but in 2009 it was kind of ground breaking since this approach had never been taken before.
“All datacenter requirements in just one system? How could that be possible?”
Those were the days of separated, disconnected, and siloed domains (compute, storage, networks) and CI was a new disruptive technology solution that would require a complete transformation in how IT would architect and consume datacenter infrastructure.
To have a clearer understanding of how Dell Technologies comprehends CI – then and now, we could define our CI end-to-end engineered turnkey system as:
VxBlock 1000, Industry-leading Converged Infrastructure, simplifies all aspects of IT by seamlessly integrating all the compute, network, storage and data protection and cloud management technologies you need into one engineered system. It is an all-in-one, “data center in a box.” You can offload the complexities and risks associated with managing enterprise-grade data center infrastructure so that your IT teams can confidently focus on higher-value activities. (from Top Reasons Why Organizations Choose VxBlock 1000 Converged Infrastructure).
For those new to VxBlock 1000, here are some of the most important values VxBlock has provided:
- High availability & data protection
- No single point of failure
- High availability in all components, fault tolerance as an option
- Broad data protection suite
- High scalability & consistent performance
- 100+ PB storage
- 1000+ blade & rack servers
- Scale-up & scale-out, symmetrically or asymmetrically
- NVMe end-to-end
- Rich data services & highest efficiency
- In-line, all-the-time services
- Compression, de-dupe, replication, encryption, copy data management & machine learning
- Cloud operating model & converged management
- Tight VMware vRealize Integration
- Consistent tool set across hybrid cloud
And what has happened during this 10+ year period?
Many things. Many milestones. Many systems sold. Many successful customer stories and projects that have led VxBlock to a very effective and consistent $1 billion annual run rate business just four years into its existence. Check the diagram below to reflect on some of the key milestones VxBlock and Dell Technologies CI as a whole have delivered during this decade.
Figure 2. VxBlock 1000 one-decade journey
Today, with more than 4500 systems installed in over 100 countries, VxBlock 1000 keeps on leading the way, innovating the CI arena in four key areas that address the second part of this blog post, namely “What’s New”:
- Flexible technology choices
- Converged management and automation
- Life cycle management
- Future proof design and support
Flexible technology choices
VxBlock System 1000 gives you a choice of industry-leading technologies to meet the needs of all your different workloads, ranging from mission-critical, general purpose (virtualized or not), Artificial Intelligence/Machine Learning, End User Computing/Virtual Desktops… you name it!
Mix and match powerful Dell EMC storage and data protection options, Cisco UCS blade and rack servers, Cisco LAN and SAN networking, and VMware virtualization and cloud management. For more details on infrastructure see VxBlock 1000 data sheet and specs.
Since VxBlock 1000 is not just a reference architecture or a bill of materials, it eliminates the traditional risks associated with “Do It Yourself” approaches. It’s a fully integrated system that is engineered, manufactured, managed, supported, and sustained as one product, delivering a turnkey experience. Dell Technologies validates interoperability of components and provides a predictable system maintenance process that improves availability and productivity.
Converged management and automation
VxBlock 1000 leverages its deep VMware integration to simplify automation of everything from daily infrastructure provisioning tasks to delivery of IaaS and SaaS. At the foundation is VxBlock Central software that provides a single unified interface and access point for converged infrastructure operations.
Figure 3. VxBlock Central, a single pane of glass for management, automation, and LCM
VxBlock Central software dramatically simplifies daily administration by providing enhanced system-level awareness, automation and analytics, including launch points to:
- VMware vRealize Orchestrator (vRO) with workflows for automating daily operational tasks
- vRealize Operations (vROps) for deep VxBlock analytics and simplified capacity management
As customers place workloads on top of VxBlock 1000, VxBlock Central helps to provide and maintain these services by managing the infrastructure underneath. See here for more great info about VxBlock Central Workflow Automation and the 40+ workflows available in the Workflow Automation Library.
Life cycle management
Dell EMC CloudIQ for VxBlock features next-generation lifecycle management (LCM) that enables IT teams to more flexibly plan ahead and control converged hardware lifecycle, further reducing risk with proactive SaaS-based insights. You gain granular control over hardware inventory, milestones, support interoperability, and upgrade scenarios.
Future proof design and support
VxBlock 1000 is built with a perpetual design, meaning it will ensure that your system stays ready to support the introduction of next-generation technologies within any of the fundamental domains of the system, whether storage, compute, or network. You can address increased performance and scalability requirements while maximizing the return on your system investment.
Dell Technologies delivers fully integrated 24/7 support with a single call. There’s never any finger-pointing between vendors. You can always rely on our fully cross-trained team for a fast resolution to any problem. Our portfolio of services (including deployment services, migration services, and residency services) accelerates speed of deployment and integration into your IT environment. It also minimizes downtime by ensuring your software and hardware remains up to date throughout the product lifecycle.
One decade ago, Dell Technologies defined the foundations for CI and created a platform that has evolved to what today is VxBlock 1000. This system (compute, network, storage and management layer) is created (engineered and manufactured), maintained (single management and support), and sustained (in ongoing certified code upgrades) by Dell EMC during its entire journey. Customers simply take the keys of the car and drive.
Related Blog Posts
Introducing new Converged Management Software with CloudIQ for VxBlock Systems
Thu, 16 Dec 2021 19:53:16 -0000|
Read Time: 0 minutes
We are delighted to announce that today, our new Converged Management Software (CMS) for VxBlock System 1000, VxBlock System 740, VxBlock System 540, and VxBlock System 350 is available. CMS is an exciting new product that provides a unified CloudIQ integrated management for Converged Infrastructure (CI) operations for VxBlock. It dramatically simplifies daily administration by providing enhanced system-level awareness, automation, and analytics. CMS replaces VxBlock Central, and VxBlock Central software is no longer available with new VxBlock Systems.
What is CMS?
CMS is a lightweight on-prem software that provides VxBlock system configuration and data discovery. CMS collects the required management data from different components within your VxBlock system and sends it to CloudIQ, a single pane of glass management dashboard for VxBlock operations for processing and analytics. With CMS, you can consolidate management and monitoring of VxBlock systems with other Dell Technologies infrastructure solutions through CloudIQ.
8 Fun-Facts about CMS:
- CloudIQ conveniently unifies the management dashboard for VxBlock systems and other Dell infrastructure products
- Deployment and system configuration time is drastically reduced with simplified on-prem CMS software
- Asset management for compute, storage, and virtualization in the context of converged infrastructure inventory allows for simplicity
- Greater visibility into lifecycle milestones for components in the converged systems for better TCO management
- Efficient monitoring of the status of service contracts for exceptional Dell support
- Automation workflows to expand compute and storage resources more quickly and systematically
- Deep KPI metrics including capacity reporting and performance analytics with historical perspective for storage devices when onboarded within CloudIQ
- Comprehensive telemetry for efficient and streamlined support experience
Dell EMC’s latest Converged Management System (CMS) is now available and replaces VxBlock Central. CMS automates complex orchestration tasks and simplifies lifecycle management while enabling exceptional infrastructure visibility. Please use the following resources to learn more about the VxBlock systems and CloudIQ.
- Dell EMC and Partner FAQs: Converged Management Software 1.0 AND VxBlock Central End of Life
- VxBlock Product Page
- VxBlock Technical Collateral
- VxBlock Product Overview
- CloudIQ Product Page
- CIoudIQ Simulator
- Dell Technologies Document Center
Authors: Udit Sharma and Sameer Mohile
Running Dell ObjectScale on VMware vSphere with Tanzu
Wed, 15 Jun 2022 15:45:18 -0000|
Read Time: 0 minutes
Underlying HCI infrastructure architecture considerations
As many organizations embrace digital transformation and the application modernization journey that is involved in this process, Dell Technologies and VMware supporting customers by providing them with modern cloud infrastructure and storage solutions that support the demands of this new set of cloud native applications.
Dell ObjectScale, VMware vSphere with Tanzu, and the vSAN Data Persistence Platform (vDPp) are all examples of next generation cloud native technologies that deliver simple, scalable, and enterprise grade Kubernetes native S3 compatible object storage services on a Kubernetes runtime built into the vSphere hypervisor. To learn more about the details of this powerful set of technologies, check out these great blog posts from my colleagues over at VMware here and here. A recently published reference architecture white paper also walks through the steps of deploying these technologies together.
Now let’s get into our primary topic for this blog, which is the underlying HCI infrastructure architecture considerations for running ObjectScale on vSphere with Tanzu.
Setting the stage
Cloud infrastructure administrators have a lot of flexibility in terms of what and how to configure the infrastructure on which Dell ObjectScale runs. These options not only come at the underlying HCI infrastructure implementation layer but also at the VMware SDDC layer. This gives administrators choices on mixing the right combination of the two layers that best meet their business and operational requirements.
So, what are the layers that make up these options? For this discussion we will break it down as follows:
HCI Infrastructure Layer Options
- Construct – Dell vSAN Ready Nodes
- Consume – Dell VxRail HCI Integrated Systems
VMware SDDC Software Layer Options
Construct - VMware vSphere with Tanzu + VMware NSX-T
- Consume - VMware Cloud Foundation (VCF) with Tanzu
After we review these options, we will highlight how they can be used to align to your ObjectScale architecture design and workload requirements.
Construct HCI and Construct VMware SDDC – Dell ObjectScale on Dell vSAN Ready Nodes with VMware vSphere with Tanzu + VMware NSX-T
This option involves deploying ObjectScale on vSphere with Tanzu enabled Dell vSAN Ready Node clusters and then manually deploying and configuring the rest of the required VMware SDDC software stack including NSX-T. This is essentially the builder’s approach to implementing the HCI infrastructure stack and the VMware SDDC stack. This gives infrastructure administrators the most control over their infrastructure configuration and components. The tradeoff, however, is that it adds a bit more complexity and more manual steps to get to an outcome that is ObjectScale ready.
Consume HCI and Construct VMware SDDC – Dell ObjectScale on Dell VxRail with VMware vSphere with Tanzu + VMware NSX-T
With this approach, infrastructure administrators can take advantage of consuming pre-validated and co-engineered Dell VxRail HCI integrated systems, enabling vSphere with Tanzu on them, and then manually deploying the NSX-T components of the solution. This speeds up and simplifies the HCI infrastructure management and operations portion of the stack while still delivering on the required SDDC infrastructure foundations needed for ObjectScale to run.
Construct HCI and Consume VMware SDDC – Dell ObjectScale on VMware Cloud Foundation with Tanzu on Dell vSAN Ready Nodes
This option delivers infrastructure administrators with granular control in constructing the underlying HCI HW components while simplifying the VMware SDDC layer and consuming it as a full cloud platform using VMware Cloud Foundation. This helps streamline the VMware SDDC to include NSX-T out of the box and can automate the deployment and configuration of the VMware SDDC components that are required to enable vSphere with Tanzu and run ObjectScale.
Consume HCI and Consume VMware SDDC – Dell ObjectScale on VMware Cloud Foundation with Tanzu on Dell VxRail
This option provides a true full stack turnkey cloud infrastructure platform for infrastructure administrators to consume. This co-engineered solution between VMware and Dell Technologies delivers the fastest path to hybrid cloud and Kubernetes. Administrators gain the operational and feature benefits of VxRail, the only HCI system with deep VMware Cloud Foundation integration, with the out of the box simplicity and automation of the VMware Cloud Foundation SDDC cloud platform. From an ObjectScale use case perspective, infrastructure administators can accelerate getting all the needed underlying cloud infrastructure up and running so that ObjectScale can be deployed quickly and easily at scale and with a standardized cloud infrastructure architecture built in.
Choosing the right ObjectScale deployment infrastructure architecture
All these options deliver the necessary infrastructure prerequisites required to deploy and run ObjectScale, just through different implementation approaches that align to an organization’s operating model. ObjectScale, however, can also be deployed in several different ways, which can affect the implementation of your underlying infrastructure.
Let’s review what these options are, how our infrastructure can support these deployment models, and when would be the best time to choose one over the other.
First, let’s call out the ObjectScale deployment architecture options available:
- Co-locate ObjectScale data services on the same clusters where user application workloads run
- Run ObjectScale data services on dedicated cluster infrastructure separate from user application workloads
How an infrastructure administrator would configure the underlying HCI and VMware SDDC stack based on these options will ultimately depend on which SDDC deployment method was used, vSphere with Tanzu + NSX-T or VCF with Tanzu.
The infrastructure implementation design details vary slightly since VCF implements a prescriptive cloud architecture using the concept of workload domains. This means that cloud infrastructure administrators must consider how to deploy vSphere with Tanzu enabled clusters to run ObjectScale within the context of this VCF’s workload domain architecture. On the other hand, if administrators were using the build approach of deploying individual vSphere with Tanzu enabled clusters, architecture design decisions are a bit more open ended. Either way, both implementation methods support both ObjectScale deployment architecture models of co-located and dedicated and can be run on both Dell vSAN Ready Nodes and Dell VxRail HCI Integrated Systems.
So, what would the first option look like when co-locating ObjectScale data services on the same cluster as where user application workloads are run?
The following figure provides a visual depiction of what this option may look like in a VCF on VxRail deployment using a single VI workload domain with a single vSphere with Tanzu enabled VxRail cluster in it. In this example, we would deploy ObjectScale to the Supervisor Cluster running on this WLD cluster. Application teams would then have their user application workloads running on the same cluster infrastructure and share the underlying physical HCI compute, network, and storage resources.
Figure 1: VCF on VxRail – ObjectScale co-location cluster deployment
This approach has advantages in terms of minimizing the infrastructure footprint required to run both workload types. It can also help drive improved resource utilization of the HCI infrastructure that has been deployed. This can also be a great fit for minimizing licensing costs if you have containerized user workloads and VM-based workloads that need to consume ObjectScale storage since there is only one cluster you need to enable vSphere with Tanzu on and vSphere can support running containers and VMs on the same vSphere cluster. However, there are possible downsides. These include resource contention for user workloads since you are sharing the same infrastructure to run ObjectScale data services and lack of independent scalability and right sizing of infrastructure resources for ObjectScale and the user applications.
Option 2, running ObjectScale data services on dedicated cluster infrastructure separate from user application workloads, eliminates the resource contention by running ObjectScale on its own dedicated cluster infrastructure separate from user workloads. In a VCF on VxRail deployment, this may be implemented in a couple of ways. The first is to create a single VI WLD with two or more VxRail clusters in it. One cluster would have vSphere with Tanzu enabled on it and is where ObjectScale would be deployed. The other cluster, depending on the types of workloads running (whether they be VM-based only or a mix of containers and VMs) may not require vSphere with Tanzu be enabled on it and can just be used to run user application workloads.
By running ObjectScale on its own workload domain cluster resources, we now have physical resource isolation for both ObjectScale and user application workloads. This avoids resource contention between the two and now have the flexibility to independently scale resources for both as needed. Using this VCF workload domain organizational model may be helpful if your organization is aligning ObjectScale storage and the workloads that consume it as part of a single business unit and you may want to keep all of that together and managed within a single managed pool of cloud infrastructure resources. The following diagram provides an illustration of how this would look.
Figure 2: VCF on VxRail – ObjectScale dedicated cluster deployment with single VI WLD
The other VCF workload domain design approach is to deploy two VI workload domains. One would contain one or more VxRail clusters with vSphere with Tanzu enabled on them and ObjectScale would be deployed on top. The other VI workload domain would contain one or more VxRail clusters that may or may not have vSphere with Tanzu enabled on them and would run user application workloads only. This method still gets you separation of physical resources to avoid resource contention as well as independent scaling for both workload types, but organizationally we have deployed workload domains based on infrastructure service function.
Deploying ObjectScale into its own dedicated workload domain provides the possibility of maximum scale of how many clusters we can deploy into a single domain that can be used solely for running ObjectScale data services. We can also help simplify the networking for those clusters since we only need to accommodate for the networking needs of ObjectScale and not also for user applications workloads, too.
The following example uses dedicated NSX-T instances for each VI workload domain. In VCF, it is possible to share an NSX-T instance across multiple VI workload domains. If we would have done this, we wouldn’t have to deploy another cluster of NSX Edge appliances and could have just used the NSX Edge appliance deployed in VI Workload Domain 2 to meet the requirements that are needed when enabling vSphere with Tanzu on vSphere clusters. But since we are using separate dedicated NSX-T instances, each VI workload domain will require NSX Edge appliances to meet these vSphere with Tanzu and ObjectScale minimum requirements for the clusters contained within them. The following figure shows an illustration of what this multi-workload domain organizational model would look like.
Figure 3: VCF on VxRail – ObjectScale dedicated cluster deployment with two VI WLDs
It is important to call out that these same co-located and dedicated cluster ObjectScale architecture models can be used in vSphere with Tanzu + NSX-T on Dell vSAN Ready Nodes/VxRail deployment options as well and are not tied to just the VCF on VxRail examples shown here. The same overall ObjectScale logical and physical layout considerations would apply. Administrators who choose to approach running ObjectScale in this way would be responsible for determining where the NSX-T Manager VM’s, Edge appliances, and vCenter components would run as there would be no Management Domain construct defined as part of a cloud platform architecture like VCF has.
This is not the end, it’s just the beginning…
I hope you have found this information helpful as you work through your ObjectScale adoption journey. This is not the end of your journey, however. For more information about VxRail and ObjectScale, check out the links at the bottom of this post.
Author: Jason Marques