headers
Gonéri Le Bouder | 17 May 15:17
Gravatar

Re: [FusionInventoryAgent][NSIS] My last skeleton...

On 17/05/2012 02:28, Work wrote:
>     Hello Gonéri,
>
>     As I promise you, I send a bit latter my last skeleton for the new FusionInventoy Agent Installer for
Microsoft Windows.
>
>     I need to add a new page for others protocol options like 'backend-collect-timeout', 'no-p2p',
'delaytime' or 'wait' and new options to be able to schedule the Windows Task with more precision.
>
>     Well, I hope you like it. It has a lot of new ideas.
This is awesome! I love it!

I attached a picture with my comments. Do you have a web space somewhere
to upload the .exe? I can create one for you if you want. This well,
it will be much
more simpler to get feedback from people, for example by sending the URL on
the mailing list or IRC.

IMO, wait parameter is useless and we will drop it probably after the
3.0 release.
“Run after installation” already means wait=10, so I don't see the
point to add a
feature only for this key.
It's more or less the same for 'backend-collect-timeout', if someone
really need it
(99.99% or the users won't), he can still create an additional .reg
file to set the
property.

Regarding the spanish/french translation, will this work with Asian or cyrillic
(Continue reading)

Permalink | Reply | 0 comments |
headers
David DURIEUX | 22 Apr 23:04
Favicon
Gravatar

beta 3 of plugin FusionInventory for GLPI 0.83+1.0

Hello all,

I have release the third BETA of plugins fusioninventory for GLPI 0.83.x

This version have all bugs fixed from 0.80+1.2 version released few
days ago. It pass too unit tests for snmp inventory, network discovery
and computers inventory. But tests not (yet?) test all :p

See tickets: http://forge.fusioninventory.org/versions/67
Some of these tickets will be moved to version 0.84, others are in
progress (like ticket for simplify tasks) and others will be coded in
the next week to set in couple of days the first Release Candidate
version. 

Please use agent 2.1.14, because version 2.2.x have some problem with
network discovery and SNMP inventory (or you can but if you have
troubles,you will don't know if come from agent or plugins).

Download here:
http://forge.fusioninventory.org/attachments/download/614/fusioninventory-for-glpi-metapackage_0.83_1.0-BETA3.tar.gz

For bugs report, use our development forge:
http://forge.fusioninventory.org/projects/fusioninventory-for-glpi

Last thing, NOT USE IT IN PRODUCTION!!

best regards,

David DURIEUX
++
(Continue reading)

Permalink | Reply | 0 comments |
headers
Remi Collet | 14 Apr 17:59

Software name and arch

In previous version of the agent, (and in OCS agent)

Software name was  "name.arch"

Starting with version 2.2.0, it's only "name"

I consider this as a regression will make information really difficult
to manage in GLPI in heterogeneous envionment (mixed version / mixed
agent / multi-lib computer)

Currently, with older agent (or ocs agent), I see in my software list
	freetype.i686		2.4.6-4.fc16
	freetype.x86_64		2.4.6-4.fc16
With agent 2.2.0
	freetype		2.4.6-4.fc16

OK : using arch in the name is a poor workaround

A better solution will be
- add arch information in the XML
- add arch information in GLPI DB scheme

Another 2 steps solution could be
- add arch information in the XML
- generate "name.arch" in the server side (glpi plugin)

But until this, please consider reverting to the previous behavior.

Remi.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Remi Collet | 14 Apr 17:29

Fusioninventory-agent + systemd

Hi,

Here is a working systemd configuration.

Envirment File
(/etc/sysconfig/fusioninventory-agent ou équivalent)

# Add tools directory if needed (tw_cli, hpacucli, ipssend, ...)
PATH=/sbin:/bin:/usr/sbin:/usr/bin
# Global options (debug for verbose log, rpc-trust-localhost for yum-plugin)
FUSINVOPT="--debug --rpc-trust-localhost"

Systemd Unit file

[Unit]
Description=FusionInventory agent
After=syslog.target network.target

[Service]
EnvironmentFile=/etc/sysconfig/fusioninventory-agent
ExecStart=/usr/bin/fusioninventory-agent $FUSINVOPT
--logfile=/var/log/fusioninventory-agent/service.log --daemon-no-fork

[Install]
WantedBy=multi-user.target

N.B. server, tag, ... could be configured in agent.log or using
FUSINVOPT (I prefer the later), ex:
FUSINVOPT="--debug --rpc-trust-localhost --tag=FUS
--server=http://localhost/glpi/plugins/fusioninventory/"
(Continue reading)

Permalink | Reply | 5 comments |
headers
Guillaume Rousse | 5 Apr 09:42
Picon

Confusion between network interfaces and network addresses

While reviewing yesterday changes from Goneri, I found there was some 
confusion in our code between two different concepts: network interfaces 
and network addresses. Worse, we are not even consistent among the 
various OS, most notably between Linux and Windows.

Let's consider a machine with two interfaces, one active with two 
attached addresses, and one inactive.

Strategy 1:
In Windows code, as seen in the t/inventory/windows/networks.t expected 
results, a 'networks' entry is strictly a network interface. The example 
scenario would result into the following internal representation:
{
   description => 'foo',
   ipaddress => [ '127.0.0.1', '127.0.0.2' ],
   ipmask    => [ '255.0.0.0', '255.0.0.0' ]
},
{
   description => 'bar',
   status => 'down'
}
Which translates into the following XML result with multiple elements of 
the same name:
<NETWORKS>
   <DESCRIPTION>foo</DESCRIPTION>
   <IPADDRESS>127.0.0.1</IPADDRESS>
   <IPADDRESS>127.0.0.2</IPADDRESS>
   <IPMASK>255.0.0.0</IPMASK>
   <IPMASK>255.0.0.0</IPMASK>
</NETWORKS>
(Continue reading)

Permalink | Reply | 7 comments |
headers
DuyLong | 2 Apr 11:57
Picon

New module for virt-top

Hi,

Do you have a doc in order to develop a module in the agent ? I want the 
base structure for create the .pm and add the infos in the xml file.

Thanks to virt-top, I want extract some infos (Total CPU, RAM 
availables, Historical %CPU on the hypervisor, %CPU and %MEM used by 
each VM...)

A example output of virt-top : 
http://people.redhat.com/~rjones/virt-top/screenshots.html

Can you help me ?
Thank you,
--
Duy Long LE
University of Strasbourg
Permalink | Reply | 2 comments |
headers
Guillaume Rousse | 13 Mar 16:35
Picon

Harmonization between README files and the forge

Hello fellow co-developpers.

I made some efforts to make the README files for the agent and the 4 
tasks compatible with 2.2.0 release a bit more consistent with each 
others, and with their forge project page also. The goal is to achieve a 
similar format first, and a similar vocabulary second.

For the README file, the structure is:
- description
- dependencies
- installation (to do for the tasks)
- other informations
- authors
- license

For the last two points, I removed any external AUTHORS file, and 
included the content directly in the README file. I also removed any 
copy of the license text, to explicitely refers to extenal LICENSE file.

For the forge page, the structure is
- descriotion
- download
- link to more documentation

Some vocabulary points:

Each task description begins with 'This task allows the agent to 
perform'. The word 'module' or 'plugin' are banned, in favor of 'task'.

The term 'prebuild' is also banned, in favor of "binary distribution",
(Continue reading)

Permalink | Reply | 0 comments |
headers
Guillaume Rousse | 8 Mar 13:32
Picon

dmidecode usage

Hello Anton.

I just saw you have a list of software using dmidecode on this page:
http://www.nongnu.org/dmidecode/

You may be interested to know than fusionventory agent is heavily 
relying on dmidecode to extract hardware informations from a wide scope 
of platforms, including windows:
http://forge.fusioninventory.org/projects/fusioninventory-agent
--

-- 
BOFH excuse #370:

Virus due to computers having unsafe sex.
Permalink | Reply | 1 comment |
headers
Remi Collet | 27 Feb 17:58

Inventory and auto-transfer

Hi,

Post again, in English

Current working mode on inventory

- link rules (search in all GLPI)
- entity rules
- computer transfer if needed
- inventory

I think, this auto-transfer feature could be useful in some
configurations, but must be optional in others (when 1 entity is 1
budget, it is a "financial" operation which must be done explicitly, so
manually).

Proposal :

If "Transfer template" is configured, keep the current behaviour.

If "Transfer template" is NOT configured

- entity rules
- link rules (only search in found entity)
- inventory

This behaviour will be closer to the current OCS/GLPI sync one, where
auto-transfer is a (recent) optional feature.

Another point would be to avoid to play the rules on each inventory,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Remi Collet | 26 Feb 13:26

Inventaire et transfert automatique

Salut,

Je vous remonte une discussion qu'on vient d'avoir sur IRC

Fonctionnement actuel de fusion sur la réception d'un inventaire

- règles de liaisons (donc recherche dans tout GLPI)
- règles d'entité
- transfert si besoin
- inventaire

Proposition

Si le "modèle de transfert" est configuré, conserver le même fonctionnement

Si le "modèle de transfert" n'est pas configuré

- règles d'entité
- règles de liaisons (limité à l'entité trouvée)
- inventaire

(d'ailleurs, actuellement, il est possible de ne pas choisir de
"modèle", je sais pas ce que ça peut donner)

On retrouve un fonctionnement plus proche de celui d'OCS et surtout on
évite des transferts particulièrement couteux (et surtout, pas forcément
super-fiable)

A discuter donc.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Fabrice Flore-Thebault | 20 Feb 14:32
Gravatar

Fwd: LOADays 2012

Loadays asking for a presentation about FusionInventory ...

-------- Original Message --------
Subject: 	LOADays 2012
Date: 	Mon, 20 Feb 2012 12:47:30 +0100
From: 	Toshaan Bharvani <load@...>
To: 	themroc@...

Fabrice,

Je n'ai pas vu une présentation de vous.
C'est peut-être interessant de présenter quelque chose de Rudder,
CFEngine, GPLi, Fusion Inventory ou du documentation des systèmes.

Voici les instructions :
>
> Steps to submit your talk :
>
> *CFP URL:* http://cfp.loadays.org/submission/LOAD2012/
>
>   * Create an account, if you do no have one
>   * Check your email and click on the link to activate your account
>   * submit a talk by clicking on the “Create Event” button
>
> *Remarks relating to submissions in the CFP system :*
>
>   * Please post your biography in your user description
>   * Please remember to post an abstract, a short summary of your
>     presentation for people to directly understand what the
>     presentation is about and a full description of your presentation.
(Continue reading)

Permalink | Reply | 1 comment |

Gmane