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

Re: [Release-team] Fwd: API doc for regprecise
by Dan Olson 13 Feb '13

13 Feb '13

I've redeployed this. It gets a startup error, which it seems to have always had.. It doesn't look like it affects deployment, but I'm going to bring it up with the owner. -- root@t21:~# ./deploy.rsc Service is regprecise No pid file /kb/deployment/services/cdmi_api/service.pid found for service cdmi_api No pid file /kb/deployment/services/idserver/service.pid found for service idserver Waiting for the domain to stop ..... Command stop-domain executed successfully. - Cloning dev_container - Cloning kb_seed - Cloning kbapi_common - Cloning typecomp - Cloning auth - Cloning idserver Running Make in dev_container Running Make deploy in dev_container ==== Deploying regprecise - Cloning regprecise * Using 20130213-test for regprecise - Processing dependencies for regprecise Starting bootstrap at /kb/dev_container Running make Running make deploy root@t21:~# There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server. Command start-domain failed. ----- Original Message ----- > From: "Miriam L. Land" <landml(a)ornl.gov> > To: "Nomi Harris" <nlharris(a)lbl.gov>, release-team(a)lists.kbase.us > Sent: Wednesday, February 13, 2013 10:29:48 AM > Subject: Re: [Release-team] Fwd: API doc for regprecise > > Nomi, > > I've marked the spreadsheet for redeploy of regprecise. > > Miriam > > From: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> > Date: Wednesday, February 13, 2013 10:26 AM > To: "release-team(a)lists.kbase.us<mailto:[email protected]>" > <release-team(a)lists.kbase.us<mailto:[email protected]>> > Subject: [Release-team] Fwd: API doc for regprecise [was Re: Initial > tech doc results for your module (Full Build, Feb 4, 2013)] > > Dear Deploy team, > Can you re-deploy regprecise? > Thanks, > Nomi > > Begin forwarded message: > > From: "Yoo, Shinjae" <sjyoo(a)bnl.gov<mailto:[email protected]>> > Subject: Re: API doc for regprecise [was Re: Initial tech doc results > for your module (Full Build, Feb 4, 2013)] > Date: February 13, 2013 12:51:00 AM PST > To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> > Cc: Pavel Novichkov <psnovichkov(a)lbl.gov<mailto:[email protected]>> > > > Nomi, > > Your suggested changes is in place now: > > root@ntest:/kb/dev_container/modules/regprecise# ls -al > /kb/deployment/services/Regulation/webroot/ > total 40 > drwxr-xr-x 2 root root 4096 2013-02-13 08:48 . > drwxr-xr-x 3 root root 4096 2013-02-13 08:48 .. > -rw-r--r-- 1 root root 32716 2013-02-13 08:48 Regulation.html > root@ntest:/kb/dev_container/modules/regprecise# > > Please let me know if you have any other issues with Makefile. > > Thanks, > -SJ > > On Feb 13, 2013, at 3:41 AM, Shinjae Yoo wrote: > > Thanks Nomi, > > Two things: > > 1) deploy-docs target fixed last week > It seems the Makefile is old version > > 2) If you want just empty folder as web root, I can make changes to > deploy-dir target to have empty webroot folder to copy it. > I'll make this change now and test it on my test VM. > > -SJ > > On Feb 12, 2013, at 5:46 PM, Nomi Harris wrote: > > (Sorry, forgot to cc you, Shinjae.) > Nomi > > Begin forwarded message: > > From: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> > Subject: API doc for regprecise [was Re: Initial tech doc results for > your module (Full Build, Feb 4, 2013)] > Date: February 12, 2013 11:55:19 AM PST > To: Pavel Novichkov <PSNovichkov(a)lbl.gov<mailto:[email protected]>> > Cc: "Tom S. Brettin" > <Brettin(a)mcs.anl.gov<mailto:[email protected]>>, Shane Canon > <scanon(a)lbl.gov<mailto:[email protected]>>, Nomi Harris > <NLHarris(a)lbl.gov<mailto:[email protected]>> > > Hi Pavel, > The "deploy-docs" target in your Makefile is still copying docs to > the wrong directory; furthermore, by copying docs/*html it copies an > index.html that is a Glassfish default page, which then hides the > actual API doc (Regulation.html) from being visible in > http://140.221.84.191/services/docs/Regulation/ . (If you look there > now, you can see Regulation.html only because Shane manually moved > index.html to index2.html.) > > Your Makefile has: > deploy-docs: build-docs > cp docs/*.html $(TARGET)/services/$(SERVICE_NAME)/webroot/docroot/ > > It should say (I think--I did not actually test this): > deploy-docs: build-docs > mkdir -p $(TARGET)/services/$(SERVICE_NAME)/webroot > cp docs/Regulation.html $(TARGET)/services/$(SERVICE_NAME)/webroot > > Please let us know when you've made that change so we can redeploy > regprecise and make sure the API doc ends up in the correct place so > that we can clear your module for production release. > > Thanks, > Nomi > > > On Feb 5, 2013, at 9:44 AM, Nomi Harris > <nlharris(a)lbl.gov<mailto:[email protected]>> wrote: > > Dear KBase Module Owner, > > Modules are required to have API docs deployed to the appropriate > webroot directory in order to be included in the release. For this > release, API docs should be visibile in > http://140.221.84.191/services/docs/ > > If your module's Makefile conforms to the KBase standard Makefile, > “make deploy” will have run “make deploy-docs”, which should make > the html documents and copy them to webroot: > ($(TARGET)/services/$(SERVICE)/webroot/ where $(TARGET) is typically > /kb/deployment and $(SERVICE) is the name of your service--so, for > example, /kb/deployment/services/idserver/webroot). These docs are > normally generated from the comments in the typespec. > > RESULTS OF TECH DOC CHECK (Full release, week of 2/4/2013) > MODULE NAME: regprecise > AUTHOR(S): psnovichkov(a)lbl.gov<mailto:[email protected]> > DIRECTORY FOR API DOCS: > http://140.221.84.191/services/docs/Regulation > API DOCS PRESENT AT THAT URL? No--your "deploy-docs" target is > copying the docs to the wrong directory. Please change to conform to > the standard Makefile, > https://git.kbase.us/dev_container.git/blob/HEAD:/doc/module.Makefile > for more info. > API DOCS COMPLETE? yes (but in wrong dir) > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] Fwd: API doc for regprecise
by Land, Miriam L. 13 Feb '13

13 Feb '13

Nomi, I've marked the spreadsheet for redeploy of regprecise. Miriam From: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> Date: Wednesday, February 13, 2013 10:26 AM To: "release-team(a)lists.kbase.us<mailto:[email protected]>" <release-team(a)lists.kbase.us<mailto:[email protected]>> Subject: [Release-team] Fwd: API doc for regprecise [was Re: Initial tech doc results for your module (Full Build, Feb 4, 2013)] Dear Deploy team, Can you re-deploy regprecise? Thanks, Nomi Begin forwarded message: From: "Yoo, Shinjae" <sjyoo(a)bnl.gov<mailto:[email protected]>> Subject: Re: API doc for regprecise [was Re: Initial tech doc results for your module (Full Build, Feb 4, 2013)] Date: February 13, 2013 12:51:00 AM PST To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> Cc: Pavel Novichkov <psnovichkov(a)lbl.gov<mailto:[email protected]>> Nomi, Your suggested changes is in place now: root@ntest:/kb/dev_container/modules/regprecise# ls -al /kb/deployment/services/Regulation/webroot/ total 40 drwxr-xr-x 2 root root 4096 2013-02-13 08:48 . drwxr-xr-x 3 root root 4096 2013-02-13 08:48 .. -rw-r--r-- 1 root root 32716 2013-02-13 08:48 Regulation.html root@ntest:/kb/dev_container/modules/regprecise# Please let me know if you have any other issues with Makefile. Thanks, -SJ On Feb 13, 2013, at 3:41 AM, Shinjae Yoo wrote: Thanks Nomi, Two things: 1) deploy-docs target fixed last week It seems the Makefile is old version 2) If you want just empty folder as web root, I can make changes to deploy-dir target to have empty webroot folder to copy it. I'll make this change now and test it on my test VM. -SJ On Feb 12, 2013, at 5:46 PM, Nomi Harris wrote: (Sorry, forgot to cc you, Shinjae.) Nomi Begin forwarded message: From: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> Subject: API doc for regprecise [was Re: Initial tech doc results for your module (Full Build, Feb 4, 2013)] Date: February 12, 2013 11:55:19 AM PST To: Pavel Novichkov <PSNovichkov(a)lbl.gov<mailto:[email protected]>> Cc: "Tom S. Brettin" <Brettin(a)mcs.anl.gov<mailto:[email protected]>>, Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>>, Nomi Harris <NLHarris(a)lbl.gov<mailto:[email protected]>> Hi Pavel, The "deploy-docs" target in your Makefile is still copying docs to the wrong directory; furthermore, by copying docs/*html it copies an index.html that is a Glassfish default page, which then hides the actual API doc (Regulation.html) from being visible in http://140.221.84.191/services/docs/Regulation/ . (If you look there now, you can see Regulation.html only because Shane manually moved index.html to index2.html.) Your Makefile has: deploy-docs: build-docs cp docs/*.html $(TARGET)/services/$(SERVICE_NAME)/webroot/docroot/ It should say (I think--I did not actually test this): deploy-docs: build-docs mkdir -p $(TARGET)/services/$(SERVICE_NAME)/webroot cp docs/Regulation.html $(TARGET)/services/$(SERVICE_NAME)/webroot Please let us know when you've made that change so we can redeploy regprecise and make sure the API doc ends up in the correct place so that we can clear your module for production release. Thanks, Nomi On Feb 5, 2013, at 9:44 AM, Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> wrote: Dear KBase Module Owner, Modules are required to have API docs deployed to the appropriate webroot directory in order to be included in the release. For this release, API docs should be visibile in http://140.221.84.191/services/docs/ If your module's Makefile conforms to the KBase standard Makefile, “make deploy” will have run “make deploy-docs”, which should make the html documents and copy them to webroot: ($(TARGET)/services/$(SERVICE)/webroot/ where $(TARGET) is typically /kb/deployment and $(SERVICE) is the name of your service--so, for example, /kb/deployment/services/idserver/webroot). These docs are normally generated from the comments in the typespec. RESULTS OF TECH DOC CHECK (Full release, week of 2/4/2013) MODULE NAME: regprecise AUTHOR(S): psnovichkov(a)lbl.gov<mailto:[email protected]> DIRECTORY FOR API DOCS: http://140.221.84.191/services/docs/Regulation API DOCS PRESENT AT THAT URL? No--your "deploy-docs" target is copying the docs to the wrong directory. Please change to conform to the standard Makefile, https://git.kbase.us/dev_container.git/blob/HEAD:/doc/module.Makefile for more info. API DOCS COMPLETE? yes (but in wrong dir)

1 0

Fwd: API doc for regprecise [was Re: Initial tech doc results for your module (Full Build, Feb 4, 2013)]
by Nomi Harris 13 Feb '13

13 Feb '13

Dear Deploy team, Can you re-deploy regprecise? Thanks, Nomi Begin forwarded message: > From: "Yoo, Shinjae" <sjyoo(a)bnl.gov> > Subject: Re: API doc for regprecise [was Re: Initial tech doc results for your module (Full Build, Feb 4, 2013)] > Date: February 13, 2013 12:51:00 AM PST > To: Nomi Harris <nlharris(a)lbl.gov> > Cc: Pavel Novichkov <psnovichkov(a)lbl.gov> > > Nomi, > > > Your suggested changes is in place now: > > root@ntest:/kb/dev_container/modules/regprecise# ls -al /kb/deployment/services/Regulation/webroot/ > total 40 > drwxr-xr-x 2 root root 4096 2013-02-13 08:48 . > drwxr-xr-x 3 root root 4096 2013-02-13 08:48 .. > -rw-r--r-- 1 root root 32716 2013-02-13 08:48 Regulation.html > root@ntest:/kb/dev_container/modules/regprecise# > > Please let me know if you have any other issues with Makefile. > > Thanks, > -SJ > > On Feb 13, 2013, at 3:41 AM, Shinjae Yoo wrote: > >> Thanks Nomi, >> >> Two things: >> >> 1) deploy-docs target fixed last week >> It seems the Makefile is old version >> >> 2) If you want just empty folder as web root, I can make changes to deploy-dir target to have empty webroot folder to copy it. >> I'll make this change now and test it on my test VM. >> >> -SJ >> >> On Feb 12, 2013, at 5:46 PM, Nomi Harris wrote: >> >>> (Sorry, forgot to cc you, Shinjae.) >>> Nomi >>> >>> Begin forwarded message: >>> >>>> From: Nomi Harris <nlharris(a)lbl.gov> >>>> Subject: API doc for regprecise [was Re: Initial tech doc results for your module (Full Build, Feb 4, 2013)] >>>> Date: February 12, 2013 11:55:19 AM PST >>>> To: Pavel Novichkov <PSNovichkov(a)lbl.gov> >>>> Cc: "Tom S. Brettin" <Brettin(a)mcs.anl.gov>, Shane Canon <scanon(a)lbl.gov>, Nomi Harris <NLHarris(a)lbl.gov> >>>> >>>> Hi Pavel, >>>> The "deploy-docs" target in your Makefile is still copying docs to the wrong directory; furthermore, by copying docs/*html it copies an index.html that is a Glassfish default page, which then hides the actual API doc (Regulation.html) from being visible in http://140.221.84.191/services/docs/Regulation/ . (If you look there now, you can see Regulation.html only because Shane manually moved index.html to index2.html.) >>>> >>>> Your Makefile has: >>>> deploy-docs: build-docs >>>> cp docs/*.html $(TARGET)/services/$(SERVICE_NAME)/webroot/docroot/ >>>> >>>> It should say (I think--I did not actually test this): >>>> deploy-docs: build-docs >>>> mkdir -p $(TARGET)/services/$(SERVICE_NAME)/webroot >>>> cp docs/Regulation.html $(TARGET)/services/$(SERVICE_NAME)/webroot >>>> >>>> Please let us know when you've made that change so we can redeploy regprecise and make sure the API doc ends up in the correct place so that we can clear your module for production release. >>>> >>>> Thanks, >>>> Nomi >>>> >>>> >>>> On Feb 5, 2013, at 9:44 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>>> >>>>> Dear KBase Module Owner, >>>>> >>>>> Modules are required to have API docs deployed to the appropriate webroot directory in order to be included in the release. For this release, API docs should be visibile in http://140.221.84.191/services/docs/ >>>>> >>>>> If your module's Makefile conforms to the KBase standard Makefile, “make deploy” will have run “make deploy-docs”, which should make the html documents and copy them to webroot: ($(TARGET)/services/$(SERVICE)/webroot/ where $(TARGET) is typically /kb/deployment and $(SERVICE) is the name of your service--so, for example, /kb/deployment/services/idserver/webroot). These docs are normally generated from the comments in the typespec. >>>>> >>>>> RESULTS OF TECH DOC CHECK (Full release, week of 2/4/2013) >>>>> MODULE NAME: regprecise >>>>> AUTHOR(S): psnovichkov(a)lbl.gov >>>>> DIRECTORY FOR API DOCS: http://140.221.84.191/services/docs/Regulation >>>>> API DOCS PRESENT AT THAT URL? No--your "deploy-docs" target is copying the docs to the wrong directory. Please change to conform to the standard Makefile, https://git.kbase.us/dev_container.git/blob/HEAD:/doc/module.Makefile for more info. >>>>> API DOCS COMPLETE? yes (but in wrong dir)

1 0

Re: [Release-team] Deployments
by Dan Olson 11 Feb '13

11 Feb '13

Hey.. I'm just getting started with the redeployments today. I had to do some reconciling of where we're at. I did that earlier this morning and sent new, additional, notices to the developers we're waiting on items from. I don't think I need any help at the moment. They should all be redeployed within an hour. ----- Original Message ----- > From: "Thomas Brettin" <brettin(a)mcs.anl.gov> > To: "Shane Canon" <scanon(a)lbl.gov>, "Dan Olson" <dolson(a)mcs.anl.gov> > Cc: release-team(a)lists.kbase.us > Sent: Monday, February 11, 2013 12:37:35 PM > Subject: Re: [Release-team] Deployments > > Hey guys, > > want me to do some deployments? > > Tom > > > On Feb 11, 2013, at 12:17 PM, "Land, Miriam L." <landml(a)ornl.gov> > wrote: > > > Will there be any deployments today? I haven't seen any changes > > since I added modules to be deployed on Friday morning. > > > > Miriam > > _______________________________________________ > > 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] Deployments
by Thomas Brettin 11 Feb '13

11 Feb '13

Hey guys, want me to do some deployments? Tom On Feb 11, 2013, at 12:17 PM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > Will there be any deployments today? I haven't seen any changes since I added modules to be deployed on Friday morning. > > Miriam > _______________________________________________ > 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

Deployments
by Land, Miriam L. 11 Feb '13

11 Feb '13

Will there be any deployments today? I haven't seen any changes since I added modules to be deployed on Friday morning. Miriam

1 0

Re: [Release-team] Some API docs missing that were there before
by Thomas Brettin 11 Feb '13

11 Feb '13

Glassfish is a web server. Is it taking the nginx port? On Feb 11, 2013, at 10:56 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > > On Feb 11, 2013, at 8:47 AM, Shane Canon <scanon(a)lbl.gov> wrote: > >> These are all fixed now. These were mostly an issue with deployment. > > Thanks! > >> Two remarks: >> * Regulation still needs to fix the docs to show the right thing. > > Yeah, I don't see their api doc--I just see a Glassfish default page. > >> * It would be nice if there was an index.html for all of the services so that following the doc link takes you to a formatted page. > > Well, this is not something that's needed for getting the API docs onto kbase.us, so I'm not sure it's a good use of developers' time (or are you suggesting that the tech doc team produce these?). The automated process that most repos use to make the API docs (typespec -> type compiler -> perl libraries -> pod2html -> html API doc) does not produce an index.html. > >> I'm especially keen on this last point. > > Why? > > Nomi > >> >> --Shane >> >> >> On Feb 9, 2013, at 4:48 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> Still missing: >>> aux_store >>> jnomics >>> protein_info_service >>> regprecise (aka Regulation) (just shows some generic Glassfish page) >>> >>> Newly missing (was there yesterday): >>> genotype_phenotype_api >>> >>> Nomi >>> >>> On Feb 8, 2013, at 1:26 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>> >>>> Here's a list of modules for which API docs are not showing up or there's some issue (weird self-referential webroot symlink?). >>>> If not otherwise indicated, then the issue is that the API docs were there at some point but are missing now. >>>> >>>> auth_service >>>> (aux_store--but I don't think that was deployed) >>>> file_type_service >>>> genome_annotation >>>> genotype_phenotype_api (doc there but has funky webroot symlink) >>>> invocation (doc there but has funky webroot symlink) >>>> jnomics (should have javadocs and user guide--Dan will try to figure out what happened to them) >>>> networks (doc was there yesterday in KBaseNetworksService--today there is no such dir, there is a networks dir, but empty) >>>> protein_info_service >>>> regprecise (aka Regulation) >>>> trees >>>> workspace_service (workspaceService) >>>> registry >>>> >>>> >>>> Begin forwarded message: >>>> >>>>> From: Nomi Harris <nlharris(a)lbl.gov> >>>>> Subject: Some API docs missing that were there before >>>>> Date: February 7, 2013 5:38:26 PM PST >>>>> To: "release-team(a)lists.kbase.us" <release-team(a)lists.kbase.us> >>>>> Cc: Nomi Harris <nlharris(a)lbl.gov> >>>>> >>>>> I'm checking API docs at http://140.221.84.191/services/docs/ >>>>> Some were there after the first deploy but are not now. They are yellow in column M of https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaEJz… >>>>> One of them--Regulation--is particularly odd since I saw the API docs there an hour or two before and now I don't. >>>>> Nomi Harris >>>>> Project Manager, KBase >>>>> >>>> >>> >> > > _______________________________________________ > 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] Some API docs missing that were there before
by Nomi Harris 11 Feb '13

11 Feb '13

On Feb 11, 2013, at 8:47 AM, Shane Canon <scanon(a)lbl.gov> wrote: > These are all fixed now. These were mostly an issue with deployment. Thanks! > Two remarks: > * Regulation still needs to fix the docs to show the right thing. Yeah, I don't see their api doc--I just see a Glassfish default page. > * It would be nice if there was an index.html for all of the services so that following the doc link takes you to a formatted page. Well, this is not something that's needed for getting the API docs onto kbase.us, so I'm not sure it's a good use of developers' time (or are you suggesting that the tech doc team produce these?). The automated process that most repos use to make the API docs (typespec -> type compiler -> perl libraries -> pod2html -> html API doc) does not produce an index.html. > I'm especially keen on this last point. Why? Nomi > > --Shane > > > On Feb 9, 2013, at 4:48 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Still missing: >> aux_store >> jnomics >> protein_info_service >> regprecise (aka Regulation) (just shows some generic Glassfish page) >> >> Newly missing (was there yesterday): >> genotype_phenotype_api >> >> Nomi >> >> On Feb 8, 2013, at 1:26 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> Here's a list of modules for which API docs are not showing up or there's some issue (weird self-referential webroot symlink?). >>> If not otherwise indicated, then the issue is that the API docs were there at some point but are missing now. >>> >>> auth_service >>> (aux_store--but I don't think that was deployed) >>> file_type_service >>> genome_annotation >>> genotype_phenotype_api (doc there but has funky webroot symlink) >>> invocation (doc there but has funky webroot symlink) >>> jnomics (should have javadocs and user guide--Dan will try to figure out what happened to them) >>> networks (doc was there yesterday in KBaseNetworksService--today there is no such dir, there is a networks dir, but empty) >>> protein_info_service >>> regprecise (aka Regulation) >>> trees >>> workspace_service (workspaceService) >>> registry >>> >>> >>> Begin forwarded message: >>> >>>> From: Nomi Harris <nlharris(a)lbl.gov> >>>> Subject: Some API docs missing that were there before >>>> Date: February 7, 2013 5:38:26 PM PST >>>> To: "release-team(a)lists.kbase.us" <release-team(a)lists.kbase.us> >>>> Cc: Nomi Harris <nlharris(a)lbl.gov> >>>> >>>> I'm checking API docs at http://140.221.84.191/services/docs/ >>>> Some were there after the first deploy but are not now. They are yellow in column M of https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaEJz… >>>> One of them--Regulation--is particularly odd since I saw the API docs there an hour or two before and now I don't. >>>> Nomi Harris >>>> Project Manager, KBase >>>> >>> >> >

1 0

Re: [Release-team] Some API docs missing that were there before
by Shane Canon 11 Feb '13

11 Feb '13

These are all fixed now. These were mostly an issue with deployment. Two remarks: * Regulation still needs to fix the docs to show the right thing. * It would be nice if there was an index.html for all of the services so that following the doc link takes you to a formatted page. I'm especially keen on this last point. --Shane On Feb 9, 2013, at 4:48 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Still missing: > aux_store > jnomics > protein_info_service > regprecise (aka Regulation) (just shows some generic Glassfish page) > > Newly missing (was there yesterday): > genotype_phenotype_api > > Nomi > > On Feb 8, 2013, at 1:26 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Here's a list of modules for which API docs are not showing up or there's some issue (weird self-referential webroot symlink?). >> If not otherwise indicated, then the issue is that the API docs were there at some point but are missing now. >> >> auth_service >> (aux_store--but I don't think that was deployed) >> file_type_service >> genome_annotation >> genotype_phenotype_api (doc there but has funky webroot symlink) >> invocation (doc there but has funky webroot symlink) >> jnomics (should have javadocs and user guide--Dan will try to figure out what happened to them) >> networks (doc was there yesterday in KBaseNetworksService--today there is no such dir, there is a networks dir, but empty) >> protein_info_service >> regprecise (aka Regulation) >> trees >> workspace_service (workspaceService) >> registry >> >> >> Begin forwarded message: >> >>> From: Nomi Harris <nlharris(a)lbl.gov> >>> Subject: Some API docs missing that were there before >>> Date: February 7, 2013 5:38:26 PM PST >>> To: "release-team(a)lists.kbase.us" <release-team(a)lists.kbase.us> >>> Cc: Nomi Harris <nlharris(a)lbl.gov> >>> >>> I'm checking API docs at http://140.221.84.191/services/docs/ >>> Some were there after the first deploy but are not now. They are yellow in column M of https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaEJz… >>> One of them--Regulation--is particularly odd since I saw the API docs there an hour or two before and now I don't. >>> Nomi Harris >>> Project Manager, KBase >>> >> >

1 0

Re: [Release-team] [Kbase-ui] prizes for this week
by Syed, Mustafa H. 11 Feb '13

11 Feb '13

Thanks for the appreciation!! I want to acknowledge Miriam, Ranjan and Shinjae for their help & guidance. Cheers, Mustafa. -----Original Message----- From: Land, Miriam L. Sent: Monday, February 11, 2013 10:04 AM To: Nomi Harris; Thomas Brettin Cc: release-team(a)lists.kbase.us; Syed, Mustafa H. Subject: Re: [Release-team] [Kbase-ui] prizes for this week I've decided that the prize for best test coverage should go to Mustafa Syed for his contribution to the genotype_phenotype_api test. He did not get a set of sample tests from the testing team, there was nothing automated to help generate hundreds of tests, the tests were more than the base minimum (test using sample data), and the first attempt included client, server, and script tests. The Chewbacca MimoMicro USB Drive & Reader goes to Mustafa. Miriam On 2/7/13 11:55 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >I decided that Chris Henry has the best API documentation >(http://140.221.84.191/services/docs/workspaceService/workspaceService. >htm l). He gives a good overview of the services, including *why* you >might use it as well as how. He included an example of how you'd use >the API from a perl program. And he documented every variable and >method. >Furthermore, he generated his API docs in the currently approved >standard KBase way, by putting comments in the typespec. I looked at a >few API docs that were very nice-looking, but were not generated the standard way. > >Overall, the API docs are looking pretty good. There are a few that are >not showing up on http://140.221.84.191/services/docs that should be, >which seems like it may be due to some sort of deploy issue. But a lot >more services have API docs now than did in November. > >I gave the Star Wars X-Wing Ice Cube Tray to Andreas to bring back to >ANL for Chris. > > Nomi > >On Feb 3, 2013, at 2:39 PM, Thomas Brettin <brettint(a)gmail.com> wrote: > >> Elizabeth was so kind as to pony up some prizes on behalf of outreach >>for this build :-) >> >> Here is what we came up with for categories-- >> >> The module that has the best test coverage of their service as >>determined by Miriam >>> Prize: Chewbacca MimoMicro USB Drive & Reader >> >> >> Best technical API documentation as determined by Nomi >>> Star Wars X-Wing Ice Cube Tray >> >> Best command line user documentation as determined by Paramvir >>> Doctor Who Dalek Tumbler >> >> >> Tom > >_______________________________________________ >Release-team mailing list >Release-team(a)lists.kbase.us >https://lists.kbase.us/mailman/listinfo/release-team

1 0