Request for install directions clarifiation

[Jim Davison]

Hello Folks, a few questions on getting everything installed & running:

My environment: CentOS 6.5, OpenChorus 4.0/Master per github

• When searching for documentation, I often find items pertaining to Alpine's "Official" chorus, e.g., https://alpine.atlassian.net/wiki/display/CD/Chorus+Documentation+Home. Is there version parity between them on what's on github, or does OpenChorus diverge?
• Wiki guide indicates GreenPlum 2.2.5 should be downloaded, scripts hard-coded to that release. GoPivotal as only 2.3.1 though. Is there a source for 2.2.5? If not,  is this newer version otherwise compatible, after changing script references? 
• Running bundle does not seem to install vagrant. Everything else runs fine, no errors, but no listing for vagrant either...  
• After installing postgres from packaging, I'm still lacking in all of the setup that would be performed by initdb, which doesn't seem to be called anywhere. Am I missing a step, a script to run to get things running prior to runing chorus_control or start-postgres?
• Is there a stock VM with everything pre-installed anywhere?

Thanks,

Jim

[Robbie GIll]

Hi Jim - Answers are inline below. Hope this helps you get up and running.  - Robbie

On Monday, June 23, 2014 5:58:20 PM UTC-7, Jim Davison wrote:

Hello Folks, a few questions on getting everything installed & running:

My environment: CentOS 6.5, OpenChorus 4.0/Master per github

• When searching for documentation, I often find items pertaining to Alpine's "Official" chorus, e.g., https://alpine.atlassian.net/wiki/display/CD/Chorus+Documentation+Home. Is there version parity between them on what's on github, or does OpenChorus diverge? 

The documentation should match what you will find in OpenChorus with the exclusion of the workflow editor and execution engine. That is a proprietary component available from Alpine. 

• Wiki guide indicates GreenPlum 2.2.5 should be downloaded, scripts hard-coded to that release. GoPivotal as only 2.3.1 though. Is there a source for 2.2.5? If not,  is this newer version otherwise compatible, after changing script references? 

Any version of Greenplum should suffice, Chorus supports all GP versions. The vagrant VM is used for integration tests and is not required to start Chorus. 

• Running bundle does not seem to install vagrant. Everything else runs fine, no errors, but no listing for vagrant either...  

Vagrant now prefers to be installed standalone and we removed it from our Gemfile - I'll update the documentation. Follow installation directions for your platform at http://www.vagrantup.com/  

• After installing postgres from packaging, I'm still lacking in all of the setup that would be performed by initdb, which doesn't seem to be called anywhere. Am I missing a step, a script to run to get things running prior to runing chorus_control or start-postgres?

rake development:init will initialize the Postgres database.  (See: https://github.com/Chorus/chorus/wiki/Getting-started-with-Chorus-development#initialize-the-database)

• Is there a stock VM with everything pre-installed anywhere?

Sorry, there is not one available 

Thanks,

Jim

[Jim Davison]

Thanks! Very helpful. I'll have to to check the output from development::init, I didn't notice an error, but I must have missed something related to postgres.