>Hello, all. >> The problem with this solution is that it disrupts the current workflow. I >> would have to go into a different part of the UI to see what is unmounted. >> It makes more sense from a user standpoint to have the unmounted group in >> the main object pane. I have been toying with the idea of creating an >> "InStorage" tag for things that are unmounted and wont be mounted anytime >> soon. The "unmounted" group I am talking about would be for newly created >> objects. >I've got a concept, which would allow filtering all kinds of data, but >it needs a bit of time and code put in. Let me get back to this >talk later with a working draft. >> Another possible bug I found is that if I put in a search term that should >> report equipment with that as a substring, it should also report rack names >> that also match. It currently does not show a rack with the search string in >> the results. >This has been added into the current list of search function >inconsistencies. >> Is there a way to automatically block off the network and broadcast IPs on a >> subnet? >The "connected" checkbox on the "create prefix" form does exactly so. > A feature I would like to see is automatic IP assignment. When an ip aware > object is created, a dropdown with the list of subnets should appear as well > as a checkbox to select auto-ip. The object would then be given the next > available IP in the subnet. Perhaps I am missing something, but there seems > to be some disjointedness between object creation and ip allocation. I can > assign an IP address to an object from the object settings, however that > doesn't include the object name properly in the IP allocation. I am looking > at RackTables as a tool to also manage our DNS records. The IP subnet > allocation does not have a name set if I setup the ip address and name from > the object settings. I have to go into the IPv4 subnet and set the name. I am > not sure what direction you want to take RackTables in regards to DNS. It > would be nice to also have support for domain names in the IPv4 system. Right > now you have to manually type the FQDN if you want to reflect a domain name. > A default do > main name as well as a user/group restrictions on what domain names that > they can use would be nice. The "allocate next unused" feature is a good point. "...doesn't include the object name properly in the IP allocation" --- could you give an example? This seems to be working in my setup. ********* If I create an object and assign it an IP the name will not appear in the name field of the IPv4 allocation screen for the subnet it was created in. That field is not populated. I have to go in and manually populate the name field. ********* Making RackTables and direct/reverse DNS zones play together would be cool, I know, and requires no rocket science. I've got necessary experience in both areas, but the facts are: I don't currently do DNS administration; and one can't write a program well, which he doesn't use. Perhaps someone else is in a better position for this? The domains you are describing (administrative scopes) quite probably can be done with tags. I hope it helps. ******** RackTables does not necessarily need to work with zone files for DNS. We have written scripts here that will pull data from an SQL database and create zone files. Currently this is being used with RackMonkey. I am just throwing this idea out there so that possible changes can be made that would help with data consistency. Another feature request would be that somehow selected optional attributes can be made mandatory. I will have multiple users working with the data and need the users to always fill in what are now optional attributes. ********