Configuration: UI ACCESS

1.To get access to CloudStack’s web interface, point your browser to the IP address of your machine e.g.
http://192.168.1.2:8080/client
2.The default username is ‘admin’, and the default password is ‘password’. ——->>> Login
Setting up a Zone:
1.Go to Infrastructure ® Zone and click on “add
zone” button.
2.Select “Core”, click on ‘Next’
3.Select “Advanced zone” and provide the following
configuration (leaving all other defaults):
Name : Zone1

IPV4 : 8.8.8.8

Internal DNS 1 : 192.168.139.2

Hypervisor : KVM
Setting up a Network:
1.On the next screen (Physical
network details), use the
defaults – we will use the
VLAN isolation method on a
single physical NIC (on the
host) that will carry all traffic
types (management, public,
guest) and
2.click “Next”.
Public traffic configuration:
Gateway - 192.168.139.2
(your VM gateway)
Netmask - 255.255.255.0
VLAN/VNI - leave blank
Start IP - 192.168.139.134
End IP - 192.168.139.164
Click on the “Add” button,
click on “Next”
Pod Configuration:

Name – e.g. Pod1

Reserved system gateway -
192.168.139. 2

Reserved system netmask -

255.255.255.0

Start reserved system IP -

192.168.139.165

Start reserved system IP -

192.168.139.195

Click on “Next”
Guest traffic:

VLAN/VNI range:
700-900

Click on “Next”
Create a cluster with the following:
Name – e.g. Cluster1
Click on “Next”
host:
Hostname - 192.168.139.133

( IP for virtual machine)

Username - root
Password: 123 (that you want to

give of your choice)

Click on “Next”
Add primary
storage:

Name – e.g. Primary1

Scope - Zone / Cluster
Protocol - NFS
Server - 192.168.139.2
(or whatever IP you have
set up for this machine)
Path is:

/export/primary

Click on “Next”
storage:

Provider - NFS

Name – e.g. Secondary1

Server - 192.168.139.2

(or whatever IP you have set

up for this machine)

Path -

/export/secondar
y

Click on “Next”
 Apache
cloudstack

STORAGE
AND
NETWORKIN
G
TABLE OF CONTENTS
• Storage
• Templates
• Networking
Add primary
storage:

Name – e.g. Primary1

Scope - Zone / Cluster
Protocol - NFS
Server - 192.168.139.2
(or whatever IP you have
set up for this machine)
Path is:

/export/primary

Click on “Next”
storage:

Provider - NFS

Name – e.g. Secondary1

Server - 192.168.139.2

(or whatever IP you have set

up for this machine)

Path -

/export/secondar
y

Click on “Next”
ADD PRIMARY
STORAGE- use NFS
or DFS
• CloudStack defines two types of storage: primary and
secondary.
• Primary storage can be accessed by either iSCSI or
NFS. Additionally, direct attached storage (DAS) may
be used for primary storage.
• Secondary storage is always accessed using NFS.
• Give name of the zone pod and cluster accordingly
• Protocol is NFS as you have created disk in linux with
that protocol
• Server will be your management server’s ip as your
storage is also on same area.
• Give path of the storage partition created earlier while
installing 45 steps.
ADD SECONDARY
STORAGE- use NFS only

• Files can be listed at a path on a secondary storage using

listImageStoreObjects command or via UI under “Browser” tab
for a secondary storage.
• Depending on the hypervisor, files and directories on a primary
storage will get associated with the cloudstack resources like
snapshots, volumes, templates, and ISOs.
• Provider is NFS as you have created disk in linux with that
protocol
• Server will be your management server’s ip as your storage is
also on same area.
• Give path of the storage partition created earlier while installing
 01

TEMPLATES
AND
ISO

BRAND GUIDELINES
2025
 01

How to add a
template-
1stly download
template
BRAND GUIDELINES
2025
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-
install-sys-tmplt -m /mnt/secondary -u
http://cloudstack.apt-get.eu/systemvm/4.11/systemvmtemplate-
4.11.1-kvm.qcow2.bz2 -h kvm -F

For template download- run above command as root user (sudo su)
It is of 300MB, will take some time to download.

See next slide after it is done

 After adding template, 01

goto UI, click on images.

Under images- template option- click
and see-template

May be not Ready but will take some

time
BRAND GUIDELINES
2025
TEMPLATES
A Template is a reusable configuration for Instances.
When Users launch Instances, they can choose from a list of
Templates in CloudStack.
Specifically, a Template is a virtual disk image that includes one of
a variety of operating systems, optional additional software such as
office applications, and settings such as access control to determine
who can use the Template. Each Template is associated with a
particular type of hypervisor, which is specified when the Template
is added to CloudStack.
 ISO
CloudStack supports ISOs and their attachment to Guest Instances.
An ISO is a read-only file that has an ISO/CD-ROM style file system. Users
can upload their ISOs and mount them on their Guest Instances.
ISOs are uploaded based on a URL.

A very light weight iso can be from core linux

http://tinycorelinux.net/15.x/x86/release/Core-current.iso

