[Capi-bof] Current charter and last call for changes.

Fri Mar 27 06:32:28 CDT 2009

Fully agree with Andy on the solution proposed by Sam, and I would  
like to thank Richard for its valuable contribution from its expertise  
as Cloud provider.

Regards
--
Ignacio M. Llorente, Full Professor (Catedratico): web http://dsa-research.org/llorente 
  and blog http://imllorente.dsa-research.org/
DSA Research Group:  web http://dsa-research.org and blog http://blog.dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org

On 27/03/2009, at 12:17, Edmonds, AndrewX wrote:

> I think what's key here is that we do not leak certain technology  
> concerns (e.g. making assumptions about IP versions). It's perfectly  
> fine to say that a VM needs a network adapter and that it needs to  
> have a static IP address, details of which are supplied by the  
> infrastructure provider after provisioning the requested resources.  
> Also perfectly fine to have network configuration specified but  
> abstractly, like as was previously discussed (Sam had suggested it)  
> here (e.g. this VM is to be part of the "public" network or  
> "private" network) but not get bogged down in "this VM needs to be  
> available on subnet XXX.YYY.ZZZ".
>
> The text that Richard suggests is fine so long as the effort is in  
> defining an abstract network configuration. :-)
>
> Andy
>
> -----Original Message-----
> From: capi-bof-bounces at ogf.org [mailto:capi-bof-bounces at ogf.org] On  
> Behalf Of Richard Davies
> Sent: 27 March 2009 10:45
> To: Thijs Metsch
> Cc: capi-bof
> Subject: Re: [Capi-bof] Current charter and last call for changes.
>
> <snip>
>
> We're keen that the standard should cover specifying the number,
> connectivity and possible static IPs for network interfaces. For
> example, "a VM has two interfaces, one on a private VLAN with IP
> allocated by DHCP, and one on the public internet with static IP of
> X.X.X.X."
>
> This is critical to support multi-tier web applications, etc. and is
> supported in most existing vendor APIs (e.g. our own
> www.elastichosts.com/products/api, but also GoGrid, Amazon Elastic  
> IP, etc.)
>
>
> Looking at the e-mail achieve, I believe that you have had this
> discussion (Michael Richardson, and Sam Johnston) and did agree that  
> all
> of what I mention is in fact in scope. Can we update the wording to
> capture this? e.g.
>
> "Storage details beyond creation and mapping of mount points is
> specifically excluded. Networking details are similarly excluded  
> beyond
> creation and mapping of interfaces, assignment of these to public or
> private networks and assignment of dynamic or static IPs."
>
>
> Cheers,
>
> Richard.
>
> Thijs Metsch wrote:
>> Hi @all,
>>
>> First of all: thank you all for joining this mailing-list. Currently
>> their are around 60 people on the list. Also the feedback we get  
>> and the
>> level of interest is great!
>>
>> Please find attached the current version of the charter. Feel free to
>> comment. If you comment please state what you like to change and  
>> how to
>> reformulate it. In special have a look at the mission statement in  
>> the
>> charter.
>>
>> I would call this the last call for changes, because we need to get  
>> the
>> charter fixes soon, so we can send the final version to the OGF  
>> steering
>> committee. The deadline for changes will be Monday 5pm (CET).
>>
>> Again thanks for joining and I'm looking forward to discuss and work
>> with you,
>>
>> -Thijs
> _______________________________________________
> Capi-bof mailing list
> Capi-bof at ogf.org
> http://www.ogf.org/mailman/listinfo/capi-bof
> -------------------------------------------------------------
> Intel Ireland Limited (Branch)
> Collinstown Industrial Park, Leixlip, County Kildare, Ireland
> Registered Number: E902934
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> _______________________________________________
> Capi-bof mailing list
> Capi-bof at ogf.org
> http://www.ogf.org/mailman/listinfo/capi-bof