Re: [Openstack] Installion guide for OpenStack Essex on Ubuntu 12.04

Hi Martin Now I have let the vnc working. install 3 package nova-consoleauth python-novnc novnc modify the nova.conf #novnc --novnc_enabled=true --novncproxy_base_url= http://10.42.0.6:6080/vnc_auto.html --vncserver_proxyclient_address=127.0.0.1 --vncserver_listen=127.0.0.1 restart service f

Re: [Openstack] "Shutoff" Status

Hi Anne :-)I think it only doesn't applies to - ESX- QEMU- LXCWhile it has been implemented on the other hypervisors technologies : http://wiki.openstack.org/HypervisorSupportMatrixMaybe some doc update needed around ?Later,Razique  Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 24 avr.

Re: [Openstack] Monitoring / Billing Architecture proposed

On 04/23/2012 10:09 PM, Sandy Walsh wrote: > Flavor information is copied to the Instance table on creation so the > Flavors can change and still be tracked in the Instance. It may just > need to be sent in the notification payload. > > The current events in the system are documented here: > http:/

Re: [Openstack] Canonical AWSOME

+1 - this is important for both incubated projects and vendor implementations. I seem to recall one of the sessions talking about gating commits to passing an upgrade test from the previous stable release and these interfaces are an obvious candidate. Identifying the specific interfaces will tak

Re: [Openstack] "Shutoff" Status

Hi all - We just added descriptions of each of the statuses to this page, but "SUSPENDED" is not one of them: http://docs.openstack.org/api/openstack-compute/2/content/List_Servers-d1e2078.html Who has more information about this server status? By grepping the code I get this additional info whic

Re: [Openstack] New OpenStack Releases in Ubuntu 12.04LTS

+1 this is HUGE! Duncan McGreggor wrote: Robbie, this is just as awesome as AWESOME and has as much mass as MAAS. With this support, you may have solved one of DreamHost's long-standing logistical issues around our cloud efforts. Thanks, Ubuntu and Canonical! d On Mon, Apr 23, 2012 at 11:02

Re: [Openstack] New OpenStack Releases in Ubuntu 12.04LTS

Robbie, this is just as awesome as AWESOME and has as much mass as MAAS. With this support, you may have solved one of DreamHost's long-standing logistical issues around our cloud efforts. Thanks, Ubuntu and Canonical! d On Mon, Apr 23, 2012 at 11:02 AM, Robbie Williamson wrote: > For those of

Re: [Openstack] Monitoring / Billing Architecture proposed

This looks like just the standard RPC traffic. You need to turn notifications on (set: notification_driver=nova.notifier.rabbit_notifier in nova's config file) and listen on the notification.* queues On Apr 23, 2012, at 2:26 PM, Luis Gervaso wrote: Joshua, I have performed a create instance o

Re: [Openstack] Monitoring / Billing Architecture proposed

StackTach is a Django-based web interface for capturing, displaying and navigating OpenStack notifications https://github.com/rackspace/stacktach -S On 04/23/2012 04:26 PM, Luis Gervaso wrote: > Joshua, > > I have performed a create instance operation and here is an example data > obtained fro

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

Hi folks, I've posted the presentation here: http://www.slideshare.net/saintkepha/quantum-virtual-network-service Also, the etherpad for quantum-folsom has been updated with the slides and a brief description. Thanks, -Peter Peter K. Lee V.P. Software & Infrastructure Engineering ClearPath N

Re: [Openstack] Monitoring / Billing Architecture proposed

Great, Now we just need to "officialize" those as a first step to making a real interchange format that can be versioned, documented... and all the other goodies u would normally expect. On 4/23/12 12:26 PM, "Luis Gervaso" wrote: Joshua, I have performed a create instance operation and here

Re: [Openstack] Canonical AWSOME

+1 on this. Implementing adapter style code may also introduce additional state maintenance within the proxy/adapter to the eventual target API and if not at a minimum more complexity. Also care would be needed to avoid leaky abstractions [1]. However, I don't necessarily agree that a REST endpoint

Re: [Openstack] New OpenStack Releases in Ubuntu 12.04LTS

Great job, congratulations to the crew :) Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 23 avr. 2012 à 17:02, Robbie Williamson a écrit :For those of you who may have missed this announcement. Canonical hascreated the Ubuntu Cloud archive. Starting with the Folsum release,users will be

Re: [Openstack] Monitoring / Billing Architecture proposed

