- Release-team - mailman3.cels.anl.gov

Re: [Release-team] CDMI Client Libraries on Downloads page
by Shiran Pasternak 21 Feb '13

21 Feb '13

Yes, I have a process that does that compression/uglification/minification (I use UglifyJS). I think that folks that want to use their own custom one can build it themselves using their desired set of services. Usually, JS libraries are distributed in both forms, so that the unminified version can be used for debugging. We'd call it kbase.js and kbase.min.js. What do you think? For both, I include a preamble at the top that looks like this: /** * The KBase API * http://kbase.us * * API documentation: http://kbase.us/developer-zone/api-documentation/ * @license Copyright (c) 2013, The DOE Systems Biology Knowledgebase Project */ Shiran On Feb 21, 2013, at 9:36 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > Not sure. I thought I saw some talk that looked like concatenating all kbase js libs into a single one, then folks saying that they custom select what they use. > > I think in any case, you could run the js libs through one of those js compressors, I forget what they are called, but you know, they take out whitespace, make the libs significantly smaller. > > Really though, I;m worse than a js000nb. What makes sense to you? > > We can always change our mind in the future, and make old libs available in the archives area of downloads. > > > t > > > > > On Feb 21, 2013, at 8:31 PM, Shiran Pasternak <shiranpasternak(a)gmail.com> wrote: > >> I handle the JS client APIs, but can also distribute the python libraries as a package, which are being deployed alongside the JavaScript libraries. But isn't it misleading to only release the CDMI API as a standalone? >> >> Thoughts? >> Shiran >> >> >> >> On Feb 21, 2013, at 8:35 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: >> >>> shiran maybe? >>> >>> >>> On Feb 21, 2013, at 7:34 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>> >>>> Is someone planning to update these today or tomorrow? >>>> <Screen Shot 2013-02-21 at 5.33.08 PM.png> >>>> >>>> Thanks, >>>> Nomi >>>> >>>> _______________________________________________ >>>> Release-team mailing list >>>> Release-team(a)lists.kbase.us >>>> https://lists.kbase.us/mailman/listinfo/release-team >>> >>> Thomas Brettin >>> 865-603-7760 (cell) >>> brettin(a)mcs.anl.gov >>> >>> >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/release-team >> > > Thomas Brettin > 865-603-7760 (cell) > brettin(a)mcs.anl.gov > > >

1 0

Re: [Release-team] CDMI Client Libraries on Downloads page
by Thomas Brettin 21 Feb '13

21 Feb '13

Not sure. I thought I saw some talk that looked like concatenating all kbase js libs into a single one, then folks saying that they custom select what they use. I think in any case, you could run the js libs through one of those js compressors, I forget what they are called, but you know, they take out whitespace, make the libs significantly smaller. Really though, I;m worse than a js000nb. What makes sense to you? We can always change our mind in the future, and make old libs available in the archives area of downloads. t On Feb 21, 2013, at 8:31 PM, Shiran Pasternak <shiranpasternak(a)gmail.com> wrote: > I handle the JS client APIs, but can also distribute the python libraries as a package, which are being deployed alongside the JavaScript libraries. But isn't it misleading to only release the CDMI API as a standalone? > > Thoughts? > Shiran > > > > On Feb 21, 2013, at 8:35 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > >> shiran maybe? >> >> >> On Feb 21, 2013, at 7:34 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> Is someone planning to update these today or tomorrow? >>> <Screen Shot 2013-02-21 at 5.33.08 PM.png> >>> >>> Thanks, >>> Nomi >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/release-team >> >> Thomas Brettin >> 865-603-7760 (cell) >> brettin(a)mcs.anl.gov >> >> >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team > Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

Re: [Release-team] CDMI Client Libraries on Downloads page
by Shiran Pasternak 21 Feb '13

21 Feb '13

I handle the JS client APIs, but can also distribute the python libraries as a package, which are being deployed alongside the JavaScript libraries. But isn't it misleading to only release the CDMI API as a standalone? Thoughts? Shiran On Feb 21, 2013, at 8:35 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > shiran maybe? > > > On Feb 21, 2013, at 7:34 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Is someone planning to update these today or tomorrow? >> <Screen Shot 2013-02-21 at 5.33.08 PM.png> >> >> Thanks, >> Nomi >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team > > Thomas Brettin > 865-603-7760 (cell) > brettin(a)mcs.anl.gov > > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] CDMI Client Libraries on Downloads page
by Thomas Brettin 21 Feb '13

21 Feb '13

