What I would like to see in the ! next version is pxe boot of the nodes. Probably not easy to achieve because of dependency on dhcp.

From: "Dotan Paz" <dpaz(a)redhat.com&gt; To: "Itamar Heim" <iheim(a)redhat.com&gt; Cc: users(a)ovirt.org Sent: Thursday, August 22, 2013 3:14:42 PM Subject: Re: [Users] so, what do you want next in oVirt? Hi Itamar , I would be happy to throw in an idea . I think oVirt is lacking the ability to assign permissions on multiple VMs at once . For example , if I want to grant permissions to a certain user on 30 VMs , I need to do it manually (or with some script). I think this feature is essential for an enterprise aimed product. Also it would be really cool to have an ability to create groups within oVirt and not in the directory, and grant a group permissions on a vm instead of adding them one by one . For example , creating a group called Dev and give the group permissions on all relevant VMs instead of adding each user one by one . Hope to see this feature in the next versions . Thanks, Dotan Paz ,

----- Original Message ----- From: "Itamar Heim" <iheim(a)redhat.com&gt; To: users(a)ovirt.org Sent: Wednesday, August 21, 2013 12:19:16 AM Subject: [Users] so, what do you want next in oVirt? earlier in the year we did a survey for feature requests / improvements / etc. since a lot of things were added, and priorities usually change, I'd like to ask again for "what do you need the most from oVirt / what are your pain points" next? below[1] I've listed my understanding of what already went in from previous survey requests (to various degrees of coverage). Thanks, Itamar [1] from the top 12 V Allow disk resize V Integrate Nagios/Zabbix monitoring - via a ui plugin V Highly Available engine - via hosted engine[2] V Open vSwitch integration - via neutron integration X Allow cloning VMs without template ? Enable hypervisor upgrade/updates through engine[3] V Allow engine on an oVirt hosted VM - via hosted engine[2] V Enable guest configuration (root password, SSH keys, network) via guest agent in engine - via cloud-init X Integrate v2v into engine ? Bond/extend ovirtmgmt with a second network for HA/increased bandwidth[4] X Integrate scheduling of snapshots and VM export for backups in engine[5] V Spice – support Google Chrome - via mime based launch Other items mentioned in previous survey which should be covered by now: - Fix timeout when adding local host during all-in-one configuration - Fix engine set-up when SELinux is disabled - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) - Allow multiple VMs to be deployed from the same template at the same time - ISO domains on local/GlusterS - Show IP addresses in Virtual Machines->Network Interfaces - OpenStack Quantum support (now called Neutron) - noVNC support - Support spice.html5 and websocket proxy - Add other guest OSes to list - Port oVirt guest agent to Ubuntu[6] - SLA - Allow resource time-sharing - Spice - Mac client (via mime based launch) - Spice - port XPI plug-in to Windows (not sure this will happen, but mime based launch allows using firefox now) - Spice - client for Ubuntu/Debian (should be covered via mime based launch) [2] hosted engine is in active development, but not released yet. [3] host update is supported, but not for general yum update. [4] a lot of improvements were done in this space, but i'm not sure if they cover this exact use case [5] backup api is now being pushed to master, and orchestration of backups should probably happen via 3rd part backup vendors? [6] I'm not sure packaging exists yet, but ubuntu is covered for the basic functionality of the guest agent. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Dne 20.8.2013 23:19, Itamar Heim napsal(a): > earlier in the year we did a survey for feature requests / > improvements / etc. > > since a lot of things were added, and priorities usually change, I'd > like to ask again for "what do you need the most from oVirt / what are > your pain points" next? > > below[1] I've listed my understanding of what already went in from > previous survey requests (to various degrees of coverage). > > Thanks, > Itamar > > [1] from the top 12 > V Allow disk resize > V Integrate Nagios/Zabbix monitoring - via a ui plugin > V Highly Available engine - via hosted engine[2] > V Open vSwitch integration - via neutron integration > X Allow cloning VMs without template > ? Enable hypervisor upgrade/updates through engine[3] > V Allow engine on an oVirt hosted VM - via hosted engine[2] > V Enable guest configuration (root password, SSH keys, network) via > guest agent in engine - via cloud-init > X Integrate v2v into engine > ? Bond/extend ovirtmgmt with a second network for HA/increased > bandwidth[4] > X Integrate scheduling of snapshots and VM export for backups in > engine[5] > V Spice – support Google Chrome - via mime based launch > > > Other items mentioned in previous survey which should be covered by now: > - Fix timeout when adding local host during all-in-one configuration > - Fix engine set-up when SELinux is disabled > - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) > - Allow multiple VMs to be deployed from the same template at the same > time > - ISO domains on local/GlusterS > - Show IP addresses in Virtual Machines->Network Interfaces > - OpenStack Quantum support (now called Neutron) > - noVNC support > - Support spice.html5 and websocket proxy > - Add other guest OSes to list > - Port oVirt guest agent to Ubuntu[6] > - SLA - Allow resource time-sharing > - Spice - Mac client (via mime based launch) > - Spice - port XPI plug-in to Windows (not sure this will happen, but > mime based launch allows using firefox now) > - Spice - client for Ubuntu/Debian (should be covered via mime based > launch) > > > [2] hosted engine is in active development, but not released yet. > [3] host update is supported, but not for general yum update. > [4] a lot of improvements were done in this space, but i'm not sure if > they cover this exact use case > [5] backup api is now being pushed to master, and orchestration of > backups should probably happen via 3rd part backup vendors? > [6] I'm not sure packaging exists yet, but ubuntu is covered for the > basic functionality of the guest agent. > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users Some time ago I was on IBM kvm virtualization preview and they show us gold image feature and I like it. It could be implemented in oVirt ;-) more info: http://pic.dhe.ibm.com/infocenter/ibmfsb/v2r1/index.jsp?topic=%2Fcom.ibm....

Next nice feature could be importing existing iSCSI domain.

Possibility of direct use of HW by VM.

and the absolutely fantastic feature would be to create clusters from Intel and AMD processors together!

Thank you ;-) _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Dne 27.8.2013 17:34, Itamar Heim napsal(a): On 08/27/2013 06:27 PM, Jakub Bittner wrote: > >> Dne 20.8.2013 23:19, Itamar Heim napsal(a): >> >>> earlier in the year we did a survey for feature requests / >>> improvements / etc. >>> >>> since a lot of things were added, and priorities usually change, I'd >>> like to ask again for "what do you need the most from oVirt / what are >>> your pain points" next? >>> >>> below[1] I've listed my understanding of what already went in from >>> previous survey requests (to various degrees of coverage). >>> >>> Thanks, >>> Itamar >>> >>> [1] from the top 12 >>> V Allow disk resize >>> V Integrate Nagios/Zabbix monitoring - via a ui plugin >>> V Highly Available engine - via hosted engine[2] >>> V Open vSwitch integration - via neutron integration >>> X Allow cloning VMs without template >>> ? Enable hypervisor upgrade/updates through engine[3] >>> V Allow engine on an oVirt hosted VM - via hosted engine[2] >>> V Enable guest configuration (root password, SSH keys, network) via >>> guest agent in engine - via cloud-init >>> X Integrate v2v into engine >>> ? Bond/extend ovirtmgmt with a second network for HA/increased >>> bandwidth[4] >>> X Integrate scheduling of snapshots and VM export for backups in >>> engine[5] >>> V Spice – support Google Chrome - via mime based launch >>> >>> >>> Other items mentioned in previous survey which should be covered by now: >>> - Fix timeout when adding local host during all-in-one configuration >>> - Fix engine set-up when SELinux is disabled >>> - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) >>> - Allow multiple VMs to be deployed from the same template at the same >>> time >>> - ISO domains on local/GlusterS >>> - Show IP addresses in Virtual Machines->Network Interfaces >>> - OpenStack Quantum support (now called Neutron) >>> - noVNC support >>> - Support spice.html5 and websocket proxy >>> - Add other guest OSes to list >>> - Port oVirt guest agent to Ubuntu[6] >>> - SLA - Allow resource time-sharing >>> - Spice - Mac client (via mime based launch) >>> - Spice - port XPI plug-in to Windows (not sure this will happen, but >>> mime based launch allows using firefox now) >>> - Spice - client for Ubuntu/Debian (should be covered via mime based >>> launch) >>> >>> >>> [2] hosted engine is in active development, but not released yet. >>> [3] host update is supported, but not for general yum update. >>> [4] a lot of improvements were done in this space, but i'm not sure if >>> they cover this exact use case >>> [5] backup api is now being pushed to master, and orchestration of >>> backups should probably happen via 3rd part backup vendors? >>> [6] I'm not sure packaging exists yet, but ubuntu is covered for the >>> basic functionality of the guest agent. >>> ______________________________**_________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org... >>> >> >> Some time ago I was on IBM kvm virtualization preview and they show us >> gold image feature and I like it. It could be implemented in oVirt ;-) >> >> more info: >> http://pic.dhe.ibm.com/**infocenter/ibmfsb/v2r1/index.** >> jsp?topic=%2Fcom.ibm.**sbsolutions.doc%**2FugGoldImageOverview.htm<htt... >> > > Can you explain how you view this as different from ovirt templates? > > >> Next nice feature could be importing existing iSCSI domain. >> > > importing any data storage domain i assume? > Yes. > Possibility of direct use of HW by VM. >> > > such as? > Telephone modem. PCI-express cards. Graphic cards > > and the absolutely fantastic feature would be to create clusters from >> Intel and AMD processors together! >> > > well, you can do that today if you want to via a config change. the only > thing is live migration won't work (you should probably use -cpu host to > get best performance, since live migration won't be used anyway) > (well, in theory we could live migrate only between hosts of same cpu > vendor, but not sure interesting enough use case to make cluster and > scheduling more complex). though you can do that part on your own with the > new pluggable scheduler, or use -cpu host to get max performance if you > don't care about live migration > > From my point of view it is better to have slower cpu performance and possibility to use all of our servers in cluster. I would like to have live migration available from intel to amd. The problem is only in cpu instruction sets? If so, I can use only common sets. Another feature which I forgot is network between VMs and mirroring traffic. Both configurable from WUI. >> Thank you ;-) >> >> >> ______________________________**_________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org... >> >> > ______________________________**_________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org...

> importing any data storage domain i assume? > Yes. > Possibility of direct use of HW by VM. >> > > such as? > Telephone modem. PCI-express cards. Graphic cards

> > and the absolutely fantastic feature would be to create clusters from >> Intel and AMD processors together! >> > > well, you can do that today if you want to via a config change. the only > thing is live migration won't work (you should probably use -cpu host to > get best performance, since live migration won't be used anyway) > (well, in theory we could live migrate only between hosts of same cpu > vendor, but not sure interesting enough use case to make cluster and > scheduling more complex). though you can do that part on your own with the > new pluggable scheduler, or use -cpu host to get max performance if you > don't care about live migration > > From my point of view it is better to have slower cpu performance and possibility to use all of our servers in cluster. I would like to have live migration available from intel to amd. The problem is only in cpu instruction sets? If so, I can use only common sets. Another feature which I forgot is network between VMs and mirroring traffic. Both configurable from WUI. >> Thank you ;-) >> >> >> ______________________________**_________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org... >> >> > ______________________________**_________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org...

earlier in the year we did a survey for feature requests / improvements / etc. since a lot of things were added, and priorities usually change, I'd like to ask again for "what do you need the most from oVirt / what are your pain points" next? below[1] I've listed my understanding of what already went in from previous survey requests (to various degrees of coverage).

On 08/21/2013 02:40 AM, Joop van de Wege wrote: > > What I would like to see in the ! next version is pxe boot of the nodes. > Probably not easy to achieve because of dependency on dhcp. Hi Joop, can you please give a bit more information on the use case / how you envision this? current thinking around bare metal provisioning of hosts is to extend the functionality around the foreman provider for this, but you may have other suggestions?

hi please add support from solaris , ubuntu and other OS's.

installation is a little hard specially in an evironment without internet.

regards, On Mon, Sep 2, 2013 at 7:43 PM, Doron Fediuck <dfediuck(a)redhat.com <mailto:dfediuck@redhat.com>> wrote: ----- Original Message ----- | From: "Karli Sjöberg" <Karli.Sjoberg(a)slu.se <mailto:Karli.Sjoberg@slu.se>> | To: "Itamar Heim" <iheim(a)redhat.com <mailto:iheim@redhat.com>> | Cc: users(a)ovirt.org <mailto:users@ovirt.org>, "Jan-Olov Persson" <jan-olov.persson(a)slu.se <mailto:jan-olov.persson@slu.se>> | Sent: Monday, September 2, 2013 10:42:52 AM | Subject: Re: [Users] so, what do you want next in oVirt? | | Hi, | | I would like to see a more advanced type of Power-Saving Cluster policy, | where an empty Host gets put into a sleep-mode, so that it draws as little | power as possible and can be awoken by engine when VM's starts to use more | resources. | | A typical scenario would be that all VM's are spread evenly over Hosts during | day-time, when customers are actively using their VM's. But then during | off-hours, VM's gets clumped up into maybe one or two Hosts, and the other | Hosts can be put to sleep to save energy, and then woken up in the morning | again. | | /Karli | Hi Karli, this should be achievable for you in 3.3 with some minor work on your side; In oVirt 3.3 we introduce the new scheduler, which allows you to run your own code when doing VM placement and load balancing. You can write your own load balancing logic replacing the built-in one, which will switch to power saving at a given time. Once a host has no running VMs, your balance logic can switch it into S3 state (sleep), and when needed or in a given time use wake-on-lan to resume all suspended hosts. If you want we can guide you through it post 3.3 release. Doron | tis 2013-08-20 klockan 17:19 -0400 skrev Itamar Heim: | | | earlier in the year we did a survey for feature requests / improvements | / etc. | | since a lot of things were added, and priorities usually change, I'd | like to ask again for "what do you need the most from oVirt / what are | your pain points" next? | | below[1] I've listed my understanding of what already went in from | previous survey requests (to various degrees of coverage). | | Thanks, | Itamar | | [1] from the top 12 | V Allow disk resize | V Integrate Nagios/Zabbix monitoring - via a ui plugin | V Highly Available engine - via hosted engine[2] | V Open vSwitch integration - via neutron integration | X Allow cloning VMs without template | ? Enable hypervisor upgrade/updates through engine[3] | V Allow engine on an oVirt hosted VM - via hosted engine[2] | V Enable guest configuration (root password, SSH keys, network) via | guest agent in engine - via cloud-init | X Integrate v2v into engine | ? Bond/extend ovirtmgmt with a second network for HA/increased | bandwidth[4] | X Integrate scheduling of snapshots and VM export for backups in | engine[5] | V Spice – support Google Chrome - via mime based launch | | | Other items mentioned in previous survey which should be covered by now: | - Fix timeout when adding local host during all-in-one configuration | - Fix engine set-up when SELinux is disabled | - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) | - Allow multiple VMs to be deployed from the same template at the same | time | - ISO domains on local/GlusterS | - Show IP addresses in Virtual Machines->Network Interfaces | - OpenStack Quantum support (now called Neutron) | - noVNC support | - Support spice.html5 and websocket proxy | - Add other guest OSes to list | - Port oVirt guest agent to Ubuntu[6] | - SLA - Allow resource time-sharing | - Spice - Mac client (via mime based launch) | - Spice - port XPI plug-in to Windows (not sure this will happen, but | mime based launch allows using firefox now) | - Spice - client for Ubuntu/Debian (should be covered via mime based | launch) | | | [2] hosted engine is in active development, but not released yet. | [3] host update is supported, but not for general yum update. | [4] a lot of improvements were done in this space, but i'm not sure if | they cover this exact use case | [5] backup api is now being pushed to master, and orchestration of | backups should probably happen via 3rd part backup vendors? | [6] I'm not sure packaging exists yet, but ubuntu is covered for the | basic functionality of the guest agent. | _______________________________________________ | Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> | http://lists.ovirt.org/mailman/listinfo/users | | | -- | | Med Vänliga Hälsningar | ------------------------------------------------------------------------------- | Karli Sjöberg | Swedish University of Agricultural Sciences | Box 7079 (Visiting Address Kronåsvägen 8) | S-750 07 Uppsala, Sweden | Phone: +46-(0)18-67 15 66 | karli.sjoberg(a)slu.se <mailto:karli.sjoberg@slu.se> | | _______________________________________________ | Users mailing list | Users(a)ovirt.org <mailto:Users@ovirt.org> | http://lists.ovirt.org/mailman/listinfo/users | _______________________________________________ Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

hi again ubuntu agent should be add in the list like vmware .

about installation i have to install ovirt packages by local repository and there is problem in this status and in adding host to ovirt manager you need to install packages that need to internet .

regards, On Tue, Sep 3, 2013 at 1:26 PM, Itamar Heim <iheim(a)redhat.com <mailto:iheim@redhat.com>> wrote: On 09/03/2013 10:53 AM, alireza sadeh seighalan wrote: hi please add support from solaris , ubuntu and other OS's. we've added in 3.3 ubuntu and suse as guest os's - i can't tell you if they work or not. you can now easily add on your own more OSs as well: http://www.ovirt.org/OS_info guest agent for ubuntu should be working. > installation is a little hard specially in an evironment without > internet. can you please share more on the issues you faced? thanks, Itamar regards, On Mon, Sep 2, 2013 at 7:43 PM, Doron Fediuck <dfediuck(a)redhat.com <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com>>> wrote: ----- Original Message ----- | From: "Karli Sjöberg" <Karli.Sjoberg(a)slu.se <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se>>> | To: "Itamar Heim" <iheim(a)redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>> | Cc: users(a)ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>>, "Jan-Olov Persson" <jan-olov.persson(a)slu.se <mailto:jan-olov.persson@slu.se> <mailto:jan-olov.persson@slu.__se <mailto:jan-olov.persson@slu.se>>> | Sent: Monday, September 2, 2013 10:42:52 AM | Subject: Re: [Users] so, what do you want next in oVirt? | | Hi, | | I would like to see a more advanced type of Power-Saving Cluster policy, | where an empty Host gets put into a sleep-mode, so that it draws as little | power as possible and can be awoken by engine when VM's starts to use more | resources. | | A typical scenario would be that all VM's are spread evenly over Hosts during | day-time, when customers are actively using their VM's. But then during | off-hours, VM's gets clumped up into maybe one or two Hosts, and the other | Hosts can be put to sleep to save energy, and then woken up in the morning | again. | | /Karli | Hi Karli, this should be achievable for you in 3.3 with some minor work on your side; In oVirt 3.3 we introduce the new scheduler, which allows you to run your own code when doing VM placement and load balancing. You can write your own load balancing logic replacing the built-in one, which will switch to power saving at a given time. Once a host has no running VMs, your balance logic can switch it into S3 state (sleep), and when needed or in a given time use wake-on-lan to resume all suspended hosts. If you want we can guide you through it post 3.3 release. Doron | tis 2013-08-20 klockan 17:19 -0400 skrev Itamar Heim: | | | earlier in the year we did a survey for feature requests / improvements | / etc. | | since a lot of things were added, and priorities usually change, I'd | like to ask again for "what do you need the most from oVirt / what are | your pain points" next? | | below[1] I've listed my understanding of what already went in from | previous survey requests (to various degrees of coverage). | | Thanks, | Itamar | | [1] from the top 12 | V Allow disk resize | V Integrate Nagios/Zabbix monitoring - via a ui plugin | V Highly Available engine - via hosted engine[2] | V Open vSwitch integration - via neutron integration | X Allow cloning VMs without template | ? Enable hypervisor upgrade/updates through engine[3] | V Allow engine on an oVirt hosted VM - via hosted engine[2] | V Enable guest configuration (root password, SSH keys, network) via | guest agent in engine - via cloud-init | X Integrate v2v into engine | ? Bond/extend ovirtmgmt with a second network for HA/increased | bandwidth[4] | X Integrate scheduling of snapshots and VM export for backups in | engine[5] | V Spice – support Google Chrome - via mime based launch | | | Other items mentioned in previous survey which should be covered by now: | - Fix timeout when adding local host during all-in-one configuration | - Fix engine set-up when SELinux is disabled | - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) | - Allow multiple VMs to be deployed from the same template at the same | time | - ISO domains on local/GlusterS | - Show IP addresses in Virtual Machines->Network Interfaces | - OpenStack Quantum support (now called Neutron) | - noVNC support | - Support spice.html5 and websocket proxy | - Add other guest OSes to list | - Port oVirt guest agent to Ubuntu[6] | - SLA - Allow resource time-sharing | - Spice - Mac client (via mime based launch) | - Spice - port XPI plug-in to Windows (not sure this will happen, but | mime based launch allows using firefox now) | - Spice - client for Ubuntu/Debian (should be covered via mime based | launch) | | | [2] hosted engine is in active development, but not released yet. | [3] host update is supported, but not for general yum update. | [4] a lot of improvements were done in this space, but i'm not sure if | they cover this exact use case | [5] backup api is now being pushed to master, and orchestration of | backups should probably happen via 3rd part backup vendors? | [6] I'm not sure packaging exists yet, but ubuntu is covered for the | basic functionality of the guest agent. | _________________________________________________ | Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> | http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users> | | | -- | | Med Vänliga Hälsningar | ------------------------------__------------------------------__------------------- | Karli Sjöberg | Swedish University of Agricultural Sciences | Box 7079 (Visiting Address Kronåsvägen 8) | S-750 07 Uppsala, Sweden | Phone: +46-(0)18-67 15 66 | karli.sjoberg(a)slu.se <mailto:karli.sjoberg@slu.se> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se>> | | _________________________________________________ | Users mailing list | Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> | http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users> | _________________________________________________ Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users> _________________________________________________ Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>

