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:<Edward.Xiao@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	A11ADD3877B3C543B65BE8E196B7BDFFB8D84088@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 3 Dec 2009 11:51:26 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Xiao, Edward" <Edward.Xiao@lsi.com>
Subject: Re: Service VM packages.
Message-ID: <20091203115126.006b83e5@ripper.onstor.net>
In-Reply-To: <A11ADD3877B3C543B65BE8E196B7BDFFB8D84088@cosmail02.lsi.com>
References: <20091202163645.071ea907@ripper.onstor.net>
	<A11ADD3877B3C543B65BE8E196B7BDFFB8D84088@cosmail02.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

Howdy,

I don't know what a horus server is.  Is it just an NFS server, or ?

On Wed, 2 Dec 2009 17:54:14 -0700 "Xiao, Edward" <Edward.Xiao@lsi.com>
wrote:

> Hi Andrew,
>   I was assuming you have access account at horus server at Milpitas
> or t1000 server at Boulder.  Also, you need to have PikesPeak
> controller to launch this domU. Anyway, the IP of these servers are:
> 147.145.212.21 (t1000 server) 147.145.244.151 (horus server).
> 
> If you don't have access to a running PikesPeak controller, I have a
> running PikesPeak controller at 172.23.221.112, login as root,
> password infiniti.
> 
> 
> -Edward
> 
> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@lsi.com]
> Sent: Wednesday, December 02, 2009 4:37 PM
> To: Xiao, Edward
> Subject: Re: Service VM packages.
> 
> On Wed, 2 Dec 2009 17:27:26 -0700 "Xiao, Edward" <Edward.Xiao@lsi.com>
> wrote:
> 
> > Hi All,
> >     Roopesh and I created a 1 GB Debian DomU image for PikesPeak FBA
> > engineering use.  This 64 bits Debian Lenny domU image has most of
> > the Debian packages use in current NAS gateway product. I also
> > patched the image with Linux kernel 2.6.31.4 and Eth0 DHCP access.
> > Location of the domU image is on Milpita's horus server,
>                                              ^^^^^
> I'll bite, what does that mean?
> 
> > under /home/exiao/debian-1GB.tar.  The tar file contains the hidePCI
> > script, vm image, and vm configuration file to launch the domU.
> >
> > Filesystem           1K-blocks      Used Available Use% Mounted on
> > /dev/sda1              1004024    549068    403952  58% /
> > tmpfs                   508000         0    508000   0% /lib/init/rw
> > udev                     10240       564      9676   6% /dev
> > tmpfs                   508000         0    508000   0% /dev/shm
> > debian:~#
> > debian:~# uname -a
> > Linux debian 2.6.31.4-custom #1 SMP Mon Nov 9 07:34:10 PST 2009
> > x86_64 GNU/Linux
> >
> > -Edward
> >
> > -----Original Message-----
> > From: Xiao, Edward
> > Sent: Tuesday, November 10, 2009 1:52 PM
> > To: Scheer, Larry; George, Elizabeth; Dailey, Aaron; Sangapu,
> > Satish; Padmanabhan, Seetharaman; S G, Roopesh; Jolad, Amarnath Cc:
> > H N, Bhuvaneshwar; Banerjee, Arindam; Nichols, Chuck; Vandever,
> > Chris; Sharp, Andy; Ariyamannil, Jobi; Stark, Brian Subject: RE:
> > Service VM packages.
> >
> > Larry,
> >   Thanks for the detail break down on various NAS components size.
> > 544 MB is good workable minimum.  I already have a 629 MB Debian 5.0
> > based domU(64 bits x86)running on a Pikespeak controller. This domU
> > is a bare minimum installation with working serial port console and
> > DHCP on eth0. The Linux kernel version I patched it with is
> > 2.6.31.4.  Location of the domU is at horus:/home/exiao/debianU.tar
> >
> > This domU also has 66MB of virtual memory swap space, which we might
> > remove latter as Amarnath suggested.  Feel free to use it to
> > experiment with Debian packages installation.  Let's see if we break
> > the 544 MB barrier.
> >
> > -Edward
> >
> > ***
> >
> > debian:/etc/udev/rules.d# fdisk -l
> >
> > Disk /dev/hda: 629 MB, 629146624 bytes
> > 255 heads, 63 sectors/track, 76 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > Disk identifier: 0x000e6814
> >
> >    Device Boot      Start         End      Blocks   Id  System
> > /dev/hda1   *           1          65      522081   83  Linux
> > /dev/hda2              66          76       88357+   5  Extended
> > /dev/hda5              66          76       88326   82  Linux swap /
> > Solaris debian:/etc/udev/rules.d# uname -a
> > Linux debian 2.6.31.4-custom #1 SMP Mon Nov 9 07:34:10 PST 2009
> > x86_64 GNU/Linux debian:/etc/udev/rules.d# df -k
> > Filesystem           1K-blocks      Used Available Use% Mounted on
> > /dev/hda1               505604    399158     80342  84% /
> > tmpfs                   508068         0    508068   0% /lib/init/rw
> > udev                     10240       564      9676   6% /dev
> > tmpfs                   508068         0    508068   0% /dev/shm
> >
> > -----Original Message-----
> > From: Scheer, Larry
> > Sent: Tuesday, November 10, 2009 12:31 PM
> > To: Xiao, Edward; George, Elizabeth; Dailey, Aaron; Sangapu, Satish;
> > Padmanabhan, Seetharaman; S G, Roopesh; Jolad, Amarnath Cc: H N,
> > Bhuvaneshwar; Banerjee, Arindam; Nichols, Chuck; Vandever, Chris;
> > Sharp, Andy; Ariyamannil, Jobi; Stark, Brian Subject: RE: Service VM
> > packages.
> >
> > The ONStor NAS gateway is currently using Debian Etch (4.0).
> > However, for Orion we will be using Debian stable which will be
> > some release of Debian 5. (Lenny, perhaps Sid, depending on release
> > time frame.)
> >
> > When you asked for image size I didn't know what you wanted was a
> > footprint of how much space our gateway currently can consume on its
> > compact flash.
> >
> > Your estimate of 420 MB is too low (340 MB plus 80 MB of log space.)
> > At a minimum we need a total of approximately 544 Mbytes.
> >
> > Here is how we arrive at that number:
> >
> > The kernel and root filesystem size is approximately 323 Mbytes
> > (developer's system ~ 300 Mbytes production system) This space is
> > fairly static and when we move to the Intel architecture  the size
> > will need to be recalculated.
> >
> > The cluster database and configuration files  need 52 Mbytes. The
> > cluster database is specified to be a maximum of 24 Mbytes. There
> > needs to be space in its partition to keep a backup copy of the
> > database and we allocate an additional 4 Mbytes for configuration
> > files stored with the cluster database. (24*2 + 4)
> >
> > The var partition needs to remain at the current 169 Mbytes. This
> > partition stores logs, crash dumps, daemon core files along with a
> > slew of miscellaneous files such as mail.
> >
> > This brings us to a total of  544 Mbytes.  ( 323+52+169)
> >
> > The output of the df command was run on a lab system with an
> > optimized root file system. This gateway had a cluster database
> > around 8 Mbytes.
> >
> > Larry
> >
> > ________________________________________
> > From: Xiao, Edward
> > Sent: Monday, November 09, 2009 5:20 PM
> > To: Scheer, Larry; George, Elizabeth; Dailey, Aaron; Sangapu,
> > Satish; Padmanabhan, Seetharaman; S G, Roopesh; Jolad, Amarnath Cc:
> > H N, Bhuvaneshwar; Banerjee, Arindam; Nichols, Chuck; Vandever,
> > Chris; Sharp, Andy; Ariyamannil, Jobi; Stark, Brian Subject: RE:
> > Service VM packages.
> >
> > Larry,
> >    Do you know what version of Debian distro is used on the NAS
> > gateway?  So the NAS application takes about 340MB plus 80MB of logs
> > files.  The minimum is 420MB. Aaron mentioned that Pikespeak's x86
> > binary might have different file size.  So, we need to do some
> > installation experiment on x86 platform to get a more accurate
> > number. -Edward
> >
> > -----Original Message-----
> > From: Scheer, Larry
> > Sent: Monday, November 09, 2009 4:56 PM
> > To: Xiao, Edward; George, Elizabeth; Dailey, Aaron; Sangapu, Satish;
> > Padmanabhan, Seetharaman; S G, Roopesh; Jolad, Amarnath Cc: H N,
> > Bhuvaneshwar; Banerjee, Arindam; Nichols, Chuck; Vandever, Chris;
> > Sharp, Andy; Ariyamannil, Jobi; Stark, Brian Subject: RE: Service VM
> > packages.
> >
> > Edward,
> >    Here is the information  provided to the Serviceability group
> > last group last week.
> >
> > Total size of CF today is 1GB.  Here's the breakdown:
> >
> > g5r8:/# df -k
> >
> > Filesystem           1K-blocks      Used Available Use% Mounted on
> >
> > /dev/sdb1               701408    300256    401152  43% /
> >
> > tmpfs                   233156         0    233156   0% /lib/init/rw
> >
> > udev                     10240        44     10196   1% /dev
> >
> > tmpfs                   233156         0    233156   0% /dev/shm
> >
> > /dev/sdb3               168871     31581    137290  19% /var
> >
> > /dev/sdb4               109327      8504    100823   8% /onstor/conf
> >
> > tmpfs                    12288        24     12264   1% /tmp
> >
> >
> > tmpfs is virtual memory and is not part of the CF...
> >
> > The ONStor unique portion of the file system (outside of logs and
> > miscellaneous files) are found in the follow two directories of the
> > root file system. I included the totals below.
> >
> > g6r8:/var/log/onstor# du -sk /boot
> > 28496   /boot
> > g6r8:/var/log/onstor# du -sk /onstor
> > 60454   /onstor
> >
> > Total: 88960 Kbytes
> >
> > ________________________________________
> > From: Xiao, Edward
> > Sent: Monday, November 09, 2009 2:42 PM
> > To: Scheer, Larry; George, Elizabeth; Dailey, Aaron; Sangapu,
> > Satish; Padmanabhan, Seetharaman; S G, Roopesh; Jolad, Amarnath Cc:
> > H N, Bhuvaneshwar; Banerjee, Arindam; Nichols, Chuck; Vandever,
> > Chris; Sharp, Andy; Ariyamannil, Jobi Subject: RE: Service VM
> > packages.
> >
> > Larry,
> >   It is good to know that 1 Gig flash can handle all the application
> > need in existing NAS gateway box.  I am assuming the NAS gateway is
> > also Debian 5.0 based. So, ff you go to your NAS gateway Linux
> > console, typing "df -l" should show the number of blocks and the use
> > percentage.  That should give the ballpark figure for the flash
> > storage for all the application packages.  I think the sizes of
> > various log files used are design issues that can be fine turned at
> > later stages.
> >
> > -Edward
> >
> > -----Original Message-----
> > From: Scheer, Larry
> > Sent: Monday, November 09, 2009 2:12 PM
> > To: Xiao, Edward; George, Elizabeth; Dailey, Aaron; Sangapu, Satish;
> > Padmanabhan, Seetharaman; S G, Roopesh; Jolad, Amarnath Cc: H N,
> > Bhuvaneshwar; Banerjee, Arindam; Nichols, Chuck; Vandever, Chris;
> > Sharp, Andy; Ariyamannil, Jobi Subject: RE: Service VM packages.
> >
> > Edward,
> >    I am not quite sure how to answer your question. Total image size
> > of what? I am not sure how much to include or exclude from that
> > number. With the exception of embedded processor core files and
> > system statistics (data gathered for EMRS) all of our storage needs
> > are met by a 1Gbyte compact flash.
> > ________________________________________ From: Xiao, Edward Sent:
> > Monday, November 09, 2009 1:08 PM To: Scheer, Larry; George,
> > Elizabeth; Dailey, Aaron; Sangapu, Satish; Padmanabhan, Seetharaman;
> > S G, Roopesh; Jolad, Amarnath Cc: H N, Bhuvaneshwar; Banerjee,
> > Arindam; Nichols, Chuck; Vandever, Chris; Sharp, Andy Subject: RE:
> > Service VM packages.
> >
> > Larry,
> >    Thanks for the list. Do you have total image size of our NAS
> > gateway today? -Edward
> >
> > -----Original Message-----
> > From: Scheer, Larry
> > Sent: Monday, November 09, 2009 12:32 PM
> > To: George, Elizabeth; Dailey, Aaron; Sangapu, Satish; Padmanabhan,
> > Seetharaman; S G, Roopesh; Jolad, Amarnath; Xiao, Edward Cc: H N,
> > Bhuvaneshwar; Banerjee, Arindam; Nichols, Chuck; Vandever, Chris;
> > Sharp, Andy Subject: RE: Service VM packages.
> >
> > Attached is a list of all the Debian packages we install on our NAS
> > gateway today (production release not development)
> >
> > ________________________________________
> > From: George, Elizabeth
> > Sent: Monday, November 09, 2009 12:15 PM
> > To: Dailey, Aaron; Sangapu, Satish; Padmanabhan, Seetharaman; S G,
> > Roopesh; Jolad, Amarnath; Xiao, Edward Cc: H N, Bhuvaneshwar;
> > Banerjee, Arindam; Nichols, Chuck; Vandever, Chris; Sharp, Andy;
> > Scheer, Larry Subject: Service VM packages.
> >
> > Good idea Aaron.  CCing  Chris, Andy and Larry, so we can get the
> > updated list of packages they would need, now that the PAS is
> > somewhat finalized. (Changed the Subject line to be more
> > appropriate). Please see original list further down in the email.
> > -Liz
> >
> > ________________________________
> > From: Dailey, Aaron
> > Sent: Monday, November 09, 2009 11:54 AM
> > To: George, Elizabeth; Sangapu, Satish; Padmanabhan, Seetharaman; S
> > G, Roopesh; Jolad, Amarnath; Xiao, Edward Cc: H N, Bhuvaneshwar;
> > Banerjee, Arindam; Nichols, Chuck Subject: RE: Debian DomU Size
> > reduction
> >
> > We need to be able to authenticate server certificates, but this
> > doesn't use LDAP. But, we should add socat to the list of required
> > software. It's a package that lets you send data across the TCP/IP
> > via CLI. It's used by EMRS. It looks like socat is dependent on
> > openssl libraries, and this combination would authenticate
> > certificates.
> >
> > We need DNS to resolve the EMRS server name, mail server, http
> > proxies, etc. Satish - I think we want DOM0 to have a DNS resolver,
> > which would need to be configured if we're not running DHCP (if
> > we're running DHCP, we'd get the necessary information). Each VM
> > would use DOM0 as its resolver.
> >
> > Also, the Onstor code uses exim as its mail transfer agent, so this
> > is another package to add to this list. Also, I'm assuming core
> > Linux commands such as ps, cat, sh, sed, grep, cron, gzip etc are
> > available, and we don't need to explicitly list them.
> >
> > It would be good to ask someone from Onstor (probably Larry Scheer)
> > for an explicit list of packages they depend upon, at least for code
> > that will be in service vm.
> >
> > Aaron
> >
> > From: George, Elizabeth
> > Sent: Monday, November 09, 2009 11:01 AM
> > To: Sangapu, Satish; Padmanabhan, Seetharaman; S G, Roopesh; Jolad,
> > Amarnath; Xiao, Edward Cc: H N, Bhuvaneshwar; Banerjee, Arindam;
> > Nichols, Chuck; Dailey, Aaron Subject: RE: Debian DomU Size
> > reduction
> >
> > Chuck/Aaron  can correct me if I'm wrong. I believe the LDAP/ or
> > other authentication is probably going to used to be used by EMRS
> > (Event Reporting and Monitoring Service) which is part of the Phone
> > Home feature, being specified by Aaron,   to look up encryption
> > certificates for authorizing the controller to send info to the
> > server configured to receive files containing the CBS, and current
> > NAS EMRS files. -Liz
> >
> > ________________________________
> > From: Sangapu, Satish
> > Sent: Monday, November 09, 2009 10:09 AM
> > To: George, Elizabeth; Padmanabhan, Seetharaman; S G, Roopesh;
> > Jolad, Amarnath; Xiao, Edward Cc: H N, Bhuvaneshwar; Banerjee,
> > Arindam; Nichols, Chuck Subject: Re: Debian DomU Size reduction
> >
> >
> > Can someone tell me the use cases or functions for dns or ldap in
> > service vm?
> >
> > Thanks
> >
> > ________________________________
> > From: George, Elizabeth
> > To: Padmanabhan, Seetharaman; S G, Roopesh; Jolad, Amarnath; Xiao,
> > Edward Cc: H N, Bhuvaneshwar; Sangapu, Satish; Banerjee, Arindam;
> > Nichols, Chuck Sent: Mon Nov 09 10:51:31 2009
> > Subject: RE: Debian DomU Size reduction
> > Hi,
> > I'm writing the Service VM AAD, since centralized logging lives
> > there. So far the list of packages required for Service Vm as
> > collected by Chuck are as follows. Note however FBA VM or the NAS VM
> > will be moving their eventd, UBIQ cluster DB, The new MXA component
> > and the webserver and CLi mapping component, along with the their
> > Zebra CLi also to Service VM.  So here are one set of packages we
> > need for some of this. I did send this to Edward. -Liz
> >
> > From our email discussions so far, it looks like we believe we need
> > support for the following packages in Linux: -SFCB
> > -HTTP server
> > -libcurl
> > -openSLP
> > -openWSMan
> > -openSSL
> > -rssh
> > -lvm
> > -opie
> > -openssh-server
> > -cramfs
> > -DNS
> > -NTP
> > -LDAP, Active Directory, or NIS client (depends on authentication
> > model) -LinuxHA cluster management
> >
> >
> >
> > ________________________________
> > From: Padmanabhan, Seetharaman
> > Sent: Monday, November 09, 2009 9:43 AM
> > To: S G, Roopesh; Jolad, Amarnath; Xiao, Edward
> > Cc: H N, Bhuvaneshwar; Sangapu, Satish; Banerjee, Arindam; George,
> > Elizabeth Subject: RE: Debian DomU Size reduction
> >
> >
> > This is good news guys and looks like we have a reasonable minimum
> > at this moment...  Can one of you please send the Packages included
> > in this image?
> >
> > Arindam / Liz and Satish:
> >                 We need a master package list for Service VM and the
> > FBA VM...  I am assuming one of your AADs cover this item.
> >
> > Paddu Padmanabhan
> >
> >
> > From: S G, Roopesh
> > Sent: Monday, November 09, 2009 5:06 AM
> > To: S G, Roopesh; Jolad, Amarnath; Xiao, Edward
> > Cc: Padmanabhan, Seetharaman; H N, Bhuvaneshwar
> > Subject: RE: Debian DomU Size reduction
> >
> > Was able to create 350MB DomU image. I could also install 2.6.31
> > kernel after which the free space was around 27MB.
> >
> > -Roopesh
> >
> > ________________________________
> > From: S G, Roopesh
> > Sent: Monday, November 09, 2009 6:02 PM
> > To: Jolad, Amarnath; Xiao, Edward
> > Cc: Padmanabhan, Seetharaman; H N, Bhuvaneshwar
> > Subject: RE: Debian DomU Size reduction
> >
> >
> >
> > The 450MB DomU image has Linux Kernel 2.6.31 (apart from debian
> > default kernel 2.6.26 [we can save ~20MB by uninstalling this]) and
> > free space of 120 MB. I think we can further reduce the size by
> > another 100MB, I shall try that tomorrow. Also, note that the linux
> > kernel 2.6.31 installed is not optimized during compilation as the
> > config file during compilation by default enables all the kernel
> > modules most of which are not required for us (ex: IRDA, Bluetooth,
> > all network drivers etc).
> >
> > -Roopesh
> >
> > ________________________________
> > From: Jolad, Amarnath
> > Sent: Monday, November 09, 2009 5:24 PM
> > To: Xiao, Edward
> > Cc: S G, Roopesh; Padmanabhan, Seetharaman; H N, Bhuvaneshwar
> > Subject: Debian DomU Size reduction
> >
> > Edward,
> >          We were able to create a Debian DomU image of size 450MB.
> > We are yet to fully ascertain the capabilities of such installation
> > though.
> >
> > Few observations:
> >
> > 1.   450MB is just about the minimum disk space required for Debian
> > installation.
> >
> > a.   This will install "minimum" default packages.
> >
> > b.   We disabled "swap space" in this (this is optional).
> >
> > c.    This will install only "essential" and few optional packages.
> > No standard packages are installed.
> >
> > 2.   With this we see about 40 MB is free disc space, I would image
> > that this could be little less for FBA packages.
> >
> > 3.   Though this is the minimum disk space required for Debian
> > installation, this may not be all that useful.
> >
> > We need following questions answered to determine how much space is
> > required over and above 450MB for the DomU to be of practical value.
> >
> > 1.   What are the package dependencies of FBA or Ser VM? That is,
> > what are the dependent packages required other than FBA itself.
> >
> > 2.   How much free disc space do FBA or S.VM app need? I would
> > imagine that FBA or SerVM may maintain metadata/configuration files
> > on local disc.
> >
> > 3.   Is it necessary to have swap space? By default, Debian is
> > creating around 92MB of swap space, I think this is as good as
> > having none at all. I think the thumb-rule for swap space is
> > determined by the amount of RAM the system has been booted with.
> > The recommended size for swap space is twice the size of RAM, 92 MB
> > is way too low and we may as well do without it. Need to check with
> > FBA folks though.
> >
> > 4.   What are the debugging capabilities required?
> >
> > 5.   What are the free disc space requirements for upgrade of
> > packages?
> >
> > -AJ
> >
> >
