cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjeev N (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-6798) [OVS] Network update from OVS to vlan does not implement the network properly
Date Wed, 28 May 2014 11:52:01 GMT
Sanjeev N created CLOUDSTACK-6798:
-------------------------------------

             Summary: [OVS] Network update from OVS to vlan does not implement the network
properly
                 Key: CLOUDSTACK-6798
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6798
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server, Network Controller
    Affects Versions: 4.4.0
         Environment: Latest build from 4.4 with commit d130530bd3e1cd6d8249d5045e00e4e4e2201521
            Reporter: Sanjeev N
            Assignee: Murali Reddy
            Priority: Critical
             Fix For: 4.4.0


[OVS] Network update from OVS to vlan does not implement the network properly

Steps to Reproduce:
==============
1.Bring up CS in advanced zone with Xen cluster
2.Create physical network with GRE isolation
3.Create network offering with virtualnetworking and OVS as the connectivity service provider
4.Create one guest network with above offering
5.Deploy few vms in the above network 
6.Stop all the vms and update network  to default isolated network offering "Offering for
Isolated networks with Source Nat service" 
7.Deploy one vm in the network after network update

Result:
======
1.Network update was successful but the network is not implemented propertly. Network did
not get any vlan ID. Broadcast uri for the network still remains as vs://985 instead of vlan://985.
2.So the guest vms would not get any ip addresses.
3.Network is of no use. On Xenserver cluster CS is not creating network with VLAN 985. Deploying
new vms or starting the existing vms are plugging vifs to the existing tunnel bridge but tunnel
ports not not getting created between the hosts since the offering does not have the OVS provider.

Following are the network details from db after network update:

mysql> select * from networks where id=207\G;
*************************** 1. row ***************************
                   id: 207
                 name: Admin-ovs
                 uuid: c545e326-218d-49ba-8fb8-4dabd9ab612f
         display_text: Admin-ovs
         traffic_type: Guest
broadcast_domain_type: Vswitch
        broadcast_uri: vs://985
              gateway: 10.1.1.1
                 cidr: 10.1.1.0/24
                 mode: Dhcp
  network_offering_id: 8
  physical_network_id: 200
       data_center_id: 1
            guru_name: OvsGuestNetworkGuru
                state: Implemented
              related: 207
            domain_id: 1
           account_id: 2
                 dns1: NULL
                 dns2: NULL
            guru_data: NULL
           set_fields: 0
             acl_type: Account
       network_domain: cs2cloud.internal
       reservation_id: 8b9fa583-35a7-4b43-a023-08efc44b88ee
           guest_type: Isolated
     restart_required: 0
              created: 2014-05-27 09:42:15
              removed: NULL
    specify_ip_ranges: 0
               vpc_id: NULL
          ip6_gateway: NULL
             ip6_cidr: NULL
         network_cidr: NULL
      display_network: 1
       network_acl_id: NULL
          streched_l2: 0
1 row in set (0.00 sec)
mysql> select * from network_offerings where id=8\G;
*************************** 1. row ***************************
                       id: 8
                     name: DefaultIsolatedNetworkOfferingWithSourceNatService
                     uuid: d82a97f9-366a-491b-9f18-ef96aac732bc
              unique_name: DefaultIsolatedNetworkOfferingWithSourceNatService
             display_text: Offering for Isolated networks with Source Nat service enabled
                  nw_rate: NULL
                  mc_rate: NULL
             traffic_type: Guest
                     tags: NULL
              system_only: 0
             specify_vlan: 0
      service_offering_id: NULL
            conserve_mode: 1
                  created: 2014-05-26 11:21:39
                  removed: NULL
                  default: 1
             availability: Required
     dedicated_lb_service: 1
shared_source_nat_service: 0
                 sort_key: 0
 redundant_router_service: 0
                    state: Enabled
               guest_type: Isolated
       elastic_ip_service: 0
  eip_associate_public_ip: 1
       elastic_lb_service: 0
        specify_ip_ranges: 0
                   inline: 0
            is_persistent: 0
              internal_lb: 0
                public_lb: 1
    egress_default_policy: 0
   concurrent_connections: NULL
       keep_alive_enabled: 0
     supports_streched_l2: 0
1 row in set (0.00 sec)


Please look for job-133 in the attached MS log file for the sequence of events happened during
update network.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message