- Devel - oVirt List Archives

ovirt engine java sdk 4.0
by 转圈圈 01 Aug '16

01 Aug '16

This is a multi-part message in MIME format. ------=_NextPart_579EE321_0A343D60_507F0E1B Content-Type: text/plain; charset="gb18030" Content-Transfer-Encoding: base64 SSB3b3VsZCBsaWtlIHRvIGNhbGwgdGhlIGVuZ2luZTQuMCBBUEkgcXVlcnkgaG9zdHOjrEJ5 IGhvc3QgbmFtZSBmdXp6eSBxdWVyeaOsSG93IHRvIHdyaXRlIHN5bnRheKO/ ------=_NextPart_579EE321_0A343D60_507F0E1B Content-Type: text/html; charset="gb18030" Content-Transfer-Encoding: base64 PGZvbnQgY29sb3I9IiM1NTU1NTUiIGZhY2U9IlNlZ29lIFVJLCBUYWhvbWEsIEhlbHZldGlj YSwgc2Fucy1zZXJpZiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTNweDsgbGluZS1oZWln aHQ6IG5vcm1hbDsiPkkgd291bGQgbGlrZSB0byBjYWxsIHRoZSBlbmdpbmU0LjAgQVBJIHF1 ZXJ5IGhvc3Rzo6w8L3NwYW4+PC9mb250PjxzcGFuIHNyY2luZm89Ijg6OSIgZHN0aW5mbz0i MTk6MjMiIHBhcmFncmFwaG5hbWU9InBhcmFncmFwaDAiIGlzc291cmNlPSJmYWxzZSIgaWQ9 Im91SGlnaGxpZ2h0X184XzlUTzE5XzIzIiBjbGFzcz0iIiBzdHlsZT0ibGluZS1oZWlnaHQ6 IG5vcm1hbDsgZm9udC1zaXplOiAxM3B4OyBmb250LWZhbWlseTogJ1NlZ29lIFVJJywgVGFo b21hLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoODUsIDg1LCA4NSk7Ij48 L3NwYW4+PHNwYW4gc3JjaW5mbz0iMDoxIiBkc3RpbmZvPSIwOjEiIHBhcmFncmFwaG5hbWU9 InBhcmFncmFwaDAiIGlzc291cmNlPSJmYWxzZSIgaWQ9Im91SGlnaGxpZ2h0X18wXzFUTzBf MSIgY2xhc3M9IiIgc3R5bGU9ImNvbG9yOiByZ2IoODUsIDg1LCA4NSk7IGZvbnQtZmFtaWx5 OiAnU2Vnb2UgVUknLCBUYWhvbWEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgZm9udC1zaXpl OiAxM3B4OyBsaW5lLWhlaWdodDogbm9ybWFsOyI+Qnk8L3NwYW4+PHNwYW4gaWQ9Im5vSGln aGxpZ2h0XzAuNTU3MzY0NTg0ODc4MDg3IiBzdHlsZT0iY29sb3I6IHJnYig4NSwgODUsIDg1 KTsgZm9udC1mYW1pbHk6ICdTZWdvZSBVSScsIFRhaG9tYSwgSGVsdmV0aWNhLCBzYW5zLXNl cmlmOyBmb250LXNpemU6IDEzcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij4mbmJzcDs8L3Nw YW4+PHNwYW4gc3JjaW5mbz0iMjozIiBkc3RpbmZvPSIzOjYiIHBhcmFncmFwaG5hbWU9InBh cmFncmFwaDAiIGlzc291cmNlPSJmYWxzZSIgaWQ9Im91SGlnaGxpZ2h0X18yXzNUTzNfNiIg Y2xhc3M9IiIgc3R5bGU9ImNvbG9yOiByZ2IoODUsIDg1LCA4NSk7IGZvbnQtZmFtaWx5OiAn U2Vnb2UgVUknLCBUYWhvbWEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAx M3B4OyBsaW5lLWhlaWdodDogbm9ybWFsOyI+aG9zdDwvc3Bhbj48c3BhbiBpZD0ibm9IaWdo bGlnaHRfMC4zMDMyMDMzNzYwMTAwNjAzIiBzdHlsZT0iY29sb3I6IHJnYig4NSwgODUsIDg1 KTsgZm9udC1mYW1pbHk6ICdTZWdvZSBVSScsIFRhaG9tYSwgSGVsdmV0aWNhLCBzYW5zLXNl cmlmOyBmb250LXNpemU6IDEzcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij4mbmJzcDs8L3Nw YW4+PHNwYW4gc3JjaW5mbz0iNDo1IiBkc3RpbmZvPSI4OjExIiBwYXJhZ3JhcGhuYW1lPSJw YXJhZ3JhcGgwIiBpc3NvdXJjZT0iZmFsc2UiIGlkPSJvdUhpZ2hsaWdodF9fNF81VE84XzEx IiBjbGFzcz0iIiBzdHlsZT0iY29sb3I6IHJnYig4NSwgODUsIDg1KTsgZm9udC1mYW1pbHk6 ICdTZWdvZSBVSScsIFRhaG9tYSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBmb250LXNpemU6 IDEzcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij5uYW1lPC9zcGFuPjxzcGFuIGlkPSJub0hp Z2hsaWdodF8wLjcwNzU5NzAyMzU3NDYzNTQiIHN0eWxlPSJjb2xvcjogcmdiKDg1LCA4NSwg ODUpOyBmb250LWZhbWlseTogJ1NlZ29lIFVJJywgVGFob21hLCBIZWx2ZXRpY2EsIHNhbnMt c2VyaWY7IGZvbnQtc2l6ZTogMTNweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsiPiZuYnNwOzwv c3Bhbj48c3BhbiBzcmNpbmZvPSI2OjciIGRzdGluZm89IjEzOjE3IiBwYXJhZ3JhcGhuYW1l PSJwYXJhZ3JhcGgwIiBpc3NvdXJjZT0iZmFsc2UiIGlkPSJvdUhpZ2hsaWdodF9fNl83VE8x M18xNyIgY2xhc3M9IiIgc3R5bGU9ImNvbG9yOiByZ2IoODUsIDg1LCA4NSk7IGZvbnQtZmFt aWx5OiAnU2Vnb2UgVUknLCBUYWhvbWEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgZm9udC1z aXplOiAxM3B4OyBsaW5lLWhlaWdodDogbm9ybWFsOyI+ZnV6enk8L3NwYW4+PHNwYW4gaWQ9 Im5vSGlnaGxpZ2h0XzAuMDM2MTQ1NzcyMDg2NDU2NDIiIHN0eWxlPSJjb2xvcjogcmdiKDg1 LCA4NSwgODUpOyBmb250LWZhbWlseTogJ1NlZ29lIFVJJywgVGFob21hLCBIZWx2ZXRpY2Es IHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTNweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsiPiZu YnNwOzwvc3Bhbj48c3BhbiBzcmNpbmZvPSI4OjkiIGRzdGluZm89IjE5OjIzIiBwYXJhZ3Jh cGhuYW1lPSJwYXJhZ3JhcGgwIiBpc3NvdXJjZT0iZmFsc2UiIGlkPSJvdUhpZ2hsaWdodF9f OF85VE8xOV8yMyIgY2xhc3M9IiIgc3R5bGU9ImNvbG9yOiByZ2IoODUsIDg1LCA4NSk7IGZv bnQtZmFtaWx5OiAnU2Vnb2UgVUknLCBUYWhvbWEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsg Zm9udC1zaXplOiAxM3B4OyBsaW5lLWhlaWdodDogbm9ybWFsOyI+cXVlcnmjrDwvc3Bhbj48 c3BhbiBzcmNpbmZvPSIyOjMiIGRzdGluZm89IjA6MiIgcGFyYWdyYXBobmFtZT0icGFyYWdy YXBoMCIgaXNzb3VyY2U9ImZhbHNlIiBpZD0ib3VIaWdobGlnaHRfXzJfM1RPMF8yIiBjbGFz cz0iIiBzdHlsZT0iY29sb3I6IHJnYig4NSwgODUsIDg1KTsgZm9udC1mYW1pbHk6ICdTZWdv ZSBVSScsIFRhaG9tYSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDEzcHg7 IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij5Ib3c8L3NwYW4+PHNwYW4gaWQ9Im5vSGlnaGxpZ2h0 XzAuMTQ3MTQ0ODA4NjY2NzgwNiIgc3R5bGU9ImNvbG9yOiByZ2IoODUsIDg1LCA4NSk7IGZv bnQtZmFtaWx5OiAnU2Vnb2UgVUknLCBUYWhvbWEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsg Zm9udC1zaXplOiAxM3B4OyBsaW5lLWhlaWdodDogbm9ybWFsOyI+Jm5ic3A7dG8mbmJzcDs8 L3NwYW4+PHNwYW4gc3JjaW5mbz0iNDo0IiBkc3RpbmZvPSI3OjExIiBwYXJhZ3JhcGhuYW1l PSJwYXJhZ3JhcGgwIiBpc3NvdXJjZT0iZmFsc2UiIGlkPSJvdUhpZ2hsaWdodF9fNF80VE83 XzExIiBjbGFzcz0iIiBzdHlsZT0iY29sb3I6IHJnYig4NSwgODUsIDg1KTsgZm9udC1mYW1p bHk6ICdTZWdvZSBVSScsIFRhaG9tYSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBmb250LXNp emU6IDEzcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij53cml0ZTwvc3Bhbj48c3BhbiBpZD0i bm9IaWdobGlnaHRfMC4xMzA3Mjk0OTMyMTk0MDU0IiBzdHlsZT0iY29sb3I6IHJnYig4NSwg ODUsIDg1KTsgZm9udC1mYW1pbHk6ICdTZWdvZSBVSScsIFRhaG9tYSwgSGVsdmV0aWNhLCBz YW5zLXNlcmlmOyBmb250LXNpemU6IDEzcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij4mbmJz cDs8L3NwYW4+PHNwYW4gc3JjaW5mbz0iMDoxIiBkc3RpbmZvPSIxMzoxOCIgcGFyYWdyYXBo bmFtZT0icGFyYWdyYXBoMCIgaXNzb3VyY2U9ImZhbHNlIiBpZD0ib3VIaWdobGlnaHRfXzBf MVRPMTNfMTgiIGNsYXNzPSIiIHN0eWxlPSJjb2xvcjogcmdiKDg1LCA4NSwgODUpOyBmb250 LWZhbWlseTogJ1NlZ29lIFVJJywgVGFob21hLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IGZv bnQtc2l6ZTogMTNweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsiPnN5bnRheKO/PC9zcGFuPg== ------=_NextPart_579EE321_0A343D60_507F0E1B-- z

1 0

execCmd() and storing stdout and stderr in log file
by Tomáš Golembiovský 29 Jul '16

29 Jul '16

Hi, I had a need recently to run a command with execCmd() and store it's output and error to a log file, while still receiving it in the calling code. Redirecting the error to output stream to have all in one stream is also useful feature. All this can be done in the calling code: a) On the shell level, by modyfing the command. This can be intentionally dangerous because things like quoting of arguments has to be considered and also could cause problems when wrappers (sudo, nice, ...) are used. b) By handling the writing to files in a code. This would add unnecessary code duplication in a long run. (I don't think I'm the only one who can see a potential in this.) Also for asynchronous process runs, when storing both stderr & stdout in one file, it requires polling and some stream magic. It would be better to have this done right and only once so it can be properly tested. That's why I think having it present in execCmd() ready for everyone's use is the best solution. Unfortunately it seems that the code is a) essential on many places in vdsm and b) not properly covered by tests. Which makes it hard to touch. Also apparently some refactoring is either planned or already underway. What is the situation about refactoring that code area? Anyone working on it? Do we have an estimation of time-frame for it? Any suggestions/ideas? Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

5 23

Is there some guideline how to replace Linux Bridge with ovs on vdsm?
by lifuqiong 27 Jul '16

27 Jul '16

