On 07/15/2009 05:24 PM, Rodrique Heron wrote:
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Michael DeHaan
Sent: Wednesday, July 15, 2009 5:08 PM
To: cobbler mailing list
Subject: Re: If you use CobblerWeb, what's your workflow with other webapps?
On 07/15/2009 05:01 PM, Rodrique Heron wrote:
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Michael DeHaan
Sent: Wednesday, July 15, 2009 4:44 PM
To: all things Cobbler
Subject: If you use CobblerWeb, what's your workflow with other webapps?
For instance, do you ever want to tweak a system in Cobbler then look at
it in Nagios/Cacti/Your-Favorite App?
I'm wondering if it makes sense to (where the other applications permit
it), putting up some simple jump links on the "list" page that will take
you to the pages
for those specific systems, to make it easier to open those other
programs in new tabs/etc and show the systems.
That all being said, I'm not aware of what apps this makes sense for,
but in the sense of Cobbler as "one ring to bind them",
lightweight-CMDB-but-not-quite sort of thing?
(Note: this does not imply hard-dependencies of any kind, and would
probably need minimal configuration in settings)
Michael-
I'd love to see links to GLPI, OCSInventory and Zenoss. Its probable easy to
tie Zenoss and Cobbler together, whereby creating a system adds it to Zenoss.
I'm adding systems to OCSInventory as part of post kickstart, and when I have
the time will figured out a scripted way for Zenoss. Since I use the system
profile name as the hostname of the system. I neat function could be to search
Zenoss and OCSinventory with the system profile name and auto generate a link.
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
Yep.
We should most definitely ship snippets of these (contributions welcome!
send them along and we'll take them!) like we've done for Func
integration. (Puppet and cfengine also seem logical, don't they?)
To save me the trouble (though I'm long overdue for looking at the
latest in many of these), if those systems put out nice links such as
"/system/hostname" or "search?hostname=foo" can you tell me what these
URLs are for ones you might use?
(If they key off something /other/ than the hostname and or system name,
things may be harder to do.)
The search stuff can probably be done, but I'd rather avoid it at first
if possible.
They do provide decent URL's, but to automate generating links, it probable
best to go against the database.
Zenoss urls can be easy if you keep your servers under one class. A simple
definition for class is just a way to group similar devices. The url for Zenoss
looks like this.
http://localhost:8080/zport/dmd/Devices/Server/Windows/SQL/Dell/devices/cobbler.internal.net
Very doable.
So this device is in class, Server>Windows>SQL>Dell.
GLPI and OCSinventory both assign ID's to systems, OCS looks like this:
http://localhost/ocsreports/machine.php?sessid=36703c462b748ab8235201c3bd7caf8d&systemid=13
These are likely out of scope as we probably don't want to teach cobbler
to login to them remotely -- perhaps an RFE for nice URLs if they do not
support "search" URLs that may work for us?
(The sessionid is probably optional. I hope! In general you should never
put session ID's in URLs anyway as that does not work well with
bookmarks. We keep our token/session information in POST data for this
reason).
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
