This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Create a Nutanix catalog
Create machine catalogs describes the wizards that create a machine catalog. The following information covers details specific to Nutanix virtualization environments.
Note:
Before creating a Nutanix catalog, you need to finish creating a connection to Nutanix. See Connection to Nutanix.
Create a machine catalog using a Nutanix snapshot
The snapshot you select is the template used to create the VMs in the catalog. Before creating the catalog, create images and snapshots in Nutanix. For more information, see the Nutanix documentation.
In the catalog creation wizard:
-
The Operating System and Machine Management pages do not contain Nutanix-specific information.
-
The Container or Cluster and Container page is unique to Nutanix.
-
If you deploy machines by using Nutanix AHV XI as the resources, on the Container page, select a container where the VMs’ identity disks will be placed.
-
If you deploy machines by using Nutanix AHV Prism Central (PC) as the resources, you see the Cluster and Container page. Select which cluster to use for the deployment of VMs and then a container.
-
-
On the Image page, select the image snapshot. Use the Acropolis console to rename your snapshots if needed. If you rename snapshots, restart the catalog creation wizard to see a refreshed list.
-
On the Virtual Machines page, indicate the number of virtual CPUs and the number of cores per vCPU.
-
On the NICs page, select the NIC type to filter associated networks. This option is available only for Nutanix AHV PC connections. There are two NIC types: VLAN and OVERLAY. Select one or more NICs that the master image contains and then select an associated virtual network for each NIC.
-
The Machine Identities, Domain Credentials, Scopes, and Summary pages do not contain Nutanix-specific information.
Limitation
When creating an MCS catalog with Nutanix host connection (specifically, Nutanix AHV plugin 2.7.1 and Nutanix AHV plugin 2.5.1), the hard disk size of provisioned VMs are incorrectly displayed on Studio.
- Nutanix AHV plugin 2.7.1: The size displayed is much smaller (1 GB) than the real storage size.
- Nutanix AHV plugin 2.5.1: The size displayed is much smaller (32 GB) than the real storage size.
However, this works as designed if the master image VM is a snapshot in VM.
Where to go next
- If this is the first catalog created, you are guided to create a delivery group.
- To review the entire configuration process, see Plan and build a deployment.
- To manage catalogs, see Manage machine catalogs.
More information
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.