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

Re: [Release-team] [Kbase-devel] need list of deploy targets - please send list of modules that need to be deployed.
by Thomas Brettin 13 Nov '13

13 Nov '13

Please provide a one sentence description of each. Are these to be deployed next week? Thanks, Tom On Nov 13, 2013, at 3:21 PM, "Yoo, Shinjae" <sjyoo(a)bnl.gov> wrote: > Tom, > > We need two repo: > > - interlog_projection > Owner: Taeyun and Gang > - gene_conservation > Owner: Gang > > I’m helping them to bring services to KBase. > > Thanks, > -SJ > > > On Nov 13, 2013, at 4:08 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > >> >> Please send the release team a note if your module(s) have changed and should be deployed to prod. >> >> Tom >> _______________________________________________ >> Kbase-devel mailing list >> Kbase-devel(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/kbase-devel >

1 0

Re: [Release-team] [Kbase-devel] need list of deploy targets - please send list of modules that need to be deployed.
by Michael Schatz 13 Nov '13

13 Nov '13

We will redeploy the variations services and deploy the new RNAseq services. Thank you, Mike On Wed, Nov 13, 2013 at 4:35 PM, Jared Bischof <jbischof(a)gmail.com> wrote: > The shock-service should be re-deployed as the Shock code has had multiple > updates. > > > On Wed, Nov 13, 2013 at 3:08 PM, Thomas Brettin <brettin(a)mcs.anl.gov>wrote: > >> >> Please send the release team a note if your module(s) have changed and >> should be deployed to prod. >> >> Tom >> _______________________________________________ >> Kbase-devel mailing list >> Kbase-devel(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/kbase-devel >> > > > _______________________________________________ > Kbase-devel mailing list > Kbase-devel(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/kbase-devel > >

1 0

Re: [Release-team] [Kbase-devel] need list of deploy targets - please send list of modules that need to be deployed.
by Jared Bischof 13 Nov '13

13 Nov '13

The shock-service should be re-deployed as the Shock code has had multiple updates. On Wed, Nov 13, 2013 at 3:08 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > > Please send the release team a note if your module(s) have changed and > should be deployed to prod. > > Tom > _______________________________________________ > Kbase-devel mailing list > Kbase-devel(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/kbase-devel >

1 0

Re: [Release-team] [Kbase-devel] need list of deploy targets - please send list of modules that need to be deployed.
by Yoo, Shinjae 13 Nov '13

13 Nov '13

Tom, We need two repo: - interlog_projection Owner: Taeyun and Gang - gene_conservation Owner: Gang I’m helping them to bring services to KBase. Thanks, -SJ On Nov 13, 2013, at 4:08 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > > Please send the release team a note if your module(s) have changed and should be deployed to prod. > > Tom > _______________________________________________ > Kbase-devel mailing list > Kbase-devel(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/kbase-devel

1 0

need list of deploy targets - please send list of modules that need to be deployed.
by Thomas Brettin 13 Nov '13

13 Nov '13

Please send the release team a note if your module(s) have changed and should be deployed to prod. Tom

1 0

Re: [Release-team] Deployment of userandjobstate
by Michael Sneddon 04 Nov '13

04 Nov '13

Ah you're right. Thanks. Change that to pass then... On Mon, Nov 4, 2013 at 3:26 PM, Murphy-Olson, Daniel E. <dolson(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: https://commons.lbl.gov/x/_591B > -------- > I think you're going to the wrong link for docs, you're going to the > service url. > Try: > http://140.221.84.191/services/docs/userandjobstate<http://140.221.84.191/services/user_and_job_state/> > > ---- > Daniel Murphy-Olson > Systems Administrator > Mathematics & Computer Science Division > Argonne National Laboratory > 630-252-0055 <callto:630-252-0055> > ------------------------------ > *From:* Michael Sneddon [mwsneddon(a)lbl.gov] > *Sent:* Monday, November 04, 2013 5:13 PM > *To:* Murphy-Olson, Daniel E. > *Cc:* release-team(a)kbase.us > *Subject:* Re: [Release-team] Deployment of userandjobstate > > Hi Dan, > I just ran through these tests, and the results are below and in the > spreadsheet. > > > On Mon, Nov 4, 2013 at 1:59 PM, Murphy-Olson, Daniel E. < > dolson(a)mcs.anl.gov> wrote: > >> Hi all, >> >> user_and_job_state has been deployed, and tested in the test environment. >> >> We're ready for the following steps: >> pass script standards >> > > pass - there are no scripts; This is a check to make sure that scrips > (if they exist) properly return a help message when '-h' or '--help' are > passed, and the correct error code. We'll also use this on new modules to > ensure script naming conventions and other standards are met (described > here: > https://docs.google.com/document/d/1bwXes9-f99Hr8EknQ8nrL0UfYpB0rlYVKsSxvE9… > ) > > >> pass initial doc qc >> > fail, docs are not appearing here: > http://140.221.84.191/services/user_and_job_state/ (although it seems > they are properly deployed to > /kb/deployment/services/userandjobstate/webroot) > This test is to ensure API documentation exists, is generated, is deployed > to the proper webroot directory, and appears here: > http://140.221.84.191/services/. We also conduct a basic read through to > make sure the documentation actually 'seems' to make sense and are mostly > complete. If other technical docs appear in webroot, we take a look as > well to make sure the docs seem to make sense. > > >> pass final doc qc >> > I believe this column is there if the initial doc qc failed, the developer > checked in changes to correct the documentation problems, and the > documentation team takes a second look. Since it looks like in the new > spreadsheet format we are creating a new row every time a service is > redeployed, do we still need this column? I propose that we get rid of > it... > > >> release notes updated > > pass - this is a simple test to make sure a Release Notes file exists, and > has minimal documentation on what is new in this release. > > >> >> > Do we have each of these documented? I would like to know what our >> criteria and pass/fail logic is for each of these. >> >> >> ---- >> Daniel Murphy-Olson >> Systems Administrator >> Mathematics & Computer Science Division >> Argonne National Laboratory >> 630-252-0055 >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >> > >

1 0

Re: [Release-team] Deployment of userandjobstate
by Murphy-Olson, Daniel E. 04 Nov '13

04 Nov '13

I think you're going to the wrong link for docs, you're going to the service url. Try: http://140.221.84.191/services/docs/userandjobstate<http://140.221.84.191/services/user_and_job_state/> ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055<callto:630-252-0055> ________________________________ From: Michael Sneddon [mwsneddon(a)lbl.gov] Sent: Monday, November 04, 2013 5:13 PM To: Murphy-Olson, Daniel E. Cc: release-team(a)kbase.us Subject: Re: [Release-team] Deployment of userandjobstate Hi Dan, I just ran through these tests, and the results are below and in the spreadsheet. On Mon, Nov 4, 2013 at 1:59 PM, Murphy-Olson, Daniel E. <dolson(a)mcs.anl.gov<mailto:[email protected]>> wrote: Hi all, user_and_job_state has been deployed, and tested in the test environment. We're ready for the following steps: pass script standards pass - there are no scripts; This is a check to make sure that scrips (if they exist) properly return a help message when '-h' or '--help' are passed, and the correct error code. We'll also use this on new modules to ensure script naming conventions and other standards are met (described here: https://docs.google.com/document/d/1bwXes9-f99Hr8EknQ8nrL0UfYpB0rlYVKsSxvE9…) pass initial doc qc fail, docs are not appearing here: http://140.221.84.191/services/user_and_job_state/ (although it seems they are properly deployed to /kb/deployment/services/userandjobstate/webroot) This test is to ensure API documentation exists, is generated, is deployed to the proper webroot directory, and appears here: http://140.221.84.191/services/. We also conduct a basic read through to make sure the documentation actually 'seems' to make sense and are mostly complete. If other technical docs appear in webroot, we take a look as well to make sure the docs seem to make sense. pass final doc qc I believe this column is there if the initial doc qc failed, the developer checked in changes to correct the documentation problems, and the documentation team takes a second look. Since it looks like in the new spreadsheet format we are creating a new row every time a service is redeployed, do we still need this column? I propose that we get rid of it... release notes updated pass - this is a simple test to make sure a Release Notes file exists, and has minimal documentation on what is new in this release. Do we have each of these documented? I would like to know what our criteria and pass/fail logic is for each of these. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055<tel:630-252-0055> _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us<mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Deployment of userandjobstate
by Michael Sneddon 04 Nov '13

04 Nov '13

Hi Dan, I just ran through these tests, and the results are below and in the spreadsheet. On Mon, Nov 4, 2013 at 1:59 PM, Murphy-Olson, Daniel E. <dolson(a)mcs.anl.gov>wrote: > Hi all, > > user_and_job_state has been deployed, and tested in the test environment. > > We're ready for the following steps: > pass script standards > pass - there are no scripts; This is a check to make sure that scrips (if they exist) properly return a help message when '-h' or '--help' are passed, and the correct error code. We'll also use this on new modules to ensure script naming conventions and other standards are met (described here: https://docs.google.com/document/d/1bwXes9-f99Hr8EknQ8nrL0UfYpB0rlYVKsSxvE9… ) > pass initial doc qc > fail, docs are not appearing here: http://140.221.84.191/services/user_and_job_state/ (although it seems they are properly deployed to /kb/deployment/services/userandjobstate/webroot) This test is to ensure API documentation exists, is generated, is deployed to the proper webroot directory, and appears here: http://140.221.84.191/services/. We also conduct a basic read through to make sure the documentation actually 'seems' to make sense and are mostly complete. If other technical docs appear in webroot, we take a look as well to make sure the docs seem to make sense. > pass final doc qc > I believe this column is there if the initial doc qc failed, the developer checked in changes to correct the documentation problems, and the documentation team takes a second look. Since it looks like in the new spreadsheet format we are creating a new row every time a service is redeployed, do we still need this column? I propose that we get rid of it... > release notes updated pass - this is a simple test to make sure a Release Notes file exists, and has minimal documentation on what is new in this release. > > Do we have each of these documented? I would like to know what our > criteria and pass/fail logic is for each of these. > > > ---- > Daniel Murphy-Olson > Systems Administrator > Mathematics & Computer Science Division > Argonne National Laboratory > 630-252-0055 > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Deployment of userandjobstate
by Murphy-Olson, Daniel E. 04 Nov '13

04 Nov '13

Hi all, user_and_job_state has been deployed, and tested in the test environment. We're ready for the following steps: pass script standards pass initial doc qc pass final doc qc release notes updated Do we have each of these documented? I would like to know what our criteria and pass/fail logic is for each of these. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055

1 0

Re: [Release-team] deployment next week
by Gavin Price 04 Nov '13

04 Nov '13

That's fine - but someone has to be the first :P -g On 11/4/2013 8:57 AM, Mundy, Michael B. (Mike) wrote: > I'll wait for the major build in a few weeks to make the switch to the > user_and_job_state service. > > Tom, please deploy CBD from what is currently in the master branch. > > Mike Mundy | Senior Analyst Programmer | Bioinformatics > Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu > Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org > <http://www.mayoclinic.org> > > > > > On 11/4/13 10:50 AM, "Gavin Price"<gaprice(a)lbl.gov> wrote: > >> I'd say the question is whether you're ok being an early adopter of an >> immature service - if you're ok with that I am as well. >> >> One minor point - I made a small change to the API of the list_jobs >> function on Friday. I'd imagine you're not using that function, but if >> you are you'll need to update. >> >> -g >> >> On 11/4/2013 6:34 AM, Mundy, Michael B. (Mike) wrote: >>> Yes, I would like a new deploy of the CBD service. Gavin, are you OK >>> with >>> switching CBD to use the user_and_job_state service? I have the changes >>> in a branch that I would need to merge to master before a deploy. >>> >>> Mike Mundy | Senior Analyst Programmer | Bioinformatics >>> Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu >>> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org >>> <http://www.mayoclinic.org> >>> >>> >>> >>> >>> On 11/1/13 2:04 PM, "Thomas Brettin"<brettin(a)mcs.anl.gov> wrote: >>> >>>> Gavin is asking for a production release of the user_and_job_state >>>> service. A production deploy of the handle_service would also be good. >>>> The may guys also want the CBD module deployed to prod. Can we start >>>> this >>>> up Monday morning? >>>> >>>> There may be others as well. >>>> >>>> Tom >

1 0