Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40342

No way to specify in the UI the network/IP address to use for SSH

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • jclouds-plugin
    • Jenkins 2.19.4
      jclouds-jenkins 2.11
      Ubuntu 14.04
      OpenStack Liberty

      We need to create multiple networks for slave runners since one network is used for logins and backend access, with the other being the default gateway for outbound Internet access (to pull down packages, etc.). While JClouds supports multiple networks, I do not see any place to define which network to use as the SSH host. Seems like about 75% of the time, it tries to use the wrong network for this.

          [JENKINS-40342] No way to specify in the UI the network/IP address to use for SSH

          Tim Soderstrom created issue -
          Tim Soderstrom made changes -
          Summary Original: No way to specify in UI network to use for SSH New: No way to specify in the UI the network/IP address to use for SSH
          Tim Soderstrom made changes -
          Environment Original: Jenkins 2.19.4
          jclouds-jenkins 2.19.3
          Ubuntu 14.04
          OpenStack Liberty
          New: Jenkins 2.19.4
          jclouds-jenkins 2.11
          Ubuntu 14.04
          OpenStack Liberty
          Fritz Elfert made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Fritz Elfert made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Fritz Elfert made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          Fritz Elfert made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Tim Soderstrom made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            felfert Fritz Elfert
            teamsnapsweetums Tim Soderstrom
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: