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

Re: [Release-team] Python servers non-functional in January build
by Mundy, Michael B. (Mike) 20 Jan '14

20 Jan '14

Shane, Thanks for adding cogent. I forgot that cogent has a dependency on mpi4py (it throws annoying error messages if it is not found). I was running on t1. I'm confused by the new test environment for this build. Are all of the servers supposed to be running on t1? Or on the instances specified in /root/services? For example, the services file says that workspace_deluxe should be running on t49 at port 7058. But when I checked on t49 this morning there was nothing listening on port 7058. I'll be at Argonne Tuesday and Wednesday. Who would be the best person to work with there? Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org> From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> Date: Friday, January 17, 2014 2:39 PM To: Michael Mundy <mundy.michael(a)mayo.edu<mailto:[email protected]>> Cc: "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>>, Christopher Henry <chrisshenry(a)gmail.com<mailto:[email protected]>>, Stephen Chan <sychan(a)lbl.gov<mailto:[email protected]>>, Matthew Benedict <matthew.n.benedict(a)gmail.com<mailto:[email protected]>>, "Chia, Nicholas, Ph.D." <Chia.Nicholas(a)mayo.edu<mailto:[email protected]>>, "N.L. Harris" <nlharris(a)lbl.gov<mailto:[email protected]>> Subject: Re: [Release-team] Python servers non-functional in January build 1. I'm not sure about this. Is this on t1 or production? It could be the client tools aren't matched. ws is the new workspace which isn't "public" yet. 2. I'm seeing this too and I think it is related to going through the nginx proxy. There have been some discussions about this. 3. I added cogent on the 2014 runtime on t1. Let me know if you need more. --Shane On Jan 17, 2014, at 10:45 AM, "Mundy, Michael B. (Mike)" <Mundy.Michael(a)mayo.edu<mailto:[email protected]>> wrote: Shane, Here's what I found in my testing: 1. I used https://kbase.us/services/ws/ as the URL for the new workspace service but I'm getting a "HTTPError: HTTP Error 502: Bad Gateway" error when accessing it. 2. I'm getting a "client-tests/1_V2.fasta: error: Error creating node: request error: 411 Length Required" error when trying to upload a file to shock. The shock team had already looked at this and said it was a problem with the old shock server. The shock-client.cfg file for the ubuntu user has the server URL set to url=http://kbase.us/services/shock-api. Is that URL going to the server in the new deployment. 3. The cogent Python package isn't installed in the kbase Python installation (cogent is installed in the system Python installation). Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org/> From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> Date: Friday, January 17, 2014 11:01 AM To: Michael Mundy <mundy.michael(a)mayo.edu<mailto:[email protected]>> Cc: "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>>, Christopher Henry <chrisshenry(a)gmail.com<mailto:[email protected]>>, Stephen Chan <sychan(a)lbl.gov<mailto:[email protected]>>, Matthew Benedict <matthew.n.benedict(a)gmail.com<mailto:[email protected]>>, "Chia, Nicholas, Ph.D." <Chia.Nicholas(a)mayo.edu<mailto:[email protected]>>, "N.L. Harris" <nlharris(a)lbl.gov<mailto:[email protected]>> Subject: Re: [Release-team] Python servers non-functional in January build Mike, When I originally built the runtime and deployment, I inadvertently used 2013 instead of 2014 in the path. I've created a new runtime and deployment with the correct date (/kbase/deployments/20140109-prod/ and /kbase/runtimes/20140109-prod/). That version should have Steve's changes. Can you test that out? I still need to restart a few services that were originally started with the 2013 tree. I will do that now. --Shane On Jan 17, 2014, at 8:43 AM, "Mundy, Michael B. (Mike)" <Mundy.Michael(a)mayo.edu<mailto:[email protected]>> wrote: Authenticated Python servers are currently non-functional in the January build. Steve Chan has fixed the problem with changes to the auth module with the following commits: commit 12f346a4ed8e2d30a580d85e7e7987c78568b9bb Merge: 1d98332 0eca1d4 Author: Steve Chan <sychan(a)lbl.gov<mailto:[email protected]>> Date: Mon Jan 13 15:46:37 2014 -0800 Merge branch 'master' into dev_requests-1.x Conflicts: Bio-KBase-Auth/lib/Bio/KBase/Auth.pm python-libs/biokbase/nexus/__init__.py commit 0eca1d43361b8955b0d9ce391778cd5a86561150 Author: Steve Chan <sychan(a)lbl.gov<mailto:[email protected]>> Date: Mon Jan 13 15:41:46 2014 -0800 Part of cleanup for the Nexus/requests library API drift Can we get these two commits in the build and installed on the t1 system. The Probabilistic Annotation and Compression Based Distance services cannot complete the build until this is done. Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org/> _______________________________________________ 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] Python servers non-functional in January build
by Shane Canon 17 Jan '14

