cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Jiang" <jerry.ji...@tyxtech.com>
Subject 答复: The IPaddr parameter for vmcreate API
Date Fri, 26 Apr 2013 09:55:24 GMT
Hello Pranav,

I would say - in this case, though vrouter(dhcp server) binds mac and ip for
vm instance, it doesn't update vm Operating system from inside. What happens
if I setup vm's OS as static IP address mode?

Thanks
Jerry

-----邮件原件-----
发件人: Pranav Saxena [mailto:pranav.saxena@citrix.com] 
发送时间: 2013年4月26日 星期五 16:37
收件人: dev@cloudstack.apache.org; users@cloudstack.apache.org
主题: RE: The IPaddr parameter for vmcreate API

I think you are absolutely right ..that's how IP allocation works!  Any
issues  ?

Thanks,
Pranav

-----Original Message-----
From: Jerry Jiang [mailto:jerry.jiang@tyxtech.com] 
Sent: Friday, April 26, 2013 1:45 PM
To: users@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: 答复: The IPaddr parameter for vmcreate API

Hello Pranav,

Thanks for your response.

My understanding for how CS allocating IP addresses to vm instance is,
Vrouter works as a dhcp server, and the template for vm is setup to dhcp
mode When cs tries to create a vm, it picks up an available IP from the IP
Pool and assign it to targeted vm instance. Am I right?

Jerry
-----邮件原件-----
发件人: Pranav Saxena [mailto:pranav.saxena@citrix.com]
发送时间: 2013年4月22日 星期一 18:57
收件人: users@cloudstack.apache.org
抄送: dev@cloudstack.apache.org
主题: RE: The IPaddr parameter for vmcreate API

Hey Jerry,

Custom ip allocation failure leads to vm deploy failure. Happens in
following cases:
============================================================================
========
* If ipAddress doesn't exist in the network.
* If requested ip address exists in the network, but already allocated.
* If network model doesn't support custom ip allocation (see list of cases
below), the runtime exception "Does not support custom ip allocation at this
time"  is being thrown.


Custom ip allocation is SUPORTED FOR - 

* Guest Virtual Network
* Direct network in Advanced zone


NOT SUPPORTED - 

* ExternalFirewall setup case. The reason for not supporting: the original
ip can be changed automatically by ExternalGuestNetworkGuru after the vm is
stopped/started.
* Basic zone - as we have 1 Global Network, but separate ip ranges per each
Pod, so the decision about which ip address to take happens after Allocators
figure out the destination Pod.
If you specify the ip address of Pod2, and allocators will pick up Pod1
- the vm creation will fail.

So you can figure out which case might explain your problem to the best
extent possible.

Thanks,
Pranav
-----Original Message-----
From: Jerry Jiang [mailto:jerry.jiang@tyxtech.com]
Sent: Monday, April 22, 2013 3:40 PM
To: users@cloudstack.apache.org
Subject: 答复: The IPaddr parameter for vmcreate API

Anyone has reponsed to the issue, thanks in advance.

 

jerry

 

发件人: Jerry Jiang [mailto:jerry.jiang@tyxtech.com]
发送时间: 2013年4月18日 星期四 10:29
收件人: 'users@cloudstack.apache.org'
主题: The IPaddr parameter for vmcreate API

 

Hello all,

 

I am using cloudstack API to create a VM instance. The IP address as one of
parameters is provided to API

However, I found it didn’t work well, The IP address of creating VM is not
what I provided for API.

Eg, using IP1 as the parameter, the vm operational IP addr is IP2

 

Why does this issue happen?

 

Thanks

Jerry




Mime
View raw message