CFV: New Project: CRaC

[Anton Kozlov]

The voting period is over. Looking back, I understand concerns that are
associated with the project, technical and organizational ones. I hope my
answers on those were clear, and I'll do my best to align actions with them.

The CRaC Project is a research project without defined success metrics, at
least for now. The proposed initial implementation is just the
proof-of-concept, and likely it will change. If you have another related work,
please bring it, and we'll see how to combine the best of them.

I have underestimated the interest of the community in the project. I hoped
that people would like to contribute. But I have not expected the initial set
of contributors would be very important since it always can grow. We are
welcome anyone willing to contribute, by a code, review, or advice, now or in
the future. For the status, a record in the JDK project looks to be a good
enough qualification for the CRaC project for a person willing to contribute.
Another CRaC-like or related implementation too.

If I'd be composing the CFV now, I would end up with the same result. I would
add more initial contributors, but I don't have names. So the most
straightforward action now is to announce voting results. Meanwhile, I'll look
at what I can do to involve more people.

Thanks,
Anton

On 7/30/21 10:17 PM, Anton Kozlov wrote:
> I hereby propose the creation of the CRaC Project with myself, Anton Kozlov,
> as the Lead and the HotSpot Group as the sponsoring Group.
> 
> The CRaC (Coordinated Restore at Checkpoint) [1] project will research
> coordination of Java programs with mechanisms to checkpoint (make an image of,
> snapshot) a Java instance while it is executing.  Restoring from the image
> could be a solution to some of the problems with the start-up and warm-up
> times.  The primary aim of the project is to develop a new standard
> mechanism-agnostic API to notify Java programs about the checkpoint and restore
> events.  Other research activities will include, but will not be limited to,
> integration with existing checkpoint/restore mechanisms and development of new
> ones, changes to JVM and JDK to make images smaller and ensure they are
> correct.
> 
> The existing proof-of-concept implementation based on the OpenJDK [2] will be a
> starting point of the project.
> 
> I work at Azul developing JVM and JDK, focusing on bug fixing, support of new
> platforms, and start-up/warm-up optimizations.  I'm a co-author of JEP-391 and
> author of the CRaC proof-of-concept implementation.
> 
> Initial Committers and Reviewers are:
> Volker Simonis (Committer)
> Anton Kozlov (Reviewer)
> 
> Votes are due by Friday, 13 August 2021, 20:00:00 GMT.
> 
> Only current OpenJDK Members [3] are eligible to vote on this
> motion.  Votes must be cast in the open on the discuss list.
> Replying to this message is sufficient if your mail program
> honors the Reply-To header.
> 
> For Lazy Consensus voting instructions, see [4].
> 
> Anton Kozlov
> 
> [1] https://mail.openjdk.java.net/pipermail/discuss/2021-July/005862.html
> [2] https://github.com/CRaC/jdk
> [3] https://openjdk.java.net/census#members
> [4] https://openjdk.java.net/projects/#new-project-vote
>