1. Mailing Lists
  2. Contributors
  3. Re: DNS Connector

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: DNS Connector

Re: DNS Connector

Avatar

Re: DNS Connector

by
Elico Corp, Eric Caudal
- 26/08/2016 01:22:00

Agree with you Dave.


Server-*: tools to manage local server resources/application. The aim of the tool is to bring server related function (scripts, letsencrypt, Dead man's switch, ldap connection tools etc)

Infra-*: tools to manage the infrastructure (servers, network, DNS, VM, docker orchestration, asset management, repos etc.)


Infrastructure is definitively broader than servers in extension (a server is part of the infrastructure) and that is the reason of the proposal. Indeed, today DNS connector does not fit in server-tools as this is  not server related: this is a connector to an external service to manage in Odoo all DNS record of a company (at least that is how we use it in our company).

If we talk about the ldap local authentication for the server, I would keep it in server-*, whereas I we would talk about managing a network of ldap servers (for whatever the purpose), I would rather have it in infra-*.


BTW (<troll>: I am not so much in favor of naming repo based on technical design and rather prefer the functional approach. This is so because I am a functional guy of course but also because an ERP is a technical tool to help improve functions in the enterprise. For the user point of view the entry point is the function not the mean.

Anyway, there would probably be hundreds of voices debating pros and cons here ;p<troll/>


But for this reason I'd rather name the repo infra-dns (the function of managing the dns for an infrastructure) rather than connector-dns (connecting to a DNS provider, which is partial because actually you could use the module with manual input).


--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/26/2016 02:08 AM, Dave Lasley wrote:
<blockquote cite="mid:FA0A714A-FD19-43F1-9EA9-2EAF0C4FDE2D@laslabs.com" type="cite">
I would say that infrastructure means the controlling of the architecture behind the server. 

For example, this proposed module may not even control the DNS record for the server it is on. Contrast this to a module like letsencrypt, which does operate at an infrastructure level, but only targeted towards the server that it is on.

I propose that the delineation of whether something is infrastructure vs. server is whether the module is working with its own server, or a collection of abstract possibly servers.


On Aug 25, 2016, at 10:53 AM, Daniel Reis <dgreis@sapo.pt> wrote:

The "server-" comes from the "server-tools".
We should split it into several repos (there's a thread discussing that), and the current proposal is to keep the "server-" prefix.

IMO that would be more intuitive for people used to the server tools single repo, and it would be helpful for these server features to be kept near each other in the repo list.

By the way, "infrastructure" sounds too broad to me. Most server-tools provide features that could be considered infrastructure.
Perhaps "server-connectivity"?

--
Daniel

No dia 25/08/2016, às 09:53, Eric Caudal <eric.caudal@elico-corp.com> escreveu:

I will take care of it tomorrow!

--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/25/2016 04:23 PM, Pedro M. Baeza (Tecnativa) wrote:
<blockquote cite="mid:CACSANCAhW5kva3PYMj-72W3hhJ48H9dzwpAEQ4+i03Yc6eY9vw@mail.gmail.com" type="cite">
Would you mind to make the honors?

2016-08-25 0:08 GMT+02:00 Eric Caudal <eric.caudal@elico-corp.com>:

OK: that was my idea of "infra-*".

I think infra/infrastructure is more meaningful so would suggest to remove the "server" part.

Whatever the name, we should be moving forward and create the repo.
--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/25/2016 01:38 AM, Pedro M. Baeza (Tecnativa) wrote:
<blockquote cite="mid:CACSANCCA2z2MJYLeERdHDN=+m5A_b0JAMeqC39i5sTETU=m39A@mail.gmail.com" type="cite">
Well, server prefix is only a way of classify the "area". We have sale, purchase, stock... and server means for me something like server related tasks, but I don't have problem in removing that part.

Regards.

2016-08-24 10:38 GMT+02:00 Eric Caudal <eric.caudal@elico-corp.com>:

Hi Pedro,

I am ok to your solution and the split.

One question though, why the name "server-infrastructure"?


Could we have better something like "infrastructure" or "infra" like I suggested? (I don't understand the "server" part which could be limiting in meaning)
--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/24/2016 03:53 PM, Pedro M. Baeza (Tecnativa) wrote:
<blockquote cite="mid:CACSANCBgddVY+=+bubNnoN95KEntz7hiDYiRmGjWm=d2AoQ9+A@mail.gmail.com" type="cite">
Splitting server-tools as proposed in the other thread, I prefer to put the main module (connector_dns) on server-infrastructure repo, and keep connector_dns_dnspod on l10n-china.

Regards.

2016-08-24 4:38 GMT+02:00 Landis Arnold <larnold@nomadic.net>:

The following seems related.  Seems some Email Management and alternatives to Odoo's catchall could be in order.  If nothing else then perhaps at least some smooth ways to use Postfix for such.

Shooting from the hip on this one.

Landis Arnold
Nomadic, Inc.

Office. 303.444.2336

Please excuse my mobile phone typos
From: Eric Caudal <eric.caudal@elico-corp.com>
Sent: Aug 23, 2016 4:38 PM
To: Contributors
Subject: Re: DNS Connector

Thanks Dave!


Any other opinion on the topic?

--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/24/2016 03:38 AM, Dave Lasley wrote:
<blockquote cite="mid:858A3A85-053F-45E8-8A1A-B133F1FAB98C@laslabs.com" type="cite">

This is great work, Eric! 


Back on track then, I am :+1 for connector-dns repo creation.

On Aug 20, 2016, at 6:53 PM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

Sure.

We have stored it in Chinese localization until we get an answer here (review welcome):

* connector_dns_dnspod: https://github.com/OCA/l10n-china/pull/22/files

* connector_dns: https://github.com/OCA/l10n-china/pull/24/files


--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/20/2016 11:08 PM, Dave Lasley wrote:
<blockquote cite="mid:2CB8DEFA-80F8-4264-9E66-200D97694690@laslabs.com" type="cite">

I prefer the `infra-` prefix for sure - also preferring option one; it just seems to clash with our other naming schemas for systems that connect to other systems. That said, this prefix opens us up for a whole slew of new module ideas!


Can you point me towards your base DNS connector code? I’d like to see how you’ve done things so I can make sure I am planning around the pre-existing wheel :)

On Aug 19, 2016, at 11:23 PM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

I tend to group rather by function than by technical aspect but both could be possible:

Option 1:

* infra-dns

* infra-amazon

* infra-azurre

* infra-lan

* infra-certs


Option 2:

* connector-dns

* infra-amazon

* infra-azurre

* infra-lan

* infra-certs


Personally prefers option 1.


Any other opinion? (about whether this is useful and the naming)

--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/20/2016 12:53 PM, Dave Lasley wrote:
<blockquote cite="mid:6803CA18-D0C8-48CD-A900-9ECE82F44715@laslabs.com" type="cite">

I like this idea. This way our Amazon whatnots could still be in a similar namespace, but just require the DNS. It would also let us start with the repo that does exist - DNS, then work out from there.


Should we still be including a connector- prefix? This seems to be the commonality between any OCA repo that connects with an outside interface.

On Aug 19, 2016, at 6:38 PM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

Maybe we would need one or several repos related to infrastructure like:

infra-dns

infra-amazon

infra-azurre

infra-lan

infra-certs

etc.


Not that we need to create them all at once but based on our current need that might make sense.


--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/20/2016 08:53 AM, Dave Lasley wrote:
<blockquote cite="mid:5CD268B6-33B0-414A-BF59-63C92E2049B0@laslabs.com" type="cite">

Apologies, I probably should have included my reasoning from the get go!


Along with our Route 53 connector, which you seem to have helped out with a lot, we are also planning on integration with other AWS services. The main five we were going for were:

  • Route 53
  • EC2
  • ECS
  • VPC
  • Cert Manager

We were going to be requiring odoo-connector as part of the plans.

I assume we’re targeting for repos of maybe 15-20 modules, so maybe expanding the scope would be a bad thing. I guess the larger question is whether more of these are in the works?

On Aug 19, 2016, at 5:23 PM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

Hi Dave,

What would be the scope of the repo?

connector-dns: any related connector to dns provider (actually using or not the odoo-connector framework)

What other functions would you like to see there? Openstack? SSL certificates, etc?


I am not against but we would need a clear scope


--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/20/2016 07:23 AM, Dave Lasley wrote:
<blockquote cite="mid:C6968C54-8F39-41B6-9952-9712CA4E9C21@laslabs.com" type="cite">

If we do create a repo for this, I propose we broaden the scope a bit. Maybe something like connector-infrastructure? 


On Aug 19, 2016, at 4:08 PM, Houssine BAKKALI <houssine.bakkali@gmail.com> wrote:

thank you for clarifying this!

2016-08-20 0:38 GMT+02:00 Eric Caudal (Elico Corp) <eric.caudal@elico-corp.com>:
It does depend on the odoo-connector framework



Eric Caudal from my mobile device


-------- Original message --------
From: Houssine BAKKALI <houssine.bakkali@gmail.com>
Date: 2016/08/19 22:38 (GMT+08:00)
To: Contributors <contributors@odoo-community.org>
Subject: Re: DNS Connector

Hi Eric,

This is a great job.

Just one question does your module depend on the connector? if not calling it connector dns could be misleading don't you think?

2016-08-19 8:08 GMT+02:00 Eric Caudal <eric.caudal@elico-corp.com>:

Hi,

We have developed time ago a DNS connector framework and created a specific one for dnspod.cn.

Basically it allows to manage all your domain in the ERP and trigger API calls to the DNS provider via Odoo framework.

We have 2 main modules currently in v8 (we will migrate them eventuallyto v9):

* connector_dns which creates the basic objects related to domain management

* connector_dnspod which is specific to dnspod.cn provider (create/delete update DNS Entries)


We plan to have as well another one for dnspod.com

Today there is repo for this kind of connector in the OCA: would it make sense to create a connector_dns to host them?

Looking forward to reading you
--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


Reference