Dave,

Another suggestion.
What about passing the OS-release to the install server when calling for the downloads of the manifests with cgi_get_manifest.py (the postdata parameters) ?
I could live with that too ;-)

Unfortunately, you cannot use HTTP_USER_AGENT on the install server when the clients connects to the install server, since the client uses wget like protocols.

Paul

On 07/28/11 10:13 AM, Paul de Nijs wrote:
Dave,

Since the release of opensolaris, I started to implement the whole install procedure in our own tool, still running on Solaris 10, our install server for, well every OS you can think of on sparc and x86. I can keep pace with installadm, and all the changes in different builds, but not the latest ones. We have a generic ai_manifest and sc_manifest, but in some builds they are different.

E.G:
- Timezone is back in b_168
- <target_device> is gone in the ai_manifest since b_167, and a lot of stuff is added. - ai_manifest and sc_manifest(s) are separate in b_164, introducing the way manifests are downloaded (as attachments rather than the single manifest file with embedded sc_manifest)
- total change in manifest since b_148

So that means that I have to know what manifests to use for different builds, (and yes, we are also running old builds, and compare the performance with newer builds. We benchmark the OS-es and Applications running on them. If we find something, we report it to the development team). We manipulate the manifests based on releases, and they are build on the fly.

On the other hand, it's pretty convenient to see the release/build when you copy the contents of the .iso to your install server, and you make a mistake in the "directory name".

Thanks

Paul


On 07/28/11 09:34 AM, Dave Miner wrote:
On 07/28/11 12:24, Paul de Nijs wrote:
All,

Can we get the .release file back in the root directory of the ai
solarisexpress iso file ?
It's been missing after build 151a

To get the release now, it can be checked in boot/grub/menu.lst, but
that is nor very convenient, and I'm not sure these files are subject to
changes.


Can you explain what problem you're trying to solve, Paul? Then we can consider putting a proper interface of some sort in place.

Dave

--



Paul de Nijs | Principal Sales Consultant, HPC Benchmark Engineer | +1.503.617.8572
Oracle HPC Sales Support
3295 NW 211th Terrace | Hillsboro, OR 97124-7110



_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

--



Paul de Nijs | Principal Sales Consultant, HPC Benchmark Engineer | +1.503.617.8572
Oracle HPC Sales Support
3295 NW 211th Terrace | Hillsboro, OR 97124-7110


_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to