All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajiv Ranganath <rajiv.ranganath@atihita.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Subject: Re: [stage1-xen PATCH v1 06/10] build/fedora: Add `xen-unstable-runit/*` scripts
Date: Wed, 13 Sep 2017 10:39:28 +0530	[thread overview]
Message-ID: <m2mv5z422f.fsf@atihita.com> (raw)
In-Reply-To: <b16b5b53-88d6-ff2d-2c3b-2de7b0a43335@citrix.com>


On Tue, Sep 12 2017 at 04:38:19 AM, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> On 11/09/2017 21:20, Stefano Stabellini wrote:

[...]

>> My only concern is about diverging from the upstream Xen codebase. I
>> think the runit scripts should call xencommons underneath. If xencommons
>> cannot cope with being called from runit, we could make changes to
>> xencommon in xen.git to make it so.
>>
>> Otherwise, we will end up in a situation such as:
>> - xen.git changes xencommons
>> - we don't notice
>> - we upgrade Xen version
>> - stage1-xen doesn't work anymore
>>
>> If we used xencommons underneath we would avoid this, and it looks like
>> xencommons could be made to work well with runit.
>
> If possible, upstream Xen should be made to be compatible with runit
> (this would be the ideal case). If not, upstream Xen should contain
> different styles of these files, which are selected between by a
> ./configure option (this is suboptimal, but better than locally
> forking). This offers the greatest chance that updates to one don't
> cause the other to be stale.

I agree that it would be beneficial to have upstream Xen support for
runit. However, runit is packaged differently in every distro.

We work around this issue by packaging our own version of runit [1].
Fedora does not include runit in its repositories. That helps because we
don't have to worry about conflicting with distro packaged runit.

One option to consider is for xen project to package its own version of
runit for major distros (we will have one for Fedora in stage1-xen), and
use that as the basis for runit support.

Since stage1-xen is still under development, maybe we can use runit in
stage1-xen as a testing ground. If things work out well, we can then see
how best to integrate with xencommons or add a configure option.

By then we will also know if there is broader community interest in
having runit support in xen.

As to changes to xencommons breaking stage1-xen, as we get closer to
stable release, we probably will have integration tests to catch this
and many other things! :-)

Best,
Rajiv

[1]: https://github.com/lambda-linux-fedora/runit/tree/ver-2.1.2-1.1.fc25

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-09-13  5:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-27  3:00 [stage1-xen PATCH v1 00/10] Add Fedora support Rajiv Ranganath
2017-08-27  3:00 ` [stage1-xen PATCH v1 01/10] .gitignore: Add Rajiv Ranganath
2017-09-06 18:42   ` Stefano Stabellini
2017-08-27  3:00 ` [stage1-xen PATCH v1 02/10] build/fedora: Add `buildroot-README.md` Rajiv Ranganath
2017-09-06 18:43   ` Stefano Stabellini
2017-08-27  3:00 ` [stage1-xen PATCH v1 03/10] build/fedora: Add `buildroot-Dockerfile` Rajiv Ranganath
2017-09-06 18:43   ` Stefano Stabellini
2017-08-27  3:00 ` [stage1-xen PATCH v1 04/10] build/fedora: Add `run` and `components/*` scripts Rajiv Ranganath
2017-09-06 18:59   ` Stefano Stabellini
2017-09-09  2:04     ` Rajiv Ranganath
2017-09-11 20:06       ` Stefano Stabellini
2017-09-13  5:17         ` Rajiv Ranganath
2017-09-13 21:23           ` Stefano Stabellini
2017-08-27  3:01 ` [stage1-xen PATCH v1 05/10] build/fedora: Add `source_path.sh` Rajiv Ranganath
2017-08-27  3:01 ` [stage1-xen PATCH v1 06/10] build/fedora: Add `xen-unstable-runit/*` scripts Rajiv Ranganath
2017-09-06 18:40   ` Stefano Stabellini
2017-09-09  1:51     ` Rajiv Ranganath
2017-09-11 20:20       ` Stefano Stabellini
2017-09-11 23:08         ` Andrew Cooper
2017-09-13  5:09           ` Rajiv Ranganath [this message]
2017-08-27  3:01 ` [stage1-xen PATCH v1 07/10] .circleci/config.yml: Add Rajiv Ranganath
2017-09-06 19:05   ` Stefano Stabellini
2017-08-27  3:01 ` [stage1-xen PATCH v1 08/10] README.md: Add CircleCI badge Rajiv Ranganath
2017-09-06 18:44   ` Stefano Stabellini
2017-08-27  3:01 ` [stage1-xen PATCH v1 09/10] build/fedora: Add `RUNNING_STAGE1_XEN.md` Rajiv Ranganath
2017-09-06 19:14   ` Stefano Stabellini
2017-09-09  2:10     ` Rajiv Ranganath
2017-09-09  2:52       ` Rajiv Ranganath
2017-09-11 20:07       ` Stefano Stabellini
2017-08-27  3:01 ` [stage1-xen PATCH v1 10/10] BUILDING.md: Add Fedora instructions Rajiv Ranganath
2017-09-06 19:07   ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2mv5z422f.fsf@atihita.com \
    --to=rajiv.ranganath@atihita.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.