shiran maybe? On Feb 21, 2013, at 7:34 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Is someone planning to update these today or tomorrow? > <Screen Shot 2013-02-21 at 5.33.08 PM.png> > > Thanks, > Nomi > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

CDMI Client Libraries on Downloads page
by Nomi Harris 21 Feb '13

21 Feb '13

Is someone planning to update these today or tomorrow? Thanks, Nomi

1 0

Production deploy of experiment
by Land, Miriam L. 21 Feb '13

21 Feb '13

I saw an 11th hour modification to experiment with a test deploy by Shane and a test by Keith (actually the email said 12:48 am here). Was that change deployed to production today? Miriam

1 0

Re: [Release-team] feature_selection API doc is in Fizzy instead of feature_selection directory
by Land, Miriam L. 21 Feb '13

21 Feb '13

Just talked to Andreas. He says that it should be public and exciting is in the eye of the beholder. He would like to go forward with the link you describe below for this go around. Dan and Andreas can talk about how to change things in the future. Miriam On 2/21/13 2:42 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >Wait, is this even going to be a public service, or is it just a >dependency? It doesn't sound very exciting for the average user: > * MODULE: Fizzy > * This service receives a list of strings containing the options > * containing the metagenome IDs that will build the data matrix > * for feature selection. The SOURCE should be specified according > * to the available options specified by the KBase matrix service. > * The Fizzy service returns a list of strings contains the feature > * names that were selected. > > Nomi > >On Feb 21, 2013, at 11:39 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Dear Deploy team, >> >> Would it be possible to make the contents of >>/kb/deployment/services/Fizzy/webroot/Fizzy.html visible from >>http://140.221.84.191/services/docs/ so we can get at the API doc for >>feature_selection (even though it's deploying to the wrong directory)? >>It seems like that would be quicker at this point than getting the >>developer to fix the path and redeploying. >> >> BTW, feature_selection is not on the Master tab >>(https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppa >>EJzOUdfMV8zN0Y3Vm5YM095aWc&pli=1#gid=15) so I will also need a >>description of it to add to the Services page, if we're really releasing >>it today. >> >> Thanks, >> Nomi >> >> Begin forwarded message: >> >>> From: "Land, Miriam L." <landml(a)ornl.gov> >>> Subject: FW: feature_selection >>> Date: February 21, 2013 10:48:12 AM PST >>> To: Nomi Harris <nlharris(a)lbl.gov>, Tom Brettin <brettin(a)mcs.anl.gov> >>> >>> Tom and Nomi, >>> >>> The feature_selection has passed testing and the spreadsheet has been >>> updated to reflect this. The documentation, however, is still >>>missing. I >>> believe that it is due to non-standard names. Instead of >>> >>> >>> /kb/deployment/services/feature_selection/webroot/feature_selection.htm >>>l >>> it is >>> /kb/deployment/services/Fizzy/webroot/Fizzy.html >>> >>> >>> Miriam >>> >>> On 2/21/13 1:38 PM, "Dan Olson" <dolson(a)mcs.anl.gov> wrote: >>> >>>> yes >>>> >>>> ----- Original Message ----- >>>>> From: "Miriam L. Land" <landml(a)ornl.gov> >>>>> To: "Dan Olson" <dolson(a)mcs.anl.gov> >>>>> Cc: "Thomas Brettin" <brettin(a)mcs.anl.gov>, "Andreas Wilke" >>>>> <wilke(a)mcs.anl.gov> >>>>> Sent: Thursday, February 21, 2013 12:27:48 PM >>>>> Subject: Re: test protocol >>>>> >>>>> Sounds like feature_selection passed testing. I deployed it on my >>>>> own >>>>> instance and the tests ran there. >>>>> >>>>> Is it okay if I mark the spreadsheet as passing testing deploy (to >>>>> get rid >>>>> of the big red rectangle)? >>>>> >>>>> Miriam >> > >_______________________________________________ >Release-team mailing list >Release-team(a)lists.kbase.us >https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] feature_selection API doc is in Fizzy instead of feature_selection directory
by Nomi Harris 21 Feb '13

21 Feb '13

Wait, is this even going to be a public service, or is it just a dependency? It doesn't sound very exciting for the average user: * MODULE: Fizzy * This service receives a list of strings containing the options * containing the metagenome IDs that will build the data matrix * for feature selection. The SOURCE should be specified according * to the available options specified by the KBase matrix service. * The Fizzy service returns a list of strings contains the feature * names that were selected. Nomi On Feb 21, 2013, at 11:39 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Dear Deploy team, > > Would it be possible to make the contents of /kb/deployment/services/Fizzy/webroot/Fizzy.html visible from http://140.221.84.191/services/docs/ so we can get at the API doc for feature_selection (even though it's deploying to the wrong directory)? It seems like that would be quicker at this point than getting the developer to fix the path and redeploying. > > BTW, feature_selection is not on the Master tab (https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaEJz…) so I will also need a description of it to add to the Services page, if we're really releasing it today. > > Thanks, > Nomi > > Begin forwarded message: > >> From: "Land, Miriam L." <landml(a)ornl.gov> >> Subject: FW: feature_selection >> Date: February 21, 2013 10:48:12 AM PST >> To: Nomi Harris <nlharris(a)lbl.gov>, Tom Brettin <brettin(a)mcs.anl.gov> >> >> Tom and Nomi, >> >> The feature_selection has passed testing and the spreadsheet has been >> updated to reflect this. The documentation, however, is still missing. I >> believe that it is due to non-standard names. Instead of >> >> /kb/deployment/services/feature_selection/webroot/feature_selection.html >> it is >> /kb/deployment/services/Fizzy/webroot/Fizzy.html >> >> >> Miriam >> >> On 2/21/13 1:38 PM, "Dan Olson" <dolson(a)mcs.anl.gov> wrote: >> >>> yes >>> >>> ----- Original Message ----- >>>> From: "Miriam L. Land" <landml(a)ornl.gov> >>>> To: "Dan Olson" <dolson(a)mcs.anl.gov> >>>> Cc: "Thomas Brettin" <brettin(a)mcs.anl.gov>, "Andreas Wilke" >>>> <wilke(a)mcs.anl.gov> >>>> Sent: Thursday, February 21, 2013 12:27:48 PM >>>> Subject: Re: test protocol >>>> >>>> Sounds like feature_selection passed testing. I deployed it on my >>>> own >>>> instance and the tests ran there. >>>> >>>> Is it okay if I mark the spreadsheet as passing testing deploy (to >>>> get rid >>>> of the big red rectangle)? >>>> >>>> Miriam >

