Federation functionality is not supported in NSX 3.2.0 release.

[kaushiklele]

Federation functionality is not supported in NSX 3.2.0 release.. So removing related modules and test scripts

[vmwclabot]

@kaushiklele, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 8222164 must be signed by [email protected]

[luischanu]

@kaushiklele, is it possible to get some further clarification on your statement that "Federation functionality is not supported in NSX 3.2.0 release"? That I'm aware of, v3.2.0 still fully supports Federation. I see the comment was from late Sept, so maybe things changed.

I am asking because I am currently using many of the Federation modules, but when I looked in the v3.2.0 branch, I didn't see any...after a little looking, I found this PR. Are there plans to put those modules back into the v3.2.0 branch?

If you can clarify, I'd greatly appreciate it.

Thank you, and I look forward to your reply.

PS> I am aware of the Federation branch, but as it's supported by v3.2.0, shouldn't all the modules be in the v3.2.0 branch?

[kcslb92]

@kaushiklele I'd like to second what @luischanu has asked. Is the functionality being reintroduced for 3.2?

Thanks!

[luischanu]

@kcslb92 FYI, NSX-T Federation is definitely supported in v3.2.0, just the importing of local sites into NSX-T Federation that was disabled in v3.2.0, so I'm wondering if that's what they were referring to. I was told the importing of NSX-T Locations into NSX-T Federation will be re-introduced in a future release, but it's unclear which release. That said, some of us currently use and configure NSX-T Federation, so it would be nice if the remaining NSX-T Federation operations (beyond NSX-T Location importing/onboarding) were included in the v3.2.0 branch.

@kaushiklele it would be very helpful if you could provide clarity to this thread and clear up (a) what was meant above regarding Federation not being supported, and (b) if/when we should expect to see the NSX-T Federation modules.

Thank you!

[kcslb92]

Hi @luischanu i should have clarified, functionality being returned to this ansible collection.

Where did you see that onboarding is disabled in 3.2.0? Does that mean that for greenfield 3.2 deployments you are unable to build and onboard new LM sites?

Cheers!

[luischanu]

@kcslb92 , I found it in two different places. The first is in the NSX-T v3.2.0 Release Notes, in the NOTE just past the Federation heading, which can be found HERE. The other is if you attempt to perform the ReST API call that on-boards a Location, if memory serves me right, it returns a note indicating that the given operation is not implemented in this version of NSX-T.

Here is the relevant portion of the Release Notes:

Federation

NOTE: While NSX releases earlier than 3.2.0 supported onboarding of existing local manager sites, this onboarding support is delayed from 3.2.0 and will be re-introduced in a later point release of 3.2.

You can still setup/create/deploy Federation, but you need to build out everything that is needed manually, from within the GM...you just can't on-board an existing LM Location. For example, one item are the edge uplinks (used for peering), as they need to be GM objects, and not LM objects.

Hope that helps...

Luis