17 Jan '14

1. I'm not sure about this. Is this on t1 or production? It could be the client tools aren't matched. ws is the new workspace which isn't "public" yet. 2. I'm seeing this too and I think it is related to going through the nginx proxy. There have been some discussions about this. 3. I added cogent on the 2014 runtime on t1. Let me know if you need more. --Shane On Jan 17, 2014, at 10:45 AM, "Mundy, Michael B. (Mike)" <Mundy.Michael(a)mayo.edu> wrote: > Shane, > > Here's what I found in my testing: > I used https://kbase.us/services/ws/ as the URL for the new workspace service but I'm getting a "HTTPError: HTTP Error 502: Bad Gateway" error when accessing it. > I'm getting a "client-tests/1_V2.fasta: error: Error creating node: request error: 411 Length Required" error when trying to upload a file to shock. The shock team had already looked at this and said it was a problem with the old shock server. The shock-client.cfg file for the ubuntu user has the server URL set to url=http://kbase.us/services/shock-api. Is that URL going to the server in the new deployment. > The cogent Python package isn't installed in the kbase Python installation (cogent is installed in the system Python installation). > 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 > > From: Shane Canon <scanon(a)lbl.gov> > Date: Friday, January 17, 2014 11:01 AM > To: Michael Mundy <mundy.michael(a)mayo.edu> > Cc: "release-team(a)kbase.us" <release-team(a)kbase.us>, Christopher Henry <chrisshenry(a)gmail.com>, Stephen Chan <sychan(a)lbl.gov>, Matthew Benedict <matthew.n.benedict(a)gmail.com>, "Chia, Nicholas, Ph.D." <Chia.Nicholas(a)mayo.edu>, "N.L. Harris" <nlharris(a)lbl.gov> > Subject: Re: [Release-team] Python servers non-functional in January build > > > Mike, > > When I originally built the runtime and deployment, I inadvertently used 2013 instead of 2014 in the path. I've created a new runtime and deployment with the correct date (/kbase/deployments/20140109-prod/ and > /kbase/runtimes/20140109-prod/). That version should have Steve's changes. Can you test that out? I still need to restart a few services that were originally started with the 2013 tree. I will do that now. > > > --Shane > > On Jan 17, 2014, at 8:43 AM, "Mundy, Michael B. (Mike)" <Mundy.Michael(a)mayo.edu> wrote: > >> Authenticated Python servers are currently non-functional in the January build. Steve Chan has fixed the problem with changes to the auth module with the following commits: >> >> commit 12f346a4ed8e2d30a580d85e7e7987c78568b9bb >> Merge: 1d98332 0eca1d4 >> Author: Steve Chan <sychan(a)lbl.gov> >> Date: Mon Jan 13 15:46:37 2014 -0800 >> >> Merge branch 'master' into dev_requests-1.x >> >> Conflicts: >> Bio-KBase-Auth/lib/Bio/KBase/Auth.pm >> python-libs/biokbase/nexus/__init__.py >> >> commit 0eca1d43361b8955b0d9ce391778cd5a86561150 >> Author: Steve Chan <sychan(a)lbl.gov> >> Date: Mon Jan 13 15:41:46 2014 -0800 >> >> Part of cleanup for the Nexus/requests library API drift >> >> Can we get these two commits in the build and installed on the t1 system. The Probabilistic Annotation and Compression Based Distance services cannot complete the build until this is done. >> >> 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 >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] Python servers non-functional in January build
by Mundy, Michael B. (Mike) 17 Jan '14

