Considering you have allocated 10.102.198.1 to 10.102.198.10 You statically assign 10.102.198.5 to your physical server. Now you can create an instance like this :
http://10.102.192.243:8096/client/api?command=deployVirtualMachine&serviceofferingid=2&templateid=4&zoneid=1&networkids=<your_shared_network_id>&ipaddress=10.102.198.6 The IP of this VM will be 10.102.198.6 Similarly few vms can be deployed using Ips like 10.102.198.2, 10.102.198.3, 10.102.198.7 .. etc. Using the Ip address param will force the vm to have the specified IP (kind of bypass the dhcp). Thanks, Saksham -----Original Message----- From: COCHE Sébastien [mailto:sco...@sigma.fr] Sent: Friday, October 11, 2013 3:51 PM To: users@cloudstack.apache.org Subject: RE: CS Ip address reservation... OK, if I understand, I have to : 1) disable DHCP service onto the network offering used 2) manage IP pool for this network, externally, in order to set address for each instances and physical servers. I would like a more friendly solution. For example, by using bare metal deployment solution. Do you think it could answer my need ? Sébastien -----Message d'origine----- De : Jayapal Reddy Uradi [mailto:jayapalreddy.ur...@citrix.com] Envoyé : vendredi 11 octobre 2013 11:53 À : <users@cloudstack.apache.org> Objet : Re: CS Ip address reservation... Hi, What I am saying is pick ip address a.b.c.d from the pool for your physical server. Once the ip is picked later if you deploy vm, we need to avoid cloudstack to assign it to user VMs to avoid conflict. For this while creating user vms specify the ip address so that cloudstack will not pick a.b.c.d. You can also do the following: pick the ip for your external server. later if you deploy VM, if the vm gets the ip which you selected then stop the VM. Thanks, Jayapal On 10-Oct-2013, at 10:28 PM, COCHE Sébastien <sco...@sigma.fr> wrote: > Thank for your reply. > I already thought about this workaround. But how ? If I do that, CS will > create a Virtual Machine (instance) onto the hypervisors cluster. This will > consume disk resources and if someone start the instance, I will have an IP > Address conflict on the network. > Am I wrong ? > How can I create a new instance without deploying it ? > Or how can I lock the instance startup ? > > Thanks, > > Sébastien > > -----Message d'origine----- > De : Saksham Srivastava [mailto:saksham.srivast...@citrix.com] > Envoyé : jeudi 10 octobre 2013 15:57 > À : users@cloudstack.apache.org > Objet : RE: CS Ip address reservation... > > Hi, > > You cannot reserve IPs in a shared network, this functionality is available > for VPC/Isolated network only. > For shared networks, as Jayapal suggested you can pick an IP and statically > assign it to the physical server. > Use deployvm API with IP address param (choose it from your unallocated > IPaddress pool) for your CloudStack vms. > > Thanks, > Saksham > > -----Original Message----- > From: Jayapal Reddy Uradi [mailto:jayapalreddy.ur...@citrix.com] > Sent: Thursday, October 10, 2013 6:58 PM > To: <users@cloudstack.apache.org> > Subject: Re: CS Ip address reservation... > > Hi, > > I think you can't reserve the ips in shared network. > > pick an ip address from the pool and use for your external server. > For Vm deployment use the API and pass ip from the unreserved pool. > > Thanks, > Jayapal > > On 10-Oct-2013, at 6:36 PM, COCHE Sébastien <sco...@sigma.fr> > wrote: > >> Hi all, >> >> Is it possible, with CloudStack, to reserve an IP address, on a shared >> network, to be used by an external server, unmanaged by CloudStack ? >> The goal is to integrate physical server (ie : Oracle Database) in a virtual >> environment managed by CloudStack. >> >> Thank a lot >> >> Best regards >> >> Sébastien >
