FeatureWishlist - Revision history

Michael.tiernan: /* Feature Wishlist */

2019-05-21T16:25:48Z

Feature Wishlist

Michael.tiernan: Added dictionary modification suggestion.

2019-05-21T16:14:33Z

Added dictionary modification suggestion.

Adoom42 at 05:10, 1 December 2013

2013-12-01T05:10:50Z

Adoom42 at 22:10, 28 November 2013

2013-11-28T22:10:42Z

Adoom42 at 19:56, 25 November 2013

2013-11-25T19:56:59Z

Adoom42 at 19:51, 25 November 2013

2013-11-25T19:51:18Z

Adoom42: Undo revision 529 by Adoom42 (talk)

2013-11-25T19:29:32Z

Undo revision 529 by Adoom42 (talk)

Adoom42: port tracing was added to 0.20.6

2013-10-19T22:26:43Z

port tracing was added to 0.20.6

Adoom42: /* Feature Wishlist */

2013-05-16T16:22:12Z

Feature Wishlist

Adoom42 at 15:23, 15 May 2013

2013-05-15T15:23:05Z

@@ Line 34: / Line 34: @@
 **** Template (described below)
 ----
 * Suggest stratification of dictionary entities to permit entries with as much information a possible.
 ** Instead of a dictionary entry for (chosen randomly) ''"SuperMicro 4U 7048R-C1R4+"''. Create dictionary entries for:

@@ Line 22: / Line 22: @@
 ** Install/uninstall, enable/disable capability capability
 ** Install/uninstall features handle DB table creation/destruction
-* Move object Make/Model information out of the Dictionary
+* Dictionary:
-** Additional information needs to be stored.  Using dedicated fields is a cleaner approach than the current one (stapling it on, separated by GPASS or other % wrappers)
+** Move object Make/Model information out of the Dictionary
-** Suggested fields:
+** Additional information needs to be stored. Using dedicated fields is a cleaner approach than the current one (stapling it on, separated by GPASS or other % wrappers)
-*** Make
+*** Suggested fields:
-*** Model
+**** Make
-*** Category (replace chapter_id, sample types are server, network switch, etc.)
+**** Model
-*** Type (rack-mountable object, module, component)
+**** Category (replace chapter_id, sample types are server, network switch, etc.)
-*** Height, depth (only applies to rack-mountable objects)
+**** Type (rack-mountable object, module, component)
-*** Rows, Columns, Orientation (only applies to chassis objects)
+**** Height, depth (only applies to rack-mountable objects)
-*** Template (described below)
+**** Rows, Columns, Orientation (only applies to chassis objects)
 * Object templates
 ** The current SNMP discovery functionality covers two core areas - interfaces and attributes.  If an object is modular, the number and type of interfaces may vary.  Some objects are static, such as non-stackable switches.  Using a template for static devices would ease the process of adding them, especially in cases where there is no SNMP support in RackTables.

@@ Line 16: / Line 16: @@
 ** Invalid data which cannot be constrained using foreign keys
 *** EntityLink table
 *** Config settings such as IPV4OBJ_LISTSRC (an object type may be removed from the list, even if objects of that type exist and have IP addresses assigned)
 * Manage plugins from the web interface
@@ Line 34: / Line 36: @@
 ** There are also cases where SNMP-derived information isn't necessary.  A user may want to add the object in order to document the rackspace allocation and port connections.  Documenting port MAC addresses and other attributes such as serial numbers and SW version provides limited or no value.  Using a pre-defined template, ports could be added during the object creation process.  If desired, SNMP re-discovery could add the missing information at a later date.
 * Refactor user management
