AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Khalid.A@lsi.com>,<Larry.Scheer@lsi.com>,<Ed.Kwan@lsi.com>,<brian.stark@lsi.com>,<Jobi.Ariyamannil@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	0D1E8821739E724A86F4D16902CE275C1C93C757DE@inbmail01.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 2 Dec 2009 10:39:24 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "A, Khalid" <Khalid.A@lsi.com>
Cc: "Scheer, Larry" <Larry.Scheer@lsi.com>, "Kwan, Ed" <Ed.Kwan@lsi.com>,
 Brian Stark <brian.stark@lsi.com>, "Ariyamannil, Jobi"
 <Jobi.Ariyamannil@lsi.com>
Subject: Re: NAS web UI questions
Message-ID: <20091202103924.02714b21@ripper.onstor.net>
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C1C93C757DE@inbmail01.lsi.com>
References: <0D1E8821739E724A86F4D16902CE275C1C93C757DE@inbmail01.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

We need to understand this better.  Orion development definitely needs
to be in a separate branch, but not necessarily all changes should be
confined to that branch if they are applicable to both the gateway and
orion projects.

Larry, do you want to figure out the best way to handle this from an
SCM standpoint?  There are many factors to be contemplated besides what
to name a branch, but I don't need to tell you that.  If you're
inclined, I'd like for you to propose a plan for how to handle this
going forward; and this is likely just the first of its kind.  Then you
can get back to these good folks with how it will all work.

Cheers,

a

On Wed, 2 Dec 2009 04:42:49 -0700 "A, Khalid" <Khalid.A@lsi.com> wrote:

