[FOLIO-3338] Transfer hosted domain aws.indexdata.com to Index Data Created: 08/Nov/21  Updated: 05/May/23

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: John Malconian Assignee: John Malconian
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 130, DevOps Sprint 131, Kitfox: sprint 165, DevOps Sprint 127, DevOps Sprint 128, DevOps sprint 132, DevOps Sprint 129, DevOps Sprint 133
Development Team: FOLIO DevOps

 Description   

The Route 53 hosted domain, aws.indexdata.com, is part of the AWS folio-org account, but should be transferred back to Index Data. The zone file should also be cleaned up to include only hosts that are currently in-use.



 Comments   
Comment by John Malconian [ 08/Nov/21 ]

Zone file cleaned up. There are 4 host records remaining:

  • jenkins.aws.indexdata.com
  • nexus.aws.indexdata.com
  • folio-registry.aws.indexdata.com
  • rancher-bastion.aws.indexdata.com

These should be migrated to the dev.folio.org domain. folio-registry has already been migrated.

Comment by John Malconian [ 08/Nov/21 ]

Note to self: Remember to clean up load balancer groups and load balancer listeners - including in folio-infrastucture/CI/ansible where appropriate.

Comment by Marc Johnson [ 02/Mar/22 ]

John Malconian

There are 4 host records remaining:

jenkins.aws.indexdata.com
nexus.aws.indexdata.com
folio-registry.aws.indexdata.com
rancher-bastion.aws.indexdata.com
These should be migrated to the dev.folio.org domain. folio-registry has already been migrated.

Does this mean that the addresses for all of these are going to be changing imminently?

If so, how is this going to be communicated?

Comment by John Malconian [ 02/Mar/22 ]

Marc Johnson- My intention is to complete this work so that it is transparent to the community. However, if it is determined that a change will cause a disruption, I will confer with others to determine the best way to communicate those changes to the community.

Comment by Marc Johnson [ 02/Mar/22 ]

John Malconian

My intention is to complete this work so that it is transparent to the community.

That's good. How do you intend to do that, considering the *aws.indexdata.com domain will no longer be owned by the community and presumably will eventually stop being used for these resources?

However, if it is determined that a change will cause a disruption, I will confer with others to determine the best way to communicate those changes to the community.

Thank you.

Generated at Thu Feb 08 23:27:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.