It is of 17MB file
ADD ISO
• ISO can be added from previous slide’s link
• URL needs to be of the iso to download
• Name, description of your choice
• Zone- all zones because anyone can access this
• OS type will be according to the iso
downloaded
• Rest details can be the default

• NOTE--- it takes time for your management

server to download the iso or templates, so it
will only be ready when it is completely
downloaded
COMPUTE OFFERINGS- it is under service offerings
A service offering is a set of virtual
hardware features such as CPU core count
and speed, memory, and disk size.
The CloudStack administrator can set up various offerings, and then end users choose from the available
offerings when they create a new Instance. Based on the user’s selected offering, CloudStack emits usage
records that can be integrated with billing systems.

Compute offerings may be “fixed”, “custom constrained” or “custom unconstrained”.

For the ease we will not create any compute offerings further
 DISK OFFERINGS
For a disk offering requires to create a disk menu for users
• Custom Disk Size: If checked, the user can set their own
disk size. If not checked, the root administrator must define
a value in Disk Size.
• Disk Size: Appears only if Custom Disk Size is not
selected. Define the volume size in GB (2^30 1GB =
1,073,741,824 Bytes).
• Provisioning type: The type of disk that should be
allocated. Valid values are thin, sparse, fat. When using the
VMWare hypervisor, these values are mapped to the
following vSphere disk provisioning types:
⚬ thin: Thin Provision
⚬ sparse: Thick Provision Lazy Zeroed
⚬ fat: Thick Provision Eager Zeroed
• The disk provisioning type strictness on VMWare is controlled with the zone level setting -
disk.provisioning.type.strictness. If set to true, the disk is created only when there is a suitable
storage pool that supports the disk provisioning type specified by the service/disk offering. If set
to false, the disk is created with a disk provisioning type supported by the pool. Default value is
false and this is currently supported for VMware only.
• Disk Size Strictness: The flag defines the size strictness of the volume created from this disk
offering. When flag is true, volume’s size cannot be changed.
• QoS Type 2: Three options: Empty (no Quality of Service), hypervisor (rate limiting enforced on
the hypervisor side), and storage (guaranteed minimum and maximum IOPS enforced on the
storage side). If leveraging QoS, make sure that the hypervisor or storage system supports this
feature.
• Custom IOPS 2: If checked, the user can set their own IOPS. If not checked, the root administrator can
define values. If the root admin does not set values when using storage QoS, default values are used
(the defauls can be overridden if the proper parameters are passed into CloudStack when creating the
primary storage in question).
• Min/Max IOPS 2: Appears only if storage QoS is to be used. Set a guaranteed minimum number of
IOPS to be enforced on the storage side.
• Hypervisor Snapshot Reserve 2: For managed storage only. This is a value that is a percentage of the
size of the data disk. For example: if the data disk is 20 GB and Hypervisor Snapshot Reserve is 200%,
 NETWORK
OFFERINGS
• Network Rate. Allowed data transfer rate in MB per
second.
• Guest Type. Choose whether the guest network is
isolated or shared.
• Persistent. Indicate whether the guest network is
persistent or not. The network that you can provision
without having to deploy an instance on it is termed
persistent network.
• Specify VLAN. Indicate whether a VLAN could be
specified when this offering is used. If you select this
option and later use this network offering while
creating a VPC Network Tier or an isolated network,
you will be able to specify a VLAN ID for the network
you create.
• VPC. This option indicate whether the guest network is Virtual Private Cloud-enabled. A
Virtual Private Cloud (VPC) is a private, isolated part of CloudStack. A VPC can have its
own virtual network topology that resembles a traditional physical network. For more
information on VPCs.
• Promiscuous Mode. Applicable for guest networks on VMware hypervisor only. It accepts
the following values for desired behaviour of the network elements:
• Reject - The switch drops any outbound frame from an Instance adapter with a source MAC
address that is different from the one in the .vmx configuration file.
• Accept - The switch does not perform filtering, and permits all outbound frames.
• Forged Transmits. Applicable for guest networks on VMware hypervisor only. It accepts the
following values for desired behaviour of the network elements:
• Reject - The switch drops any outbound frame from an Instance adapter with a source MAC
address that is different from the one in the .vmx configuration file.
• Accept - The switch does not perform filtering, and permits all outbound frames.

• MAC Address Changes. Applicable for guest networks on VMware hypervisor only. It
accepts the following values for desired behaviour of the network elements:
• Reject - If the guest OS changes the effective MAC address of the Instance to a value that is
different from the MAC address of the instance network adapter (set in the .vmx
configuration file), the switch drops all inbound frames to the adapter.
CREATE
INSTANCE
• To create an instance
• select your desired zone, pod,
cluster and host.
• Templates or ISO is your choice

• 2nd tab below dashoboard –is

Compute.
• Under compute-create new
instance
• As you can see your added
ISOs go to my templates tab
• Compute offerings created go
into 3 part, so you can create
a different one as you like
• Disk offerings are added to
part 4 and can be chosen as
desired
• For network offering you can
create an isolated network as
given.
• For a new machine it is
recommended to have an
isolated network
• After this you can click launch instance without adding any other details and it
will work for you.