Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-10-08 Thread Punith s 
it was the /etc/hosts script i had to modify, i had change my ip from dhcp
to static, so had to include my ip in the hosts file.


On Mon, Oct 7, 2013 at 11:25 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Interesting...I see you have another e-mail out on this, as well.
>
> I'd be curious if the recommendation solved your problem.
>
>
> On Mon, Oct 7, 2013 at 1:58 AM, Punith s  wrote:
>
> > hi mike ,
> >
> > today i rebuilt the ACS with the new 4.2 official release, but while
> > debugging the CS in eclipse its popping up an error saying ,
> > Failed to connect to remote VM. Connection refused.
> > Connection refused
> >
> >
> > i have shut down the firewall by service iptables stop,
> >
> > also if i do netstat -nap | grep 8787 , the port is shown listening
> > tcp0  0 127.0.0.1:8787  127.0.0.1:51909
> > ESTABLISHED 14862/java
> >
> > ps -auxx | grep jetty shows that i have exported the following
> > export="-Xmx1024m
> > -XX:MaxPermSize=800m -Xdebug
> > -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
> >
> > ps -auxx | grep jetty
> > root 14862 12.2 6.1 5758204 969372 pts/1 Sl+ 13:01 2:11
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java -Xmx1024m
> > -XX:MaxPermSize=800m -Xdebug
> > -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -classpath
> > /usr/local/apache-maven-3.1.0/boot/plexus-classworlds-2.4.2.jar
> > -Dclassworlds.conf=/usr/local/apache-maven-3.1.0/bin/m2.conf
> > -Dmaven.home=/usr/local/apache-maven-3.1.0
> > org.codehaus.plexus.classworlds.launcher.Launcher -pl :cloud-client-ui
> > jetty:run
> >
> > also # jmap 14862 shows,
> >
> > [root@mycloudstack home]# jmap 14862
> > Attaching to process ID 14862, please wait...
> > Debugger attached successfully.
> > Server compiler detected.
> > JVM version is 23.7-b01
> > 0x0040 9K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java
> > 0x00310fa0 153K /lib64/ld-2.12.so
> > 0x00310fe0 54K
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/jli/libjli.so
> > 0x00311020 1877K /lib64/libc-2.12.so
> > 0x00311060 22K /lib64/libdl-2.12.so
> > 0x003110a0 142K /lib64/libpthread-2.12.so
> > 0x003110e0 88K /lib64/libz.so.1.2.3
> > 0x00311120 45K /lib64/librt-2.12.so
> > 0x003112e0 12K /usr/lib64/libXau.so.6.0.0
> > 0x00311320 121K /usr/lib64/libxcb.so.1.1.0
> > 0x003113a0 1269K /usr/lib64/libX11.so.6.3.0
> > 0x00311460 79K /usr/lib64/libXext.so.6.4.0
> > 0x003114e0 61K /usr/lib64/libXi.so.6.1.0
> > 0x00311560 41K /usr/lib64/libXrender.so.1.3.0
> > 0x00311ba0 91K /lib64/libgcc_s-4.4.7-20120601.so.1
> > 0x00311ca0 966K /usr/lib64/libstdc++.so.6.0.13
> > 0x00312660 25K /usr/lib64/libXtst.so.6.1.0
> > 0x7fc0524b9000 347K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/xawt/libmawt.so
> > 0x7fc052711000 698K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libawt.so
> > 0x7fc053df8000 31K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libmanagement.so
> > 0x7fc060c3e000 92K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnet.so
> > 0x7fc060e55000 68K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnio.so
> > 0x7fc06166c000 16K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libdt_socket.so
> > 0x7fc071f94000 31K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libzip.so
> > 0x7fc07219c000 64K /lib64/libnss_files-2.12.so
> > 0x7fc0723c 12K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnpt.so
> > 0x7fc0725c3000 234K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjdwp.so
> > 0x7fc0727fe000 168K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjava.so
> > 0x7fc072a28000 58K
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libverify.so
> > 0x7fc072d38000 584K /lib64/libm-2.12.so
> > 0x7fc072fbc000 10975K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/server/libjvm.s
> >
> > any suggestions ?? thanks.
> >
> > regards,
> > punith s
> >
> >
> >
> > On Sun, Sep 15, 2013 at 5:43 PM, Rohit Yadav 
> wrote:
> >
> > > #3 is best and also since devcloud2 was created to provide host-only
> mode
> > > so that it could be used a throw away appliance for a faster CloudStack
> > > development.
> > >
> > > #3: CloudStack will run on your host OS so debugging becomes easier.
> > >
> > > HTH.
> > >
> > >
> > > On Thu, Sep 12, 2013 at 2:49 PM, Punith s 
> > wrote:
> > >
> > > > hi folks,
> > > >
> > > > i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using
> *full
> > > > sandbox mode* ,
> > > >
> > > > devcloud allows following modes ,
> > > > *1.full sandbox mode - *build and deploy inside devcloud
> > > > *2.deployment m

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-10-07 Thread Mike Tutkowski 
Interesting...I see you have another e-mail out on this, as well.

