new-user
i want to behin with contributing to cloudstack. please guide me on how to begin with learning process and then forward Thank You Gaurav
Re: new-user
Hi, Getting involved is fairly easy. From my experience the community is very helpful. I'll briefly go through some of the things the community have. 1) JIRA The cloudstack JIRA can be found at: https://issues.apache.org/jira/browse/CLOUDSTACK all bugs are reported over there. 2) Review board When you make a change to the code you generate a .patch file(Will cover generate of patch files in a moment), you upload this patch to the review board and a committer will review it and hopefully ship it. https://reviews.apache.org/groups/cloudstack/ 3) Git / Patch creating The Cloudstack project uses git for source control management. Community member Sebastien has a great screencast over at: https://www.youtube.com/watch?v=3c5JIW4onGk there is written documentation over here: https://cloudstack.apache.org/develop/non-committer.html 4) Setting up a development environment https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment 5) How to build https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+on+master+branch 6) The wiki There's general documentation on the wiki under development 101 that will help you figure things out: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+101 7) Coding conventions https://cloudstack.apache.org/develop/coding-conventions.html 8) Developer FAQ https://cloudstack.apache.org/develop/developer-faq.html 9) The cloudstack university https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+University 10) Finally getting help Mailing list: https://cloudstack.apache.org/mailing-lists.html IRC: irc.freenode.net in #cloudstack-dev you can access it from your browser at http://webchat.freenode.net Hope this helps! Ian On 6 July 2013 11:05, gaurav jain wrote: > i want to behin with contributing to cloudstack. > please guide me on how to begin with learning process and then forward > > Thank You > Gaurav
Re: [GSOC] Update to document
I will update the report. I am aware that a "Intro to Mesos" post is also pending from my side. Want to write on my experience while doing changes on large and active code base too, but that is gona take some time. I am little off in my timeline. I plan to get mesos on cloudstack working by midterm and shift focus on cloudformation from there. I would also like to know if there is any particular expectation. Thanks, Dharmesh On Fri, Jul 5, 2013 at 6:48 PM, Sebastien Goasguen wrote: > Hi guys, > > I modified the format of our "report", I moved the proposals to a chapter > and started a new chapter called "updates". > Each of you should use a section to write a small report/updates on your > progress so far. > > You can see the doc at: > > http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf > > Your respective sections should be self-explanatory when you checkout the > code. > > We will use this for the mid-summer evaluation that Google wants/needs. > > A good example of progress report is from Ian at: > > http://imduffy15.blogspot.co.uk > > You can include specific things about your project but also things related > to CloudStack itself, what you are learning (jira, git etc..) and what you > contributed so far outside your project (e.g Meng gave us the quick install > guide for 4.1 and Dharmesh is looking at a significant update to the code > with CLOUDSTACK-212) > > Cheers, > > -Sebastien
Re: AWS SDK version for object store
On Fri, Jul 05, 2013 at 06:27:46PM +0530, Prasanna Santhanam wrote: > There was another issue I found today with the SDK v1.3.21. It appears > I can't use periods in the name of a bucket. I see an SSL Exception > when this is done [1]. The bug is fixed in the v1.3.22. There are also > couple of other issues fixed related to s3 on the latest version of > the SDK. Is there any reason not to use the latest stable SDK version > in CloudStack? IOW, why did we choose the v1.3.21? > > [1] http://issues.apache.org/jira/browse/CLOUDSTACK-3374 > Fixed by bumping up the version to 1.3.22. But would still like to bump it up to the latest stable version of the SDK available at the time of the release ACS 4.2 Thoughts? -- Prasanna., Powered by BigRock.com
Re: Spring Framework Question
Thanks!
On Fri, Jul 5, 2013 at 7:46 PM, Soheil Eizadi wrote:
> Hi Mike,
> You typically have a public interface for your DAO:
> public interface InfobloxDao extends GenericDao{
>
> }
>
> Then an implementation:
> public class InfobloxDaoImpl extends GenericDaoBase
> implements InfobloxDao {
> ...
> }
>
> This is a good link for the details of Database Access:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Data+Access+Layer
>
> The DataBase DAO is one of the Beans you register with Spring
> componentContext.xml.in: class="org.apache.cloudstack.network.dao.InfobloxDaoImpl" />
>
> Then at run time the call like the one you have below wires your
> application typically plugin to the plugin data base implementation:
> @Inject
> InfobloxDao _infobloxDao;
>
>
>
> From: Mike Tutkowski [mike.tutkow...@solidfire.com]
> Sent: Sunday, April 21, 2013 11:53 AM
> To: cloudstack-...@incubator.apache.org
> Subject: Spring Framework Question
>
> Hi,
>
> I'm new to the Spring Framework. I understand the basic concepts, but am
> not familiar with the details regarding how to hook up dependencies.
>
> For example, I see this in various classes:
>
> @Inject DiskOfferingDao diskOfferingDao;
>
>
> What did we have to do in Spring (ex. files to configure) so that the
> proper runtime instance of DiskOfferingDao was instantiated and assigned to
> diskOfferingDao?
>
>
> Thanks!
>
> --
> *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
*™*
database connection resilience
I've noticed that the cloudstack management server creates persistent connections to the database, and crashes if the database connection is lost. I haven't looked at the code yet, but I was wondering if anyone knew about what was going on here, if it's simply not set up to gracefully handle reconnect, or something else. We have a multi-master database setup, but cloudstack doesn't take advantage of it since it doesn't attempt graceful reconnect, if the particular node it connected to on startup goes down, it simply crashes.
Re: database connection resilience
I see that my db.properties has db.cloud.autoReconnect=true, which translates to setting autoReconnect in the jdbc driver connection in utils/src/com/cloud/utils/db/Transaction.java. I also see that if I manually trigger the issue I get: 013-07-07 00:42:50,502 ERROR [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Runtime DB exception com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 1,503 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago. at sun.reflect.GeneratedConstructorAccessor159.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3567) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3456) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3997) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:409) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:350) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:907) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:912) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.cluster.dao.ManagementServerHostDaoImpl.getActiveList(ManagementServerHostDaoImpl.java:158) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.cluster.ClusterManagerImpl.peerScan(ClusterManagerImpl.java:1057) at com.cloud.cluster.ClusterManagerImpl.access$1200(ClusterManagerImpl.java:95) at com.cloud.cluster.ClusterManagerImpl$4.run(ClusterManagerImpl.java:789) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost. ... 55 more 2013-07-07 00:42:50,505 ERROR [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) DB communication problem detected, fence it And I have only to restart cloudstack-management so it can connect to another member in the loadbalanced multimaster database to get things running again. On Sun, Jul 7, 2013 at 12:35 AM, Marcus Sorensen wrote: > I've noticed that the cloudstack management server creates persistent > connections to the database, and crashes if the database connection is > lost. I haven't looked at the code yet, but I was wondering if anyone > knew about what was going on here, if it's simply not set up to > gracefully handle reconnect, or something else. We have a > multi-master database setup, but cloudstack doesn't take advantage of > it since it doesn't attempt graceful reconnect, if the particular node > it connected to on startup goes down, it simply crashes.
Re: database connection resilience
Hi, On 07/07/2013 08:45 AM, Marcus Sorensen wrote: I see that my db.properties has db.cloud.autoReconnect=true, which translates to setting autoReconnect in the jdbc driver connection in utils/src/com/cloud/utils/db/Transaction.java. I also see that if I manually trigger the issue I get: Just to confirm, I see the same issues. I haven't looked into this yet, but this is also one of the things I want to have fixed. Maybe create an issue for it? Wido 013-07-07 00:42:50,502 ERROR [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) Runtime DB exception com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 1,503 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago. at sun.reflect.GeneratedConstructorAccessor159.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3567) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3456) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3997) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:409) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:350) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:907) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:912) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.cluster.dao.ManagementServerHostDaoImpl.getActiveList(ManagementServerHostDaoImpl.java:158) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.cluster.ClusterManagerImpl.peerScan(ClusterManagerImpl.java:1057) at com.cloud.cluster.ClusterManagerImpl.access$1200(ClusterManagerImpl.java:95) at com.cloud.cluster.ClusterManagerImpl$4.run(ClusterManagerImpl.java:789) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost. ... 55 more 2013-07-07 00:42:50,505 ERROR [cloud.cluster.ClusterManagerImpl] (Cluster-Heartbeat-1:null) DB communication problem detected, fence it And I have only to restart cloudstack-management so it can connect to another member in the loadbalanced multimaster database to get things running again. On Sun, Jul 7, 2013 at 12:35 AM, Marcus Sorensen wrote: I've noticed that the cloudstack management server creates persistent connections to the database, and crashes if the database connection is lost. I haven't looked at the code yet, but I was wondering if anyone knew about what was going on here, if it's simply not set up to gracefully handle reconnect, or something else. We have a multi-master database setup, but cloudstack doesn't take advantage of it since it doesn't attempt graceful reconnect, if the particular nod
