Hi, have you read the Profiles from dmtf.org? Sometimes they are helpfull (sometimes not:-)
DSP1014_1.0.0.pdf DSP1035_1.0.0.pdf DSP1036_1.0.1.pdf DSP1038_1.0.1.pdf http://www.dmtf.org/standards/published_documents/ Am Mittwoch, 12. August 2009 13:50:09 schrieb Michal Zugec: > 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: [email protected] > 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: [email protected] > For additional commands, e-mail: [email protected] > > -- MFG Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: [email protected] -------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
signature.asc
Description: This is a digitally signed message part.
