Op 29/10/2024 om 10:17 schreef Wido den Hollander:
Hello,
I got my inspiration for this proposal from the recently added object
storage [0] plugin in CloudStack.
I added an issue for this on Github to track the feature:
https://github.com/apache/cloudstack/issues/9958
Wido
My idea i
Op 29/10/2024 om 10:17 schreef Wido den Hollander:
Hello,
I got my inspiration for this proposal from the recently added object
storage [0] plugin in CloudStack.
I added an issue for this on Github to track the feature:
https://github.com/apache/cloudstack/issues/9958
Wido
My idea i
d back then and I'd love to see that implemented in ACS
-Original Message-
From: Wido den Hollander
Sent: 30 October 2024 10:36
To: dev@cloudstack.apache.org; Ruben Bosch
Subject: Re: [PROPOSAL] DNS provider framework in CloudStack
Op 30/10/2024 om 09:40 schreef Ruben Bosch
Op 30/10/2024 om 09:40 schreef Ruben Bosch:
Great suggestion Wido. One suggestion I would have is to include PTR
(reverse DNS) in here also, and make the PTR equal to the
vm_instance.display_name
Ah, yes, good suggestion! Per CloudStack zone you would set 3 DNS zones:
- Zone to create A an
Great suggestion Wido. One suggestion I would have is to include PTR
(reverse DNS) in here also, and make the PTR equal to the
vm_instance.display_name
Kind regards,
Ruben Bosch
On Tue, Oct 29, 2024 at 10:18 AM Wido den Hollander
wrote:
> Hello,
>
> I got my inspiration for this proposal from
understood, again, great idea
On Tue, Oct 29, 2024 at 11:50 AM Wido den Hollander wrote:
>
>
> Op 29/10/2024 om 11:11 schreef Daan Hoogland:
> > sounds good @Wido den Hollander ,
> >
> > several questions come to mind (most of them in the realm of 'details':
> > credentials; can these be operat
Op 29/10/2024 om 11:11 schreef Daan Hoogland:
sounds good @Wido den Hollander ,
several questions come to mind (most of them in the realm of 'details':
credentials; can these be operator property or must these be user property
(bring your own)? (or can we configure both setups)
My idea is
sounds good @Wido den Hollander ,
several questions come to mind (most of them in the realm of 'details':
credentials; can these be operator property or must these be user property
(bring your own)? (or can we configure both setups)
ttl; is there a maximum configurable as well?
record types; do w
Hello,
I got my inspiration for this proposal from the recently added object
storage [0] plugin in CloudStack.
My idea is as follows:
- A new framework is addedd: Authorative DNS
- This allows for admins and end-users to manage DNS zones
- Different providers implement different APIs, example
