Having problem during configuring autoscaling feature in CloudStack
Hi All, We are trying to use autoscaling feature in Cloudstack either with NetScaler or without NetScaler. We have tried with both Cloudstack versions 4.4 and 4.5. *Our configuration:* -- management server : centos 6.4 ip:192.168.1.10 netmask:255.255.255.0 gateway:192.168.1.1 -- host : xenserver 6.1 ip:192.168.1.11 netmask:255.255.255.0 gateway:192.168.1.1 -- we have a router with vlan support,and we configured 4 vlans as untagged in order to get access to internet (according to router user manual): vlan id (1) : 192.168.1.0/24 vlan id (2) : 192.168.2.0/24 vlan id (3) : 192.168.3.0/24 vlan id (4) : 192.168.4.0/24 - all vlans can ping each other and can access internet. - firewall is off in the router. *==> We tried with the following approaches:* *1) Installation with Basic zone:* --Network offering: DefaultSharedNetscalerEIPandELBNetworkOffering --management network: 192.168.1.0/24 (vlan1) --guest network: 192.168.1.0/24 (vlan1) --public network: 192.168.2.0/24 (vlan2) --Note: we prepared the template with snmp and application *--Issues in this configuration:* -We can not ping the public ip assigned to the load balancer that getting from public ips pool. -We stopped the firewall in XenServer (btw :firewall is restarted frequently even though with chkconfig iptables off) *2) Installation with Advance zone:* --guest cidr (3 different installation): 10.10.0.0/24 192.168.1.0/24 192.168.2.0/24 --management network: 192.168.1.0/24 (vlan1) --public network (3 different installation): 192.168.1.0/24 (vlan1) 192.168.2.0/24 (vlan2) --guest vlan tag range (2 different installation): 700-800 blank-blank --We tried with both shared and isolated guest network from vlan1 and vlan2: vlan1:192.168.1.0/24 vlan2:192.168.2.0/24 *--Issues in this configuration:* -We cannot ping the VM IP created with either isolated or shared network from any vlans and from vm we can not also access the internet. -We stopped the firewall in xenserver (btw :firewall is restarted frequently even though with chkconfig iptables off) Now we are not sure how to proceed with autoscaler configuration, what combination we should try to make it work. Can any one please give us some direction to make autoscale running. We really appreciate any comments or suggestions. Please let us know if you have any clarification questions. Thanks in advance,
Re: Having problem during configuring autoscaling feature in CloudStack
Hi Mr. Rajesh Battala, Thanks a lot for your nice reply. We have installed NetScaler VPX (*Version 10.5-55.8*) on XenServer and using the 90 days free license. *We have tried the following steps for AutoScaling with NetScaler:* 1. We have installed cloudstack with with *Basic zone* and added netscaler by selecting the network offering as DefaultSharedNetscalerEIPandELBNetworkOffering. 2. We gave the management (pod) network as 192.168.1.0/24 (vlan1), guest network as 192.168.1.0/24 (vlan1) and public network as 192.168.2.0/24 (vlan2) 3. Registered an Ubuntu 12.04 server iso, installed an instance and prepared a template with snmp agent running on the VM and application running on 8080 port for the autoscaler. 4. Then we configured the autoscaler by clicking Network -> Configuration -> LoadBalancing -> configured a Autoscale rule (e.g., cpu >80% add VM and cpu<20% remove VM). But the problem we are having in this configuration is that we can not ping the public ip assigned to the autoscaler getting from public network (192.168.2.0/24). 5. We stopped the firewall in XenServer by using the command 'service iptables stop'. Not really sure the above steps are correct or not. Please let us know your valuable comments or suggestions. Waiting for your kind response. Thanks in Advance
Fwd: Problem in configuring autoscaling feature in CloudStack
Hi All, We are trying to use autoscaling feature in Cloudstack either with NetScaler or without NetScaler. We have tried with both Cloudstack versions 4.4 and 4.5. *Our configuration:* -- management server : centos 6.4 ip:192.168.1.10 netmask:255.255.255.0 gateway:192.168.1.1 -- host : xenserver 6.1 ip:192.168.1.11 netmask:255.255.255.0 gateway:192.168.1.1 -- we have a router with vlan support,and we configured 4 vlans as untagged in order to get access to internet (according to router user manual): vlan id (1) : 192.168.1.0/24 vlan id (2) : 192.168.2.0/24 vlan id (3) : 192.168.3.0/24 vlan id (4) : 192.168.4.0/24 - all vlans can ping each other and can access internet. - firewall is off in the router. *==> We tried with the following approaches:* *1) Installation with Basic zone:* --Network offering: DefaultSharedNetscalerEIPandELBNetworkOffering --management network: 192.168.1.0/24 (vlan1) --guest network: 192.168.1.0/24 (vlan1) --public network: 192.168.2.0/24 (vlan2) --Note: we prepared the template with snmp and application *--Issues in this configuration:* -We can not ping the public ip assigned to the load balancer that getting from public ips pool. -We stopped the firewall in XenServer (btw :firewall is restarted frequently even though with chkconfig iptables off) *2) Installation with Advance zone:* --guest cidr (3 different installation): 10.10.0.0/24 192.168.1.0/24 192.168.2.0/24 --management network: 192.168.1.0/24 (vlan1) --public network (3 different installation): 192.168.1.0/24 (vlan1) 192.168.2.0/24 (vlan2) --guest vlan tag range (2 different installation): 700-800 blank-blank --We tried with both shared and isolated guest network from vlan1 and vlan2: vlan1:192.168.1.0/24 vlan2:192.168.2.0/24 *--Issues in this configuration:* -We cannot ping the VM IP created with either isolated or shared network from any vlans and from vm we can not also access the internet. -We stopped the firewall in xenserver (btw :firewall is restarted frequently even though with chkconfig iptables off) Now we are not sure how to proceed with autoscaler configuration, what combination we should try to make it work. Can any one please give us some direction to make autoscale running. We really appreciate any comments or suggestions. Please let us know if you have any clarification questions. Thanks in advance,
Re: Having problem during configuring autoscaling feature in CloudStack
Can anyone please help us to resolve this issue. We would appreciate any guideline or suggestion that might help us. Thanks. On Fri, Aug 7, 2015 at 12:47 AM, cloud stack wrote: > Hi Mr. Rajesh Battala, > > > Thanks a lot for your nice reply. > > > We have installed NetScaler VPX (*Version 10.5-55.8*) on XenServer and > using the 90 days free license. > > > *We have tried the following steps for AutoScaling with NetScaler:* > > 1. We have installed cloudstack with with *Basic zone* and added > netscaler by selecting the network offering > as DefaultSharedNetscalerEIPandELBNetworkOffering. > > 2. We gave the management (pod) network as 192.168.1.0/24 (vlan1), > > guest network as 192.168.1.0/24 (vlan1) and > > public network as 192.168.2.0/24 (vlan2) > > 3. Registered an Ubuntu 12.04 server iso, installed an instance and > prepared a template with snmp agent running on the VM and > application running on 8080 port for the autoscaler. > > 4. Then we configured the autoscaler by clicking Network -> Configuration > -> LoadBalancing -> configured a Autoscale rule (e.g., cpu >80% add VM and > cpu<20% remove VM). But the problem we are having in this configuration is > that we can not ping the public ip assigned to the autoscaler getting from > public network (192.168.2.0/24). > > 5. We stopped the firewall in XenServer by using the command 'service > iptables stop'. > > > Not really sure the above steps are correct or not. Please let us know > your valuable comments or suggestions. > > Waiting for your kind response. > > > > Thanks in Advance > >
auto scaling configuration with netscaler
Hi all , We have tested tagging network works in advance zone for default isolated network where the three networks assigned as follow -management network assigned to vlan1 (192,168.1.x) -public network assigned to vlan2 (192,168.2.x) -guest network assigned to vlan3 and vlan4 (192,168.3,4.x) In details, VM got assigned to IP from guest network, and this IP encapsulated by the second IP from the public network. Thus, we can ping the public IP from management network and access the webapp as well. However, once the customized isolated network that support netscaler instead of a virtual router used to create load balancer feature. In this case, we can not immediately reach the public IP of loadbalnacer (192.168.2.14) as showing below from management network even though the minimum vms ( with proper template used for the first test) is deployed and running and we stop firewall in VM,XenServer, netscaler VM, and management server. # ping 192.168.2.14 PING 192.168.2.14 (192.168.2.14) 56(84) bytes of data. >From 192.168.1.1: icmp_seq=2 Redirect Host(New nexthop: 192.168.2.14) >From 192.168.1.1: icmp_seq=3 Redirect Host(New nexthop: 192.168.2.14) >From 192.168.1.1 icmp_seq=1 Destination Host Unreachable >From 192.168.1.1 icmp_seq=2 Destination Host Unreachable >From 192.168.1.1 icmp_seq=3 Destination Host Unreachable 64 bytes from 192.168.2.14: icmp_seq=4 ttl=255 time=0.262 ms 64 bytes from 192.168.2.14: icmp_seq=5 ttl=255 time=0.268 ms 64 bytes from 192.168.2.14: icmp_seq=6 ttl=255 time=0.260 ms Any suggestion would be appreciated Thanks,
