IP Library Granted Patent US 12,401,718
Granted Patent B2
US 12,401,718 · App. 18/114,946 · Granted Aug 26, 2025

Orchestrating allocation of shared resources in a datacenter

Inventors: Aman Nijhawan (Seattle, WA); Anil Kumar Kushwah (Bengaluru, IN); Avi Bhandari (San Jose, CA); Jan Ralf Alexander Olderdissen (Herrenberg, DE)
Assignee: Nutanix, Inc.
H04L67/1097G06F9/45541G06F13/4027H04L49/351H04L49/354
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,401,718
App. No.
18/114,946
Filed
Feb 27, 2023
Granted
Aug 26, 2025
Kind
B2
Art Unit
2446
USPC
709/219
Abstract

A cluster configuration request to form a hyperconverged computing infrastructure (HCI) cluster in a cloud computing environment is processed. Based on the cluster configuration request and any other cluster specifications, a plurality of bare metal computing nodes of the cloud computing environment are configured to operate as an HCI cluster. First, a tenant-specific secure network overlay is formed on a first set of tenant-specific networking hardware resources. Then, the tenant-specific secure network overlay is used by an orchestrator to provision a second set of tenant-specific networking hardware resources. The second set of tenant-specific networking hardware resources are configured to interconnect node-local storage devices into a shared storage pool having a contiguous address space. Top-of-rack switches are configured to form a network overlay on the first set of tenant-specific networking hardware resources. Then, top-of-rack switches are configured to form a layer-2 subnet on the second set of tenant-specific networking hardware resources.

Claims (38)

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 a set of acts comprising:

in a cloud computing environment comprising a plurality of bare metal computing nodes, configuring computing environments for separate tenants form the plurality of bare metal computing nodes, at least by:

forming, for a first tenant, a first computing environment comprising a first cluster formed from a first set of bare metal computing nodes of the plurality of bare metal computing nodes by provisioning a first secure network overlay and using the first secure network overlay to provision a first bootstrapping node, wherein the first bootstrapping node configure the first set of bare metal computing nodes over the first secure network overlay;

forming, for a second tenant, a second computing environment comprising a second cluster formed from a second set of bare metal computing nodes of the plurality of bare metal computing nodes by provisioning a second secure network overlay and using the second secure network overlay to provision a second bootstrapping node, wherein the second bootstrapping node configure the second set of bare metal computing nodes over the second secure network overlay, and the second secure network overlay being separate and isolated from the first secure network overlay; and

whereby the first set of bare metal computing nodes of the first tenant are isolated from the second set of bare metal computing nodes of the second tenant.

2. The non-transitory computer readable medium of claim 1 , wherein the set of acts further comprise adding an additional bare metal computing node of the plurality of bare metal computing nodes to the first cluster.

3. The non-transitory computer readable medium of claim 2 , wherein the first secure network overlay is used to provision the additional bare metal computing node.

4. The non-transitory computer readable medium of claim 1 , wherein configuring computing environments further comprises configuring per-tenant firewalls for the first and second tenants.

5. The non-transitory computer readable medium of claim 1 , wherein the set of acts further comprise assigning a tenant-specific identity to the bare metal computing nodes of the first cluster.

6. The non-transitory computer readable medium of claim 1 , wherein the set of acts further comprise configuring a top-of-rack switch to form a VxLAN as a network overlay.

7. The non-transitory computer readable medium of claim 1 , wherein the set of acts further comprise configuring a first top-of-rack switch to form a layer-2 network that interconnects the first set of bare metal computing nodes.

8. The non-transitory computer readable medium of claim 7 , wherein the set of acts further comprise configuring a second top-of-rack switch using a VxLAN to extend the layer-2 network to operate as a common subnet that spans from the first top-of-rack switch to the second top-of-rack switch.

9. A method comprising:

in a cloud computing environment comprising a plurality of bare metal computing nodes, configuring computing environments for separate tenants from the plurality of bare metal computing nodes, at least by:

forming, for a first tenant, a first computing environment comprising a first cluster formed from a first set of bare metal computing nodes of the plurality of bare metal computing nodes by provisioning a first secure network overlay and using the first secure network overlay to provision a first bootstrapping node, wherein the first bootstrapping node configure the first set of bare metal computing nodes over the first secure network overlay;

forming, for a second tenant, a second computing environment comprising a second cluster formed from a second set of bare metal computing nodes of the plurality of bare metal computing nodes by provisioning a second secure network overlay and using the second secure network overlay to provision a second bootstrapping node, wherein the second bootstrapping node configure the second set of bare metal computing nodes over the second secure network overlay, and the second secure network overlay being separate and isolated from the first secure network overlay; and

