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 cr
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 be
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 N
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