17 Jan '14

Shane, Here's what I found in my testing: 1. I used https://kbase.us/services/ws/ as the URL for the new workspace service but I'm getting a "HTTPError: HTTP Error 502: Bad Gateway" error when accessing it. 2. I'm getting a "client-tests/1_V2.fasta: error: Error creating node: request error: 411 Length Required" error when trying to upload a file to shock. The shock team had already looked at this and said it was a problem with the old shock server. The shock-client.cfg file for the ubuntu user has the server URL set to url=http://kbase.us/services/shock-api. Is that URL going to the server in the new deployment. 3. The cogent Python package isn't installed in the kbase Python installation (cogent is installed in the system Python installation). Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org> From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> Date: Friday, January 17, 2014 11:01 AM To: Michael Mundy <mundy.michael(a)mayo.edu<mailto:[email protected]>> Cc: "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>>, Christopher Henry <chrisshenry(a)gmail.com<mailto:[email protected]>>, Stephen Chan <sychan(a)lbl.gov<mailto:[email protected]>>, Matthew Benedict <matthew.n.benedict(a)gmail.com<mailto:[email protected]>>, "Chia, Nicholas, Ph.D." <Chia.Nicholas(a)mayo.edu<mailto:[email protected]>>, "N.L. Harris" <nlharris(a)lbl.gov<mailto:[email protected]>> Subject: Re: [Release-team] Python servers non-functional in January build Mike, When I originally built the runtime and deployment, I inadvertently used 2013 instead of 2014 in the path. I've created a new runtime and deployment with the correct date (/kbase/deployments/20140109-prod/ and /kbase/runtimes/20140109-prod/). That version should have Steve's changes. Can you test that out? I still need to restart a few services that were originally started with the 2013 tree. I will do that now. --Shane On Jan 17, 2014, at 8:43 AM, "Mundy, Michael B. (Mike)" <Mundy.Michael(a)mayo.edu<mailto:[email protected]>> wrote: Authenticated Python servers are currently non-functional in the January build. Steve Chan has fixed the problem with changes to the auth module with the following commits: commit 12f346a4ed8e2d30a580d85e7e7987c78568b9bb Merge: 1d98332 0eca1d4 Author: Steve Chan <sychan(a)lbl.gov<mailto:[email protected]>> Date: Mon Jan 13 15:46:37 2014 -0800 Merge branch 'master' into dev_requests-1.x Conflicts: Bio-KBase-Auth/lib/Bio/KBase/Auth.pm python-libs/biokbase/nexus/__init__.py commit 0eca1d43361b8955b0d9ce391778cd5a86561150 Author: Steve Chan <sychan(a)lbl.gov<mailto:[email protected]>> Date: Mon Jan 13 15:41:46 2014 -0800 Part of cleanup for the Nexus/requests library API drift Can we get these two commits in the build and installed on the t1 system. The Probabilistic Annotation and Compression Based Distance services cannot complete the build until this is done. Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org/> _______________________________________________ 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] Python servers non-functional in January build
by Mundy, Michael B. (Mike) 17 Jan '14

17 Jan '14