I'd be curious if the recommendation solved your problem.


On Mon, Oct 7, 2013 at 1:58 AM, Punith s  wrote:

> hi mike ,
>
> today i rebuilt the ACS with the new 4.2 official release, but while
> debugging the CS in eclipse its popping up an error saying ,
> Failed to connect to remote VM. Connection refused.
> Connection refused
>
>
> i have shut down the firewall by service iptables stop,
>
> also if i do netstat -nap | grep 8787 , the port is shown listening
> tcp0  0 127.0.0.1:8787  127.0.0.1:51909
> ESTABLISHED 14862/java
>
> ps -auxx | grep jetty shows that i have exported the following
> export="-Xmx1024m
> -XX:MaxPermSize=800m -Xdebug
> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
>
> ps -auxx | grep jetty
> root 14862 12.2 6.1 5758204 969372 pts/1 Sl+ 13:01 2:11
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java -Xmx1024m
> -XX:MaxPermSize=800m -Xdebug
> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -classpath
> /usr/local/apache-maven-3.1.0/boot/plexus-classworlds-2.4.2.jar
> -Dclassworlds.conf=/usr/local/apache-maven-3.1.0/bin/m2.conf
> -Dmaven.home=/usr/local/apache-maven-3.1.0
> org.codehaus.plexus.classworlds.launcher.Launcher -pl :cloud-client-ui
> jetty:run
>
> also # jmap 14862 shows,
>
> [root@mycloudstack home]# jmap 14862
> Attaching to process ID 14862, please wait...
> Debugger attached successfully.
> Server compiler detected.
> JVM version is 23.7-b01
> 0x0040 9K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java
> 0x00310fa0 153K /lib64/ld-2.12.so
> 0x00310fe0 54K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/jli/libjli.so
> 0x00311020 1877K /lib64/libc-2.12.so
> 0x00311060 22K /lib64/libdl-2.12.so
> 0x003110a0 142K /lib64/libpthread-2.12.so
> 0x003110e0 88K /lib64/libz.so.1.2.3
> 0x00311120 45K /lib64/librt-2.12.so
> 0x003112e0 12K /usr/lib64/libXau.so.6.0.0
> 0x00311320 121K /usr/lib64/libxcb.so.1.1.0
> 0x003113a0 1269K /usr/lib64/libX11.so.6.3.0
> 0x00311460 79K /usr/lib64/libXext.so.6.4.0
> 0x003114e0 61K /usr/lib64/libXi.so.6.1.0
> 0x00311560 41K /usr/lib64/libXrender.so.1.3.0
> 0x00311ba0 91K /lib64/libgcc_s-4.4.7-20120601.so.1
> 0x00311ca0 966K /usr/lib64/libstdc++.so.6.0.13
> 0x00312660 25K /usr/lib64/libXtst.so.6.1.0
> 0x7fc0524b9000 347K
>
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/xawt/libmawt.so
> 0x7fc052711000 698K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libawt.so
> 0x7fc053df8000 31K
>
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libmanagement.so
> 0x7fc060c3e000 92K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnet.so
> 0x7fc060e55000 68K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnio.so
> 0x7fc06166c000 16K
>
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libdt_socket.so
> 0x7fc071f94000 31K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libzip.so
> 0x7fc07219c000 64K /lib64/libnss_files-2.12.so
> 0x7fc0723c 12K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnpt.so
> 0x7fc0725c3000 234K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjdwp.so
> 0x7fc0727fe000 168K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjava.so
> 0x7fc072a28000 58K
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libverify.so
> 0x7fc072d38000 584K /lib64/libm-2.12.so
> 0x7fc072fbc000 10975K
>
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/server/libjvm.s
>
> any suggestions ?? thanks.
>
> regards,
> punith s
>
>
>
> On Sun, Sep 15, 2013 at 5:43 PM, Rohit Yadav  wrote:
>
> > #3 is best and also since devcloud2 was created to provide host-only mode
> > so that it could be used a throw away appliance for a faster CloudStack
> > development.
> >
> > #3: CloudStack will run on your host OS so debugging becomes easier.
> >
> > HTH.
> >
> >
> > On Thu, Sep 12, 2013 at 2:49 PM, Punith s 
> wrote:
> >
> > > hi folks,
> > >
> > > i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
> > > sandbox mode* ,
> > >
> > > devcloud allows following modes ,
> > > *1.full sandbox mode - *build and deploy inside devcloud
> > > *2.deployment mode - *build code in localhost and deploying in devcloud
> > > *3.host only mode - *using devcloud only as host
> > >
> > >
> > > which mode do you think its feasible for development and  interactive
> > > debugging ?
> > > can you elaborate more on setting up remote debugging in Devcloud2
> > > (fullsandbox mode) using eclipse ??
> > >
> > > thanks,
> > > punith s
> > >
> >
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.c

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-10-07 Thread Punith s 
hi mike ,

today i rebuilt the ACS with the new 4.2 official release, but while
debugging the CS in eclipse its popping up an error saying ,
Failed to connect to remote VM. Connection refused.
Connection refused


i have shut down the firewall by service iptables stop,

also if i do netstat -nap | grep 8787 , the port is shown listening
tcp0  0 127.0.0.1:8787  127.0.0.1:51909
ESTABLISHED 14862/java

ps -auxx | grep jetty shows that i have exported the following
export="-Xmx1024m
-XX:MaxPermSize=800m -Xdebug
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"

ps -auxx | grep jetty
root 14862 12.2 6.1 5758204 969372 pts/1 Sl+ 13:01 2:11
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java -Xmx1024m
-XX:MaxPermSize=800m -Xdebug
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -classpath
/usr/local/apache-maven-3.1.0/boot/plexus-classworlds-2.4.2.jar
-Dclassworlds.conf=/usr/local/apache-maven-3.1.0/bin/m2.conf
-Dmaven.home=/usr/local/apache-maven-3.1.0
org.codehaus.plexus.classworlds.launcher.Launcher -pl :cloud-client-ui
jetty:run

also # jmap 14862 shows,

[root@mycloudstack home]# jmap 14862
Attaching to process ID 14862, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 23.7-b01
0x0040 9K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java
0x00310fa0 153K /lib64/ld-2.12.so
0x00310fe0 54K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/jli/libjli.so
0x00311020 1877K /lib64/libc-2.12.so
0x00311060 22K /lib64/libdl-2.12.so
0x003110a0 142K /lib64/libpthread-2.12.so
0x003110e0 88K /lib64/libz.so.1.2.3
0x00311120 45K /lib64/librt-2.12.so
0x003112e0 12K /usr/lib64/libXau.so.6.0.0
0x00311320 121K /usr/lib64/libxcb.so.1.1.0
0x003113a0 1269K /usr/lib64/libX11.so.6.3.0
0x00311460 79K /usr/lib64/libXext.so.6.4.0
0x003114e0 61K /usr/lib64/libXi.so.6.1.0
0x00311560 41K /usr/lib64/libXrender.so.1.3.0
0x00311ba0 91K /lib64/libgcc_s-4.4.7-20120601.so.1
0x00311ca0 966K /usr/lib64/libstdc++.so.6.0.13
0x00312660 25K /usr/lib64/libXtst.so.6.1.0
0x7fc0524b9000 347K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/xawt/libmawt.so
0x7fc052711000 698K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libawt.so
0x7fc053df8000 31K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libmanagement.so
0x7fc060c3e000 92K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnet.so
0x7fc060e55000 68K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnio.so
0x7fc06166c000 16K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libdt_socket.so
0x7fc071f94000 31K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libzip.so
0x7fc07219c000 64K /lib64/libnss_files-2.12.so
0x7fc0723c 12K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnpt.so
0x7fc0725c3000 234K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjdwp.so
0x7fc0727fe000 168K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjava.so
0x7fc072a28000 58K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libverify.so
0x7fc072d38000 584K /lib64/libm-2.12.so
0x7fc072fbc000 10975K
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/server/libjvm.s

