Change Details

db1001 needs maintenance, or even decommissioning like db100[2-7]. To do that we need to perform an m1-master rotation to db1016. In the past this was a painful prospect due to the sheer number of services connecting directly to db1011, but m1-master CNAME and dbproxy1001 were added and services migrated to use them, so it should now be easier. However, big stuff is affected: * puppet * bacula * etherpad * racktables * librenms Needs planning or input from other Opsen.

db1001 needs maintenance, or even decommissioning like db100[2-7]. To do that we need to perform an m1-master rotation to db1016. In the past this was a painful prospect due to the sheer number of services connecting directly to db1001, but m1-master CNAME and dbproxy1001 were added and services migrated to use them, so it should now be easier. However, big stuff is affected: * puppet * bacula * etherpad * racktables * librenms Needs planning or input from other Opsen.

db1001 needs maintenance, or even decommissioning like db100[2-7]. To do that we need to perform an m1-master rotation to db1016. In the past this was a painful prospect due to the sheer number of services connecting directly to db101101, but m1-master CNAME and dbproxy1001 were added and services migrated to use them, so it should now be easier. However, big stuff is affected: * puppet * bacula * etherpad * racktables * librenms Needs planning or input from other Opsen.