Hi all.
In my opinion it is about things that can live in one form or another, because
in some cases there is a need to place an instance in the same place where its
block device is located or will be attached. Both solutions that let you do it,
I mean filter and weigher, have a right to life. A
Hi,
Since python-sqlalchemy 0.8.2 has been uploaded to Sid, Quantum is
uninstallable there right now (see #715294).
I am wondering: what's wrong with sqlalchemy = 0.8, so that it is
written explicitly in the requirements that we shouldn't use it? Is
there a chance that having such a version of
On Sat, Jul 06 2013, Jobin Raju George wrote:
I am trying to use the meters provided by ceilometer to extract usage
values from the VM's deployed using openstack.
However, in order to programmatically do this I need the XSD files for
ceilometer. I tried googling them, posting them on forums
Hi Thomas,
I would prefer to avoid such things at this moment.
First of all we are using different wrappers around sqlalchemy in different
projects.
There is a lot of hacks and they could probably produce hidden bugs.
Also our db code is not fully covered by tests. So I would prefer to:
1)
On 07/08/2013 08:53 AM, Thomas Goirand wrote:
Hi,
Since python-sqlalchemy 0.8.2 has been uploaded to Sid, Quantum is
uninstallable there right now (see #715294).
I am wondering: what's wrong with sqlalchemy = 0.8, so that it is
written explicitly in the requirements that we shouldn't use
Ok, that's fine. I am currently investigating into it. Lets see if I get
any clues. Thanks for you time!
On Mon, Jul 8, 2013 at 1:32 PM, Julien Danjou jul...@danjou.info wrote:
On Sat, Jul 06 2013, Jobin Raju George wrote:
I am trying to use the meters provided by ceilometer to extract
On Mon, 2013-07-08 at 15:53 +0800, Thomas Goirand wrote:
Hi,
Since python-sqlalchemy 0.8.2 has been uploaded to Sid, Quantum is
uninstallable there right now (see #715294).
I am wondering: what's wrong with sqlalchemy = 0.8, so that it is
written explicitly in the requirements that we
Hi all,
I just noticed the following bug -
https://bugs.launchpad.net/cinder/+bug/1197648
which is very similar to an issue I recently looked at in Swift -
https://bugs.launchpad.net/swift/+bug/1181146
Basically these problems are actually a result of a bug in
python-eventlet 0.13 i.e.
On 05/07/13 14:26, Boris Pavlovic wrote:
Hi all,
I would like to explain very high level steps of our work:
1) Sync work with DB in all projects (We have what we have, let it be in
one place)
2) Refactor work with DB in one place (not independently in all projects)
So I understand
On 07/08/2013 04:50 AM, Mark McLoughlin wrote:
On Mon, 2013-07-08 at 15:53 +0800, Thomas Goirand wrote:
Hi,
Since python-sqlalchemy 0.8.2 has been uploaded to Sid, Quantum is
uninstallable there right now (see #715294).
I am wondering: what's wrong with sqlalchemy = 0.8, so that it is
written
I have created a blueprint here:
https://blueprints.launchpad.net/neutron/+spec/zone-based-router
I'll complete the full specification soon
On Sun, Jul 7, 2013 at 12:37 AM, Salvatore Orlando sorla...@nicira.com wrote:
Thanks for sharing your thoughts on the mailing list.
I will read them
On 07/03/2013 01:08 PM, David Kranz wrote:
On 07/03/2013 12:30 PM, Day, Phil wrote:
Hi Folks,
I have a change submitted which adds the same clean shutdown logic to
stop and delete that exists for soft reboot – the rational being that
its always better to give a VM a chance to shutdown cleanly
On 07/05/2013 08:14 PM, Qiu Yu wrote:
Russell,
Should ComputeCapabilitiesFilter also be restricted to use scoped
format only? Currently it recognize and compare BOTH scoped and
non-scoped key, which is causing the conflict.
I've already submitted a bug and patch review before.
On Jul 3, 2013 5:22 PM, Ala Rezmerita ala.rezmer...@cloudwatt.com wrote:
Hi everyone,
I have a question regarding too many token generation in nova when using
quantumclient (also related to bug reports
https://bugs.launchpad.net/nova/+bug/1192383 +
On 07/02/2013 06:40 PM, Russell Bryant wrote:
Greetings,
I would like to propose Christopher Yoeh to be added to the nova-core team.
Welcome to the team!
--
Russell Bryant
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 07/08/2013 09:56 AM, Joe Gordon wrote:
On Jul 3, 2013 12:44 PM, guohliu guoh...@linux.vnet.ibm.com
mailto:guoh...@linux.vnet.ibm.com wrote:
Hello,
As we know, nova have different compute drivers with different
limitations, you can see in this link,
On 06/24/2013, Russell Bryant wrote:
On 06/24/2013 02:01 PM, Sunjeet Singh wrote:
/
/ / OpenStack currently uses AMQP 0.8. Are there any plans to upgrade?
/
OpenStack is not specifically tied to an AMQP version. It's more about
what clients we have support for, what versions they speak,
If you have a recent version of kombu, and amqp[1] rather than amqplib
installed, things will just start using AMQP 0.9.1.
Ubuntu doesn't package a new enough Kombu, and they don't package amqp
at all.. Not sure about other distro's.
Thanks,
Kiall
[1]: https://pypi.python.org/pypi/amqp
On
Hi
On Mon, Jul 08, 2013 at 03:11:02PM +, Mac Innes, Kiall wrote:
If you have a recent version of kombu, and amqp[1] rather than amqplib
installed, things will just start using AMQP 0.9.1.
Ubuntu doesn't package a new enough Kombu, and they don't package amqp
at all.. Not sure about
On 07/08/2013 10:51 AM, Ted Ross wrote:
If someone from the Qpid community were to work on integrating the new
AMQP 1.0 technology into OpenStack, where would be the right place to
start? Would it be to add a new transport to oslo.messaging?
I think so, yes. oslo.messaging is new, but it
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting tomorrow, Tuesday July 9th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone interested in
-Original Message-
From: Eoghan Glynn [mailto:egl...@redhat.com]
Sent: Thursday, July 04, 2013 3:36 AM
To: OpenStack Development Mailing List; Neal, Phil
Subject: Re: [openstack-dev] [Ceilometer] Changing pollster/pipeline
parameters
Hi Phil,
Some more thoughts inline ...
On 07/05/2013 10:57 AM, Dolph Mathews wrote:
On Mon, Jul 1, 2013 at 3:24 PM, David Ripton drip...@redhat.com
mailto:drip...@redhat.com wrote:
On 07/01/2013 12:49 PM, Brant Knudson wrote:
'Stackers -
I've got a review up in Keystone that converts tables from
Does anyone know if the IRC channels have been renamed or will be renamed?
PCM (Paul Michali)
MAIL p...@cisco.com
IRC pcm_ (irc.freenode.net)
TW @pmichali
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hey, all!
I have prepared the XSD for ceilometer and would like to contribute it to
the repositories on github. Can somebody help me out with the process to do
this?
On Mon, Jul 8, 2013 at 2:19 PM, Jobin Raju George jobin...@gmail.comwrote:
Ok, that's fine. I am currently investigating into
On 2013-07-08 12:53:10 -0400 (-0400), Paul Michali wrote:
Does anyone know if the IRC channels have been renamed or will be
renamed?
The infrastructure team registered #openstack-neutron on Freenode
and configured the openstackgerrit bot to report in there similarly
to #openstack-quantum. Looks
Hi neutron folks,
There has been a discussion around this patch
https://review.openstack.org/#/c/29750/ that introduces configuration
options and db table for storing service providers.
The discussion is about whether we should store configuration in the db or
not.
The brief of discussion has
Many people are converting their code, which is out for review, to neutron. One
thing I'm seeing is the files which have been moved and renamed, are showing up
as new files (not to pick on it, but as an example
https://review.openstack.org/#/c/33297/10/neutron/tests/unit/ml2/test_type_gre.py)
Cool! Thanks! I'm preparing to setup IRC on another computer and adding my
channels and was wondering about that.
PCM (Paul Michali)
MAIL p...@cisco.com
IRC pcm_ (irc.freenode.net)
TW @pmichali
On Jul 8, 2013, at 3:00 PM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2013-07-08 12:53:10
On 07/01/2013 01:35 PM, Clint Byrum wrote:
The way the new keystone-manage command token_flush works right now
is quite broken by MySQL and InnoDB's gap locking behavior:
https://bugs.launchpad.net/1188378
Presumably other SQL databases like PostgreSQL will have similar problems
with doing
Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700:
On 07/01/2013 01:35 PM, Clint Byrum wrote:
The way the new keystone-manage command token_flush works right now
is quite broken by MySQL and InnoDB's gap locking behavior:
https://bugs.launchpad.net/1188378
Presumably
As per the recent TC decision around programs, the existing programs
need to provide a name, acting PTL and Mission Statement. Enjoy:
Official Title: OpenStack Infrastructure
PTL: Monty Taylor mord...@inaugust.com
Mission Statement:
Develop and maintain the tooling and infrastructure needed to
thanks for the feedback folks! you brought up good use case questions and
some gaps in our bp explanation. i guess the main goal here was to
highlight a standard that could possibly help with how we deal with
notifications currently -- possibly standardizing it a bit more rather than
a grab bag
Hi Eugene
It still not make sense for me to store static configuration on the DB
just for easy implementation.
However if the service type will support creation and deletion REST
api in future, I would like to approve this patch
as a first step of it.
You answered I think it's doable but I'd
Hi All,
I'm wondering if anyone has deployed openstack without any proprietary
software/component?
Thanks,
Qing
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I thought I would get some input on a draft statement before submitting one
for the TC to vote on.
We're very focused on using OpenStack components in the delivery as much as
possible - growing the capabilities of OpenStack rather than working around
things; so I've captured that in the mission
On 07/08/2013 04:35 PM, Clint Byrum wrote:
Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700:
On 07/01/2013 01:35 PM, Clint Byrum wrote:
The way the new keystone-manage command token_flush works right now
is quite broken by MySQL and InnoDB's gap locking behavior:
On 9 July 2013 12:32, Adam Young ayo...@redhat.com wrote:
* I am asking about MySQL.. presumably a real database.
I have to admit I am a bit of a Postgresql Bigot. I don't really consider
MySQL a real database, althought it has improved a lot over the years. I
am not up to speed
Tokens are, for the most part, immutable. Once they are written, they
don't change except if they get revoked. This is a fairly rare
occurance, but it does happen.
Deleting tokens based on age should be fairly straight forward, and
locks should not need to be held for a significant amount
Excerpts from Adam Young's message of 2013-07-08 17:32:30 -0700:
On 07/08/2013 04:35 PM, Clint Byrum wrote:
Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700:
On 07/01/2013 01:35 PM, Clint Byrum wrote:
The way the new keystone-manage command token_flush works right now
is
On Mon, 2013-07-08 at 21:55 -0400, Adam Young wrote:
Tokens are, for the most part, immutable. Once they are written, they
don't change except if they get revoked. This is a fairly rare
occurance, but it does happen.
Deleting tokens based on age should be fairly straight forward, and
(Sorry, I've been away and didn't get this out sooner).
A couple of issues have come up on the mailing list that would be good to go
over if the critical people can be at the meeting tomorrow:
1) Scheduler code re-factoring
2) Volume affinity filter
3) Follow ups on the scheduler BPs
4)
Hello folks,
I've found this page to be informative in trying to understanding monitoring vs
instrumentation within OpenStack:
https://wiki.openstack.org/wiki/UnifiedInstrumentationMetering
It is a bit dated though (from October last year I believe). I was curious if
it still reflects current
43 matches
Mail list logo
