Maybe we could make a table of what type of user we need to do which parts of the work?
TaskRequires sudoRequires password-less ssh on all nodesMust be trafodion idMust know CDH/Ambari passwordInstall RPMsYY Create trafodion user on all nodesYY Unpack and copy Trafodion files Y Configure CDH/Ambari via REST YRestart Hadoop/HBase YStart Trafodion Y This is probably very incomplete. Thanks, Hans On Tue, Oct 20, 2015 at 12:43 PM, Gunnar Tapper <[email protected]> wrote: > Hi, > > Installers that require sudo/pbrun/etc. access are always iffy for IT > departments that deal with systems that do operational work. It'd be good > if > you can figure out what actions beyond software install require sudo access > to see if they can become optional or prerequisites. As a matter of fact, > RPM downloads etc. may even be handled by a different team that requires > tickets to be opened for anything that requires sudo access; for example, > package download, port opening, user ID creation, changes to firewalls, > etc. > This is especially common for customers that operate their environments per > ITIL principles. > > It would, therefore, be a good idea if a customer can choose to install and > perform all sudo-level activities separately from the Trafodion installer > as > well as have the installer perform the action. > > The same goes for actions such as restarting other Hadoop-level services: > it > may or may not be a set of actions the person installing Trafodion has > access to. Therefore, the installer needs to handle automatic mode, manual > mode, and continue mode (continue mode: someone else has to take actions > such as HBase restart, which may be tomorrow or whenever). > > Thanks, > > Gunnar > > -----Original Message----- > From: Hans Zeller [mailto:[email protected]] > Sent: Tuesday, October 20, 2015 12:48 PM > To: dev <[email protected]> > Subject: Re: Removing the EPEL Repo prompt question in Installer > > Hi Amanda, what I did on my CentOS AWS instance was this: > > yum -y install epel-release > > > Then I installed the remaining RPMs with yum. > > So, I would suggest the installer does at least that. If the installation > of epel-release fails, then it could try to download EPEL as an RPM, like > described here ( > > http://www.rackspace.com/knowledge_center/article/install-epel-and-additional-repositories-on-centos-and-red-hat > ). > > Thanks, > > Hans > > On Tue, Oct 20, 2015 at 11:03 AM, Amanda Moran <[email protected]> > wrote: > > > Hi there Hans- > > > > So you would propose that we still attempt to install the required RPMs > if > > they are not found already installed? Should we still attempt to download > > the EPEL repo if it is not found on the system? > > > > Thanks! > > > > Amanda > > > > > > On Tue, Oct 20, 2015 at 10:59 AM, Hans Zeller <[email protected]> > > wrote: > > > > > 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 > > > > > > > > > > > > > > > -- > > Thanks, > > > > Amanda Moran > > >
