Hi, Here is what I would like the installer to do:
- Ask no questions relating to EPEL. - Attempt to install the required RPMs or packages and also attempt to install EPEL on RedHat/CentOS first. - If those installs fail, then exit with a message, indicating what needs to be installed (on all nodes). This won't require any extra effort in the normal case, and it will enable a user in special situations (e.g. no internet access and no EPEL repo) to work around the issue. Thanks, Hans On Tue, Oct 20, 2015 at 10:49 AM, Amanda Moran <[email protected]> wrote: > Hi there All- > > Currently in the installer we prompt for them EPEL rpm location so that it > can be installed by the installer. **We need the EPEL repository for Centos > OS installs to get required packages installed for Trafodion, pdsh etc. > > I would like to propose that we remove that question. I feel that is very > confusing. I think it would be better if the installer just stated before > the install began (and was documented in our documentation) which packages > are required and ask the user to install those on their system in advance. > The user could use whatever process works for them. This would simply the > installer since it would no longer need to download the EPEL repo (if it > wasn't already installed or the RPM was not provided) and Trafodion install > would no longer need internet access to install. > > The installer would continue to check that packages are installed, and it > would attempt to install them. > > Thoughts? Any idea how other projects get their required RPM packages > installed? > > Thanks all! > > -- > Thanks, > > Amanda Moran >
