The Architect Client
Client library and CLI for Architect API service.
Client Installation
Following steps show how to deploy and configure Architect Client.
pip install architect-client
Create configuration file /etc/architect/client.yml for client.
inventory: project-name
host: architect-api
port: 8181
username: salt
password: password
Multiple Inventory Support
If the inventory_mappings is specified, multiple inventories can be queried from the single orchestrator according to the node name.
inventory_mappings:
node.domain: project01-name
node2.domain: inventory02-name
SaltStack Integration
To setup architect as Salt master Pillar source, set following configuration to your Salt master at /etc/salt/master.d/_master.conf file.
ext_pillar:
- cmd_yaml: 'architect-salt-pillar %s'
To setup architect as Salt master Tops source, set following configuration to your Salt master at /etc/salt/master.d/_master.conf file.
master_tops:
ext_nodes: architect-salt-top
You can test the SaltStack Pillar by calling command:
$ architect-salt-pillar {{ minion-id }}
Ansible Integration
To setup architect as Ansible dynamic inventory source, set following configuration to your Ansible control node.
$ ansible -i architect-ansible-inventory
You can test the ansible inventory by calling command:
$ architect-ansible-inventory --list
Puppet Integration
To tell Puppet Server to use an ENC, you need to set two settings: node_terminus has to be set to “exec”, and external_nodes must have the path to the executable.
[master]
node_terminus = exec
external_nodes = /usr/local/bin/architect-puppet-classifier
Chef Integration
We can use -j parameter of chef-client command, It’s the path to a file that contains JSON data used to setup the client run. We pass
$ architect-chef-data {{ node_name }} {{ file_name }}.json
$ chef-client -j {{ file_name }}.json --environment _default
Client Usage
You can use the client to initialise the inventories.
$ architect-inventory-create <cluster-name> <cluster-domain>
You can use the client to initialise the SaltStack managers.
$ architect-manager-salt-create <manager-name> <manager-url> <manager-username> <manager-password>
References
Metadata
Release files for architect-client 0.8.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| architect_client-0.8.3-py2-none-any.whl | Python 2 | none | any | Details for architect_client-0.8.3-py2-none-any.whl |
Release files / architect_client-0.8.3-py2-none-any.whl
| Download URL | architect_client-0.8.3-py2-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
48fd97e0e35f8aec4b8d5e6d33e7a59b8c8c0e09f1c6b3bf790aad8bc90062cd
|
|
BLAKE2b-256 checksum How to use checksums |
1df7c3e114a280f31d02c6b136045d7a070b82aa9ad2bb4d9934f1905d28eef4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.9.1 pkginfo/1.4.1 requests/2.18.4 setuptools/38.5.2 requests-toolbelt/0.8.0 tqdm/4.19.6 CPython/2.7.15rc1
|
Security for architect-client 0.8.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.