View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
534 | RackTables | default | public | 2012-02-29 21:42 | 2012-09-22 12:03 |
Reporter | infrastation | Assigned To | infrastation | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Target Version | 0.20.1 | Fixed in Version | 0.20.1 | ||
Summary | 534: multiple Cacti servers | ||||
Description | Below is a draft spec of the feature, may be, you will consider implementing it in one of the next releases, or someone else will volunteer to do. I feel better without having to remember about this matter. 1. A new CactiServer table should be created with "id", "base_url", "username" and "password" columns. The first record (id=1) should be inserted based on the CACTI_URL, CACTI_USERNAME and CACTI_USERPASS options, which should be deleted. 2. The CactiGraph SQL table needs to be extended with "server_id" column (all records get id=1 at the time of conversion), which should be locked on CactiServer.id by means of FK. 3. renderObjectCactiGraphs(), getCactiGraphsForObject() and $opspec_list need to be updated respectively. 4. A new "Cacti servers" item should be available on the "Configuration" list. Making it work shouldn't be hard with $opspec_list. I've got the data to test this functionality against. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2012-02-29 21:42 | infrastation | New Issue | |
2012-02-29 21:42 | infrastation | Status | new => assigned |
2012-02-29 21:42 | infrastation | Assigned To | => user105 |
2012-09-21 22:10 | infrastation | Note Added: 0000806 | |
2012-09-21 22:10 | infrastation | Assigned To | user105 => infrastation |
2012-09-21 22:10 | infrastation | Target Version | => 0.20.1 |
2012-09-22 12:03 | infrastation | Status | assigned => closed |
2012-09-22 12:03 | infrastation | Resolution | open => fixed |
2012-09-22 12:03 | infrastation | Fixed in Version | => 0.20.1 |