Thanks Shane. I was able to start both servers using the 20140109-prod deployment. I'll try testing them next. Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org> From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> Date: Friday, January 17, 2014 11:01 AM To: Michael Mundy <mundy.michael(a)mayo.edu<mailto:[email protected]>> Cc: "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>>, Christopher Henry <chrisshenry(a)gmail.com<mailto:[email protected]>>, Stephen Chan <sychan(a)lbl.gov<mailto:[email protected]>>, Matthew Benedict <matthew.n.benedict(a)gmail.com<mailto:[email protected]>>, "Chia, Nicholas, Ph.D." <Chia.Nicholas(a)mayo.edu<mailto:[email protected]>>, "N.L. Harris" <nlharris(a)lbl.gov<mailto:[email protected]>> Subject: Re: [Release-team] Python servers non-functional in January build Mike, When I originally built the runtime and deployment, I inadvertently used 2013 instead of 2014 in the path. I've created a new runtime and deployment with the correct date (/kbase/deployments/20140109-prod/ and /kbase/runtimes/20140109-prod/). That version should have Steve's changes. Can you test that out? I still need to restart a few services that were originally started with the 2013 tree. I will do that now. --Shane On Jan 17, 2014, at 8:43 AM, "Mundy, Michael B. (Mike)" <Mundy.Michael(a)mayo.edu<mailto:[email protected]>> wrote: Authenticated Python servers are currently non-functional in the January build. Steve Chan has fixed the problem with changes to the auth module with the following commits: commit 12f346a4ed8e2d30a580d85e7e7987c78568b9bb Merge: 1d98332 0eca1d4 Author: Steve Chan <sychan(a)lbl.gov<mailto:[email protected]>> Date: Mon Jan 13 15:46:37 2014 -0800 Merge branch 'master' into dev_requests-1.x Conflicts: Bio-KBase-Auth/lib/Bio/KBase/Auth.pm python-libs/biokbase/nexus/__init__.py commit 0eca1d43361b8955b0d9ce391778cd5a86561150 Author: Steve Chan <sychan(a)lbl.gov<mailto:[email protected]>> Date: Mon Jan 13 15:41:46 2014 -0800 Part of cleanup for the Nexus/requests library API drift Can we get these two commits in the build and installed on the t1 system. The Probabilistic Annotation and Compression Based Distance services cannot complete the build until this is done. Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org/> _______________________________________________ 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] Python servers non-functional in January build
by Shane Canon 17 Jan '14

17 Jan '14

Mike, When I originally built the runtime and deployment, I inadvertently used 2013 instead of 2014 in the path. I've created a new runtime and deployment with the correct date (/kbase/deployments/20140109-prod/ and /kbase/runtimes/20140109-prod/). That version should have Steve's changes. Can you test that out? I still need to restart a few services that were originally started with the 2013 tree. I will do that now. --Shane On Jan 17, 2014, at 8:43 AM, "Mundy, Michael B. (Mike)" <Mundy.Michael(a)mayo.edu> wrote: > Authenticated Python servers are currently non-functional in the January build. Steve Chan has fixed the problem with changes to the auth module with the following commits: > > commit 12f346a4ed8e2d30a580d85e7e7987c78568b9bb > Merge: 1d98332 0eca1d4 > Author: Steve Chan <sychan(a)lbl.gov> > Date: Mon Jan 13 15:46:37 2014 -0800 > > Merge branch 'master' into dev_requests-1.x > > Conflicts: > Bio-KBase-Auth/lib/Bio/KBase/Auth.pm > python-libs/biokbase/nexus/__init__.py > > commit 0eca1d43361b8955b0d9ce391778cd5a86561150 > Author: Steve Chan <sychan(a)lbl.gov> > Date: Mon Jan 13 15:41:46 2014 -0800 > > Part of cleanup for the Nexus/requests library API drift > > Can we get these two commits in the build and installed on the t1 system. The Probabilistic Annotation and Compression Based Distance services cannot complete the build until this is done. > > 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 > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Python servers non-functional in January build
by Mundy, Michael B. (Mike) 17 Jan '14

17 Jan '14

Authenticated Python servers are currently non-functional in the January build. Steve Chan has fixed the problem with changes to the auth module with the following commits: commit 12f346a4ed8e2d30a580d85e7e7987c78568b9bb Merge: 1d98332 0eca1d4 Author: Steve Chan <sychan(a)lbl.gov> Date: Mon Jan 13 15:46:37 2014 -0800 Merge branch 'master' into dev_requests-1.x Conflicts: Bio-KBase-Auth/lib/Bio/KBase/Auth.pm python-libs/biokbase/nexus/__init__.py commit 0eca1d43361b8955b0d9ce391778cd5a86561150 Author: Steve Chan <sychan(a)lbl.gov> Date: Mon Jan 13 15:41:46 2014 -0800 Part of cleanup for the Nexus/requests library API drift Can we get these two commits in the build and installed on the t1 system. The Probabilistic Annotation and Compression Based Distance services cannot complete the build until this is done. Mike Mundy | Senior Analyst Programmer | Bioinformatics Systems Unit | 507-266-7232 | mundy.michael(a)mayo.edu<mailto:[email protected]> Mayo Clinic | 200 First Street SW | Rochester, MN 55905 | mayoclinic.org<http://www.mayoclinic.org>

