Uploaded image for project: 'IT: Release Engineering'
  1. IT: Release Engineering
  2. RELENG-4067

Sigul: Update all configs to new bridges

Issue XMLXMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • General
    • Sigul: Update all configs to new bridges
    • All / Cross Project

      From Konstantin:

      In preparation for the upcoming PDX datacenter move, we are removing
      all dependencies on PDX infrastructure for day-to-day operations. All
      projects using sigul MUST update their client configuration to the
      following (only listing the lines that must change – the other ones
      should stay the same):

      EDIT: Don't forget to update SIGUL_BRIDGE_IP global var in global-vars-{production,sandbox}.sh when making the below changes.
      sigul-bridge-yul.linuxfoundation.org: 199.204.45.55
      sigul-bridge-us-west-2.linuxfoundation.org: 44.232.126.158

      projects in vex-yul:
      [client]
      bridge-hostname: sigul-bridge-yul.linuxfoundation.org
      server-hostname: vex-yul-wl-sigul-server-1.dr.codeaurora.org

      projects in AWS (and elsewhere, like vex-sjc):
      [client]
      bridge-hostname: sigul-bridge-us-west-2.linuxfoundation.org
      server-hostname: aws-us-west-2-lfit-sigul-server-1.dr.codeaurora.org

      A couple of notes:
      1. this can be done at any time as the new bridges work alongside
      current ones; you should be able to schedule this migration and roll
      back to the previous configuration if you encounter problems
      2. the new bridges are listening on external IPs, so the clients must
      be able to reach out to the internet on the sigul bridge port
      (tcp/44334)
      3. if this isn't done by mid-January, your project is likely to
      experience disruptions as we continue to work on VPN sunset at PDX, so
      please don't put it off

              agrimberg Andrew Grimberg
              eball Eric Ball
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: