You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data (S3 Object Store) - Ewelina to Lead
Assets and Catalogs
What is backed up?
This is stored in Local drive, VM, External sources. We are hopeful we have most of the lost data.
What is the priority?
Probably references from any external sources
What is not backed up?
We will confirm this as part of 1)
MetaData - Garin to Lead
GitHub/EarthCODE Catalogue
Confirm no metadata is lost and we can re-use this?
This is currently no reason to suspect this is an issue.
This does assume that we use the same data location at CloudFerro?
We have asked CloudFerro if they can provide the same S3 instance location.
Scripts/Process - Ewelina to Lead
Do we have scripts to move data to S3 or is this done manually?
Yes, we have scripts with some manual effort
Confirm that we can just move data again without changing the existing metadata?
Yes we think so if CloudFerro can help above.
Assume that PPR script will be used later?
Yes, we have suggested some PPR scenarios to support this.
Environment - Garin to Lead
Can we use CloudFerro?
Assumes yes subject to clarification of operational procedures.
Can we use PRR?
Yes in parallel to S3. We have more info from Salvatore.
One possible bonus is that we can deploy the above products to PRR when the new script is ready.
CloudFerro alternate S3.
Not currently planned unless there are problems with 1)
Operational Stability - Garin to Lead
Review/Confirm CloudFerro Operational Procedures
See Meta Data point 2)
ESA PRR
When is PRR prototype app package available?
When is PRR production environment available?
What is the PRR SLA?
The text was updated successfully, but these errors were encountered:
Hi @edobrowolska,
I assigned this task to both of us, because it seemed easier and more flexible.
I used the core plan we worked on together earlier and I suggested the tasks that we each lead on.
I will arrange a catch-up on Thursday.
I created a simple excel file with the datasets to be resotred (attached here). Column F indicates the priority of the data to be restored. In two cases we are missing backup for the data itself - I will contact data providers to update us on the access to that assets. In the next step the catalog.json collection files will need to be restored-re-created. This will be next step on me to be checked. Missing-data-list.xlsx
EarthCODE Data Restore Plan
Data (S3 Object Store) - Ewelina to Lead
Assets and Catalogs
This is stored in Local drive, VM, External sources. We are hopeful we have most of the lost data.
Probably references from any external sources
We will confirm this as part of 1)
MetaData - Garin to Lead
GitHub/EarthCODE Catalogue
This is currently no reason to suspect this is an issue.
We have asked CloudFerro if they can provide the same S3 instance location.
Scripts/Process - Ewelina to Lead
Yes, we have scripts with some manual effort
Yes we think so if CloudFerro can help above.
Yes, we have suggested some PPR scenarios to support this.
Environment - Garin to Lead
Assumes yes subject to clarification of operational procedures.
Yes in parallel to S3. We have more info from Salvatore.
One possible bonus is that we can deploy the above products to PRR when the new script is ready.
Not currently planned unless there are problems with 1)
Operational Stability - Garin to Lead
See Meta Data point 2)
When is PRR prototype app package available?
When is PRR production environment available?
What is the PRR SLA?
The text was updated successfully, but these errors were encountered: