View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 625 | RackTables | default | public | 2012-10-03 21:01 | 2013-06-23 20:05 |
| Reporter | Assigned To | ||||
| Priority | low | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 0.20.0 | ||||
| Summary | 625: Application Dependencies | ||||
| Description | I think a killer feature for RackTables would be application dependencies. So much of my environment is documented in RackTables, that it seems like a no-brainer to have dependencies mapped within. Here is how I see this happening: - New section on the homepage, "Dependencies" - Can create applications or processes within this new screen - Create links to various racktable objects (typically servers) and describe the dependency of that link (file share or web call etc, this could just be a basic description for the time being). - Main view shows application > dependencies > upstream dependencies (switch server connects to, router maybe, any containers) - Servers now show any applications that are depended upon them - Eventually, add another type of object called "users" that can depend on these applications or processes | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-10-03 21:01 |
|
New Issue | |
| 2013-06-23 20:05 | andriyanov | Note Added: 0001539 | |
| 2013-06-23 20:05 | andriyanov | Status | new => closed |
| 2013-06-23 20:05 | andriyanov | Resolution | open => no change required |
