RE: VM Instance ip difference beetween Network types
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 Guest CIDR for the associated network and the VM Placement has no impact on this so the IP is assigned during VM creation. The IP allocation for a VM in a Basic Zone could be seen by some as inferior when compared to an Advanced Zone. In an Advanced Zone you can assign the IP when you create the VM (via API) but this is not possible for a Basic Zone, even for Root Admins. I know this does not answer your question, just giving you the background as to why it works the way it does. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Antonio Petrocelli [mailto:a.petroce...@netsons.com] Sent: 19 December 2013 11:32 To: users@cloudstack.apache.org Subject: VM Instance ip difference beetween Network types Hello, on *Basic *Network types the IP is assigned only after VM start first time but on *Advanced *Network types the IP is assigned immediatly after vm deploy and before before VM start first time. Is there a way to make Advanced work like Basic (IP will be assigned only after VM start)? Thanks. Best Regards. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
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 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 Higginbottom ha scritto: 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 Guest CIDR for the associated network and the VM Placement has no impact on this so the IP is assigned during VM creation. The IP allocation for a VM in a Basic Zone could be seen by some as inferior when compared to an Advanced Zone. In an Advanced Zone you can assign the IP when you create the VM (via API) but this is not possible for a Basic Zone, even for Root Admins. I know this does not answer your question, just giving you the background as to why it works the way it does. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Antonio Petrocelli [mailto:a.petroce...@netsons.com] Sent: 19 December 2013 11:32 To: users@cloudstack.apache.org Subject: VM Instance ip difference beetween Network types Hello, on *Basic *Network types the IP is assigned only after VM start first time but on *Advanced *Network types the IP is assigned immediatly after vm deploy and before before VM start first time. Is there a way to make Advanced work like Basic (IP will be assigned only after VM start)? Thanks. Best Regards. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
RE: VM Instance ip difference beetween Network types
Antonio, Not sure why it's a problem having the IP assigned in an isolated network, can you elaborate why you don't like this. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 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 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 Higginbottom ha scritto: 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 Guest CIDR for the associated network and the VM Placement has no impact on this so the IP is assigned during VM creation. The IP allocation for a VM in a Basic Zone could be seen by some as inferior when compared to an Advanced Zone. In an Advanced Zone you can assign the IP when you create the VM (via API) but this is not possible for a Basic Zone, even for Root Admins. I know this does not answer your question, just giving you the background as to why it works the way it does. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Antonio Petrocelli [mailto:a.petroce...@netsons.com] Sent: 19 December 2013 11:32 To: users@cloudstack.apache.org Subject: VM Instance ip difference beetween Network types Hello, on *Basic *Network types the IP is assigned only after VM start first time but on *Advanced *Network types the IP is assigned immediatly after vm deploy and before before VM start first time. Is there a way to make Advanced work like Basic (IP will be assigned only after VM start)? Thanks. Best Regards. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
RE: VM Instance ip difference beetween Network types
Antonio, I guess the bit I can't understand is why is it a problem to have an IP allocated. Guest IPs in an Advanced Zone are unique to their CIDR, are behind their Virtual Router, take up no resources, and do not cost anything in real terms. I can only guess that you are using a Shared Network with real Public IPs that you have a limited supply of. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@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. When i used basic network configuration, by API i send deployvirtualmachine command with startvm set to false in according to: http://cloudstack.apache.org/docs/api/apidocs-4.2/domain_admin/deployVirtualMachine.html By doing this i was able to create configuration of a vm WITHOUT assign immediately an IP address. This is much important for us. This is my goal. Create vm config and NOT assign IP address immediately. Instead, if i use advanced network configuration and same commands to API, IP address will AUTOMATICALLY assigned to vm ( a sort of reservation of IP ). I want avoid this because i do not want to have a situation where N customers can create vm without using them and IP addresses will be reserved for them. With basic network configuration i can do this. With advanced i can not. Waiting for your reply Best regards Il 19/12/2013 13:05, Geoff Higginbottom ha scritto: Antonio, Not sure why it's a problem having the IP assigned in an isolated network, can you elaborate why you don't like this. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 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 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 Higginbottom ha scritto: 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 Guest CIDR for the associated network and the VM Placement has no impact on this so the IP is assigned during VM creation. The IP allocation for a VM in a Basic Zone could be seen by some as inferior when compared to an Advanced Zone. In an Advanced Zone you can assign the IP when you create the VM (via API) but this is not possible for a Basic Zone, even for Root Admins. I know this does not answer your question, just giving you the background as to why it works the way it does. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Antonio Petrocelli [mailto:a.petroce...@netsons.com] Sent: 19 December 2013 11:32 To: users@cloudstack.apache.org Subject: VM Instance ip difference beetween Network types Hello, on *Basic *Network types the IP is assigned only after VM start first time but on *Advanced *Network types the IP is assigned immediatly after vm deploy and before before VM start first time. Is there a way to make Advanced work like Basic (IP will be assigned only after VM start)? Thanks. Best Regards. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those
Re: VM Instance ip difference beetween Network types
Yes, exactly...we have a limited supply of Public IPs. Thanks a lot! Il 19/12/2013 15:07, Geoff Higginbottom ha scritto: Antonio, I guess the bit I can't understand is why is it a problem to have an IP allocated. Guest IPs in an Advanced Zone are unique to their CIDR, are behind their Virtual Router, take up no resources, and do not cost anything in real terms. I can only guess that you are using a Shared Network with real Public IPs that you have a limited supply of. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@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. When i used basic network configuration, by API i send deployvirtualmachine command with startvm set to false in according to: http://cloudstack.apache.org/docs/api/apidocs-4.2/domain_admin/deployVirtualMachine.html By doing this i was able to create configuration of a vm WITHOUT assign immediately an IP address. This is much important for us. This is my goal. Create vm config and NOT assign IP address immediately. Instead, if i use advanced network configuration and same commands to API, IP address will AUTOMATICALLY assigned to vm ( a sort of reservation of IP ). I want avoid this because i do not want to have a situation where N customers can create vm without using them and IP addresses will be reserved for them. With basic network configuration i can do this. With advanced i can not. Waiting for your reply Best regards Il 19/12/2013 13:05, Geoff Higginbottom ha scritto: Antonio, Not sure why it's a problem having the IP assigned in an isolated network, can you elaborate why you don't like this. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 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 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 Higginbottom ha scritto: 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 Guest CIDR for the associated network and the VM Placement has no impact on this so the IP is assigned during VM creation. The IP allocation for a VM in a Basic Zone could be seen by some as inferior when compared to an Advanced Zone. In an Advanced Zone you can assign the IP when you create the VM (via API) but this is not possible for a Basic Zone, even for Root Admins. I know this does not answer your question, just giving you the background as to why it works the way it does. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: Antonio Petrocelli [mailto:a.petroce...@netsons.com] Sent: 19 December 2013 11:32 To: users@cloudstack.apache.org Subject: VM Instance ip difference beetween Network types Hello, on *Basic *Network types the IP is assigned only after VM start first time but on *Advanced *Network types the IP is assigned immediatly after vm deploy and before before VM start first time. Is there a way to make Advanced work like Basic (IP will be assigned only after VM start)? Thanks. Best Regards. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed
