r1406 + imported all major feature requests

diff --git a/TODO b/TODO
index 332cff42c08fcde2d917c278cfbf9bdefbe2e13e..6e42ceafd9d0868394d31c553838dc877f5de6a5 100644 (file)
--- a/TODO
+++ b/TODO
@@ -135,12 +135,12 @@ Implement a special edition of object viewing page, which would:
 The only and main purpose of this page would be to assist colocation service customers in accessing their hardware on-site and performing maintenance.
 ----
 ====Major features missing
-* [AD] rack (picture) attachments
+* [AD] [trac#56] rack (picture) attachments
        Implement "attachments" tab for racks and objects, which would allow attaching random files
        and generate thumbnails for those of them, which seem to be picture files (like it is done
        in JIRA).
 
-* Asset management
+* [trac#57] Asset management
        This is a long-awaited silver bullet, which would ease documenting the hardware with no
        rackspace allocated. The solution would be to introduce "rooms" of an abstract capacity
        and taxonomy, capable of containing the objects. An object then could be either rack-mounted
@@ -149,14 +149,14 @@ The only and main purpose of this page would be to assist colocation service cus
        accept objects, which are considered deleted. Such objects would be excluded from all
        views, lists, searches and reports, but still available directly from the attic.
 
-* "Live CDP" tab
+* [trac#58] "Live CDP" tab
        Although simple to explain, not yet known how to implement feature. Having the port list
        with remote switches configured, we could paste "sh cdp ne"/"sh fdp ne" output into a text
        area, submit and expect some AI to point out all inconsistencies and probably adjust the
        data in DB accoring to the field data. The only implementation requirement clear so far
        is having some naming on procedural conventions across the organization.
 
-* Unified IP address tree
+* [trac#59] Unified IP address tree
        This feature would allow representing the whole IP address space as a tree. The idea
        can be best illustrated by WordPress categories. First of all, we let IP addresses to
        exist without a containing subnet. To be precise, we introduce subnet 0.0.0.0/0, which
@@ -167,14 +167,14 @@ The only and main purpose of this page would be to assist colocation service cus
        each particular address. This will allow us to have branches, which will reflect not
        only connected prefixes or routed networks, but any arbitrary super- or subnets.
 
-* Object hierarchy
+* [trac#60] Object hierarchy
        Building a tree of IP subnets is only a metter of calculation. Building a tree of objects
        requires only just a little more. Provide the root group, then allow a user to inherit
        more groups from the root or any other group, and we have a tree similar to the one of
        IP addresses. The current "objects" page has a list of object group types to the left,
        it is nothing else, as what the object root tree should look initially.
 
-* Auto-constructor
+* [trac#61] Auto-constructor
        This feature consists of some encoded intelligence combined with field data. For example,
        if we render a brand new network switch, router or KVM switch, of which is known its
        hardware model only, a trigger could fire, which would offer to create all that ports,
@@ -184,20 +184,20 @@ The only and main purpose of this page would be to assist colocation service cus
        "base MAC address"es. The only estimation I can give at the moment is that this code
        will require a long and gradual implementation.
 
-* User groups
+* [trac#55] User groups
        Granting the same permission to half of new users is sometimes a boring procedure.
 
-* More means of user authentication and authorization
+* [trac#62] More means of user authentication and authorization
        LDAP/AD, of course.
 
-* Live PTR tab
+* [trac#63] Live PTR tab
        Add a tab to the IP subnet page, which would list the back-resolved PTR DNS records for each
        IP address. The user then should be able to mark, which records he wants to be updated from
        the live data. To ease DNS maintenance, the IP addresses, which have both comment field set
        and PTR record resolved, should be highlighted in the case strings differ. Should we allow
        prefixes and suffixes for comment auto-assignment?
 
-* Pluggable ports support
+* [trac#64] Pluggable ports support
        To provide appropriate support for GBIC/SFP/X2/SmartSerial ports, the following logic should
        be implemented:
        1. Introduce generalized (empty) and all possible media modules as port types: {SFP-1000,
@@ -213,7 +213,7 @@ The only and main purpose of this page would be to assist colocation service cus
        or cables available connector type (LC, SC, FC) would still be encoded in the port type like
        it is done now.
 
-* Data export and import
+* [trac#54] Data export and import
        For backup purposes it is recommended to distinguish stock data from the data entered
        by user and generate an SQL dump with the latter. And if we could correctly narrow down
        the process to some rack(s), the resulting dump would be a good supplement for the hardware