ParOscLabEnv < Keck/NGAO

---+!! NGWFC Lab Environment

---++ MVME6100

---+++ Boot parameters
Uses oneo (128.171.96.192) as the boot host instead of deprecated kuhio.  Oneo is a solaris-8 container setup specifically to replace kuhio and be the 'new' NGWFC build host.
<verbatim>
boot device          : geisc0 
processor number     : 0 
host name            : host 
file name            : /usr/local/vw/ngwfc/rtc/VxWorks_vec/default/vxWorks 
inet on ethernet (e) : 10.96.10.17 
inet on backplane (b): 
host inet (h)        : 128.171.96.192 
gateway inet (g)     : 10.96.0.1 
user (u)             : target 
ftp password (pw) (blank = use rsh): calabash 
flags (f)            : 0x0 
target name (tn)     : ngwfc0 
startup script (s)   : <ngwfc/labStartupScript 
other (o)            : 
</verbatim>

---+++ Console port connection
   * *telnet hqconsoles-2 2011*

---+++ Startup script

---++ Build host: *oneo*
This is the development build and test host.  It's a solaris-8 container modeled on makua, the current AO build server.  The main reason for the creation of oneo, is to separate the development area for NGWFC upgrades and protect the controlled build area.  This is the area that Microgate would also use to do their lab testing.

---+++ oneo:/kroot
Oneo's /kroot is brand new and was built from scratch on 2010aug31.  To do this the original makua /kroot link was removed (/home/aobld/kroot) and a new one on the filer was created and linked to.

   * oneo:/kroot -> /net/filer/vol/vol0/kroot/ngwfcdev_kroot

Once we got the top level /kroot directory setup, the following command was used to checkout and build the core DCS hierarchy:

   * ~cm/swcm/default/autoBuildKROOT.csh krootCoreDCS -user -head

This is checks out and build krootCore and adds DCS which contains EPCOM which is needed to build the AO subsystems.  After this was successfully built, each AO subsystem was individually checked out and built.
This topic: Keck/NGAO > WebHome > ParOscRiskReduction > ParOscLabEnv
Topic revision: r2 - 2010-08-31 - KevinTsubota