Re: [Openstack] Enabling remote participation at Folsom Design Summit

The PSF has had fairly good luck with Ustream for our members' meetings. They are 1-way, though, so questions or comments from remote participants have to be relayed by someone in the room (we used IRC). On Thu, Mar 22, 2012 at 1:44 AM, Marton Kiss wrote: > Ustream broadcast as an alternative op

Re: [Openstack] Being pedantic about pedanticism: HACKING styleguide

Why are those sorts of instructions replicated in each project in the first place? Shouldn't they be in the wiki? On Thu, Mar 22, 2012 at 12:22 PM, Andrew Bogott wrote: >Just now I set out to merge a recent style guide change from > python-novaclient into the hacking docs of other OpenStack p

Re: [Openstack] Being pedantic about pedanticism: HACKING styleguide

On Thu, Mar 22, 2012 at 4:22 PM, Jay Pipes wrote: > On 03/22/2012 01:47 PM, Doug Hellmann wrote: > >> Why are those sorts of instructions replicated in each project in the >> first place? Shouldn't they be in the wiki? >> > > :) Have you ever tried to get a do

Re: [Openstack] ESXi documentation..

ink is dead: http://nova.openstack.org/vmwareapi_readme.html >> >> Does anyone have any links that might help in this endeavor? >> >> thanks! >> > > > Hi Mike: > > That link was killed by this commit authored by Doug Hellmann about a month >

Re: [Openstack] ESXi documentation..

gt; Take care, > > Lorin > -- > Lorin Hochstein > Lead Architect - Cloud Services > Nimbis Services, Inc. > www.nimbisservices.com > > > > > > On Apr 4, 2012, at 1:43 PM, Doug Hellmann wrote: > >> I think it was because it was not linked from an

Re: [Openstack] Agreeing a common set of Image Properties

On Sat, Apr 7, 2012 at 6:13 PM, Justin Santa Barbara wrote: > Is there a (de-facto) standard for image metadata/properties? I'd like to > be able to able to launch e.g. the Debian Squeeze image provided by the > cloud. This is particularly important for clouds that don't allow image > upload, bu

Re: [Openstack] Agreeing a common set of Image Properties

On Mon, Apr 9, 2012 at 12:40 PM, Justin Santa Barbara wrote: > On Mon, Apr 9, 2012 at 8:18 AM, Doug Hellmann > wrote: > >> I'm thinking of the os prefix as standing for OpenStack, not Operating >>> System. >>> >> >> I would never have guessed

Re: [Openstack] Image API v2 Draft 4

On Mon, Apr 9, 2012 at 5:14 PM, Justin Santa Barbara wrote: > When you're designing JSON considering only JSON, you'd probably use { >>> >> key1: value1 } - as you have done. If you're designing generically, >>> you'd probably use { key: key1, value: value1 }. >>> >> >> You mean we'd have to do d

Re: [Openstack] Image API v2 Draft 4

Nova had (and hopefully moving > it to openstack-common before bringing the code into Glance). > > Best, > -jay > > > On 04/10/2012 06:51 AM, Doug Hellmann wrote: > >> >> >> On Mon, Apr 9, 2012 at 5:14 PM, Justin Santa Barbara >> mailto:jus...@fat

Re: [Openstack] Just JSON, and extensibility

On Fri, Apr 13, 2012 at 4:20 PM, Justin Santa Barbara wrote: > I don't think that works for non-linear extensibility... > > I would be very happy if we could agree out how we're going to deal with > extensibility in JSON. It is easy to support XML & JSON & any future > formats, and have them all

Re: [Openstack] Just JSON, and extensibility

On Sat, Apr 14, 2012 at 10:46 AM, Justin Santa Barbara wrote: > >>>- Each (known) extension has its own strongly-typed model object. >>> >>> >> Does that mean that an extension cannot add properties to an existing >> object (such as adding a new attribute an Image), or just that all of those >

Re: [Openstack] OpenStack Client Followup

On Wed, Apr 18, 2012 at 11:07 PM, Dean Troyer wrote: > We had a good discussion about a unified OpenStack command line client > on Monday at the Design Summit. The notes are in the Etherpad at > http://etherpad.openstack.org/FolsumCLI, I summarized my recollection > at the bottom; those who were

Re: [Openstack] Python UUID and SELinux AVC denials

Have you tried changing Dashboard to monkey patch the uuid module to blank out the functions being loaded from ctypes? If the _uuid_generate_* functions are not set, the existing python implementation is used instead and it looks like that just uses urandom() inline. On Thu, Apr 19, 2012 at 11:53

Re: [Openstack] Python UUID and SELinux AVC denials

On Sun, Apr 22, 2012 at 1:49 PM, Adam Young wrote: > On 04/20/2012 11:51 AM, Doug Hellmann wrote: > > Have you tried changing Dashboard to monkey patch the uuid module to blank > out the functions being loaded from ctypes? If the _uuid_generate_* > functions are not set, the

Re: [Openstack] Canonical AWSOME

On Mon, Apr 23, 2012 at 8:39 AM, Thierry Carrez wrote: > Philipp Wollermann wrote: > > What's the advantage of replacing the native EC2 compatibility layer > with AWSOME from a user / operator point of view? > > One thing that was mentioned is that the proxy could be run on top of a > public cloud

Re: [Openstack] [Keystone] What exactly are we modeling with endpoints?

On Fri, Apr 20, 2012 at 5:15 PM, Joseph Heck wrote: > While I've been roaming about the summit and conference, I've been trying > to figure out exactly what we're modeling with the current "service" and > "endpoints" that are in the API today. After talking with a number of > folks, it's getting

Re: [Openstack] HTTP status value naming normalization

This sounds like a good candidate to live in openstack-common, rather than being limited to Swift. On Sat, Apr 21, 2012 at 12:22 PM, John Dickinson wrote: > I like what you are trying to do here. Can you please submit this as a > patch through gerrit so we can get the rest of the core devs to lo

Re: [Openstack] Monitoring / Billing Architecture proposed

On Sun, Apr 22, 2012 at 5:29 PM, Brian Schott < brian.sch...@nimbisservices.com> wrote: > Dough is a proposed billing service. There was a session at Folsom design > summit. This is a practical project for an OpenStack provider with test > code on github. > http://summit.openstack.org/sessions/v

Re: [Openstack] Canonical AWSOME

Martin Packman mentioned that there are some other groups interested in creating a separate AWS validation test suite, and that AWSOME would probably be using that. I think Joshua Harlow from Yahoo! was working in that area, too. On Mon, Apr 23, 2012 at 1:38 PM, Joshua Harlow wrote: > We just ha

Re: [Openstack] Monitoring / Billing Architecture proposed

On Mon, Apr 23, 2012 at 1:50 PM, Brian Schott < brian.sch...@nimbisservices.com> wrote: > So, we could build on this. No reason to reinvent, but we might want to > expand the number of events. I'm concerned about things like what happens > when flavors change over time. Maybe the answer is, alwa

Re: [Openstack] [quantum] summit slides for clearpath service insertion

It would also be helpful for us newbies if you add your (full) name as session leader. I have first names and faces for a lot of people, but there are quite a few duplicate first names on the lists. Thanks! Doug On Mon, Apr 23, 2012 at 1:58 PM, Dan Wendlandt wrote: > Adding Peter, who gave that

Re: [Openstack] Monitoring / Billing Architecture proposed

services.com > ph: 443-274-6064 fx: 443-274-6060 > > > > On Apr 23, 2012, at 3:23 PM, Doug Hellmann wrote: > > > > On Mon, Apr 23, 2012 at 1:50 PM, Brian Schott < > brian.sch...@nimbisservices.com> wrote: > >> So, we could build on this. No reason t

Re: [Openstack] Using Foreign Keys

On Wed, Apr 25, 2012 at 7:38 AM, Andrew Hutchings wrote: > On 12/04/12 13:35, J. Daniel Schmidt wrote: > > While testing our SUSE OpenStack packages we hit a nasty bug and > reported it > > as: https://bugs.launchpad.net/keystone/+bug/972502 > > > > We found out that the underlying cause was a la

Re: [Openstack] Using Foreign Keys

e integer keys (if the reference is still needed at all). > > > Vish > > On Apr 25, 2012, at 11:02 AM, Doug Hellmann wrote: > > > > On Wed, Apr 25, 2012 at 7:38 AM, Andrew Hutchings > wrote: > >> On 12/04/12 13:35, J. Daniel Schmidt wrote: >&g

Re: [Openstack] db & notification support for API extension?

