Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Kelcey Damage \(BT\)" <kelcey@backbonetechnology.com>
To: <cloudstack-dev@incubator.apache.org>
References: <02dd01cddd4f$6e97a800$4bc6f800$@backbonetechnology.com>
 <CCF5FA7B.3C629%chiradeep.vittal@citrix.com>
In-Reply-To: <CCF5FA7B.3C629%chiradeep.vittal@citrix.com>
Subject: RE: Functional Specification for the multiple IPs per NIC
Date: Tue, 18 Dec 2012 10:53:17 -0800
Message-ID: <02df01cddd50$f1045e90$d30d1bb0$@backbonetechnology.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQK4ZpO10Xq0xUNv37SL1C+J9sYHfpZJ1F0A
Content-Language: en-us


>-----Original Message-----
>From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com]
>Sent: Tuesday, December 18, 2012 10:50 AM
>To: CloudStack DeveloperList
>Subject: Re: Functional Specification for the multiple IPs per NIC
>
>Yes, that is a mere matter of updating the metadata. How the vm wishes to
>use it is another matter.
>Concerns such as "allow expiration of data, wider variety of data
supported"
>are important, but not in this context.
>Different feature IMO

Ok, I'm starting to see where you're coming from. I'm ok with us pulling the
CloudInit stuff back out of this proposal and making that a separate issue.

+1

>
>On 12/18/12 10:42 AM, "Kelcey Damage (BT)"
><kelcey@backbonetechnology.com>
>wrote:
>
>>
>>
>>>-----Original Message-----
>>>From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com]
>>>Sent: Tuesday, December 18, 2012 10:39 AM
>>>To: CloudStack DeveloperList
>>>Subject: Re: Functional Specification for the multiple IPs per NIC
>>>
>>>Sorry, not sure why cloud-init is being clubbed into this feature.
>>
>>I believe it is seen as a way to further automate or complete the
>>multiple IP transaction. Currently the proposal will track IPs in the
>>DB, but the user still has to manually configure everything... status quo.
>>
>>>
>>>The secondary ips can be made available through the usual metadata
>>>scheme.
>>>
>>>On 12/18/12 10:36 AM, "John Kinsella" <jlk@stratosec.co> wrote:
>>>
>>>>Is there any logic behind 30? At some point, we're going to be asked,
>>>>so I'd like to have a decent answer. :)
>>>>
>>>>On the rest of this, I'd like to get some level of consensus on the
>>>>design. What looks best to me:
>>>>* Improve UserData/CloudInit support in CloudStack (I'm willing to
>>>>work on this, consider it important) -
>>>>* Create the multi-IPs-per-NIC code to get IPs via CloudInit (Need to
>>>>think through Windows equivalent)
>>>>* Update the password changing script to use CloudInit
>>>>
>>>>Thoughts? Or Jayapal have you already started work on the multi-IP
>>>>feature?
>>>>
>>>>On Dec 18, 2012, at 2:03 AM, Jayapal Reddy Uradi
>>>><jayapalreddy.uradi@citrix.com> wrote:
>>>>
>>>>> Regarding IP limit,  it can be made as configurable using global
>>>>>settings and default value will be 30.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Jayapal
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com]
>>>>>> Sent: Monday, December 17, 2012 12:59 PM
>>>>>> To: CloudStack DeveloperList
>>>>>> Subject: Re: Functional Specification for the multiple IPs per NIC
>>>>>>
>>>>>> In basic/shared networks the allocation is bounded by what is
>>>>>>already
>>>>>>"used-
>>>>>> up". To prevent tenants from hogging all the available ips, there
>>>>>>needs to be  limits.
>>>>>>
>>>>>> On 12/15/12 8:38 AM, "John Kinsella" <jlk@stratosec.co> wrote:
>>>>>>
>>>>>>> I'd remove the limitation of having 30 IPs per interface. Modern
>>>>>>> OSes can support way more.
>>>>>>>
>>>>>>> Why no support for basic networking? I can see a small hosting
>>>>>>>provider  with a basic setup wanting to manage web servers...
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> On Dec 14, 2012, at 9:37 AM, Jayapal Reddy Uradi
>>>>>>> <jayapalreddy.uradi@citrix.com> wrote:
>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Current guest VM by default having one NIC and one IP address
>>>>>>>>assigned.
>>>>>>>> If your wants extra IP for the guest VM, there no provision from
>>>>>>>>the  CS.
>>>>>>>>
>>>>>>>> Using multiple IP address per NIC feature CS can associate IP
>>>>>>>>address for the NIC,  user can take that IP and assign it to the
>>>>>>>>VM.
>>>>>>>>
>>>>>>>> Please find the FS for  the more details.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Multiple+
>>>>>>>> IP
>>>>>>>> +a
>>>>>> dd
>>>>>>>> res
>>>>>>>> s+per+NIC
>>>>>>>>
>>>>>>>> Please provide your comments on the FS.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> jayapal
>>>>>>>
>>>>>>> Stratosec - Secure Infrastructure as a Service
>>>>>>> o: 415.315.9385
>>>>>>> @johnlkinsella
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>Stratosec - Secure Infrastructure as a Service
>>>>o: 415.315.9385
>>>>@johnlkinsella
>>>>
>>
>>