I agree. It makes sense to me that we update provisioning guide to document primarily pyinstaller, along with a small note that the legacy command-line installer is deprecated, but available. We can direct users to 2.0 release for documentation on that installer, so that we don't have to clutter the document with duplicate info.
I can add info on how to install the Ambari plug-in, perhaps with a pointer to Ambari docs on how to use it. Pyinstaller is the main one, since it supports multiple distros. Eason, if I take the first shot at the high-level stuff and Ambari info, can you update the command-line installer parts? --Steve > -----Original Message----- > From: Sandhya Sundaresan [mailto:[email protected]] > Sent: Monday, February 13, 2017 2:27 PM > To: [email protected] > Subject: RE: [RELEASE] 2.1 Release Branch Coming Soon -- Install > documentation > > Agree, I think we should include it and offer both and suggest trying Python > installer first. If Jenkins tests are starting to use the python installer > then it's > getting tested every night. > Sandhya > > -----Original Message----- > From: Dave Birdsall [mailto:[email protected]] > Sent: Monday, February 13, 2017 1:57 PM > To: [email protected] > Subject: RE: [RELEASE] 2.1 Release Branch Coming Soon -- Install > documentation > > What's the thinking on the legacy installer? Is it the intent that the Python > installer will replace it? If so, how fast? > > Seems like the existing installer should be retained for 2.1 since it is > tried and > true. > > The Python installer should be fully documented so that it will get more > testing and usage. Perhaps there should be a disclaimer: Try Python first and > if there are issues, fall back to the old one. > > -----Original Message----- > From: Steve Varnau [mailto:[email protected]] > Sent: Monday, February 13, 2017 1:50 PM > To: [email protected] > Subject: RE: [RELEASE] 2.1 Release Branch Coming Soon -- Install > documentation > > Regarding the upcoming release, we now have a new command-line installer > (pyinstaller) and an Ambari plug-in. > > I am sure neither one of these has nearly as much testing/usage as the > legacy command-line installer. > > Automated tests, for instance, have not yet switched to using pyinstaller > (hopefully coming soon). > > There is a very small wiki page that gives a clue to developers about the > installers (mostly a pointer to the README in the source tree). > https://cwiki.apache.org/confluence/display/TRAFODION/Cluster+Installatio > n > > But the provisioning guide still discusses only the legacy installer > (sections: > 2,6,7,9). > http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html > > My question is which of these install tools should we document for release > 2.1 in the guide? Should we stick with the tried-and-true option, or get the > new methods out in front? Opinions? > > --Steve > > > -----Original Message----- > > From: Sandhya Sundaresan [mailto:[email protected]] > > Sent: Thursday, February 9, 2017 10:55 AM > > To: [email protected] > > Subject: RE: [RELEASE] 2.1 Release Branch Coming Soon > > > > Hi, > > I'll take over this next release 2.1 for Trafodion . I will create > > the release branch on 2/15/207 . > > If there is any content you'd really like to be part of this upcoming > > release please get them in and let me know if there is a reason to > > wait a few more days to create the release branch. > > Thanks > > Sandhya > > > > -----Original Message----- > > From: Gunnar Tapper [mailto:[email protected]] > > Sent: Monday, January 30, 2017 11:31 AM > > To: [email protected] > > Subject: [RELEASE] 2.1 Release Branch Coming Soon > > > > Hi, > > > > As you know, we're been planning for the 2.1 release for the last 6-8 > > weeks. The content is available at: > > https://cwiki.apache.org/confluence/display/TRAFODION/Release+2.1 > > > > In order to move forward, I'm planning to create the 2.1 release > > branch on Thursday February 2, 2017. > > > > Please ensure that you: > > > > 1. Check changes that should be part of this release. > > 2. Update Jira statuses. > > > > Please speak up if you have an issue with us moving forward with the > > 2.1 release at this point. > > > > -- > > Thanks, > > > > Gunnar > > *If you think you can you can, if you think you can't you're right.*
