Ok ...
I think it's worth considering ... the software in general gives huge
performance
and resilience boosts over other technologies, but in the context of OpenNebula
specifically,
with vdc-store, there is no deployment latency which makes a huge difference to
starting
up VM's. Trying to start a 100G image over NFS involves making coffee, whereas
creating a
vdc-store cache to launch a 100G image takes under a second.
(I will have the same latency for non-persistent images soon .. )
Having all features / settings available in the GUI would give it a much better
"feel".
Also (!) there are other tweaks which would be "nice" .. :)
Specifically, in the template, currently we need to add a variable to set the
size of
the cache .. having this selected from an entry field or drop-down would be
good, and in
images we need to specify the capacity of an image, again a field would be good.
(currently we add something like "CAPACITY = 10G" as a custom field)
..
--
Gareth Bult
“The odds of hitting your target go up dramatically when you aim at it.”
See the status of my current project at http://vdc-store.com
----- Original Message -----
From: "Javier Fontan" <jfon...@opennebula.org>
To: "Gareth Bult" <gar...@linux.co.uk>, "Daniel Molina" <dmol...@opennebula.org>
Cc: dev@lists.opennebula.org
Sent: Tuesday, 14 January, 2014 4:00:06 PM
Subject: Re: [one-dev] Re; VDC-Store
It seems a bit tricky indeed. The plugins generate one tab but can not
modify an existing one. Maybe some of my colleagues more familiar with
the web interface have some ideas.
On Tue, Jan 14, 2014 at 3:23 PM, Gareth Bult <gar...@linux.co.uk> wrote:
>>It's because this in your email:
>>"For now I'm doing this using template tags and while sustainable, it's less
>>than ideal."
>
> Ahh, Ok, just to clarify;
>
> When working with replica's, I'm relying on having a tag in the template to
> specify
> the image id of the instance's replica. This is not really ideal as it doesn't
> provide for any interactivity in terms of choosing a replica, nor does it
> provide
> for any validation or checking. (or reference counting, replica's should be
> marked as
> used so nothing else can use them)
>
> Moving beyond this will need support from the GUI - which is beyond the scope
> of what
> I can do alone at the moment. So replica's work, but working with replicas
> isn't as
> "nice" is the rest of the interface.
>
> Ideally, for replica's (and this would apply to any storage mechanism that
> supports
> replicas) something like;
>
> On Templates, Update, where you have "add a disk", a new button for "add a
> replica".
> - this would have the same screen and do the same thing as "add a disk", but
> with one
> main difference, that disk must *not* be added to the VM then it's deployed,
> but instead
> handled by the storage infrastructure. (the advanced options would not be
> needed for
> add-a-replica)
>
> Then on "virtual machines->storage", as well as "add a new disk", we would
> need "add a new replica".
> Same deal, add a reference and call a script - but don't try to attach it to
> a VM.
>
> These are "relatively" trivial changes, but need to be done by someone
> familiar with the
> GUI who's working with the source ..
>
> Gareth.
>
> --
>
> Gareth Bult
> “The odds of hitting your target go up dramatically when you aim at it.”
> See the status of my current project at http://vdc-store.com
>
>
> ----- Original Message -----
> From: "Javier Fontan" <jfon...@opennebula.org>
> To: "Gareth Bult" <gar...@linux.co.uk>
> Cc: dev@lists.opennebula.org
> Sent: Tuesday, 14 January, 2014 1:48:48 PM
> Subject: Re: [one-dev] Re; VDC-Store
>
> I'll prepare the repository right away. I've been busy with some issues here.
>
> On Mon, Jan 13, 2014 at 12:52 PM, Gareth Bult <gar...@linux.co.uk> wrote:
>
>>>All our monitoring information (storage included) is stored in the
>>>object template. In the case of storage this is retrieved from the
>>>hosts. Is there any trouble with this?
>>
>> Sorry, not sure I understand fully - what was it you thought might be a
>> problem ??
>
> It's because this in your email:
>
> "For now I'm doing this using template tags and while sustainable,
> it's less than ideal."
>
> --
> Javier Fontán Muiños
> Developer
> OpenNebula - The Open Source Toolkit for Data Center Virtualization
> www.OpenNebula.org | @OpenNebula | github.com/jfontan
--
Javier Fontán Muiños
Developer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | @OpenNebula | github.com/jfontan
_______________________________________________
Dev mailing list
Dev@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/dev-opennebula.org
