IP Library Granted Patent US 12,591,446
Granted Patent B2
US 12,591,446 · App. 18/216,511 · Granted Mar 31, 2026

Configuring virtualization system images for a computing cluster

Inventors: Joshua John Berry (Redwood City, CA); Mohan Maturi (San Jose, CA); Shlomo Shlomi Vaknin (San Jose, CA); Aman Nijhawan (Seattle, WA); Anil Kumar Kushwah (Bengaluru, IN); Avi Bhandari (San Jose, CA); Jan Ralf Alexander Olderdissen (Herrenberg, DE)
Assignee: Nutanix, Inc.
G06F9/45558G06F8/60H04L67/10G06F2009/45579
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,591,446
App. No.
18/216,511
Filed
Jun 29, 2023
Granted
Mar 31, 2026
Kind
B2
Art Unit
2455
USPC
718/1
Abstract

A plurality of different virtualization system images are configured for deployment to a plurality of nodes in heterogeneous environments. Individual ones of the virtualization system images are configured such that once deployed, the nodes form a computer cluster having a storage pool that is shared across the nodes. When configuring the virtualization system images, information that describes the heterogeneous computing environments is accessed, and constraints pertaining the heterogeneous computing environments are reconciled in advance of configuring the different virtualization system images. A common subnet across the heterogeneous environments is established. The plurality of different virtualization system images are configured to access the common subnet once deployed. The common subnet serves as a storage I/O communication path over which a cluster-wide storage pool is implemented. The virtualization system images are configured to correspond to address portions of a contiguous address space that is used to access data in the storage pool.

Claims (47)

1 . A non-transitory computer readable medium having stored thereon a sequence of instructions which, when stored in memory and executed by a processor, cause acts comprising:

identifying a set of candidate nodes, the set of candidate nodes being distributed across first and second cloud environments;

identifying a subset of nodes of the set of candidate nodes that can be configured to be included in a cluster distributed across the first and second cloud environments and interconnected using a common subnet; and

bringing up a cluster comprising the subset of nodes by exchanging communications between each node of the subset of nodes over the same common subnet, at least by:

defining a logical subnet across the first and second cloud environments; and

deploying one of two or more configurations to respective nodes of a portion of the subset of nodes to form the cluster, wherein

the two or more configurations comprise virtualization system images, a first virtualization system image corresponding to the first cloud environment and a second virtualization system image corresponding to the second cloud environment, the virtualization system images are configured to be node specific, each node of the subset of nodes is assigned a network identity and a cluster identity in a corresponding virtualization system image, the network identity is associated with the cluster identity, and each node of the subset of nodes knows which nodes have been assigned into the cluster, and

the common subnet forms a communication path for the portion of the subset of nodes that form the cluster, the cluster spanning the first and second cloud environments, and the configurations of the respective nodes of the portion of the subset of nodes cause the subset of nodes to self-assemble using the common subnet.

2 . The non-transitory computer readable medium of claim 1 , wherein the acts further comprise provisioning networking equipment to form an isolated network for the cluster using a private VxLAN as an overlay and provisioning a tenant-specific secure underlay within the private VxLAN.

3 . The non-transitory computer readable medium of claim 1 , wherein the cluster indicates readiness to process a workload after completing self-assembly.

4 . The non-transitory computer readable medium of claim 1 , wherein the first cloud environment comprises a first heterogeneous pool of on-premises nodes and the second cloud environment comprises a second heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, or specialized nodes.

5 . The non-transitory computer readable medium of claim 1 , wherein the common subnet further spans a third cloud environment, and one or more nodes of the third cloud environment are configured to cause the one or more nodes to self-assemble with the subset of nodes using the common subnet.

6 . The non-transitory computer readable medium of claim 1 , wherein the virtualization system images are configured such that, when executed, the portion of the subset of nodes are able to communicate with each other to self-assemble themselves into a cluster.

7 . The non-transitory computer readable medium of claim 1 , wherein the virtualization system images are configured by one or more of: (1) assigning node-specific identities, (2) assigning an initial leader, (3) setting of initial environment-specific parameters, (4) setting parameters for an initial networking configuration, (5) setting an initial networking configuration for communications between first and second cloud environments, or (6) setting parameters for accepting commands or other messages from on-cluster or external control systems.