1 0

feature_selection API doc is in Fizzy instead of feature_selection directory
by Nomi Harris 21 Feb '13

21 Feb '13

Dear Deploy team, Would it be possible to make the contents of /kb/deployment/services/Fizzy/webroot/Fizzy.html visible from http://140.221.84.191/services/docs/ so we can get at the API doc for feature_selection (even though it's deploying to the wrong directory)? It seems like that would be quicker at this point than getting the developer to fix the path and redeploying. BTW, feature_selection is not on the Master tab (https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaEJz…) so I will also need a description of it to add to the Services page, if we're really releasing it today. Thanks, Nomi Begin forwarded message: > From: "Land, Miriam L." <landml(a)ornl.gov> > Subject: FW: feature_selection > Date: February 21, 2013 10:48:12 AM PST > To: Nomi Harris <nlharris(a)lbl.gov>, Tom Brettin <brettin(a)mcs.anl.gov> > > Tom and Nomi, > > The feature_selection has passed testing and the spreadsheet has been > updated to reflect this. The documentation, however, is still missing. I > believe that it is due to non-standard names. Instead of > > /kb/deployment/services/feature_selection/webroot/feature_selection.html > it is > /kb/deployment/services/Fizzy/webroot/Fizzy.html > > > Miriam > > On 2/21/13 1:38 PM, "Dan Olson" <dolson(a)mcs.anl.gov> wrote: > >> yes >> >> ----- Original Message ----- >>> From: "Miriam L. Land" <landml(a)ornl.gov> >>> To: "Dan Olson" <dolson(a)mcs.anl.gov> >>> Cc: "Thomas Brettin" <brettin(a)mcs.anl.gov>, "Andreas Wilke" >>> <wilke(a)mcs.anl.gov> >>> Sent: Thursday, February 21, 2013 12:27:48 PM >>> Subject: Re: test protocol >>> >>> Sounds like feature_selection passed testing. I deployed it on my >>> own >>> instance and the tests ran there. >>> >>> Is it okay if I mark the spreadsheet as passing testing deploy (to >>> get rid >>> of the big red rectangle)? >>> >>> Miriam

1 0

URL confusion
by Dan Olson 21 Feb '13

21 Feb '13

The URLs defined in production are *exactly* what was in test. I think I need to remove the URL Module tab to prevent confusion. We are working toward the form in the URL Module tab, but we aren't there yet.

1 0