# 2. Create a Catalog
## **Overview**
A catalog is a container for vApp templates\ VM templates, and media files in an organization.
HI GIO provides a public catalog that contains standard virtual machine (VM) sizes and operating systems.
The public catalog is a good place to start when deploying VMs into the HI GIO. However, you may want to create your catalogs containing specific application images, which you can then use to deploy VMs quickly.
## **Procedure**
{% tabs %}
{% tab title="I. Create a catalog" %}
**Step 1:** In the menu bar, select **Libraries**.
**Step 2:** In the left navigation panel, under **Content Libraries**, select **Catalogs** >> **NEW**
**Step 3:** In the *Create Catalog* dialog box, enter a **Name** for the catalog and give it a **Description** (optional).
**Step 4:** To specify a particular storage policy for the catalog, select the **Pre-provision on specific storage policy option,** then select the **Storage Policy**
**Step 5:** When you're done, click **OK**.
**Step 6:** To make the catalog visible to others within your organization, click the three vertical dots and select **Share**.
**Step 7:** In the Share Catalog dialog box, from the *Share with*, select:
* **All Users and Groups** are to share the catalog with everyone in the organization.
* **Specific Users and Groups** to share the catalog with individual or group users. With permission: **Read Only**, **Read/Write** or **Full Control**.
8\. Click **Save** to complete.
{% endtab %}
{% tab title="II. Upload Media Files" %}
You can upload new media files or new versions of existing media files to a catalog. Users accessing the catalog can open the media files with their virtual machines.
**Prerequisites:** This operation requires the rights included in the predefined Catalog Author role or an equivalent set of rights.
**Step 1:** In the top navigation bar, click **Libraries,** and in the left panel, select **Media & Other** >>**Add**.
**Step 2:** In the **Upload Media** dialog box:
Select the **Catalog** to which you want to upload the media.
Enter a **Name** for the media If you do not enter a name, the name text box automatically uses the name of the media file.
Click the **Upload** icon and browse to the image file you want to upload.
**Step 3:** Click OK.
Depending on the file size, the upload might take some time to complete. You can monitor the status of the upload in the **Recent Tasks** view.
{% endtab %}
{% tab title="III. Upload OVF Package as a vApp Template" %}
HI GIO supports the Open Virtualization Format (OVF) and Open Virtualization Appliance (OVA) specifications. If you upload an OVF file that includes OVF properties for customizing its virtual machines, those properties are preserved in the vApp template.
1. In the top navigation bar, click **Libraries** and in the left panel, select **vApp Templates** >> **New**
2\. Enter a URL address of the OVF file or click the **Upload** icon to browse to a location accessible from your computer and select the OVF/OVA template file.
**\*\*** The location might be your local hard drive, a network share, or a CD/DVD drive. The supported file extensions include .ova, .ovf, .vmdk, .mf, .cert, and .strings. If you select to upload an OVF file, which references more files than you are trying to upload. For example, a VMDK file, you must browse and select all files.
3\. Verify the details of the OVF/OVA template you are about to deploy and click **Next**.
4\. Enter a **Name**, **Description** (optionally) for the vApp template.
From the **Catalog** drop-down menu, select the catalog, to which you want to add the template and click **Next**.
5\. Review the vApp template settings and click **Finish**
{% endtab %}
{% endtabs %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.higiocloud.vn/management/2.-create-a-catalog.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