On Mon, Apr 23, 2012 at 4:14 PM, Brian Schott < brian.sch...@nimbisservices.com> wrote: > Doug, > > Do we mirror the table structure of nova, etc. and add created/modified > columns? > > Or do we flatten into an instance event record with everything? > I lean towards flattening the data as it is

Re: [Openstack] Canonical AWSOME

Yes. Very yes. On Apr 23, 2012, at 10:15 AM, Justin Santa Barbara wrote: What's the advantage of replacing the native EC2 compatibility layer with AWSOME from a user / operator point of view? Although I wasn't able to attend the design summit session, right now we have two "native" APIs, whic

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] Canonical AWSOME

On Monday, April 23, 2012 at 4:00 PM, Joshua Harlow wrote: > Re: [Openstack] Canonical AWSOME How are REST endpoints not reliable or > scalable ;-) > > I’d like to know, seeing as the web is built on them :-) The resiliency of the internet is actually built on BGP. REST endpoints fall over

Re: [Openstack] Canonical AWSOME

+1 if you want people to care about something then it should be part of the main repo and part of the regular regression testing. thanks -Doug __ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | d...@us.ibm

Re: [Openstack] Using Nova APIs from Javascript: possible?

Sorry, meant to say "server-less client applications". The OP is trying to create a client-side JS application that communicates directly to an OS endpoint (specifically trystack). I believe his problem is same origin policy, not authentication. On Apr 23, 2012, at 12:33 PM, Adam Young wrote:

Re: [Openstack] Monitoring / Billing Architecture proposed

Doug, Do we mirror the table structure of nova, etc. and add created/modified columns? Or do we flatten into an instance event record with everything? Bran - Brian Schott, CTO Nimbis Services, Inc. brian.sch...@nimbisservices.com ph: 443-274-6

Re: [Openstack] Monitoring / Billing Architecture proposed

Flavor information is copied to the Instance table on creation so the Flavors can change and still be tracked in the Instance. It may just need to be sent in the notification payload. The current events in the system are documented here: http://wiki.openstack.org/SystemUsageData -Sandy On 04/23

Re: [Openstack] Canonical AWSOME

So the risks u have just stated do make sense. But isn't this problem solved by strong leadership saying we will not let people screw over the EC2 apis? And strong leadership not letting that happen... Shouldn't the question be what is the right architectural solution, not one that is being do

Re: [Openstack] Canonical AWSOME

How are REST endpoints not reliable or scalable ;-) I'd like to know, seeing as the web is built on them :-) It is clearly better to access the internal API's if performance is an issue, from an abstraction point of view if the EC2 apis are a "view" on top of the OS apis then that seems to make

Re: [Openstack] Canonical AWSOME

On Monday, April 23, 2012 at 3:42 PM, Justin Santa Barbara wrote: > I didn't realize people were willing to do so. > Ah yes, well, that problem might still remain. There are certainly seem to be volunteers to work on the versioning code, but defining, tagging, and adhering to API contracts

Re: [Openstack] Monitoring / Billing Architecture proposed

The following links to work from OGF in the usage accounting and tracking area might be useful. First of all, we have the UsageRecord format (UR), which has been used in a variety of distributed computing environments for tracking usage. It defines an XML-based format for exchange of usage r

Re: [Openstack] Canonical AWSOME

On Mon, Apr 23, 2012 at 12:31 PM, Eric Windisch wrote: > There seemed to be a strong agreement at the summit regarding the need for > contracts on those "private" apis. This is because those APIs are no longer > really private, they're shared amongst incubated projects. Furthermore, it > seems th

Re: [Openstack] Using Nova APIs from Javascript: possible?

On 04/23/2012 01:13 PM, Tres Henry wrote: Adam, in what way should the OS API support server-less clients? AFAIK the options are CORS or JSONP, no? I am not quite sure what you mean by serverless clients, but I think the answer to this is getting a real Single Sign On solution, which is ba

Re: [Openstack] Canonical AWSOME

There seemed to be a strong agreement at the summit regarding the need for contracts on those "private" apis. This is because those APIs are no longer really private, they're shared amongst incubated projects. Furthermore, it seems this may be required to support version heterogeneity during up

Re: [Openstack] Monitoring / Billing Architecture proposed

Joshua, I have performed a create instance operation and here is an example data obtained from stable/essex rabbitmq nova catch all exchange. [*] Waiting for messages. To exit press CTRL+C [x] Received '{"_context_roles": ["admin"], "_msg_id": "a2d13735baad4613b89c6132e0fa8302", "_context_read_

Re: [Openstack] Canonical AWSOME

I think the documented 'private' API should be the OpenStack API and should be available to all callers (subject to permissions). I only see downside to having two APIs (public & internal). If a proxy needs additional functionality, odds are it probably belongs in the official OpenStack API becau

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] Monitoring / Billing Architecture proposed

I like http://wiki.openstack.org/SystemUsageData I just wonder if there should be offical formats for the data sent across the wire. Or at least high level formats that define the data, maybe in a simple python "map" style layout. With examples would be awesome. On 4/23/12 10:40 AM, "Luis Ger

Re: [Openstack] Canonical AWSOME

Ya, we should figure out how to organize to make this happen. It seems to provide many benefits (not just for openstack). Maybe setup a little working group around this... On 4/23/12 12:01 PM, "Doug Hellmann" wrote: Martin Packman mentioned that there are some other groups interested in creat

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

Brian, Dough isn't dependent on Horizon. Dough has a client that can be inserted anywhere to notify the start/end of using a resource. We inserted the client in horizon just to try out the many ways our billing system could be integrated with our existing deployment. We are planning to make a N

Re: [Openstack] Canonical AWSOME

On 04/23/2012 10:42 AM, Doug Hellmann wrote: > > > 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

Re: [Openstack] Monitoring / Billing Architecture proposed

On 04/23/2012 07:06 PM, Luis Gervaso wrote: > Nick, I want contribute in the discussion group. Luis, I just sent your an invite to the doodle to pick the best time for this irc meeting. Once the date will have been finalized (I'll close the poll tomorrow EOD), I'll announce the date, time and pla

Re: [Openstack] Canonical AWSOME

Creating a contract on the private API will allow the external APIs to be created and tested without needing a translation layer, even if contributory APIs were developed outside of the project (such as in AWSOME). It is clearly better, architecturally, if the EC2/OCCI apis can access the inter

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

Adding Peter, who gave that presentation. To all Quantum team members: if you haven't already, please post slides to the main etherpad page: http://etherpad.openstack.org/quantum-folsom Thanks! Dan On Mon, Apr 23, 2012 at 9:58 AM, andi abes wrote: > During the summit, there was an API proposa

Re: [Openstack] Monitoring / Billing Architecture proposed

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, always append to the flavor/instance-type table. The code I remember and the admin interface th

Re: [Openstack] Monitoring / Billing Architecture proposed

If you wanted to use Yagi, it would be trivial to add a JSON only notifier to Yagi. If you're interested and need a hand, feel free to hit Dragon or I for assistance. From: Monsyne Dragon mailto:mdra...@rackspace.com>> Date: Mon, 23 Apr 2012 16:39:08 + To: Luis Gervaso mailto:l...@woorea.es>

Re: [Openstack] Monitoring / Billing Architecture proposed

I have been looking at : http://wiki.openstack.org/SystemUsageData On Mon, Apr 23, 2012 at 7:35 PM, Brian Schott < brian.sch...@nimbisservices.com> wrote: > Is there a document somewhere on what events the services emit? > > - > Brian Schott, CTO >

Re: [Openstack] Canonical AWSOME

We just have to be careful here to make sure that lots and lots of tests are done to ensure that the EC2 response is valid as well as to ensure the performance is not de-graded by having this proxy layer. If it does get de-graded then there needs to be some work done to ensure that this does not

Re: [Openstack] Monitoring / Billing Architecture proposed

Is there a document somewhere on what events the services emit? - Brian Schott, CTO Nimbis Services, Inc. brian.sch...@nimbisservices.com ph: 443-274-6064 fx: 443-274-6060 On Apr 23, 2012, at 12:39 PM, Monsyne Dragon wrote: > This already exis

[Openstack] Regular XenAPI Meeting

Hi, Are people keen for a XenAPI virt layer meetup on IRC every month? I have added a suggested time to the wiki, as a starting point: Monthly, second Wednesday at 17:00 UTC Does that seem a reasonable time for those that want to attend? It can be more frequent if we find that useful. I don't

Re: [Openstack] Using Nova APIs from Javascript: possible?

Adam, in what way should the OS API support server-less clients? AFAIK the options are CORS or JSONP, no? On Apr 23, 2012, at 5:50 AM, Adam Young wrote: > I see this as a feature, not a drawback.The inability to access portions > of the HTTP protocol is there to defend against attacks suc

Re: [Openstack] Canonical AWSOME

+1000 I've wanted to see the APIs move to being adapters for the "real" API for some time now. Given the debugging argument alone, I think it's a worthwhile endeavor. From: Justin Santa Barbara mailto:jus...@fathomdb.com>> Date: Mon, 23 Apr 2012 08:15:05 -0700 To: Philipp Wollermann mailto:wol

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] Monitoring / Billing Architecture proposed

Nick, I want contribute in the discussion group. I have seen yagi implementation, and i like it. I like the protocol. But I think that it's a protocol that fits very well when no sensible data is involved (content feeds). When money, resources, companies are involved i think we need to use a more

Re: [Openstack] Coverage report generation crashes with UnicodeDecodeError (#987077)

On Apr 23, 2012, at 11:59 AM, Sean Dague wrote: > On 04/23/2012 10:01 AM, Renier Morales wrote: >> Hello, >> >> Anyone experiencing a UnicodeDecodeError crash when running the nova tests >> with coverage reporting turned on (i.e. run_tests.sh -c)? Might this be a >> common environment misconfig

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

During the summit, there was an API proposal for service insertion, present by folks from Clear path. Does anyone have links? a. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchp

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] [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] Monitoring / Billing Architecture proposed

This already exists in trunk. The Notification system was designed specifically to feed billing and monitoring systems. Basically, we don't want Nova/Glance/etc to be in the business of trying to determine billing logic, since it is different for pretty much everyone, so we just emit notifica

[Openstack] orphaned floating_ips if you terminate before disassociating?

Hi, We are running Essex on 12.04 b2. Has anyone else noticed that, using the dashboard, if you terminate an instance before disassociating a floating ip, the result is that the floating_ips record is orphaned (refers to deleted instance). In this state, accessing the tenant using the dashboard,

Re: [Openstack] Coverage report generation crashes with UnicodeDecodeError (#987077)

On 04/23/2012 10:01 AM, Renier Morales wrote: Hello, Anyone experiencing a UnicodeDecodeError crash when running the nova tests with coverage reporting turned on (i.e. run_tests.sh -c)? Might this be a common environment misconfiguration problem on my side? More details at: https://bugs.lanchp

Re: [Openstack] Quantum and multi-nic

Hi Mandar, If a question is quantum-specific, best to associated it with the "quantum" project, not the "nova" project. Associating it with the Quantum project will make sure that Quantum developers are notified. Most quantum developers are not notified for each question asked about nova. I've

Re: [Openstack] Canonical AWSOME

> > What's the advantage of replacing the native EC2 compatibility layer with > AWSOME from a user / operator point of view? > Although I wasn't able to attend the design summit session, right now we have two "native" APIs, which means we have two paths into the system. That is poor software engi

[Openstack] New OpenStack Releases in Ubuntu 12.04LTS

For those of you who may have missed this announcement. Canonical has created the Ubuntu Cloud archive. Starting with the Folsum release, users will be able to elect to enable this archive, and install newer releases of OpenStack (and the dependencies) as they become available up through the next U

Re: [Openstack] Canonical AWSOME

On 04/23/2012 02:39 PM, 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 that ch

Re: [Openstack] Monitoring / Billing Architecture proposed

On Sun, 2012-04-22 at 20:50 +0200, Luis Gervaso wrote: > I want to share the architecture i am developing in order to perform > the monitorig / billing OpenStack support: > > > 1. AMQP Client which listen to RabbitMQ / QPid (this should be > interchangeable) (Own Stuff or ServiceMix / Camel) > >

Re: [Openstack] Monitoring / Billing Architecture proposed

On 04/23/2012 04:39 PM, Alexey Ababilov wrote: > Hi! > > We have developed Nova Billing v2. Its documentation is currently > available at http://aababilov.github.com/nova-billing-doc.github.com/. > The documentation includes a glossary and architecture and API descriptions. > > Nova Billing v2 is

Re: [Openstack] Glance Test Dependencies

I typically run 'pip install -r tools/pip-requires -r tools/test-requires' from the root directory. You could also manually translate those lists to a list of ubuntu packages if you prefer not to use pip. Brian On Apr 17, 2012, at 5:49 AM, Scott Lavender wrote: > I have a Jenkins job setup to

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] Monitoring / Billing Architecture proposed

Hi! We have developed Nova Billing v2. Its documentation is currently available at http://aababilov.github.com/nova-billing-doc.github.com/. The documentation includes a glossary and architecture and API descriptions. Nova Billing v2 is a totally new solution. Its API and architecture were rewrit

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 existing python impl

Re: [Openstack] "Shutoff" Status

