On Thu, 2003-01-23 at 15:09, Jason B. wrote: > At 02:59 PM 1/23/2003 -0500, Michael Chase-Salerno wrote: > >On Thu, 2003-01-23 at 14:56, Jason B. wrote: > > > I really don't like the current file selection windows we use (e.g. in > > Step > > > 4, choosing rpmlist, in Step 6, choosing MAC file). They don't maintain > > > their state very well, and don't update the window very well. For > > example, > > > if I go into the selection window and Cancel out of it, the previous > > > information is erased. Also, I never noticed the small File entry box on > > > the bottom of the window until I looked around for something on the MAC > > > file saving window. This should be integrated into the top line (so that > > > it includes the whole path), or should be accentuated somehow. > > > >All fine comments, but I don't think we should spend much time tweaking > >the current GUI since there are new interfaces coming down the line > >shortly. > I bring this up because we will still be using those dialogues, similar to > how they are used now. i.e. the window is still going to be an issue. > > > > Also, when saving MACs, shouldn't we also be saving the MACs that are > > > assigned? If anything, shouldn't we ONLY be saving the assigned MACs? I > > > don't want to save the number of MACs that appear when collecting on a > > > public network, just the ones that I have assigned. In addition, we > > should > > > probably check the imported MACs against the list of collected MACs (and > > > server MACs) so that you don't assign duplicates. It currently allows > > > importing of MACs that already have been assigned. > > > >The assigned MACs are already saved in the database. I believe the main > >purpose of this tool is to take in a list of MACs that were collected > >via some outboard means, like polling from the switches or other such > >things. It isn't intended to back up the MACs that have already been > >dealt with. > What if I want a file that has all the MACs for the machines that I test > with that take 5 minutes to boot? I thought that was one purpose for this > function. What other MACs would you save to a file?
As I said before, I believe the purpose of this was to take a file from some collection method and be able to import it into the process, not as a backup utility. You could save the entire client defs like this: mksimachine --List > filename To get just the MACs would require some scripty-fu stuff, but it would be simple. Personally, I just create a script that has the required mksimachine --Update commands to put the MACs in the database eg mksimachine --Update --name node1 --MAC aaaaaaaaaaaa mksimachine --Update --name node2 --MAC aaaaaaaaaaab Not an integrated solution, but useful for test/development. Of course, you could just backup the whole /var/lib/sis directory and get the whole database, but there's no way to restore it and get all the right API triggers run. Mike > Jason > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Oscar-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/oscar-devel > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
