<div dir="ltr"><br><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">shreeya<br></div></div></div>
<br><div class="gmail_quote">On Thu, Jul 14, 2016 at 1:17 AM, <span dir="ltr"><<a href="mailto:openstack-dev-request@lists.openstack.org" target="_blank">openstack-dev-request@lists.openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send OpenStack-dev mailing list submissions to<br>
<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openstack-dev-request@lists.openstack.org">openstack-dev-request@lists.openstack.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openstack-dev-owner@lists.openstack.org">openstack-dev-owner@lists.openstack.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OpenStack-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [TripleO] Making TripleO CI easier to consume outside of<br>
TripleO CI (Wesley Hayutin)<br>
2. Re: [mistral] [murano] [yaql] yaqluator bug (Alexey Khivin)<br>
3. Re: [TripleO] Making TripleO CI easier to consume outside of<br>
TripleO CI (Michal Pryc)<br>
4. Re: [kolla] New specs process - a dicussion (Steven Dake (stdake))<br>
5. Re: [TripleO] Making TripleO CI easier to consume outside of<br>
TripleO CI (Wesley Hayutin)<br>
6. [Neutron][DVR] - No IRC Meeting today (Brian Haley)<br>
7. [storlets] IRC meeting times (<a href="mailto:eran@itsonlyme.name">eran@itsonlyme.name</a>)<br>
8. Re: [cinder] [nova] os-brick privsep failures and an upgrade<br>
strategy? (Ivan Kolodyazhny)<br>
9. [new][oslo] debtcollector 1.6.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
10. [new][oslo] mox3 0.17.0 release (newton) (<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
11. [new][oslo] futurist 0.15.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
12. [new][oslo] oslo.cache 1.11.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
13. [new][oslo] automaton 1.3.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
14. [new][oslo] oslo.config 3.13.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
15. [new][oslo] oslo.context 2.6.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
16. [new][oslo] oslo.concurrency 3.12.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
17. [new][oslo] oslo.i18n 3.8.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
18. [new][oslo] oslo.middleware 3.15.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
19. [new][oslo] oslo.log 3.12.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
20. [new][oslo] oslo.db 4.8.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
21. Re: The future of OpenStack documentation (Markus Zoeller)<br>
22. [new][oslo] oslo.reports 1.12.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
23. [new][oslo] oslo.privsep 1.10.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
24. [new][oslo] oslo.policy 1.12.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
25. [new][oslo] oslo.serialization 2.11.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
26. [new][oslo] oslo.versionedobjects 1.13.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
27. [new][oslo] oslo.rootwrap 4.4.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
28. [new][oslo] oslo.service 1.13.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
29. [new][oslo] oslotest 2.7.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
30. [new][oslo] taskflow 2.3.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
31. [new][oslo] oslosphinx 4.6.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
32. [new][oslo] oslo.vmware 2.11.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
33. [new][oslo] stevedore 1.16.0 release (newton)<br>
(<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
34. [new][oslo] tooz 1.41.0 release (newton) (<a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a>)<br>
35. [release][ptl][all] newton-2 milestone deadline 14 July<br>
(Doug Hellmann)<br>
36. Re: [new][oslo] mox3 0.17.0 release (newton) (Markus Zoeller)<br>
37. Re: The future of OpenStack documentation (Matt Kassawara)<br>
38. Re: [TripleO] Making TripleO CI easier to consume outside of<br>
TripleO CI (David Moreau Simard)<br>
39. Re: [TripleO] Making TripleO CI easier to consume outside of<br>
TripleO CI (Ricardo Carrillo Cruz)<br>
40. Re: The future of OpenStack documentation (Doug Hellmann)<br>
41. Re: [nova] focused review pipeline of bug fix changes?<br>
(Jeremy Stanley)<br>
42. Re: [nova] focused review pipeline of bug fix changes?<br>
(Jeremy Stanley)<br>
43. Re: [all][oslo] pbr potential breaking change coming<br>
(Jeremy Stanley)<br>
44. Re: [new][oslo] mox3 0.17.0 release (newton) (Jeremy Stanley)<br>
45. [app-catalog] App Catalog IRC meeting Thursday July 14th<br>
(Christopher Aedo)<br>
46. Re: [openstack-ansible] Nominating Jean-Philippe Evrard for<br>
core in openstack-ansible and all openstack-ansible-* roles<br>
(Jesse Pretorius)<br>
47. Re: [openstack-ansible] Nominating Jean-Philippe Evrard for<br>
core in openstack-ansible and all openstack-ansible-* roles<br>
(Steve Lewis)<br>
48. Re: [openstack-ansible] Nominating Jean-Philippe Evrard for<br>
core in openstack-ansible and all openstack-ansible-* roles<br>
(Carter, Kevin)<br>
49. [designate] Designate News Round Up (Hayes, Graham)<br>
50. Re: [openstack-ansible] Nominating Jean-Philippe Evrard for<br>
core in openstack-ansible and all openstack-ansible-* roles<br>
(Jimmy McCrory)<br>
51. Re: [all] Status of the OpenStack port to Python 3 (Denis Makogon)<br>
52. [Cinder][CI] Rule of recheck keywords has been updated<br>
(Watanabe, Isao)<br>
53. [nova] Let's kill quota classes (again) (Matt Riedemann)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 13 Jul 2016 08:13:41 -0400<br>
From: Wesley Hayutin <<a href="mailto:whayutin@redhat.com">whayutin@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [TripleO] Making TripleO CI easier to<br>
consume outside of TripleO CI<br>
Message-ID:<br>
<<a href="mailto:CAOHJT4JYNxMjnvYOYSDTWMNAJTHhXt3PTP23UhjbDjX9MdQjOw@mail.gmail.com">CAOHJT4JYNxMjnvYOYSDTWMNAJTHhXt3PTP23UhjbDjX9MdQjOw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Tue, Jul 12, 2016 at 3:39 PM, John Trowbridge <<a href="mailto:trown@redhat.com">trown@redhat.com</a>> wrote:<br>
<br>
> Howdy folks,<br>
><br>
> In the TripleO meeting two weeks ago, it came up that tripleo-quickstart<br>
> is being used as a CI tool in RDO. This came about organically, because<br>
> we needed to use RDO CI to self-gate quickstart (it relies on having a<br>
> baremetal virthost). It displaced another ansible based CI tool there<br>
> (khaleesi) and most(all?) of the extra functionality from that tool<br>
> (upgrades, scale, baremetal, etc.) has been moved into discrete ansible<br>
> roles that are able to plugin to quickstart.[1]<br>
><br>
> We are still left with two different tool sets, where one should suffice<br>
> (and focus CI efforts in one place).<br>
><br>
> I see two different ways to resolve this.<br>
><br>
> 1. Actively work on making the tripleo-ci scripts consumable external to<br>
> tripleo-ci. We have a project in RDO (WeiRDO)[2] that is consuming<br>
> upstream CI for packstack and puppet, so it is not totally far-fetched<br>
> to add support for TripleO jobs.<br>
><br>
<br>
I think we have to at least point out that RDO is not the only other target<br>
for a CI tool.<br>
There are a few more groups that would benefit from the leadership of the<br>
upstream CI system. Without<br>
calling out specific groups, I'm thinking of the various OpenStack network<br>
teams, performance teams,<br>
test teams, etc.. that rely on setting up TripleO as the base for their<br>
work. To make things a bit more complicated<br>
there is not a single source of requirements for the various groups that<br>
would benefit from a robust,<br>
flexible upstream TripleO CI tool set. I'm not convinced that the current<br>
bash scripts can be<br>
reworked or wrapped in a way that can be flexible enough to handle what is<br>
an essentially<br>
unknown set of requirements.<br>
<br>
IMHO we require a tool set that is pluggable, composable and flexible<br>
enough such that<br>
other development, and CI teams that rely on TripleO as the base for their<br>
work feel comfortable extending<br>
and replacing parts of the CI tool set to fit their needs.<br>
<br>
<br>
<br>
><br>
> Pros:<br>
> - All CI development just happens directly in tripleo-ci and RDO just<br>
> inherits that work.<br>
><br>
> Cons:<br>
> - This is totally untried, and therefore a totally unknown amount of work.<br>
> - It is all or nothing in that there is no incremental path to get the<br>
> CI scripts working outside of CI.<br>
> - We have to rewrite a bunch of working ansible code in bash which IMO<br>
> is the wrong direction for a modern CI system.<br>
><br>
><br>
> 2. Actively work on making tripleo-ci consume the ansible work in<br>
> tripleo-quickstart and the external role ecosystem around it.<br>
><br>
> Pros:<br>
> - This could be done incrementally, replacing a single function from<br>
> tripleo.sh with an invocation of tripleo-quickstart that performs that<br>
> function instead.<br>
> - We would be able to pull in a lot of extra functionality via these<br>
> external roles for free(ish).<br>
><br>
> Cons:<br>
> - Similarly unknown amount of work to completely switch.<br>
> - CI development would be done in multiple repos, though each would have<br>
> discrete and well defined functionality.<br>
><br>
><br>
> Personally, I don't think we should do anything drastic with CI until<br>
> after we release Newton, so we don't add any risk of impacting new<br>
> features that haven't landed yet. I do think it would be a good goal for<br>
> Ocata to have a CI system in TripleO that is consumable outside of<br>
> TripleO. In any case, this email is simply to garner feedback if other's<br>
> think this is a worthy thing to pursue and opinions on how we can get<br>
> there.<br>
><br>
<br>
+1 here. I agree there should be enough time for thoughtful conversation<br>
without<br>
disrupting higher priority work.<br>
<br>
Thanks for sending this out John!<br>
<br>
<br>
><br>
><br>
> [1]<br>
><br>
> <a href="https://github.com/redhat-openstack?utf8=%E2%9C%93&query=ansible-role-tripleo" rel="noreferrer" target="_blank">https://github.com/redhat-openstack?utf8=%E2%9C%93&query=ansible-role-tripleo</a><br>
> (note not all of these are actively used/developed)<br>
> [2] <a href="https://github.com/rdo-infra/weirdo" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo</a><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/15ec1005/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/15ec1005/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 13 Jul 2016 12:40:46 +0000<br>
From: Alexey Khivin <<a href="mailto:akhivin@gmail.com">akhivin@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug<br>
Message-ID:<br>
<CAB2Nh0L76XAyCZervTQ+OauzjjXF9cp+=<a href="mailto:W6yeMoyuWYrNGA7LA@mail.gmail.com">W6yeMoyuWYrNGA7LA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thank You Renat, Moshe, Stan and all!<br>
<br>
<br>
??, 6 ???. 2016 ?. ? 7:01, Renat Akhmerov <<a href="mailto:renat.akhmerov@gmail.com">renat.akhmerov@gmail.com</a>>:<br>
<br>
> Great! Alex, enjoy using yaqluator :)<br>
><br>
> Renat Akhmerov<br>
> @Nokia<br>
><br>
> On 05 Jul 2016, at 23:16, Elisha, Moshe (Nokia - IL) <<br>
> <a href="mailto:moshe.elisha@nokia.com">moshe.elisha@nokia.com</a>> wrote:<br>
><br>
> Thank you all for assisting.<br>
><br>
> When I tested Mistral I used an older version of Mistral (meaning an older<br>
> version of yaql).<br>
><br>
> I have verified that latest Mistral is working as expected.<br>
> I have upgraded the yaql library in yaqluator to 1.1.0 and it is now<br>
> working as expected.<br>
><br>
> Thanks!<br>
><br>
> From: Dougal Matthews <<a href="mailto:dougal@redhat.com">dougal@redhat.com</a>><br>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<br>
> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Date: Tuesday, 5 July 2016 at 17:53<br>
> To: "OpenStack Development Mailing List (not for usage questions)" <<br>
> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Subject: Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug<br>
><br>
><br>
><br>
> On 5 July 2016 at 08:32, Renat Akhmerov <<a href="mailto:renat.akhmerov@gmail.com">renat.akhmerov@gmail.com</a>> wrote:<br>
><br>
>> Stan, thanks for clarification. What?s the latest stable version that<br>
>> we?re supposed to use? global-requirements.txt has yaql>=1.1.0, I wonder<br>
>> if it?s correct.<br>
>><br>
><br>
> It is also worth looking at the upper-constraints.txt. It has 1.1.1 which<br>
> is the latest release. So it all seems up to date.<br>
><br>
><br>
> <a href="https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L376" rel="noreferrer" target="_blank">https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L376</a><br>
><br>
> I think the problem is that this external project isn't being updated.<br>
> Assuming they have not deployed anything that isn't committed, then they<br>
> are running YAQL 1.0.2 which is almost a year old.<br>
><br>
> <a href="https://github.com/ALU-CloudBand/yaqluator/blob/master/requirements.txt#L3" rel="noreferrer" target="_blank">https://github.com/ALU-CloudBand/yaqluator/blob/master/requirements.txt#L3</a><br>
><br>
><br>
>><br>
>> Renat Akhmerov<br>
>> @Nokia<br>
>><br>
>> On 05 Jul 2016, at 12:12, Stan Lagun <<a href="mailto:slagun@mirantis.com">slagun@mirantis.com</a>> wrote:<br>
>><br>
>> Hi!<br>
>><br>
>> The issue with join is just a yaql bug that is already fixed. The problem<br>
>> with yaqluator is that it doesn't use the latest yaql library.<br>
>><br>
>> Another problem is that it does't sets options correctly. As a result it<br>
>> is possible to bring the site down with a query that produces endless<br>
>> collection<br>
>><br>
>> Sincerely yours,<br>
>> Stan Lagun<br>
>> Principal Software Engineer @ Mirantis<br>
>><br>
>> <<a href="mailto:slagun@mirantis.com">slagun@mirantis.com</a>><br>
>><br>
>> On Tue, Jun 28, 2016 at 9:46 AM, Elisha, Moshe (Nokia - IL) <<br>
>> <a href="mailto:moshe.elisha@nokia.com">moshe.elisha@nokia.com</a>> wrote:<br>
>><br>
>>> Hi,<br>
>>><br>
>>> Thank you for the kind words, Alexey.<br>
>>><br>
>>> I was able to reproduce your bug and I have also found the issue.<br>
>>><br>
>>> The problem is that we did not create the parser with the engine_options<br>
>>> used in the yaql library by default when using the CLI.<br>
>>> Specifically, the "yaql.limitIterators" was missing? I am not sure that<br>
>>> this settings should have this affect but maybe the Yaql guys can comment<br>
>>> on that.<br>
>>><br>
>>> If we will change yaqluator to use this setting it will mean that<br>
>>> yaqluator will not be consistent with Mistral because Mistral is using YAQL<br>
>>> without this engine option (If I use your example in a workflow, Mistral<br>
>>> returns exactly like the yaqluator returns)<br>
>>><br>
>>><br>
>>> Workflow:<br>
>>><br>
>>> ---<br>
>>> version: '2.0'<br>
>>><br>
>>> test_yaql:<br>
>>> tasks:<br>
>>> test_yaql:<br>
>>> action: std.noop<br>
>>> publish:<br>
>>> output_expr: <% [1,2].join([3], true, [$1, $2]) %><br>
>>><br>
>>><br>
>>> Workflow result:<br>
>>><br>
>>><br>
>>> [root@s53-19 ~(keystone_admin)]# mistral task-get-published<br>
>>> 01d2bce3-20d0-47b2-84f2-7bd1cb2bf9f7<br>
>>> {<br>
>>> "output_expr": [<br>
>>> [<br>
>>> 1,<br>
>>> 3<br>
>>> ]<br>
>>> ]<br>
>>> }<br>
>>><br>
>>><br>
>>> As Matthews pointed out, the yaqluator is indeed OpenSource and<br>
>>> contributions are welcomed.<br>
>>><br>
>>> [1]<br>
>>> <a href="https://github.com/ALU-CloudBand/yaqluator/commit/e523dacdde716d200b5ed1015543d4c4680c98c2" rel="noreferrer" target="_blank">https://github.com/ALU-CloudBand/yaqluator/commit/e523dacdde716d200b5ed1015543d4c4680c98c2</a><br>
>>><br>
>>><br>
>>><br>
>>> From: Dougal Matthews <<a href="mailto:dougal@redhat.com">dougal@redhat.com</a>><br>
>>> Reply-To: "OpenStack Development Mailing List (not for usage<br>
>>> questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
>>> Date: Monday, 27 June 2016 at 16:44<br>
>>> To: "OpenStack Development Mailing List (not for usage questions)" <<br>
>>> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
>>> Subject: Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug<br>
>>><br>
>>> On 27 June 2016 at 14:30, Alexey Khivin <<a href="mailto:akhivin@gmail.com">akhivin@gmail.com</a>> wrote:<br>
>>><br>
>>>> Hello, Moshe<br>
>>>><br>
>>>> Tomorrow I discovered <a href="http://yaqluator.com" rel="noreferrer" target="_blank">yaqluator.com</a> for myself! Thanks for the useful<br>
>>>> tool!<br>
>>>><br>
>>>> But suddenly I was said that the expression<br>
>>>> [1,2].join([3], true, [$1, $2])<br>
>>>> evaluated to [[1,3]] on the yaqluator<br>
>>>><br>
>>>> A the same time this expression evaluated right when I using raw yaql<br>
>>>> interpreter.<br>
>>>><br>
>>>> Could we fix this issue?<br>
>>>><br>
>>>> By the way, don't you want to make yaqluator opensource? If you would<br>
>>>> transfer yaqluator to Openstack Foundation, then community will be able to<br>
>>>> fix such kind of bugs<br>
>>>><br>
>>><br>
>>> It looks like it is open source, there is a link in the footer:<br>
>>> <a href="https://github.com/ALU-CloudBand/yaqluator" rel="noreferrer" target="_blank">https://github.com/ALU-CloudBand/yaqluator</a><br>
>>><br>
>>><br>
>>>><br>
>>>> Thank you!<br>
>>>> Best regards, Alexey Khivin<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> __________________________________________________________________________<br>
>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>> Unsubscribe:<br>
>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe</a>><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>><br>
>>>><br>
>>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a><br>
>> ?subject:unsubscribe<br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe</a>><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/109ba2fa/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/109ba2fa/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 13 Jul 2016 14:54:20 +0200<br>
From: Michal Pryc <<a href="mailto:mpryc@redhat.com">mpryc@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [TripleO] Making TripleO CI easier to<br>
consume outside of TripleO CI<br>
Message-ID:<br>
<<a href="mailto:CACJAfezG30UZdFM_mrxba4j6rU3tdmnSAZvoh8bJCvjHpAV_0A@mail.gmail.com">CACJAfezG30UZdFM_mrxba4j6rU3tdmnSAZvoh8bJCvjHpAV_0A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
John,<br>
<br>
On Tue, Jul 12, 2016 at 9:39 PM, John Trowbridge <<a href="mailto:trown@redhat.com">trown@redhat.com</a>> wrote:<br>
<br>
> Howdy folks,<br>
><br>
> In the TripleO meeting two weeks ago, it came up that tripleo-quickstart<br>
> is being used as a CI tool in RDO. This came about organically, because<br>
> we needed to use RDO CI to self-gate quickstart (it relies on having a<br>
> baremetal virthost). It displaced another ansible based CI tool there<br>
> (khaleesi) and most(all?) of the extra functionality from that tool<br>
> (upgrades, scale, baremetal, etc.) has been moved into discrete ansible<br>
> roles that are able to plugin to quickstart.[1]<br>
><br>
><br>
Here is small sum of frameworks/tools to give you an idea what we are<br>
currently using to test RHOS components.<br>
<br>
To create Triple-O undercloud/overcloud we are using the:<br>
<br>
<a href="https://github.com/redhat-openstack/ansible-ovb" rel="noreferrer" target="_blank">https://github.com/redhat-openstack/ansible-ovb</a><br>
<br>
And then to install RHOSP on existing Triple-O:<br>
<br>
<a href="https://github.com/redhat-openstack/ansible-rhosp" rel="noreferrer" target="_blank">https://github.com/redhat-openstack/ansible-rhosp</a><br>
<br>
Then to run CI in such environment we use octario which is our main tool to<br>
run different flavors of tests and it's separate CI tool to be ready with<br>
different provisioning frameworks.<br>
<br>
<a href="https://github.com/redhat-openstack/octario/" rel="noreferrer" target="_blank">https://github.com/redhat-openstack/octario/</a><br>
<br>
<br>
In the simplistic environment to run simple tests we are using InfraRed to<br>
provision simple instance (without Triple-O):<br>
<br>
<a href="https://github.com/rhosqeauto/InfraRed" rel="noreferrer" target="_blank">https://github.com/rhosqeauto/InfraRed</a><br>
<br>
And then we run octario in such environment to run actual tests.<br>
<br>
Ideally if the provisioning parts were common and we could reuse them.<br>
Currently we need to use yet another set of tools to be able to patch rpm's<br>
prior to running tests.<br>
<br>
There was an idea planted by dsariel to move some of the playbooks into<br>
ansible-galaxy roles (possibly other teams had such idea as well), which I<br>
can see it's another +1 for going with tools currently developed by Wes as<br>
they are pretty separate and could be converted into ansible-galaxy, to be<br>
available across different use-cases, but then it would need to be well<br>
defined so the roles are not multiplied and we won't end up having similar<br>
roles.<br>
<br>
<br>
best<br>
Michal Pryc<br>
<br>
<br>
<br>
> We are still left with two different tool sets, where one should suffice<br>
> (and focus CI efforts in one place).<br>
><br>
> I see two different ways to resolve this.<br>
><br>
> 1. Actively work on making the tripleo-ci scripts consumable external to<br>
> tripleo-ci. We have a project in RDO (WeiRDO)[2] that is consuming<br>
> upstream CI for packstack and puppet, so it is not totally far-fetched<br>
> to add support for TripleO jobs.<br>
><br>
> Pros:<br>
> - All CI development just happens directly in tripleo-ci and RDO just<br>
> inherits that work.<br>
><br>
> Cons:<br>
> - This is totally untried, and therefore a totally unknown amount of work.<br>
> - It is all or nothing in that there is no incremental path to get the<br>
> CI scripts working outside of CI.<br>
> - We have to rewrite a bunch of working ansible code in bash which IMO<br>
> is the wrong direction for a modern CI system.<br>
><br>
><br>
> 2. Actively work on making tripleo-ci consume the ansible work in<br>
> tripleo-quickstart and the external role ecosystem around it.<br>
><br>
> Pros:<br>
> - This could be done incrementally, replacing a single function from<br>
> tripleo.sh with an invocation of tripleo-quickstart that performs that<br>
> function instead.<br>
> - We would be able to pull in a lot of extra functionality via these<br>
> external roles for free(ish).<br>
><br>
> Cons:<br>
> - Similarly unknown amount of work to completely switch.<br>
> - CI development would be done in multiple repos, though each would have<br>
> discrete and well defined functionality.<br>
><br>
><br>
> Personally, I don't think we should do anything drastic with CI until<br>
> after we release Newton, so we don't add any risk of impacting new<br>
> features that haven't landed yet. I do think it would be a good goal for<br>
> Ocata to have a CI system in TripleO that is consumable outside of<br>
> TripleO. In any case, this email is simply to garner feedback if other's<br>
> think this is a worthy thing to pursue and opinions on how we can get<br>
> there.<br>
><br>
><br>
> [1]<br>
><br>
> <a href="https://github.com/redhat-openstack?utf8=%E2%9C%93&query=ansible-role-tripleo" rel="noreferrer" target="_blank">https://github.com/redhat-openstack?utf8=%E2%9C%93&query=ansible-role-tripleo</a><br>
> (note not all of these are actively used/developed)<br>
> [2] <a href="https://github.com/rdo-infra/weirdo" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo</a><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/a4ce9600/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/a4ce9600/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 13 Jul 2016 13:04:59 +0000<br>
From: "Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [kolla] New specs process - a dicussion<br>
Message-ID: <<a href="mailto:D3ABB3B7.24F67%25stdake@cisco.com">D3ABB3B7.24F67%stdake@cisco.com</a>><br>
Content-Type: text/plain; charset="iso-8859-2"<br>
<br>
Josh,<br>
<br>
We did have the discussion at summit. We aren't even going to have a "big<br>
spec". We are going to run as bare minimal of a spec as possible. The<br>
reason I brought up spec additions is because Kolla has become so large,<br>
managing the project using current techniques is not optimal. I don't<br>
like process but in the future, the PTL will need an easy on-ramp to<br>
managing Kolla output.<br>
<br>
I agree with all of the risks you point out related to usage of specs. I<br>
am hopeful we can make this is a super lightweight process without the<br>
nitpicking that occurs in other projects. That said, the rollcall vote<br>
specs I expect to be as painful as they currently are (by design).<br>
<br>
Regards<br>
-steve<br>
<br>
<br>
On 7/12/16, 4:03 PM, "Joshua Harlow" <<a href="mailto:harlowja@fastmail.com">harlowja@fastmail.com</a>> wrote:<br>
<br>
>Something for consideration to make the specs process not to painful and<br>
>one that I think (?) glance pioneered is to have a 'bigger spec' and a<br>
>'smaller spec' template.<br>
><br>
><a href="https://github.com/openstack/glance-specs/blob/master/specs/lite-specs.rst" rel="noreferrer" target="_blank">https://github.com/openstack/glance-specs/blob/master/specs/lite-specs.rst</a><br>
><br>
>(smaller)<br>
><br>
><a href="https://github.com/openstack/glance-specs/blob/master/specs/template.rst" rel="noreferrer" target="_blank">https://github.com/openstack/glance-specs/blob/master/specs/template.rst</a><br>
>(bigger)<br>
><br>
>Just my 2 cents, don't bog down people to much with just big specs and<br>
>nit picking and trying to develop the whole feature in the spec (cause<br>
>that will off-put new people and senior people and ...).<br>
><br>
>-Josh<br>
><br>
>Micha? Jastrz?bski wrote:<br>
>> Hey guys,<br>
>><br>
>> Since our project matured, we decided that we should have a discussion<br>
>> regarding our spec process.<br>
>><br>
>> <a href="https://etherpad.openstack.org/p/kolla-N-midcycle-specs" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/kolla-N-midcycle-specs</a><br>
>><br>
>> Currently we do specs for most critical things, and they require<br>
>>majority vote.<br>
>><br>
>> We want to introduce another way, to enable non-nuclear specs.<br>
>> To summarize our discussion so far:<br>
>><br>
>> 1. Specs will require only 2 * +2 by default<br>
>> 2. Specs sit at minimum 2 weeks in gerrit before first +2 arrives, so<br>
>> other people will have time to look at it<br>
>> 3. Any core can require a rollcall vote - then it becomes rollcall vote<br>
>> 4. If nobody calls for rollcall vote, after 2 weeks spec can be merged<br>
>> with normal 2 * +2<br>
>><br>
>> Thoughts?<br>
>> Michal<br>
>><br>
>><br>
>>_________________________________________________________________________<br>
>>_<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
>__________________________________________________________________________<br>
>OpenStack Development Mailing List (not for usage questions)<br>
>Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 13 Jul 2016 09:06:37 -0400<br>
From: Wesley Hayutin <<a href="mailto:whayutin@redhat.com">whayutin@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [TripleO] Making TripleO CI easier to<br>
consume outside of TripleO CI<br>
Message-ID:<br>
<<a href="mailto:CAOHJT4Kf_siw7SBw2GhyOzi9qAtDZm3Hf893CjaKYuNRJ2hENg@mail.gmail.com">CAOHJT4Kf_siw7SBw2GhyOzi9qAtDZm3Hf893CjaKYuNRJ2hENg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Wed, Jul 13, 2016 at 8:54 AM, Michal Pryc <<a href="mailto:mpryc@redhat.com">mpryc@redhat.com</a>> wrote:<br>
<br>
> John,<br>
><br>
> On Tue, Jul 12, 2016 at 9:39 PM, John Trowbridge <<a href="mailto:trown@redhat.com">trown@redhat.com</a>> wrote:<br>
><br>
>> Howdy folks,<br>
>><br>
>> In the TripleO meeting two weeks ago, it came up that tripleo-quickstart<br>
>> is being used as a CI tool in RDO. This came about organically, because<br>
>> we needed to use RDO CI to self-gate quickstart (it relies on having a<br>
>> baremetal virthost). It displaced another ansible based CI tool there<br>
>> (khaleesi) and most(all?) of the extra functionality from that tool<br>
>> (upgrades, scale, baremetal, etc.) has been moved into discrete ansible<br>
>> roles that are able to plugin to quickstart.[1]<br>
>><br>
>><br>
> Here is small sum of frameworks/tools to give you an idea what we are<br>
> currently using to test RHOS components.<br>
><br>
> To create Triple-O undercloud/overcloud we are using the:<br>
><br>
> <a href="https://github.com/redhat-openstack/ansible-ovb" rel="noreferrer" target="_blank">https://github.com/redhat-openstack/ansible-ovb</a><br>
><br>
> And then to install RHOSP on existing Triple-O:<br>
><br>
> <a href="https://github.com/redhat-openstack/ansible-rhosp" rel="noreferrer" target="_blank">https://github.com/redhat-openstack/ansible-rhosp</a><br>
><br>
> Then to run CI in such environment we use octario which is our main tool<br>
> to run different flavors of tests and it's separate CI tool to be ready<br>
> with different provisioning frameworks.<br>
><br>
> <a href="https://github.com/redhat-openstack/octario/" rel="noreferrer" target="_blank">https://github.com/redhat-openstack/octario/</a><br>
><br>
><br>
> In the simplistic environment to run simple tests we are using InfraRed to<br>
> provision simple instance (without Triple-O):<br>
><br>
> <a href="https://github.com/rhosqeauto/InfraRed" rel="noreferrer" target="_blank">https://github.com/rhosqeauto/InfraRed</a><br>
><br>
> And then we run octario in such environment to run actual tests.<br>
><br>
> Ideally if the provisioning parts were common and we could reuse them.<br>
> Currently we need to use yet another set of tools to be able to patch rpm's<br>
> prior to running tests.<br>
><br>
<br>
+1, agree<br>
I think this part has been addressed w/<br>
<a href="https://blueprints.launchpad.net/tripleo/+spec/tripleo-quickstart" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/tripleo/+spec/tripleo-quickstart</a><br>
<br>
<br>
><br>
> There was an idea planted by dsariel to move some of the playbooks into<br>
> ansible-galaxy roles (possibly other teams had such idea as well), which I<br>
> can see it's another +1 for going with tools currently developed by Wes as<br>
> they are pretty separate and could be converted into ansible-galaxy, to be<br>
> available across different use-cases, but then it would need to be well<br>
> defined so the roles are not multiplied and we won't end up having similar<br>
> roles.<br>
><br>
><br>
We also considered ansible-galaxy and any of the ansible roles found in<br>
github/redhat-openstack/ansible-role could be moved into galaxy. Galaxy<br>
did not end up meeting our requirements for installing the roles and we<br>
ended up using python setuptools. Some roles have specific config and<br>
playbooks that need to be copied to a standard location and galaxy just did<br>
not do that very well.<br>
<br>
<br>
><br>
> best<br>
> Michal Pryc<br>
><br>
><br>
><br>
>> We are still left with two different tool sets, where one should suffice<br>
>> (and focus CI efforts in one place).<br>
>><br>
>> I see two different ways to resolve this.<br>
>><br>
>> 1. Actively work on making the tripleo-ci scripts consumable external to<br>
>> tripleo-ci. We have a project in RDO (WeiRDO)[2] that is consuming<br>
>> upstream CI for packstack and puppet, so it is not totally far-fetched<br>
>> to add support for TripleO jobs.<br>
>><br>
>> Pros:<br>
>> - All CI development just happens directly in tripleo-ci and RDO just<br>
>> inherits that work.<br>
>><br>
>> Cons:<br>
>> - This is totally untried, and therefore a totally unknown amount of work.<br>
>> - It is all or nothing in that there is no incremental path to get the<br>
>> CI scripts working outside of CI.<br>
>> - We have to rewrite a bunch of working ansible code in bash which IMO<br>
>> is the wrong direction for a modern CI system.<br>
>><br>
>><br>
>> 2. Actively work on making tripleo-ci consume the ansible work in<br>
>> tripleo-quickstart and the external role ecosystem around it.<br>
>><br>
>> Pros:<br>
>> - This could be done incrementally, replacing a single function from<br>
>> tripleo.sh with an invocation of tripleo-quickstart that performs that<br>
>> function instead.<br>
>> - We would be able to pull in a lot of extra functionality via these<br>
>> external roles for free(ish).<br>
>><br>
>> Cons:<br>
>> - Similarly unknown amount of work to completely switch.<br>
>> - CI development would be done in multiple repos, though each would have<br>
>> discrete and well defined functionality.<br>
>><br>
>><br>
>> Personally, I don't think we should do anything drastic with CI until<br>
>> after we release Newton, so we don't add any risk of impacting new<br>
>> features that haven't landed yet. I do think it would be a good goal for<br>
>> Ocata to have a CI system in TripleO that is consumable outside of<br>
>> TripleO. In any case, this email is simply to garner feedback if other's<br>
>> think this is a worthy thing to pursue and opinions on how we can get<br>
>> there.<br>
>><br>
>><br>
>> [1]<br>
>><br>
>> <a href="https://github.com/redhat-openstack?utf8=%E2%9C%93&query=ansible-role-tripleo" rel="noreferrer" target="_blank">https://github.com/redhat-openstack?utf8=%E2%9C%93&query=ansible-role-tripleo</a><br>
>> (note not all of these are actively used/developed)<br>
>> [2] <a href="https://github.com/rdo-infra/weirdo" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo</a><br>
>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/9f6be61a/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/9f6be61a/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 13 Jul 2016 09:32:31 -0400<br>
From: Brian Haley <<a href="mailto:brian.haley@hpe.com">brian.haley@hpe.com</a>><br>
To: OpenStack Development Mailing List<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: [openstack-dev] [Neutron][DVR] - No IRC Meeting today<br>
Message-ID: <<a href="mailto:578642EF.8050003@hpe.com">578642EF.8050003@hpe.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Hi Folks,<br>
<br>
Sorry for the late notice, but we will not have a DVR sub-team meeting today<br>
since neither Swami nor myself will be there to chair it.<br>
<br>
We will resume our meetings next week on July 20th.<br>
<br>
If you have any questions please ping us on IRC or send an email to the list.<br>
<br>
<a href="https://wiki.openstack.org/wiki/Meetings/Neutron-DVR" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Meetings/Neutron-DVR</a><br>
<br>
Thanks,<br>
<br>
-Brian<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 13 Jul 2016 08:35:27 -0500<br>
From: <a href="mailto:eran@itsonlyme.name">eran@itsonlyme.name</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [storlets] IRC meeting times<br>
Message-ID:<br>
<<a href="mailto:20160713083527.Horde.JjqJt86jqdhpfV7V6XE-oyL@e15.ehosts.com">20160713083527.Horde.JjqJt86jqdhpfV7V6XE-oyL@e15.ehosts.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes<br>
<br>
Hi,<br>
I would like to change the IRC meeting times to Tuesdays at 07:00AM UTC<br>
That's:<br>
16:00 JST<br>
10:00 IST<br>
<br>
Any objections?<br>
Thanks!<br>
Eran<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Wed, 13 Jul 2016 16:54:50 +0300<br>
From: Ivan Kolodyazhny <<a href="mailto:e0ne@e0ne.info">e0ne@e0ne.info</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [cinder] [nova] os-brick privsep failures<br>
and an upgrade strategy?<br>
Message-ID:<br>
<CAGocpaHJ61e-5Lcijip=<a href="mailto:SVwZZ8U9m%2BT6R-9b2jACV2P41UMrog@mail.gmail.com">SVwZZ8U9m+T6R-9b2jACV2P41UMrog@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks for the update, Matt.<br>
<br>
I will join our meeting next week.<br>
<br>
Regards,<br>
Ivan Kolodyazhny,<br>
<a href="http://blog.e0ne.info/" rel="noreferrer" target="_blank">http://blog.e0ne.info/</a><br>
<br>
On Tue, Jul 12, 2016 at 4:25 PM, Matt Riedemann <<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>><br>
wrote:<br>
<br>
> On 7/12/2016 6:29 AM, Ivan Kolodyazhny wrote:<br>
><br>
>> Hi team,<br>
>><br>
>> Do we have any decision on this issue? I've found few patches but both<br>
>> of them are -1'ed.<br>
>><br>
>> From Cinder perspective, it blocks us to release new os-brick with<br>
>> features, which are needed for other projects like Cinder and<br>
>> python-brick-cinderclient-ext.<br>
>><br>
>> Regards,<br>
>> Ivan Kolodyazhny,<br>
>> <a href="http://blog.e0ne.info/" rel="noreferrer" target="_blank">http://blog.e0ne.info/</a><br>
>><br>
>> On Wed, Jun 22, 2016 at 5:47 PM, Matt Riedemann<br>
>> <<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a> <mailto:<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>>> wrote:<br>
>><br>
>> On 6/21/2016 10:12 PM, Angus Lees wrote:<br>
>><br>
>> On Wed, 22 Jun 2016 at 05:59 Matt Riedemann<br>
>> <<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a> <mailto:<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>><br>
>> <mailto:<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a><br>
>><br>
>> <mailto:<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>>>> wrote:<br>
>><br>
>> Angus, what should we be looking at from the privsep side<br>
>> for debugging<br>
>> this?<br>
>><br>
>><br>
>> The line above the screen-n-cpu.txt.gz failure you linked to is:<br>
>> 2016-06-21 16:21:30.994<br>
>> <<br>
>> <a href="http://logs.openstack.org/85/331885/2/check/gate-grenade-dsvm-multinode/415e1bc/logs/new/screen-n-cpu.txt.gz?level=TRACE#_2016-06-21_16_21_30_994" rel="noreferrer" target="_blank">http://logs.openstack.org/85/331885/2/check/gate-grenade-dsvm-multinode/415e1bc/logs/new/screen-n-cpu.txt.gz?level=TRACE#_2016-06-21_16_21_30_994</a><br>
>> >1840<br>
>> WARNING oslo.privsep.daemon [-] privsep log:<br>
>> /usr/local/bin/nova-rootwrap: Unauthorized command: privsep-helper<br>
>> --config-file /etc/nova/nova.conf --privsep_context<br>
>> os_brick.privileged.default --privsep_sock_path<br>
>> /tmp/tmpV5w2VC/privsep.sock (no filter matched)<br>
>><br>
>> .. so nova-rootwrap is rejecting the privsep-helper command line<br>
>> because no filter matched. This indicates the nova<br>
>> compute.filters file<br>
>> has not been updated, or is incorrect.<br>
>><br>
>><br>
>> As was later pointed out by mtreinish, grenade is attempting to<br>
>> run the<br>
>> newton code against mitaka configs, and this includes using mitaka<br>
>> rootwrap filters. Unfortunately, the change to add privsep to<br>
>> nova's<br>
>> rootwrap filters wasn't approved until the newton cycle (so that<br>
>> all the<br>
>> os-brick privsep-related changes could be approved together), and<br>
>> so<br>
>> this doesn't Just Work.<br>
>><br>
>> Digging in further, it appears that there *is* a mechanism in<br>
>> grenade to<br>
>> upgrade rootwrap filters between major releases, but this needs<br>
>> to be<br>
>> explicitly updated for each project+release and hasn't been for<br>
>> nova+mitaka->newton. I'm not sure how this is *meant* to work,<br>
>> since<br>
>> the grenade "theory of upgrade" doesn't mention when configs<br>
>> should be<br>
>> updated - the only mechanism provided is an "exception ... used<br>
>> sparingly."<br>
>><br>
>><br>
>> As noted in the review, my understanding of the config changes is<br>
>> deprecation of options across release boundaries so that you can't<br>
>> drop a config option that would break someone from release to<br>
>> release without it being deprecated first. So deprecate option foo<br>
>> in mitaka, people upgrading from liberty to mitaka aren't broken,<br>
>> but they get warnings in mitaka so that when you drop the option in<br>
>> newton it's not a surprise and consumers should have adjusted during<br>
>> mitaka.<br>
>><br>
>> For rootwrap filters I agree this is more complicated.<br>
>><br>
>><br>
>> Anyway, I added an upgrade step for nova mitaka->newton that<br>
>> updates<br>
>> rootwrap filters appropriately(*). Again, I'm not sure what this<br>
>> communicates to deployers compared to cinder (which *did* have the<br>
>> updated rootwrap filter merged in mitaka, but of course that<br>
>> update<br>
>> still needs to be installed at some point).<br>
>> (*) <a href="https://review.openstack.org/#/c/332610" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/332610</a><br>
>><br>
>> - Gus<br>
>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
>> Alternatively Walter had a potential workaround to fallback to<br>
>> rootwrap for os-brick:<br>
>><br>
>> <a href="https://review.openstack.org/#/c/329586/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/329586/</a><br>
>><br>
>> So we could maybe use that for newton. But os-vif doesn't have<br>
>> anything like that, so we'd have to see what kind of (immediately<br>
>> deprecated) workaround could happen for os-vif in newton and then<br>
>> drop that in ocata.<br>
>><br>
>> I'm told danpb is out until tomorrow though so we'll probably need<br>
>> to wait to talk to him about options there.<br>
>><br>
>><br>
>> --<br>
>><br>
>> Thanks,<br>
>><br>
>> Matt Riedemann<br>
>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> ><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
> We probably aren't doing anything while Sean Dague is on vacation. He's<br>
> back next week and we have the nova/cinder meetups, so I'm planning on<br>
> talking about the grenade issue in person and hopefully we'll have a plan<br>
> by the end of next week to move forward.<br>
><br>
><br>
> --<br>
><br>
> Thanks,<br>
><br>
> Matt Riedemann<br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/bdab20d1/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/bdab20d1/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 9<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] debtcollector 1.6.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21348.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21348.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are pumped to announce the release of:<br>
<br>
debtcollector 1.6.0: A collection of Python deprecation patterns and<br>
strategies that help you collect your technical debt in a non-<br>
destructive manner.<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/debtcollector" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/debtcollector</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/debtcollector" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/debtcollector</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/debtcollector" rel="noreferrer" target="_blank">http://bugs.launchpad.net/debtcollector</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in debtcollector 1.5.0..1.6.0<br>
-------------------------------------<br>
<br>
d46b64a Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
test-requirements.txt | 2 +-<br>
1 file changed, 1 insertion(+), 1 deletion(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index d1f9b5d..16f75c6 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -10 +10 @@ python-subunit>=0.0.18 # Apache-2.0/BSD<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 10<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] mox3 0.17.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21349.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21349.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are tickled pink to announce the release of:<br>
<br>
mox3 0.17.0: Mock object framework for Python<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/mox3" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/mox3</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/mox3" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/mox3</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/python-mox3" rel="noreferrer" target="_blank">http://bugs.launchpad.net/python-mox3</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in mox3 0.16.0..0.17.0<br>
------------------------------<br>
<br>
2b58961 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
test-requirements.txt | 2 +-<br>
1 file changed, 1 insertion(+), 1 deletion(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index ad30fa2..df05b72 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -20 +20 @@ six>=1.9.0 # MIT<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 11<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] futurist 0.15.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21350.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21350.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are eager to announce the release of:<br>
<br>
futurist 0.15.0: Useful additions to futures, from the future.<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/futurist" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/futurist</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/futurist" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/futurist</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/futurist" rel="noreferrer" target="_blank">http://bugs.launchpad.net/futurist</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in futurist 0.14.0..0.15.0<br>
----------------------------------<br>
<br>
4ca63cb Don't include openstack/common in flake8 exclude list<br>
c7c67ca Updated from global requirements<br>
dc08625 Begin adding our own thread pool executor<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
futurist/_futures.py | 80 ++++++++++++++-------------<br>
futurist/_thread.py | 146 ++++++++++++++++++++++++++++++++++++++++++++++++++<br>
futurist/_utils.py | 2 +<br>
test-requirements.txt | 2 +-<br>
tox.ini | 2 +-<br>
5 files changed, 193 insertions(+), 39 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 6e6d300..68ed7a0 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -14 +14 @@ python-subunit>=0.0.18 # Apache-2.0/BSD<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 12<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.cache 1.11.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21351.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21351.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are psyched to announce the release of:<br>
<br>
oslo.cache 1.11.0: Cache storage for Openstack projects.<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.cache" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.cache</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.cache" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.cache</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.cache" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.cache</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.cache 1.10.0..1.11.0<br>
------------------------------------<br>
<br>
86bcd66 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
requirements.txt | 2 +-<br>
test-requirements.txt | 4 ++--<br>
2 files changed, 3 insertions(+), 3 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 28e46dd..b1defe2 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -10 +10 @@ oslo.log>=1.14.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.14.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 42f2881..0510e84 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -8,2 +8,2 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
-reno>=1.6.2 # Apache2<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
+reno>=1.8.0 # Apache2<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 13<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] automaton 1.3.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21352.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21352.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are satisfied to announce the release of:<br>
<br>
automaton 1.3.0: Friendly state machines for python.<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/automaton" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/automaton</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/automaton" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/automaton</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/automaton" rel="noreferrer" target="_blank">http://bugs.launchpad.net/automaton</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in automaton 1.2.0..1.3.0<br>
---------------------------------<br>
<br>
4008814 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
test-requirements.txt | 2 +-<br>
1 file changed, 1 insertion(+), 1 deletion(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 0036b56..2c695bc 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -11 +11 @@ python-subunit>=0.0.18 # Apache-2.0/BSD<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 14<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.config 3.13.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21353.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21353.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are thrilled to announce the release of:<br>
<br>
oslo.config 3.13.0: Oslo Configuration API<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.config" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.config</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.config" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.config</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.config" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.config</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.config 3.12.0..3.13.0<br>
-------------------------------------<br>
<br>
335b184 Add Python 3.5 classifier and venv<br>
d174a4e Enabling your project for mutable-config<br>
7539018 Add namespace to _list_opts() in test<br>
a08ec74 decode subprocess output so doc build works on python3<br>
7111070 Updated from global requirements<br>
4f97c6f Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
setup.cfg | 1 +<br>
test-requirements.txt | 4 +-<br>
tox.ini | 2 +-<br>
7 files changed, 128 insertions(+), 5 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 4789fb0..d444b33 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -21 +21 @@ coverage>=3.6 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
@@ -23 +23 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-reno>=1.6.2 # Apache2<br>
+reno>=1.8.0 # Apache2<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 15<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.context 2.6.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21354.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21354.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are chuffed to announce the release of:<br>
<br>
oslo.context 2.6.0: Oslo Context library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.context" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.context</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.context" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.context</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.context" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.context</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.context 2.5.0..2.6.0<br>
------------------------------------<br>
<br>
740b817 Handle openstack.request_id in from_environ<br>
d3af1d0 Add is_admin_project to context<br>
4db9262 Updated from global requirements<br>
f0de0c6 Add oslo.context name attributes matching ids<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
oslo_context/context.py | 45 +++++++-<br>
test-requirements.txt | 4 +-<br>
3 files changed, 174 insertions(+), 92 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 1db9871..79fca04 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -11,2 +11,2 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
-reno>=1.6.2 # Apache2<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
+reno>=1.8.0 # Apache2<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 16<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.concurrency 3.12.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21355.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21355.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are chuffed to announce the release of:<br>
<br>
oslo.concurrency 3.12.0: Oslo Concurrency library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.concurrency" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.concurrency</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.concurrency" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.concurrency</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.concurrency" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.concurrency</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.concurrency 3.11.0..3.12.0<br>
------------------------------------------<br>
<br>
f7821d9 Updated from global requirements<br>
68df6b2 Imported Translations from Zanata<br>
f13a21c Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
.../locale/en_GB/LC_MESSAGES/releasenotes.po | 30 ++++++++++++++++++++++<br>
requirements.txt | 4 +--<br>
test-requirements.txt | 4 +--<br>
3 files changed, 34 insertions(+), 4 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 51b3c76..864afc1 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -8 +8 @@ iso8601>=0.1.11 # MIT<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
@@ -10 +10 @@ oslo.i18n>=2.1.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 8418f39..e431107 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -13,2 +13,2 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
-reno>=1.6.2 # Apache2<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
+reno>=1.8.0 # Apache2<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 17<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.i18n 3.8.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21356.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21356.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are overjoyed to announce the release of:<br>
<br>
oslo.i18n 3.8.0: Oslo i18n library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.i18n" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.i18n</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.i18n" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.i18n</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.i18n" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.i18n</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.i18n 3.7.0..3.8.0<br>
---------------------------------<br>
<br>
16f40a6 Updated from global requirements<br>
6bc0cfc Don't include openstack/common in flake8 exclude list<br>
82e8a63 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
test-requirements.txt | 4 ++--<br>
tox.ini | 2 +-<br>
2 files changed, 3 insertions(+), 3 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 758c7d5..80bdbbb 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -7 +7 @@ hacking<0.11,>=0.10.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
@@ -15 +15 @@ coverage>=3.6 # Apache-2.0<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 18<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.middleware 3.15.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21357.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21357.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are thrilled to announce the release of:<br>
<br>
oslo.middleware 3.15.0: Oslo Middleware library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.middleware" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.middleware</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.middleware" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.middleware</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.middleware" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.middleware</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.middleware 3.14.0..3.15.0<br>
-----------------------------------------<br>
<br>
6ca6c88 Updated from global requirements<br>
45e90c6 Updated from global requirements<br>
b07c27d Updated from global requirements<br>
7e519d0 Deprecate using String as valid value for allowed_origin.<br>
399e940 Deprecate multiple config block parsing.<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
oslo_middleware/cors.py | 10 +++++++++-<br>
requirements.txt | 4 ++--<br>
test-requirements.txt | 2 +-<br>
4 files changed, 13 insertions(+), 29 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 01c7f22..b80e5c6 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -7 +7 @@ Jinja2>=2.8 # BSD License (3 clause)<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
@@ -10 +10 @@ oslo.i18n>=2.1.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index d913843..5f53419 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -10 +10 @@ oslotest>=1.10.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 19<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.log 3.12.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21358.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21358.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are thrilled to announce the release of:<br>
<br>
oslo.log 3.12.0: oslo.log library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.log" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.log</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.log" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.log</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.log" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.log</a><br>
<br>
For more details, please see below.<br>
<br>
3.12.0<br>
^^^^^^<br>
<br>
New Features<br>
<br>
* The log_config_append configuration option is now mutable and the<br>
logging settings it controls are reconfigured when the configuration<br>
file is reread. This can be used to, for example, change logger or<br>
handler levels.<br>
<br>
Changes in oslo.log 3.11.0..3.12.0<br>
----------------------------------<br>
<br>
c426a42 Replace "LOG.exception(_" with "LOG.exception(_LE"<br>
5082d92 Updated from global requirements<br>
8fde280 Reload log_config_append config on SIGHUP<br>
e4c651b Imported Translations from Zanata<br>
e3bd7e6 Updated from global requirements<br>
fc490c0 log: Introduce _iter_loggers<br>
15ef585 Imported Translations from Zanata<br>
1bea3a5 Updated from global requirements<br>
68bde95 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
oslo_log/_options.py | 1 +<br>
oslo_log/locale/de/LC_MESSAGES/oslo_log.po | 60 +++++<br>
oslo_log/locale/en_GB/LC_MESSAGES/oslo_log.po | 55 ++++<br>
oslo_log/locale/oslo_log.pot | 63 -----<br>
oslo_log/log.py | 38 ++-<br>
.../notes/reload_log_config-743817192b1172b6.yaml | 5 +<br>
.../locale/en_GB/LC_MESSAGES/releasenotes.po | 63 +++++<br>
requirements.txt | 4 +-<br>
test-requirements.txt | 4 +-<br>
11 files changed, 488 insertions(+), 105 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 26c3390..9bac65f 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -7 +7 @@ six>=1.9.0 # MIT<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
@@ -10 +10 @@ oslo.i18n>=2.1.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index c2d83c8..4c9bc0c 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -21 +21 @@ coverage>=3.6 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
@@ -23 +23 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-reno>=1.6.2 # Apache2<br>
+reno>=1.8.0 # Apache2<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 20<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.db 4.8.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21359.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21359.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are satisfied to announce the release of:<br>
<br>
oslo.db 4.8.0: Oslo Database library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.db" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.db</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.db" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.db</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.db" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.db</a><br>
<br>
For more details, please see below.<br>
<br>
4.8.0<br>
^^^^^<br>
<br>
<br>
New Features<br>
************<br>
<br>
* enginefacade decorators can now be used for class and instance<br>
methods, which implicitly receive the first positional argument.<br>
Previously, it was required that all decorated functions receive a<br>
context value as the first argument.<br>
<br>
<br>
Deprecation Notes<br>
*****************<br>
<br>
* The configuration option "sqlite_db" is now deprecated and will be<br>
removed in the future. Please use configuration option "connection"<br>
or "slave_connection" to connect to the database.<br>
<br>
Changes in oslo.db 4.6.0..4.8.0<br>
-------------------------------<br>
<br>
fc3c23a Updated from global requirements<br>
462296b Add support for LONGTEXT, MEDIUMTEXT to JsonEncodedType<br>
0a1bae9 Deprecate config option sqlite_db for removal<br>
16886e5 Catch empty value DBDuplicate errors<br>
1d7e7e4 Updated from global requirements<br>
8e3b356 api: use sane default in wrap_db_retry()<br>
21491e1 Imported Translations from Zanata<br>
e59c2b5 exc_filters: catch and translate non existent table on drop<br>
e0db469 exception: make message mandatory in DbMigrationError and deprecates it<br>
8a5fbb7 Make it possible to use enginefacade decorators with class methods<br>
ef97c25 Updated from global requirements<br>
4c82261 tests: fix order of assertEqual in exc_filter<br>
c4f025d exc_filters: catch and translate non existent constraint on drop<br>
1579c7c Replace tempest-lib dependency with os-testr<br>
b8ffab6 Imported Translations from Zanata<br>
a2da070 Fix typos in comments and docstring<br>
c0005aa Updated from global requirements<br>
9b9170f Updated from global requirements<br>
a71fe96 Fix typo: 'olso' to 'oslo'<br>
34a3da3 Repair boolean CHECK constraint detection<br>
2938f28 api: do not log a traceback if error is not expected<br>
e351f44 Fix imports in doc<br>
044cf85 Allow testing of MySQL and PostgreSQL scenario locally<br>
4bbadac Add support for custom JSON serializer<br>
663092d api: always enable retry_on_request<br>
7574ab7 Remove oslo-incubator related stuff<br>
3ac4f3f Updated from global requirements<br>
268987f Updated from global requirements<br>
4afa0ce Remove direct dependency on babel<br>
976bcdf Imported Translations from Zanata<br>
3816739 Add debtcollector to requirements<br>
30f061d Fix unit tests failures, when psycopg2 is not installed<br>
f5a8fb3 Fix server_default comparison for BigInteger<br>
c9e0bcd Remove unused sqlite_fk in _init_connection_args call<br>
531ed45 Updated from global requirements<br>
59b845d Correct docstring<br>
46767e5 Updated from global requirements<br>
b283e7d Updated from global requirements<br>
419a42f Updated from global requirements<br>
af0b3d3 Updated from global requirements<br>
b45a20b Updated from global requirements<br>
08f4911 Raise DbMigrationError for invalid version<br>
b1de3f7 Add new filter for DBDataError exception<br>
4048c8f Fix spelling mistake<br>
f98cb90 Let enginefacade._TransactionContextManager look for context<br>
09c531b Remove sqlalchemy < 1.0.0 compatible layer<br>
045a6fb Update reno for stable/mitaka<br>
6c9cc58 Updated from global requirements<br>
e9cbc6e Add tests for float interval values in wrap_db_retry()<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
CONTRIBUTING.rst | 27 ++<br>
oslo_db/api.py | 34 +-<br>
oslo_db/exception.py | 41 +++<br>
.../locale/en_GB/LC_MESSAGES/oslo_db-log-error.po | 11 +-<br>
.../locale/en_GB/LC_MESSAGES/oslo_db-log-info.po | 8 +-<br>
.../en_GB/LC_MESSAGES/oslo_db-log-warning.po | 8 +-<br>
oslo_db/locale/en_GB/LC_MESSAGES/oslo_db.po | 17 +-<br>
oslo_db/locale/es/LC_MESSAGES/oslo_db-log-error.po | 11 +-<br>
oslo_db/locale/es/LC_MESSAGES/oslo_db-log-info.po | 8 +-<br>
.../locale/es/LC_MESSAGES/oslo_db-log-warning.po | 8 +-<br>
oslo_db/locale/es/LC_MESSAGES/oslo_db.po | 11 +-<br>
oslo_db/locale/fr/LC_MESSAGES/oslo_db-log-error.po | 11 +-<br>
oslo_db/locale/fr/LC_MESSAGES/oslo_db-log-info.po | 8 +-<br>
.../locale/fr/LC_MESSAGES/oslo_db-log-warning.po | 8 +-<br>
oslo_db/locale/fr/LC_MESSAGES/oslo_db.po | 11 +-<br>
oslo_db/locale/oslo_db-log-error.pot | 51 ---<br>
oslo_db/locale/oslo_db-log-info.pot | 29 --<br>
oslo_db/locale/oslo_db-log-warning.pot | 44 ---<br>
oslo_db/locale/oslo_db.pot | 83 -----<br>
oslo_db/options.py | 3 +<br>
oslo_db/sqlalchemy/compat/__init__.py | 25 --<br>
oslo_db/sqlalchemy/compat/handle_error.py | 341 ---------------------<br>
oslo_db/sqlalchemy/enginefacade.py | 16 +-<br>
oslo_db/sqlalchemy/engines.py | 11 +-<br>
oslo_db/sqlalchemy/exc_filters.py | 50 ++-<br>
oslo_db/sqlalchemy/migration.py | 25 +-<br>
oslo_db/sqlalchemy/migration_cli/manager.py | 4 +-<br>
oslo_db/sqlalchemy/provision.py | 3 +-<br>
oslo_db/sqlalchemy/test_migrations.py | 7 +-<br>
oslo_db/sqlalchemy/types.py | 13 +<br>
oslo_db/sqlalchemy/update_match.py | 2 +-<br>
oslo_db/sqlalchemy/utils.py | 31 +-<br>
...eprecate_config_sqlite_db-bd41d49343049319.yaml | 7 +<br>
.../enginefacade_decorators-4660862fe22d2669.yaml | 6 +<br>
releasenotes/source/conf.py | 10 +-<br>
releasenotes/source/index.rst | 1 +<br>
.../locale/en_GB/LC_MESSAGES/releasenotes.po | 89 ++++++<br>
releasenotes/source/mitaka.rst | 6 +<br>
requirements.txt | 12 +-<br>
setup.cfg | 14 +-<br>
tox.ini | 28 +-<br>
54 files changed, 789 insertions(+), 958 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 352db43..fbc015b 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -6,2 +6,2 @@ pbr>=1.6 # Apache-2.0<br>
-alembic>=0.8.0 # MIT<br>
-Babel>=1.3 # BSD<br>
+alembic>=0.8.4 # MIT<br>
+debtcollector>=1.2.0 # Apache-2.0<br>
@@ -9,3 +9,3 @@ oslo.i18n>=2.1.0 # Apache-2.0<br>
-oslo.config>=3.4.0 # Apache-2.0<br>
-oslo.context>=0.2.0 # Apache-2.0<br>
-oslo.utils>=3.5.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
+oslo.context>=2.4.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
@@ -14 +14 @@ sqlalchemy-migrate>=0.9.6 # Apache-2.0<br>
-stevedore>=1.5.0 # Apache-2.0<br>
+stevedore>=1.10.0 # Apache-2.0<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 21<br>
Date: Wed, 13 Jul 2016 16:11:26 +0200<br>
From: Markus Zoeller <<a href="mailto:mzoeller@linux.vnet.ibm.com">mzoeller@linux.vnet.ibm.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: Re: [openstack-dev] The future of OpenStack documentation<br>
Message-ID: <<a href="mailto:57864C0E.70602@linux.vnet.ibm.com">57864C0E.70602@linux.vnet.ibm.com</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
On 11.07.2016 00:02, Steve Martinelli wrote:<br>
> I personally like this solution, it seems much more scalable. This follows<br>
> the same pattern of the API docs (moving the content to project repos),<br>
> which puts the onus back on the project team to maintain and create<br>
> documentation. I'm also hoping this results in less duplication between the<br>
> guides and the keystone developer docs (the latter of which start to stray<br>
> from "developer" docs and begin to look like "user" docs.<br>
<br>
After reading this, the "configuration reference" comes to my mind.<br>
Having the api-ref and the config-ref at one place, near the code, seems<br>
logical to me. Nova put a lot of effort into providing valuable help<br>
text for the config options in the last months. We should also make sure<br>
that it will result in a good manual, which could be easier if it's<br>
in-tree, near the code.<br>
<br>
--<br>
Regards, Markus Zoeller (markus_z)<br>
<br>
> The folks that contribute to the keystone guides today would still be very<br>
> welcomed to continue to contribute once/if the switch is made.<br>
><br>
> On Fri, Jul 8, 2016 at 5:02 PM, Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>> wrote:<br>
><br>
>> Currently, OpenStack provides central documentation (primarily in the<br>
>> openstack-manuals repository) for operators and users. The single location<br>
>> and consistent structure eases audiences of various technical expertise<br>
>> into OpenStack, typically operators and users rather than developers.<br>
>> Although I'm not a fan of the word "product", increasingly less technical<br>
>> audiences are learning about OpenStack and tend to compare it with other<br>
>> cloud infrastructure products. Such audiences expect a coherent, relatively<br>
>> mature product to easily evaluate, usually via proof-of-concept. Upon<br>
>> deciding to implement OpenStack, the central documentation attempts to<br>
>> gracefully lead them toward a production deployment that meets or exceeds<br>
>> requirements and expectations.<br>
>><br>
>> However, since I began contributing to OpenStack documentation around the<br>
>> Havana release, I am seeing many projects, particularly core projects,<br>
>> trending toward more independence from other projects including central<br>
>> documentation. For operator and user documentation, a couple of projects<br>
>> contribute to the central documentation repository, some projects<br>
>> contribute to their own repositories, and an alarmingly large number of<br>
>> projects simply do not contribute such documentation and assume that all<br>
>> audiences involve developers. These differences lead to an increasingly<br>
>> negative overall experience for the audiences that OpenStack needs to<br>
>> increase adoption/growth and maintain the existing deployment base.<br>
>><br>
>> As a contributor to central documentation and one or more other projects<br>
>> including neutron, I see the problems from both sides and don't<br>
>> particularly blame either party for them. Some politics, some technical,<br>
>> some a lack of resources, and some just a general misunderstanding about<br>
>> documentation. However, I think we need to develop a solution that works<br>
>> for both parties and ultimately benefits our audiences.<br>
>><br>
>> One potential solution essentially involves moving operator and user<br>
>> documentation into project repositories (similar to developer<br>
>> documentation) and using infrastructure to coherently present it on<br>
>> <a href="http://docs.openstack.org" rel="noreferrer" target="_blank">docs.openstack.org</a> which achieves the following goals:<br>
>><br>
>> 1) Project developers can contribute documentation and code in the same<br>
>> patch, thus avoiding two different review queues and reviewers with<br>
>> different motivations and guidelines.<br>
>> 2) Project developers can either work directly or via liaison with one or<br>
>> more documentation team members to improve documentation components during<br>
>> development or after merging technically accurate content.<br>
>> 3) Rather than attempting to document all projects with little (if any)<br>
>> assistance from those projects, the primary role of the documentation team<br>
>> becomes managing overall organization/presentation of documentation and<br>
>> assisting projects with their contributions.<br>
>><br>
>> We're seeing decent adoption of moving API documentation into project<br>
>> repositories, so I want to initiate some discussion about moving additional<br>
>> documentation (or other options) prior to mid-cycles (including ops) and<br>
>> the next summit.<br>
>><br>
>> Matt<br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 22<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.reports 1.12.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21360.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21360.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are eager to announce the release of:<br>
<br>
oslo.reports 1.12.0: oslo.reports library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.reports" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.reports</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.reports" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.reports</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.reports" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.reports</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.reports 1.11.0..1.12.0<br>
--------------------------------------<br>
<br>
4b37e30 Updated from global requirements<br>
96fa66c Updated from global requirements<br>
30cfeab Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
requirements.txt | 2 +-<br>
test-requirements.txt | 4 ++--<br>
2 files changed, 3 insertions(+), 3 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 62f078c..67f73ae 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -11 +11 @@ oslo.i18n>=2.1.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index ff73ef3..a180841 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -10 +10 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
@@ -13 +13 @@ sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 23<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.privsep 1.10.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21361.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21361.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are content to announce the release of:<br>
<br>
oslo.privsep 1.10.0: OpenStack library for privilege separation<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.privsep" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.privsep</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.privsep" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.privsep</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.privsep" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.privsep</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.privsep 1.9.0..1.10.0<br>
-------------------------------------<br>
<br>
e46eebf Updated from global requirements<br>
b5e1c13 Updated from global requirements<br>
021c911 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
requirements.txt | 4 ++--<br>
test-requirements.txt | 2 +-<br>
2 files changed, 3 insertions(+), 3 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index e77185a..1397b11 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -7,2 +7,2 @@ oslo.i18n>=2.1.0 # Apache-2.0<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 634e4c1..b3deaba 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -12 +12 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 24<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.policy 1.12.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21362.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21362.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are jazzed to announce the release of:<br>
<br>
oslo.policy 1.12.0: Oslo Policy library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.policy" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.policy</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.policy" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.policy</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.policy" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.policy</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.policy 1.11.0..1.12.0<br>
-------------------------------------<br>
<br>
cbb0824 Updated from global requirements<br>
d0d39a4 Updated from global requirements<br>
202340c Fix mispelled method name in setup.cfg<br>
a7a51bc Updated from global requirements<br>
7e114b6 Updated from global requirements<br>
123c155 Imported Translations from Zanata<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po | 9 ++++++---<br>
requirements.txt | 4 ++--<br>
setup.cfg | 2 +-<br>
test-requirements.txt | 4 ++--<br>
4 files changed, 11 insertions(+), 8 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 7204ac2..09e1525 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -6 +6 @@ requests>=2.10.0 # Apache-2.0<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
@@ -9 +9 @@ oslo.serialization>=1.10.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index f4844ab..eb9c954 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -7 +7 @@ oslotest>=1.10.0 # Apache-2.0<br>
-requests-mock>=0.7.0 # Apache-2.0<br>
+requests-mock>=1.0 # Apache-2.0<br>
@@ -16 +16 @@ sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
-reno>=1.6.2 # Apache2<br>
+reno>=1.8.0 # Apache2<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 25<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.serialization 2.11.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21363.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21363.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are glad to announce the release of:<br>
<br>
oslo.serialization 2.11.0: Oslo Serialization library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.serialization" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.serialization</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.serialization" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.serialization</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.serialization" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.serialization</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.serialization 2.10.0..2.11.0<br>
--------------------------------------------<br>
<br>
7ad9a95 Updated from global requirements<br>
5ee90fc Updated from global requirements<br>
1ec85e9 Use {} instead of dict()<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
oslo_serialization/jsonutils.py | 4 ++--<br>
requirements.txt | 2 +-<br>
test-requirements.txt | 2 +-<br>
3 files changed, 4 insertions(+), 4 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 6872a60..54901dd 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -13 +13 @@ msgpack-python>=0.4.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 0a065c6..0a0d3bf 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -10 +10 @@ netaddr!=0.7.16,>=0.7.12 # BSD<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 26<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.versionedobjects 1.13.0<br>
release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21364.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21364.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are glad to announce the release of:<br>
<br>
oslo.versionedobjects 1.13.0: Oslo Versioned Objects library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.versionedobjects" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.versionedobjects</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.versionedobjects" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.versionedobjects</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.versionedobjects" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.versionedobjects</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.versionedobjects 1.12.0..1.13.0<br>
-----------------------------------------------<br>
<br>
b6410fe Updated from global requirements<br>
c6eaf00 Imported Translations from Zanata<br>
e80ab96 JSON schema get_schema implementation for common fields<br>
cf2838f Updated from global requirements<br>
92e7ac7 JSON schema generation for versioned objects<br>
cf28125 Extend test_hashes to allow extra info gathering<br>
f5fdfc2 Updated from global requirements<br>
238fd19 Improved error message for Object.coerce<br>
1500618 Imported Translations from Zanata<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
oslo_versionedobjects/base.py | 44 ++++++++++++++<br>
oslo_versionedobjects/fields.py | 42 +++++++++++++-<br>
oslo_versionedobjects/fixture.py | 4 +-<br>
.../LC_MESSAGES/oslo_versionedobjects-log-error.po | 18 ++++--<br>
.../LC_MESSAGES/oslo_versionedobjects-log-error.po | 18 ++++--<br>
requirements.txt | 4 +-<br>
test-requirements.txt | 2 +-<br>
10 files changed, 255 insertions(+), 15 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 52bdb85..7813946 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -6 +6 @@ oslo.concurrency>=3.8.0 # Apache-2.0<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
@@ -10 +10 @@ oslo.serialization>=1.10.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 64d87df..b30d301 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -9 +9 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 27<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.rootwrap 4.4.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21365.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21365.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are gleeful to announce the release of:<br>
<br>
oslo.rootwrap 4.4.0: Oslo Rootwrap<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.rootwrap" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.rootwrap</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.rootwrap" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.rootwrap</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.rootwrap" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.rootwrap</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.rootwrap 4.3.0..4.4.0<br>
-------------------------------------<br>
<br>
3a70d2e Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
test-requirements.txt | 2 +-<br>
1 file changed, 1 insertion(+), 1 deletion(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index e4b24c3..65bf3d1 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -15 +15 @@ testtools>=1.4.0 # MIT<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 28<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.service 1.13.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21366.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21366.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are eager to announce the release of:<br>
<br>
oslo.service 1.13.0: oslo.service library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.service" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.service</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.service" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.service</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.service" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.service</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.service 1.12.0..1.13.0<br>
--------------------------------------<br>
<br>
3f39b9b Updated from global requirements<br>
6421273 Updated from global requirements<br>
84b53e6 Updated from global requirements<br>
e7317d7 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
requirements.txt | 4 ++--<br>
test-requirements.txt | 2 +-<br>
2 files changed, 3 insertions(+), 3 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 87352e2..83d22d4 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -9 +9 @@ monotonic>=0.6 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
@@ -11 +11 @@ oslo.concurrency>=3.8.0 # Apache-2.0<br>
-oslo.config>=3.10.0 # Apache-2.0<br>
+oslo.config>=3.12.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index d0b8e20..de31b9a 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -12 +12 @@ oslosphinx!=3.4.0,>=2.5.0 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 29<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslotest 2.7.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21367.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21367.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are pleased to announce the release of:<br>
<br>
oslotest 2.7.0: Oslo test framework<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslotest" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslotest</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslotest" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslotest</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslotest" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslotest</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslotest 2.6.0..2.7.0<br>
--------------------------------<br>
<br>
a0eb134 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
test-requirements.txt | 2 +-<br>
1 file changed, 1 insertion(+), 1 deletion(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index bfdb9ba..cecb61e 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -13 +13 @@ coverage>=3.6 # Apache-2.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 30<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] taskflow 2.3.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21368.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21368.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are jazzed to announce the release of:<br>
<br>
taskflow 2.3.0: Taskflow structured state management library.<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/taskflow" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/taskflow</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/taskflow" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/taskflow</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/taskflow/" rel="noreferrer" target="_blank">http://bugs.launchpad.net/taskflow/</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in taskflow 2.2.0..2.3.0<br>
--------------------------------<br>
<br>
0b198de Updated from global requirements<br>
185830b remove unused LOG<br>
6ca905c Fixes: typo error in comments<br>
ec99a02 Updated from global requirements<br>
7422194 Fix some misspellings in the function name and descriptions<br>
21aa375 Updated from global requirements<br>
599b270 Add tests to verify kwargs behavior on revert validation<br>
6e21e31 Make tests less dependent on transient state<br>
0766397 Use the full 'get_execute_failures' vs the shortname<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
requirements.txt | 2 +-<br>
taskflow/engines/action_engine/actions/retry.py | 3 -<br>
taskflow/engines/action_engine/compiler.py | 8 +--<br>
taskflow/engines/action_engine/engine.py | 12 ++--<br>
taskflow/engines/action_engine/executor.py | 3 -<br>
taskflow/engines/action_engine/process_executor.py | 2 +-<br>
taskflow/engines/base.py | 2 +-<br>
taskflow/examples/99_bottles.py | 2 +-<br>
taskflow/jobs/backends/impl_zookeeper.py | 2 +-<br>
taskflow/jobs/base.py | 2 +-<br>
taskflow/patterns/graph_flow.py | 2 +-<br>
taskflow/persistence/backends/impl_memory.py | 2 +-<br>
taskflow/persistence/models.py | 3 -<br>
taskflow/storage.py | 2 +-<br>
taskflow/types/failure.py | 8 +--<br>
taskflow/types/notifier.py | 4 +-<br>
taskflow/types/tree.py | 2 +-<br>
test-requirements.txt | 2 +-<br>
22 files changed, 73 insertions(+), 65 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index af3db31..73819aa 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -44 +44 @@ automaton>=0.5.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index e57fda1..6606911 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -38 +38 @@ eventlet!=0.18.3,>=0.18.2 # MIT<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 31<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslosphinx 4.6.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21369.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21369.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are jubilant to announce the release of:<br>
<br>
oslosphinx 4.6.0: OpenStack Sphinx Extensions and Theme<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslosphinx" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslosphinx</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslosphinx" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslosphinx</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslosphinx" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslosphinx</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslosphinx 4.5.0..4.6.0<br>
----------------------------------<br>
<br>
e2ded8e Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
test-requirements.txt | 2 +-<br>
1 file changed, 1 insertion(+), 1 deletion(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index 506a68b..3ee4d7d 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -8 +8 @@ hacking<0.11,>=0.10.0<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 32<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] oslo.vmware 2.11.0 release<br>
(newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21370.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21370.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are delighted to announce the release of:<br>
<br>
oslo.vmware 2.11.0: Oslo VMware library<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/oslo.vmware" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/oslo.vmware</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/oslo.vmware" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/oslo.vmware</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/oslo.vmware" rel="noreferrer" target="_blank">http://bugs.launchpad.net/oslo.vmware</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in oslo.vmware 2.10.0..2.11.0<br>
-------------------------------------<br>
<br>
421b41c Updated from global requirements<br>
04ad3d8 Add a py35 tox venv for upcoming py35 support<br>
7b04a56 Updated from global requirements<br>
c202eff Remove unnecessary properties from image-meta<br>
029bc0a Updated from global requirements<br>
a4a74ab Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
oslo_vmware/image_transfer.py | 8 +++++---<br>
requirements.txt | 4 ++--<br>
setup.cfg | 1 +<br>
test-requirements.txt | 2 +-<br>
tox.ini | 2 +-<br>
6 files changed, 14 insertions(+), 10 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index c952316..4f4f3a6 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -12 +12 @@ oslo.i18n>=2.1.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.15.0 # Apache-2.0<br>
@@ -18 +18 @@ lxml>=2.3 # BSD<br>
-suds-jurko>=0.6 # LGPL<br>
+suds-jurko>=0.6 # LGPLv3+<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index a40ffab..b8c2e46 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -25 +25 @@ sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
-reno>=1.6.2 # Apache2<br>
+reno>=1.8.0 # Apache2<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 33<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] stevedore 1.16.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21371.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21371.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are overjoyed to announce the release of:<br>
<br>
stevedore 1.16.0: Manage dynamic plugins for Python applications<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/stevedore" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/stevedore</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/stevedore" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/stevedore</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="https://bugs.launchpad.net/python-stevedore" rel="noreferrer" target="_blank">https://bugs.launchpad.net/python-stevedore</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in stevedore 1.15.0..1.16.0<br>
-----------------------------------<br>
<br>
1218ab6 Fix NamedExtensionManager fails when loading failing extension in order<br>
da83cd8 Remove irrelated output item<br>
e3d08ce Fix broken link about setuptools entry points<br>
6f81f6f NamedExtensionManager: call a callback when some names cannot be found<br>
f33b810 Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
README.rst | 2 +-<br>
stevedore/named.py | 20 +++++++++++++++++++-<br>
test-requirements.txt | 2 +-<br>
6 files changed, 62 insertions(+), 4 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/test-requirements.txt b/test-requirements.txt<br>
index d59feb9..977194a 100644<br>
--- a/test-requirements.txt<br>
+++ b/test-requirements.txt<br>
@@ -6 +6 @@ Pillow>=2.4.0 # PIL License<br>
-sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
+sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 34<br>
From: <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] [new][oslo] tooz 1.41.0 release (newton)<br>
Message-ID:<br>
<<a href="mailto:mailman.21372.1468439277.7714.openstack-dev@lists.openstack.org">mailman.21372.1468439277.7714.openstack-dev@lists.openstack.org</a>><br>
<br>
We are jazzed to announce the release of:<br>
<br>
tooz 1.41.0: Coordination library for distributed systems.<br>
<br>
This release is part of the newton release series.<br>
<br>
With source available at:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/tooz" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/tooz</a><br>
<br>
With package available at:<br>
<br>
<a href="https://pypi.python.org/pypi/tooz" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/tooz</a><br>
<br>
Please report issues through launchpad:<br>
<br>
<a href="http://bugs.launchpad.net/python-tooz/" rel="noreferrer" target="_blank">http://bugs.launchpad.net/python-tooz/</a><br>
<br>
For more details, please see below.<br>
<br>
Changes in tooz 1.40.0..1.41.0<br>
------------------------------<br>
<br>
3541e7c File driver: properly handle Windows paths<br>
6716456 Updated from global requirements<br>
7ea400a Updated from global requirements<br>
<br>
<br>
Diffstat (except docs and test files)<br>
-------------------------------------<br>
<br>
requirements.txt | 2 +-<br>
setup.cfg | 46 +++++++++++++++----------------------<br>
tooz/drivers/file.py | 17 +++++++++++++-<br>
4 files changed, 85 insertions(+), 30 deletions(-)<br>
<br>
<br>
Requirements updates<br>
--------------------<br>
<br>
diff --git a/requirements.txt b/requirements.txt<br>
index 826db66..a9cecef 100644<br>
--- a/requirements.txt<br>
+++ b/requirements.txt<br>
@@ -14 +14 @@ futurist>=0.11.0 # Apache-2.0<br>
-oslo.utils>=3.11.0 # Apache-2.0<br>
+oslo.utils>=3.14.0 # Apache-2.0<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 35<br>
Date: Wed, 13 Jul 2016 10:55:11 -0400<br>
From: Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: [openstack-dev] [release][ptl][all] newton-2 milestone<br>
deadline 14 July<br>
Message-ID: <1468421604-sup-2300@lrrr.local><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
PTLs and release liaisons, please remember that 14 July is the<br>
deadline for proposing your second milestone tags for deliverables<br>
using the cycle-with-milestone release model during newton. Milestones<br>
are date-based, so if missing the deadline means missing the<br>
milestone.<br>
<br>
Doug<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 36<br>
Date: Wed, 13 Jul 2016 17:10:20 +0200<br>
From: Markus Zoeller <<a href="mailto:mzoeller@linux.vnet.ibm.com">mzoeller@linux.vnet.ibm.com</a>><br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: Re: [openstack-dev] [new][oslo] mox3 0.17.0 release (newton)<br>
Message-ID: <<a href="mailto:578659DC.9070902@linux.vnet.ibm.com">578659DC.9070902@linux.vnet.ibm.com</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
On 13.07.2016 16:01, <a href="mailto:no-reply@openstack.org">no-reply@openstack.org</a> wrote:<br>
> We are tickled pink to announce the release of:<br>
><br>
<br>
Whoever chooses the wording in these announcements, you're a genius!<br>
<br>
<br>
--<br>
Regards, Markus Zoeller (markus_z)<br>
<br>
> mox3 0.17.0: Mock object framework for Python<br>
><br>
> This release is part of the newton release series.<br>
><br>
> With source available at:<br>
><br>
> <a href="http://git.openstack.org/cgit/openstack/mox3" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/mox3</a><br>
><br>
> With package available at:<br>
><br>
> <a href="https://pypi.python.org/pypi/mox3" rel="noreferrer" target="_blank">https://pypi.python.org/pypi/mox3</a><br>
><br>
> Please report issues through launchpad:<br>
><br>
> <a href="http://bugs.launchpad.net/python-mox3" rel="noreferrer" target="_blank">http://bugs.launchpad.net/python-mox3</a><br>
><br>
> For more details, please see below.<br>
><br>
> Changes in mox3 0.16.0..0.17.0<br>
> ------------------------------<br>
><br>
> 2b58961 Updated from global requirements<br>
><br>
><br>
> Diffstat (except docs and test files)<br>
> -------------------------------------<br>
><br>
> test-requirements.txt | 2 +-<br>
> 1 file changed, 1 insertion(+), 1 deletion(-)<br>
><br>
><br>
> Requirements updates<br>
> --------------------<br>
><br>
> diff --git a/test-requirements.txt b/test-requirements.txt<br>
> index ad30fa2..df05b72 100644<br>
> --- a/test-requirements.txt<br>
> +++ b/test-requirements.txt<br>
> @@ -20 +20 @@ six>=1.9.0 # MIT<br>
> -sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD<br>
> +sphinx!=1.3b1,<1.3,>=1.2.1 # BSD<br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 37<br>
Date: Wed, 13 Jul 2016 09:52:45 -0600<br>
From: Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] The future of OpenStack documentation<br>
Message-ID:<br>
<CABA+jQqQ25_pVhar0vV5jZBrucYNppkhi6ktd+tC4kkug=<a href="mailto:W1EQ@mail.gmail.com">W1EQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
The configuration reference essentially uses a script to parse help strings<br>
from code in project repositories. Occasionally, the documentation team<br>
augments content beyond what the automation provides. However, these<br>
content augmentations, the script, and schedule for running the script<br>
belong to the documentation team. Moving control of these items to projects<br>
would likely yield a more robust configuration reference, particularly<br>
regarding nuances of each project.<br>
<br>
Speaking of help strings, I see a conflict between providing sufficient<br>
content and preventing bloat of example configuration files. At the last<br>
summit, I suggested implementing two types of help strings... one long and<br>
one short. The configuration reference pulls the long string and the<br>
configuration file generator pulls the short string. If this idea makes<br>
sense, moving the configuration reference to project repositories would<br>
potentially enable each project to implement such changes at its own pace.<br>
<br>
On Wed, Jul 13, 2016 at 8:11 AM, Markus Zoeller <<a href="mailto:mzoeller@linux.vnet.ibm.com">mzoeller@linux.vnet.ibm.com</a><br>
> wrote:<br>
<br>
> On 11.07.2016 00:02, Steve Martinelli wrote:<br>
> > I personally like this solution, it seems much more scalable. This<br>
> follows<br>
> > the same pattern of the API docs (moving the content to project repos),<br>
> > which puts the onus back on the project team to maintain and create<br>
> > documentation. I'm also hoping this results in less duplication between<br>
> the<br>
> > guides and the keystone developer docs (the latter of which start to<br>
> stray<br>
> > from "developer" docs and begin to look like "user" docs.<br>
><br>
> After reading this, the "configuration reference" comes to my mind.<br>
> Having the api-ref and the config-ref at one place, near the code, seems<br>
> logical to me. Nova put a lot of effort into providing valuable help<br>
> text for the config options in the last months. We should also make sure<br>
> that it will result in a good manual, which could be easier if it's<br>
> in-tree, near the code.<br>
><br>
> --<br>
> Regards, Markus Zoeller (markus_z)<br>
><br>
> > The folks that contribute to the keystone guides today would still be<br>
> very<br>
> > welcomed to continue to contribute once/if the switch is made.<br>
> ><br>
> > On Fri, Jul 8, 2016 at 5:02 PM, Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>><br>
> wrote:<br>
> ><br>
> >> Currently, OpenStack provides central documentation (primarily in the<br>
> >> openstack-manuals repository) for operators and users. The single<br>
> location<br>
> >> and consistent structure eases audiences of various technical expertise<br>
> >> into OpenStack, typically operators and users rather than developers.<br>
> >> Although I'm not a fan of the word "product", increasingly less<br>
> technical<br>
> >> audiences are learning about OpenStack and tend to compare it with other<br>
> >> cloud infrastructure products. Such audiences expect a coherent,<br>
> relatively<br>
> >> mature product to easily evaluate, usually via proof-of-concept. Upon<br>
> >> deciding to implement OpenStack, the central documentation attempts to<br>
> >> gracefully lead them toward a production deployment that meets or<br>
> exceeds<br>
> >> requirements and expectations.<br>
> >><br>
> >> However, since I began contributing to OpenStack documentation around<br>
> the<br>
> >> Havana release, I am seeing many projects, particularly core projects,<br>
> >> trending toward more independence from other projects including central<br>
> >> documentation. For operator and user documentation, a couple of projects<br>
> >> contribute to the central documentation repository, some projects<br>
> >> contribute to their own repositories, and an alarmingly large number of<br>
> >> projects simply do not contribute such documentation and assume that all<br>
> >> audiences involve developers. These differences lead to an increasingly<br>
> >> negative overall experience for the audiences that OpenStack needs to<br>
> >> increase adoption/growth and maintain the existing deployment base.<br>
> >><br>
> >> As a contributor to central documentation and one or more other projects<br>
> >> including neutron, I see the problems from both sides and don't<br>
> >> particularly blame either party for them. Some politics, some technical,<br>
> >> some a lack of resources, and some just a general misunderstanding about<br>
> >> documentation. However, I think we need to develop a solution that works<br>
> >> for both parties and ultimately benefits our audiences.<br>
> >><br>
> >> One potential solution essentially involves moving operator and user<br>
> >> documentation into project repositories (similar to developer<br>
> >> documentation) and using infrastructure to coherently present it on<br>
> >> <a href="http://docs.openstack.org" rel="noreferrer" target="_blank">docs.openstack.org</a> which achieves the following goals:<br>
> >><br>
> >> 1) Project developers can contribute documentation and code in the same<br>
> >> patch, thus avoiding two different review queues and reviewers with<br>
> >> different motivations and guidelines.<br>
> >> 2) Project developers can either work directly or via liaison with one<br>
> or<br>
> >> more documentation team members to improve documentation components<br>
> during<br>
> >> development or after merging technically accurate content.<br>
> >> 3) Rather than attempting to document all projects with little (if any)<br>
> >> assistance from those projects, the primary role of the documentation<br>
> team<br>
> >> becomes managing overall organization/presentation of documentation and<br>
> >> assisting projects with their contributions.<br>
> >><br>
> >> We're seeing decent adoption of moving API documentation into project<br>
> >> repositories, so I want to initiate some discussion about moving<br>
> additional<br>
> >> documentation (or other options) prior to mid-cycles (including ops) and<br>
> >> the next summit.<br>
> >><br>
> >> Matt<br>
> >><br>
> >><br>
> __________________________________________________________________________<br>
> >> OpenStack Development Mailing List (not for usage questions)<br>
> >> Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> >><br>
> >><br>
> ><br>
> ><br>
> ><br>
> ><br>
> __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/4056b361/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/4056b361/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 38<br>
Date: Wed, 13 Jul 2016 11:58:20 -0400<br>
From: David Moreau Simard <<a href="mailto:dms@redhat.com">dms@redhat.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [TripleO] Making TripleO CI easier to<br>
consume outside of TripleO CI<br>
Message-ID:<br>
<<a href="mailto:CAH7C%2BPrNqB6WWDHKPZTybqS0eUmbQn-42Fa5wqcwVnjP16X67w@mail.gmail.com">CAH7C+PrNqB6WWDHKPZTybqS0eUmbQn-42Fa5wqcwVnjP16X67w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Wed, Jul 13, 2016 at 9:06 AM, Wesley Hayutin <<a href="mailto:whayutin@redhat.com">whayutin@redhat.com</a>> wrote:<br>
> We also considered ansible-galaxy and any of the ansible roles found in<br>
> github/redhat-openstack/ansible-role could be moved into galaxy. Galaxy did<br>
> not end up meeting our requirements for installing the roles and we ended up<br>
> using python setuptools. Some roles have specific config and playbooks that<br>
> need to be copied to a standard location and galaxy just did not do that<br>
> very well.<br>
<br>
What special requirements do you have around that ?<br>
I'm able to install roles both from git (zuul-cloner) and from<br>
ansible-galaxy just fine.<br>
<br>
- ansible-role-requirements.yml [1]<br>
- ansible-galaxy install [2]<br>
- ansible.cfg role path [3]<br>
<br>
Stuff doesn't necessarily need to be "uploaded" to galaxy.<br>
ansible-galaxy is really a glorified wrapper around git :)<br>
<br>
[1]: <a href="https://github.com/rdo-infra/weirdo/blob/master/ansible-role-requirements.yml" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo/blob/master/ansible-role-requirements.yml</a><br>
[2]: <a href="https://github.com/rdo-infra/weirdo/blob/master/tox.ini#L26" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo/blob/master/tox.ini#L26</a><br>
[3]: <a href="https://github.com/rdo-infra/weirdo/blob/master/playbooks/ansible.cfg#L9" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo/blob/master/playbooks/ansible.cfg#L9</a><br>
<br>
David Moreau Simard<br>
Senior Software Engineer | Openstack RDO<br>
<br>
dmsimard = [irc, github, twitter]<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 39<br>
Date: Wed, 13 Jul 2016 18:04:25 +0200<br>
From: Ricardo Carrillo Cruz <<a href="mailto:ricardo.carrillo.cruz@gmail.com">ricardo.carrillo.cruz@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [TripleO] Making TripleO CI easier to<br>
consume outside of TripleO CI<br>
Message-ID:<br>
<CADe0dKDZDxuT_7iEczugyt9yA1QZG2sEANQge7mmQ-jjTB=<a href="mailto:o%2BA@mail.gmail.com">o+A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I concur, in infra we install roles from git repos.<br>
Those are defined in a yaml that are then feeded to ansible-galaxy tool:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack-infra/system-config/tree/roles.yaml" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack-infra/system-config/tree/roles.yaml</a><br>
<br>
Regards<br>
<br>
2016-07-13 17:58 GMT+02:00 David Moreau Simard <<a href="mailto:dms@redhat.com">dms@redhat.com</a>>:<br>
<br>
> On Wed, Jul 13, 2016 at 9:06 AM, Wesley Hayutin <<a href="mailto:whayutin@redhat.com">whayutin@redhat.com</a>><br>
> wrote:<br>
> > We also considered ansible-galaxy and any of the ansible roles found in<br>
> > github/redhat-openstack/ansible-role could be moved into galaxy. Galaxy<br>
> did<br>
> > not end up meeting our requirements for installing the roles and we<br>
> ended up<br>
> > using python setuptools. Some roles have specific config and playbooks<br>
> that<br>
> > need to be copied to a standard location and galaxy just did not do that<br>
> > very well.<br>
><br>
> What special requirements do you have around that ?<br>
> I'm able to install roles both from git (zuul-cloner) and from<br>
> ansible-galaxy just fine.<br>
><br>
> - ansible-role-requirements.yml [1]<br>
> - ansible-galaxy install [2]<br>
> - ansible.cfg role path [3]<br>
><br>
> Stuff doesn't necessarily need to be "uploaded" to galaxy.<br>
> ansible-galaxy is really a glorified wrapper around git :)<br>
><br>
> [1]:<br>
> <a href="https://github.com/rdo-infra/weirdo/blob/master/ansible-role-requirements.yml" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo/blob/master/ansible-role-requirements.yml</a><br>
> [2]: <a href="https://github.com/rdo-infra/weirdo/blob/master/tox.ini#L26" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo/blob/master/tox.ini#L26</a><br>
> [3]:<br>
> <a href="https://github.com/rdo-infra/weirdo/blob/master/playbooks/ansible.cfg#L9" rel="noreferrer" target="_blank">https://github.com/rdo-infra/weirdo/blob/master/playbooks/ansible.cfg#L9</a><br>
><br>
> David Moreau Simard<br>
> Senior Software Engineer | Openstack RDO<br>
><br>
> dmsimard = [irc, github, twitter]<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/fc1be016/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/fc1be016/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 40<br>
Date: Wed, 13 Jul 2016 12:12:24 -0400<br>
From: Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] The future of OpenStack documentation<br>
Message-ID: <1468425854-sup-236@lrrr.local><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Excerpts from Matt Kassawara's message of 2016-07-13 09:52:45 -0600:<br>
> The configuration reference essentially uses a script to parse help strings<br>
> from code in project repositories. Occasionally, the documentation team<br>
> augments content beyond what the automation provides. However, these<br>
> content augmentations, the script, and schedule for running the script<br>
> belong to the documentation team. Moving control of these items to projects<br>
> would likely yield a more robust configuration reference, particularly<br>
> regarding nuances of each project.<br>
<br>
oslo.config already includes support for showing option values in<br>
sphinx-processed documentation. See<br>
<a href="http://docs.openstack.org/developer/oslo.config/sphinxext.html" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/oslo.config/sphinxext.html</a> for<br>
instructions on the directives, and<br>
<a href="http://docs.openstack.org/developer/oslo.messaging/opts.html" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/oslo.messaging/opts.html</a> for an<br>
example of what it looks like rendered into HTML. You could experiment<br>
with this the existing developer documentation and if project teams<br>
agree it makes sense we could start setting up a separate reference<br>
guide in each repo.<br>
<br>
OTOH, sometimes configuring an application actually requires dealing<br>
with a deliverable that is spread across multiple repositories.<br>
Which is why at the summit we discussed updating the config generator<br>
to produce a format that is easier to parse (YAML, probably) and<br>
then use those files to produce the central config reference guide<br>
(or multiple guides). With a periodic job to propose patches to<br>
the guide repo, it could stay very close to up to date more or less<br>
automatically. Some of the other things I've been doing this cycle<br>
have delayed me starting on this, but I'm happy to share my ideas<br>
in more detail with anyone who wants to pick it up and work on it.<br>
<br>
> Speaking of help strings, I see a conflict between providing sufficient<br>
> content and preventing bloat of example configuration files. At the last<br>
> summit, I suggested implementing two types of help strings... one long and<br>
> one short. The configuration reference pulls the long string and the<br>
> configuration file generator pulls the short string. If this idea makes<br>
> sense, moving the configuration reference to project repositories would<br>
> potentially enable each project to implement such changes at its own pace.<br>
><br>
> On Wed, Jul 13, 2016 at 8:11 AM, Markus Zoeller <<a href="mailto:mzoeller@linux.vnet.ibm.com">mzoeller@linux.vnet.ibm.com</a><br>
> > wrote:<br>
><br>
> > On 11.07.2016 00:02, Steve Martinelli wrote:<br>
> > > I personally like this solution, it seems much more scalable. This<br>
> > follows<br>
> > > the same pattern of the API docs (moving the content to project repos),<br>
> > > which puts the onus back on the project team to maintain and create<br>
> > > documentation. I'm also hoping this results in less duplication between<br>
> > the<br>
> > > guides and the keystone developer docs (the latter of which start to<br>
> > stray<br>
> > > from "developer" docs and begin to look like "user" docs.<br>
> ><br>
> > After reading this, the "configuration reference" comes to my mind.<br>
> > Having the api-ref and the config-ref at one place, near the code, seems<br>
> > logical to me. Nova put a lot of effort into providing valuable help<br>
> > text for the config options in the last months. We should also make sure<br>
> > that it will result in a good manual, which could be easier if it's<br>
> > in-tree, near the code.<br>
> ><br>
> > --<br>
> > Regards, Markus Zoeller (markus_z)<br>
> ><br>
> > > The folks that contribute to the keystone guides today would still be<br>
> > very<br>
> > > welcomed to continue to contribute once/if the switch is made.<br>
> > ><br>
> > > On Fri, Jul 8, 2016 at 5:02 PM, Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>><br>
> > wrote:<br>
> > ><br>
> > >> Currently, OpenStack provides central documentation (primarily in the<br>
> > >> openstack-manuals repository) for operators and users. The single<br>
> > location<br>
> > >> and consistent structure eases audiences of various technical expertise<br>
> > >> into OpenStack, typically operators and users rather than developers.<br>
> > >> Although I'm not a fan of the word "product", increasingly less<br>
> > technical<br>
> > >> audiences are learning about OpenStack and tend to compare it with other<br>
> > >> cloud infrastructure products. Such audiences expect a coherent,<br>
> > relatively<br>
> > >> mature product to easily evaluate, usually via proof-of-concept. Upon<br>
> > >> deciding to implement OpenStack, the central documentation attempts to<br>
> > >> gracefully lead them toward a production deployment that meets or<br>
> > exceeds<br>
> > >> requirements and expectations.<br>
> > >><br>
> > >> However, since I began contributing to OpenStack documentation around<br>
> > the<br>
> > >> Havana release, I am seeing many projects, particularly core projects,<br>
> > >> trending toward more independence from other projects including central<br>
> > >> documentation. For operator and user documentation, a couple of projects<br>
> > >> contribute to the central documentation repository, some projects<br>
> > >> contribute to their own repositories, and an alarmingly large number of<br>
> > >> projects simply do not contribute such documentation and assume that all<br>
> > >> audiences involve developers. These differences lead to an increasingly<br>
> > >> negative overall experience for the audiences that OpenStack needs to<br>
> > >> increase adoption/growth and maintain the existing deployment base.<br>
> > >><br>
> > >> As a contributor to central documentation and one or more other projects<br>
> > >> including neutron, I see the problems from both sides and don't<br>
> > >> particularly blame either party for them. Some politics, some technical,<br>
> > >> some a lack of resources, and some just a general misunderstanding about<br>
> > >> documentation. However, I think we need to develop a solution that works<br>
> > >> for both parties and ultimately benefits our audiences.<br>
> > >><br>
> > >> One potential solution essentially involves moving operator and user<br>
> > >> documentation into project repositories (similar to developer<br>
> > >> documentation) and using infrastructure to coherently present it on<br>
> > >> <a href="http://docs.openstack.org" rel="noreferrer" target="_blank">docs.openstack.org</a> which achieves the following goals:<br>
> > >><br>
> > >> 1) Project developers can contribute documentation and code in the same<br>
> > >> patch, thus avoiding two different review queues and reviewers with<br>
> > >> different motivations and guidelines.<br>
> > >> 2) Project developers can either work directly or via liaison with one<br>
> > or<br>
> > >> more documentation team members to improve documentation components<br>
> > during<br>
> > >> development or after merging technically accurate content.<br>
> > >> 3) Rather than attempting to document all projects with little (if any)<br>
> > >> assistance from those projects, the primary role of the documentation<br>
> > team<br>
> > >> becomes managing overall organization/presentation of documentation and<br>
> > >> assisting projects with their contributions.<br>
> > >><br>
> > >> We're seeing decent adoption of moving API documentation into project<br>
> > >> repositories, so I want to initiate some discussion about moving<br>
> > additional<br>
> > >> documentation (or other options) prior to mid-cycles (including ops) and<br>
> > >> the next summit.<br>
> > >><br>
> > >> Matt<br>
> > >><br>
> > >><br>
> > __________________________________________________________________________<br>
> > >> OpenStack Development Mailing List (not for usage questions)<br>
> > >> Unsubscribe:<br>
> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> > >><br>
> > >><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > __________________________________________________________________________<br>
> > > OpenStack Development Mailing List (not for usage questions)<br>
> > > Unsubscribe:<br>
> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> > ><br>
> ><br>
> ><br>
> ><br>
> > __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 41<br>
Date: Wed, 13 Jul 2016 16:45:53 +0000<br>
From: Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [nova] focused review pipeline of bug fix<br>
changes?<br>
Message-ID: <<a href="mailto:20160713164553.GJ2458@yuggoth.org">20160713164553.GJ2458@yuggoth.org</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On 2016-07-13 09:56:37 +0200 (+0200), Sahid Orentino Ferdjaoui wrote:<br>
[...]<br>
> Gerrit comments are lost when the patch get merged, we may want to<br>
> provide some stats from these tags in future that's why I think commit<br>
> message is better.<br>
<br>
It's not true at all that Gerrit comments are lost when the patch<br>
gets merged. You can continue to query comments in Gerrit for merged<br>
changes, or even selectively limit to, e.g., status:merged or<br>
status:abandoned or whatever when generating your stats.<br>
<br>
> Also if we only change commit messages, all of the gate is<br>
> re-executed ?<br>
[...]<br>
<br>
It depends on your project configuration in Gerrit and Zuul as to<br>
whether votes are reset and which jobs are (re)run. We're also<br>
hoping to be able to detect commit message edits explicitly in a<br>
future version of Zuul and be able to have specific handling for<br>
that too (right now you're limited to deciding which jobs run based<br>
on filename patterns appearing in the diff instead).<br>
--<br>
Jeremy Stanley<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 42<br>
Date: Wed, 13 Jul 2016 16:50:04 +0000<br>
From: Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [nova] focused review pipeline of bug fix<br>
changes?<br>
Message-ID: <<a href="mailto:20160713165003.GK2458@yuggoth.org">20160713165003.GK2458@yuggoth.org</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On 2016-07-13 13:35:18 +0200 (+0200), Markus Zoeller wrote:<br>
[...]<br>
> it cannot be used in "gerrty" though, or can it?<br>
[...]<br>
<br>
It's probably one or two more lines of code to also print the Gerrit<br>
query such that it could be pasted into Gertty ^O (or make use of<br>
`gertty --open` to trigger opening that query URL directly into a<br>
running Gertty session?).<br>
--<br>
Jeremy Stanley<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 43<br>
Date: Wed, 13 Jul 2016 17:11:42 +0000<br>
From: Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [all][oslo] pbr potential breaking change<br>
coming<br>
Message-ID: <<a href="mailto:20160713171142.GL2458@yuggoth.org">20160713171142.GL2458@yuggoth.org</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On 2016-07-13 13:25:44 +0200 (+0200), Markus Zoeller wrote:<br>
> For some reason the gate docs job didn't find the issue (wrong json<br>
> format) which got fixed with change [1]. It doesn't even emit a warning.<br>
> Locally, the execution of "tox -e docs" does find the issue. Can we make<br>
> the gate docs job aware of such json format issues?<br>
[...]<br>
<br>
It looks like your "docs" tox env is doing some additional checks[1]<br>
with the json.tool module. The gate-{name}-docs CI jobs don't call<br>
`tox -e docs` but `tox -evenv -- python setup.py build_sphinx`<br>
directly[2]. Changing that has been discussed[3][4] (and<br>
rejected/withdrawn) by the TC in the past.<br>
<br>
I agree with Andreas that if you want additional checking of this<br>
you probably need it in a different job. The same goes for tests of<br>
your config/policy generation and API guide/reference builds. The<br>
goal of gate-{name}-docs is to make sure that the setup.py<br>
build_sphinx entrypoint works across all covered projects (per the<br>
CTI[5]) without requiring any extra nonstandard magic.<br>
<br>
[1] <a href="http://git.openstack.org/cgit/openstack/nova/tree/tox.ini?id=df0aa8a#n97" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/nova/tree/tox.ini?id=df0aa8a#n97</a><br>
[2] <a href="http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/run-docs.sh" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/run-docs.sh</a><br>
[3] <a href="http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-09-30-20.01.log.html#l-27" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-09-30-20.01.log.html#l-27</a><br>
[4] <a href="https://review.openstack.org/119875" rel="noreferrer" target="_blank">https://review.openstack.org/119875</a><br>
[5] <a href="http://governance.openstack.org/reference/cti/python_cti.html#documentation" rel="noreferrer" target="_blank">http://governance.openstack.org/reference/cti/python_cti.html#documentation</a><br>
--<br>
Jeremy Stanley<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 44<br>
Date: Wed, 13 Jul 2016 17:22:32 +0000<br>
From: Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [new][oslo] mox3 0.17.0 release (newton)<br>
Message-ID: <<a href="mailto:20160713172232.GM2458@yuggoth.org">20160713172232.GM2458@yuggoth.org</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On 2016-07-13 17:10:20 +0200 (+0200), Markus Zoeller wrote:<br>
> Whoever chooses the wording in these announcements, you're a genius!<br>
<br>
You too can be a genius--add some more--there's only ~20 at the<br>
moment so they repeat pretty often:<br>
<br>
<URL: <a href="http://git.openstack.org/cgit/openstack-infra/release-tools/tree/releasetools/release_notes.py?id=da89264#n33" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack-infra/release-tools/tree/releasetools/release_notes.py?id=da89264#n33</a> ><br>
--<br>
Jeremy Stanley<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 45<br>
Date: Wed, 13 Jul 2016 12:39:15 -0500<br>
From: Christopher Aedo <<a href="mailto:doc@aedo.net">doc@aedo.net</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>,<br>
<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>, user-committee<br>
<<a href="mailto:user-committee@lists.openstack.org">user-committee@lists.openstack.org</a>><br>
Subject: [openstack-dev] [app-catalog] App Catalog IRC meeting<br>
Thursday July 14th<br>
Message-ID:<br>
<CA+odVQGHay-pahhxiahdcyLvNe=<a href="mailto:Dun7MBpdne1xecjdt%2Brcw3Q@mail.gmail.com">Dun7MBpdne1xecjdt+rcw3Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Join us Thursday for our weekly meeting, scheduled for July 14th at<br>
17:00UTC in #openstack-meeting-3<br>
<br>
The agenda can be found here, and please add to if you want to discuss<br>
something with the Community App Catalog team:<br>
<a href="https://wiki.openstack.org/wiki/Meetings/app-catalog" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Meetings/app-catalog</a><br>
<br>
Tomorrow we will be talking more about our plan to implement GLARE as<br>
a back-end for the Community App Catalog, and what we'll need to merge<br>
in the next few weeks to make this a reality.<br>
<br>
Hope to see you there tomorrow!<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 46<br>
Date: Wed, 13 Jul 2016 17:46:13 +0000<br>
From: Jesse Pretorius <<a href="mailto:Jesse.Pretorius@rackspace.co.uk">Jesse.Pretorius@rackspace.co.uk</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [openstack-ansible] Nominating<br>
Jean-Philippe Evrard for core in openstack-ansible and all<br>
openstack-ansible-* roles<br>
Message-ID: <<a href="mailto:96401D83-9561-4527-B1EC-CE817F598B86@rackspace.co.uk">96401D83-9561-4527-B1EC-CE817F598B86@rackspace.co.uk</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
<br>
From: "Truman, Travis" <<a href="mailto:Travis_Truman@comcast.com">Travis_Truman@comcast.com</a><mailto:<a href="mailto:Travis_Truman@comcast.com">Travis_Truman@comcast.com</a>>><br>
Subject: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles<br>
<br>
Jean-Philippe has been providing great code reviews and patches for some time. His recent commitment to running bug triage every week shows his willingness to step up and take responsibilities within the community. He?s also found an opportunity to innovate by introducing an improved bug triage process. He can often be found in #openstack-ansible as evrardjp providing support to deployers in a welcoming and friendly manner.<br>
<br>
In short, just the kind of contribution our community desires from core reviewers.<br>
<br>
Very much agreed. +1 from me!<br>
<br>
________________________________<br>
Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at <a href="http://www.rackspace.co.uk/legal/privacy-policy" rel="noreferrer" target="_blank">www.rackspace.co.uk/legal/privacy-policy</a> - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at <a href="mailto:abuse@rackspace.com">abuse@rackspace.com</a> and delete the original message. Your cooperation is appreciated.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/31e6b206/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/31e6b206/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 47<br>
Date: Wed, 13 Jul 2016 10:47:12 -0700<br>
From: Steve Lewis <<a href="mailto:stevelle@gmail.com">stevelle@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [openstack-ansible] Nominating<br>
Jean-Philippe Evrard for core in openstack-ansible and all<br>
openstack-ansible-* roles<br>
Message-ID:<br>
<<a href="mailto:CACuNDX9wacF_cfqrhSxzspGtU2BOYwZvFeS7eR3TYk-Ma1gqoA@mail.gmail.com">CACuNDX9wacF_cfqrhSxzspGtU2BOYwZvFeS7eR3TYk-Ma1gqoA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Tue, Jul 12, 2016 at 11:33 AM, Truman, Travis <<a href="mailto:Travis_Truman@comcast.com">Travis_Truman@comcast.com</a>><br>
wrote:<br>
<br>
> In short, just the kind of contribution our community desires from core<br>
> reviewers.<br>
><br>
<br>
I'm happy to add my +1.<br>
<br>
--<br>
SteveL<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/db80bf30/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/db80bf30/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 48<br>
Date: Wed, 13 Jul 2016 12:47:26 -0500<br>
From: "Carter, Kevin" <<a href="mailto:kevin@cloudnull.com">kevin@cloudnull.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [openstack-ansible] Nominating<br>
Jean-Philippe Evrard for core in openstack-ansible and all<br>
openstack-ansible-* roles<br>
Message-ID:<br>
<CAAG3CGos_kbwqQ=<a href="mailto:EjHrjbiuwHXRcAwDbx5pUN-wEY1_vDTh2Pg@mail.gmail.com">EjHrjbiuwHXRcAwDbx5pUN-wEY1_vDTh2Pg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
+1 from me too. It'll be great to have him on the core team.<br>
<br>
On Tue, Jul 12, 2016 at 1:33 PM, Truman, Travis<br>
<<a href="mailto:Travis_Truman@comcast.com">Travis_Truman@comcast.com</a>> wrote:<br>
> Jean-Philippe has been providing great code reviews and patches for some<br>
> time. His recent commitment to running bug triage every week shows his<br>
> willingness to step up and take responsibilities within the community. He?s<br>
> also found an opportunity to innovate by introducing an improved bug triage<br>
> process. He can often be found in #openstack-ansible as evrardjp providing<br>
> support to deployers in a welcoming and friendly manner.<br>
><br>
> In short, just the kind of contribution our community desires from core<br>
> reviewers.<br>
><br>
> Thanks for all that you do for the community Jean-Philippe,<br>
> Travis Truman<br>
><br>
><br>
><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 49<br>
Date: Wed, 13 Jul 2016 17:49:35 +0000<br>
From: "Hayes, Graham" <<a href="mailto:graham.hayes@hpe.com">graham.hayes@hpe.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: [openstack-dev] [designate] Designate News Round Up<br>
Message-ID:<br>
<<a href="mailto:CS1PR84MB02150DDAC09E88FC35985D9090310@CS1PR84MB0215.NAMPRD84.PROD.OUTLOOK.COM">CS1PR84MB02150DDAC09E88FC35985D9090310@CS1PR84MB0215.NAMPRD84.PROD.OUTLOOK.COM</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi All,<br>
<br>
Just a quick update on a few things!<br>
<br>
Mid Cycle<br>
=========<br>
<br>
The Mid Cycle is confirmed for 22-26th of August.<br>
<br>
It will be in Dublin, in the city center.<br>
<br>
The address is<br>
<br>
64 Mount Street Lower,<br>
Dublin 2.<br>
D02 TH77<br>
Ireland<br>
<br>
I will be updating the page on the wiki with local hotels<br>
over the next day or so, so keep an eye on<br>
<br>
<a href="https://wiki.openstack.org/wiki/Sprints/DesignateNewtonSprint" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Sprints/DesignateNewtonSprint</a><br>
<br>
This is a shared office space, so we will need to let people in<br>
as they arrive - my phone number is +353 87 377 8315<br>
<br>
Docs Sprint<br>
===========<br>
<br>
Today's docs sprint went well, we have a few reviews outstanding, so if<br>
everyone could have a look at the following:<br>
<br>
# <a href="https://review.openstack.org/#/c/341622/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/341622/</a><br>
# <a href="https://review.openstack.org/#/c/341614/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/341614/</a><br>
# <a href="https://review.openstack.org/#/c/341583/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/341583/</a><br>
# <a href="https://review.openstack.org/#/c/341672/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/341672/</a><br>
<br>
<br>
Project Mascot<br>
==============<br>
<br>
The foundation has kindly offered to create mascots for each project.<br>
<br>
Can everyone put ideas in the etherpad:<br>
<br>
<a href="https://etherpad.openstack.org/p/designate-mascot" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/designate-mascot</a><br>
<br>
And if you see an idea you like, stick a "+" beside it.<br>
<br>
We will take the top few ideas and pass them to the foundation.<br>
<br>
Thanks!<br>
<br>
- Graham<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 50<br>
Date: Wed, 13 Jul 2016 13:03:36 -0500<br>
From: Jimmy McCrory <<a href="mailto:jimmy.mccrory@gmail.com">jimmy.mccrory@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [openstack-ansible] Nominating<br>
Jean-Philippe Evrard for core in openstack-ansible and all<br>
openstack-ansible-* roles<br>
Message-ID:<br>
<CAG9FQbb+t8Fi6Tn3VJ4B0U5heJC88df7mR11_NWJ3gS6P=<a href="mailto:rXJw@mail.gmail.com">rXJw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
+1, would make a great addition.<br>
<br>
On Wed, Jul 13, 2016 at 12:47 PM, Carter, Kevin <<a href="mailto:kevin@cloudnull.com">kevin@cloudnull.com</a>> wrote:<br>
<br>
> +1 from me too. It'll be great to have him on the core team.<br>
><br>
> On Tue, Jul 12, 2016 at 1:33 PM, Truman, Travis<br>
> <<a href="mailto:Travis_Truman@comcast.com">Travis_Truman@comcast.com</a>> wrote:<br>
> > Jean-Philippe has been providing great code reviews and patches for some<br>
> > time. His recent commitment to running bug triage every week shows his<br>
> > willingness to step up and take responsibilities within the community.<br>
> He?s<br>
> > also found an opportunity to innovate by introducing an improved bug<br>
> triage<br>
> > process. He can often be found in #openstack-ansible as evrardjp<br>
> providing<br>
> > support to deployers in a welcoming and friendly manner.<br>
> ><br>
> > In short, just the kind of contribution our community desires from core<br>
> > reviewers.<br>
> ><br>
> > Thanks for all that you do for the community Jean-Philippe,<br>
> > Travis Truman<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/a9bd1f61/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/a9bd1f61/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 51<br>
Date: Wed, 13 Jul 2016 22:17:59 +0300<br>
From: Denis Makogon <<a href="mailto:lildee1991@gmail.com">lildee1991@gmail.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: Re: [openstack-dev] [all] Status of the OpenStack port to<br>
Python 3<br>
Message-ID:<br>
<CALzSdt=<a href="mailto:XV01jzBX1YgMMwHcnEd3vB_zSPiUr6P4YLpORgvNHvg@mail.gmail.com">XV01jzBX1YgMMwHcnEd3vB_zSPiUr6P4YLpORgvNHvg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello to All.<br>
<br>
<br>
I have free capacity to work on porting code to Py3. So, if any PTL is<br>
running out of team capacity i can help to work on project to enable Py3<br>
support.<br>
<br>
Kind regards,<br>
Denys Makogon<br>
<br>
<br>
2016-07-06 13:01 GMT+03:00 Flavio Percoco <<a href="mailto:flavio@redhat.com">flavio@redhat.com</a>>:<br>
<br>
> On 24/06/16 12:17 -0400, Sean Dague wrote:<br>
><br>
>> On 06/24/2016 11:48 AM, Doug Hellmann wrote:<br>
>><br>
>>> Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200:<br>
>>><br>
>>>> On 06/23/2016 11:21 PM, Clark Boylan wrote:<br>
>>>><br>
>>>>> On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote:<br>
>>>>><br>
>>>>>> Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200:<br>
>>>>>><br>
>>>>>>> On 06/23/2016 06:11 PM, Doug Hellmann wrote:<br>
>>>>>>><br>
>>>>>>>> I'd like for the community to set a goal for Ocata to have Python<br>
>>>>>>>> 3 functional tests running for all projects.<br>
>>>>>>>><br>
>>>>>>>> As Tony points out, it's a bit late to have this as a priority for<br>
>>>>>>>> Newton, though work can and should continue. But given how close<br>
>>>>>>>> we are to having the initial phase of the port done (thanks<br>
>>>>>>>> Victor!),<br>
>>>>>>>> and how far we are from discussions of priorities for Ocata, it<br>
>>>>>>>> seems very reasonable to set a community-wide goal for our next<br>
>>>>>>>> release cycle.<br>
>>>>>>>><br>
>>>>>>>> Thoughts?<br>
>>>>>>>><br>
>>>>>>>> Doug<br>
>>>>>>>><br>
>>>>>>><br>
>>>>>>> +1<br>
>>>>>>><br>
>>>>>>> Just think about it for a while. If we get Nova to work with Py3, and<br>
>>>>>>> everything else is working, including all functional tests in<br>
>>>>>>> Tempest,<br>
>>>>>>> then after Otaca, we could even start to *REMOVE* Py2 support after<br>
>>>>>>> Otaca+1. That would be really awesome to stop all the compat layer<br>
>>>>>>> madness and use the new features available in Py3.<br>
>>>>>>><br>
>>>>>><br>
>>>>>> We'll need to get some input from other distros and from deployers<br>
>>>>>> before we decide on a timeline for dropping Python 2. For now, let's<br>
>>>>>> focus on making Python 3 work. Then we can all rejoice while having<br>
>>>>>> the<br>
>>>>>> discussion of how much longer to support Python 2. :-)<br>
>>>>>><br>
>>>>>><br>
>>>>>>> I really would love to ship a full stack running Py3 for Debian<br>
>>>>>>> Stretch.<br>
>>>>>>> However, for this, it'd be super helful to have as much visibility as<br>
>>>>>>> possible. Are we setting a hard deadline for the Otaca release? Or is<br>
>>>>>>> this just a goal we only "would like" to reach, but it's not really a<br>
>>>>>>> big deal if we don't reach it?<br>
>>>>>>><br>
>>>>>><br>
>>>>>> Let's see what PTLs have to say about planning, but I think if not<br>
>>>>>> Ocata then we'd want to set one for the P release. We're running<br>
>>>>>> out of supported lifetime for Python 2.7.<br>
>>>>>><br>
>>>>><br>
>>>>> Keep in mind that there is interest in running OpenStack on PyPy which<br>
>>>>> is python 2.7. We don't have to continue supporting CPython 2.7<br>
>>>>> necessarily but we may want to support python 2.7 by way of PyPy.<br>
>>>>><br>
>>>><br>
>>>> PyPy folks have been working on python 3 support for some time already:<br>
>>>> <a href="http://doc.pypy.org/en/latest/release-pypy3.3-v5.2-alpha1.html" rel="noreferrer" target="_blank">http://doc.pypy.org/en/latest/release-pypy3.3-v5.2-alpha1.html</a><br>
>>>> It's an alpha, but by the time we consider dropping Python 2 it will<br>
>>>> probably be released :)<br>
>>>><br>
>>><br>
>>> We're targeting Python >=3.4, right now. We'll have to decide as<br>
>>> a community whether PyPy support is a sufficient reason to keep<br>
>>> support for "older" versions (either 2.x or earlier versions of 3).<br>
>>> Before we can have that discussion, though, we need to actually run on<br>
>>> Python 3, so let's focus on that and evaluate the landscape of other<br>
>>> interpreters when the porting work is done.<br>
>>><br>
>><br>
>> +1, please don't get ahead of things until there is real full stack<br>
>> testing running on python3.<br>
>><br>
>> It would also be good if some of our operators were running on python 3<br>
>> and providing feedback that it works in the real world before we even<br>
>> talk about dropping. Because our upstream testing (even the full stack<br>
>> testing) only can catch so much.<br>
>><br>
>> So next steps:<br>
>><br>
>> 1) full stack testing of everything we've got on python3 - (are there<br>
>> volunteers to get that going?)<br>
>> 2) complete Nova port to enable full stack testing on python3 for iaas<br>
>> base<br>
>> 3) encourage operators to deploy with python3 in production<br>
>> 4) gather real world feedback, develop rest of plan<br>
>><br>
><br>
><br>
> Just one to +1 the above steps. I'd be very hesitant to make any plan<br>
> until we<br>
> are able to get not only nova but all the projects in the<br>
> starter-kit:compute[0]<br>
> running pn python3 (and w/ a full stack test).<br>
><br>
> [0]<br>
> <a href="https://governance.openstack.org/reference/tags/starter-kit_compute.html" rel="noreferrer" target="_blank">https://governance.openstack.org/reference/tags/starter-kit_compute.html</a><br>
><br>
><br>
> Flavio<br>
><br>
> --<br>
> @flaper87<br>
> Flavio Percoco<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/1cb6173c/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/attachments/20160713/1cb6173c/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 52<br>
Date: Wed, 13 Jul 2016 19:38:03 +0000<br>
From: "Watanabe, Isao" <<a href="mailto:watanabe_isao@jp.fujitsu.com">watanabe_isao@jp.fujitsu.com</a>><br>
To: "<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: [openstack-dev] [Cinder][CI] Rule of recheck keywords has<br>
been updated<br>
Message-ID: <AC0F94DB49C0C2439892181E6CDA6E6C173917D4@G01JPEXMBYT05><br>
Content-Type: text/plain; charset="iso-2022-jp"<br>
<br>
Hello Cinder Third-Party CI Maintainers,<br>
<br>
The rule of recheck keywords has been discussed in today's IRC meeting [1].<br>
And the wiki [2] of tested-3rdParty-drivers has been updated.<br>
# The diff is [3].<br>
<br>
Please check the update and update your CI.<br>
It would be appreciated if you could also update the "Recheck trigger" information in your CI's wiki.<br>
You can find your CI's wiki pages at [4].<br>
<br>
[1] <a href="http://eavesdrop.openstack.org/meetings/cinder/2016/cinder.2016-07-13-16.00.log.html" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/meetings/cinder/2016/cinder.2016-07-13-16.00.log.html</a><br>
[2] <a href="https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_trigger_my_CI_to_rerun_on_gerrit_comments.3F" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_trigger_my_CI_to_rerun_on_gerrit_comments.3F</a><br>
[3] <a href="https://wiki.openstack.org/w/index.php?title=Cinder/tested-3rdParty-drivers&curid=3690&diff=128050&oldid=126774" rel="noreferrer" target="_blank">https://wiki.openstack.org/w/index.php?title=Cinder/tested-3rdParty-drivers&curid=3690&diff=128050&oldid=126774</a><br>
[4] <a href="https://wiki.openstack.org/wiki/ThirdPartySystems" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/ThirdPartySystems</a><br>
<br>
Best regards,<br>
Watanabe.isao<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 53<br>
Date: Wed, 13 Jul 2016 14:47:53 -0500<br>
From: Matt Riedemann <<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)"<br>
<<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
Subject: [openstack-dev] [nova] Let's kill quota classes (again)<br>
Message-ID: <<a href="mailto:9a418d72-2ce1-970a-11e2-53b5472739d0@linux.vnet.ibm.com">9a418d72-2ce1-970a-11e2-53b5472739d0@linux.vnet.ibm.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
We got a bug that the os-quota-class-sets API isn't documented:<br>
<br>
<a href="https://bugs.launchpad.net/nova/+bug/1602400" rel="noreferrer" target="_blank">https://bugs.launchpad.net/nova/+bug/1602400</a><br>
<br>
That's probably because we hate it and no one understands it.<br>
<br>
See this previous thread about trying to sort this out from the long<br>
long ago:<br>
<br>
<a href="https://lists.launchpad.net/openstack/msg12200.html" rel="noreferrer" target="_blank">https://lists.launchpad.net/openstack/msg12200.html</a><br>
<br>
We tried killing it before, but it turns out, it's actually used by<br>
something!<br>
<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2014-May/036031.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-May/036031.html</a><br>
<br>
But we didn't have integration testing in Tempest for default quotas at<br>
that time (we added those tests in when we reverted the delete of the<br>
API back in Juno).<br>
<br>
I got looking at this because of the quota_class attribute in the nova<br>
RequestContext:<br>
<br>
<a href="https://github.com/openstack/nova/blob/93cc5e3ffd2867bdb39a707a230c1efc6ed2f5f4/nova/context.py#L138-L141" rel="noreferrer" target="_blank">https://github.com/openstack/nova/blob/93cc5e3ffd2867bdb39a707a230c1efc6ed2f5f4/nova/context.py#L138-L141</a><br>
<br>
That led me to markmc's thread about that only being there for the<br>
turnstile project and some old API rate limiting stuff that Rackspace<br>
was doing out of tree (it appears to set a type of middleware for a<br>
quota class for rate limiting).<br>
<br>
Anyway, super duper out of tree stuff that is probably not even used<br>
anymore (Vek - if you're reading, please speak up).<br>
<br>
I'll also point out that API rate limiting as a paste config was only in<br>
the v2 API and that code was all dropped and the API rate limiting stuff<br>
wasn't carried over for the v2.1 API, for good reason, see:<br>
<br>
<a href="http://lists.openstack.org/pipermail/openstack-operators/2016-June/010692.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-operators/2016-June/010692.html</a><br>
<br>
You can still create unique quota classes via the os-quota-class-sets<br>
API (it does a create if the update operation fails), but as far as I<br>
can tell you can't really use those in any meaningful way.<br>
<br>
We really just have the 'default' quota class with a buttload of code<br>
and plumbing to use that, which sucks, because it's all very complicated.<br>
<br>
So I think I'm going to start a pet project of rooting this stuff out<br>
again, starting with nova.context.RequestContext.quota_class, unless<br>
anyone has a good reason we should keep this in tree.<br>
<br>
I think we should also add a microversion to the API in Ocata to disable<br>
the ability to create new quota classes, so that update is only update,<br>
and a 404 for anything else.<br>
<br>
--<br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
End of OpenStack-dev Digest, Vol 51, Issue 26<br>
*********************************************<br>
</blockquote></div><br></div></div>