<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/foss-cloud/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 07 Dec 2016 19:14:21 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/foss-cloud/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Physical GPU sharing.  VGPU </title><link>https://sourceforge.net/p/foss-cloud/feature-requests/34/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I would like to install a single graphics card into a host and share it out between multiple VM's.   Here are some articles on how it can be done in gentoo/qemu but I'm not a guru so I'm not sure if this is possible in Foss.&lt;br/&gt;
&lt;a href="https://events.linuxfoundation.org/sites/events/files/slides/KVMGT-a%20Full%20GPU%20Virtualization%20Solution_1.pdf" rel="nofollow"&gt;https://events.linuxfoundation.org/sites/events/files/slides/KVMGT-a%20Full%20GPU%20Virtualization%20Solution_1.pdf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.kraxel.org/blog/tag/virtio-gpu/" rel="nofollow"&gt;https://www.kraxel.org/blog/tag/virtio-gpu/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://virgil3d.github.io/" rel="nofollow"&gt;https://virgil3d.github.io/&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">brad</dc:creator><pubDate>Wed, 07 Dec 2016 19:14:21 -0000</pubDate><guid>https://sourceforge.net982ab03ca6277e6365d0a4949274357b88db0c14</guid></item><item><title>#33 Connection Broker to offer RDP connections</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/33/?limit=25#c295</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;sorry i didn't see the previous ticket asking for this.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">brad</dc:creator><pubDate>Wed, 07 Dec 2016 16:41:33 -0000</pubDate><guid>https://sourceforge.net90eec5fb117d23c80a19059abff2e1c93f9fb946</guid></item><item><title>Connection Broker to offer RDP connections</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/33/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The connection broker should give the option to connect over RDP.   Spice doesn't offer as nice a connection as rdp currently and it would be nice to have another option in case the spice client is busted. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">brad</dc:creator><pubDate>Wed, 07 Dec 2016 16:36:49 -0000</pubDate><guid>https://sourceforge.netc1cc333147d111ba9be3379c6ffecaea3d97c255</guid></item><item><title>Auto recover after after power blackout</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/32/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;One currently should start the nodes in a specific order.&lt;br /&gt;
So after a power blackout, manual actions have to be performed, otherwise all nodes will start simultaneously.&lt;/p&gt;
&lt;p&gt;Would be nice if we found a way around this, like auto-restarting fc-broker in such cases or similar.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stefan K.</dc:creator><pubDate>Sat, 02 Nov 2013 13:28:08 -0000</pubDate><guid>https://sourceforge.net2ba4e5f4de3e81f86dbcf16b832513dffc5c05e8</guid></item><item><title>#20 Create User Save button</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/20/?limit=25#b118</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;Description has changed:&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Diff:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span class="gd"&gt;--- old&lt;/span&gt;
&lt;span class="gi"&gt;+++ new&lt;/span&gt;
&lt;span class="gu"&gt;@@ -1 +1 @@&lt;/span&gt;
&lt;span class="gd"&gt;-Create user form should have a additional butten &amp;quot;Save and create New&amp;quot;&lt;/span&gt;
&lt;span class="gi"&gt;+Create user form should have a additional butten &amp;quot;Save and create New&amp;quot;. The existign button should be &amp;quot;Save and Exit&amp;quot; (Julius)&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Priority&lt;/strong&gt;: 3 --&amp;gt; 3&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Beat Stebler</dc:creator><pubDate>Thu, 24 Oct 2013 16:53:05 -0000</pubDate><guid>https://sourceforge.netf801434c06203ca41ae906894f6dc1e64f69cbb0</guid></item><item><title>#30 Writecacheback</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/30/?limit=25#c322</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;Description has changed:&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Diff:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span class="gd"&gt;--- old&lt;/span&gt;
&lt;span class="gi"&gt;+++ new&lt;/span&gt;
&lt;span class="gu"&gt;@@ -1 +1 @@&lt;/span&gt;
&lt;span class="gd"&gt;-On persistent vm's the vm-manager should verifying if writecacheback is enabled. If yes, there should be a warning message.&lt;/span&gt;
&lt;span class="gi"&gt;+On persistent vm's the vm-manager should verifying if writecacheback is enabled. If yes, there should be a warning message before migrating a VM.&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Beat Stebler</dc:creator><pubDate>Sun, 01 Sep 2013 12:07:18 -0000</pubDate><guid>https://sourceforge.net07f581f31a2301b30f3b6717bb26864de94fd1a6</guid></item><item><title>Node Installation Script</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/31/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;After the questions IP for the gateway and IP for the DNS resolver, there should be another question if it is correct just for this area, before the script as after the correctness of the whole network information.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Beat Stebler</dc:creator><pubDate>Thu, 25 Jul 2013 10:45:55 -0000</pubDate><guid>https://sourceforge.net738cfcd347d54c93d7277b938c26875ee420796b</guid></item><item><title>Writecacheback</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/30/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;On persistent vm's the vm-manager should verifying if writecacheback is enabled. If yes, there should be a warning message.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Beat Stebler</dc:creator><pubDate>Sat, 20 Jul 2013 11:55:34 -0000</pubDate><guid>https://sourceforge.net9c0b7e92ec44b208ec14583e7808e0bb81f416a7</guid></item><item><title>Writecacheback</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/30/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 30 has been modified: Writecacheback&lt;br /&gt;
Edited By: Beat Stebler (bstebler)&lt;br /&gt;
Description updated:&lt;br /&gt;
--- description-old&lt;/p&gt;
&lt;p&gt;+++ description-new&lt;/p&gt;
&lt;p&gt;@@ -1 +1 @@&lt;/p&gt;
&lt;p&gt;-On persistent vm's the vm-manager should verifying if writecacheback is enabled. If yes, there should be a warning message.&lt;br /&gt;
+On persistent vm's the vm-manager should verifying if writecacheback is enabled. If yes, there should be a warning message before migrating a VM.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Beat Stebler</dc:creator><pubDate>Sat, 20 Jul 2013 11:55:34 -0000</pubDate><guid>https://sourceforge.net7f3420c67875d318e1246eec02fb55fbc5717e21</guid></item><item><title>Automatization installation procedure</title><link>https://sourceforge.net/p/foss-cloud/feature-requests/29/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The installation procedure should ask, if the internal network configuration should be default. So all internal staff should added automatically. If no, the script should go through the process as it is.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Beat Stebler</dc:creator><pubDate>Sat, 20 Jul 2013 08:57:40 -0000</pubDate><guid>https://sourceforge.net095036a471346c7ee71b3829c4aa0220f9b5f478</guid></item></channel></rss>