omnibus-gitlab merge requestshttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests2017-10-06T22:21:21Zhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1845Enable builds to occur on forks and pipelines hosted on gitlab instances2017-10-06T22:21:21Zusername-removed-693353Enable builds to occur on forks and pipelines hosted on gitlab instancesCurrently these builds are hard-coded to only run on this repo hosted at gitlab.com, not on a fork or a private instance of gitlab.
I'd like to enable fork-and-build for projects to make it easier for people to get started contributing.Currently these builds are hard-coded to only run on this repo hosted at gitlab.com, not on a fork or a private instance of gitlab.
I'd like to enable fork-and-build for projects to make it easier for people to get started contributing.https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1832Create AWS CloudFormation template2020-07-09T14:11:15ZJoshua LambertCreate AWS CloudFormation templateI have opened this MR to contain the GitLab CE documentation changes needed to support the AWS quickstart.
Closes #2176
I have also created a new repo to host the AWS templates: https://gitlab.com/gitlab-com/gitlab-aws-quickstart...I have opened this MR to contain the GitLab CE documentation changes needed to support the AWS quickstart.
Closes #2176
I have also created a new repo to host the AWS templates: https://gitlab.com/gitlab-com/gitlab-aws-quickstart
Architecture:
![GitLabQuickStartAWSArchitecture](/uploads/1dee6e828aaa5b4cd78cfd56df0771f3/GitLabQuickStartAWSArchitecture.png)
Installation instructions are currently in the README.md of the new repo.https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1780WIP: Ncurses update2020-07-09T14:43:14ZDJ MountneyWIP: Ncurses updateThis updates to the current patched version of ncurses.
This supposedly fixes a bug in building on arm64 for: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1625
I did try the non-patched 6.0 release, but it does not compile on D...This updates to the current patched version of ncurses.
This supposedly fixes a bug in building on arm64 for: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1625
I did try the non-patched 6.0 release, but it does not compile on Debian 9.
Test packages available here: https://dev.gitlab.org/gitlab/omnibus-gitlab/pipelines/56365
ncurses changed a bunch of it's defaults in 6, so it is likely that this has broken something, if the libs we use that depend on it haven't been updated to support it yet.
We would need to test these packages on each platform before turning this MR as non-WIP.
patch specific changes to ncurses:
http://invisible-island.net/ncurses/NEWS.html
cc\ @elrarohttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1753Remove duplicated shared object files from grpc gem2017-09-04T15:43:51Zusername-removed-100770Remove duplicated shared object files from grpc gemThis MR removes duplicated, unused and large shared object files included in grpc gem.
Closes #2585This MR removes duplicated, unused and large shared object files included in grpc gem.
Closes #2585Marin JankovskiMarin Jankovskihttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1714Redis: patch IPv6 support detection2020-07-09T14:33:53ZJason PlumRedis: patch IPv6 support detection### Summary
The Redis codebase has an issue with IPv6, and detecting failure.
### Explanation
When provided with no bind address, Redis will attempt to listen on both IPv6
IPv4 localhost, however it only handles `EAFNOSUPPORT` an...### Summary
The Redis codebase has an issue with IPv6, and detecting failure.
### Explanation
When provided with no bind address, Redis will attempt to listen on both IPv6
IPv4 localhost, however it only handles `EAFNOSUPPORT` and not `EPROTONOSUPPORT`.
This can, and does cause Redis to exit on a machine that has no IPv6 protocol,
such as most recent releases of `dockerd`.
I experience this surprise during the building of the `gitlab-pivotal/gcp-infra`
project, but that was with Redis in the same `v3.x` family but outside our codebase.
This time, we found Redis to be a problem when examining ARMv7 builds (RPi 2),
and I was reminded of this problem.
Essentially pulled from https://github.com/antirez/redis/issues/3894
The included patch file was originally made against Redis `3.2.8`, but applies cleanly with a few lines of fuzz to `3.2.5` (https://github.com/antirez/redis/blob/3.2.8/src/server.c#L1786)
### Why does this matter
Unless we explicitly ensure that only those protocols supported by the host system are specific in the `redis.conf`, we can't ensure that a host system without support for IPv6 will function. Currently this has not bitten us directly. As seen with https://gitlab.com/gitlab-terraform/gce/ being functional, this may not be a high priority. We can not, however, assume that this will be a reliable item without ensuring that proper detection and handling does occur.
See
* https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2545#note_34061035
* https://github.com/pivotal-cf/cf-redis-release/issues/44
* https://github.com/antirez/redis/blob/unstable/src/server.c#L1786
* The `v4.0`, `v3.2`, and `unstable` branches have been examined, and contain this issue.DJ MountneyDJ Mountneyhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1704Default to not running the populate cache command if S3 caching is not setup2020-07-09T14:28:53ZDJ MountneyDefault to not running the populate cache command if S3 caching is not setupDefault to not running the populate cache command if S3 caching is not setup
This makes it easier to run the omnibus without setting up cache.
I ran into this issue earlier this week in my fork, and @ayufan ran into it today.Default to not running the populate cache command if S3 caching is not setup
This makes it easier to run the omnibus without setting up cache.
I ran into this issue earlier this week in my fork, and @ayufan ran into it today.9.4DJ MountneyDJ Mountneyhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1686Expand unicorn chpst environment with envs from env_dir2017-06-27T12:45:14Zusername-removed-384663Expand unicorn chpst environment with envs from env_dirFixes #2534
Initializes the unicorn environment from `env_dir` when process is started with `chpst`.Fixes #2534
Initializes the unicorn environment from `env_dir` when process is started with `chpst`.https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1684WIP: Resolve "Upgrading a geo instance results in error rendering pg_hba.conf...2017-06-26T19:14:22ZIan BaumWIP: Resolve "Upgrading a geo instance results in error rendering pg_hba.conf template"Closes #2528Closes #2528https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1639WIP: Resolve "Split postgresql recipes into a separate cookbook"2020-07-09T14:11:58ZIan BaumWIP: Resolve "Split postgresql recipes into a separate cookbook"Closes #2480Closes #2480Ian BaumIan Baumhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1593Added GoDaddy (SSL), alphabetized email providers.2017-05-31T12:19:44Zusername-removed-1363219Added GoDaddy (SSL), alphabetized email providers.Added GoDaddy (SSL), alphabetized email providers.Added GoDaddy (SSL), alphabetized email providers.https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1592Removed requirement for port number in mattermost['service_site_url'] setting2017-06-06T15:30:27Zusername-removed-695691Removed requirement for port number in mattermost['service_site_url'] settinghttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1589use privileged scc for openshift user2017-06-08T23:37:07Zusername-removed-799439use privileged scc for openshift usersshd as configured in the gitlab ce image uses `UsePrivilegeSeparation`, which requires `SYS_CHROOT` permissions. The `anyuid` scc does not allow this.
`$ oc describe scc anyuid
Name: anyuid
Priority: 10
Access:
Users: ...sshd as configured in the gitlab ce image uses `UsePrivilegeSeparation`, which requires `SYS_CHROOT` permissions. The `anyuid` scc does not allow this.
`$ oc describe scc anyuid
Name: anyuid
Priority: 10
Access:
Users: system:serviceaccount:gitlab-ce:gitlab-ce-user
Groups: system:cluster-admins
Settings:
Allow Privileged: false
Default Add Capabilities: <none>
Required Drop Capabilities: MKNOD,SYS_CHROOT <--
...`
However, `privileged` does. This PR updates the docs and unifies the method for updating the scc.
As an alternative to this PR, `UsePrivilegeSeparation` could be set to `no` in the `sshd_config`.https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1559added the capability to adjust the presistence of the omnibus redis instance ...2017-05-27T06:13:02ZJason Tevnanadded the capability to adjust the presistence of the omnibus redis instance (or also disable it)This change adds the ability to adjust the persistence of the redis instance -> the defaults fall back to the redis default, so no changes should be made.
it is based on the standard [redis cookbook](https://github.com/brianbianco/redisi...This change adds the ability to adjust the persistence of the redis instance -> the defaults fall back to the redis default, so no changes should be made.
it is based on the standard [redis cookbook](https://github.com/brianbianco/redisio/blob/master/templates/default/redis.conf.erb#155)Jason TevnanJason Tevnanhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1505Add Runner template example2017-05-22T19:45:39ZDJ MountneyAdd Runner template exampleCloses: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2260Closes: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/22609.2DJ MountneyDJ Mountneyhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1459add persistent volume for git backups2018-06-16T10:11:47Zusername-removed-1160602add persistent volume for git backupsAdd a persistent volume for git backups on Openshift, for https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2045Add a persistent volume for git backups on Openshift, for https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2045https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1457WIP: Use realpath to locate analyze_new_cluster.sh2017-06-21T14:39:10ZIan BaumWIP: Use realpath to locate analyze_new_cluster.shFor users who have their postgresql data in an alternate location.
Closes #1930For users who have their postgresql data in an alternate location.
Closes #19309.0Ian BaumIan Baumhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1421WIP: Connect to redis/postgres with the gitlab user for prometheus exporters2018-10-09T23:14:30ZDJ MountneyWIP: Connect to redis/postgres with the gitlab user for prometheus exporters
Related: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2107
Related: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2107Ben KochieBen Kochiehttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1417WIP: Resolve "Refactor nginx recipe and template"2017-08-23T18:48:57Zusername-removed-917896WIP: Resolve "Refactor nginx recipe and template"Closes #784Closes #784https://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1390add database probe monitoring2017-03-23T10:28:46Zusername-removed-668822add database probe monitoringregarding this issue https://gitlab.com/gitlab-org/gitlab-monitor/issues/20, I propose to add the possibility to chose which database probe we want to activate.
cc @ahmadsherifregarding this issue https://gitlab.com/gitlab-org/gitlab-monitor/issues/20, I propose to add the possibility to chose which database probe we want to activate.
cc @ahmadsherifhttps://staging.gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/1389WIP: Automate Azure image creation2017-06-15T11:08:38ZBalasankar CWIP: Automate Azure image creationCloses #2060Closes #2060