Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

on-call: Note that devs should escalate to RE for vCloud Director issues #2207

Merged
merged 3 commits into from Jan 9, 2020

Conversation

@issyl0
Copy link
Member

issyl0 commented Jan 8, 2020

  • There used to be instructions at step 7 which required all devs to
    have vCloud Director set up. In reality, these instructions never
    worked and messed up the existing VPN configuration. 馃槺
  • Instead, escalate to RE. RE GOV.UK team members know how to do access
    vCloud Director and do Carrenza machine things, and can help us.
  • While I was there, though, @sengi told me that the instructions aren't
    100% reliable for AnyConnect depending on the versions of things, and
    they require rewriting on every version. The OpenConnect ones require
    less manual effort, so keep those, but delete the AnyConnect ones as
    it's less faff to only update one set!

There's more context in the commit messages.

issyl0 added 3 commits Jan 8, 2020
- These don't work. According to @sengi, we spend time every time
  there's an update working out why they don't work and fixing it. For
  the number of times, it's not worth it. Even trying them out blats
  your existing GDS VPN configuration, requiring a reinstall. So let's
  not even try.
- This updates the OpenConnect instructions to be slightly more verbose,
  as they have a higher chance of working. (Though I didn't have any
  success either.)
- This repo is archived as the mirrors are in S3 and Google Cloud.
- It's fine to escalate to RE for things like this. So note that we
  should know how to escalate to them. For brave devs, I've included the
  link to the instructions that RE also follow, but don't expect
  success!
@sengi
sengi approved these changes Jan 9, 2020
Copy link
Contributor

sengi left a comment

LGTM. I haven't tested the setup steps for OpenConnect but it's more important to remove the now-rotten instructions for AnyConnect so that nobody else breaks their setup.

@issyl0 issyl0 merged commit 2f97e01 into master Jan 9, 2020
1 check passed
1 check passed
continuous-integration/jenkins/branch This commit looks good
Details
@issyl0 issyl0 deleted the on-call-vcloud branch Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can鈥檛 perform that action at this time.