[one-users] Request for more image attributes

[Ruben S. Montero]

Hi Claude,

This is very interesting indeed. There are quite a lot interest by
some communities and projects to use OVF render for OCCI (and even at
the CLI level). This would be a wonderful contribution to the
ecosystem! Let me know if you want to discuss this any further....


Cheers

Ruben

On Thu, Oct 7, 2010 at 1:44 AM, Claude Noshpitz
<cnoshpitz at attinteractive.com> wrote:
> I've been thinking of building an OVF wrapper
> (http://www.dmtf.org/standards/ovf) on top of ONE, probably via OCCI.  This
> might be applicable to some of these use cases.
>
> Has anyone had enough interest in OVF to think about something like this?
>
> --Claude
>
>
> On 10/5/10 3:38 PM, "Carsten.Friedrich at csiro.au"
> <Carsten.Friedrich at csiro.au> wrote:
>
>> Hi Ruben,
>>
>> Thanks for your reply, this will work fine for me here.
>>
>> Thinking of a larger context, especially portability of images and hybrid
>> clouds, I think it would be good to develop some guidelines / recommendations
>> / de-facto standard for making an image and its template a self-contained unit
>> that includes all information that is necessary to launch it on a hypervisor.
>> There are obviously limits to that, especially context files which would be
>> hard to include, but I think as lot can be done nevertheless.
>>
>> I started along the lines of your first option and use the description field
>> to store XML with my extended information. If there is interest I'd be happy
>> to contribute / share the xsd for that.
>>
>> Carsten
>>
>> -----Original Message-----
>> From: rsmontero at gmail.com [mailto:rsmontero at gmail.com] On Behalf Of Ruben S.
>> Montero
>> Sent: Monday, 4 October 2010 7:27
>> To: Friedrich, Carsten (ICT Centre, Acton)
>> Cc: users at lists.opennebula.org
>> Subject: Re: [one-users] Request for more image attributes
>>
>> Hi,
>>
>> You have two options to do this:
>>
>> 1.- Use the description field
>> 2.- Add the variables you need when creating the image or using the
>> addatr, update and rmattr commands of the oneimage tool
>>
>> Example, check the DESCRIPTION and the ROOT_PASSWORD
>>> oneimage show 6
>> IMAGE  INFORMATION
>> ID             : 6
>> NAME           : Arch
>> TYPE           : OS
>> REGISTER TIME  : 09/025 12:22:49
>> PUBLIC         : Yes
>> PERSISTENT     : No
>> SOURCE         : /srv/cloud/images/3b33133b76375165d2a698702b844f681fbe4888
>> STATE          : rdy
>> RUNNING_VMS    : 0
>>
>> IMAGE TEMPLATE
>> BUS=virtio
>> DESCRIPTION=A vanilla installation of Arch Linux. Context enabled to get IP
>> DEV_PREFIX=hd
>> NAME=Arch
>> PATH=/srv/cloud/images/tmp/archie.raw
>> ROOT_PASSWD=1234
>> TYPE=OS
>>
>> Cheers
>>
>> Ruben
>>
>> On Tue, Sep 28, 2010 at 7:54 AM,  <Carsten.Friedrich at csiro.au> wrote:
>>> It would be nice if one could store more information with an image,
>>> especially OS image information that is relevant for creating a VM template.
>>> Such information could include:
>>>
>>>
>>>
>>> * Supported network models
>>>
>>> * Supported disk busses
>>>
>>> * Which features are supported (e.g. acpi )
>>>
>>> * Which context variables are supported (and how are they used)
>>>
>>>
>>>
>>> Carsten
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
Dr. Ruben Santiago Montero
Associate Professor (Profesor Titular), Complutense University of Madrid

URL: http://dsa-research.org/doku.php?id=people:ruben
Weblog: http://blog.dsa-research.org/?author=7