This is a multipart message in MIME format. ------=_NextPart_000_012C_01D1E818.185185B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I want to using ovs replace with Linux bridge, Is there some guideline or advice? If I want to use dpdk vhost-user port, how can I do that? Thank you Mark ------=_NextPart_000_012C_01D1E818.185185B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-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=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 = (filtered medium)"><style></style></head><body lang=3DZH-CN link=3Dblue = vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div = class=3DWordSection1>Hi, = <o:p></o:p>         I want to = using ovs replace with Linux bridge, Is there some guideline or advice? = If I want to use dpdk vhost-user port, how can I do = that?<o:p></o:p><o:p> </o:p>Thank you<o:p></o:p>Mark<o:p></o:p></div></body></html> ------=_NextPart_000_012C_01D1E818.185185B0--

2 1

[ANN] oVirt 4.0.2 Seconf Release Candidate is now available
by Sandro Bonazzola 27 Jul '16

27 Jul '16

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 4.0.2 for testing, as of July 27st, 2016. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the first release candidate of the second in a series of stabilization updates to the 4.0 series. 4.0.2 brings 12 enhancements and nearly 100 bugfixes, including 43 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is available. [4] * A new oVirt Next Generation Node is available [4]. * A new oVirt Engine Appliance is already available. * Mirrors[5] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.2 release highlights: http://www.ovirt.org/release/4.0.2/ * 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/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.0.2/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] 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 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Seeing a memory issue in 4.0.1.1-1.el7.centos
by Lynn Dixon 27 Jul '16