> Hi Larry,
> This is continuation mail, to last request for setting up the
> development environment for NAS WEB BUI development, can you please
> help us with perforce account, and I learned from Jobi that, we must
> have account in perforce to checkout /checkin the change the NAS BUI
> code. Actually I am working integration part of Orion management
> application, and hence I need to modify the NAS WEB UI code to
> address the new Orion requirements. If possible, we would like to
> have a separate branch for Orion development, let me know if works.
> 
> -Khalid
> ________________________________
> From: A, Khalid
> Sent: Friday, November 20, 2009 5:26 PM
> To: Scheer, Larry; Kwan, Ed
> Cc: Sharp, Andy; Hardiman, Richard
> Subject: RE: NAS web UI questions
> 
> 
> Hi Larry,
> 
> Thanks for help, I have Red Hat EL4 running on 32 bit i386 system,
> with GCC 3.5 version but can be upgraded to 4.1.
> 
> I don't have access to perforce yet; actually I am going to ask with
> my manager to get an account created in perforce to checkout/check in
> the code. As of now, I have local snapshot of WEB-UI and CLI code on
> my Linux box; we are trying to build the code to get familiarize with
> UI code base.
> 
> 
> 
> May be you can share the toolchain as an initial step, and help me in
> installing and setting up the dev station, if you can share your
> contact details and free time then I setup a conf call if required.
> 
> -Khalid
> 
> 
> 
> -----Original Message-----
> From: Scheer, Larry
> Sent: Thursday, November 19, 2009 11:33 PM
> To: Kwan, Ed; A, Khalid
> Cc: Sharp, Andy; Hardiman, Richard
> Subject: RE: NAS web UI questions
> 
> 
> 
> Yes, we do have a process to get a developer Linux workstation
> together. I have been working with Richard Hardiman to complete the
> image and automate the final deployment of this image.  We are
> working on completing an image for a 32 bit Intel processors and 64
> bit Intel/AMD processors with Debian Linux.
> 
> 
> 
> If you have one of the following systems I have a process that can
> get these Linux systems working as an ONStor developers workstation:
> 
> 
> 
> Debian Lenny (5.3 -- stable)
> 
> Debian Etch (4.0 -- oldstable)
> 
> Ubuntu 8.10
> 
> Red Hat EL4
> 
> 
> 
> Note about the various Linux flavors:  Our latest build environment
> works best with Debian or Ubuntu 32 or 64 bit systems. I have not
> tested our environment on an Ubuntu system with 9.X installed. 64 bit
> systems running Red Hat EL4 will not compile some of our unit tests.
> A 32 bit system (i386) running RHEL 4 works better than  the amd64
> architecture.
> 
> 
> 
> If you have a one of the above systems I can work with you to get our
> tool chain installed.
> 
> Your system will also need perforce installed and be able to access
> our perforce depot.
> 
> 
> 
> The version of gcc we are currently using is 4.1. We cross compile
> for the mipsel architecture installing the toolchain installs
> mipsel-linux-gnu-gcc-4.1 and a host of other packages to support
> building and running our applications. We don't specify any
> particular version of the JRE for the build environment.
> 
> 
> 
> Larry
> 
> ________________________________________
> 
> From: Kwan, Ed
> 
> Sent: Thursday, November 19, 2009 9:08 AM
> 
> To: A, Khalid; Scheer, Larry
> 
> Cc: Sharp, Andy
> 
> Subject: RE: NAS web UI questions
> 
> 
> 
> I recall Larry was working on a standardized Linux image that has all
> the proper tools for Onstor/EverON developers.  Larry?
> 
> 
> 
> From: A, Khalid
> 
> Sent: Thursday, November 19, 2009 4:50 AM
> 
> To: Kwan, Ed
> 
> Cc: Sharp, Andy
> 
> Subject: RE: NAS web UI questions
> 
> 
> 
> Hi Ed,
> 
> Thanks for below information, and it was really helpful.
> 
> 
> 
> Currently I am trying to set up the WEB UI and CLI development
> environment in my local setups. I believe web UI and CLI are complied
> on Linux system and images are deployed on NAS gateways (running
> Linux OS).Can you please suggest some pointers (some document can do)
> in order to setup the development stations?
> 
> 
> 
> All I did till now is, I have snap of web UI and CLI code on Linux
> box, I could see some make file, but before that I wanted to
> understand what are pre-requisites such as which C complier (GCC
> version), JRE version, etc.
> 
> 
> 
> -Khalid
> 
> ________________________________
> 
> From: Kwan, Ed
> 
> Sent: Friday, November 13, 2009 12:32 PM
> 
> To: A, Khalid
> 
> Cc: Sharp, Andy
> 
> Subject: RE: NAS web UI questions
> 
> 
> 
> CC'ing Andy Sharp.
> 
> 
> 
> There's no web server running on the gateway.  We have daemon called
> sscccc that runs on the gateway that talks to the clients via https.
> 
> The source code is in nfx-tree/code/sm-sct.  The code to process the
> GET requests are in sct-http.c.  The ssl connection is handled in
> sct-ccc-ssl.c.
> 
> If you want to execute a basic NAS command, I suggest "system show
> version".  Here's a sample CLI output:
> 
> 
> 
> g9r208 diag> system show version
> 
> 
> 
> chassis
> 
> --------
> 
>   Model number: ONS-SYS-6720
> 
>   System revision: 3.0
> 
>   System serial number: 0804050003
> 
>   MAC addr: 00:07:34:07:85:00
> 
> 
> 
>   Board model number: ONS-SYS-6720
> 
>   Board revision: 3.0
> 
>   Board serial number: 0804050003
> 
>   BMFPGA : Version 4
> 
>   Boot Dev: sda1 (cf1)
> 
> SSC
> 
>   PROM_SIBYTE_CG : Cougar-prom-1.0.8 : Thu Jul 31 17:59:23 2008
> 
> 
> 
> TXRX0
> 
>   PROM_SIBYTE_CG : Cougar-prom-1.0.8 : Thu Jul 31 17:59:23 2008
> 
>   NFP_TXRX : EverON-4.0.2.9CG : Fri Nov  6 10:13:05 2009
> 
> TXRX1
> 
>   PROM_SIBYTE_CG : Cougar-prom-1.0.8 : Thu Jul 31 17:59:23 2008
> 
>   NFP_TXRX : EverON-4.0.2.9CG : Fri Nov  6 10:13:05 2009
> 
> FP0
> 
>   PROM_SIBYTE_CG : Cougar-prom-1.0.8 : Thu Jul 31 17:59:23 2008
> 
>   NFP_FP : EverON-4.0.2.9CG : Fri Nov  6 10:11:48 2009
> 
> FP1
> 
>   PROM_SIBYTE_CG : Cougar-prom-1.0.8 : Thu Jul 31 17:59:23 2008
> 
>   NFP_FP : EverON-4.0.2.9CG : Fri Nov  6 10:11:48 2009
> 
> FP2
> 
>   PROM_SIBYTE_CG : Cougar-prom-1.0.8 : Thu Jul 31 17:59:23 2008
> 
>   NFP_FP : EverON-4.0.2.9CG : Fri Nov  6 10:11:48 2009
> 
> FP3
> 
>   PROM_SIBYTE_CG : Cougar-prom-1.0.8 : Thu Jul 31 17:59:23 2008
> 
>   NFP_FP : EverON-4.0.2.9CG : Fri Nov  6 10:11:48 2009
> 
> 
> 
> Power Supply 0 (sig=PSMI)
> 
>   Product Version:  00
> 
>   Serial Number:    007052
> 
> 
> 
> Power Supply 1 (sig=PSMI)
> 
>   Product Version:  00
> 
>   Serial Number:    007055
> 
> 
> 
> From: A, Khalid
> 
> Sent: Thursday, November 12, 2009 10:44 PM
> 
> To: Kwan, Ed
> 
> Subject: NAS web UI questions
> 
> 
> 
> Ed,
> 
> I am working on program to provide NAS web UI access from SANtricity.
> I am able to launch web from SANtricity application, but before
> adding a NAS node in SANtricity GUI, I wanted to make sure the IP
> address is of NAS gateway and it is running web UI services in order
> to connect it from browser, I believe it is running some sort of web
> services (web server or demon process).
> 
> 
> 
> Currently I am creating a SSLSocket at port 443 and then create a
> connection object, if this successfully creates object then I am
> calling it as NAS gateway, this requires SSL certificate while
> creating the con object, hence it should be packaged along with
> SANtricity binaries, or we need to download it from NAS gateway while
> installation or discovery of NAS gateways.
> 
> 
> 
> This may not be enough to call it as NAS gateway because, we can
> start NAS web UI web server on any desktop (please correct me if I am
> wrong), and when ever SANtricity discover NAS gateways, I think this
> desktop is also listed, which is not a NAS gateway.
> 
> 
> 
> 
> 
> So I am thinking about sending some GET request commands and expect
> some response from web server on MXA agent loaded and this is NAS
> box, so that I can query it and call it as NAS gateway , other way is
> to execute some basic NAS command, and check the response, not sure
> which command to use?
> 
> 
> 
> I wanted to understand the current NAS web UI behavior, because
> today, when I entered valid NAS gateway IP in IE, then on https
> protocol it loads initial authentication page. So I wanted to
> understand the current logic so that I can use it here.
> 
> 
> 
> -Khalid
