20db6bd9b2
Proxmox supports tags, so class Proxmox supports tags, too. It is possible to show and change tags in config and `e status` prints tags. The new command `e ct volume_move NAMEORID DISK POOL` "moves" the disk of a CT to an other RBD-pool. It only supports RBD, yet. It uses XFS on the new device. The CT must be stopped on the same machine, you are calling the command. The class PVE::Output helps to print status. Supports info, failed and progress (with a spinner). Monitoring tasks used a custom spinner, which is now part of the new PVE::Output. The status of CTs/VMs/Nodes are symbols only. Strings shouldn't be used anymore. |
||
---|---|---|
bin | ||
lib | ||
.gitignore | ||
Gemfile | ||
LICENSE.txt | ||
pve.gemspec | ||
Rakefile | ||
README.adoc |
Proxmox Virtual Environment High Level API for Ruby =================================================== This is a limited, but easier to use library for ruby. It provides additional a command line interface for administration named `pvecli`. The Rest-API will be used for controlling your server. You need to provide a config-file `/etc/pve/pvecli.yml`: auth: username: USERNAME password: PASSWORD realm: pve or something like that connect: verify_tls: no if you do not use known CA-signed X509-Certificates Featurs ======= The library provides an interface to interact with PVE-servers. Provided abstractions for: * Node * LXC (create, delete, modify, use) * Qemu (create, delete, modify, use) * Storages (list, list content) * Appliances (list, download to storage) pvecli ====== This tool should usable like PVE-WebGUI, instead of low-level-tools like `pct` or user-unfriendlier tools like `pvesh`. So `pvecli` provides a global control over your cluster on command line.