Add SSH support to GitLab PCF Tile

"We had to use port 2222 as 22 is already in use on the VMs, also for the configuration of the elastic load balancer to work correctly. It was also a pre-emptive move so that when we have the TCP Router functionality in CloudFoundry where we can more easily expose the SSH functionality the port falls in an allowed range.

The piece that sounds like it is missing is for the GitLab UI to be updated so the example git urls provided have the 2222 port given instead of 22. "

Work on SSH support can be done after gitlab-pivotal/p-gitlab-ee#12 (closed) and gitlab-pivotal/p-gitlab-ee#21 (closed) is completed. @WarheadsSE looked into it quickly and mentioned that it is doable. Once those issues are completed, we'll check how much work is needed and how much interested from our customers and potential customers there is.

/cc @regisF

moved from gitlab-pivotal/p-gitlab-ee#1 (closed)

added pcf label

Moved to omnibus-gitlab repository so we can have a global overview and plan better the Build milestones.

changed milestone to %9.2

changed title from Set gitlab_rails['gitlab_shell_ssh_port'] = 2222`by default to Add SSH support to GitLab PCF Tile

added Scheduled label

@regisF are there any requests for this? Otherwise I think it might be worth prioritizing other things (Terraform Runner support)

I think that clarification needs a comment from @malessio

After checking with @WarheadsSE, it appears we already have a way to support SSH (documentation), but it's not pretty nor simple. This current issue would make it easier.

Because support for SSH is possible today, although a bit painful to setup, this issue can be put on the side for a while, until we receive concrete demand for this.

@regisF @WarheadsSE @marin ok, deprioritized

changed milestone to %Backlog

@WarheadsSE No customer has asked me for it. This does not mean that they are not asking PCF sales reps for it - but none of them have relayed it on to us. Since there is a workaround (per @regisF's comment above) I would say this is safe to have a lower priority

removed Scheduled label

Per https://gitlab.com/gitlab-pivotal/p-gitlab-ee/issues/24#note_28302899, we should be sure to properly handle gitlab_shell['auth_file'] and gitlab_shell['custom_hooks_dir'] when we revisit this.

Closing.

closed