October 2015 - Devel - oVirt List Archives

AppErrors cleanup
by Allon Mureinik 15 Dec '15

15 Dec '15

Hi all, A recent bug [1] reported as part of the translation effort alerted me to the fact that we have a lot (and I mean a LOT - over 100 per file) of deprecated, unused keys in the various AppErrors files that serve no purpose and just take up space and waste translators time when they examine them. To make a long story short - I've just merged a patch to remove all these useless messages, and enforce via unit tests that EVERY key there should have a corresponding constant in the EngineMessage or EngineError enums. Many thanks to my reviewers! I know this was an tedious patch that couldn't have been too fun to review. -Allon [1] https://bugzilla.redhat.com/show_bug.cgi?id=1244766

5 6

Proposal: Hystrix for realtime command monitoring
by Roman Mohr 15 Dec '15

15 Dec '15

Hi All, I am contributing to the engine for three months now. While I dug into the code I started to wonder how to visualize what the engine is actually doing. To get better insights I added hystrix[1] to the engine. Hystrix is a circuit breaker library which was developed by Netflix and has one pretty interesting feature: Real time metrics for commands. In combination with hystrix-dashboard[2] it allows very interesting insights. You can easily get an overview of commands involved in operations, their performance and complexity. Look at [2] and the attachments in [5] and [6] for screenshots to get an Impression. I want to propose to integrate hystrix permanently because from my perspective the results were really useful and I also had some good experiences with hystrix in past projects. A first implementation can be found on gerrit[3]. # Where is it immediately useful? During development and QA. An example: I tested the hystrix integration on /api/vms and /api/hosts rest endpoints and immediately saw that the number of command exectuions grew lineary whit the number of vms and hosts. The bug reports [5] and [6] are the result. # How to monitor the engine? It is as easy as starting a hystrix-dashboard [2] with $ git clone https://github.com/Netflix/Hystrix.git $ cd Hystrix/hystrix-dashboard $ ../gradlew jettyRun and point the dashboard to https://<customer.engine.ip>/ovirt-engine/hystrix.stream. # Other possible benefits? * Live metrics at customer site for admins, consultants and support. * Historical metrics for analysis in addition to the log files. The metrics information is directly usable in graphite [7]. Therefore it would be possible to collect the json stream for a certain time period and analyze them later like in [4]. To do that someone just has to run curl --user admin@internal:engine http://localhost:8080/ovirt-engine/api/hystrix.stream > hystrix.stream for as long as necessary. The results can be analyzed later. # Possible architectural benefits? In addition to the live metrics we might also have use for the real hystrix features: * Circuit Breaker * Bulk execution of commands * De-dublication of commands (Caching) * Synchronous and asynchronous execution support * ... Our commands do already have a lot of features, so I don't think that there are some quick wins, but maybe there are interesting opportunities for infra. # Overhead? In [5] the netflix employees describe their results regarding the overhead of wrapping every command into a new instance of a hystrix command. They ran their tests on a standard 4-core Amazon EC2 server with a load of 60 request per second. When using threadpools they measured a mean overhead of less than one millisecond (so negligible). At the 90th percentile they measured an overhead of 3 ms. At the 99th percentile of about 9 ms. When configuring the hystrix commands to use semaphores instead of threadpools they are even faster. # How to integrate? A working implementation can be found on gerrit[3]. These patch sets wrap a hystrix command around every VdcAction, every VdcQuery and every VDSCommand. This just required four small modifications in the code base. # Security? In the provided patches the hystrix-metrics-servlet is accessible at /ovirt-engine/api/hystrix.stream. It is protected by basic auth but accessible for everyone who can authenticate. We should probably restrict it to admins. # Todo? 1) We do report failed actions with return values. Hystrix expects failing commands to throw an exception. So on the dashboard almost every command looks like a success. To overcome this, it would be pretty easy to throw an exception inside the command and catch it immediately after it leaves the hystrix wrapper. 2) Finetuning Do we want semaphores or a thread pool. When the thread pool, what size do we want? 3) Three unpackaged dependencies: archaius, hystrix-core, hystrix-contrib # References [1] https://github.com/Netflix/Hystrix [2] https://github.com/Netflix/Hystrix/tree/master/hystrix-dashboard [3] https://gerrit.ovirt.org/#/q/topic:hystrix [4] http://www.nurkiewicz.com/2015/02/storing-months-of-historical-metrics.html [5] https://github.com/Netflix/Hystrix/wiki/FAQ#what-is-the-processing-overhead… [5] https://bugzilla.redhat.com/show_bug.cgi?id=1268216 [6] https://bugzilla.redhat.com/show_bug.cgi?id=1268224 [7] http://graphite.wikidot.com

3 5

Maintainer rights on vdsm - ovirt-3.5-gluster
by Sahina Bose 17 Nov '15

17 Nov '15

Hi! On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to Bala (barumuga(a)redhat.com) ? thanks sahina

4 11

Running oVirt 3.5 on fc21 with open jdk 1.8 (dev)
by Eli Mesika 05 Nov '15

05 Nov '15

Hi I upgraded my workstation from fc20 to fc21 and had troubles running engine-setup on a 3.5 application. The following instructions did the trick to me (Thanks to Alon Bar Lev) 1) Download jboss-eap-x.y from http://www.jboss.org/products/eap/overview/ (zip) 2) Extract it to /opt (insure that it has the right permissions) 3) set the following environment variables : a) export OVIRT_ENGINE_JAVA_HOME=/usr/lib/jvm/jre b) export OVIRT_ENGINE_JAVA_HOME_FORCE=1 4) run engine-setup as follows : engine-setup --jboss-home=/opt/jboss-eap-x.y Thanks Eli Mesika

2 1

