Filter
Top Products
Chapter 13. Working with Templates
114
A default template is provided for each of XenServer, KVM, and vSphere. The templates that
are downloaded depend on the hypervisor type that is available in your cloud. Each template is
approximately 2.5 GB physical size.
The default template includes the standard iptables rules, which will block most access to the template
excluding ssh.
# iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT esp -- anywhere anywhere
ACCEPT ah -- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
REJECT all -- anywhere anywhere reject-with icmp-host-
13.5. Private and Public Templates
When a user creates a template, it can be designated private or public.
Private templates are only available to the user who created them. By default, an uploaded template is
private.
When a user marks a template as “public,” the template becomes available to all users in all accounts
in the user's domain, as well as users in any other domains that have access to the Zone where the
template is stored. This depends on whether the Zone, in turn, was defined as private or public. A
private Zone is assigned to a single domain, and a public Zone is accessible to any domain. If a public
template is created in a private Zone, it is available only to users in the domain assigned to that Zone.
If a public template is created in a public Zone, it is available to all users in all domains.
13.6. Creating a Template from an Existing Virtual Machine
Once you have at least one VM set up in the way you want, you can use it as the prototype for other
VMs.
1. Create and start a virtual machine using any of the techniques given in Section 11.4, “Creating
VMs”.
2. Make any desired configuration changes on the running VM, then click Stop.
3. Wait for the VM to stop. When the status shows Stopped, go to the next step.
4. Click Create Template and provide the following: