![]() ![]() The following shows a high-level view of the Nutanix platform services: For backup we partnered with vendors like Veeam and Hycu, for others like file and object services we built them as services into the platform. Rather than requiring customers to use other vendors and products for some services we figured which ones we should partner on and which ones we should build ourselves. People still needed additional services like file shares, object storage, or containers. With these capabilities we solved for a lot of the infrastructure level issues, but we didn’t stop there. Over the years this has expanded into things like abstracting virtualization (we believe this should be something transparent and part of the system) by introducing our own hypervisor (AHV), simplifying upgrades, and providing other essential services like security and encryption. The following shows a high-level view of the AOS core platform: In the beginning this was just the DSF product, however we continue to expand the platform’s capabilities to help simplify and abstract the stack. The core provides the foundational services and components that facilitate the running of workloads (VMs/Containers) and other higher-level Nutanix services. Services building upon core services providing additional capabilities/services.To simplify things I’ve broken these down into two core areas: Over the years, we’ve added a great deal of features and capabilities. BIBLE DISCOVERY STUNS SOFTWAREWe started this journey by simplifying storage with a feature called the Distributed Storage Fabric (DSF then known as the Nutanix Distributed Filesystem aka NDFS), which combined local storage resources with intelligent software to provide “centralized storage” like capabilities. The following shows a high-level architecture of the Nutanix platform: We’re not trying to build one-off products, we’re building a platform. NOTE: Platform is one key word that is used throughout the section and in general. This allows the customer to choose what is best for them, as well as use this for negotiations purposes between vendors. ![]() ![]() We now have support for over 12 different hardware platforms (direct/OEM/third-party), multiple hypervisors (AHV, ESXi, Hyper-V, etc.), and expanding integrations with all of the major cloud vendors (AWS, Azure, GCP). All delivered with the same experience since it’s all part of the Nutanix platform. By giving them the ability to move between them, we give them flexibility. By supporting multiple under the same platform we give the customer choice and leverage. Not one hypervisor, platform, or cloud will fit all customer’s needs. natively in the kernel (a lot more reasons there), etc. run as a plug-in in vCenter, run as a VM vs. This was one of the reasons we chose to build our own UI from scratch vs. Though we started with a single hardware platform (NX) supporting a single hypervisor (ESXi), we’ve always known we were more than a single hypervisor/platform/cloud company. Provide an intuitive user interface (UI) through focus on user experience (UX) and design (Prism).Simplify the “stack” through convergence, abstraction and intelligent software (AOS).Enable choice and portability (HCI/Cloud/Hypervisor).This simplicity was to be achieved by focus in three core areas: Make infrastructure computing invisible, anywhere. When Nutanix was conceived it was focused on one goal: This book will cover these basics as well as the core architectural concepts. API-based automation and rich analytics. ![]() There are a few key constructs used when talking about “Web-scale” infrastructure: Web-scale principles are applicable and beneficial at any scale, whether 3-nodes or thousands of nodes. Web-scale doesn’t mean you need to be as big as Google, Facebook, Amazon, or Microsoft in order to leverage them. Nutanix leverages “Web-scale” principles throughout our software stack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |