June 2013 - openlmi-devel - Fedora Mailing-Lists

by Radek Novacek

Disclaimer: I know this is OpenLMI mailing list, but I will post announcements about new versions of KonkretCMPI here, because many of OpenLMI providers use it. Since KonkretCMPI upstream [1] is dead for long time (last upstream version 0.8.7 was released 2008-10-22) I've decided to continue development myself. I don't have access to original SCM repository or web page, so I've created git repo at github [2]. Highlights of version 0.9.0: * Use CMake as buildsystem (added FindCMPI.cmake and FindKonkretCMPI.cmake modules) * Python bindings for the MOF parser * Fixed using experimental schema * Assertion crash fixed * Add missing headers * Many other minor bugs fixed You can download the new version from github [3]. It is already in Fedora rawhide and it's coming to Fedora 18 soon. Radek Novacek [1] http://konkretcmpi.org/ [2] https://github.com/rnovacek/konkretcmpi [3] https://github.com/rnovacek/konkretcmpi/archive/0.9.0/konkretcmpi-0.9.0.t...

10 years, 8 months

2
1
0 / 0

RFC: Script development

by Jan Safranek

Hi, I've been talking to Stephen Gallagher how to proceed with client script development in lmishell. The goal is to provide high-level functionality to manage remote systems without complete knowledge of the CIM API. We agreed that: - we should provide python modules with high-level functions (we were thinking about nice classes, e.g. VolumeGroup with methods to extend/destroy/examine a volume group, but it would end up in duplicating the API we already have. We also assume that our users are not familiar with OOP). - these python functions try to hide the object model - we assume that administrators won't remember association names and won't use e.g. vg.associators(AssocClass="LMI_VGAssociatedComponentExtent") to get list of physical volumes of a vg. We want nice vg_get_pvs(vg) function. We will expose CIM classes and properties though. - these python functions are synchronous, i.e. they do stuff and return once the stuff is finished. They can do stuff in parallel inside (e.g. format multiple devices simultaneously) but from outside perspective, the stuff is completed once the function returns. (we were thinking about python functions just scheduling multiple actions and do stuff in parallel massively, but we quickly got into lot of corner cases) - each high-level function takes a LmiNamespace parameter, which specifies the WBEM connection + the namespace on which it operates -> i.e. applications/other scripts can run our functions on multiple connections -> if the LmiNamespace is not provided by caller, some 'global' one will be used (so users just connect once and this connection is then used for all high-level functions) - we should probably split these high-level function to several modules by functionality, i.e. have lmi.networking and lmi.storage.vg, lmi.storage.lv etc. - it should be easy to build command-line versions for these high-level functions -> it is not clear if we should mimic existing cmdline tools (mdadm, vgcreate, ip, ...) or make some cleanup (so creation of MD raid looks the same like creation of a VG) - we should introduce some 'lmi' metacommand, which would wrap these command line tools, like 'lmi vgcreate mygroup /dev/sda1 /dev/sdb1' and 'lmi ip addr show'. It's quite similar to fedpkg or koji command line utilities. - 'lmi' metacommand could also have a shell: $ lmi shell > vgcreate mygroup /dev/sda1 /dev/sdb1 > ip addr show I tried to create a simple module for volume group management. I ran into several issues with lmishell (see trac tickets), attached you can find first proposal. It's quite crude and misses several important aspects like proper logging and error handling. Please look at it and let us know what you think. It is just a proposal, we can change it in any way. Once we agree on the concept, we must also define strict documentation and logging standards so all functions and scripts are nicely documented and all of them provide the same user experience. Jan P.S.: note that I'm out of office for next week and with sporadic email access this week.

10 years, 11 months

8
21
0 / 0

Fwd: how to get a policy for openlmi-*

by Jan Safranek

I got a quick info how to start writing policy for OpenLMI providers, see below. Please try so for you providers and send AVCs to Mirek Grepl. I can only add: 0.1: Install necessary packages # yum install selinux-policy-devel 0.2: read /usr/share/doc/tog-pegasus-2.12.1/README.RedHat.Security 0.3: based on the document above: # cp /usr/share/doc/tog-pegasus-2.12.1/cmpiOSBase_OperatingSystemProvider-cimprovagt.example /usr/libexec/pegasus/<yourprovider>-cimprovagt (and package the file) # chmod 755 /usr/libexec/pegasus/<yourprovider>-cimprovagt Jan -------- Original Message -------- Subject: how to get a policy for openlmi-* Date: Wed, 29 May 2013 10:16:36 +0200 From: Miroslav Grepl <mgrepl(a)redhat.com> To: jsafrane(a)redhat.com 1. create own policy for a provider # cat mypol.te policy_module(mypol,1.0) pegasus_openlmi_domain_template(providername) and run # make -f /usr/share/selinux/devel/Makefile mypol.pp # semodule -i mypol.pp # chcon -t pegasus_openlmi_providername_exec_t PATH_TO/providername test it and run # ausearch -m avc -ts recent and send me AVC msgs. For example we define in the policy pegasus_openlmi_domain_template(account) If you want to activate the policy for this account provider, you need to run # chcon -t pegasus_openlmi_account_exec_t /usr/libexec/pegasus/cmpiLMI_Account-cimprovagt

10 years, 11 months

3
5
0 / 0

lmishell, instance filtering

by Peter Hatina

Hi, from now, there is a preferred way, how to filter instances and instance names by using a dictionary. The old means of filtering still works, as well. Examples (with networking provider): eth0 = cimv2.LMI_IPNetworkConnection.first_instance(key="Name", value="eth0") vs. eth0 = cimv2.LMI_IPNetworkConnection.first_instance({"Name" : "eth0"}) The main reason, why we switched to this is: there can be more filter elements present: active_ifs = cimv2.LMI_IPNetworkConnection.instances({"EnabledDefault" : 2, "OperatingStatus" : 16}) Cheers -- Peter Hatina ENG Server Experience, System Management Red Hat Czech, Brno

10 years, 12 months

3
5
0 / 0

Service discovery: should we use SLP?

by Tomáš Smetana

Hello, I have mentioned this several times before: I had been asked to provide some example scripts that would "for every computer on the network... do something". It's not quite obvious how to actually find every WBEM-capable device on the network. There are several ways how to do that and it seems like SLP is being used in combination with WBEM quite often. Maybe it is the right thing for us to use for the OpenLMI discovery as well. The Pegasus CIMOM can register itself in the local SLP server and then even advertises the registered profiles as the service attributes. Here's the sample output from my testing machine for the illustration: [tsmetana@zaphod ~]$ slptool -u f-19-local findsrvs service:wbem service:wbem:https://[fe80::5054:ff:feb6:b32]:5989,65025 service:wbem:https://192.168.122.12:5989,65025 [tsmetana@zaphod ~]$ slptool -u f-19-local findattrs service:wbem (template-url-syntax=https://192.168.122.12:5989),(service-id=PG:192-168-122-12),(service-hi-name=Pegasus),(service-hi-description=Pegasus OpenPegasus Version 2.12.1 Development),(template-type=wbem),(template-version=1.0),(template-description=This template describes the attributes used for advertising Pegasus CIM Servers.),(InteropSchemaNamespace=root/PG_InterOp),(FunctionalProfilesSupported=Basic Read,Basic Write,Schema Manipulation,Instance Manipulation,Association Traversal,Query Execution,Qualifier Declaration,Indications),(MultipleOperationsSupported=FALSE),(AuthenticationMechanismsSupported=Basic),(AuthenticationMechanismDescriptions=Basic),(CommunicationMechanism=CIM-XML),(ProtocolVersion=1.0),(Namespace=root/PG_InterOp,root/PG_Internal,root/cimv2,root),(RegisteredProfilesSupported=SNIA:Server,DMTF:Profile Registration,SNIA:Server:Indication,SNIA:Profile Registration,SNIA:Server:Software,SNIA:SMI-S) SLP would bring another dependency (the slpd daemon) but has some advantages: the discovery queries are multicasted, Pegasus already supports this out-of-the-box (we only need to start registering profiles properly) and it looks to be quite simple. While playing with the SLP tools in Fedora I have written Python bindings for OpenSLP, so we should be able to integrate SLP support in the LMI shell: https://github.com/tsmetana/pyslp (We can "openlmify" the sources and integrate in our code eventually.) Opinions? Thanks and regards, -- Tomáš Smetana Platform Engineering, Red Hat

10 years, 12 months

5
10
0 / 0

Re: Review Request 458: prototype CIM<->PCP bridge

by Radek Novacek

Sending to openlmi-devel@ to have wider audience then on -review list. Thanks for providing this proof of concept, I think having access to pcp metrics would be very valueble for us. But I'm not sure that the approach of having the classes dynamically created runtime is the right way to go. Here goes some notes: 1) "PCP metrics can come and go" - the question is when the classes should be regenerated? First creation can be done on package installation. But what to do if one want to regenerate later (possible remotely). I think we should at least have CIM API for regenerating this class list. 2) What about WS-Man? This model won't work with WS-Man, because WS-Man doesn't have EnumerateClasses. Do we care about WS-Man? 3) I would rather see some internal logic instead of having direct 1:1 export of pcp metrics. E.g. association between network.interface.* metric and CIM representation of given network interface (IPNetworkConnection). I think we should follow CIM modelling more closely. Radek Novacek On Sat 15 of Jun 2013 3:41:24 Frank Eigler wrote: > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard-openlmi.rhcloud.com/r/458/ > ----------------------------------------------------------- > > Review request for OpenLMI Developers. > > > Repository: openlmi-providers > > > Description > ------- > > prototype CIM<->PCP (performance co-pilot) bridge, for review/comment > > > Diffs > ----- > > src/pcp/PCP_Metric.mof PRE-CREATION > src/pcp/PCP_Metric_PMNS.mof PRE-CREATION > src/pcp/PCP_Metric_PMNS.reg PRE-CREATION > src/pcp/PCP_pmns2mofreg.sh PRE-CREATION > src/pcp/README PRE-CREATION > src/pcp/pcp-metric.py PRE-CREATION > > Diff: http://reviewboard-openlmi.rhcloud.com/r/458/diff/ > > > Testing > ------- > > smoke-testing via YAWN web gui > > > Thanks, > > Frank Eigler

11 years

5
7
0 / 0

Custom CIM Schema file

by George varghese

Hi, Could you please tell me the steps for creating a cim schema file for custom provider. Which tool I shall use for creating schema file? Please help me. Regards, George

11 years

1
0
0 / 0

openlmi-reviews Digest, Vol 2, Issue 8

by openlmi-reviews-request＠lists.fedorahosted.org

