Implementation of DNS Provider for Bind
Hi there, I work at Globo.com, a media company in Brazil. Here we use a cloudstack private network with an advanced zone setup (isolated vlans). For some couple of reasons, the name of virtual machine needs to be available not only on virtual router network context, but on our internal DNS servers. Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) thru an open source API written by globo.com called DNSAPI. More info at https://github.com/globocom/Dns-Api. To make this implementation of DNS provider, we based our plugin on "dns-notifier", but we had to add more classes for our implementation. * DnsAPINetworkDAO to manage the networkDomain for each network. * DnsAPIVirtualMachineDAO to manage DNS records for vms. * DnsAPIElement, this class implements the provider itself. * DnsAPIResource, implements all communications with DNSAPI (ServerResource). Besides this classes, another one was necessary to the call to DnsAPIResource and return the answer, and one API command was created to configure the provider in Zone. Above a video that show you how everything was integrated. https://www.youtube.com/watch?v=fAB53T_NZMI We really appreciate all your comments about our implementation, thanks in advance
Re: Implementation of DNS Provider for Bind
On Fri, Jun 13, 2014 at 7:08 AM, Silvano Buback wrote: > Hi there, > > I work at Globo.com, a media company in Brazil. Here we use a cloudstack > private network with an advanced zone setup (isolated vlans). > > For some couple of reasons, the name of virtual machine needs to be > available not only on virtual router network context, but on our internal > DNS servers. > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) > thru an open source API written by globo.com called DNSAPI. More info at > https://github.com/globocom/Dns-Api. > > To make this implementation of DNS provider, we based our plugin on > "dns-notifier", but we had to add more classes for our implementation. > > * DnsAPINetworkDAO to manage the networkDomain for each network. > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > > * DnsAPIElement, this class implements the provider itself. > > * DnsAPIResource, implements all communications with DNSAPI > (ServerResource). > > Besides this classes, another one was necessary to the call to > DnsAPIResource and return the answer, and one API command was created to > configure the provider in Zone. > > > Above a video that show you how everything was integrated. > > > https://www.youtube.com/watch?v=fAB53T_NZMI > > I like it, and it seems to be rather straight forward to add other DNS providers as well, if they are based on your DNS API. -- Erik Weber
[DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi there, I work at Globo.com, a media company in Brazil. Here we use a cloudstack private network with an advanced zone setup (isolated vlans). For some couple of reasons, the name of virtual machine needs to be available not only on virtual router network context, but on our internal DNS servers. Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) thru an open source API written by globo.com called DNSAPI. More info at https://github.com/globocom/Dns-Api. To make this implementation of DNS provider, we based our plugin on "dns-notifier", but we had to add more classes for our implementation. * DnsAPINetworkDAO to manage the networkDomain for each network. * DnsAPIVirtualMachineDAO to manage DNS records for vms. * DnsAPIElement, this class implements the provider itself. * DnsAPIResource, implements all communications with DNSAPI (ServerResource). Besides this classes, another one was necessary to the call to DnsAPIResource and return the answer, and one API command was created to configure the provider in Zone. Above a video that show you how everything was integrated. https://www.youtube.com/watch?v=fAB53T_NZMI We really appreciate all your comments about our implementation, thanks in advance PS: Sorry about duplicated e-mail in mailing list, but I forget to use DISCUSS and send using company e-mail)
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi Silvano, I really liked what you did. I'm curious if this DNS provider will work with non-isolated/shared advanced network zones as well. Otherwise, great approach to solving the last DNS puzzle. I now wonder how easy it would be to add other DNS Providers support into CloudStack besides Bind. Can you share the changes you've made to your cloudstack env to support DNSApis? Also noticed DBaaS-CloudStack in github, sounds interesting, what is it based on? If you can, please kindly explain. Regards ilya On 6/12/14, 10:21 PM, Silvano Nogueira Buback wrote: Hi there, I work at Globo.com, a media company in Brazil. Here we use a cloudstack private network with an advanced zone setup (isolated vlans). For some couple of reasons, the name of virtual machine needs to be available not only on virtual router network context, but on our internal DNS servers. Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) thru an open source API written by globo.com called DNSAPI. More info at https://github.com/globocom/Dns-Api. To make this implementation of DNS provider, we based our plugin on "dns-notifier", but we had to add more classes for our implementation. * DnsAPINetworkDAO to manage the networkDomain for each network. * DnsAPIVirtualMachineDAO to manage DNS records for vms. * DnsAPIElement, this class implements the provider itself. * DnsAPIResource, implements all communications with DNSAPI (ServerResource). Besides this classes, another one was necessary to the call to DnsAPIResource and return the answer, and one API command was created to configure the provider in Zone. Above a video that show you how everything was integrated. https://www.youtube.com/watch?v=fAB53T_NZMI We really appreciate all your comments about our implementation, thanks in advance PS: Sorry about duplicated e-mail in mailing list, but I forget to use DISCUSS and send using company e-mail)
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
On Fri, Jun 13, 2014 at 7:21 AM, Silvano Nogueira Buback < silv...@corp.globo.com> wrote: > Hi there, > > > I work at Globo.com, a media company in Brazil. Here we use a cloudstack > private network with an advanced zone setup (isolated vlans). > > For some couple of reasons, the name of virtual machine needs to be > available not only on virtual router network context, but on our internal > DNS servers. > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) > thru an open source API written by globo.com called DNSAPI. More info at > https://github.com/globocom/Dns-Api. > > To make this implementation of DNS provider, we based our plugin on > "dns-notifier", but we had to add more classes for our implementation. > > * DnsAPINetworkDAO to manage the networkDomain for each network. > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > * DnsAPIElement, this class implements the provider itself. > * DnsAPIResource, implements all communications with DNSAPI > (ServerResource). > > Besides this classes, another one was necessary to the call to > DnsAPIResource and return the answer, and one API command was created to > configure the provider in Zone. > > Above a video that show you how everything was integrated. > > https://www.youtube.com/watch?v=fAB53T_NZMI > > We really appreciate all your comments about our implementation, > replying in the right thread this time :-) I like the idea and the fact that the backend is available as open source. That should make it pretty straight forward to convert it to other DNS solutions (PowerDNS for me). - What happens if there is a conflict? - Does it require / assume that the domain is non-existant on the DNS servers? - How does cleanup handle additional records added outside of CloudStack? -- Erik Weber
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi Silvano, On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < silv...@corp.globo.com> wrote: > Hi there, > > > I work at Globo.com, a media company in Brazil. Here we use a cloudstack > private network with an advanced zone setup (isolated vlans). > > For some couple of reasons, the name of virtual machine needs to be > available not only on virtual router network context, but on our internal > DNS servers. > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) > thru an open source API written by globo.com called DNSAPI. More info at > https://github.com/globocom/Dns-Api. > Thanks for the proposal. I recommend that you document your design goals in 4.5 or above design docs wiki: https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents I saw the video you shared, it looked seamless but I could not figure out how the ACS plugin interacts with the DNS provider. The API library you mentioned is written in Ruby, so how does it integrate or work with the dns plugin in ACS, is it over HTTP or RPC/Thrift? Regards. > > To make this implementation of DNS provider, we based our plugin on > "dns-notifier", but we had to add more classes for our implementation. > > * DnsAPINetworkDAO to manage the networkDomain for each network. > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > * DnsAPIElement, this class implements the provider itself. > * DnsAPIResource, implements all communications with DNSAPI > (ServerResource). > > Besides this classes, another one was necessary to the call to > DnsAPIResource and return the answer, and one API command was created to > configure the provider in Zone. > > Above a video that show you how everything was integrated. > > https://www.youtube.com/watch?v=fAB53T_NZMI > > We really appreciate all your comments about our implementation, > > thanks in advance > PS: Sorry about duplicated e-mail in mailing list, but I forget to use > DISCUSS and send using company e-mail) >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
It looks like the DnsProvider calls the REST API of the RoR-based DNSAPI. +1, but as Rohit said, I’d love to see the design details on the Wiki. This will make it easier for folks like Erik to integrate PowerDns. Does the VR use the Bind server for name resolution? That is, is the Bind server the same as the zone DNS? Is this configured on a region level or a zone level? Or is it strictly per network offering? From: Rohit Yadav mailto:bhais...@apache.org>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org>> Date: Friday, June 13, 2014 at 6:53 AM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org>> Subject: Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5) Hi Silvano, On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < silv...@corp.globo.com<mailto:silv...@corp.globo.com>> wrote: Hi there, I work at Globo.com, a media company in Brazil. Here we use a cloudstack private network with an advanced zone setup (isolated vlans). For some couple of reasons, the name of virtual machine needs to be available not only on virtual router network context, but on our internal DNS servers. Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) thru an open source API written by globo.com called DNSAPI. More info at https://github.com/globocom/Dns-Api. Thanks for the proposal. I recommend that you document your design goals in 4.5 or above design docs wiki: https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents I saw the video you shared, it looked seamless but I could not figure out how the ACS plugin interacts with the DNS provider. The API library you mentioned is written in Ruby, so how does it integrate or work with the dns plugin in ACS, is it over HTTP or RPC/Thrift? Regards. To make this implementation of DNS provider, we based our plugin on "dns-notifier", but we had to add more classes for our implementation. * DnsAPINetworkDAO to manage the networkDomain for each network. * DnsAPIVirtualMachineDAO to manage DNS records for vms. * DnsAPIElement, this class implements the provider itself. * DnsAPIResource, implements all communications with DNSAPI (ServerResource). Besides this classes, another one was necessary to the call to DnsAPIResource and return the answer, and one API command was created to configure the provider in Zone. Above a video that show you how everything was integrated. https://www.youtube.com/watch?v=fAB53T_NZMI We really appreciate all your comments about our implementation, thanks in advance PS: Sorry about duplicated e-mail in mailing list, but I forget to use DISCUSS and send using company e-mail)
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi Ilya, I put the plugin code in https://github.com/globocom/cloudstack/tree/4.3.0-globo/plugins/network-elements/dns-api. We use it with Shared/Advanced network zones. But in order to communicate with other networks (bind server network, for example), it is necessary to define and implement an ACL. In Globo.com this is made automatically by our NetworkAPI that has common ACLs to new networks that allow all virtual machines to access DNSAPI on port 53. The IP of bind managed by DNSAPI is the same of internal DNS configured in the zone. DNSAPI works without NetworkAPI as well, you just have to configure ACLs manually. I will prepare the Design Document, which will explain all changes made and send it to this mailing list. We are working to improve DNS-API Documentation too. You can check it out now, but we're still working on it: https://github.com/globocom/Dns-Api. We intend to make NetworkAPI code open source too to manage shared networks. Using NetworkAPI, shared network are created by regular users, because this api are responsible to choose ip address and vlan number, and to create network in different equipment too. I want to talk about this in another thread, when I submit the code of NetworkAPI to community. Inside Globo we are working in our own tool of Database as a Service ( https://github.com/globocom/database-as-a-service). The module you saw at github is responsible to provision new VMs using Cloudstack. We are developing an connector to Cloud Portal Business Manager too. If you want more information about DBaaS, you can send an e-mail to db...@corp.globo.com. People there can explain detail about the implementation / feature and plans. I'm in that list too. Regards, Silvano Buback Globo.com Infra-structure Expert On Fri, Jun 13, 2014 at 3:24 AM, ilya musayev wrote: > Hi Silvano, > > I really liked what you did. > > I'm curious if this DNS provider will work with non-isolated/shared > advanced network zones as well. > Otherwise, great approach to solving the last DNS puzzle. I now wonder how > easy it would be to add other DNS Providers support into CloudStack besides > Bind. > > Can you share the changes you've made to your cloudstack env to support > DNSApis? > > Also noticed DBaaS-CloudStack in github, sounds interesting, what is it > based on? If you can, please kindly explain. > > Regards > ilya > > On 6/12/14, 10:21 PM, Silvano Nogueira Buback wrote: > >> Hi there, >> >> >> I work at Globo.com, a media company in Brazil. Here we use a cloudstack >> private network with an advanced zone setup (isolated vlans). >> >> For some couple of reasons, the name of virtual machine needs to be >> available not only on virtual router network context, but on our internal >> DNS servers. >> >> Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) >> thru an open source API written by globo.com called DNSAPI. More info at >> https://github.com/globocom/Dns-Api. >> >> To make this implementation of DNS provider, we based our plugin on >> "dns-notifier", but we had to add more classes for our implementation. >> >> * DnsAPINetworkDAO to manage the networkDomain for each network. >> * DnsAPIVirtualMachineDAO to manage DNS records for vms. >> * DnsAPIElement, this class implements the provider itself. >> * DnsAPIResource, implements all communications with DNSAPI >> (ServerResource). >> >> Besides this classes, another one was necessary to the call to >> DnsAPIResource and return the answer, and one API command was created to >> configure the provider in Zone. >> >> Above a video that show you how everything was integrated. >> >> https://www.youtube.com/watch?v=fAB53T_NZMI >> >> We really appreciate all your comments about our implementation, >> >> thanks in advance >> PS: Sorry about duplicated e-mail in mailing list, but I forget to use >> DISCUSS and send using company e-mail) >> >> >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi Erik, At Globo, network domain always have exclusive names, based on zone name and vlan number, so there is no conflict. At the point of view of plugin, if domain exists it will be used. If a record exists, it will be overwritten. When you delete a network, dns domain will be deleted too, doesn't matter if it exists before network creation or not. Records in this domain will be removed too. []'s, Silvano Buback On Fri, Jun 13, 2014 at 3:52 AM, Erik Weber wrote: > On Fri, Jun 13, 2014 at 7:21 AM, Silvano Nogueira Buback < > silv...@corp.globo.com> wrote: > > > Hi there, > > > > > > I work at Globo.com, a media company in Brazil. Here we use a cloudstack > > private network with an advanced zone setup (isolated vlans). > > > > For some couple of reasons, the name of virtual machine needs to be > > available not only on virtual router network context, but on our internal > > DNS servers. > > > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind > server) > > thru an open source API written by globo.com called DNSAPI. More info at > > https://github.com/globocom/Dns-Api. > > > > To make this implementation of DNS provider, we based our plugin on > > "dns-notifier", but we had to add more classes for our implementation. > > > > * DnsAPINetworkDAO to manage the networkDomain for each network. > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > > * DnsAPIElement, this class implements the provider itself. > > * DnsAPIResource, implements all communications with DNSAPI > > (ServerResource). > > > > Besides this classes, another one was necessary to the call to > > DnsAPIResource and return the answer, and one API command was created to > > configure the provider in Zone. > > > > Above a video that show you how everything was integrated. > > > > https://www.youtube.com/watch?v=fAB53T_NZMI > > > > We really appreciate all your comments about our implementation, > > > > > replying in the right thread this time :-) > > I like the idea and the fact that the backend is available as open source. > That should make it pretty straight forward to convert it to other DNS > solutions (PowerDNS for me). > > - What happens if there is a conflict? > - Does it require / assume that the domain is non-existant on the DNS > servers? > - How does cleanup handle additional records added outside of CloudStack? > > -- > Erik Weber >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi Rohit, I started the documentation and I think on next wednesday I'm with the first version ready for community feedback. I will put the details of how plugin work with DNSAPI and how DNSAPI work with bind. I don't have permission to create new pages on wiki. I submit the documentation to here or someone will give me access to update wiki? []'s, Silvano Buback On Fri, Jun 13, 2014 at 7:53 AM, Rohit Yadav wrote: > Hi Silvano, > > On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < > silv...@corp.globo.com> wrote: > > > Hi there, > > > > > > I work at Globo.com, a media company in Brazil. Here we use a cloudstack > > private network with an advanced zone setup (isolated vlans). > > > > For some couple of reasons, the name of virtual machine needs to be > > available not only on virtual router network context, but on our internal > > DNS servers. > > > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind > server) > > thru an open source API written by globo.com called DNSAPI. More info at > > https://github.com/globocom/Dns-Api. > > > > Thanks for the proposal. > > I recommend that you document your design goals in 4.5 or above design docs > wiki: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents > > I saw the video you shared, it looked seamless but I could not figure out > how the ACS plugin interacts with the DNS provider. The API library you > mentioned is written in Ruby, so how does it integrate or work with the dns > plugin in ACS, is it over HTTP or RPC/Thrift? > > Regards. > > > > > > To make this implementation of DNS provider, we based our plugin on > > "dns-notifier", but we had to add more classes for our implementation. > > > > * DnsAPINetworkDAO to manage the networkDomain for each network. > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > > * DnsAPIElement, this class implements the provider itself. > > * DnsAPIResource, implements all communications with DNSAPI > > (ServerResource). > > > > Besides this classes, another one was necessary to the call to > > DnsAPIResource and return the answer, and one API command was created to > > configure the provider in Zone. > > > > Above a video that show you how everything was integrated. > > > > https://www.youtube.com/watch?v=fAB53T_NZMI > > > > We really appreciate all your comments about our implementation, > > > > thanks in advance > > PS: Sorry about duplicated e-mail in mailing list, but I forget to use > > DISCUSS and send using company e-mail) > > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi Chiradeep, Bind server is configured per zone. We did not test with PowerDNS, but I think they are able to talk because API is the same. We are configuring bind server managed by "DNSAPI" as internal DNS in zone. So VR doesn't provide more name resolution for network. I will put the details in documentation. Regards, Silvano Buback Globo.com Infra-structure Expert On Mon, Jun 16, 2014 at 2:50 AM, Chiradeep Vittal < chiradeep.vit...@citrix.com> wrote: > It looks like the DnsProvider calls the REST API of the RoR-based DNSAPI. > > +1, but as Rohit said, I’d love to see the design details on the Wiki. > This will make it easier for folks like Erik to integrate PowerDns. > Does the VR use the Bind server for name resolution? That is, is the Bind > server the same as the zone DNS? Is this configured on a region level or a > zone level? Or is it strictly per network offering? > > From: Rohit Yadav mailto:bhais...@apache.org>> > Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> > Date: Friday, June 13, 2014 at 6:53 AM > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> > Subject: Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind > (for 4.5) > > Hi Silvano, > > On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < > silv...@corp.globo.com<mailto:silv...@corp.globo.com>> wrote: > > Hi there, > > > I work at Globo.com, a media company in Brazil. Here we use a cloudstack > private network with an advanced zone setup (isolated vlans). > > For some couple of reasons, the name of virtual machine needs to be > available not only on virtual router network context, but on our internal > DNS servers. > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind server) > thru an open source API written by globo.com called DNSAPI. More info at > https://github.com/globocom/Dns-Api. > > > Thanks for the proposal. > > I recommend that you document your design goals in 4.5 or above design docs > wiki: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents > > I saw the video you shared, it looked seamless but I could not figure out > how the ACS plugin interacts with the DNS provider. The API library you > mentioned is written in Ruby, so how does it integrate or work with the dns > plugin in ACS, is it over HTTP or RPC/Thrift? > > Regards. > > > > To make this implementation of DNS provider, we based our plugin on > "dns-notifier", but we had to add more classes for our implementation. > > * DnsAPINetworkDAO to manage the networkDomain for each network. > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > * DnsAPIElement, this class implements the provider itself. > * DnsAPIResource, implements all communications with DNSAPI > (ServerResource). > > Besides this classes, another one was necessary to the call to > DnsAPIResource and return the answer, and one API command was created to > configure the provider in Zone. > > Above a video that show you how everything was integrated. > > https://www.youtube.com/watch?v=fAB53T_NZMI > > We really appreciate all your comments about our implementation, > > thanks in advance > PS: Sorry about duplicated e-mail in mailing list, but I forget to use > DISCUSS and send using company e-mail) > > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
On Thu, Jun 19, 2014 at 7:36 PM, Silvano Nogueira Buback < silv...@corp.globo.com> wrote: > Hi Rohit, > > I started the documentation and I think on next wednesday I'm with the > first version ready for community feedback. I will put the details of how > plugin work with DNSAPI and how DNSAPI work with bind. > That would be nice. > > I don't have permission to create new pages on wiki. I submit the > documentation to here or someone will give me access to update wiki? > Create a user account on cwiki.a.o and share with us your account/username/email. I don't have admin access but I'm sure someone such as Daan or Chip would be able to help you. Cheers. > []'s, > > Silvano Buback > > > On Fri, Jun 13, 2014 at 7:53 AM, Rohit Yadav wrote: > > > Hi Silvano, > > > > On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < > > silv...@corp.globo.com> wrote: > > > > > Hi there, > > > > > > > > > I work at Globo.com, a media company in Brazil. Here we use a > cloudstack > > > private network with an advanced zone setup (isolated vlans). > > > > > > For some couple of reasons, the name of virtual machine needs to be > > > available not only on virtual router network context, but on our > internal > > > DNS servers. > > > > > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind > > server) > > > thru an open source API written by globo.com called DNSAPI. More info > at > > > https://github.com/globocom/Dns-Api. > > > > > > > Thanks for the proposal. > > > > I recommend that you document your design goals in 4.5 or above design > docs > > wiki: > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents > > > > I saw the video you shared, it looked seamless but I could not figure out > > how the ACS plugin interacts with the DNS provider. The API library you > > mentioned is written in Ruby, so how does it integrate or work with the > dns > > plugin in ACS, is it over HTTP or RPC/Thrift? > > > > Regards. > > > > > > > > > > To make this implementation of DNS provider, we based our plugin on > > > "dns-notifier", but we had to add more classes for our implementation. > > > > > > * DnsAPINetworkDAO to manage the networkDomain for each network. > > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > > > * DnsAPIElement, this class implements the provider itself. > > > * DnsAPIResource, implements all communications with DNSAPI > > > (ServerResource). > > > > > > Besides this classes, another one was necessary to the call to > > > DnsAPIResource and return the answer, and one API command was created > to > > > configure the provider in Zone. > > > > > > Above a video that show you how everything was integrated. > > > > > > https://www.youtube.com/watch?v=fAB53T_NZMI > > > > > > We really appreciate all your comments about our implementation, > > > > > > thanks in advance > > > PS: Sorry about duplicated e-mail in mailing list, but I forget to use > > > DISCUSS and send using company e-mail) > > > > > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Of course, I forgotten my account info: snbuback / silv...@corp.globo.com On Thu, Jun 19, 2014 at 11:20 AM, Rohit Yadav wrote: > On Thu, Jun 19, 2014 at 7:36 PM, Silvano Nogueira Buback < > silv...@corp.globo.com> wrote: > > > Hi Rohit, > > > > I started the documentation and I think on next wednesday I'm with > the > > first version ready for community feedback. I will put the details of how > > plugin work with DNSAPI and how DNSAPI work with bind. > > > > That would be nice. > > > > > > I don't have permission to create new pages on wiki. I submit the > > documentation to here or someone will give me access to update wiki? > > > > Create a user account on cwiki.a.o and share with us your > account/username/email. I don't have admin access but I'm sure someone such > as Daan or Chip would be able to help you. > > Cheers. > > > > []'s, > > > > Silvano Buback > > > > > > On Fri, Jun 13, 2014 at 7:53 AM, Rohit Yadav > wrote: > > > > > Hi Silvano, > > > > > > On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < > > > silv...@corp.globo.com> wrote: > > > > > > > Hi there, > > > > > > > > > > > > I work at Globo.com, a media company in Brazil. Here we use a > > cloudstack > > > > private network with an advanced zone setup (isolated vlans). > > > > > > > > For some couple of reasons, the name of virtual machine needs to be > > > > available not only on virtual router network context, but on our > > internal > > > > DNS servers. > > > > > > > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind > > > server) > > > > thru an open source API written by globo.com called DNSAPI. More > info > > at > > > > https://github.com/globocom/Dns-Api. > > > > > > > > > > Thanks for the proposal. > > > > > > I recommend that you document your design goals in 4.5 or above design > > docs > > > wiki: > > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents > > > > > > I saw the video you shared, it looked seamless but I could not figure > out > > > how the ACS plugin interacts with the DNS provider. The API library you > > > mentioned is written in Ruby, so how does it integrate or work with the > > dns > > > plugin in ACS, is it over HTTP or RPC/Thrift? > > > > > > Regards. > > > > > > > > > > > > > > To make this implementation of DNS provider, we based our plugin on > > > > "dns-notifier", but we had to add more classes for our > implementation. > > > > > > > > * DnsAPINetworkDAO to manage the networkDomain for each network. > > > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > > > > * DnsAPIElement, this class implements the provider itself. > > > > * DnsAPIResource, implements all communications with DNSAPI > > > > (ServerResource). > > > > > > > > Besides this classes, another one was necessary to the call to > > > > DnsAPIResource and return the answer, and one API command was created > > to > > > > configure the provider in Zone. > > > > > > > > Above a video that show you how everything was integrated. > > > > > > > > https://www.youtube.com/watch?v=fAB53T_NZMI > > > > > > > > We really appreciate all your comments about our implementation, > > > > > > > > thanks in advance > > > > PS: Sorry about duplicated e-mail in mailing list, but I forget to > use > > > > DISCUSS and send using company e-mail) > > > > > > > > > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi guys, I finish the first version of design document: https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub . Someone could give me access to put design documents in wiki? Bellow the username of people work with Cloudstack in Globo.com and need access. snbuback silv...@corp.globo.com daniel.simoes daniel.sim...@corp.globo.com lokama - lok...@gmail.com Regards, Silvano Buback On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback wrote: > Of course, I forgotten my account info: > snbuback / silv...@corp.globo.com > > > On Thu, Jun 19, 2014 at 11:20 AM, Rohit Yadav wrote: > > > On Thu, Jun 19, 2014 at 7:36 PM, Silvano Nogueira Buback < > > silv...@corp.globo.com> wrote: > > > > > Hi Rohit, > > > > > > I started the documentation and I think on next wednesday I'm with > > the > > > first version ready for community feedback. I will put the details of > how > > > plugin work with DNSAPI and how DNSAPI work with bind. > > > > > > > That would be nice. > > > > > > > > > > I don't have permission to create new pages on wiki. I submit the > > > documentation to here or someone will give me access to update wiki? > > > > > > > Create a user account on cwiki.a.o and share with us your > > account/username/email. I don't have admin access but I'm sure someone > such > > as Daan or Chip would be able to help you. > > > > Cheers. > > > > > > > []'s, > > > > > > Silvano Buback > > > > > > > > > On Fri, Jun 13, 2014 at 7:53 AM, Rohit Yadav > > wrote: > > > > > > > Hi Silvano, > > > > > > > > On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < > > > > silv...@corp.globo.com> wrote: > > > > > > > > > Hi there, > > > > > > > > > > > > > > > I work at Globo.com, a media company in Brazil. Here we use a > > > cloudstack > > > > > private network with an advanced zone setup (isolated vlans). > > > > > > > > > > For some couple of reasons, the name of virtual machine needs to be > > > > > available not only on virtual router network context, but on our > > > internal > > > > > DNS servers. > > > > > > > > > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind > > > > server) > > > > > thru an open source API written by globo.com called DNSAPI. More > > info > > > at > > > > > https://github.com/globocom/Dns-Api. > > > > > > > > > > > > > Thanks for the proposal. > > > > > > > > I recommend that you document your design goals in 4.5 or above > design > > > docs > > > > wiki: > > > > > > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents > > > > > > > > I saw the video you shared, it looked seamless but I could not figure > > out > > > > how the ACS plugin interacts with the DNS provider. The API library > you > > > > mentioned is written in Ruby, so how does it integrate or work with > the > > > dns > > > > plugin in ACS, is it over HTTP or RPC/Thrift? > > > > > > > > Regards. > > > > > > > > > > > > > > > > > > To make this implementation of DNS provider, we based our plugin on > > > > > "dns-notifier", but we had to add more classes for our > > implementation. > > > > > > > > > > * DnsAPINetworkDAO to manage the networkDomain for each network. > > > > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. > > > > > * DnsAPIElement, this class implements the provider itself. > > > > > * DnsAPIResource, implements all communications with DNSAPI > > > > > (ServerResource). > > > > > > > > > > Besides this classes, another one was necessary to the call to > > > > > DnsAPIResource and return the answer, and one API command was > created > > > to > > > > > configure the provider in Zone. > > > > > > > > > > Above a video that show you how everything was integrated. > > > > > > > > > > https://www.youtube.com/watch?v=fAB53T_NZMI > > > > > > > > > > We really appreciate all your comments about our implementation, > > > > > > > > > > thanks in advance > > > > > PS: Sorry about duplicated e-mail in mailing list, but I forget to > > use > > > > > DISCUSS and send using company e-mail) > > > > > > > > > > > > > > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
you three have access to the wiki On Wed, Jun 25, 2014 at 10:38 PM, Silvano Nogueira Buback wrote: > Hi guys, > >I finish the first version of design document: > https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub > . > >Someone could give me access to put design documents in wiki? Bellow the > username of people work with Cloudstack in Globo.com and need access. > > snbuback silv...@corp.globo.com > daniel.simoes daniel.sim...@corp.globo.com > lokama - lok...@gmail.com > > Regards, > > Silvano Buback > > > > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback wrote: > >> Of course, I forgotten my account info: >> snbuback / silv...@corp.globo.com >> >> >> On Thu, Jun 19, 2014 at 11:20 AM, Rohit Yadav wrote: >> >> > On Thu, Jun 19, 2014 at 7:36 PM, Silvano Nogueira Buback < >> > silv...@corp.globo.com> wrote: >> > >> > > Hi Rohit, >> > > >> > > I started the documentation and I think on next wednesday I'm with >> > the >> > > first version ready for community feedback. I will put the details of >> how >> > > plugin work with DNSAPI and how DNSAPI work with bind. >> > > >> > >> > That would be nice. >> > >> > >> > > >> > > I don't have permission to create new pages on wiki. I submit the >> > > documentation to here or someone will give me access to update wiki? >> > > >> > >> > Create a user account on cwiki.a.o and share with us your >> > account/username/email. I don't have admin access but I'm sure someone >> such >> > as Daan or Chip would be able to help you. >> > >> > Cheers. >> > >> > >> > > []'s, >> > > >> > > Silvano Buback >> > > >> > > >> > > On Fri, Jun 13, 2014 at 7:53 AM, Rohit Yadav >> > wrote: >> > > >> > > > Hi Silvano, >> > > > >> > > > On Fri, Jun 13, 2014 at 10:51 AM, Silvano Nogueira Buback < >> > > > silv...@corp.globo.com> wrote: >> > > > >> > > > > Hi there, >> > > > > >> > > > > >> > > > > I work at Globo.com, a media company in Brazil. Here we use a >> > > cloudstack >> > > > > private network with an advanced zone setup (isolated vlans). >> > > > > >> > > > > For some couple of reasons, the name of virtual machine needs to be >> > > > > available not only on virtual router network context, but on our >> > > internal >> > > > > DNS servers. >> > > > > >> > > > > Our proposal is integrate cloudstack (v 4.5) with DNS server (Bind >> > > > server) >> > > > > thru an open source API written by globo.com called DNSAPI. More >> > info >> > > at >> > > > > https://github.com/globocom/Dns-Api. >> > > > > >> > > > >> > > > Thanks for the proposal. >> > > > >> > > > I recommend that you document your design goals in 4.5 or above >> design >> > > docs >> > > > wiki: >> > > > >> > > >> > >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.5+Design+Documents >> > > > >> > > > I saw the video you shared, it looked seamless but I could not figure >> > out >> > > > how the ACS plugin interacts with the DNS provider. The API library >> you >> > > > mentioned is written in Ruby, so how does it integrate or work with >> the >> > > dns >> > > > plugin in ACS, is it over HTTP or RPC/Thrift? >> > > > >> > > > Regards. >> > > > >> > > > >> > > > > >> > > > > To make this implementation of DNS provider, we based our plugin on >> > > > > "dns-notifier", but we had to add more classes for our >> > implementation. >> > > > > >> > > > > * DnsAPINetworkDAO to manage the networkDomain for each network. >> > > > > * DnsAPIVirtualMachineDAO to manage DNS records for vms. >> > > > > * DnsAPIElement, this class implements the provider itself. >> > > > > * DnsAPIResource, implements all communications with DNSAPI >> > > > > (ServerResource). >> > > > > >> > > > > Besides this classes, another one was necessary to the call to >> > > > > DnsAPIResource and return the answer, and one API command was >> created >> > > to >> > > > > configure the provider in Zone. >> > > > > >> > > > > Above a video that show you how everything was integrated. >> > > > > >> > > > > https://www.youtube.com/watch?v=fAB53T_NZMI >> > > > > >> > > > > We really appreciate all your comments about our implementation, >> > > > > >> > > > > thanks in advance >> > > > > PS: Sorry about duplicated e-mail in mailing list, but I forget to >> > use >> > > > > DISCUSS and send using company e-mail) >> > > > > >> > > > >> > > >> > >> -- Daan
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback wrote: > Hi guys, > >I finish the first version of design document: > https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub > . > >Someone could give me access to put design documents in wiki? Bellow the > username of people work with Cloudstack in Globo.com and need access. > > snbuback silv...@corp.globo.com > daniel.simoes daniel.sim...@corp.globo.com > lokama - lok...@gmail.com > > Regards, > > Silvano Buback > > > > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback wrote: > >> Of course, I forgotten my account info: >> snbuback / silv...@corp.globo.com >> Done. --David
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Thank you David. I put design documents on wiki: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI. I create an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6998 too. I look forward to hearing your feedbacks. []'s, Silvano Buback On Wed, Jun 25, 2014 at 5:50 PM, David Nalley wrote: > On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback > wrote: > > Hi guys, > > > >I finish the first version of design document: > > > https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub > > . > > > >Someone could give me access to put design documents in wiki? Bellow > the > > username of people work with Cloudstack in Globo.com and need access. > > > > snbuback silv...@corp.globo.com > > daniel.simoes daniel.sim...@corp.globo.com > > lokama - lok...@gmail.com > > > > Regards, > > > > Silvano Buback > > > > > > > > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback > wrote: > > > >> Of course, I forgotten my account info: > >> snbuback / silv...@corp.globo.com > >> > > > Done. > > --David >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi guys, I think you are busy because 4.4 release tasks, but I'm worried about the time to 4.5 feature freeze. I put the documentation of feature in wiki as requested and I hoped people read there and make some comments here. To help, I will put design issues that are in document, one by one, and we can discuss in this thread. After each discussion I will change the document. I have one question about removing DNS domain when network has been deleted. In my current implementation I remove DNS domain when network is removed. But if the DNS domain is shared with another network or maybe is a dns domain used outside ACS this can be a problem. What I can do with DNS domain when network is removed: 1. Keep the current implementation. Always deleted DNS domain when network is removed (works well if the ACS is the only manager for the DNS (one network domain per network). 2. Remove DNS domain only if the domain was created by ACS. This can be a problem if someone put records after ACS creation. 3. Remove DNS domain only if there is no more records there. Maybe DNS domain can stay forever there because an inconsistency that keep only one record. Which one is the best? []'s, Silvano Buback On Thu, Jun 26, 2014 at 11:34 AM, Silvano Nogueira Buback < silv...@corp.globo.com> wrote: > Thank you David. > > I put design documents on wiki: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI. > I create an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6998 > too. > > I look forward to hearing your feedbacks. > > []'s, > > Silvano Buback > > > On Wed, Jun 25, 2014 at 5:50 PM, David Nalley wrote: > >> On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback >> wrote: >> > Hi guys, >> > >> >I finish the first version of design document: >> > >> https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub >> > . >> > >> >Someone could give me access to put design documents in wiki? Bellow >> the >> > username of people work with Cloudstack in Globo.com and need access. >> > >> > snbuback silv...@corp.globo.com >> > daniel.simoes daniel.sim...@corp.globo.com >> > lokama - lok...@gmail.com >> > >> > Regards, >> > >> > Silvano Buback >> > >> > >> > >> > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback >> wrote: >> > >> >> Of course, I forgotten my account info: >> >> snbuback / silv...@corp.globo.com >> >> >> >> >> Done. >> >> --David >> > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
To push that choice over to the operator you could add it as a global/zone/network option. As an operator i would prefer to have my own logic to handle cleanup, but this varies for everyone hence the option :-) Erik 3. juli 2014 21:45 skrev "Silvano Nogueira Buback" følgende: > Hi guys, > > I think you are busy because 4.4 release tasks, but I'm worried about > the time to 4.5 feature freeze. I put the documentation of feature in wiki > as requested and I hoped people read there and make some comments here. > > To help, I will put design issues that are in document, one by one, and we > can discuss in this thread. After each discussion I will change the > document. > >I have one question about removing DNS domain when network has been > deleted. In my current implementation I remove DNS domain when network is > removed. But if the DNS domain is shared with another network or maybe is a > dns domain used outside ACS this can be a problem. What I can do with DNS > domain when network is removed: > >1. Keep the current implementation. Always deleted DNS domain when >network is removed (works well if the ACS is the only manager for the > DNS >(one network domain per network). >2. Remove DNS domain only if the domain was created by ACS. This can be >a problem if someone put records after ACS creation. >3. Remove DNS domain only if there is no more records there. Maybe DNS >domain can stay forever there because an inconsistency that keep only > one >record. > > > Which one is the best? > > []'s, > > Silvano Buback > > > > On Thu, Jun 26, 2014 at 11:34 AM, Silvano Nogueira Buback < > silv...@corp.globo.com> wrote: > > > Thank you David. > > > > I put design documents on wiki: > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI > . > > I create an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6998 > > too. > > > > I look forward to hearing your feedbacks. > > > > []'s, > > > > Silvano Buback > > > > > > On Wed, Jun 25, 2014 at 5:50 PM, David Nalley wrote: > > > >> On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback > >> wrote: > >> > Hi guys, > >> > > >> >I finish the first version of design document: > >> > > >> > https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub > >> > . > >> > > >> >Someone could give me access to put design documents in wiki? > Bellow > >> the > >> > username of people work with Cloudstack in Globo.com and need access. > >> > > >> > snbuback silv...@corp.globo.com > >> > daniel.simoes daniel.sim...@corp.globo.com > >> > lokama - lok...@gmail.com > >> > > >> > Regards, > >> > > >> > Silvano Buback > >> > > >> > > >> > > >> > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback > >> wrote: > >> > > >> >> Of course, I forgotten my account info: > >> >> snbuback / silv...@corp.globo.com > >> >> > >> > >> > >> Done. > >> > >> --David > >> > > > > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
I tend to agree with Erik, flexibility solves the problem for more people, while solution 1 is likely the easiest to implement. I am not sure that it makes sense for most people though - and would really only work for greenfield deployments or clouds that had all of the DNS entries relating to instances in the cloud. First question; how are you intending on using it? Which of those solutions works for you? --David On Thu, Jul 3, 2014 at 3:49 PM, Erik Weber wrote: > To push that choice over to the operator you could add it as a > global/zone/network option. > > As an operator i would prefer to have my own logic to handle cleanup, but > this varies for everyone hence the option :-) > > Erik > 3. juli 2014 21:45 skrev "Silvano Nogueira Buback" > følgende: > >> Hi guys, >> >> I think you are busy because 4.4 release tasks, but I'm worried about >> the time to 4.5 feature freeze. I put the documentation of feature in wiki >> as requested and I hoped people read there and make some comments here. >> >> To help, I will put design issues that are in document, one by one, and we >> can discuss in this thread. After each discussion I will change the >> document. >> >>I have one question about removing DNS domain when network has been >> deleted. In my current implementation I remove DNS domain when network is >> removed. But if the DNS domain is shared with another network or maybe is a >> dns domain used outside ACS this can be a problem. What I can do with DNS >> domain when network is removed: >> >>1. Keep the current implementation. Always deleted DNS domain when >>network is removed (works well if the ACS is the only manager for the >> DNS >>(one network domain per network). >>2. Remove DNS domain only if the domain was created by ACS. This can be >>a problem if someone put records after ACS creation. >>3. Remove DNS domain only if there is no more records there. Maybe DNS >>domain can stay forever there because an inconsistency that keep only >> one >>record. >> >> >> Which one is the best? >> >> []'s, >> >> Silvano Buback >> >> >> >> On Thu, Jun 26, 2014 at 11:34 AM, Silvano Nogueira Buback < >> silv...@corp.globo.com> wrote: >> >> > Thank you David. >> > >> > I put design documents on wiki: >> > >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI >> . >> > I create an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6998 >> > too. >> > >> > I look forward to hearing your feedbacks. >> > >> > []'s, >> > >> > Silvano Buback >> > >> > >> > On Wed, Jun 25, 2014 at 5:50 PM, David Nalley wrote: >> > >> >> On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback >> >> wrote: >> >> > Hi guys, >> >> > >> >> >I finish the first version of design document: >> >> > >> >> >> https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub >> >> > . >> >> > >> >> >Someone could give me access to put design documents in wiki? >> Bellow >> >> the >> >> > username of people work with Cloudstack in Globo.com and need access. >> >> > >> >> > snbuback silv...@corp.globo.com >> >> > daniel.simoes daniel.sim...@corp.globo.com >> >> > lokama - lok...@gmail.com >> >> > >> >> > Regards, >> >> > >> >> > Silvano Buback >> >> > >> >> > >> >> > >> >> > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback >> >> wrote: >> >> > >> >> >> Of course, I forgotten my account info: >> >> >> snbuback / silv...@corp.globo.com >> >> >> >> >> >> >> >> >> Done. >> >> >> >> --David >> >> >> > >> > >>
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
I think the question is relevant to network creation as well. If I provide a domain that already exists, what is the result? A couple of other comments: - are we going to handle the case of secondary IP addresses? - DNSAPI sounds generic, but it actually refers to one specific API architected by Globo. To avoid confusion, would it make sense to rename it GloboDNSAPI? Alternately, give the DNSAPI project a less generic name (e.g., vincular) From: David Nalley mailto:da...@gnsa.us>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org>> Date: Friday, July 11, 2014 at 10:06 AM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org>> Subject: Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5) I tend to agree with Erik, flexibility solves the problem for more people, while solution 1 is likely the easiest to implement. I am not sure that it makes sense for most people though - and would really only work for greenfield deployments or clouds that had all of the DNS entries relating to instances in the cloud. First question; how are you intending on using it? Which of those solutions works for you? --David On Thu, Jul 3, 2014 at 3:49 PM, Erik Weber mailto:terbol...@gmail.com>> wrote: To push that choice over to the operator you could add it as a global/zone/network option. As an operator i would prefer to have my own logic to handle cleanup, but this varies for everyone hence the option :-) Erik 3. juli 2014 21:45 skrev "Silvano Nogueira Buback" mailto:silv...@corp.globo.com>> følgende: Hi guys, I think you are busy because 4.4 release tasks, but I'm worried about the time to 4.5 feature freeze. I put the documentation of feature in wiki as requested and I hoped people read there and make some comments here. To help, I will put design issues that are in document, one by one, and we can discuss in this thread. After each discussion I will change the document. I have one question about removing DNS domain when network has been deleted. In my current implementation I remove DNS domain when network is removed. But if the DNS domain is shared with another network or maybe is a dns domain used outside ACS this can be a problem. What I can do with DNS domain when network is removed: 1. Keep the current implementation. Always deleted DNS domain when network is removed (works well if the ACS is the only manager for the DNS (one network domain per network). 2. Remove DNS domain only if the domain was created by ACS. This can be a problem if someone put records after ACS creation. 3. Remove DNS domain only if there is no more records there. Maybe DNS domain can stay forever there because an inconsistency that keep only one record. Which one is the best? []'s, Silvano Buback On Thu, Jun 26, 2014 at 11:34 AM, Silvano Nogueira Buback < silv...@corp.globo.com<mailto:silv...@corp.globo.com>> wrote: > Thank you David. > > I put design documents on wiki: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI . > I create an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6998 > too. > > I look forward to hearing your feedbacks. > > []'s, > > Silvano Buback > > > On Wed, Jun 25, 2014 at 5:50 PM, David Nalley > mailto:da...@gnsa.us>> wrote: > >> On Wed, Jun 25, 2014 at 4:38 PM, Silvano Nogueira Buback >> mailto:silv...@corp.globo.com>> wrote: >> > Hi guys, >> > >> >I finish the first version of design document: >> > >> https://docs.google.com/document/d/1kbPQJrBC87ZtR-t7LwHFDzAmT436ShtjwKE84FVfByM/pub >> > . >> > >> >Someone could give me access to put design documents in wiki? Bellow >> the >> > username of people work with Cloudstack in Globo.com and need access. >> > >> > snbuback silv...@corp.globo.com<mailto:silv...@corp.globo.com> >> > daniel.simoes >> > daniel.sim...@corp.globo.com<mailto:daniel.sim...@corp.globo.com> >> > lokama - lok...@gmail.com<mailto:lok...@gmail.com> >> > >> > Regards, >> > >> > Silvano Buback >> > >> > >> > >> > On Thu, Jun 19, 2014 at 11:29 AM, Silvano Buback >> > mailto:snbub...@gmail.com>> >> wrote: >> > >> >> Of course, I forgotten my account info: >> >> snbuback / silv...@corp.globo.com<mailto:silv...@corp.globo.com> >> >> >> >> >> Done. >> >> --David >> > >
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi guys, @David As Silvano mentioned earlier, our cloud-related DNS have unique names (based on network info), so conflicts do not happen. As such, these domains are exclusive to our cloud infrastructure and we let Cloudstack have full authority over them. For that reason, whenever a network is deleted, the domain associated to it is removed, along with every record in it. @Chiradeep If a domain already exists when a network is created, the plugin takes over that domain, creating and removing records as needed. It does not handle any records created externally. The only exception is when the domain is removed, as explained just above. Secondary IPs are currently not handled by the plugin, since we understand that once that IP is reserved by Cloudstack, routing and name resolution should be done manually by the operator. As for the name, GloboDNS sounds about right :) We'll make the appropriate changes to avoid confusion. This is what makes sense for us in this first release. Implementing every option available to the operator might make the plugin configuration very confusing. A simpler approach would be to create one single global/zone option that allows Cloudstack to have full authority over domains/records or not. In the case where Cloudstack does not have authority, an error could be thrown if the domain/record already exists and domains are never removed by the plugin itself, so an operator would need to do it manually (or by means of another tool). What do you think? -- Daniel Simões Time Evolução Infra - Globo.com E-mail: daniel.sim...@corp.globo.com Tel.: +55 21 2483-6977 2014-07-14 14:20 GMT-03:00 Chiradeep Vittal : > I think the question is relevant to network creation as well. If I provide > a domain that already exists, what is the result? > > A couple of other comments: > - are we going to handle the case of secondary IP addresses? > - DNSAPI sounds generic, but it actually refers to one specific API > architected by Globo. To avoid confusion, would it make sense to rename it > GloboDNSAPI? Alternately, give the DNSAPI project a less generic name > (e.g., vincular) > > From: David Nalley mailto:da...@gnsa.us>> > Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> > Date: Friday, July 11, 2014 at 10:06 AM > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> > Subject: Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind > (for 4.5) > > I tend to agree with Erik, flexibility solves the problem for more > people, while solution 1 is likely the easiest to implement. I am not > sure that it makes sense for most people though - and would really > only work for greenfield deployments or clouds that had all of the DNS > entries relating to instances in the cloud. > > First question; how are you intending on using it? Which of those > solutions works for you? > > --David > > > > On Thu, Jul 3, 2014 at 3:49 PM, Erik Weber terbol...@gmail.com>> wrote: > To push that choice over to the operator you could add it as a > global/zone/network option. > > As an operator i would prefer to have my own logic to handle cleanup, but > this varies for everyone hence the option :-) > > Erik > 3. juli 2014 21:45 skrev "Silvano Nogueira Buback" <mailto:silv...@corp.globo.com>> > følgende: > > Hi guys, > > I think you are busy because 4.4 release tasks, but I'm worried about > the time to 4.5 feature freeze. I put the documentation of feature in wiki > as requested and I hoped people read there and make some comments here. > > To help, I will put design issues that are in document, one by one, and we > can discuss in this thread. After each discussion I will change the > document. > > I have one question about removing DNS domain when network has been > deleted. In my current implementation I remove DNS domain when network is > removed. But if the DNS domain is shared with another network or maybe is a > dns domain used outside ACS this can be a problem. What I can do with DNS > domain when network is removed: > > 1. Keep the current implementation. Always deleted DNS domain when > network is removed (works well if the ACS is the only manager for the > DNS > (one network domain per network). > 2. Remove DNS domain only if the domain was created by ACS. This can be > a problem if someone put records after ACS creation. > 3. Remove DNS domain only if there is no more records there. Maybe DNS > domain can stay forever there because an inconsistency that keep only > one > record. > > &
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
Hi guys, Since nobody was opposed to the approach suggested in the last e-mail, we went on and implemented the global option that authorizes the plugin to override record entries when they already exist in the DNS server. We also updated the name to GloboDNS and the functional spec to reflect both changes. You can take a look at the table that summarizes the actions for the GloboDNS plugin on the wiki <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI>. Unit tests were implemented to make sure all of these cases behave as expected. Please let me know how we can move forward to integrate this in the Cloudstack repository. Cheers, -- Daniel Simões Time Evolução Infra - Globo.com E-mail: daniel.sim...@corp.globo.com Tel.: +55 21 2483-6977 2014-07-14 16:41 GMT-03:00 Daniel Vega Simões : > Hi guys, > > @David > As Silvano mentioned earlier, our cloud-related DNS have unique names > (based on network info), so conflicts do not happen. As such, these domains > are exclusive to our cloud infrastructure and we let Cloudstack have full > authority over them. For that reason, whenever a network is deleted, the > domain associated to it is removed, along with every record in it. > > > @Chiradeep > If a domain already exists when a network is created, the plugin takes > over that domain, creating and removing records as needed. It does not > handle any records created externally. The only exception is when the > domain is removed, as explained just above. > > Secondary IPs are currently not handled by the plugin, since we understand > that once that IP is reserved by Cloudstack, routing and name resolution > should be done manually by the operator. > > As for the name, GloboDNS sounds about right :) We'll make the appropriate > changes to avoid confusion. > > > > This is what makes sense for us in this first release. Implementing every > option available to the operator might make the plugin configuration very > confusing. > > A simpler approach would be to create one single global/zone option that > allows Cloudstack to have full authority over domains/records or not. In > the case where Cloudstack does not have authority, an error could be thrown > if the domain/record already exists and domains are never removed by the > plugin itself, so an operator would need to do it manually (or by means of > another tool). > > > What do you think? > > > -- > Daniel Simões > Time Evolução Infra - Globo.com > E-mail: daniel.sim...@corp.globo.com > Tel.: +55 21 2483-6977 > > > 2014-07-14 14:20 GMT-03:00 Chiradeep Vittal : > > I think the question is relevant to network creation as well. If I provide >> a domain that already exists, what is the result? >> >> A couple of other comments: >> - are we going to handle the case of secondary IP addresses? >> - DNSAPI sounds generic, but it actually refers to one specific API >> architected by Globo. To avoid confusion, would it make sense to rename it >> GloboDNSAPI? Alternately, give the DNSAPI project a less generic name >> (e.g., vincular) >> >> From: David Nalley mailto:da...@gnsa.us>> >> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < >> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> >> Date: Friday, July 11, 2014 at 10:06 AM >> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < >> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> >> Subject: Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind >> (for 4.5) >> >> I tend to agree with Erik, flexibility solves the problem for more >> people, while solution 1 is likely the easiest to implement. I am not >> sure that it makes sense for most people though - and would really >> only work for greenfield deployments or clouds that had all of the DNS >> entries relating to instances in the cloud. >> >> First question; how are you intending on using it? Which of those >> solutions works for you? >> >> --David >> >> >> >> On Thu, Jul 3, 2014 at 3:49 PM, Erik Weber > terbol...@gmail.com>> wrote: >> To push that choice over to the operator you could add it as a >> global/zone/network option. >> >> As an operator i would prefer to have my own logic to handle cleanup, but >> this varies for everyone hence the option :-) >> >> Erik >> 3. juli 2014 21:45 skrev "Silvano Nogueira Buback" < >> silv...@corp.globo.com<mailto:silv...@corp.globo.com>> >> følgende: >> >> Hi guys, >> >> I
Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for Bind (for 4.5)
No change in the last two weeks, just sent code for review. https://reviews.apache.org/r/24611/ Regards, -- Daniel Simões Time Evolução Infra - Globo.com E-mail: daniel.sim...@corp.globo.com Tel.: +55 21 2483-6977 2014-07-30 11:04 GMT-03:00 Daniel Vega Simões : > Hi guys, > > Since nobody was opposed to the approach suggested in the last e-mail, we > went on and implemented the global option that authorizes the plugin to > override record entries when they already exist in the DNS server. > > We also updated the name to GloboDNS and the functional spec to reflect > both changes. You can take a look at the table that summarizes the actions > for the GloboDNS plugin on the wiki > <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bind+and+PowerDNS+integration+by+Globo+DNSAPI>. > Unit tests were implemented to make sure all of these cases behave as > expected. > > Please let me know how we can move forward to integrate this in the > Cloudstack repository. > > > Cheers, > > -- > Daniel Simões > Time Evolução Infra - Globo.com > E-mail: daniel.sim...@corp.globo.com > Tel.: +55 21 2483-6977 > > > 2014-07-14 16:41 GMT-03:00 Daniel Vega Simões < > daniel.sim...@corp.globo.com>: > > Hi guys, >> >> @David >> As Silvano mentioned earlier, our cloud-related DNS have unique names >> (based on network info), so conflicts do not happen. As such, these domains >> are exclusive to our cloud infrastructure and we let Cloudstack have full >> authority over them. For that reason, whenever a network is deleted, the >> domain associated to it is removed, along with every record in it. >> >> >> @Chiradeep >> If a domain already exists when a network is created, the plugin takes >> over that domain, creating and removing records as needed. It does not >> handle any records created externally. The only exception is when the >> domain is removed, as explained just above. >> >> Secondary IPs are currently not handled by the plugin, since we >> understand that once that IP is reserved by Cloudstack, routing and name >> resolution should be done manually by the operator. >> >> As for the name, GloboDNS sounds about right :) We'll make the >> appropriate changes to avoid confusion. >> >> >> >> This is what makes sense for us in this first release. Implementing every >> option available to the operator might make the plugin configuration very >> confusing. >> >> A simpler approach would be to create one single global/zone option that >> allows Cloudstack to have full authority over domains/records or not. In >> the case where Cloudstack does not have authority, an error could be thrown >> if the domain/record already exists and domains are never removed by the >> plugin itself, so an operator would need to do it manually (or by means of >> another tool). >> >> >> What do you think? >> >> >> -- >> Daniel Simões >> Time Evolução Infra - Globo.com >> E-mail: daniel.sim...@corp.globo.com >> Tel.: +55 21 2483-6977 >> >> >> 2014-07-14 14:20 GMT-03:00 Chiradeep Vittal >> : >> >> I think the question is relevant to network creation as well. If I >>> provide a domain that already exists, what is the result? >>> >>> A couple of other comments: >>> - are we going to handle the case of secondary IP addresses? >>> - DNSAPI sounds generic, but it actually refers to one specific API >>> architected by Globo. To avoid confusion, would it make sense to rename it >>> GloboDNSAPI? Alternately, give the DNSAPI project a less generic name >>> (e.g., vincular) >>> >>> From: David Nalley mailto:da...@gnsa.us>> >>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" >>> mailto:dev@cloudstack.apache.org>> >>> Date: Friday, July 11, 2014 at 10:06 AM >>> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < >>> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> >>> Subject: Re: [DISCUSS] [PROPOSAL] Implementation of DNS Provider for >>> Bind (for 4.5) >>> >>> I tend to agree with Erik, flexibility solves the problem for more >>> people, while solution 1 is likely the easiest to implement. I am not >>> sure that it makes sense for most people though - and would really >>> only work for greenfield deployments or clouds that had all of the DNS >>> entries relating to instances in the cloud. >>> >>> First question; how are you i