8 . The non-transitory computer readable medium of claim 1 , wherein the first cloud environment comprises a first heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, on-premises nodes, or specialized nodes, and the second cloud environment comprises a second heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, on-premises nodes, or specialized nodes.

9 . A method comprising:

identifying a set of candidate nodes, the set of candidate nodes being distributed across first and second cloud environments;

identifying a subset of nodes of the set of candidate nodes that can be configured to be included in a cluster distributed across the first and second cloud environments and interconnected using a common subnet; and

bringing up a cluster comprising the subset of nodes by exchanging communications between each node of the subset of nodes over the same common subnet, at least by:

defining a logical subnet across the first and second cloud environments; and

deploying one of two or more configurations to respective nodes of a portion of the subset of nodes to form the cluster, wherein

the two or more configurations comprise virtualization system images, a first virtualization system image corresponding to the first cloud environment and a second virtualization system image corresponding to the second cloud environment, the virtualization system images are configured to be node specific, each node of the subset of nodes is assigned a network identity and a cluster identity in a corresponding virtualization system image, the network identity is associated with the cluster identity, and each node of the subset of nodes knows which nodes have been assigned into the cluster, and

the common subnet forms a communication path for the portion of the subset of nodes that form the cluster, the cluster spanning the first and second cloud environments, and the configurations of the respective nodes of the portion of the subset of nodes cause the subset of nodes to self-assemble using the common subnet.

10 . The method of claim 9 , further comprising provisioning networking equipment to form an isolated network for the cluster using a private VxLAN as an overlay and provisioning a tenant-specific secure underlay within the private VxLAN.

11 . The method of claim 9 , wherein the cluster indicates readiness to process a workload after completing self-assembly.

12 . The method of claim 9 , wherein the first cloud environment comprises a first heterogeneous pool of on-premises nodes and the second cloud environment comprises a second heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, or specialized nodes.

13 . The method of claim 9 , wherein the common subnet further spans a third cloud environment, and one or more nodes of the third cloud environment are configured to cause the one or more nodes to self-assemble with the subset of nodes using the common subnet.

14 . The method of claim 9 , wherein the virtualization system images are configured such that, when executed, the portion of the subset of nodes are able to communicate with each other to self-assemble themselves into a cluster.

15 . The method of claim 9 , wherein the virtualization system images are configured by one or more of: (1) assigning node-specific identities, (2) assigning an initial leader, (3) setting of initial environment-specific parameters, (4) setting parameters for an initial networking configuration, (5) setting an initial networking configuration for communications between first and second cloud environments, or (6) setting parameters for accepting commands or other messages from on-cluster or external control systems.

16 . The method of claim 9 , wherein the first cloud environment comprises a first heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, on-premises nodes, or specialized nodes, and the second cloud environment comprises a second heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, on-premises nodes, or specialized nodes.

17 . A computing system comprising:

a storage medium having stored thereon a sequence of instructions; and

a processor that executes the sequence of instructions to cause a set of acts comprising:

identifying a set of candidate nodes, the set of candidate nodes being distributed across first and second cloud environments;

identifying a subset of nodes of the set of candidate nodes that can be configured to be included in a cluster distributed across the first and second cloud environments and interconnected using a common subnet; and

bringing up a cluster comprising the subset of nodes by exchanging communications between each node of the subset of nodes over the same common subnet, at least by:

defining a logical subnet across the first and second cloud environments; and

deploying one of two or more configurations to respective nodes of a portion of the subset of nodes to form the cluster, wherein

the two or more configurations comprise virtualization system images, a first virtualization system image corresponding to the first cloud environment and a second virtualization system image corresponding to the second cloud environment, the virtualization system images are configured to be node specific, each node of the subset of nodes is assigned a network identity and a cluster identity in a corresponding virtualization system image, the network identity is associated with the cluster identity, and each node of the subset of nodes knows which nodes have been assigned into the cluster, and

the common subnet forms a communication path for the portion of the subset of nodes that form the cluster, the cluster spanning the first and second cloud environments, and the configurations of the respective nodes of the portion of the subset of nodes cause the subset of nodes to self-assemble using the common subnet.

