Add (firewall management for) VPC support #151
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
``` Running RSpec tests in folder : vmlifecycle Using Vagrant file : Vagrantfile.advanced_networking VM Life Cycle starts Linux and Windows VM destroys Linux and Windows VM Finished in 3 minutes 5.1 seconds (files took 0.13309 seconds to load) 2 examples, 0 failures Running RSpec tests in folder : networking Using Vagrant file : Vagrantfile.advanced_networking Networking features creates firewall and portwarding rules Finished in 2 minutes 42.1 seconds (files took 0.13307 seconds to load) 1 example, 0 failures Running RSpec tests in folder : rsync Using Vagrant file : Vagrantfile.advanced_networking VM RSync There was an error when attempting to rsync a synced folder. Please inspect the error message below for more info. Host path: /cyg/y/vagrant-cloudstack/functional-tests/rsync/ Guest path: /vagrant Command: rsync --verbose --archive --delete -z --copy-links <--snip--> mm_receive_fd: no message header process_mux_new_session: failed to receive fd 0 from slave mux_client_request_session: read from master failed: Connection reset by peer Failed to connect to new control master rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2] ``` RSync to be expected on Windows...
bheuvel
force-pushed
the
refact/prepare_for_vpc
branch
from
8514e4e to
5a8ffa2
Compare
|
When using a scenario which doesn't use |
|
Changes Unknown when pulling 8c8c01b on refact/prepare_for_vpc into * on master*. |
bheuvel
force-pushed
the
refact/prepare_for_vpc
branch
from
8c8c01b to
7d8202c
Compare
|
Changes Unknown when pulling 7d8202c on refact/prepare_for_vpc into * on master*. |
|
Changes Unknown when pulling 54b9f07 on refact/prepare_for_vpc into * on master*. |
bheuvel
force-pushed
the
refact/prepare_for_vpc
branch
from
54b9f07 to
035e2c0
Compare
|
Changes Unknown when pulling 035e2c0 on refact/prepare_for_vpc into * on master*. |
|
Functional tests are successful now: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
My environment was set using:
The
VPC_..andVR_...are used to specifically target those. The last two are the "default" which are used in the other tests; (VM Life Cycle) was thereby done in a VPC-tier.The
Networking featurestest, does the same testing as it used to, only now the 2 (tests/) vms specifically in a guest network/Virtual Router, and also the same (tests/)vms in a tier of a VPC.