[Engine-devel] if there is a updated debug environment how to?

Alon Bar-Lev alonbl at redhat.com
Fri Jun 7 19:51:17 UTC 2013 


----- Original Message -----
> From: "Alexander Wels" <awels at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: engine-devel at ovirt.org, "bigclouds" <bigclouds at 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 at redhat.com>
> > > To: "Alon Bar-Lev" <alonbl at redhat.com>
> > > Cc: engine-devel at ovirt.org, "bigclouds" <bigclouds at 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 at redhat.com>
> > > > > To: "Alon Bar-Lev" <alonbl at redhat.com>
> > > > > Cc: engine-devel at ovirt.org, "bigclouds" <bigclouds at 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 at redhat.com>
> > > > > > > To: engine-devel at ovirt.org
> > > > > > > Cc: "Alon Bar-Lev" <alonbl at redhat.com>, "bigclouds"
> > > > > > > <bigclouds at 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 at 163.com>
> > > > > > > > > To: "Alon Bar-Lev" <alonbl at redhat.com>
> > > > > > > > > Cc: "Eli Mesika" <emesika at redhat.com>, "engine-devel"
> > > > > > > > > <engine-devel at 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 at redhat.com>
> wrote:
> > > > > > > > > >----- Original Message -----
> > > > > > > > > >
> > > > > > > > > >> From: "bigclouds" <bigclouds at 163.com>
> > > > > > > > > >> To: "Eli Mesika" <emesika at redhat.com>
> > > > > > > > > >> Cc: "engine-devel" <engine-devel at 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 at redhat.com>
> > > > > > > > > >> 
> > > > > > > > > >> wrote:
> > > > > > > > > >> >----- Original Message -----
> > > > > > > > > >> >
> > > > > > > > > >> >> From: "bigclouds" <bigclouds at 163.com>
> > > > > > > > > >> >> To: "engine-devel" <engine-devel at 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 at ovirt.org
> > > > > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/engine-devel
> > > > > > > > > >> 
> > > > > > > > > >> _______________________________________________
>

More information about the Devel mailing list