# openstackclient mit Homebrew, Nix installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für openstackclient in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:openstackclient ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install openstackclient ``` Evidenz: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#openstackclient ``` Evidenz: nixpkgs package indexes: openstackclient from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## Paketfakten - **Paketschlüssel:** brew:openstackclient - **Paketmanager:** Homebrew - **Version:** 10.2.1 - **Quellzusammenfassung:** Command-line client for OpenStack - **Homepage:** - **Zuletzt aktualisiert:** 2026-07-16T10:33:25Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - openstack (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 10.2.1 ## Projektgeschichte und Nutzung OpenStackClient, also packaged as `python-openstackclient`, is the unified `openstack` command-line interface for OpenStack clouds. It brings commands for services such as Compute, Identity, Image, Network, Object Store, and Block Storage into one command structure, replacing the older habit of juggling service-specific CLIs such as `nova`, `glance`, and `keystone`. ### Projektgeschichte OpenStack’s early client experience mirrored its service architecture: each major project shipped its own Python client and CLI. The UnifiedCLI proposal documented the pain of inconsistent commands, options, and terminology, and proposed a single OpenStack CLI that reused existing client modules where possible rather than duplicating every REST implementation. The `python-openstackclient` project turned that design goal into the `openstack` binary. Its documentation states the primary goal as a unified shell command structure and common language for OpenStack operations, with additional service APIs available through plugins. ### Adoptionsgeschichte OpenStackClient became the operator-facing CLI because it matched how cloud administrators and users actually work: they create projects, images, networks, volumes, servers, users, roles, and quotas across service boundaries. OpenStack release notes track OpenStackClient versions alongside OpenStack named releases, emphasizing cross-release compatibility instead of a one-client-per-cloud-version model. Distributions and package managers package it as a Python application because OpenStack deployments often rely on scripted administration. Debian describes it as a thin wrapper over the stock Python service client modules, which captures its role as a unifying front end over the OpenStack client ecosystem. ### Wie es verwendet wird Operators configure authentication through environment variables, command-line options, or `clouds.yaml`, then use `openstack` commands for day-to-day cloud administration and automation. Output format options such as table, JSON, YAML, CSV, and value-oriented output make it useful both for humans and scripts. The CLI is also a compatibility layer for OpenStack documentation and support: operational runbooks can say `openstack server list` or `openstack network create` without teaching users which legacy service-specific binary owns each resource. ### Warum Paket-Nerds sich dafür interessieren The package is interesting because it is less a standalone tool than a negotiated interface across a large plugin-heavy cloud platform. Its dependency graph, Python compatibility, OpenStackSDK integration, and release-series mapping matter to anyone packaging private-cloud tooling. ### Zeitleiste - 2010: OpenStack began as an open-source cloud platform, creating the multi-service client problem that OpenStackClient later addressed. - 2010s: the UnifiedCLI design documented the plan for a single OpenStack command structure over service-specific clients. - 2014: OpenStack Juno-era packaging used OpenStackClient 0.4.1, showing the tool’s early place in named OpenStack release cycles. - 2023: Antelope/2023.1 release notes mapped OpenStackClient 6.1.0 to that OpenStack release. ### Related projects - Related packages include OpenStackSDK and service clients such as python-novaclient, python-glanceclient, python-cinderclient, python-neutronclient, and python-keystoneclient. OpenStackClient sits above them as the consistent user-facing shell. ### Quellen - - - - - ## Sicherheitshinweise Für openstackclient wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ~/.config/openstack/clouds.yaml, ~/.config/openstack/secure.yaml ## Credential files - Unix: ~/.config/openstack/clouds.yaml, ~/.config/openstack/secure.yaml ## Andere Paketmanager-Einträge - Nix - openstackclient: normalized package name match | nixpkgs package indexes: openstackclient from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## Combined YAML source View the package source record on GitHub. [combined/openstackclient.yml](https://github.com/mxcl/pkgdb/blob/main/combined/openstackclient.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph