On 6/7/12 9:25 AM, "Eric Reeves" <[email protected]> wrote:
>Alena responded to my email and stated that IP addresses stick with >virtual machines for the entire lifecycle. > >Is that only guaranteed to be the case if you have a single POD in basic >networking mode? (Or is it not even guaranteed then?) It is guaranteed in: * All cases in the Basic zone, no matter how many Pods you have * In Advance zone when VirtualRouter is used as DHCP provider. -Alena. > >What are the downsides of just hard-coding IP addresses on these systems >to IP's outside of the allocated guest ranges for the PODs? Cloudstack >will not know where to reach them, but does it really need to? > >I appreciate everybody's input on this topic. > >Eric Reeves > > >On Jun 7, 2012, at 1:49 AM, Geoff Higginbottom wrote: > >Whilst this would be possible if you were using Advanced Networking, >although still only by manual DB updating, and not via the GUI, you >cannot do it with Basic Networking. > >Using the API you can deploy VMs with a specific IP if you are using >Advanced networking, but you cannot with Basic networking, this is >because with Basic networking each POD has a different Guest CIDA, so if >you shut down your VM then restart it later, it could be placed on a >different POD, and get allocated a different IP. > >