any suggestions ?? thanks.

regards,
punith s



On Sun, Sep 15, 2013 at 5:43 PM, Rohit Yadav  wrote:

> #3 is best and also since devcloud2 was created to provide host-only mode
> so that it could be used a throw away appliance for a faster CloudStack
> development.
>
> #3: CloudStack will run on your host OS so debugging becomes easier.
>
> HTH.
>
>
> On Thu, Sep 12, 2013 at 2:49 PM, Punith s  wrote:
>
> > hi folks,
> >
> > i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
> > sandbox mode* ,
> >
> > devcloud allows following modes ,
> > *1.full sandbox mode - *build and deploy inside devcloud
> > *2.deployment mode - *build code in localhost and deploying in devcloud
> > *3.host only mode - *using devcloud only as host
> >
> >
> > which mode do you think its feasible for development and  interactive
> > debugging ?
> > can you elaborate more on setting up remote debugging in Devcloud2
> > (fullsandbox mode) using eclipse ??
> >
> > thanks,
> > punith s
> >
>

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-15 Thread Rohit Yadav 
#3 is best and also since devcloud2 was created to provide host-only mode
so that it could be used a throw away appliance for a faster CloudStack
development.

#3: CloudStack will run on your host OS so debugging becomes easier.

HTH.


On Thu, Sep 12, 2013 at 2:49 PM, Punith s  wrote:

> hi folks,
>
> i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
> sandbox mode* ,
>
> devcloud allows following modes ,
> *1.full sandbox mode - *build and deploy inside devcloud
> *2.deployment mode - *build code in localhost and deploying in devcloud
> *3.host only mode - *using devcloud only as host
>
>
> which mode do you think its feasible for development and  interactive
> debugging ?
> can you elaborate more on setting up remote debugging in Devcloud2
> (fullsandbox mode) using eclipse ??
>
> thanks,
> punith s
>

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-13 Thread Mike Tutkowski 
Yeah, remote debugging in Eclipse - whether the process I connect to is in
a different VM, same VM, or on a different physical machine - usually
works. Not sure what was going on yesterday and I haven't tried it yet
today.


On Fri, Sep 13, 2013 at 4:32 AM, Punith s  wrote:

> hi guys ,
>
> thanks a lot for the info , you guys are right , now i'm using #*3.host
> only mode *in devcloud2 , and i'm able to debug the MS from
> eclipse seamlessly in my localhost.
> and mike if you have such problems then you can try *full sandbox mode *in
> devcloud2 and connect to it remotely from eclipse by giving the ip of the
> MS (192.168.56.10) , but again it's pretty uncomfortable having everything
> inside devcloud  but anyway its good to try new ways if things work , like
> how i switched from fullsandbox to host only mode. thanks again
>
> regards,
> punith s
> cloudbyte
>
>
> On Fri, Sep 13, 2013 at 5:03 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > Here is a relevant link:
> >
> > https://cwiki.apache.org/CLOUDSTACK/using-eclipse-with-cloudstack.html
> >
> > The part at the bottom:
> >
> > Remote Debugging
> >
> > You can use Eclipse to attach to the Management Server and debug
> > CloudStack. You setup a Remote Debug Session (Run > Debug Configuration),
> > connect to Port 8787. Typically you would use the project you want to
> debug
> > as the target and include other projects that you need to debug, e.g.
> > cloud-agent, cloud-api, cloud-core and cloud-server.
> >
> > **
> >
> > Currently I am having trouble in 4.3 with remote debugging. I'm not sure
> > why.
> >
> > I have my Remote Java Application configured and running. It connects to
> > the CloudStack Management Server.
> >
> > I set a breakpoint and execute some logic on the front end that should
> hit
> > this breakpoint on the back end, but it doesn't break.
> >
> >
> >
> > On Thu, Sep 12, 2013 at 12:41 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > I should have been a bit more specific.
> > >
> > > Once you do what I wrote in my previous e-mail, then run your
> management
> > > server.
> > >
> > > Then run your Remote Java Application and set breakpoints.
> > >
> > >
> > > On Thu, Sep 12, 2013 at 12:27 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com> wrote:
> > >
> > >> If you want to debug remotely, run the CloudStack Management Server
> with
> > >> an environment variable such as the following:
> > >>
> > >> MAVEN_OPTS=-XX:MaxPermSize=512m -Xmx1024m -Xdebug
> > >> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
> > >>
> > >> Then in Eclipse, go to Debug Configurations and create a new Remote
> Java
> > >> Application.
> > >>
> > >> Browse and select cloud-server for the Project field.
> > >>
> > >> Enter you IP address for the Host field.
> > >>
> > >> Assuming you used 8787 in MAVEN_OPTS, use 8787 for the Port field.
> > >>
> > >> You may now run your management server and set breakpoints as need be.
> > >>
> > >>
> > >> On Thu, Sep 12, 2013 at 12:19 PM, Mike Tutkowski <
> > >> mike.tutkow...@solidfire.com> wrote:
> > >>
> > >>> I prefer #3, as well.
> > >>>
> > >>>
> > >>> On Thu, Sep 12, 2013 at 10:09 AM, Chiradeep Vittal <
> > >>> chiradeep.vit...@citrix.com> wrote:
> > >>>
> >  #3 works best, I think
> > 
> >  On 9/12/13 2:19 AM, "Punith s"  wrote:
> > 
> >  >hi folks,
> >  >
> >  >i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using
> > *full
> >  >sandbox mode* ,
> >  >
> >  >devcloud allows following modes ,
> >  >*1.full sandbox mode - *build and deploy inside devcloud
> >  >*2.deployment mode - *build code in localhost and deploying in
> > devcloud
> >  >*3.host only mode - *using devcloud only as host
> >  >
> >  >
> >  >which mode do you think its feasible for development and
>  interactive
> >  >debugging ?
> >  >can you elaborate more on setting up remote debugging in Devcloud2
> >  >(fullsandbox mode) using eclipse ??
> >  >
> >  >thanks,
> >  >punith s
> > 
> > 
> > >>>
> > >>>
> > >>> --
> > >>> *Mike Tutkowski*
> > >>> *Senior CloudStack Developer, SolidFire Inc.*
> > >>> e: mike.tutkow...@solidfire.com
> > >>> o: 303.746.7302
> > >>> Advancing the way the world uses the cloud<
> > http://solidfire.com/solution/overview/?video=play>
> > >>> *™*
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> *Mike Tutkowski*
> > >> *Senior CloudStack Developer, SolidFire Inc.*
> > >> e: mike.tutkow...@solidfire.com
> > >> o: 303.746.7302
> > >> Advancing the way the world uses the cloud<
> > http://solidfire.com/solution/overview/?video=play>
> > >> *™*
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the cloud<
> > http://solidfire.com/solution/overview/?video=play>
> > > *™*
> > >
> >
> >
> >
> > --
> > *Mike Tu

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-13 Thread Punith s 
hi guys ,

