6aac32480a
We have seen the following error message crop up a couple times recently: ``` FATAL: could not create shared memory segment: No space left on device DETAIL: Failed system call was shmget(key=5432001, size=56, 03600). HINT: This error does *not* mean that you have run out of disk space. It occurs either if all available shared memory IDs have been taken, in which case you need to raise the SHMMNI parameter in your kernel, or because the system's overall limit for shared memory has been reached. The PostgreSQL documentation contains more information about shared memory configuration. child process exited with exit code 1 ``` Based on [the PostgreSQL documentation](https://www.postgresql.org/docs/12/kernel-resources.html), this should fix it. CHANGELOG_BEGIN CHANGELOG_END |
||
---|---|---|
.. | ||
macos | ||
modules/gcp_cdn_bucket | ||
.gitignore | ||
apply | ||
bazel_cache.tf | ||
data_bucket.tf | ||
dumps_bucket.tf | ||
hoogle_server.tf | ||
main.tf | ||
nix_cache.tf | ||
periodic_killer.tf | ||
README.md | ||
vsts_agent_linux_startup.sh | ||
vsts_agent_linux.tf | ||
vsts_agent_windows.tf | ||
writer.tf |
DAML
This is the terraform code used by the DAML repository to deploy supporting infrastructure such as the Bazel caches, Nix caches and Azure Pipeline (VSTS) Agents.
Setup
To deploy the infrastructure changes, you will to get access to the
da-dev-gcp-daml-language
Google project from DA IT. Then run
gcloud auth login
to configure the local credentials.
Deployment
All the infrastructure is currently deployed using Terraform. For convenience we have a little wrapper script that you can run to apply the latest changes:
$ ./apply
Writer service-account key
To avoid holding the secret key into the store, creating the key has to be done through the UI.
This can be done here: https://console.cloud.google.com/iam-admin/serviceaccounts/details/104272946446260011088?project=da-dev-gcp-daml-language
Setting up credentials
In order to interact with these Terraform files, you will need security to give
you access to the relevant GCP project (da-dev-gcp-daml-language
), and login
via gcloud
by running:
gcloud auth application-default login --account your.name@gcloud-domain.com