On Wed, Apr 25, 2012 at 6:04 PM, Andrew Bogott wrote: > On 4/25/12 4:48 PM, Nathanael Burton wrote: > >> On Thu, Mar 8, 2012 at 11:53 AM, Andrew Bogott >> wrote: >> >>>I'm working on an API and implementation to support the creation of >>> filesystems that are shared among Nova instances. >>>

Re: [Openstack] [Metering] schema and counter definitions

On Mon, Apr 30, 2012 at 6:46 AM, Loic Dachary wrote: > On 04/30/2012 12:15 PM, Loic Dachary wrote: > > We could start a discussion from the content of the following sections: > > > > http://wiki.openstack.org/EfficientMetering#Counters > I think the rationale of the counter aggregation needs to b

Re: [Openstack] [Metering] schema and counter definitions

On Mon, Apr 30, 2012 at 11:43 AM, Loic Dachary wrote: > On 04/30/2012 03:49 PM, Doug Hellmann wrote: > > > > On Mon, Apr 30, 2012 at 6:46 AM, Loic Dachary wrote: > >> On 04/30/2012 12:15 PM, Loic Dachary wrote: >> > We could start a discussion from the

Re: [Openstack] OpenStack Client Followup

On Mon, Apr 30, 2012 at 12:13 PM, Adam Spiers wrote: > Dean Troyer (dtro...@gmail.com) wrote: > > One of the first things to do is to find out who is interested in > > contributing to this project.and hopefully coordinating some of the > > work with the other emerging project-specific clients. S

Re: [Openstack] OpenStack Client Followup

On Mon, Apr 30, 2012 at 2:56 PM, Dean Troyer wrote: > On Mon, Apr 30, 2012 at 1:18 PM, Doug Hellmann > wrote: > > Running a cliff-based app without any arguments enters "interactive" mode > > (as of 0.4) which gives the user a new prompt and lets them run multiple

Re: [Openstack] OpenStack Client Followup

On Mon, Apr 30, 2012 at 3:19 PM, Dolph Mathews wrote: > > > On Mon, Apr 30, 2012 at 1:18 PM, Doug Hellmann < > doug.hellm...@dreamhost.com> wrote: > >> >> >> On Mon, Apr 30, 2012 at 12:13 PM, Adam Spiers wrote: >> >>> Dean Troyer (dtro...@gm

Re: [Openstack] OpenStack Client Followup

On Mon, Apr 30, 2012 at 3:27 PM, Dean Troyer wrote: > On Mon, Apr 30, 2012 at 2:19 PM, Dolph Mathews > wrote: > > I find this behavior really annoying... --help should be contextual > > (depending on whether a subcommand is present, and what it is). > > > I hope not... +1 for argparse. > > Actua

Re: [Openstack] [Metering] schema and counter definitions

On Mon, Apr 30, 2012 at 3:43 PM, Loic Dachary wrote: > On 04/30/2012 08:03 PM, Doug Hellmann wrote: > > > > On Mon, Apr 30, 2012 at 11:43 AM, Loic Dachary wrote: > >> On 04/30/2012 03:49 PM, Doug Hellmann wrote: >> >> >> >> On Mon, Apr 30, 20

Re: [Openstack] [Metering] schema and counter definitions

On Tue, May 1, 2012 at 10:38 AM, Nick Barcet wrote: > On 05/01/2012 02:23 AM, Loic Dachary wrote: > > On 04/30/2012 11:39 PM, Doug Hellmann wrote: > >> > >> > >> On Mon, Apr 30, 2012 at 3:43 PM, Loic Dachary >> <mailto:l...@enovance.com>>

Re: [Openstack] [Metering] schema and counter definitions

On Tue, May 1, 2012 at 11:49 AM, Doug Hellmann wrote: > > > On Tue, May 1, 2012 at 10:38 AM, Nick Barcet wrote: > >> On 05/01/2012 02:23 AM, Loic Dachary wrote: >> > On 04/30/2012 11:39 PM, Doug Hellmann wrote: >> >> >> >> >> >&g

Re: [Openstack] OpenStack Client Followup

On Tue, May 1, 2012 at 1:54 PM, Adam Spiers wrote: > Matt Joyce (m...@nycresistor.com) wrote: > > > 3. I think it would be good if the HIG recommended that, at least > > > when subcommands are permitted, single arguments '--help' and > > > 'help' always generate identical output: > > > >

Re: [Openstack] [client] OpenStack Client Followup

On Tue, May 1, 2012 at 2:35 PM, Adam Spiers wrote: > Doug Hellmann (doug.hellm...@dreamhost.com) wrote: > > On Mon, Apr 30, 2012 at 12:13 PM, Adam Spiers wrote: > > > > > Dean Troyer (dtro...@gmail.com) wrote: > > > > One of the first things to do

Re: [Openstack] [client] OpenStack Client Followup

On Tue, May 1, 2012 at 3:36 PM, Matt Joyce wrote: > On Tue, May 1, 2012 at 11:49 AM, Adam Spiers wrote: > > Doug Hellmann (doug.hellm...@dreamhost.com) wrote: > >> On Mon, Apr 30, 2012 at 2:56 PM, Dean Troyer wrote: > >> > On Mon, Apr 30, 2012 at 1:18 P

[Openstack] [client] creating blueprints for the unified CLI project

I have started creating blueprints from my notes about activities we need to complete for the unified CLI. Please check the list at https://blueprints.launchpad.net/python-openstackclient/ and make sure I haven't missed anything that has been discussed so far, and open a blueprint if I have. Thank

Re: [Openstack] [client] creating blueprints for the unified CLI project

ur use case? > > Maybe just ignore that question until we've got something beyond the > basics. > > -Matt > > On Tue, May 1, 2012 at 4:34 PM, Matt Joyce wrote: > > Awesome. will do. > > > > On Tue, May 1, 2012 at 1:47 PM, Doug Hellmann > > wrote

Re: [Openstack] OpenStack Client Followup

There are a couple of ways to handle that: 1. A separate "openstackadmin" CLI that looks for commands using a different plugin namespace, and therefore only loads the admin commands. 2. Prefix admin-related commands in the unified cli with "admin" (so "openstack admin create network" or whatever)

Re: [Openstack] [client] creating blueprints for the unified CLI project

age by default when executing > without parameters? Or do we want a flag to engage that ( people can > alias on their own if they want ). > > -Matt > > On Tue, May 1, 2012 at 4:52 PM, Doug Hellmann > wrote: > > I borrowed Guido's time machine and added a

Re: [Openstack] [client] creating blueprints for the unified CLI project

On Wed, May 2, 2012 at 10:39 AM, Adam Spiers wrote: > Doug Hellmann (doug.hellm...@dreamhost.com) wrote: > > I have started creating blueprints from my notes about activities we need > > to complete for the unified CLI. Please check the list at > > https://blueprints

Re: [Openstack] OpenStack Client Followup

On Wed, May 2, 2012 at 10:40 AM, Adam Spiers wrote: > Dean Troyer (dtro...@gmail.com) wrote: > > On Tue, May 1, 2012 at 12:54 PM, Adam Spiers wrote: > > > Agreed - while server-side auditing is a more important component than > > > client-side, having both sounds potentially useful to me too. A

Re: [Openstack] [client] Where will client API libraries live?

On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein wrote: > (Apologies if this has been already answered in the mailing list, dealing > with a large backlog of mailing list emails). > > With the current "nova" client (python-novaclient), there are Python > bindings so you can write Python scripts th

Re: [Openstack] [client] final openstackclient binary name

Oops, I saw the code change before this message and I went ahead and approved it. On Wed, May 2, 2012 at 10:59 AM, Dean Troyer wrote: > There has been a little more activity in the discussion in > http://etherpad.openstack.org/FolsumCLI this week regarding the name > of the python-openstackclien

Re: [Openstack] [Openstack-operators] OpenStack Client Followup

the > >>> remote service that's ultimately going to enforce it's own policies. > It may > >>> be a decent feature to warn the user something is probably not going > to work > >>> (or better yet, the ability to ask the remote service if something will >

Re: [Openstack] OpenStack Client Followup

On Wed, May 2, 2012 at 1:23 PM, Adam Spiers wrote: > Dean Troyer (dtro...@gmail.com) wrote: > > On Tue, May 1, 2012 at 2:11 PM, Adam Spiers wrote: > > > As of my recent patch, --help is contextual in nova: > > > > I hadn't seen that yet... > > > > > and I have started work on some of the other c

Re: [Openstack] OpenStack Client Followup

On Wed, May 2, 2012 at 6:01 PM, Doug Hellmann wrote: > > > On Wed, May 2, 2012 at 1:23 PM, Adam Spiers wrote: > >> Dean Troyer (dtro...@gmail.com) wrote: >> > On Tue, May 1, 2012 at 2:11 PM, Adam Spiers wrote: >> > > As of my recent patch, --help is cont

Re: [Openstack] [client] Where will client API libraries live?

On Wed, May 2, 2012 at 1:34 PM, Lorin Hochstein wrote: > > On May 2, 2012, at 11:30 AM, Doug Hellmann wrote: > > > > On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein > wrote: > >> (Apologies if this has been already answered in the mailing list, dealing >>

Re: [Openstack] Metering question??

On Wed, May 2, 2012 at 2:31 PM, Joshua Harlow wrote: > Hi all, > > I was just looking over the efficient metering stuff yesterday. > > Just a couple of questions, that might be dups (sorry if they are). > > I am noticing that there seems to be a mix of billing specifics there and > metering speci

[Openstack] [metering] interesting notes on billing issues with Azure

Via @jessenoller: http://www.nasuni.com/blog/177-azure_fair_and_balanced ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net

Re: [Openstack] Glance store question??

Andrew is doing some work on a plugin architecture. This sounds like another good application of that. On Wed, May 2, 2012 at 7:01 PM, Joshua Harlow wrote: > Right, if there isn’t that existing, then I think I might just make a > blueprint out of that. I just wanted to check beforehand that I am

Re: [Openstack] [Metering] how should it be done ? ( Was: schema and counter definitions)

On Thu, May 3, 2012 at 11:59 AM, Loic Dachary wrote: > On 05/03/2012 09:58 AM, Robert Collins wrote: > > On Wed, May 2, 2012 at 10:28 AM, Loic Dachary wrote: > > > >> As I wrote in a previous mail, once we manage to provide an > implementation that proves useful, we will be in a position to appr

Re: [Openstack] [QA] Tempest Devstack/Jenkins gate job now passing

+1000 On Fri, May 4, 2012 at 11:30 AM, Daryl Walleck wrote: > This is great news! Thanks Jay for all the hard work you've put into > getting this up and running. > > Daryl > > On May 4, 2012, at 8:34 AM, Jay Pipes wrote: > > > All, > > > > A momentous event has occurred. We now have all Tempest

Re: [Openstack] [Swift][Keystone] Swift Quotas

On Fri, May 4, 2012 at 12:02 PM, Jay Pipes wrote: > On 05/04/2012 10:14 AM, Rouault, Jason (Cloud Services) wrote: > >> IMHO, if it is a quota related to a tenant or user, then managing it in >> Keystone makes sense. >> > > I think, as Eoghan mentioned, there was pretty broad agreement that > *st

Re: [Openstack] [Metering] how should it be done ? ( Was: schema and counter definitions)

On Fri, May 4, 2012 at 4:51 PM, Christopher MacGown wrote: > > Do you envision that writing to AMQP directly, or using the existing > notification API (which seems to be a wrapper over the RPC layer, which is > in turn a wrapper for AMQP)? > > > The RPC layer is not merely a wrapper for AMQP, in a

Re: [Openstack] [Metering] Adding a source notion to the schema

On Fri, May 4, 2012 at 12:29 PM, Nick Barcet wrote: > Following up on the discussion on IRC yesterday during the metering > meeting, I'd like to explain my proposal to add the notion of source to the > schema of our event. The current goal we have for ceilometer is to provide > a common way to ac

Re: [Openstack] [Nova] EC2 api testing

On Fri, May 4, 2012 at 1:09 PM, Martin Packman wrote: > At the Folsom Design Summit we discussed[1] trying to collaborate on a > test suite for EC2 api support. Currently nova supports the common > stuff pretty well has differing behaviour in a lot of edge cases. > Having a separate suite, along

Re: [Openstack] [Metering] Adding a source notion to the schema

On Fri, May 4, 2012 at 6:03 PM, Nick Barcet wrote: > On 05/04/2012 02:25 PM, Doug Hellmann wrote: > > > > > > On Fri, May 4, 2012 at 12:29 PM, Nick Barcet > <mailto:nick.bar...@canonical.com>> wrote: > > > > Following up on the discussion on IRC

Re: [Openstack] Moving nova.rpc into openstack.common

The metering project will probably want to take advantage of this work. How far along is it, and how can we help? On Fri, Apr 6, 2012 at 6:56 AM, Swaminathan Venkataraman < venkat...@gmail.com> wrote: > Hi, > I've created a blueprint for this. Please take a look and let me know your > comments. >

Re: [Openstack] [Metering] External API definition

On Tue, May 8, 2012 at 11:27 AM, Nick Barcet wrote: > Hello, > > The 3rd meeting of the Ceilometer project will be held on May 10th at > 1600 UTC in the #openstack-meeting channel on Freenode. The main subject > we will be tackling this week is the external API definition and I'd > like to gather

[Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

I'm working on some code to monitor notification messages coming from nova by listening directly on the AMQP queue. Unfortunately, nova is using a topic exchange so it seems I can't safely consume the messages or they might not go to some other client that is expecting to see them (especially some

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

On Tue, May 8, 2012 at 5:45 PM, Russell Bryant wrote: > On 05/08/2012 04:19 PM, Doug Hellmann wrote: > > I'm working on some code to monitor notification messages coming from > > nova by listening directly on the AMQP queue. Unfortunately, nova is > > using a topic ex

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

On Tue, May 8, 2012 at 6:04 PM, Russell Bryant wrote: > On 05/08/2012 05:59 PM, Doug Hellmann wrote: > > Here is a relevant section pulled out of the amqp 0-9-1 spec: > > > >3.1.3.3 The Topic Exchange Type > > > >The topic exchange type works

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

help, Doug > > On May 8, 2012, at 3:19 PM, Doug Hellmann wrote: > > > I'm working on some code to monitor notification messages coming from > nova by listening directly on the AMQP queue. Unfortunately, nova is using > a topic exchange so it seems I can't safely consume

Re: [Openstack] ceilometer (java implementation)

On Tue, May 8, 2012 at 7:19 PM, Luis Gervaso wrote: > Hi, > > I have uploaded a toy version of ceilometer (java implementation). > > It does implement the first two counters (instance : rabbitmq listener and > cpu : polling from libvirt) > > i need more clarification on the meaining: > > counter_

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

all need to create separate “ >> notifications.info” queues into that exchange.And isn’t that exactly >> what Nova currently does to create a shared queue ? >> >> ** ** >> >> Phil >> >> ** ** >> >> *From:* Kiall Mac Innes [mailto:ki...@managedit.ie

Re: [Openstack] [Metering] External API definition

On Tue, May 8, 2012 at 8:43 PM, Nick Barcet wrote: > On 05/08/2012 11:39 AM, Doug Hellmann wrote: > [..] > > * Requests must be authenticated (separate from keystone, or only > linked > > to accounting type account) > > > > > > What is the motiv

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

What is the difference between review.stackforge.org and review.openstack.org and why aren't we using the latter? On Wed, May 9, 2012 at 11:13 AM, Julien Danjou wrote: > Hi there, > > I've added a first script that's able to connect to the AMQP > notification queue using Nova RPC module. Later it

Re: [Openstack] [Metering] External API definition

On Wed, May 9, 2012 at 11:27 AM, Nick Barcet wrote: > On 05/08/2012 08:27 AM, Nick Barcet wrote: > [..] > > Thinking about this, I think we need to expend the API a bit to reflect > the evolutions of the schema that we decided last week. Here are my > proposals: > > > * Requests allow to > > GE

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

o StackForge as long as it is related to > OpenStack in some way. > > > > 2012/5/9 Doug Hellmann : > > What is the difference between review.stackforge.org and > > review.openstack.org and why aren't we using the latter? > > > > > > On Wed, May

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

a.conf. > > ## (ListOpt) AMQP topic used for Nova notifications > notification_topics="notifications,metering,monitoring" > > This will allow you to consume all the messages from a different service. > > On Wed, May 9, 2012 at 10:34 AM, Doug Hellmann < > doug.hellm...@dre

Re: [Openstack] [Metering] schema and counter definitions

On Wed, May 9, 2012 at 12:42 PM, Tomasz Paszkowski wrote: > Here is the simplified version of my code (without ampq support, > counter stored directly to mysql db). > > https://github.com/ss7pro/rescnt > > Code is started from main.py which is constantly collecting counters > from libvirt and sto

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

topics are more powerful and handy to use than fanout. > Now that I see how it works, I agree. :-) > > > > On Wed, May 9, 2012 at 6:34 PM, Doug Hellmann > wrote: > >> >> >> On Wed, May 9, 2012 at 6:42 AM, Kiall Mac Innes wrote: >> >>> Kinda! The queue h

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

On Wed, May 9, 2012 at 11:13 AM, Julien Danjou wrote: > Hi there, > > I've added a first script that's able to connect to the AMQP > notification queue using Nova RPC module. Later it will be able to treat > them when we'll know what to do with them. > > https://review.stackforge.org/#/c/26/ > h

Re: [Openstack] [Metering] schema and counter definitions

On Wed, May 9, 2012 at 3:07 PM, Tomasz Paszkowski wrote: > On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann > wrote: > > > > Nice! > > > > For production code I think we are going to want to separate collection > from > > storage, aren't we? We don&#

Re: [Openstack] [Metering] Meeting agenda for today 16:00 UTC (May 3rd, 2012)

On Thu, May 10, 2012 at 12:17 AM, Daniel Dyer wrote: > A question/comment about the scope of the schema or maybe the > architecture. Assuming the services will provide the instrumentation to > populate the raw metric data, it seems likely that you will need to define > an interface between the se

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

On Thu, May 10, 2012 at 3:57 AM, Julien Danjou wrote: > On Wed, May 09 2012, Doug Hellmann wrote: > > > I'm not sure what you mean. I was able to use nova.service to create a > > "metering" server and a simple manager that subscribes to the > notificatio

Re: [Openstack] [Metering] API Extensibility (was: External API definition)

On Thu, May 10, 2012 at 9:22 AM, Loic Dachary wrote: > > Another item that we need to discuss is extensibility of this API. > > Hi, > > Here is a proposal, which we could discuss further during the meeting. > > GET extension=¶m1=foo¶m2=bar > > The API looks up /usr/share/ceilometer/extensions

[Openstack] [metering] public API design

During yesterday's meeting we discussed the API proposal at http://wiki.openstack.org/EfficientMetering#API and came up with a few missing items and other points for discussion. We should try to work out those details on the list before the meeting next week. The original proposal included these A

Re: [Openstack] [client] Event handling

On Thu, May 10, 2012 at 5:58 PM, Matt Joyce wrote: > How are we doing event handling in the client? Is there a blueprint on > this somewhere? What sort of event handling? Doug ___ Mailing list: https://launchpad.net/~openstack Post to : openstack

Re: [Openstack] [client] Event handling

x27;m still missing something... > > > On Fri, May 11, 2012 at 12:19 PM, Doug Hellmann < > doug.hellm...@dreamhost.com> wrote: > >> >> >> On Thu, May 10, 2012 at 5:58 PM, Matt Joyce >> wrote: >> >>> How are we doing event handling in the c

[Openstack] [metering] licensing

I was very surprised to see the change to license ceilometer as AGPL [1]. Why are we not using the same Apache v2 license that all other OpenStack projects are using? Doug [1] https://review.stackforge.org/#/c/29/ ___ Mailing list: https://launchpad.net

Re: [Openstack] [metering] licensing

uot; http://wiki.openstack.org/Governance/Foundation/Bylaws On Fri, May 11, 2012 at 4:01 PM, Doug Hellmann wrote: > I was very surprised to see the change to license ceilometer as AGPL [1]. > Why are we not using the same Apache v2 license that all other OpenStack > projects are using? >

Re: [Openstack] [metering] public API design

On Fri, May 11, 2012 at 3:40 PM, Loic Dachary wrote: > On 05/11/2012 05:55 PM, Doug Hellmann wrote: > > During yesterday's meeting we discussed the API proposal at > > http://wiki.openstack.org/EfficientMetering#API and came up with a few > > missing items and other

Re: [Openstack] [metering] public API design

On Fri, May 11, 2012 at 3:40 PM, Loic Dachary wrote: > On 05/11/2012 05:55 PM, Doug Hellmann wrote: > > While thinking about this use case I also had a simple idea to optimize > the storage of events and added it to the wiki > http://wiki.openstack.org/EfficientMetering?action=di

Re: [Openstack] [metering] licensing

On Fri, May 11, 2012 at 5:27 PM, Loic Dachary wrote: > On 05/11/2012 10:01 PM, Doug Hellmann wrote: > > I was very surprised to see the change to license ceilometer as AGPL > [1]. Why are we not using the same Apache v2 license that all other > OpenStack projects are usin

Re: [Openstack] [metering] licensing

On Mon, May 14, 2012 at 3:50 AM, Loic Dachary wrote: > On 05/12/2012 01:30 AM, Doug Hellmann wrote: > > > > On Fri, May 11, 2012 at 5:27 PM, Loic Dachary wrote: > >> On 05/11/2012 10:01 PM, Doug Hellmann wrote: >> > I was very surprised to see the change to

Re: [Openstack] [Netstack] Want to start Keystone support for Quantum Client

On Mon, May 14, 2012 at 8:35 AM, Yong Sheng Gong wrote: > Hi, > How can I help with the common openstack client? I think quantum needs > its own client to be implemented first and then common openstack client > (just as a thin wrapper) can call the client module if we have quantum > client desig

Re: [Openstack] [metering] resources metadata (was: public API design)

On Fri, May 11, 2012 at 3:55 PM, Loic Dachary wrote: > > > - The interesting metadata for a resource may depend on the type of > > resource. Do we need separate "tables" for that or can we normalize > > somehow? > > - How do we map a resource to the correct version of its metadata at > > any give

[Openstack] [metering] need +2 reviews/approvals

Julien has done a good bit of work bootstrapping the server implementation, but we need to have more +2 reviews (and approvals) of the code [1] before it will make it into the public repository. Are we holding off on doing those reviews on purpose until after the series of design meetings is comple

Re: [Openstack] Stackforge server migration

On Mon, May 14, 2012 at 1:35 PM, Andrew Hutchings wrote: > Hey Jay, > > On 14/05/12 17:12, Jay Pipes wrote: > > On 05/14/2012 11:38 AM, Andrew Hutchings wrote: > >> The first problem is more serious and can't be fixed where Gerrit is > >> now, so it will require us to migrate Gerrit to a different

Re: [Openstack] [metering] resources metadata

On Mon, May 14, 2012 at 1:04 PM, Loic Dachary wrote: > On 05/14/2012 04:15 PM, Doug Hellmann wrote: > > > > On Fri, May 11, 2012 at 3:55 PM, Loic Dachary wrote: > >> >> > - The interesting metadata for a resource may depend on the type of >> > resource

Re: [Openstack] [metering] resources metadata

Copying the list... On Tue, May 15, 2012 at 10:26 AM, Doug Hellmann wrote: > > > On Tue, May 15, 2012 at 8:21 AM, Julien Danjou > wrote: > >> On Tue, May 15 2012, Loic Dachary wrote: >> >> > On 05/15/2012 12:05 PM, Julien Danjou wrote: >> >> &g

Re: [Openstack] [metering] resources metadata

On Wed, May 16, 2012 at 5:20 AM, Julien Danjou wrote: > On Wed, May 16 2012, Loic Dachary wrote: > > > It makes sense and I updated the wiki accordingly: > > > > http://wiki.openstack.org/EfficientMetering?action=diff&rev2=81&rev1=80 > > > > What do you think ? > > I think we can remove the payloa

Re: [Openstack] [metering] Do we need an API and storage?

On Thu, May 17, 2012 at 5:47 AM, Nick Barcet wrote: > On 05/17/2012 11:13 AM, Loic Dachary wrote: > > On 05/16/2012 11:00 PM, Francis J. Lacoste wrote: > >> > >> I'm now of the opinion that we exclude storage and API from the > >> metering project scope. Let's just focus on defining a metering > >

[Openstack] [metering] example of discrete counter

I have added a row to the list of counters for discrete events such as uploading an image to glance [1]. Please let me know if you think I need more exposition to explain discrete counters. Doug [1] http://wiki.openstack.org/EfficientMetering?action=diff&rev2=89&rev1=87 __

Re: [Openstack] RFC: Plugin framework draft

On Thu, May 17, 2012 at 4:32 PM, Andrew Bogott wrote: >I would appreciate comments on the nascent Nova plugin framework that > I'm working on. My Nova code is in a fairly modern forked branch here: > > https://github.com/**andrewbogott/nova/tree/plugin

Re: [Openstack] About openstack common client

On Fri, May 18, 2012 at 10:09 AM, Andrew Bogott wrote: > On 5/18/12 12:16 AM, Yong Sheng Gong wrote: > > > Hi, > I just want to ask about the relationship among openstackclient > https://launchpad.net/python-openstackclient and other clients. > Will openstackclient replace other clients ( such as

Re: [Openstack] [metering] Choice of a messaging queue

On Fri, May 18, 2012 at 4:42 AM, Nick Barcet wrote: > Hello everyone, > > Next week's irc meeting will have for goal to choose a reference > messaging queue service for the ceilometer project. For this meeting to > be able to be successful, a discussion on the choices that we have to > make need

  1   2   3   >