Open Fry-4TF1V opened 1 month ago
@Fry-4TF1V Thanks for your issue. I have reworded it to be more generic. Let me know if you think something is missing.
In the mean time and as a work around, you can define those attributes through the openstack GUI / CLI / terraform provider. See documentation on https://help.ovhcloud.com
Hello!
It seems to copy a lot of features of the Openstack terraform provider :
https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/networking_subnet_v2 https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/networking_subnet_route_v2
I don't really see the value added if we just copy those features inside the OVH provider...
Problem statement
In order to manage some DHCP attributes from a subnet, user has to use Openstack control panel (CLI or Horizon GUI). Notably the following fields cannot be managed through OVHcloud API (and the associated interfaces Control Panel, SDK or terraform provider)
dns-nameserver
(DHCP option 6): the default is currently OVHcloud DNS resolver213.186.33.99
and can only be set through Openstackhost-route
(DHCP option 121): can only be set through OpenstackUser story
As a user, I can manage all the subnet attributes provided by Openstack in OVHcloud control panel (GUI, API/SDK & terraform) so that I do not have to use multiple interface to configure my services
Acceptance criteria
Those roles are available in OVHCloud Control Panel, in the API and in the Terraform provider cloud_project_network_private_subnet ressource.
Follow, Vote and give your Feedback
You can follow this task with the notification on the right tab. Ask us anything here in the comments below, and vote with emojis for most requested items ! 👍 to vote for this issue
Discuss on Discord
Feel free to discuss with us on https://discord.gg/ovhcloud => "Network-Public Cloud" channels
------------ Original issue -------------- As an OVHcloud customer using any Public Cloud Database, I want this database to be reachable from different subnets/instances inside my project (and not only inside the same subnet) via routers (OVHcloud routers or third-party deployed).
For now, I need to attach an additional port to any instance that need to access my database.