- Users - oVirt List Archives

Archiving huge ovirt_engine_history table
by Eric Wong 26 Nov '15

26 Nov '15

--_000_2ad2e929edd04ef4a923887e0c9ab804MSEX04FRA9corpsolviansc_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello oVirt guru out there: I notice our oVirt engine postgres db size is growing quite fast for past c= ouple of months. I checked the database size. Found that our ovirt_engine= _history is 73GB in size. engine=3D# \connect ovirt_engine_history You are now connected to database "ovirt_engine_history" as user "postgres"= . ovirt_engine_history=3D# SELECT pg_size_pretty( pg_database_size( current_d= atabase() ) ) As human_size , pg_database_size( current_database() ) As raw_size; human_size | raw_size ------------+------------- 73 GB | 78444213368 (1 row) Brief check the records, there are entries dated back 2014. I want to see if there is a safe way to archive and remove some of the olde= r records? Thanks, Eric --_000_2ad2e929edd04ef4a923887e0c9ab804MSEX04FRA9corpsolviansc_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-size:8.5pt;font-family:"Hel= vetica","sans-serif"">Hello oVirt guru out there:<br> <br> I notice our oVirt engine postgres db size is growing quite fast for past c= ouple of months.  I checked the database size.  Found that our ov= irt_engine_history is 73GB in size.  <br> <br> <br> engine=3D# \connect ovirt_engine_history<br> You are now connected to database "ovirt_engine_history" as user = "postgres".<br> ovirt_engine_history=3D# SELECT pg_size_pretty( pg_database_size( current_d= atabase() ) ) As human_size<br>    , pg_database_size( current_database() ) As raw_size;<br> human_size |  raw_size<br> ------------+-------------<br> 73 GB      | 78444213368<br> (1 row)<br> <br> <br> Brief check the records, there are entries dated back 2014.  <br> <br> I want to see if there is a safe way to archive and remove some of the olde= r records?<br> <br> Thanks,<br> Eric</span><o:p></o:p></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif""><o:p> </o:p></span></p> </div> </body> </html> --_000_2ad2e929edd04ef4a923887e0c9ab804MSEX04FRA9corpsolviansc_--

2 1

VM Network activity on RHEV-M UI
by Marc Seward 26 Nov '15

26 Nov '15

I'm generating network activity on a RHEV 3.5 VM using iperf.The VM acts as an iperf client.On the client,iperf reports that data has been successfully sent to iperf server.The iperf server also shows that it's successfully receiving data from the iperf client.But,network is at 0% on the RHEV-M UI.The client and server are on different private networks. On the same VM,when I generate network activity by fetching a file from a public network using wget,the network column correctly shows activity on the RHEV-M UI for the VM. Could someone help me understand why I am unable to see network activity on the RHEV-M UI when iperf is used? Appreciate your help.TIA.

2 1

Node not talking NFS to Node.
by admin 26 Nov '15

26 Nov '15

Hello Been trying to resolve a problem with my second node which does not want to connect : one of my 2 nodes are not connecting, the problem is that the Node cant talk NFS to Node. the node used to function fine, after performing a hardware upgrade and bringing the system back up it seems to have come up with this issue. we also performed a yum update, updated around 447 packages. Can someone please help me with this. Thanks Sol

3 3

3.6: vNIC profiles aren't selectable - can't add NIC for VMs
by Wee Sritippho 26 Nov '15

26 Nov '15

Hi, I'm trying to add virtual NICs for a new VM. However, there is no vNIC profile in the drop down list for 'nic1' even though I already have a vNIC profile named 'ovirtmgmt' within 'ovirtmgmt' network. I attached 'ovirt-cant-add-nic-for-vms.mp4' as a visual explanation. oVirt 3.6 @ CentOS 7 Regards, Wee --- ซอฟต์แวร์ Avast แอนตี้ไวรัสตรวจสอบหาไวรัสจากอีเมลนี้แล้ว https://www.avast.com/antivirus

1 0

Re: [ovirt-users] Ovirt 3.6 | After upgrade host can not connect to storage domains | returned by VDSM was: 480
by Sahina Bose 26 Nov '15

26 Nov '15

This is a multi-part message in MIME format. --------------010405060202050306040708 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit The error 480 - Gluster volume replica count is not supported, seems to indicate that vdsm has not read the updated conf. Have you made the change in all the nodes (hypervisor)? [+users] On 11/26/2015 07:13 AM, Punit Dambiwal wrote: > Hi Sahina, > > Still the same error "480" > > Engine Logs :- http://fpaste.org/294595/ > > ----------- > 2015-11-06 15:01:51,042 ERROR > [org.ovirt.engine.core.bll.storage.BaseFsStorageHelper] > (DefaultQuartzScheduler_Worker-78) [40bde6e1] The connection with > details 'gluster1.3linux.com:/ssd' failed because of error code '480' > and error message is: 480 > 2015-11-06 15:01:51,103 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (DefaultQuartzScheduler_Worker-78) [40bde6e1] Correlation ID: null, > Call Stack: null, Custom Event ID: -1, Message: The error message for > connection gluster.3linux.com:/sata returned by VDSM was: 480 > 2015-11-06 15:01:51,104 ERROR > [org.ovirt.engine.core.bll.storage.BaseFsStorageHelper] > (DefaultQuartzScheduler_Worker-78) [40bde6e1] The connection with > details 'gluster.3linux.com:/sata' failed because of error code '480' > and error message is: 480 > 2015-11-06 15:01:51,104 INFO > [org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] > (DefaultQuartzScheduler_Worker-78) [40bde6e1] Host 'compute6' storage > connection was failed > ---------- > > Thanks, > Punit > > On Wed, Nov 25, 2015 at 9:30 PM, Sahina Bose <sabose(a)redhat.com > <mailto:sabose@redhat.com>> wrote: > > Hi Punit, > > Based on comment 2 in > https://bugzilla.redhat.com/show_bug.cgi?id=1238093, you should be > able to edit /etc/vdsm/vdsm.conf > > allowed_replica_counts=2,3 > > and restart vdsm. > > Could you attach error that you continue to face (post above step?) > > > > On 11/25/2015 08:02 AM, Punit Dambiwal wrote: >> Hi Sahina, >> >> Yes...i have restarted the vdsm and even rebooted the whole >> machine but not work.. >> >> On Tue, Nov 24, 2015 at 10:19 PM, Sahina Bose <sabose(a)redhat.com >> <mailto:sabose@redhat.com>> wrote: >> >> Have you restarted vdsm? >> >> On 11/24/2015 07:38 AM, Punit Dambiwal wrote: >>> Hi Sahina, >>> >>> Either after make the changes in the vdsm.conf,still not >>> able to connect to the replica=2 storage.. >>> >>> Thanks, >>> Punit >>> >>> On Mon, Nov 23, 2015 at 4:15 PM, Punit Dambiwal >>> <hypunit(a)gmail.com <mailto:hypunit@gmail.com>> wrote: >>> >>> Hi Sahina, >>> >>> Thanks for the update...would you mind to let me know >>> the correct syntax to add the line in the vdsm.conf ?? >>> >>> Thanks, >>> Punit >>> >>> On Mon, Nov 23, 2015 at 3:48 PM, Sahina Bose >>> <sabose(a)redhat.com <mailto:sabose@redhat.com>> wrote: >>> >>> You can change the allowed_replica_count to 2 in >>> vdsm.conf - though this is not recommended in >>> production. Supported replica count is 3. >>> >>> thanks >>> sahina >>> >>> >>> On 11/23/2015 07:58 AM, Punit Dambiwal wrote: >>>> Hi Sahina, >>>> >>>> Is there any workaround to solve this issue ? >>>> >>>> Thanks, >>>> Punit >>>> >>>> On Wed, Nov 11, 2015 at 9:36 AM, Sahina Bose >>>> <sabose(a)redhat.com <mailto:sabose@redhat.com>> wrote: >>>> >>>> Hi, >>>> >>>> Thanks for your email. I will be back on 16th >>>> Nov and will get back to you then. >>>> >>>> thanks >>>> sahina >>>> >>>> >>> >>> >>> >> >> > > --------------010405060202050306040708 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> The error 480 - Gluster volume replica count is not supported, seems to indicate that vdsm has not read the updated conf.<br> Have you made the change in all the nodes (hypervisor)?<br> <br> [+users]<br> <br> <br> <br> <div class="moz-cite-prefix">On 11/26/2015 07:13 AM, Punit Dambiwal wrote:<br> </div> <blockquote cite="mid:CAGZcrBn+8Vh4kkkrCwPyhx+XaQgtwaj344D2KXAXPF+Lio=NOw@mail.gmail.com" type="cite"> <div dir="ltr">Hi Sahina, <div><br> </div> <div>Still the same error "480"</div> <div><br> </div> <div>Engine Logs :- <a moz-do-not-send="true" href="http://fpaste.org/294595/">http://fpaste.org/294595/</a></div> <div><br> </div> <div>-----------</div> <div> <div>2015-11-06 15:01:51,042 ERROR [org.ovirt.engine.core.bll.storage.BaseFsStorageHelper] (DefaultQuartzScheduler_Worker-78) [40bde6e1] The connection with details 'gluster1.3linux.com:/ssd' failed because of error code '480' and error message is: 480</div> <div>2015-11-06 15:01:51,103 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-78) [40bde6e1] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: The error message for connection gluster.3linux.com:/sata returned by VDSM was: 480</div> <div>2015-11-06 15:01:51,104 ERROR [org.ovirt.engine.core.bll.storage.BaseFsStorageHelper] (DefaultQuartzScheduler_Worker-78) [40bde6e1] The connection with details 'gluster.3linux.com:/sata' failed because of error code '480' and error message is: 480</div> <div>2015-11-06 15:01:51,104 INFO [org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-78) [40bde6e1] Host 'compute6' storage connection was failed</div> </div> <div>----------</div> <div><br> </div> <div>Thanks,</div> <div>Punit</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Wed, Nov 25, 2015 at 9:30 PM, Sahina Bose <span dir="ltr"><<a moz-do-not-send="true" href="mailto:sabose@redhat.com" target="_blank">sabose(a)redhat.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div text="#000000" bgcolor="#FFFFFF"> Hi Punit,<br> <br> Based on comment 2 in <a moz-do-not-send="true" href="https://bugzilla.redhat.com/show_bug.cgi?id=1238093" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1238093</a>, you should be able to edit /etc/vdsm/vdsm.conf<br> <br> allowed_replica_counts=2,3<br> <br> and restart vdsm.<br> <br> Could you attach error that you continue to face (post above step?) <div> <div class="h5"><br> <br> <br> <div>On 11/25/2015 08:02 AM, Punit Dambiwal wrote:<br> </div> <blockquote type="cite"> <div dir="ltr">Hi Sahina, <div><br> </div> <div>Yes...i have restarted the vdsm and even rebooted the whole machine but not work..</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Tue, Nov 24, 2015 at 10:19 PM, Sahina Bose <span dir="ltr"><<a moz-do-not-send="true" href="mailto:sabose@redhat.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:sabose@redhat.com">sabose(a)redhat.com</a></a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div text="#000000" bgcolor="#FFFFFF"> Have you restarted vdsm?<span><br> <br> <div>On 11/24/2015 07:38 AM, Punit Dambiwal wrote:<br> </div> <blockquote type="cite"> <div dir="ltr">Hi Sahina, <div><br> </div> <div>Either after make the changes in the vdsm.conf,still not able to connect to the replica=2 storage..</div> <div><br> </div> <div>Thanks,</div> <div>Punit</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Mon, Nov 23, 2015 at 4:15 PM, Punit Dambiwal <span dir="ltr"><<a moz-do-not-send="true" href="mailto:hypunit@gmail.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:hypunit@gmail.com">hypunit(a)gmail.com</a></a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr">Hi Sahina, <div><br> </div> <div>Thanks for the update...would you mind to let me know the correct syntax to add the line in the vdsm.conf ??</div> <div><br> </div> <div>Thanks,</div> <div>Punit</div> </div> <div> <div> <div class="gmail_extra"><br> <div class="gmail_quote">On Mon, Nov 23, 2015 at 3:48 PM, Sahina Bose <span dir="ltr"><<a moz-do-not-send="true" href="mailto:sabose@redhat.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:sabose@redhat.com">sabose(a)redhat.com</a></a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div text="#000000" bgcolor="#FFFFFF"> You can change the allowed_replica_count to 2 in vdsm.conf - though this is not recommended in production. Supported replica count is 3.<br> <br> thanks<span><font color="#888888"><br> sahina</font></span> <div> <div><br> <br> <div>On 11/23/2015 07:58 AM, Punit Dambiwal wrote:<br> </div> <blockquote type="cite"> <div dir="ltr">Hi Sahina, <div><br> </div> <div>Is there any workaround to solve this issue ?</div> <div><br> </div> <div>Thanks,</div> <div>Punit</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Wed, Nov 11, 2015 at 9:36 AM, Sahina Bose <span dir="ltr"><<a moz-do-not-send="true" href="mailto:sabose@redhat.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:sabose@redhat.com">sabose(a)redhat.com</a></a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> <br> Thanks for your email. I will be back on 16th Nov and will get back to you then.<br> <br> thanks<br> <span><font color="#888888">sahina<br> </font></span></blockquote> </div> <br> </div> </blockquote> <br> </div> </div> </div> </blockquote> </div> <br> </div> </div> </div> </blockquote> </div> <br> </div> </blockquote> <br> </span></div> </blockquote> </div> <br> </div> </blockquote> <br> </div> </div> </div> </blockquote> </div> <br> </div> </blockquote> <br> </body> </html> --------------010405060202050306040708--

2 1

Re: [ovirt-users] oVirt 4.0 wishlist: oVirt Self Hosted Engine Setup
by Giuseppe Ragusa 25 Nov '15

25 Nov '15

On Wed, Nov 25, 2015, at 12:13, Simone Tiraboschi wrote: > > > On Mon, Nov 23, 2015 at 10:10 PM, Giuseppe Ragusa <giuseppe.ragusa(a)hotmail.com> wrote: >> Hi all, >> I go on with my wishlist, derived from both solitary mumblings and community talks at the the first Italian oVirt Meetup. >> >> I offer to help in coding (work/family schedules permitting) but keep in mind that I'm a sysadmin with mainly C and bash-scripting skills (but hoping to improve my less-than-newbie Python too...) >> >> I've sent separate wishlist messages for oVirt Node, oVirt Engine and VDSM. >> >> oVirt Self Hosted Engine Setup: >> >> *) allow virtual hardware customizations for locally-created Engine vm, specifically: allow to add an arbitrary number of NICs (asking for MAC address and local bridge to connect to) and maybe also an arbitrary number of disks (asking for size) as these seem to be the only/most_useful items missing; maybe the prebuilt appliance image too may be inspected by setup to detect a customized one and connect any further NICs to custom local bridges (which the user should be asked for) > > For 3.6.1 (it should be in 3.6.0 but it's bugged) you will be able to edit some parameter of the engine VM from the engine (than of course you need to reboot to make them effective). > I'm not sure if it's worth to make the setup more complex or if it's better to keep it simple (single nic, single disk) and then let you edit the VM only from the engine as for other VMs. Thanks Simone for your reply! You are right: I was bothering you with this setup wishlist item *mainly* because further Engine vm modification was impossible/awkward/difficult before 3.6.1 Nonetheless I have seen many cases in which at least a second NIC would be absolutely needed to complete the Engine installation: it is a well known best practice to keep the management network (maybe conflated with the IPMI network in smaller cases) completely isolated from other services and to allow only limited access to/from it, and that network would be the ovirtmgmt-bridge-connected network (the only one available to the Engine, as of now); now think of a kickstart-based Engine OS installation/update from a local repository/mirror which would be reachable on a different network only (further access to the User/Administration Web portal could have similar needs but could be more easily covered by successive Engine vm modifications) The "additional disks" part was (maybe "artificially") added by me out of fantasy, but I know of at least one enterprise customer that by policy mandates separate disks for OS and data (mainly on FC LUNs, to be honest, but FC is supported by hosted Engine now, isn't it?) I absolutely don't know how the setup code is structured (and the recent logical "duplication" between mixins.py and vm.conf.in scares me a bit, actually ;), but I naively hope that changing the two single hardcoded nic/hdd questions into two loops of minimum 1 iteration (with a corresponding generalization of related otopi parameters) should not increase the complexity too much (and could be an excuse to rationalize/unify it further). Obviously I could stand instantly corrected by anyone who really knows the code, but in exchange I would gain for free some interesting pointers/insights into the setup code/structure ;) >> Regards, >> Giuseppe >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users

1 0

Updated Invitation: [Deep dive] Host Network QoS - oVirt 3.6 @ Wed Dec 2, 2015 5pm - 6pm (ibarkan@redhat.com)
by ibarkan＠redhat.com 25 Nov '15

25 Nov '15

This event has been changed. Title: [Deep dive] Host Network QoS - oVirt 3.6 Hangouts on air: https://plus.google.com/events/c3la9vdse911atq991qflogtq0g you tube link: https://plus.google.com/events/c3la9vdse911atq991qflogtq0g When: Wed Dec 2, 2015 5pm - 6pm Jerusalem (changed) Calendar: ibarkan(a)redhat.com Who: * ibarkan(a)redhat.com - organizer * users(a)ovirt.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NGZxZXU0dDRka2ZrMmd1c… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account users(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Import OVA
by Massimo Mad 25 Nov '15

25 Nov '15

Hi, How i cam inport a virtual appliance (OVA), what should I write in the field "path" ? I try with 10.10.10.73:/export/nfsshare but i have this error: VDSM ovirtsrv102 command failed: ['Permission denied, please try again.', 'Permission denied, please try again.', 'Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).', '/usr/bin/tar: 10.10.10.73\\:/export/nfsshare: Cannot open: Input/output error', '/usr/bin/tar: Error is not recoverable: exiting now'] I try to add the memory on a running vm ad i have this error: Failed to hot set memory to VM CoverterV2V-REL6. Underlying error message: unsupported configuration: unknown device type 'memory' VDSM ovirtsrv104 command failed: unsupported configuration: unknown device type 'memory' Regards Massimo

3 5

[ANN] oVirt 3.6.1 First Release Candidate is now available for testing
by Sandro Bonazzola 25 Nov '15

25 Nov '15

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.1 for testing, as of November 25th, 2015. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.1, CentOS Linux >= 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.1, CentOS Linux >= 7.1 (or similar) and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.1 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO is also available[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 1

oVirt Node roadmap
by Fabian Deutsch 25 Nov '15

25 Nov '15

Hey, in the last few months the Node team spent a lot of efforts in stabilizing Node by closing tons of bugs, rebasing Node onto CentOS 7.2, and in addition adding features like Hosted-Engine - to get Node in shape for the recently released oVirt 3.6.0. But we were also seeing how Node is showing it's age. It becomes more and more challenging to solve bugs and implement features in Node's current architecture. To address these problems, and let Node adjust better to new changes, a few months ago we started to look at how we can change Node, to make it easier to develop, test, and use. This comparison [1] shows a brief summary of our investigations. We especially looked at Atomic and containers [2]. At the bottom line both of them provided us an architecture which would help us to achieve something like 70% of what we need. But during early trials we quickly ran into issues which we experience in similar ways with today's Node. Finally we settled an approach - the idea was around since right from the beginning - which aligns very well with existing technologies which we already use in the oVirt and Fedora/CentOS scope. The new Node will be using anaconda for installation, LVM for upgrades and rollbacks, and Cockpit [3] for administration. The future design is taking care that packages don't need to take special care to work on Node - which was a major obstacle in the past. Node will rather behave (mostly) like a regular host - but with the advantages of an easy & ready to use image, image based delivery and a robust rollback. The current design principles and links to some additional resources are in the wiki [4]. Stay tuned, we are just getting started. On behalf of the Node Team fabian -- [1] http://www.ovirt.org/Node/Specs#Comparison:_Possible_Implementations [2] http://www.projectatomic.io/ ~ http://docker.com/ [3] http://cockpit-project.org/ [4] http://www.ovirt.org/Node/4.0

1 0