Re: [ovirt-devel] [oVirt 3.6 Localization Question #35] "QoS Out average"
by Yuko Katabami 04 Nov '15

04 Nov '15

Hello again, I need to re-post this as still requiring some extra information about "Out" part of theses strings. Is it referring to "Outbound"? Kind regards, Yuko On Thu, Oct 29, 2015 at 5:56 AM, Yuko Katabami <ykatabam(a)redhat.com> wrote: > Hi Eliraz, > > Just in case you overlooked, I had one additional question in my last > reply, which is: > > I need one additional clarification. > In "QoS Out xxx", "out" stands for "outgoing"? (as for outgoing traffic?) > > Could you please help me with this as well? > > Kind regards, > > Yuko > > On Wed, Oct 28, 2015 at 7:05 PM, Yuko Katabami <ykatabam(a)redhat.com> > wrote: > >> Hi Eliraz and all, >> >> Thank you very much for replying to my question with thorough information. >> I need one additional clarification. >> In "QoS Out xxx", "out" stands for "outgoing"? (as for outgoing traffic?) >> >> Kind regards, >> >> Yuko >> >> >> On Wed, Oct 28, 2015 at 6:32 PM, Eliraz Levi <elevi(a)redhat.com> wrote: >> >>> Hi, >>> these strings represent different QoS configuration values. >>> These will be represented in the "out of sync tool tip" in case of >>> differences between the values configured in the host and the those defined >>> in the Data center (DC). >>> a screen shot is attached. >>> steps to reproduce: >>> 1. add a host. >>> 2. attache a network to a host's interface using setup network. >>> 3. edit the host's attached network using the pencil to the right, >>> check "override qos" checkbox and add values in the fields. (say 12, 11, >>> 11) >>> 4. press ok twice (setup network will take action now). wait until the >>> action successfully finished. >>> 5. open a terminal to the host. >>> 6. as root, >>> # tc class change dev <host_interface_name_of_step_2> parent 1389: >>> classid 1388 hfsc ul m2 2008bit ls m2 808 rt m2 1108bit >>> 7. refresh host capabilities. >>> 8. go to setup network and hover over the out of sync icon. >>> >>> for any more details or questions, feel free to ask me :) >>> >>> thanks. >>> >>> Eliraz. >>> >>> >>> >>> >>> ----- Original Message ----- >>> >>> >>> From: "Moti Asayag" <masayag(a)redhat.com> >>> To: "Eliraz Levi" <elevi(a)redhat.com>, "Alona Kaplan" < >>> alkaplan(a)redhat.com> >>> Sent: Wednesday, 28 October, 2015 9:22:16 AM >>> Subject: Fwd: [ovirt-devel] [oVirt 3.6 Localization Question #35] "QoS >>> Out average" >>> >>> Please reply >>> >>> >>> ---------- Forwarded message ---------- >>> From: Yuko Katabami <ykatabam(a)redhat.com> >>> Date: Tue, Oct 27, 2015 at 2:59 AM >>> Subject: [ovirt-devel] [oVirt 3.6 Localization Question #35] "QoS Out >>> average" >>> To: devel(a)ovirt.org >>> >>> >>> Hello all, >>> >>> I would like to ask for your help with the following question. >>> >>> File: ApplicationConstants >>> Resource IDs: >>> outAverageLinkShareOutOfSyncPopUp >>> outAverageRealTimeOutOfSyncPopUp >>> outAverageUpperLimitOutOfSyncPopUp >>> Strings: >>> QoS Out average link share >>> QoS Out average real time >>> QoS Out average upper limit >>> Question: Could anyone please tell us where these strings appear in >>> the GUI and how they are used? >>> >>> Kind regards, >>> >>> Yuko Katabami >>> >>> >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >>> >>> >>> -- >>> Regards, >>> Moti >> >> >> >> >> >> > > > >

2 1

Contribute with Ovirt
by Somansh Arora 01 Nov '15

01 Nov '15

Hi All, I am a Linux Admin from India aged 24, working for a reputed company handling their Linux, AIX and HPUX server from last 2 years. I would like to give some of my time now contributing to some of the open projects. I liked ovirt. Please let me know if i could be of any help in any ways around. Help from anyone in your team responding to me is appreciated. -- Thanks & Regards Somansh Arora +91- 9582671964

4 4

vdsm_master_unit-tests_merged is failing
by Sandro Bonazzola 30 Oct '15

30 Oct '15

Hi, looks like http://jenkins.ovirt.org/job/vdsm_master_unit-tests_merged/ is failing due to non infra issues. Can you please take a look at http://jenkins.ovirt.org/job/vdsm_master_unit-tests_merged/872/console ? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[ATN] Switch to Java 8 in master branch merged
by Juan Hernández 30 Oct '15

30 Oct '15

Hello, The change that switches the master branch to Java 8 has been merged: core: Use Java 8 as source and target https://gerrit.ovirt.org/46288 Make sure that you use Java 8 in your development and runtime environments. This change doesn't affect other branches, only master. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

1 0

[ANN] oVirt 3.5.6 First Release Candidate is now available for testing
by Sandro Bonazzola 29 Oct '15

29 Oct '15

The oVirt Project is pleased to announce the availability of the First oVirt 3.5.6 Release Candidate for testing, as of October 29th, 2015. This release is available now for 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 6.7, CentOS Linux 6.7 (or similar), Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar) and Fedora 21. This release includes updated packages for: - oVirt Engine - oVirt Engine client - oVirt Engine SDK - oVirt Hosted Engine HA - QEMU KVM and its dependencies - VDSM See the release notes [1] for a list of fixed bugs. Please refer to release notes [1] for Installation / Upgrade instructions. a new oVirt Live ISO is already 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. Please add yourself to the test page[4] if you're testing this release. [1] http://www.ovirt.org/OVirt_3.5.6_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/ovirt-live/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors [4] http://www.ovirt.org/Testing/oVirt_3.5.6_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Fwd: System V to systemd unit migration
by Sandro Bonazzola 28 Oct '15

28 Oct '15

FYI ---------- Forwarded message ---------- From: Stephen Gallagher <sgallagh(a)redhat.com> Date: Wed, Oct 28, 2015 at 7:12 PM Subject: System V to systemd unit migration To: devel-announce(a)lists.fedoraproject.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At the FESCo meeting on October 14th, it was decided that the time has come to finally complete the migration away from System V init scripts. What does this mean for you as a packager? When we branch from Rawhide for Fedora 24 (currently scheduled for February 2nd, 2016), we will be immediately retiring any package in the Fedora collection that relies on a System V init script instead of a systemd unit file to start. We will consider reasonable requests to delay this action on a case-by-case basis for anyone who submits a ticket to FESCo no later than 23:59 UTC on January 12, 2016. There is no plan to remove System V compatibility from Fedora, due to the necessity of supporting legacy third-party software. We are also not making any changes at all to the EPEL project. EPEL packages may continue to use System V init scripts (in the case of EPEL 5 and EPEL 6, there is no other option). We will be going through the Wiki packaging documentation over the next month and updating all related entries to reflect this change in policy. This will be the first such announcement. The Change Wrangler will be sending additional reminders from now until February 2nd, so no one will be surprised by this event. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlYxEAAACgkQeiVVYja6o6NmxwCeI7gSKCwmQ7AtBqoM3MoB8Q7a SlgAniagJ8mrWWmr/BTqEyltF21FRbBd =U6rs -----END PGP SIGNATURE----- _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Call for Proposals: Virtualization & IaaS Devroom at FOSDEM 2016
by Mikey Ariel 28 Oct '15

28 Oct '15

I'm happy to announce that the call for proposals is now open for the virtualization and Infrastructure-as-a-Service devroom at FOSDEM 2016. See the full text in this blog post: http://community.redhat.com/blog/2015/10/call-for-proposals-fosdem16-virtua… Please don't hesitate to ping me with any questions, as well as share this post with people or projects that you think might be interested. Cheers, Mikey -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady

1 0

Re: [ovirt-devel] [ATN] Introduction of RESTAPI metamodel
by Juan Hernández 28 Oct '15

28 Oct '15

On 10/26/2015 04:56 PM, Roman Mohr wrote: > Hi Juan, > > The way to specify the contract look pretty clean and nice. > I would love to read a few words about the big picture. What is the > final scenario? > The motivation for this change is that currently we don't have a central place where the RESTAPI is specified, rather we have several different places, using several different technologies: * XML schema for the data model. * JAX-RS for part of the operational model (without the parameters). * rsdl_metadata.yaml for the parameters of the operational model. This makes it difficult to infer information about the model. For example, the generators of the SDKs have to download the XML schema, and the RSDL (which is generated from the JAX-RS interfaces using reflection and combining it with the information from the rsdl_metadata.yaml file) and then they have to do their own computations to extract what they need. Same happens with the CLI: it has to extract the information it needs from the Python code generated for the Python SDK, yet another level of indirection. We are also lacking a comprehensive reference documentation of the RESTAPI. What we currently have has been written by hand, and gets out of sync very quickly, and we don't even notice. To solve these issues I intend to have the specification of the RESTAPI only in one place, and using only one technology. I decided to use Java interfaces for that. Note however that they are just the support for the information, like paper is the support for ink. I decided to use Java because it is easy to create, modify and re-factor using tools familiar to most of us. These source of these interfaces is analysed (using QDox, currently) and a "model" of the RESTAPI is generated in memory. This model is independent of the supporting Java source, and easy to consume. For example, imagine that you want to list all the types available in the model and for each one display its documentation: Model model = ...; for (Type type : model.getTypes()) { Name name = type.getName(); String doc = type.getDoc(); System.out.println(name + ": " + doc); } Something like this, but more elaborate, will be part of a web application that provides comprehensive reference documentation, assuming that we dedicate the time to write documentation comments in the specification. I intend to use this model also to do simplify the generators of the SDKs and the CLI. In addition these are some of the things that I would like to change in the near future (for 4.0): * Move the specification of the parameters of operations out of the rsdl_metadata.yaml file and into the model. For example: @Service public VmService { /** * The operation to add a virtual machine. */ interface Add { /** * The representation of the virtual machine is received * as parameter, and the representation of the created * virtual machine is returned as result. */ @In @Out Vm vm(); /** * In the future, we will be able to specify other * parameters here. */ @In Boolean force(); /** * Even with default values. */ @In default Boolean force() { return true; } /** * And we will be able to specify constraints, which * will replace the rsdl_metadata.yaml file. */ @Constraint default boolean vmNameMustNotBeNull() { return vm().name() != null; } } } * Enforce the constraints automatically. If the constraints are in the model, then we can just check them and reject requests before delivering them to the application. Currently we do this manually (and often forget) with calls to "validate(...)" methods. * Generate the Java classes directly from the model. Instead of Model -> XML Schema -> Java, we can do Model -> Java. This will allow us to solve some of the XJC compiler limitations, like the horrible way we handle arrays today. * Replace JAX-RS with a simpler infrastructure that supports better streaming and CDI injection. * Add support for multiple versions of the API, using the "Version" header, and generating different Java classes for entities and services. For example, if we have versions 4 and 5 of the model as separate artifacts, then we can generate "V4Vm" and "V5Vm" entity classes, and "V4VmService" and "V5VmService" service classes. These can be used simultaneously in the server, so we can have in the same engine implementations for multiple versions. The final picture isn't completely defined yet. Regards, Juan Hernandez > On Mon, Oct 26, 2015 at 4:03 PM, Juan Hernández <jhernand(a)redhat.com > <mailto:jhernand@redhat.com>> wrote: > > Hello, > > I will soon merge the following patches that introduce a new way to > specify the contracts of the RESTAPI: > > restapi: Introduce metamodel > https://gerrit.ovirt.org/45852 > > restapi: Use metamodel > https://gerrit.ovirt.org/46478 > > restapi: Generate JAX-RS interfaces from model > https://gerrit.ovirt.org/47337 > > > Looks pretty much like we are replacing one way of annotating things > with another way of specifying things. > Could you elaborate what the benefit of that way of description is? > > How would I customize endpoints with e.g. @Gzip annotations? Would I at > the end still have my JAX-RS annotates resource classes? > > > These patches introduce a new "metamodel" concept, and move the current > specification of the RESTAPI based on XML schema and JAX-RS interfaces > to a new "model" built on the new metamodel. > > > What does this mean for you in practical terms? Currently when you want > to introduce or modify one of the data types used by the RESTAPI you > start by modifying the XML schema. Once the patches are merged the XML > schema will never be touched, as it will be automatically generated from > the "model". For example, imagine that you need to add a new "color" > attribute to the "VM" entity. To do so with the new model you will have > to modify the following file, which is the specification of the "Vm" > entity, written as a Java interface: > > > https://gerrit.ovirt.org/#/c/46478/16/backend/manager/modules/restapi/model… > > In that interface you will have to add a line like this: > > String color(); > > Note that this Java interface is just the specification of the entity, > it won't be used at all during runtime. Instead of that the XML schema > will be generated from it, and then Java will be generated from the XML > schema, as we do today (this will change in the future, but not yet). > > Same for the services. If you want to add a new "paint" action to the > "Vm" resource then you won't modify the JAX-RS interfaces, instead of > that you will modify the following file, which is the specification of > the "Vm" service, written as a Java interface: > > > https://gerrit.ovirt.org/#/c/47337/6/backend/manager/modules/restapi/model/… > > In that interface you will need to add a sub-interface representing the > action: > > interface Paint { > } > > The JAX-RS interface will be generated from that. Currently these > sub-interfaces are empty. In the future they will contain the > specifications of the parameters (currently in the rsdl_metadata.yml > file). > > > > These changes will currently affect only the specification of the > RESTAPI, not the implementation, so in in the "Backend*Resource" classes > things won't change yet. > > > Currently I do not really understand where we are going here. Are we > trying to get rid of rdsl? > > So basically two questions: > > 1) What is the final goal? > 2) What speaks agains using Hibernate validator on Daos in combination > with JAX-RS annotated resources (and just removing all interfaces, as > far as I can see we only have one implementation per endpoint) and > creating all schemas and clients through SWAGGER tooling? > > > If you have doubts, please let me know. > > Regards, > Juan Hernandez > > -- > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > 3ºD, 28016 Madrid, Spain > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat > S.L. > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org <mailto:Devel@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/devel > > > Thanks, > > Roman -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

3 16

Requiring Java 8 during runtime
by Juan Hernández 28 Oct '15

28 Oct '15

Hello, As you probably know oVirt Engine 4 will use WildFly 10, and that requires Java 8. The version of WildFly that we currently use is 8.2.1, and it can work with both Java 7 and Java 8. In order to ease the transition I'm about to merge the following patch, that will require Java 8 during runtime: core: Require Java 8 during runtime https://gerrit.ovirt.org/46872 The implication of this for you is that you must make sure that you have Java 8 installed in the machine where you run your the engine. Fedora 22 only supports Java 8, so that isn't a problem. EL6 supports both Java 7 and Java 8, so make sure that you have Java 8 installed: yum -y install java-1.8.0-openjdk-devel If you have objections please speak now, otherwise I will merge the patch tomorrow. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

4 5

rethinking fake-kvm and faqemu
by Martin Polednik 27 Oct '15

27 Oct '15

Hello everyone, I've been reworking the fake_kvm and faqemu VDSM hook to make them somewhat more usable and mostly to allow testing of ppc64le on x86_64 based hosts. TL;DR version: checkout [1], enable fake_kvm and happy ppc64le hacking :) Current fake_kvm isn't really a hook and is contained within 'caps' module. This is wrong for multiple reasons, the most important one being mixing optional with mainline code. Another issue appears when one tries to move the fake_kvm code into a hook: the whole notion of architectures within VDSM is contained within the 'caps' module. The patch series, which git tip is at [1], introduces new cpuinfo module that moves information related to architecture to 'cpuinfo' module of the VDSM library. Intermediate benefit is that current hooks and library code can access the information related to host's cpu. This allows for moving fake_kvm code into a hook that I've called fakearch. Fakearch is, in my opinion, more suitable name - there is barely any KVM faking, but the host 'fakes' selected architecture. Faqemu is, on the other hand, a hook. Unfortunately it wasn't really updated and doesn't allow running VMs under fake architecture. The series therefore try to refactor it to allow cross-arch VMs to be started (the VM actually uses host architecture, but from engine's point of view it's running on the faked arch). So far tested cross-arch runs are * x86_64->x86_64 (faqemu functionality), * x86_64->ppc64le (the most important one), * ppc64le->x86_64, * ppc64le->ppc64le (faqemu for Power). I'm interested in your reviews and comments regarding this effort! [1] https://gerrit.ovirt.org/#/c/46962/ Best regards, mpolednik

3 6

