Feature #20982
closedWrite a blog post with highlights of new release
Added by Peter Amstutz 11 months ago. Updated 4 months ago.
Files
Screenshot from 2023-11-13 09-13-08.png (26.2 KB) Screenshot from 2023-11-13 09-13-08.png | Peter Amstutz, 01/02/2024 09:09 PM |
Updated by Brett Smith 11 months ago
At Thursday's meeting Sarah indicated she was interested in writing a post about the new features in Workbench 2.
I think it honesty might be cool to have two posts from two different perspectives, that one and then a more admin/cluster-level view of the scaling improvements.
Updated by Peter Amstutz 11 months ago
- Target version changed from Development 2023-09-27 sprint to Development 2023-10-11 sprint
Updated by Peter Amstutz 11 months ago
- Target version changed from Development 2023-10-11 sprint to Development 2023-10-25 sprint
Updated by Brett Smith 10 months ago
Updated by Peter Amstutz 10 months ago
- Target version changed from Development 2023-10-25 sprint to Development 2023-11-08 sprint
Updated by Peter Amstutz 10 months ago
- Target version changed from Development 2023-11-08 sprint to Development 2023-11-29 sprint
Updated by Peter Amstutz 9 months ago
- Target version changed from Development 2023-11-29 sprint to Development 2024-01-03 sprint
Updated by Peter Amstutz 8 months ago
Thoughts on what direction to go to make people more excited about Arvados when they read it.
I think maybe one place to start is who the audience is. Tentatively I'm going to suggest writing for people who want to learn a little bit more about the capabilities of Arvados and are technical but not familiar with the Arvados architecture. So then the goal of getting into technical details is to pull those people in (so it doesn't read like a fluff piece that asserts things without backing it up) without being overwhelming.
So perhaps instead of talking about 2.7 features specifically, I think we could start by talking about the kind of scale Arvados is designed for and being a little more specific about uses, e.g. our customers need to run a workflow that takes 4-6 hours on a batch of 2000 samples, and they want to get the results the next day, that's not an easy thing to do, but Arvados can do it. Then we can examine several specific approaches that we've had to develop to let us achieve that.
We should also try to provide more specific numbers -- the attached graph doesn't have any identifying information.
The section on container logs is pretty good, but I think we can take out the comparison to the old system and just keep the part where we talk about how we don't waste time transmitting logs that don't get viewed.
I think the section on request prioritization is also good.
Unfortunately talking about client request limiting and retries doesn't seem very exciting. Maybe replace it with new section(s) about arvados-dispatch-cloud and/or compute node local keepstore?
Updated by Peter Amstutz 8 months ago
- Target version changed from Development 2024-01-03 sprint to Development 2024-01-17 sprint
Updated by Peter Amstutz 7 months ago
- Target version changed from Development 2024-01-17 sprint to Development 2024-01-31 sprint
Updated by Peter Amstutz 7 months ago
- Target version changed from Development 2024-01-31 sprint to Development 2024-02-14 sprint
Updated by Peter Amstutz 6 months ago
- Target version changed from Development 2024-02-14 sprint to Development 2024-02-28 sprint
Updated by Peter Amstutz 6 months ago
- Target version changed from Development 2024-02-28 sprint to Development 2024-03-13 sprint
Updated by Peter Amstutz 5 months ago
- Target version changed from Development 2024-03-13 sprint to Development 2024-03-27 sprint
Updated by Peter Amstutz 5 months ago
- Target version changed from Development 2024-03-27 sprint to Development 2024-04-10 sprint
Updated by Peter Amstutz 5 months ago
- Target version changed from Development 2024-04-10 sprint to Development 2024-04-24 sprint
Updated by Peter Amstutz 4 months ago
- Status changed from In Progress to Closed