Hey Serge,

No.  All processes in one container must be in the same Resource Pool.

Even if they could accomplish what they want, this would violate the Oracle license agreement and the whole point of Oracle's "capped container" licensing policy.

There are a few other ways to configure this, but they won't meet all of the goals mentioned. Howver, they won't violate the licensing policies.

The simplest is probably:
* One BEA pool, one Oracle pool, one default pool
* Three zones per pool: UserGroup 1, UserGroup 2, UserGroup3.
* Projects to wrap up all the resource controls, accounting, etc.

Does that help?

serge nadon wrote:

Begin forwarded message:

    *From: *Michael OConnor <[EMAIL PROTECTED]>
    *Date: *June 13, 2006 3:22:42 PM PDT
    *Cc: *Michael O'Connor <[EMAIL PROTECTED]>, Serge
    *Subject: Global zone projects & local zones

    Customer asks - is it possible to configure the projects mechanism
    in the global zone to bind specific local zone processes associated
    with a specific UIDs to specific resource pools while other
    processes in these same local zones are bound to the default
    resource pool/pset? Idea is to have individual customers isolated
    into their own local zone but rather than binding the entire zone
    (and all its processes) to a single resource pool, only have
    specific processes within each zone bound to specific shared
    resource pools.

    Attached graphic should help illustrate what I'm looking for.

    Customer wants to minimize the number of zones he has to manage on a
    larger server and doesn't want to license both BEA and Oracle for
    the whole box. Customer has 3 classes of processes 1) Oracle, 2) BEA
    and 3) Other. If this scenario is not possible, he will need to
    create 3 unique zones for each customer and then bind each local
    zone to the respective resource pool which will drive up his
    management costs. Btw, our managed services group charges
    ~$120/month to manage each local zone which is part of what's
    driving this discussion.

     >From what I've read, once we introduce local zones then we lose
    the ability to use the project mechanism to associate subsets of
    process within each local zone with different processor sets. Hoping
    this is not the case.





    * Michael E. O'Connor *
    Engagement Architect
    Sun Microsystems, Inc.
    8880 Cal Center Drive, Suite 200
    Sacramento, CA 95630 US
    Phone x69479 / +1 415.762.2709
    Mobile: 916.716.0361
    Web: www.sun.com


    /This message sent using: Open Source Solaris 10 x86 (01/06),
    OpenSolaris iwi driver, Java Desktop System R3, Mozilla 1.7/

    /PRIVACY & CONFIDENTIALITY NOTICE: The information contained in this
    e-mail and any attachments is intended for the named recipient(s)
    only, unless otherwise waived in writing by me. It may contain
    privileged and confidential information. If you are not the intended
    recipient, you must not copy, forward or distribute. If you have
    received this e-mail in error, please notify me immediately and
    destroy all copies of the original message. Have a nice day :)/



zones-discuss mailing list

Jeff VICTOR              Sun Microsystems            jeff.victor @ sun.com
OS Ambassador            Sr. Technical Specialist
Solaris 10 Zones FAQ:    http://www.opensolaris.org/os/community/zones/faq
zones-discuss mailing list

Reply via email to