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