Setup MarineMap stack for Oregon

[GoogleCodeExporter]

May be on AWS, may be on a DLCD server.

Original issue reported on code.google.com by underbluewaters on 31 May 2010 at 9:49

[GoogleCodeExporter]

let's hope it's AWS.  I don't think a state machine would be an easy thing to 
deal
with.  

Original comment by ColinMEb...@gmail.com on 31 May 2010 at 10:38

[GoogleCodeExporter]

We will be making all the relavent arguments to try and be sure that happens. 
Do you think this time estimate is 
generous or to little? Efficiency of setup will be another point to make with 
them.

Original comment by underbluewaters on 1 Jun 2010 at 6:02

[GoogleCodeExporter]

I think if it's an AWS box, it could be down to 12 or so.  If it's a box 
managed on a
government setup, it could be a week, maybe longer.  There's really no way to 
tell.

Original comment by ColinMEb...@gmail.com on 1 Jun 2010 at 8:09

[GoogleCodeExporter]

This ticket represents the work for just the dev server. It should be the same 
type of setup as what the 
production server will eventually become.

Original comment by underbluewaters on 1 Jun 2010 at 11:05

• Added labels: OregonWorkPlan-2

[GoogleCodeExporter]

From the work plan:

"The first step in the development of OMM is the setup of the base development 
server and application. After 
setup, the server and application then will be transferred over to a production 
server.  The base development 
server will be maintained in conjunction with the production server for testing 
and additional feature and 
function development.  Both development and server setup with be done in 
collaboration with DLCD staff, as 
the application will likely be hosted on-site by DLCD after completion."

This could mean a setup that DLCD would support long term on AWS.

Original comment by underbluewaters on 1 Jun 2010 at 11:10

[GoogleCodeExporter]

ready to go on a root EBS volume

Original comment by ColinMEb...@gmail.com on 1 Jul 2010 at 4:44

• Changed state: Done