Configuring external physical switch from OVS plugin

not yet. but it seems we have already talked it about. I will file a blueprint for it.

What do you want to configure on the external switch? You can just trunk all the ports on the external switch a head of time and then there is no need for quantum to do anything with the physical switch.

currently, we will use br-ex to host qg-xxx tap device created by l3 agent. we need to see how it is useful to change it into provider network.

sorry, I don't follow your response.

I thought the question is about br-ex and gq-xxx device. the external network already supports the provider network.

Thanks Yong and Aaron for your responses.
> What do you want to configure on the external switch? You can just trunk all the ports on the external switch a head of time and then there is no need for quantum to do anything with the physical switch.

Eg., Configure VLANs on Cisco Switch at the time of Quantum network creation (instead of trunking all ports ahead of time)

> not yet. but it seems we have already talked it about. I will file a blueprint for it.
I'll look for it.

Hey Krishna

The cisco plugin does support dynamic physical hardware configuration on
top of OVS but the VLAn configuration is not done at the network creation
time but rather on VM creation for selective trunking of only the VLAn's
needed for that instance. Currently only NXOS based switches are supported
by the cisco plugin.

It's all documented here:
https://wiki.openstack.org/wiki/Cisco-quantum

Please let me know if you have any other questions.

Thanks
Arvind

On 3/27/13 10:56 AM, "Krishna K" <email address hidden>
wrote:

>Question #225245 on quantum changed:
>https://answers.launchpad.net/quantum/+question/225245
>
>Krishna K posted a new comment:
>Thanks Yong and Aaron for your responses.
>> What do you want to configure on the external switch? You can just
>>trunk all the ports on the external switch a head of time and then there
>>is no need for quantum to do anything with the physical switch.
>
>Eg., Configure VLANs on Cisco Switch at the time of Quantum network
>creation (instead of trunking all ports ahead of time)
>
>> not yet. but it seems we have already talked it about. I will file a
>>blueprint for it.
>I'll look for it.
>
>--
>You received this question notification because you are a member of
>Netstack Core Developers, which is an answer contact for quantum.

Hi Arvind,

Thanks much for the info.

> on VM creation for selective trunking of only the VLAN's needed for that instance.

Trying to locate the code and flow for the above. Could you pls correct below one.

   cisco_nexus_plugin_v2.py::create_network
     - cisco_nexus_network_driver_v2.py::create_vlan // # Create vlan and trunk vlan on the port

   cisco_nexus_plugin_v2.py ::create_port(self, tenant_id, net_id, port_state, port_id, **kwargs)

        """
        This is probably not applicable to the Nexus plugin.
        Delete if not required.
        """
        LOG.debug(_("NexusPlugin:create_port() called"))

Thanks,
Krishna