Difference between revisions of "CentOS 8.x Cloudstack 4.15 Initial zone setup with VLANs"

From Notes_Wiki
(Created page with "<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=...")
 
Line 7: Line 7:
# Choose "Continue with installation"
# Choose "Continue with installation"
# Change default password to something more secure
# 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
# Do not Enable "Security groups".  Leave them disabled and click Next on zone type window leaving default of Advanced zone setup as it is
#: Security group features can be achieved via guest networks  Refer: https://svn.apache.org/repos/asf/cloudstack/docsite/html/docs/en-US/Apache_CloudStack/4.1.1/html/Admin_Guide/security-groups.html
# Enter details for initial zone to be created.  Example values are:
# Enter details for initial zone to be created.  Example values are:
#:; Name: Zone1
#:; Name: Zone1
Line 13: Line 14:
#:; Internal DNS1: 172.31.1.160  
#:; Internal DNS1: 172.31.1.160  
#:; Hypervisor: KVM
#:; Hypervisor: KVM
#:; Guest CIDR: 10.100.0.0/16 -- Completely isolated network not used anywhere in the organization and not planned for future use either
#: Note that all members in a zone (Pods, clusters, etc.) share same secondary storage
#: 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
#: Add more DNS IPs if available.  Leave other values to their defaults and choose Next
Line 22: Line 24:
## Add other appropriate traffics to the available physical networks.   
## Add other appropriate traffics to the available physical networks.   
##: Only guest traffic can be part of multiple networks.   
##: Only guest traffic can be part of multiple networks.   
##: Management and storage are part of one physical network only.
##: Public, Management and storage are part of one physical network only.
## Click next to continue
## Click next to continue
# In public Network enter appropriate values.  Example
#:; Gateway: 172.31.1.1
#:; Netmask: 255.255.255.0  (Note /24 will pass form validation but will lead to error during launch)
#:; VLAN/VNI: (Leave blank for untagged public network)
#:; Start IP: 172.31.1.191
#:; End IP: 172.31.1.200
#: Click "add" and then click "next"
# 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
# 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
#:; Pod name: Pod1
#:; Reserved system gateway: 172.31.1.1
#:; Reserved system gateway: 172.31.1.1
#:; Reserved system netmask: 255.255.255.0 (or 24)
#:; Reserved system netmask: 255.255.255.0   (Note /24 will pass form validation but will lead to error during launch)
#:; Start Reserved system IP: 172.31.1.201
#:; Start Reserved system IP: 172.31.1.201
#:; End Reserved system IP: 172.31.1.210
#:; End Reserved system IP: 172.31.1.210
#: Pod can have one or more clusters.  Each cluster has many hosts sharing same primary storage
#: Pod can have one or more clusters.  Each cluster has many hosts sharing same primary storage
#: Choose add and click Next
#: Choose add and click Next
# In Guests section leave blank and click next.   
# In VLAN/VNI range enter appropriate VLANs that are tagged to all cloudstack hosts on physical switch level.  Example values
#:; VLANs Range: 50-70
# 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)
# 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
#:; Gateway: 172.31.1.1
#:; Netmask: 255.255.255.0 or 24
#:; Netmask: 255.255.255.0   (Note /24 will pass form validation but will lead to error during launch)
#:; VLAN/VNI:  (Leave blank if storage traffic is coming untagged to the physical network (cloudbr0, cloudbr1, etc.) specified for storage traffic)  
#:; 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
#:; Start IP: 172.31.1.211
Line 43: Line 53:
#; Cluster name: Cluster1
#; 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
# 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
#; Hostname: 172.31.1.161
#; Username: root
#; Username: root
#; Password: <secret>
#; Password: <secret>
Line 62: Line 72:
#: Click "Next"
#: Click "Next"
# Click "Launch Zone" to start zone deployment
# Click "Launch Zone" to start zone deployment




Revision as of 14:51, 12 February 2021

<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:

  1. Open cloudstack manager in the browser at URL http://<cloudstack-manager-ip-or-fqdn>:8080/
    Default username is 'admin' and default password is 'password'
  2. Choose "Continue with installation"
  3. Change default password to something more secure
  4. Do not Enable "Security groups". Leave them disabled and click Next on zone type window leaving default of Advanced zone setup as it is
    Security group features can be achieved via guest networks Refer: https://svn.apache.org/repos/asf/cloudstack/docsite/html/docs/en-US/Apache_CloudStack/4.1.1/html/Admin_Guide/security-groups.html
  5. 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
    Guest CIDR
    10.100.0.0/16 -- Completely isolated network not used anywhere in the organization and not planned for future use either
    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
  6. In Physical Network section do following changes:
    1. Update Physical network name to "cloudbr0"
    2. Leave isolation method as "VLAN"
    3. If there is more than one bridge (eg cloudbr1) with a different physical NIC then add one more physical network
    4. Add storage traffic to one of the physical networks. It can be added to only one of the physical networks.
    5. Add other appropriate traffics to the available physical networks.
      Only guest traffic can be part of multiple networks.
      Public, Management and storage are part of one physical network only.
    6. Click next to continue
  7. In public Network enter appropriate values. Example
    Gateway
    172.31.1.1
    Netmask
    255.255.255.0 (Note /24 will pass form validation but will lead to error during launch)
    VLAN/VNI
    (Leave blank for untagged public network)
    Start IP
    172.31.1.191
    End IP
    172.31.1.200
    Click "add" and then click "next"
  8. 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 (Note /24 will pass form validation but will lead to error during launch)
    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
  9. In VLAN/VNI range enter appropriate VLANs that are tagged to all cloudstack hosts on physical switch level. Example values
    VLANs Range
    50-70
  10. 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 (Note /24 will pass form validation but will lead to error during launch)
    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
  11. Cllick next and enter cluster name. Example
    Cluster name
    Cluster1
  12. 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.161
    Username
    root
    Password
    <secret>
    Tags
    (Leave blank)
    Click next
  13. 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"
  14. 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"
  15. 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>

Retrieved from "http://www.sbarjatiya.com/notes_wiki/index.php?title=CentOS_8.x_Cloudstack_4.15_Initial_zone_setup_with_VLANs&oldid=4866"