Register VC to NSX-T using API #MIT #NSX-TAPI #OtherPlatform #Python
nsxt_create_compute_manager.py
In this class ( NSXTManagerRestAPI.java) , - It will connect to NSX-T manager - Method to get the Logical Switches information - Method to get the Cluster Configurations. Note : To use this class add " spring-web-4.0.6.RELEASE.jar , spring-core-4.0.6.RELEASE.jar and commons-logging...
NSX-T_JAVA_REST_APIs-master.zip
Register compute manager(vCenter) with NSX-T Manager. Note : To use this class add below jars in the build path libraries/dependencies. - spring-web-4.0.6.RELEASE.jar - spring-core-4.0.6.RELEASE.jar - commons-logging-1.2.jar - jackson-core-asl-1.9.2.jar - jackson-mapper-asl-1.9.2...
RegisterComputeManagerWithNSX.java
NSX-T Manager Postman Collection - This zip contains a 141k line JSON to be imported to Postman. May take >5 mins to load in Postman. #NSX-TDataCenter #MIT #NSX-TManagerAPI #POSTMANCollection #NSX-TAPI #NSX-TRESTAPI
Postman_Collection_NSX_T_Manager_API.zip
Get the List of Compute Mangers in NSX-T #OtherPlatform #MIT #NSX-TManagerAPI #Python
nsxt_get_compute_manager.py
This script will perform the following actions, Register vCenter server to NSX-T Create Transport Zone in the NSX-T #NSX-TAPI #Python #VMwareNSX-TforPython #MIT
nsxt_cm_tz_tn.py
Pre-requisites: Python 3.7 or above Requests, json, argparse, sys, requests, glob, os, xml.dom, xml.etree.Elementtree, getpass python libraries installed Connectivity to the internet from where script will be executed Connectivity to VMC SDDC over HTTPS (443) Connectivity to NSX-T Manager or VIP over HTTPS (443) Follow steps below: Step: Download script by clicking Download button on this page IF VMC: Step: Copy VMC Refresh token Login to https://console.cloud.vmware.com/ Click My Account -> API Tokens tab -> Generate Token or Regenerate an existing token Token must have NSX Cloud Admin service role under VMC on AWS service
snippet.py
Make sure to change the host and hosts value in complete-example/cafe-ingress.yml file to reflect your environment $ kubectl apply -f complete-example/cafe-ingress.yml ingress.extensions/cafe-ingress created Note that there is a annotation in the file 'kubernetes.io/ingress.class: "contour"' which is essentially being listened by Contour on the api server. When Contour sees this annotation, it does the ingress for this service
Apps-on-PKS-master.zip