On 01/10/12 15:19, Paul de Nijs wrote:
Ethan,
Thanks, but it still doesn't make sense to me then, because the DTD
tells me that you can have multiple
<software type="IPS">
in the ai_manifest.
I thought that this was actually cool, because then you would know
where all the different <pkg><name ....>/<pkg> would come from, kind
of a distinction between the "main" repo and you "owncompany" repo,
see what I mean ?
You can achieve this by fully qualifying the package names as fmri's
that include the publisher from which you want to install it from. For
example:
<software type="IPS">
<source>
<publisher name="solaris">
<origin name="http://saeosol.us.oracle.com/s11-2011.11"/>
</publisher>
<publisher name="sae">
<origin name="http://saeosol.us.oracle.com/sae"/>
</publisher>
</source>
<software_data action="install">
<name>pkg:/entire</name>
<name>pkg://solaris/babel_install</name>
<name>pkg://sae/AIPostAsterix</name>
</software_data>
<software_data action="uninstall">
<name>pkg:/babel_install</name>
<name>pkg:/slim_install</name>
</software_data>
</software>
The separate processing of <software> allowed us to achieve the use case
for setting up a different publisher on the end system than was used to
install it. For example in manufacturing, we may pre-install systems
from some local publisher but set up the installed system with something
else.
What would happen if you also include the other software types ?, like
'SVR4','CPIO','ARCHIVE','IMAGE','P5I','DU','P5P' then, will you end up
with only one ?, or is it just that all the software types are kind of
"bundled" together per software type ?
Correct. These other types wouldn't intersect with type="IPS".
-ethan
Thanks
Paul
On 01/10/12 02:40 PM, Ethan Quach wrote:
Paul,
Separation of your two <software> sections is what's causing this.
The publisher(s) in the second <software> element (as it is processed
in document order) is what ends up left in the image. You should
instead merge them into one:
<software type="IPS">
<source>
<publisher name="solaris">
<origin name="http://saeosol.us.oracle.com/s11-2011.11"/>
</publisher>
<publisher name="sae">
<origin name="http://saeosol.us.oracle.com/sae"/>
</publisher>
</source>
<software_data action="install">
<name>pkg:/entire</name>
<name>pkg:/babel_install</name>
<name>pkg:/AIPostAsterix</name>
</software_data>
<software_data action="uninstall">
<name>pkg:/babel_install</name>
<name>pkg:/slim_install</name>
</software_data>
</software>
Note, you shouldn't really be using "babel_install" anymore. It
works for backwards compatibility, but if you're install S11, you
should replace this with "pkg:/group/system/solaris-desktop". You
should also be able to remove the whole <software_data> section that
specifies the "uninstall" as well.
-ethan
On 01/10/12 13:57, Paul de Nijs wrote:
All,
I installed a system with solaris11 (2011.11) and tried to include a
zone. It failed since my main publisher in the global zone is gone...
This is the ai_manifest for the global zone:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance name="default" auto_reboot="true">
<target>
<disk whole_disk="true">
<disk_keyword key="boot_disk"/>
<partition name="1" action="create" part_type="191">
<slice name="6" action="create" force="true">
<size val="100mb"/>
</slice>
<slice name="7" action="create" force="true">
<size val="100mb"/>
</slice>
<slice name="0" action="create"/>
</partition>
</disk>
</target>
<software type="IPS">
<source>
<publisher name="solaris">
<origin name="http://saeosol.us.oracle.com/s11-2011.11"/>
</publisher>
</source>
<software_data action="install">
<name>pkg:/entire</name>
<name>pkg:/babel_install</name>
</software_data>
<software_data action="uninstall">
<name>pkg:/babel_install</name>
<name>pkg:/slim_install</name>
</software_data>
</software>
<software type="IPS">
<source>
<publisher name="sae">
<origin name="http://saeosol.us.oracle.com/sae"/>
</publisher>
</source>
<software_data action="install">
<name>pkg:/AIPostAsterix</name>
</software_data>
</software>
<configuration name="x4100-001-vm1"
source="http://10.196.231.30:10101/10.196.8.2/zones/x4100-001-vm1/zonecfg";
type="zone"/>
</ai_instance>
</auto_install>
As you can see, 2 publishers
After the installation the first publisher
(http://saeosol.us.oracle.com/s11-2011.11, solaris) is gone, and the
zone install fails
A cannot imagine that this is good, or is it ?
BTW my zone ai_manifest looks like:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE auto_install SYSTEM 'file:///usr/share/install/ai.dtd.1'>
<auto_install>
<ai_instance name='zone_default'>
<software type='IPS'>
<destination>
<image>
<facet set='true'>facet.locale.en</facet>
<facet set='true'>facet.locale.en_US</facet>
</image>
</destination>
<software_data action='install'>
<name>pkg:/group/system/solaris-large-server</name>
</software_data>
</software>
</ai_instance>
</auto_install>
Thanks
Paul
--
Paul de Nijs | Principal Software Engineer | Performance
Technologies | +1.503.495.7882
Oracle Strategic Applications Engineering (SAE)
3295 NW 211th Terrace | Hillsboro, OR 97124-7110
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
--
Paul de Nijs | Principal Software Engineer | Performance Technologies
| +1.503.495.7882
Oracle Strategic Applications Engineering (SAE)
3295 NW 211th Terrace | Hillsboro, OR 97124-7110
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