whereby the first set of bare metal computing nodes of the first tenant are isolated from the second set of bare metal computing nodes of the second tenant.

10. The method of claim 9 , further comprising adding an additional bare metal computing node of the plurality of bare metal computing nodes to the first cluster.

11. The method of claim 10 , wherein the first secure network overlay is used to provision the additional bare metal computing node.

12. The method of claim 9 , wherein configuring computing environments further comprises configuring per-tenant firewalls for the first and second tenants.

13. The method of claim 9 , further comprising assigning a tenant-specific identity to the bare metal computing nodes of the first cluster.

14. The method of claim 9 , further comprising configuring a top-of-rack switch to form a VxLAN as a network overlay.

15. The method of claim 9 , further comprising configuring a first top-of-rack switch to form a layer-2 network that interconnects the first set of bare metal computing nodes.

16. The method of claim 15 , further comprising configuring a second top-of-rack switch using a VxLAN to extend the layer-2 network to operate as a common subnet that spans from the first top-of-rack switch to the second top-of-rack switch.

17. A system comprising:

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

a processor that executes the sequence of instructions to cause th processor to perform acts comprising,

in a cloud computing environment comprising a plurality of bare metal computing nodes, configuring computing environments for separate tenants from the plurality of bare metal computing nodes, at least by:

forming, for a first tenant, a first computing environment comprising a first cluster formed from a first set of bare metal computing nodes of the plurality of bare metal computing nodes by provisioning a first secure network overlay and using the first secure network overlay to provision a first bootstrapping node, wherein the first bootstrapping node configure the first set of bare metal computing nodes over the first secure network overlay;

forming, for a second tenant, a second computing environment comprising a second cluster formed from a second set of bare metal computing nodes of the plurality of bare metal computing nodes by provisioning a second secure network overlay and using the second secure network overlay to provision a second bootstrapping node, wherein the second bootstrapping node configure the second set of bare metal computing nodes over the second secure network overlay, and the second secure network overlay being separate and isolated from the first secure network overlay; and

whereby the first set of bare metal computing nodes of the first tenant are isolated from the second set of bare metal computing nodes of the second tenant.

18. The system of claim 17 , wherein the acts further comprise adding an additional bare metal computing node of the plurality of bare metal computing nodes to the first cluster.

19. The system of claim 18 , wherein the first secure network overlay is used to provision the additional bare metal computing node.

20. The system of claim 17 , wherein configuring computing environments further comprises configuring per-tenant firewalls for the first and second tenants.

21. The system of claim 17 , wherein the acts further comprise assigning a tenant-specific identity to the bare metal computing nodes of the first cluster.

22. The system of claim 17 , wherein the acts further comprise configuring a top-of-rack switch to form a VxLAN as a network overlay.

23. The system of claim 17 , wherein the acts further comprise configuring a first top-of-rack switch to form a layer-2 network that interconnects the first set of bare metal computing nodes.

24. The system of claim 23 , wherein the acts further comprise configuring a second top-of-rack switch using a VxLAN to extend the layer-2 network to operate as a common subnet that spans from the first top-of-rack switch to the second top-of-rack switch.

