Ran through most of the FBA functions called from the narrative, and things still seem to be working correctly....


On Fri, Feb 7, 2014 at 6:57 PM, Michael Sneddon <mwsneddon@lbl.gov> wrote:
Cool!  I tried one method against https://kbase.us/services/KBaseFBAModeling, and it actually seemed to work as expected.  I'll start switching over other narrative functions and see if we encounter any issues.


On Fri, Feb 7, 2014 at 6:50 PM, Shane Canon <scanon@lbl.gov> wrote:

I think this fell through the cracks with all the excitement.

I've deployed in production.  I'm worried there may be an issue.  Can you check it out?

--Shane

On Feb 7, 2014, at 5:51 PM, Michael Sneddon <mwsneddon@lbl.gov> wrote:

I know all the mongo problems got in the way, but any updates on deploying the FBA service to production?
thanks,
-michael


On Fri, Feb 7, 2014 at 9:19 AM, Shane Canon <scanon@lbl.gov> wrote:

I'll quickly pull the update and then we can start promoting things to prod soon.   Dan: Does this sound good?

--Shane

On Feb 7, 2014, at 9:08 AM, "Land, Miriam L." <landml@ornl.gov> wrote:

> I think this can up because we have FBAModeling in limbo.
>
> Chris fixed command-line help on "ga-annotate-ws-genome" and "fba-adjustmapcomplex" and checked them into master.
>
> WHAT is  our next step?  Are we going to
>
> 1.  update the test VM with his latest changes or
> 2.  promote the version in test to production?
>
> This is a critical module and we shouldn't postpone this decision any further. The burden in on the deploy team so I would like to hear their vote.
>
> Miriam
>
>
> From: Shane Canon <scanon@lbl.gov<mailto:scanon@lbl.gov>>
> Date: Thursday, February 6, 2014 4:03 PM
> To: "release-team@kbase.us<mailto:release-team@kbase.us>" <release-team@kbase.us<mailto:release-team@kbase.us>>
> Subject: [Release-team] Changes for deploy
>
>
> FYI.  For some modules, I've had to make some changes to get things to deploy.  This makes pulling updates a bit of  a pain.
> So I'm not trying to keep things in a branch, so that I can just do a merge to get any updates.  I've been calling this branch
> deploy-20140206.  I'm _not_ pushing it to git.kbase.us.  It is just local to the t1 cluster.
>
> --Shane
> _______________________________________________
> Release-team mailing list
> Release-team@lists.kbase.us<mailto:Release-team@lists.kbase.us>
> https://lists.kbase.us/mailman/listinfo/release-team
>

_______________________________________________
Release-team mailing list
Release-team@lists.kbase.us
https://lists.kbase.us/mailman/listinfo/release-team