# Artifacts

## What is an Artifact?

An artifact is simply a smaller component or informational property of a larger object, resource, or service that acts in a manner to produce or determine an intended output. It can also be defined as the logic that defines what elements of a deployment have to be installed and how. These informational pieces are created to be used for the deployment and operation of a system.

## Airctl and Helpers

The following artifacts are used to aid in the implementation and configuration of the different airctl elements.

* *airctl-.tar.gz*: This compressed file contains the airctl binary. This is the primary CLI tool used for management of the Platform9 Edge DU
* *airctl-scripts-.tar.gz*: This compact file contains all the associated scripts used by airctl
* *pf9-deploy-.tar*: This is a helper container that creates the configuration file for the Platform9 management plane
* *du-.tar.gz*: The compressed DU file includes the CentOS 7.x VM image, along with the required binaries. This VM is configured through the *pf9-deploy* and *ansible-stack* commands
* *ansible-.tar.gz*: This file contains the ansible stack utilized by the *pf9-deploy* command above

## Offline Packages

The following artifacts are primarily employed for offline (or air-gapged) edge cloud installations.

* *hostagent-.tar.gz*: This file contains the yum repo information for the platform9 agents running on the hosts. Platform9 can automatically deploy this, or it can be added using foreman
* *docker-.tar.gz*: Similar to the file above, it can be either installed using Platform9 *airctl* or using foreman
* *docker-imgs-.tar.gz*: This file contains all the docker images that Platform9 initially requires. Airctl can add it to the cache of every host.
* *pf9-kube-.tar.gz*: This file contains the packages needed for a Kubernetes multi-version implementation

## Installed File Locations

Once setup, all the installed files are located under the `/opt/pf9/airctl` directory.

{% tabs %}
{% tab title="Bash" %}

```bash
ls -alh /opt/pf9/airctl
drwxr-xr-x.  8 root root  203 Sep  9 17:05 .
drwxr-xr-x.  3 root root   20 Sep  9 17:04 ..
-rwxr-xr-x.  1  350  350  18M Sep  8 22:33 airctl
drwxr-xr-x. 12  350  350 4.0K Sep  9 17:22 ansible-stack
drwxr-xr-x.  2  350  350  113 Sep  9 17:23 conf
drwxr-xr-x.  2 root root   47 Sep  9 17:04 deploy
-rw-r--r--.  1 root root 107M Sep  9 17:05 docker-v-5.3.0-1675863.tar.gz
-rw-r--r--.  1 root root  11G Sep 13 23:21 du.qcow2
-rw-r--r--.  1 root root  17M Sep  9 17:05 hostagent-v-5.3.0-1675863.tar.gz
drwxr-xr-x.  2 root root   80 Sep  9 17:04 imgs
drwxr-xr-x.  2 root root   29 Sep  9 17:04 pf9-kube
drwxr-xr-x.  3  350  350  220 Sep  9 17:07 scripts
```

{% 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.platform9.com/self-managed-cloud-platform/5.7/sso-configuration/artifacts.md?ask=<question>
```

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.