cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolás Vázquez <nicovazque...@gmail.com>
Subject Re: Vmware NSX Transformers
Date Thu, 04 Aug 2016 18:37:48 GMT
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 <sahmed@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 <nicovazquez90@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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message