You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2021. It is now read-only.
Of course I am not an expert. So I may have made a mistake here but anyway - here goes:
Part of my Vagrantfile:
` config.vm.define "alice" do |alice|
alice.vm.provider :azure do |azure, override|
do_common_azure_stuff.call azure, override
azure.vm_name="a2l-alice"
azure.vm_image_urn = "MicrosoftWindowsServer:WindowsServer:2019-Datacenter:2019.0.20190115"
azure.vm_size = myMachineSize
# winrm lytter på 5985/5986. Vagrant bruger 5986
override.winrm.port = 15001
override.vm.network "forwarded_port", host: 15001, guest: 5986, protocol: "tcp"
end
end
config.vm.define "bob" do |bob|
bob.vm.provider :azure do |azure, override|
do_common_azure_stuff.call azure, override
azure.vm_name="a2l-bob"
azure.vm_image_urn = "MicrosoftWindowsDesktop:Windows-10:19h1-pro:18362.418.1910070306"
azure.vm_size = myMachineSize
# winrm lytter på 5985/5986. Vagrant bruger 5986
override.winrm.port = 15002
override.vm.network "forwarded_port", host: 15002, guest: 5986, protocol: "tcp"
end
end
`
The Idea was to see how the NSG would be built.
I expected a rule 124 opening port 15001 and a rule 125 opening port 15002
That didn't happen. Only port 15002 opened.
So I ran the test again running up only Alice.
Rule 124 opened port 15001
Then I ran up Bob
Rule 124 was replaced now opening port 15002
Of course now port 15001 is no longer open.
When running up both machines it also appeared as if only the one machine was truly allocated. The other machine would have the public IP allocated but not much more.
Obviously Vagrant would eventually complain that the machine it had failed to setup wouldn't answer. In essence: had that happen it would truly be a virtual machine.
Am I barking up the wrong tree?
Cheers,
Karsten
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Of course I am not an expert. So I may have made a mistake here but anyway - here goes:
Part of my Vagrantfile:
` config.vm.define "alice" do |alice|
alice.vm.provider :azure do |azure, override|
do_common_azure_stuff.call azure, override
azure.vm_name="a2l-alice"
azure.vm_image_urn = "MicrosoftWindowsServer:WindowsServer:2019-Datacenter:2019.0.20190115"
azure.vm_size = myMachineSize
# winrm lytter på 5985/5986. Vagrant bruger 5986
override.winrm.port = 15001
override.vm.network "forwarded_port", host: 15001, guest: 5986, protocol: "tcp"
end
end
config.vm.define "bob" do |bob|
bob.vm.provider :azure do |azure, override|
do_common_azure_stuff.call azure, override
azure.vm_name="a2l-bob"
azure.vm_image_urn = "MicrosoftWindowsDesktop:Windows-10:19h1-pro:18362.418.1910070306"
azure.vm_size = myMachineSize
# winrm lytter på 5985/5986. Vagrant bruger 5986
override.winrm.port = 15002
override.vm.network "forwarded_port", host: 15002, guest: 5986, protocol: "tcp"
end
end
`
The Idea was to see how the NSG would be built.
I expected a rule 124 opening port 15001 and a rule 125 opening port 15002
That didn't happen. Only port 15002 opened.
So I ran the test again running up only Alice.
Rule 124 opened port 15001
Then I ran up Bob
Rule 124 was replaced now opening port 15002
Of course now port 15001 is no longer open.
When running up both machines it also appeared as if only the one machine was truly allocated. The other machine would have the public IP allocated but not much more.
Obviously Vagrant would eventually complain that the machine it had failed to setup wouldn't answer. In essence: had that happen it would truly be a virtual machine.
Am I barking up the wrong tree?
Cheers,
Karsten
The text was updated successfully, but these errors were encountered: