You would make changes in the components.xml to make your NetworkGuru the default.
As I described to Salvatore in another email, the best way is to add an isolation method parameter to physical network. This isolation method will drive the selection of the NetworkGuru for the guest network. Right now, we assume the isolation method is always VLAN. But it would be best to add to the guest traffic type, the isolation method used at the physical network level. Then, NetworkManager chooses the NetworkGuru depending on the physical isolation used. --Alex > -----Original Message----- > From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com] > Sent: Monday, June 04, 2012 11:09 AM > To: 'cloudstack-dev@incubator.apache.org' > Subject: SDN integration with CloudStack > > Heya All, > > This week we will be working from the Nicira office on integrating SDN with > CloudStack. In the recent discussion thread "making VM startup more fine- > grained" one of our questions is already addressed. > > Another more basic question is how do we get our NetworkGuru to be > used/selected by CloudStack when we build a new network. Basically what > we want to do is when a guest network is created it should call our > NetworkGuru to create the logical switch in the SDN and when a VM is > started it should plug the NIC into an lport. The code to get this done is > looking straight forward (except for the vif uuid discussion mentioned > earlier). What has me baffled is the way to "plug" the new guru into > CloudStack, how do we do this? > > I was looking at code commited by Salvatore as the OVS GRE implementation > looks similar to what I intend to do. It appears he is in the process of > adding a > Service "Connectivity", is this the way to do it? > > In the end I want to be able to create one or two networkofferings for the > SDN integration, so my Guru gets called when a new network is created. How > do I do this? > > Cheers, > > Hugo
