Hi Folks,

I had requested a similar feature back in Jun-2009 and one of the LDOM active 
member (Octave Orgeron) submitted and RFE.

Here is the link of it,

http://defect.opensolaris.org/bz/show_bug.cgi?id=9466

Has this RFE being implemented in the latest release of LDOM, If not any plans 
to add it and when?

Thanks for your everybody's time :)

Regards,
AN. 


> From: ldoms-discuss-request at opensolaris.org
> Subject: ldoms-discuss Digest, Vol 30, Issue 18
> To: ldoms-discuss at opensolaris.org
> Date: Thu, 21 Jan 2010 12:00:00 -0800
> 
> Send ldoms-discuss mailing list submissions to
>       ldoms-discuss at opensolaris.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
> or, via email, send a message with subject or body 'help' to
>       ldoms-discuss-request at opensolaris.org
> 
> You can reach the person managing the list at
>       ldoms-discuss-owner at opensolaris.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ldoms-discuss digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: autosave feature and autorecovery_policy starting with
>       LDOM 1.2 (Mike Christensen)
>    2. Re: autosave feature and autorecovery_policy starting with
>       (Andras Spitzer)
>    3. Re: autosave feature and autorecovery_policy starting with
>       (Mike Christensen)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 20 Jan 2010 14:22:37 -0800
> From: Mike Christensen <Michael.Christensen at Sun.COM>
> To: Andras Spitzer <wsendai at gmail.com>
> Cc: ldoms-discuss at opensolaris.org
> Subject: Re: [ldoms-discuss] autosave feature and autorecovery_policy
>       starting with LDOM 1.2
> Message-ID: <4B57822D.6040002 at Sun.COM>
> Content-Type: text/plain; CHARSET=US-ASCII; format=flowed
> 
> On 01/20/10 10:51, Andras Spitzer wrote:
> > Hi,
> > 
> > If I understand correctly, the autosave functionality added in LDOM 1.2, is 
> > not intended to replace the manual command (ldm add-spconfig) to save the 
> > configuration on the SC, is this correct?
> 
> Yes, that's correct.
> 
> > If I understand correctly the standard operation still is to manually save 
> > the configuration to the SC (using ldm add-spconfig) after any change you 
> > want to keep, and the autosave is a safety-net in case you forgot to do it 
> > manually.
> 
> Yes, that's correct.
> 
> > The reason why it's confusing if I set "autorecovery_policy=3", which 
> > automatically updates the config on the SC in case the autosaved 
> > configuration is newer than the one on the SC. Can we use this as an "auto 
> > save" feature which keeps the config on the SC up-to-date, and just forget 
> > to save tha config manually?
> 
> It's at best a partial safety net in case you've forgotten to do the
> manual update and LDoms manager daemon (ldmd) has restarted for some
> reason (e.g. reboot or 'svcadm restart ldmd').
> 
> The autorecovery_policy isn't checked on every change to the config,
> only on ldmd restart.
> 
> > The actions of autorecovery_policy takes place at which phase, only once 
> > during a system/ldm startup, or after any change in the configuration?
> 
> Currently the autorecovery_policy is only checked on any restart of
> ldmd.  So, you could automatically force the update if you did a
> 'svcadm restart ldmd' (with autorecovery_policy set to 3).
> 
> One problem with doing an update on every change is that ldm
> add-spconfig's take some time to do (typically 15-30 seconds), and it
> would probably be unpleasant to do those updates whenever the config
> changes.  For example, when you're building a new domain, there are a
> lot of interim config's that you're probably not really interested in
> temporarily saving.
> 
> Mike
> 
> > Could anyone clarify this?
> > 
> > Regards,
> > sendai
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 21 Jan 2010 06:29:07 PST
> From: Andras Spitzer <wsendai at gmail.com>
> To: ldoms-discuss at opensolaris.org
> Subject: Re: [ldoms-discuss] autosave feature and autorecovery_policy
>       starting with
> Message-ID: <731208667.61264084177744.JavaMail.Twebapp at sf-app1>
> Content-Type: text/plain; charset=UTF-8
> 
> Mike,
> 
> Thanks for the clarification. This question will be a bit off-topic, but as 
> far as I know today there is no possible way/command to view the 
> configurations stored on the SC, is this correct? We can add, remove, or 
> activate configurations on the SC, but we can't view their contents.
> 
> If that's the case, at least do we have an RFE for this? That would be really 
> handy to see a config on the SC from the OS before I decide to select it and 
> boot it.
> 
> Regards,
> sendai
> -- 
> This message posted from opensolaris.org
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 21 Jan 2010 11:48:42 -0800
> From: Mike Christensen <Michael.Christensen at Sun.COM>
> To: Andras Spitzer <wsendai at gmail.com>
> Cc: ldoms-discuss at opensolaris.org
> Subject: Re: [ldoms-discuss] autosave feature and autorecovery_policy
>       starting with
> Message-ID: <4B58AF9A.10009 at Sun.COM>
> Content-Type: text/plain; CHARSET=US-ASCII; format=flowed
> 
> On 01/21/10 06:29, Andras Spitzer wrote:
> > Mike,
> > 
> > Thanks for the clarification. This question will be a bit off-topic, but as 
> > far as I know today there is no possible way/command to view the 
> > configurations stored on the SC, is this correct? We can add, remove, or 
> > activate configurations on the SC, but we can't view their contents.
> 
> Yes, that's correct.
> 
> The format of the SP config's is a set of binary Machine
> Descriptions (MDs) - the same format as what you'd get from
> /dev/mdesc.  We have crude dump utilities for
> the binaries, but no "pretty printer".  Nothing close
> to something that could be given to a user.
> 
> And, FWIW, the autosave configs are stored as a set of
> these MD binaries also (each with a 296 byte "autosave header"
> prepended) at: /var/opt/SUNWldm/autosave-<config_name>/*
> if you want to look at them.  Doing a 'strings' on the files may
> give you some clue what the config looks like (e.g.
> if you do 'strings hv-md.bin', the ldom domain names
> are part of the output, usually at the end, I think).
> 
> If you're booted on a config, and it hasn't already been autosaved,
> you can force an autosave of it by doing some innocuous change of
> the config, like a set-var.
> 
> > If that's the case, at least do we have an RFE for this? That would be 
> > really handy to see a config on the SC from the OS before I decide to 
> > select it and boot it.
> 
> I'm not aware of an RFE for this.  And there isn't really an
> easy way to grab a config off the SP to (say) a file on the
> control domain, so you'd need that functionality also.
> I vaguely remember an RFE for grabbing a copy of an SP config,
> but I can't find it right now.
> 
> Mike
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> ldoms-discuss mailing list
> ldoms-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
> 
> 
> End of ldoms-discuss Digest, Vol 30, Issue 18
> *********************************************
                                          
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/196390707/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/ldoms-discuss/attachments/20100121/c43c6720/attachment.html>

Reply via email to