For 4.3/4.4, I’m guessing this is the same solution.

For 4.5, here’s a couple of options we could implement:

  1.  New isolation provider (“BrocadeVLAN” or “JuniperEXVLAN”)
  2.  When creating the network offering, the administrator gets to select the 
guru
  3.  New VLAN provider mechanism.

From: Pradeep Cloudstack 
<pradeepcloudst...@yahoo.com<mailto:pradeepcloudst...@yahoo.com>>
Reply-To: Pradeep Cloudstack 
<pradeepcloudst...@yahoo.com<mailto:pradeepcloudst...@yahoo.com>>
Date: Wednesday, June 25, 2014 at 3:06 AM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" 
<dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>, Chiradeep Vittal 
<chiradeep.vit...@citrix.com<mailto:chiradeep.vit...@citrix.com>>
Cc: Sheng Yang <sheng.y...@citrix.com<mailto:sheng.y...@citrix.com>>, Jayapal 
Reddy Uradi 
<jayapalreddy.ur...@citrix.com<mailto:jayapalreddy.ur...@citrix.com>>, Alena 
Prokharchyk <alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>>
Subject: Re: NetworkOrchestrator selects 2 NetworkGurus at one time....

We have a use-case where we will patch an existing 4.3 installation with our 
plugin.
We are facing the same issue .
In 4.2, we used to disable the entry for ExternalNetworkGuru in
componentContext.xml as part of installing the patch.

How do we do this in 4.3 (on an existing installation) ?

-Pradeep

________________________________
From: Ritu Sabharwal <rsabh...@brocade.com<mailto:rsabh...@brocade.com>>
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" 
<dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>; Chiradeep Vittal 
<chiradeep.vit...@citrix.com<mailto:chiradeep.vit...@citrix.com>>
Cc: Sheng Yang <sheng.y...@citrix.com<mailto:sheng.y...@citrix.com>>; Jayapal 
Reddy Uradi 
<jayapalreddy.ur...@citrix.com<mailto:jayapalreddy.ur...@citrix.com>>; Alena 
Prokharchyk <alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>>
Sent: Thursday, June 12, 2014 12:13 AM
Subject: RE: NetworkOrchestrator selects 2 NetworkGurus at one time....

Thanks Chiradeep and Murali for the reply!

I am thinking of explicitly telling ExternalNetworkGuru to skip design when 
Brocade plugin is designing the network. I don't want to disable 
ExternalNetworkGuru from default build when Brocade plugin is not present so 
won't exclude it from the spring class loader.

Thanks & Regards,
Ritu S.



-----Original Message-----
From: Murali Reddy 
[mailto:murali.re...@citrix.com<mailto:murali.re...@citrix.com>]
Sent: Tuesday, June 10, 2014 10:54 PM
To: Chiradeep Vittal; 
dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Cc: Sheng Yang; Jayapal Reddy Uradi; Alena Prokharchyk
Subject: Re: NetworkOrchestrator selects 2 NetworkGurus at one time....

This is know design issue. Unlike service orchestration (which has prescriptive 
way to tell which network elements to be called for with network offerings ) 
there is no such logic for network design. Orchestrator just loops through all 
the network guru's asking to design the network which can results in one or 
more networks. Hugo did a cleanup [1] but I believe it was not merged as there 
was no consensus. There is 1-1 mapping between isolation type and Guru but In 
this case both Brocade Guru and ExternalNetworkGuru will attempt to design the 
VLAN isolated networks.

One in-elegent solution is to hard code ExternalGuestNetworu guru to skip 
network deign when Brocade plug-in is supposed to do design the network. Other 
option could be exclude ExternalNetworkGuru bean from spring class loader.

[1] https://www.mail-archive.com/dev@cloudstack.apache.org/msg17344.html

From: Chiradeep Vittal 
<chiradeep.vit...@citrix.com<mailto:chiradeep.vit...@citrix.com><mailto:chiradeep.vit...@citrix.com<mailto:chiradeep.vit...@citrix.com>>>
Date: Wednesday, 11 June 2014 6:24 AM
To: 
"dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>"
 
<dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>>
Cc: Sheng Yang 
<sheng.y...@citrix.com<mailto:sheng.y...@citrix.com><mailto:sheng.y...@citrix.com<mailto:sheng.y...@citrix.com>>>,
 Murali Reddy 
<murali.re...@citrix.com<mailto:murali.re...@citrix.com><mailto:murali.re...@citrix.com<mailto:murali.re...@citrix.com>>>,
 Jayapal Reddy Uradi 
<jayapalreddy.ur...@citrix.com<mailto:jayapalreddy.ur...@citrix.com><mailto:jayapalreddy.ur...@citrix.com<mailto:jayapalreddy.ur...@citrix.com>>>,
 Alena Prokharchyk 
<alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com><mailto:alena.prokharc...@citrix.com<mailto:alena.prokharc...@citrix.com>>>
Subject: Re: NetworkOrchestrator selects 2 NetworkGurus at one time....

That is strange. Looks like a bug to me. That is because the 
ExternalGuestNetworkGuru returns 'true' for canHandle.

From: Ritu Sabharwal 
<rsabh...@brocade.com<mailto:rsabh...@brocade.com><mailto:rsabh...@brocade.com<mailto:rsabh...@brocade.com>>>
Reply-To: 
"dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>"
 
<dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>>
Date: Tuesday, June 10, 2014 at 11:02 AM
To: 
"dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>"
 
<dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>>
Subject: NetworkOrchestrator selects 2 NetworkGurus at one time....

Hi,

I am writing a Network Guru for automatically orchestrating Brocade VDX 
switches to provide tenant isolation via VLAN. In my NetworkGuru, I have 
implemented the canHandle() method for Guest isolated network in Advanced zone 
using VLAN isolation. When the NetworkOrchestrator selects the NetworkGuru, it 
selects my NetworkGuru and the ExternalGuestNetworkGuru also and I see 2 
networks created. How do I make sure that ExternalGuestNetworkGuru is not 
selected by NetworkOrchestrator.

Thanks & Regards,
Ritu S.


Reply via email to