[oVirt 3.6 Localization Question #36] "Network's configurations differ from"
by Yuko Katabami 27 Oct '15

27 Oct '15

Hello all, Here is another question. *File:* ApplicationConstants *Resource ID:* hostOutOfSyncPreviewSentence *String: *Network's configurations differ from *Question:* Is this a part of an error message, followed by another string? Could you please show an example how the final message is going to be shown to users? Kind regards, Yuko Katabami

1 0

[oVirt 3.6 Localization Question #35] "QoS Out average"
by Yuko Katabami 27 Oct '15

27 Oct '15

Hello all, I would like to ask for your help with the following question. *File:* ApplicationConstants *Resource IDs:* outAverageLinkShareOutOfSyncPopUp outAverageRealTimeOutOfSyncPopUp outAverageUpperLimitOutOfSyncPopUp *Strings: * QoS Out average link share QoS Out average real time QoS Out average upper limit *Question: *Could anyone please tell us where these strings appear in the GUI and how they are used? Kind regards, Yuko Katabami

1 0

[ATN] Introduction of RESTAPI metamodel
by Juan Hernández 26 Oct '15

26 Oct '15

Hello, I will soon merge the following patches that introduce a new way to specify the contracts of the RESTAPI: restapi: Introduce metamodel https://gerrit.ovirt.org/45852 restapi: Use metamodel https://gerrit.ovirt.org/46478 restapi: Generate JAX-RS interfaces from model https://gerrit.ovirt.org/47337 These patches introduce a new "metamodel" concept, and move the current specification of the RESTAPI based on XML schema and JAX-RS interfaces to a new "model" built on the new metamodel. What does this mean for you in practical terms? Currently when you want to introduce or modify one of the data types used by the RESTAPI you start by modifying the XML schema. Once the patches are merged the XML schema will never be touched, as it will be automatically generated from the "model". For example, imagine that you need to add a new "color" attribute to the "VM" entity. To do so with the new model you will have to modify the following file, which is the specification of the "Vm" entity, written as a Java interface: https://gerrit.ovirt.org/#/c/46478/16/backend/manager/modules/restapi/model… In that interface you will have to add a line like this: String color(); Note that this Java interface is just the specification of the entity, it won't be used at all during runtime. Instead of that the XML schema will be generated from it, and then Java will be generated from the XML schema, as we do today (this will change in the future, but not yet). Same for the services. If you want to add a new "paint" action to the "Vm" resource then you won't modify the JAX-RS interfaces, instead of that you will modify the following file, which is the specification of the "Vm" service, written as a Java interface: https://gerrit.ovirt.org/#/c/47337/6/backend/manager/modules/restapi/model/… In that interface you will need to add a sub-interface representing the action: interface Paint { } The JAX-RS interface will be generated from that. Currently these sub-interfaces are empty. In the future they will contain the specifications of the parameters (currently in the rsdl_metadata.yml file). These changes will currently affect only the specification of the RESTAPI, not the implementation, so in in the "Backend*Resource" classes things won't change yet. If you have doubts, please let me know. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

2 1

[ANN] oVirt 3.5.5 Final Release is now available
by Sandro Bonazzola 26 Oct '15

26 Oct '15

The oVirt Project is pleased to announce the availability of the oVirt 3.5.5 Final Release, as of October 26th, 2015. This release is available now for 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 6.7, CentOS Linux 6.7 (or similar), Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar) and Fedora 21. This release of oVirt 3.5.5 includes updated packages for: - oVirt Engine - oVirt Hosted Engine HA - oVirt Hosted Engine Setup - VDSM - oVirt Data Warehouse - oVirt Reports - oVirt Engine SDK - oVirt Engine client - QEMU KVM See the release notes [1] for a list of fixed bugs. Please refer to release notes [1] for Installation / Upgrade instructions. a new oVirt Live ISO is already 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.5.5_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.5/iso/ovirt-live/ [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 0

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 22 Oct '15

22 Oct '15

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6 for testing, as of October 22nd, 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), Fedora 21 and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.0 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. New oVirt Node ISO and oVirt Live ISO will be available soon as well[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://plain.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 0

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 22 Oct '15

22 Oct '15

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6 for testing, as of October 22nd, 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), Fedora 21 and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.0 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. New oVirt Node ISO and oVirt Live ISO will be available soon as well[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://plain.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 0

Hello and a question about VM Custom Property
by zhukaijie 21 Oct '15

21 Oct '15

Hello, recently I have read something about VM custom properties. There is a question I'm thinking about. If a VM A has a custom property named PARAM. I set VM A'S PARAM a value. Then before I start the VM from web, where is the PARAM value stores? Does it store in Postgresql? Thank you.

2 1

Hello and a question about VM Custom Property
by zhukaijie 21 Oct '15

21 Oct '15

Hello, recently I have read something about VM custom properties. There is a question I'm thinking about. If a VM A has a custom property named PARAM. I set VM A'S PARAM a value. Then before I start the VM from web, where is the PARAM value stores? Does it store in Postgresql? Thank you.

1 0

Re: [ovirt-devel] Question about the ovirt-engine-sdk-java
by Michael Pasternak 20 Oct '15

20 Oct '15

------=_Part_291056_1850182726.1445347932554 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Salifou, OK, i see now, then you have two options: a) To extend the sdk: 1. extend java-sdk by allowing to inject custom headers in every request=C2= =A0(not trivial as all ovirt SDKs are auto-generated,but if its common case= , you may find yourself getting help from community/maintainers) 2. fork java-sdk customizing it for your needs I'd recommend the former as fork will leave you with no support/maintenance= from community plus you'll haveto implement new=C2=A0features by your own = (what will become a moving target very quickly)=20 b) Proxying the sdk You can implement dynamic proxy wrapping SDK's HttpProxy.java#execute and i= ntercept the context from there,but you've to stay tuned as backward compat= ibility is for interface and not for SDK internals,so "potentially" you can= find your code broken in one of the following upgrades hope it helps.=C2=A0 On Monday, October 19, 2015 6:05 PM, Salifou Sidi M. Malick <ssidimah@= redhat.com> wrote: =20 Hi Micheal, Thanks for replying. Unfortunately the headers are dynamic ... Here is the story: We implemented a custom RHEV-M AAA module for a client in order to allow their custom portal to make RHEV-M API=20 calls.=20 The custom AAA module requires extra dynamic data in the HTTP=20 request (as request headers for now but request parameters=20 should be fine too).=20 Their is no problem if they go with the REST API, I am just=20 trying to anticipate/identify potential integration problem ... It seems like they will have to use the REST API or modify the=20 java sdk ...=C2=A0=20 Thanks a lot, Salifou ----- Original Message ----- From: "Michael Pasternak" <mishka8520(a)yahoo.com> To: "Salifou Sidi M. Malick" <ssidimah(a)redhat.com> Cc: "Users" <users(a)ovirt.org> Sent: Sunday, October 18, 2015 5:45:05 AM Subject: Re: Question about the ovirt-engine-sdk-java Hi=C2=A0Salifou, Actually java sdk is=C2=A0intentionally=C2=A0hiding transport level interna= ls so developers could stay in java domain,if your headers are static, easi= est way would be using reverse proxy in a middle to intercept requests,=C2= =A0 can you tell me why do you need this? =20 =C2=A0 =C2=A0 On Friday, October 16, 2015 1:14 AM, Salifou Sidi M. Malick <= ssidimah(a)redhat.com> wrote: =C2=A0=20 Hi Micheal, I have a question about the ovirt-engine-sdk-java. Is there a way to add custom request headers to each RHEVM API call? Here is an example of a request that I would like to do: $ curl -v -k \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -H "ID: user1(a)ad.xyz.com" \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -H "PASSWORD: Pwssd" \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -H "TARGET: kobe" \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://vm0.smalick.com/api/hosts I would like to add ID, PASSWORD and TARGET as HTTP request header.=20 Thanks, Salifou =20 ------=_Part_291056_1850182726.1445347932554 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <html><head></head><body><div style=3D"color:#000; background-color:#fff; f= ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve= tica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id=3D"yiv487097= 0104"><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_1_1445338067930_25413">= <br><br></div><div class=3D"yiv4870970104yqt0049005238" id=3D"yiv4870970104= yqtfd33472"><div id=3D"yui_3_16_0_1_1445338067930_25382"><div style=3D"colo= r:#000;background-color:#fff;font-family:HelveticaNeue-Light, Helvetica Neu= e Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-s= ize:13px;" id=3D"yui_3_16_0_1_1445338067930_25381"><div id=3D"yiv4870970104= yui_3_16_0_1_1445338067930_23478"><span style=3D"font-family:'Helvetica Neu= e', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif;">Hi Salifou,= </span><br clear=3D"none"></div><div class=3D"yiv4870970104qtdSeparateBR" i= d=3D"yui_3_16_0_1_1445338067930_25383"><br clear=3D"none"><br clear=3D"none= "></div> </div></div></div></div><div class=3D".yiv4870970104yahoo_quoted" = id=3D"yui_3_16_0_1_1445338067930_25398"><div id=3D"yiv4870970104yui_3_16_0_= 1_1445338067930_23388" style=3D"font-family:HelveticaNeue-Light, Helvetica = Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fon= t-size:13px;"><div id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23387" sty= le=3D"font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida G= rande, sans-serif;font-size:16px;"><div class=3D"yiv4870970104y_msg_contain= er" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23484"><div id=3D"yiv4870= 970104"><div id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23483"><div id= =3D"yiv4870970104yui_3_16_0_1_1445338067930_23482" style=3D"color:#000;back= ground-color:#fff;font-family:HelveticaNeue-Light, Helvetica Neue Light, He= lvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;">= <div id=3D"yiv4870970104"><div id=3D"yiv4870970104yui_3_16_0_1_144533806793= 0_7276"><div id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7275" style=3D"c= olor:#000;background-color:#fff;font-family:HelveticaNeue-Light, Helvetica = Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fon= t-size:13px;"><div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_144533806793= 0_4283"><span></span></div><div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1= _1445338067930_4283"><span style=3D"font-family: 'Helvetica Neue', 'Segoe U= I', Helvetica, Arial, 'Lucida Grande', sans-serif;" id=3D"yui_3_16_0_1_1445= 338067930_25412">OK, i see now, then you have two options:</span><br></div>= <div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span = class=3D"yiv4870970104" style=3D"font-family:'Helvetica Neue', 'Segoe UI', = Helvetica, Arial, 'Lucida Grande', sans-serif;"><br clear=3D"none"></span><= /div><div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><= span class=3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_= 7286" style=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, = 'Lucida Grande', sans-serif;">a) To extend the sdk:</span></div><div dir=3D= "ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yi= v4870970104" style=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, = Arial, 'Lucida Grande', sans-serif;"><br clear=3D"none"></span></div><div d= ir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class= =3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4800" styl= e=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Gr= ande', sans-serif;">1. extend java-sdk by allowing to inject custom headers= in every request</span><span class=3D"yiv4870970104" style=3D"font-family:= 'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif= ;"> </span><span class=3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0= _1_1445338067930_8082" style=3D"font-family:'Helvetica Neue', 'Segoe UI', H= elvetica, Arial, 'Lucida Grande', sans-serif;">(not trivial as all ovirt SD= Ks are auto-generated</span><span style=3D"font-family:'Helvetica Neue', 'S= egoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif;">,</span></div><di= v dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span cla= ss=3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_9090" st= yle=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida = Grande', sans-serif;">but if its common case, you may find yourself getting= help from community/maintainers)</span></div><div dir=3D"ltr" id=3D"yiv487= 0970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yiv4870970104" style= =3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Gra= nde', sans-serif;"><br clear=3D"none"></span></div><div dir=3D"ltr" id=3D"y= iv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yiv4870970104" = id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4801" style=3D"font-family:'H= elvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif;"= >2. fork java-sdk customizing it for your needs</span></div><div dir=3D"ltr= " id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yiv487= 0970104" style=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Aria= l, 'Lucida Grande', sans-serif;"><br clear=3D"none"></span></div><div dir= =3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D= "yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4974" style= =3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Gra= nde', sans-serif;">I'd recommend the former as fork will leave you with no = support/maintenance from community plus you'll have</span></div><div dir=3D= "ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yi= v4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7285" style=3D"f= ont-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande',= sans-serif;">to implement new </span><span id=3D"yiv4870970104yui_3_1= 6_0_1_1445338067930_5162" style=3D"font-family:'Helvetica Neue', 'Segoe UI'= , Helvetica, Arial, 'Lucida Grande', sans-serif;">features by your own (wha= t will become a moving target very quickly)</span></div> <br clear=3D"none= "><div class=3D"yiv4870970104qtdSeparateBR" dir=3D"ltr" id=3D"yiv4870970104= yui_3_16_0_1_1445338067930_7274">b) Proxying the sdk</div><div class=3D"yiv= 4870970104qtdSeparateBR" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_144533= 8067930_7274"><br clear=3D"none"></div><div class=3D"yiv4870970104qtdSepara= teBR" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7274">You c= an implement dynamic proxy wrapping SDK's HttpProxy.java#execute and interc= ept the context from there,</div><div class=3D"yiv4870970104qtdSeparateBR" = dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7274">but you've = to stay tuned as backward compatibility is for interface and not for SDK in= ternals,</div><div class=3D"yiv4870970104qtdSeparateBR" dir=3D"ltr" id=3D"y= iv4870970104yui_3_16_0_1_1445338067930_7274">so "potentially" you can find = your code broken in one of the following upgrades</div><div class=3D"yiv487= 0970104qtdSeparateBR" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_144533806= 7930_7274"><br clear=3D"none"></div><div class=3D"yiv4870970104qtdSeparateB= R" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7274">hope it = helps. <br clear=3D"none"><br clear=3D"none"></div><div class=3D"yiv48= 70970104yqt0562777282" id=3D"yiv4870970104yqt81591"></div></div></div></div= ><div class=3D"yiv4870970104yqt7829638567" id=3D"yiv4870970104yqt81845"><di= v id=3D"yiv4870970104yui_3_16_0_1_1445338067930_8533"> <div id=3D"yiv487097= 0104yui_3_16_0_1_1445338067930_8532" style=3D"font-family:HelveticaNeue-Lig= ht, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, = sans-serif;font-size:13px;"> <div id=3D"yiv4870970104yui_3_16_0_1_144533806= 7930_8531" style=3D"font-family:HelveticaNeue, Helvetica Neue, Helvetica, A= rial, Lucida Grande, sans-serif;font-size:16px;"> <div dir=3D"ltr" id=3D"yi= v4870970104yui_3_16_0_1_1445338067930_8554"> <font id=3D"yiv4870970104yui_3= _16_0_1_1445338067930_8559" size=3D"2" face=3D"Arial"> On Monday, October 1= 9, 2015 6:05 PM, Salifou Sidi M. Malick <ssidimah(a)redhat.com> wrote:<= br clear=3D"none"> </font> </div> <br clear=3D"none"><br clear=3D"none"> <= div class=3D"yiv4870970104y_msg_container" id=3D"yiv4870970104yui_3_16_0_1_= 1445338067930_8712">Hi Micheal,<br clear=3D"none"><br clear=3D"none">Thanks= for replying. Unfortunately the headers are dynamic ...<br clear=3D"none">= <br clear=3D"none">Here is the story:<br clear=3D"none"><br clear=3D"none">= We implemented a custom RHEV-M AAA module for a client<br clear=3D"none">in= order to allow their custom portal to make RHEV-M API <br clear=3D"none">c= alls. <br clear=3D"none"><br clear=3D"none">The custom AAA module requires = extra dynamic data in the HTTP <br clear=3D"none">request (as request heade= rs for now but request parameters <br clear=3D"none">should be fine too). <= br clear=3D"none"><br clear=3D"none">Their is no problem if they go with th= e REST API, I am just <br clear=3D"none">trying to anticipate/identify pote= ntial integration problem ...<br clear=3D"none"><br clear=3D"none">It seems= like they will have to use the REST API or modify the <br clear=3D"none">j= ava sdk ...  <br clear=3D"none"><br clear=3D"none">Thanks a lot,<br cl= ear=3D"none">Salifou<br clear=3D"none"><br clear=3D"none"><div class=3D"yiv= 4870970104yqt8023103542" id=3D"yiv4870970104yqtfd83808"><br clear=3D"none">= ----- Original Message -----<br clear=3D"none">From: "Michael Pasternak" &l= t;<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:mishka8520@yahoo.com= " target=3D"_blank" href=3D"mailto:mishka8520@yahoo.com">mishka8520(a)yahoo.c= om</a>><br clear=3D"none">To: "Salifou Sidi M. Malick" <<a rel=3D"nof= ollow" shape=3D"rect" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23606" = ymailto=3D"mailto:ssidimah@redhat.com" target=3D"_blank" href=3D"mailto:ssi= dimah(a)redhat.com">ssidimah(a)redhat.com</a>><br clear=3D"none">Cc: "Users"= <<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:users@ovirt.org" = target=3D"_blank" href=3D"mailto:users@ovirt.org">users(a)ovirt.org</a>><b= r clear=3D"none">Sent: Sunday, October 18, 2015 5:45:05 AM<br clear=3D"none= ">Subject: Re: Question about the ovirt-engine-sdk-java<br clear=3D"none"><= br clear=3D"none">Hi Salifou,<br clear=3D"none">Actually java sdk is&n= bsp;intentionally hiding transport level internals so developers could= stay in java domain,if your headers are static, easiest way would be using= reverse proxy in a middle to intercept requests, <br clear=3D"none"><= br clear=3D"none">can you tell me why do you need this?<br clear=3D"none"> = <br clear=3D"none"><br clear=3D"none"><br clear=3D"none">    On = Friday, October 16, 2015 1:14 AM, Salifou Sidi M. Malick <<a rel=3D"nofo= llow" shape=3D"rect" ymailto=3D"mailto:ssidimah@redhat.com" target=3D"_blan= k" href=3D"mailto:ssidimah@redhat.com">ssidimah(a)redhat.com</a>> wrote:<b= r clear=3D"none">  <br clear=3D"none"><br clear=3D"none"> Hi Micheal,= <br clear=3D"none"><br clear=3D"none">I have a question about the ovirt-eng= ine-sdk-java.<br clear=3D"none"><br clear=3D"none">Is there a way to add cu= stom request headers to each RHEVM API call?<br clear=3D"none"><br clear=3D= "none">Here is an example of a request that I would like to do:<br clear=3D= "none"><br clear=3D"none">$ curl -v -k \<br clear=3D"none">    &n= bsp;     -H "ID: <a rel=3D"nofollow" shape=3D"rect" ymailto=3D"ma= ilto:user1@ad.xyz.com" target=3D"_blank" href=3D"mailto:user1@ad.xyz.com">u= ser1(a)ad.xyz.com</a>" \<br clear=3D"none">         = -H "PASSWORD: Pwssd" \<br clear=3D"none">        &nbsp= ; -H "TARGET: kobe" \<br clear=3D"none">          = <a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"https://vm0.sm= alick.com/api/hosts">https://vm0.smalick.com/api/hosts</a><br clear=3D"none= "><br clear=3D"none"><br clear=3D"none">I would like to add ID, PASSWORD an= d TARGET as HTTP request header. <br clear=3D"none"><br clear=3D"none">Than= ks,<br clear=3D"none">Salifou<br clear=3D"none"><br clear=3D"none"><br clea= r=3D"none"></div><br clear=3D"none"><br clear=3D"none"></div> </div> </div= > </div></div></div></div></div><br clear=3D"none"><br clear=3D"none"></di= v> </div> </div> </div></div></body></html> ------=_Part_291056_1850182726.1445347932554--