1 0

Re: [Release-team] Status of modules for the Jan. 15 deadline
by Brettin, Thomas S. 15 Jan '14

15 Jan '14

I thought that Shock shouldn't be going through nginx. Is it? Jared could definitely help. tom On Jan 15, 2014, at 12:53 PM, Shane Canon <scanon(a)lbl.gov> wrote: > > There is a header (content-length) that is getting added/dropped somewhere in the communication chain. > > So Jared Bischof could help too? > > --Shane > > > On Jan 15, 2014, at 10:41 AM, "Brettin, Thomas S." <brettin(a)cels.anl.gov> wrote: > >> What's the issue? >> >> Python lib and shock? That would be Travis or Jared. >> >> >> On Jan 15, 2014, at 12:39 PM, Shane Canon <scanon(a)lbl.gov> >> wrote: >> >>> >>> On further investigation I think it is an interaction between nginx and the service. I've got a question out to Tobias about it. Is there anyone >>> else we could ask? >>> >>> --Shane >>> >>> >>> On Jan 15, 2014, at 9:36 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >>> >>>> I think you are right about the python. >>>> >>>> Miriam >>>> >>>> From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> >>>> Date: Wednesday, January 15, 2014 11:41 AM >>>> To: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]>> >>>> Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>>, "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>> >>>> Subject: Re: [Release-team] Status of modules for the Jan. 15 deadline >>>> >>>> >>>> I don't recall updating the spreadsheet. However, my recollection is that we don't have any tests for AWE and Shock anyway. >>>> So I'm not sure how we validate it. >>>> >>>> I'm working on an issue related to shock, but I now think it may be related to the python request library. >>>> >>>> --Shane >>>> >>>> >>>> On Jan 14, 2014, at 3:26 PM, "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov<mailto:[email protected]>> wrote: >>>> >>>> Miriam, >>>> I believe Shane was working on troubleshooting the shock issues, and he may know the details behind the anonymous edits. >>>> I haven't made any updates other than opening the new workspace service up. >>>> Tomorrow we're going to need a big push to get everything to production. I'll be available all day. >>>> ---- >>>> Daniel Murphy-Olson >>>> Systems Administrator >>>> Mathematics & Computer Science Division >>>> Argonne National Laboratory >>>> 630-252-0055 >>>> ________________________________________ >>>> From: release-team-bounces(a)lists.kbase.us<mailto:[email protected]> [release-team-bounces(a)lists.kbase.us<mailto:[email protected]>] on behalf of Land, Miriam L. [landml(a)ornl.gov<mailto:[email protected]>] >>>> Sent: Tuesday, January 14, 2014 2:12 PM >>>> To: release-team(a)kbase.us<mailto:[email protected]> >>>> Subject: [Release-team] Status of modules for the Jan. 15 deadline >>>> All, >>>> I haven't seen any status changes in the KBase Services spreadsheet since I left on Friday. Have there been any changes? >>>> I noticed that 'anonymous' marked Shock and Workspace deluxe as 'okay to deploy to production' and 'deployed on prod' without passing testing and Shock had no review of script standards, documentation, or release notes. I'm okay with having exceptions in our process but why are we doing it as anonymous and without explanation/documentation?? >>>> Miriam >>>> _______________________________________________ >>>> Release-team mailing list >>>> Release-team(a)lists.kbase.us<mailto:[email protected]> >>>> https://lists.kbase.us/mailman/listinfo/release-team >>>> _______________________________________________ >>>> Release-team mailing list >>>> Release-team(a)lists.kbase.us<mailto:[email protected]> >>>> 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 >> > > _______________________________________________ > 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 modules for the Jan. 15 deadline
by Shane Canon 15 Jan '14

15 Jan '14

There is a header (content-length) that is getting added/dropped somewhere in the communication chain. So Jared Bischof could help too? --Shane On Jan 15, 2014, at 10:41 AM, "Brettin, Thomas S." <brettin(a)cels.anl.gov> wrote: > What's the issue? > > Python lib and shock? That would be Travis or Jared. > > > On Jan 15, 2014, at 12:39 PM, Shane Canon <scanon(a)lbl.gov> > wrote: > >> >> On further investigation I think it is an interaction between nginx and the service. I've got a question out to Tobias about it. Is there anyone >> else we could ask? >> >> --Shane >> >> >> On Jan 15, 2014, at 9:36 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >> >>> I think you are right about the python. >>> >>> Miriam >>> >>> From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> >>> Date: Wednesday, January 15, 2014 11:41 AM >>> To: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]>> >>> Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>>, "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>> >>> Subject: Re: [Release-team] Status of modules for the Jan. 15 deadline >>> >>> >>> I don't recall updating the spreadsheet. However, my recollection is that we don't have any tests for AWE and Shock anyway. >>> So I'm not sure how we validate it. >>> >>> I'm working on an issue related to shock, but I now think it may be related to the python request library. >>> >>> --Shane >>> >>> >>> On Jan 14, 2014, at 3:26 PM, "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov<mailto:[email protected]>> wrote: >>> >>> Miriam, >>> I believe Shane was working on troubleshooting the shock issues, and he may know the details behind the anonymous edits. >>> I haven't made any updates other than opening the new workspace service up. >>> Tomorrow we're going to need a big push to get everything to production. I'll be available all day. >>> ---- >>> Daniel Murphy-Olson >>> Systems Administrator >>> Mathematics & Computer Science Division >>> Argonne National Laboratory >>> 630-252-0055 >>> ________________________________________ >>> From: release-team-bounces(a)lists.kbase.us<mailto:[email protected]> [release-team-bounces(a)lists.kbase.us<mailto:[email protected]>] on behalf of Land, Miriam L. [landml(a)ornl.gov<mailto:[email protected]>] >>> Sent: Tuesday, January 14, 2014 2:12 PM >>> To: release-team(a)kbase.us<mailto:[email protected]> >>> Subject: [Release-team] Status of modules for the Jan. 15 deadline >>> All, >>> I haven't seen any status changes in the KBase Services spreadsheet since I left on Friday. Have there been any changes? >>> I noticed that 'anonymous' marked Shock and Workspace deluxe as 'okay to deploy to production' and 'deployed on prod' without passing testing and Shock had no review of script standards, documentation, or release notes. I'm okay with having exceptions in our process but why are we doing it as anonymous and without explanation/documentation?? >>> Miriam >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us<mailto:[email protected]> >>> https://lists.kbase.us/mailman/listinfo/release-team >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us<mailto:[email protected]> >>> 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 modules for the Jan. 15 deadline
by Brettin, Thomas S. 15 Jan '14

15 Jan '14