thanks a lot for the info , you guys are right , now i'm using #*3.host
only mode *in devcloud2 , and i'm able to debug the MS from
eclipse seamlessly in my localhost.
and mike if you have such problems then you can try *full sandbox mode *in
devcloud2 and connect to it remotely from eclipse by giving the ip of the
MS (192.168.56.10) , but again it's pretty uncomfortable having everything
inside devcloud  but anyway its good to try new ways if things work , like
how i switched from fullsandbox to host only mode. thanks again

regards,
punith s
cloudbyte


On Fri, Sep 13, 2013 at 5:03 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Here is a relevant link:
>
> https://cwiki.apache.org/CLOUDSTACK/using-eclipse-with-cloudstack.html
>
> The part at the bottom:
>
> Remote Debugging
>
> You can use Eclipse to attach to the Management Server and debug
> CloudStack. You setup a Remote Debug Session (Run > Debug Configuration),
> connect to Port 8787. Typically you would use the project you want to debug
> as the target and include other projects that you need to debug, e.g.
> cloud-agent, cloud-api, cloud-core and cloud-server.
>
> **
>
> Currently I am having trouble in 4.3 with remote debugging. I'm not sure
> why.
>
> I have my Remote Java Application configured and running. It connects to
> the CloudStack Management Server.
>
> I set a breakpoint and execute some logic on the front end that should hit
> this breakpoint on the back end, but it doesn't break.
>
>
>
> On Thu, Sep 12, 2013 at 12:41 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > I should have been a bit more specific.
> >
> > Once you do what I wrote in my previous e-mail, then run your management
> > server.
> >
> > Then run your Remote Java Application and set breakpoints.
> >
> >
> > On Thu, Sep 12, 2013 at 12:27 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> If you want to debug remotely, run the CloudStack Management Server with
> >> an environment variable such as the following:
> >>
> >> MAVEN_OPTS=-XX:MaxPermSize=512m -Xmx1024m -Xdebug
> >> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
> >>
> >> Then in Eclipse, go to Debug Configurations and create a new Remote Java
> >> Application.
> >>
> >> Browse and select cloud-server for the Project field.
> >>
> >> Enter you IP address for the Host field.
> >>
> >> Assuming you used 8787 in MAVEN_OPTS, use 8787 for the Port field.
> >>
> >> You may now run your management server and set breakpoints as need be.
> >>
> >>
> >> On Thu, Sep 12, 2013 at 12:19 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> I prefer #3, as well.
> >>>
> >>>
> >>> On Thu, Sep 12, 2013 at 10:09 AM, Chiradeep Vittal <
> >>> chiradeep.vit...@citrix.com> wrote:
> >>>
>  #3 works best, I think
> 
>  On 9/12/13 2:19 AM, "Punith s"  wrote:
> 
>  >hi folks,
>  >
>  >i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using
> *full
>  >sandbox mode* ,
>  >
>  >devcloud allows following modes ,
>  >*1.full sandbox mode - *build and deploy inside devcloud
>  >*2.deployment mode - *build code in localhost and deploying in
> devcloud
>  >*3.host only mode - *using devcloud only as host
>  >
>  >
>  >which mode do you think its feasible for development and  interactive
>  >debugging ?
>  >can you elaborate more on setting up remote debugging in Devcloud2
>  >(fullsandbox mode) using eclipse ??
>  >
>  >thanks,
>  >punith s
> 
> 
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the cloud<
> http://solidfire.com/solution/overview/?video=play>
> >>> *™*
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the cloud<
> http://solidfire.com/solution/overview/?video=play>
> >> *™*
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud<
> http://solidfire.com/solution/overview/?video=play>
> > *™*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
>

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-12 Thread Mike Tutkowski 
Here is a relevant link:

