[
https://issues.apache.org/jira/browse/CLOUDSTACK-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735625#comment-13735625
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2535:
-----------------------------------------------------------------
Cleaning up port profiles isn't a high priority in cloud orchestration. Infact
keeping them around is probably time saving during orchestration. Having port
profiles on a vSwitch or a VEM or VSS doesn't consume resources - it's only
when a vNIC is associated with a port profile that ports are used up on the
switching modules.
I don't think this is a critical issue, even if we were to clean up the
profiles.
> Cleanup port-profiles that gets created on Nexus switch as part of network
> cleanup
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2535
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2535
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
> Affects Versions: pre-4.0.0, 4.0.0
> Environment: Vmware
> Reporter: Koushik Das
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
>
> Port profiles are not cleaned up when a guest network using it gets removed.
> As part of network shutdown all port profiles that got created on the Nexus
> switch should be removed.
> The same problem is also there for vSwitch and dvSwitch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
