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

Re: [Release-team] Status of initial tech doc testing
by Dan Olson 12 Aug '13

12 Aug '13

I'm not sure I understand.. Are you saying the dmg itself is a service? We're going to release everything that was tagged and tested this time around, along with anything that has ever been tested and released. However the modules that were not tested during this build will be released as the last tagged version. ----- Original Message ----- > From: "Nomi Harris" <nlharris(a)lbl.gov> > To: release-team(a)kbase.us > Sent: Monday, August 12, 2013 12:47:02 AM > Subject: Re: [Release-team] Status of initial tech doc testing > > > > > It occurred to me, if we're creating a new dmg and new IRIS, then > we're releasing services that weren't "in" this release, aren't we? > So they weren't tested or checked for API docs or release notes, but > they get released anyway? Am I missing something here about what it > means to be "in" a release? > > > Update on API docs (for services "in" this release): > > > On Aug 9, 2013, at 9:55 AM, Nomi Harris < nlharris(a)lbl.gov > wrote: > > > > > > Thanks. expression still has an extra webroot that needs to be > removed. Now fixed > > > > > > > Most of the modules now have API docs in the right place. The only > exceptions: > functional_ortholog_predictor (no dir in > http://140.221.84.191/services/docs/ ) (is fine, I just looked in > the wrong place the first time) > > > > > > > assembly: No obvious API doc in > http://140.221.84.191/services/docs/assembly/ > seems to have CLI documentation but not API > > > > > > matR: has dir but no API doc Still no API doc > > > > > > > shock_service: there is a "shock_store" (empty) directory in > http://140.221.84.191/services/docs/ but no shock dir. Maybe a > Makefile problem? This is still the case > > > > > > > typecomp: Has there been a decision that it doesn't need API docs > since it's for internal use? Seems like it would still be useful to > have API docs for the use of internal people. I agree with this. :-) > > > As for the release notes, almost all the developers have now created > or updated them, so yay! The only two services that are "in" this > release and not just internal or dependencies, that lack up-to-date > release notes, are: > KBaseFBAModeling [but I kind of feel sorry for that module--it had a > hard day today, what with unexpectedly having its lib and docs dirs > removed] > Workspace service > > > Nomi > > > > > > > > > > > On Aug 8, 2013, at 9:31 AM, Shane Canon < scanon(a)lbl.gov > wrote: > > > > > > > I fixed auth and expression. > > > --S > > > On Aug 8, 2013, at 9:22 AM, Nomi Harris < nlharris(a)lbl.gov > wrote: > > > > > > On Aug 7, 2013, at 7:58 PM, Michael Sneddon < mwsneddon(a)lbl.gov > > wrote: > > > > Nearly all of the services that have been deployed passed the initial > doc testing. > > > The two exceptions are 'sim_service', which is not deploying API docs > at all (needs to add the proper doc generation and deployment code > to its Makefile), and 'search', which was deployed to a test VM that > I couldn't find (not available from t1 by ssh search ??), and has no > docs appearing here: http://140.221.84.191/services/docs/search/ > > > Bob fixed the Makefile and the API doc should appear when sim_service > is redeployed. > > > > > In addition, several modules do have proper documentation that seems > to be properly deployed, but is not appearing here: > http://140.221.84.191/services/docs . It's probably just a proxy > issue, but here is the list of those modules: > > > auth_service The doc now appears where it should but there is an > extra self-referential webroot link in > http://140.221.84.191/services/docs/authorization_server/ so that > you can go to, for example, > http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… > > > > > cluster_service > Now ok > > > > expression Almost: the doc is at > http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… > rather than > http://140.221.84.191/services/docs/expression/ExpressionServices.html > as it should. > > > > > KBaseFBAModeling Now ok, at > http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html > > > > > plant_expression_service Now ok at > http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS… > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team > > > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] Status of initial tech doc testing
by Nomi Harris 12 Aug '13

12 Aug '13

It occurred to me, if we're creating a new dmg and new IRIS, then we're releasing services that weren't "in" this release, aren't we? So they weren't tested or checked for API docs or release notes, but they get released anyway? Am I missing something here about what it means to be "in" a release? Update on API docs (for services "in" this release): On Aug 9, 2013, at 9:55 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Thanks. expression still has an extra webroot that needs to be removed. Now fixed > Most of the modules now have API docs in the right place. The only exceptions: > functional_ortholog_predictor (no dir in http://140.221.84.191/services/docs/) (is fine, I just looked in the wrong place the first time) > assembly: No obvious API doc in http://140.221.84.191/services/docs/assembly/ seems to have CLI documentation but not API > matR: has dir but no API doc Still no API doc > shock_service: there is a "shock_store" (empty) directory in http://140.221.84.191/services/docs/ but no shock dir. Maybe a Makefile problem? This is still the case > typecomp: Has there been a decision that it doesn't need API docs since it's for internal use? Seems like it would still be useful to have API docs for the use of internal people. I agree with this. :-) As for the release notes, almost all the developers have now created or updated them, so yay! The only two services that are "in" this release and not just internal or dependencies, that lack up-to-date release notes, are: KBaseFBAModeling [but I kind of feel sorry for that module--it had a hard day today, what with unexpectedly having its lib and docs dirs removed] Workspace service Nomi > > On Aug 8, 2013, at 9:31 AM, Shane Canon <scanon(a)lbl.gov> wrote: > >> >> I fixed auth and expression. >> >> --S >> >> On Aug 8, 2013, at 9:22 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> On Aug 7, 2013, at 7:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: >>> >>>> Nearly all of the services that have been deployed passed the initial doc testing. >>>> >>>> The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ >>> >>> Bob fixed the Makefile and the API doc should appear when sim_service is redeployed. >>> >>>> In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: >>>> >>>> auth_service >>> The doc now appears where it should but there is an extra self-referential webroot link in http://140.221.84.191/services/docs/authorization_server/ so that you can go to, for example, >>> http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… >>> >>>> cluster_service >>> Now ok >>> >>>> expression >>> Almost: the doc is at >>> http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… rather than http://140.221.84.191/services/docs/expression/ExpressionServices.html as it should. >>> >>>> KBaseFBAModeling >>> Now ok, at >>> http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html >>> >>>> plant_expression_service >>> Now ok at http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS… >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/release-team >> >

1 0

Re: [Release-team] Status of initial tech doc testing
by Nomi Harris 09 Aug '13

09 Aug '13

On Aug 9, 2013, at 10:03 AM, Shane Canon <scanon(a)lbl.gov> wrote: > FYI > > * Fixed expression webroot > * functional_ortholog_predictor: http://140.221.84.191/services/docs/FunctionalOrthologPredictor/ Oops, you're right. The alphabetical order that lists capitalized words separately threw me off (not for the first time). I wish the directories in services/docs matched the names of the modules. That would enable more automation and reduce human error. Nomi > > > > On Aug 9, 2013, at 9:55 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Thanks. expression still has an extra webroot that needs to be removed. >> >> Most of the modules now have API docs in the right place. The only exceptions: >> functional_ortholog_predictor (no dir in http://140.221.84.191/services/docs/) >> assembly: No obvious API doc in http://140.221.84.191/services/docs/assembly/ >> matR: has dir but no API doc >> shock_service: there is a "shock_store" (empty) directory in http://140.221.84.191/services/docs/ but no shock dir. Maybe a Makefile problem? >> typecomp: Has there been a decision that it doesn't need API docs since it's for internal use? Seems like it would still be useful to have API docs for the use of internal people. >> >> On Aug 8, 2013, at 9:31 AM, Shane Canon <scanon(a)lbl.gov> wrote: >> >>> >>> I fixed auth and expression. >>> >>> --S >>> >>> On Aug 8, 2013, at 9:22 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>> >>>> On Aug 7, 2013, at 7:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: >>>> >>>>> Nearly all of the services that have been deployed passed the initial doc testing. >>>>> >>>>> The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ >>>> >>>> Bob fixed the Makefile and the API doc should appear when sim_service is redeployed. >>>> >>>>> In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: >>>>> >>>>> auth_service >>>> The doc now appears where it should but there is an extra self-referential webroot link in http://140.221.84.191/services/docs/authorization_server/ so that you can go to, for example, >>>> http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… >>>> >>>>> cluster_service >>>> Now ok >>>> >>>>> expression >>>> Almost: the doc is at >>>> http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… rather than http://140.221.84.191/services/docs/expression/ExpressionServices.html as it should. >>>> >>>>> KBaseFBAModeling >>>> Now ok, at >>>> http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html >>>> >>>>> plant_expression_service >>>> Now ok at http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS… >>>> >>>> _______________________________________________ >>>> Release-team mailing list >>>> Release-team(a)lists.kbase.us >>>> https://lists.kbase.us/mailman/listinfo/release-team >>> >> >

1 0

Re: [Release-team] Status of initial tech doc testing
by Shane Canon 09 Aug '13

09 Aug '13

FYI * Fixed expression webroot * functional_ortholog_predictor: http://140.221.84.191/services/docs/FunctionalOrthologPredictor/ On Aug 9, 2013, at 9:55 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Thanks. expression still has an extra webroot that needs to be removed. > > Most of the modules now have API docs in the right place. The only exceptions: > functional_ortholog_predictor (no dir in http://140.221.84.191/services/docs/) > assembly: No obvious API doc in http://140.221.84.191/services/docs/assembly/ > matR: has dir but no API doc > shock_service: there is a "shock_store" (empty) directory in http://140.221.84.191/services/docs/ but no shock dir. Maybe a Makefile problem? > typecomp: Has there been a decision that it doesn't need API docs since it's for internal use? Seems like it would still be useful to have API docs for the use of internal people. > > On Aug 8, 2013, at 9:31 AM, Shane Canon <scanon(a)lbl.gov> wrote: > >> >> I fixed auth and expression. >> >> --S >> >> On Aug 8, 2013, at 9:22 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> On Aug 7, 2013, at 7:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: >>> >>>> Nearly all of the services that have been deployed passed the initial doc testing. >>>> >>>> The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ >>> >>> Bob fixed the Makefile and the API doc should appear when sim_service is redeployed. >>> >>>> In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: >>>> >>>> auth_service >>> The doc now appears where it should but there is an extra self-referential webroot link in http://140.221.84.191/services/docs/authorization_server/ so that you can go to, for example, >>> http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… >>> >>>> cluster_service >>> Now ok >>> >>>> expression >>> Almost: the doc is at >>> http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… rather than http://140.221.84.191/services/docs/expression/ExpressionServices.html as it should. >>> >>>> KBaseFBAModeling >>> Now ok, at >>> http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html >>> >>>> plant_expression_service >>> Now ok at http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS… >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> https://lists.kbase.us/mailman/listinfo/release-team >> >

1 0

Re: [Release-team] Status of initial tech doc testing
by Nomi Harris 09 Aug '13

09 Aug '13

