COMPLETED - DOCUMENT IN TICKET
do we plan to create more consistency between databases, environments, and naming schemas during this migration? that might help us know what is what.
ANSWER: We have not discussed that yet, but I agree, I think better names are necessary.
ANSWER: appname-prod or appname-test
COMPLETED - CREATE TICKET
do we plan to document all of these databases and their associated servers as part of this move?
ANSWER: CB has a todo to start that work for a meeting with the database team next week. We can continue that forward as a deliverable for closeout. CB has spreadsheet
CONFIRMING - CREATE/DOCUMENT IN TICKET
finally will all the applications have to move to the cloud, or are we assuming no they don't need to we're just moving databases?
ANSWER: OIT has not asked us to move the applications to the cloud, only the databases. They have asked for IP addresses to make the databases available to the application servers, so I do not expect changes there. OIT has only talked about moving the MySQL databases to the the cloud, not Oracle, which is a point I want clarification on. Moving the Oracle database would (I assume) run into issues with the Rushdie deposit agreement.
1.) The Fedora (oracle db) migration effort will result in our oracle databases staying on-premise and NOT moving to AWS. Is that correct?
[SD]: As of now we are doing the on-prem upgrade using the VM. But eventually, all the on-prem infra needs to be migrated to the cloud unless there are some technical or legal issues.
2.) Are there any costs (or changes to costs) that we need to address in the oracle db migration project (i.e. speedtype provision etc.)
[SD]: Yes. For the billing we tagged every on-prem VM or the RDS instance with the concern application speed type. The system team also charges a flat monthly fee or sysadmin charge of $158 every month. Please reach out to the System team (Steve Siegelman) if you want to know the exact cost for your on-prem infrastructure.
COMPLETED - DOCUMENT IN TICKET do we plan to create more consistency between databases, environments, and naming schemas during this migration? that might help us know what is what.
ANSWER: We have not discussed that yet, but I agree, I think better names are necessary. ANSWER: appname-prod or appname-test
COMPLETED - CREATE TICKET do we plan to document all of these databases and their associated servers as part of this move? ANSWER: CB has a todo to start that work for a meeting with the database team next week. We can continue that forward as a deliverable for closeout. CB has spreadsheet
CONFIRMING - CREATE/DOCUMENT IN TICKET finally will all the applications have to move to the cloud, or are we assuming no they don't need to we're just moving databases? ANSWER: OIT has not asked us to move the applications to the cloud, only the databases. They have asked for IP addresses to make the databases available to the application servers, so I do not expect changes there. OIT has only talked about moving the MySQL databases to the the cloud, not Oracle, which is a point I want clarification on. Moving the Oracle database would (I assume) run into issues with the Rushdie deposit agreement.
1.) The Fedora (oracle db) migration effort will result in our oracle databases staying on-premise and NOT moving to AWS. Is that correct? [SD]: As of now we are doing the on-prem upgrade using the VM. But eventually, all the on-prem infra needs to be migrated to the cloud unless there are some technical or legal issues.
2.) Are there any costs (or changes to costs) that we need to address in the oracle db migration project (i.e. speedtype provision etc.) [SD]: Yes. For the billing we tagged every on-prem VM or the RDS instance with the concern application speed type. The system team also charges a flat monthly fee or sysadmin charge of $158 every month. Please reach out to the System team (Steve Siegelman) if you want to know the exact cost for your on-prem infrastructure.