https://cwiki.apache.org/CLOUDSTACK/using-eclipse-with-cloudstack.html

The part at the bottom:

Remote Debugging

You can use Eclipse to attach to the Management Server and debug
CloudStack. You setup a Remote Debug Session (Run > Debug Configuration),
connect to Port 8787. Typically you would use the project you want to debug
as the target and include other projects that you need to debug, e.g.
cloud-agent, cloud-api, cloud-core and cloud-server.

**

Currently I am having trouble in 4.3 with remote debugging. I'm not sure
why.

I have my Remote Java Application configured and running. It connects to
the CloudStack Management Server.

I set a breakpoint and execute some logic on the front end that should hit
this breakpoint on the back end, but it doesn't break.



On Thu, Sep 12, 2013 at 12:41 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I should have been a bit more specific.
>
> Once you do what I wrote in my previous e-mail, then run your management
> server.
>
> Then run your Remote Java Application and set breakpoints.
>
>
> On Thu, Sep 12, 2013 at 12:27 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> If you want to debug remotely, run the CloudStack Management Server with
>> an environment variable such as the following:
>>
>> MAVEN_OPTS=-XX:MaxPermSize=512m -Xmx1024m -Xdebug
>> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
>>
>> Then in Eclipse, go to Debug Configurations and create a new Remote Java
>> Application.
>>
>> Browse and select cloud-server for the Project field.
>>
>> Enter you IP address for the Host field.
>>
>> Assuming you used 8787 in MAVEN_OPTS, use 8787 for the Port field.
>>
>> You may now run your management server and set breakpoints as need be.
>>
>>
>> On Thu, Sep 12, 2013 at 12:19 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> I prefer #3, as well.
>>>
>>>
>>> On Thu, Sep 12, 2013 at 10:09 AM, Chiradeep Vittal <
>>> chiradeep.vit...@citrix.com> wrote:
>>>
 #3 works best, I think

 On 9/12/13 2:19 AM, "Punith s"  wrote:

 >hi folks,
 >
 >i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
 >sandbox mode* ,
 >
 >devcloud allows following modes ,
 >*1.full sandbox mode - *build and deploy inside devcloud
 >*2.deployment mode - *build code in localhost and deploying in devcloud
 >*3.host only mode - *using devcloud only as host
 >
 >
 >which mode do you think its feasible for development and  interactive
 >debugging ?
 >can you elaborate more on setting up remote debugging in Devcloud2
 >(fullsandbox mode) using eclipse ??
 >
 >thanks,
 >punith s


>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkow...@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the 
>>> cloud
>>> *™*
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-12 Thread Mike Tutkowski 
I prefer #3, as well.


On Thu, Sep 12, 2013 at 10:09 AM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:

> #3 works best, I think
>
> On 9/12/13 2:19 AM, "Punith s"  wrote:
>
> >hi folks,
> >
> >i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
> >sandbox mode* ,
> >
> >devcloud allows following modes ,
> >*1.full sandbox mode - *build and deploy inside devcloud
> >*2.deployment mode - *build code in localhost and deploying in devcloud
> >*3.host only mode - *using devcloud only as host
> >
> >
> >which mode do you think its feasible for development and  interactive
> >debugging ?
> >can you elaborate more on setting up remote debugging in Devcloud2
> >(fullsandbox mode) using eclipse ??
> >
> >thanks,
> >punith s
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-12 Thread Chiradeep Vittal 
#3 works best, I think

On 9/12/13 2:19 AM, "Punith s"  wrote:

>hi folks,
>
>i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
>sandbox mode* ,
>
>devcloud allows following modes ,
>*1.full sandbox mode - *build and deploy inside devcloud
>*2.deployment mode - *build code in localhost and deploying in devcloud
>*3.host only mode - *using devcloud only as host
>
>
>which mode do you think its feasible for development and  interactive
>debugging ?
>can you elaborate more on setting up remote debugging in Devcloud2
>(fullsandbox mode) using eclipse ??
>
>thanks,
>punith s

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-12 Thread Mike Tutkowski 
If you want to debug remotely, run the CloudStack Management Server with an
environment variable such as the following:

