cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jessica Tomechak (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1478) Document baremetal kickstart
Date Sat, 16 Mar 2013 20:38:12 GMT


Jessica Tomechak commented on CLOUDSTACK-1478:

I have some text written for this. However, now I notice that bare metal hosts are not otherwise
documented at all. Is it right to add this without any other mention of bare metal in the
docs? Is this, alone, enough to get someone started with bare metal hosts?

CloudStack supports the kickstart installation method for RPM-based Linux operating systems
on baremetal hosts in basic zones. Users can provision a baremetal host managed by CloudStack
as long as they have the kickstart file and corresponding OS installation ISO ready.

Supported Features of Kickstart Baremetal Install

Security groups, as long as the baremetal security group agent is installed by the kickstart


Binding IP address allocated to VM to host when adding host. Then VM starting on that host
will be assigned to fixed IP.

Limitations of Kickstart Baremetal Install

When this feature is used, the following are not supported:

Use in advanced zones
CloudStack storage concepts: primary storage, secondary storage, volume, snapshot
System VMs: SSVM, CPVM, VR
Template copy or template download
VM migration
Multiple NICs
Using host tag for allocating host, capacity (cpu, memory) specifying in service offering
A stopped VM (the OS running on host) can only start on the host it was most recently on
> Document baremetal kickstart
> ----------------------------
>                 Key: CLOUDSTACK-1478
>                 URL:
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>            Reporter: Jessica Tomechak
>            Assignee: Jessica Tomechak
>            Priority: Minor
>             Fix For: 4.1.0

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message