27 Jul '16

Hello all. I hope I am sending this to the proper mailing list. If not, please let me know. I just installed the latest oVirt engine onto a RHEL7.2 machine last night. I haven't built any VM's yet, but noticed that 27gig of memory was being consumed in the Dashboard. I did a quick check on top and noticed this: http://i.imgur.com/j9LB4q9.jpg The two java processes seem to be using a heavy amount of ram and reservations. How shall I troubleshoot this to find out whats going on? *Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Sr. Cloud Consultant* | Cloud Management Practice Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>

3 2

[VDSM] Using INFO log by default
by Nir Soffer 27 Jul '16

27 Jul '16

Hi all, We are using now INFO log level by default. This has two important effects: - We are not generating huge logs filling your disk - Some flows may not be logged properly now Please check that your code is logged properly - basically any state change in the system must be logged using log.info(). To increase log level temporarily, use: vdsClient -s 0 setLogLevel LEVEL [logger] logger is one of vdsm logger, see /etc/vdsm/logger.conf for the names. Without logger, the root logger is modified. To change logging level permanently, edit /etc/vdsm/logger.conf. Nir

2 1

Reply: [ovirt-users] Some question about vdsm rpc
by lifuqiong 27 Jul '16

27 Jul '16

Thank you very much for your helpful reply . The error of my question 4 is solved after I stopping debug vdsm code, just using print log info instead. On Tue, Jul 26, 2016 at 12:46 PM, lifuqiong <lifuqiong(a)cncloudsec.com> wrote: > 1. We know that xmlrpc and jsonrpc are enabled default in vdsm, vdsm > supply these two service in one port or two? What’s the port number > and how we can change it? > We use single port for both protocols. There is a code which peeks the data stream and decides which part of the code should handle the connection. In config.py you can find 'management_port' option which defines which port will be used. > > > 2. How can we know a vdsm host can supply an xmlrpc service or a > jsonrpc service? > In config.py we have 'xmlrpc_enable' and 'jsonrpc_enable' which determine protocols available during runtime. With the latest vdsm both are enabled but keep in mind that xmlrpc is deprecated and will be removed soon. > > > 3. I found that while ovirt engine installing a vdsm host, engine will > check whether we are connecting to vdsm which supports xmlrpc only, > engine send a ‘Host.ping’ jsonrpc request, why the code will enter > into bindingxmlrpc.py? > > Did both jsonrpc and xmlrpc will call bindingxmlrpc.py? > During host installation we attempt to connect to a host using jsonrpc first and if it fails we we attempt to use xmlrpc. Older vdsms provide only xmlrpc so this behavior is for backward compatibility. There are two binding modules bindingjsonrpc.py and bindingxmlrpc.py. Common module for both bindings is API.py > > > 4. Then, I just get an json return with code = 0 or code = 99. What > does these error code mean ? I can’t find detail in rpcjson > Specification(http://www.jsonrpc.org/specification) > There is a time when vdsm is not able to handle requests due to recovery logic which may take several seconds during this time we return code 99. Once the recovery is done vdsm returns correct codes like 0. Recovery occurs only during start of vdsm. > > > 5. When installing vdsm, I got an “Host server117 installation failed. > Host is not reachable” error. Debugging code as follows: > > Bindingxmlrpc.py > > line637 def ping(self): > > line638 # print 'os.getuid()',os.getuid() = 0 > > line639 # print 'os.getegit()',os.getegid() =0 > > line640 api = API.Global() > > line641 return api.ping() > Can you share the logs with above failure? > > > the api.ping() just open an file and update the file updating time, > why these will throw an error code 0 or 99? And I see the ping() > function created file /var/run/vdsm/client.log already exists in os, > ping verb was reused to detect whether vdsm is able to use jsonrpc. This verb originally is used to make sure that any network reconfiguration did not break connection to the engine. During the process of reconfiguration engine call ping and vdsm based on file update time can restore old network configuration in case of failure. > the only difference is the file is owned by root:root , not the vdsm:kvm? > Why? > There are 2 vdsm processes running with different user permissions. > > > Thank you. > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >

1 0

Some question about vdsm rpc
by lifuqiong 27 Jul '16

27 Jul '16

This is a multipart message in MIME format. ------=_NextPart_000_00F7_01D1E76E.0E1E4A60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 1. We know that xmlrpc and jsonrpc are enabled default in vdsm, vdsm supply these two service in one port or two? What's the port number and how we can change it? 2. How can we know a vdsm host can supply an xmlrpc service or a jsonrpc service? 3. I found that while ovirt engine installing a vdsm host, engine will check whether we are connecting to vdsm which supports xmlrpc only, engine send a 'Host.ping' jsonrpc request, why the code will enter into bindingxmlrpc.py? Did both jsonrpc and xmlrpc will call bindingxmlrpc.py? 4. Then, I just get an json return with code = 0 or code = 99. What does these error code mean ? I can't find detail in rpcjson Specification(http://www.jsonrpc.org/specification) 5. When installing vdsm, I got an "Host server117 installation failed. Host is not reachable" error. Debugging code as follows: Bindingxmlrpc.py line637 def ping(self): line638 # print 'os.getuid()',os.getuid() = 0 line639 # print 'os.getegit()',os.getegid() =0 line640 api = API.Global() line641 return api.ping() the api.ping() just open an file and update the file updating time, why these will throw an error code 0 or 99? And I see the ping() function created file /var/run/vdsm/client.log already exists in os, the only difference is the file is owned by root:root , not the vdsm:kvm? Why? Thank you. ------=_NextPart_000_00F7_01D1E76E.0E1E4A60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-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=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 = (filtered medium)"><style></style></head><body lang=3DZH-CN link=3Dblue = vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div = class=3DWordSection1><![if !supportLists]>1.       = <![endif]>We know that xmlrpc = and jsonrpc are enabled default in vdsm, vdsm supply these two service = in one port or two? What’s the port number and how we can change = it?<o:p></o:p><o:p> </o:p><![if !supportLists]>2.       = <![endif]>How can we know a vdsm = host can supply an xmlrpc service or a jsonrpc = service?<o:p></o:p><o:p> </o:p> = <o:p></o:p><![if !supportLists]>3.       = <![endif]>I found that while = ovirt engine installing a vdsm host, engine will check whether we are = connecting to vdsm which supports xmlrpc only, engine send a = ‘Host.ping’ jsonrpc request,  why the code will enter = into bindingxmlrpc.py?<o:p></o:p>Did both jsonrpc and xmlrpc will call = bindingxmlrpc.py?<o:p></o:p><o:p> </o:p><![if !supportLists]>4.       = <![endif]>Then, I just get an = json return with code =3D 0 or code =3D 99. What does these error code = mean ? I can’t find detail in rpcjson Specification(<a = href=3D"http://www.jsonrpc.org/specification">http://www.jsonrpc.org/spec= ification</a>)<o:p></o:p><o:p> </o:p><![if !supportLists]>5.       = <![endif]>When installing vdsm, = I got an “Host server117 installation failed. Host is not = reachable” error. Debugging code as = follows:<o:p></o:p>Bindingxmlrpc.py<o:p></o:p>line637  def = ping(self):<o:p></o:p>line638       # print = 'os.getuid()',os.getuid() =3D 0<o:p></o:p>line639       # print = 'os.getegit()',os.getegid() =3D0<o:p></o:p>line640        api =3D = API.Global()<o:p></o:p>line641        return = api.ping()<o:p></o:p><o:p> </o:p>the api.ping() just open an file and update the file = updating time, why these will throw an error code 0 or 99? And I see the = ping() function created file /var/run/vdsm/client.log already exists in = os, <o:p></o:p>the = only difference is the file is owned by root:root , not the vdsm:kvm? = Why?<o:p></o:p><o:p> </o:p>Thank you.<o:p></o:p><o:p> </o:p></div></body></html> ------=_NextPart_000_00F7_01D1E76E.0E1E4A60--

2 1

Debug vdsm 4.0.0 report error: libvirt: XML-RPC error : Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
by lifuqiong 26 Jul '16

26 Jul '16

This is a multipart message in MIME format. ------=_NextPart_000_001E_01D1E509.19780F20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I debugged vdsm with PyCharm, And I logged on my Centos 7.2 with root, and get an error as follows: Problem: Traceback (most recent call last): File "/usr/share/vdsm/vdsm", line 149, in run serve_clients(log) File "/usr/share/vdsm/vdsm", line 104, in serve_clients cif = clientIF.getInstance(irs, log, scheduler) File "/usr/share/vdsm/clientIF.py", line 204, in getInstance cls._instance = clientIF(irs, log, scheduler) File "/usr/share/vdsm/clientIF.py", line 106, in __init__ secret.clear() File "/usr/lib/python2.7/site-packages/vdsm/virt/secret.py", line 92, in clear con = libvirtconnection.get() File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 163, in get password) File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 99, in open_connection return utils.retry(libvirtOpen, timeout=10, sleep=0.2) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 546, in retry return func() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 105, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied Investitate: According to the traceback above, the code in libvirt.py as below, and os.geteuid() get '0' which shows the current user is root; def openAuth(uri, auth, flags=0): #print os.geteuid() ret = libvirtmod.virConnectOpenAuth(uri, auth, flags) if ret is None:raise libvirtError('virConnectOpenAuth() failed') return virConnect(_obj=ret) [root@server117 libvirt]# ll /var/run/libvirt/libvirt-sock srwxrwx---. 1 root qemu 0 Jul 19 23:43 /var/run/libvirt/libvirt-sock According that, root should not get an Permission denied error ? But why? And I setenforce=0 , and still show Perssion denied error. What's the reason? And how to solve it? Thank you. ------=_NextPart_000_001E_01D1E509.19780F20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-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=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 = (filtered medium)"><style></style></head><body lang=3DZH-CN link=3Dblue = vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div = class=3DWordSection1>I debugged = vdsm with PyCharm, And I logged on my Centos 7.2 with root,  and = get an error as follows:<o:p></o:p><o:p> </o:p>Problem:<o:p></o:p><o:p> </o:p>Traceback (most recent call last):<o:p></o:p>  File = "/usr/share/vdsm/vdsm", line 149, in = run<o:p></o:p>    = serve_clients(log)<o:p></o:p>  File "/usr/share/vdsm/vdsm", line 104, in = serve_clients<o:p></o:p>    cif =3D clientIF.getInstance(irs, log, = scheduler)<o:p></o:p>  File "/usr/share/vdsm/clientIF.py", line = 204, in getInstance<o:p></o:p>    cls._instance =3D clientIF(irs, log, = scheduler)<o:p></o:p>  File "/usr/share/vdsm/clientIF.py", line = 106, in __init__<o:p></o:p>    secret.clear()<o:p></o:p>  File = "/usr/lib/python2.7/site-packages/vdsm/virt/secret.py", line = 92, in clear<o:p></o:p>    con =3D = libvirtconnection.get()<o:p></o:p>  File = "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", = line 163, in get<o:p></o:p>    password)<o:p></o:p>  File = "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", = line 99, in open_connection<o:p></o:p>    return = utils.retry(libvirtOpen, timeout=3D10, = sleep=3D0.2)<o:p></o:p>  File = "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 546, in = retry<o:p></o:p>    return func()<o:p></o:p>  File = "/usr/lib64/python2.7/site-packages/libvirt.py", line 105, in = openAuth<o:p></o:p>    if ret is None:raise = libvirtError('virConnectOpenAuth() failed')<o:p></o:p>libvirtError: Failed to connect = socket to '/var/run/libvirt/libvirt-sock': Permission = denied<o:p></o:p><o:p> </o:p>Investitate:<o:p></o:p>According to the traceback above, = the code in libvirt.py as below, and  os.geteuid() get = ‘0’ which shows the current user is = root;<o:p></o:p><o:p> </o:p>def openAuth(uri, auth, flags=3D0):<o:p></o:p>         #print = os.geteuid()<o:p></o:p>    ret =3D = libvirtmod.virConnectOpenAuth(uri, auth, flags)<o:p></o:p>    if ret is = None:raise libvirtError('virConnectOpenAuth() = failed')<o:p></o:p>return = virConnect(_obj=3Dret)<o:p></o:p><o:p> </o:p>[root@server117 libvirt]# ll = /var/run/libvirt/libvirt-sock<o:p></o:p>srwxrwx---. 1 root qemu 0 Jul 19 = 23:43 /var/run/libvirt/libvirt-sock<o:p></o:p><o:p> </o:p>According that, root should not get = an Permission denied error ? But why?<o:p></o:p><o:p> </o:p>And I setenforce=3D0 , and still = show Perssion denied error.<o:p></o:p><o:p> </o:p>What’s the reason? And how to = solve it?<o:p></o:p><o:p> </o:p>Thank you.<o:p></o:p></div></body></html> ------=_NextPart_000_001E_01D1E509.19780F20--

5 9

Type Safety on the Frontend (refactoring of all async queries)
by Martin Betak 26 Jul '16

26 Jul '16

Hi All, today a *major* frontend refactoring was merged [1]. Its purpose was to remove some of the most significant artifacts of legacy C# code. Huge thanks to Vojtech and Alex for heavenly patience during code review! For a complete description please see the commit message, but here are some highlights for programmers that need to touch FE code: 1) AsyncQuery, AsyncCallback and Converter are now generic and typesafe (formerly INewAsyncCallback and IAsyncConverter). 2) It is no longer possible (or desirable) to PASS MODEL to queries. From within Model sublasses `new AsyncQuery<>(...)` will have the correct value set (see patch for impl details) and if you want to run a query on a different model (so the infrastructure would set the progress spinner on that model instead), usually for the purpose of a ListModel showing a popup window - where we want to display the spinner on the dialog window instead, you can use the `myWindowModel.asyncQuery(...)` helper factory to create query with model set to myWindowModel. // note: this also has the nice side-effect of eliminating the harmful pattern of using // the model value from within callbacks by casting it to surrounding model type (while that // value is already available by feature of java inner classes) 3) AsyncDataProvider's API methods now deal with strongly typed queries. This is facilitated through usage of strongly typed Converters (please see some defined converters -> usually you just need a CastingConverter<> or a ListConverter<>). Please use this architectural layer of strongly typed AsyncDataProvider to your advantage. (as plain Fronted.runQuery does not provide any guarantees and leaves you at risk of mis-casting the return value). If you have any more questions please feel free to ask me or look at the patch for details (warning: it's quite big!). This kind of major change necessarily touched all areas of the code (those issuing queries...) and there is of course some probability that something may break. But I believe this risk is well outweight by the benefits. Nevertheless if you find any issue please let me know and we can fix it together. Thanks again to anyone who contributed to this noble effort. Best regards :-) Martin [1] https://gerrit.ovirt.org/#/c/60822/

2 1