- Devel - oVirt List Archives

[oVirt 3.5 Localization Question #6] "xx with newer configuration for next run"
by Yuko Katabami 19 Jun '14

19 Jun '14

This is a multi-part message in MIME format. --------------070104050205000604020204 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello again. We have another question that requires some clarification: *File:*** CommonApplicationConstants *Resource IDs:*****desktopChanges, serverChanges, statelessDesktopChanges, statelessServerChanges *Strings:** *Desktop with newer configuration for next run Desktop with newer configuration for next run Stateless Desktop with newer configuration for next run Stateless Server with newer configuration for next run* * *Question: *How are these strings used in the GUI? Are there for specifying VMs to apply changes when rebooted? (it is difficult for us to know without having demo environment to check these on the GUI.) Kind regards, Yuko --------------070104050205000604020204 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello again. We have another question that requires some clarification: File: CommonApplicationConstants <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> Resource IDs: desktopChanges,  serverChanges,  statelessDesktopChanges,  statelessServerChanges <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> Strings: Desktop with newer configuration for next run Desktop with newer configuration for next run Stateless Desktop with newer configuration for next run Stateless Server with newer configuration for next run Question: How are these strings used in the GUI? Are there for specifying VMs to apply changes when rebooted? (it is difficult for us to know without having demo environment to check these on the GUI.) Kind regards, Yuko </body> </html> --------------070104050205000604020204--

2 2

Karma request: mom-0.4.1-1
by Adam Litke 19 Jun '14

19 Jun '14

Hi Kobi, Martin, et al. I've included the necessary changes for oVirt-3.5 into a new mom update (0.4.1) for fc19, fc20, and el6. Could you please try out these builds (especially fc20 and fc19) and give me some karma to fast-track them into updates? Thanks! https://admin.fedoraproject.org/updates/mom-0.4.1-1.fc19 https://admin.fedoraproject.org/updates/mom-0.4.1-1.fc20 https://admin.fedoraproject.org/updates/mom-0.4.1-1.el6 -- Adam Litke

2 1

supervdsm defunct bug?
by Sven Kieske 18 Jun '14

18 Jun '14

Hi, I just stumbled upon a defunct supervdsm process: root 2824 2815 0 Apr04 ? 00:01:01 /usr/bin/python /usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock --pidfile /var/run/vdsm/supervdsmd.pid qemu 31321 2824 0 May02 ? 00:00:00 [supervdsmServer] <defunct> any chance to debug this? might this be an instance of this closed (but never fixed) bug? https://bugzilla.redhat.com/show_bug.cgi?id=841486 -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

4 11

[QE][ACTION NEEDED] oVirt 3.5.0 Beta status
by Sandro Bonazzola 18 Jun '14

18 Jun '14

Hi, We're going to compose oVirt 3.5.0 Beta on Thu *2014-06-26 08:00 UTC*. Maintainers: - Please be sure that master snapshot allow to create VMs before *2014-06-25 15:00 UTC* The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1001100 integration NEW Add log gathering for a new ovirt module (External scheduler) 1073944 integration ASSIGNED Add log gathering for a new ovirt module (External scheduler) 1060198 integration NEW [RFE] add support for Fedora 20 About Add log gathering for a new ovirt module (External scheduler), patch have been merged on upstream sos master branch. Just waiting for a new sos build. Feature freeze is now effective, no more features should be pushed. The following features should be testable in 3.5.0 Beta according to Features Status Table [2] Group oVirt BZ Title gluster 1096713 Monitoring (UI plugin) Dashboard (Integrated with Nagios monitoring) gluster 1040795 Gluster Volume Capacity monitoring gluster 1083583 Gluster Profile infra 1079821 [RFE] Prevent host fencing while kdumping infra 1081049 [RFE] replace XML-RPC communication (engine-vdsm) with json-rpc based on bidirectional transport infra 1083993 [RFE] using foreman provider to provision bare-metal hosts infra 1090530 [RFE] Please add host count and guest count columns to "Clusters" tab in webadmin infra 1078738 [RFE] make ovirt easy configurable to allow redirection of all logs to syslog infra 1054778 [RFE] Allow to perform fence operations from a host in another DC infra 1090803 [RFE] Change the "Slot" field to "Service Profile" when cisco_ucs is selected as the fencing type infra 1090511 [RFE] Improve fencing robustness by retrying failed attempts infra 1090800 [RFE] Add periodic power management health check to detect/warn about link-down detection of power management LAN infra 1090529 [RFE] - introduction of Command-Coordination infrastructure infra 1090794 [RFE] Search VMs based on MAC address from web-admin portal infra 1090796 [RFE] Re-work engine ovirt-node host-deploy sequence infra 1090798 [RFE] Admin GUI - Add host uptime information to the "General" tab infra 1108861 [RFE] Support logging of commands parameters infra 1108866 [RFE] Maintenance operations on a VM would ask for an optional reason infra 1094123 [RFE][host-deploy] support more ciphers for ssh - upgrade apache-sshd to 0.11.0 infra 1108876 [RFE] report SELinux policy and show it in UI + warn when not enabled infra 1090808 [RFE] Ability to dismiss alerts and events from web-admin portal infra 1058737 [RFE] Restart HA VMs ASAP infra-api 1090797 [RFE] RESTAPI: Add /tags sub-collection for Template resource infra-cli 855724 [RFE] ovirt-engine-restapi : Statistic values representation issues infra-dwh 1091686 prevent OutOfMemoryError after starting the dwh service. infra-dwh 1091687 History DB should sync user's first and last name for user usage tables integration 1026930 ovirt-guest-tools-iso similar to rhev-guest-tools-iso and uploaded to ISO domain by default integration 1080402 Allow setup of iSCSI based storage for hosted engine integration 1080992 websocket proxy running on separate host network 1078836 Add a warning when adding display network network 1079719 Display of NIC Slave/Bond fault on Event Log network 1080984 Support bridging_opts functionality within oVirt network 1080987 Support ethtool_opts functionality within oVirt node 875088 ovirt-node-registration - a generic node registration node 1038616 ovirt node support for hosted engine nodes node 1053435 oVirt virtual appliance sla 1036731 hosted engine on iscsi sla 1093051 Integrating with Opta Planner to demonstrate a balanced cluster sla 1108602 Implement REST API for oVirt scheduler storage 1054241 Store OVF on any domains storage 1055640 Get rid of storage pool metadata on master storage domain storage 1083312 Disk alias recycling in web-admin portal storage 1086181 [RFE] Snapshot overview in webadmin portal ux 987953 support tree refresh ux 1057212 add an explanation tool-tip to the 'Feedback' button ux 1066425 UI plugin API - add SystemTreeSelectionChange callback ux 1110566 automatically select item in the grid if it is the only item ux optimize queries invocation for left-pane tree data retrieval virt 1058832 Allow to clone a (down) VM without snapshot/template virt 1031040 can't set different keymap for vnc via runonce option virt 1043471 oVirt guest agent for SLES virt 1073453 Debian 7 support (incl. 1043474 oVirt guest agent for Debian) virt 1072313 Edit Running Vm virt 1083049 add progress bar for vm migration virt 1083065 EL 7 guest compatibility virt 1083059 "Instance types (new template handling) - adding flavours" virt Allow guest serial number to be configurable virt 1047624 [RFE] support BIOS boot device menu virt 1082479 disable spice file transfer & copy and paste virt 1083129 allows setting netbios name, locale, language and keyboard settings for windows vm's virt 1108599 spice-html5 button to show debug console/output window virt 1080002 [RFE] Enable user defined Windows Sysprep file Recently added to the table: infra 1076964 [AAA] rewrite/refactor infra 1075556 Expose bookmarks through REST API network 1079691 Set 'save network configuration' default to 'true' on setup networks dialog network 1091863 Accept vlan devices identified by any name network 590413 Sort by 'IP address' (in VM tab) should not treat the IP address as a string node 984939 add method to edit and persist grub command line node 999325 Framework to publish supported services/protocols and offer a limited set of RPC functions node 1073720 Add --update option to edit-node node 75902 Add ovirt-node-config commandline tool to configure Node storage 1087059 NFS custom mountoptions storage 1095494 Support single disk snapshot on preview snapshot action in REST-API virt 557125 internationalize exitMessage; use meaningful exitCode virt 1040088 add freebsd to list of guest os's virt 1076917 Enable log-in (ssh key) for a regular user via cloud-init virt 1082497 add hostname attribute for windows sysprep infra 1084770 vdsm-tool: replace libvirt-configure.sh with python code Some more features may be included since they were near to be completed on last sync meeting. The table will be updated on next sync meeting scheduled for 2014-06-18. There are still 358 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 297 bugs [4] targeted to 3.5.0. Maintainers / Assignee: - Please remember to rebuild your packages before *2014-06-04 15:00 UTC* if needed, otherwise nightly snapshot will be taken. - Please be sure that master snapshot allow to create VMs before *2014-06-25 15:00 UTC* - If you find a blocker bug please remember to add it to the tracker [1] - Please start filling release notes, the page has been created here [5] - Please review and add test cases to oVirt 3.5 Test Day [6] Community: - You're welcome to join us testing this beta release and getting involved in oVirt Quality Assurance[7]! [1] http://bugzilla.redhat.com/1073943 [2] http://bit.ly/17qBn6F [3] http://red.ht/1pVEk7H [4] http://red.ht/1rLCJwF [5] http://www.ovirt.org/OVirt_3.5_Release_Notes [6] http://www.ovirt.org/OVirt_3.5_TestDay [7] http://www.ovirt.org/OVirt_Quality_Assurance Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 1

ovirt-engine master doesn't build anymore
by Sandro Bonazzola 18 Jun '14

18 Jun '14

See http://jenkins.ovirt.org/job/ovirt-engine_master_create-rpms-quick_gerrit/2… Please fix ASAP, thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 3

[QE][ACTION NEEDED] oVirt 3.4.3 RC status
by Sandro Bonazzola 18 Jun '14

18 Jun '14

Hi, We're going to start composing oVirt 3.4.3 RC on *2014-07-10 08:00 UTC* from 3.4 branch. A 3.4.3 branch will be created immediately after using the same hash of the build. The bug tracker [1] shows no blocking bugs for the release There are still 38 bugs [2] targeted to 3.4.3. Excluding node and documentation bugs we still have 16 bugs [3] targeted to 3.4.2. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.4.3 should not be released without them fixed. - Please update the target to any next release for bugs that won't be in 3.4.3: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please build packages before *2014-07-09 15:00 UTC*. Community: - If you're testing oVirt 3.4 nightly snapshot, please add yourself to the test page [5] [1] bugzilla.redhat.com/1107968 [2] http://red.ht/1lBAw2R [3] http://red.ht/1ly9hfA [4] http://www.ovirt.org/OVirt_3.4.3_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.4.3_Testing Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[oVirt 3.5 Localization Question #1] "Permissive"
by Yuko Katabami 18 Jun '14

18 Jun '14

This is a multi-part message in MIME format. --------------030602090603000708080005 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello all, I am a Brisbane-based translator working on oVirt 3.5 localization project along with 5 other translators, each specialized in a different locale. Our localization cycle is just kicked off and I would like to post our questions to this mailing list, just as I did for 3.4. It would be greatly appreciated if you could help us by answering questions, so that we can ensure accuracy of our translations, based on the context. Here is our first question. *File:***LocalizedEnums* **Resource ID:*** SELinuxMode___PERMISSIVE* **Strings:*** Permissive *Question:* Could someone explain to us how this appears in the Admin Portal? (we currently do not have a demo environment and cannot check it on the screen). Translators usually leave SELinux modes untranslated as they appear in the command line in English, however this string starts with the uppercase letter "P". We just wonder if this is used as descriptive or it refers exactly the "permissive" mode as shown in the terminal. Kind regards, Yuko Katabami --------------030602090603000708080005 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello all, I am a Brisbane-based translator working on oVirt 3.5 localization project along with 5 other translators, each specialized in a different locale. Our localization cycle is just kicked off and I would like to post our questions to this mailing list, just as I did for 3.4. It would be greatly appreciated if you could help us by answering questions, so that we can ensure accuracy of our translations, based on the context. Here is our first question. File: LocalizedEnums Resource ID: SELinuxMode___PERMISSIVE Strings: Permissive Question: Could someone explain to us how this appears in the Admin Portal? (we currently do not have a demo environment and cannot check it on the screen). Translators usually leave SELinux modes untranslated as they appear in the command line in English, however this string starts with the uppercase letter "P". We just wonder if this is used as descriptive or it refers exactly the "permissive" mode as shown in the terminal. Kind regards, Yuko Katabami </body> </html> --------------030602090603000708080005--

3 7

Re: [ovirt-devel] oVirt's MoM feature list ?
by Adam Litke 17 Jun '14

17 Jun '14

On 13/06/14 11:52 +0000, Vinod, Chegu wrote: >Cc'ng Gilad >Vinod > >From: Vinod, Chegu >Sent: Friday, June 13, 2014 4:45 AM >To: alitke(a)redhat.com >Subject: oVirt's MoM feature list ? > >Hi Adam, > >Where can I find some information about the future features/enhancements that are planned in MoM ? Perhaps it was discussed already in some email group or in some presentation...If yes can you please point me to the same ? This is a great question for the devel list (added to cc:). I think Doron and Martin (added to cc:) will be able to give some better responses to this as well. -- Adam Litke

3 2

Gerrit planned downtime
by David Caro 17 Jun '14

17 Jun '14

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0UcbK2UxKcnbGFPGbXNtbAHvUs0U3hihB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi! In 15 minutes I'll start updating the gerrit machine, it will take some t= ime and I'll have to reboot it after, that should be the only planned downtime, b= ut if you might have some slowness and maybe even connection failures when updating/rebooting, I'll send an update once finished. Cheers! --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --0UcbK2UxKcnbGFPGbXNtbAHvUs0U3hihB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJToIMpAAoJEEBxx+HSYmnDpqkH/02c2SOoqc18ymenAx9rZsF1 oAkJRcty1GxE3OgsdqdzVWJP6IN4hR0DxOBmWGOBA6SlyL0gnJcPMRE7sYXcB/4j FQBFNauytwfWEkfI2rcmBWGT91l2uzZntkEKlE+hkf9UEG4VZm7omwVqvg/wwLPt Z0+U3oqADJUorMTQmSiRfm1tOfp2WmMbamREyTOQHxPgzTkDtd+ElnNLMpR8rQZ+ eCip16/LQ7PBTihJu2346bS/oI/zVAZcvjTkWT677JHgG/tyHETjRLfIsWAftbdD L+MgDxXe6iFoYpEbUnAwid81xW03YR+kRXyHv+IQqgpDt09qdg6UdPcLB2Pu1n8= =da5c -----END PGP SIGNATURE----- --0UcbK2UxKcnbGFPGbXNtbAHvUs0U3hihB--

1 2

oVirt.js - source control & distribution
by Vojtech Szocs 17 Jun '14

17 Jun '14

Hello, I'd like to share my ideas on how to manage oVirt.js source code and distribution for consumer applications. Please let me know what you think, nothing is set in stone :) 1, Idea: separate git repo for oVirt.js, example: "ovirt-engine-sdk-js" - using Node/Grunt for building oVirt.js distributable package - development build: ovirt.js - production build: ovirt.min.js - source maps for production build: ovirt.min.js.map - not sure we really need platform (make/RPM) build here, since WebAdmin & UserPortal are planned to have oVirt.js injected right into their output (GWT-generated) JavaScript code (no need to fetch it at runtime) 2, Idea: contain GWT/Java overlay for oVirt.js in "ovirt-engine" repo - overlay = Java facade to oVirt.js which uses JSNI [1] to delegate calls to underlying JavaScript (oVirt.js) code - for now, WebAdmin & UserPortal are the only GWT applications intended to consume oVirt.js, we can extract the overlay into different repo later if needed 3, Idea: distribute oVirt.js via Bower [2] for common audience - just like any other JavaScript library is distributed - this is similar to oVirt _Java_ SDK distributed via Maven Central (in that case, common audience = Java developers using Maven) 4, Idea: integrate oVirt.js into Engine Maven build as dependency - building oVirt.js would (also) produce ovirt-js-<version>.jar - GWT/Java overlay project (essentially GWT module) would depend on ovirt-js-<version>.jar, including its content into overlay's output JAR - WebAdmin & UserPortal would consume ovirt-js-gwt-<version>.jar (GWT overlay) as GWT module in their <moduleName>.gwt.xml files [1] http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJSNI.html [2] http://bower.io/ Regards, Vojtech

1 0