Le 21/08/2014 14:21, David DURIEUX a écrit :
Le Wed, 20 Aug 2014 14:37:02 +0200
Guillaume Rousse <guillomovi...@gmail.com> a écrit:
Hello.
Hi
I'm trying to adapt GLPI to our local needs, which means basically
being able to attach additional informations to some objects.
The first set of those adaptations are quite specific to our usages,
and unlikely to interest anybody else ('offer type', 'hypervisor
cluster', etc...).
You can see plugin appliance
(https://forge.indepnet.net/projects/appliances). Like it you can
create clusters. For hypervisor, perhaps use virtual machine in
computer form
A 'virtual machine' association in GLPI associate one given virtual host
with one given hypervisor (the one it is currently running on), not with
a set of hypervisors.
I'll have a look a the appliance plugin, tough.
Quick'n'dirty solution: use a multiline comment (or note) field to
store a list of key/values pairs.
Better solution: develop a custom plugin, adding 2/3 new fields to the
current data model. I wonder however how to expose those additional
fields through web services: should we also patch this plugin to make
it able to access them ?
The second set of changes, tough, should be more generic, as we need
to add additional fields to already-existing network objects:
- range
Range? what is this?
The definition of the network itself.
- vlan
You have it on network ports
That's a property of a computer object.
- gateway
You have it on network ports related with IP
Same issue.
For instance, the 'dmz' network, which is defined as 192.168.0.0/24 (its
range) and VLAN 1, exists, independently of any plugged computer. Hence
my interest in having networks are first-class citizens, with their own
properties.
--
Guillaume
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
