CentOS 8.x Cloudstack 4.15 Initial zone setup with VLANs
From Notes_Wiki
<yambe:breadcrumb self="Initial zone setup with VLANs">CentOS 8.x Cloudstack 4.15|Cloudstack 4.15</yambe:breadcrumb>
CentOS 8.x Cloudstack 4.15 Initial zone setup with VLANs
After setting up a new management server as described at CentOS 8.x Cloudstack 4.15 Setup Management server, it can be configured for initial zone with VLANs using:
- Open cloudstack manager in the browser at URL http://<cloudstack-manager-ip-or-fqdn>:8080/
- Default username is 'admin' and default password is 'password'
- Choose "Continue with installation"
- Change default password to something more secure
- Enable "Security groups" and then click choose Next on zone type window leaving default of Advanced zone setup as it is
- Enter details for initial zone to be created. Example values are:
- Name
- Zone1
- IPv4 DNS1
- 4.2.2.2 -- This is supposed to be public DNS which resolves to public IPs for your servers.
- Internal DNS1
- 172.31.1.160
- Hypervisor
- KVM
- Note that all members in a zone (Pods, clusters, etc.) share same secondary storage
- Add more DNS IPs if available. Leave other values to their defaults and choose Next
- In Physical Network section do following changes:
- Update Physical network name to "cloudbr0"
- Leave isolation method as "VLAN"
- If there is more than one bridge (eg cloudbr1) with a different physical NIC then add one more physical network
- Add storage traffic to one of the physical networks. It can be added to only one of the physical networks.
- Add other appropriate traffics to the available physical networks.
- Only guest traffic can be part of multiple networks.
- Management and storage are part of one physical network only.
- Click next to continue
- In Pod section enter desired naame and IPs for Secondary storage VM, Console proxy VMs, etc. Example values are given below: Refer http://docs.cloudstack.apache.org/en/latest/installguide/configuration.html#adding-a-pod
- Pod name
- Pod1
- Reserved system gateway
- 172.31.1.1
- Reserved system netmask
- 255.255.255.0 (or 24)
- Start Reserved system IP
- 172.31.1.201
- End Reserved system IP
- 172.31.1.210
- Pod can have one or more clusters. Each cluster has many hosts sharing same primary storage
- Choose add and click Next
- In Guests section leave blank and click next.
- In Storage traffic add at least one network which will have access to the secondary storage VM IP (Pod1 IPs) while also having access to primary storage (If it is NFS)
- Gateway
- 172.31.1.1
- Netmask
- 255.255.255.0 or 24
- VLAN/VNI
- (Leave blank if storage traffic is coming untagged to the physical network (cloudbr0, cloudbr1, etc.) specified for storage traffic)
- Start IP
- 172.31.1.211
- End IP
- 172.31.1.220
- Click add and then click Next
- Cllick next and enter cluster name. Example
- Cluster name
- Cluster1
- Under Add Resources -> IP address we should add at least one KVM host. Enter details of KVM host prepared using CentOS 8.x Cloudstack 4.15 Setup KVM host. Example values
- Hostname
- 172.31.1.30
- Username
- root
- Password
- <secret>
- Tags
- (Leave blank)
- Click next
- Under PrimaryStorage enter details. Example values are
- Name
- Primary1
- Scope
- Cluster
- Protocol
- Shared mount point -- This assumes use of steps suggested at CentOS 8.x Cloudstack 4.15 Setup primary storage to get appropriate shared storage among all cluster hosts
- Path
- /mnt/primary
- Storage tags
- (Leave blank)
- Click "Next"
- Under Second Storage enter details. This assumes availability of NFS via storage server or setup via CentOS 8.x Cloudstack 4.15 Setup NFS server. Example values
- Provider
- NFS
- Name
- Secondary1
- Server
- 172.31.1.165
- Path
- /mnt/secondary -- This is already mounted on secondary server via NFS while importing system VM templates
- Click "Next"
- Click "Launch Zone" to start zone deployment
<yambe:breadcrumb self="Initial zone setup with VLANs">CentOS 8.x Cloudstack 4.15|Cloudstack 4.15</yambe:breadcrumb>
