From: Dr. N. - E. R. <eu...@dr...> - 2006-10-27 16:07:18
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content=3D"text/html;charset=3DISO-8859-15" http-equiv=3D"Content-Type"> </head> <body bgcolor=3D"#ffffff" text=3D"#000000"> Ming Zhang schrieb: <blockquote cite=3D"mid1161963910.2562.23.camel@localhost.localdomain" type=3D"cite"> <blockquote type=3D"cite"> <pre wrap=3D"">Hi all, Been offline (Holiday in Austria). </pre> </blockquote> <pre wrap=3D""><!----> do brainstorming? ;) </pre> </blockquote> <br> No, visting my parents-in-law ;)<br> <br> I meant: I am from Austria, and yesterday was a holiday (national holiday)<br> <br> <blockquote cite=3D"mid1161963910.2562.23.camel@localhost.localdomain" type=3D"cite"> <blockquote type=3D"cite"> <pre wrap=3D"">My 2 cents: 1.) IMHO making ietadm work flowlessly is the right way to go -=20 independent of web interface. 2.) Openfiler: IMHO there are 2 schenarios - Want a 'turn-key' storage solution with IET _and others_: Use Openfile= r - Want to manage your own server (kernel etc) and use IET _exklusivly_,=20 but need a web-interface for IET: Don't use Openfiler </pre> </blockquote> <pre wrap=3D""><!----> why? </pre> </blockquote> <br> Openfiler is not only a web-interface, it is a (mini-distribution). As such IMHO ist is perfect for some "all-in-one" storage device on commodity hardware. But I suspect, that high-power users (we have some dual opteron guys here) will want to use a supported distribution like RH or Novell or so. Additionally, Samba etc. are not needed/wanted on a dedicated iscsi storage server.<br> <br> <blockquote cite=3D"mid1161963910.2562.23.camel@localhost.localdomain" type=3D"cite"> <pre wrap=3D"">open-iscsi go away from db and i think we should do that= as well. </pre> </blockquote> Sorry, I didn't make myself clear:<br> <br> - primary configuration source should be ietd.conf (ofcourse)<br> - those, who want to use a web interface can empty out ietd.conf and use web-interface, which maintains a seperate instance of configuration data and can apply it to IET via ietadm.<br> - those, who want to use web-interface and automatically apply current settings on startup can hook into web interface from command line to do just that<br> <br> <blockquote cite=3D"mid1161963910.2562.23.camel@localhost.localdomain" type=3D"cite"> <pre wrap=3D"">run iet in a CF/usb linux distribution will be nice and draw more eyeballs. </pre> </blockquote> Ofcourse - this is case #1 from above, where Openfiler is perfect. My humble objections against a homebrew distro concerning support/stability (on the kernel/distribution layer, not IET) still stand.<br> <br> <blockquote cite=3D"mid1161963910.2562.23.camel@localhost.localdomain" type=3D"cite"> <pre wrap=3D"">do you think an option to export current configuration a= s a ietd.conf format will be useful? </pre> </blockquote> Perfect idea. This bridges the gap.<br> <br> The reason why I plan to maintain a seperate set of configuration data is being defensive: I don't want to overwrite ietd.conf as a routine! But doing so on demand (via an export) seems perfect to me.<br> <br> <pre class=3D"moz-signature" cols=3D"72">--=20 Gru=DF Eugen :-) Eugen Rieck (-: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:eu...@dr...">eu= ge...@dr...</a> Programmer: Biological device, designed to convert coffee into code </pre> </body> </html> |