RE: [DISCUSS] UI: New look and feel
Hi, Sorry about that. Our ISP seems to be down. I am not sure if it will be back soon. Shiva Teja On Sep 30, 2013 10:04 AM, "Santhosh Edukulla" wrote: > Hi Shiva, > > Iam trying to access http://students.iitmandi.ac.in:2, but couldnt. > It seems there was a name resolution issue. Iam accessing it from my dev > box and using dns server "10.103.128.16" to resolve the uri in your link, > which is internal to citrix. May be you can provide the ip to check the > link directly if it is ok? > > BTW, I appreciate your effort, I am ok to join the development effort. > Though iam not much of a UI guy, one of our product in my earlier > organization used angular js and moved away from their earlier js > frameworks, They had very good views on this, it will be a good learning > for me to see. > > > Thanks! > Santhosh > > From: Shiva Teja [shivate...@gmail.com] > Sent: Sunday, September 29, 2013 2:33 PM > To: dev@cloudstack.apache.org" > Subject: Re: [DISCUSS] UI: New look and feel > > On Fri, Sep 27, 2013 at 5:44 PM, SuichII, Christopher < > chris.su...@netapp.com> wrote: > > > > > Shiva & Sebastien - What impact would this angular.js project have on UI > > plugins? > > > > It would definitely make it easy and offer cleaner code. I'll try to write > an overview soon. In a brief way : > > 1. You don't have to write any API calls. They'll be taken care by the > resources modules[0]. > 2. You don't have to do any DOM manipulation. Angular's directives[1] that > we write will take care of them. > 3. There's no 'listView' or 'detailView'. Each plugin can have its own > template(s)[2]. These templates must be very small if directives are used > effectively. 'confirm', 'vm-state-label', 'ng-repeat' are some of the > directives you can see in the template given at the end for example usage. > > Every tab that you see on the side nav bar in this UI is a plugin. So you > can checkout any plugin to start with. > > Demo is running at http://students.iitmandi.ac.in:2/ . It is running > on > DevCloud. Feel free to play around. Username and password are the default > ones: admin-password. > > As far as themes are concerned, I used bootstrap. So there are lots of > bootstrap themes out there which can be easily added to this UI without > worrying about breaking things. > > I am yet to add unit tests, add the functionalities to bring at par with > the current UI and clean up the designs. Maybe we could have both the UIs > for some time and then see how things go. If anybody is interested in > joining the further development, please let me know :) > > [0] > > https://github.com/shivateja/cloudstack-ui/tree/angular-rawapi/static/js/common/resources > [1] > > https://github.com/shivateja/cloudstack-ui/tree/angular-rawapi/static/js/common/directives > [2] This is an example template : > > https://github.com/shivateja/cloudstack-ui/blob/angular-rawapi/static/js/app/instances/instances.tpl.html > > Thanks, > Shiva Teja
Re: [DISCUSS] UI: New look and feel
On Fri, Sep 27, 2013 at 5:44 PM, SuichII, Christopher < chris.su...@netapp.com> wrote: > > Shiva & Sebastien - What impact would this angular.js project have on UI > plugins? It would definitely make it easy and offer cleaner code. I'll try to write an overview soon. In a brief way : 1. You don't have to write any API calls. They'll be taken care by the resources modules[0]. 2. You don't have to do any DOM manipulation. Angular's directives[1] that we write will take care of them. 3. There's no 'listView' or 'detailView'. Each plugin can have its own template(s)[2]. These templates must be very small if directives are used effectively. 'confirm', 'vm-state-label', 'ng-repeat' are some of the directives you can see in the template given at the end for example usage. Every tab that you see on the side nav bar in this UI is a plugin. So you can checkout any plugin to start with. Demo is running at http://students.iitmandi.ac.in:2/ . It is running on DevCloud. Feel free to play around. Username and password are the default ones: admin-password. As far as themes are concerned, I used bootstrap. So there are lots of bootstrap themes out there which can be easily added to this UI without worrying about breaking things. I am yet to add unit tests, add the functionalities to bring at par with the current UI and clean up the designs. Maybe we could have both the UIs for some time and then see how things go. If anybody is interested in joining the further development, please let me know :) [0] https://github.com/shivateja/cloudstack-ui/tree/angular-rawapi/static/js/common/resources [1] https://github.com/shivateja/cloudstack-ui/tree/angular-rawapi/static/js/common/directives [2] This is an example template : https://github.com/shivateja/cloudstack-ui/blob/angular-rawapi/static/js/app/instances/instances.tpl.html Thanks, Shiva Teja
Re: [DISCUSS] UI: New look and feel
On Fri, Sep 27, 2013 at 9:28 AM, Ian Duffy wrote: > I think so > implementation of AngularJS like the way Shiva did it for his GSoC > project would be good. > I'm trying to setup a demo for my project. This should give an idea about the code. https://github.com/shivateja/cloudstack-ui/blob/angular-rawapi/static/js/common/resources/virtualmachines.js https://github.com/shivateja/cloudstack-ui/blob/angular-rawapi/static/js/app/instances/instances.js https://github.com/shivateja/cloudstack-ui/blob/angular-rawapi/static/js/app/instances/instances.tpl.html Thanks, Shiva Teja
Re: [DISCUSS] CSS framework for CloudStack UI
Another positive side of using grunt would be to minimize and package javascript. Currently, we load a huge number of javascript files separately. It'd be great if we can minimize them into a single file during build. Also, if we were to add any UI tests using libraries like jasmine, grunt makes it easy automate them. Shiva Teja On Wed, Sep 18, 2013 at 9:49 PM, Brian Federle wrote: > Yeah, I'm definitely thinking the newer spec, which is better for us > anyway since it is backwards-compatible with existing CSS. > > What I'll do is setup a dummy branch, which basically renames > cloudstack3.css to cloudstack.scss or something like that, without much > modification right now, and then see if it can be converted to the .css. > > Re: NPM, -- that is actually why I suggested the SASS plugin instead of > the vanilla version of sass (installed via gem), since it would prevent > people from having to install yet another dependency on their system, since > I believe all required libs (including jRuby) are packaged in the jar, > which may eliminate the need for Grunt for now? > > -Brian > > From: Chip Childers [chip.child...@sungard.com] > Sent: Wednesday, September 18, 2013 6:01 AM > To: dev@cloudstack.apache.org > Cc: Rayees Namathponnan; Frank Zhang; Animesh Chaturvedi > Subject: Re: [DISCUSS] CSS framework for CloudStack UI > > On Wed, Sep 18, 2013 at 11:53:18AM +0530, Amit Das wrote: > > Hi Brian, > > > > I agree with Edison on usage of grunt & using maven-exec to call grunt. > > > > Will wait for your repository that has your experiments. > > I believe setting up the Maven tasks will be a one-time setting & should > > work without issues. > > IIRC, Grunt is installed via NPM. So does that pull in a bunch of new > developer requirements to build the project? Is there a standalone > installation for Grunt to lighten the build dependency chain? > > How about using SassC? [1] > > Let's be sure to use the scss spec, not the sass older style (HAML > inspired)! That appears to be Hampton's focus these days [2]. > > -chip > > [1] https://github.com/hcatlin/sassc > [2] Per intro on http://sass-lang.com/ >
[UI] Unnecessary cookie
Hi I was going through the UI code. The cookie for capabilities[0] is set to a JS object. It comes up as capabilities=%5Bobject%20Object%5D in the cookies. I don't think this is necessary. [0]: https://github.com/apache/cloudstack/blob/master/ui/scripts/cloudStack.js#L303 Thanks, Shiva Teja
Re: [GSOC][Urgent] Build docbook failed
Oops, *paste it somewhere On Sat, Jul 27, 2013 at 10:06 PM, Shiva Teja wrote: > Hi, > > Can you send the paste it somewhere and give a link? I can try. > > > On Sat, Jul 27, 2013 at 9:46 PM, Nguyen Anh Tu wrote: > >> Hi guys, >> >> I build my GSoC mid-term review and get an error here: >> >> Validation failed: >> CloudStack_GSoC_Guide.xml:67: validity error : Element itemizedlist >> content >> does not follow the DTD, expecting (blockinfo? , (title , titleabbrev?)? , >> (caution | important | note | tip | warning | literallayout | >> programlisting | programlistingco | screen | screenco | screenshot | >> synopsis | cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | >> constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | >> para | simpara | address | blockquote | graphic | graphicco | mediaobject >> | >> mediaobjectco | informalequation | informalexample | informalfigure | >> informaltable | anchor | bridgehead | remark | highlights | abstract | >> authorblurb | epigraph | indexterm | beginpage)* , listitem+), got >> (listitem mediaobject listitem mediaobject ) >> >> Sound like I use in wrong way. But I don't know what >> exactly >> causes the error. >> >> Urgent. Anyone can help? Thank so much! >> >> -- >> >> N.g.U.y.e.N.A.n.H.t.U >> > >
Re: [GSOC][Urgent] Build docbook failed
Hi, Can you send the paste it somewhere and give a link? I can try. On Sat, Jul 27, 2013 at 9:46 PM, Nguyen Anh Tu wrote: > Hi guys, > > I build my GSoC mid-term review and get an error here: > > Validation failed: > CloudStack_GSoC_Guide.xml:67: validity error : Element itemizedlist content > does not follow the DTD, expecting (blockinfo? , (title , titleabbrev?)? , > (caution | important | note | tip | warning | literallayout | > programlisting | programlistingco | screen | screenco | screenshot | > synopsis | cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | > constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | > para | simpara | address | blockquote | graphic | graphicco | mediaobject | > mediaobjectco | informalequation | informalexample | informalfigure | > informaltable | anchor | bridgehead | remark | highlights | abstract | > authorblurb | epigraph | indexterm | beginpage)* , listitem+), got > (listitem mediaobject listitem mediaobject ) > > Sound like I use in wrong way. But I don't know what exactly > causes the error. > > Urgent. Anyone can help? Thank so much! > > -- > > N.g.U.y.e.N.A.n.H.t.U >
Re: Review Request 12995: [GSoC] Add midterm report to docs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/12995/ --- (Updated July 27, 2013, 1:11 p.m.) Review request for cloudstack and Sebastien Goasguen. Repository: cloudstack-git Description --- GSoC - Add midterm review Diffs - docs/en-US/gsoc-midsummer-shiva.xml 67755c4 docs/en-US/images/add-account-screen.png PRE-CREATION docs/en-US/images/async-calls.png PRE-CREATION docs/en-US/images/configuration-edit-success.png PRE-CREATION docs/en-US/images/configurations-screen.png PRE-CREATION docs/en-US/images/create-account-post.png PRE-CREATION docs/en-US/images/create-account-request.png PRE-CREATION docs/en-US/images/edit-configuration.png PRE-CREATION docs/en-US/images/instances-screen.png PRE-CREATION docs/en-US/images/list-domain-vms.png PRE-CREATION docs/en-US/images/list-specific-vm.png PRE-CREATION docs/en-US/images/list-virtualmachines.png PRE-CREATION docs/en-US/images/start-vm-screen.png PRE-CREATION docs/en-US/images/vm-running.png PRE-CREATION Diff: https://reviews.apache.org/r/12995/diff/ Testing --- Build was successful with publican Thanks, Shiva Teja Reddy
Review Request 12995: [GSoC] Add midterm report to docs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/12995/ --- Review request for cloudstack and Sebastien Goasguen. Repository: cloudstack-git Description --- GSoC - Add midterm review Diffs - docs/en-US/gsoc-midsummer-shiva.xml 67755c4 docs/en-US/images/add-account-screen.png PRE-CREATION docs/en-US/images/async-calls.png PRE-CREATION docs/en-US/images/configuration-edit-success.png PRE-CREATION docs/en-US/images/configurations-screen.png PRE-CREATION docs/en-US/images/create-account-post.png PRE-CREATION docs/en-US/images/create-account-request.png PRE-CREATION docs/en-US/images/edit-configuration.png PRE-CREATION docs/en-US/images/instances-screen.png PRE-CREATION docs/en-US/images/list-domain-vms.png PRE-CREATION docs/en-US/images/list-specific-vm.png PRE-CREATION docs/en-US/images/list-virtualmachines.png PRE-CREATION docs/en-US/images/start-vm-screen.png PRE-CREATION docs/en-US/images/vm-running.png PRE-CREATION Diff: https://reviews.apache.org/r/12995/diff/ Testing --- Build was successful with publican Thanks, Shiva Teja Reddy
Re: [GSoC] Updates
Hi Rohit, On Thu, Jun 27, 2013 at 4:42 AM, Rohit Yadav wrote: > - Have search features right from beginning of your work. For ex. implement > something to search all fields on a table, make the head of the table > sortable. Have Lucene integration, which would be awesome to do searching. > A typical Cloud can have hundreds or thousands of instances etc. > Not sure if Lucene is needed here. It could done on the client side. It is a couple of minutes task to add a search feature with angular's filter directive. Here's an example from their tutorials( http://docs.angularjs.org/tutorial/step_03). Maybe this could just be enough. I am not sure about the performance with thousands of instances. Will look into it. I am yet to design the mockups for the final UI. I'll keep all other suggestions in mind. Thanks! Shiva Teja.
[GSoC] Updates
Hi all,
I made a little progress with my GSoC project("Create a Bootstrap based
UI"). I made basic prototypes with angular.js and backbone.js and I would
like to continue with angular.js. A demo of the prototype with angular.js
is available at http://students.iitmandi.ac.in:2/#/ . Currently, I am
finishing up reading angular.js docs and refactoring this prototype to
separate them into different modules.
Prototype with angular.js is available at
https://github.com/shivateja/cloudstack-ui/tree/angular
and prototype with backbone.js is at
https://github.com/shivateja/cloudstack-ui/
Regards,
Shiva Teja.
Re: [GSoC] Update
I am studying the current ui and still working on the prototype with angular.js. Hoping to finish it by sunday. On Fri, Jun 21, 2013 at 2:17 AM, Sebastien Goasguen wrote: > Dharmesh, Shiva, how are you guys doing ? > > -sebastien >
Review Request: Add GSoC proposal to docs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/11866/ --- Review request for cloudstack and Sebastien Goasguen. Description --- Added Shiva Teja's GSoC project(Create a new bootstrap based GUI for Apache CloudStack) proposal to docs Diffs - docs/en-US/CloudStack_GSoC_Guide.xml 1f43593 docs/en-US/gsoc-shiva.xml PRE-CREATION Diff: https://reviews.apache.org/r/11866/diff/ Testing --- Build was successful with publican Thanks, Shiva Teja Reddy
Re: [GSOC] Community Bonding Period
Oops, pressed send by mistake. Yes, the wrapper API will use Flask. On Thu, May 30, 2013 at 10:42 PM, Shiva Teja wrote: > Hey Kelcey, > > I was about to send an email off-list with updates. > Yes, the wrapper API > > > On Thu, May 30, 2013 at 10:37 PM, Kelcey Jamison Damage > wrote: > >> Hello Shiva, I am your mentor, lol. >> >> How's it going? I'm pretty excited about your project. >> >> Are you still planning to integrate Flask into your project? >> >> - Original Message - >> From: "Shiva Teja" >> To: dev@cloudstack.apache.org >> Sent: Thursday, May 30, 2013 9:54:26 AM >> Subject: Re: [GSOC] Community Bonding Period >> >> Hi, >> >> I am Shiva Teja, 2nd year computer science undergrad student from IIT >> Mandi, India. I'll be working on #CLOUDSTACK-1778 "Create a new bootstrap >> based GUI for CloudStack". I like algorithm research, web development and >> a >> bit of system administration. >> >> I'll be creating a new UI for CloudStack using Bootstrap by Twitter and >> Backbone.js. Along with this, I'll creating a RESTful wrapper API on top >> the current CloudStack API to make things easy working with backbone.js. I >> made a prototype along with my proposal which can found at >> https://github.com/shivateja/cloudstack-ui. This will make custom UIs >> very >> easy as the backbone models can be reused very easily. >> >> jira : https://issues.apache.org/jira/browse/CLOUDSTACK-1778 >> wiki: >> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Create+a+bootstrap+based+GUI+for+CloudStack >> (I messed up a bit too while creating the wiki page, same as Dharmesh's >> mistake. I think cleaned it up too.) >> Full proposal: >> >> https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/shivateja/1 >> Github : https://github.com/shivateja/ >> IRC nick: teja >> >> My username on JIRA, review board and wiki is teja. >> >> Looking forward for an awesome summer! >> >> Thanks, >> Shiva Teja >> >> >> On Thu, May 30, 2013 at 7:51 PM, Abhinandan Prateek < >> cloudst...@aprateek.com >> > wrote: >> >> > Welcome Ian ! >> > >> > On 30/05/13 3:05 AM, "Ian Duffy" wrote: >> > >> > >Hi All, >> > > >> > >My name is Ian Duffy and I will be working on the the project titled >> "LDAP >> > >User provisioning". I am a Computer Science Student at Dublin City >> > >University in Ireland. I have interests in virtualization, automation, >> > >information systems, networking and web development. >> > > >> > >The aim of my project, as stated in my proposal is to provide a more >> > >effective mechanism to provision users from LDAP into cloudstack. >> > >Currently >> > >cloudstack enables LDAP authentication. In this authentication users >> must >> > >be first setup in cloudstack. Once the user is setup in cloudstack they >> > >can >> > >authenticate using their ldap username and password. This project will >> > >improve cloudstack LDAP integration by enabling users to be >> automatically >> > >setup using their LDAP credentials. The full proposal can be seen here: >> > >http://ianduffy.ie/cloudstack-ldap.pdf >> > > >> > >JIRA entry: https://issues.apache.org/jira/browse/CLOUDSTACK-2014 >> > >Wiki page: >> > > >> > >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/LDAP+user+provision >> > >ing+in+cloudstack >> > > >> > >I have connected my BNC to #gsoc, #cloudstack and #cloudstack-dev under >> > >the >> > >nickname of imduffy15, so it should I should be there 24/7. I have >> added >> > >both Sebastien and Abhi on Skype, if anybody else wishes to connect on >> > >skype my username is duffyi3. >> > > >> > >I have registered accounts on JIRA, review board and the wiki under the >> > >username imduffy15. >> > > >> > >Look forward to working with you! >> > >Ian >> > >> > >> > >> > >
Re: [GSOC] Community Bonding Period
Hey Kelcey, I was about to send an email off-list with updates. Yes, the wrapper API On Thu, May 30, 2013 at 10:37 PM, Kelcey Jamison Damage wrote: > Hello Shiva, I am your mentor, lol. > > How's it going? I'm pretty excited about your project. > > Are you still planning to integrate Flask into your project? > > - Original Message - > From: "Shiva Teja" > To: dev@cloudstack.apache.org > Sent: Thursday, May 30, 2013 9:54:26 AM > Subject: Re: [GSOC] Community Bonding Period > > Hi, > > I am Shiva Teja, 2nd year computer science undergrad student from IIT > Mandi, India. I'll be working on #CLOUDSTACK-1778 "Create a new bootstrap > based GUI for CloudStack". I like algorithm research, web development and a > bit of system administration. > > I'll be creating a new UI for CloudStack using Bootstrap by Twitter and > Backbone.js. Along with this, I'll creating a RESTful wrapper API on top > the current CloudStack API to make things easy working with backbone.js. I > made a prototype along with my proposal which can found at > https://github.com/shivateja/cloudstack-ui. This will make custom UIs very > easy as the backbone models can be reused very easily. > > jira : https://issues.apache.org/jira/browse/CLOUDSTACK-1778 > wiki: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Create+a+bootstrap+based+GUI+for+CloudStack > (I messed up a bit too while creating the wiki page, same as Dharmesh's > mistake. I think cleaned it up too.) > Full proposal: > > https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/shivateja/1 > Github : https://github.com/shivateja/ > IRC nick: teja > > My username on JIRA, review board and wiki is teja. > > Looking forward for an awesome summer! > > Thanks, > Shiva Teja > > > On Thu, May 30, 2013 at 7:51 PM, Abhinandan Prateek < > cloudst...@aprateek.com > > wrote: > > > Welcome Ian ! > > > > On 30/05/13 3:05 AM, "Ian Duffy" wrote: > > > > >Hi All, > > > > > >My name is Ian Duffy and I will be working on the the project titled > "LDAP > > >User provisioning". I am a Computer Science Student at Dublin City > > >University in Ireland. I have interests in virtualization, automation, > > >information systems, networking and web development. > > > > > >The aim of my project, as stated in my proposal is to provide a more > > >effective mechanism to provision users from LDAP into cloudstack. > > >Currently > > >cloudstack enables LDAP authentication. In this authentication users > must > > >be first setup in cloudstack. Once the user is setup in cloudstack they > > >can > > >authenticate using their ldap username and password. This project will > > >improve cloudstack LDAP integration by enabling users to be > automatically > > >setup using their LDAP credentials. The full proposal can be seen here: > > >http://ianduffy.ie/cloudstack-ldap.pdf > > > > > >JIRA entry: https://issues.apache.org/jira/browse/CLOUDSTACK-2014 > > >Wiki page: > > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/LDAP+user+provision > > >ing+in+cloudstack > > > > > >I have connected my BNC to #gsoc, #cloudstack and #cloudstack-dev under > > >the > > >nickname of imduffy15, so it should I should be there 24/7. I have added > > >both Sebastien and Abhi on Skype, if anybody else wishes to connect on > > >skype my username is duffyi3. > > > > > >I have registered accounts on JIRA, review board and the wiki under the > > >username imduffy15. > > > > > >Look forward to working with you! > > >Ian > > > > > > >
Re: [GSOC] Community Bonding Period
Hi, I am Shiva Teja, 2nd year computer science undergrad student from IIT Mandi, India. I'll be working on #CLOUDSTACK-1778 "Create a new bootstrap based GUI for CloudStack". I like algorithm research, web development and a bit of system administration. I'll be creating a new UI for CloudStack using Bootstrap by Twitter and Backbone.js. Along with this, I'll creating a RESTful wrapper API on top the current CloudStack API to make things easy working with backbone.js. I made a prototype along with my proposal which can found at https://github.com/shivateja/cloudstack-ui. This will make custom UIs very easy as the backbone models can be reused very easily. jira : https://issues.apache.org/jira/browse/CLOUDSTACK-1778 wiki: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Create+a+bootstrap+based+GUI+for+CloudStack (I messed up a bit too while creating the wiki page, same as Dharmesh's mistake. I think cleaned it up too.) Full proposal: https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/shivateja/1 Github : https://github.com/shivateja/ IRC nick: teja My username on JIRA, review board and wiki is teja. Looking forward for an awesome summer! Thanks, Shiva Teja On Thu, May 30, 2013 at 7:51 PM, Abhinandan Prateek wrote: > Welcome Ian ! > > On 30/05/13 3:05 AM, "Ian Duffy" wrote: > > >Hi All, > > > >My name is Ian Duffy and I will be working on the the project titled "LDAP > >User provisioning". I am a Computer Science Student at Dublin City > >University in Ireland. I have interests in virtualization, automation, > >information systems, networking and web development. > > > >The aim of my project, as stated in my proposal is to provide a more > >effective mechanism to provision users from LDAP into cloudstack. > >Currently > >cloudstack enables LDAP authentication. In this authentication users must > >be first setup in cloudstack. Once the user is setup in cloudstack they > >can > >authenticate using their ldap username and password. This project will > >improve cloudstack LDAP integration by enabling users to be automatically > >setup using their LDAP credentials. The full proposal can be seen here: > >http://ianduffy.ie/cloudstack-ldap.pdf > > > >JIRA entry: https://issues.apache.org/jira/browse/CLOUDSTACK-2014 > >Wiki page: > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/LDAP+user+provision > >ing+in+cloudstack > > > >I have connected my BNC to #gsoc, #cloudstack and #cloudstack-dev under > >the > >nickname of imduffy15, so it should I should be there 24/7. I have added > >both Sebastien and Abhi on Skype, if anybody else wishes to connect on > >skype my username is duffyi3. > > > >I have registered accounts on JIRA, review board and the wiki under the > >username imduffy15. > > > >Look forward to working with you! > >Ian > > >
Re: [GSOC] deadline today
Any last minute reviews on https://gist.github.com/shivateja/f1651c21563b5dbe0f16 ? Thanks, Shiva Teja. On Fri, May 3, 2013 at 11:33 PM, Sebastien Goasguen wrote: > Remember to submit your proposals today. This is the end of the > application period. > > -Sebastien
Re: [GSoC] Introduction and Project Discussion
This probably needs of lot of discussion. For now, I'll stick to basics and
concentrate more on the UI. Thanks for the help.
Regards,
Shiva Teja.
On Mon, Apr 29, 2013 at 10:45 AM, Rohit Yadav wrote:
> On Mon, Apr 29, 2013 at 1:53 AM, Shiva Teja wrote:
>
> > Hi Rohit,
> >
> > I think you made my work a lot easier :) I can use code from cloudmonkey
> to
> > generate API cache and then build the code for the wrapper using it.
> >
> > I might need some information on this. How would a RESTful CloudStack API
> > look like ?
>
>
> This is a hard issue because the challenge is not just to implement
> something, but something that will be maintainable. Your APIs are your
> interface or contract to the outside world so once you give away your spec
> to the outside world, you've the burden to keep backward compatibility and
> not mess up when you do any kind of refactoring.
>
> Some general rules I see are; all entities are nouns, the verbs are not
> part of the url but how you call them; so list/read would be GET, create
> would be POST, update would be PUT, remove/del would be DELETE... that said
> you can create your own X- headers to mean something. People have written
> books, gave talk on how to write good RESTful APIs.
>
>
> > If I get these basic rules, I am guessing it shouldn't be tough
> > to generate the wrapper.
> >
>
> The implementation won't be tough, but getting it right would be. Right now
> I'm just splitting the apiname at the camelCase's hump in cloudmonkey, so
> camel becomes a command and Case becomes the entity.
>
>
> >
> > Here's a very basic idea. I am using the same terminology used in
> > cloudmonkey. In "listUsers", users is subject and list is the verb.
> > In most of the cases the URL for an API command can be something like
> > "baseurl/subject/verb" with an appropriately chosen HTTP method based on
> > the verb. For some "verbs" like list, get, update, delete, add, it
> doesn't
> > make sense to have them in the URL and using the appropriate HTTP method
> > would mean the same. So I'll have to write the rules for each verb. These
> > rules might contain method to be used for the verb, should the verb be in
> > the URL or not...etc. And use these rules to generate the wrapper.
> >
>
> It's not straight forward, for example create/add/generate are few words in
> apis which would be GET Apis in restful terms. One way would be to manually
> sort/group the apis, other would be to annotate each api with an entity
> name, RESTful type {one of GET, POST, PUT etc.} and parent (For example,
> /zone/pod/cluster makes sense?).
>
>
> > I am trying to decide these rules, so that they don't deviate from the
> > point of being a RESTful API. Will get back with final implementation
> > details before I finish my application for GSoC.
> >
>
> Lastly, talk to Sebastien or someone who would is participating in GSoC as
> a mentor because it's important to identify who would mentor you if they
> would, best of luck.
>
> Cheers.
> I'm skipping applying to being a GSoC mentor this year, pissed off from
> GSoC admins this year. FOSS is just going to dogs; fck they did not include
> one project that has no real company to back its development and really
> needs help; VideoLAN/VLC.
>
>
>
> > Regard,
> > Shiva Teja(irc: teja)
> >
> >
> > On Sat, Apr 27, 2013 at 10:14 PM, Rohit Yadav
> wrote:
> >
> > > Hi Shiva,
> > >
> > > On Sat, Apr 27, 2013 at 1:29 AM, Shiva Teja
> > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I am Shiva Teja, an undergrad student from IIT Mandi, India. I will
> be
> > > > participating in GSoC this year. I'd like to work on the new
> CloudStack
> > > UI
> > > > with bootstrap project[1]. I've been experimenting with API for the
> > past
> > > > few days. After reading a couple of blog posts by Sebastien, his
> recent
> > > > hack on this[2] and a recent discussion[3] on the mailing list about
> > > making
> > > > CloudStack API RESTfull, here are the things I plan to do.
> > > >
> > >
> > > Have you started working on your plan or just proposing? Hope you have
> a
> > > setup and tried CloudStack on DevCloud. For starters I suggest you to
> > > download, build and deploy CloudStack, play around APIs, cloudmonkey (a
> > > CLI) and the API Discovery service because both of your idea proposals
> > are
> > > around APIs
Re: [GSoC] Introduction and Project Discussion
Hi Rohit, I think you made my work a lot easier :) I can use code from cloudmonkey to generate API cache and then build the code for the wrapper using it. I might need some information on this. How would a RESTful CloudStack API look like ? If I get these basic rules, I am guessing it shouldn't be tough to generate the wrapper. Here's a very basic idea. I am using the same terminology used in cloudmonkey. In "listUsers", users is subject and list is the verb. In most of the cases the URL for an API command can be something like "baseurl/subject/verb" with an appropriately chosen HTTP method based on the verb. For some "verbs" like list, get, update, delete, add, it doesn't make sense to have them in the URL and using the appropriate HTTP method would mean the same. So I'll have to write the rules for each verb. These rules might contain method to be used for the verb, should the verb be in the URL or not...etc. And use these rules to generate the wrapper. I am trying to decide these rules, so that they don't deviate from the point of being a RESTful API. Will get back with final implementation details before I finish my application for GSoC. Regard, Shiva Teja(irc: teja) On Sat, Apr 27, 2013 at 10:14 PM, Rohit Yadav wrote: > Hi Shiva, > > On Sat, Apr 27, 2013 at 1:29 AM, Shiva Teja wrote: > > > Hi all, > > > > I am Shiva Teja, an undergrad student from IIT Mandi, India. I will be > > participating in GSoC this year. I'd like to work on the new CloudStack > UI > > with bootstrap project[1]. I've been experimenting with API for the past > > few days. After reading a couple of blog posts by Sebastien, his recent > > hack on this[2] and a recent discussion[3] on the mailing list about > making > > CloudStack API RESTfull, here are the things I plan to do. > > > > Have you started working on your plan or just proposing? Hope you have a > setup and tried CloudStack on DevCloud. For starters I suggest you to > download, build and deploy CloudStack, play around APIs, cloudmonkey (a > CLI) and the API Discovery service because both of your idea proposals are > around APIs. > > 1. A more "human", RESTfull wrapper API on top of CloudStack API using > > Flask python framework. Something like "GET /users" will directly > > correspond to "listUsers" API command. "DELETE /user/" will > correspond > > to the respective "deleteUser" API call. > > > > It's tricky, first you should get a full list of entities. It's a lot of > hard work if you do it manually but you can do smartly if you use Api > Discovery. There are more than 300+ APIs in CloudStack, now groupped as per > entities (see a package like org.apache.cloudstack.api.. class>). > > So, first you need to classify the entities, get it checked (like write > tests) and then define these operations. Few of us are inclined towards > rewriting an API server that is RESTful and not query based. The challenge > there is to reuse present cmd classes, one way is to use reflections and > another round of api annotations refactoring. Easiest way would be to just > fix/add/reuse Api Discovery, or write something use metaprogamming that > auto generates your wrapper. > > I'm floating these ideas so you can think about it and come up with a > strategy that creates maintainable, extendable code which would require > less time to implement it. > > 2. A complete UI designed using Twitter Bootstrap and Backbone.js. > > Obviously this will use the API that I'll be making. > > > > +1 This is a fantastic idea, a better, faster, modular UI that is > responsive is much appreciated and we will have an alternative to the > default one. > > Avoid sending direct emails to anyone and feel free to reach out to the dev > ML, email like a boss™. > > Happy hacking! > > Cheers. > > (An app made using Bootstrap and Backbone.js: > > http://coenraets.org/directory/ ) > > > > Any suggestions/comments ? > > > > [1] https://issues.apache.org/jira/browse/CLOUDSTACK-1778 > > [2] https://github.com/runseb/cloudstack-flask > > [3] > > > > > http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201304.mbox/%3C20130424083847.GA11354%40cloud-2.local%3E > > > > Thanks, > > Shiva Teja. > > >
[GSoC] Introduction and Project Discussion
Hi all, I am Shiva Teja, an undergrad student from IIT Mandi, India. I will be participating in GSoC this year. I'd like to work on the new CloudStack UI with bootstrap project[1]. I've been experimenting with API for the past few days. After reading a couple of blog posts by Sebastien, his recent hack on this[2] and a recent discussion[3] on the mailing list about making CloudStack API RESTfull, here are the things I plan to do. 1. A more "human", RESTfull wrapper API on top of CloudStack API using Flask python framework. Something like "GET /users" will directly correspond to "listUsers" API command. "DELETE /user/" will correspond to the respective "deleteUser" API call. 2. A complete UI designed using Twitter Bootstrap and Backbone.js. Obviously this will use the API that I'll be making. (An app made using Bootstrap and Backbone.js: http://coenraets.org/directory/ ) Any suggestions/comments ? [1] https://issues.apache.org/jira/browse/CLOUDSTACK-1778 [2] https://github.com/runseb/cloudstack-flask [3] http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201304.mbox/%3C20130424083847.GA11354%40cloud-2.local%3E Thanks, Shiva Teja.
