Mailinglist Archive: yast-devel (246 mails)

< Previous Next >
Re: [yast-devel] WebYaST: Network CIM Model
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Mon, 17 Aug 2009 17:02:51 +0200
  • Message-id: <20090817150251.GA31657@xxxxxxxxxxxxx>
* Martin Vidner <mvidner@xxxxxxx> [Aug 17. 2009 16:52]:
On Mon, Aug 17, 2009 at 02:49:31PM +0200, Klaus Kaempf wrote:
Well, modeling _is_ _hard_. Thats one of the reasons I'd like us to
look at existing models instead of inventing our own.
The initial proposal
( was fine,
just adapt the class and attribute names (to whats used in CIM) and use
REST pathes for the dependencies.

I and Miso have tried to continue with this. It is taking too long,
and I think that we face two options:
1) use the CIM model properly (simplified (denormalized) or not). It
will take us very long and it will be hard to use

Agreed. So use the CIM model as a guidance.

2) use CIM so-so, not to spend too much time on it.
If it looks like CIM, some people will be put off by its complexity
(actual or reputed). Those who won't will be disappointed by the
inaccuracies in our simplifications.

You'll never please everyone ;-)

So I propose to go ahead with prototyping the non-CIM interface that
we sent as v1 (or some small improvement of it).

No objections. But try to follow CIM attribute and class names.

Please document your findings inside the client module to inform
others about the API decisions being taken.


SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)

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

< Previous Next >