Thanks Alena,
I see that both Elastic LB and Elastic IP are set to false. Looks like
a bug then.
-Syed
On Wed 18 Dec 2013 02:22:52 PM EST, Alena Prokharchyk wrote:
Syed,
You can get this info from the network offering of your network.
http://localhost:8096/?command=listNetworkOfferings&id=
Š.
<capability>
<name>ElasticLb</name>
<value>false</value>
ŠŠ.
-Alena.
On 12/18/13, 11:19 AM, "Syed Ahmed" <sah...@cloudops.com> wrote:
Thanks for the reply Alena,
I have an isolated network which has Netscaler as the LB provider. Does
that enable elastic LB? I was looking at the other default network
offering for elastic LB and did not find anything like "elastic LB" or
"elastic IP" in the service capabilities. How Do I know if elastic LB is
enabled or not?
-Syed
On 12/18/2013 02:05 PM, Alena Prokharchyk wrote:
Syed, is ElasticLB support enabled in your network? If yes, then its ok
to
see 2 tabs.
When you go 1) Network->Add LB, the ip address for your lb rule will get
allocated on the fly as a part of LB rule creation as a part of elastic
Lb
functionality.
You can add more lb rules for the public ip address associated on the
previous step; for that you have to go 2) path, select the IP and
create a
rule for it.
If elastic LB is not enabled on the network, seeing 1) path in the UI
is a
UI bug.
-Alena.
On 12/18/13, 8:48 AM, "Syed Ahmed" <sah...@cloudops.com> wrote:
Hi All,
In the UI there are two places where we can add a loadbalancer rule.
1) Network-> myNetwork -> Add Load Balancer tab
2) Network -> myNetwork -> View IP Addresses -> [IP] -> Configuration
->
LoadBalancing ( View All )
What is the difference between those two? Adding a rule on (2) seems to
work but when I try to add it on (1) it fails saying cannot allocate
source IP.
Thanks,
-Syed
