sample gerrit setup with Akaros vmm

[ron minnich]

I've been feeling for some time that we'd have to break out applications for akaros from the akaros tree itself. It's a necessary part of the maturation process; not every program should be in the kernel source tree :-)

With that breakout would come the possibility of using a different workflow for commits and reviews.

See this: https://review.gerrithub.io/#/q/project:Akaros/vmm-akaros

for one such example. I've separated the VMM for Akaros from the Akaros tree, and set it up so that change management for it is now via gerrithub.io. Once our other VMM hacker (Gan) is on gerrithub we'll be managing the VMM code this way.

ron

[Barret Rhoden]

On 2015-11-10 at 06:07 ron minnich <rmin...@gmail.com> wrote:
> I've been feeling for some time that we'd have to break out
> applications for akaros from the akaros tree itself. It's a necessary
> part of the maturation process; not every program should be in the
> kernel source tree :-)

Agreed, in general, though I'm a little concerned about taking the VMM
out, given the tight coupling of the VMM with the kernel. It's this
same coupling that allows us to make changes to the kernel headers and
glibc at the same time.

We are far from having stable kernel interfaces, and I'm worried having
a different repo will make things more difficult. If we make changes
in Akaros to VMM code (such as the upcoming changes to treat VMs as
just another type of context), how do we test this? Do we need to sync
up between repos?

> With that breakout would come the possibility of using a different
> workflow for commits and reviews.

I think you two could have been doing that already - using gerrit to
manage virtio-r, but still as part of the main repo.

Barret

[ron minnich]

I got worried that we were starting to bake in things that might make it hard to make this separation later. We'll see how it goes. We can always bring it back in. But I'd like to have a clear understanding of how we support code that we don't want in the kernel repo itself. So far it's been very easy, which is a real credit to how you two set it up in the first place.

ron

[Barret Rhoden]

I'm all for the "let's try it out and see." =)

[ron minnich]

You can't shoot off your toes unless you are aiming for the stars.

ron

--
You received this message because you are subscribed to the Google Groups "Akaros" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akaros+un...@googlegroups.com.
To post to this group, send email to aka...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dan Cross]

That's not even wrong....

[Davide Libenzi]

Cool. How does that work? ☺

Any docs?

Is this one of the standard processes within kernel or google in general?

--

[Edward Hyunkoo Jee]

I guess we will eventually need to separate various components (kernel, toolchain, libraries, etc) from each other. As I mentioned before, I feel that Android "repo" might be a good tool for Akaros. It helps manage and synchronize multiple Git repositories that compose a platform.

Android is developed internally first, and then released as open source. Meanwhile it also accepts and merge external contributors' changes. This complex merging model might be a good fit for Akaros.

[ron minnich]

Sign in to gerrithub.io, tell me your id, and I'll add you to the Akaros group.

ron