Assignments (2)
SECURITY INTEREST Recorded Feb 13, 2025
From: NUTANIX, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 070206/0463 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 27, 2023
From: NIJHAWAN, AMAN; KUSHWAH, ANIL KUMAR; BHANDARI, AVI; OLDERDISSEN, JAN RALF ALEXANDER
To: NUTANIX, INC.
Reel/Frame 062818/0708 →
Continuity (4)
Continuation 17187698 · Feb 26, 2021
Continuation In Part 17139541 · Dec 31, 2020
Provisional Application 63132729 · Dec 31, 2020
Related Publication 20230362245A1 · Nov 9, 2023
References Cited (213)
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 et al. · 2013 [cited by applicant]
US 8555383B1 · Marshall · 2013 [cited by examiner]
US 8601473B1 · Aron et al. · 2013 [cited by applicant]
US 8660129B1 · Brendel · 2014 [cited by examiner]
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 · 2015 [cited by examiner]
US 9354912B1 · Aron et al. · 2016 [cited by applicant]
US 9652265B1 · Narayanasamy et al. · 2017 [cited by applicant]
US 9712486B2 · Johnson et al. · 2017 [cited by applicant]
US 9772866B1 · Aron et al. · 2017 [cited by applicant]
US 9813303B1 · Guigli · 2017 [cited by examiner]
US 10210567B2 · Mick et al. · 2019 [cited by applicant]
US 10268593B1 · Olson et al. · 2019 [cited by applicant]
US 10447806B1 · Sahay et al. · 2019 [cited by applicant]
US 10637724B2 · Johnson et al. · 2020 [cited by applicant]
US 10637916B2 · Ding · 2020 [cited by applicant]
US 10693715B1 · Strauss · 2020 [cited by examiner]
US 10708082B1 · Bakiaraj · 2020 [cited by examiner]
US 10742557B1 · Miriyala · 2020 [cited by examiner]
US 10862852B1 · Thunga · 2020 [cited by examiner]
US 10902062B1 · Guha et al. · 2021 [cited by applicant]
US 10921991B1 · Olson et al. · 2021 [cited by applicant]
US 11108629B1 · Cahyadi · 2021 [cited by examiner]
US 11159366B1 · Gawade · 2021 [cited by examiner]
US 11196591B2 · Hira et al. · 2021 [cited by applicant]
US 11316822B1 · Gawade · 2022 [cited by examiner]
US 11611618B2 · Nijhawan · 2023 [cited by examiner]
US 20050257072A1 · Cross et al. · 2005 [cited by applicant]
US 20060253570A1 · Biswas et al. · 2006 [cited by applicant]
US 20100077158A1 · Asano · 2010 [cited by applicant]
US 20100191779A1 · Hinrichs · 2010 [cited by applicant]
US 20100228798A1 · Kodama et al. · 2010 [cited by applicant]
US 20110282975A1 · Carter · 2011 [cited by applicant]
US 20120218672A1 · Nunes et al. · 2012 [cited by applicant]
US 20120233668A1 · Leafe et al. · 2012 [cited by applicant]
US 20130104251A1 · Moore et al. · 2013 [cited by applicant]
US 20130136123A1 · Ge · 2013 [cited by examiner]
US 20130205028A1 · Crockett et al. · 2013 [cited by applicant]
US 20130238785A1 · Hawk et al. · 2013 [cited by applicant]
US 20140025816A1 · Otani · 2014 [cited by examiner]
US 20140052877A1 · Mao · 2014 [cited by examiner]
US 20140222917A1 · Poirier · 2014 [cited by applicant]
US 20140317314A1 · Nigam et al. · 2014 [cited by applicant]
US 20140337500A1 · Lee · 2014 [cited by applicant]
US 20150036541A1 · Xu · 2015 [cited by examiner]
US 20150095788A1 · Thiele · 2015 [cited by examiner]
US 20150120887A1 · Hu et al. · 2015 [cited by applicant]
US 20150121370A1 · Beisiegel et al. · 2015 [cited by applicant]
US 20160105471A1 · Nunes · 2016 [cited by examiner]
US 20160203528A1 · Saha · 2016 [cited by examiner]
US 20160216909A1 · Provenzano et al. · 2016 [cited by applicant]
US 20160218947A1 · Hughes et al. · 2016 [cited by applicant]
US 20160218991A1 · Sharabi · 2016 [cited by examiner]
US 20160248732A1 · Kolesnik et al. · 2016 [cited by applicant]
US 20160285970A1 · Cai et al. · 2016 [cited by applicant]
US 20160337272A1 · Berman · 2016 [cited by examiner]
US 20160352735A1 · Zou et al. · 2016 [cited by applicant]
US 20160357642A1 · Burshan et al. · 2016 [cited by applicant]
US 20170033976A1 · Ahmed · 2017 [cited by examiner]
US 20170093790A1 · Banerjee et al. · 2017 [cited by applicant]
US 20170093910A1 · Gukal et al. · 2017 [cited by applicant]
US 20170163475A1 · Olson · 2017 [cited by applicant]
US 20170171019A1 · Nayak · 2017 [cited by examiner]
US 20170180211A1 · Johnson · 2017 [cited by applicant]
US 20170223117A1 · Messerli et al. · 2017 [cited by applicant]
US 20170310706A1 · Wu et al. · 2017 [cited by applicant]
US 20180011874A1 · Lacapra et al. · 2018 [cited by applicant]
US 20180026904A1 · Van De et al. · 2018 [cited by applicant]
US 20180049043A1 · Hoffberg et al. · 2018 [cited by applicant]
US 20180063231A1 · Park · 2018 [cited by examiner]
US 20180063233A1 · Park · 2018 [cited by examiner]
US 20180067866A1 · Shanbhogue et al. · 2018 [cited by applicant]
US 20180227243A1 · Zhang · 2018 [cited by examiner]
US 20180227244A1 · Zhang · 2018 [cited by examiner]
US 20180242154A1 · Ballard · 2018 [cited by examiner]
US 20180248743A1 · Chandrashekhar · 2018 [cited by examiner]
US 20180351851A1 · Parthasarathy · 2018 [cited by applicant]
US 20190097900A1 · Rodriguez et al. · 2019 [cited by applicant]
US 20190109783A1 · Kommula · 2019 [cited by examiner]
US 20190158353A1 · Johnson et al. · 2019 [cited by applicant]
US 20190166192A1 · Ding · 2019 [cited by applicant]
US 20190212944A1 · Hutchison et al. · 2019 [cited by applicant]
US 20190243687A1 · Chen · 2019 [cited by applicant]
US 20190268421A1 · Markuze · 2019 [cited by examiner]
US 20190278483A1 · Mahmood et al. · 2019 [cited by applicant]
US 20190332575A1 · Aron et al. · 2019 [cited by applicant]
US 20190342160A1 · Baddepudi et al. · 2019 [cited by applicant]
US 20190349426A1 · Smith et al. · 2019 [cited by applicant]
US 20200026579A1 · Bahramshahry et al. · 2020 [cited by applicant]
US 20200034063A1 · Somasundaram et al. · 2020 [cited by applicant]
US 20200099745A1 · Diaconu et al. · 2020 [cited by applicant]
US 20200125690A1 · Kim · 2020 [cited by applicant]
US 20200134479A1 · Parthasarathy · 2020 [cited by examiner]
US 20200175854A1 · Dousse et al. · 2020 [cited by applicant]
US 20200177452A1 · Schardt et al. · 2020 [cited by applicant]
US 20200225924A1 · Sathyanarayanamurthy et al. · 2020 [cited by applicant]
US 20200225925A1 · Sathyanarayanamurthy et al. · 2020 [cited by applicant]
US 20200250153A1 · Krivenok · 2020 [cited by examiner]
US 20200280492A1 · Devireddy · 2020 [cited by examiner]
US 20200344296A1 · Jain · 2020 [cited by examiner]
US 20200394071A1 · Panse · 2020 [cited by examiner]
US 20200396176A1 · Lochhead · 2020 [cited by examiner]
US 20200396179A1 · Lochhead · 2020 [cited by examiner]
US 20200396181A1 · Lochhead · 2020 [cited by examiner]
US 20200401457A1 · Singhal · 2020 [cited by examiner]
US 20210067468A1 · Cidon · 2021 [cited by examiner]
US 20210132928A1 · Xiao · 2021 [cited by applicant]
US 20210224093A1 · Fu · 2021 [cited by examiner]
US 20210234715A1 · Liu · 2021 [cited by examiner]
US 20210311760A1 · Oki · 2021 [cited by examiner]
US 20210334004A1 · Krivenok · 2021 [cited by examiner]
US 20210350596A1 · Nunez · 2021 [cited by examiner]
US 20210360075A1 · Islam et al. · 2021 [cited by applicant]
US 20210367884A1 · Drake · 2021 [cited by examiner]
US 20220124150A1 · Alagna et al. · 2022 [cited by applicant]
US 20220206832A1 · Berry · 2022 [cited by examiner]
US 20220210226A1 · Nijhawan · 2022 [cited by examiner]
US 20220357958A1 · Deokule et al. · 2022 [cited by applicant]
US 20230025529A1 · Fu · 2023 [cited by examiner]
US 20230362245A1 · Nijhawan · 2023 [cited by examiner]
CN 104935455A · 2015 [cited by applicant]
CN 107454019A · 2017 [cited by examiner]
CN 109565467A · 2019 [cited by examiner]
EP 3731461 · 2020 [cited by applicant]
EP 3731461A1 · 2020 [cited by examiner]
JP 2016039531A · 2016 [cited by examiner]
JP 2020510325A · 2020 [cited by examiner]
WO WO2005076553 · 2005 [cited by applicant]
WO WO2005106659 · 2005 [cited by applicant]
WO WO2014041394 · 2014 [cited by applicant]
WO WO2015069573 · 2015 [cited by applicant]
WO WO2015123849A1 · 2015 [cited by examiner]
WO WO2015180056A1 · 2015 [cited by examiner]
WO WO2016069382A1 · 2016 [cited by examiner]
WO WO2016165139A1 · 2016 [cited by examiner]
WO WO2016165142A1 · 2016 [cited by examiner]
WO WO2018134911A1 · 2018 [cited by examiner]
WO WO2022019930 · 2022 [cited by applicant]
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/216,511 dated May 28, 2024. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/216,511 dated Sep. 16, 2024. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 18/216,511 dated Feb. 13, 2025. [cited by applicant]