Hello Alyssa, the status is the one reported when you supend your instance Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 16 avr. 2012 à 18:15, Alyssa Hurtgen a écrit : Hi all, I work at Rackspace and noticed a new Nova server status of "shutoff".   What does this status mean?How

[Openstack] Glance Test Dependencies

I have a Jenkins job setup to execute the Glance tests. It will run on my master, but not a slave. Obviously there is a dependency missing on the slave. What is the best way to get a dependency list? I need to get this slave working for all OpenStack tests so that I can clone it... FAIL: test_add_

[Openstack] "Shutoff" Status

Hi all, I work at Rackspace and noticed a new Nova server status of "shutoff". * What does this status mean? * How does the server get into this status? * Should the user be able to perform any actions against the server? Thanks, Alyssa Hurtgen ___

[Openstack] Coverage report generation crashes with UnicodeDecodeError (#987077)

Hello, Anyone experiencing a UnicodeDecodeError crash when running the nova tests with coverage reporting turned on (i.e. run_tests.sh -c)? Might this be a common environment misconfiguration problem on my side? More details at: https://bugs.lanchpad.net/nova/+bug/987077 Thanks, --Reni

Re: [Openstack] Python UUID and SELinux AVC denials

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 existing python > implementation is used instead and it looks like that just uses > urandom() inline.

Re: [Openstack] Instances can't access eachother via external (floating) ips?

Hi Calvin, show us iptables -nL -t nat | grep NAT on the node with nova-network. Could it be that your fixed_range flag in nova.conf covers both subnets, like 192.168.0.0/16 ? Second reason - I presume that the traffic from VM will go via your router if you access another VM via floating IP, so r

Re: [Openstack] Using Nova APIs from Javascript: possible?

I see this as a feature, not a drawback.The inability to access portions of the HTTP protocol is there to defend against attacks such as cross site request forgeries. If we suppress that mechanism, we open up a lot of security holes. On 04/23/2012 06:09 AM, Adrian Smith wrote: The auth

Re: [Openstack] Canonical AWSOME

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 that chose to only deploy OpenStack API support. -- Thierry C

Re: [Openstack] what's wrong with novnc package in Ubuntu precise ?

Alexander Gordeev wrote: > the current novnc package from universe is not workable with Essex release > > I filled a bug against this, but with no response at all > > https://bugs.launchpad.net/ubuntu/+source/novnc/+bug/956949 Fixed now. -- Thierry

Re: [Openstack] Using Nova APIs from Javascript: possible?

This is for Swift of course. But I guess there are similar headers for Nova. On 23 April 2012 11:09, Adrian Smith wrote: > The authentication request returns X-Storage-Url and X-Auth-Token > headers. For the JS client to see them they need to be referenced in > Access-Control-Expose-Headers. As o

Re: [Openstack] Using Nova APIs from Javascript: possible?

The authentication request returns X-Storage-Url and X-Auth-Token headers. For the JS client to see them they need to be referenced in Access-Control-Expose-Headers. As of the last time checked, both these headers were being stripped from the response before being presented to JS. Adrian On 23 A

Re: [Openstack] Monitoring / Billing Architecture proposed

On 04/23/2012 11:17 AM, Ahn, Jaesuk wrote: > Hi, > > Although metering and billing always comes together for the deployment, > for the sake of clarity, I also think metering should be a separate > project from the billing, especially in openstack. > (As you mentioned it, billing is complex and

Re: [Openstack] Using Nova APIs from Javascript: possible?

Hi Adrian, Good to know this is a known issue. Why does the client need to see custom headers from the server anyway? I know the client needs to pass the authorisation header to the server, but I haven't seen any of the APIs yet that return custom headers. (It's likely I'm missing them though) N

Re: [Openstack] Monitoring / Billing Architecture proposed

Hi, Although metering and billing always comes together for the deployment, for the sake of clarity, I also think metering should be a separate project from the billing, especially in openstack. (As you mentioned it, billing is complex and has too many different requirements per provider) A

Re: [Openstack] Using Nova APIs from Javascript: possible?

Hi Nick, I did some work with CORS a few months back [1]. At the time I couldn't get any browser to work properly with CORS so I just parked the code. The problem was lack of support for the Access-Control-Expose-Headers header. According to the Chrome bug report [2] this issue may well be fixed

Re: [Openstack] Monitoring / Billing Architecture proposed

Hello Luis, I presented a blueprint last week [1] which proposes to clearly differentiate metering from the overall billing process. It is my understanding that billing is too complex a beast to be solved for each requirement in a satisfactory way and have therefore proposed that we should first