[libvirt] EMOTIVE Cloud based in Libvirt

Hi, We can link in http://libvirt.org/apps.html EMOTIVE Cloud ( www.emotivecloud.net ) ? It is an interesting middleware based in Libvirt. Thank you

On 07/14/2011 01:31 PM, Alex Vaqué Brull wrote:
Hi,
We can link in http://libvirt.org/apps.html EMOTIVE Cloud ( www.emotivecloud.net ) ? It is an interesting middleware based in Libvirt.
Sure - we're always glad to advertise clients. Which category does it best belong in? Perhaps IaaS? Would you mind writing up a paragraph or so about the project, or is this blurb from the project home page good enough:
EMOTIVE Cloud (Elastic Management Of Tasks In Virtualized Environments)
The middleware EMOTIVE allows executing tasks and providing virtualized environments to the users with Xen, KVM or VirtualBox hypervisor. EMOTIVE main feature is VM management with different scheduling policies. It can be also used as a cloud provider and is very easy to extend thanks to its modular Web Services architecture.
Furthermore, it also has the capability to use external resources, like from the public Cloud of Amazon EC2. This feature allows to be involved in a Cloud federation (insourcing/outsorcing) and create public, private and hybrids clouds.
-- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org

Infrastructure as a Service (IaaS) Nimbus <http://www.nimbusproject.org/>Nimbus is an open-source toolkit focused on providing Infrastructure-as-a-Service (IaaS) capabilities to the scientific community. It uses libvirt for communication with all KVM and Xen virtual machines. <goog_319587068>EMOTIVE Cloud <http://www.emotivecloud.net>The EMOTIVE middleware allows executing tasks and providing virtualized environments to the users with Xen, KVM or VirtualBox hypervisor. EMOTIVE main feature is VM management with different scheduling policies. It can be also used as a cloud provider and is very easy to extend thanks to its modular Web Services architecture. 2011/7/14 Eric Blake <eblake@redhat.com>
On 07/14/2011 01:31 PM, Alex Vaqué Brull wrote:
Hi,
We can link in http://libvirt.org/apps.html EMOTIVE Cloud ( www.emotivecloud.net ) ? It is an interesting middleware based in Libvirt.
Sure - we're always glad to advertise clients. Which category does it best belong in? Perhaps IaaS? Would you mind writing up a paragraph or so about the project, or is this blurb from the project home page good enough:
EMOTIVE Cloud (Elastic Management Of Tasks In Virtualized Environments)
The middleware EMOTIVE allows executing tasks and providing virtualized
environments to the users with Xen, KVM or VirtualBox hypervisor. EMOTIVE main feature is VM management with different scheduling policies. It can be also used as a cloud provider and is very easy to extend thanks to its modular Web Services architecture.
Furthermore, it also has the capability to use external resources, like
from the public Cloud of Amazon EC2. This feature allows to be involved in a Cloud federation (insourcing/outsorcing) and create public, private and hybrids clouds.
-- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org

Thanks you can define EMOTIVE how IaaS.... I send you some idea.... Infrastructure as a Service (IaaS) EMOTIVE Cloud<http://www.emotivecloud.net/>The EMOTIVE middleware allows executing tasks and providing virtualized environments to the users with Xen, KVM or VirtualBox hypervisor. EMOTIVE main feature is VM management with different scheduling policies. It can be also used as a cloud provider and is very easy to extend thanks to its modular Web Services architecture.Thank you Àlex 2011/7/14 Alex Vaqué Brull <memfis@gmail.com>
Infrastructure as a Service (IaaS) Nimbus <http://www.nimbusproject.org/>Nimbus is an open-source toolkit focused on providing Infrastructure-as-a-Service (IaaS) capabilities to the scientific community. It uses libvirt for communication with all KVM and Xen virtual machines. <http://goog_319587068>EMOTIVE Cloud <http://www.emotivecloud.net>The EMOTIVE middleware allows executing tasks and providing virtualized environments to the users with Xen, KVM or VirtualBox hypervisor. EMOTIVE main feature is VM management with different scheduling policies. It can be also used as a cloud provider and is very easy to extend thanks to its modular Web Services architecture.
2011/7/14 Eric Blake <eblake@redhat.com>
On 07/14/2011 01:31 PM, Alex Vaqué Brull wrote:
Hi,
We can link in http://libvirt.org/apps.html EMOTIVE Cloud ( www.emotivecloud.net ) ? It is an interesting middleware based in Libvirt.
Sure - we're always glad to advertise clients. Which category does it best belong in? Perhaps IaaS? Would you mind writing up a paragraph or so about the project, or is this blurb from the project home page good enough:
EMOTIVE Cloud (Elastic Management Of Tasks In Virtualized Environments)
The middleware EMOTIVE allows executing tasks and providing virtualized
environments to the users with Xen, KVM or VirtualBox hypervisor. EMOTIVE main feature is VM management with different scheduling policies. It can be also used as a cloud provider and is very easy to extend thanks to its modular Web Services architecture.
Furthermore, it also has the capability to use external resources, like
from the public Cloud of Amazon EC2. This feature allows to be involved in a Cloud federation (insourcing/outsorcing) and create public, private and hybrids clouds.
-- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org

From: Alex Vaqué Brull <memfis@gmail.com> * docs/apps.html.in: Add EMOTIVE. --- Is this okay to push in your name? I've elided the AUTHORS change from this email, to avoid exposing your address in plaintext on the list archives, but that change should be obvious to figure out. AUTHORS | 1 + docs/apps.html.in | 11 +++++++++++ 2 files changed, 12 insertions(+), 0 deletions(-) diff --git a/AUTHORS b/AUTHORS index a8b315e..d6144f3 100644 --- a/AUTHORS +++ b/AUTHORS diff --git a/docs/apps.html.in b/docs/apps.html.in index b5160fa..28caff6 100644 --- a/docs/apps.html.in +++ b/docs/apps.html.in @@ -202,6 +202,16 @@ <h2><a name="iaas">Infrastructure as a Service (IaaS)</a></h2> <dl> + <dt><a href="http://www.emotivecloud.net">EMOTIVE Cloud</a></dt> + <dd>The EMOTIVE (Elastic Management Of Tasks In Virtualized + Environments) middleware allows executing tasks and providing + virtualized environments to the users with Xen, KVM or + VirtualBox hypervisor. EMOTIVE's main feature is VM management + with different scheduling policies. It can be also used as a + cloud provider and is very easy to extend thanks to its + modular Web Services architecture. + </dd> + <dt><a href="http://www.nimbusproject.org">Nimbus</a></dt> <dd> Nimbus is an open-source toolkit focused on providing -- 1.7.4.4

You can put my name but I am a simple collaborator from EMOTIVE Cloud . I am not the author from the middleware..... I developed some things and I am doing some little research about EMOTIVE. Tomorrow I ask to the autors to give me better name to put here. I am a simple collaborator.... It is possible to put only the URL to contact ? Thank you ALex On 14 July 2011 22:25, Eric Blake <eblake@redhat.com> wrote:
From: Alex Vaqué Brull <memfis@gmail.com>
* docs/apps.html.in: Add EMOTIVE. ---
Is this okay to push in your name? I've elided the AUTHORS change from this email, to avoid exposing your address in plaintext on the list archives, but that change should be obvious to figure out.
AUTHORS | 1 + docs/apps.html.in | 11 +++++++++++ 2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/AUTHORS b/AUTHORS index a8b315e..d6144f3 100644 --- a/AUTHORS +++ b/AUTHORS diff --git a/docs/apps.html.in b/docs/apps.html.in index b5160fa..28caff6 100644 --- a/docs/apps.html.in +++ b/docs/apps.html.in @@ -202,6 +202,16 @@ <h2><a name="iaas">Infrastructure as a Service (IaaS)</a></h2>
<dl> + <dt><a href="http://www.emotivecloud.net">EMOTIVE Cloud</a></dt> + <dd>The EMOTIVE (Elastic Management Of Tasks In Virtualized + Environments) middleware allows executing tasks and providing + virtualized environments to the users with Xen, KVM or + VirtualBox hypervisor. EMOTIVE's main feature is VM management + with different scheduling policies. It can be also used as a + cloud provider and is very easy to extend thanks to its + modular Web Services architecture. + </dd> + <dt><a href="http://www.nimbusproject.org">Nimbus</a></dt> <dd> Nimbus is an open-source toolkit focused on providing -- 1.7.4.4

On 07/14/2011 03:17 PM, Alex Vaqué Brull wrote:
You can put my name but I am a simple collaborator from EMOTIVE Cloud . I am not the author from the middleware..... I developed some things and I am doing some little research about EMOTIVE. Tomorrow I ask to the autors to give me better name to put here. I am a simple collaborator....
It is possible to put only the URL to contact ?
We've put the URL in the apps page, and I just rewrote the commit to be authored by me, only mentioning you by name in the commit message, rather than attributing the commit to you. At any rate, thanks for calling this project to our attention, and the web page should be updated within the hour! -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org

On 07/14/2011 03:33 PM, Eric Blake wrote:
On 07/14/2011 03:17 PM, Alex Vaqué Brull wrote:
You can put my name but I am a simple collaborator from EMOTIVE Cloud . I am not the author from the middleware..... I developed some things and I am doing some little research about EMOTIVE. Tomorrow I ask to the autors to give me better name to put here. I am a simple collaborator....
Oh, perhaps I see your confusion. I was talking about the "AUTHORS" file of libvirt, where we list the names of everyone that contributed a patch (basically, anyone that shows up as an author in libvirt.git), even for just one patch. It was not a reference to who authored EMOTIVE; rather the one paragraph mention in apps.html would take you to EMOTIVE's home page, where you can then learn about who authored EMOTIVE independently of libvirt contributions. But misunderstandings aside, thanks again for contributing today. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org

Good morning, I talked with Jordi Guitart, an author of EMOTIVE Cloud . And he say me that you can use this email "jordi.guitart@bsc.es" in http://libvirt.org/apps.html#iaas". Thanks a lot! Alex Vaqué 2011/7/14 Alex Vaqué Brull <memfis@gmail.com>
You can put my name but I am a simple collaborator from EMOTIVE Cloud . I am not the author from the middleware..... I developed some things and I am doing some little research about EMOTIVE. Tomorrow I ask to the autors to give me better name to put here. I am a simple collaborator....
It is possible to put only the URL to contact ?
Thank you ALex
On 14 July 2011 22:25, Eric Blake <eblake@redhat.com> wrote:
From: Alex Vaqué Brull <memfis@gmail.com>
* docs/apps.html.in: Add EMOTIVE. ---
Is this okay to push in your name? I've elided the AUTHORS change from this email, to avoid exposing your address in plaintext on the list archives, but that change should be obvious to figure out.
AUTHORS | 1 + docs/apps.html.in | 11 +++++++++++ 2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/AUTHORS b/AUTHORS index a8b315e..d6144f3 100644 --- a/AUTHORS +++ b/AUTHORS diff --git a/docs/apps.html.in b/docs/apps.html.in index b5160fa..28caff6 100644 --- a/docs/apps.html.in +++ b/docs/apps.html.in @@ -202,6 +202,16 @@ <h2><a name="iaas">Infrastructure as a Service (IaaS)</a></h2>
<dl> + <dt><a href="http://www.emotivecloud.net">EMOTIVE Cloud</a></dt> + <dd>The EMOTIVE (Elastic Management Of Tasks In Virtualized + Environments) middleware allows executing tasks and providing + virtualized environments to the users with Xen, KVM or + VirtualBox hypervisor. EMOTIVE's main feature is VM management + with different scheduling policies. It can be also used as a + cloud provider and is very easy to extend thanks to its + modular Web Services architecture. + </dd> + <dt><a href="http://www.nimbusproject.org">Nimbus</a></dt> <dd> Nimbus is an open-source toolkit focused on providing -- 1.7.4.4
participants (2)
-
Alex Vaqué Brull
-
Eric Blake