Send openlmi-reviews mailing list submissions to openlmi-reviews(a)lists.fedorahosted.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews or, via email, send a message with subject or body 'help' to openlmi-reviews-request(a)lists.fedorahosted.org You can reach the person managing the list at openlmi-reviews-owner(a)lists.fedorahosted.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openlmi-reviews digest..." Today's Topics: 1. Re: Review Request 440: openlmi-networking <indications> [5/5] test: test for lifetime indications (Radek Novacek) 2. Review Request 441: indications [1/3] Account: Indication for creating instances (Roman Rakus) 3. Review Request 442: indications [2/3] Account: Indications. Hack around temporary files. (Roman Rakus) 4. Review Request 443: indications [3/3] Account: Indication for deleting instances (Roman Rakus) 5. Re: Review Request 440: openlmi-networking <indications> [5/5] test: test for lifetime indications (Roman Rakus) 6. Re: Review Request 436: openlmi-networking <indications> [1/5] Fix threading (Roman Rakus) 7. Re: Review Request 441: indications [1/3] Account: Indication for creating instances (Radek Novacek) 8. Re: Review Request 442: indications [2/3] Account: Indications. Hack around temporary files. (Radek Novacek) 9. Re: Review Request 443: indications [3/3] Account: Indication for deleting instances (Radek Novacek) 10. Re: Review Request 437: openlmi-networking <indications> [2/5] IPAssignmentSettingDataEnumInstances cleanup (Roman Rakus) 11. Re: Review Request 438: openlmi-networking <indications> [3/5] Move EnumInstances of port-based classes to common function (Roman Rakus) 12. Re: Review Request 439: openlmi-networking <indications> [4/5] Add Lifetime indication (Jan Synacek) 13. Re: Review Request 439: openlmi-networking <indications> [4/5] Add Lifetime indication (Jan Synacek) 14. Re: Review Request 437: openlmi-networking <indications> [2/5] IPAssignmentSettingDataEnumInstances cleanup (Radek Novacek) 15. Re: Review Request 439: openlmi-networking <indications> [4/5] Add Lifetime indication (Radek Novacek) 16. Re: Review Request 440: openlmi-networking <indications> [5/5] test: test for lifetime indications (Radek Novacek) 17. Re: Review Request 436: openlmi-networking <indications> [1/5] Fix threading (Radek Novacek) 18. Re: Review Request 437: openlmi-networking <indications> [2/5] IPAssignmentSettingDataEnumInstances cleanup (Radek Novacek) 19. Re: Review Request 438: openlmi-networking <indications> [3/5] Move EnumInstances of port-based classes to common function (Radek Novacek) 20. Re: Review Request 439: openlmi-networking <indications> [4/5] Add Lifetime indication (Radek Novacek) 21. Re: Review Request 440: openlmi-networking <indications> [5/5] test: test for lifetime indications (Radek Novacek) 22. Re: Review Request 440: openlmi-networking <indications> [5/5] test: test for lifetime indications (Roman Rakus) 23. Review Request 444: [1/1] Add mounting tests. (Jan Synacek) 24. Review Request 445: openlmi-networking [1/6] test: add test for bridging support (Radek Novacek) 25. Review Request 446: openlmi-networking [2/6] Silence couple of buildtime warnings (Radek Novacek) 26. Review Request 447: openlmi-networking [3/6] test: fix some potential test failures (Radek Novacek) 27. Review Request 448: openlmi-networking [4/6] test: remove calling nmcli from test_object (Radek Novacek) 28. Review Request 449: openlmi-networking [5/6] Handle generic device type properly (Radek Novacek) 29. Review Request 450: openlmi-networking [6/6] Fix referencing LMI_DNSProtocolEndpoint from LMI_IPConfigurationServiceAffectsElementProvider (Radek Novacek) 30. Re: Review Request 426: Account [1/1] Account: Use asprintf instead of snprintf (Roman Rakus) 31. Re: Review Request 426: Account [1/1] Account: Use asprintf instead of snprintf (Roman Rakus) 32. Re: Review Request 443: indications [3/3] Account: Indication for deleting instances (Roman Rakus) 33. Re: Review Request 441: indications [1/3] Account: Indication for creating instances (Roman Rakus) 34. Re: Review Request 442: indications [2/3] Account: Indications. Hack around temporary files. (Roman Rakus) 35. Review Request 451: Clean in account [1/2] Account: Use KReturn2 instead of CMReturnWithChars (Roman Rakus) 36. Review Request 452: Clean in account [2/2] Account: Use asprintf instead of snprintf (Roman Rakus) 37. Re: Review Request 451: Clean in account [1/2] Account: Use KReturn2 instead of CMReturnWithChars (Radek Novacek) 38. Re: Review Request 452: Clean in account [2/2] Account: Use asprintf instead of snprintf (Radek Novacek) 39. Re: Review Request 451: Clean in account [1/2] Account: Use KReturn2 instead of CMReturnWithChars (Roman Rakus) 40. Re: Review Request 452: Clean in account [2/2] Account: Use asprintf instead of snprintf (Roman Rakus) 41. Review Request 457: openlmi-networking [1/1] Fix memory issues, missing unlocks, etc. (Radek Novacek) 42. Re: Review Request 445: openlmi-networking [1/6] test: add test for bridging support (Jan Synacek) 43. Re: Review Request 446: openlmi-networking [2/6] Silence couple of buildtime warnings (Jan Synacek) 44. Re: Review Request 447: openlmi-networking [3/6] test: fix some potential test failures (Jan Synacek) 45. Re: Review Request 448: openlmi-networking [4/6] test: remove calling nmcli from test_object (Jan Synacek) 46. Re: Review Request 449: openlmi-networking [5/6] Handle generic device type properly (Jan Synacek) 47. Re: Review Request 450: openlmi-networking [6/6] Fix referencing LMI_DNSProtocolEndpoint from LMI_IPConfigurationServiceAffectsElementProvider (Jan Synacek) 48. Re: Review Request 457: openlmi-networking [1/1] Fix memory issues, missing unlocks, etc. (Jan Synacek) 49. Re: Review Request 445: openlmi-networking [1/6] test: add test for bridging support (Radek Novacek) 50. Re: Review Request 446: openlmi-networking [2/6] Silence couple of buildtime warnings (Radek Novacek) 51. Re: Review Request 447: openlmi-networking [3/6] test: fix some potential test failures (Radek Novacek) 52. Re: Review Request 448: openlmi-networking [4/6] test: remove calling nmcli from test_object (Radek Novacek) 53. Re: Review Request 449: openlmi-networking [5/6] Handle generic device type properly (Radek Novacek) 54. Re: Review Request 450: openlmi-networking [6/6] Fix referencing LMI_DNSProtocolEndpoint from LMI_IPConfigurationServiceAffectsElementProvider (Radek Novacek) 55. Re: Review Request 457: openlmi-networking [1/1] Fix memory issues, missing unlocks, etc. (Radek Novacek) 56. Review Request 458: prototype CIM<->PCP bridge (Frank Eigler) 57. Review Request 459: openlmi-networking [1/1] Fix compilation with NM 0.9.9 (Radek Novacek) 58. Re: Review Request 459: openlmi-networking [1/1] Fix compilation with NM 0.9.9 (Jan Synacek) 59. Re: Review Request 459: openlmi-networking [1/1] Fix compilation with NM 0.9.9 (Radek Novacek) 60. Re: Review Request 458: prototype CIM<->PCP bridge (Roman Rakus) 61. Re: Review Request 458: prototype CIM<->PCP bridge (Roman Rakus) 62. Re: Review Request 298: fix embedded instances class, namespace members (Peter Hatina) 63. Review Request 461: lmishell, properties access (Peter Hatina) 64. Re: Review Request 461: lmishell, properties access (Stephen Gallagher) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

11 years

1
0
0 / 0

writing mof file

by George varghese

Hi, Using the tutorial for writing a new mof file, https://fedorahosted.org/openlmi/wiki/ProviderTutorialImplementationC For generating C skeleton, KONKRET_SCHEMA_DIR*=*/usr/share/sfcb/CIM konkret -m tutorial.mof TUT_UnixProcess TUT_ProcessChild After executing this command, created only .h files. not created TUT_UnixProcessProvider.c, TUT_ProcessChildProvider.c What can I do for creating provider files? Please note that konkret version is 0.9.0 Regards, George

11 years

2
1
0 / 0

ANNOUNCE: openlmi-networking-0.0.9

by Radek Novacek

New version of openlmi-networking just came to life: 0.0.9 New in this version: * Bridge/bond support * LifeTime indications for LMI_IPAssignmentSettingData and LMI_IPNetworkConnection classes You can grab it here: https://fedorahosted.org/released/openlmi-networking/openlmi-networking-0... Radek Novacek

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

openlmi-devel June 2013