Submitting Kimchi project as an oVirt incubator project
Hi, Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment. We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user. More information about Kimchi is available at: http://github.com/kimchi-project/kimchi Let me know if there is additional information I can provide about the project. Regards, Anthony Liguori
Hi Anthony, It looks great, Is it used for starting machines on your local machine? (by local I mean the machine Kimchi is installed on) Livnat On 07/24/2013 06:22 PM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
Livnat Peer <lpeer@redhat.com> writes:
Hi Anthony, It looks great, Is it used for starting machines on your local machine? (by local I mean the machine Kimchi is installed on)
Yes. It's specifically limited to that use case too. It will never have a global database or anything like that. Regards, Anthony Liguori
Livnat
On 07/24/2013 06:22 PM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 07/24/2013 11:22 PM, Anthony Liguori wrote:
Livnat Peer <lpeer@redhat.com> writes:
Hi Anthony, It looks great, Is it used for starting machines on your local machine? (by local I mean the machine Kimchi is installed on)
Yes. It's specifically limited to that use case too. It will never have a global database or anything like that.
Regards,
Anthony Liguori
Perfect, I would use it myself. I think it is really missing in the current oVirt palette. +1
Livnat
On 07/24/2013 06:22 PM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 07/24/2013 11:22 AM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
The ovirt-node team is very excited by this project. We can't wait to get it incorporated into an ovirt-node build. Mike
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 07/24/2013 06:22 PM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
hi Anthony, I think it will be great to compliment the ovirt solution. Is the idea to try and match the user portal/power user portal look and feel / style? I think its important to try and make it feel its coming from the same family. we'll VMs and templates be portable from one to the other (via ovf? something else?) show list of VMs from a remote ovirt-engine as well? do i understand correctly its a simplified web based "virt-manager", or 'server oriented' boxes, or am i missing something? (say, what's the envisioned roadmap of development for features?) Thanks, Itamar
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
----- Original Message ----- | From: "Itamar Heim" <iheim@redhat.com> | To: "Anthony Liguori" <aliguori@us.ibm.com> | Cc: "board" <board@ovirt.org> | Sent: Friday, July 26, 2013 6:59:29 AM | Subject: Re: Submitting Kimchi project as an oVirt incubator project | | On 07/24/2013 06:22 PM, Anthony Liguori wrote: | > | > Hi, | > | > Kimchi is a web-based management tool meant as an entry level tool for | > interacting with KVM. It compliments oVirt well allowing the project to | > provide both a starting point for virtualization that can expand to a | > large enterprise environment. | > | > We believe that Kimchi will benefit by being part of the oVirt umbrella | > as we can work together to make the interfaces consistent with the oVirt | > UI and integrate with ovirt-node to provide a complete stand alone | > virtualization experience for an end-user. | Indeed much needed for various use cases from my talks in various events. People would often ask me about managing a 1-2 hosts setup and Kimchi fits right in and I'll be happy to demo it once I have the opportunity. | hi Anthony, | | I think it will be great to compliment the ovirt solution. | Is the idea to try and match the user portal/power user portal look and | feel / style? | I think its important to try and make it feel its coming from the same | family. | we'll VMs and templates be portable from one to the other (via ovf? | something else?) | show list of VMs from a remote ovirt-engine as well? | | do i understand correctly its a simplified web based "virt-manager", or | 'server oriented' boxes, or am i missing something? | (say, what's the envisioned roadmap of development for features?) | | Thanks, | Itamar | I agree keeping user experience and interoperability are important to make it a valuable member of the oVirt ecosystem. This should allow Kimchi users to grow their setups on the one hand, while test a specific VM locally using Kimchy on the other hand. So +1 from me, as long as we make sure users can benefit both projects together without needing to re-create their guests. | > | > More information about Kimchi is available at: | > | > http://github.com/kimchi-project/kimchi | > | > Let me know if there is additional information I can provide about the | > project. | > | > Regards, | > | > Anthony Liguori | > | > _______________________________________________ | > Board mailing list | > Board@ovirt.org | > http://lists.ovirt.org/mailman/listinfo/board | > | | _______________________________________________ | Board mailing list | Board@ovirt.org | http://lists.ovirt.org/mailman/listinfo/board |
Doron Fediuck <dfediuck@redhat.com> writes:
----- Original Message ----- | From: "Itamar Heim" <iheim@redhat.com> | To: "Anthony Liguori" <aliguori@us.ibm.com> | Cc: "board" <board@ovirt.org> | Sent: Friday, July 26, 2013 6:59:29 AM | Subject: Re: Submitting Kimchi project as an oVirt incubator project | | On 07/24/2013 06:22 PM, Anthony Liguori wrote: | > | > Hi, | > | > Kimchi is a web-based management tool meant as an entry level tool for | > interacting with KVM. It compliments oVirt well allowing the project to | > provide both a starting point for virtualization that can expand to a | > large enterprise environment. | > | > We believe that Kimchi will benefit by being part of the oVirt umbrella | > as we can work together to make the interfaces consistent with the oVirt | > UI and integrate with ovirt-node to provide a complete stand alone | > virtualization experience for an end-user. |
Indeed much needed for various use cases from my talks in various events. People would often ask me about managing a 1-2 hosts setup and Kimchi fits right in and I'll be happy to demo it once I have the opportunity.
Yes, this is what started the project. We've been getting a lot of feedback from users/customers and the piece that we keep hearing is that it's too hard to get started with a small deployment. This is KVM feedback in general, not just oVirt related.
| do i understand correctly its a simplified web based "virt-manager", or | 'server oriented' boxes, or am i missing something? | (say, what's the envisioned roadmap of development for features?) | | Thanks, | Itamar |
I agree keeping user experience and interoperability are important to make it a valuable member of the oVirt ecosystem. This should allow Kimchi users to grow their setups on the one hand, while test a specific VM locally using Kimchy on the other hand.
Yes. From a development point of view, I'd prefer that we focus on the "hand off" experience verses trying to converge the CSS themes or anything like that though. I think the later is a good idea in the very long term but in the short term, there's much more value in the former.
So +1 from me, as long as we make sure users can benefit both projects together without needing to re-create their guests.
Thanks! Regards, Anthony Liguori
| > | > More information about Kimchi is available at: | > | > http://github.com/kimchi-project/kimchi | > | > Let me know if there is additional information I can provide about the | > project. | > | > Regards, | > | > Anthony Liguori | > | > _______________________________________________ | > Board mailing list | > Board@ovirt.org | > http://lists.ovirt.org/mailman/listinfo/board | > | | _______________________________________________ | Board mailing list | Board@ovirt.org | http://lists.ovirt.org/mailman/listinfo/board |
On 07/26/2013 06:59 AM, Itamar Heim wrote:
On 07/24/2013 06:22 PM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
hi Anthony,
I think it will be great to compliment the ovirt solution. Is the idea to try and match the user portal/power user portal look and feel / style? I think its important to try and make it feel its coming from the same family. we'll VMs and templates be portable from one to the other (via ovf? something else?)
I think it is a nice idea. A way I see such an integration happening is by being able to export a VM in oVirt into an ova file (OVF and the images) and then being able to import this file into Kimchi, and of course the other way around. An interesting point to note here is that oVirt and Kimchi should be aligned on the OVF format they use (OVF is supposedly standard but de-facto it is not exactly so). I could see myself using the above functionality :)
show list of VMs from a remote ovirt-engine as well?
do i understand correctly its a simplified web based "virt-manager", or 'server oriented' boxes, or am i missing something? (say, what's the envisioned roadmap of development for features?)
Thanks, Itamar
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
Livnat Peer <lpeer@redhat.com> writes:
On 07/26/2013 06:59 AM, Itamar Heim wrote:
we'll VMs and templates be portable from one to the other (via ovf? something else?)
I think it is a nice idea. A way I see such an integration happening is by being able to export a VM in oVirt into an ova file (OVF and the images) and then being able to import this file into Kimchi, and of course the other way around.
An interesting point to note here is that oVirt and Kimchi should be aligned on the OVF format they use (OVF is supposedly standard but de-facto it is not exactly so).
Exactly :-/ OVF is probably a handy way of communicating the metadata. An open question is storage/network configuration. We have the concept of storage/network pools that are implemented strictly in terms of libvirt. It would be really handy to be able to have ovirt automatically create a storage pool from one defined in Kimchi for the entire datacenter so that you can do mobility. If we do it right, the concept could also extend beyond Kimchi for a number of libvirt-based tools. Regards, Anthony Liguori
Itamar Heim <iheim@redhat.com> writes:
On 07/24/2013 06:22 PM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
hi Anthony,
I think it will be great to compliment the ovirt solution. Is the idea to try and match the user portal/power user portal look and feel / style?
That would be ideal although not a short term goal. What we really want is for there to be a seamless transition between Kimchi and oVirt-engine. We envision a user install Kimchi (via a Fedora based oVirt node ISO), playing around with KVM, creating some guests, and then deciding they need more. The user would then initial bringing the node into a datacenter and ideally, would be able to import those VMs into ovirt-engine in a seamless fashion. This is the bigger focus for us vs. just making the look and feel the same.
I think its important to try and make it feel its coming from the same family. we'll VMs and templates be portable from one to the other (via ovf? something else?)
Yes, this is an explicit goal.
show list of VMs from a remote ovirt-engine as well?
The scope right now is narrowly focused on single node. I personally think it's important to avoid creeping the scope beyond that. It really is about getting someone to do useful things with KVM with the absolute smallest number of steps.
do i understand correctly its a simplified web based "virt-manager", or 'server oriented' boxes, or am i missing something?
Web-based virt-manager is a good starting point. The biggest difference though is that while virt-manager is a UI designed around exposing the features of libvirt, Kimchi's UI design is much more oriented to a particular type of user and simplifying the workflows that they'd have. The user we focus on is the "tire-kicker". They are primarily Windows users who may already have experience with VMware but no direct experience with oVirt or KVM.
(say, what's the envisioned roadmap of development for features?)
https://github.com/kimchi-project/kimchi/wiki/TODO Regards, Anthony Liguori
Thanks, Itamar
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 07/29/2013 03:55 PM, Anthony Liguori wrote:
Itamar Heim <iheim@redhat.com> writes:
On 07/24/2013 06:22 PM, Anthony Liguori wrote:
Hi,
Kimchi is a web-based management tool meant as an entry level tool for interacting with KVM. It compliments oVirt well allowing the project to provide both a starting point for virtualization that can expand to a large enterprise environment.
We believe that Kimchi will benefit by being part of the oVirt umbrella as we can work together to make the interfaces consistent with the oVirt UI and integrate with ovirt-node to provide a complete stand alone virtualization experience for an end-user.
hi Anthony,
I think it will be great to compliment the ovirt solution. Is the idea to try and match the user portal/power user portal look and feel / style?
That would be ideal although not a short term goal.
What we really want is for there to be a seamless transition between Kimchi and oVirt-engine. We envision a user install Kimchi (via a Fedora based oVirt node ISO), playing around with KVM, creating some guests, and then deciding they need more.
The user would then initial bringing the node into a datacenter and ideally, would be able to import those VMs into ovirt-engine in a seamless fashion.
to make this as seamless as possible, creating the files (or at least symlinks to them) in the storage domain file layout will allow the easiest importing as "an existing storage domain"?
This is the bigger focus for us vs. just making the look and feel the same.
I think its important to try and make it feel its coming from the same family. we'll VMs and templates be portable from one to the other (via ovf? something else?)
Yes, this is an explicit goal.
show list of VMs from a remote ovirt-engine as well?
The scope right now is narrowly focused on single node. I personally think it's important to avoid creeping the scope beyond that.
It really is about getting someone to do useful things with KVM with the absolute smallest number of steps.
do i understand correctly its a simplified web based "virt-manager", or 'server oriented' boxes, or am i missing something?
Web-based virt-manager is a good starting point. The biggest difference though is that while virt-manager is a UI designed around exposing the features of libvirt, Kimchi's UI design is much more oriented to a particular type of user and simplifying the workflows that they'd have.
The user we focus on is the "tire-kicker". They are primarily Windows users who may already have experience with VMware but no direct experience with oVirt or KVM.
(say, what's the envisioned roadmap of development for features?)
what's define/discover peers?
Regards,
Anthony Liguori
Thanks, Itamar
More information about Kimchi is available at:
http://github.com/kimchi-project/kimchi
Let me know if there is additional information I can provide about the project.
Regards,
Anthony Liguori
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
participants (5)
-
Anthony Liguori -
Doron Fediuck -
Itamar Heim -
Livnat Peer -
Mike Burns