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 <bhais...@apache.org> 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) > > >