[jira] [Commented] (TRAFODION-24) Removing the Scanner from Trafodion Install

["Anoop Sharma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TRAFODION-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619508#comment-14619508 ] 

Anoop Sharma commented on TRAFODION-24:
---------------------------------------

Are these checks in multiple places? Traf install script and scanner?
Is there a list of checks/validation that the scanner does? And the
ones that are part install scripts?

If relevant scanner functionality is now part of install script, then
it could be removed. Can no_scanner option be made the default
instead of removing code?

anoop


> Removing the Scanner from Trafodion Install
> -------------------------------------------
>
>                 Key: TRAFODION-24
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-24
>             Project: Apache Trafodion
>          Issue Type: Brainstorming
>            Reporter: Amanda Moran
>            Priority: Minor
>              Labels: installer
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Would like to get some feedback on possibly removing the scanner from Trafodion Install. We currently have a --no_scanner option that we have had to use on every POC/customer install. We get many false errors from the scanner and when we use the --no_scanner option we get a successful install and Trafodion works fine. 
> All the important checks that are vital for trafodion installing properly are in the trafodion install scripts (all of the important checks that are in the scanner were taken from the Trafodion install scripts). 
> I suggest we discontinue use of the scanner at this time. If we need additional checks we can add them to the installer scripts. We can also do some tweaking to the installer to "pick up where it left off" so that way when we do find errors we don't have to rerun the installer all over again, we will just start in the appropriate place. 
> Looking forward to a discussion on this!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)