README
- Install our code in virtualenv or user directory (not recommended to install the python package globally)
pip install titamu --user
or
virtualenv ~/titamu
cd ~/titamu
pip install titamu
-
pycurl (which is one of the dependencies) is not easy to install and the errors could be quite different for both MacOS and Linux. Use google :)
-
Set necessary environment variables as followings. You can appened the content in your ~/.bash_profile (MacOS) or ~/.bashrc (Linux)
export TITAMU_URL='https://lab-rhevm.microsoft.rdu.com/ovirt-engine/api'
export TITAMU_USERNAME='adminuser@your_domain'
export TITAMU_PASSWORD='password'
export TITAMU_CA_FILE='ca.pem'
export TITAMU_VM_PREFIX='your_vm_prefix'
export TITAMU_DEFAULT_TEMPLATE='your_preferred_template'
export TITAMU_DIST='MacOS'
- Download ca.pem. Save the ca.pem to your preferred path and set TITAMU_CA_FILE correctly. For example, export TITAMU_CA_FILE='/root/ca.pem'
$ wget '<Your RHV URL>/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA' --no-check-certificate
$ mv pki-resource\?resource\=ca-certificate\&format\=X509-PEM-CA ca.pem
- Some examples
$ titamu -h
usage: titamu [-h] {start,test,stop,show,delete,list,boot,console} ...
positional arguments:
{start,test,stop,show,delete,list,boot,console}
optional arguments:
-h, --help show this help message and exit
# To list the VMs which filters by TITAMU_VM_PREFIX environment variable
$ titamu list
+--------------------------------------+--------------------------+--------+----------------+-----------------------------+
| ID | Name | Status | Networks | Comment |
+--------------------------------------+--------------------------+--------+----------------+-----------------------------+
| cd8212b3-f208-40b0-8f31-4140d57eac9b | cchen-7u4 | DOWN | | DNS server for all gss user |
| 89c9976f-fe53-49b4-b1fd-1e7a4b86a0e1 | cchen-7u5-template | DOWN | | |
| 7f4ef4f8-1641-4145-8812-234dcec478e0 | cchen-desktop | UP | 10.72.37.242 | |
+--------------------------------------+--------------------------+--------+----------------+-----------------------------+
$ titamu show cchen-desktop
+-------------+---------------------------------------------------------------------------------------+
| Item | Value |
+-------------+---------------------------------------------------------------------------------------+
| Name | cchen-desktop |
| ID | 7f4ef4f8-1641-4145-8812-234dcec478e0 |
| Memory | 8192M |
| CPU | 4 |
| Disks | ['cchen-7u5-template_Disk1', 'ee9e366f-6930-4ab2-9eb7-095e4c22b0c7', '40G'] |
| Active Nics | ['nic1', '00:1a:4a:16:02:41', 'bcda0f88-eae7-4234-a897-5dafecc5856b', '10.72.37.242'] |
+-------------+---------------------------------------------------------------------------------------+
Metadata
Release files for titamu 0.65
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 |
|---|---|---|---|---|
| titamu-0.65.tar.gz | 8.8 kB | Without provenance | Details for titamu-0.65.tar.gz |
Release files / titamu-0.65.tar.gz
| Download URL | titamu-0.65.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e75a77825b09dcb159363d72d60e958b206328b69225467b974ce8d3ecd1050a
|
|
BLAKE2b-256 checksum How to use checksums |
bdd7d11d6a29e2f09e8e45d68ea09751ef88d4f630600a23597d15dcc3d3e4ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.8.3 requests/2.27.1 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.64.0 CPython/2.7.5
|
Security for titamu 0.65
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.