Change | User | Description | Committed |
---|---|---|---|
13528 | tjuricek | Moved rack and app server configuration to be managed via Salt. Also, only using a sing...le 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. « |
10 years ago |
13489 | tjuricek | Add zookeeper service to cluster for development evaluation. It's a little unclear exac...tly what values need to be distributed via zk, since a lot of the configuration may end up being handled via ports. I wanted to at least provide a way to evaluate this. P4WEBAPI-60 « |
10 years ago |
13488 | tjuricek | Added hsm:startworld and hsm:stopworld tasks to do global starts and stops. This is not... without apparent issues. It appears bundler or ruby is pausing before the nginx launch task happens. I'm not sure if there's some kind of resource issue first. P4WEBAPI-49 « |
10 years ago |
13487 | tjuricek | Pushing host, port, and URL configuration into docker-compose.yml consistently. All oth...er configuration will be figured out by a separate system later. P4WEBAPI-51 « |
10 years ago |
13479 | tjuricek | Add basic configurations for nginx and redis in the cluster. | 10 years ago |
13477 | tjuricek | More docker-compose configuration for projects in research for HSM. Added a geminabox h...ost for the cluster, which allows for quick rebuilds. Each cluster will cache the gems it needs, and publish as well. We may want to put the overwrite commands for all publish steps by default. Note: referencing "external links" can only be done 'at runtime', so "bundle install" really needs to be run in the context of 'docker-compose up' not 'docker-compose build'. This was edited in all configured libraries so far. Finally, added the p4_project_services projects to configuration, which is running under it's own puma instance. The postgres instance is a little tricky to figure out the exact workflow. Right now I'm using the host rake db:migrate task and calling createdb manually, since we need to pass the password along. « |
10 years ago |
13476 | tjuricek | Some initial concepts for 'hsm' Using docker-machine and docker-compose for a basis is... very useful, instructions are documented in hsm/hsm/README.md Currently uses the installer for perforce, doesn't have to. We *very likely* want to consider a way to set up a Docker image with data. Probably should change the Docker image for perforce to use an internal 15.x release. We may want to have all other web services just use the p4_web_api for auth, and alter our shared middleware approach. It's likely that we'd want a library of 'docker images' for our components, since not every component will get touched frequently. This will save a lot of startup time, just download and go. This may be step #1 even of hsm. « |
10 years ago |