From: David Markey <admin@dmarkey.com>
To: George Shuklin <nge@narod.ru>
Cc: xen-devel@lists.xensource.com
Subject: Re: [XCP] automated installation of XCP
Date: Sat, 19 Jun 2010 16:32:47 +0100 [thread overview]
Message-ID: <AANLkTinY-EDHP5HJDIkjLcfdlYOIzvEp7E5me00Wjxfw@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilDOnNU6-wG91pUDbIoojpsefH83GLMykjy_rVL@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]
Actually this is more current
http://docs.vmd.citrix.com/XenServer/5.6.0/1.0/en_gb/installation.html#pxe_boot_install-pxe_answerfile
On 19 June 2010 16:31, David Markey <admin@dmarkey.com> wrote:
> http://docs.vmd.citrix.com/XenServer/4.0.1/installation/apcs02.html
>
> This should apply
>
>
> On 19 June 2010 15:40, George Shuklin <nge@narod.ru> wrote:
>
>> Good day.
>>
>> I wounder if XCP have an some way to perform unattended installation
>> (kickstart, preseed, etc)...
>>
>> If no solution available right now i think, for fast pool deploy, those
>> can be very important:
>>
>> * allow to point to some kind of 'answer file' at installation startup
>> * allow to specify a pool-join command.
>> * perform host synchronization with pool-wide settings, reflected to
>> host settings (VLAN creation, pdb initialization, etc).
>> * Allow network installation (kickstart-like) from PXE.
>>
>> Thank you.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2023 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-06-19 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 14:40 [XCP] automated installation of XCP George Shuklin
2010-06-19 15:31 ` David Markey
2010-06-19 15:32 ` David Markey [this message]
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=AANLkTinY-EDHP5HJDIkjLcfdlYOIzvEp7E5me00Wjxfw@mail.gmail.com \
--to=admin@dmarkey.com \
--cc=nge@narod.ru \
--cc=xen-devel@lists.xensource.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
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).