hi ubuntu should list in ther agent list. when you want to create vm's in the operating list drop down menu. please dont forget other OS's. regards

On Tue, Sep 3, 2013 at 4:07 PM, Itamar Heim <iheim(a)redhat.com <mailto:iheim@redhat.com>> wrote: On 09/03/2013 12:02 PM, alireza sadeh seighalan wrote: hi again ubuntu agent should be add in the list like vmware . added in which list? > about installation i have to install ovirt packages by local repository and there is problem in this status and in adding host to ovirt manager you need to install packages that need to internet . why do you need internet? you just need the host to be configured with a repo containing the packages, which can be local as well? regards, On Tue, Sep 3, 2013 at 1:26 PM, Itamar Heim <iheim(a)redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>> wrote: On 09/03/2013 10:53 AM, alireza sadeh seighalan wrote: hi please add support from solaris , ubuntu and other OS's. we've added in 3.3 ubuntu and suse as guest os's - i can't tell you if they work or not. you can now easily add on your own more OSs as well: http://www.ovirt.org/OS_info guest agent for ubuntu should be working. > installation is a little hard specially in an evironment without > internet. can you please share more on the issues you faced? thanks, Itamar regards, On Mon, Sep 2, 2013 at 7:43 PM, Doron Fediuck <dfediuck(a)redhat.com <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com>> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com>>>> wrote: ----- Original Message ----- | From: "Karli Sjöberg" <Karli.Sjoberg(a)slu.se <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se>> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se>>>__> | To: "Itamar Heim" <iheim(a)redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>> <mailto:iheim@redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>>> | Cc: users(a)ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>> <mailto:users@ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>, "Jan-Olov Persson" <jan-olov.persson(a)slu.se <mailto:jan-olov.persson@slu.se> <mailto:jan-olov.persson@slu.__se <mailto:jan-olov.persson@slu.se>> <mailto:jan-olov.persson@slu. <mailto:jan-olov.persson@slu.>____se <mailto:jan-olov.persson@slu.__se <mailto:jan-olov.persson@slu.se>>>> | Sent: Monday, September 2, 2013 10:42:52 AM | Subject: Re: [Users] so, what do you want next in oVirt? | | Hi, | | I would like to see a more advanced type of Power-Saving Cluster policy, | where an empty Host gets put into a sleep-mode, so that it draws as little | power as possible and can be awoken by engine when VM's starts to use more | resources. | | A typical scenario would be that all VM's are spread evenly over Hosts during | day-time, when customers are actively using their VM's. But then during | off-hours, VM's gets clumped up into maybe one or two Hosts, and the other | Hosts can be put to sleep to save energy, and then woken up in the morning | again. | | /Karli | Hi Karli, this should be achievable for you in 3.3 with some minor work on your side; In oVirt 3.3 we introduce the new scheduler, which allows you to run your own code when doing VM placement and load balancing. You can write your own load balancing logic replacing the built-in one, which will switch to power saving at a given time. Once a host has no running VMs, your balance logic can switch it into S3 state (sleep), and when needed or in a given time use wake-on-lan to resume all suspended hosts. If you want we can guide you through it post 3.3 release. Doron | tis 2013-08-20 klockan 17:19 -0400 skrev Itamar Heim: | | | earlier in the year we did a survey for feature requests / improvements | / etc. | | since a lot of things were added, and priorities usually change, I'd | like to ask again for "what do you need the most from oVirt / what are | your pain points" next? | | below[1] I've listed my understanding of what already went in from | previous survey requests (to various degrees of coverage). | | Thanks, | Itamar | | [1] from the top 12 | V Allow disk resize | V Integrate Nagios/Zabbix monitoring - via a ui plugin | V Highly Available engine - via hosted engine[2] | V Open vSwitch integration - via neutron integration | X Allow cloning VMs without template | ? Enable hypervisor upgrade/updates through engine[3] | V Allow engine on an oVirt hosted VM - via hosted engine[2] | V Enable guest configuration (root password, SSH keys, network) via | guest agent in engine - via cloud-init | X Integrate v2v into engine | ? Bond/extend ovirtmgmt with a second network for HA/increased | bandwidth[4] | X Integrate scheduling of snapshots and VM export for backups in | engine[5] | V Spice – support Google Chrome - via mime based launch | | | Other items mentioned in previous survey which should be covered by now: | - Fix timeout when adding local host during all-in-one configuration | - Fix engine set-up when SELinux is disabled | - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) | - Allow multiple VMs to be deployed from the same template at the same | time | - ISO domains on local/GlusterS | - Show IP addresses in Virtual Machines->Network Interfaces | - OpenStack Quantum support (now called Neutron) | - noVNC support | - Support spice.html5 and websocket proxy | - Add other guest OSes to list | - Port oVirt guest agent to Ubuntu[6] | - SLA - Allow resource time-sharing | - Spice - Mac client (via mime based launch) | - Spice - port XPI plug-in to Windows (not sure this will happen, but | mime based launch allows using firefox now) | - Spice - client for Ubuntu/Debian (should be covered via mime based | launch) | | | [2] hosted engine is in active development, but not released yet. | [3] host update is supported, but not for general yum update. | [4] a lot of improvements were done in this space, but i'm not sure if | they cover this exact use case | [5] backup api is now being pushed to master, and orchestration of | backups should probably happen via 3rd part backup vendors? | [6] I'm not sure packaging exists yet, but ubuntu is covered for the | basic functionality of the guest agent. | ___________________________________________________ | Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> | http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>> | | | -- | | Med Vänliga Hälsningar | ------------------------------____----------------------------__--__------------------- | Karli Sjöberg | Swedish University of Agricultural Sciences | Box 7079 (Visiting Address Kronåsvägen 8) | S-750 07 Uppsala, Sweden | Phone: +46-(0)18-67 15 66 | karli.sjoberg(a)slu.se <mailto:karli.sjoberg@slu.se> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se>> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se>>> | | ___________________________________________________ | Users mailing list | Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> | http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>> | ___________________________________________________ Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>> ___________________________________________________ Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>>

hi in ovirt 3.2 there isnt ubuntu in the list. 3.3 is released?can i download it ?

regards On Tue, Sep 3, 2013 at 5:25 PM, Itamar Heim <iheim(a)redhat.com <mailto:iheim@redhat.com>> wrote: On 09/03/2013 03:54 PM, alireza sadeh seighalan wrote: hi ubuntu should list in ther agent list. when you want to create vm's in the operating list drop down menu. please dont forget other OS's. regards sorry, I'm still not sure i understand. we added ubuntu and sles to list of OSs in 3.3. can you please elaborate on what is missing? thanks, Itamar On Tue, Sep 3, 2013 at 4:07 PM, Itamar Heim <iheim(a)redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>> wrote: On 09/03/2013 12:02 PM, alireza sadeh seighalan wrote: hi again ubuntu agent should be add in the list like vmware . added in which list? > about installation i have to install ovirt packages by local repository and there is problem in this status and in adding host to ovirt manager you need to install packages that need to internet . why do you need internet? you just need the host to be configured with a repo containing the packages, which can be local as well? regards, On Tue, Sep 3, 2013 at 1:26 PM, Itamar Heim <iheim(a)redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>> <mailto:iheim@redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>>> wrote: On 09/03/2013 10:53 AM, alireza sadeh seighalan wrote: hi please add support from solaris , ubuntu and other OS's. we've added in 3.3 ubuntu and suse as guest os's - i can't tell you if they work or not. you can now easily add on your own more OSs as well: http://www.ovirt.org/OS_info guest agent for ubuntu should be working. > installation is a little hard specially in an evironment without > internet. can you please share more on the issues you faced? thanks, Itamar regards, On Mon, Sep 2, 2013 at 7:43 PM, Doron Fediuck <dfediuck(a)redhat.com <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com>> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com>>> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com>> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com <mailto:dfediuck@redhat.com>>>>__> wrote: ----- Original Message ----- | From: "Karli Sjöberg" <Karli.Sjoberg(a)slu.se <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se>> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se>>> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se>> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se <mailto:Karli.Sjoberg@slu.se>>>__>__> | To: "Itamar Heim" <iheim(a)redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>> <mailto:iheim@redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>> <mailto:iheim@redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>> <mailto:iheim@redhat.com <mailto:iheim@redhat.com> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>>>> | Cc: users(a)ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>> <mailto:users@ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> <mailto:users@ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>> <mailto:users@ovirt.org <mailto:users@ovirt.org> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>, "Jan-Olov Persson" <jan-olov.persson(a)slu.se <mailto:jan-olov.persson@slu.se> <mailto:jan-olov.persson@slu.__se <mailto:jan-olov.persson@slu.se>> <mailto:jan-olov.persson@slu. <mailto:jan-olov.persson@slu.>____se <mailto:jan-olov.persson@slu.__se <mailto:jan-olov.persson@slu.se>>> <mailto:jan-olov.persson@slu <mailto:jan-olov.persson@slu>. <mailto:jan-olov.persson@slu <mailto:jan-olov.persson@slu>.>______se <mailto:jan-olov.persson@slu. <mailto:jan-olov.persson@slu.>____se <mailto:jan-olov.persson@slu.__se <mailto:jan-olov.persson@slu.se>>>>> | Sent: Monday, September 2, 2013 10:42:52 AM | Subject: Re: [Users] so, what do you want next in oVirt? | | Hi, | | I would like to see a more advanced type of Power-Saving Cluster policy, | where an empty Host gets put into a sleep-mode, so that it draws as little | power as possible and can be awoken by engine when VM's starts to use more | resources. | | A typical scenario would be that all VM's are spread evenly over Hosts during | day-time, when customers are actively using their VM's. But then during | off-hours, VM's gets clumped up into maybe one or two Hosts, and the other | Hosts can be put to sleep to save energy, and then woken up in the morning | again. | | /Karli | Hi Karli, this should be achievable for you in 3.3 with some minor work on your side; In oVirt 3.3 we introduce the new scheduler, which allows you to run your own code when doing VM placement and load balancing. You can write your own load balancing logic replacing the built-in one, which will switch to power saving at a given time. Once a host has no running VMs, your balance logic can switch it into S3 state (sleep), and when needed or in a given time use wake-on-lan to resume all suspended hosts. If you want we can guide you through it post 3.3 release. Doron | tis 2013-08-20 klockan 17:19 -0400 skrev Itamar Heim: | | | earlier in the year we did a survey for feature requests / improvements | / etc. | | since a lot of things were added, and priorities usually change, I'd | like to ask again for "what do you need the most from oVirt / what are | your pain points" next? | | below[1] I've listed my understanding of what already went in from | previous survey requests (to various degrees of coverage). | | Thanks, | Itamar | | [1] from the top 12 | V Allow disk resize | V Integrate Nagios/Zabbix monitoring - via a ui plugin | V Highly Available engine - via hosted engine[2] | V Open vSwitch integration - via neutron integration | X Allow cloning VMs without template | ? Enable hypervisor upgrade/updates through engine[3] | V Allow engine on an oVirt hosted VM - via hosted engine[2] | V Enable guest configuration (root password, SSH keys, network) via | guest agent in engine - via cloud-init | X Integrate v2v into engine | ? Bond/extend ovirtmgmt with a second network for HA/increased | bandwidth[4] | X Integrate scheduling of snapshots and VM export for backups in | engine[5] | V Spice – support Google Chrome - via mime based launch | | | Other items mentioned in previous survey which should be covered by now: | - Fix timeout when adding local host during all-in-one configuration | - Fix engine set-up when SELinux is disabled | - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) | - Allow multiple VMs to be deployed from the same template at the same | time | - ISO domains on local/GlusterS | - Show IP addresses in Virtual Machines->Network Interfaces | - OpenStack Quantum support (now called Neutron) | - noVNC support | - Support spice.html5 and websocket proxy | - Add other guest OSes to list | - Port oVirt guest agent to Ubuntu[6] | - SLA - Allow resource time-sharing | - Spice - Mac client (via mime based launch) | - Spice - port XPI plug-in to Windows (not sure this will happen, but | mime based launch allows using firefox now) | - Spice - client for Ubuntu/Debian (should be covered via mime based | launch) | | | [2] hosted engine is in active development, but not released yet. | [3] host update is supported, but not for general yum update. | [4] a lot of improvements were done in this space, but i'm not sure if | they cover this exact use case | [5] backup api is now being pushed to master, and orchestration of | backups should probably happen via 3rd part backup vendors? | [6] I'm not sure packaging exists yet, but ubuntu is covered for the | basic functionality of the guest agent. | _____________________________________________________ | Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> | http://lists.ovirt.org/______mailman/listinfo/users <http://lists.ovirt.org/____mailman/listinfo/users> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users>> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>>> | | | -- | | Med Vänliga Hälsningar | ------------------------------______--------------------------__--__--__------------------- | Karli Sjöberg | Swedish University of Agricultural Sciences | Box 7079 (Visiting Address Kronåsvägen 8) | S-750 07 Uppsala, Sweden | Phone: +46-(0)18-67 15 66 | karli.sjoberg(a)slu.se <mailto:karli.sjoberg@slu.se> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se>> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se>>> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se>> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se> <mailto:karli.sjoberg@slu.se <mailto:karli.sjoberg@slu.se>>>__> | | _____________________________________________________ | Users mailing list | Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> | http://lists.ovirt.org/______mailman/listinfo/users <http://lists.ovirt.org/____mailman/listinfo/users> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users>> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>>> | _____________________________________________________ Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> http://lists.ovirt.org/______mailman/listinfo/users <http://lists.ovirt.org/____mailman/listinfo/users> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users>> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>>> _____________________________________________________ Users mailing list Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> http://lists.ovirt.org/______mailman/listinfo/users <http://lists.ovirt.org/____mailman/listinfo/users> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users>> <http://lists.ovirt.org/____mailman/listinfo/users <http://lists.ovirt.org/__mailman/listinfo/users> <http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>>>

