-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
Geoffroy VALLEE a écrit : > Hi all, > > Working on the new GUI, which is based on the CLI, i realized that > the code for bootstrapping (i.e., OSCAR initialization) is not very > clean and is actually pretty incomplete for the CLI. > > For instance, systemimager-client and systeminstaller-oscar are > installed during wizard-prep execution which is called by > oscar_wizard. It means that if you try to execute the CLI directly, > you will most certainly face issues because of not-installed > packages (there is also somehow kind of weird because we try to > refer to systemimager-client in oscar_wizard before to actually > install it). > > Therefore i would like to "clean up" the bootstrap and at the end > have something that can be used with the current CLI, the current > GUI and the new GUI. Note that if i can do that, i will also > include the configuration tool i was working on. For that my idea > is to do the following: install_cluster->bootstrap->system sanity > check and then call oscar_wizard or main_cli. Of course i plan to > reuse the prereq mechanism and as many stuff we already have. > > Any suggestions/remarks? I will start to work on that in few days > so if you have any remarks, please speak-up ASAP. I don't know deeply the current bootstrap mechanism, so I may say stupid things, but here is some remarks about what I imagine it should be. There might be a clear separation between the several parts of bootstrapping: 1 - third part software checking and, eventually, installation. 2 - OSCAR core software installation. Installation paths must be editable. 3 - repositories configuration: 3.1 - local repositories installation (optional) 3.2 - yum/apt configuration 4 - sanity check: ODA integrity, DHCP config checkup, etc. Step 1 is only done once. It must be switched off when installing from packages. Installation, FMHO, must not be done automatically, only a summary of missing software given to the user. Step 2 may install OSCAR sofware in standard paths: /usr or /usr/local and not /opt, or at least this must be setup by the user. This is important for packaging. Step 3 can be done once the UI is launched, because user can be asked for which repositories he wants and where to install it. Step 4 is the only step run at every launch of OSCAR UI. IMO, use of autotools should ease a lot of things. Everybody knows configure script with its numerous options for installation paths. Then Makefile have standard targets: 'make install' to install and 'make dist' to get tarball. Maybe it is not the best tool but its use is well-known by everyone. I'd like to help on this task but I'm already plenty of other work :-( Regards, Jean > > Regards, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHZukJ8P+pSEjr0u4RAjgwAJ44cWR9A1T9m3K2b8mNSqKHxemioACfSwIG maKnf7S9QOTNnlrHppFe30Q= =IjUX -----END PGP SIGNATURE----- ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
