OpenStack VM to VM Communication Using Manual User Mapping
Ping VM created on Compute from VM created on Controller.
Prerequisites:- Have OneController open in web browser.
- Have SSH Karaf command line interface session open. This is needed to get the
VTN names created by OpenStack so that you can manually map port/VLANs of Summit
440 series switches to appropriate vInterface of
VM.
admin@OC.extremenetworks.com:~$ ssh karaf@127.0.0.1 -p 8101 Password authentication Password: (karaf) opendaylight-user@root>log:tail |grep vtn
- Have an SSH session of VTN coordinator VM to input cURL commands.
- Have proper cURL commands ready (see cURL Commands)
- .
- In upper-right corner, click Create Network.
- Create the network, and then add a subnet.
- Click .
-
Create VM1:
- Use Flavor == m1.tiny and image == cirros.
- Click the Network tab, and then use the network created in step 3.
- Verify the VTN names in SSH session.
- Map vInterface of VM to VLAN/port that VM is directly connected to on the Summit X440 switch.
-
Create VM2:
- Use Flavor == m1.tiny and image == cirros.
- Click the Network tab, and then use the network created in step 3.
- Verify the VTN names in SSH session.
- Map vInterface of VM to VLAN/port that VM is directly connected to on the Summit X440 switch using the cURL commands (see cURL Commands).
- Verify that a VM resides on each server (Junoos-control-compute1.ova and Junoos-compute2).
- Open the VM console in a new browser tab.
-
After the port/VLAN/VTN mapping has occured, the VMs can obtina a DHCP address.
On each VM console execute:
sudo ifup eth0 sudo ifconfig
- Ping VM1 to VM2.
- Ping VM2 to VM1.