18 . The computing system of claim 17 , wherein the set of acts further comprise provisioning networking equipment to form an isolated network for the cluster using a private VxLAN as an overlay and provisioning a tenant-specific secure underlay within the private VxLAN.

19 . The computing system of claim 17 , wherein the cluster indicates readiness to process a workload after completing self-assembly.

20 . The computing system of claim 17 , wherein the first cloud environment comprises a first heterogeneous pool of on-premises nodes and the second cloud environment comprises a second heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, or specialized nodes.

21 . The computing system of claim 17 , wherein the common subnet further spans a third cloud environment, and one or more nodes of the third cloud environment are configured to cause the one or more nodes to self-assemble with the subset of nodes using the common subnet.

22 . The computing system of claim 17 , wherein the virtualization system images are configured such that, when executed, the portion of the subset of nodes are able to communicate with each other to self-assemble themselves into a cluster.

23 . The computing system of claim 17 , wherein the virtualization system images are configured by one or more of: (1) assigning node-specific identities, (2) assigning an initial leader, (3) setting of initial environment-specific parameters, (4) setting parameters for an initial networking configuration, (5) setting an initial networking configuration for communications between first and second cloud environments, or (6) setting parameters for accepting commands or other messages from on-cluster or external control systems.

24 . The computing system of claim 17 , wherein the first cloud environment comprises a first heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, on-premises nodes, or specialized nodes, and the second cloud environment comprises a second heterogeneous pool of: nodes of a public cloud facility, nodes of a bare metal provider, on-premises nodes, or specialized nodes.

Assignments (1)
SECURITY INTEREST Recorded Feb 13, 2025
From: NUTANIX, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 070206/0463 →
Continuity (2)
Continuation 17139541 · Dec 31, 2020
Related Publication 20240069952A1 · Feb 29, 2024
References Cited (219)
US 7843907B1 · Abou-Emara et al. · 2010 [cited by applicant]
US 7990994B1 · Yeh et al. · 2011 [cited by applicant]
US 8195760B2 · Lacapra et al. · 2012 [cited by applicant]
US 8200700B2 · Moore et al. · 2012 [cited by applicant]
US 8345692B2 · Smith · 2013 [cited by applicant]
US 8347088B2 · Moore et al. · 2013 [cited by applicant]
US 8549518B1 · Aron · 2013 [cited by examiner]
US 8555383B1 · Marshall et al. · 2013 [cited by applicant]
US 8601473B1 · Aron · 2013 [cited by examiner]
US 8660129B1 · Brendel et al. · 2014 [cited by applicant]
US 8713295B2 · Bax et al. · 2014 [cited by applicant]
US 8743872B2 · Chidambaram et al. · 2014 [cited by applicant]
US 8850130B1 · Aron et al. · 2014 [cited by applicant]
US 9087319B2 · Nguyen · 2015 [cited by applicant]
US 9141625B1 · Thornewell et al. · 2015 [cited by applicant]
US 9154327B1 · Marino et al. · 2015 [cited by applicant]
US 9354912B1 · Aron · 2016 [cited by examiner]
US 9652265B1 · Narayanasamy · 2017 [cited by examiner]
US 9712486B2 · Johnson et al. · 2017 [cited by applicant]
US 9772866B1 · Aron et al. · 2017 [cited by applicant]
US 9813303B1 · Guigli · 2017 [cited by applicant]
US 10210567B2 · Mick et al. · 2019 [cited by applicant]
US 10268593B1 · Olson · 2019 [cited by examiner]
US 10447806B1 · Sahay · 2019 [cited by examiner]
US 10637724B2 · Johnson et al. · 2020 [cited by applicant]
US 10637916B2 · Ding · 2020 [cited by examiner]
US 10693715B1 · Strauss et al. · 2020 [cited by applicant]
US 10708082B1 · Bakiaraj et al. · 2020 [cited by applicant]
US 10742557B1 · Miriyala et al. · 2020 [cited by applicant]
US 10862852B1 · Thunga et al. · 2020 [cited by applicant]
US 10902062B1 · Guha · 2021 [cited by examiner]
US 10921991B1 · Olson · 2021 [cited by examiner]
US 11108629B1 · Cahyadi et al. · 2021 [cited by applicant]
US 11159366B1 · Gawade et al. · 2021 [cited by applicant]
US 11196591B2 · Hira et al. · 2021 [cited by applicant]
US 11316822B1 · Gawade et al. · 2022 [cited by applicant]
US 11611618B2 · Nijhawan et al. · 2023 [cited by applicant]
US 20050257072A1 · Cross · 2005 [cited by examiner]
US 20060253570A1 · Biswas · 2006 [cited by examiner]
US 20100077158A1 · Asano · 2010 [cited by examiner]
US 20100191779A1 · Hinrichs · 2010 [cited by examiner]
US 20100228798A1 · Kodama · 2010 [cited by examiner]
US 20110282975A1 · Carter · 2011 [cited by examiner]
US 20120117229A1 · Van Biljon · 2012 [cited by examiner]
US 20120233668A1 · Leafe · 2012 [cited by examiner]
US 20130104251A1 · Moore et al. · 2013 [cited by applicant]
US 20130136123A1 · Ge et al. · 2013 [cited by applicant]
US 20130205028A1 · Crockett · 2013 [cited by examiner]
US 20130238785A1 · Hawk · 2013 [cited by examiner]
US 20140025816A1 · Otani · 2014 [cited by applicant]
US 20140052877A1 · Mao · 2014 [cited by applicant]
US 20140222917A1 · Poirier · 2014 [cited by examiner]
US 20140282889A1 · Ishaya · 2014 [cited by examiner]
US 20140317314A1 · Nigam · 2014 [cited by examiner]
US 20140337500A1 · Lee · 2014 [cited by examiner]
US 20150036541A1 · Xu et al. · 2015 [cited by applicant]
US 20150095788A1 · Thiele et al. · 2015 [cited by applicant]
US 20150120887A1 · Hu et al. · 2015 [cited by applicant]
US 20150121370A1 · Beisiegel · 2015 [cited by examiner]
US 20160105471A1 · Nunes et al. · 2016 [cited by applicant]
US 20160203528A1 · Saha et al. · 2016 [cited by applicant]
US 20160216909A1 · Provenzano · 2016 [cited by examiner]
US 20160218947A1 · Hughes et al. · 2016 [cited by applicant]
US 20160218991A1 · Sharabi et al. · 2016 [cited by applicant]
US 20160248732A1 · Kolesnik · 2016 [cited by examiner]
US 20160285970A1 · Cai · 2016 [cited by examiner]
US 20160337272A1 · Berman · 2016 [cited by applicant]
US 20160352735A1 · Zou · 2016 [cited by examiner]
US 20160357642A1 · Burshan et al. · 2016 [cited by applicant]
US 20170033976A1 · Ahmed et al. · 2017 [cited by applicant]
US 20170093790A1 · Banerjee · 2017 [cited by examiner]
US 20170093910A1 · Gukal · 2017 [cited by examiner]
US 20170163475A1 · Olson · 2017 [cited by examiner]
US 20170171019A1 · Nayak et al. · 2017 [cited by applicant]
US 20170180211A1 · Johnson · 2017 [cited by examiner]
US 20170223117A1 · Messerli · 2017 [cited by examiner]
US 20170310706A1 · Wu · 2017 [cited by examiner]
US 20180011874A1 · Lacapra et al. · 2018 [cited by applicant]
US 20180026904A1 · Van De Groenendaal · 2018 [cited by examiner]
US 20180049043A1 · Hoffberg et al. · 2018 [cited by applicant]
US 20180063231A1 · Park · 2018 [cited by applicant]
US 20180063233A1 · Park · 2018 [cited by applicant]
US 20180067866A1 · Shanbhogue · 2018 [cited by examiner]
US 20180227243A1 · Zhang et al. · 2018 [cited by applicant]
US 20180227244A1 · Zhang et al. · 2018 [cited by applicant]
US 20180242154A1 · Ballard et al. · 2018 [cited by applicant]
US 20180248743A1 · Chandrashekhar et al. · 2018 [cited by applicant]
US 20180351851A1 · Parthasarathy · 2018 [cited by examiner]
US 20190097900A1 · Rodriguez · 2019 [cited by examiner]
US 20190109783A1 · Kommula et al. · 2019 [cited by applicant]
US 20190158353A1 · Johnson et al. · 2019 [cited by applicant]
US 20190166192A1 · Ding · 2019 [cited by examiner]
US 20190212944A1 · Hutchison · 2019 [cited by examiner]
US 20190243687A1 · Chen · 2019 [cited by examiner]
US 20190268421A1 · Markuze · 2019 [cited by examiner]
US 20190278483A1 · Mahmood · 2019 [cited by examiner]
US 20190332575A1 · Aron · 2019 [cited by examiner]
US 20190342160A1 · Baddepudi · 2019 [cited by examiner]
US 20190349426A1 · Smith et al. · 2019 [cited by applicant]
US 20200026579A1 · Bahramshahry · 2020 [cited by examiner]
US 20200034063A1 · Somasundaram · 2020 [cited by examiner]
US 20200099745A1 · Diaconu · 2020 [cited by examiner]
US 20200125690A1 · Kim · 2020 [cited by examiner]
US 20200134479A1 · Parthasarathy · 2020 [cited by applicant]
US 20200175854A1 · Dousse · 2020 [cited by examiner]
US 20200177452A1 · Schardt · 2020 [cited by examiner]
US 20200225924A1 · Sathyanarayanamurthy · 2020 [cited by examiner]
US 20200225925A1 · Sathyanarayanamurthy · 2020 [cited by examiner]
US 20200250153A1 · Krivenok · 2020 [cited by applicant]
US 20200280492A1 · Devireddy · 2020 [cited by applicant]
US 20200344296A1 · Jain et al. · 2020 [cited by applicant]
US 20200394071A1 · Panse et al. · 2020 [cited by applicant]
US 20200396176A1 · Lochhead · 2020 [cited by applicant]
US 20200396179A1 · Lochhead et al. · 2020 [cited by applicant]
US 20200396181A1 · Lochhead et al. · 2020 [cited by applicant]
US 20200401457A1 · Singhal et al. · 2020 [cited by applicant]
US 20210067468A1 · Cidon et al. · 2021 [cited by applicant]
US 20210132928A1 · Xiao · 2021 [cited by examiner]
US 20210218672A1 · Mackie · 2021 [cited by examiner]
US 20210224093A1 · Fu · 2021 [cited by examiner]
US 20210234715A1 · Liu et al. · 2021 [cited by applicant]
US 20210311760A1 · Oki et al. · 2021 [cited by applicant]
US 20210334004A1 · Krivenok · 2021 [cited by applicant]
US 20210350596A1 · Nunez · 2021 [cited by applicant]
US 20210360075A1 · Islam · 2021 [cited by examiner]
US 20210367884A1 · Drake et al. · 2021 [cited by applicant]
US 20220124150A1 · Alagna · 2022 [cited by examiner]
US 20220206832A1 · Berry et al. · 2022 [cited by applicant]
US 20220210226A1 · Nijhawan et al. · 2022 [cited by applicant]
US 20220357958A1 · Deokule · 2022 [cited by examiner]
US 20230025529A1 · Fu · 2023 [cited by examiner]
US 20230362245A1 · Nijhawan et al. · 2023 [cited by applicant]
CN 104935455A · 2015 [cited by applicant]
CN 107454019 · 2017 [cited by applicant]
CN 109565467 · 2019 [cited by applicant]
EP 3731461 · 2020 [cited by applicant]
JP 2016039531 · 2016 [cited by applicant]
JP 2020510325 · 2020 [cited by applicant]
WO WO2005076553A1 · 2005 [cited by examiner]
WO WO2005106659 · 2005 [cited by applicant]
WO WO2005106659A1 · 2005 [cited by examiner]
WO WO2014041394 · 2014 [cited by applicant]
WO WO2014041394A1 · 2014 [cited by examiner]
WO WO2015069573 · 2015 [cited by applicant]
WO WO2015123849 · 2015 [cited by applicant]
WO WO2015180056 · 2015 [cited by applicant]
WO WO2016069382 · 2016 [cited by applicant]
WO WO2016165139 · 2016 [cited by applicant]
WO WO2016165142 · 2016 [cited by applicant]
WO WO2018134911 · 2018 [cited by applicant]
WO WO2022019930 · 2022 [cited by applicant]
WO WO2022019930A1 · 2022 [cited by examiner]
Poitras, Steven. “The Nutanix Bible” (Oct. 15, 2013), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jan. 11, 2014), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jun. 20, 2014), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jan. 7, 2015), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jun. 9, 2015), from http://stevenpoitras.com/the-nutanix-bible/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Sep. 4, 2015), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jan. 12, 2016), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jun. 9, 2016), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jan. 3, 2017), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jun. 8, 2017), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jan. 3, 2018), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jun. 25, 2018), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jan. 8, 2019), from https://nutanixbible.com/. [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jul. 9, 2019), from https://nutanixbible.com/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Feb. 3, 2020), from https://nutanixbible.com/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Aug. 1, 2020), from https://nutanixbible.com/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Poitras, Steven. “The Nutanix Bible” (Jan. 30, 2021), from https://nutanixbible.com/ (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Cano, I. et al., “Curator: Self-Managing Storage for Enterprise Clusters”, 14th USENIX Symposium on Networked Systems Design and Implementation, NSDI '17, (Mar. 27, 2017). [cited by applicant]
“A Simple, Scalable Way to Extend Your Connectivity Reach Across Data Centers,” Equinix, copyright 2019. [cited by applicant]
Bowker, M., “Interconnection Amplifies the Value of Bare Metal Deployments,” ESG White Paper, The Enterprise Strategy Group, Inc., dated Oct. 2020. [cited by applicant]
“Building Stateless/Diskless Images,” IBM Corporation, date found via Internet Archive as Sep. 14, 2016, URL: https://xcat-docs.readthedocs.io/en/stable/advanced/mixed_cluster/building_stateless_images.html. [cited by applicant]
“Node images,” Google Cloud, date found via Internet Archives are Jul. 18, 2021, URL: https://cloud.google.com/kubernetes-engine/docs/concepts/node-images. [cited by applicant]
“Specifying a node image,” Google Cloud, date found via Internet Archives as Aug. 16, 2021, URL: https://cloud.google.com/kubernetes-engine/docs/how-to/node-images. [cited by applicant]
Vallée, G., et al., “SSI-OSCAR: a Cluster Distribution for High Performance Computing Using a Single System Image,” Proceedings of the 19th International Symposium on High Performance Computing Systems and Applications,… [cited by applicant]
“Bigstep Metal Cloud vs AWS”, Bigstep, date found via Internet Archive as Feb. 14, 2020, URL: https://bigstep.com//bigstep-vs-aws. [cited by applicant]
“Metal Cloud Distributed MicroSAN Storage,” Bigstep, date found via Internet Archive as Feb. 14, 2020, URL: https://bigstep.com//distributed-storage. [cited by applicant]
“Looking for an alternative to Dedicated Servers?,” Bigstep, date found via Internet Archive as Jul. 27, 2020, URL: https://bigstep.com//bigstep-vs-dedicated-servers. [cited by applicant]
“Bigstep Container Service,” Bigstep, date found via Internet Archive as Feb. 14, 2020, URL: https://bigstep.com//products/bigstep-container-service. [cited by applicant]
“An Infrastructure as a Service Serious Wordbook,” Bigstep, dated Apr. 3, 2019, URL: https://bigstep.com/blog/an-infrastructure-as-a-service-serious-wordbook. [cited by applicant]
Lim, E., et al., “Self-provisioning and configuration system for heterogeneous diskless cluster system,” IEEE, dated 2015. [cited by applicant]
“Bigstep delivers giant leap in performance with Full Metal Cloud,” Hewlett Packard Enterprise, date found via Google as Feb. 15, 2016. [cited by applicant]
Pintoiu, C., “MongoDB vs DocumentDB,” BigStep, date found via Google as Apr. 1, 2019. [cited by applicant]
Non-Final Office Action dated May 12, 2022 for related U.S. Appl. No. 17/139,541. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/187,698 dated May 17, 2022. [cited by applicant]
Aviatrix Systems, “Aviatrix Transit Architecture for Azure”, Aviatrix Docs, (Oct. 28, 2020), (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Aviatrix Systems, “Aviatrix Next Gen Transit with customized SNAT and DNAT features”, Aviatrix Docs, (Oct. 28, 2020), (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Aviatrix Systems, “Gateway”, Aviatrix Docs, (Oct. 28, 2020), (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
VMware, “Deploy the NSX Public Cloud Gateway”, VMware Docs, (Jun. 19, 2020). [cited by applicant]
VMware, “Azure VMware Solution Planning and Deployment Guide”, (Sep. 1, 2021), (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Chebaro, S. “Step By Step Deploy VMware NSX with Microsoft Azure IPSEC VPN Site-to-Site”, Zero to Hero, (Mar. 17, 2017). [cited by applicant]
IBM, “Planning for Bare Metal Servers on VPC”, IBM Cloud Docs, (Last updated Jan. 21, 2022). [cited by applicant]
IBM, “VMware NSX-T logical routers on VPC deployments”, IBM Cloud Docs, (Last updated Jun. 21, 2022). [cited by applicant]
Google, “Private access options for services”, Google Cloud, (Last updated Nov. 16, 2020). [cited by applicant]
Google, “Private Google Access”, Google Cloud, (Last updated May 12, 2021). [cited by applicant]
Hosken, M. et al., “Data Center Modernization with VMware Cloud on AWS”, VMware, First edition, (Sep. 2019). [cited by applicant]
AWS, “Example routing options”, Amazon Virtual Private Cloud, user guide, (Oct. 26, 2020), (Publication date based on indicated capture date by Archive.org; first publication date unknown). [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/187,698 dated Nov. 16, 2022. [cited by applicant]
Final Office Action for U.S. Appl. No. 17/139,541 dated Nov. 28, 2022. [cited by applicant]
Notice of Allowance dated Mar. 29, 2023 for U.S. Appl. No. 17/139,541. [cited by applicant]
Kumar, R., et al., “Open Source Infrastructure for Cloud Computing Platform Using Eucalyptus,” Global Journal of Computers & Technology, vol. 1, No. 2, dated Dec. 24, 2014, ISSN: 2394-501X. [cited by applicant]
Jacquemart, Q., et al., “D3.3—Inter-site Network Virtualization Orchestrator,” dated May 3, 2018. [cited by applicant]
Janiszewski, C., et al., “A blueprint for OpenStack and bare metal,” Red Hat Blog, URL: https://www.redhat.com/en/blog/blueprint-openstack-and-bare-metal, dated Dec. 3, 2019. [cited by applicant]
“Oracle® SuperCluster M8 and SuperCluster M7 Security Guide,” Oracle, dated Jun. 2020. [cited by applicant]
“Sparc M8 and Sparc M7 Servers Administration Guide,” Oracle, dated Sep. 2017. [cited by applicant]
“Multi-tenant design considerations for Amazon EKS clusters,” AWS, URL: https://aws.amazon.com/blogs/containers/multi-tenant-design-considerations-for-amazon-eks-clusters/, dated Mar. 27, 2020. [cited by applicant]
Ango, A., “How to create a Kubernetes cluster on Amazon EKS in GitLab,” dated Mar. 9, 2020. [cited by applicant]
“Managed Kubernetes Clusters,” AWS, URL: https://web.archive.org/web/20201129204035/https://aws.amazon.com/eks/features/, date found via Internet Archive as Nov. 29, 2020. [cited by applicant]
“Cluster VPC considerations,” AWS, URL: https://web.archive.org/web/20201201060045/https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html, date found via Internet Archive as Dec. 1, 2020. [cited by applicant]
Lokare, “Secure Multi-Tenancy for Enterprises and Managed Service Providers,” Diamanti, dated Jul. 27, 2020. [cited by applicant]
“Federated Kubernetes for Stateful Applications,” Diamanti, date found via Internet Archive as Aug. 7, 2020. [cited by applicant]
“Diamanti Spektra 3.0 Simplifies Hybrid Cloud for Kubernetes Applications,” Diamanti, dated Jun. 30, 2020. [cited by applicant]
“Multiple Tenant Access to a Shared Storage Cluster Using Kubernetes,” Nexenta, URL: https://nexentaedge.io/docs/multi-tenancy-considerations.html, date found via Google as May 2, 2018. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 18/114,946 dated Jan. 5, 2024. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/114,946 dated Sep. 5, 2024. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/114,946 dated Jun. 25, 2024. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/114,946 dated Jan. 3, 2025. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/114,946 dated May 1, 2025. [cited by applicant]