MAVEN_OPTS=-XX:MaxPermSize=512m -Xmx1024m -Xdebug
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n

Then in Eclipse, go to Debug Configurations and create a new Remote Java
Application.

Browse and select cloud-server for the Project field.

Enter you IP address for the Host field.

Assuming you used 8787 in MAVEN_OPTS, use 8787 for the Port field.

You may now run your management server and set breakpoints as need be.


On Thu, Sep 12, 2013 at 12:19 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I prefer #3, as well.
>
>
> On Thu, Sep 12, 2013 at 10:09 AM, Chiradeep Vittal <
> chiradeep.vit...@citrix.com> wrote:
>
>> #3 works best, I think
>>
>> On 9/12/13 2:19 AM, "Punith s"  wrote:
>>
>> >hi folks,
>> >
>> >i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
>> >sandbox mode* ,
>> >
>> >devcloud allows following modes ,
>> >*1.full sandbox mode - *build and deploy inside devcloud
>> >*2.deployment mode - *build code in localhost and deploying in devcloud
>> >*3.host only mode - *using devcloud only as host
>> >
>> >
>> >which mode do you think its feasible for development and  interactive
>> >debugging ?
>> >can you elaborate more on setting up remote debugging in Devcloud2
>> >(fullsandbox mode) using eclipse ??
>> >
>> >thanks,
>> >punith s
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-12 Thread Mike Tutkowski 
I should have been a bit more specific.

Once you do what I wrote in my previous e-mail, then run your management
server.

Then run your Remote Java Application and set breakpoints.


On Thu, Sep 12, 2013 at 12:27 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> If you want to debug remotely, run the CloudStack Management Server with
> an environment variable such as the following:
>
> MAVEN_OPTS=-XX:MaxPermSize=512m -Xmx1024m -Xdebug
> -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
>
> Then in Eclipse, go to Debug Configurations and create a new Remote Java
> Application.
>
> Browse and select cloud-server for the Project field.
>
> Enter you IP address for the Host field.
>
> Assuming you used 8787 in MAVEN_OPTS, use 8787 for the Port field.
>
> You may now run your management server and set breakpoints as need be.
>
>
> On Thu, Sep 12, 2013 at 12:19 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> I prefer #3, as well.
>>
>>
>> On Thu, Sep 12, 2013 at 10:09 AM, Chiradeep Vittal <
>> chiradeep.vit...@citrix.com> wrote:
>>
>>> #3 works best, I think
>>>
>>> On 9/12/13 2:19 AM, "Punith s"  wrote:
>>>
>>> >hi folks,
>>> >
>>> >i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
>>> >sandbox mode* ,
>>> >
>>> >devcloud allows following modes ,
>>> >*1.full sandbox mode - *build and deploy inside devcloud
>>> >*2.deployment mode - *build code in localhost and deploying in devcloud
>>> >*3.host only mode - *using devcloud only as host
>>> >
>>> >
>>> >which mode do you think its feasible for development and  interactive
>>> >debugging ?
>>> >can you elaborate more on setting up remote debugging in Devcloud2
>>> >(fullsandbox mode) using eclipse ??
>>> >
>>> >thanks,
>>> >punith s
>>>
>>>
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Which DevCloud2 Usage Mode is good for Development and Debugging ????

2013-09-12 Thread Punith s 
hi folks,

i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using *full
sandbox mode* ,

devcloud allows following modes ,
*1.full sandbox mode - *build and deploy inside devcloud
*2.deployment mode - *build code in localhost and deploying in devcloud
*3.host only mode - *using devcloud only as host


which mode do you think its feasible for development and  interactive
debugging ?
can you elaborate more on setting up remote debugging in Devcloud2
(fullsandbox mode) using eclipse ??

thanks,
punith s