Hi,
My understanding is that you can create pools in the GZ and attach
zones to them. However, you can't create pools or psets from a NGZ. You
can of course create projects within a zone with resource capping,
lwps, ipc settings, etc. Those projects would not be visable/available
in the global zon
Thinking outloud, Ihsan,
I haven't tried it, but I would expect a NGZ's *project.pool to not be
able to bind to a pool, since the NGZ has no visibility into a pool
(right now; don't know if this could or will be extended).
Regarding what you are trying to accomplish, what are you referring to
Steffen,
Thanks for your contribution on this.
As you know, the project attribute, project.pool,
specifies the pool to which processes associated with the project entry
should be bound.
project.pool=pool_name. pools are fixed resources and processes are
uniquely identified Globaly or localy t
Ihsan Zaghmouth wrote On 09/14/06 11:59,:
Hi again,
I am posting this message just in case it was missed or forgotten.
*Can we assign the Zone to a pool and the Zone's Project to another pool ?*
I don't believe so. The pools should not be visible in a zone, as they
are a *system* resource, a
Hi again,
I am posting this message just in case it was missed or forgotten.
Can we assign the Zone to a pool and the Zone's Project to another
pool ?
any thoughts ?
cheers
Ihsan
Ihsan Zaghmouth wrote:
Hi,
A general question regarding Zones, Pools and Projects within
these Zo
Hi,
A general question regarding Zones, Pools and Projects within
these Zones.
I am aware of zone associations to pools and their psets. Many zones to
1 pool and not visa versa.
The question is, if we decide on 2 Pools, could we associate a Zone
to pool_1 (set pool = "pool_1" in zonecfg or p
