Simple workthrough

We describe how to create network, VMs and show the VMs can communicate through network configured by OpenstackSwitching. We do describe the detail of how to use Openstack. If you are not familiar with Openstack, we recommend to walk through tutorials in Openstack community sites. We use horizon UI interface to simplify the steps.

1. Login to the horizon interface using the ID and password. If you followed the steps described in the ONOS wiki pages, ID is admin and password is nova.
   
2. Create a network by clicking the Create Network button of admin > Network > Networks menu
   
   
   
   

3. Create four VMs using the network net1 just created above : Compute > Instances > Launch Instance
   
   
   
   When a VM is created successfully, you can see that a new bridge called br-int and a port for the VM are created.

   ~/devstack$ sudo ovs-vsctl show
   1265d109-8a0a-40d5-bfee-f8ee9c7438c1
       Manager "ptcp:6640"
       Bridge br-int
           Controller "tcp:10.40.101.152:6653"
               is_connected: true
           fail_mode: secure
           Port vxlan
               Interface vxlan
                   type: vxlan
                   options: {key=flow, remote_ip=flow}
           Port br-int
               Interface br-int
           Port "tap8ee7ff66-af"
               Interface "tap8ee7ff66-af"

   You can also check that forwarding flow rules for the VM are added in the bridge.

   ~/devstack$ sudo ovs-ofctl dump-flows br-int -O openflow13
   OFPST_FLOW reply (OF1.3) (xid=0x2):
    cookie=0x2e00004890be8f, duration=3597.059s, table=0, n_packets=60, n_bytes=19890, send_flow_rem priority=40000,udp,tp_src=68,tp_dst=67 actions=CONTROLLER:65535
    cookie=0x90000fb1cfd50, duration=2087.721s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=50000,ip,nw_dst=10.1.0.7 actions=output:2
    cookie=0x230000d3b8195c, duration=2077.477s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=5000,tun_id=0x433,in_port=1,dl_dst=fa:16:3e:5c:d4:8d actions=output:3
    cookie=0x2e0000487f4dd5, duration=3597.056s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=40000,dl_type=0x88cc actions=CONTROLLER:65535
    cookie=0x2e0000487f5c1f, duration=3597.056s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=40000,dl_type=0x8942 actions=CONTROLLER:65535
    cookie=0x2e0000488eb5db, duration=3597.056s, table=0, n_packets=66, n_bytes=2772, send_flow_rem priority=40000,arp actions=CONTROLLER:65535

   Repeat the process above to create another three VMs as below. IP addresses of the VMs might be different from the example below.
   

   From the Admin>System>Instances menu, you can see the location of the VMs. You can see that VMs have been created alternatively. If your VMs are created only one host, then there must be some issues in the host. Please check the logs of the compute node referring the Trouble Shooting page in the wiki.