[openstack-dev] [ceilometer] zombie process after ceilometer-api
Hi, I see a zombie process left out by ceilometer-api after a client command like "ceilometer meter-list". This seems to occur only when I change the number of workers for [api] section in ceilometer.conf to 2 or more. With default value of workers = 1, there is no zombie. Has anybody encountered this problem ? OR is there already a bug to tackle this ? Thanks, Madhu Mohan __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ceilometer] zombie process after ceilometer-api
Here is the output of "ps aux | grep ceilometer-api" after "ceilometer meter-list" ceilome+ 27192 1.0 1.1 247400 60388 ?Ss 14:10 0:00 /usr/bin/python /usr/bin/ceilometer-api --config-file=/etc/ceilometer/ceilometer.conf --logfile=/var/log/ceilometer/api.log ceilome+ 27655 15.3 0.0 0 0 ?Z14:11 0:00 [ceilometer-api] Its the second line I am concerned about. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-dev[[Congress]
Hi Congress Team, Has anyone tried writing policies with Builtin operators like gt(), lt(). I see the class CongressBuiltinCategoryMap() to add/update the start map defined in the same file. However, these classes are never referred in any part of the code. So clearly, I can assume Congress does not support such operators at this point Is there a plan to implement this feature or someone looking into it already ? Thanks and Regards, Madhu Mohan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Ramp-up strategy
Hi, Since a few weeks I am trying to get a hold on Congress code base and understand the flow. Here is a brief summary what I am trying out: Prepared a dummy client to send the policy strings to congress_server listening at the path /policies. This is now changed to v1/policies. I am using POST request to send the policy string to the server. The call to server somehow seems to get converted to an action with the name create_policies Added a new API create_policies in the api model policy_model.py which gets the policy string in params. I am able to call compile.parse() and runtime.initialize() functions from this API. The compilation produces a result in the format below: *Rule(head=[Literal(table=u'error', arguments=[Variable(name=u'vm')], negated=False)], body=[Literal(table=u'nova:virtual_machine', arguments=[Variable(name=u'vm')],. * I am not really sure about how to go about from here to see the policies actually getting applied and monitored. Any resource or instructions on getting through the code flow will be of great help to proceed further. Thanks in Advance, Madhu Mohan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Policy Enforcement logic
Hi, I am quite new to the Congress and Openstack as well and this question may seem very trivial and basic. I am trying to figure out the policy enforcement logic, Can some body help me understand how exactly, a policy enforcement action is taken. From the example policy there is an action defined as: *action(disconnect_network)nova:network-(vm, network) :- disconnect_network(vm, network) * I assume that this statement when applied would translate to deletion of entry in the database. But, how does this affect the actual setup (i.e) How is this database update translated to actual disconnection of the VM from the network. How does nova know that it has to disconnect the VM from the network ? Thanks and Regards, Madhu Mohan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Help in understanding API Flow
Hi,
Can some one help me understand how an API is exposed to the clients from
Congress server ?
I see that a cage service ('api-policy') is created in congress_server.py.
I believe this is implemented in policy_model. I tried to send a
json_request from my client on the server.
I tried sending list_members, get_items, PUT and POST as methods
and all these give me NotImplemented error response.
Any help in this direction ?
I also want to add new APIs and hence understanding the API flow is crucial.
Thanks,
Madhu Mohan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress]Congress API model
Hi, I am building a congress-based demo and setting up server exposed as API. Can somebody clarify a couple of my questions: 1. What is the port that is planned to be used for Congress to listen to API calls ? 2. What is the Web Framework model that is planned to be adapted (Pecan/WSME) does it follow the OSAPI model from Nova ? Thanks, Madhu Mohan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Integration Demo
Hi All, I have been working on integrating developing a policy demo using Congress. I have done following activities in this direction - Integrated Congress as a service with keystone - Developed a trivial Python-Congressclient with support for basic commands through command line - Integrated congress and python-congressclient into devstack To verify the integration, I am using the example policy files (VM Grouping policy) as input and trying to see the policies being written to the Congress tables and the Data source tables. Could some one help me out understand what are the other missing parts to get this integration working ? What needs to be implemented from the Congress server side ? I am particularly interested in Contributing to all areas of Congress including policy definition, enforcement and also have special interests in run-time optimization, high-availability use-cases. Any guidance would be of utmost help. Thanks and Regards, Madhu Mohan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Error running scripts/run_api_server
Hi,
I recently cloned the latest Congress source code and tried to run
unit-tests on my Ubuntu PC. Using *scripts/run_api_server*, I found this
following error:
*Jun 20 11:28:11|0|__main__|INFO|Starting congress server*
*Traceback (most recent call last):*
* File /usr/lib/python2.7/dist-packages/eventlet/greenpool.py, line 80,
in _spawn_n_impl*
*func(*args, **kwargs)*
* File server.py, line 82, in ad_update_thread*
*ad_model.update_from_ad() # XXX: blocks eventlet*
* File /home/madhu/Project/policyFW/congress/congress/server/ad_sync.py,
line 72, in update_from_ad*
*l.simple_bind_s(BIND_USER, BIND_PW)*
* File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 206, in
simple_bind_s*
*msgid = self.simple_bind(who,cred,serverctrls,clientctrls)*
* File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 200, in
simple_bind*
*return
self._ldap_call(self._l.simple_bind,who,cred,EncodeControlTuples(serverctrls),EncodeControlTuples(clientctrls))*
* File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 96, in
_ldap_call*
*result = func(*args,**kwargs)*
*SERVER_DOWN: {'desc': Can't contact LDAP server}*
*(5065) wsgi starting up on http://0.0.0.0:8080/ http://0.0.0.0:8080/*
Does other guys face this error too ?
Am i missing any prerequisite to run the congress unit-test ?
make was successful and had no issues.
Please suggest a way to proceed further.
Thanks and Regards,
Madhu Mohan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
