Create a GitLab package for DCOS

Create a GitLab package for Mesosphere DCOS.

Mesosphere Universe is the package repository.

Each package in the repository is consistes of serveral json files. Example, see jenkins package. Each number represents a version.

package.json contains the package information. resource.json contains assets necessary for the package in case the package is being installed in closed environment. config.json configuration for the package marathon.json.mustache core definitions of the docker containers.

• Create basic template for gitlab-ce (https://github.com/twk3/universe/tree/gitlab/repo/packages/G/gitlab-ce/0)
• Add support for external db/redis if provided
• figure out how to properly handle ssh clone through the proxy
• add stmp options to the template
• support multiple instances running. (don't persist sockets, config)
• finese template, messaging, image assets (https://gitlab.com/gitlab-com/marketing/issues/303)
• PR for merging the template into the universe
• Add GitLab EE install option to the template
• Add support for persistent volumes (droped)
• Support for external volumes (new feature)
• Document a getting started guide
• Create a tutorial using the package
• Run through CD/CI workflow
• Fix Git SSH, (our keys are being denied atm for some reason, they were previously working)
• Update package to GitLab 8.10

cc @eliran.mesika

We agreed a few pair programming sessions with @twk3 and Mesosphere this week. This issue should be used to track progress.

Thanks to sunil and colin, we have a basic template working. https://github.com/twk3/universe/tree/gitlab/repo/packages/G/gitlab-ce/0

@twk3 Awesome news! Thanks for adding the checklist to the description, should make it easier to follow the progress.

We kept running into issues with the external db, where things were just hung and no errors were seen before the health check killed the process. Need to look into our connection wait timeout in gitlab to see how soon it timesout so we can adjust healthchecks accordingly.

We can also increase the healthcheck timeout for the first time (or even the interval). Those values are just defaults.

Marked the task figure out how to properly handle ssh clone through the proxy as completed

Realised the way we're doing persistent volumes is wrong - so we need to fix that. We also need to ensure we have a PR up for installation documentation available at the same time as we merge.

Marked the task add stmp options to the template as completed

Marked the task Add GitLab EE install option to the template as completed

Marked the task fix the persistant volumes to support multiple instances running. (don't persist sockets, config) as completed

@twk3 could it be the keepalive setting and that connection just timeouts? See this issue for some background.

@marin, yes, that could be it. We are still running migrations first, as part of bringing up the docker image, and then after it is up the intent was to run the schema load, and seed_fu (basically undoing all the migration work) So it's possible that getting the gitlab:db:configure change in would also help.

We got stuck today on the persistent storage. Something is chowning the postgres data directory to root. We will be investigating in the meantime, and continue our meetings on Tuesday.

@twk3 Could you write the current status?

Marked the task Add support for persistent and external volumes as completed

We figured out what was going on with the chown, and had it reported and adjusted in DC/OS. With that fix our template seems to be working as intended, but requires DC/OS 1.8 which isn't released yet. Our Tuesday meeting got pushed to Friday. So we will learn more then.

Milestone changed to %8.10

Marked the task PR for merging the template into the universe as completed

Today we confirmed the persistent volumes are working with the patch. We've created a Pull Request against the mesosphere universe: https://github.com/mesosphere/universe/pull/509

While testing the optional external volumes config we may have run into this issue in GitLab: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1106

Not 100% sure, so we will need to confirm.

While I am gone on vacation for the next two weeks, Collin and Sunil are going to continue with the remaining tasks around the documentation/tutorial. @marin has been left as technical contact, and @eliran.mesika for anything else

Met with the Mesosphere guys again today, we were re-testing the package.

• external volumes still aren't working for us, they are going to investigate on their side this week, and we will drop support for them in the GitLab package for now if we can't get them working
• SSH support has stopped working. Since we last had it working, we've moved the mounted directories, moved to a different version of GitLab (an 8.10 RC) and to the 1.8dev version of DC/OS, so this week I will explore which of those broke it, and what we can do to fix it.
• Other than that this week we are trying to walk through a gitlab - jenkins CI/CD demo, and I will be giving an overview of GitLab CI to them on Thursday, so we can start thinking about how to make that, and registry, work with mesosphere.

@twk3 for the last point, making registry work: is it possible to not rely on our bundled registry but link an official container?

@marin yes, what are your thoughts on bundled vs official container?

Just created https://github.com/emccode/rexray/issues/511 to track the external volumes issue.

SSH problem has been fixed. I had changed omnibus' git user home directory, but hadn't actually changed it on the OS. I turned back on manage_accounts for gitlab on mesosphere, and it is working again.

@twk3 If you run into issues with bundled registry, we should consider using official container with the same version we bundle to make things move faster.

Marked the task Fix Git SSH, (our keys are being denied atm for some reason, they were previously working) as completed

Today we ran through an intro to GitLab CI. Sunil has two proposals he is going to email out for how we might want to persue support. Other than that we tested the registry. The only difficulty we ran into was http vs https. In order to use it (just for a test) I had to turn off auth on the registry. It seemed to otherwise work. Not sure the best solution to the auth issue yet.

Marked the task Update package to GitLab 8.10 as completed

The GitLab version used in the Pull Request has been updated to the released version of 8.10.0

Current pull request: https://github.com/mesosphere/universe/pull/509 My understanding of the status of the pull request looks like the following:

• Discussion is progressing on the external volumes issue https://github.com/emccode/rexray/issues/511, the current PR still has support for external volumes, so is waiting on that

Optionally:

• Registry support will require us to add some new config options to the PR, so if the PR is still open because of the when we figure the registry out, it's likely registry config options may go into the PR before it is merged

Milestone changed to %8.11

The registry issue may have been related to the version of gitlab we were running. Production had the same problem for a while. I will try again this week with 8.10.3 to see if the auth problems are fixed with the registry.

Can't wait!

Didn't get around to testing the registry this week. So I will try and fit it in on Monday.

The registry has been enabled in the pull request. So I believe the external volumes issue is the remaining one.

@ssk2 there doesn't appear to have been movement on https://github.com/emccode/rexray/issues/511 in a few weeks, it's not waiting on us to retest something is it?

Today we decided to drop the persistent volume support. This is due to it not being easy to update your install to newer GitLab versions if you are using persistent volumes. In it's place we added support for host pinning, which makes sure your app keeps coming up on the same host. A trade-off of fall-over resilience for ability to upgrade. The hope is that better backup and restore tools will enable us to revisit upgrades on persistent volumes in the future.

The good news is that we think external volumes are working. We ran out of time today to finish testing them, but they looked very promising.

With these changes what is left to do now is:

• Current package needs to be retested (single node normal, single node with external volumes, and HA mode)
• A quick start quide needs to be created (there is a shared google doc where sunil and I will be collaborating next week)
• A production setup guide needs to be created

Great work @twk3 and @ssk2 !

Milestone changed to %8.12

Milestone changed to %8.13

This was shipped in 8.12 https://mesosphere.com/blog/2016/09/16/gitlab-dcos/

Status changed to closed

The template lives in Mesosphere's universe repo: https://github.com/mesosphere/universe/tree/version-3.x/repo/packages/G/gitlab