Lingxian, yes, that’s basically what I suggest too.
Renat Akhmerov
@ Mirantis Inc.
> On 22 Apr 2015, at 16:03, Lingxian Kong wrote:
>
> Hi all,
>
> In my understanding, the meaning of the 'break-on' in 'retry' policy
> is just give an oppotunity to end the task execution earlier, i.e. we
> d
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
On 04/22/2015 04:09 AM, Angus Salkeld wrote:
> Hi
>
> Can we please have a new release of novaclient (after the below fix)?
>
> Heat's unit tests pass fine with:
> python-novaclient (2.23.0)
>
> but python-novaclient 2.24.0 introduces this bug:
> https://bugs.launchpad.net/python-novaclient/+bug
On Wed, Apr 22, 2015 at 12:57:01PM +0200, Kashyap Chamarthy wrote:
> On Tue, Apr 21, 2015 at 02:58:57PM -0700, Joe Gordon wrote:
> > On Fri, Apr 17, 2015 at 1:22 AM, Victor Stinner wrote:
> >
> > > >> For the full list, see the wiki page:
> > > >> https://wiki.openstack.org/wiki/Python3#Core_Open
On Tue, Apr 21, 2015 at 02:58:57PM -0700, Joe Gordon wrote:
> On Fri, Apr 17, 2015 at 1:22 AM, Victor Stinner wrote:
>
> > >> For the full list, see the wiki page:
> > >> https://wiki.openstack.org/wiki/Python3#Core_OpenStack_projects
> >
> > > Thanks for updating the wiki page that is a very use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/22/2015 05:01 AM, Doug Hellmann wrote:
> Excerpts from Ihar Hrachyshka's message of 2015-04-17 14:45:58
> +0200:
>> Hi,
>>
>> tl;dr neutron has special semantics for policy targets that
>> relies on private symbols from oslo.policy, and it's i
Hi all
I am having trouble running tox tests on neutron-lbaas on a default clone. I
can see from the tox logs that it downloads the neutron egg just fine, however,
when running some of the tests it gets import errors when trying to import from
the neutron side of things.
I checked the neutro
Hi,
Ian Bicking allowed me to publish new versions of the Paste project:
https://bitbucket.org/ianb/paste
This project blocked many OpenStack applications to be ported to Python 3:
https://wiki.openstack.org/wiki/Python3#OpenStack_applications
Good news: I just released Paste 2.0 which h
Hi,
It's moving fast. I'm currently working on porting remaining libraries to
prepare my spec for nova.
> oslo.db -- looks like it is almost there
I don't know the status of oslo.db support of Python 3. I guess that it already
works on Python 3, it's just a matter of running tests with MySQL
Hi all,
In my understanding, the meaning of the 'break-on' in 'retry' policy
is just give an oppotunity to end the task execution earlier, i.e. we
don't need to wait for all the iterations. I prefer that we keep the
ERROR state, and keep it simple.
On Wed, Apr 22, 2015 at 5:06 PM, Renat Akhmerov
Hi Madhuri,
1) I think we'd better not jump to v1beta3 API if our image not updated.
In release, we need to provide person with easy to use and function works
well.
As you mentioned, the v1beta3 not work with our image with many issues.
2) If we could update our image, which integrate the l
Hi,
sqlachemy-migrate already works on Python3. I sent a patch to add missing
Python 3 classifiers, so the "caniusepython3" automated tool will stop
reporting false alarm on this library.
https://review.openstack.org/174738
Or is someone aware of issues with Python 3?
Again, check the wiki pag
Hi All,
As we are using fedora-21-atomic-2 image and that has Kubernetes v0.11.0, I
tried to run v1beta3 APIs on it. Some of the APIs failed.
The Kubernetes developer said "v1beta3 wasn't fully supported until the
0.15.0 release". Hence this is causing some APIs to fail.
Below are the failures:
Hey fellow developers,
I'd like to announce my candidacy for the Technical Committee election
that's happening.
TL;DR: Vote for me to bring back the fun and raise the bar! :)
As you might know, I've been a member of the OpenStack community for
several years now, and I actually already seated a
Ok, after all thinking my suggestion is to leave "break-on” but clarify its
semantics and behavior a little bit as follow:
As Dmitri wrote before “success-on” and “error-on” may be easily confused with
“on-success” and “on-error”.
“retry" policy loop may only stop if:
Task action/workflow complet
Robert Collins wrote:
> Endish of my workday, but https://review.openstack.org/#/c/176113/ has
> some promise. It doesn't install the 'right' versions- thats something
> we're going to have to circle back on, but it does run the tests
> successfully, which should unwedge us and let us take a little
Hi, Since some of the regular folks are not going be available for the
meeting today, it was suggested that we skip the meeting today.
Best,
~Sumit.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 21/04/15 21:37, Ian Cordasco wrote:
> Also, isn’t sqlalchemy-migrate something we currently maintain (or a group
> of OpenStack developers do it for OpenStack. Can’t we work with them to
> add support for Python 3?
There seems to have been some work on that already:
https://github.com/stackforg
Ben Swartzlander wrote:
> My main request was that the Manila sessions didn't overlap with the
> Cinder sessions, since there are some key people who are involved in
> both projects. It looks like some attempt was made to avoid overlaps
> (the fishbowl sessions at least), but the working sessions c
Cross-posting to operators@ as I think they are rather interested in the
$subject :-)
Le 21/04/2015 23:42, Artom Lifshitz a écrit :
Hello,
I'd like to gauge acceptance of introducing a feature that would give operators
a config option to perform real database deletes instead of soft deletes.
Hi,
Thank you for putting it up Dmitry.
As I wrote into the blueprint,
if there are requests to implement API aborting introspection from
operators,
we should introduce this feature as API, I think.
But if we just want to use this feature as debug,
we had better not to introduce it as API.
And,
Hi
Can we please have a new release of novaclient (after the below fix)?
Heat's unit tests pass fine with:
python-novaclient (2.23.0)
but python-novaclient 2.24.0 introduces this bug:
https://bugs.launchpad.net/python-novaclient/+bug/1437244
We still need this patch in: https://review.openstack
Hi,
I'd like to announce my candidacy for re-election to the TC.
About Me
I am the PTL for the OpenStack Infrastructure Program, which I have
been helping to build for nearly four years. I have also served on
the TC since the Icehouse cycle.
I am responsible for a significant portion
Yatin,
Please, feel free to add it. Even better if you can help us with the proper
documentation.
Thanks,
Edgar
From: yatin kumbhare mailto:yatinkumbh...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesd
But maybe some component depend on another one. And it would be difficult to
test all the components combination.
/Yalei
From: Guo, Ruijing [mailto:ruijing@intel.com]
Sent: Wednesday, April 22, 2015 10:23 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [opens
101 - 125 of 125 matches
Mail list logo