1 0

Termin gestrichen: oVirt Node weekly meeting - Mo 19. Okt. 2015 16:00 - 16:30 (fdeutsch@redhat.com)
by fdeutsch＠redhat.com 19 Oct '15

19 Oct '15

Dieser Termin wurde gestrichen und aus Ihrem Kalender entfernt. Titel: oVirt Node weekly meeting Hey, this is an invitation to the weekly oVirt Node devel meetings. Anyone interested or related to Node development is welcome. Wann: Mo 19. Okt. 2015 16:00 - 16:30 Berlin Wo: irc://irc.oftc.net#ovirt Kalender: fdeutsch(a)redhat.com Wer * Fabian Deutsch - Organisator * tlitovsk(a)redhat.com * devel(a)ovirt.org * wdaniel(a)redhat.com Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter devel(a)ovirt.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie können auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen für Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empfänger Ihre Antwort auf die Einladung ändern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding

1 0

[QE][ACTION REQUIRED] oVirt 3.6.0 status
by Sandro Bonazzola 15 Oct '15

15 Oct '15

Hi, We planned to start composing next milestone of oVirt 3.6.0 on *2015-10-12 08:00 UTC* from 3.6 branches. There are still 234 bugs [1] targeted to 3.6.0. Whiteboard RC GA Total docs 5 0 15 dwh 1 0 1 external 0 1 1 gluster 40 0 40 i18n 2 0 2 infra 23 6 29 integration 0 1 1 network 27 1 28 node 4 0 4 reports 1 0 1 sla 36 2 38 storage 49 9 58 ux 10 0 10 virt 5 1 6 Total 213 21 234 Maintainers must scrub them and push non critical bugs to ZStream releases. There is 1 acknowledged blocker for 3.6.0: Bug 1196640 - [Monitoring] Network utilisation is not shown for the VM And there are 21 bugs suggested as blockers for 3.6.0: Bug ID Status Whiteboard Summary 1259441 NEW gluster Can't create new Gluster storage domain - Permission denied 1261822 NEW integration BUILD WGT 3.6 1259468 NEW network Setupnetworks fails from time to time with error 'Failed to bring interface up' 1262026 NEW network Host booted up after upgrading it 3.5.4->3.6 with rhevm bridge with DEFROUTE=no. 1262051 NEW network Host move from 'up' to 'connecting' and back to 'up' from time to time 1243811 POST sla vm with dedicate host fails to run on other host, if dedicated host is in maintenance 1262293 POST sla Creating a VM with Foreman fails if cluster has more than one CPU profile 1239297 ASSIGNED storage Logical disk name is not showing up 1118349 NEW storage [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError 1250540 NEW storage Re-attaching fresh export domain fails - hsm::2543::Storage.HSM::(disconnectStorageServer) Could not disconnect from storageServer 1253790 NEW storage [BLOCKED] consume fix for "iscsi_session recovery_tmo revert back to default when a path becomes active" 1253975 NEW storage [vdsm] extendVolumeSize task is not cleared in case of a live merge failure for a volume that was extended 1151838 NEW storage [vdsm] Scan alignment fails with a VirtAlignError 1238239 NEW storage Deployment of hosted engine failed on ISCSI storage with 'Error block device action' 1257240 NEW storage Template's disk format is wrong 1261953 NEW storage [vdsm] Host fails to connect to storage pool 'MiscBlockReadException: Internal block device read failure' 1261980 NEW storage failed LSM due to connection lost with qemu process 1138144 NEW storage [BLOCKED]Failed to autorecover storage domain after unblocking connection with host 1253756 POST storage [BLOCKED] libvirt reports physical=0 for COW2 volumes on block storage 1251008 POST storage [BLOCKED] libvirt reports physical=0 for COW2 volumes on block storage 1258901 POST storage [UX] Toggling wad property while vm is up shouldn't be greyed out There are 17 bugs marked as regressions to be solved in 3.6.0 [2] Given current bugs status, release criteria are not met [3] so we need to review bug status for planning the RC. Action items: - Developers: check suggested blockers, fix acknowledged blockers, regressions and re-target remaining blockers. - Please check Jenkins status for 3.6 jobs and sync with relevant maintainers if there are issues. - Please fill release notes, the page has been created here [4] - Please test oVirt 3.6 nightly snapshot and check for regressions from 3.5 [1] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir… status%3Anew%2Cassigned%2Cpost [2] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir… [3] http://www.ovirt.org/OVirt_3.6_Release_Management#Candidate_Release_Criteria [4] http://www.ovirt.org/OVirt_3.6_Release_Notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 4