Forwarding this query based on recommendations from Sreedhar.

Any response will be appreciated.

Thanks,
Murali

-------- Original Message --------
Subject:        S11 AI LDom configurations
Date:   Wed, 19 Dec 2012 23:12:22 +0530
From:   muralidhar rao <[email protected]>
Organization:   Oracle Corporation
To:     [email protected]



Hi Ethan,

I'm part of the OpsCenter engineering team, and as you probably already
know, we provide a way of installing S11 on client systems by hosting
our own AI server and publisher etc

I write to you, seeking some help in the context of LDOMs. Please point
me to the right person/alias, if you're not the right person to answer
my queries.

Lemme provide some context. On every machine that the customer wishes to
install S11 on, we also install some Ops Center related 'agentry'
software. This allows us to implement other actions like monitoring,
patching, virtualization etc, on the freshly installed S11 system. As of
today, we install the agent software, through a 'first-boot'
service/script mechanism. So, as of today, the S11 installation
completes, the first boot service runs, configures some networking and
then installs the agent, after which we disable the service. Since this
is created as a 'transient' service, this doesn't get enabled on every
reboot, only at the first one.

We've unconvered multiple scenarios recently, in which we'd like to
perform some additional configuration AND perform a reboot (mandatory)
before installing the agent. All of them are related to LDOMs, where we
will need to enable MPxIO or run a delayed reconfiguration or something.
We were wondering if there is some way that we could achieve this
through the AI framework itself (like we used to have JET for S10).

We could, of course, remove the 'transient' property from the service
and make it run repeatedly, and check for 'first-boot', 'second-boot'
and 'subsequent-boot' and handle these cases. But one of the main
concerns we have is, how do we know when it is safe/legal to instantiate
the mandatory reboot that we need to, after finishing the configuration
post first reboot? If we reboot, before the other SMF services have
finished, we might leave the system in an incosistent state.

Thanks in advance for reading through a rather detailed email, and
providing any hints/inputs.

Thanks,
Murali

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

Reply via email to