tagging instances

[shantanu]

Hi,
This is a two part question:

Would it be possible to assign custom tags to qemu vms.
Software from inside the vm could then "query" those tags to get other metadata about the vms.

Example:
I will tag by server machines with the tag "myserver"

Then my client machine can try to discover such instances to get the server's IP address.
(So I don't have to know the server IP address beforehand)

*** Modelled exactly after AWS EC2 tags.

Regards,
Shantanu

 

[guletz]

I said about the same ideaa about tags(user define) in a old post using consul. And not only at VM level. So you can do/define a task using a tag. Like make a bakup for any VM/CT with tag X. Or make a pve-zsync for any storage with tag Y.

 

[shantanu]

My use case exactly. Consul and Nomad!!!

 

[dcsapak]

could you maybe open a bug (as enhancement) in the bug tracker? thanks https://bugzilla.proxmox.com/

 

[shantanu]

could you maybe open a bug (as enhancement) in the bug tracker? thanks https://bugzilla.proxmox.com/

Done!

https://bugzilla.proxmox.com/show_bug.cgi?id=1934

I hope I have set all the fields correctly and hope this gets picked up in the upcoming releases soon!

 

[jermudgeon]

My use case exactly. Consul and Nomad!!!

shantanu, are you using nomad "natively" with consul, i.e., managing containers? I'd like to get into this (already using consul) but not sure if someone's created a solution already.

 

[shantanu]

@jermudgeon

Yes, I configure Consul and Nomad as SystemD services, as direct binary execution.

After, I install Nomad/Consul inside the VMs, they would in turn be used to manage Docker containers (inside the VM).

 

[jermudgeon]

Thanks for the reply, @shantanu. I may have misworded my question. I was wondering if you were using nomad to directly create containers (LXC) on the cluster, but it sounds like you are using nomad inside prebuilt VMs.

I'm trying to avoid the overhead of having large, not-very-portable VMs; I'd rather use LXC, and this is quite doable with non-orchestrated Proxmox. It's finding an orchestrator for LXC that appears to be difficult.