Hi Dmitri,

SUMAVI link that you have is a real good one, I blindly followed it and then 
slowly things started to make more sense once it worked.
Also xCAT forum was very helpful. 

Thank you,
Amit

> -----Original Message-----
> From: dcheb...@gmu.edu [mailto:dcheb...@gmu.edu]
> Sent: Friday, February 10, 2012 10:15 AM
> To: vcl-user@incubator.apache.org; aaron_pee...@ncsu.edu
> Subject: Re: VCL and xCat
> 
> 
> Thank you, I hope we can make it work in our environment as well...
> 
> I keep searching and reading xCat docs - here is good one ->
> http://sumavi.com/books/xcat-administrators-guide.
> BTW, if you have any docs outside of xcat.org site, please share... At
> this point I'm looking for xCat overview docs, i.e. to understand the
> process.
> 
> Looks like xCat makes extensive use of DHCP server to manage nodes. Are
> you using different DHCPd servers for VCL VMs and xCat nodes, or just
> keep everything on one DHCP server and being careful with which MAC
> gets what?
> 
> Thanks again for your help...
> 
> On Feb 10, 2012, at 9:30 , Aaron Peeler wrote:
> 
> > Dmitri,
> >
> > Just to add to Amit, comments.
> >
> > We use xCAT extensively here at ncsu. From provisioning end-user
> > desktops and our hypervisors. xCAT very helpful when needed to
> install
> > a chassis full of blades with esxi.
> >
> > As your installing xCAT  You'll want to review
> > https://cwiki.apache.org/VCL/adding-support-for-partimage-and-
> partimag
> > e-ng-to-xcat-2x-unofficial.html We added in VCL support for partimage
> > - which is used to capture the disk images of end-user
> > environments/desktops for windows and linux.
> >
> > When your adding nodes to vcl through the manage computers tool, make
> > sure to choose "xCAT 2.x" .  If your doing windows bare-metal, you'll
> > also need to include sysprep and related mass storage drivers so it
> > can be reloaded successfully.
> >
> > For sysprep review step 8 on this page:
> >
> https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+Management+N
> > ode+Installation
> >
> > Hope this info helps,
> > Aaron
> >
> >
> > On Thu, Feb 9, 2012 at 4:03 PM, Dmitri Chebotarov <dcheb...@gmu.edu>
> wrote:
> >>
> >> Amit,
> >>
> >> Thanks a lot.
> >>
> >>
> >> On Feb 9, 2012, at 15:57 , Kumar, Amit H. wrote:
> >>
> >>> Hi Dmitri,
> >>>
> >>> You general idea is correct to my best understanding.
> >>>
> >>> "Install Path" in the Edit management Node will be the path for
> xCAT(bare metal) image repository. In addition when you configure the
> "Site" table in xCAT you will set the "installdir" to point to the
> location where you will store your images.
> >>>
> >>> We have IBM E Blade Chassis with HS22 blade servers.
> >>>
> >>> Best,
> >>> Amit
> >>>
> >>>> -----Original Message-----
> >>>> From: dcheb...@gmu.edu [mailto:dcheb...@gmu.edu]
> >>>> Sent: Thursday, February 09, 2012 3:44 PM
> >>>> To: vcl-user@incubator.apache.org
> >>>> Subject: Re: VCL and xCat
> >>>>
> >>>>
> >>>> Amit,
> >>>>
> >>>> I'm trying to get general idea about xCat/VCL : so, basically xCat
> >>>> needs to be installed and configured on VCL Mgm node(s) before it
> >>>> can be used with VCL, and I should be able to successfully
> >>>> provision xCat nodes/clients with different images. Once xCat is
> >>>> working then I can add bare-metal computers - blade with xCat 2.x
> >>>> engine. Does it sound right?
> >>>>
> >>>> How do you tell VCL where to get image files for xCat nodes - is
> it
> >>>> 'Install Path' setting under Management Nodes -> Edit management
> >>>> node information?
> >>>>
> >>>> What kind of hardware do you have for xCat nodes? Are those IBM
> >>>> blade servers or/and PCs?
> >>>>
> >>>>
> >>>> Thanks.
> >>>>
> >>>>
> >>>> On Feb 9, 2012, at 15:16 , Kumar, Amit H. wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> We do not need an additional/dedicated server to do both xCAT and
> >>>>> VCL
> >>>> together, your management node can serve as your xCAT server.
> >>>>>
> >>>>> I would recommend getting xCAT to work by itself before using VCL
> >>>>> to
> >>>> manage your images and guest OS.
> >>>>>
> >>>>> This has worked well for us so far.
> >>>>>
> >>>>> :Amit
> >>>>>
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: dcheb...@gmu.edu [mailto:dcheb...@gmu.edu]
> >>>>>> Sent: Thursday, February 09, 2012 3:03 PM
> >>>>>> To: vcl-user@incubator.apache.org
> >>>>>> Subject: VCL and xCat
> >>>>>>
> >>>>>> Hi All
> >>>>>>
> >>>>>> Anyone is using xCat with VCL?
> >>>>>>
> >>>>>> I have generic question about xCat and VCL - where do I start?
> >>>>>> Do I need working xCat environment before I can add it to VCL?
> >>>>>> Does xCat need dedicated server? Or does it run on the VCL
> >>>> management
> >>>>>> node?
> >>>>>> Are there any special hardware requirements for xCat "clients"?
> >>>>>>
> >>>>>>
> >>>>>> Thank you.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Thank you.
> >>>>
> >>>> -----------------
> >>>> Dmitri Chebotarov
> >>>> dcheb...@gmu.edu
> >>>> 703-993-6175
> >>>> -----------------
> >>>>
> >>>
> >>
> >>
> >>
> >>
> >> Thank you.
> >>
> >> -----------------
> >> Dmitri Chebotarov
> >> dcheb...@gmu.edu
> >> 703-993-6175
> >> -----------------
> >>
> >>
> >>
> >> -----BEGIN PGP SIGNATURE-----
> >>
> >> iQEcBAEBAgAGBQJPNDStAAoJEMRKpymufl8aAxkH/iCGHjBRUMR85l4+D3clzzem
> >> eb4+RtsjvqfnJO7IjjF3Ajs73labFWvoEgpJrbFous2v6ou/gNsUgB82hWicqNTm
> >> 5+ZKkdncM2qWl2QI1ED6kvZt0OHmG/cUbRk0XRlPSjf99dIYgjqPZBL4xFNje62X
> >> xzNNPCEC7S5lixouyUcFPh7KhVR+11zvZsliV19CYH6HqXLpSphRt/gN5HIK77gD
> >> xNpfymdAPf2iJ1Dur5MNngnJIYTgdNgYq8pTvmrxPNEixumYsTU1UQzYFbijpctI
> >> yL8gUhP2kX2Yd45mVGzZxmJXDrOkg0rLxmIxVrrmGH2/iLSHpSFE+8mY0kqbTmA=
> >> =86fD
> >> -----END PGP SIGNATURE-----
> >>
> >
> >
> >
> > --
> > Aaron Peeler
> > Program Manager
> > Virtual Computing Lab
> > NC State University
> >
> > All electronic mail messages in connection with State business which
> > are sent to or received by this account are subject to the NC Public
> > Records Law and may be disclosed to third parties.
> 
> 
> 
> 
> Thank you.
> 
> -----------------
> Dmitri Chebotarov
> dcheb...@gmu.edu
> 703-993-6175
> -----------------
> 

Reply via email to