From: Ian Jackson <email@example.com> To: Andrew Cooper <firstname.lastname@example.org> Cc: email@example.com, "Edwin Török" <firstname.lastname@example.org>, "Christian Lindig" <email@example.com>, "Jürgen Groß" <firstname.lastname@example.org>, "Wei Liu" <email@example.com> Subject: Re: [OSSTEST PATCH 7/7] make-flight: Stripy xenstored Date: Fri, 22 Jan 2021 16:22:32 +0000 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Andrew Cooper writes ("Re: [OSSTEST PATCH 7/7] make-flight: Stripy xenstored"): > A couple of quick questions/observations. Does this cope in a sensible > way if, for whatever reason, the chosen daemon isn't present? That would depend on what you mean by "sensible". I think that given that we now think we support both on all architectures, "sensible" means "the tests fail if one of the xenstoreds doesn't build". And that's what this will do :-). > How hard would it be to add the 3rd option, stub-cxenstored into this > mix? It is just one other key in xencommons to tweak. We would presumably want to do that for a smaller set of tests, but yes, that could be done as a future enhancement. > SUPPORT.md doesn't appear to make any statements about the disposition > of xenstoreds, but stub-cxenstored is used by at least two major > downstreams so is obviously has security support in practice, and ought > to be tested. Looking at /etc/default/xencommons, I think that testing would be done by setting XENSTORETYPE=domain. Do we want to test stub C xentored or stub ocaml xenstored or both ? The config seems not to have a way to specify which. Do we build only one ? Ian.
next prev parent reply index Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-22 15:55 [OSSTEST PATCH 1/7] target_editfile_kvp_replace: Support changing multiple keys Ian Jackson 2021-01-22 15:55 ` [OSSTEST PATCH 2/7] target_editfile_kvp_replace: Add a bit of logging Ian Jackson 2021-01-22 15:55 ` [OSSTEST PATCH 3/7] ts-xen-install: Rename $commons_config_file Ian Jackson 2021-01-22 15:56 ` [OSSTEST PATCH 4/7] ts-xen-install: Break out @commons_config Ian Jackson 2021-01-22 15:56 ` [OSSTEST PATCH 5/7] ts-xen-install: Honour xenstored target var Ian Jackson 2021-01-22 15:56 ` [OSSTEST PATCH 6/7] mfi-common: Provide stripy_rand Ian Jackson 2021-01-22 15:56 ` [OSSTEST PATCH 7/7] make-flight: Stripy xenstored Ian Jackson 2021-01-22 16:07 ` Andrew Cooper 2021-01-22 16:22 ` Ian Jackson [this message] 2021-01-22 16:24 ` Jürgen Groß 2021-01-22 16:26 ` Ian Jackson 2021-01-22 16:29 ` Jürgen Groß 2021-01-22 16:29 ` Andrew Cooper 2021-01-22 17:37 ` [OSSTEST PATCH 7/7] make-flight: Stripy xenstored [and 2 more messages] Ian Jackson 2021-01-22 17:52 ` Andrew Cooper 2021-01-28 14:26 ` Ian Jackson 2021-01-22 16:11 ` [OSSTEST PATCH 7/7] make-flight: Stripy xenstored Christian Lindig 2021-01-22 16:36 ` Andrew Cooper 2021-01-22 16:40 ` Edwin Torok
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
Xen-Devel Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/xen-devel/0 xen-devel/git/0.git git clone --mirror https://lore.kernel.org/xen-devel/1 xen-devel/git/1.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 xen-devel xen-devel/ https://lore.kernel.org/xen-devel \ firstname.lastname@example.org email@example.com public-inbox-index xen-devel Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.xenproject.lists.xen-devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git