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
implementation is used instead and it looks like that just uses
Hi,
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)
2. Events should be stored on a NoSQL document oriented database
What about using the Dough project?
Endre.
2012/4/22 Endre Karlson endre.karl...@gmail.com
What about using the Dough project ?
Endre.
2012/4/22 Luis Gervaso l...@woorea.es
Hi,
I want to share the architecture i am developing in order to perform the
monitorig / billing OpenStack
Dough is the proposed billing platform/product (where the billing rules
live), isn't it?
I don't know Dough enough, so please me correct me if i'm wrong.
I'm trying to define a generic/agnostic integration process, obviously
where Dough
can fit perfectly. I would like it become part to the
Correct me if I am wrong but mongo has not been used in openstack
previously? What is the benefit here that justifies bringing in new
technology?
Also are you planning an active polling process over AMPQ or passive
listening for the monitor?
It seems to me that most of the main components today
On Sun, Apr 22, 2012 at 9:57 PM, Matt Joyce m...@nycresistor.com wrote:
Correct me if I am wrong but mongo has not been used in openstack
previously? What is the benefit here that justifies bringing in new
technology?
Mongo is document oriented, which i consider fits perfectly with the
Have you started a blueprint and/or Etherpad? We should do that.
Couple of comments:
1. I had an idea for naming the metering service after Nipper, the famous RCA
dog :-)
http://en.wikipedia.org/wiki/Nipper
2. A common metering service that listens on Rabbit/ZeroMQ bus for registering
events
I see this blueprint for metering, but none for Dough currently.
http://wiki.openstack.org/EfficientMetering
Here are the Dough slides, however:
http://www.slideshare.net/lzyeval/dough-openstack-billing-project
We collectively need to talk more about the user scenarios, because I don't
think
What is Dough then compared to what you want to do ?
2012/4/22 Endre Karlson endre.karl...@gmail.com
What is Dough then ?
2012/4/22 Brian Schott brian.sch...@nimbisservices.com
I see this blueprint for metering, but none for Dough currently.
http://wiki.openstack.org/EfficientMetering
my comments below
On Sun, Apr 22, 2012 at 10:32 PM, Brian Schott
brian.sch...@nimbisservices.com wrote:
Have you started a blueprint and/or Etherpad? We should do that.
Couple of comments:
1. I had an idea for naming the metering service after Nipper, the famous
RCA dog :-)
Hi,
Has anyone checked this
http://www.griddynamics.com/openstack/docs/nova-billing/quickstart.html
From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Endre
Karlson
On Sun, Apr 22, 2012 at 11:18 PM, Luis Gervaso l...@woorea.es wrote:
I think Dough takes care about pricing and billing.
I have proposed an arch and technologies to fill the gap between openstack
and
whatever billing system / monitoring system.
On Sun, Apr 22, 2012 at 10:57 PM, Endre
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/view/37
The billing system consists of three components.
1) API Server, which receives
I see this is an accounting system, a billing system needs things like
promotional codes, vat, invoices ...
I'm proposing the way the events should be orchestated
Please, correct me, if i'm wrong
Luis
On Sun, Apr 22, 2012 at 11:16 PM, Atul Jha atul@csscorp.com wrote:
Hi,
Has anyone
The heart of nova-biling is built around accounts, resources, billing segments
with a tariff and cost. Not clear at my first review where/how these costs are
set.
Brian
-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
Monitoring and billing seem to be two VERY different beasts.
Should we be separating the two efforts?
On Sun, Apr 22, 2012 at 3:08 PM, Brian Schott
brian.sch...@nimbisservices.com wrote:
The heart of nova-biling is built around accounts, resources, billing
segments with a tariff and cost. Not
Why can't Dough / Kanyun be used for this?
Endre.
2012/4/23 Brian Schott brian.sch...@nimbisservices.com
The heart of nova-biling is built around accounts, resources, billing
segments with a tariff and cost. Not clear at my first review where/how
these costs are set.
Brian
You are right.
OpenStack should do only cloudcomputing. Others should manage better
monitor and billing
So we have to focus the effort to define the piece/component that
orchestates the two/three/four ... beasts
around OpenStack in a loosely coupled way.
That is, other *should not* know
I'm trying runnig a windows image on nova
I run the image under KVM (qemu), i have disabled the firewall and have
activated the RDP connection.
I run succesfully the euca-bundle-image command but i'm trying to execute
the euca-upload-bundle i have the following error !
any idea about that !! i
Agreed. Not to mention all of those web commerce systems (Ubercart, Sachmo,
Mezzanine/Cartridge, and many wordpress and rails commerce platforms I don't
know). We don't need to reinvent selling stuff on the Internet. So, what's
really missing?
1) The ability to query historical cloud
On Mon, Apr 23, 2012 at 2:10 AM, Brian Schott
brian.sch...@nimbisservices.com wrote:
Agreed. Not to mention all of those web commerce systems (Ubercart,
Sachmo, Mezzanine/Cartridge, and many wordpress and rails commerce
platforms I don't know). We don't need to reinvent selling stuff on the
Hi, I'm the person who presented Dough.
After my presentation there were lots of feedback from many people.
The conclusion was that no matter how generic I tried to design Dough, the
billing requirements of each company will vary if they have different
metering specifications.
Therefore a few
Congrats for the project!
On Mon, Apr 23, 2012 at 3:06 AM, Zhongyue Luo lzye...@gmail.com wrote:
Hi, I'm the person who presented Dough.
After my presentation there were lots of feedback from many people.
The conclusion was that no matter how generic I tried to design Dough, the
billing
Hi,
Please confirm the environment variable S3_URL with the following command.
export | grep S3
Normally the value should be something like
http://XXX.XXX.XXX.XXX:;. If the IP address is specified you
should confirm whether it is valid. If the host name is specified you
should confirm
I captured some of our discussion in the etherpad, but feel free to extend.
Brian
-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
ph: 443-274-6064 fx: 443-274-6060
On Apr 22, 2012, at 9:32 PM, Luis Gervaso wrote:
Yes. See http://wiki.openstack.org/XenServer/XenXCPAndXenServer.
Cheers,
Ewan.
From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf
Of livemoon
Sent: Friday, April 20, 2012 6:49 AM
To:
exactly
2012/4/23 Ewan Mellor ewan.mel...@eu.citrix.com:
Yes. See http://wiki.openstack.org/XenServer/XenXCPAndXenServer.
Cheers,
Ewan.
From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On
Dan,
Can you help with this ?
https://answers.launchpad.net/nova/+question/194111
Thanks,
-Mandar
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain
28 matches
Mail list logo
