James Carlson wrote:
> Alan Maguire writes:
>
>> James Carlson wrote:
>>
>>> I think modifying the contents of a zone that's been booted at least
>>> once means entering the zone.
>>>
>>>
>>>
>> understood. are there other edge cases where -R <altroot> might
>> be used in a non-?install/upgrade? environment i wonder? i can't
>> think of any offhand.
>>
>
> The only one I know of is when administering diskless boot images.
> I'm not sure that applies in this case.
>
>
>>> I have some per-datalink information, such as default vlan id, but
>>> also some that's per-bridge-instance, such as STP configuration.
>>> There's some information that could go either way, such as assignment
>>> of links to bridges, but that I'm leaning towards having as attributes
>>> of bridges rather than as attributes of links.
>>>
>>> ("Bridge instances" are new objects in this area.)
>>>
>>>
>> so there would be an SMF instance for each bridge instance?
>>
>
> Yes. I'm writing that part of the design as we speak, that's the
> direction I'm headed right now. It might change if I hit a wall.
>
>
>> one thing we will have to think about is the effects of link
>> rename - if the link name is a property of the bridge instance,
>> we will have to ensure that renames are propogated to bridge
>> instances also (unless we use linkids to identify associated
>> datalinks, but i believe the intent is to expose linkids as little
>> as possible). thanks!
>>
>
> Good point. I hadn't thought about that. I'll see if I can factor it
> in. If not, then renames will need to propagate as you're suggesting.
>
I'm not sure what is the best way to propagate instance renaming within
our current smf framework.
With my current prototype, I fix all dependencies during renaming
(before deleting the old instance)
a datalink smf instance. But, if there is an instance that silently
refers the name of the instance being
renamed using the way other than creating dependency (saves the name in
an instance's property), it
will be hard to detect such referring and fix it during renaming...
Max
