FusionInventory Agent

Sure, I don't use it myself. Could you provide a patch for that or give us what commands need to be run to get the required informations?

Could you give me output of libvirt's virsh?

I don't understand. Do you use libvirt to controle your lxc container?

No, we're using lxc-tools. Just wanna to look at libvirt's output and compare it :)

oh. I don't use lxc at all myself :)

Ok, do we need some kind of unique ID for a container, or just the name & the status would be okay?

Hi Egor,

You can get the Inventory format documentation with:

perldoc FusionInventory::Agent::Task::Inventory::Inventory

or directly by browsing:
https://metacpan.org/module/FusionInventory::Agent::Task::Inventory::Inventory

UUID is important in general because, it's the sole information that can be use to create the relation between the VM and the Hypervisor.
Sometime, VMID or the MAC address is enough. I don't know for lxc.

=head2 VIRTUALMACHINES
=item MEMORY Memory size, in MB.
=item NAME The name of the virtual machine.
=item UUID
=item STATUS: the VM status: running, idle, paused, shutdown, crashed, dying, off
=item SUBSYSTEM The virtualisation software. E.g: VmWare ESX
=item VMTYPE The name of the virtualisation system family. The same type found is HARDWARE/VMSYSTEM
=item VCPU Number of CPU affected to the virtual machine
=item VMID The ID of virtual machine in the virtual managment system.
=item MAC The list of the MAC addresses of the virtual machine. The delimiter is '/'. e.g: 00:23:18:91:db:8d/00:23:57:31:sb:8e
=item COMMENT a comment
=item OWNER

Hi,

LXC doesn't have it's own UUID, but it has independent MAC address. Not sure about VMID and where it can be taken of :)

It seems we need your help.

We've done filling these fields:

    <VIRTUALMACHINES>
      <MAC>0A:AB:BC:CD:DE:EF</MAC>
      <MEMORY>1024000</MEMORY>
      <NAME>test1</NAME>
      <STATUS>RUNNING</STATUS>
      <VCPU>7</VCPU>
      <VMID>13018</VMID>
      <VMTYPE>LXC</VMTYPE>
    </VIRTUALMACHINES>

Hi Egor,

This look great.

Is it possible for you to use getFileHandle() instead of open. It would be interesting to create specific function for "/usr/bin/lxc-ls -1" and "/usr/bin/lxc-info -n $vm" parsing. This way we will be able to do some unit test scripts like we do for the rest of the Inventory modules (see in t/inventory/virtualization/*).

If you don't want to do that, just attach, some "lxc-ls -1" and "lxc-info -n $vm" outputs. I will do that myself.

Just a minor point, we use 4 spaces instead of tab to indent the code.

Best regards and thank you for your efforts! :)

Here's the new version :)

And the output for the commands:

# lxc-ls -1
name1
name2
name3
name1
name2
name3

# lxc-info -n name1
state:   RUNNING
pid:     13018

# cat /var/lib/lxc/mysql-test1/config 
lxc.utsname = name1
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.ipv4 = 0.0.0.0
lxc.network.hwaddr = 01:23:45:67:89:0A

lxc.cgroup.memory.limit_in_bytes = 2048000
lxc.cgroup.cpuset.cpus = 0,3-5

lxc.tty = 4
lxc.pts = 1024
lxc.rootfs = /var/lib/lxc/name1/rootfs
lxc.mount  = /var/lib/lxc/name1/fstab
lxc.arch = 

lxc.cgroup.devices.deny = a
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm

Pushed in 2.2.x branch. Again Egor, a big thank you!

Great :)