Versions Compared

Old Version 7

changes.mady.by.user Sangho Shin

Saved on

compared with

New Version 8

changes.mady.by.user Sangho Shin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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 port "tapxxxx" for the VM is created in the host. You can check the host of the VM in the menu of admin>system>instances.

    Code Block
    languagetext
    $ 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 of the host.

    Code Block
    languagetext
    $ sudo ovs-ofctl dump-flows br-int -O openflow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
 cookie=0x2e00004890be8f0x3300004890be8f, duration=35974.059s875s, table=0, n_packets=600, n_bytes=198900, send_flow_rem priority=40000,udp,tp_src=68,tp_dst=67 actions=CONTROLLER:65535
 cookie=0x90000fb1cfd500x3900004642a9bd, duration=208735.721s979s, 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:3goto_table:1
 cookie=0x2e0000487f4dd50x330000487f4dd5, duration=359735.056s925s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=40000,dl_type=0x88cc actions=CONTROLLER:65535
 cookie=0x2e0000487f5c1f0x330000488eb5db, duration=359735.056s926s, table=0, n_packets=0243, n_bytes=010206, send_flow_rem priority=40000,dl_type=0x8942arp actions=CONTROLLER:65535
 cookie=0x2e0000488eb5db0x3900004642a9be, duration=359735.056s980s, table=01, n_packets=660, n_bytes=27720, send_flow_rem priority=40000,arp0 actions=CONTROLLER:65535drop

    Repeat the process above to create three other VMs as 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 in only one host, then there must be some issues in the other host. Please check the logs of the compute node referring to the Trouble Shooting page in the wiki.

  4. Ping test
    Log in to the VM using by clicking the vm name in the list above and click the console tab as below.

    Log in to any VM using the console as guided in the console screen: cirros as the user name and cubswin:) as the password.
    Then, please try to ping as below to all VMs. You should be able to ping to the VM created in the same host and different VMs.
    cirros