[Engine-devel] if there is a updated debug environment how to?
------=_Part_185146_1531092936.1370424870201 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit hi, engine guys: i want to make a engine debug environment for a looong time, due to all kinds of reasons i have not made it. now i still have the need for a debug environment. (it seems like that i am keeped away from you all) if there is a updated doc for building engine debug environment? thanks so much. ------=_Part_185146_1531092936.1370424870201 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: 7bit <div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><div>hi, engine guys:</div><div>i want to make a engine debug environment for a looong time, <font size="2">due to all kinds of reasons i have not made it.</font></div><div><font size="2">now i still have the need for a debug environment. (it seems like that i am keeped away from you all)</font></div><div><font size="2">if there is a updated doc for building engine debug environment?</font></div><div><font size="2"></font> </div><div><font size="2">thanks so much.</font></div></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span> ------=_Part_185146_1531092936.1370424870201--
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "engine-devel" <engine-devel@ovirt.org> Sent: Wednesday, June 5, 2013 12:34:30 PM Subject: [Engine-devel] if there is a updated debug environment how to?
hi, engine guys: i want to make a engine debug environment for a looong time, due to all kinds of reasons i have not made it. now i still have the need for a debug environment. (it seems like that i am keeped away from you all) if there is a updated doc for building engine debug environment? thanks so much.
Please follow Allon's B L doc on how to create a development environment http://www.ovirt.org/OVirt_Engine_Development_Environment
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
------=_Part_18972_194529262.1370566155106 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 aGk6CnRoZXJlIGlzIGVycm9yIHdoZW4gZW5naW5lLXNldHVwLTIuIGZpbmFsbHkgb25seSA4NzAy IGFuZCA4NzAzIHBvcnQgaXMgaW4gbGlzdGVuIHN0YXRlLgppIGNhbiBub3QgdmlzaXQgODA4MCB2 aWEgYnJvd3Nlci4KZW5naW5lLXNldHVwLTLvu78KWyBJTkZPICBdIENyZWF0aW5nIENBClsgSU5G TyAgXSBDcmVhdGluZyBkYXRhYmFzZSBzY2hlbWEKWyBFUlJPUiBdIEZhaWxlZCB0byBleGVjdXRl IHN0YWdlICdNaXNjIGNvbmZpZ3VyYXRpb24nOiBDb21tYW5kICcvaG9tZS9iZXN0L292aXJ0LWVu Z2luZS9zaGFyZS9vdmlydC1lbmdpbmUvZGJzY3JpcHRzL2NyZWF0ZV9zY2hlbWEuc2gnIGZhaWxl ZCB0byBleGVjdXRlClsgSU5GTyAgXSBTdGFnZTogQ2xlYW4gdXAKICAgICAgICAgIExvZyBmaWxl IGlzIGxvY2F0ZWQgYXQgL3RtcC9vdmlydC1lbmdpbmUtc2V0dXAtMjAxMzA2MDYxNzIyMDYubG9n CgoKCgoKCkF0IDIwMTMtMDYtMDYgMDU6MTc6MDcsIkVsaSBNZXNpa2EiIDxlbWVzaWthQHJlZGhh dC5jb20+IHdyb3RlOgo+Cj4KPi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPj4gRnJvbTog ImJpZ2Nsb3VkcyIgPGJpZ2Nsb3Vkc0AxNjMuY29tPgo+PiBUbzogImVuZ2luZS1kZXZlbCIgPGVu Z2luZS1kZXZlbEBvdmlydC5vcmc+Cj4+IFNlbnQ6IFdlZG5lc2RheSwgSnVuZSA1LCAyMDEzIDEy OjM0OjMwIFBNCj4+IFN1YmplY3Q6IFtFbmdpbmUtZGV2ZWxdIGlmIHRoZXJlIGlzIGEgdXBkYXRl ZCBkZWJ1ZyBlbnZpcm9ubWVudCBob3cgdG8/Cj4+IAo+PiBoaSwgZW5naW5lIGd1eXM6Cj4+IGkg d2FudCB0byBtYWtlIGEgZW5naW5lIGRlYnVnIGVudmlyb25tZW50IGZvciBhIGxvb29uZyB0aW1l LCBkdWUgdG8gYWxsIGtpbmRzCj4+IG9mIHJlYXNvbnMgaSBoYXZlIG5vdCBtYWRlIGl0Lgo+PiBu b3cgaSBzdGlsbCBoYXZlIHRoZSBuZWVkIGZvciBhIGRlYnVnIGVudmlyb25tZW50LiAoaXQgc2Vl bXMgbGlrZSB0aGF0IGkgYW0KPj4ga2VlcGVkIGF3YXkgZnJvbSB5b3UgYWxsKQo+PiBpZiB0aGVy ZSBpcyBhIHVwZGF0ZWQgZG9jIGZvciBidWlsZGluZyBlbmdpbmUgZGVidWcgZW52aXJvbm1lbnQ/ Cj4+IHRoYW5rcyBzbyBtdWNoLgo+PiAKPgo+UGxlYXNlIGZvbGxvdyBBbGxvbidzIEIgTCBkb2Mg b24gaG93IHRvIGNyZWF0ZSBhIGRldmVsb3BtZW50IGVudmlyb25tZW50IAo+Cj5odHRwOi8vd3d3 Lm92aXJ0Lm9yZy9PVmlydF9FbmdpbmVfRGV2ZWxvcG1lbnRfRW52aXJvbm1lbnQKPgo+Cj4+IAo+ PiAKPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPj4g RW5naW5lLWRldmVsIG1haWxpbmcgbGlzdAo+PiBFbmdpbmUtZGV2ZWxAb3ZpcnQub3JnCj4+IGh0 dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9lbmdpbmUtZGV2ZWwKPj4gCg== ------=_Part_18972_194529262.1370566155106 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6MS43O2NvbG9yOiMwMDAwMDA7Zm9udC1zaXplOjE0cHg7 Zm9udC1mYW1pbHk6YXJpYWwiPjxkaXY+PGRpdj48Zm9udCBzdHlsZT0iYmFja2dyb3VuZC1jb2xv cjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+PC9mb250PiA8L2Rpdj48c3BhbiBzdHlsZT0iY29sb3I6 IHJnYigwLCAwLCAwKTsiPjxkaXY+PGZvbnQgc3R5bGU9ImJhY2tncm91bmQtY29sb3I6IHJnYigy NTUsIDI1NSwgMjU1KTsiPmhpOjwvZm9udD48L2Rpdj48ZGl2Pjxmb250IHN0eWxlPSJiYWNrZ3Jv dW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUsIDI1NSk7Ij50aGVyZSBpcyBlcnJvciB3aGVuIGVuZ2lu ZS1zZXR1cC0yLiAgZmluYWxseSBvbmx5IDg3MDIgYW5kIDg3MDMgcG9ydCBpcyBpbiBsaXN0ZW4g c3RhdGUuPC9mb250PjwvZGl2PjxkaXY+aSBjYW4gbm90IHZpc2l0IDgwODAgdmlhIGJyb3dzZXIu PC9kaXY+PHByZSBzdHlsZT0iZm9udDogMTNweC8yMHB4IE1vbmFjbywgTWVubG8sIENvbnNvbGFz LCAmcXVvdDtDb3VyaWVyIE5ldyZxdW90OywgbW9ub3NwYWNlOyBtYXJnaW46IDEwcHggMHB4OyBw YWRkaW5nOiA4cHggMTBweDsgYm9yZGVyLXJhZGl1czogNnB4OyBib3JkZXI6IGN1cnJlbnRDb2xv cjsgY29sb3I6IHJnYigyMzgsIDIzOCwgMjM4KTsgdGV4dC10cmFuc2Zvcm06IG5vbmU7IHRleHQt aW5kZW50OiAwcHg7IGxldHRlci1zcGFjaW5nOiBub3JtYWw7IHdvcmQtc3BhY2luZzogMHB4OyBk aXNwbGF5OiBibG9jazsgd2hpdGUtc3BhY2U6IHByZS13cmFwOyB3b3JkLWJyZWFrOiBicmVhay1h bGw7IHdvcmQtd3JhcDogYnJlYWstd29yZDsgZm9udC1zaXplLWFkanVzdDogbm9uZTsgZm9udC1z dHJldGNoOiBub3JtYWw7IGJhY2tncm91bmQtY29sb3I6IHJnYigxMzYsIDEzNiwgMTM2KTsgLXdl YmtpdC10ZXh0LXN0cm9rZS13aWR0aDogMHB4OyI+PGZvbnQ+PGZvbnQgc3R5bGU9ImJhY2tncm91 bmQtY29sb3I6IHJnYigyNTUsIDI1NSwgMjU1KTsiPjxzcGFuIHN0eWxlPSJjb2xvcjogcmdiKDAs IDAsIDApOyI+ZW5naW5lLXNldHVwLTI8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2IoMCwg MCwgMCk7Ij7vu788L3NwYW4+PC9mb250PjwvZm9udD48L3ByZT48cHJlIHN0eWxlPSJmb250OiAx M3B4LzIwcHggTW9uYWNvLCBNZW5sbywgQ29uc29sYXMsICZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7 LCBtb25vc3BhY2U7IG1hcmdpbjogMTBweCAwcHg7IHBhZGRpbmc6IDhweCAxMHB4OyBib3JkZXIt cmFkaXVzOiA2cHg7IGJvcmRlcjogY3VycmVudENvbG9yOyBjb2xvcjogcmdiKDIzOCwgMjM4LCAy MzgpOyB0ZXh0LXRyYW5zZm9ybTogbm9uZTsgdGV4dC1pbmRlbnQ6IDBweDsgbGV0dGVyLXNwYWNp bmc6IG5vcm1hbDsgd29yZC1zcGFjaW5nOiAwcHg7IGRpc3BsYXk6IGJsb2NrOyB3aGl0ZS1zcGFj ZTogcHJlLXdyYXA7IHdvcmQtYnJlYWs6IGJyZWFrLWFsbDsgd29yZC13cmFwOiBicmVhay13b3Jk OyBmb250LXNpemUtYWRqdXN0OiBub25lOyBmb250LXN0cmV0Y2g6IG5vcm1hbDsgYmFja2dyb3Vu ZC1jb2xvcjogcmdiKDEzNiwgMTM2LCAxMzYpOyAtd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAw cHg7Ij48Zm9udCBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+ PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7Ij5bIElORk8gIF0gQ3JlYXRpbmcgQ0E8 L3NwYW4+PGJyPjxzcGFuIHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyI+WyBJTkZPICBdIENy ZWF0aW5nIGRhdGFiYXNlIHNjaGVtYTwvc3Bhbj48YnI+PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2Io MCwgMCwgMCk7Ij5bIEVSUk9SIF0gRmFpbGVkIHRvIGV4ZWN1dGUgc3RhZ2UgJ01pc2MgY29uZmln dXJhdGlvbic6IENvbW1hbmQgJy9ob21lL2Jlc3Qvb3ZpcnQtZW5naW5lL3NoYXJlL292aXJ0LWVu Z2luZS9kYnNjcmlwdHMvY3JlYXRlX3NjaGVtYS5zaCcgZmFpbGVkIHRvIGV4ZWN1dGU8L3NwYW4+ PGJyPjxzcGFuIHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyI+WyBJTkZPICBdIFN0YWdlOiBD bGVhbiB1cDwvc3Bhbj48YnI+PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7Ij4gICAg ICAgICAgTG9nIGZpbGUgaXMgbG9jYXRlZCBhdCAvdG1wL292aXJ0LWVuZ2luZS1zZXR1cC0yMDEz MDYwNjE3MjIwNi5sb2c8L3NwYW4+PC9mb250PjwvcHJlPjwvc3Bhbj48ZGl2PjxwcmUgc3R5bGU9 ImZvbnQ6IDEzcHgvMjBweCBNb25hY28sIE1lbmxvLCBDb25zb2xhcywgJnF1b3Q7Q291cmllciBO ZXcmcXVvdDssIG1vbm9zcGFjZTsgbWFyZ2luOiAxMHB4IDBweDsgcGFkZGluZzogOHB4IDEwcHg7 IGJvcmRlci1yYWRpdXM6IDZweDsgYm9yZGVyOiBjdXJyZW50Q29sb3I7IGNvbG9yOiByZ2IoMjM4 LCAyMzgsIDIzOCk7IHRleHQtdHJhbnNmb3JtOiBub25lOyB0ZXh0LWluZGVudDogMHB4OyBsZXR0 ZXItc3BhY2luZzogbm9ybWFsOyB3b3JkLXNwYWNpbmc6IDBweDsgZGlzcGxheTogYmxvY2s7IHdo aXRlLXNwYWNlOiBwcmUtd3JhcDsgd29yZC1icmVhazogYnJlYWstYWxsOyB3b3JkLXdyYXA6IGJy ZWFrLXdvcmQ7IGZvbnQtc2l6ZS1hZGp1c3Q6IG5vbmU7IGZvbnQtc3RyZXRjaDogbm9ybWFsOyBi YWNrZ3JvdW5kLWNvbG9yOiByZ2IoMTM2LCAxMzYsIDEzNik7IC13ZWJraXQtdGV4dC1zdHJva2Ut d2lkdGg6IDBweDsiPjxmb250IHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUs IDI1NSk7Ij48L2ZvbnQ+IDwvcHJlPjwvZGl2Pjxicj48YnI+PGJyPjxicj48L2Rpdj48ZGl2Pjwv ZGl2PjxkaXYgaWQ9ImRpdk5ldGVhc2VNYWlsQ2FyZCI+PC9kaXY+PGRpdj48L2Rpdj48cHJlPjxi cj5BdCZuYnNwOzIwMTMtMDYtMDYmbmJzcDswNToxNzowNywiRWxpJm5ic3A7TWVzaWthIiZuYnNw OyZsdDtlbWVzaWthQHJlZGhhdC5jb20mZ3Q7Jm5ic3A7d3JvdGU6CiZndDsKJmd0OwomZ3Q7LS0t LS0mbmJzcDtPcmlnaW5hbCZuYnNwO01lc3NhZ2UmbmJzcDstLS0tLQomZ3Q7Jmd0OyZuYnNwO0Zy b206Jm5ic3A7ImJpZ2Nsb3VkcyImbmJzcDsmbHQ7YmlnY2xvdWRzQDE2My5jb20mZ3Q7CiZndDsm Z3Q7Jm5ic3A7VG86Jm5ic3A7ImVuZ2luZS1kZXZlbCImbmJzcDsmbHQ7ZW5naW5lLWRldmVsQG92 aXJ0Lm9yZyZndDsKJmd0OyZndDsmbmJzcDtTZW50OiZuYnNwO1dlZG5lc2RheSwmbmJzcDtKdW5l Jm5ic3A7NSwmbmJzcDsyMDEzJm5ic3A7MTI6MzQ6MzAmbmJzcDtQTQomZ3Q7Jmd0OyZuYnNwO1N1 YmplY3Q6Jm5ic3A7W0VuZ2luZS1kZXZlbF0mbmJzcDtpZiZuYnNwO3RoZXJlJm5ic3A7aXMmbmJz cDthJm5ic3A7dXBkYXRlZCZuYnNwO2RlYnVnJm5ic3A7ZW52aXJvbm1lbnQmbmJzcDtob3cmbmJz cDt0bz8KJmd0OyZndDsmbmJzcDsKJmd0OyZndDsmbmJzcDtoaSwmbmJzcDtlbmdpbmUmbmJzcDtn dXlzOgomZ3Q7Jmd0OyZuYnNwO2kmbmJzcDt3YW50Jm5ic3A7dG8mbmJzcDttYWtlJm5ic3A7YSZu YnNwO2VuZ2luZSZuYnNwO2RlYnVnJm5ic3A7ZW52aXJvbm1lbnQmbmJzcDtmb3ImbmJzcDthJm5i c3A7bG9vb25nJm5ic3A7dGltZSwmbmJzcDtkdWUmbmJzcDt0byZuYnNwO2FsbCZuYnNwO2tpbmRz CiZndDsmZ3Q7Jm5ic3A7b2YmbmJzcDtyZWFzb25zJm5ic3A7aSZuYnNwO2hhdmUmbmJzcDtub3Qm bmJzcDttYWRlJm5ic3A7aXQuCiZndDsmZ3Q7Jm5ic3A7bm93Jm5ic3A7aSZuYnNwO3N0aWxsJm5i c3A7aGF2ZSZuYnNwO3RoZSZuYnNwO25lZWQmbmJzcDtmb3ImbmJzcDthJm5ic3A7ZGVidWcmbmJz cDtlbnZpcm9ubWVudC4mbmJzcDsoaXQmbmJzcDtzZWVtcyZuYnNwO2xpa2UmbmJzcDt0aGF0Jm5i c3A7aSZuYnNwO2FtCiZndDsmZ3Q7Jm5ic3A7a2VlcGVkJm5ic3A7YXdheSZuYnNwO2Zyb20mbmJz cDt5b3UmbmJzcDthbGwpCiZndDsmZ3Q7Jm5ic3A7aWYmbmJzcDt0aGVyZSZuYnNwO2lzJm5ic3A7 YSZuYnNwO3VwZGF0ZWQmbmJzcDtkb2MmbmJzcDtmb3ImbmJzcDtidWlsZGluZyZuYnNwO2VuZ2lu ZSZuYnNwO2RlYnVnJm5ic3A7ZW52aXJvbm1lbnQ/CiZndDsmZ3Q7Jm5ic3A7dGhhbmtzJm5ic3A7 c28mbmJzcDttdWNoLgomZ3Q7Jmd0OyZuYnNwOwomZ3Q7CiZndDtQbGVhc2UmbmJzcDtmb2xsb3cm bmJzcDtBbGxvbidzJm5ic3A7QiZuYnNwO0wmbmJzcDtkb2MmbmJzcDtvbiZuYnNwO2hvdyZuYnNw O3RvJm5ic3A7Y3JlYXRlJm5ic3A7YSZuYnNwO2RldmVsb3BtZW50Jm5ic3A7ZW52aXJvbm1lbnQm bmJzcDsKJmd0OwomZ3Q7aHR0cDovL3d3dy5vdmlydC5vcmcvT1ZpcnRfRW5naW5lX0RldmVsb3Bt ZW50X0Vudmlyb25tZW50CiZndDsKJmd0OwomZ3Q7Jmd0OyZuYnNwOwomZ3Q7Jmd0OyZuYnNwOwom Z3Q7Jmd0OyZuYnNwO19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fCiZndDsmZ3Q7Jm5ic3A7RW5naW5lLWRldmVsJm5ic3A7bWFpbGluZyZuYnNwO2xpc3QKJmd0 OyZndDsmbmJzcDtFbmdpbmUtZGV2ZWxAb3ZpcnQub3JnCiZndDsmZ3Q7Jm5ic3A7aHR0cDovL2xp c3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VuZ2luZS1kZXZlbAomZ3Q7Jmd0OyZuYnNw Owo8L3ByZT48L2Rpdj48YnI+PGJyPjxzcGFuIHRpdGxlPSJuZXRlYXNlZm9vdGVyIj48c3BhbiBp ZD0ibmV0ZWFzZV9tYWlsX2Zvb3RlciI+PC9zcGFuPjwvc3Bhbj4= ------=_Part_18972_194529262.1370566155106--
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Eli Mesika" <emesika@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 3:49:15 AM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
hi: there is error when engine-setup-2. finally only 8702 and 8703 port is in listen state. i can not visit 8080 via browser.
Well, if setup fails... probably application won't work.
engine-setup-2 [ INFO ] Creating CA [ INFO ] Creating database schema [ ERROR ] Failed to execute stage 'Misc configuration': Command '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_schema.sh' failed to execute [ INFO ] Stage: Clean up Log file is located at /tmp/ovirt-engine-setup-20130606172206.log
What database have you used? If you don't have anything important there, can you please try to initialize it so you start fresh? # systemctl stop postgresql.service # rm -fr /var/lib/pgsql # postgresql-setup initdb # vi /var/lib/pgsql/data/pg_hba.conf modify 127.0.0.1/32 and ::1/128 lines to password at last field # su - postgres -c psql -d template1 template1=# create user engine password 'engine'; template1=# create database engine owner engine; # \q
At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "engine-devel" <engine-devel@ovirt.org> Sent: Wednesday, June 5, 2013 12:34:30 PM Subject: [Engine-devel] if there is a updated debug environment how to? hi, engine guys: i want to make a engine debug environment for a looong time, due to all kinds of reasons i have not made it. now i still have the need for a debug environment. (it seems like that i am keeped away from you all) if there is a updated doc for building engine debug environment? thanks so much.
Please follow Allon's B L doc on how to create a development environment
http://www.ovirt.org/OVirt_Engine_Development_Environment
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "bigclouds" <bigclouds@163.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 9:55:41 AM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Eli Mesika" <emesika@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 3:49:15 AM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
hi: there is error when engine-setup-2. finally only 8702 and 8703 port is in listen state. i can not visit 8080 via browser.
Well, if setup fails... probably application won't work.
engine-setup-2 [ INFO ] Creating CA [ INFO ] Creating database schema [ ERROR ] Failed to execute stage 'Misc configuration': Command '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_schema.sh' failed to execute [ INFO ] Stage: Clean up Log file is located at /tmp/ovirt-engine-setup-20130606172206.log
What database have you used? If you don't have anything important there, can you please try to initialize it so you start fresh?
# systemctl stop postgresql.service # rm -fr /var/lib/pgsql # postgresql-setup initdb # vi /var/lib/pgsql/data/pg_hba.conf modify 127.0.0.1/32 and ::1/128 lines to password at last field # systemctl start postgresql.service # su - postgres -c psql -d template1 template1=# create user engine password 'engine'; template1=# create database engine owner engine; # \q
At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "engine-devel" <engine-devel@ovirt.org> Sent: Wednesday, June 5, 2013 12:34:30 PM Subject: [Engine-devel] if there is a updated debug environment how to? hi, engine guys: i want to make a engine debug environment for a looong time, due to all kinds of reasons i have not made it. now i still have the need for a debug environment. (it seems like that i am keeped away from you all) if there is a updated doc for building engine debug environment? thanks so much.
Please follow Allon's B L doc on how to create a development environment
http://www.ovirt.org/OVirt_Engine_Development_Environment
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
------=_Part_133632_1530618413.1370590165039 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 c28gbWFueSB0aGlua3MsaSAgZmluYWxseSBtYWtlIGl0LgogCmlmIGkgY2FuIGRlYnVnIGd3dCAg aW4gdGhpcyBlbnZpcm9ubWVudD8gIGFuZCBob3c/CiAKIAppZiB0aGlzIGxpbmsgaXMgc3RpbGwg aW4gdXNlLCBodHRwOi8vd3d3Lm92aXJ0Lm9yZy9EZWJ1Z0Zyb250ZW5kCiAKdGhhbmtzLgoKCgoK CkF0IDIwMTMtMDYtMDcgMTQ6NTU6NDEsIkFsb24gQmFyLUxldiIgPGFsb25ibEByZWRoYXQuY29t PiB3cm90ZToKPgo+Cj4tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tCj4+IEZyb206ICJiaWdj bG91ZHMiIDxiaWdjbG91ZHNAMTYzLmNvbT4KPj4gVG86ICJFbGkgTWVzaWthIiA8ZW1lc2lrYUBy ZWRoYXQuY29tPgo+PiBDYzogImVuZ2luZS1kZXZlbCIgPGVuZ2luZS1kZXZlbEBvdmlydC5vcmc+ Cj4+IFNlbnQ6IEZyaWRheSwgSnVuZSA3LCAyMDEzIDM6NDk6MTUgQU0KPj4gU3ViamVjdDogUmU6 IFtFbmdpbmUtZGV2ZWxdIGlmIHRoZXJlIGlzIGEgdXBkYXRlZCBkZWJ1ZyBlbnZpcm9ubWVudCBo b3cgdG8/Cj4+IAo+PiBoaToKPj4gdGhlcmUgaXMgZXJyb3Igd2hlbiBlbmdpbmUtc2V0dXAtMi4g ZmluYWxseSBvbmx5IDg3MDIgYW5kIDg3MDMgcG9ydCBpcyBpbgo+PiBsaXN0ZW4gc3RhdGUuCj4+ IGkgY2FuIG5vdCB2aXNpdCA4MDgwIHZpYSBicm93c2VyLgo+Cj5XZWxsLCBpZiBzZXR1cCBmYWls cy4uLiBwcm9iYWJseSBhcHBsaWNhdGlvbiB3b24ndCB3b3JrLgo+Cj4+IGVuZ2luZS1zZXR1cC0y IO+7vwo+PiBbIElORk8gIF0gQ3JlYXRpbmcgQ0EKPj4gWyBJTkZPICBdIENyZWF0aW5nIGRhdGFi YXNlIHNjaGVtYQo+PiBbIEVSUk9SIF0gRmFpbGVkIHRvIGV4ZWN1dGUgc3RhZ2UgJ01pc2MgY29u ZmlndXJhdGlvbic6IENvbW1hbmQKPj4gJy9ob21lL2Jlc3Qvb3ZpcnQtZW5naW5lL3NoYXJlL292 aXJ0LWVuZ2luZS9kYnNjcmlwdHMvY3JlYXRlX3NjaGVtYS5zaCcKPj4gZmFpbGVkIHRvIGV4ZWN1 dGUKPj4gWyBJTkZPICBdIFN0YWdlOiBDbGVhbiB1cAo+PiBMb2cgZmlsZSBpcyBsb2NhdGVkIGF0 IC90bXAvb3ZpcnQtZW5naW5lLXNldHVwLTIwMTMwNjA2MTcyMjA2LmxvZwo+Cj5XaGF0IGRhdGFi YXNlIGhhdmUgeW91ICB1c2VkPwo+SWYgeW91IGRvbid0IGhhdmUgYW55dGhpbmcgaW1wb3J0YW50 IHRoZXJlLCBjYW4geW91IHBsZWFzZSB0cnkgdG8gaW5pdGlhbGl6ZSBpdCBzbyB5b3Ugc3RhcnQg ZnJlc2g/Cj4KPiMgc3lzdGVtY3RsIHN0b3AgcG9zdGdyZXNxbC5zZXJ2aWNlCj4jIHJtIC1mciAv dmFyL2xpYi9wZ3NxbAo+IyBwb3N0Z3Jlc3FsLXNldHVwIGluaXRkYgo+IyB2aSAvdmFyL2xpYi9w Z3NxbC9kYXRhL3BnX2hiYS5jb25mCj5tb2RpZnkgMTI3LjAuMC4xLzMyIGFuZCA6OjEvMTI4IGxp bmVzIHRvIHBhc3N3b3JkIGF0IGxhc3QgZmllbGQKPiMgc3UgLSBwb3N0Z3JlcyAtYyBwc3FsIC1k IHRlbXBsYXRlMQo+dGVtcGxhdGUxPSMgY3JlYXRlIHVzZXIgZW5naW5lIHBhc3N3b3JkICdlbmdp bmUnOwo+dGVtcGxhdGUxPSMgY3JlYXRlIGRhdGFiYXNlIGVuZ2luZSBvd25lciBlbmdpbmU7Cj4j IFxxCj4KPj4gCj4+IAo+PiAKPj4gCj4+IEF0IDIwMTMtMDYtMDYgMDU6MTc6MDcsIkVsaSBNZXNp a2EiIDxlbWVzaWthQHJlZGhhdC5jb20+IHdyb3RlOgo+PiA+Cj4+ID4KPj4gPi0tLS0tIE9yaWdp bmFsIE1lc3NhZ2UgLS0tLS0KPj4gPj4gRnJvbTogImJpZ2Nsb3VkcyIgPGJpZ2Nsb3Vkc0AxNjMu Y29tPgo+PiA+PiBUbzogImVuZ2luZS1kZXZlbCIgPGVuZ2luZS1kZXZlbEBvdmlydC5vcmc+Cj4+ ID4+IFNlbnQ6IFdlZG5lc2RheSwgSnVuZSA1LCAyMDEzIDEyOjM0OjMwIFBNCj4+ID4+IFN1Ympl Y3Q6IFtFbmdpbmUtZGV2ZWxdIGlmIHRoZXJlIGlzIGEgdXBkYXRlZCBkZWJ1ZyBlbnZpcm9ubWVu dCBob3cgdG8/Cj4+ID4+IAo+PiA+PiBoaSwgZW5naW5lIGd1eXM6Cj4+ID4+IGkgd2FudCB0byBt YWtlIGEgZW5naW5lIGRlYnVnIGVudmlyb25tZW50IGZvciBhIGxvb29uZyB0aW1lLCBkdWUgdG8g YWxsCj4+ID4+ICBraW5kcwo+PiA+PiBvZiByZWFzb25zIGkgaGF2ZSBub3QgbWFkZSBpdC4KPj4g Pj4gbm93IGkgc3RpbGwgaGF2ZSB0aGUgbmVlZCBmb3IgYSBkZWJ1ZyBlbnZpcm9ubWVudC4gKGl0 IHNlZW1zIGxpa2UgdGhhdCBpCj4+ID4+ICBhbQo+PiA+PiBrZWVwZWQgYXdheSBmcm9tIHlvdSBh bGwpCj4+ID4+IGlmIHRoZXJlIGlzIGEgdXBkYXRlZCBkb2MgZm9yIGJ1aWxkaW5nIGVuZ2luZSBk ZWJ1ZyBlbnZpcm9ubWVudD8KPj4gPj4gdGhhbmtzIHNvIG11Y2guCj4+ID4+IAo+PiA+Cj4+ID5Q bGVhc2UgZm9sbG93IEFsbG9uJ3MgQiBMIGRvYyBvbiBob3cgdG8gY3JlYXRlIGEgZGV2ZWxvcG1l bnQgZW52aXJvbm1lbnQKPj4gPgo+PiA+aHR0cDovL3d3dy5vdmlydC5vcmcvT1ZpcnRfRW5naW5l X0RldmVsb3BtZW50X0Vudmlyb25tZW50Cj4+ID4KPj4gPgo+PiA+PiAKPj4gPj4gCj4+ID4+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4+ID4+IEVuZ2lu ZS1kZXZlbCBtYWlsaW5nIGxpc3QKPj4gPj4gRW5naW5lLWRldmVsQG92aXJ0Lm9yZwo+PiA+PiBo dHRwOi8vbGlzdHMub3ZpcnQub3JnL21haWxtYW4vbGlzdGluZm8vZW5naW5lLWRldmVsCj4+ID4+ IAo+PiAKPj4gCj4+IAo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXwo+PiBFbmdpbmUtZGV2ZWwgbWFpbGluZyBsaXN0Cj4+IEVuZ2luZS1kZXZlbEBvdmly dC5vcmcKPj4gaHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VuZ2luZS1k ZXZlbAo+PiAK ------=_Part_133632_1530618413.1370590165039 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6MS43O2NvbG9yOiMwMDAwMDA7Zm9udC1zaXplOjE0cHg7 Zm9udC1mYW1pbHk6YXJpYWwiPjxkaXY+c28gbWFueSB0aGlua3MsaSZuYnNwOyBmaW5hbGx5IG1h a2UgaXQuPC9kaXY+PGRpdj4mbmJzcDs8L2Rpdj48ZGl2PmlmIGkgY2FuIGRlYnVnIGd3dCZuYnNw OyBpbiB0aGlzIGVudmlyb25tZW50PyZuYnNwOyBhbmQgaG93PzwvZGl2PjxkaXY+Jm5ic3A7PC9k aXY+PGRpdj4mbmJzcDs8L2Rpdj48ZGl2PmlmIHRoaXMgbGluayBpcyBzdGlsbCBpbiB1c2UsIDxh IGhyZWY9Imh0dHA6Ly93d3cub3ZpcnQub3JnL0RlYnVnRnJvbnRlbmQiPmh0dHA6Ly93d3cub3Zp cnQub3JnL0RlYnVnRnJvbnRlbmQ8L2E+PC9kaXY+PGRpdj4mbmJzcDs8L2Rpdj48ZGl2PnRoYW5r cy48YnI+PGJyPjxicj48YnI+PC9kaXY+PGRpdj48L2Rpdj48ZGl2IGlkPSJkaXZOZXRlYXNlTWFp bENhcmQiPjwvZGl2PjxkaXY+PC9kaXY+PHByZT48YnI+QXQmbmJzcDsyMDEzLTA2LTA3Jm5ic3A7 MTQ6NTU6NDEsIkFsb24mbmJzcDtCYXItTGV2IiZuYnNwOyZsdDthbG9uYmxAcmVkaGF0LmNvbSZn dDsmbmJzcDt3cm90ZToKJmd0OwomZ3Q7CiZndDstLS0tLSZuYnNwO09yaWdpbmFsJm5ic3A7TWVz c2FnZSZuYnNwOy0tLS0tCiZndDsmZ3Q7Jm5ic3A7RnJvbTombmJzcDsiYmlnY2xvdWRzIiZuYnNw OyZsdDtiaWdjbG91ZHNAMTYzLmNvbSZndDsKJmd0OyZndDsmbmJzcDtUbzombmJzcDsiRWxpJm5i c3A7TWVzaWthIiZuYnNwOyZsdDtlbWVzaWthQHJlZGhhdC5jb20mZ3Q7CiZndDsmZ3Q7Jm5ic3A7 Q2M6Jm5ic3A7ImVuZ2luZS1kZXZlbCImbmJzcDsmbHQ7ZW5naW5lLWRldmVsQG92aXJ0Lm9yZyZn dDsKJmd0OyZndDsmbmJzcDtTZW50OiZuYnNwO0ZyaWRheSwmbmJzcDtKdW5lJm5ic3A7NywmbmJz cDsyMDEzJm5ic3A7Mzo0OToxNSZuYnNwO0FNCiZndDsmZ3Q7Jm5ic3A7U3ViamVjdDombmJzcDtS ZTombmJzcDtbRW5naW5lLWRldmVsXSZuYnNwO2lmJm5ic3A7dGhlcmUmbmJzcDtpcyZuYnNwO2Em bmJzcDt1cGRhdGVkJm5ic3A7ZGVidWcmbmJzcDtlbnZpcm9ubWVudCZuYnNwO2hvdyZuYnNwO3Rv PwomZ3Q7Jmd0OyZuYnNwOwomZ3Q7Jmd0OyZuYnNwO2hpOgomZ3Q7Jmd0OyZuYnNwO3RoZXJlJm5i c3A7aXMmbmJzcDtlcnJvciZuYnNwO3doZW4mbmJzcDtlbmdpbmUtc2V0dXAtMi4mbmJzcDtmaW5h bGx5Jm5ic3A7b25seSZuYnNwOzg3MDImbmJzcDthbmQmbmJzcDs4NzAzJm5ic3A7cG9ydCZuYnNw O2lzJm5ic3A7aW4KJmd0OyZndDsmbmJzcDtsaXN0ZW4mbmJzcDtzdGF0ZS4KJmd0OyZndDsmbmJz cDtpJm5ic3A7Y2FuJm5ic3A7bm90Jm5ic3A7dmlzaXQmbmJzcDs4MDgwJm5ic3A7dmlhJm5ic3A7 YnJvd3Nlci4KJmd0OwomZ3Q7V2VsbCwmbmJzcDtpZiZuYnNwO3NldHVwJm5ic3A7ZmFpbHMuLi4m bmJzcDtwcm9iYWJseSZuYnNwO2FwcGxpY2F0aW9uJm5ic3A7d29uJ3QmbmJzcDt3b3JrLgomZ3Q7 CiZndDsmZ3Q7Jm5ic3A7ZW5naW5lLXNldHVwLTImbmJzcDvvu78KJmd0OyZndDsmbmJzcDtbJm5i c3A7SU5GTyZuYnNwOyZuYnNwO10mbmJzcDtDcmVhdGluZyZuYnNwO0NBCiZndDsmZ3Q7Jm5ic3A7 WyZuYnNwO0lORk8mbmJzcDsmbmJzcDtdJm5ic3A7Q3JlYXRpbmcmbmJzcDtkYXRhYmFzZSZuYnNw O3NjaGVtYQomZ3Q7Jmd0OyZuYnNwO1smbmJzcDtFUlJPUiZuYnNwO10mbmJzcDtGYWlsZWQmbmJz cDt0byZuYnNwO2V4ZWN1dGUmbmJzcDtzdGFnZSZuYnNwOydNaXNjJm5ic3A7Y29uZmlndXJhdGlv bic6Jm5ic3A7Q29tbWFuZAomZ3Q7Jmd0OyZuYnNwOycvaG9tZS9iZXN0L292aXJ0LWVuZ2luZS9z aGFyZS9vdmlydC1lbmdpbmUvZGJzY3JpcHRzL2NyZWF0ZV9zY2hlbWEuc2gnCiZndDsmZ3Q7Jm5i c3A7ZmFpbGVkJm5ic3A7dG8mbmJzcDtleGVjdXRlCiZndDsmZ3Q7Jm5ic3A7WyZuYnNwO0lORk8m bmJzcDsmbmJzcDtdJm5ic3A7U3RhZ2U6Jm5ic3A7Q2xlYW4mbmJzcDt1cAomZ3Q7Jmd0OyZuYnNw O0xvZyZuYnNwO2ZpbGUmbmJzcDtpcyZuYnNwO2xvY2F0ZWQmbmJzcDthdCZuYnNwOy90bXAvb3Zp cnQtZW5naW5lLXNldHVwLTIwMTMwNjA2MTcyMjA2LmxvZwomZ3Q7CiZndDtXaGF0Jm5ic3A7ZGF0 YWJhc2UmbmJzcDtoYXZlJm5ic3A7eW91Jm5ic3A7Jm5ic3A7dXNlZD8KJmd0O0lmJm5ic3A7eW91 Jm5ic3A7ZG9uJ3QmbmJzcDtoYXZlJm5ic3A7YW55dGhpbmcmbmJzcDtpbXBvcnRhbnQmbmJzcDt0 aGVyZSwmbmJzcDtjYW4mbmJzcDt5b3UmbmJzcDtwbGVhc2UmbmJzcDt0cnkmbmJzcDt0byZuYnNw O2luaXRpYWxpemUmbmJzcDtpdCZuYnNwO3NvJm5ic3A7eW91Jm5ic3A7c3RhcnQmbmJzcDtmcmVz aD8KJmd0OwomZ3Q7IyZuYnNwO3N5c3RlbWN0bCZuYnNwO3N0b3AmbmJzcDtwb3N0Z3Jlc3FsLnNl cnZpY2UKJmd0OyMmbmJzcDtybSZuYnNwOy1mciZuYnNwOy92YXIvbGliL3Bnc3FsCiZndDsjJm5i c3A7cG9zdGdyZXNxbC1zZXR1cCZuYnNwO2luaXRkYgomZ3Q7IyZuYnNwO3ZpJm5ic3A7L3Zhci9s aWIvcGdzcWwvZGF0YS9wZ19oYmEuY29uZgomZ3Q7bW9kaWZ5Jm5ic3A7MTI3LjAuMC4xLzMyJm5i c3A7YW5kJm5ic3A7OjoxLzEyOCZuYnNwO2xpbmVzJm5ic3A7dG8mbmJzcDtwYXNzd29yZCZuYnNw O2F0Jm5ic3A7bGFzdCZuYnNwO2ZpZWxkCiZndDsjJm5ic3A7c3UmbmJzcDstJm5ic3A7cG9zdGdy ZXMmbmJzcDstYyZuYnNwO3BzcWwmbmJzcDstZCZuYnNwO3RlbXBsYXRlMQomZ3Q7dGVtcGxhdGUx PSMmbmJzcDtjcmVhdGUmbmJzcDt1c2VyJm5ic3A7ZW5naW5lJm5ic3A7cGFzc3dvcmQmbmJzcDsn ZW5naW5lJzsKJmd0O3RlbXBsYXRlMT0jJm5ic3A7Y3JlYXRlJm5ic3A7ZGF0YWJhc2UmbmJzcDtl bmdpbmUmbmJzcDtvd25lciZuYnNwO2VuZ2luZTsKJmd0OyMmbmJzcDtccQomZ3Q7CiZndDsmZ3Q7 Jm5ic3A7CiZndDsmZ3Q7Jm5ic3A7CiZndDsmZ3Q7Jm5ic3A7CiZndDsmZ3Q7Jm5ic3A7CiZndDsm Z3Q7Jm5ic3A7QXQmbmJzcDsyMDEzLTA2LTA2Jm5ic3A7MDU6MTc6MDcsIkVsaSZuYnNwO01lc2lr YSImbmJzcDsmbHQ7ZW1lc2lrYUByZWRoYXQuY29tJmd0OyZuYnNwO3dyb3RlOgomZ3Q7Jmd0OyZu YnNwOyZndDsKJmd0OyZndDsmbmJzcDsmZ3Q7CiZndDsmZ3Q7Jm5ic3A7Jmd0Oy0tLS0tJm5ic3A7 T3JpZ2luYWwmbmJzcDtNZXNzYWdlJm5ic3A7LS0tLS0KJmd0OyZndDsmbmJzcDsmZ3Q7Jmd0OyZu YnNwO0Zyb206Jm5ic3A7ImJpZ2Nsb3VkcyImbmJzcDsmbHQ7YmlnY2xvdWRzQDE2My5jb20mZ3Q7 CiZndDsmZ3Q7Jm5ic3A7Jmd0OyZndDsmbmJzcDtUbzombmJzcDsiZW5naW5lLWRldmVsIiZuYnNw OyZsdDtlbmdpbmUtZGV2ZWxAb3ZpcnQub3JnJmd0OwomZ3Q7Jmd0OyZuYnNwOyZndDsmZ3Q7Jm5i c3A7U2VudDombmJzcDtXZWRuZXNkYXksJm5ic3A7SnVuZSZuYnNwOzUsJm5ic3A7MjAxMyZuYnNw OzEyOjM0OjMwJm5ic3A7UE0KJmd0OyZndDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwO1N1YmplY3Q6Jm5i c3A7W0VuZ2luZS1kZXZlbF0mbmJzcDtpZiZuYnNwO3RoZXJlJm5ic3A7aXMmbmJzcDthJm5ic3A7 dXBkYXRlZCZuYnNwO2RlYnVnJm5ic3A7ZW52aXJvbm1lbnQmbmJzcDtob3cmbmJzcDt0bz8KJmd0 OyZndDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwOwomZ3Q7Jmd0OyZuYnNwOyZndDsmZ3Q7Jm5ic3A7aGks Jm5ic3A7ZW5naW5lJm5ic3A7Z3V5czoKJmd0OyZndDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwO2kmbmJz cDt3YW50Jm5ic3A7dG8mbmJzcDttYWtlJm5ic3A7YSZuYnNwO2VuZ2luZSZuYnNwO2RlYnVnJm5i c3A7ZW52aXJvbm1lbnQmbmJzcDtmb3ImbmJzcDthJm5ic3A7bG9vb25nJm5ic3A7dGltZSwmbmJz cDtkdWUmbmJzcDt0byZuYnNwO2FsbAomZ3Q7Jmd0OyZuYnNwOyZndDsmZ3Q7Jm5ic3A7Jm5ic3A7 a2luZHMKJmd0OyZndDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwO29mJm5ic3A7cmVhc29ucyZuYnNwO2km bmJzcDtoYXZlJm5ic3A7bm90Jm5ic3A7bWFkZSZuYnNwO2l0LgomZ3Q7Jmd0OyZuYnNwOyZndDsm Z3Q7Jm5ic3A7bm93Jm5ic3A7aSZuYnNwO3N0aWxsJm5ic3A7aGF2ZSZuYnNwO3RoZSZuYnNwO25l ZWQmbmJzcDtmb3ImbmJzcDthJm5ic3A7ZGVidWcmbmJzcDtlbnZpcm9ubWVudC4mbmJzcDsoaXQm bmJzcDtzZWVtcyZuYnNwO2xpa2UmbmJzcDt0aGF0Jm5ic3A7aQomZ3Q7Jmd0OyZuYnNwOyZndDsm Z3Q7Jm5ic3A7Jm5ic3A7YW0KJmd0OyZndDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwO2tlZXBlZCZuYnNw O2F3YXkmbmJzcDtmcm9tJm5ic3A7eW91Jm5ic3A7YWxsKQomZ3Q7Jmd0OyZuYnNwOyZndDsmZ3Q7 Jm5ic3A7aWYmbmJzcDt0aGVyZSZuYnNwO2lzJm5ic3A7YSZuYnNwO3VwZGF0ZWQmbmJzcDtkb2Mm bmJzcDtmb3ImbmJzcDtidWlsZGluZyZuYnNwO2VuZ2luZSZuYnNwO2RlYnVnJm5ic3A7ZW52aXJv bm1lbnQ/CiZndDsmZ3Q7Jm5ic3A7Jmd0OyZndDsmbmJzcDt0aGFua3MmbmJzcDtzbyZuYnNwO211 Y2guCiZndDsmZ3Q7Jm5ic3A7Jmd0OyZndDsmbmJzcDsKJmd0OyZndDsmbmJzcDsmZ3Q7CiZndDsm Z3Q7Jm5ic3A7Jmd0O1BsZWFzZSZuYnNwO2ZvbGxvdyZuYnNwO0FsbG9uJ3MmbmJzcDtCJm5ic3A7 TCZuYnNwO2RvYyZuYnNwO29uJm5ic3A7aG93Jm5ic3A7dG8mbmJzcDtjcmVhdGUmbmJzcDthJm5i c3A7ZGV2ZWxvcG1lbnQmbmJzcDtlbnZpcm9ubWVudAomZ3Q7Jmd0OyZuYnNwOyZndDsKJmd0OyZn dDsmbmJzcDsmZ3Q7aHR0cDovL3d3dy5vdmlydC5vcmcvT1ZpcnRfRW5naW5lX0RldmVsb3BtZW50 X0Vudmlyb25tZW50CiZndDsmZ3Q7Jm5ic3A7Jmd0OwomZ3Q7Jmd0OyZuYnNwOyZndDsKJmd0OyZn dDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwOwomZ3Q7Jmd0OyZuYnNwOyZndDsmZ3Q7Jm5ic3A7CiZndDsm Z3Q7Jm5ic3A7Jmd0OyZndDsmbmJzcDtfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwomZ3Q7Jmd0OyZuYnNwOyZndDsmZ3Q7Jm5ic3A7RW5naW5lLWRldmVsJm5i c3A7bWFpbGluZyZuYnNwO2xpc3QKJmd0OyZndDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwO0VuZ2luZS1k ZXZlbEBvdmlydC5vcmcKJmd0OyZndDsmbmJzcDsmZ3Q7Jmd0OyZuYnNwO2h0dHA6Ly9saXN0cy5v dmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9lbmdpbmUtZGV2ZWwKJmd0OyZndDsmbmJzcDsmZ3Q7 Jmd0OyZuYnNwOwomZ3Q7Jmd0OyZuYnNwOwomZ3Q7Jmd0OyZuYnNwOwomZ3Q7Jmd0OyZuYnNwOwom Z3Q7Jmd0OyZuYnNwO19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fCiZndDsmZ3Q7Jm5ic3A7RW5naW5lLWRldmVsJm5ic3A7bWFpbGluZyZuYnNwO2xpc3QKJmd0 OyZndDsmbmJzcDtFbmdpbmUtZGV2ZWxAb3ZpcnQub3JnCiZndDsmZ3Q7Jm5ic3A7aHR0cDovL2xp c3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VuZ2luZS1kZXZlbAomZ3Q7Jmd0OyZuYnNw Owo8L3ByZT48L2Rpdj48YnI+PGJyPjxzcGFuIHRpdGxlPSJuZXRlYXNlZm9vdGVyIj48c3BhbiBp ZD0ibmV0ZWFzZV9tYWlsX2Zvb3RlciI+PC9zcGFuPjwvc3Bhbj4= ------=_Part_133632_1530618413.1370590165039--
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 AM Subject: Re:Re: [Engine-devel] if there is a updated debug environment how to?
so many thinks,i finally make it.
if i can debug gwt in this environment? and how?
if this link is still in use, http://www.ovirt.org/DebugFrontend
thanks.
This is interesting, I would like to work with someone that knows GWT to make this happen. If I read this correctly, all you need to do is: $ make install-dev PREFIX="${HOME}/ovirt-engine" EXTRA_BUILD_FLAGS_DEV="-Pgwtdev" And connect eclipse using the standard jboss debug port. But I know nothing of GWT, I will appreciate help in that... How do we connect to a running instance of jboss and debug gwt, what setting should we have? Thanks!
At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Eli Mesika" <emesika@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 3:49:15 AM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
hi: there is error when engine-setup-2. finally only 8702 and 8703 port is in listen state. i can not visit 8080 via browser.
Well, if setup fails... probably application won't work.
engine-setup-2 [ INFO ] Creating CA [ INFO ] Creating database schema [ ERROR ] Failed to execute stage 'Misc configuration': Command '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_schema.sh' failed to execute [ INFO ] Stage: Clean up Log file is located at /tmp/ovirt-engine-setup-20130606172206.log
What database have you used? If you don't have anything important there, can you please try to initialize it so you start fresh?
# systemctl stop postgresql.service # rm -fr /var/lib/pgsql # postgresql-setup initdb # vi /var/lib/pgsql/data/pg_hba.conf modify 127.0.0.1/32 and ::1/128 lines to password at last field # su - postgres -c psql -d template1 template1=# create user engine password 'engine'; template1=# create database engine owner engine; # \q
At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "engine-devel" <engine-devel@ovirt.org> Sent: Wednesday, June 5, 2013 12:34:30 PM Subject: [Engine-devel] if there is a updated debug environment how to?
hi, engine guys: i want to make a engine debug environment for a looong time, due to all kinds of reasons i have not made it. now i still have the need for a debug environment. (it seems like that i am keeped away from you all) if there is a updated doc for building engine debug environment? thanks so much.
Please follow Allon's B L doc on how to create a development environment
http://www.ovirt.org/OVirt_Engine_Development_Environment
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 AM Subject: Re:Re: [Engine-devel] if there is a updated debug environment how to?
so many thinks,i finally make it.
if i can debug gwt in this environment? and how?
if this link is still in use, http://www.ovirt.org/DebugFrontend
thanks.
This is interesting, I would like to work with someone that knows GWT to make this happen.
If I read this correctly, all you need to do is:
$ make install-dev PREFIX="${HOME}/ovirt-engine" EXTRA_BUILD_FLAGS_DEV="-Pgwtdev"
And connect eclipse using the standard jboss debug port.
But I know nothing of GWT, I will appreciate help in that...
How do we connect to a running instance of jboss and debug gwt, what setting should we have?
Once you have the engine up and running as explained about, you can use http://www.ovirt.org/DebugFrontend to run GWT debugging. You can safely skip step 0 in that document (I think that needs to be updated). And start at step 1. The document explains quite well what to do, but the short version is: 1. cd into the source code directory of either webadmin or user portal. Usually: ovirt- engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true from the command line. Once it is done compiling it will tell you it is listening on port 8000. 3.In eclipse (or your favorite java IDE) make a remote java application connection to port 8000 4. Once connected this will open up a GWT debug window. 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you are working with and refresh the page. 6. It will either ask you to install the plugin in your browser or load the page depending on if you have the plugin already. Alexander
Thanks!
At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Eli Mesika" <emesika@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 3:49:15 AM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
hi: there is error when engine-setup-2. finally only 8702 and 8703 port is in listen state. i can not visit 8080 via browser.
Well, if setup fails... probably application won't work.
engine-setup-2 [ INFO ] Creating CA [ INFO ] Creating database schema [ ERROR ] Failed to execute stage 'Misc configuration': Command '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_schema.sh' failed to execute [ INFO ] Stage: Clean up Log file is located at /tmp/ovirt-engine-setup-20130606172206.log
What database have you used? If you don't have anything important there, can you please try to initialize it so you start fresh?
# systemctl stop postgresql.service # rm -fr /var/lib/pgsql # postgresql-setup initdb # vi /var/lib/pgsql/data/pg_hba.conf modify 127.0.0.1/32 and ::1/128 lines to password at last field # su - postgres -c psql -d template1 template1=# create user engine password 'engine'; template1=# create database engine owner engine; # \q
At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "engine-devel" <engine-devel@ovirt.org> Sent: Wednesday, June 5, 2013 12:34:30 PM Subject: [Engine-devel] if there is a updated debug environment how to?
hi, engine guys: i want to make a engine debug environment for a looong time, due to all
kinds
of reasons i have not made it. now i still have the need for a debug environment. (it seems like that i
am
keeped away from you all) if there is a updated doc for building engine debug environment? thanks so much.
Please follow Allon's B L doc on how to create a development environment
http://www.ovirt.org/OVirt_Engine_Development_Environment
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: engine-devel@ovirt.org Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 3:09:19 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 AM Subject: Re:Re: [Engine-devel] if there is a updated debug environment how to?
so many thinks,i finally make it.
if i can debug gwt in this environment? and how?
if this link is still in use, http://www.ovirt.org/DebugFrontend
thanks.
This is interesting, I would like to work with someone that knows GWT to make this happen.
If I read this correctly, all you need to do is:
$ make install-dev PREFIX="${HOME}/ovirt-engine" EXTRA_BUILD_FLAGS_DEV="-Pgwtdev"
And connect eclipse using the standard jboss debug port.
But I know nothing of GWT, I will appreciate help in that...
How do we connect to a running instance of jboss and debug gwt, what setting should we have?
Hi Alex,
Once you have the engine up and running as explained about, you can use http://www.ovirt.org/DebugFrontend to run GWT debugging. You can safely skip step 0 in that document (I think that needs to be updated). And start at step 1. The document explains quite well what to do, but the short version is:
1. cd into the source code directory of either webadmin or user portal. Usually: ovirt- engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true from the command line. Once it is done compiling it will tell you it is listening on port 8000.
This will not run as jboss, right? Or you mean it will run on the jboss of the legacy (not the new environment). I would like a solution in which we can use the already running jboss instance that use for production in order to debug gwt. Is that possible? I guess some properties need to be passed, or new modules. Thanks!
3.In eclipse (or your favorite java IDE) make a remote java application connection to port 8000 4. Once connected this will open up a GWT debug window. 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you are working with and refresh the page. 6. It will either ask you to install the plugin in your browser or load the page depending on if you have the plugin already.
Alexander
Thanks!
At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Eli Mesika" <emesika@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 3:49:15 AM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
hi: there is error when engine-setup-2. finally only 8702 and 8703 port is in listen state. i can not visit 8080 via browser.
Well, if setup fails... probably application won't work.
engine-setup-2 [ INFO ] Creating CA [ INFO ] Creating database schema [ ERROR ] Failed to execute stage 'Misc configuration': Command '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_schema.sh' failed to execute [ INFO ] Stage: Clean up Log file is located at /tmp/ovirt-engine-setup-20130606172206.log
What database have you used? If you don't have anything important there, can you please try to initialize it so you start fresh?
# systemctl stop postgresql.service # rm -fr /var/lib/pgsql # postgresql-setup initdb # vi /var/lib/pgsql/data/pg_hba.conf modify 127.0.0.1/32 and ::1/128 lines to password at last field # su - postgres -c psql -d template1 template1=# create user engine password 'engine'; template1=# create database engine owner engine; # \q
At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote:
----- Original Message -----
> From: "bigclouds" <bigclouds@163.com> > To: "engine-devel" <engine-devel@ovirt.org> > Sent: Wednesday, June 5, 2013 12:34:30 PM > Subject: [Engine-devel] if there is a updated debug environment how > to? > > hi, engine guys: > i want to make a engine debug environment for a looong time, due to > all > > kinds > > of reasons i have not made it. > now i still have the need for a debug environment. (it seems like > that > i > > am > > keeped away from you all) > if there is a updated doc for building engine debug environment? > thanks so much.
Please follow Allon's B L doc on how to create a development environment
http://www.ovirt.org/OVirt_Engine_Development_Environment
> _______________________________________________ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________
On Friday, June 07, 2013 08:26:32 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: engine-devel@ovirt.org Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 3:09:19 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 AM Subject: Re:Re: [Engine-devel] if there is a updated debug environment how to?
so many thinks,i finally make it.
if i can debug gwt in this environment? and how?
if this link is still in use, http://www.ovirt.org/DebugFrontend
thanks.
This is interesting, I would like to work with someone that knows GWT to make this happen.
If I read this correctly, all you need to do is:
$ make install-dev PREFIX="${HOME}/ovirt-engine" EXTRA_BUILD_FLAGS_DEV="-Pgwtdev"
And connect eclipse using the standard jboss debug port.
But I know nothing of GWT, I will appreciate help in that...
How do we connect to a running instance of jboss and debug gwt, what setting should we have?
Hi Alex,
Once you have the engine up and running as explained about, you can use http://www.ovirt.org/DebugFrontend to run GWT debugging. You can safely skip step 0 in that document (I think that needs to be updated). And start at step 1. The document explains quite well what to do, but the short version is:
1. cd into the source code directory of either webadmin or user portal. Usually: ovirt- engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true from the command line. Once it is done compiling it will tell you it is listening on port 8000.
This will not run as jboss, right?
No it is a normal java application (The GWT debugger).
Or you mean it will run on the jboss of the legacy (not the new environment). I would like a solution in which we can use the already running jboss instance that use for production in order to debug gwt. Is that possible? I guess some properties need to be passed, or new modules.
Thanks!
The GWT debugger is completely agnostic with regards to what serves the host page. The GWT debugger is connected to the browser, not the server. The host page can be served from a local JBOSS, a remote Apache, a file, whatever. The GWT debugger doesn't care as it is talking to the browser. IMO the only thing we could do to improve this is update the make file to provide a target to start the debugger, which basically just calls maven with the appropriate parameters.
3.In eclipse (or your favorite java IDE) make a remote java application connection to port 8000 4. Once connected this will open up a GWT debug window. 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you are working with and refresh the page. 6. It will either ask you to install the plugin in your browser or load the page depending on if you have the plugin already.
Alexander
Thanks!
At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Eli Mesika" <emesika@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 3:49:15 AM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
hi: there is error when engine-setup-2. finally only 8702 and 8703 port is in listen state. i can not visit 8080 via browser.
Well, if setup fails... probably application won't work.
engine-setup-2 [ INFO ] Creating CA [ INFO ] Creating database schema [ ERROR ] Failed to execute stage 'Misc configuration': Command '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_schema .sh' failed to execute [ INFO ] Stage: Clean up Log file is located at /tmp/ovirt-engine-setup-20130606172206.log
What database have you used? If you don't have anything important there, can you please try to initialize it so you start fresh?
# systemctl stop postgresql.service # rm -fr /var/lib/pgsql # postgresql-setup initdb # vi /var/lib/pgsql/data/pg_hba.conf modify 127.0.0.1/32 and ::1/128 lines to password at last field # su - postgres -c psql -d template1 template1=# create user engine password 'engine'; template1=# create database engine owner engine; # \q
At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote: >----- Original Message ----- > >> From: "bigclouds" <bigclouds@163.com> >> To: "engine-devel" <engine-devel@ovirt.org> >> Sent: Wednesday, June 5, 2013 12:34:30 PM >> Subject: [Engine-devel] if there is a updated debug environment >> how >> to? >> >> hi, engine guys: >> i want to make a engine debug environment for a looong time, due >> to >> all >> >> kinds >> >> of reasons i have not made it. >> now i still have the need for a debug environment. (it seems >> like >> that >> i >> >> am >> >> keeped away from you all) >> if there is a updated doc for building engine debug environment? >> thanks so much. > >Please follow Allon's B L doc on how to create a development >environment > >http://www.ovirt.org/OVirt_Engine_Development_Environment > >> _______________________________________________ >> Engine-devel mailing list >> Engine-devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 4:14:59 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 08:26:32 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: engine-devel@ovirt.org Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 3:09:19 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 AM Subject: Re:Re: [Engine-devel] if there is a updated debug environment how to?
so many thinks,i finally make it.
if i can debug gwt in this environment? and how?
if this link is still in use, http://www.ovirt.org/DebugFrontend
thanks.
This is interesting, I would like to work with someone that knows GWT to make this happen.
If I read this correctly, all you need to do is:
$ make install-dev PREFIX="${HOME}/ovirt-engine" EXTRA_BUILD_FLAGS_DEV="-Pgwtdev"
And connect eclipse using the standard jboss debug port.
But I know nothing of GWT, I will appreciate help in that...
How do we connect to a running instance of jboss and debug gwt, what setting should we have?
Hi Alex,
Once you have the engine up and running as explained about, you can use http://www.ovirt.org/DebugFrontend to run GWT debugging. You can safely skip step 0 in that document (I think that needs to be updated). And start at step 1. The document explains quite well what to do, but the short version is:
1. cd into the source code directory of either webadmin or user portal. Usually: ovirt- engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true from the command line. Once it is done compiling it will tell you it is listening on port 8000.
This will not run as jboss, right?
No it is a normal java application (The GWT debugger).
Or you mean it will run on the jboss of the legacy (not the new environment). I would like a solution in which we can use the already running jboss instance that use for production in order to debug gwt. Is that possible? I guess some properties need to be passed, or new modules.
Thanks!
The GWT debugger is completely agnostic with regards to what serves the host page. The GWT debugger is connected to the browser, not the server. The host page can be served from a local JBOSS, a remote Apache, a file, whatever. The GWT debugger doesn't care as it is talking to the browser.
Can you please explain this text from the wiki: gwt.noserver tells Development Mode that the application is already deployed on JBoss AS (don't use embedded Jetty instance to serve application content) Or this: Q: Client-side logs are not persisted on Engine, e.g. $JBOSS_HOME/standalone/log/engine/engine-ui.log. A: Currently, client-side logs are enabled only when debugging the application via Development Mode. What listens on port 8700? Thanks!
IMO the only thing we could do to improve this is update the make file to provide a target to start the debugger, which basically just calls maven with the appropriate parameters.
3.In eclipse (or your favorite java IDE) make a remote java application connection to port 8000 4. Once connected this will open up a GWT debug window. 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you are working with and refresh the page. 6. It will either ask you to install the plugin in your browser or load the page depending on if you have the plugin already.
Alexander
Thanks!
At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote:
----- Original Message -----
> From: "bigclouds" <bigclouds@163.com> > To: "Eli Mesika" <emesika@redhat.com> > Cc: "engine-devel" <engine-devel@ovirt.org> > Sent: Friday, June 7, 2013 3:49:15 AM > Subject: Re: [Engine-devel] if there is a updated debug > environment > how > to? > > hi: > there is error when engine-setup-2. finally only 8702 and 8703 > port > is > in > listen state. > i can not visit 8080 via browser.
Well, if setup fails... probably application won't work.
> engine-setup-2 > [ INFO ] Creating CA > [ INFO ] Creating database schema > [ ERROR ] Failed to execute stage 'Misc configuration': Command > '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_schema > .sh' > failed to execute > [ INFO ] Stage: Clean up > Log file is located at /tmp/ovirt-engine-setup-20130606172206.log
What database have you used? If you don't have anything important there, can you please try to initialize it so you start fresh?
# systemctl stop postgresql.service # rm -fr /var/lib/pgsql # postgresql-setup initdb # vi /var/lib/pgsql/data/pg_hba.conf modify 127.0.0.1/32 and ::1/128 lines to password at last field # su - postgres -c psql -d template1 template1=# create user engine password 'engine'; template1=# create database engine owner engine; # \q
> At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote: > >----- Original Message ----- > > > >> From: "bigclouds" <bigclouds@163.com> > >> To: "engine-devel" <engine-devel@ovirt.org> > >> Sent: Wednesday, June 5, 2013 12:34:30 PM > >> Subject: [Engine-devel] if there is a updated debug environment > >> how > >> to? > >> > >> hi, engine guys: > >> i want to make a engine debug environment for a looong time, > >> due > >> to > >> all > >> > >> kinds > >> > >> of reasons i have not made it. > >> now i still have the need for a debug environment. (it seems > >> like > >> that > >> i > >> > >> am > >> > >> keeped away from you all) > >> if there is a updated doc for building engine debug > >> environment? > >> thanks so much. > > > >Please follow Allon's B L doc on how to create a development > >environment > > > >http://www.ovirt.org/OVirt_Engine_Development_Environment > > > >> _______________________________________________ > >> Engine-devel mailing list > >> Engine-devel@ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/engine-devel > > _______________________________________________
On Friday, June 07, 2013 12:22:10 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 4:14:59 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 08:26:32 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: engine-devel@ovirt.org Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 3:09:19 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "bigclouds" <bigclouds@163.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 AM Subject: Re:Re: [Engine-devel] if there is a updated debug environment how to?
so many thinks,i finally make it.
if i can debug gwt in this environment? and how?
if this link is still in use, http://www.ovirt.org/DebugFrontend
thanks.
This is interesting, I would like to work with someone that knows GWT to make this happen.
If I read this correctly, all you need to do is:
$ make install-dev PREFIX="${HOME}/ovirt-engine" EXTRA_BUILD_FLAGS_DEV="-Pgwtdev"
And connect eclipse using the standard jboss debug port.
But I know nothing of GWT, I will appreciate help in that...
How do we connect to a running instance of jboss and debug gwt, what setting should we have?
Hi Alex,
Once you have the engine up and running as explained about, you can use http://www.ovirt.org/DebugFrontend to run GWT debugging. You can safely skip step 0 in that document (I think that needs to be updated). And start at step 1. The document explains quite well what to do, but the short version is:
1. cd into the source code directory of either webadmin or user portal. Usually: ovirt- engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true from the command line. Once it is done compiling it will tell you it is listening on port 8000.
This will not run as jboss, right?
No it is a normal java application (The GWT debugger).
Or you mean it will run on the jboss of the legacy (not the new environment). I would like a solution in which we can use the already running jboss instance that use for production in order to debug gwt. Is that possible? I guess some properties need to be passed, or new modules.
Thanks!
The GWT debugger is completely agnostic with regards to what serves the host page. The GWT debugger is connected to the browser, not the server. The host page can be served from a local JBOSS, a remote Apache, a file, whatever. The GWT debugger doesn't care as it is talking to the browser.
Can you please explain this text from the wiki:
gwt.noserver tells Development Mode that the application is already deployed on JBoss AS (don't use embedded Jetty instance to serve application content)
There are different ways of using the GWT debug mode. One of the ways is to have the GWT debugger spin up an instance of jetty and have your web application deployed in it. Then have it launch a browser with the appropriate url in it. Adding the --gwt.noserver on the command line tells GWT you don't want to spin up the jetty server, that the application you are working with is somewhere else and you will manually go to it.
Or this:
Q: Client-side logs are not persisted on Engine, e.g. $JBOSS_HOME/standalone/log/engine/engine-ui.log. A: Currently, client-side logs are enabled only when debugging the application via Development Mode.
When the application is running normally it is all just javascript running in the browser. There are 'log' statements in the code but no loggers to write the data to. When you are connected to the browser with the GWT debugger the GWT debugger provides a logger to write to.
What listens on port 8700?
In the old environment JBOSS. in the new environment nothing as JBOSS is listening on 8080 and 8443
Thanks!
IMO the only thing we could do to improve this is update the make file to provide a target to start the debugger, which basically just calls maven with the appropriate parameters.
3.In eclipse (or your favorite java IDE) make a remote java application connection to port 8000 4. Once connected this will open up a GWT debug window. 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you are working with and refresh the page. 6. It will either ask you to install the plugin in your browser or load the page depending on if you have the plugin already.
Alexander
Thanks!
At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote: >----- Original Message ----- > >> From: "bigclouds" <bigclouds@163.com> >> To: "Eli Mesika" <emesika@redhat.com> >> Cc: "engine-devel" <engine-devel@ovirt.org> >> Sent: Friday, June 7, 2013 3:49:15 AM >> Subject: Re: [Engine-devel] if there is a updated debug >> environment >> how >> to? >> >> hi: >> there is error when engine-setup-2. finally only 8702 and 8703 >> port >> is >> in >> listen state. >> i can not visit 8080 via browser. > >Well, if setup fails... probably application won't work. > >> engine-setup-2 >> [ INFO ] Creating CA >> [ INFO ] Creating database schema >> [ ERROR ] Failed to execute stage 'Misc configuration': Command >> '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_sc >> hema >> .sh' >> failed to execute >> [ INFO ] Stage: Clean up >> Log file is located at >> /tmp/ovirt-engine-setup-20130606172206.log > >What database have you used? >If you don't have anything important there, can you please try to >initialize it so you start fresh? > ># systemctl stop postgresql.service ># rm -fr /var/lib/pgsql ># postgresql-setup initdb ># vi /var/lib/pgsql/data/pg_hba.conf >modify 127.0.0.1/32 and ::1/128 lines to password at last field ># su - postgres -c psql -d template1 >template1=# create user engine password 'engine'; >template1=# create database engine owner engine; ># \q > >> At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> wrote: >> >----- Original Message ----- >> > >> >> From: "bigclouds" <bigclouds@163.com> >> >> To: "engine-devel" <engine-devel@ovirt.org> >> >> Sent: Wednesday, June 5, 2013 12:34:30 PM >> >> Subject: [Engine-devel] if there is a updated debug >> >> environment >> >> how >> >> to? >> >> >> >> hi, engine guys: >> >> i want to make a engine debug environment for a looong time, >> >> due >> >> to >> >> all >> >> >> >> kinds >> >> >> >> of reasons i have not made it. >> >> now i still have the need for a debug environment. (it seems >> >> like >> >> that >> >> i >> >> >> >> am >> >> >> >> keeped away from you all) >> >> if there is a updated doc for building engine debug >> >> environment? >> >> thanks so much. >> > >> >Please follow Allon's B L doc on how to create a development >> >environment >> > >> >http://www.ovirt.org/OVirt_Engine_Development_Environment >> > >> >> _______________________________________________ >> >> Engine-devel mailing list >> >> Engine-devel@ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> >> _______________________________________________
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 8:35:27 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 12:22:10 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 4:14:59 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 08:26:32 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: engine-devel@ovirt.org Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 3:09:19 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote:
----- Original Message -----
> From: "bigclouds" <bigclouds@163.com> > To: "Alon Bar-Lev" <alonbl@redhat.com> > Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" > <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 AM > Subject: Re:Re: [Engine-devel] if there is a updated debug > environment > how > to? > > so many thinks,i finally make it. > > if i can debug gwt in this environment? and how? > > > if this link is still in use, http://www.ovirt.org/DebugFrontend > > thanks.
This is interesting, I would like to work with someone that knows GWT to make this happen.
If I read this correctly, all you need to do is:
$ make install-dev PREFIX="${HOME}/ovirt-engine" EXTRA_BUILD_FLAGS_DEV="-Pgwtdev"
And connect eclipse using the standard jboss debug port.
But I know nothing of GWT, I will appreciate help in that...
How do we connect to a running instance of jboss and debug gwt, what setting should we have?
Hi Alex,
Once you have the engine up and running as explained about, you can use http://www.ovirt.org/DebugFrontend to run GWT debugging. You can safely skip step 0 in that document (I think that needs to be updated). And start at step 1. The document explains quite well what to do, but the short version is:
1. cd into the source code directory of either webadmin or user portal. Usually: ovirt- engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true from the command line. Once it is done compiling it will tell you it is listening on port 8000.
This will not run as jboss, right?
No it is a normal java application (The GWT debugger).
Or you mean it will run on the jboss of the legacy (not the new environment). I would like a solution in which we can use the already running jboss instance that use for production in order to debug gwt. Is that possible? I guess some properties need to be passed, or new modules.
Thanks!
The GWT debugger is completely agnostic with regards to what serves the host page. The GWT debugger is connected to the browser, not the server. The host page can be served from a local JBOSS, a remote Apache, a file, whatever. The GWT debugger doesn't care as it is talking to the browser.
Can you please explain this text from the wiki:
gwt.noserver tells Development Mode that the application is already deployed on JBoss AS (don't use embedded Jetty instance to serve application content)
There are different ways of using the GWT debug mode. One of the ways is to have the GWT debugger spin up an instance of jetty and have your web application deployed in it. Then have it launch a browser with the appropriate url in it. Adding the --gwt.noserver on the command line tells GWT you don't want to spin up the jetty server, that the application you are working with is somewhere else and you will manually go to it.
Or this:
Q: Client-side logs are not persisted on Engine, e.g. $JBOSS_HOME/standalone/log/engine/engine-ui.log. A: Currently, client-side logs are enabled only when debugging the application via Development Mode.
When the application is running normally it is all just javascript running in the browser. There are 'log' statements in the code but no loggers to write the data to. When you are connected to the browser with the GWT debugger the GWT debugger provides a logger to write to.
So how did it reached to the jboss-as log? Should I add configuration to jboss logging to have this?
What listens on port 8700?
In the old environment JBOSS. in the new environment nothing as JBOSS is listening on 8080 and 8443
OK, thanks. So if I understand correctly, the following is sequence is required: Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start Execute the gwt debugger as standalone $ mvn gwt:debug -Pgwtdev -Dgwt.noserver=true Connect eclipse gwt debugger to localhost:8000 Navigate to application, add ?gwt.codesvr=127.0.0.1:9997 as suffix, example: WebAdmin: http://127.0.0.1:8080/webadmin/webadmin/WebAdmin.html?gwt.codesvr=127.0.0.1:... UserPortal: http://127.0.0.1:8080/UserPortal/org.ovirt.engine.ui.userportal.UserPortal/U... In other words, it should not be required to re-compile the code to execute the debugger... as environment is fully deployed. Well, the above sequence is not working, I wounder what I miss in principal... the mvn gwt:debug complains about: [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug (default-cli) on project webadmin: The parameters 'runTarget' for goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug are missing or invalid -> [Help 1] Thanks!
Thanks!
IMO the only thing we could do to improve this is update the make file to provide a target to start the debugger, which basically just calls maven with the appropriate parameters.
3.In eclipse (or your favorite java IDE) make a remote java application connection to port 8000 4. Once connected this will open up a GWT debug window. 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you are working with and refresh the page. 6. It will either ask you to install the plugin in your browser or load the page depending on if you have the plugin already.
Alexander
Thanks!
> At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote: > >----- Original Message ----- > > > >> From: "bigclouds" <bigclouds@163.com> > >> To: "Eli Mesika" <emesika@redhat.com> > >> Cc: "engine-devel" <engine-devel@ovirt.org> > >> Sent: Friday, June 7, 2013 3:49:15 AM > >> Subject: Re: [Engine-devel] if there is a updated debug > >> environment > >> how > >> to? > >> > >> hi: > >> there is error when engine-setup-2. finally only 8702 and 8703 > >> port > >> is > >> in > >> listen state. > >> i can not visit 8080 via browser. > > > >Well, if setup fails... probably application won't work. > > > >> engine-setup-2 > >> [ INFO ] Creating CA > >> [ INFO ] Creating database schema > >> [ ERROR ] Failed to execute stage 'Misc configuration': > >> Command > >> '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/create_sc > >> hema > >> .sh' > >> failed to execute > >> [ INFO ] Stage: Clean up > >> Log file is located at > >> /tmp/ovirt-engine-setup-20130606172206.log > > > >What database have you used? > >If you don't have anything important there, can you please try > >to > >initialize it so you start fresh? > > > ># systemctl stop postgresql.service > ># rm -fr /var/lib/pgsql > ># postgresql-setup initdb > ># vi /var/lib/pgsql/data/pg_hba.conf > >modify 127.0.0.1/32 and ::1/128 lines to password at last field > ># su - postgres -c psql -d template1 > >template1=# create user engine password 'engine'; > >template1=# create database engine owner engine; > ># \q > > > >> At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> > >> wrote: > >> >----- Original Message ----- > >> > > >> >> From: "bigclouds" <bigclouds@163.com> > >> >> To: "engine-devel" <engine-devel@ovirt.org> > >> >> Sent: Wednesday, June 5, 2013 12:34:30 PM > >> >> Subject: [Engine-devel] if there is a updated debug > >> >> environment > >> >> how > >> >> to? > >> >> > >> >> hi, engine guys: > >> >> i want to make a engine debug environment for a looong > >> >> time, > >> >> due > >> >> to > >> >> all > >> >> > >> >> kinds > >> >> > >> >> of reasons i have not made it. > >> >> now i still have the need for a debug environment. (it > >> >> seems > >> >> like > >> >> that > >> >> i > >> >> > >> >> am > >> >> > >> >> keeped away from you all) > >> >> if there is a updated doc for building engine debug > >> >> environment? > >> >> thanks so much. > >> > > >> >Please follow Allon's B L doc on how to create a development > >> >environment > >> > > >> >http://www.ovirt.org/OVirt_Engine_Development_Environment > >> > > >> >> _______________________________________________ > >> >> Engine-devel mailing list > >> >> Engine-devel@ovirt.org > >> >> http://lists.ovirt.org/mailman/listinfo/engine-devel > >> > >> _______________________________________________
On Friday, June 07, 2013 03:20:11 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 8:35:27 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 12:22:10 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 4:14:59 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 08:26:32 AM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: engine-devel@ovirt.org Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 3:09:19 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote: > ----- Original Message ----- > > > From: "bigclouds" <bigclouds@163.com> > > To: "Alon Bar-Lev" <alonbl@redhat.com> > > Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" > > <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 > > AM > > Subject: Re:Re: [Engine-devel] if there is a updated debug > > environment > > how > > to? > > > > so many thinks,i finally make it. > > > > if i can debug gwt in this environment? and how? > > > > > > if this link is still in use, > > http://www.ovirt.org/DebugFrontend > > > > thanks. > > This is interesting, I would like to work with someone that > knows > GWT > to > make this happen. > > If I read this correctly, all you need to do is: > > $ make install-dev PREFIX="${HOME}/ovirt-engine" > EXTRA_BUILD_FLAGS_DEV="-Pgwtdev" > > And connect eclipse using the standard jboss debug port. > > But I know nothing of GWT, I will appreciate help in that... > > How do we connect to a running instance of jboss and debug gwt, > what > setting > should we have?
Hi Alex,
Once you have the engine up and running as explained about, you can use http://www.ovirt.org/DebugFrontend to run GWT debugging. You can safely skip step 0 in that document (I think that needs to be updated). And start at step 1. The document explains quite well what to do, but the short version is:
1. cd into the source code directory of either webadmin or user portal. Usually: ovirt- engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true from the command line. Once it is done compiling it will tell you it is listening on port 8000.
This will not run as jboss, right?
No it is a normal java application (The GWT debugger).
Or you mean it will run on the jboss of the legacy (not the new environment). I would like a solution in which we can use the already running jboss instance that use for production in order to debug gwt. Is that possible? I guess some properties need to be passed, or new modules.
Thanks!
The GWT debugger is completely agnostic with regards to what serves the host page. The GWT debugger is connected to the browser, not the server. The host page can be served from a local JBOSS, a remote Apache, a file, whatever. The GWT debugger doesn't care as it is talking to the browser.
Can you please explain this text from the wiki:
gwt.noserver tells Development Mode that the application is already deployed on JBoss AS (don't use embedded Jetty instance to serve application content)
There are different ways of using the GWT debug mode. One of the ways is to have the GWT debugger spin up an instance of jetty and have your web application deployed in it. Then have it launch a browser with the appropriate url in it. Adding the --gwt.noserver on the command line tells GWT you don't want to spin up the jetty server, that the application you are working with is somewhere else and you will manually go to it.
Or this:
Q: Client-side logs are not persisted on Engine, e.g. $JBOSS_HOME/standalone/log/engine/engine-ui.log. A: Currently, client-side logs are enabled only when debugging the application via Development Mode.
When the application is running normally it is all just javascript running in the browser. There are 'log' statements in the code but no loggers to write the data to. When you are connected to the browser with the GWT debugger the GWT debugger provides a logger to write to.
So how did it reached to the jboss-as log? Should I add configuration to jboss logging to have this?
What listens on port 8700?
In the old environment JBOSS. in the new environment nothing as JBOSS is listening on 8080 and 8443
OK, thanks.
So if I understand correctly, the following is sequence is required:
Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
Execute the gwt debugger as standalone $ mvn gwt:debug -Pgwtdev -Dgwt.noserver=true
Connect eclipse gwt debugger to localhost:8000
Navigate to application, add ?gwt.codesvr=127.0.0.1:9997 as suffix, example: WebAdmin: http://127.0.0.1:8080/webadmin/webadmin/WebAdmin.html?gwt.codesvr=127.0.0.1 :9997 UserPortal: http://127.0.0.1:8080/UserPortal/org.ovirt.engine.ui.userportal.UserPortal/ UserPortal.html?gwt.codesvr=127.0.0.1:9997
In other words, it should not be required to re-compile the code to execute the debugger... as environment is fully deployed.
Well, the above sequence is not working, I wounder what I miss in principal... the mvn gwt:debug complains about: [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug (default-cli) on project webadmin: The parameters 'runTarget' for goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug are missing or invalid -> [Help 1]
Thanks!
Thanks!
IMO the only thing we could do to improve this is update the make file to provide a target to start the debugger, which basically just calls maven with the appropriate parameters.
3.In eclipse (or your favorite java IDE) make a remote java application connection to port 8000 4. Once connected this will open up a GWT debug window. 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you are working with and refresh the page. 6. It will either ask you to install the plugin in your browser or load the page depending on if you have the plugin already.
Alexander
> Thanks! > > > At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote: > > >----- Original Message ----- > > > > > >> From: "bigclouds" <bigclouds@163.com> > > >> To: "Eli Mesika" <emesika@redhat.com> > > >> Cc: "engine-devel" <engine-devel@ovirt.org> > > >> Sent: Friday, June 7, 2013 3:49:15 AM > > >> Subject: Re: [Engine-devel] if there is a updated debug > > >> environment > > >> how > > >> to? > > >> > > >> hi: > > >> there is error when engine-setup-2. finally only 8702 and > > >> 8703 > > >> port > > >> is > > >> in > > >> listen state. > > >> i can not visit 8080 via browser. > > > > > >Well, if setup fails... probably application won't work. > > > > > >> engine-setup-2 > > >> [ INFO ] Creating CA > > >> [ INFO ] Creating database schema > > >> [ ERROR ] Failed to execute stage 'Misc configuration': > > >> Command > > >> '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/creat > > >> e_sc > > >> hema > > >> .sh' > > >> failed to execute > > >> [ INFO ] Stage: Clean up > > >> Log file is located at > > >> /tmp/ovirt-engine-setup-20130606172206.log > > > > > >What database have you used? > > >If you don't have anything important there, can you please > > >try > > >to > > >initialize it so you start fresh? > > > > > ># systemctl stop postgresql.service > > ># rm -fr /var/lib/pgsql > > ># postgresql-setup initdb > > ># vi /var/lib/pgsql/data/pg_hba.conf > > >modify 127.0.0.1/32 and ::1/128 lines to password at last > > >field > > ># su - postgres -c psql -d template1 > > >template1=# create user engine password 'engine'; > > >template1=# create database engine owner engine; > > ># \q > > > > > >> At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> > > >> > > >> wrote: > > >> >----- Original Message ----- > > >> > > > >> >> From: "bigclouds" <bigclouds@163.com> > > >> >> To: "engine-devel" <engine-devel@ovirt.org> > > >> >> Sent: Wednesday, June 5, 2013 12:34:30 PM > > >> >> Subject: [Engine-devel] if there is a updated debug > > >> >> environment > > >> >> how > > >> >> to? > > >> >> > > >> >> hi, engine guys: > > >> >> i want to make a engine debug environment for a looong > > >> >> time, > > >> >> due > > >> >> to > > >> >> all > > >> >> > > >> >> kinds > > >> >> > > >> >> of reasons i have not made it. > > >> >> now i still have the need for a debug environment. (it > > >> >> seems > > >> >> like > > >> >> that > > >> >> i > > >> >> > > >> >> am > > >> >> > > >> >> keeped away from you all) > > >> >> if there is a updated doc for building engine debug > > >> >> environment? > > >> >> thanks so much. > > >> > > > >> >Please follow Allon's B L doc on how to create a > > >> >development > > >> >environment > > >> > > > >> >http://www.ovirt.org/OVirt_Engine_Development_Environment > > >> > > > >> >> _______________________________________________ > > >> >> Engine-devel mailing list > > >> >> Engine-devel@ovirt.org > > >> >> http://lists.ovirt.org/mailman/listinfo/engine-devel > > >> > > >> _______________________________________________
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:27:54 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:20:11 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 8:35:27 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 12:22:10 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 4:14:59 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 08:26:32 AM Alon Bar-Lev wrote:
----- Original Message -----
> From: "Alexander Wels" <awels@redhat.com> > To: engine-devel@ovirt.org > Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" > <bigclouds@163.com> > Sent: Friday, June 7, 2013 3:09:19 PM > Subject: Re: [Engine-devel] if there is a updated debug > environment > how > to? > > On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote: > > ----- Original Message ----- > > > > > From: "bigclouds" <bigclouds@163.com> > > > To: "Alon Bar-Lev" <alonbl@redhat.com> > > > Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" > > > <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 10:29:25 > > > AM > > > Subject: Re:Re: [Engine-devel] if there is a updated debug > > > environment > > > how > > > to? > > > > > > so many thinks,i finally make it. > > > > > > if i can debug gwt in this environment? and how? > > > > > > > > > if this link is still in use, > > > http://www.ovirt.org/DebugFrontend > > > > > > thanks. > > > > This is interesting, I would like to work with someone that > > knows > > GWT > > to > > make this happen. > > > > If I read this correctly, all you need to do is: > > > > $ make install-dev PREFIX="${HOME}/ovirt-engine" > > EXTRA_BUILD_FLAGS_DEV="-Pgwtdev" > > > > And connect eclipse using the standard jboss debug port. > > > > But I know nothing of GWT, I will appreciate help in that... > > > > How do we connect to a running instance of jboss and debug gwt, > > what > > setting > > should we have?
Hi Alex,
> Once you have the engine up and running as explained about, you > can > use > http://www.ovirt.org/DebugFrontend to run GWT debugging. You can > safely > skip step 0 > in that document (I think that needs to be updated). And start at > step > 1. > The document explains quite well what to do, but the short > version > is: > > 1. cd into the source code directory of either webadmin or user > portal. > Usually: ovirt- > engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) > 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user -Dgwt.noserver=true > from > the > command line. Once it is done compiling it will tell you it is > listening > on > port 8000.
This will not run as jboss, right?
No it is a normal java application (The GWT debugger).
Or you mean it will run on the jboss of the legacy (not the new environment). I would like a solution in which we can use the already running jboss instance that use for production in order to debug gwt. Is that possible? I guess some properties need to be passed, or new modules.
Thanks!
The GWT debugger is completely agnostic with regards to what serves the host page. The GWT debugger is connected to the browser, not the server. The host page can be served from a local JBOSS, a remote Apache, a file, whatever. The GWT debugger doesn't care as it is talking to the browser.
Can you please explain this text from the wiki:
gwt.noserver tells Development Mode that the application is already deployed on JBoss AS (don't use embedded Jetty instance to serve application content)
There are different ways of using the GWT debug mode. One of the ways is to have the GWT debugger spin up an instance of jetty and have your web application deployed in it. Then have it launch a browser with the appropriate url in it. Adding the --gwt.noserver on the command line tells GWT you don't want to spin up the jetty server, that the application you are working with is somewhere else and you will manually go to it.
Or this:
Q: Client-side logs are not persisted on Engine, e.g. $JBOSS_HOME/standalone/log/engine/engine-ui.log. A: Currently, client-side logs are enabled only when debugging the application via Development Mode.
When the application is running normally it is all just javascript running in the browser. There are 'log' statements in the code but no loggers to write the data to. When you are connected to the browser with the GWT debugger the GWT debugger provides a logger to write to.
So how did it reached to the jboss-as log? Should I add configuration to jboss logging to have this?
What listens on port 8700?
In the old environment JBOSS. in the new environment nothing as JBOSS is listening on 8080 and 8443
OK, thanks.
So if I understand correctly, the following is sequence is required:
Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp
As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
Is there any reason why not to add <something> to root pom? Activating the debugger should be generic, right, I mean it should not have any dependency with specific module... the fact that we use maven for that is only as a wrapper, right?
Execute the gwt debugger as standalone $ mvn gwt:debug -Pgwtdev -Dgwt.noserver=true
Connect eclipse gwt debugger to localhost:8000
Navigate to application, add ?gwt.codesvr=127.0.0.1:9997 as suffix, example: WebAdmin: http://127.0.0.1:8080/webadmin/webadmin/WebAdmin.html?gwt.codesvr=127.0.0.1 :9997 UserPortal: http://127.0.0.1:8080/UserPortal/org.ovirt.engine.ui.userportal.UserPortal/ UserPortal.html?gwt.codesvr=127.0.0.1:9997
In other words, it should not be required to re-compile the code to execute the debugger... as environment is fully deployed.
Well, the above sequence is not working, I wounder what I miss in principal... the mvn gwt:debug complains about: [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug (default-cli) on project webadmin: The parameters 'runTarget' for goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug are missing or invalid -> [Help 1]
Thanks!
Thanks!
IMO the only thing we could do to improve this is update the make file to provide a target to start the debugger, which basically just calls maven with the appropriate parameters.
> 3.In eclipse (or your favorite java IDE) make a remote java > application > connection to > port 8000 > 4. Once connected this will open up a GWT debug window. > 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url you > are > working with and > refresh the page. > 6. It will either ask you to install the plugin in your browser > or > load > the > page depending > on if you have the plugin already. > > Alexander > > > Thanks! > > > > > At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com> wrote: > > > >----- Original Message ----- > > > > > > > >> From: "bigclouds" <bigclouds@163.com> > > > >> To: "Eli Mesika" <emesika@redhat.com> > > > >> Cc: "engine-devel" <engine-devel@ovirt.org> > > > >> Sent: Friday, June 7, 2013 3:49:15 AM > > > >> Subject: Re: [Engine-devel] if there is a updated debug > > > >> environment > > > >> how > > > >> to? > > > >> > > > >> hi: > > > >> there is error when engine-setup-2. finally only 8702 and > > > >> 8703 > > > >> port > > > >> is > > > >> in > > > >> listen state. > > > >> i can not visit 8080 via browser. > > > > > > > >Well, if setup fails... probably application won't work. > > > > > > > >> engine-setup-2 > > > >> [ INFO ] Creating CA > > > >> [ INFO ] Creating database schema > > > >> [ ERROR ] Failed to execute stage 'Misc configuration': > > > >> Command > > > >> '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/creat > > > >> e_sc > > > >> hema > > > >> .sh' > > > >> failed to execute > > > >> [ INFO ] Stage: Clean up > > > >> Log file is located at > > > >> /tmp/ovirt-engine-setup-20130606172206.log > > > > > > > >What database have you used? > > > >If you don't have anything important there, can you please > > > >try > > > >to > > > >initialize it so you start fresh? > > > > > > > ># systemctl stop postgresql.service > > > ># rm -fr /var/lib/pgsql > > > ># postgresql-setup initdb > > > ># vi /var/lib/pgsql/data/pg_hba.conf > > > >modify 127.0.0.1/32 and ::1/128 lines to password at last > > > >field > > > ># su - postgres -c psql -d template1 > > > >template1=# create user engine password 'engine'; > > > >template1=# create database engine owner engine; > > > ># \q > > > > > > > >> At 2013-06-06 05:17:07,"Eli Mesika" <emesika@redhat.com> > > > >> > > > >> wrote: > > > >> >----- Original Message ----- > > > >> > > > > >> >> From: "bigclouds" <bigclouds@163.com> > > > >> >> To: "engine-devel" <engine-devel@ovirt.org> > > > >> >> Sent: Wednesday, June 5, 2013 12:34:30 PM > > > >> >> Subject: [Engine-devel] if there is a updated debug > > > >> >> environment > > > >> >> how > > > >> >> to? > > > >> >> > > > >> >> hi, engine guys: > > > >> >> i want to make a engine debug environment for a looong > > > >> >> time, > > > >> >> due > > > >> >> to > > > >> >> all > > > >> >> > > > >> >> kinds > > > >> >> > > > >> >> of reasons i have not made it. > > > >> >> now i still have the need for a debug environment. (it > > > >> >> seems > > > >> >> like > > > >> >> that > > > >> >> i > > > >> >> > > > >> >> am > > > >> >> > > > >> >> keeped away from you all) > > > >> >> if there is a updated doc for building engine debug > > > >> >> environment? > > > >> >> thanks so much. > > > >> > > > > >> >Please follow Allon's B L doc on how to create a > > > >> >development > > > >> >environment > > > >> > > > > >> >http://www.ovirt.org/OVirt_Engine_Development_Environment > > > >> > > > > >> >> _______________________________________________ > > > >> >> Engine-devel mailing list > > > >> >> Engine-devel@ovirt.org > > > >> >> http://lists.ovirt.org/mailman/listinfo/engine-devel > > > >> > > > >> _______________________________________________
On Friday, June 07, 2013 03:51:17 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:27:54 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 03:20:11 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 8:35:27 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 12:22:10 PM Alon Bar-Lev wrote:
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 4:14:59 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
On Friday, June 07, 2013 08:26:32 AM Alon Bar-Lev wrote: > ----- Original Message ----- > > > From: "Alexander Wels" <awels@redhat.com> > > To: engine-devel@ovirt.org > > Cc: "Alon Bar-Lev" <alonbl@redhat.com>, "bigclouds" > > <bigclouds@163.com> > > Sent: Friday, June 7, 2013 3:09:19 PM > > Subject: Re: [Engine-devel] if there is a updated debug > > environment > > how > > to? > > > > On Friday, June 07, 2013 03:46:12 AM Alon Bar-Lev wrote: > > > ----- Original Message ----- > > > > > > > From: "bigclouds" <bigclouds@163.com> > > > > To: "Alon Bar-Lev" <alonbl@redhat.com> > > > > Cc: "Eli Mesika" <emesika@redhat.com>, "engine-devel" > > > > <engine-devel@ovirt.org> Sent: Friday, June 7, 2013 > > > > 10:29:25 > > > > AM > > > > Subject: Re:Re: [Engine-devel] if there is a updated debug > > > > environment > > > > how > > > > to? > > > > > > > > so many thinks,i finally make it. > > > > > > > > if i can debug gwt in this environment? and how? > > > > > > > > > > > > if this link is still in use, > > > > http://www.ovirt.org/DebugFrontend > > > > > > > > thanks. > > > > > > This is interesting, I would like to work with someone that > > > knows > > > GWT > > > to > > > make this happen. > > > > > > If I read this correctly, all you need to do is: > > > > > > $ make install-dev PREFIX="${HOME}/ovirt-engine" > > > EXTRA_BUILD_FLAGS_DEV="-Pgwtdev" > > > > > > And connect eclipse using the standard jboss debug port. > > > > > > But I know nothing of GWT, I will appreciate help in that... > > > > > > How do we connect to a running instance of jboss and debug > > > gwt, > > > what > > > setting > > > should we have? > > Hi Alex, > > > Once you have the engine up and running as explained about, > > you > > can > > use > > http://www.ovirt.org/DebugFrontend to run GWT debugging. You > > can > > safely > > skip step 0 > > in that document (I think that needs to be updated). And start > > at > > step > > 1. > > The document explains quite well what to do, but the short > > version > > is: > > > > 1. cd into the source code directory of either webadmin or > > user > > portal. > > Usually: ovirt- > > engine/frontend/webadmin/modules/(webadmin or userportal-gwtp) > > 2. mvn gwt:debug -Pgwtdev,gwt-admin,gwt-user > > -Dgwt.noserver=true > > from > > the > > command line. Once it is done compiling it will tell you it is > > listening > > on > > port 8000. > > This will not run as jboss, right?
No it is a normal java application (The GWT debugger).
> Or you mean it will run on the jboss of the legacy (not the new > environment). I would like a solution in which we can use the > already > running jboss instance that use for production in order to debug > gwt. > Is > that possible? > I guess some properties need to be passed, or new modules. > > Thanks!
The GWT debugger is completely agnostic with regards to what serves the host page. The GWT debugger is connected to the browser, not the server. The host page can be served from a local JBOSS, a remote Apache, a file, whatever. The GWT debugger doesn't care as it is talking to the browser.
Can you please explain this text from the wiki:
gwt.noserver tells Development Mode that the application is already deployed on JBoss AS (don't use embedded Jetty instance to serve application content)
There are different ways of using the GWT debug mode. One of the ways is to have the GWT debugger spin up an instance of jetty and have your web application deployed in it. Then have it launch a browser with the appropriate url in it. Adding the --gwt.noserver on the command line tells GWT you don't want to spin up the jetty server, that the application you are working with is somewhere else and you will manually go to it.
Or this:
Q: Client-side logs are not persisted on Engine, e.g. $JBOSS_HOME/standalone/log/engine/engine-ui.log. A: Currently, client-side logs are enabled only when debugging the application via Development Mode.
When the application is running normally it is all just javascript running in the browser. There are 'log' statements in the code but no loggers to write the data to. When you are connected to the browser with the GWT debugger the GWT debugger provides a logger to write to.
So how did it reached to the jboss-as log? Should I add configuration to jboss logging to have this?
What listens on port 8700?
In the old environment JBOSS. in the new environment nothing as JBOSS is listening on 8080 and 8443
OK, thanks.
So if I understand correctly, the following is sequence is required:
Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp
As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
Is there any reason why not to add <something> to root pom? Activating the debugger should be generic, right, I mean it should not have any dependency with specific module... the fact that we use maven for that is only as a wrapper, right?
Execute the gwt debugger as standalone $ mvn gwt:debug -Pgwtdev -Dgwt.noserver=true
Connect eclipse gwt debugger to localhost:8000
Navigate to application, add ?gwt.codesvr=127.0.0.1:9997 as suffix, example: WebAdmin: http://127.0.0.1:8080/webadmin/webadmin/WebAdmin.html?gwt.codesvr=127.0. 0.1
:9997 UserPortal: http://127.0.0.1:8080/UserPortal/org.ovirt.engine.ui.userportal.UserPort al/ UserPortal.html?gwt.codesvr=127.0.0.1:9997
In other words, it should not be required to re-compile the code to execute the debugger... as environment is fully deployed.
Well, the above sequence is not working, I wounder what I miss in principal... the mvn gwt:debug complains about: [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug (default-cli) on project webadmin: The parameters 'runTarget' for goal org.codehaus.mojo:gwt-maven-plugin:2.3.0:debug are missing or invalid -> [Help 1]
Thanks!
Thanks!
IMO the only thing we could do to improve this is update the make file to provide a target to start the debugger, which basically just calls maven with the appropriate parameters.
> > 3.In eclipse (or your favorite java IDE) make a remote java > > application > > connection to > > port 8000 > > 4. Once connected this will open up a GWT debug window. > > 5. In your browser as ?gwt.codesvr=127.0.0.1:9997 to the url > > you > > are > > working with and > > refresh the page. > > 6. It will either ask you to install the plugin in your > > browser > > or > > load > > the > > page depending > > on if you have the plugin already. > > > > Alexander > > > > > Thanks! > > > > > > > At 2013-06-07 14:55:41,"Alon Bar-Lev" <alonbl@redhat.com>
wrote:
> > > > >----- Original Message ----- > > > > > > > > > >> From: "bigclouds" <bigclouds@163.com> > > > > >> To: "Eli Mesika" <emesika@redhat.com> > > > > >> Cc: "engine-devel" <engine-devel@ovirt.org> > > > > >> Sent: Friday, June 7, 2013 3:49:15 AM > > > > >> Subject: Re: [Engine-devel] if there is a updated debug > > > > >> environment > > > > >> how > > > > >> to? > > > > >> > > > > >> hi: > > > > >> there is error when engine-setup-2. finally only 8702 > > > > >> and > > > > >> 8703 > > > > >> port > > > > >> is > > > > >> in > > > > >> listen state. > > > > >> i can not visit 8080 via browser. > > > > > > > > > >Well, if setup fails... probably application won't work. > > > > > > > > > >> engine-setup-2 > > > > >> [ INFO ] Creating CA > > > > >> [ INFO ] Creating database schema > > > > >> [ ERROR ] Failed to execute stage 'Misc configuration': > > > > >> Command > > > > >> '/home/best/ovirt-engine/share/ovirt-engine/dbscripts/c > > > > >> reat > > > > >> e_sc > > > > >> hema > > > > >> .sh' > > > > >> failed to execute > > > > >> [ INFO ] Stage: Clean up > > > > >> Log file is located at > > > > >> /tmp/ovirt-engine-setup-20130606172206.log > > > > > > > > > >What database have you used? > > > > >If you don't have anything important there, can you > > > > >please > > > > >try > > > > >to > > > > >initialize it so you start fresh? > > > > > > > > > ># systemctl stop postgresql.service > > > > ># rm -fr /var/lib/pgsql > > > > ># postgresql-setup initdb > > > > ># vi /var/lib/pgsql/data/pg_hba.conf > > > > >modify 127.0.0.1/32 and ::1/128 lines to password at last > > > > >field > > > > ># su - postgres -c psql -d template1 > > > > >template1=# create user engine password 'engine'; > > > > >template1=# create database engine owner engine; > > > > ># \q > > > > > > > > > >> At 2013-06-06 05:17:07,"Eli Mesika" > > > > >> <emesika@redhat.com> > > > > >> > > > > >> wrote: > > > > >> >----- Original Message ----- > > > > >> > > > > > >> >> From: "bigclouds" <bigclouds@163.com> > > > > >> >> To: "engine-devel" <engine-devel@ovirt.org> > > > > >> >> Sent: Wednesday, June 5, 2013 12:34:30 PM > > > > >> >> Subject: [Engine-devel] if there is a updated debug > > > > >> >> environment > > > > >> >> how > > > > >> >> to? > > > > >> >> > > > > >> >> hi, engine guys: > > > > >> >> i want to make a engine debug environment for a > > > > >> >> looong > > > > >> >> time, > > > > >> >> due > > > > >> >> to > > > > >> >> all > > > > >> >> > > > > >> >> kinds > > > > >> >> > > > > >> >> of reasons i have not made it. > > > > >> >> now i still have the need for a debug environment. > > > > >> >> (it > > > > >> >> seems > > > > >> >> like > > > > >> >> that > > > > >> >> i > > > > >> >> > > > > >> >> am > > > > >> >> > > > > >> >> keeped away from you all) > > > > >> >> if there is a updated doc for building engine debug > > > > >> >> environment? > > > > >> >> thanks so much. > > > > >> > > > > > >> >Please follow Allon's B L doc on how to create a > > > > >> >development > > > > >> >environment > > > > >> > > > > > >> >http://www.ovirt.org/OVirt_Engine_Development_Environm > > > > >> >ent > > > > >> > > > > > >> >> _______________________________________________ > > > > >> >> Engine-devel mailing list > > > > >> >> Engine-devel@ovirt.org > > > > >> >> http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > >> > > > > >> _______________________________________________
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:56:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
So if I understand correctly, the following is sequence is required:
Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp
As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
You perceive this as something of gwt project, while I perceive this part of the environment. What I expect it to allow as simple development environment as we can. Just like I enable the debug port of jboss automatically I would like to enable gwt debug. If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using: $ make install-dev PREFIX="${HOME}/ovirt-engine" I can even add GWT_DEBUGGER=1 to optionally enable/disable this feature. Now, after starting ovirt-engine service, all I expect is a simple command to start the gwt debugger. $ make gwt-debugger or: ./gwt-debugger The fact that maven is used to start the debugger is not important. What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal). I would have understood if I had to execute something like the following to run the debugger: $ cd frontend $ mvn gwt:debug -Dgwt.noserver=true Or better to avoid building anything: $ cd frontend/debugger $ mvn gwt:debug -Dgwt.noserver=true But I do not understand why a cd to specific application is required. Thanks! Alon
Hi Alon, revisiting this thread, I have some comments regarding GWT debugging via standard development environment, as described in README.developer. - README.developer says: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt-plugin.localWorkers=2" however this should be: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt.compiler.localWorkers=2" - README.developer says: By default, only the gecko1_8 support is built I'd rather explain what this means: By default, only the gecko1_8 (Mozilla Firefox) support is built - what's the point of having EXTRA_BUILD_FLAGS_DEV_GWT vs. EXTRA_BUILD_FLAGS_DEV ? if EXTRA_BUILD_FLAGS_DEV_GWT is meant to control target browser(s) then it should be renamed appropriately if EXTRA_BUILD_FLAGS_DEV_GWT is meant to group all GWT-specific flags, README.developer shouldn't advise to do EXTRA_BUILD_FLAGS_DEV="-Dgwt..." - Makefile gwt-debug target looks OK to me
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
gwt-maven-plugin must be invoked in context of a specific Maven module representing GWT application you want to debug. In other words, you need to start GWT Development Mode for specific application module. This is why you need to "cd" to specific directory (webadmin/userportal-gwtp) before invoking "mvn ... gwt:debug" command. You cannot start GWT Development Mode in a generic (application-agnostic) way and *then* connect to it from browser and Java IDE, this is not how GWT Development Mode is meant to be used. JBoss remote socket debugging and GWT application debugging are two different things.
The fact that maven is used to start the debugger is not important.
gwt-maven-plugin is just a wrapper to invoke GWT Development Mode (Java class). Regardless of how you start GWT Development Mode, you need to specify which application (more precisely, GWT modules) you want to debug right when starting GWT Development Mode. See [1] - "module(s)" are always specific for given application. [1] https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDeb...
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
Yes, as described in [2], besides using "gwtdev" profile for debugging, it can also be used for GWT compilation (i.e. "make install-dev") - in this case, resulting JavaScript will be un-obfuscated and not-too-optimized in order to easily profile the JavaScript application in the browser. In other words, using "gwtdev" for GWT compilation has nothing to do with debugging, maybe we should create separate profile for this purpose. [2] http://www.ovirt.org/DebugFrontend#Compiling_Frontend_applications_in_detail... PS: I'll update http://www.ovirt.org/DebugFrontend with regard to standard development environment, as described in README.developer Vojtech ----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: awels@redhat.com Cc: engine-devel@ovirt.org Sent: Friday, June 7, 2013 10:07:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:56:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
So if I understand correctly, the following is sequence is required:
Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp
As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
You perceive this as something of gwt project, while I perceive this part of the environment.
What I expect it to allow as simple development environment as we can. Just like I enable the debug port of jboss automatically I would like to enable gwt debug.
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
$ make install-dev PREFIX="${HOME}/ovirt-engine"
I can even add GWT_DEBUGGER=1 to optionally enable/disable this feature.
Now, after starting ovirt-engine service, all I expect is a simple command to start the gwt debugger.
$ make gwt-debugger or: ./gwt-debugger
The fact that maven is used to start the debugger is not important.
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
I would have understood if I had to execute something like the following to run the debugger:
$ cd frontend $ mvn gwt:debug -Dgwt.noserver=true
Or better to avoid building anything:
$ cd frontend/debugger $ mvn gwt:debug -Dgwt.noserver=true
But I do not understand why a cd to specific application is required.
Thanks! Alon _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
----- Original Message -----
From: "Vojtech Szocs" <vszocs@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 2:01:01 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
Hi Alon,
revisiting this thread, I have some comments regarding GWT debugging via standard development environment, as described in README.developer.
Thank you for your comments! As the file is within git, you can submit a patch... :) I will create one for the following comments.
- README.developer says: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt-plugin.localWorkers=2" however this should be: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt.compiler.localWorkers=2"
Fixed.
- README.developer says: By default, only the gecko1_8 support is built I'd rather explain what this means: By default, only the gecko1_8 (Mozilla Firefox) support is built
Fixed.
- what's the point of having EXTRA_BUILD_FLAGS_DEV_GWT vs. EXTRA_BUILD_FLAGS_DEV ?
I wanted to allow customization of GWT as standalone as it require more flags and defaults. So I can put the following with a default for gwt while allowing application customization. For example if I have: EXTRA_BUILD_FLAGS_DEV_GWT:=-D gwt.userAgent=gecko1_8 and execute: $ make EXTRA_BUILD_FLAGS_DEV="-DskipTests" I do not override the GWT settings. BTW: there is a pending patch to rename this to DEV_XXXX[1] to be more consistent. [1] http://gerrit.ovirt.org/#/c/15735/
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to control target browser(s) then it should be renamed appropriately
Any flags, including debug port and such. But I am opened to suggestions... what do you expect it to be named?
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to group all GWT-specific flags, README.developer shouldn't advise to do EXTRA_BUILD_FLAGS_DEV="-Dgwt..."
But then I lose the gwt settings.
- Makefile gwt-debug target looks OK to me
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
gwt-maven-plugin must be invoked in context of a specific Maven module representing GWT application you want to debug. In other words, you need to start GWT Development Mode for specific application module. This is why you need to "cd" to specific directory (webadmin/userportal-gwtp) before invoking "mvn ... gwt:debug" command.
You cannot start GWT Development Mode in a generic (application-agnostic) way and *then* connect to it from browser and Java IDE, this is not how GWT Development Mode is meant to be used. JBoss remote socket debugging and GWT application debugging are two different things.
Well, I do expect this to be a feature of top level pom.xml... something like: $ mvn -Pgwt-debug -Ddebug.module=webadmin so that the profile will do whatever necessary to activate the debugger.
The fact that maven is used to start the debugger is not important.
gwt-maven-plugin is just a wrapper to invoke GWT Development Mode (Java class). Regardless of how you start GWT Development Mode, you need to specify which application (more precisely, GWT modules) you want to debug right when starting GWT Development Mode. See [1] - "module(s)" are always specific for given application.
So basically what you saying is that you cannot debug two modules at one time... It is strange... but as long as you fine with it, we are OK.
[1] https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDeb...
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
Yes, as described in [2], besides using "gwtdev" profile for debugging, it can also be used for GWT compilation (i.e. "make install-dev") - in this case, resulting JavaScript will be un-obfuscated and not-too-optimized in order to easily profile the JavaScript application in the browser. In other words, using "gwtdev" for GWT compilation has nothing to do with debugging, maybe we should create separate profile for this purpose.
That's good.
[2] http://www.ovirt.org/DebugFrontend#Compiling_Frontend_applications_in_detail...
PS: I'll update http://www.ovirt.org/DebugFrontend with regard to standard development environment, as described in README.developer
Vojtech
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: awels@redhat.com Cc: engine-devel@ovirt.org Sent: Friday, June 7, 2013 10:07:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:56:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
So if I understand correctly, the following is sequence is required:
Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp
As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
You perceive this as something of gwt project, while I perceive this part of the environment.
What I expect it to allow as simple development environment as we can. Just like I enable the debug port of jboss automatically I would like to enable gwt debug.
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
$ make install-dev PREFIX="${HOME}/ovirt-engine"
I can even add GWT_DEBUGGER=1 to optionally enable/disable this feature.
Now, after starting ovirt-engine service, all I expect is a simple command to start the gwt debugger.
$ make gwt-debugger or: ./gwt-debugger
The fact that maven is used to start the debugger is not important.
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
I would have understood if I had to execute something like the following to run the debugger:
$ cd frontend $ mvn gwt:debug -Dgwt.noserver=true
Or better to avoid building anything:
$ cd frontend/debugger $ mvn gwt:debug -Dgwt.noserver=true
But I do not understand why a cd to specific application is required.
Thanks! Alon _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "Vojtech Szocs" <vszocs@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 1:32:52 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Vojtech Szocs" <vszocs@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 2:01:01 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
Hi Alon,
revisiting this thread, I have some comments regarding GWT debugging via standard development environment, as described in README.developer.
Thank you for your comments! As the file is within git, you can submit a patch... :) I will create one for the following comments.
Thanks! I +2'ed your patch [http://gerrit.ovirt.org/#/c/15827/]
- README.developer says: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt-plugin.localWorkers=2" however this should be: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt.compiler.localWorkers=2"
Fixed.
- README.developer says: By default, only the gecko1_8 support is built I'd rather explain what this means: By default, only the gecko1_8 (Mozilla Firefox) support is built
Fixed.
- what's the point of having EXTRA_BUILD_FLAGS_DEV_GWT vs. EXTRA_BUILD_FLAGS_DEV ?
I wanted to allow customization of GWT as standalone as it require more flags and defaults.
So I can put the following with a default for gwt while allowing application customization.
For example if I have: EXTRA_BUILD_FLAGS_DEV_GWT:=-D gwt.userAgent=gecko1_8
and execute: $ make EXTRA_BUILD_FLAGS_DEV="-DskipTests"
I do not override the GWT settings.
I see, so developer should only use EXTRA_BUILD_FLAGS_DEV to provide any additional settings (or override existing settings), i.e. both GWT and non-GWT settings can be customized via EXTRA_BUILD_FLAGS_DEV. If I understand correctly, EXTRA_BUILD_FLAGS_DEV_GWT is used internally for: - setting default target browser to Firefox (only) - enabling draft compile (if DEV_BUILD_GWT_DRAFT == 1) We can consider renaming EXTRA_BUILD_FLAGS_DEV_GWT -> EXTRA_BUILD_FLAGS_DEV_GWT_DEFAULTS. But in any case, I suggest to apply EXTRA_BUILD_FLAGS_DEV_GWT *before* EXTRA_BUILD_FLAGS_DEV (instead of the opposite like today). This way, EXTRA_BUILD_FLAGS_DEV can be used to override any settings set by EXTRA_BUILD_FLAGS_DEV_GWT. For example: $(MVN) \ $(EXTRA_BUILD_FLAGS_DEV_GWT) \ --> GWT-specific defaults $(EXTRA_BUILD_FLAGS_DEV) \ --> generic overrides (both GWT and non-GWT) ... install \ EXTRA_BUILD_FLAGS="$(EXTRA_BUILD_FLAGS_DEV_GWT) $(EXTRA_BUILD_FLAGS_DEV)" \ --> this one is OK Let me know what you think about this.
BTW: there is a pending patch to rename this to DEV_XXXX[1] to be more consistent.
+1'ed this patch.
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to control target browser(s) then it should be renamed appropriately
Any flags, including debug port and such. But I am opened to suggestions... what do you expect it to be named?
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to group all GWT-specific flags, README.developer shouldn't advise to do EXTRA_BUILD_FLAGS_DEV="-Dgwt..."
But then I lose the gwt settings.
Right, please see my suggestion above.
- Makefile gwt-debug target looks OK to me
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
gwt-maven-plugin must be invoked in context of a specific Maven module representing GWT application you want to debug. In other words, you need to start GWT Development Mode for specific application module. This is why you need to "cd" to specific directory (webadmin/userportal-gwtp) before invoking "mvn ... gwt:debug" command.
You cannot start GWT Development Mode in a generic (application-agnostic) way and *then* connect to it from browser and Java IDE, this is not how GWT Development Mode is meant to be used. JBoss remote socket debugging and GWT application debugging are two different things.
Well, I do expect this to be a feature of top level pom.xml...
something like: $ mvn -Pgwt-debug -Ddebug.module=webadmin
so that the profile will do whatever necessary to activate the debugger.
This would be problematic because when you invoke Maven on root pom, Maven only sees root pom classpath/artifacts, and we need Maven/GWT-Plugin to see application-specific classpath/artifacts. I'm not saying this is impossible, I'm just saying it will be much harder to do than just "cd" to webadmin/userportal-gwtp directory and invoking Maven there.. We could introduce new flags like DEBUG_GWT_WEBADMIN [0/1] which would take care of providing correct settings to gwt-maven-plugin, not sure if it's really worth it, because we already have DEBUG_MODULE and Makefile internally cd's to it.
The fact that maven is used to start the debugger is not important.
gwt-maven-plugin is just a wrapper to invoke GWT Development Mode (Java class). Regardless of how you start GWT Development Mode, you need to specify which application (more precisely, GWT modules) you want to debug right when starting GWT Development Mode. See [1] - "module(s)" are always specific for given application.
So basically what you saying is that you cannot debug two modules at one time... It is strange... but as long as you fine with it, we are OK.
Yes, basically you need to specify all "modules" that make up for one application at time when you start GWT Development Mode. So GWT Development Mode, once started, is tied to specific application.
[1] https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDeb...
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
Yes, as described in [2], besides using "gwtdev" profile for debugging, it can also be used for GWT compilation (i.e. "make install-dev") - in this case, resulting JavaScript will be un-obfuscated and not-too-optimized in order to easily profile the JavaScript application in the browser. In other words, using "gwtdev" for GWT compilation has nothing to do with debugging, maybe we should create separate profile for this purpose.
That's good.
OK, I'll make a patch to introduce "gwtdraft" profile with following effects once activated (via -Pgwtdraft): - set draftCompile to true -> prevent JavaScript code optimizations - set style to DETAILED -> produce pretty JavaScript without obfuscation After this, I suggest to modify Makefile so that DEV_BUILD_GWT_DRAFT=1 activates "gwtdraft" profile, instead of just doing -Dgwt.draftCompile=true
[2] http://www.ovirt.org/DebugFrontend#Compiling_Frontend_applications_in_detail...
PS: I'll update http://www.ovirt.org/DebugFrontend with regard to standard development environment, as described in README.developer
Vojtech
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: awels@redhat.com Cc: engine-devel@ovirt.org Sent: Friday, June 7, 2013 10:07:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:56:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
> So if I understand correctly, the following is sequence is > required: > > Build and deploy code: > $ make install-dev PREFIX="${HOME}/ovirt-engine" > $ > "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" > start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp
As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
You perceive this as something of gwt project, while I perceive this part of the environment.
What I expect it to allow as simple development environment as we can. Just like I enable the debug port of jboss automatically I would like to enable gwt debug.
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
$ make install-dev PREFIX="${HOME}/ovirt-engine"
I can even add GWT_DEBUGGER=1 to optionally enable/disable this feature.
Now, after starting ovirt-engine service, all I expect is a simple command to start the gwt debugger.
$ make gwt-debugger or: ./gwt-debugger
The fact that maven is used to start the debugger is not important.
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
I would have understood if I had to execute something like the following to run the debugger:
$ cd frontend $ mvn gwt:debug -Dgwt.noserver=true
Or better to avoid building anything:
$ cd frontend/debugger $ mvn gwt:debug -Dgwt.noserver=true
But I do not understand why a cd to specific application is required.
Thanks! Alon _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
----- Original Message -----
From: "Vojtech Szocs" <vszocs@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 4:16:25 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "Vojtech Szocs" <vszocs@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 1:32:52 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Vojtech Szocs" <vszocs@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 2:01:01 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
Hi Alon,
revisiting this thread, I have some comments regarding GWT debugging via standard development environment, as described in README.developer.
Thank you for your comments! As the file is within git, you can submit a patch... :) I will create one for the following comments.
Thanks! I +2'ed your patch [http://gerrit.ovirt.org/#/c/15827/]
- README.developer says: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt-plugin.localWorkers=2" however this should be: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt.compiler.localWorkers=2"
Fixed.
- README.developer says: By default, only the gecko1_8 support is built I'd rather explain what this means: By default, only the gecko1_8 (Mozilla Firefox) support is built
Fixed.
- what's the point of having EXTRA_BUILD_FLAGS_DEV_GWT vs. EXTRA_BUILD_FLAGS_DEV ?
I wanted to allow customization of GWT as standalone as it require more flags and defaults.
So I can put the following with a default for gwt while allowing application customization.
For example if I have: EXTRA_BUILD_FLAGS_DEV_GWT:=-D gwt.userAgent=gecko1_8
and execute: $ make EXTRA_BUILD_FLAGS_DEV="-DskipTests"
I do not override the GWT settings.
I see, so developer should only use EXTRA_BUILD_FLAGS_DEV to provide any additional settings (or override existing settings), i.e. both GWT and non-GWT settings can be customized via EXTRA_BUILD_FLAGS_DEV.
If I understand correctly, EXTRA_BUILD_FLAGS_DEV_GWT is used internally for: - setting default target browser to Firefox (only)
Right.
- enabling draft compile (if DEV_BUILD_GWT_DRAFT == 1)
I am going to change that[1] [1] http://gerrit.ovirt.org/#/c/15736/
We can consider renaming EXTRA_BUILD_FLAGS_DEV_GWT -> EXTRA_BUILD_FLAGS_DEV_GWT_DEFAULTS.
OK, will do.
But in any case, I suggest to apply EXTRA_BUILD_FLAGS_DEV_GWT *before* EXTRA_BUILD_FLAGS_DEV (instead of the opposite like today). This way, EXTRA_BUILD_FLAGS_DEV can be used to override any settings set by EXTRA_BUILD_FLAGS_DEV_GWT.
For example:
$(MVN) \ $(EXTRA_BUILD_FLAGS_DEV_GWT) \ --> GWT-specific defaults $(EXTRA_BUILD_FLAGS_DEV) \ --> generic overrides (both GWT and non-GWT) ...
install \ EXTRA_BUILD_FLAGS="$(EXTRA_BUILD_FLAGS_DEV_GWT) $(EXTRA_BUILD_FLAGS_DEV)" \ --> this one is OK
Let me know what you think about this.
Good for me.
BTW: there is a pending patch to rename this to DEV_XXXX[1] to be more consistent.
+1'ed this patch.
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to control target browser(s) then it should be renamed appropriately
Any flags, including debug port and such. But I am opened to suggestions... what do you expect it to be named?
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to group all GWT-specific flags, README.developer shouldn't advise to do EXTRA_BUILD_FLAGS_DEV="-Dgwt..."
But then I lose the gwt settings.
Right, please see my suggestion above.
- Makefile gwt-debug target looks OK to me
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
gwt-maven-plugin must be invoked in context of a specific Maven module representing GWT application you want to debug. In other words, you need to start GWT Development Mode for specific application module. This is why you need to "cd" to specific directory (webadmin/userportal-gwtp) before invoking "mvn ... gwt:debug" command.
You cannot start GWT Development Mode in a generic (application-agnostic) way and *then* connect to it from browser and Java IDE, this is not how GWT Development Mode is meant to be used. JBoss remote socket debugging and GWT application debugging are two different things.
Well, I do expect this to be a feature of top level pom.xml...
something like: $ mvn -Pgwt-debug -Ddebug.module=webadmin
so that the profile will do whatever necessary to activate the debugger.
This would be problematic because when you invoke Maven on root pom, Maven only sees root pom classpath/artifacts, and we need Maven/GWT-Plugin to see application-specific classpath/artifacts.
I'm not saying this is impossible, I'm just saying it will be much harder to do than just "cd" to webadmin/userportal-gwtp directory and invoking Maven there.. We could introduce new flags like DEBUG_GWT_WEBADMIN [0/1] which would take care of providing correct settings to gwt-maven-plugin, not sure if it's really worth it, because we already have DEBUG_MODULE and Makefile internally cd's to it.
OK, this issue is not that important now... :)
The fact that maven is used to start the debugger is not important.
gwt-maven-plugin is just a wrapper to invoke GWT Development Mode (Java class). Regardless of how you start GWT Development Mode, you need to specify which application (more precisely, GWT modules) you want to debug right when starting GWT Development Mode. See [1] - "module(s)" are always specific for given application.
So basically what you saying is that you cannot debug two modules at one time... It is strange... but as long as you fine with it, we are OK.
Yes, basically you need to specify all "modules" that make up for one application at time when you start GWT Development Mode. So GWT Development Mode, once started, is tied to specific application.
[1] https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDeb...
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
Yes, as described in [2], besides using "gwtdev" profile for debugging, it can also be used for GWT compilation (i.e. "make install-dev") - in this case, resulting JavaScript will be un-obfuscated and not-too-optimized in order to easily profile the JavaScript application in the browser. In other words, using "gwtdev" for GWT compilation has nothing to do with debugging, maybe we should create separate profile for this purpose.
That's good.
OK, I'll make a patch to introduce "gwtdraft" profile with following effects once activated (via -Pgwtdraft): - set draftCompile to true -> prevent JavaScript code optimizations - set style to DETAILED -> produce pretty JavaScript without obfuscation
After this, I suggest to modify Makefile so that DEV_BUILD_GWT_DRAFT=1 activates "gwtdraft" profile, instead of just doing -Dgwt.draftCompile=true
[2] http://www.ovirt.org/DebugFrontend#Compiling_Frontend_applications_in_detail...
PS: I'll update http://www.ovirt.org/DebugFrontend with regard to standard development environment, as described in README.developer
Vojtech
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: awels@redhat.com Cc: engine-devel@ovirt.org Sent: Friday, June 7, 2013 10:07:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:56:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
> > So if I understand correctly, the following is sequence is > > required: > > > > Build and deploy code: > > $ make install-dev PREFIX="${HOME}/ovirt-engine" > > $ > > "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" > > start > > You missed this part: > 1. cd into the source code directory of either webadmin or user > portal. > you have to change directory to either > frontend/webadmin/modules/webadmin > or frontend/webadmin/modules/userportal-gwtp > > As the maven gwt plugin is only defined in the webadmin and > userportal > poms > and > not in the root pom.
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
You perceive this as something of gwt project, while I perceive this part of the environment.
What I expect it to allow as simple development environment as we can. Just like I enable the debug port of jboss automatically I would like to enable gwt debug.
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
$ make install-dev PREFIX="${HOME}/ovirt-engine"
I can even add GWT_DEBUGGER=1 to optionally enable/disable this feature.
Now, after starting ovirt-engine service, all I expect is a simple command to start the gwt debugger.
$ make gwt-debugger or: ./gwt-debugger
The fact that maven is used to start the debugger is not important.
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
I would have understood if I had to execute something like the following to run the debugger:
$ cd frontend $ mvn gwt:debug -Dgwt.noserver=true
Or better to avoid building anything:
$ cd frontend/debugger $ mvn gwt:debug -Dgwt.noserver=true
But I do not understand why a cd to specific application is required.
Thanks! Alon _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "Vojtech Szocs" <vszocs@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 4:56:49 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Vojtech Szocs" <vszocs@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 4:16:25 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "Vojtech Szocs" <vszocs@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 1:32:52 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Vojtech Szocs" <vszocs@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: awels@redhat.com, engine-devel@ovirt.org Sent: Tuesday, June 18, 2013 2:01:01 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
Hi Alon,
revisiting this thread, I have some comments regarding GWT debugging via standard development environment, as described in README.developer.
Thank you for your comments! As the file is within git, you can submit a patch... :) I will create one for the following comments.
Thanks! I +2'ed your patch [http://gerrit.ovirt.org/#/c/15827/]
- README.developer says: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt-plugin.localWorkers=2" however this should be: For example, if your machine is low on memory, use: EXTRA_BUILD_FLAGS_DEV="-Dgwt.compiler.localWorkers=2"
Fixed.
- README.developer says: By default, only the gecko1_8 support is built I'd rather explain what this means: By default, only the gecko1_8 (Mozilla Firefox) support is built
Fixed.
- what's the point of having EXTRA_BUILD_FLAGS_DEV_GWT vs. EXTRA_BUILD_FLAGS_DEV ?
I wanted to allow customization of GWT as standalone as it require more flags and defaults.
So I can put the following with a default for gwt while allowing application customization.
For example if I have: EXTRA_BUILD_FLAGS_DEV_GWT:=-D gwt.userAgent=gecko1_8
and execute: $ make EXTRA_BUILD_FLAGS_DEV="-DskipTests"
I do not override the GWT settings.
I see, so developer should only use EXTRA_BUILD_FLAGS_DEV to provide any additional settings (or override existing settings), i.e. both GWT and non-GWT settings can be customized via EXTRA_BUILD_FLAGS_DEV.
If I understand correctly, EXTRA_BUILD_FLAGS_DEV_GWT is used internally for: - setting default target browser to Firefox (only)
Right.
- enabling draft compile (if DEV_BUILD_GWT_DRAFT == 1)
I am going to change that[1]
[1] http://gerrit.ovirt.org/#/c/15736/
We can consider renaming EXTRA_BUILD_FLAGS_DEV_GWT -> EXTRA_BUILD_FLAGS_DEV_GWT_DEFAULTS.
OK, will do.
But in any case, I suggest to apply EXTRA_BUILD_FLAGS_DEV_GWT *before* EXTRA_BUILD_FLAGS_DEV (instead of the opposite like today). This way, EXTRA_BUILD_FLAGS_DEV can be used to override any settings set by EXTRA_BUILD_FLAGS_DEV_GWT.
For example:
$(MVN) \ $(EXTRA_BUILD_FLAGS_DEV_GWT) \ --> GWT-specific defaults $(EXTRA_BUILD_FLAGS_DEV) \ --> generic overrides (both GWT and non-GWT) ...
install \ EXTRA_BUILD_FLAGS="$(EXTRA_BUILD_FLAGS_DEV_GWT) $(EXTRA_BUILD_FLAGS_DEV)" \ --> this one is OK
Let me know what you think about this.
Good for me.
After http://gerrit.ovirt.org/#/c/15736/ gets merged, I can make a patch that modifies this: DEV_BUILD_FLAGS:=$(DEV_BUILD_FLAGS) $(DEV_EXTRA_BUILD_FLAGS) DEV_BUILD_FLAGS:=$(DEV_BUILD_FLAGS) $(DEV_EXTRA_BUILD_FLAGS_GWT) to this: DEV_BUILD_FLAGS:=$(DEV_BUILD_FLAGS) $(DEV_EXTRA_BUILD_FLAGS_GWT) DEV_BUILD_FLAGS:=$(DEV_BUILD_FLAGS) $(DEV_EXTRA_BUILD_FLAGS) otherwise, it looks good to me.
BTW: there is a pending patch to rename this to DEV_XXXX[1] to be more consistent.
+1'ed this patch.
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to control target browser(s) then it should be renamed appropriately
Any flags, including debug port and such. But I am opened to suggestions... what do you expect it to be named?
if EXTRA_BUILD_FLAGS_DEV_GWT is meant to group all GWT-specific flags, README.developer shouldn't advise to do EXTRA_BUILD_FLAGS_DEV="-Dgwt..."
But then I lose the gwt settings.
Right, please see my suggestion above.
- Makefile gwt-debug target looks OK to me
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
gwt-maven-plugin must be invoked in context of a specific Maven module representing GWT application you want to debug. In other words, you need to start GWT Development Mode for specific application module. This is why you need to "cd" to specific directory (webadmin/userportal-gwtp) before invoking "mvn ... gwt:debug" command.
You cannot start GWT Development Mode in a generic (application-agnostic) way and *then* connect to it from browser and Java IDE, this is not how GWT Development Mode is meant to be used. JBoss remote socket debugging and GWT application debugging are two different things.
Well, I do expect this to be a feature of top level pom.xml...
something like: $ mvn -Pgwt-debug -Ddebug.module=webadmin
so that the profile will do whatever necessary to activate the debugger.
This would be problematic because when you invoke Maven on root pom, Maven only sees root pom classpath/artifacts, and we need Maven/GWT-Plugin to see application-specific classpath/artifacts.
I'm not saying this is impossible, I'm just saying it will be much harder to do than just "cd" to webadmin/userportal-gwtp directory and invoking Maven there.. We could introduce new flags like DEBUG_GWT_WEBADMIN [0/1] which would take care of providing correct settings to gwt-maven-plugin, not sure if it's really worth it, because we already have DEBUG_MODULE and Makefile internally cd's to it.
OK, this issue is not that important now... :)
The fact that maven is used to start the debugger is not important.
gwt-maven-plugin is just a wrapper to invoke GWT Development Mode (Java class). Regardless of how you start GWT Development Mode, you need to specify which application (more precisely, GWT modules) you want to debug right when starting GWT Development Mode. See [1] - "module(s)" are always specific for given application.
So basically what you saying is that you cannot debug two modules at one time... It is strange... but as long as you fine with it, we are OK.
Yes, basically you need to specify all "modules" that make up for one application at time when you start GWT Development Mode. So GWT Development Mode, once started, is tied to specific application.
[1] https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDeb...
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
Yes, as described in [2], besides using "gwtdev" profile for debugging, it can also be used for GWT compilation (i.e. "make install-dev") - in this case, resulting JavaScript will be un-obfuscated and not-too-optimized in order to easily profile the JavaScript application in the browser. In other words, using "gwtdev" for GWT compilation has nothing to do with debugging, maybe we should create separate profile for this purpose.
That's good.
OK, I'll make a patch to introduce "gwtdraft" profile with following effects once activated (via -Pgwtdraft): - set draftCompile to true -> prevent JavaScript code optimizations - set style to DETAILED -> produce pretty JavaScript without obfuscation
After this, I suggest to modify Makefile so that DEV_BUILD_GWT_DRAFT=1 activates "gwtdraft" profile, instead of just doing -Dgwt.draftCompile=true
[2] http://www.ovirt.org/DebugFrontend#Compiling_Frontend_applications_in_detail...
PS: I'll update http://www.ovirt.org/DebugFrontend with regard to standard development environment, as described in README.developer
Vojtech
----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: awels@redhat.com Cc: engine-devel@ovirt.org Sent: Friday, June 7, 2013 10:07:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:56:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
> > > So if I understand correctly, the following is sequence is > > > required: > > > > > > Build and deploy code: > > > $ make install-dev PREFIX="${HOME}/ovirt-engine" > > > $ > > > "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" > > > start > > > > You missed this part: > > 1. cd into the source code directory of either webadmin or user > > portal. > > you have to change directory to either > > frontend/webadmin/modules/webadmin > > or frontend/webadmin/modules/userportal-gwtp > > > > As the maven gwt plugin is only defined in the webadmin and > > userportal > > poms > > and > > not in the root pom. >
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
You perceive this as something of gwt project, while I perceive this part of the environment.
What I expect it to allow as simple development environment as we can. Just like I enable the debug port of jboss automatically I would like to enable gwt debug.
If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using:
$ make install-dev PREFIX="${HOME}/ovirt-engine"
I can even add GWT_DEBUGGER=1 to optionally enable/disable this feature.
Now, after starting ovirt-engine service, all I expect is a simple command to start the gwt debugger.
$ make gwt-debugger or: ./gwt-debugger
The fact that maven is used to start the debugger is not important.
What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal).
I would have understood if I had to execute something like the following to run the debugger:
$ cd frontend $ mvn gwt:debug -Dgwt.noserver=true
Or better to avoid building anything:
$ cd frontend/debugger $ mvn gwt:debug -Dgwt.noserver=true
But I do not understand why a cd to specific application is required.
Thanks! Alon _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (5)
-
Alexander Wels -
Alon Bar-Lev -
bigclouds -
Eli Mesika -
Vojtech Szocs