inbot...@shapeblue.com
-Original Message-
From: Antonio Petrocelli [mailto:a.petroce...@netsons.com]
Sent: 19 December 2013 14:00
To: users@cloudstack.apache.org
Subject: Re: VM Instance ip difference beetween Network types
Geoff,
i try to explain you what happened and which is my target.
W
14:00
To: users@cloudstack.apache.org
Subject: Re: VM Instance ip difference beetween Network types
Geoff,
i try to explain you what happened and which is my target.
When i used basic network configuration, by API i send deployvirtualmachine
command with startvm set to false in according to:
7968161581
geoff.higginbot...@shapeblue.com
-Original Message-
From: Antonio Petrocelli [mailto:a.petroce...@netsons.com]
Sent: 19 December 2013 12:03
To: users@cloudstack.apache.org
Subject: Re: VM Instance ip difference beetween Network types
Thanks a lot...
i know this, but my goal is
m: Antonio Petrocelli [mailto:a.petroce...@netsons.com]
Sent: 19 December 2013 12:03
To: users@cloudstack.apache.org
Subject: Re: VM Instance ip difference beetween Network types
Thanks a lot...
i know this, but my goal is to assign the ip afterwards, to allow users have
deployed and not started
Thanks a lot...
i know this, but my goal is to assign the ip afterwards, to allow users
have deployed and not started VM.
With this configuration i assign an IP for every deployed VM, even if
they are never turned on!
Are there other ways?
Thanks.
Regards.
Il 19/12/2013 12:51, Geoff Hig
Antonio
This behaviour is because of the differences between Basic and Advanced
Networking.
In a Basic Zone, the IP is determined by the POD the VM gets assigned to, but
this assignment only happens when it is started for the first time.
With an Advanced Network, the IP is assigned from the Gu
