Skip to content
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

add azurerm_proximity_placement_group resource #4127

Closed
andrey-dubnik opened this issue Aug 21, 2019 · 3 comments · Fixed by #4020
Closed

add azurerm_proximity_placement_group resource #4127

andrey-dubnik opened this issue Aug 21, 2019 · 3 comments · Fixed by #4020

Comments

@andrey-dubnik
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Azure introduced a new feature - Proximity Placement Group which allows placing VMs in the close network proximity from one another.

New or Affected Resource(s)

  • azurerm_proximity_placement_group

  • azurerm_virtual_machine

Potential Terraform Configuration

resource "azurerm_proximity_placement_group" "ppg" {
  name                = "myppg"
  location            = "${azurerm_resource_group.test.location}"
  resource_group_name = "${azurerm_resource_group.test.name}"

  tags = {
    Hello = "World"
  }
}

resource "azurerm_virtual_machine" "main" {
 
# PPG ID is optional parameter, forces the new resource
  proximity_placement_group_id = "${azurerm_proximity_placement_group.ppg.id}"

 # Standard VM sample from the TF docs
  name                  = "${var.prefix}-vm"
  location              = "${azurerm_resource_group.main.location}"
  resource_group_name   = "${azurerm_resource_group.main.name}"
  network_interface_ids = ["${azurerm_network_interface.main.id}"]
  vm_size               = "Standard_DS1_v2"

  # Uncomment this line to delete the OS disk automatically when deleting the VM
  # delete_os_disk_on_termination = true


  # Uncomment this line to delete the data disks automatically when deleting the VM
  # delete_data_disks_on_termination = true

  storage_image_reference {
    publisher = "Canonical"
    offer     = "UbuntuServer"
    sku       = "16.04-LTS"
    version   = "latest"
  }
  storage_os_disk {
    name              = "myosdisk1"
    caching           = "ReadWrite"
    create_option     = "FromImage"
    managed_disk_type = "Standard_LRS"
  }
  os_profile {
    computer_name  = "hostname"
    admin_username = "testadmin"
    admin_password = "Password1234!"
  }
  os_profile_linux_config {
    disable_password_authentication = false
  }
  tags = {
    environment = "staging"
  }
}

References

https://docs.microsoft.com/en-ie/azure/virtual-machines/linux/proximity-placement-groups

@andrey-dubnik andrey-dubnik changed the title add proximity_placement group resource add proximity_placement_group resource Aug 21, 2019
@andrey-dubnik andrey-dubnik changed the title add proximity_placement_group resource add azurerm_proximity_placement_group resource Aug 21, 2019
@nexxai
Copy link
Contributor

nexxai commented Aug 22, 2019

This is being worked on here

@ghost
Copy link

ghost commented Sep 18, 2019

This has been released in version 1.34.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.34.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Oct 5, 2019

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Oct 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants