deps.sls #2

  • //
  • guest/
  • tjuricek/
  • p4ws/
  • salt/
  • srv/
  • perforce/
  • web-services/
  • p4webapi/
  • deps.sls
  • Commits
# Change User Description Committed
#2 15791 tjuricek Removing very old p4ws branch
#1 13266 tjuricek Reorganized depot to avoid stream/main in path.

This may be re-imported.
//guest/tjuricek/p4ws/stream/main/salt/srv/perforce/web-services/p4webapi/deps.sls
#9 13262 tjuricek Added the 'eval' Vagrant box that uses our deployed packages.
#8 13254 tjuricek Revise package and gem versioning.

Packages will use [gem]-[changelist] as their versions. Gems will use a standard Ruby MAJOR.MINOR.REVISION format.

P4WEBAPI-64
#7 13238 tjuricek Moved rack and app server configuration to be managed via Salt.

Also, only using a single value "url" to configure how the p4_project_services instance references the p4_web_api.

And, removing the Docker setup, since that won't work for a production system.
#6 13235 tjuricek Setup God to manage both the p4 web api and p4 project services processes.

Apparently, there can only be one true god per machine.
#5 13230 tjuricek Created a 'cluster' build procedure that creates an installer on build, and executes the install on a test instance.

The main change is to package all gem dependencies via 'vendor/cache' (using the 'bundle package' command).

Right now, there appears to be an issue with test data initialization, which may need a revised approach.
#4 13227 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 13225 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 13222 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 13206 tjuricek Complete and seed the setup of the p4webapi in a development mode.

This works against the local development tree for dev environments.