This morning I dealt with some more issues raised in security scans of Quicksilver, as well as fixing an error they had revealed and improving the error handling.
This afternoon I went to the Grid kickoff meeting, and after that I was focusing on cleanup and implementing some more of the service implementation for NPDSAMDS
Showing posts with label NPDS-AMDS. Show all posts
Showing posts with label NPDS-AMDS. Show all posts
Thursday, April 16, 2009
Tuesday, April 14, 2009
Discussions and progress
Today we had a meeting about some of the ways that the AMDS grid services and AMDS viewers are going to interact in their planned environments. It helped clear up a lot of ambiguities about how they would connect to each other and what sorts of security requirements would be needed and what sorts of security should be expected at different points on the grid.
We also had discussions about ways to handle CAs now and in the future, and how to package things so that we make it easier for other developers to play with stuff should they want to.
I have been making some progress with the NPDSAMDS project, and forgot how handy it is to just write the interface and start pulling in types to wrap your head around all the bits in a service. I really do grok java better than XML Schema still.
Finally, I have been stopping what I was doing to help deal with minor issues in the production deploy of QuickSilver. Said deploy will probably loom for some time, but I can't complain because, hey, code going live is neat!
We also had discussions about ways to handle CAs now and in the future, and how to package things so that we make it easier for other developers to play with stuff should they want to.
I have been making some progress with the NPDSAMDS project, and forgot how handy it is to just write the interface and start pulling in types to wrap your head around all the bits in a service. I really do grok java better than XML Schema still.
Finally, I have been stopping what I was doing to help deal with minor issues in the production deploy of QuickSilver. Said deploy will probably loom for some time, but I can't complain because, hey, code going live is neat!
Friday, April 10, 2009
Creating a new maven project: npdsamds
I have created a new maven project to hold the service end of the npds-to-amds code, and it is appropriately named npdsamds. It will essentially be a gridified version of the npds service that should be served up via a globus container (Thus requiring security and all that jazz).
Maven solves many worlds of hurt with its dependency management, and the repositories where you can store jars so that others may use them. It also makes other tools pale in comparison and seem much more annoying.
One of them is SVN, which for some reason is "old" on my copy of ubuntu and cannot be easily upgraded using the standard ubuntu tools. Thus, whenever I try and add new projects to the SVN repository or move files, I always have to create new folders and re-check-out the code because otherwise the version of subclipse I use with (you guessed it) eclipse touches the svn special secret hidden files and makes it so that lowly command-line subversion is eschewed from adding the files. I also have to do this every time that subclipse botches something.
The other tool is ant. Don't get me wrong, maven /uses/ ant. But maven is to ant as a chocolate cake is to baker's chocolate. The combination maven of which ant is a part, is much better than the bitter chunks of ant by itself. Ant offers all sorts of commands that rely on all sorts of duck-aligning and basically anyone who writes an ant script also has to write a very long doc about what each part of the script can do and how to invoke it. Maven, you can usually just tell someone "type 'mvn package'" and it will produce the thingy they need, and it is a LOT easier for the person who coded the stuff inside the maven package to set up the project that way.
Don't get me wrong, both tools are very powerful and useful in their own right. I just have a small personal bias in that maven hasn't made me curse it's name yet.
But, we might write a plugin that allows maven to build globus services. So, I'm sure I will be cursing it's name soon enough.
Maven solves many worlds of hurt with its dependency management, and the repositories where you can store jars so that others may use them. It also makes other tools pale in comparison and seem much more annoying.
One of them is SVN, which for some reason is "old" on my copy of ubuntu and cannot be easily upgraded using the standard ubuntu tools. Thus, whenever I try and add new projects to the SVN repository or move files, I always have to create new folders and re-check-out the code because otherwise the version of subclipse I use with (you guessed it) eclipse touches the svn special secret hidden files and makes it so that lowly command-line subversion is eschewed from adding the files. I also have to do this every time that subclipse botches something.
The other tool is ant. Don't get me wrong, maven /uses/ ant. But maven is to ant as a chocolate cake is to baker's chocolate. The combination maven of which ant is a part, is much better than the bitter chunks of ant by itself. Ant offers all sorts of commands that rely on all sorts of duck-aligning and basically anyone who writes an ant script also has to write a very long doc about what each part of the script can do and how to invoke it. Maven, you can usually just tell someone "type 'mvn package'" and it will produce the thingy they need, and it is a LOT easier for the person who coded the stuff inside the maven package to set up the project that way.
Don't get me wrong, both tools are very powerful and useful in their own right. I just have a small personal bias in that maven hasn't made me curse it's name yet.
But, we might write a plugin that allows maven to build globus services. So, I'm sure I will be cursing it's name soon enough.
Thursday, April 9, 2009
Transitioning
Today I spent a some time transitioning with Felicia, learning where the docs are for dealing with library conflicts, that sort of thing.
Otherwise, I contributed a bit Brian and Vaughn's discussions about how grid services will deal with different security schemes and how they should be loaded, and I have a much better idea for how to design my NPDS-AMDS service and the new AMDS viewer client.
Most of today was spent helping the SDN team get Quicksilver ready for deployment. I helped debug a database issue, and wrote the "these are the properties files you need to change to deploy to a new server" guide.
Cheers!
Otherwise, I contributed a bit Brian and Vaughn's discussions about how grid services will deal with different security schemes and how they should be loaded, and I have a much better idea for how to design my NPDS-AMDS service and the new AMDS viewer client.
Most of today was spent helping the SDN team get Quicksilver ready for deployment. I helped debug a database issue, and wrote the "these are the properties files you need to change to deploy to a new server" guide.
Cheers!
Subscribe to:
Posts (Atom)
Posts
