> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-3/command-line-path.md).

# Command-line path

OpenStackClient calls the same service APIs from a shell. This path is an alternative to Horizon, not a continuation of it. We use a clean practice project, remove the dashboard-created resources first or choose distinct names.

The command-line path makes discovery and returned identifiers explicit. It first verifies the scoped profile, then resolves the image identifier, flavor, networks, volume type, Nova availability zone, Cinder availability zone and quota. A network becomes the floating-IP pool only after Neutron reports `router:external: true` and `status: ACTIVE`.

```bash
CLOUD=my-cloud
IMAGE_ID=$(openstack --os-cloud "$CLOUD" image show ubuntu -f value -c id)
openstack --os-cloud "$CLOUD" network show external-network \
  -f json -c id -c status -c "router:external"
openstack --os-cloud "$CLOUD" availability zone list --compute
openstack --os-cloud "$CLOUD" availability zone list --volume
```

The full creation sequence uses the immutable image ID, bounded waits and the floating address returned by Neutron. It stops on API errors, terminal error states and timeouts. After creation, validation follows stable identifiers across services:

```bash
SERVER_ID=$(openstack --os-cloud "$CLOUD" server show web-01 -f value -c id)
PORT_IDS=$(openstack --os-cloud "$CLOUD" port list --server "$SERVER_ID" -f value -c ID)
set -- $PORT_IDS
[ "$#" -eq 1 ] || exit 1
PORT_ID=$1

[ "$(openstack --os-cloud "$CLOUD" port show "$PORT_ID" -f value -c device_id)" = "$SERVER_ID" ] || exit 1
```

This single relationship is only the first check. Acceptance also compares the security-group ID attached to the port, the floating IP's `port_id` and the Cinder attachment's `server_id`. [Lab 04](https://git.vanillacore.net/giga/content/src/branch/main/chapter-3/lab/walkthroughs/04-cli-provisioning.md) contains the complete creation path. [Lab 06](https://git.vanillacore.net/giga/content/src/branch/main/chapter-3/lab/walkthroughs/06-combined-validation.md) contains the combined read-back. The companion videos are [C3-P4](https://git.vanillacore.net/giga/content/src/branch/main/chapter-3/VIDEO_SCOPES.md#user-content-c3-p4-provision-the-request-with-openstackclient) and [C3-P6](https://git.vanillacore.net/giga/content/src/branch/main/chapter-3/VIDEO_SCOPES.md#user-content-c3-p6-prove-the-cross-service-resource-chain).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-3/command-line-path.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.