[ad_1]
Terraform Supplier VCD 3.5 launched preliminary help for VDC Teams, however protection for present assets was nonetheless lacking. We heard the demand loud and clear! This launch centered on VDC Group help throughout our present assets. This record of assets (together with information sources) help VDC Teams now:
VDC Group help for these entities introduces a brand new discipline, owner_id which deprecates vdc discipline or by inheriting entity location from guardian objects (e.g. vcd_network_routed_v2 inherits guardian VDC or VDC Group from vcd_nsxt_edgegateway)
Distributed firewall
As our assets now help VDC Teams – Distributed Firewall administration is now supported throughvcd_nsxt_distributed_firewall and an extra information supply for people who wish to reference Community Context Profiles vcd_nsxt_network_context_profile.
Extra particulars in a brand new documentation web page devoted to VDC Group help in official documentation as nicely documentation for every affected useful resource is up to date.
Metadata help in most assets
Seventeen assets with information sources obtained help for metadata.
It’s straightforward to handle metadata:
|
|
useful resource “vcd_catalog” “myNewCatalog” {   org = “my-org”    identify            = “my-catalog”   description      = “catalog for recordsdata”   delete_recursive = “true”   delete_force    = “true”     # 3.6.0 launched fields   metadata = {     license = “public”     model = “v1”   } }  |
Capacity to configure superior compute settings for VM
The vcd_vapp_vm and vcd_vm will get the flexibility of configure superior compute settings. Values are in MHz and MB.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
|
useful resource “vcd_vapp” “internet” {   identify = “internet” }  useful resource “vcd_vapp_vm” “advancedVM” {   vapp_name    = vcd_vapp.internet.identify   identify          = “webApp”   computer_name = “my webApp”   reminiscence        = 2048   cpus          = 2   cpu_cores    = 1    os_type          = “sles10_64Guest”   hardware_version = “vmx-14”   catalog_name    = “my-catalog”   boot_image      = “myMedia”    # 3.6.0 launched fields   memory_priority    = “CUSTOM”   memory_shares      = “480”   memory_reservation = “8”   memory_limit      = “48”    cpu_priority    = “CUSTOM”   cpu_shares      = “512”   cpu_reservation = “200”   cpu_limit      = “1000” }  |
Extra catalog and catalog merchandise dealing with options
- useful resource/vcd_catalog_item permits to add OVF utilizing URL utilizing propertyÂ
ovf_url - useful resource/vcd_org permits configure catalog publish settings with propertiesÂ
can_publish_external_catalogs andÂcan_subscribe_external_catalogs - useful resource/vcd_catalog permits to publish a catalog externally to make its vApp templates and media recordsdata obtainable for subscription by organizations exterior the Cloud Director set up
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
|
useful resource “vcd_org” “my-org” {   identify            = “my-org”   full_name        = “My group”   description      = “The satisfaction of my work”   is_enabled      = “true”   delete_recursive = “true”   delete_force    = “true”    # 3.6.0 launched fields   can_publish_external_catalogs  = true   can_subscribe_external_catalogs = true }   useful resource “vcd_catalog” “myNewCatalog” {   org              = vcd_org.my–org.identify   identify            = “my-catalog”   description      = “catalog for recordsdata”   delete_recursive = “true”   delete_force    = “true”    # 3.6.0 launched fields   publish_enabled              = true   cache_enabled                = true   preserve_identity_information = true   password                      = “my password” }  |
Extra info
As at all times, as a part of Terraform Supplier VCD growth, we enhance underlying Go SDK for VMware Cloud Director and a brand new model v2.15 is launched. Verify changelog for extra particulars.
[ad_2]
