Dave Lasley

@pedrobaeza - We were actually thinking of hooking into this at the product_brand level, but that's mainly because I didn't know about the product_manufacturer module. Seems like a why not...

👍

While abstracting out the container management, it would be nice if we also considered Amazon ECS as a potential runner.

I haven't actually dug into the DNS controllers yet, but it would be nice to support Route53 instead of just bind. Check these out: - [infrastructure-dns/connector_dns](https://github.com/OCA/infrastructure-dns/pull/6) - [preliminary Route53 connector...

Sweet I look forward to the PoC. Also agree on the need for an incubator branch, what if we consider it as a v10 incubator? Major version increments are the...

Maybe the completion of the incubator is the right time for the OCA migration too? Starting with a fresh production in a fresh repo will make it even more clear...

We have incredible buy-in (3-4 delegates), so I'm certain it's happening. We won't be able to move it in before we fix things like the #141 & some other OCA...

Hmmm so maybe an implementation using [LibCloud](https://libcloud.readthedocs.io/en/latest/dns/index.html), then a simple selection to determine the [driver for the intended service](https://libcloud.readthedocs.io/en/latest/dns/supported_providers.html)

Regarding external services, I think the way to manage them is via the Connector libraries. We can be naive of the external service itself, simply providing a dummy model like...

Damn I love it when things are convenient! Rare case right here so let us take the time to revel in it 😆 🎉 🌮 cc @t3ddftw