Hi All,
this oslotest release break oslo.messaging gate - unittest fails
with ImportError, on import mox from six.moves - [0].
It caused by commit [1], which removed adding mox to six moves.
There is a fix for oslo.messaging - [2] - please, help to merge it.
[0] - http://paste.openstack.org/show
+1 from me
On Thu, May 7, 2015 at 5:52 PM, Jay Pipes wrote:
> Note an oslo core, but big +1 from me.
>
> On 05/07/2015 10:36 AM, Davanum Srinivas wrote:
>
>> Dear Oslo folks,
>>
>> I'd like to propose adding Mehdi Abaakouk to oslo-core. He is already
>> leading the oslo.messaging team and helpin
Hi, All,
My 2c are:
- yes, oslo.db supports python 3 (unittests passes, at least :) )
- MySQL-python still default MySQL DB driver in OpenStack, but at the
moment the only DB driver for MySQL in python3 environment is PyMySQL, so I
think, it's ok to use it with python 3.
On Wed, Apr 22, 2015 a
Thanks for your work on this! :)
On Thu, Apr 9, 2015 at 7:25 PM, Victor Stinner wrote:
> Hi,
>
> During the last OpenStack Summit at Paris, we discussed how we can port
> OpenStack to Python 3, because eventlet was not compatible with Python 3.
> There are multiple approaches: port eventlet to P
Hi folks!
The Oslo team is pleased to announce the release of: oslo.db - OpenStack
common DB library
Changes from the previous release:
$ git log --oneline --no-merges 1.4.1..1.5.0
7bfdb6a Make DBAPI class work with mocks correctly
96cabf4 Updated from global requirements
a3a1bdd Imported Transl
Hello folks!
The Oslo team is pleased to announce the release of oslo.db - 1.4.1
This is a bugfix release to address a problem found in the 1.4.0 release -
oslo.db API change break neutron functional tests
Change in openstack/oslo.db 1.4.0..1.4.1
commit b1fc55c7ce6004311379f4002fdceddcc8da978
Hello Folks
The Oslo team is pleased to announce the release of oslo.db 1.2.0.
This release includes several bug fixes as well as many other changes:
$ git log --abbrev-commit --pretty=oneline --no-merges 1.1.0..1.2.0
f740e3b Imported Translations from Transifex
ca1ad56 Make test_models pass on
exposed after the release (and not before), any idea
> which oslo.db change impacted this?
>
> -Sean
>
> On 11/18/2014 11:17 AM, Victor Sergeyev wrote:
> > Matt,
> >
> > As for race in Nova - it caused by deprecated is_backend_avail()
> > function, which calls
g/#/c/135293/
[2] https://review.openstack.org/#/c/103920/
On Tue, Nov 18, 2014 at 5:22 AM, Matt Riedemann
wrote:
>
>
> On 11/17/2014 9:36 AM, Victor Sergeyev wrote:
>
>> Hello All!
>>
>> Oslo team is pleased to announce the new release of Oslo database
>> handl
Hello All!
Oslo team is pleased to announce the new release of Oslo database handling
library - oslo.db 1.1.0
List of changes:
$ git log --oneline --no-merges 1.0.2..master
1b0c2b1 Imported Translations from Transifex
9aa02f4 Updated from global requirements
766ff5e Activate pep8 check that _ is
Great job, Mike, thanks!
Doug, as for migration from sqlalchemy-migrate to Alembic - at the moment
it's hard to realize this because we suppose to keep backward compatibility
with available migrations. I'd like to re-review existing approach with
Mike and Roman, create road-map for this migration,
Hello All!
Oslo team is pleased to announce the new Oslo database handling library
release - oslo.db 0.5.0
List of changes:
$ git log --oneline --no-merges 0.4.0..0.5.0
c785bee Updated from global requirements
ac05c2a Imported Translations from Transifex
57f499e Add a check for SQLite transactio
Hello Folks!
Oslo team is pleased to announce the new Oslo database handling library
release - oslo.db 0.4.0
Thanks all for contributions to this release.
Feel free to report issues using the launchpad tracker:
https://bugs.launchpad.net/oslo and mark them with ``db`` tag.
See the full list of c
Sure, here is my +1
Folks, it looks like, that there is no no objection to this proposal.
Welcome to the team, Mike!
On Tue, Aug 19, 2014 at 12:02 PM, Flavio Percoco wrote:
> On 08/15/2014 10:26 PM, Doug Hellmann wrote:
> >
> > On Aug 15, 2014, at 10:00 AM, Ben Nemec wrote:
> >
> >> On 08/15/
Hello Doug, All.
>> This release is currently blocked on landing some changes in projects
using the library so they don’t break when the new version starts using
different exception classes. We’re tracking that work in
https://etherpad.openstack.org/p/sqla_exceptions_caught
>> It looks like we’re
tream projects. If ten projects all use eventlet, they shouldn't all
> have to replicate the same test over and over that should just be upwards
> of them.
>
>
>
>
>
>
>
> -Sean
>
> On 07/10/2014 07:42 AM, Victor Sergeyev wrote:
>
> Hello
Hello Angus!
IMO, the simple answer on your question is - tests for eventlet and oslo.db
interaction should be in the same place, where eventlet and oslo.db
interact. :)
A little digression - we suppose, that oslo.db should neither know, nor
take care whether target projects use eventlet/gevent/O
Hello Folks!
The Oslo team is pleased to announce the release of oslo.db 0.3.0
oslo.db is the database handling library.
This release includes the following changes:
$ git log --oneline --no-merges 0.2.0..0.3.0
404de36 Add a base test case for DB schema comparison
a1fd49f Test for distinct SQL
Hello, Folks!
Please, be informed, that the oslo.db library has been released and is
available on PyPi.
See [1] for the source code, [2] for the documentation.
There is an example of how to switch an OpenStack project to oslo.db - see
patch to Ironic [3]. oslo.db team is going to eventually make
ranch ready to start testing with.
>
> --
> Chuck
>
> -- Forwarded message --
> From: Sergey Shepelev
> Date: Fri, Jun 13, 2014 at 1:18 PM
> Subject: [Eventletdev] Eventlet 0.15 pre-release testers needed
> To: eventletdev , Noah Glusenkamp <
> n..
Hello Matt.
Thanks a lot for your working on this!
In my opinion, these steps are correct. Please see a few minor notes below.
1 - Yes, you right, oslo.db is not in global-requirements now. Blueprint
``Split openstack.common.db code into a separate oslo.db library `` [1] is
not completed at the
Hello all,
During Icehouse release cycle our team has been working on splitting of
openstack common db code into a separate library blueprint [1]. At the
moment the issues, mentioned in this bp and [2] are solved and we are
moving forward to graduation of oslo.db. You can find the new oslo.db code
Hello All.
We suppose to have common database code oslo.db library. So we decided to
let end applications to cope with engines, not oslo.db. For example, see
work with slave engine in Nova [1]. These is also patch to oslo with more
details - [2]
Also, Darren, please inform us about your usecase a
Hello All
I and Roman Podoliaka are familiar with the changes made to common db code,
so we are ready to help with syncing it to OS projects.
But we want to ask you for more activity in reviewing of these patches.
Thanks, Victor
On Thu, Feb 20, 2014 at 4:27 AM, Doug Hellmann
wrote:
>
>
>
> On
Hello Joe.
Thanks for pointing this issue. We will investigate this situation and fix
it.
In the future in such cases you can just create a bug on launchpad.
Also feel free to ping me (and another db maintainers) in IRC.
Thanks,
Victor
On Wed, Feb 5, 2014 at 9:12 PM, Joe Gordon wrote:
> Hi B
Hello All.
Also I have a proposition to discuss current graduation status of oslo.db
code.
This code going to move into a separate library (it will be soon, I hope),
so it's would be nice to look at it's state/issues/and-so-on due to speed
up graduation process and avoid any confusion in the futur
Hello All.
As for lockutils - a few days ago I wondered why we used custom oslo module
instead of lockfile library [1]. AFAIK, it must be due to this bug [2]
(please fix me, if I wrong).
This library is available on github [3] and there is a pull-request fixing
the bug [4], but unfortunately it h
Hi folks!
At the moment I and Roman Podoliaka are working on splitting of
openstack.common.db code into a separate library. And it would be nice to
drop dependency on eventlet before oslo.db is released.
Currently, there is only one place in oslo.db where we use eventlet -
wrapping of DB API meth
By the way, pep8 says, that "it is okay to increase the nominal line length
from 80 to 100 characters". See
http://www.python.org/dev/peps/pep-0008/#maximum-line-length
I'm ok with 80 characters, but just for information - is there any plans
to to increase the line length in OpenStack?
Victor
O
Hello all,
I noticed, that when I run tests using tox I get some redundant modules
installed to tox virtual environments. At the moment, pep8 specific
requirements (such as pep8, flake8 and so on) are stated in
test-requirements.txt file, which is meant to contain testing specific
modules (nose, t
Hello All.
Glance cores (Mark Washenberger, Flavio Percoco, Iccha Sethi) have some
questions about Oslo DB code, and why is it so important to use it instead
of custom implementation and so on. As there were a lot of questions it was
really hard to answer on all this questions in IRC. So we decide
Hello.
Any suggestions, please?
On Mon, Jul 22, 2013 at 11:39 AM, Victor Sergeyev wrote:
> Hi All.
>
> There is a blueprint (
> https://blueprints.launchpad.net/nova/+spec/db-reconnect) by Devananda
> van der Veen, which goal is to implement reconnection to a database and
> re
Hi All.
There is a blueprint (
https://blueprints.launchpad.net/nova/+spec/db-reconnect) by Devananda van
der Veen, which goal is to implement reconnection to a database and
retrying of the last operation if a db connection fails. I’m working on the
implementation of this BP in oslo-incubator (
ht
Hello All.
I have a question about the patch `Add unique constraint to FixedIp` (see
https://review.openstack.org/#/c/29364/), which is a part of blueprint
`Complete db unique key enforcement on all tables dbs` (
https://blueprints.launchpad.net/nova/+spec/db-enforce-unique-keys).
There is a disc
34 matches
Mail list logo