Thanks. expression still has an extra webroot that needs to be removed. Most of the modules now have API docs in the right place. The only exceptions: functional_ortholog_predictor (no dir in http://140.221.84.191/services/docs/) assembly: No obvious API doc in http://140.221.84.191/services/docs/assembly/ matR: has dir but no API doc shock_service: there is a "shock_store" (empty) directory in http://140.221.84.191/services/docs/ but no shock dir. Maybe a Makefile problem? typecomp: Has there been a decision that it doesn't need API docs since it's for internal use? Seems like it would still be useful to have API docs for the use of internal people. On Aug 8, 2013, at 9:31 AM, Shane Canon <scanon(a)lbl.gov> wrote: > > I fixed auth and expression. > > --S > > On Aug 8, 2013, at 9:22 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> On Aug 7, 2013, at 7:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: >> >>> Nearly all of the services that have been deployed passed the initial doc testing. >>> >>> The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ >> >> Bob fixed the Makefile and the API doc should appear when sim_service is redeployed. >> >>> In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: >>> >>> auth_service >> The doc now appears where it should but there is an extra self-referential webroot link in http://140.221.84.191/services/docs/authorization_server/ so that you can go to, for example, >> http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… >> >>> cluster_service >> Now ok >> >>> expression >> Almost: the doc is at >> http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… rather than http://140.221.84.191/services/docs/expression/ExpressionServices.html as it should. >> >>> KBaseFBAModeling >> Now ok, at >> http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html >> >>> plant_expression_service >> Now ok at http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS… >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] Status of initial tech doc testing
by Thomas Brettin 09 Aug '13

09 Aug '13

thanks guys t On Aug 8, 2013, at 11:31 AM, Shane Canon <scanon(a)lbl.gov> wrote: > > I fixed auth and expression. > > --S > > On Aug 8, 2013, at 9:22 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> On Aug 7, 2013, at 7:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: >> >>> Nearly all of the services that have been deployed passed the initial doc testing. >>> >>> The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ >> >> Bob fixed the Makefile and the API doc should appear when sim_service is redeployed. >> >>> In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: >>> >>> auth_service >> The doc now appears where it should but there is an extra self-referential webroot link in http://140.221.84.191/services/docs/authorization_server/ so that you can go to, for example, >> http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… >> >>> cluster_service >> Now ok >> >>> expression >> Almost: the doc is at >> http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… rather than http://140.221.84.191/services/docs/expression/ExpressionServices.html as it should. >> >>> KBaseFBAModeling >> Now ok, at >> http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html >> >>> plant_expression_service >> Now ok at http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS… >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Status of initial tech doc testing
by Shane Canon 08 Aug '13

08 Aug '13

I fixed auth and expression. --S On Aug 8, 2013, at 9:22 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > On Aug 7, 2013, at 7:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: > >> Nearly all of the services that have been deployed passed the initial doc testing. >> >> The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ > > Bob fixed the Makefile and the API doc should appear when sim_service is redeployed. > >> In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: >> >> auth_service > The doc now appears where it should but there is an extra self-referential webroot link in http://140.221.84.191/services/docs/authorization_server/ so that you can go to, for example, > http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… > >> cluster_service > Now ok > >> expression > Almost: the doc is at > http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… rather than http://140.221.84.191/services/docs/expression/ExpressionServices.html as it should. > >> KBaseFBAModeling > Now ok, at > http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html > >> plant_expression_service > Now ok at http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS… > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Status of initial tech doc testing
by Nomi Harris 08 Aug '13

08 Aug '13

On Aug 7, 2013, at 7:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: > Nearly all of the services that have been deployed passed the initial doc testing. > > The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ Bob fixed the Makefile and the API doc should appear when sim_service is redeployed. > In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: > > auth_service The doc now appears where it should but there is an extra self-referential webroot link in http://140.221.84.191/services/docs/authorization_server/ so that you can go to, for example, http://140.221.84.191/services/docs/authorization_server/webroot/webroot/we… > cluster_service Now ok > expression Almost: the doc is at http://140.221.84.191/services/docs/expression/webroot/ExpressionServices.h… rather than http://140.221.84.191/services/docs/expression/ExpressionServices.html as it should. > KBaseFBAModeling Now ok, at http://140.221.84.191/services/docs/fbaModelServices/fbaModelServices.html > plant_expression_service Now ok at http://140.221.84.191/services/docs/PlantExpressionService/PlantExpressionS…

1 0

Re: [Release-team] Status of initial tech doc testing
by Shane Canon 08 Aug '13

08 Aug '13

Ahhh. And the docs are now fixed for FBA too. --Shane On Aug 8, 2013, at 8:24 AM, "Moulton, Steve" <moultonsa(a)ornl.gov> wrote: > -------- > WARNING: At least one of the links in the message below goes to an IP address (e.g. > 10.1.1.1), which could be malicious. To learn how to protect yourself, please go here: > http://www.lbl.gov/cyber/services/suspicious-links.html > -------- > > Because I just now did it. J > > -s > > -- > Steve Moulton UNIX/Linux Systems Engineer > Cyber Operations & Research Integration (R&D Support), ITSD > Oak Ridge National Laboratory > Voice: 865-574-9609 Fax: 865-576-7605 moultonsa at ornl dot gov > > From: Shane Canon [mailto:[email protected]] > Sent: Thursday, August 08, 2013 10:41 AM > To: Thomas Brettin > Cc: Michael Sneddon; Dan Olson (dolson(a)mcs.anl.gov) Moulton, Steve; release-team(a)kbase.us > Subject: Re: [Release-team] Status of initial tech doc testing > > > > I've re-generated the nginx config. The only difference I saw was the addition of the microbes_model_builder which looks like a lab (versus a service) and doesn't have any > typical service documentation. Was there anything else missing? > > I've fixed the broken links for all but FBA. FBA doesn't appeared to be deployed. I wasn't sure if there was a reason for that. > > --Shane > > On Aug 7, 2013, at 9:14 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > > > -------- > WARNING: At least one of the links in the message below goes to an IP address (e.g. > 10.1.1.1), which could be malicious. To learn how to protect yourself, please go here: > http://www.lbl.gov/cyber/services/suspicious-links.html > -------- > > Can someone on the sys admin team fix this? > > Thanks, > Tom > > > On Aug 7, 2013, at 6:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: > > > Nearly all of the services that have been deployed passed the initial doc testing. > > The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ > > In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: > > auth_service > cluster_service > expression > KBaseFBAModeling > plant_expression_service > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] Status of initial tech doc testing
by Moulton, Steve 08 Aug '13

08 Aug '13

Because I just now did it. :) -s -- Steve Moulton UNIX/Linux Systems Engineer Cyber Operations & Research Integration (R&D Support), ITSD Oak Ridge National Laboratory Voice: 865-574-9609 Fax: 865-576-7605 moultonsa at ornl dot gov From: Shane Canon [mailto:[email protected]] Sent: Thursday, August 08, 2013 10:41 AM To: Thomas Brettin Cc: Michael Sneddon; Dan Olson (dolson(a)mcs.anl.gov) Moulton, Steve; release-team(a)kbase.us Subject: Re: [Release-team] Status of initial tech doc testing I've re-generated the nginx config. The only difference I saw was the addition of the microbes_model_builder which looks like a lab (versus a service) and doesn't have any typical service documentation. Was there anything else missing? I've fixed the broken links for all but FBA. FBA doesn't appeared to be deployed. I wasn't sure if there was a reason for that. --Shane On Aug 7, 2013, at 9:14 PM, Thomas Brettin <brettin(a)mcs.anl.gov<mailto:[email protected]>> wrote: -------- WARNING: At least one of the links in the message below goes to an IP address (e.g. 10.1.1.1), which could be malicious. To learn how to protect yourself, please go here: http://www.lbl.gov/cyber/services/suspicious-links.html -------- Can someone on the sys admin team fix this? Thanks, Tom On Aug 7, 2013, at 6:58 PM, Michael Sneddon <mwsneddon(a)lbl.gov<mailto:[email protected]>> wrote: Nearly all of the services that have been deployed passed the initial doc testing. The two exceptions are 'sim_service', which is not deploying API docs at all (needs to add the proper doc generation and deployment code to its Makefile), and 'search', which was deployed to a test VM that I couldn't find (not available from t1 by ssh search ??), and has no docs appearing here: http://140.221.84.191/services/docs/search/ In addition, several modules do have proper documentation that seems to be properly deployed, but is not appearing here: http://140.221.84.191/services/docs . It's probably just a proxy issue, but here is the list of those modules: auth_service cluster_service expression KBaseFBAModeling plant_expression_service _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us<mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team

1 0