On 05/12/10 12:25 PM, James Carlson wrote:
Darren J Moffat wrote:
On 12/05/2010 17:01, Sebastien Roy wrote:
The svc:/network/install service will support configuring one IPv4
interface and/or one IPv6 interface and, optionally, a default route
reachable by these interfaces. The service will define two property
groups, one for an IPv4 interface and one for an IPv6 interface. The
service will use its properties and ipadm(1M) to configure the network
interfaces. And similarly, the service will use its properties and
route(1M) to define a default route.
Why is this limited to a single address for v4 and v6 ?
Can multiple instances of network/install be created in a profile and be
activated by the installer to create hosts with multiple IP addresses ?
As is I believe possible today with jumpstart ?
For the DNS configuration why are the resolv.conf "options", "sortlist"
directives not supported for configuration in svc:/network/dns/install ?
There seem to be quite a few issues in the same area:
- Where are NIS and LDAP? Or are they not needed by this part of
the installation process?
They are missing. But as of yet there has been no requirement for their
support. Nothing about this proposal prevents the addition of interfaces
to support them in the future.
- How does routing configuration work? Are "default routes" the only
thing that's ever needed?
At the moment, the only requirement is that we can configure a default
route.
- What about datalink configuration?
What about it? This proposal isn't trying to solve every possible
network configuration possibility. If we need to support datalink
configuration, then we'll ARC interfaces when the need arises.
- What about systems that need to have IPMP or other IP-level bits
such as tunnels or IPsec?
Again, we're not trying to support all networking configuration
possibilities with this proposal. We're trying to provide the Install
team with the interfaces that they need to fulfill their requirements of
being able to configure one IP interface, a default router for that
interface and a DNS client. This proposal is trying to satisfy those
requirements without limiting future requirements. If future
requirements require a change to the interfaces proposed here, then the
interfaces can be adjusted at that time.
I think what might be missing here are the boundaries of this case. I'm
a little queasy with the idea of assuming that the only interfaces that
matter are available-at-boot Ethernet drivers with simple IP
configuration and not much else, but perhaps it makes sense in some
particular (limited?) context.
It makes sense in the context I mentioned above. We'd be very surprised
if more requirements don't appear before the Solaris Next release. The
interfaces proposed here may have to change as a result. But at the
moment, the Install team has identified the requirements already
described above. And this proposal is intended to meet those requirements.
Is there some case that describes what the "Solaris Next" installer can
and can't do over a network?
I don't think there is one yet. As I mentioned in the proposal, I expect
the Install team to ARC a case for AI at some point.
_______________________________________________
opensolaris-arc mailing list
[email protected]
