From kennelson11 at gmail.com  Mon Mar  7 19:59:30 2022
From: kennelson11 at gmail.com (Kendall Nelson)
Date: Mon, 7 Mar 2022 11:59:30 -0800
Subject: [Rust-VMM] Fwd: Reminder! PTG April 2022 Team Signup Deadline
In-Reply-To: <CAJ6yrQhTyxYO-VWOy4tyN6GjwTMrpJvh_tQZ0V=Jrq9osJntaQ@mail.gmail.com>
References: <CAJ6yrQhTyxYO-VWOy4tyN6GjwTMrpJvh_tQZ0V=Jrq9osJntaQ@mail.gmail.com>
Message-ID: <CAJ6yrQjVwVW77T5agY8Zy2XtN5KFLxB0GqjpQXYKmkUHWr6fmw@mail.gmail.com>

Hello Everyone,

Don't forget to sign your team up for the next Project Teams Gathering
(PTG), which will be held virtually from Monday, April 4 to Friday, April
8, 2022!

If you haven't already done so and your team is interested in
participating, please complete BOTH the survey[1] AND reserve time in the
ethercalc[2] by end of day March 11.

Then make sure to register[3] for the PTG because that's how you'll receive
event details, passwords, and other relevant information about the PTG.

Thanks!

-Kendall (diablo_rojo)

[1] Team Survey:
https://openinfrafoundation.formstack.com/forms/april2022_vptg_survey
[2] Ethercalc Signup: https://ethercalc.openstack.org/7yxdas7suqnd
[3] PTG Registration: https://openinfra-ptg.eventbrite.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20220307/7c7a616a/attachment.htm>

From kennelson11 at gmail.com  Mon Mar 21 21:53:15 2022
From: kennelson11 at gmail.com (Kendall Nelson)
Date: Mon, 21 Mar 2022 16:53:15 -0500
Subject: [Rust-VMM] Fwd: Forum Submissions Open for Berlin Summit 2022!
In-Reply-To: <CAJ6yrQgc+1a0+t4fWfBy+4dZ_Re7rK8zgQM+yVFENTwQXp60Qw@mail.gmail.com>
References: <CAJ6yrQgc+1a0+t4fWfBy+4dZ_Re7rK8zgQM+yVFENTwQXp60Qw@mail.gmail.com>
Message-ID: <CAJ6yrQiGPscQ-xuEJp8J4M_tVFvsNLLRcQGZjUJOmWFqFo1W5Q@mail.gmail.com>

Hello Everyone!

We are now accepting Forum [1] submissions for the 2022 Open Infrastructure
Summit Forum [2].  Please submit your ideas through the Summit CFP tool [3]
through April 8th.  Don't forget to put your brainstorming etherpad up on
the Berlin Forum page [4].

This is not a classic conference track with speakers and presentations.
OpenInfra community members (participants in development teams, operators,
working groups, SIGs, and other interested individuals) discuss the topics
they want to cover and get alignment on and we welcome your participation.
The Forum is your opportunity to help shape the development of future
project releases. More information about the Forum [1].

The timeline for submissions is as follows:

March 21st | Formal topic submission tool opens: https://cfp.openstack.org.
April 8th | Deadline for proposing Forum topics. Scheduling committee
meeting to make draft agenda.
April 15th | Draft Forum schedule published. Crowd sourced session conflict
detection. Forum promotion begins.
April 22nd | Forum schedule final
June 20th | Forum begins!

If you have questions or concerns, please reach out to
speakersupport at openinfra.dev.

Cheers,
- Kendall Nelson (diablo_rojo)

[1] https://wiki.openstack.org/wiki/Forum
[2] https://openinfra.dev/summit
[3] https://cfp.openstack.org
[4] https://wiki.openstack.org/wiki/Forum/Berlin2022
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20220321/f2b17bb4/attachment.htm>

From kennelson11 at gmail.com  Mon Mar 21 22:03:33 2022
From: kennelson11 at gmail.com (Kendall Nelson)
Date: Mon, 21 Mar 2022 17:03:33 -0500
Subject: [Rust-VMM] Forum Submissions Open for Berlin Summit 2022!
In-Reply-To: <CAJ6yrQiGPscQ-xuEJp8J4M_tVFvsNLLRcQGZjUJOmWFqFo1W5Q@mail.gmail.com>
References: <CAJ6yrQgc+1a0+t4fWfBy+4dZ_Re7rK8zgQM+yVFENTwQXp60Qw@mail.gmail.com>
 <CAJ6yrQiGPscQ-xuEJp8J4M_tVFvsNLLRcQGZjUJOmWFqFo1W5Q@mail.gmail.com>
Message-ID: <CAJ6yrQj7pcbhf6xwx7T7qaEBeE4EQ92c8DxsQ47XSdpgHD=e5Q@mail.gmail.com>

Correction :) Because... Mondays

The Forum starts June 7th!

Sorry for any confusion!

-Kendall

On Mon, Mar 21, 2022 at 4:53 PM Kendall Nelson <kennelson11 at gmail.com>
wrote:

> Hello Everyone!
>
> We are now accepting Forum [1] submissions for the 2022 Open
> Infrastructure Summit Forum [2].  Please submit your ideas through the
> Summit CFP tool [3] through April 8th.  Don't forget to put your
> brainstorming etherpad up on the Berlin Forum page [4].
>
> This is not a classic conference track with speakers and presentations.
> OpenInfra community members (participants in development teams, operators,
> working groups, SIGs, and other interested individuals) discuss the topics
> they want to cover and get alignment on and we welcome your participation.
> The Forum is your opportunity to help shape the development of future
> project releases. More information about the Forum [1].
>
> The timeline for submissions is as follows:
>
> March 21st | Formal topic submission tool opens: https://cfp.openstack.org
> .
> April 8th | Deadline for proposing Forum topics. Scheduling committee
> meeting to make draft agenda.
> April 15th | Draft Forum schedule published. Crowd sourced session
> conflict detection. Forum promotion begins.
> April 22nd | Forum schedule final
> June 20th | Forum begins!
>
> If you have questions or concerns, please reach out to
> speakersupport at openinfra.dev.
>
> Cheers,
> - Kendall Nelson (diablo_rojo)
>
> [1] https://wiki.openstack.org/wiki/Forum
> [2] https://openinfra.dev/summit
> [3] https://cfp.openstack.org
> [4] https://wiki.openstack.org/wiki/Forum/Berlin2022
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20220321/97178d2c/attachment.htm>

From stefanha at gmail.com  Wed Mar 16 13:16:24 2022
From: stefanha at gmail.com (Stefan Hajnoczi)
Date: Wed, 16 Mar 2022 13:16:24 -0000
Subject: [Rust-VMM] Call for GSoC and Outreachy project ideas for summer
 2022
In-Reply-To: <CAJSP0QVqvvN=sbm=XMT8mxHQNcSfNfTrnWJXXf-QgXwxAfzdcA@mail.gmail.com>
References: <CAJSP0QX7O_auRgTKFjHkBbkBK=B3Z-59S6ZZi10tzFTv1_1hkQ@mail.gmail.com>
 <244647ca-a247-cfc1-d0df-b8c74d434a77@amazon.com>
 <CAJSP0QVqvvN=sbm=XMT8mxHQNcSfNfTrnWJXXf-QgXwxAfzdcA@mail.gmail.com>
Message-ID: <CAJSP0QUZS=vcruOixYwsC_Nwy2mvgeemuJimSqv98KsKr4BdSQ@mail.gmail.com>

On Mon, 14 Feb 2022 at 13:58, Stefan Hajnoczi <stefanha at gmail.com> wrote:
>
> On Wed, 9 Feb 2022 at 14:50, Alexander Graf <graf at amazon.com> wrote:
> > On 28.01.22 16:47, Stefan Hajnoczi wrote:
> > > Dear QEMU, KVM, and rust-vmm communities,
> > > QEMU will apply for Google Summer of Code 2022
> > > (https://summerofcode.withgoogle.com/) and has been accepted into
> > > Outreachy May-August 2022 (https://www.outreachy.org/). You can now
> > > submit internship project ideas for QEMU, KVM, and rust-vmm!
> > >
> > > If you have experience contributing to QEMU, KVM, or rust-vmm you can
> > > be a mentor. It's a great way to give back and you get to work with
> > > people who are just starting out in open source.
> > >
> > > Please reply to this email by February 21st with your project ideas.
> > >
> > > Good project ideas are suitable for remote work by a competent
> > > programmer who is not yet familiar with the codebase. In
> > > addition, they are:
> > > - Well-defined - the scope is clear
> > > - Self-contained - there are few dependencies
> > > - Uncontroversial - they are acceptable to the community
> > > - Incremental - they produce deliverables along the way
> > >
> > > Feel free to post ideas even if you are unable to mentor the project.
> > > It doesn't hurt to share the idea!
> >
> >
> > I have one that I'd absolutely *love* to see but not gotten around
> > implementing myself yet :)
> >
> >
> > Summary:
> >
> > Implement -M nitro-enclave in QEMU
> >
> > Nitro Enclaves are the first widely adopted implementation of hypervisor
> > assisted compute isolation. Similar to technologies like SGX, it allows
> > to spawn a separate context that is inaccessible by the parent Operating
> > System. This is implemented by "giving up" resources of the parent VM
> > (CPU cores, memory) to the hypervisor which then spawns a second vmm to
> > execute a completely separate virtual machine. That new VM only has a
> > vsock communication channel to the parent and has a built-in lightweight
> > TPM.
> >
> > One big challenge with Nitro Enclaves is that due to its roots in
> > security, there are very few debugging / introspection capabilities.
> > That makes OS bringup, debugging and bootstrapping very difficult.
> > Having a local dev&test environment that looks like an Enclave, but is
> > 100% controlled by the developer and introspectable would make life a
> > lot easier for everyone working on them. It also may pave the way to see
> > Nitro Enclaves adopted in VM environments outside of EC2.
> >
> > This project will consist of adding a new machine model to QEMU that
> > mimics a Nitro Enclave environment, including the lightweight TPM, the
> > vsock communication channel and building firmware which loads the
> > special "EIF" file format which contains kernel, initramfs and metadata
> > from a -kernel image.
> >
> > Links:
> >
> > https://aws.amazon.com/ec2/nitro/nitro-enclaves/
> > https://lore.kernel.org/lkml/20200921121732.44291-10-andraprs at amazon.com/T/
> >
> > Details:
> >
> > Skill level: intermediate - advanced (some understanding of QEMU machine
> > modeling would be good)
> > Language: C
> > Mentor: Maybe me (Alexander Graf), depends on timelines and holiday
> > season. Let's find an intern first - I promise to find a mentor then :)
> > Suggested by: Alexander Graf
> >
> >
> > Note: I don't know enough about rust-vmm's debugging capabilities. If it
> > has gdbstub and a local UART that's easily usable, the project might be
> > perfectly viable under its umbrella as well - written in Rust then of
> > course.
>
> It would be great to have an open source Enclave environment for
> development and testing in QEMU.
>
> Could you add a little more detail about the tasks involved. Something
> along the lines of:
> - Implement a device model for the TPM device (link to spec or driver
> code below)
> - Implement vsock device (or is this virtio-mmio vsock?)
> - Add a test for the TPM device
> - Add an acceptance test that boots a minimal EIF payload
>
> This will give candidates more keywords and links to research this project.

Hi Alex,
Would you like me to add this project idea to the list? Please see
what I wrote above about adding details about the tasks involved.

Thanks,
Stefan


From graf at amazon.com  Wed Mar 16 13:36:24 2022
From: graf at amazon.com (Alexander Graf)
Date: Wed, 16 Mar 2022 13:36:24 -0000
Subject: [Rust-VMM] Call for GSoC and Outreachy project ideas for summer
 2022
In-Reply-To: <CAJSP0QUZS=vcruOixYwsC_Nwy2mvgeemuJimSqv98KsKr4BdSQ@mail.gmail.com>
References: <CAJSP0QX7O_auRgTKFjHkBbkBK=B3Z-59S6ZZi10tzFTv1_1hkQ@mail.gmail.com>
 <244647ca-a247-cfc1-d0df-b8c74d434a77@amazon.com>
 <CAJSP0QVqvvN=sbm=XMT8mxHQNcSfNfTrnWJXXf-QgXwxAfzdcA@mail.gmail.com>
 <CAJSP0QUZS=vcruOixYwsC_Nwy2mvgeemuJimSqv98KsKr4BdSQ@mail.gmail.com>
Message-ID: <da1dd6ee-6f3b-0470-cff3-9c2eb44d0ae6@amazon.com>

Hey Stefan!

On 16.03.22 14:16, Stefan Hajnoczi wrote:
> On Mon, 14 Feb 2022 at 13:58, Stefan Hajnoczi <stefanha at gmail.com> wrote:
>> On Wed, 9 Feb 2022 at 14:50, Alexander Graf <graf at amazon.com> wrote:
>>> On 28.01.22 16:47, Stefan Hajnoczi wrote:
>>>> Dear QEMU, KVM, and rust-vmm communities,
>>>> QEMU will apply for Google Summer of Code 2022
>>>> (https://summerofcode.withgoogle.com/) and has been accepted into
>>>> Outreachy May-August 2022 (https://www.outreachy.org/). You can now
>>>> submit internship project ideas for QEMU, KVM, and rust-vmm!
>>>>
>>>> If you have experience contributing to QEMU, KVM, or rust-vmm you can
>>>> be a mentor. It's a great way to give back and you get to work with
>>>> people who are just starting out in open source.
>>>>
>>>> Please reply to this email by February 21st with your project ideas.
>>>>
>>>> Good project ideas are suitable for remote work by a competent
>>>> programmer who is not yet familiar with the codebase. In
>>>> addition, they are:
>>>> - Well-defined - the scope is clear
>>>> - Self-contained - there are few dependencies
>>>> - Uncontroversial - they are acceptable to the community
>>>> - Incremental - they produce deliverables along the way
>>>>
>>>> Feel free to post ideas even if you are unable to mentor the project.
>>>> It doesn't hurt to share the idea!
>>>
>>> I have one that I'd absolutely *love* to see but not gotten around
>>> implementing myself yet :)
>>>
>>>
>>> Summary:
>>>
>>> Implement -M nitro-enclave in QEMU
>>>
>>> Nitro Enclaves are the first widely adopted implementation of hypervisor
>>> assisted compute isolation. Similar to technologies like SGX, it allows
>>> to spawn a separate context that is inaccessible by the parent Operating
>>> System. This is implemented by "giving up" resources of the parent VM
>>> (CPU cores, memory) to the hypervisor which then spawns a second vmm to
>>> execute a completely separate virtual machine. That new VM only has a
>>> vsock communication channel to the parent and has a built-in lightweight
>>> TPM.
>>>
>>> One big challenge with Nitro Enclaves is that due to its roots in
>>> security, there are very few debugging / introspection capabilities.
>>> That makes OS bringup, debugging and bootstrapping very difficult.
>>> Having a local dev&test environment that looks like an Enclave, but is
>>> 100% controlled by the developer and introspectable would make life a
>>> lot easier for everyone working on them. It also may pave the way to see
>>> Nitro Enclaves adopted in VM environments outside of EC2.
>>>
>>> This project will consist of adding a new machine model to QEMU that
>>> mimics a Nitro Enclave environment, including the lightweight TPM, the
>>> vsock communication channel and building firmware which loads the
>>> special "EIF" file format which contains kernel, initramfs and metadata
>>> from a -kernel image.
>>>
>>> Links:
>>>
>>> https://aws.amazon.com/ec2/nitro/nitro-enclaves/
>>> https://lore.kernel.org/lkml/20200921121732.44291-10-andraprs at amazon.com/T/
>>>
>>> Details:
>>>
>>> Skill level: intermediate - advanced (some understanding of QEMU machine
>>> modeling would be good)
>>> Language: C
>>> Mentor: Maybe me (Alexander Graf), depends on timelines and holiday
>>> season. Let's find an intern first - I promise to find a mentor then :)
>>> Suggested by: Alexander Graf
>>>
>>>
>>> Note: I don't know enough about rust-vmm's debugging capabilities. If it
>>> has gdbstub and a local UART that's easily usable, the project might be
>>> perfectly viable under its umbrella as well - written in Rust then of
>>> course.
>> It would be great to have an open source Enclave environment for
>> development and testing in QEMU.
>>
>> Could you add a little more detail about the tasks involved. Something
>> along the lines of:


I must've completely missed your email, sorry :).


>> - Implement a device model for the TPM device (link to spec or driver
>> code below)
>> - Implement vsock device (or is this virtio-mmio vsock?)


Yeah, it's derived from Firecracker. So virtio-mmio for vsock.


>> - Add a test for the TPM device
>> - Add an acceptance test that boots a minimal EIF payload
>>
>> This will give candidates more keywords and links to research this project.
> Hi Alex,
> Would you like me to add this project idea to the list? Please see
> what I wrote above about adding details about the tasks involved.


Petre literally pointed me to the fact that the project did not end up 
on the wiki page a few hours ago. I added it and augmented the bits 
above. Please let me know if you see anything else missing! :)


Alex





Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879



From stefanha at gmail.com  Tue Mar 29 20:30:10 2022
From: stefanha at gmail.com (Stefan Hajnoczi)
Date: Tue, 29 Mar 2022 20:30:10 -0000
Subject: [Rust-VMM] Call for GSoC and Outreachy project ideas for summer
 2022
In-Reply-To: <da1dd6ee-6f3b-0470-cff3-9c2eb44d0ae6@amazon.com>
References: <CAJSP0QX7O_auRgTKFjHkBbkBK=B3Z-59S6ZZi10tzFTv1_1hkQ@mail.gmail.com>
 <244647ca-a247-cfc1-d0df-b8c74d434a77@amazon.com>
 <CAJSP0QVqvvN=sbm=XMT8mxHQNcSfNfTrnWJXXf-QgXwxAfzdcA@mail.gmail.com>
 <CAJSP0QUZS=vcruOixYwsC_Nwy2mvgeemuJimSqv98KsKr4BdSQ@mail.gmail.com>
 <da1dd6ee-6f3b-0470-cff3-9c2eb44d0ae6@amazon.com>
Message-ID: <CAJSP0QVrhzuso+=Wdt=mnkc04L332cnW4BmOL-OqA3e8cQCrnw@mail.gmail.com>

On Wed, 16 Mar 2022 at 13:36, Alexander Graf <graf at amazon.com> wrote:
> Petre literally pointed me to the fact that the project did not end up
> on the wiki page a few hours ago. I added it and augmented the bits
> above. Please let me know if you see anything else missing! :)

Thanks for posting it!

Stefan