Dne 3.9.2013 15:50, Itamar Heim napsal(a): > On 09/03/2013 03:58 PM, alireza sadeh seighalan wrote: >> hi >> >> in ovirt 3.2 there isnt ubuntu in the list. 3.3 is released?can i >> download it ? > > go/no-go on 3.3 release is happening right now... > >> regards >> >> >> On Tue, Sep 3, 2013 at 5:25 PM, Itamar Heim <iheim(a)redhat.com >> <mailto:iheim@redhat.com>> wrote: >> >> On 09/03/2013 03:54 PM, alireza sadeh seighalan wrote: >> >> hi >> >> ubuntu should list in ther agent list. when you want to create >> vm's in >> the operating list drop down menu. please dont forget other >> OS's. >> regards >> >> >> sorry, I'm still not sure i understand. we added ubuntu and sles to >> list of OSs in 3.3. can you please elaborate on what is missing? >> >> thanks, >> Itamar >> >> >> >> On Tue, Sep 3, 2013 at 4:07 PM, Itamar Heim <iheim(a)redhat.com >> <mailto:iheim@redhat.com> >> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>> wrote: >> >> On 09/03/2013 12:02 PM, alireza sadeh seighalan wrote: >> >> hi again >> >> ubuntu agent should be add in the list like vmware . >> >> >> added in which list? >> >> >> > about installation >> >> i have to install ovirt packages by local repository >> and there is >> problem in this status and in adding host to ovirt >> manager you >> need to >> install packages that need to internet . >> >> >> why do you need internet? you just need the host to be >> configured >> with a repo containing the packages, which can be local as >> well? >> >> regards, >> >> >> On Tue, Sep 3, 2013 at 1:26 PM, Itamar Heim >> <iheim(a)redhat.com <mailto:iheim@redhat.com> >> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>> >> <mailto:iheim@redhat.com <mailto:iheim@redhat.com> >> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>>>> wrote: >> >> On 09/03/2013 10:53 AM, alireza sadeh seighalan >> wrote: >> >> hi >> >> please add support from solaris , ubuntu and >> other OS's. >> >> >> we've added in 3.3 ubuntu and suse as guest os's - >> i can't >> tell you >> if they work or not. >> you can now easily add on your own more OSs as >> well: >> http://www.ovirt.org/OS_info >> >> guest agent for ubuntu should be working. >> >> >> >> >> > installation is a little hard specially in an >> evironment without >> > internet. >> >> can you please share more on the issues you faced? >> >> thanks, >> Itamar >> >> >> regards, >> >> >> On Mon, Sep 2, 2013 at 7:43 PM, Doron Fediuck >> <dfediuck(a)redhat.com >> <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com >> <mailto:dfediuck@redhat.com>> >> <mailto:dfediuck@redhat.com >> <mailto:dfediuck@redhat.com> <mailto:dfediuck@redhat.com >> <mailto:dfediuck@redhat.com>>> >> <mailto:dfediuck@redhat.com >> <mailto:dfediuck@redhat.com> >> <mailto:dfediuck@redhat.com >> <mailto:dfediuck@redhat.com>> <mailto:dfediuck@redhat.com >> <mailto:dfediuck@redhat.com> >> <mailto:dfediuck@redhat.com >> <mailto:dfediuck@redhat.com>>>>__> wrote: >> >> ----- Original Message ----- >> | From: "Karli Sjöberg" >> <Karli.Sjoberg(a)slu.se <mailto:Karli.Sjoberg@slu.se> >> <mailto:Karli.Sjoberg@slu.se >> <mailto:Karli.Sjoberg@slu.se>> >> <mailto:Karli.Sjoberg@slu.se >> <mailto:Karli.Sjoberg@slu.se> <mailto:Karli.Sjoberg@slu.se >> <mailto:Karli.Sjoberg@slu.se>>> >> <mailto:Karli.Sjoberg@slu.se >> <mailto:Karli.Sjoberg@slu.se> >> <mailto:Karli.Sjoberg@slu.se >> <mailto:Karli.Sjoberg@slu.se>> <mailto:Karli.Sjoberg@slu.se >> <mailto:Karli.Sjoberg@slu.se> >> <mailto:Karli.Sjoberg@slu.se >> <mailto:Karli.Sjoberg@slu.se>>>__>__> >> | To: "Itamar Heim" <iheim(a)redhat.com >> <mailto:iheim@redhat.com> >> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>> >> <mailto:iheim@redhat.com >> <mailto:iheim@redhat.com> <mailto:iheim@redhat.com >> <mailto:iheim@redhat.com>>> >> <mailto:iheim@redhat.com <mailto:iheim@redhat.com> >> <mailto:iheim@redhat.com <mailto:iheim@redhat.com>> >> <mailto:iheim@redhat.com >> <mailto:iheim@redhat.com> <mailto:iheim@redhat.com >> <mailto:iheim@redhat.com>>>>> >> >> | Cc: users(a)ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>> >> <mailto:users@ovirt.org >> <mailto:users@ovirt.org> <mailto:users@ovirt.org >> <mailto:users@ovirt.org>> >> <mailto:users@ovirt.org <mailto:users@ovirt.org> >> <mailto:users@ovirt.org <mailto:users@ovirt.org>>>>, "Jan-Olov >> Persson" >> <jan-olov.persson(a)slu.se >> <mailto:jan-olov.persson@slu.se> >> <mailto:jan-olov.persson@slu.__se >> <mailto:jan-olov.persson@slu.se>> >> <mailto:jan-olov.persson@slu. >> <mailto:jan-olov.persson@slu.>____se >> <mailto:jan-olov.persson@slu.__se >> <mailto:jan-olov.persson@slu.se>>> >> <mailto:jan-olov.persson@slu >> <mailto:jan-olov.persson@slu>. >> <mailto:jan-olov.persson@slu >> <mailto:jan-olov.persson@slu>.>______se >> >> <mailto:jan-olov.persson@slu. >> <mailto:jan-olov.persson@slu.>____se >> <mailto:jan-olov.persson@slu.__se >> <mailto:jan-olov.persson@slu.se>>>>> >> >> | Sent: Monday, September 2, 2013 >> 10:42:52 AM >> | Subject: Re: [Users] so, what do you >> want next >> in oVirt? >> | >> | Hi, >> | >> | I would like to see a more advanced >> type of >> Power-Saving >> Cluster >> policy, >> | where an empty Host gets put into a >> sleep-mode, >> so that >> it draws >> as little >> | power as possible and can be awoken by >> engine >> when VM's >> starts to >> use more >> | resources. >> | >> | A typical scenario would be that all >> VM's are spread >> evenly over >> Hosts during >> | day-time, when customers are >> actively using >> their VM's. >> But then >> during >> | off-hours, VM's gets clumped up into >> maybe one >> or two >> Hosts, and >> the other >> | Hosts can be put to sleep to save >> energy, and >> then woken >> up in the >> morning >> | again. >> | >> | /Karli >> | >> >> Hi Karli, >> this should be achievable for you in 3.3 >> with some >> minor >> work on >> your side; >> In oVirt 3.3 we introduce the new >> scheduler, which >> allows >> you to run >> your own >> code when doing VM placement and load >> balancing. >> >> You can write your own load balancing >> logic >> replacing the >> built-in one, >> which will switch to power saving at a >> given time. >> Once a >> host has no >> running VMs, your balance logic can >> switch it into >> S3 state >> (sleep), and >> when needed or in a given time use >> wake-on-lan to >> resume all >> suspended hosts. >> >> If you want we can guide you through it >> post 3.3 >> release. >> >> Doron >> >> | tis 2013-08-20 klockan 17:19 -0400 >> skrev Itamar >> Heim: >> | >> | >> | earlier in the year we did a survey for >> feature >> requests / >> improvements >> | / etc. >> | >> | since a lot of things were added, and >> priorities >> usually >> change, I'd >> | like to ask again for "what do you need >> the most >> from >> oVirt / what are >> | your pain points" next? >> | >> | below[1] I've listed my understanding >> of what >> already >> went in from >> | previous survey requests (to various >> degrees of >> coverage). >> | >> | Thanks, >> | Itamar >> | >> | [1] from the top 12 >> | V Allow disk resize >> | V Integrate Nagios/Zabbix monitoring - >> via a ui >> plugin >> | V Highly Available engine - via hosted >> engine[2] >> | V Open vSwitch integration - via >> neutron integration >> | X Allow cloning VMs without template >> | ? Enable hypervisor upgrade/updates >> through >> engine[3] >> | V Allow engine on an oVirt hosted VM >> - via >> hosted engine[2] >> | V Enable guest configuration (root >> password, SSH >> keys, >> network) via >> | guest agent in engine - via >> cloud-init >> | X Integrate v2v into engine >> | ? Bond/extend ovirtmgmt with a second >> network for >> HA/increased >> | bandwidth[4] >> | X Integrate scheduling of snapshots >> and VM >> export for >> backups in >> | engine[5] >> | V Spice – support Google Chrome - via >> mime based >> launch >> | >> | >> | Other items mentioned in previous >> survey which >> should be >> covered >> by now: >> | - Fix timeout when adding local host >> during >> all-in-one >> configuration >> | - Fix engine set-up when SELinux is >> disabled >> | - Provide packages for el6 (CentOS, >> Red Hat >> Enterprise Linux) >> | - Allow multiple VMs to be deployed >> from the same >> template at the same >> | time >> | - ISO domains on local/GlusterS >> | - Show IP addresses in Virtual >> Machines->Network >> Interfaces >> | - OpenStack Quantum support (now called >> Neutron) >> | - noVNC support >> | - Support spice.html5 and websocket >> proxy >> | - Add other guest OSes to list >> | - Port oVirt guest agent to Ubuntu[6] >> | - SLA - Allow resource time-sharing >> | - Spice - Mac client (via mime based >> launch) >> | - Spice - port XPI plug-in to Windows >> (not sure >> this will >> happen, but >> | mime based launch allows using >> firefox now) >> | - Spice - client for Ubuntu/Debian >> (should be >> covered via >> mime based >> | launch) >> | >> | >> | [2] hosted engine is in active >> development, but not >> released yet. >> | [3] host update is supported, but >> not for >> general yum update. >> | [4] a lot of improvements were done >> in this >> space, but >> i'm not sure if >> | they cover this exact use case >> | [5] backup api is now being pushed to >> master, and >> orchestration of >> | backups should probably happen via >> 3rd part >> backup >> vendors? >> | [6] I'm not sure packaging exists yet, >> but ubuntu is >> covered for the >> | basic functionality of the guest >> agent. >> | >> _____________________________________________________ >> >> | Users mailing list Users(a)ovirt.org >> <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>>>> >> >> | >> http://lists.ovirt.org/______mailman/listinfo/users >> <http://lists.ovirt.org/____mailman/listinfo/users> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users>> >> >> >> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users> >> <http://lists.ovirt.org/__mailman/listinfo/users >> <http://lists.ovirt.org/mailman/listinfo/users>>> >> | >> | >> | -- >> | >> | Med Vänliga Hälsningar >> | >> >> >> >> ------------------------------______--------------------------__--__--__------------------- >> >> >> >> | Karli Sjöberg >> | Swedish University of Agricultural >> Sciences >> | Box 7079 (Visiting Address >> Kronåsvägen 8) >> | S-750 07 Uppsala, Sweden >> | Phone: +46-(0)18-67 15 66 >> | karli.sjoberg(a)slu.se >> <mailto:karli.sjoberg@slu.se> >> <mailto:karli.sjoberg@slu.se >> <mailto:karli.sjoberg@slu.se>> <mailto:karli.sjoberg@slu.se >> <mailto:karli.sjoberg@slu.se> >> <mailto:karli.sjoberg@slu.se >> <mailto:karli.sjoberg@slu.se>>> >> <mailto:karli.sjoberg@slu.se >> <mailto:karli.sjoberg@slu.se> >> <mailto:karli.sjoberg@slu.se >> <mailto:karli.sjoberg@slu.se>> <mailto:karli.sjoberg@slu.se >> <mailto:karli.sjoberg@slu.se> >> <mailto:karli.sjoberg@slu.se >> <mailto:karli.sjoberg@slu.se>>>__> >> | >> | >> _____________________________________________________ >> >> >> | Users mailing list >> | Users(a)ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>>> >> >> | >> http://lists.ovirt.org/______mailman/listinfo/users >> <http://lists.ovirt.org/____mailman/listinfo/users> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users>> >> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users> >> <http://lists.ovirt.org/__mailman/listinfo/users >> <http://lists.ovirt.org/mailman/listinfo/users>>> >> | >> >> _____________________________________________________ >> >> Users mailing list >> Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>> >> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>>>> >> >> http://lists.ovirt.org/______mailman/listinfo/users >> <http://lists.ovirt.org/____mailman/listinfo/users> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users>> >> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users> >> <http://lists.ovirt.org/__mailman/listinfo/users >> <http://lists.ovirt.org/mailman/listinfo/users>>> >> >> >> >> >> >> _____________________________________________________ >> >> >> Users mailing list >> Users(a)ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org>> <mailto:Users@ovirt.org >> <mailto:Users@ovirt.org> >> <mailto:Users@ovirt.org <mailto:Users@ovirt.org>>> >> http://lists.ovirt.org/______mailman/listinfo/users >> <http://lists.ovirt.org/____mailman/listinfo/users> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users>> >> >> <http://lists.ovirt.org/____mailman/listinfo/users >> <http://lists.ovirt.org/__mailman/listinfo/users> >> <http://lists.ovirt.org/__mailman/listinfo/users >> <http://lists.ovirt.org/mailman/listinfo/users>>> >> >> >> >> >> >> >> > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users Hello, I dont have Ubuntu in Operating system picker in new VM creating dialog. Iam using oVirt 3.3RC.

Someone wrote that there is working ovirt-agent for Ubuntu, but I can not find any info about it. Is there a deb package somewhere or howto about deploying it?

I would suggest another feature (maybe it is covered by external providers). Network NAT for VMs (with buildin DHCP). Thank you. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 09/02/2013 05:29 PM, NOC wrote: > On 08/21/2013 12:11 PM, Itamar Heim wrote: >> On 08/21/2013 02:40 AM, Joop van de Wege wrote: >>> >>> What I would like to see in the ! next version is pxe boot of the >>> nodes. >>> Probably not easy to achieve because of dependency on dhcp. >> >> Hi Joop, >> >> can you please give a bit more information on the use case / how you >> envision this? >> >> current thinking around bare metal provisioning of hosts is to extend >> the functionality around the foreman provider for this, but you may >> have other suggestions? > > I think Joop means to be able to add hosts (nodes) to a cluster by > adding their MAC address to the dhcp list for PXE boot into ovirt-node > and thus join the cluster. This would make it easy to add new physical > nodes without any spinning disks or other local storage requirements. we started adding foreman integration in 3.3: http://www.ovirt.org/Features/ForemanIntegration adding ohad and oved for their thoughts on this. > > I suppose this may not be easy with complex network connections (bonds > on mgmt network, mgmt network on a tagged vlan, etc), but it should be > possible if the management network interface is plain and physical. > > /Simon > > PS, Perhaps Joop can confirm this idea, we've talked about it IRL. > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users

What about swap? Don´t they have any swap file, or partition at all? Swap-file over NFS must suck quite badly, no? We have bought semi-cheap SSD's for our Hosts to use as swap to get more out of them from memory overprovisioning.

>> On 08/21/2013 12:11 PM, Itamar Heim wrote: >>> On 08/21/2013 02:40 AM, Joop van de Wege wrote: >>>> >>>> What I would like to see in the ! next version is pxe boot of the >>>> nodes. >>>> Probably not easy to achieve because of dependency on dhcp. >>> >>> Hi Joop, >>> >>> can you please give a bit more information on the use case / how you >>> envision this? >>> >>> current thinking around bare metal provisioning of hosts is to extend >>> the functionality around the foreman provider for this, but you may >>> have other suggestions? >> >> I think Joop means to be able to add hosts (nodes) to a cluster by >> adding their MAC address to the dhcp list for PXE boot into ovirt-node >> and thus join the cluster. This would make it easy to add new physical >> nodes without any spinning disks or other local storage requirements. > > we started adding foreman integration in 3.3: > http://www.ovirt.org/Features/ForemanIntegration > > adding ohad and oved for their thoughts on this. > >> >> I suppose this may not be easy with complex network connections (bonds >> on mgmt network, mgmt network on a tagged vlan, etc), but it should be >> possible if the management network interface is plain and physical. >> >> /Simon >> >> PS, Perhaps Joop can confirm this idea, we've talked about it IRL. >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > This isn't about provisioning with Foreman. Its about having the compute nodes NOT having any spinning disks. So the only way to start a node is to pxeboot it and then let it (re)connect with the engine. Then it will be identified by engine as either a new node or a reconnecting node and it will get its configuration from the engine. For reference: thats how VirtualIron works. It has a managment network, just like ovirt, and on that it runs a tftp and dhcp server. Nodes are plugged into the managment network, without disk, and then pxe booted after which they appear in the webui as new unconfigured nodes. You then can set various settings and upon rebooting the nodes will recieve these settings because it is recognised by its mac address. The advantage of this construct is that you can place a new server into a rack, cable it, power on and go back to you office where you'll find the new node waiting to be configured. No messing around with CDs to install an OS, not being in the datacenter for hours on end, just in and out. Yes, disks are cheap but they brake down, need maintenance, means downtime and in general more admin time then when you don't have them. ( its a shame to have a raid1 of 2 1Tb disk just to install an OS of less then 10G)

On 09/05/2013 10:30 AM, noc wrote: >>> On 08/21/2013 12:11 PM, Itamar Heim wrote: >>>> On 08/21/2013 02:40 AM, Joop van de Wege wrote: >>>>> >>>>> What I would like to see in the ! next version is pxe boot of the >>>>> nodes. >>>>> Probably not easy to achieve because of dependency on dhcp. >>>> >>>> Hi Joop, >>>> >>>> can you please give a bit more information on the use case / how you >>>> envision this? >>>> >>>> current thinking around bare metal provisioning of hosts is to extend >>>> the functionality around the foreman provider for this, but you may >>>> have other suggestions? >>> >>> I think Joop means to be able to add hosts (nodes) to a cluster by >>> adding their MAC address to the dhcp list for PXE boot into ovirt-node >>> and thus join the cluster. This would make it easy to add new physical >>> nodes without any spinning disks or other local storage requirements. >> >> we started adding foreman integration in 3.3: >> http://www.ovirt.org/Features/ForemanIntegration >> >> adding ohad and oved for their thoughts on this. >> >>> >>> I suppose this may not be easy with complex network connections (bonds >>> on mgmt network, mgmt network on a tagged vlan, etc), but it should be >>> possible if the management network interface is plain and physical. >>> >>> /Simon >>> >>> PS, Perhaps Joop can confirm this idea, we've talked about it IRL. >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >> > This isn't about provisioning with Foreman. Its about having the compute > nodes NOT having any spinning disks. So the only way to start a node is > to pxeboot it and then let it (re)connect with the engine. Then it will > be identified by engine as either a new node or a reconnecting node and > it will get its configuration from the engine. For reference: thats how > VirtualIron works. It has a managment network, just like ovirt, and on > that it runs a tftp and dhcp server. Nodes are plugged into the > managment network, without disk, and then pxe booted after which they > appear in the webui as new unconfigured nodes. You then can set various > settings and upon rebooting the nodes will recieve these settings > because it is recognised by its mac address. The advantage of this > construct is that you can place a new server into a rack, cable it, > power on and go back to you office where you'll find the new node > waiting to be configured. No messing around with CDs to install an OS, > not being in the datacenter for hours on end, just in and out. > > Yes, disks are cheap but they brake down, need maintenance, means > downtime and in general more admin time then when you don't have them. ( > its a shame to have a raid1 of 2 1Tb disk just to install an OS of less > then 10G) just wondering, how do they prevent a rogue node/guest from masquerading as such a host, getting access/secrets/VMs to be launched on such an untrusted node (they could easily report a different mac address if the layer 2 isn't hardened against that)?

other than that, yes. we actually used to have this via the AutoApprovePatterns config option, which would have the engine approve a pending node as it registers (I admit i don't think anyone used this last several years, and it may be totally broken by now). please note this doesn't solve the need for a disk, just the auto-registration part (if it still works)

Could be great o have on the Engine: - An upload option for the ISO files - A backup and restore option - An high availability for the engine: install the engine on 2 platforms (hardware?), than integrate them for synchronization Jose ------------------------------ *From: *"noc" <noc(a)nieuwland.nl&gt; *Cc: *users(a)ovirt.org *Sent: *Sexta-feira, 6 de Setembro de 2013 10:28:09 *Subject: *Re: [Users] so, what do you want next in oVirt? On 6-9-2013 10:12, Itamar Heim wrote: > On 09/05/2013 10:30 AM, noc wrote: >>>> On 08/21/2013 12:11 PM, Itamar Heim wrote: >>>>> On 08/21/2013 02:40 AM, Joop van de Wege wrote: >>>>>> >>>>>> What I would like to see in the ! next version is pxe boot of the >>>>>> nodes. >>>>>> Probably not easy to achieve because of dependency on dhcp. >>>>> >>>>> Hi Joop, >>>>> >>>>> can you please give a bit more information on the use case / how you >>>>> envision this? >>>>> >>>>> current thinking around bare metal provisioning of hosts is to extend >>>>> the functionality around the foreman provider for this, but you may >>>>> have other suggestions? >>>> >>>> I think Joop means to be able to add hosts (nodes) to a cluster by >>>> adding their MAC address to the dhcp list for PXE boot into ovirt-node >>>> and thus join the cluster. This would make it easy to add new physical >>>> nodes without any spinning disks or other local storage requirements. >>> >>> we started adding foreman integration in 3.3: >>> http://www.ovirt.org/Features/ForemanIntegration >>> >>> adding ohad and oved for their thoughts on this. >>> >>>> >>>> I suppose this may not be easy with complex network connections (bonds >>>> on mgmt network, mgmt network on a tagged vlan, etc), but it should be >>>> possible if the management network interface is plain and physical. >>>> >>>> /Simon >>>> >>>> PS, Perhaps Joop can confirm this idea, we've talked about it IRL. >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>> >> This isn't about provisioning with Foreman. Its about having the compute >> nodes NOT having any spinning disks. So the only way to start a node is >> to pxeboot it and then let it (re)connect with the engine. Then it will >> be identified by engine as either a new node or a reconnecting node and >> it will get its configuration from the engine. For reference: thats how >> VirtualIron works. It has a managment network, just like ovirt, and on >> that it runs a tftp and dhcp server. Nodes are plugged into the >> managment network, without disk, and then pxe booted after which they >> appear in the webui as new unconfigured nodes. You then can set various >> settings and upon rebooting the nodes will recieve these settings >> because it is recognised by its mac address. The advantage of this >> construct is that you can place a new server into a rack, cable it, >> power on and go back to you office where you'll find the new node >> waiting to be configured. No messing around with CDs to install an OS, >> not being in the datacenter for hours on end, just in and out. >> >> Yes, disks are cheap but they brake down, need maintenance, means >> downtime and in general more admin time then when you don't have them. ( >> its a shame to have a raid1 of 2 1Tb disk just to install an OS of less >> then 10G) > > just wondering, how do they prevent a rogue node/guest from > masquerading as such a host, getting access/secrets/VMs to be launched > on such an untrusted node (they could easily report a different mac > address if the layer 2 isn't hardened against that)? > They would need physical access to your rack which ofcourse is locked, you would need to powerdown/up which would trigger an alert, switch port down/up would trigger an alert, so probably you're notified that something not quite right is happening. I haven't gone through the source to see if there is more then just the mac address check. > other than that, yes. we actually used to have this via the > AutoApprovePatterns config option, which would have the engine approve > a pending node as it registers (I admit i don't think anyone used this > last several years, and it may be totally broken by now). > > please note this doesn't solve the need for a disk, just the > auto-registration part (if it still works) What I would like is to have the ovirt Node pxe booting and getting its config from engine or autoregister. I know there is a script which converts the iso into a huge pxeboot kernel but don't know how to solve or if its solved the config part. @karli: If you run your cluster in Memory Optimization=None then you won't need swap. Have been doing that for years and haven't had a single problem attributed to that. I just would like to have the choice, pxe boot the node and know that you don't have swap. Run with disks if you really need overprovisioning. Regards, Joop _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 09/06/2013 02:19 PM, Andrew Lau wrote: > A lot of work.. but has there been any consideration into redesigning > the web UI? Right now it's so complex and heavy, takes a while to load > and too many features are hidden! I've been using oVirt for half a > year.. and I'm still finding small useful things hidden here and there. > > Can you provide more details on issues you're seeing, and suggestions for a future approach?

From: suporte(a)logicworks.pt To: users(a)ovirt.org Sent: Friday, September 6, 2013 1:43:04 PM Subject: Re: [Users] so, what do you want next in oVirt? Could be great o have on the Engine: - An upload option for the ISO files - A backup and restore option - An high availability for the engine: install the engine on 2 platforms (hardware?), than integrate them for synchronization Jose From: "noc" <noc(a)nieuwland.nl&gt; Cc: users(a)ovirt.org Sent: Sexta-feira, 6 de Setembro de 2013 10:28:09 Subject: Re: [Users] so, what do you want next in oVirt? On 6-9-2013 10:12, Itamar Heim wrote: > On 09/05/2013 10:30 AM, noc wrote: >>>> On 08/21/2013 12:11 PM, Itamar Heim wrote: >>>>> On 08/21/2013 02:40 AM, Joop van de Wege wrote: >>>>>> >>>>>> What I would like to see in the ! next version is pxe boot of the >>>>>> nodes. >>>>>> Probably not easy to achieve because of dependency on dhcp. >>>>> >>>>> Hi Joop, >>>>> >>>>> can you please give a bit more information on the use case / how you >>>>> envision this? >>>>> >>>>> current thinking around bare metal provisioning of hosts is to extend >>>>> the functionality around the foreman provider for this, but you may >>>>> have other suggestions? >>>> >>>> I think Joop means to be able to add hosts (nodes) to a cluster by >>>> adding their MAC address to the dhcp list for PXE boot into ovirt-node >>>> and thus join the cluster. This would make it easy to add new physical >>>> nodes without any spinning disks or other local storage requirements. >>> >>> we started adding foreman integration in 3.3: >>> http://www.ovirt.org/Features/ForemanIntegration >>> >>> adding ohad and oved for their thoughts on this. >>> >>>> >>>> I suppose this may not be easy with complex network connections (bonds >>>> on mgmt network, mgmt network on a tagged vlan, etc), but it should be >>>> possible if the management network interface is plain and physical. >>>> >>>> /Simon >>>> >>>> PS, Perhaps Joop can confirm this idea, we've talked about it IRL. >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>> >> This isn't about provisioning with Foreman. Its about having the compute >> nodes NOT having any spinning disks. So the only way to start a node is >> to pxeboot it and then let it (re)connect with the engine. Then it will >> be identified by engine as either a new node or a reconnecting node and >> it will get its configuration from the engine. For reference: thats how >> VirtualIron works. It has a managment network, just like ovirt, and on >> that it runs a tftp and dhcp server. Nodes are plugged into the >> managment network, without disk, and then pxe booted after which they >> appear in the webui as new unconfigured nodes. You then can set various >> settings and upon rebooting the nodes will recieve these settings >> because it is recognised by its mac address. The advantage of this >> construct is that you can place a new server into a rack, cable it, >> power on and go back to you office where you'll find the new node >> waiting to be configured. No messing around with CDs to install an OS, >> not being in the datacenter for hours on end, just in and out. >> >> Yes, disks are cheap but they brake down, need maintenance, means >> downtime and in general more admin time then when you don't have them. ( >> its a shame to have a raid1 of 2 1Tb disk just to install an OS of less >> then 10G) > > just wondering, how do they prevent a rogue node/guest from > masquerading as such a host, getting access/secrets/VMs to be launched > on such an untrusted node (they could easily report a different mac > address if the layer 2 isn't hardened against that)? > They would need physical access to your rack which ofcourse is locked, you would need to powerdown/up which would trigger an alert, switch port down/up would trigger an alert, so probably you're notified that something not quite right is happening. I haven't gone through the source to see if there is more then just the mac address check. > other than that, yes. we actually used to have this via the > AutoApprovePatterns config option, which would have the engine approve > a pending node as it registers (I admit i don't think anyone used this > last several years, and it may be totally broken by now). > > please note this doesn't solve the need for a disk, just the > auto-registration part (if it still works) What I would like is to have the ovirt Node pxe booting and getting its config from engine or autoregister. I know there is a script which converts the iso into a huge pxeboot kernel but don't know how to solve or if its solved the config part. @karli: If you run your cluster in Memory Optimization=None then you won't need swap. Have been doing that for years and haven't had a single problem attributed to that. I just would like to have the choice, pxe boot the node and know that you don't have swap. Run with disks if you really need overprovisioning. Regards, Joop _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hi Doron, But first you have to install the engine, before the VM. So, the idea is to make a backup and restore it to a VM?

------------------------------------------------------------------------ *From: *"Doron Fediuck" <dfediuck(a)redhat.com&gt; *To: *suporte(a)logicworks.pt *Cc: *users(a)ovirt.org *Sent: *Domingo, 8 de Setembro de 2013 23:06:20 *Subject: *Re: [Users] so, what do you want next in oVirt? Hi Jose, the latter is available by hosted engine, which is a highly available VM which will be migrated / restarted on a different host if something goes wrong. ----- Original Message ----- > From: suporte(a)logicworks.pt > To: users(a)ovirt.org > Sent: Friday, September 6, 2013 1:43:04 PM > Subject: Re: [Users] so, what do you want next in oVirt? > > Could be great o have on the Engine: > - An upload option for the ISO files > - A backup and restore option > - An high availability for the engine: install the engine on 2 platforms > (hardware?), than integrate them for synchronization > > Jose > > > From: "noc" <noc(a)nieuwland.nl&gt; > Cc: users(a)ovirt.org > Sent: Sexta-feira, 6 de Setembro de 2013 10:28:09 > Subject: Re: [Users] so, what do you want next in oVirt? > > On 6-9-2013 10:12, Itamar Heim wrote: > > On 09/05/2013 10:30 AM, noc wrote: > >>>> On 08/21/2013 12:11 PM, Itamar Heim wrote: > >>>>> On 08/21/2013 02:40 AM, Joop van de Wege wrote: > >>>>>> > >>>>>> What I would like to see in the ! next version is pxe boot of the > >>>>>> nodes. > >>>>>> Probably not easy to achieve because of dependency on dhcp. > >>>>> > >>>>> Hi Joop, > >>>>> > >>>>> can you please give a bit more information on the use case / how you > >>>>> envision this? > >>>>> > >>>>> current thinking around bare metal provisioning of hosts is to extend > >>>>> the functionality around the foreman provider for this, but you may > >>>>> have other suggestions? > >>>> > >>>> I think Joop means to be able to add hosts (nodes) to a cluster by > >>>> adding their MAC address to the dhcp list for PXE boot into ovirt-node > >>>> and thus join the cluster. This would make it easy to add new physical > >>>> nodes without any spinning disks or other local storage requirements. > >>> > >>> we started adding foreman integration in 3.3: > >>> http://www.ovirt.org/Features/ForemanIntegration > >>> > >>> adding ohad and oved for their thoughts on this. > >>> > >>>> > >>>> I suppose this may not be easy with complex network connections (bonds > >>>> on mgmt network, mgmt network on a tagged vlan, etc), but it should be > >>>> possible if the management network interface is plain and physical. > >>>> > >>>> /Simon > >>>> > >>>> PS, Perhaps Joop can confirm this idea, we've talked about it IRL. > >>>> _______________________________________________ > >>>> Users mailing list > >>>> Users(a)ovirt.org > >>>> http://lists.ovirt.org/mailman/listinfo/users > >>> > >> This isn't about provisioning with Foreman. Its about having the compute > >> nodes NOT having any spinning disks. So the only way to start a node is > >> to pxeboot it and then let it (re)connect with the engine. Then it will > >> be identified by engine as either a new node or a reconnecting node and > >> it will get its configuration from the engine. For reference: thats how > >> VirtualIron works. It has a managment network, just like ovirt, and on > >> that it runs a tftp and dhcp server. Nodes are plugged into the > >> managment network, without disk, and then pxe booted after which they > >> appear in the webui as new unconfigured nodes. You then can set various > >> settings and upon rebooting the nodes will recieve these settings > >> because it is recognised by its mac address. The advantage of this > >> construct is that you can place a new server into a rack, cable it, > >> power on and go back to you office where you'll find the new node > >> waiting to be configured. No messing around with CDs to install an OS, > >> not being in the datacenter for hours on end, just in and out. > >> > >> Yes, disks are cheap but they brake down, need maintenance, means > >> downtime and in general more admin time then when you don't have them. ( > >> its a shame to have a raid1 of 2 1Tb disk just to install an OS of less > >> then 10G) > > > > just wondering, how do they prevent a rogue node/guest from > > masquerading as such a host, getting access/secrets/VMs to be launched > > on such an untrusted node (they could easily report a different mac > > address if the layer 2 isn't hardened against that)? > > > They would need physical access to your rack which ofcourse is locked, > you would need to powerdown/up which would trigger an alert, switch port > down/up would trigger an alert, so probably you're notified that > something not quite right is happening. I haven't gone through the > source to see if there is more then just the mac address check. > > > other than that, yes. we actually used to have this via the > > AutoApprovePatterns config option, which would have the engine approve > > a pending node as it registers (I admit i don't think anyone used this > > last several years, and it may be totally broken by now). > > > > please note this doesn't solve the need for a disk, just the > > auto-registration part (if it still works) > What I would like is to have the ovirt Node pxe booting and getting its > config from engine or autoregister. I know there is a script which > converts the iso into a huge pxeboot kernel but don't know how to solve > or if its solved the config part. > > @karli: > If you run your cluster in Memory Optimization=None then you won't need > swap. Have been doing that for years and haven't had a single problem > attributed to that. I just would like to have the choice, pxe boot the > node and know that you don't have swap. Run with disks if you really > need overprovisioning. > > Regards, > > Joop > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

De: "Itamar Heim" <iheim(a)redhat.com&gt; À: users(a)ovirt.org Envoyé: Mardi 20 Août 2013 23:19:16 Objet: [Users] so, what do you want next in oVirt? earlier in the year we did a survey for feature requests / improvements / etc. since a lot of things were added, and priorities usually change, I'd like to ask again for "what do you need the most from oVirt / what are your pain points" next? below[1] I've listed my understanding of what already went in from previous survey requests (to various degrees of coverage). Thanks, Itamar [1] from the top 12 V Allow disk resize V Integrate Nagios/Zabbix monitoring - via a ui plugin V Highly Available engine - via hosted engine[2] V Open vSwitch integration - via neutron integration X Allow cloning VMs without template ? Enable hypervisor upgrade/updates through engine[3] V Allow engine on an oVirt hosted VM - via hosted engine[2] V Enable guest configuration (root password, SSH keys, network) via guest agent in engine - via cloud-init X Integrate v2v into engine ? Bond/extend ovirtmgmt with a second network for HA/increased bandwidth[4] X Integrate scheduling of snapshots and VM export for backups in engine[5] V Spice – support Google Chrome - via mime based launch Other items mentioned in previous survey which should be covered by now: - Fix timeout when adding local host during all-in-one configuration - Fix engine set-up when SELinux is disabled - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) - Allow multiple VMs to be deployed from the same template at the same time - ISO domains on local/GlusterS - Show IP addresses in Virtual Machines->Network Interfaces - OpenStack Quantum support (now called Neutron) - noVNC support - Support spice.html5 and websocket proxy - Add other guest OSes to list - Port oVirt guest agent to Ubuntu[6] - SLA - Allow resource time-sharing - Spice - Mac client (via mime based launch) - Spice - port XPI plug-in to Windows (not sure this will happen, but mime based launch allows using firefox now) - Spice - client for Ubuntu/Debian (should be covered via mime based launch) [2] hosted engine is in active development, but not released yet. [3] host update is supported, but not for general yum update. [4] a lot of improvements were done in this space, but i'm not sure if they cover this exact use case [5] backup api is now being pushed to master, and orchestration of backups should probably happen via 3rd part backup vendors? [6] I'm not sure packaging exists yet, but ubuntu is covered for the basic functionality of the guest agent. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

earlier in the year we did a survey for feature requests / improvements / etc. since a lot of things were added, and priorities usually change, I'd like to ask again for "what do you need the most from oVirt / what are your pain points" next? below[1] I've listed my understanding of what already went in from previous survey requests (to various degrees of coverage). Thanks, Itamar [1] from the top 12 V Allow disk resize V Integrate Nagios/Zabbix monitoring - via a ui plugin V Highly Available engine - via hosted engine[2] V Open vSwitch integration - via neutron integration X Allow cloning VMs without template ? Enable hypervisor upgrade/updates through engine[3] V Allow engine on an oVirt hosted VM - via hosted engine[2] V Enable guest configuration (root password, SSH keys, network) via guest agent in engine - via cloud-init X Integrate v2v into engine ? Bond/extend ovirtmgmt with a second network for HA/increased bandwidth[4] X Integrate scheduling of snapshots and VM export for backups in engine[5] V Spice – support Google Chrome - via mime based launch Other items mentioned in previous survey which should be covered by now: - Fix timeout when adding local host during all-in-one configuration - Fix engine set-up when SELinux is disabled - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) - Allow multiple VMs to be deployed from the same template at the same time - ISO domains on local/GlusterS - Show IP addresses in Virtual Machines->Network Interfaces - OpenStack Quantum support (now called Neutron) - noVNC support - Support spice.html5 and websocket proxy - Add other guest OSes to list - Port oVirt guest agent to Ubuntu[6] - SLA - Allow resource time-sharing - Spice - Mac client (via mime based launch) - Spice - port XPI plug-in to Windows (not sure this will happen, but mime based launch allows using firefox now) - Spice - client for Ubuntu/Debian (should be covered via mime based launch) [2] hosted engine is in active development, but not released yet. [3] host update is supported, but not for general yum update. [4] a lot of improvements were done in this space, but i'm not sure if they cover this exact use case [5] backup api is now being pushed to master, and orchestration of backups should probably happen via 3rd part backup vendors? [6] I'm not sure packaging exists yet, but ubuntu is covered for the basic functionality of the guest agent. _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

----- Original Message ----- > From: "René Koch (ovido)" <r.koch(a)ovido.at&gt; > To: "Itamar Heim" <iheim(a)redhat.com&gt; > Cc: "ovirt-users" <users(a)ovirt.org&gt; > Sent: Thursday, September 5, 2013 11:31:57 AM > Subject: Re: [Users] so, what do you want next in oVirt? > > Hi, > > Thanks for starting this thread again. > > > > On Tue, 2013-08-20 at 17:19 -0400, Itamar Heim wrote: > > earlier in the year we did a survey for feature requests / improvements > > / etc. > > > > since a lot of things were added, and priorities usually change, I'd > > like to ask again for "what do you need the most from oVirt / what are > > your pain points" next? > > > > below[1] I've listed my understanding of what already went in from > > previous survey requests (to various degrees of coverage). > > > > Thanks, > > Itamar > > > > [1] from the top 12 > > V Allow disk resize > > > Great! > > > > V Integrate Nagios/Zabbix monitoring - via a ui plugin > > > Zabbix isn't working yet with my ui plugin (is there maybe another one > which integrates Zabbix?) - but it will be available in a future > release. > Btw, there will be a new version of the monitoring ui plugin with new > features available out at the end of this week... > > > > V Highly Available engine - via hosted engine[2] > > V Open vSwitch integration - via neutron integration > > X Allow cloning VMs without template > > > This is definitely one feature I would like to see. > > > > ? Enable hypervisor upgrade/updates through engine[3] > > > The next feature I would like to request. > > > > V Allow engine on an oVirt hosted VM - via hosted engine[2] > > V Enable guest configuration (root password, SSH keys, network) via > > guest agent in engine - via cloud-init > > > Cool. Can this be done on oVirt-node as well or only on > CentOS/RHEL/Fedora hosts? > > > > X Integrate v2v into engine > > > Vote for this again :) > > > > ? Bond/extend ovirtmgmt with a second network for HA/increased > > bandwidth[4] > > X Integrate scheduling of snapshots and VM export for backups in > > engine[5] > > V Spice – support Google Chrome - via mime based launch > > > At the moment spice support is really a pain (especially on Windows as > the SpiceX.cab is missing). Great to hear that spice support has > improved and Chrome can be used as well! > > > > > > > Other items mentioned in previous survey which should be covered by now: > > - Fix timeout when adding local host during all-in-one configuration > > - Fix engine set-up when SELinux is disabled > > - Provide packages for el6 (CentOS, Red Hat Enterprise Linux) > > - Allow multiple VMs to be deployed from the same template at the same > > time > > - ISO domains on local/GlusterS > > > ISO and export domains on FC/iSCSI would be good to have as well. > > > > - Show IP addresses in Virtual Machines->Network Interfaces > > - OpenStack Quantum support (now called Neutron) > > - noVNC support > > - Support spice.html5 and websocket proxy > > - Add other guest OSes to list > > > Good to hear that other Linux distributions will be added as well. > > > > - Port oVirt guest agent to Ubuntu[6] > > - SLA - Allow resource time-sharing > > - Spice - Mac client (via mime based launch) > > - Spice - port XPI plug-in to Windows (not sure this will happen, but > > mime based launch allows using firefox now) > > - Spice - client for Ubuntu/Debian (should be covered via mime based > > launch) > > > Additional features I would like to see are: > - oVirt guest agent for Ubuntu/openSUSE/SLES/Debian * > > *Ubuntu is already available thanks to Zhou Zheng Sheng > > - Resource pools > At the moment only Quotas are available (which is great, btw), but in > some cases it's necessary to implement resource pools. E.g. Limit CPU, > Memory and Network for group of test vms, but give full resources to > production vms. Maybe this could be done with cgroups? > So e.g. I don't want to give a compile machine a full cpu core, but only > 1 core with 500MHz or limit the bandwith to e.g. 10Mbit/s. > Hi René, Due to time constraints, it did not make it into the 3.3 release, however in master we already have network QoS allowing you to limit bandwidth for vNICs. Also, we managed to implement CPU shares which allows you to handle priorities. Both will be included in the next version, and hopefuly some more. So if you ever feel like taking a ride with the bleeding edge, you have both network QoS and CPU shares waiting there.

> - Upload ISOs within the GUI to ISO domain > > - Use existing share for ISO domain > When creating an ISO domain, oVirt creates it's own directory > structure with IDs. It would be nice if an existing share could be used > (e.g. an ISO share on NFS server which is used by other service, too) > without creating the structure with IDs. I know that the IDs are needed > internally but I think it should be possible to reuse an existing share. > > > Last but not least I want to thank all contributors of this project for > their great work so far! > > > Regards, > René > > > > > > > > [2] hosted engine is in active development, but not released yet. > > [3] host update is supported, but not for general yum update. > > [4] a lot of improvements were done in this space, but i'm not sure if > > they cover this exact use case > > [5] backup api is now being pushed to master, and orchestration of > > backups should probably happen via 3rd part backup vendors? > > [6] I'm not sure packaging exists yet, but ubuntu is covered for the > > basic functionality of the guest agent. > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > >

This: http://lists.ovirt.org/pipermail/users/2013-August/015713.html (freedom in mixing storage domain types no SPF Master Storage domain)

From: "Itamar Heim" <iheim(a)redhat.com&gt; To: "\"René \"Koch (ovido)\"\"" <r.koch(a)ovido.at&gt;, "Doron Fediuck" <dfediuck(a)redhat.com&gt; Cc: "ovirt-users" <users(a)ovirt.org&gt; Sent: Sunday, October 6, 2013 10:41:27 PM Subject: Re: [Users] so, what do you want next in oVirt? On 09/05/2013 11:31 AM, René Koch (ovido) wrote: > - Resource pools > At the moment only Quotas are available (which is great, btw), but in > some cases it's necessary to implement resource pools. E.g. Limit CPU, > Memory and Network for group of test vms, but give full resources to > production vms. Maybe this could be done with cgroups? > So e.g. I don't want to give a compile machine a full cpu core, but only > 1 core with 500MHz or limit the bandwith to e.g. 10Mbit/s. doron - doesn't cpu shared provide this?