Supporting session alias's
Especially for sub-connections it would be good to have the ability to just reference an existing connection rather than re-creating it. Of course some per-connection customization might be needed for the command line etc.
SSH scripting & internal scripting
It would be really nice to be able to right click on an object (or whatever) and be able to run a set of ssh scripts on remote systems. Or possiby add a sub-connection that will run a script. these scripts should allow for asking for input as well as pulling variables from the record.
An example use case would be to be able to change the vlan of the interface that a device is plugged into, or enable/disable the port of a device, update the description, etc... Another example could be to request the configuration or metrics of a switch port and display like the "ping" utility does.
Also, the ability to setup internal scripts that configure, add, or update sessions based on other session variables. So, for example, if I am setting up a new server, I would like to be able to use a template and have ask what sub connections are needed, then set them up based on feedback. This could also be handled via having custom variables and having the sub connections support using those variables.
so, for example, most of the servers I setup will have sub connections like:
- Web interface for server
- Web interface for the application it runs
- ssh interface to server
- serial interface to server
- OOB / management board interface to server
- KVM interface to server
- connection to PDU
- web interface to monitoring package
- Web interface to switch the server is plugged into
If I can add to the base session fields like "switch port", "KVM Port", "Serial Port", etc, the the sub connections would pull that info direct from the main record.
Custom Data Fields
The ability to add custom fields in to the record. Such as support agreement date or support contact information. I know there are the generic fields, however they do not always support exactly what I would like to track.
A few features for consideration:
First, thanks for the great product!
I have a few feature thoughts; These kind of wander all over, and in some cases overlap with different methods of achieving a similar result, but I wanted to throw them out for your consideration. I am sure that there is no way of getting most of these (or even any depending on the time frame) in any near term release unless you are already working on them but I wanted to at least get them on the table while I was thinking about them.
Again, thanks, and the below list is in no way a slight on your product!
1: Command Line Templates: The ability to configure a template based on a command line, sort of an on demand new device type. So, for example I could create a template called ReallyCoolTool, select parameters that I cared about based on a set of options, and set the command line to run: "ReallyCoolTool.exe $HOST$ UID=$USERNAME$ PW=$PASSWORD$", then when creating a new record, I could simply fill in the host, username, and password, and it would run the reallycooltool.
2: XML based device templates: This could take the place of the above suggestion, allow for defining a new device type based on an xml file (Something like;
<Tool>
<Name>Really Cool Tool</Name>
<MainPageParameters>
<Tab1>
<TabName>General</General>
<Parameters>
Hostname
Password
UserID
</Parameters>
</Tab>
</MainPageParameters>
<Command>
<String>"ReallyCoolTool.exe $HOST$ $UID$ $PW$"</String>
<Dir>"\Program Files\RCT\"</Dir>
</Command>
</Tool>
(Of course, it would have to have a lot more details than the above, but generally the idea would be to allow anyone to define a new template... you could then even allow for uploading and sharing of templates!)
3: Drag and Drop: Allow me to drag and drop one session ontop of another to create a sub-connection
4: Editing sub connections: allow for right clicking and editing/creating/deleting sub-connections without editing the main connection.
5: build in simple scripting... I know you allow for vb script launching, but allow for a similar but more basic version something like:
"Before connection: ( ) None; ( ) Script; ( ) Command Line; ( ) The following: [ ] Ping, [ ] Wake on lan, [ ] VPN: [Drop down select vpn], [ ] Other session [Drop down select other session]"
-- (parens are radio buttons, sq brackets are check boxes) This would also combine several existing elements of your UI into a single page and (IMHO) simplify it a bit.
6: Grouping: Allow for launching multiple sessions from one session (though the above would handle this as well). For example anytime I am working on a specific device, I always end up with several other sesisons open, it would be nice to allow for this automatically. (or how about something like "auto launch sub-sesssions)?)
7: Filter / Group / Display in a table additional data: such as the info on the details or info page, so I might want to filter based on all windows machines, or all switches... or find something based on a note in the description entry.
8: Allow for configurable additional info: So, I know there is the basic 5 custom fields, but how about in the payed version allowing for building more fields and setting basic field types: (rack number, console port number, power switch number), a REALLY NICE ONE would be: related session: so I could create, for example, two new related sessions on my dell servers, called "Power Management" and "Server Administrator", then when I create a dell server session, I point the "power management" field to the APC and the "Server Administrator" to the Dell server mgr software... I could do this today using sub connections, but would have to recreate them each time.
9: Sub Connections in templates: Allow creating a template that also includes sub-connections... most of the time, my devices have multiple ways of getting into them, and often those ways are pretty consistent (web main use, ssh secondary, serial console server backup) so I could create a template that contained these settings.
9a: Allow for more complex use of the variables to allow for more "hands off" control over the sub connections and events: for example, if my serial connections are always using ip address 1.2.3.4 and some custom port, how about allowing me to use a variable like: SSH Hostname: 1.2.3.4 $PARENT.CUSTOM1$, then all I have to do is to put the port number in the parent's custom 1 field and never touch the sub connection.
10: Configurable VPN connections: not complex ones, but at least allowing for creating something like a url or command line option to launch my own vpn client. it obviously won't work for everyone, but it would help.
11: Allow for custom session and main tools.
12: Allow display of sessions from multiple data sources in a single tree... so when I create a session, I define which of the currently configured data sources I want that session stored in. but they are all shown on the screen at once. (OK, I assume this would be pretty hard, but hey, it can't hurt to ask!)
Dan Strohl