-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy an NSX Edge Cluster #111
Comments
Hi @cybernils we're actually in the middle of developing the feature. CC: @stoyanzhelyazkov |
That is awesome! Do you have an ETA for when we can expect it to be released? Thanks. |
I'd say 2-4 weeks, depending on a lot of factors... |
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Adds a new resource for NSX Edge Clusters. The lifecycle of the resource is based on the public API and supports creation, expansion, and shrinkage. Formatted all .tf files with `terraform fmt -recursive`. Ref: #111 Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]> Signed-off-by: Stoyan Zhelyazkov <[email protected]>
Hi @cybernils, Support for NSX Edge clusters has been released with the latest v0.8.0 version. Best Regards, |
I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Code of Conduct
Description
Please add "Deploy an NSX Edge Cluster" feature.
Use Case(s)
Deploy an NSX Edge Cluster.
Potential Configuration
{
"asn": 65003,
"edgeAdminPassword": "VMware123!VMware123!",
"edgeAuditPassword": "VMware123!VMware123!",
"edgeRootPassword": "VMware123!VMware123!",
"mtu": 8940,
"tier0Name": "VLC-Tier-0",
"tier0RoutingType": "EBGP",
"tier0ServicesHighAvailability": "ACTIVE_ACTIVE",
"tier1Name": "VLC-Tier-1",
"edgeClusterName": "EC-01",
"edgeClusterProfileType": "DEFAULT",
"edgeClusterType": "NSX-T",
"edgeFormFactor": "LARGE",
"edgeNodeSpecs": [ {
"clusterId": "",
"edgeNodeName": "edge1-mgmt.vcf.sddc.lab",
"edgeTep1IP": "172.27.13.2/24",
"edgeTep2IP": "172.27.13.3/24",
"edgeTepGateway": "172.27.13.1",
"edgeTepVlan": 13,
"interRackCluster": false,
"managementGateway": "10.0.0.221",
"managementIP": "10.0.0.23/24",
"uplinkNetwork": [ {
"asnPeer": 65001,
"bgpPeerPassword": "VMware123!",
"peerIP": "172.27.11.1/24",
"uplinkInterfaceIP": "172.27.11.2/24",
"uplinkVlan": 11
},{
"asnPeer": 65001,
"bgpPeerPassword": "VMware123!",
"peerIP": "172.27.12.1/24",
"uplinkInterfaceIP": "172.27.12.2/24",
"uplinkVlan": 12
} ]
},{
"clusterId": "",
"edgeNodeName": "edge2-mgmt.vcf.sddc.lab",
"edgeTep1IP": "172.27.13.4/24",
"edgeTep2IP": "172.27.13.5/24",
"edgeTepGateway": "172.27.13.1",
"edgeTepVlan": 13,
"interRackCluster": false,
"managementGateway": "10.0.0.221",
"managementIP": "10.0.0.24/24",
"uplinkNetwork": [ {
"asnPeer": 65001,
"bgpPeerPassword": "VMware123!",
"peerIP": "172.27.11.1/24",
"uplinkInterfaceIP": "172.27.11.3/24",
"uplinkVlan": 11
},{
"asnPeer": 65001,
"bgpPeerPassword": "VMware123!",
"peerIP": "172.27.12.1/24",
"uplinkInterfaceIP": "172.27.12.3/24",
"uplinkVlan": 12
} ]
} ]
}
References
https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/com.vmware.vcf.vxrail.doc/GUID-D17D0274-7764-43BD-8252-D9333CA7415A.html
The text was updated successfully, but these errors were encountered: