Re: [ovirt-users] [ANN] oVirt 4.2.0 First Beta Release is now available for testing

I just tested the new 4.2, looks new shiny UI, thanks. I would like to join to Jiris statement, ovirt should become more stable, clean and useful. The right or left clicks or UI designs, mobile friendly or not,those futures are the secondary tasks for me. For those who would like to manage the vms from the mobile devices they can use mOvirt app. I wish that the development team will concentrate on the main advertised futures to make them stable. as a user I wish that the following points can make it stronger: - please make a ovirt as a FULL HA solution - one of the weak points of the ovirt is a spm, this should go away in the first point, not the right click one:). - hosts management like a foreman, but without foreman. - strong solution with a multirail HA storage - move hosts complete to disk-less infrastructure, easy to scale-up - scheduled backup solution integrated in the gui/api - reasonable reports,( similar like dwd in 3.6) Most of the points are almost done, but we have always hire or there half-solved problems. Greetings from Potsdam, Arman. PS an Ovirt user since 3.x 8hosts >50Vms 4hosts > 6VMS 10G,IB,RDMA. looking to deploy ovirt on a cluster environment on user demand. On Thu, Nov 2, 2017 at 9:34 PM, Jiří Sléžka <jiri.slezka(a)slu.cz&gt; wrote: > On 10/31/2017 06:57 PM, Oved Ourfali wrote: > >> As mentioned earlier, this is one motivation but not the only one. You >> see right click less and less in web applications, as it isn't >> considered a good user experience. This is also the patternfly guideline >> (patternfly is a framework we heavily use throughout the application). >> >> We will however consider bringing this back if there will be high demand. >> > I'm using right click time to time, but for me is much more important > clean, simple and compatible UI. Especially if this means it will be > possible to simple select and copy any text or log messages from UI. > This is my biggest pain when interacting with manager. > > Cheers, Jiri > > Thanks for the feedback! >> Oved >> >> On Oct 31, 2017 7:50 PM, "Darrell Budic" <budic(a)onholyground.com >> <mailto:budic@onholyground.com>> wrote: >> >> Agreed. I use the right click functionality all the time and will >> miss it. With 70+ VMs, I may check status in a mobile interface, but >> I’m never going to use it for primary work. Please prioritize ease >> of use on Desktop over Mobile! >> >> >> ----------------------------------------------------------- >>> ------------- >>> *From:* FERNANDO FREDIANI <fernando.frediani(a)upx.com >>> <mailto:fernando.frediani@upx.com>> >>> *Subject:* Re: [ovirt-users] [ANN] oVirt 4.2.0 First Beta Release >>> is now available for testing >>> *Date:* October 31, 2017 at 11:59:20 AM CDT >>> *To:* users(a)ovirt.org <mailto:users@ovirt.org> >>> >>> >>> On 31/10/2017 13:43, Alexander Wels wrote: >>> >>>> Will the right click dialog be available in the final release? >>>>> Because, >>>>> currently in 4.2 we need to go at the up right corner to >>>>> interact with >>>>> object (migrate, maintenance...) >>>>> >>>>> Short answer: No, we removed it on purpose. >>>> >>>> Long answer: No, here are the reasons why: >>>> - We are attempting to get the UI more mobile friendly, and while >>>> its not 100% >>>> there yet, it is actually quite useable on a mobile device now. >>>> Mobile devices >>>> don't have a right click, so hiding functionality in there would >>>> make no >>>> sense. >>>> >>> Please don't put mobile usage over Desktop usage. While mobile >>> usage is nice to have in "certain" situations. In real day by day >>> operation nobody uses mobile devices to do their deployments and >>> manage their large environments. If having both options where you >>> can switch between then is nice, but if something should prevail >>> should always be Desktop. We are not talking about a Stock Trading >>> interface or something you need that level or flexibility and >>> mobility to do static things anytime anywhere. >>> >>> So I beg you to consider well before remove things which are >>> pretty useful for a day by day and real management usage because >>> of a new trend or buzz stuff. >>> Right click is always on popular on Desktop enviroments and will >>> be for quite a while. >>> >>>> - You can now right click and get the browsers menu instead of >>>> ours and you >>>> can do things like copy from the menu. >>>> - We replicated all the functionality from the menu in the >>>> buttons/kebab menu >>>> available on the right. Our goal was to have all the commonly >>>> used actions as >>>> a button, and less often used actions in the kebab to declutter >>>> the interface. >>>> We traded an extra click for some mouse travel >>>> - Lots of people didn't realize there even was a right click menu >>>> because its >>>> a web interface, and they couldn't find some functionality that >>>> was only >>>> available in the right click menu. >>>> >>>> Now that being said, we are still debating if it was a good move >>>> or not. For >>>> now we want to see how it plays out, if a lot of people want it >>>> back, it is >>>> certainly possible we will put it back. >>>> >>>> that is something you are interested in. Its also much faster >>>>>> and better >>>>>> than before. >>>>>> >>>>>> On 31/10/2017 10:13, Sandro Bonazzola wrote: >>>>>>> >>>>>>>> The oVirt Project is pleased to announce the availability of >>>>>>>> the First >>>>>>>> Beta Release of oVirt 4.2.0, as of October 31st, 2017 >>>>>>>> >>>>>>>> >>>>>>>> This is pre-release software. This pre-release should not to >>>>>>>> be used >>>>>>>> in production. >>>>>>>> >>>>>>>> Please take a look at our community page[1] to learn how to >>>>>>>> ask >>>>>>>> questions and interact with developers and users.All issues >>>>>>>> or bugs >>>>>>>> should be reported via oVirt Bugzilla[2]. >>>>>>>> >>>>>>>> This update is the first beta release of the 4.2.0 version. >>>>>>>> This >>>>>>>> release brings more than 230 enhancements and more than one >>>>>>>> thousand >>>>>>>> bug fixes, including more than 380 high or urgent severity >>>>>>>> fixes, on >>>>>>>> top of oVirt 4.1 series. >>>>>>>> >>>>>>>> >>>>>>>> What's new in oVirt 4.2.0? >>>>>>>> >>>>>>>> * >>>>>>>> The Administration Portalhas been completely >>>>>>>> redesigned using >>>>>>>> Patternfly, a widely adopted standard in web application >>>>>>>> design. >>>>>>>> It now features a cleaner, more intuitive design, for an >>>>>>>> improved >>>>>>>> user experience. >>>>>>>> * >>>>>>>> There is an all-new VM Portalfor non-admin users. >>>>>>>> * >>>>>>>> A new High Performance virtual machinetype has been >>>>>>>> added to the >>>>>>>> New VM dialog box in the Administration Portal. >>>>>>>> * >>>>>>>> Open Virtual Network (OVN)adds support for Open >>>>>>>> vSwitch software >>>>>>>> defined networking (SDN). >>>>>>>> * >>>>>>>> oVirt now supports Nvidia vGPU. >>>>>>>> * >>>>>>>> The ovirt-ansible-rolespackage helps users with common >>>>>>>> administration tasks. >>>>>>>> * >>>>>>>> Virt-v2vnow supports Debian/Ubuntu based VMs. >>>>>>>> >>>>>>>> For more information about these and other features, check >>>>>>>> out the >>>>>>>> oVirt 4.2.0 blog post >>>>>>>> <https://ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/ >>>>>>>> <https://ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/>>;. >>>>>>>> >>>>>>>> >>>>>>>> This release is available now on x86_64 architecture for: >>>>>>>> >>>>>>>> * Red Hat Enterprise Linux 7.4 or later >>>>>>>> >>>>>>>> * CentOS Linux (or similar) 7.4 or later >>>>>>>> >>>>>>>> >>>>>>>> This release supports Hypervisor Hosts on x86_64 and ppc64le >>>>>>>> architectures for: >>>>>>>> >>>>>>>> * Red Hat Enterprise Linux 7.4 or later >>>>>>>> >>>>>>>> * CentOS Linux (or similar) 7.4 or later >>>>>>>> >>>>>>>> * oVirt Node 4.2 (available for x86_64 only) >>>>>>>> >>>>>>>> >>>>>>>> See the release notes draft [3] for installation / upgrade >>>>>>>> instructions and a list of new features and bugs fixed. >>>>>>>> >>>>>>>> >>>>>>>> Notes: >>>>>>>> >>>>>>>> - oVirt Appliance is already available. >>>>>>>> >>>>>>>> - An async release of oVirt Node will follow soon. >>>>>>>> >>>>>>>> >>>>>>>> Additional Resources: >>>>>>>> >>>>>>>> * Read more about the oVirt 4.2.0 release highlights: >>>>>>>> http://www.ovirt.org/release/4.2.0/ >>>>>>>> <http://www.ovirt.org/release/4.2.0/> >>>>>>>> <http://www.ovirt.org/release/4.2.0/ >>>>>>>> <http://www.ovirt.org/release/4.2.0/>> >>>>>>>> >>>>>>>> * Get more oVirt project updates on Twitter: >>>>>>>> https://twitter.com/ovirt >>>>>>>> >>>>>>>> * Check out the latest project news on the oVirt blog: >>>>>>>> http://www.ovirt.org/blog/ >>>>>>>> >>>>>>>> >>>>>>>> [1] https://www.ovirt.org/community/ >>>>>>>> <https://www.ovirt.org/community/> >>>>>>>> <https://www.ovirt.org/community/ >>>>>>>> <https://www.ovirt.org/community/>> >>>>>>>> >>>>>>>> [2] >>>>>>>> https://bugzilla.redhat.com/enter_bug.cgi?classification=oV >>>>>>>> irt <https://bugzilla.redhat.com/enter_bug.cgi?classification=oV >>>>>>>> irt> >>>>>>>> <https://bugzilla.redhat.com/enter_bug.cgi?classification=o >>>>>>>> Virt >>>>>>>> <https://bugzilla.redhat.com/enter_bug.cgi?classification=o >>>>>>>> Virt>> >>>>>>>> >>>>>>>> [3] http://www.ovirt.org/release/4.2.0/ >>>>>>>> <http://www.ovirt.org/release/4.2.0/> >>>>>>>> <http://www.ovirt.org/release/4.2.0/ >>>>>>>> <http://www.ovirt.org/release/4.2.0/>> >>>>>>>> >>>>>>>> [4] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ >>>>>>>> <http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/> >>>>>>>> <http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ >>>>>>>> <http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/>> >>>>>>>> >>>>>>>> >>>>>>>> SANDRO BONAZZOLA >>>>>>>> >>>>>>>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG >>>>>>>> VIRTUALIZATION R&D >>>>>>>> >>>>>>>> Red Hat EMEA <https://www.redhat.com/> >>>>>>>> >>>>>>>> <https://red.ht/sig> >>>>>>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>>>>>>> >>>>>>>> <http://www.teraplan.it/redhat-osd-2017/ >>>>>>>> <http://www.teraplan.it/redhat-osd-2017/>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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> >>>>>>>> >>>>>>> _______________________________________________ >>>>>> 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> >>>>>> >>>>> _______________________________________________ >>>> 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> >>>> >>> _______________________________________________ >>> 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> >>> >> >> _______________________________________________ >> 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> >> >> >> >> _______________________________________________ >> 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