From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [OSSTEST PATCH] README.dev: Document things that are now handled by ansible in Mass
Date: Thu, 13 Sep 2018 17:56:38 +0100 [thread overview]
Message-ID: <20180913165638.5476-1-ian.jackson@eu.citrix.com> (raw)
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
README.dev | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/README.dev b/README.dev
index a8bfbb53..eff82350 100644
--- a/README.dev
+++ b/README.dev
@@ -92,14 +92,14 @@ Set up any necessary host properties:
For example, one might need something like this:
- $ ./mg-hosts setprops marilith-n4 -- dhcp-watch-method 'leases dhcp3 dns-cam1.uk.xensource.com:5556'
-
-(Many of these things are not needed in Massachusetts as the ansible
-playbook will provide it via an autogenerated config file - see above.)
+ $ ./mg-hosts setprops marilith-n4 -- dhcp-watch-method 'leases dhcp3 dns-cam1.uk.xensource.com:5556' # not needed in Mass
Set the firmware, if it's UEFI:
- $ ./mg-hosts setprops albana{0,1} -- Firmware uefi
+ $ ./mg-hosts setprops albana{0,1} -- Firmware uefi # not needed in Mass
+
+(Many of these things are not needed in Massachusetts as the ansible
+playbook will provide it via an autogenerated config file - see above.)
Create the tftp directory (must be done after firmware is set):
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-09-13 16:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180913165638.5476-1-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).