-** Today, user accounts cannot be deleted.  Users should never be deleted from the DB because various tables record their actions.  Add a 'deleted' column to the UserAccounts table and provide a way to 'delete' them from the web interface (the 'deleted' column would be set to true').
+** The first time a user logs in via an external authentication source (LDAP), a record should be auto-added to the UserAccount table.
 ** The user_name column must be unique, but only for 'undeleted' accounts.  Use DB triggers (ideal) or PHP code to ensure uniqueness.
 ** Change existing tables to reference UserAccount by user_id instead of user_name (IPv(4|6)Log, MountOperation, ObjectHistory, ObjectLog, PortLog, TagStorage, UserConfig, VLANSwitchTemplate).

← Older revision		Revision as of 22:10, 28 November 2013
Line 33:		Line 33:
	** The current SNMP discovery functionality covers two core areas - interfaces and attributes. If an object is modular, the number and type of interfaces may vary. Some objects are static, such as non-stackable switches. Using a template for static devices would ease the process of adding them, especially in cases where there is no SNMP support in RackTables.		** The current SNMP discovery functionality covers two core areas - interfaces and attributes. If an object is modular, the number and type of interfaces may vary. Some objects are static, such as non-stackable switches. Using a template for static devices would ease the process of adding them, especially in cases where there is no SNMP support in RackTables.
	** There are also cases where SNMP-derived information isn't necessary. A user may want to add the object in order to document the rackspace allocation and port connections. Documenting port MAC addresses and other attributes such as serial numbers and SW version provides limited or no value. Using a pre-defined template, ports could be added during the object creation process. If desired, SNMP re-discovery could add the missing information at a later date.		** There are also cases where SNMP-derived information isn't necessary. A user may want to add the object in order to document the rackspace allocation and port connections. Documenting port MAC addresses and other attributes such as serial numbers and SW version provides limited or no value. Using a pre-defined template, ports could be added during the object creation process. If desired, SNMP re-discovery could add the missing information at a later date.
		+	* Refactor user management
		+	** Today, user accounts cannot be deleted. Users should never be deleted from the DB because various tables record their actions. Add a 'deleted' column to the UserAccounts table and provide a way to 'delete' them from the web interface (the 'deleted' column would be set to true').
		+	** The user_name column must be unique, but only for 'undeleted' accounts. Use DB triggers (ideal) or PHP code to ensure uniqueness.
		+	** Change existing tables to reference UserAccount by user_id instead of user_name (IPv(4\|6)Log, MountOperation, ObjectHistory, ObjectLog, PortLog, TagStorage, UserConfig, VLANSwitchTemplate).

@@ Line 14: / Line 14: @@
 ** Missing system-level rows (Attributes, for example)
 ** Missing foreign keys or triggers
-** Invalid data which cannot be constrained using foreign keys (EntityLink, for example)
+** Invalid data which cannot be constrained using foreign keys
 * Manage plugins from the web interface
 ** Install/uninstall, enable/disable capability capability

← Older revision		Revision as of 19:51, 25 November 2013
Line 18:		Line 18:
	** Install/uninstall, enable/disable capability capability		** Install/uninstall, enable/disable capability capability
	** Install/uninstall features handle DB table creation/destruction		** Install/uninstall features handle DB table creation/destruction
		+	* Move object Make/Model information out of the Dictionary
		+	** Additional information needs to be stored. Using dedicated fields is a cleaner approach than the current one (stapling it on, separated by GPASS or other % wrappers)
		+	** Suggested fields:
		+	*** Make
		+	*** Model
		+	*** Category (replace chapter_id, sample types are server, network switch, etc.)
		+	*** Type (rack-mountable object, module, component)
		+	*** Height, depth (only applies to rack-mountable objects)
		+	*** Rows, Columns, Orientation (only applies to chassis objects)
		+	*** Template (described below)
		+	* Object templates
		+	** The current SNMP discovery functionality covers two core areas - interfaces and attributes. If an object is modular, the number and type of interfaces may vary. Some objects are static, such as non-stackable switches. Using a template for static devices would ease the process of adding them, especially in cases where there is no SNMP support in RackTables.
		+	** There are also cases where SNMP-derived information isn't necessary. A user may want to add the object in order to document the rackspace allocation and port connections. Documenting port MAC addresses and other attributes such as serial numbers and SW version provides limited or no value. Using a pre-defined template, ports could be added during the object creation process. If desired, SNMP re-discovery could add the missing information at a later date.

@@ Line 6: / Line 6: @@
 * Re-discover an object
 ** NICs may be exchanged in a server, or a blade may be added to a switch.  Re-discovering the object would add/change ports and other attributes, but wouldn't delete any existing data unless confirmed by the user.
 * Allow duplicate IPv4 networks, at least for the private space.
 ** When assigning a non-unique IP to an object, ask the user to specify which subnet it is from.

← Older revision		Revision as of 16:22, 16 May 2013
Line 15:		Line 15:
	** Missing foreign keys or triggers		** Missing foreign keys or triggers
	** Invalid data which cannot be constrained using foreign keys (EntityLink, for example)		** Invalid data which cannot be constrained using foreign keys (EntityLink, for example)
		+	* Manage plugins from the web interface
		+	** Install/uninstall, enable/disable capability capability
		+	** Install/uninstall features handle DB table creation/destruction

← Older revision		Revision as of 15:23, 15 May 2013
Line 10:		Line 10:
	* Allow duplicate IPv4 networks, at least for the private space.		* Allow duplicate IPv4 networks, at least for the private space.
	** When assigning a non-unique IP to an object, ask the user to specify which subnet it is from.		** When assigning a non-unique IP to an object, ask the user to specify which subnet it is from.
		+	* Provide an 'Integrity Check' report which lists problems
		+	** Tables using the MyISAM engine which should be using InnoDB
		+	** Missing system-level rows (Attributes, for example)
		+	** Missing foreign keys or triggers
		+	** Invalid data which cannot be constrained using foreign keys (EntityLink, for example)