Mailinglist Archive: yast-devel (246 mails)

< Previous Next >
[yast-devel] webYaST: network CIM model summary
  • From: Michal Zugec <mzugec@xxxxxxx>
  • Date: Wed, 12 Aug 2009 13:50:09 +0200
  • Message-id: <4A82AC71.4070706@xxxxxxx>
UI mockup
---------
http://mschmidkunz.110mb.com/network.html


Requirements
------------
There were some requirements:
- only "eth" devices (no wireless, no bridges, no vlans)
- configure one or none device
- no global settings (networkmanager, disable ipv6, dhcp
options)
- ifup only
- device can be configured via DHCP or with address(IPv4
or IPv6)
- no "no address" option, no additional addresses, no ifplugd,
STARTMODE=onboot by default
- nameserver - use "old YaST" options
- route - setup only default route (no additional routes, no metrics)

The meaning of this module is to set machine to be "connected",
accessible via ssh - that's all. For all other, special, "expert" setup
is here old YaST


CIM model
---------
Network is defined in CIM model widely:
http://www.wbemsolutions.com/tutorials/CIM/cim-model-net.html
But what we need is only about 10-20% of that. It's because there are
parameters needed for several network devices, routers, wireless AP,
switches, network infrastructure definition, ...

We have package "cim-schema" in distribution with some interesting .mof
files. Some of them are deprecated!

/usr/share/mof/cimv2.19.1/Device/CIM_EthernetPort.mof
ethernet device - only interesting is MAC address

/usr/share/mof/cimv2.19.1/Device/CIM_NetworkPort.mof
almost the same with higher abstraction

/usr/share/mof/cimv2.19.1/Network/CIM_IPConfigurationService.mof
in the future may be deprecated (but without information what we should
use instead of it)
network configuration, IP address settings

/usr/share/mof/cimv2.19.1/Network/CIM_IPAssignmentSettingData.mof
this is equal to our BOOTPROTO parameter

/usr/share/mof/cimv2.19.1/Network/CIM_IPProtocolEndpoint.mof
don't know difference between this and CIM_IPConfigurationService (but
this is more similar to our configurations)

/usr/share/mof/cimv2.19.1/Network/CIM_NetworkVLAN.mof
VLAN settings (but there are no .mof files for other network types -
bridge, bonding, ...)

There are also some mof files for DNS (resolv.conf) settings
/usr/share/mof/cimv2.19.1/Network/CIM_DNSGeneralSettingData.mof
/usr/share/mof/cimv2.19.1/Network/CIM_DNSProtocolEndpoint.mof
/usr/share/mof/cimv2.19.1/Network/CIM_DNSSettingData.mof

As Klaus suggested, we'll use option names (in rest-api) based on names
from CIM model.

Bye,
Michal


--
Best Regards,
Michal Zugec
Software developer
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: mzugec@xxxxxxx
Lihovarska 1060/12 tel: +420 284 028 960
190 00 Praha 9 fax: +420 296 542 374
Czech Republic http://www.suse.cz/

--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >