On 05/10/2012 02:14 PM, Loic Dachary wrote:
Hi,
The metering project team holds a meeting in #openstack-meeting, Thursdays at
1600 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?hour=16min=0sec=0.
Everyone is welcome.
I propose an agenda based on the discussions we had on this list.
http://wiki.openstack.org/Meetings/MeteringAgenda
Topic: external API definition
* API defaults and API extensions
* API extension
* extension= loads the python module
* method query is called with the
* QUERY_STRING
* a handler to the storage
* a pointer to the configuration
* API calls common arguments
* Datetime range : start and end
* Transparent cache for aggregation
* API defaults http://wiki.openstack.org/EfficientMetering#API
* GET list components
* GET list components meters (argument : name of the component)
* GET list accounts
* GET list of meter_type
* GET list of events per account
* GET sum of (meter_volume, meter_duration) for meter_type and account_id
* other ?
* open discussion
For the record. There were too many issues raised during the meeting to agree
on the API. Instead, another meeting was scheduled and the agenda calendar
postponed for a week.
http://wiki.openstack.org/Meetings/MeteringAgenda?action=diffrev2=20rev1=19
==
#openstack-meeting Meeting
==
Meeting started by dachary at 16:00:22 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html
.
Meeting summary
---
* LINK: https://lists.launchpad.net/openstack/msg11523.html (dachary,
16:00:22)
* actions from previous meetings (dachary, 16:00:22)
* LINK:
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-03-16.00.html
(dachary, 16:00:22)
* dachary removed obsolete comment about floating IP
http://wiki.openstack.org/EfficientMetering?action=diffrev2=70rev1=69
(dachary, 16:00:22)
* dachary o6 : note that the resource_id is the container id.
http://wiki.openstack.org/EfficientMetering?action=diffrev2=71rev1=70
(dachary, 16:00:23)
* The discussion about adding the source notion to the schema took
place on the mailing list
https://lists.launchpad.net/openstack/msg11217.html (nijaba,
16:01:25)
* The conclusion was to add a source field to the event record, but no
additional record type to list existing sources. (nijaba, 16:01:25)
* jd___ add Swift counters, add resource ID info in counter
definition, describe the table
http://wiki.openstack.org/EfficientMetering?action=diffrev2=57rev1=54
(jd___, 16:03:08)
* meeting organisation (dachary, 16:04:37)
* This is 2/5 meetings to decide the details of the architecture of
the Metering project https://launchpad.net/ceilometer (dachary,
16:04:37)
* Today's focus is on the definition of external REST API (dachary,
16:04:37)
* There has not been enough discussions on the list to cover all
aspects and the focus of this meeting was modified to cope with it.
(dachary, 16:04:37)
* The meeting is time boxed and there will not be enough time to
introduce inovative ideas and research for solutions. (dachary,
16:04:37)
* The debate will be about the pro and cons of the options already
discussed on the mailing list. (dachary, 16:04:38)
* LINK: https://lists.launchpad.net/openstack/msg11368.html (dachary,
16:04:38)
* API defaults and API extensions (dachary, 16:05:28)
* AGREED: Ceilometer shouldn't invent its own API extensions
mechanism... it should use the system in Nova. (dachary, 16:09:20)
* LINK: https://github.com/cloudbuilders/openstack-munin (dachary,
16:10:18)
* LINK: https://github.com/sileht/openstack-munin (dachary, 16:10:23)
* ACTION: dachary add info to the wiki on the topic of poll versus
push (dachary, 16:12:17)
* API defaults (dachary, 16:13:08)
* GET list components (dachary, 16:13:14)
* GET list components meters (argument : name of the component)
(dachary, 16:13:14)
* GET list [user_id|project_id|source] (dachary, 16:13:14)
* GET list of meter_type (dachary, 16:13:14)
* GET list of events per [user_id|project_id|source] ( allow to
specify user_id or project_id (dachary, 16:13:14)
* GET sum of (meter_volume, meter_duration) for meter_type and
[user_id|project_id|source] (dachary, 16:13:15)
* other ? (dachary, 16:13:16)
* GET list of events per user_id project_id (dachary, 16:14:20)
* LINK: http://wiki.openstack.org/OpenStackRESTAPI (dachary,
16:15:48)
* LINK: http://wiki.openstack.org/EfficientMetering#Meters (dachary,
16:16:48)
* LINK: http://wiki.openstack.org/EfficientMetering#API (nijaba,
16:23:45)
* AGREED: all meters have a [start,end[ ( start = timestamp end )
that limits the returned result
