I've been thinking that it could be easier to adapt existing Nicira NVP Plugin than creating a new one. A possible approach could be this one:
Add a parameter to addNiciraNvpDeviceCmd, say isnsxtransformers, that could work like this: - if it is false (or null): actual nicira nvp device will be created, and will use existing API methods, basically work as it is. - if it is true (or not null): device created should call NSX-T API methods and types. For this interactions, classes and wrappers should be created, instead of creating a whole new plugin. What do you think about this approach? Do you think that this new parameter should be required or not required for addNiciraNvpDeviceCmd? Another possible approach? 2016-08-04 15:37 GMT-03:00 Nicolás Vázquez <nicovazque...@gmail.com>: > Hi Syed, > > I've been comparing NSX 4.2 and NSX-T 1.0 and the main differences I could > find are: > > - API url base, which change from /ws.v1/ to /api/v1/, API methods > also different, see attached Documentations > - There's a substantial difference in logical routers, NSX-T makes > difference between TIER-0 and TIER-1 logical routers allowing their > creation, but that's not possible in NSX 4.2, there's a unified logical > router option. > - The same happens on NAT, TIER-0 and TIER-1 depending on the type of > router in NSX-T > - Controller cluster on NSX 4.2 had role types and usually API was > exposed by them, not by NSX Manager. On NSX-T API is exposed by NSX > Management Nodes > > In my opinion it would be suitable to create a new plugin, but would like > to bring it into discussion. I also attach API documentation for NSX 4.2 > and it newest version NSX-T 1.0 for you to compare them. > NSX 4.2 API DOC: https://drive.google.com/open?id= > 0BzG1lGxO9JKpa2pmMzd3RjBIeEk > NSX-T API DOC: https://drive.google.com/open?id= > 0BzG1lGxO9JKpc2d2VWRBVHhzYjQ > > Thanks, > Nicolas > > > 2016-08-04 14:30 GMT-03:00 Syed Ahmed <sah...@cloudops.com>: > >> Hi Nicolas, >> >> It would be preferable if you integrated that in the existing plugin. If >> there are a lot of differences between NSX and NSX-T, you could create a >> new Resource within the same plugin and based on a config decide which one >> to use. Can you share more info between the differences between NSX and >> NSX-T? >> >> Thanks, >> -Syed >> >> >> On Tue, Aug 2, 2016 at 1:31 PM, Nicolás Vázquez <nicovazque...@gmail.com> >> wrote: >> >> > Hi guys, >> > >> > I would like to bring into discussion this topic. We use NSX plugin on >> > Cloudstack for network virtualization, and as NSX Transformers (NSX-T) >> was >> > released, we would like to adapt it to Cloudstack. >> > >> > What do you think it would be the best approach: create a new plugin or >> > adapt the existing plugin to support NSX-T? >> > >> > Thanks, >> > Nicolas >> > >> > >
