Support for using the ServiceNet IP address for SSH connections #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an optional config setting
:servicenet
, which defaults tofalse
.When
true
, the driver will use the first private address of thenode instead of the first public address. The first private ip
address should always be the ServiceNet interface (10.184.0.0/13
or 10.208.0.0/12).
The ServiceNet interface may be preferable when running kitchen
on another Rackspace cloud server, like a Jenkins build server,
or for customers with VPN access to ServiceNet.
Using ServiceNet avoids bandwidth charges and may avoid changes
to the PublicNet/RackConnect firewall rules to allow
SSH connections to the kitchen test VMs from the public Internet.