What's the issue? Python lib and shock? That would be Travis or Jared. On Jan 15, 2014, at 12:39 PM, Shane Canon <scanon(a)lbl.gov> wrote: > > On further investigation I think it is an interaction between nginx and the service. I've got a question out to Tobias about it. Is there anyone > else we could ask? > > --Shane > > > On Jan 15, 2014, at 9:36 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > >> I think you are right about the python. >> >> Miriam >> >> From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> >> Date: Wednesday, January 15, 2014 11:41 AM >> To: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]>> >> Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>>, "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>> >> Subject: Re: [Release-team] Status of modules for the Jan. 15 deadline >> >> >> I don't recall updating the spreadsheet. However, my recollection is that we don't have any tests for AWE and Shock anyway. >> So I'm not sure how we validate it. >> >> I'm working on an issue related to shock, but I now think it may be related to the python request library. >> >> --Shane >> >> >> On Jan 14, 2014, at 3:26 PM, "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov<mailto:[email protected]>> wrote: >> >> Miriam, >> I believe Shane was working on troubleshooting the shock issues, and he may know the details behind the anonymous edits. >> I haven't made any updates other than opening the new workspace service up. >> Tomorrow we're going to need a big push to get everything to production. I'll be available all day. >> ---- >> Daniel Murphy-Olson >> Systems Administrator >> Mathematics & Computer Science Division >> Argonne National Laboratory >> 630-252-0055 >> ________________________________________ >> From: release-team-bounces(a)lists.kbase.us<mailto:[email protected]> [release-team-bounces(a)lists.kbase.us<mailto:[email protected]>] on behalf of Land, Miriam L. [landml(a)ornl.gov<mailto:[email protected]>] >> Sent: Tuesday, January 14, 2014 2:12 PM >> To: release-team(a)kbase.us<mailto:[email protected]> >> Subject: [Release-team] Status of modules for the Jan. 15 deadline >> All, >> I haven't seen any status changes in the KBase Services spreadsheet since I left on Friday. Have there been any changes? >> I noticed that 'anonymous' marked Shock and Workspace deluxe as 'okay to deploy to production' and 'deployed on prod' without passing testing and Shock had no review of script standards, documentation, or release notes. I'm okay with having exceptions in our process but why are we doing it as anonymous and without explanation/documentation?? >> Miriam >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us<mailto:[email protected]> >> https://lists.kbase.us/mailman/listinfo/release-team >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us<mailto:[email protected]> >> 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 modules for the Jan. 15 deadline
by Land, Miriam L. 15 Jan '14

15 Jan '14

Mike Munday was raising issues because of the CBD and Probabilistic Annotation modules. Miriam From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]>> Date: Wednesday, January 15, 2014 1:39 PM To: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>> Cc: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]>>, "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>> Subject: Re: [Release-team] Status of modules for the Jan. 15 deadline On further investigation I think it is an interaction between nginx and the service. I've got a question out to Tobias about it. Is there anyone else we could ask? --Shane On Jan 15, 2014, at 9:36 AM, "Land, Miriam L." <landml(a)ornl.gov<mailto:[email protected]>> wrote: I think you are right about the python. Miriam From: Shane Canon <scanon(a)lbl.gov<mailto:[email protected]><mailto:[email protected]>> Date: Wednesday, January 15, 2014 11:41 AM To: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]><mailto:[email protected]>> Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]><mailto:[email protected]>>, "release-team(a)kbase.us<mailto:[email protected]><mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]><mailto:[email protected]>> Subject: Re: [Release-team] Status of modules for the Jan. 15 deadline I don't recall updating the spreadsheet. However, my recollection is that we don't have any tests for AWE and Shock anyway. So I'm not sure how we validate it. I'm working on an issue related to shock, but I now think it may be related to the python request library. --Shane On Jan 14, 2014, at 3:26 PM, "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov<mailto:[email protected]><mailto:[email protected]>> wrote: Miriam, I believe Shane was working on troubleshooting the shock issues, and he may know the details behind the anonymous edits. I haven't made any updates other than opening the new workspace service up. Tomorrow we're going to need a big push to get everything to production. I'll be available all day. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055 ________________________________________ From: release-team-bounces(a)lists.kbase.us<mailto:[email protected]><mailto:[email protected]> [release-team-bounces(a)lists.kbase.us<mailto:[email protected]><mailto:[email protected]>] on behalf of Land, Miriam L. [landml(a)ornl.gov<mailto:[email protected]><mailto:[email protected]>] Sent: Tuesday, January 14, 2014 2:12 PM To: release-team(a)kbase.us<mailto:[email protected]><mailto:[email protected]> Subject: [Release-team] Status of modules for the Jan. 15 deadline All, I haven't seen any status changes in the KBase Services spreadsheet since I left on Friday. Have there been any changes? I noticed that 'anonymous' marked Shock and Workspace deluxe as 'okay to deploy to production' and 'deployed on prod' without passing testing and Shock had no review of script standards, documentation, or release notes. I'm okay with having exceptions in our process but why are we doing it as anonymous and without explanation/documentation?? Miriam _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us<mailto:[email protected]><mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us<mailto:[email protected]><mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team

1 0