# System user and group used for the p4d account. # Using the same account for web service applications is not recommended. p4d.group: perforce p4d.user: perforce # The default 'server name' we configure for. # This is actually called 'helix-evaluation' since this code could easily be # a part of an eval package suite. If it happens to be, then don't create a # p4d instance, just use the one already there. p4d.server: helix-evaluation p4d.users.super.user: super p4d.users.super.password: superuser1A! # Default settings p4d.P4PORT: 1666 p4d.P4ROOT: /var/lib/perforce/p4d # This should be used, but isn't at the moment due to a weird issue with Salt # kind of ignoring the version number of virtual packages perforce.pkg.version: 2015.1* # The typical path where we expect our Ruby wrappers to be deployed p4webapi.ruby.gemset: /home/webservices/.rvm/gems/ruby-2.2.2@p4webapi p4webapi.ruby.wrappers: /home/webservices/.rvm/wrappers/ruby-2.2.2@p4webapi
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 13517 | tjuricek |
Revised Salt hierarchy to allow for CD clustering. Now, there are two main salt environments: 'build' and 'eval'. The 'eval' environment can be configured for testing or development by setting the Grain 'dev_pillar: True' or 'test_pillar: True'. The test modes may need a bit more effort to figure out exactly where I'll put the .deb files. The dev box passes p4_web_api tests. |
||
#3 | 13515 | tjuricek |
Initial configuration for the p4_project_services. The tests haven't been run yet, so it's likely missing some more configuration. Using vagrant to even manage these environments may not be our realistic CD premise. I may end up moving some more responsibility into the Salt layer, which would make vSphere automation easier. |
||
#2 | 13512 | tjuricek |
Add 'test-ubuntu12' environment that sets up projects based on "production" packages. Packages are installed from source files that should have been created by the last 'build-ubuntu12' environment. Since the package building process "dirties" up the environment it's better to use a clean system to test package installation. |
||
#1 | 13495 | tjuricek |
Basic p4d configuration for development/evaluation. Uses the perforce-server package and just triggers the creation of the helix-evaluation server "instance". This should nicely just ignore the default setup in case these scripts are used in the Helix OVA appliance setup. |