Re: [GSOC] Update to document
Yes of course -Sebastien On 25 Jul 2013, at 04:17, Nguyen Anh Tu ng.t...@gmail.com wrote: Hi Seb, May I extend the mid-term report to more than 3-4 pages? I want to add more design description that I learned from CloudStack's architecture. Of course they relate to my GSoC project. 2013/7/23 Sebastien Goasguen run...@gmail.com Hi Guys (Ian, Dharmesh, Shiva, Meng, Nguyen), Google needs to get our evaluation of your progress so far to decide if you keep on going or not. I sent the email below on July 5th. You now have only few days left to get it done ( I need it before Friday). I am looking for 3/4 pages describing what you have done in the last month and half, describe your progress, your challenges, what you learn about OSS development and how you see your deliverables going forward. -sebastien Begin forwarded message: From: Sebastien Goasguen run...@gmail.com Subject: [GSOC] Update to document Date: July 5, 2013 9:18:07 AM EDT To: dev@cloudstack.apache.org dev@cloudstack.apache.org 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 CLLU) Cheers, -Sebastien -- N.g.U.y.e.N.A.n.H.t.U
Re: [GSOC] Update to document
On Jul 12, 2013, at 1:00 PM, Nguyen Anh Tu ng.t...@gmail.com wrote: @Sebgoa: I added my first update progress report on blogspot. Like Ian Duffy, It's also my primary channel to report. From now until the end, I will frequently update to the blog and then transfer to ACS document. Please take a look on it: http://ngtuna.blogspot.com/ Cool, you should tweet it so we can spread the news. 2013/7/8 Dharmesh Kakadia dhkaka...@gmail.com @sebgoa Thanks for the clear spec. 1. My intro post is already done. 2. install and run post will follow. 3. stackmate blog with whirr/provisionr comparison I will check whirr driver possibility. Thanks, Dharmesh On Mon, Jul 8, 2013 at 1:03 PM, Sebastien Goasguen run...@gmail.com wrote: On Jul 6, 2013, at 7:14 AM, Dharmesh Kakadia dhkaka...@gmail.com wrote: 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. In your case, I would like to see an intro to Mesos (your first post, plus basic quick install steps, plus examples of running jobs in hadoop and mpi), plus basic steps of starting VMs in cloudstack and setting up Mesos on those VMs. Plus a discussions on how stackmate will help with the deployment and how it differs from whirr/provisionr. While stackamte is an interesting way to go, I also think that you could easily patch whirr to provide a driver for Mesos, it would be a nice contribution to whirr. -sebastien Thanks, Dharmesh On Fri, Jul 5, 2013 at 6:48 PM, Sebastien Goasguen run...@gmail.com 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 -- N.g.U.y.e.N.A.n.H.t.U
Re: [GSOC] Update to document
@sebgoa: done. Twitter is not popular at my country, Facebook instead. I created a new one. Hello world :D 2013/7/13 Sebastien Goasguen run...@gmail.com On Jul 12, 2013, at 1:00 PM, Nguyen Anh Tu ng.t...@gmail.com wrote: @Sebgoa: I added my first update progress report on blogspot. Like Ian Duffy, It's also my primary channel to report. From now until the end, I will frequently update to the blog and then transfer to ACS document. Please take a look on it: http://ngtuna.blogspot.com/ Cool, you should tweet it so we can spread the news. 2013/7/8 Dharmesh Kakadia dhkaka...@gmail.com @sebgoa Thanks for the clear spec. 1. My intro post is already done. 2. install and run post will follow. 3. stackmate blog with whirr/provisionr comparison I will check whirr driver possibility. Thanks, Dharmesh On Mon, Jul 8, 2013 at 1:03 PM, Sebastien Goasguen run...@gmail.com wrote: On Jul 6, 2013, at 7:14 AM, Dharmesh Kakadia dhkaka...@gmail.com wrote: 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. In your case, I would like to see an intro to Mesos (your first post, plus basic quick install steps, plus examples of running jobs in hadoop and mpi), plus basic steps of starting VMs in cloudstack and setting up Mesos on those VMs. Plus a discussions on how stackmate will help with the deployment and how it differs from whirr/provisionr. While stackamte is an interesting way to go, I also think that you could easily patch whirr to provide a driver for Mesos, it would be a nice contribution to whirr. -sebastien Thanks, Dharmesh On Fri, Jul 5, 2013 at 6:48 PM, Sebastien Goasguen run...@gmail.com 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 -- N.g.U.y.e.N.A.n.H.t.U -- N.g.U.y.e.N.A.n.H.t.U
Re: [GSOC] Update to document
On Jul 6, 2013, at 7:14 AM, Dharmesh Kakadia dhkaka...@gmail.com wrote: 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. In your case, I would like to see an intro to Mesos (your first post, plus basic quick install steps, plus examples of running jobs in hadoop and mpi), plus basic steps of starting VMs in cloudstack and setting up Mesos on those VMs. Plus a discussions on how stackmate will help with the deployment and how it differs from whirr/provisionr. While stackamte is an interesting way to go, I also think that you could easily patch whirr to provide a driver for Mesos, it would be a nice contribution to whirr. -sebastien Thanks, Dharmesh On Fri, Jul 5, 2013 at 6:48 PM, Sebastien Goasguen run...@gmail.com 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: [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 run...@gmail.com 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: [GSOC] Update to document
On Fri, Jul 05, 2013 at 09:18:10AM -0400, 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) Excellent work so far. Great work all! -- Prasanna., Powered by BigRock.com
Re: [GSOC] Update to document
@Sebastien - Is it ok to just copy and paste over what I had in that blog post? (Excluding the opening image and closing paragraph) On 5 July 2013 14:25, Prasanna Santhanam t...@apache.org wrote: On Fri, Jul 05, 2013 at 09:18:10AM -0400, 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) Excellent work so far. Great work all! -- Prasanna., Powered by BigRock.com
Re: [GSOC] Update to document
On Jul 5, 2013, at 10:25 AM, Ian Duffy i...@ianduffy.ie wrote: @Sebastien - Is it ok to just copy and paste over what I had in that blog post? (Excluding the opening image and closing paragraph) yes no problem, I'd love to see some info on your jenkins setup though :) and you can add the snapshots too... On 5 July 2013 14:25, Prasanna Santhanam t...@apache.org wrote: On Fri, Jul 05, 2013 at 09:18:10AM -0400, 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) Excellent work so far. Great work all! -- Prasanna., Powered by BigRock.com
Re: [GSOC] Update to document
Sorry to create two emails in a row... Just in terms of the Google wants/needs deadline on the 29th, is there anything you guys, the cloudstack community specifically want to see? I know Abhi mentioned the creation of a prototype for me in one of the gtalk conversations we had awhile back. So I'm hoping to have the plugin I detailed in the blog post completely cleaned up and ready for review by you guys with full end to end testing by that date. This would allow me to have the second half of the Google summer of code term to work on creating a UI to allow admins to easily provision users and extending the plugin where/if required. As mentioned to Sebastien during the skype interviews I would *ideally* like to have the project wrapped up by the end of August, based on the progress so far this seems possible. On 5 July 2013 15:25, Ian Duffy i...@ianduffy.ie wrote: @Sebastien - Is it ok to just copy and paste over what I had in that blog post? (Excluding the opening image and closing paragraph) On 5 July 2013 14:25, Prasanna Santhanam t...@apache.org wrote: On Fri, Jul 05, 2013 at 09:18:10AM -0400, 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) Excellent work so far. Great work all! -- Prasanna., Powered by BigRock.com
Re: [GSOC] Update to document
On Jul 5, 2013, at 10:35 AM, Ian Duffy i...@ianduffy.ie wrote: Sorry to create two emails in a row... Just in terms of the Google wants/needs deadline on the 29th, is there anything you guys, the cloudstack community specifically want to see? I am going to check exactly what Google requires, the evaluation will be submitted by your mentor: Abhi :) In general I think a prototype demo and seeing your code committed is really what we would like. So don't be afraid to commit, if you don't want to break the existing setup we can created a feature branch for you. But we'd rather see lots of small commits than a large chunk at the end. I know Abhi mentioned the creation of a prototype for me in one of the gtalk conversations we had awhile back. So I'm hoping to have the plugin I detailed in the blog post completely cleaned up and ready for review by you guys with full end to end testing by that date. This would allow me to have the second half of the Google summer of code term to work on creating a UI to allow admins to easily provision users and extending the plugin where/if required. As mentioned to Sebastien during the skype interviews I would *ideally* like to have the project wrapped up by the end of August, based on the progress so far this seems possible. On 5 July 2013 15:25, Ian Duffy i...@ianduffy.ie wrote: @Sebastien - Is it ok to just copy and paste over what I had in that blog post? (Excluding the opening image and closing paragraph) On 5 July 2013 14:25, Prasanna Santhanam t...@apache.org wrote: On Fri, Jul 05, 2013 at 09:18:10AM -0400, 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) Excellent work so far. Great work all! -- Prasanna., Powered by BigRock.com
