search

meltano / handbook

Source for Meltano's public handbook (https://handbook.meltano.com/) and public issue tracker for process and policy proposals that will be documented there.
MIT License
3 stars 4 forks source link

Migrate DNS and NS management to Engineering, esp. Snowplow, including process docs for maintaining #59

Open MeltyBot opened 2 years ago

MeltyBot commented 2 years ago

Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/65

Originally created by @afolson on 2022-03-01 00:37:57

I've moved DNS hosting from SiteGround to Route 53 and need to update the handbook. This should also include documenting the sp NS records per https://gitlab.com/meltano/marketing/website/-/issues/11#note_855914523

therebbie commented 1 year ago

@afolson I see that Route 53 is documented in the handbook. I'm not sure what you mean above re: the sp NS records. There is no reference in the linked issue to that. There is a reference to here that says to make sure to document the differences for sp and why -- though there is no detail given. I will note that the NS records for sp are different, though:

sp.meltano.com. 21600 IN NS ns-1020.awsdns-63.net. sp.meltano.com. 21600 IN NS ns-1191.awsdns-20.org. sp.meltano.com. 21600 IN NS ns-2013.awsdns-59.co.uk. sp.meltano.com. 21600 IN NS ns-355.awsdns-44.com.

and

meltano.com. 21600 IN NS ns-1488.awsdns-58.org. meltano.com. 21600 IN NS ns-1953.awsdns-52.co.uk. meltano.com. 21600 IN NS ns-309.awsdns-38.com. meltano.com. 21600 IN NS ns-709.awsdns-24.net.

aaronsteers commented 1 year ago

@magreenbaum - I'm assigning this to you but you can also delegate to another team member if someone else is able to pick up. This is one area where @afolson jumped in to help us get this set up, but we really should be owning in Engineering long-term. This was originally created solely as a 'process docs' issue in the Handbook repo, but feel free to open an infra-side issue as well if consolidation is helpful in long-term management.

magreenbaum commented 1 year ago

@aaronsteers @afolson No problem moving this to engineering. I do have a few questions about it.

afolson commented 1 year ago

@tayloramurphy @pnadolny13 You all set Snowplow up right? sp.* was just delegated to snowplow to manage DNS or something right? How is that managed?

aaronsteers commented 1 year ago

Cc @WillDaSilva, @pnadolny13 in case they have additional context.

tayloramurphy commented 1 year ago

@magreenbaum I've invited you to the snowcatcloud channel in slack which has more info on the snowplow domain

magreenbaum commented 1 year ago

Thanks @tayloramurphy for adding me to that channel. So we're just setting our NS records for sp.meltano.com to allow snowcatcloud to host the DNS record is my understanding.

therebbie commented 1 year ago

@magreenbaum As part of this effort I'd like to make sure we at least consider all of our domains. The complete list is here. Ideally we would have all of these with a single registrar (not, alas, possible), and a single DNS provider.

magreenbaum commented 1 year ago

@therebbie sounds good. I'll update the docs for this issue as needed and then move the rest to an internal issue (around migrating to a single DNS provider).

magreenbaum commented 8 months ago

Heads up @cjohnhanson, I've removed my assignment.