cloudgenix_vff_push_config
Synopsis
Helper script to PUSH a Virtual Form Factor (VFF) config to a newly booted virtual ION waiting for config.
Available methods:
- Serial (requires knowledge of tty/pty path of serial port)
- Serial also requires PySerial module, which may need an additional install.
- Telnet (KVM serial redirect to TCP port/telnet style)
- virsh console (KVM/QEMU without serial)
- SSH (for AWS/GCE/Azure - Can use password or private key.)
Requirements
- Active CloudGenix Account
- Python >= 2.7 or >=3.6
- Python modules:
- pyserial >= 3.0 - https://pythonhosted.org/pyserial/
- pexpect >= 4.0 - https://pexpect.readthedocs.io/en/stable/
Installation
Available via PIP - pip install cloudgenix_vff_push_config.
PIP should add a vff_push_config or vff_push_config.exe command to the path.
Examples
Example configuration files for CloudGenix Virtual Form Factors (VFF) are in ./example_configs subdirectory. For more info on the CloudGenix VFF config file options, see https://support.cloudgenix.com
Serial example usage:
aaron@partner-lab-traf:~/vff_push_config$ sudo vff_push_config serial --file ./example_configs/example.cfg --pty /dev/pts/2
[VFF_PUSH] Starting VFF Config Push script.
[VFF_PUSH] Current directory is /home/aaron/vff_push_config
[VFF_PUSH] Successfully loaded 373 chars from ./example_configs/example.cfg.
[VFF_PUSH_SERIAL] Opening /dev/pts/2
[VFF_PUSH_SERIAL] 1 Got config prompt. Continuing.
[VFF_PUSH_SERIAL] Setting up config push.
[VFF_PUSH_SERIAL] Config successfully sent! Exiting.
aaron@partner-lab-traf:~/vff_push_config$
Telnet example usage:
aaron@partner-lab-traf:~/vff_push_config$ vff_push_config telnet --file ./example_configs/example.cfg --host 127.0.0.1 --port 4000
[VFF_PUSH] Starting VFF Config Push script.
[VFF_PUSH] Current directory is /home/aaron/vff_push_config
[VFF_PUSH] Successfully loaded 373 chars from ./example_configs/example.cfg.
[VFF_PUSH_TELNET] Opening 127.0.0.1:4000
[VFF_PUSH_TELNET] 127.0.0.1:4000 Opened
[VFF_PUSH_TELNET] 1 Got config prompt. Continuing.
[VFF_PUSH_TELNET] Setting up config push.
[VFF_PUSH_TELNET] Config successfully sent! Exiting.
aaron@partner-lab-traf:~/vff_push_config$
Virsh console example usage:
aaron@partner-lab-traf:~/vff_push_config$ vff_push_config virsh --domain Test_script_kvm4_ion_1 --file example_configs/example.yaml
[VFF_PUSH] Starting VFF Config Push script.
[VFF_PUSH] Current directory is /home/aaron/vff_push_config
[VFF_PUSH] Successfully loaded 380 chars from example_configs/example.yaml.
[VFF_PUSH_VIRSH] Launched '/usr/bin/virsh console Test_script_kvm4_ion_1', waiting for prompt.
[VFF_PUSH_VIRSH] 1 Got config prompt. Continuing.
[VFF_PUSH_VIRSH] Setting up config push.
[VFF_PUSH_VIRSH] Config successfully sent! Exiting.
aaron@partner-lab-traf:~/vff_push_config$
SSH console example usage:
aaron@partner-lab-traf:~/vff_push_config$ vff_push_config ssh --file example_configs/example.yaml --host 172.22.5.244 --user virtualsetup --privkey ../TME-LAB-CONTROLLER.pem
[VFF_PUSH] Starting VFF Config Push script.
[VFF_PUSH] Current directory is /home/aaron/vff_push_config
[VFF_PUSH] Successfully loaded 380 chars from example_configs/example.yaml.
[VFF_PUSH_SSH] Connecting to virtualsetup@172.22.5.244:22, Password: No, Private Key: Yes. Waiting for prompt.
[VFF_PUSH_SSH] 1 Got config prompt. Continuing.
[VFF_PUSH_SSH] Setting up config push.
[VFF_PUSH_SSH] Config successfully sent! Exiting.
aaron@partner-lab-traf:~/vff_push_config$
KVM/QEMU specific notes:
- To set up serial port pty - add
--serial=ptyto virt-install command.- To determine pty filename, do
virsh dumpxml "VMNAME" | grep console | grep pty. Example Output:<console type='pty' tty='/dev/pts/2'>
- To determine pty filename, do
- To set up serial port telnet listener - add
--serial tcp,host=<IF IP or 0.0.0.0>:<TCP PORT>,mode=bind,protocol=telnetto virt-install command.
License
MIT
Version
| Version | Changes |
|---|---|
| 1.1.1 | Fix parser_type and global config file data |
| 1.1.0 | Updated with Dynamic menu item support, and minor fixes. |
| 1.0.0 | Initial Release. |
Metadata
Release files for cloudgenix_vff_push_config 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cloudgenix_vff_push_config-1.1.1.tar.gz | 6.7 kB | Without provenance | Details for cloudgenix_vff_push_config-1.1.1.tar.gz |
Release files / cloudgenix_vff_push_config-1.1.1.tar.gz
| Download URL | cloudgenix_vff_push_config-1.1.1.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45c73bddbdf66a4513ccece04dc9528c6c4ccdf7ff3f5f05596536b08eebea62
|
|
BLAKE2b-256 checksum How to use checksums |
cad9fe9291f0dea58a87fa0fbd1fe8d0d0bc19acfeab874c2ac6693a7ecbb7f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cloudgenix_vff_push_config 1.1.1
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.