cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Musayev, Ilya" <imusa...@webmd.net>
Subject RE: IP Address Allocation
Date Tue, 06 Aug 2013 18:49:24 GMT
Can this be done on system VMs as well? I see that its targeted for the guests, if there is
a way to abstract and apply ip address on any component - it would certainly make ACS much
more flexible than it is now.

> -----Original Message-----
> From: Soheil Eizadi [mailto:seizadi@infoblox.com]
> Sent: Tuesday, August 06, 2013 2:29 PM
> To: dev@cloudstack.apache.org
> Subject: RE: IP Address Allocation
> 
> We can define a third type of element for IP Address Allocation, let me look
> at the code and see is there is standard base class that it can extend or we
> have to come up with a new base class like we have for NetworkElements.
> -Soheil
> ________________________________________
> From: Chiradeep Vittal [Chiradeep.Vittal@citrix.com]
> Sent: Tuesday, August 06, 2013 11:14 AM
> To: dev@cloudstack.apache.org
> Cc: Alex Huang
> Subject: Re: IP Address Allocation
> 
> The way the gurus are consulted for network design and reservation makes it
> difficult to put this inside a guru.
> However it does seem odd to put this inside an element. Perhaps we need a
> 3rd type (IpAddressReserver?)
> 
> 
> On 8/6/13 10:42 AM, "Soheil Eizadi" <seizadi@infoblox.com> wrote:
> 
> >The NetworkGuru does a lot more than IP address allocation, e.g. handle
> >the Layer2/3 networking unique to the particular vendor. There are a
> >lot of NetworkElements providing their own NetworkGuru plugins (Nicira,
> >MidoNet, ...) extending the standard CloudStack Gurus.
> >
> >The feature of providing IP Address Allocation, DHCP and DNS is common
> >for all these networks, so rather than provide our own Guru the
> >proposed design would allow the above functions to coexist with existing
> Gurus.
> >
> >-Soheil
> >________________________________________
> >From: Murali Reddy [Murali.Reddy@citrix.com]
> >Sent: Tuesday, August 06, 2013 3:24 AM
> >To: dev@cloudstack.apache.org
> >Subject: Re: IP Address Allocation
> >
> >On 06/08/13 8:59 AM, "Soheil Eizadi" <seizadi@infoblox.com> wrote:
> >
> >>One way to achieve this behavior is to have a call out in prepareNic()
> >>to the NetworkElements before the call to the NetworkGuru allowing the
> >>NetworkElement to update the Nic Profile. In this use case the Network
> >>Element would suggest an IP Address. In the use case below the IP
> >>Address would be updated by the NetworkElement. There is logic in
> >>getIp(), the current IP Allocation that handles the case where the Nic
> >>Profile already has an IP Address. This needs to be updated to handle this
> new use case.
> >>The current use case assume that the VM had already been prepared
> once
> >>and has an IP Address allocated that could be reused.
> >>
> >>Does anyone see a problem with this approach?
> >
> >Purpose of Guru (to design the network) and Element (implement the
> >network) are different. Right way would be for your plug-in to
> >implement both network Guru and element and let the guru do the IP
> >address allocation.
> >
> >>-Soheil
> >>________________________________________
> >>From: Soheil Eizadi [seizadi@infoblox.com]
> >>Sent: Monday, August 05, 2013 2:35 PM
> >>To: dev@cloudstack.apache.org
> >>Subject: IP Address Allocation
> >>
> >>I am trying to figure out what would be the proper way for a Plugin to
> >>interact with the CloudStack VM deployment and provide an
> >>authoritative IP Address from its database versus the local CloudStack
> >>database. It looks like the NetworkElements are not presented an
> >>opportunity to provide an IP Address and you must develop a
> >>NetworkGuru to provide this function. There is some customization of
> >>the IP Address designed into the Secondary NICs (see allocateGuestIP()).
> >>-Soheil
> >>
> >
> >
> 



Mime
View raw message