-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey all,
as per [1], Cisco Nexus ML2 plugin requires a patched version of
ncclient from github. I wonder:
- - whether this information is still current;
- - why don't we depend on ncclient thru our requirements.txt file.
[1]: https://wiki.openstac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/08/14 17:12, Henry Gessau wrote:
> On 8/12/2014 10:27 AM, Ihar Hrachyshka wrote:
>> as per [1], Cisco Nexus ML2 plugin requires a patched version of
>> ncclient from github. I wonder:
>>
>> - - whether this i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/08/14 09:28, Angus Lees wrote:
> I'm doing various small cleanup changes as I explore the neutron
> codebase. Some of these cleanups are to fix actual bugs discovered
> in the code. Almost all of them are tiny and "obviously correct".
>
> A r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
several periodic checks for havana are failing due to missing
libffi-devel or missing rpm/yum tools on bare-centos (sic!) node.
For example, see [1] (rpm/yum missing) and [2] (compile failure due to
missing libffi-devel).
AFAIK there is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/08/14 14:07, Daniel P. Berrange wrote:
> On Wed, Aug 13, 2014 at 12:55:48PM +0100, Steven Hardy wrote:
>> On Wed, Aug 13, 2014 at 11:42:52AM +0100, Daniel P. Berrange
>> wrote:
>>> On Thu, Aug 07, 2014 at 03:56:04AM -0700, Jay Pipes wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/08/14 02:43, Angus Lees wrote:
> On Wed, 13 Aug 2014 11:11:51 AM Kevin Benton wrote:
>> Is the pylint static analysis that caught that error prone to
>> false positives? If not, I agree that it would be really nice if
>> that were made part of
tack.org/114213
/Ihar
On 12/08/14 16:27, Ihar Hrachyshka wrote:
> Hey all,
>
> as per [1], Cisco Nexus ML2 plugin requires a patched version of
> ncclient from github. I wonder:
>
> - whether this information is still current; - why don't we depend
> on ncclient thru o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
some plugins depend on modules that are not mentioned in
requirements.txt. Among them, Cisco Nexus (ncclient), Brocade
(ncclient), Embrane (heleosapi)... Some other plugins put their
dependencies in requirements.txt though (like Arista depen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/08/14 13:09, Osanai, Hisashi wrote:
>
> Hi,
>
> On Tuesday, August 05, 2014 8:57 PM, Ihar Hrachyshka wrote:
>>> Thanks. To facilitate quicker backport, you may also propose
>>> the patch for review yourself.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+1. [Not being an oslo core in any way,] I think Mike, with all his
prior experience and vision on where oslo.db should strive to, will be
a great addition to the core team.
/Ihar
On 15/08/14 10:21, Roman Podoliaka wrote:
> Hi Oslo team,
>
> I prop
g inside
Oracle. I'll update once I know more about that.
- - once all the relevant patches land in affected projects and
devstack, I'm going to introduce a separate gate job to run against
mysqlconnector.
Cheers,
/Ihar
On 22/07/14 15:03, Ihar Hrachyshka wrote:
> FYI: I've mov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17/08/14 02:09, Angus Lees wrote:
>
> On 16 Aug 2014 06:09, "Doug Hellmann" <mailto:d...@doughellmann.com>> wrote:
>>
>>
>> On Aug 15, 2014, at 9:29 AM, Ihar Hrachyshka
>> <mailto:ihrac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/08/14 11:00, Thierry Carrez wrote:
> Mark McLoughlin wrote:
>> [...] I don't see how any self-respecting open-source project can
>> throw a release over the wall and have no ability to address
>> critical bugs with that release until the next r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/08/14 18:33, Ben Nemec wrote:
> On 08/14/2014 08:37 AM, Ihar Hrachyshka wrote:
>> Hi all,
>
>> some plugins depend on modules that are not mentioned in
>> requirements.txt. Among them, Cisco Nexus (ncclient), Brocade
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I've found out there are no clear public instructions on how to handle
oslo-incubator synchronizations in master and stable branches neither
at [1] nor at [2]. Though my observations show that there is some oral
tradition around community on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 19/08/14 17:33, wrote:
> Hi,all I can't found the clear python version? in the document of
> the openstack.org?. Colud someone can tell me whether the havana or
> the icehouce supports the python 2.7.5?Does it shoudmodify the
> code?? to supp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks!
And I'm immediately bumping the version [1] to utilize
raise_on_warnings=False for my mysql-connector effort. :)
[1]: https://review.openstack.org/115626
On 20/08/14 14:38, Victor Sergeyev wrote:
> Hello Folks!
>
> Oslo team is pleased to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 20/08/14 15:42, Vijay Venkatachalam wrote:
> Hi,
>
> I am writing a unit testcase with context as subnet, code here [1].
> When the context exits a delete of subnet is attempted and I am
> getting a MismatchError . Traceback posted here [2].
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I've read the proposal for incubator as described at [1], and I have
several comments/concerns/suggestions to this.
Overall, the idea of giving some space for experimentation that does
not alienate parts of community from Neutron is good. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 20/08/14 18:28, Salvatore Orlando wrote:
> Some comments inline.
>
> Salvatore
>
> On 20 August 2014 17:38, Ihar Hrachyshka <mailto:ihrac...@redhat.com>> wrote:
>
> Hi all,
>
> I've read the proposal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 08:33, loy wolfe wrote:
>> It's also unfair that core team reviewers are forced to spend
>> time on 3rd plugins and drivers under existing process. There are
>> so many 3rd networking backend technologies, from hardware to
>> controller,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 02:03, Clark Boylan wrote:
> On Mon, Aug 18, 2014, at 01:59 AM, Ihar Hrachyshka wrote: On
> 17/08/14 02:09, Angus Lees wrote:
>>>>
>>>> On 16 Aug 2014 06:09, "Doug Hellmann" &g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 09:42, Endre Karlson wrote:
> Why pymysql over mysql-python?
>
http://specs.openstack.org/openstack/oslo-specs/specs/juno/enable-mysql-connector.html#problem-description
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 18:34, Dolph Mathews wrote:
>
> On Thu, Aug 21, 2014 at 11:21 AM, Daniel P. Berrange
> mailto:berra...@redhat.com>> wrote:
>
> On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote:
>> "I would prefer that you didn't merge this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
this week is quite bumpy for unit testing in gate. First, it was
upgrade to new 'tox' version that broke quite some branches.
And today new testtools 0.9.36 were released and were caught by gate,
which resulted in the following unit test fa
following backport:
https://review.openstack.org/116271
/Ihar
On 22/08/14 14:55, Ihar Hrachyshka wrote:
> Hi all,
>
> this week is quite bumpy for unit testing in gate. First, it was
> upgrade to new 'tox' version that broke quite some branches.
>
> And today new te
Neutron, it should be handled by the following backport:
https://review.openstack.org/116271
/Ihar
On 22/08/14 14:55, Ihar Hrachyshka wrote:
> Hi all,
>
> this week is quite bumpy for unit testing in gate. First, it was
> upgrade to new 'tox' version that broke quite s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24/08/14 20:40, Maru Newby wrote:
>
> On Aug 24, 2014, at 5:14 PM, Henry Gessau
> wrote:
>
>> Ihar Hrachyshka wrote:
>>> Now, maybe putting the module into requirements.txt is an
>>> overkill (though I
for new testtools?
[1]:
https://review.openstack.org/#/q/I10c58b3af75d3ab9153a8bbd2a539bf1577de328,n,z
/Ihar
On 09/07/14 13:17, Ihar Hrachyshka wrote:
> Hi all,
>
> Multiple projects are suffering from db lock timeouts due to
> deadlocks deep in mysqldb library that we use to inte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 13:20, Sean Dague wrote:
> On 09/12/2014 06:41 AM, Ihar Hrachyshka wrote:
>> Some updates/concerns/questions.
>>
>> The status of introducing a new driver to gate is:
>>
>> - all the patches for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 16:33, Mike Bayer wrote:
> I agree with this, changing the MySQL driver now is not an option.
That was not the proposal. The proposal was to introduce support to
run against something different from MySQLdb + a gate job for that
alternat
/StableBranch#Proposing_Fixes
On 19/08/14 15:52, Ihar Hrachyshka wrote:
> Hi all,
>
> I've found out there are no clear public instructions on how to
> handle oslo-incubator synchronizations in master and stable
> branches neither at [1] nor at [2]. Though my observations show
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 17:30, Mike Bayer wrote:
>
> On Sep 12, 2014, at 10:40 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 12/09/14 16:33, Mike Bayer wrote:
>>> I agree with this, changing the MySQL driver now is not an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 19:08, Doug Hellmann wrote:
>
> On Sep 12, 2014, at 1:03 PM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 12/09/14 17:30, Mike Bayer wrote:
>>>
>>> On Sep 12, 2014, at 10:40 AM, Ihar Hrachys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 18:00, Mike Bayer wrote:
>
> On Sep 12, 2014, at 11:56 AM, Johannes Erdfelt
> wrote:
>
>> On Fri, Sep 12, 2014, Doug Hellmann
>> wrote:
>>> I don’t think we will want to retroactively change the
>>> migration scripts (that’s not somet
Hi all,
I'm new to openstack and qpid, trying to get more insight into messaging. I've
attempted to verify the fix for the bug 1257293 in LP, but the scenario fails
for me, even though oslo.messaging fix reached github master I used for my
verification attempt.
Briefly, I've repeated actions f
I've asked Mark McClain to tag a new release before *specifically* because
we're going to hit the issue. The issue is in both master and stable/havana.
Latest client releases were tagged by Mark, but since he seems to be busy these
days, I think someone should step in and tag and release a new c
And for those interested in details:
the issue was triggered by 3799efe792700e773c40cc42c265eee09230 in master
(15a912b1ca3c24ba8851b8b77d6de8027e120d78 in stable/havana). The required fix
in neutronclient that should be released ASAP is:
02baef46968b816ac544b037297273ff6a4e8e1b. I'm going t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/11/14 20:17, Jay S. Bryant wrote:
> All,
>
> This is a question I have been struggling with for Cinder recently.
> Where do we draw the line on backports. How do we handle config changes?
>
> One thing for Cinder I am also considering, in ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/10/14 11:52, Steven Hardy wrote:
> On Mon, Oct 20, 2014 at 03:27:19PM -0700, Joe Gordon wrote:
>> On Mon, Oct 20, 2014 at 11:12 AM, gordon chung
>> wrote:
>>
>>> The issue I'm highlighting is that those projects using the
>>> code now
>> have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
we've introduced a regression when backporting the following patch [1]
which shows up as metadata proxy process not spawned for networks with
a ipv6 subnet. There was no official Juno release that would include
the patch though, yet. The iss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+2
On 27/11/14 10:15, Alan Pevec wrote:
> +1
>
> ___ OpenStack-dev
> mailing list OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-BEGIN PGP S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 27/11/14 12:09, Thomas Goirand wrote:
> On 11/27/2014 12:31 AM, Donald Stufft wrote:
>>
>>> On Nov 26, 2014, at 10:34 AM, Thomas Goirand
>>> wrote:
>>>
>>> Hi,
>>>
>>> I tried to package suds-jurko. I was first happy to see that
>>> there was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 27/11/14 19:10, Thomas Goirand wrote:
> On 11/28/2014 12:06 AM, Ihar Hrachyshka wrote:
>> On 27/11/14 12:09, Thomas Goirand wrote:
>>> On 11/27/2014 12:31 AM, Donald Stufft wrote:
>>>>
>>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 28/11/14 01:26, Angus Lees wrote:
> Context: https://review.openstack.org/#/c/135616
>
> As far as I can make out, the fix for CVE-2014-7821 removed a backslash
> that effectively disables the negative look-ahead assertion that
> verifies that ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Indeed, the review queue is non-responsive. There are other patches in
the queue that bit rot there:
https://review.openstack.org/#/q/status:open+project:stackforge/sqlalchemy-migrate,n,z
I guess since no one with a +2 hammer systematically monitor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Are we going to have stable releases for those branches?
On 01/12/14 15:19, Doug Hellmann wrote:
> As part of setting up version caps for Oslo and client libraries in
> the stable branches, we discovered that the fact that we do not
> always create
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It's weird: we run python33 job for gate but not checks. Adding Cyril
Roelandt who ported the library to py3 to CC.
On 01/12/14 23:40, Thomas Goirand wrote:
> On 12/01/2014 06:19 PM, Ihar Hrachyshka wrote:
>> Indeed, the revie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/12/14 21:19, Kyle Mestery wrote:
> On Mon, Dec 1, 2014 at 6:12 AM, Assaf Muller
> wrote:
>>
>>
>> - Original Message -
>>>
>>> My proposal here, is, _let’s not deprecate this setting_, as
>>> it’s a valid use case of a gateway confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/12/14 14:22, Alan Pevec wrote:
> Hi all,
>
> here are exception proposal I have collected when preparing for
> the 2014.2.1 release, stable-maint members please have a look!
>
>
> General: cap Oslo and client library versions - sync from
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> On Thursday, 4 de December de 2014 at 15:06, Miguel Ángel Ajo
> wrote:
>
>>
>>
>> During Juno, we introduced the enhanced security groups rpc
>> (security_groups_info_for_devices) instead of
>> (security_group_rules_for_devices), and the ipset
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/12/14 14:22, Alan Pevec wrote:
> Hi all,
>
> here are exception proposal I have collected when preparing for
> the 2014.2.1 release, stable-maint members please have a look!
>
>
> General: cap Oslo and client library versions - sync from
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/12/14 16:59, Vadivel Poonathan wrote:
> Hi Kyle and all,
>
> Was there any conclusion in the design summit or the meetings
> afterward about splitting the vendor plugins/drivers from the
> mainstream neutron and documentation of out-of-tree
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/12/14 21:58, Doug Hellmann wrote:
> As we’ve discussed a few times, we want to isolate applications
> from the configuration options defined by libraries. One way we
> have of doing that is the ConfigFilter class in oslo.config. When a
> regula
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+100. I vote -1 there and would like to point out that we *must* keep
history during the split, and split from u/s code base, not random
repositories. If you don't know how to achieve this, ask oslo people,
they did it plenty of times when graduating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/12/14 22:12, Jeremy Stanley wrote:
> On 2014-12-10 16:07:35 -0500 (-0500), Jay Pipes wrote:
>> On 12/10/2014 04:05 PM, Jeremy Stanley wrote:
>>> I think the bigger question is whether the lack of a quota
>>> implementation for everything a ten
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/12/14 00:05, Mathieu Gagné wrote:
> We recently had an issue in production where a user had 2
> "default" security groups (for reasons we have yet to identify).
This is probably the result of the race condition that is discussed in
the thread:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Reading the latest comments at
https://github.com/PyMySQL/PyMySQL/issues/275, it seems to me that the
issue is not to be solved in drivers themselves but instead in
libraries that arrange connections (sqlalchemy/oslo.db), correct?
Will the proposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
the question arose recently in one of reviews for neutron-*aas repos
to remove all oslo-incubator code from those repos since it's
duplicated in neutron main repo. (You can find the link to the review
at the end of the email.)
Brief hostory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15/12/14 15:15, Ihar Hrachyshka wrote:
> - it's a delusion that there will be no neutron-main syncs that
> will break neutron-*aas repos ever.
OK, I've just decided to check whether my (non-native speaker)
understanding of th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/12/14 09:45, Thomas Goirand wrote:
> Hi,
>
> As I am slowing fixing all systemd issues for the daemons of
> OpenStack in Debian (and hopefully, have this ready before the
> freeze of Jessie), I was wondering what kind of Type= directive to
> p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I was (rightfully) asked to share my comments on the matter that I
left in gerrit here. See below.
On 12/12/14 22:40, Sean Dague wrote:
> On 12/12/2014 01:05 PM, Maru Newby wrote:
>>
>> On Dec 11, 2014, at 2:27 PM, Sean Dague wrote:
>>
>>> On 12/
option 2, but it implies a few things
>>> about your time, and I wanted to chat with you before
>>> presuming.
>>>
>>> Maintenance can not involve breaking changes. At this point,
>>> the co-gate will block it. Also, oslo graduation changes will
&
.
>
> Thanks, doug
>
>
> On 12/15/14, 6:15 AM, "Ihar Hrachyshka"
> wrote:
>
> Hi all,
>
> the question arose recently in one of reviews for neutron-*aas
> repos to remove all oslo-incubator code from those repos since
> it's duplicated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/12/14 12:50, Doug Hellmann wrote:
>
> On Dec 16, 2014, at 5:13 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 15/12/14 18:57, Doug Hellmann wrote:
>>> There may be a similar problem managing dependencies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/12/14 12:52, Doug Hellmann wrote:
>
> On Dec 16, 2014, at 5:22 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 15/12/14 17:22, Doug Wiegley wrote:
>>> Hi Ihar,
>>>
>>> I’m actually in f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/12/14 13:41, Doug Hellmann wrote:
>
> On Dec 16, 2014, at 7:27 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 16/12/14 12:50, Doug Hellmann wrote:
>>>
>>> On Dec 16, 2014, at 5:13 AM, Ihar Hrachys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I suspect that's some Red Hat distro, and radvd lacks SELinux context
set to allow neutron l3 agent to spawn it.
On 18/12/14 15:50, Jerry Zhao wrote:
> It seems that radvd was not spawned successfully in l3-agent log:
>
> Dec 18 11:23:34 ci-overclo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/11/14 20:26, Thomas Goirand wrote:
> On 11/01/2014 11:29 PM, Kashyap Chamarthy wrote:
>> On Sat, Nov 01, 2014 at 09:13:21PM +0800, Thomas Goirand wrote:
>>> Hi,
>>>
>>> I was wondering if some distribution OpenStack package
>>> maintainers wou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 23/12/14 08:17, Thomas Goirand wrote:
> On 12/19/2014 11:55 PM, Ihar Hrachyshka wrote:
>> Note that OSLO_PACKAGE_VERSION is not public.
>
> Well, it used to be public, it has been added and discussed a few
> years ago becau
On 01/06/2015 03:09 AM, Matt Riedemann wrote:
On 1/5/2015 2:16 PM, Doug Hellmann wrote:
On Jan 5, 2015, at 12:22 PM, Doug Hellmann
wrote:
On Jan 5, 2015, at 12:00 PM, Matt Riedemann
wrote:
There is a deprecation warning in pip 6.0.6 which is making the
py26 (on stable branches) an
On 01/06/2015 12:04 PM, foss geek wrote:
Dear All,
Is it possible to configure neutron to take VM ip from external DHCP
server?
I am having All In One openstack env deployed using devstack icehouse.
I am looking for an option to integrate it with external DHCP server.
At the moment, there
On 01/06/2015 05:33 PM, Daniel P. Berrange wrote:
On Tue, Jan 06, 2015 at 10:21:10AM -0600, Matt Riedemann wrote:
Odd...eventlet 0.16.0 was released on 12/30 and the eventlet.util import is
still in the libvirt host module, but this isn't blowing up in the Jenkins
runs, so what's different? The
On 01/06/2015 08:32 PM, Adam Gandelman wrote:
Hiya-
Flavio has been actively involved in stable branch maintenance for as
long as I can remember, but it looks like his +2 abilities were
removed after the organizational changes made to the stable
maintenance teams. He has expressed interest i
Hi,
FYI I've created draft release notes for 2014.2.2:
https://wiki.openstack.org/wiki/ReleaseNotes/2014.2.2
I assume that Trove will be released for 2014.2.2, so I've added it to
the list of projects.
Feel free to add more notes there.
/Ihar
___
Hi all,
I've found out that dnsmasq < 2.67 does not work properly for IPv6
clients when it comes to MAC address matching (it fails to match, and so
clients get 'no addresses available' response). I've requested version
bump to 2.67 in: https://review.openstack.org/145482
Now, since we've alr
o the operators?
On Wed, Jan 7, 2015 at 6:57 AM, Kyle Mestery <mailto:mest...@mestery.com>> wrote:
On Wed, Jan 7, 2015 at 8:21 AM, Ihar Hrachyshka
mailto:ihrac...@redhat.com>> wrote:
Hi all,
I've found out that dnsmasq < 2.67 does not work pro
hursday, 8 de January de 2015 at 12:36, Ihar Hrachyshka wrote:
The problem is probably due to the fact that some operators may run
neutron from git and manage their dependencies in some other way;
or distributions may suck sometimes, so packagers may miss the
release note and fail to upgrade d
On 01/07/2015 03:21 PM, Ihar Hrachyshka wrote:
Hi all,
I've found out that dnsmasq < 2.67 does not work properly for IPv6
clients when it comes to MAC address matching (it fails to match, and
so clients get 'no addresses available' response). I've requested
version
On 01/05/2015 04:51 PM, Doug Hellmann wrote:
As each library is released, we will send release notes to this list, as usual. At that point
the Oslo liaisons should start planning patches to change imports in their projects from
"oslo.foo" to “oslo_foo". The old imports should still work for now
to be safe. Shouldn't take a ton of effort.
Jay
On Jan 8, 2015 12:03 PM, "Doug Hellmann" <mailto:d...@doughellmann.com>> wrote:
> On Jan 8, 2015, at 11:29 AM, Ihar Hrachyshka
mailto:ihrac...@redhat.com>> wrote:
>
> On 01/05/2015 04:51 PM, Doug H
On 01/08/2015 07:03 PM, Doug Hellmann wrote:
I’m not sure that’s something we need to enforce. Liaisons should be updating
projects now as we release libraries, and then we’ll consider whether we can
drop the namespace packages when we plan the next cycle.
Without a hacking rule, there is a c
On 01/09/2015 11:44 AM, Thierry Carrez wrote:
Hi stable-maint people,
We seem to still have a number of issues with stable branch in the gate,
both in Icehouse and Juno. I'd like to help where I can but I have a bit
of a hard time tracking down the remaining failures and things that have
already
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our take on that? Shouldn't clients still support Python 2.6?
[1]:
https://github.com/openstack/ironic-python-agent/commit/d95a99d5d1a62ef5c085ce
On 01/09/2015 02:33 PM, Andreas Jaeger wrote:
On 01/09/2015 02:25 PM, Ihar Hrachyshka wrote:
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our take on that? Shouldn't clients sti
g the appropriate
namespace so that we don't have the wrong usage sneak in.
I haven't gotten any rules written yet. Have had to attend to a family
commitment the last few days. Hope that I can tackle the namspace changes
next week.
Jay
On 01/08/2015 12:24 PM, Ihar Hrachyshka wrote:
On 01/0
You can get Python 2.7 via SCL:
https://www.softwarecollections.org/en/scls/rhscl/python27/
On 01/12/2015 05:32 PM, Igor Kalnitsky wrote:
Hi, Roman,
Indeed, we have to go forward and drop python 2.6 support. That's how
it supposed to be, but, unfortunately, it may not be as easy as it
seems at
On 01/14/2015 11:15 AM, Jakub Libosvar wrote:
On 01/14/2015 10:58 AM, yatin kumbhare wrote:
Many of them on gerrit page.
Mine is also one of them.
https://review.openstack.org/#/c/145290/
Regards,
Yatin
The cause is that nova-compute cannot start on stable/juno branch:
http://logs.openstack.o
On 01/09/2015 01:02 PM, Ihar Hrachyshka wrote:
I think we should have some common document (etherpad?) with branch
status and links.
OK, I moved forward and created an Etherpad. I also filed it in with
current state. Please fill it in with updates.
https://etherpad.openstack.org/p/stable
On 01/14/2015 01:44 PM, Daniel P. Berrange wrote:
On Wed, Jan 14, 2015 at 07:39:59AM -0500, Sean Dague wrote:
On 01/14/2015 04:08 AM, Dr. Jens Rosenboom wrote:
Am 14/01/15 um 05:17 schrieb Adam Gandelman:
So eventlet 0.16.x has started hitting slaves and breaking stable
branches
(its not like
On 01/15/2015 01:42 PM, Sean Dague wrote:
The stable/havana branch of devstack was deleted when the stable/havana
branches of the projects were end of lifed.
That said, tag is still there:
http://git.openstack.org/cgit/openstack-dev/devstack/tag/?id=havana-eol
___
Hi Kyle/all,
(we were going to walk thru that on Mon, but since US is on vacation
today, sending it via email to openstack-dev@.)
So I've talked to Doug Hellmann from oslo, and here is what we have in
our oslo queue to consider:
1. minor oslo.concurrency cleanup for *aas repos (we need to d
Hi all,
Any updates from infra on why it occurs? It's still one of the issues
that make periodic stable jobs fail.
We also have other failures due to missing packages on nodes. F.e.,
keystone python-ldap installation failing due to missing devel files for
openldap:
http://logs.openstack.org
Unit tests should run successfully in a very limited environment, with
no sudo, namespaces etc. Some packagers even run unit tests as part of
their build process in hardened environment (I know Debian does, and
some teams from Red Hat consider it too, like Neutron).
So if it really needs to in
On 01/20/2015 05:40 PM, Paul Michali wrote:
Review https://review.openstack.org/#/c/146508/ is adding support for
StrongSwan VPN, which needs mount bind to be able to specify different
paths for config files.
The code, which used some older patch, does a test for /proc/1/ns/net,
instead of /p
Hi all,
as per:
https://github.com/openstack/neutron-specs/blob/master/specs/kilo/core-vendor-decomposition.rst,
neutron is going to spin off vendor plugins into separate trees outside
of neutron core team control. This raises several questions on how we
are going to handle stable branches th
thing I would like to add is that the deadline for stable/juno is only
one week away - hence, it raises the urgency to call for action.
Thanks
-Sukhdev
On Jan 21, 2015 1:43 PM, "Ihar Hrachyshka" <mailto:ihrac...@redhat.com>> wrote:
>
> Hi all,
>
> as per:
https
On 01/23/2015 05:38 PM, Mike Bayer wrote:
Doug Hellmann wrote:
We put the new base class for RequestContext in its own library because
both the logging and messaging code wanted to influence it's API. Would
it make sense to do this database setup there, too?
whoa, where’s that? is this an os
Hi Andreas,
On 01/26/2015 10:58 AM, Andreas Scheuring wrote:
Hi Ihar,
we're currently running stable/juno devstack on rhel7 base. But I see
troubles to get it running on the master branch due to bug 1408297.
The fix for this bug increases the minimal dnsmasq version for master
branch up to 2.6
On 01/26/2015 11:00 AM, Julie Pichon wrote:
On 26/01/15 06:34, A mailing list for the OpenStack Stable Branch test
reports. wrote:
Build failed.
- periodic-horizon-docs-icehouse
http://logs.openstack.org/periodic-stableperiodic-horizon-docs-icehouse/9382030/
: SUCCESS in 4m 14s
- periodic-hor
1 - 100 of 932 matches
Mail list logo
