On Jul 11, 2012, at 11:18 AM, Day, Phil wrote:
Hi All,
I’m looking at the network bandwidth code with a view to how the current
framework could be made to work with libvirt, and a I have a couple of
questions that hopefully someone familiar with the Xen implementation can
answer:
-
(from
http://nova.openstack.org/~soren/stats/nova-review-stats.html) the following
people have been very low on reviews over the past few months:
Brian Lamar (12)
Jesse Andrews (12)
Joshua McKenty (0)
Monsyne Dragon (12)
Monty Taylor (4)
Paul Voccio (7)
Soren Hansen (10)
termie (0)
Todd Willey (0
The reason nova uses a topic exchange and queues like it does is so the
processing of notifications can be round-robined to multiple workers. You
should be able to open a new queue on the same exchange and receive copies of
each message.
On May 8, 2012, at 3:19 PM, Doug Hellmann wrote:
I'm
Yes, the publisher_id is servicename.host, so ya, you can determine the compute
host from that.
On Apr 25, 2012, at 4:44 PM, Joshua Harlow wrote:
Hi all,
I was looking at the notification outputs, which are very useful and I was
wondering if the way to say figure out which hypervisor a VM is
Even better, what would it take to try using Alembic?
(http://alembic.readthedocs.org/en/latest/front.html#project-homepage)
It's a big improvement over sqlalchemy. Amongst other things, migrations are
not numbered, they are linked by dependancy, and run in topological-sort order.
That there
The notification system is simply 'borrowing' some code from rpc to push
notifications. The notifications have a specified JSON message format,
documented on the wiki: http://wiki.openstack.org/NotificationSystem
As far as the notification drivers, they are very very simple.
On Apr 25,
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each instance
The event has the somewhat generic name of 'compute.instance.exists' and is
emitted on an periodic basis, currently by a cronjob.
Currently, we only populate bandwidth data from XenServer, but if the hook is
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote:
On 04/24/2012 03:06 PM, Monsyne Dragon wrote:
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each instance
The event has the somewhat generic name of 'compute.instance.exists' and is
emitted on an periodic basis, currently
On Apr 24, 2012, at 11:00 AM, Loic Dachary wrote:
On 04/24/2012 04:45 PM, Monsyne Dragon wrote:
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote:
On 04/24/2012 03:06 PM, Monsyne Dragon wrote:
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each instance
The event has
wrote:
Probably an extra audit system is required. I'm searching for solutions in the
IT market.
Regards
On Tue, Apr 24, 2012 at 6:00 PM, Loic Dachary
l...@enovance.commailto:l...@enovance.com wrote:
On 04/24/2012 04:45 PM, Monsyne Dragon wrote:
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote
an extra audit system is required. I'm searching for solutions in the
IT market.
Regards
On Tue, Apr 24, 2012 at 6:00 PM, Loic Dachary
l...@enovance.commailto:l...@enovance.com wrote:
On 04/24/2012 04:45 PM, Monsyne Dragon wrote:
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote:
On 04/24/2012 03:06
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
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
On Apr 5, 2012, at 10:06 AM, Yun Mao wrote:
Right now, if you use KVM via libvirt (the default case), on the
compute node, nova-compute runs on the host. If you use Xen via
xenapi, nova-compute runs on Dom-U. (I'll ignore Xen via libvirt since
no one really uses it.)
What's the
On Mar 23, 2012, at 10:20 AM, Kevin L. Mitchell wrote:
On Fri, 2012-03-23 at 13:43 +, Gabe Westmaas wrote:
However, I kind of expect that many users
will still poll even if they know they won't get new data until X
time.
I wish there was some kind of way for us to issue push
yes, in your yagi.conf, in the persistence section, set the entry_ttl value
like so:
For 120 second expiration:
[persistence]
entry_ttl = 120
The value is in seconds, so for 1 hr use 3600, etc.
On Mar 13, 2012, at 1:50 PM, Craig Vyvial wrote:
I noticed that in the configuration file
On Mar 12, 2012, at 11:33 AM, Jay Pipes wrote:
On 03/12/2012 11:56 AM, Johannes Erdfelt wrote:
On Mon, Mar 12, 2012, Jay Pipesjaypi...@gmail.com wrote:
On 03/12/2012 09:33 AM, Swaminathan Venkataraman wrote:
I've been playing around with openstack for a month now and was looking
to see how
On Mar 2, 2012, at 9:17 AM, Jay Pipes wrote:
On 03/02/2012 05:34 AM, Day, Phil wrote:
In our experience (running clusters of several hundred nodes) the DB
performance is not generally the significant factor, so making its calls
non-blocking gives only a very small increase in processing
On Feb 14, 2012, at 1:25 PM, Jay Pipes wrote:
-1 on shard b/c of database terminology. -1 on cluster because of HPC and
database terminology.
Zone was originally used because it is general -- referring to merely a
collection of hosts or other zones and not having a geographic connotation
Lazy consensus seems to say yes (6 +1's and no negatives, and it's been 5
days).
Would someone mind adding me to the nova-core group?
On Feb 6, 2012, at 4:48 PM, Matt Dietz wrote:
Hey guys,
Dragon has really stepped up lately on reviewing patches into Nova, and has a
ton of knowledge around
On Feb 13, 2012, at 11:50 AM, Juan Antonio García Lebrijo wrote:
On 02/13/2012 06:37 PM, Andrew Bogott wrote:
On 2/13/12 9:47 AM, Juan Antonio García Lebrijo wrote:
Hello Andrew,
as we could find in the notification system
wikihttp://wiki.openstack.org/NotificationSystem, we had to add the
Yes the documentation should be current.
The notification system, and some basic events were added in diablo. This has
been expanded in Essex.
On Jan 10, 2012, at 12:56 PM, Leander Bessa wrote:
Hello,
I'm trying to figure out how to obtain information about the instances running
in the
On Dec 15, 2011, at 1:10 AM, Chris Behrens wrote:
I've seen a number of patches lately that have code like this:
instance = db.instance_get(...)
instance_uuid = instance.uuid
instead of:
instance_uuid = instance['uuid']
There's a mix of usage throughout the code, and I know some
On Dec 15, 2011, at 1:27 PM, Devin Carlen wrote:
Matt, that answer is simple: so we can use things other than sqlalchemy.
Except that we don't need to do that to use other things that sqlalchemy.
We can have sqlalchemy map to plain python objects, and use those.
And any other persistence
On Nov 3, 2011, at 8:41 AM, Anne Gentle wrote:
Hi Christian (oh hai list) -
I've answered this a few times recently so I think it's useful to post info to
the list. It's a highly requested bit of info. The documentation for
notifications could be in a couple different areas. There's the the
On Oct 27, 2011, at 10:20 PM, Bryan Taylor wrote:
Just to be clear we are talking about APIs fit for customer consumption here,
not internal integrations where both ends are under our control.
On 10/27/2011 11:38 AM, George Reese wrote:
I disagree. The web was designed specifically to
On Oct 27, 2011, at 11:38 AM, George Reese wrote:
Sent from my iPhone
On Oct 27, 2011, at 11:26, Bryan Taylor btay...@rackspace.com wrote:
On 10/27/2011 10:36 AM, George Reese wrote:
#3 Push scales a hell of a lot better than having tools polling a cloud
constantly. It doesn't matter
On Oct 26, 2011, at 10:48 AM, Kevin L. Mitchell wrote:
On Tue, 2011-10-25 at 15:30 -0700, Joseph Heck wrote:
It sounds like even though most of us hate WADL, it's what we're
expending effort after to make a consolidated API set. So unless Nati
and Ravi want to switch to using Swagger (or
I answered Roe Lee's question via email, but I figured some other folks on the
list might want to know as well...
Begin forwarded message:
Date: October 26, 2011 12:21:34 AM CDT
To: Roe Lee hrlee...@gmail.commailto:hrlee...@gmail.com
Subject: Re: SystemUsageData in Diablo via notification
On Sep 7, 2011, at 10:34 AM, Sandy Walsh wrote:
Heh. Like I mentioned at the top of the thread, it's just a hack. We're
currently merging with Roundabout to handle the Jenkins integration and make
roundabout's workflow strategies pluggable.
So, right now only the pull request and core
On Sep 7, 2011, at 1:19 PM, Bryan Taylor wrote:
An incident is a form of ticket that recognizes that an existing requirement
(customer or internal) isn't being met.
On 09/07/2011 06:20 AM, Soren Hansen wrote:
2011/9/7 Bryan Taylorbtay...@rackspace.com:
I'm working on an incident system
On Aug 26, 2011, at 2:22 PM, Ed Leafe wrote:
Sorry I haven't come up with a snazzy name for it yet, but what I have
in mind is a new service that is essential for my employer (Rackspace), and
might be important for other OpenStack deployments. This new service would be
completely
On Jul 7, 2011, at 10:40 AM, John Tran wrote:
This method is used for the instance-usage-audit executable , however,
we believe it would be useful to have it exposed in either the OpenStack
or EC2 API. Thoughts?
Hmm... What would be exposed? THis method is used for any of the instance
On May 11, 2011, at 10:47 AM, Matt Dietz wrote:
Hey Seshu,
1) Yes, that will be contained within the publisher_id field of the message body
2) We should be able to get customer related data from the message where it
makes sense. It would be contained within the payload dictionary. Given that
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
--
-Monsyne Dragon
work: 210-312-4190
Also, I should note that there seems to be merges pending to make the
v1.1 api use urls as instance identifiers in api calls, rather than
integer id's...
I'm not sure of the impact of that with the v1.0 compat, but that is
something to think of.
--
--
-Monsyne Dragon
Confidentiality
.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
--
-Monsyne Dragon
work: 210-312-4190
mobile210-441-0965
google voice
to the
'nearest' endpoint).
--
--
-Monsyne Dragon
work: 210-312-4190
mobile210-441-0965
google voice: 210-338-0336
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use
On 3/3/11 5:51 PM, Eric Day wrote:
Taking this from the MP to ML for wider audience.
On Thu, Mar 03, 2011 at 11:29:43PM -, Monsyne Dragon wrote:
Actually, the OpenStack API only defines compute methods, it punts on
auth currently (as it should). There is no definitive OpenStack Auth
this to pass the project name in.
--
--
-Monsyne Dragon
work: 210-312-4190
mobile210-441-0965
google voice: 210-338-0336
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use
, since reliable queueing is one of those things that is
simple in concept, but has an awful lot of nasty details. (That said, I
have no objection to re-inventing wheels if a: our new ones fly, or b:
the existing ones are square : )
--
--
-Monsyne Dragon
work: 210-312-4190
://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
--
-Monsyne Dragon
work: 210-312-4190
mobile210-441-0965
google voice: 210-338-0336
03, 2011 2:42 PM
To: Devin Carlen; Monsyne Dragon
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Pondering multi-tenant needs in nova.
I think that this could be done in the current proposal. Specifically, the
account_id is an arbitrary string that is generated externally to Nova. You
).
On Feb 2, 2011, at 5:37 PM, Monsyne Dragon wrote:
I am sorting out some possible implementations for the
multi-tenant-accounting blueprint, and the related
system-usage-records bp,
and I just wanted to run this by anyone interested in such matters.
Basically, for multitenant purposes we
44 matches
Mail list logo
