Xunni:
Since you use the on-nightly, you will need to modify your xml as follow
to unconstrain the osnet-incorporation in order for the build to work.
Please look at the attachment about using facet to do this for DC
builds. I will suggest you also upgrade your DC build machine following
Niall Power flag date due to the grub2/uefi changes that comes in.
On 04/18/12 02:02 AM, xunni wrote:
Hi, Mary:
Recently the nightly result has changed:
it was: packages/i386/nightly-nd/repo.redist repo.extra
now: packages/i386/nightly-nd/osnet osnet-internal
so according to this change, is there any change to our
dc_text_x86.xml?
I build it with the changed path but got failed, is there other
thing that i should change?
the log is in the attachment.
Thanks,
Xun
Xun Ni:
I was away and just got back.
You can use DC to include driver/storage/scu in the dc_text_sparc.xml
and dc_text_x86.xml
i.e:
You need to add it to here:
<software_data action="install">
<name>pkg:/entire@latest</name>
<name>pkg:/group/system/solaris-large-server</name>
<name>pkg:/system/install/text-install</name>
<name>pkg:/driver/storage/lsc</name>
<name>pkg:/system/install/media/internal</name>
</software_data>
On 03/31/12 12:05 AM, xunni wrote:
Hi, Mary:
currently we have a new driver 'lsc' driver/storage/lsc, it
doesn't exist in the 'server_install' group. but we want to test the
installation. is there any way to use the TI to create the DVD to
perform the test?
Thanks,
Xun
Xun Ni:
If you look at http://ipkg.us.oracle.com and seach for
driver/storage/scu, it is in:
auto_install
slim_install
server_install
redistributable
So AI should work.
http://ipkg.us.oracle.com/solaris11/dev/en/search.shtml?token=driver%2Fstorage%2Fscu+&action=Search
On 05/25/11 08:09 PM, xun.ni wrote:
root@solaris:~# pkg info scu
Name: driver/storage/scu
Summary: Intel SCU SAS/SATA HBA driver
Description: Intel Storage Controller Unit (SCU) SAS/SATA HBA
Driver
Category: Drivers/Storage
State: Installed
Publisher: on-nightly
Version: 0.5.11
Build Release: 5.11
Branch: 0.166
Packaging Date: Wed May 25 06:13:57 2011
Size: 884.76 kB
FMRI:
pkg://on-nightly/driver/storage/[email protected],5.11-0.166:20110525T061357Z
is this command? but i still can't find which group pkgs
On 05/26/11 11:02, Mary Ding wrote:
Xun Ni:
You can bring up the pkg repo and search to see where scu is in.
On 05/25/11 07:58 PM, xun.ni wrote:
is there a way to see which group packages my driver in? my
driver name is scu
Thanks,
Xun
On 05/26/11 10:20, Mary Ding wrote:
Xun ni:
I had included Karen on this and she is more famillar with
DC. If this is with TI, is your driver included in the
server_install group packages. If it does, then the install
should work.
You can easily confirm this by booting the TI image and check
it out.
On 05/25/11 07:13 PM, xun.ni wrote:
Hi, Marry:
Thanks for your help, I need another confirm that if i have
a new controller, and an old driver already in s11
but the driver don't support installation on the controller.
After we modify the code , it supports the installation,
And i use the DC to modify the publisher to my workspace,
build an ISO, is this ISO support the installation.
You know that if the driver support installation, the driver
should be updated in both the repo and the ramdisk(miniroot),
does the DC update both the repo and the ramdisk(miniroot)?
Thanks,
Xun
On 05/19/11 02:25, Mary Ding wrote:
Xun Ni:
You cannot use a dc xml to do AI install.
If you want to test your binaries, I will suggest you do a TI
build. You make a copy of the dc_text_x86.xml, modify the
repo just like you did for the AI build. Remove the entire
and do the TI build.
Then you can boot the iso or usb and test TI install and it
is easier to test your bits.
On 05/18/11 04:30 AM, xun.ni wrote:
Hi, Marry
is it ok to remove the entire? I build the ISO successfully.
I create the DVD and boot from dvd, choose the custom boot
menu, but it seems that the installation failed due to
can't find manifest?
should i choose the custom menu, other menu seems ok but i
am not sure, the following is the log:
===============================================
Hostname: solaris3, 2011, Oracle and/or its affiliates. All
rights reserved.
Remounting root read/write
Probing for device nodes ...
Preparing image for use
Done mounting image
Configuring devices.
WARNING: No randomness provider enabled for /dev/random. Use
cryptoadm(1M) to enable a provider.
Enter the URL for the AI manifest [HTTP, default]:
Obtaining manifest from the following location:
/net/coloraxe.cn.oracle.com/builds/xunni/dc_ai_x86.xml
/net/coloraxe.cn.oracle.com/builds/xunni/dc_ai_x86.xml:
Scheme missing.
solaris console login:
Automated Installation started
The progress of the Automated Installation can be followed
by viewing
the logfile at /tmp/install_log
solaris console login: Invalid or incompatible manifest
provided
Please refer to the
/var/svc/log/application-auto-installer:default.log file
for details
Mar 8 23:33:21 solaris svc.startd[8]:
application/auto-installer:default failed fatally:
transitioned to maintenance (see 'svcs -xv' for details)
root@solaris:~# cat
/var/svc/log/application-auto-installer:default.log
[ Mar 8 23:33:15 Executing start method
("/lib/svc/method/auto-installer"). ]
Automated Installation started
The progress of the Automated Installation can be followed
by viewing
the logfile at /tmp/install_log
Error instantiating manifest tree:
Error creating in-memory copy of Manifest data.
Error parsing xml file /tmp/ai.xml
Invalid or incompatible manifest provided
Please refer to the
/var/svc/log/application-auto-installer:default.log file
for details
[ Mar 8 23:33:21 Method "start" exited with status 95. ]
Thanks,
Xun
On 05/18/11 11:27, Mary Ding wrote:
This will not work:
1. You will need to add the on-extra nightly before solaris
<publisher name="on-nightly">
<origin name="file:///root/nightly/repo.redist"/>
</publisher>
<publisher name="solaris">
<origin name="http://ipkg.us.oracle.com/solaris11/dev"/>
</publisher>
2. You will need to remove entire from the xml in order for
the build to work.
On 05/17/11 08:24 PM, xun.ni wrote:
Hi, Marry:
I set my repo before the 'solaris' publisher, see
<publisher name="on-nightly">
<origin name="file:///root/nightly/repo.redist"/>
</publisher>
<publisher name="solaris">
<origin name="http://ipkg.us.oracle.com/solaris11/dev"/>
</publisher>
but the log show failed:
10:59:46 No matching version of entire can be installed:
Reject:
pkg://solaris/[email protected],5.11-0.151:20101027T142141Z
Reason: All versions matching 'require' dependency
pkg:/consolidation/osnet/osnet-incorporation are rejected
Reject:
pkg://on-nightly/consolidation/osnet/[email protected],5.11-0.166:20110517T104016Z
Reason: Excluded by proposed incorporation 'entire'
Reject:
pkg://solaris/consolidation/osnet/[email protected],5.11-0.151:20101026T180317Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.151.0.1:20101104T230646Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.152:20101112T165745Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.153:20101118T212652Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.154:20101203T190550Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.155:20101220T213006Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.156:20101230T214548Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.157:20110114T201511Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.158:20110127T191809Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.159:20110214T040231Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.160:20110226T064127Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.161:20110315T051502Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.162:20110325T170554Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.163:20110410T031009Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.164:20110422T153115Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.165:20110510T013316Z
On 05/18/11 05:11, Mary Ding wrote:
Xun Ni:
You did not do this correctly.
I will suggest you use the following repo instead of
using a custom script to replace the scu package:
For your local repo where you had your package, you need
to list that first before the solaris repo:
e.g:
When I test my install nightly repo, this is what I did:
<source>
<publisher name="install-nightly">
<origin
name="file:/export/home/ding/sunstudio12u1patch/slim_source/packages/i386/nightly-nd/repo.redist"/>
</publisher>
<publisher name="solaris">
<origin name="http://ipkg.us.oracle.com/solaris11/dev"/>
On 05/15/11 11:32 PM, xun.ni wrote:
Hi, Dave:
I need to replace my package scu(driver/storage/scu)
with the lastest using the DC, and currently my
dc_ai_x86.xml and the custom script is in the
attachment, The key error point is "Unable to install
pkg://solaris/scu", my step is that i create a local
IPS server with "/usr/lib/pkg.depotd -d
/root/nightly/repo.redist/ -p 10000" and it contain the
lastest package, and then i run "/usr/bin/distro_const
build -v /root/dc_ai_x86.xml". I set a custom script to
replace the package with my own but it failed, can you
help me to figure out why it fail?
The output error is
2011-05-16 13:17:29,012
InstallationLogger.custom-script INFO ===
Executing Custom Script Checkpoint ===
2011-05-16 13:17:29,012
InstallationLogger.custom-script INFO Custom
Script provided is: '/export/home/scu_script.sh
{PKG_IMAGE_PATH} scu'
2011-05-16 13:17:29,012
InstallationLogger.custom-script INFO Custom
Script to run is: '/export/home/scu_script.sh
/export/home/dc/ai/build_data/pkg_image scu'
2011-05-16 13:17:29,013
InstallationLogger.custom-script DEBUG Executing:
/export/home/scu_script.sh
/export/home/dc/ai/build_data/pkg_image scu
2011-05-16 13:17:29,712
InstallationLogger.custom-script DEBUG /usr/bin/pkg
-R /export/home/dc/ai/build_data/pkg_image uninstall scu
2011-05-16 13:17:30,161
InstallationLogger.custom-script ERROR pkg: The
image cannot be modified as it is currently in use by
another package client: pkg on glasspaper.cn, pid 1257.
2011-05-16 13:17:30,202
InstallationLogger.custom-script ERROR
/export/home/scu_script.sh: Unable to install
pkg://solaris/scu
2011-05-16 13:17:30,254 InstallationLogger ERROR
Error occurred during execution of 'custom-script'
checkpoint.
Thanks,
Xun
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
Typically to test out a bugfix, we will need to do a DC build and remove the
entire from the dc xml. This had changed after the dependencies are now
faceted.
Briefly, all of the dependencies in entire on the various consolidation incorpor
ations are now faceted, so that you can loosen the chains on a particular consol
idation while keeping all the others locked together, rather than unconstraining
all consolidations as results when entire is removed.
These are the steps to use distribution-constructor to build images for testing
changes.
Step 1: Need to install distribution-constructor:
$ sudo pkg install distribution-constructor
Step 2: Make a copy of the xml that you want to test. In my example, I am
using dc_ai_x86.xml. You can do this for livecd, text- install and ai.
$ cp /usr/share/distro_const/dc_ai_x86.xml dc_ai_x86_on_facet.xml
$
Step 3: Make a copy of lang_facets.xml and modify as follow. The example is
to unconstrain the osnet-incorporation.
$ cp /usr/share/distro_const/lang_facets.xml lang_facets_on.xml
$
Then you edit lang_facets_on.xml and add the following line to unconstrain the
os-net consolidation.
<facet
set="false">facet.version-lock.consolidation/osnet/osnet-incorporation</facet>
These are the diff of the change:
osol-bldx{ding}203: diff lang_facets_on.xml
/usr/share/distro_const/lang_facets.xml
29,30d28
< <facet set="true">facet.locale.zh_TW</facet>
< <facet
set="false">facet.version-lock.consolidation/osnet/osnet-incorporation</facet>
osol-bldx{ding}204:
Step 4: Now you need to modify dc_ai_x86_on_facet.xml to point to the
on-nightly and on-extra repo first. You also need to change href
/usr/share/distro_const/lang_facets.xml to your own version.
These are the diffs of the changes:
osol-bldx{ding}208: diff /usr/share/distro_const/dc_ai_x86.xml
dc_ai_x86_on_facet.xml
3a4
>
83,84c84,85
< <zpool name="rpool" action="use_existing">
< <filesystem name="dc/ai" action="preserve"/>
---
> <zpool name="datapool" action="use_existing">
> <filesystem name="ding/dc/dc_ai_on" action="preserve"/>
103c104
< href="/usr/share/distro_const/lang_facets.xml"/>
---
> href="/datapool/ding/lang_facets_on.xml"/>
105a107,112
> <publisher name="on-nightly">
> <origin
> name="http://ipkg.us.oracle.com/internal/solaris11/on/nightly/"/>
> </publisher>
> <publisher name="on-extra">
> <origin
> name="http://ipkg.us.oracle.com/internal/solaris11/on/extra/"/>
> </publisher>
107c114
< <origin name="http://pkg.oracle.com/solaris/release"/>
---
> <origin name="http://ipkg.us.oracle.com/solaris11/dev"/>
osol-bldx{ding}209:
osol-bldx(ding}
Now you are ready to do the AI build. You can use the -p feature to pause the
DC build as follow:
sol-bldx{ding}209: sudo distro_const build -l dc_ai_x86_on_facet.xml
Checkpoint Resumable Description
---------- --------- -----------
transfer-ips-install Transfer pkg contents from IPS
set-ips-attributes Set post-install IPS attributes
pre-pkg-img-mod Pre package image modification
ba-init Boot Archive Initialization
ba-config Boot Archive Configuration
ba-arch Boot Archive Archival
boot-setup Setup boot menu
pkg-img-mod Pkg image area modification
create-iso ISO media creation
create-usb USB media creation
ai-publish-package Publish pkg(5) repository
osol-bldx{ding}210:
osol-bldx{ding}211:
sudo distro_const build -p set-ips-attributes dc_ai_x86_on_facet.xml
17:10:35 Build datasets successfully setup
17:10:35 Simple log:
/datapool/ding/dc/dc_ai_on/logs/simple-log.2012-01-04.17:10
17:10:35 Detail Log:
/datapool/ding/dc/dc_ai_on/logs/detail-log.2012-01-04.17:10
17:10:36 Creating IPS image
17:10:51 Installing packages from:
17:10:51 on-nightly
17:10:51 origin:
http://ipkg.us.oracle.com/internal/solaris11/on/nightly/
17:10:51 on-extra
17:10:51 origin:
http://ipkg.us.oracle.com/internal/solaris11/on/extra/
17:10:51 solaris
17:10:51 origin: http://ipkg.us.oracle.com/solaris11/dev/
DOWNLOAD PKGS FILES XFER (MB)
Completed 335/335 32381/32381 214.2/214.2
PHASE ACTIONS
Install Phase 49222/49222
PHASE ITEMS
Package State Update Phase 335/335
Image State Update Phase 2/2
osol-bldx{ding}212:
You can check and make sure you got the correct version of packages:
osol-bldx{ding}264: pkg -R /datapool/ding/dc/dc_ai_on/build_data/pkg_image list
| grep boot
system/boot-environment-utilities 0.5.11-0.175.1.0.0.6.18358 i--
system/boot/grub 0.97-0.175.1.0.0.6.18358 i--
system/boot/wanboot 0.5.11-0.175.1.0.0.6.18358 i--
system/library/boot-management 0.5.11-0.175.1.0.0.6.18358 i--
osol-bldx{ding}265:
Then you can resume the build with the -r option as follow:
osol-bldx{ding}266: sudo distro_const build -r set-ips-attributes
dc_ai_x86_on_facet.xml
18:07:51 Build datasets successfully setup
18:07:51 Simple log:
/datapool/ding/dc/dc_ai_on/logs/simple-log.2012-01-05.18:07
18:07:51 Detail Log:
/datapool/ding/dc/dc_ai_on/logs/detail-log.2012-01-05.18:07
18:07:58 Setting post-install publishers to:
18:07:58 solaris
18:07:58 origin: http://pkg.oracle.com/solaris/release/
18:08:22 === Executing Pre-Package Image Modification Checkpoint ===
18:08:22 Preloading SMF repository
18:08:56 Applying SMF profile: /etc/svc/profile/generic_limited_net.xml
18:08:59 Applying SMF profile: /usr/share/distro_const/profile/generic.xml
18:09:02 Applying SMF profile: /usr/share/distro_const/profile/ai.xml
18:09:03 Applying SMF profile: /etc/svc/profile/ns_files.xml
18:09:15 === Executing ba-init Checkpoint ===
18:09:16 Transferring files to
/datapool/ding/dc/dc_ai_on/build_data/boot_archive
18:09:19 Transferring files to
/datapool/ding/dc/dc_ai_on/build_data/boot_archive
18:09:28 === Executing Boot Archive Configuration Checkpoint ===
18:09:30 preparing boot archive
18:09:33 === Executing Boot Archive Archive Checkpoint ===
18:09:34 ramdisk will be 207 MB in size with an nbpi of 4096
18:09:34 Populating ramdisks
18:09:36 === Executing Archive Population Checkpoint ===
18:09:37 Transferring files to
/datapool/ding/dc/dc_ai_on/build_data/tmp/x86_lofimnt
18:15:58 === Executing Boot Loader Setup Checkpoint ===
18:15:58 Updating /datapool/ding/dc/dc_ai_on/build_data/pkg_image/.image_info
18:15:59 === Executing Pkg Image Modification Checkpoint ===
18:15:59 Removing sbin, kernel and lib from pkg_image area
18:15:59 Generating /usr file system archive
18:16:52 Compressing /usr file system archive using: lzma
18:22:27 Generating /mnt/misc file system archive
18:22:33 Compressing /mnt/misc file system archive using: lzma
18:24:10 === Executing Create ISO Checkpoint ==
18:24:10 Making final ISO image:
/datapool/ding/dc/dc_ai_on/media/Oracle_Solaris_AI_X86.iso
18:24:12 === Executing Create USB Checkpoint ===
18:24:12 Making final USB image:
/datapool/ding/dc/dc_ai_on/media/Oracle_Solaris_AI_X86.usb
18:24:33 === Executing AI Publish Packages Checkpoint ===
18:24:33 Creating repository
18:24:35 Publishing
pkg://ai-image/install-image/[email protected]
18:25:06
pkg://ai-image/install-image/[email protected],5.11-0.175.1.0.0.6.1524:20120106T022437Z
PUBLISHED
osol-bldx{ding}267:
Extra tips:
If you want to constrait your DC build to a certain build of os-net, you can do
this:
The M4 team had on-nightly and on-extra packages based on s11u1_03. They do
the following to do a custom DC AI build for their distrubutions.
They modify the lang_facets.xml and unlock the os-net incorporation.
Their on-nightly and on-extra repos are at the following location with s11u1_03:
<source>
<publisher name="on-nightly">
<origin name="file:///ws/m4-on/builds/S11/m4-t5-on11_010/packages/Jan3
/sparc/nightly-nd/repo.redist"/>
</publisher>
<!--
If additional publishers need to be set, they can be set here
-->
<publisher name="on-extra">
<origin name="file:///ws/m4-on/builds/S11/m4-t5-on11_010/packages/Jan3
/sparc/nightly-nd/repo.extra"/>
</publisher>
sher name="solaris">
<origin name="http://scapen-pkg-1.sfbay.sun.com/sol-11-u1-03";></origin
>
</publisher>
In order for DC to build with a certain build like s11u1_03, they change
entire@latest to the following:
<name>pkg:/[email protected]</name>
These are the diffs of the xml:
indiana-build-sp{ding}99: diff /usr/share/distro*/dc_ai_sparc.xml
m4-on11-10.ai.nd.entire.xml
29c29
< <filesystem name="dc/ai" action="preserve"/>
---
> <filesystem name="dc/ai/m4-on11-10.nd.entire_Jan4-2"
> action="preserve"/>
48c48
< href="/usr/share/distro_const/lang_facets.xml"/>
---
> href="/usr/share/distro_const/lang_facets_unconstrain_osnet.xml"/>
51,58c51,52
< <publisher name="solaris">
< <origin name="http://pkg.oracle.com/solaris/release"/>
< <!--
< If mirrors for this publisher need to be set, specify them here.
< -->
< <!-- Uncomment before using
< <mirror name="mirror.example.com"></mirror>
< -->
---
> <publisher name="on-nightly">
> <origin
> name="file:///ws/m4-on/builds/S11/m4-t5-on11_010/packages/Jan3/sparc/nightly-nd/repo.redist"/>
63c57,59
< <!-- Uncomment before using
---
> <publisher name="on-extra">
> <origin
> name="file:///ws/m4-on/builds/S11/m4-t5-on11_010/packages/Jan3/sparc/nightly-nd/repo.extra"/>
> </publisher>
65,67c61
< <origin name="http://example.com";></origin>
< <mirror name="mirror1.example.com"></mirror>
< <mirror name="mirror2.example.com"></mirror>
---
> <origin
> name="http://scapen-pkg-1.sfbay.sun.com/sol-11-u1-03";></origin>
69d62
< -->
82c75
< <name>pkg:/entire@latest</name>
---
> <name>pkg:/[email protected]</name>
indiana-build-sp{ding}100:
With the above xml, the M4 team is able to do DC build with their on-nightly
and on-extra packages based on s11u1_03 and the rest of the packages from the
solaris repo based on s11u1_03.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
