From: r.polanskis@uws.edu.au
Date: Fri Aug 05 2005 - 21:47:14 EDT
Hi managers,
I am succcessfully using N1SPS version 5.0 to provision server builds via
Jet. I can even get the SDS root mirror to work perfectly.
The only thing I am having problems with is the syntax to the
variables:
(N1SPS): profile_additional_disks_base_co
(Jet:): base_config_profile_additional_disks
The N1SPS variable is setup in the GUI one way and then transformed to the
Jet Template somehow.
The problem is, none of the docs match and when I input the vars in the
suggested fashion for the GUI, they do not come out correctly in Jet.
In fact the log for the GUI shows "bad substitution" for the
params I input:
/opt/jet/Utils/solaris/client_build[205]:
${base_config_profile_disk_c1t2d0s0:/opt/app:139264s0_mtpt}: bad substitution
/opt/jet/Utils/solaris/client_build[205]:
${base_config_profile_disk_c1t2d0s0:/opt/app:139264s0_size}: bad substitutionn
I am hoping someone who is familiar with N1SPS or Jet can give me a concrete
example of exactly what the vars and params should look like so I can
do it myself.
I have read what little documentation there is for Jet and the N1SPS
docs, but they contradict one another and are vague about certain details.
What I want to do is setup an "additional disk" with slice 0 as all the disk
(free) and S7 as a 32Mb sds State database. The disk is a Sun 143gb
type.
This is my only show stopper for a 100% automated build. Can anyone
who is familiar with the products please enlighten me?
Thanks
rachel
--
Rachel Polanskis Systems Admin, University of Western Sydney
ADD Werrington North Campus (+61 2) 9678 7291 <r.polanskis@uws.edu.au>
"I have found the solution, Doctor. Knife them in the neck" - Leela, Dr Who
"Who do you trust?" - John W Howard
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:31:15 EDT