Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: jclouds-plugin
-
Environment:Jenkins 2.19.4
jclouds-jenkins 2.11
Ubuntu 14.04
OpenStack Liberty
-
Similar Issues:
Description
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.
Attachments
Activity
Installed, thanks! I'm validating things right now. Having an issue I think that is more with Jenkins than the plugin so I'm working on that. Mostly I just wanted to update the issue so you knew I was taking a look.
Tim Soderstrom
added a comment - Installed, thanks! I'm validating things right now. Having an issue I think that is more with Jenkins than the plugin so I'm working on that. Mostly I just wanted to update the issue so you knew I was taking a look. In my testing so far, it seems to be working as described. I tried it with both networks just to make sure it wasn't do anything funky. I think our actual jobs are doing something odd I need to look at (and/or I picked the wrong job to use as a test), but the plugin itself seems to work as advertised (I see in the logs it's trying to connect where I tell it when it matches and likewise the UI has the proper IP bolded).
I need to test more, but so far, it looks like we're in business!
Tim Soderstrom
added a comment - In my testing so far, it seems to be working as described. I tried it with both networks just to make sure it wasn't do anything funky. I think our actual jobs are doing something odd I need to look at (and/or I picked the wrong job to use as a test), but the plugin itself seems to work as advertised (I see in the logs it's trying to connect where I tell it when it matches and likewise the UI has the proper IP bolded).
I need to test more, but so far, it looks like we're in business!
I just released v2.12 of the plugin.
So if you are ok with that, you can close the issue.
2.12 appeas to be working great! Thanks so much for getting this fixed up and in rapid order too!
Tim Soderstrom
added a comment - 2.12 appeas to be working great! Thanks so much for getting this fixed up and in rapid order too! 
Ok, I have something to test for you:
https://jenkins.ci.cloudbees.com/job/plugins/job/jclouds-plugin/org.jenkins-ci.plugins$jclouds-jenkins/lastSuccessfulBuild/artifact/org.jenkins-ci.plugins/jclouds-jenkins/2.12-SNAPSHOT/jclouds-jenkins-2.12-SNAPSHOT.hpi
This adds a new Textfield "Preferred Address" in the Advanced Settings of the template. There you can enter an address/prefix and that should then match one of the node's IP-Addresses.
Please report back if that fits your needs (or with any further suggestions). If everything is ok for you, I then will release v 2.12 with that change.
Cheers
-Fritz
Edit: URL changed to latest artifact.