I tend to agree that from an architectural perspective, the site.xml
might better be handled as Obsolete -- it seems that the new mechanism
is superior.
I also agree that Patch (as specified in the document) is fine for this
case.
- Garrett
On 05/ 4/10 12:14 PM, John Fischer wrote:
Tony,
This looks fine.
My only question is what is the release binding? Would it
be a Minor release of Solaris or a Patch release of Solaris?
I think a Minor release of Solaris.
Also the site.xml file should be declared Obsolete Committed.
Right?
Thanks,
John
On 05/ 4/10 11:53 AM, Liane Praza wrote:
I'm submitting this proposal on behalf of Tony Nguyen. It's
submitted as closed-approved-automatic because it was reviewed on
smf-discuss, and is a fairly straightforward extension to an existing
mechanism. I appreciate it may be a little on the line, so am happy
to convert it to a fasttrack if there are substantial questions or
people would like more time to comment.
liane
---
1. Introduction
1.1. Project/Component Working Name:
A directory for site profiles
1.2. Name of Document Author/Supplier:
[email protected]
4. Technical Description:
Summary:
SMF allows administrator(s) and administrative tools to deliver
service customizations into /etc/svc/profile/site.xml profile which
is applied once during system/early-manifest-import. Essentially, all
customizations via profile must be delivered at the same time which
prevents administrators from incrementally customize the system by
delivering multiple profiles and forces administrative tools to
coordinate their use of a single site.xml file. These shortcomings
really limit the benefit for profiles. For example, Distribution
Constructor provides a smf_service_profile section to allow
specification of profiles to be manually applied during image build
process and auto-installer also manually applies network_nwam.xml
during boot. All these manual profile applications can be removed
if there's support for automatic applying a set of administrative
profiles during boot.
This project delivers a new empty /etc/svc/profile/site directory in
which administrators and administrative tools can deliver service
customization profiles. Profiles in /etc/svc/profile/site are applied
once at boot during system/early-manifest-import. On a running
system,
administrator can put new profiles into /etc/svc/profile/site and
restart system/manifest-import to apply the new profiles. Current
profile behaviors are preserved, namely:
- profiles are applied only once, i.e. updated profiles are not
re-applied
- profile unapplying is not supported
- no ordering support for profiles
/etc/svc/profile/site.xml profile is still supported for backward
compatibility. /usr/sbin/svccfg apply subcommand is also enhanced to
accept a directory containing profiles.
Interfaces:
New profile directory processed during manifest import:
/etc/svc/profile/site Committed
svccfg apply takes either file or directory argument:
svccfg apply file|directory Committed
No incompatible change is proposed, so this case seeks patch binding,
though no backport is explicitly planned.
Doc Impact:
svccfg(1M)
--- svccfg.orig Wed Apr 21 23:32:07 2010
+++ svccfg.new Thu Apr 22 00:10:53 2010
@@ -1,7 +1,7 @@
Service Profile Subcommands
- apply [-n] file
+ apply [-n] file|directory
- If a file is a service profile, properties, including
+ If argument is a service profile, properties, including
general/enabled, that are specified in the file are
modified in the SMF repository. Not-yet-existent proper-
ties and property groups will be created. The type of
@@ -17,5 +17,10 @@
description of service profiles. This command requires
privileges to modify properties in the service and
instance. See smf_security(5) for the privileges
- required to modify properties. If file is not a service
- profile, the subcommand fails.
+ required to modify properties.
+
+ If argument is a directory, all profiles found under that
+ directory tree will get applied as described above. The
+ subcommand fails if specified file or any file found under
+ specified directory is not a service profile.
+
smf_bootstrap(5)
--- smf_bootstrap.orig Thu Apr 22 00:34:37 2010
+++ smf_bootstrap.new Thu Apr 22 00:33:44 2010
@@ -7,11 +7,16 @@
/etc/svc/profile/platform.xml
/etc/svc/profile/site.xml
- The svc:/smf/manifest service is used in a similar fashion.
+ Except for the three mentioned profiles, none of the
+ /etc/svc/profile profiles are automatically applied to the
+ repository. A profile can be manually applied or re-applied
+ using svccfg(1M).
- Additional service profiles that characterize the activation
- of various groups of service instances might be present in
- /etc/svc/profile. None of the /etc/svc/profile profiles are
- automatically applied to the repository. A profile can be
- manually applied or re-applied using svccfg(1M).
+ The /etc/svc/profile/site directory is delivered to contain
+ additional site specific profiles which also get applied by
+ system manifest import services. Administrators and
+ administrative tools can place new profiles into this
+ directory and restart system/manifest-import or reboot the
+ system to apply the new profiles.
+ The svc:/smf/manifest service is used in a similar fashion.
_______________________________________________
opensolaris-arc mailing list
[email protected]
