Consolidating w3up and upload-service

[alanshaw]

📚 Preview

[hannahhoward]

This sounds involved enough that it should happen BEFORE we monorepo. Do you agree? (otherwise the merge could be complicated)

Am I correct that this would actually have the prod network working with the routing protocol? (just data would ONLY go to a single SP running CARPARK)

Overall makes sense if we can implement quickly. Is this something you can get help with or would it be just you? Maybe @fforbeck or @Peeja ?

[alanshaw]

This sounds involved enough that it should happen BEFORE we monorepo. Do you agree? (otherwise the merge could be complicated)

Yes agree.

Am I correct that this would actually have the prod network working with the routing protocol? (just data would ONLY go to a single SP running CARPARK)

Correct 😄

Overall makes sense if we can implement quickly. Is this something you can get help with or would it be just you? Maybe @fforbeck or @Peeja ?

I'd be happy to take this on and get it done ASAP.

It would make sense for the work to port changes from w3up to upload-service and to alter existing modules to import @storacha equivalents to be tackled concurrently by @fforbeck and/or @Peeja. Implementing the "maintenance mode" switch would also be useful to delegate.

[fforbeck]

@alanshaw / @hannahhoward - Happy to help! I just need to wrap up the egress rollout, and then I’ll be ready to jump into the next task.

[alanshaw]

@Peeja @fforbeck @hannahhoward FYI I've updated the migration strategy (write to both) and removed the task to create a maintenance switch. I'll merge this now and create an issue in the project planning with the task/people allocations we discussed.