Re: [openstack-dev] [nova] Dropping DB Downgrades, need Turbo Hipster tests updated
Hey, turbo-hipster is no longer testing downgrades as per the TC decision. The CI bot now passes on that change. Cheers, Josh Rackspace Australia On 4/20/15 10:16 PM, Sean Dague wrote: Awesome, thanks Josh. On 04/20/2015 07:14 AM, Joshua Hesketh wrote: Hi Sean, Thanks for your work on this. I'll take a closer look tomorrow and remove the downgrade testing from turbo-hipster in line with the TC decision. Cheers, Josh From: Sean Dague s...@dague.net Sent: Monday, 20 April 2015 8:38 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [nova] Dropping DB Downgrades, need Turbo Hipster tests updated This proposed patch to drop the db downgrades in Nova master is making Turbo Hipster face plant - https://review.openstack.org/#/c/175010/ It appears that turbo hipster is walking all the way up, then walking back down through migrations, which clearly, is no longer a thing. It would be nice to merge this patch sooner rather than later, so would be great if Turbo hipster could function on migrations without downgrades RSN. -Sean -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Rackspace Hosting Australia PTY LTD a company registered in the state of Victoria, Australia (company registered number ACN 153 275 524) whose registered office is at Level 1, 37 Pitt Street, Sydney, NSW 2000, Australia. Rackspace Hosting Australia PTY LTD privacy policy can be viewed at www.rackspace.com.au/company/legal-privacy-statement.php - 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 ab...@rackspace.com and delete the original message. Your cooperation is appreciated. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Required data migrations in Kilo, need Turbo Hipster tests updated
Hey, turbo hipster already knows how to upgrade major releases, so adding this should be possible. That said, I've been travelling all day so haven't had a chance to look at this. If Josh doesn't beat me to it, I will take a look when I get to my hotel tonight. (We should also note that we can just merge a thing without turbo hipster passing if we understand the reason for the test failure. Sure, that breaks the rest of the turbo hipster runs, but we're not 100% blocked here.) Michael On Tue, Apr 21, 2015 at 12:09 AM, Dan Smith d...@danplanet.com wrote: This proposed patch requiring a data migration in Nova master is making Turbo Hipster face plant - https://review.openstack.org/#/c/174480/ This is because we will require Kilo deployers to fully migrate their flavor data from system_metadata to instance_extra before they upgrade to the next release. They (and turbo hipster) will need to do this first: https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L963 I'm not sure how you want to handle this, either by converting your data sets, or only converting the ones that master runs. It would be nice to merge this patch as soon as grenade is ready to do so, as it's blocking all other db migrations in master. Thanks! --Dan __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Rackspace Australia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Regarding openstack swift implementation
Hello, On Tue, Apr 21, 2015 at 7:34 AM, Subbulakshmi Subha subbulakshmisubh...@gmail.com wrote: I want to simulate it one javasim,so I want to know how are objects stored in the partitions in swift.I computed the md5 hash of the objects url, n the medium of storage is hashmap,so I want to know how doea it store it there?is there any algorithm for it? this should be documented here : http://docs.openstack.org/developer/swift/overview_ring.html Chmouel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [glance] Why no DB index on sort parameters
Hi All, I see that glance supports arbitrary sort parameters and the default is created_at while listing images. Is there any reason why we don't have index over these fields? If we have an index over these fields then we would avoid a full table scan to do sorting. IMO at least the created_at field should have an index on it. Cheers, Ajaya __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Are routed TAP interfaces (and DHCP for them) in scope for Neutron?
I haven't yet had any responses to this, so reflagging it in case it was just missed in the helter skelter of activity that is the openstack-dev mailing list... On the other hand, if I need to describe more clearly what I'm on about, please don't be afraid to say that! Any comments and steer would be appreciated, even if they're more of a high level gut feel, than an exhaustive treatment. Thanks, Neil On 16/04/15 15:12, Neil Jerram wrote: I have a Neutron DHCP agent patch whose purpose is to launch dnsmasq with options such that it works (= provides DHCP service) for TAP interfaces that are _not_ bridged to the DHCP interface (ns-XXX). For the sake of being concrete, this involves: - creating the ns-XXX interface as a dummy, instead of as a veth pair - launching dnsmasq with --bind-dynamic --listen=ns-XXX --listen=tap* --bridge-interface=ns-XXX,tap* - not running in a separate namespace - running the DHCP agent on every compute host, instead of only on the network node - using the relevant subnet's gateway IP on the ns-XXX interface (on every host), instead of allocating a different IP for each ns-XXX interface. I proposed a spec for this in the Kilo cycle [1], but it didn't get enough traction, and I'm now wondering what to do with this work/function. Specifically, whether to look again at integrating it into Neutron during the Liberty cycle, or whether to maintain an independent DHCP agent for my project outside the upstream Neutron tree. I would very much appreciate any comments or advice on this. For answering that last question, I suspect the biggest factor is whether routed TAP interfaces - i.e. forms of networking implementation that rely on routing data between VMs instead of bridging it - is in scope for Neutron, at all. If it is, I understand that there could be a lot more detail to work on, such as how it meshes with other Neutron features such as DVR and the IPAM work, and that it might end up being quite different from the blueprint linked below. But it would be good to know whether this would ultimately be in scope and of interest for Neutron at all. Please do let me now what you think. Many thanks, Neil [1] https://blueprints.launchpad.net/neutron/+spec/dhcp-for-routed-ifs __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]
- Original Message - From: Jeremy Stanley fu...@yuggoth.org To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Friday, April 17, 2015 9:35:07 PM Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work] On 2015-04-17 11:49:23 -0700 (-0700), Kevin Benton wrote: I definitely understand that. But what is the major complaint from operators? I understood that quote to imply it was around Neutron's model of self-service networking. My takeaway from Tom's message was that there was a concern about complexity in all forms (not just of the API but also due to the lack of maturity, documentation and debuggability of the underlying technology), and that the self-service networking model was simply one example of that. Perhaps I was reading between the lines too much because of prior threads on both the operators and developers mailing lists. Anyway, I'm sure Tom will clarify what he meant if necessary. IMHO the OVS is less complex than netfilter (iptables, *tables), if someone able to deal with reading the netfilter rules he should be able to deal with OVS as well. OVS has debugging tools for internal operations, I guess you are looking for something else. I do not have any `good debugging` tool for net-filter either. The way how openstack/neutron/devstack by default uses OVS is simpler, than most small (non openstack related) OVS example trying to explain. I kind of agree with the lack of documentation part. A documentation which explains howto use OVS in same way as neutron does would be helpfull for new comers. If the main reason the remaining Nova-net operators don't want to use Neutron is due to the fact that they don't want to deal with the Neutron API, swapping some implementation defaults isn't really going to get us anywhere on that front. This is where I think the subthread has definitely wandered off topic too. Swapping implementation defaults in DevStack because it's quicker and easier to get running on the typical all-in-one/single-node setup and faster to debug problems with (particularly when you're trying to work on non-network-related bits and just need to observe the network communication between your services) doesn't seem like it should have a lot to do with the recommended default configuration for a large production deployment. One size definitely does not fit all. It's an important distinction because it determines what actionable items we can take (e.g. what Salvatore mentioned in his email about defaults). Does that make sense? It makes sense in the context of the Neutron/Nova network parity topic, but not so much in the context of the DevStack default settings topic. DevStack needs a simple default that just works, and doesn't need the kitchen sink. You can turn on more complex options as you need to test them out. In some ways this has parallels to the complexity concerns the operator community has over Neutron and OVS, but I think they're still relatively distinct topics. -- Jeremy Stanley __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] debtcollector release 0.4.0 (liberty)
We are stoked to announce the release of: debtcollector 0.4.0: A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non- destructive manner. For more details, please see the git log history below and: http://launchpad.net/debtcollector/+milestone/0.4.0 Please report issues through launchpad: http://bugs.launchpad.net/debtcollector Changes in debtcollector 0.3.0..0.4.0 - 62a75d7 2015-04-16 17:49:16 + Uncap library requirements for liberty 3afa864 2015-04-10 17:37:16 -0700 No longer need to workaround six issue/bug 3eddc93 2015-04-08 10:35:17 -0700 Add pypi download + version badges cd3e5d8 2015-03-21 00:08:07 + Updated from global requirements Diffstat (except docs and test files) - README.rst | 8 debtcollector/moves.py | 8 +--- requirements.txt | 2 +- test-requirements.txt | 4 ++-- 5 files changed, 14 insertions(+), 11 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 6af7f18..827fc3b 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8 +8 @@ six=1.9.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 8592bde..031650a 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11,2 +11,2 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] project) release 1.3.0 (liberty)
We are glad to announce the release of: django_openstack_auth 1.3.0: Django authentication backend for use with OpenStack Identity For more details, please see the git log history below and: https://launchpad.net/django-openstack-auth/+milestone/1.3.0 Please report issues through launchpad: https://bugs.launchpad.net/django-openstack-auth Changes in django_openstack_auth 1.2.0..1.3.0 - 3a8d34f 2015-04-21 14:51:17 + Update README to work with release tools 03446e8 2015-04-20 06:03:10 + Imported Translations from Transifex 8657c04 2015-04-19 06:02:29 + Imported Translations from Transifex 866471a 2015-04-17 06:03:00 + Imported Translations from Transifex 1786833 2015-04-16 17:50:31 + Uncap library requirements for liberty Diffstat (except docs and test files) - README.rst| 9 + openstack_auth/locale/ar/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ca/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/cs/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/de/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/en_AU/LC_MESSAGES/django.po | 12 +++- openstack_auth/locale/en_GB/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/es/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/es_MX/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fi_FI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fr/LC_MESSAGES/django.po| 9 + openstack_auth/locale/hi/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/it/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ko_KR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/ne/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/nl_NL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pa_IN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pl_PL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pt/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/pt_BR/LC_MESSAGES/django.po | 18 ++ openstack_auth/locale/ru/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/sl_SI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/sr/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/tr_TR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/uk/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/zh_CN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/zh_TW/LC_MESSAGES/django.po | 6 +++--- requirements.txt | 2 +- test-requirements.txt | 2 +- 29 files changed, 98 insertions(+), 92 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 8116201..bdbd4b5 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ Django=1.4.2,1.8 -oslo.config=1.9.3,1.10.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index c8c6a3b..58cab54 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-barbicanclient release 3.0.1 (liberty)
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Liberty Design Summit - Proposed room / time layout
On 04/17/2015 05:00 AM, Thierry Carrez wrote: Hi PTLs, Following the slot allocation last week, here is the proposed room layout: https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit?usp=sharing It takes into account the following changes: - Barbican donates on fishbowl room to Security - Magnum takes one of the available Friday-afternoon sprints You'll notice that we still have 3 unallocated Friday afternoon sprints, as well as an unallocated fishbowl room. Ceilometer expressed interest in having the latter (which would require some shuffling around since they have a work session at that time). At this point I prefer to keep it for late adjustments. If you see major problems with the proposed layout let me know. I may have missed a blatant issue. It's a bit difficult to find a combination that works for everyone, especially when you add conference talk conflicts in the mix, but I'll do my best to accommodate reported issues. My main request was that the Manila sessions didn't overlap with the Cinder sessions, since there are some key people who are involved in both projects. It looks like some attempt was made to avoid overlaps (the fishbowl sessions at least), but the working sessions could be adjusted to overlap less (space permitting). I would prefer that some of the Wednesday Manila working sessions were moved to the end of Thursday (after the Cinder ones). -Ben Swartzlander Barring major issues we'll push this to the Design Summit sched and let PTLs update the content there as they refine content. Regards, __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] keystonemiddleware release 1.6.0 (liberty)
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.utils release 1.5.0 (liberty)
We are pleased to announce the release of: oslo.utils 1.5.0: Oslo Utility library For more details, please see the git log history below and: http://launchpad.net/oslo.utils/+milestone/1.5.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.utils Changes in oslo.utils 1.4.0..1.5.0 -- a18b051 2015-04-17 17:57:07 + Add liberty release name to versionutils 824732d 2015-04-17 17:56:53 + Expose opts entry point for version_utils 9044829 2015-04-17 17:56:41 + Switch from oslo.config to oslo_config bbf48f0 2015-04-17 17:56:26 + Remove oslo.log code and clean up versionutils API 5ae762c 2015-04-17 17:56:11 + Remove code that moved to oslo.i18n b7e5c5f 2015-04-17 17:55:56 + Enhance versionutils.deprecated to work with classes 0672a61 2015-04-17 17:55:33 + Add Kilo release name to versionutils 427b8af 2015-04-17 13:54:48 -0400 Allow deprecated decorator to specify no plan for removal 3371550 2015-04-16 18:09:46 + Uncap library requirements for liberty 96e1ab7 2015-04-16 11:37:26 + Add JUNO as a target to versionutils module 3a7fca5 2015-04-13 10:49:20 -0700 Add missing reflection + uuidutils docs c50d816 2015-04-10 17:15:31 +0200 timeutils: avoid passing leap second to datetime cb88d17 2015-04-07 18:19:37 -0700 Add pypi download + version badges 6ab5ae2 2015-04-04 02:22:36 -0400 Cleanup README.rst and setup.cfg 0fae531 2015-04-03 12:27:59 + pep8: fixed multiple violations 486fac2 2015-04-03 12:27:59 + Use oslotest instead of common test module a55dc72 2015-04-03 12:27:59 + Use hacking import_exceptions for gettextutils._ e00421c 2015-04-03 12:27:59 + fixed typos 7c8ebe8 2015-04-03 12:27:59 + Fix violations of H302:import only modules db513b5 2015-04-03 12:27:59 + Adds decorator to deprecate functions and methods d5f98cd 2015-04-03 12:27:59 + Remove vim header 6afa675 2015-04-03 12:27:59 + Add `versionutils` for version compatibility checks 597d5dd 2015-04-03 12:27:59 + Update hacking setting a649d55 2015-03-28 02:34:31 + Updated from global requirements 69526a1 2015-03-26 06:12:10 + Imported Translations from Transifex 782e41f 2015-03-23 17:53:49 + Clean up TestIsIPv6Enabled b200da8 2015-03-23 14:37:56 +0100 Fix test_netutils: stop patches 4ab214e 2015-03-18 12:37:01 -0400 Add a new string to the list of masked patterns 1a6dc73 2015-03-16 15:33:18 -0700 Provide common `fetch_current_thread_functor` function 6fe565d 2015-03-16 06:11:07 + Imported Translations from Transifex e1bc333 2015-01-28 13:44:59 -0500 add dependency warning to requirements.txt Diffstat (except docs and test files) - README.rst | 15 +- openstack/common/versionutils.py | 262 +++ oslo.utils/locale/de/LC_MESSAGES/oslo.utils.po | 30 ++- oslo.utils/locale/en_GB/LC_MESSAGES/oslo.utils.po | 30 ++- .../locale/fr/LC_MESSAGES/oslo.utils-log-error.po | 12 +- .../locale/fr/LC_MESSAGES/oslo.utils-log-info.po | 43 oslo.utils/locale/fr/LC_MESSAGES/oslo.utils.po | 32 ++- oslo.utils/locale/oslo.utils.pot | 30 ++- oslo_utils/eventletutils.py| 18 ++ oslo_utils/reflection.py | 3 +- oslo_utils/strutils.py | 3 +- oslo_utils/timeutils.py| 9 +- oslo_utils/uuidutils.py| 4 + requirements.txt | 7 +- test-requirements.txt | 6 +- 23 files changed, 849 insertions(+), 74 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index be23276..11d5413 100644 --- a/requirements.txt +++ b/requirements.txt @@ -4,0 +5,5 @@ +# NOTE(dhellmann): Because oslo.utils is used by the client libraries, +# we do not want to add a lot of dependencies to it. If you find that +# adding a new feature to oslo.utils means adding a new dependency, +# that is a likely indicator that the feature belongs somewhere else. + @@ -9 +14 @@ iso8601=0.1.9 -oslo.i18n=1.3.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 0fab2b3..7f335ce 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -5 +5 @@ -hacking=0.9.1,0.10 +hacking=0.10.0,0.11 @@ -13 +13 @@ testtools=0.9.36,!=1.2.0 -oslotest=1.2.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -22 +22 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] pycadf release 0.9.0 (liberty)
We are stoked to announce the release of: pycadf 0.9.0: CADF Library For more details, please see the git log history below and: https://launchpad.net/pycadf/+milestone/0.9.0 Please report issues through launchpad: https://bugs.launchpad.net/pycadf Changes in pycadf 0.8.0..0.9.0 -- 9501f4f 2015-04-16 18:11:14 + Uncap library requirements for liberty f436f9b 2015-03-21 00:17:21 + Updated from global requirements b697115 2015-03-17 18:05:45 -0400 update README.rst to include additional links 1a55d1c 2015-03-12 11:47:05 -0400 Remove empty _templates folder 87f5f39 2015-03-11 23:36:36 -0400 Add a section for audit maps ad80497 2015-03-07 19:28:21 + Fix formatting error for geolocation note 0379e70 2015-03-07 19:27:37 + add a new set of release notes 8180e64 2015-03-07 13:45:29 -0500 Clean up pycadf's doc landing page 25a4227 2015-03-07 12:14:29 -0500 Add api_audit_map.conf for Trove project 72acde6 2015-03-06 17:38:23 + Updated from global requirements e935333 2015-03-05 04:57:34 + Updated from global requirements ebc86a7 2015-02-20 13:59:09 + Updated from global requirements 6c1ee2e 2015-02-19 06:00:29 + Additional doc clean up 1613013 2015-02-16 13:57:51 -0500 cleanup documentation Diffstat (except docs and test files) - README.rst | 21 ++-- etc/pycadf/trove_api_audit_map.conf| 23 requirements.txt | 10 +- test-requirements.txt | 6 +- 24 files changed, 458 insertions(+), 444 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index af6ce08..a446088 100644 --- a/requirements.txt +++ b/requirements.txt @@ -5,4 +5,4 @@ Babel=1.3 -oslo.config=1.6.0 # Apache-2.0 -oslo.context=0.1.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.serialization=1.2.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 +oslo.context=0.2.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 @@ -10 +10 @@ pytz=2013.6 -six=1.7.0 +six=1.9.0 diff --git a/test-requirements.txt b/test-requirements.txt index f68f957..a5cc83d 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11,2 +11,2 @@ mock=1.0 -oslo.messaging=1.6.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 +oslo.messaging=1.8.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -18 +18 @@ testtools=0.9.36,!=1.2.0 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.policy release 0.4.0 (liberty)
We are tickled pink to announce the release of: oslo.policy 0.4.0: Oslo Policy library For more details, please see the git log history below and: http://launchpad.net/oslo.policy/+milestone/0.4.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.policy Changes in oslo.policy 0.3.1..0.4.0 --- cf8b445 2015-04-16 18:07:06 + Uncap library requirements for liberty 9cbfab6 2015-04-14 13:40:48 +0200 Fix invalid indentation in _load_policy_file method 3beba6b 2015-04-04 02:33:28 -0400 Cleanup README.rst and setup.cfg b5f07df 2015-03-31 22:25:00 -0400 Avoid reloading policy files in policy.d for every call a08bc79 2015-03-31 13:35:13 -0400 Lists for Generic Checks b3fe254 2015-03-21 00:17:05 + Updated from global requirements Diffstat (except docs and test files) - README.rst | 3 +- oslo_policy/_checks.py | 49 --- oslo_policy/policy.py | 43 +++--- requirements.txt | 6 +- setup.cfg | 2 +- test-requirements.txt | 4 +- 9 files changed, 349 insertions(+), 28 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index d21ad4b..1d780b2 100644 --- a/requirements.txt +++ b/requirements.txt @@ -5,3 +5,3 @@ -oslo.config=1.9.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.serialization=1.2.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index d921e2b..55b42c2 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -6 +6 @@ hacking=0.10.0,0.11 -oslotest=1.2.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -9 +9 @@ oslotest=1.2.0 # Apache-2.0 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] taskflow release 0.9.0 (liberty)
We are psyched to announce the release of: taskflow 0.9.0: Taskflow structured state management library. For more details, please see the git log history below and: http://launchpad.net/taskflow/+milestone/0.9.0 Please report issues through launchpad: http://bugs.launchpad.net/taskflow/ Changes in taskflow 0.8.1..0.9.0 c76ee25 2015-04-18 14:44:24 + Validate correct exception subclass in 'raise_with_cause' 18d3cd1 2015-04-17 21:05:21 -0700 Remove link to kazoo eventlet handler 672e1f4 2015-04-16 16:29:49 -0700 Add states generating venv and use pydot2 50eb387 2015-04-16 12:08:30 -0700 Add strict job state transition checking 0a94d68 2015-04-16 18:15:17 + Uncap library requirements for liberty 018dbf6 2015-04-15 16:10:33 -0700 Have reset state handlers go through a shared list 0eee98d 2015-04-15 15:43:08 -0700 Add job states in docs + states in python 661f3b0 2015-04-12 22:57:28 -0700 Expose r/o listener callback + details filter callback 15d73cb 2015-04-11 10:16:13 -0700 Expose listener notification type + docs d8e76fd 2015-04-10 20:25:51 -0700 Ensure listener args are always a tuple/immutable 624001a 2015-04-10 17:11:26 -0700 Include the 'dump_memory_backend' example in the docs 8910cdb 2015-04-09 15:02:06 -0700 Make resolution/retry strategies more clear and better 4ef79bc 2015-04-08 16:21:34 -0700 Rename notifier 'listeners' to 'topics' ee7f07f 2015-04-08 15:28:25 -0700 Mention link to states doc in notify state transitions 0ad2fd9 2015-04-08 15:22:46 -0700 Ensure we don't get stuck in formatting loops c64ca27 2015-04-08 14:04:38 -0700 Add note about thread safety of fake filesystem 647b69e 2015-04-05 09:46:19 -0700 Have the notification/listener docs match other sections ebc0782 2015-04-04 19:46:20 -0700 Put semantics preservation section into note block 2ad837c 2015-04-03 17:37:34 -0700 Note that the traditional mode also avoids this truncation issue 7e8981a 2015-04-03 16:11:04 -0700 Avoid going into causes of non-taskflow exceptions aa8be4b 2015-04-03 16:04:46 -0700 Use the ability to chain exceptions correctly 9cb7181 2015-04-03 17:40:28 + Add a example showing how to share an executor c553d65 2015-04-02 11:54:42 -0700 Shrink the bookshelf description 17b7c21 2015-04-01 17:12:38 -0700 Remove link about implementing job garbage binning 254d3f9 2015-04-01 14:34:30 -0700 Put the examples/misc/considerations under a new section f7d81c7 2015-04-01 13:10:49 -0700 Add a suspension engine section ce7b1d2 2015-03-31 11:43:55 -0700 Allow ls() to list recursively (using breadth-first) 1714cca 2015-03-30 14:55:05 -0700 Turn 'check_who' into a decorator bb0af4f 2015-03-30 13:05:43 -0700 Use 'node' terminology instead of 'item' terminology de68bc2 2015-03-29 22:59:04 -0700 Allow providing a node stringify function to tree pformat f11579b 2015-03-29 22:53:47 -0700 Add in memory filesystem clearing d33b316 2015-03-29 22:48:42 -0700 Just unify having a single requirements.txt file 30c7c0c 2015-03-25 21:59:27 -0700 Add memory backend get() support Diffstat (except docs and test files) - requirements-py2.txt | 36 - requirements-py3.txt | 30 requirements.txt | 36 + taskflow/engines/action_engine/analyzer.py | 6 +- taskflow/engines/action_engine/completer.py| 131 taskflow/engines/action_engine/runtime.py | 33 +++-- taskflow/engines/worker_based/protocol.py | 32 ++-- taskflow/examples/dump_memory_backend.py | 7 +- taskflow/examples/share_engine_thread.py | 81 ++ taskflow/exceptions.py | 16 +- taskflow/jobs/backends/impl_zookeeper.py | 164 + taskflow/patterns/graph_flow.py| 91 ++-- taskflow/persistence/backends/impl_dir.py | 8 +- taskflow/persistence/backends/impl_memory.py | 61 +++- taskflow/persistence/backends/impl_sqlalchemy.py | 74 ++ taskflow/persistence/backends/impl_zookeeper.py| 32 ++-- taskflow/states.py | 33 - .../unit/persistence/test_memory_persistence.py| 40 + taskflow/types/notifier.py | 81 ++ taskflow/types/tree.py | 17 ++- test-requirements.txt | 4 +- tools/generate_states.sh | 36 - tools/state_graph.py | 18 ++- tools/update_states.sh | 40 + tox.ini| 18 ++- 38 files changed, 982 insertions(+), 408 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt new file mode 100644 index 000..8e0c5f3 --- /dev/null +++ b/requirements.txt @@ -0,0 +1,36 @@ +#
[openstack-dev] [release] python-saharaclient release 0.9.0 (liberty)
We are tickled pink to announce the release of: python-saharaclient 0.9.0: Client library for Sahara API For more details, please see the git log history below. Changes in python-saharaclient 0.7.7..0.9.0 --- b909f04 2015-04-16 18:13:39 + Uncap library requirements for liberty 0d8e838 2015-04-14 10:31:14 +0300 Add regions support to saharaclient 67e3d66 2015-04-14 10:24:02 +0300 Provide user-agent in saharaclient 513387d 2015-04-07 10:20:27 + Add CONTRIBUTING.rst 5e8b889 2015-04-07 10:23:24 +0200 Port to Python 3 67b4e76 2015-04-02 11:04:56 +0900 add --name option to assign name to job-binary-internal 2141b6a 2015-03-27 16:17:04 +1100 Rework authentication fb9cf4e 2015-03-26 15:24:36 -0400 Add support for job-types-list b0511a8 2015-03-26 12:44:48 +0100 Add post_test_hook for functional tests 86dd3d4 2015-03-24 16:15:13 +0100 Copy functional tests from tempest CLI 0a00e75 2015-03-21 00:18:02 + Updated from global requirements f7f1e22 2015-03-20 12:36:06 +0300 Add support for show_events parameter 6b1c801 2015-03-03 16:47:42 +0300 Added support of instance locality Diffstat (except docs and test files) - CONTRIBUTING.rst | 21 +++ requirements.txt | 8 +- saharaclient/api/base.py | 14 +- saharaclient/api/client.py | 181 +++-- saharaclient/api/clusters.py | 10 +- saharaclient/api/events.py | 31 saharaclient/api/httpclient.py | 54 -- saharaclient/api/images.py | 8 +- saharaclient/api/job_binary_internals.py | 5 +- saharaclient/api/job_types.py | 28 saharaclient/api/node_group_templates.py | 18 +- saharaclient/api/plugins.py| 2 +- saharaclient/api/shell.py | 93 +++ saharaclient/shell.py | 22 +-- setup.cfg | 3 + test-requirements.txt | 12 +- tox.ini| 6 + 25 files changed, 596 insertions(+), 304 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 46eb375..3fa675b 100644 --- a/requirements.txt +++ b/requirements.txt @@ -9,3 +9,3 @@ netaddr=0.7.12 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 -python-keystoneclient=1.0.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 +python-keystoneclient=1.1.0 @@ -13 +13 @@ requests=2.2.0,!=2.4.0 -six=1.7.0 +six=1.9.0 diff --git a/test-requirements.txt b/test-requirements.txt index ac3a773..118a5cc 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10,4 +10,4 @@ mock=1.0 -oslo.config=1.6.0 # Apache-2.0 -oslosphinx=2.2.0 # Apache-2.0 -python-neutronclient=2.3.6,3 -python-novaclient=2.18.0 +oslo.config=1.9.3 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +python-neutronclient=2.3.11,3 +python-novaclient=2.22.0 @@ -15 +15 @@ python-swiftclient=2.2.0 -requests-mock=0.5.1 # Apache-2.0 +requests-mock=0.6.0 # Apache-2.0 @@ -17 +17 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -tempest-lib=0.2.0 +tempest-lib=0.4.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side
On Tue, Apr 21, 2015 at 1:27 PM, Chris Friesen chris.frie...@windriver.com wrote: On 04/21/2015 11:35 AM, Hayes, Graham wrote: From: Jay Pipes [jaypi...@gmail.com] The existing --os-compute-api-version CLI option should be made to take: * 2 * \d+.\d+ * latest And nothing else. Yes - please don't add a flag to the cli (or the python bindings for that matter) Isn't a cli flag exactly what Jay was describing? It is, it already exists, it just needs to be made to properly recognize the required version strings, which is what Jay was suggesting. This should be done via discovery. If a call requires a micro-version that is not deployed - return an error. I haven't had the pleasure(?) of needing to do this, but wouldn't you need to know what API versions are available before you try to do some task? (In order to know what actions are available, or what parameters to expect to be returned.) When a user needs to know much more about the API than this is the one that does Whiz-Bang Feature that I want then we've failed. Also, many users aren't probably going to care about API microversions, more likely to care that GWclient 2.1.2 is the version they need to use Whiz-Bang since that's what they'll have control over. As I understand it, Jay's proposal is that if you don't specify a version you get the default (currently version 2, I think), if you do specify a version you get that version, and if you specify latest then you get the most recent version that the server knows about. The way we've been headed in other discovery implementations is to negotiate the highest compatible version between the client and server unless a specific version requested. What happens in the client will of course be client-specific, but as a user I would hope that it either makes a best effort to fail gracefully or make a lot of noise that includes a clue as to why it failed. dt -- Dean Troyer dtro...@gmail.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][lbaas] adding lbaas core
I want to be friends with Phil :(. Congrats! Cheers, --Jorge On 4/21/15, 11:57 AM, Brandon Logan brandon.lo...@rackspace.com wrote: Welcome Phil! From: Doug Wiegley doug...@parksidesoftware.com Sent: Tuesday, April 21, 2015 11:54 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][lbaas] adding lbaas core It¹s been a week, welcome Phil. Thanks, doug On Apr 13, 2015, at 2:39 PM, Doug Wiegley doug...@parksidesoftware.com wrote: Hi all, I'd like to nominate Philip Toohill as a neutron-lbaas core. Good guy, did a bunch of work on the ref impl for lbaasv2, and and I'll let the numbers[1] speak for themselves. Existing lbaas cores, please vote. All three of us. :-) [1] http://stackalytics.com/report/contribution/neutron-lbaas/30 Thanks, doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] lp release 1.3.0 (liberty)
We are glad to announce the release of: django_openstack_auth 1.3.0: Django authentication backend for use with OpenStack Identity For more details, please see the git log history below and: https://launchpad.net/django-openstack-auth/+milestone/1.3.0 Please report issues through launchpad: https://bugs.launchpad.net/django-openstack-auth Changes in django_openstack_auth 1.2.0..1.3.0 - 3a8d34f 2015-04-21 14:51:17 + Update README to work with release tools 03446e8 2015-04-20 06:03:10 + Imported Translations from Transifex 8657c04 2015-04-19 06:02:29 + Imported Translations from Transifex 866471a 2015-04-17 06:03:00 + Imported Translations from Transifex 1786833 2015-04-16 17:50:31 + Uncap library requirements for liberty Diffstat (except docs and test files) - README.rst| 9 + openstack_auth/locale/ar/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ca/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/cs/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/de/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/en_AU/LC_MESSAGES/django.po | 12 +++- openstack_auth/locale/en_GB/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/es/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/es_MX/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fi_FI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fr/LC_MESSAGES/django.po| 9 + openstack_auth/locale/hi/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/it/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ko_KR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/ne/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/nl_NL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pa_IN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pl_PL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pt/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/pt_BR/LC_MESSAGES/django.po | 18 ++ openstack_auth/locale/ru/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/sl_SI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/sr/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/tr_TR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/uk/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/zh_CN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/zh_TW/LC_MESSAGES/django.po | 6 +++--- requirements.txt | 2 +- test-requirements.txt | 2 +- 29 files changed, 98 insertions(+), 92 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 8116201..bdbd4b5 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ Django=1.4.2,1.8 -oslo.config=1.9.3,1.10.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index c8c6a3b..58cab54 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] (no release 1.3.0 (liberty)
We are stoked to announce the release of: django_openstack_auth 1.3.0: Django authentication backend for use with OpenStack Identity For more details, please see the git log history below and: https://launchpad.net/django-openstack-auth/+milestone/1.3.0 Please report issues through launchpad: https://bugs.launchpad.net/django-openstack-auth Changes in django_openstack_auth 1.2.0..1.3.0 - 3a8d34f 2015-04-21 14:51:17 + Update README to work with release tools 03446e8 2015-04-20 06:03:10 + Imported Translations from Transifex 8657c04 2015-04-19 06:02:29 + Imported Translations from Transifex 866471a 2015-04-17 06:03:00 + Imported Translations from Transifex 1786833 2015-04-16 17:50:31 + Uncap library requirements for liberty Diffstat (except docs and test files) - README.rst| 9 + openstack_auth/locale/ar/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ca/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/cs/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/de/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/en_AU/LC_MESSAGES/django.po | 12 +++- openstack_auth/locale/en_GB/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/es/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/es_MX/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fi_FI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fr/LC_MESSAGES/django.po| 9 + openstack_auth/locale/hi/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/it/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ko_KR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/ne/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/nl_NL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pa_IN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pl_PL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pt/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/pt_BR/LC_MESSAGES/django.po | 18 ++ openstack_auth/locale/ru/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/sl_SI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/sr/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/tr_TR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/uk/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/zh_CN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/zh_TW/LC_MESSAGES/django.po | 6 +++--- requirements.txt | 2 +- test-requirements.txt | 2 +- 29 files changed, 98 insertions(+), 92 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 8116201..bdbd4b5 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ Django=1.4.2,1.8 -oslo.config=1.9.3,1.10.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index c8c6a3b..58cab54 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] taskflow release 0.6.0 (liberty)
We are satisfied to announce the release of: taskflow 0.6.0: Taskflow structured state management library. For more details, please see the git log history below and: http://launchpad.net/taskflow/+milestone/0.6.0 Please report issues through launchpad: http://bugs.launchpad.net/taskflow/ Changes in taskflow 0.5.0..0.6.0 4e514f4 2014-12-18 13:55:41 -0800 Move over to using oslo.utils [reflection, uuidutils] e5ae74d 2014-12-18 01:28:41 + Updated from global requirements 6520b9c 2014-12-17 19:13:45 + Add a basic map/reduce example to show how this can be done cafa3b2 2014-12-17 19:13:35 + Add a parallel table mutation example 1b06183 2014-12-15 19:19:18 -0800 Add a 'can_be_registered' method that checks before notifying 97b4e18 2014-12-15 15:52:39 -0800 Base task executor should provide 'wait_for_any' e9ecdc7 2014-12-14 21:46:51 -0800 Replace autobind with a notifier module helper function aa8d55d 2014-12-15 03:38:52 + Cleanup some doc warnings/bad/broken links 1f4dd72 2014-12-13 19:09:03 -0800 Use the notifier type in the task class/module directly cdfd8ec 2014-12-13 17:13:07 -0800 Use a tiny clamp helper to clamp the 'on_progress' value 624d966 2014-12-12 22:12:03 -0800 Retain the existence of a 'EngineBase' until 0.7 or later f5060ff 2014-12-12 22:05:03 -0800 Remove the base postfix from the internal task executor b4e4e21 2014-12-12 20:52:58 + Remove usage of listener base postfix a440ec4 2014-12-12 12:39:57 -0800 Add a moved_inheritable_class deprecation helper 1c7d242 2014-12-11 13:15:19 -0800 Avoid holding the lock while scanning for existing jobs 79ff9e7 2014-12-10 23:25:08 -0800 Remove the base postfix for engine abstract base class 880f7d2 2014-12-10 23:21:31 -0800 Avoid popping while another entity is iterating a908124 2014-12-11 07:20:45 + Updated from global requirements fda6fde 2014-12-11 04:10:16 + Use explict 'attr_dict' when adding provider-consumer edge eaf4995 2014-12-10 20:05:44 -0800 Properly handle and skip empty intermediary flows f1457a0 2014-12-10 18:58:42 -0800 Ensure message gets processed correctly b275c51 2014-12-09 15:52:14 -0800 Just assign a empty collection instead of copy/clear f333e1b 2014-12-09 00:15:34 -0800 Remove rtype from task clone() doc 14431bc 2014-12-08 22:09:13 -0800 Add and use a new simple helper logging module a113368 2014-12-08 16:51:27 -0800 Have the sphinx copyright date be dynamic 2f78ecf 2014-12-08 14:27:53 -0800 Add appropriate links into README.rst 4eb0ca2 2014-12-08 01:21:15 + Use condition variables using 'with' 50b866c 2014-12-07 18:52:54 + Use an appropriate ``extract_traceback`` limit c4d3279 2014-12-07 09:42:17 -0800 Allow all deprecation helpers to take a stacklevel cd664bd 2014-12-07 00:25:01 -0800 Correctly identify stack level in ``_extract_engine`` 5f0b514 2014-12-06 15:03:58 -0800 Stop returning atoms from execute/revert methods dc4262e 2014-12-06 14:46:09 -0800 Have tasks be able to provide copy() methods e978eca 2014-12-06 22:30:14 + Allow stopwatches to be restarted af62f4c 2014-12-06 22:30:10 + Ensure that failures can be pickled e168f44 2014-12-06 14:29:24 -0800 Rework pieces of the task callback capability dc39351 2014-12-05 21:12:03 -0800 Just use 4 spaces for classifier indents 4707ac7 2014-12-05 00:13:15 -0800 Move atom action handlers to there own subfolder/submodule 2033d01 2014-12-05 03:30:41 + Workflow documentation is now in infra-manual 2f03736 2014-12-05 01:53:47 + Ensure frozen attribute is set in fsm clones/copies 8150553 2014-12-04 16:59:54 -0800 Fix split on + for connection strings that specify dialects b8e975e 2014-12-04 19:04:14 + Update listeners to ensure they correctly handle all atoms cf45a70 2014-12-04 11:03:36 -0800 Allow for the notifier to provide a 'details_filter' c698842 2014-12-04 08:05:09 + Be explicit about publish keyword arguments 6a6aa79 2014-12-03 16:15:05 -0800 Some package additions and adjustments to the env_builder.sh a692138 2014-12-02 16:02:24 -0800 Cache immutable visible scopes in the runtime component 14ecaa4 2014-12-02 12:47:03 -0800 Raise value errors instead of asserts 1de8bbd 2014-12-01 21:39:23 -0800 Add a claims listener that connects job claims to engines 1e8fabd 2014-12-01 19:26:20 -0800 Split the scheduler into sub-schedulers 35fcd90 2014-12-01 18:15:02 -0800 Use a module level constant to provide the DEFAULT_LISTEN_FOR 178f279 2014-12-02 01:57:37 + Move the _pformat() method to be a classmethod 9675964 2014-11-28 15:10:31 -0800 Add link to issue 17911 e07fb21 2014-11-28 15:07:20 -0800 Avoid deepcopying exception values 95e94f7 2014-11-28 13:07:38 -0800 Include documentation of the utility modules 265181f 2014-11-27 20:07:21 -0800 Use a metaclass to dynamically add testcases to example runner cf85dd0 2014-11-25 09:57:16 -0800 Remove default setting of 'mysql_traditional_mode' bb8ea56 2014-11-24 18:13:56 -0800 Move scheduler and completer
[openstack-dev] [release] oslo.config release 1.11.0 (liberty)
We are psyched to announce the release of: oslo.config 1.11.0: Oslo Configuration API For more details, please see the git log history below and: http://launchpad.net/oslo.config/+milestone/1.11.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.config Changes in oslo.config 1.10.0..1.11.0 - 2e32e58 2015-04-16 17:56:05 + Uncap library requirements for liberty Diffstat (except docs and test files) - requirements.txt | 2 +- test-requirements.txt | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index f560a0e..3e21533 100644 --- a/requirements.txt +++ b/requirements.txt @@ -9 +9 @@ six=1.9.0 -stevedore=1.3.0,1.4.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index a23ab6e..27f6050 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -13 +13 @@ testtools=0.9.36,!=1.2.0 -oslotest=1.5.1,1.6.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -22 +22 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -25 +25 @@ oslosphinx=2.5.0,2.6.0 # Apache-2.0 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.messaging release 1.9.0 (liberty)
We are happy to announce the release of: oslo.messaging 1.10.0: Oslo Messaging API For more details, please see the git log history below and: http://launchpad.net/oslo.messaging/+milestone/1.10.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.messaging Changes in oslo.messaging 1.9.0..1.10.0 --- 9dd8441 Uncap library requirements for liberty 72c5014 Use unittest.mock on Python 3 a00d075 Enable redis test dependency on Python 3 9ef3fa8 Remove amqp driver 'unpacked content' logging ef3575d Updated from global requirements 4decea1 Add pypi download + version badges 48441a6 Fix TypeError caused by err_msg formatting 6a83bfb Fix typo in oslo_messaging/_drivers/protocols/amqp/opts.py d214770 Document notification_driver possible values 07c3e8b Do not skip functional test for amqp driver 5ec72e8 Add functional test for notify.logger 6f4e32a Properly deserialize received AMQP 1.0 messages fb8c431 Make notify driver messaging play well with publish_errors c244126 Imported Translations from Transifex 49c6d9c Sync with latest oslo-incubator f033fc9 Don't raise Timeout on no-matchmaker results Diffstat (except docs and test files) - README.rst | 8 +++ .../locale/en_GB/LC_MESSAGES/oslo.messaging.po | 22 +++--- oslo_messaging/_drivers/amqp.py| 6 +- oslo_messaging/_drivers/impl_rabbit.py | 2 +- oslo_messaging/_drivers/impl_zmq.py| 9 ++- oslo_messaging/_drivers/protocols/amqp/driver.py | 3 +- oslo_messaging/_drivers/protocols/amqp/opts.py | 2 +- oslo_messaging/notify/log_handler.py | 3 +- oslo_messaging/notify/logger.py| 34 - oslo_messaging/notify/notifier.py | 4 +- oslo_messaging/openstack/common/versionutils.py| 13 +++- requirements-py3.txt | 14 ++-- requirements.txt | 14 ++-- test-requirements-py3.txt | 8 ++- test-requirements.txt | 6 +- 46 files changed, 273 insertions(+), 99 deletions(-) Requirements updates diff --git a/requirements-py3.txt b/requirements-py3.txt index 4ec18c6..a37a824 100644 --- a/requirements-py3.txt +++ b/requirements-py3.txt @@ -5,6 +5,6 @@ -oslo.config=1.9.3,1.10.0 # Apache-2.0 -oslo.context=0.2.0,0.3.0 # Apache-2.0 -oslo.serialization=1.4.0,1.5.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 -stevedore=1.3.0,1.4.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 +oslo.context=0.2.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 @@ -22 +22 @@ kombu=2.5.0 -oslo.middleware=1.0.0,1.1.0 # Apache-2.0 +oslo.middleware=1.0.0 # Apache-2.0 diff --git a/requirements.txt b/requirements.txt index ec5fef6..aaf7390 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7,6 +7,6 @@ pbr=0.6,!=0.7,1.0 -oslo.config=1.9.3,1.10.0 # Apache-2.0 -oslo.context=0.2.0,0.3.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 -oslo.serialization=1.4.0,1.5.0 # Apache-2.0 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 -stevedore=1.3.0,1.4.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 +oslo.context=0.2.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 @@ -29 +29 @@ kombu=2.5.0 -oslo.middleware=1.0.0,1.1.0 # Apache-2.0 +oslo.middleware=1.0.0 # Apache-2.0 diff --git a/test-requirements-py3.txt b/test-requirements-py3.txt index f137195..22b4c4e 100644 --- a/test-requirements-py3.txt +++ b/test-requirements-py3.txt @@ -10 +9,0 @@ fixtures=0.3.14 -mock=1.0 @@ -16 +15,4 @@ testtools=0.9.36,!=1.2.0 -oslotest=1.5.1,1.6.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 + +# for test_matchmaker_redis +redis=2.10.0 @@ -25 +27 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 5afaa74..c962f4a 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -16 +16 @@ testtools=0.9.36,!=1.2.0 -oslotest=1.5.1,1.6.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -25 +25 @@ redis=2.10.0 -pyzmq=14.3.1 +pyzmq=14.3.1 # LGPL+BSD @@ -34 +34 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:
[openstack-dev] [release] python-barbicanclient release 3.1.0 (liberty)
We are amped to announce the release of: python-barbicanclient 3.1.0: Client Library for OpenStack Barbican Key Management API For more details, please see the git log history below. Changes in python-barbicanclient 3.0.3..3.1.0 - e24ed33 2015-04-20 13:58:33 -0500 Excluding tests from coverage report 137a893 2015-04-17 10:24:26 -0500 Fix the clientrc file to match defaults and add docs f2ddf1e 2015-04-16 17:36:59 -0500 Updating client and client docs for accuracy c1fd9d4 2015-04-16 16:13:41 -0500 Porting over more documentation to RST from cli wiki 538daa3 2015-04-16 18:12:46 + Uncap library requirements for liberty 840a98c 2015-04-15 15:38:27 -0500 Adding payload flag to get secret e06df05 2015-04-15 14:20:56 -0500 Raising errors from the client instead of ksclient bbd14af 2015-04-10 11:43:21 +0200 Fix order listing on the command line. f0fe464 2015-04-08 19:02:22 -0500 Fixing the broken functional tests 54a52ae 2015-04-02 08:32:23 +1100 Use the ksc Adapter instead of custom HTTPClient 7c0a1d7 2015-03-26 15:47:11 -0500 Negative tests for orders Diffstat (except docs and test files) - .coveragerc| 2 +- barbicanclient/barbican_cli/orders.py | 6 +- barbicanclient/barbican_cli/secrets.py | 14 +- barbicanclient/base.py | 2 +- barbicanclient/client.py | 130 +- barbicanclient/containers.py | 37 +++- barbicanclient/exceptions.py | 28 +++ barbicanclient/orders.py | 55 -- barbicanclient/secrets.py | 35 ++-- clientrc | 25 ++- .../client/v1/functional/test_containers.py| 47 +++-- .../client/v1/functional/test_orders.py| 196 + .../client/v1/functional/test_secrets.py | 81 ++--- requirements.txt | 8 +- test-requirements.txt | 4 +- 20 files changed, 770 insertions(+), 217 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index b125e91..187135f 100644 --- a/requirements.txt +++ b/requirements.txt @@ -9,4 +9,4 @@ python-keystoneclient=1.1.0 -cliff=1.10.0,1.11.0 # Apache-2.0 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 -oslo.serialization=1.4.0,1.5.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +cliff=1.10.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 684cef9..036e2f9 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -12 +12 @@ testtools=0.9.36,!=1.2.0 -oslotest=1.5.1,1.6.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -17 +17 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-ironicclient release 0.6.0 (liberty)
We are psyched to announce the release of: python-ironicclient 0.6.0: OpenStack Bare Metal Provisioning API Client Library For more details, please see the git log history below. Changes in python-ironicclient 0.5.1..0.6.0 --- 8f476f4 2015-04-21 00:10:08 + Encode exception on cli for UnicodeDecodeError 28bdd0b 2015-04-17 16:25:44 +0200 Implement and enable retries on Conflict fba8364 2015-04-16 18:13:06 + Uncap library requirements for liberty Diffstat (except docs and test files) - ironicclient/client.py | 9 +- ironicclient/common/http.py | 46 + ironicclient/shell.py| 32 +- requirements.txt | 4 +- test-requirements.txt| 2 +- 6 files changed, 265 insertions(+), 11 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index b20966d..b837718 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7,2 +7,2 @@ lxml=2.3 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index d2e45fe..57e162e 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11 +11 @@ mock=1.0 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-designateclient release 1.2.0 (liberty)
We are happy to announce the release of: python-designateclient 1.2.0: OpenStack DNS as a Service - Client For more details, please see the git log history below and: http://launchpad.net/python-designateclient/+milestone/1.2.0 Please report issues through launchpad: http://bugs.launchpad.net/python-designateclient Changes in python-designateclient 1.1.1..1.2.0 -- 39d8b54 2015-04-21 15:07:07 + Update README to work with release tools ed808de 2015-04-16 18:12:56 + Uncap library requirements for liberty 94c242f 2015-03-21 00:17:31 + Updated from global requirements debf39a 2015-02-24 12:44:24 +0530 Added extra previllege to list all domains from all tenants 4118d0f 2015-02-20 13:59:17 + Updated from global requirements ab3ed69 2015-02-13 02:00:03 + Updated from global requirements e0e428a 2015-01-29 15:07:09 +0100 Fix if checking on ttl for Create/Update commands 92b5872 2015-01-26 10:34:00 + Updated from global requirements e20b1d3 2014-12-05 03:30:39 + Workflow documentation is now in infra-manual Diffstat (except docs and test files) - README.rst | 17 + designateclient/cli/domains.py | 4 ++-- designateclient/cli/records.py | 4 ++-- designateclient/shell.py | 4 designateclient/utils.py | 3 ++- designateclient/v1/__init__.py | 5 - requirements.txt | 8 8 files changed, 36 insertions(+), 11 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 82387a7..2ced90a 100644 --- a/requirements.txt +++ b/requirements.txt @@ -4 +4 @@ -cliff=1.7.0 # Apache-2.0 +cliff=1.10.0 # Apache-2.0 @@ -7 +7 @@ pbr=0.6,!=0.7,1.0 -python-keystoneclient=0.11.1 +python-keystoneclient=1.1.0 @@ -9,2 +9,2 @@ requests=2.2.0,!=2.4.0 -six=1.7.0 -stevedore=1.1.0 # Apache-2.0 +six=1.9.0 +stevedore=1.3.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][lbaas] adding lbaas core
Congrats Phil !! Thanks, Vivek On Apr 21, 2015, at 10:16 AM, Phillip Toohill phillip.tooh...@rackspace.com wrote: Thank you! Phillip V. Toohill III Software Developer phone: 210-312-4366 mobile: 210-440-8374 From: Brandon Logan brandon.lo...@rackspace.com Sent: Tuesday, April 21, 2015 11:57 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][lbaas] adding lbaas core Welcome Phil! From: Doug Wiegley doug...@parksidesoftware.com Sent: Tuesday, April 21, 2015 11:54 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][lbaas] adding lbaas core It’s been a week, welcome Phil. Thanks, doug On Apr 13, 2015, at 2:39 PM, Doug Wiegley doug...@parksidesoftware.com wrote: Hi all, I'd like to nominate Philip Toohill as a neutron-lbaas core. Good guy, did a bunch of work on the ref impl for lbaasv2, and and I'll let the numbers[1] speak for themselves. Existing lbaas cores, please vote. All three of us. :-) [1] http://stackalytics.com/report/contribution/neutron-lbaas/30 Thanks, doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [keystone] keystonemiddleware stable/juno broken
On Tue, Apr 21, 2015 at 12:10 PM, gordon chung g...@live.ca wrote: __ Date: Tue, 21 Apr 2015 11:12:12 -0500 From: b...@acm.org To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [keystone] keystonemiddleware stable/juno broken On Sun, Apr 19, 2015 at 2:21 PM, Brant Knudson b...@acm.orgmailto:b...@acm.org wrote: Ever since the stable/juno branch was created for keystonemiddleware it's been broken and there are several changes piling up there. The fix for bug 1408838 Tests fail with new oslo.utils 1.2.1 allows the tests to pass. I cherry-picked the fix here[1]. Based on the title of the bug, you'd think that capping oslo.utils1.2.1 would be an alternative fix, but I tried installing older versions of oslo.utils and eventually it failed with a completely different error, so I think that's a dead end. [1] https://review.openstack.org/#/c/175232/ So this fix has merged, but keystonemiddleware has another problem -- the proposal bot posted a change to get the requirements up to date and that's failing all the -python* jobs. Looks like what's happening is that during the tox venv installation the oslo.messaging package is being updated to version 1.9.0, which is way newer than the other oslo packages and this is causing a test that uses pkg_resource to fail with a dependency issue (oslo.messaging 1.9.0 requires oslo.utils1.5.0,1.4.0 but global requirements has oslo.utils1.2.0, so that's what's installed). This all appears to be related to other issues we've seen where the dep resolver isn't working as expected. I tried using an older pycadf (which, from the tox logs is where oslo.messaging is being upgraded) but it was only with a very old version of pycadf that things worked. does it make sense to make a stable/juno branch for pycadf and remove the oslo.messaging requirement? it actually isn't a mandatory requirement and was moved to test-requirements in 0.7.0 Gordon - I think that would also work... if I have some time I'll take a look at it, or maybe someone else will get to it first. :: Brant __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.serialization release 1.1.0 (liberty)
We are amped to announce the release of: oslo.serialization 1.1.0: oslo.serialization library For more details, please see the git log history below and: http://launchpad.net/oslo/+milestone/1.1.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo Changes in oslo.serialization 0.3.0..1.1.0 -- a7bade1 2014-10-24 09:29:18 -0400 Add pbr to installation requirements 9701670 2014-10-22 19:16:47 + Updated from global requirements f3aa93c 2014-10-08 22:25:56 +0100 Fix pep8, docs, requirements issues in jsonutils and tests d4e3609 2014-10-08 22:50:04 +0200 Remove extraneous vim editor configuration comments ce89925 2014-10-02 16:18:01 -0400 Support building wheels (PEP-427) 472e6c9 2014-10-01 16:47:57 +0200 Fix coverage testing ddde5a5 2014-09-19 08:51:05 + Updated from global requirements 0929bde 2014-09-15 10:11:55 +0100 Support 'built-in' datetime module 9498865 2014-09-10 09:54:05 -0400 Add history/changelog to docs Diffstat (except docs and test files) - oslo/__init__.py| 2 -- oslo/serialization/jsonutils.py | 20 +++- requirements.txt| 4 +++- setup.cfg | 3 +++ test-requirements.txt | 11 ++- 8 files changed, 27 insertions(+), 20 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 2dc5dea..176ce3c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -3,0 +4,2 @@ + +pbr=0.6,!=0.7,1.0 @@ -9 +11 @@ iso8601=0.1.9 -oslo.utils=0.3.0 # Apache-2.0 +oslo.utils=1.0.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index a0ed1c5..f4c82b9 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -4 +4 @@ -hacking=0.5.6,0.8 +hacking=0.9.2,0.10 @@ -9,2 +9,2 @@ netaddr=0.7.12 -sphinx=1.1.2,!=1.2.0,1.3 -oslosphinx=2.2.0.0a2 +sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 +oslosphinx=2.2.0 # Apache-2.0 @@ -12 +12 @@ oslosphinx=2.2.0.0a2 -oslotest=1.1.0.0a2 +oslotest=1.2.0 # Apache-2.0 @@ -14 +14,2 @@ simplejson=2.2.0 -oslo.i18n=0.3.0 # Apache-2.0 +oslo.i18n=1.0.0 # Apache-2.0 +coverage=3.6 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.vmware release 0.8.0 (liberty)
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.policy release 0.2.0 (liberty)
We are eager to announce the release of: oslo.middleware 0.2.0: Oslo Middleware library For more details, please see the git log history below and: http://launchpad.net/oslo/+milestone/0.2.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo Changes in oslo.middleware 0.1.0..0.2.0 --- 7baf57a 2014-11-20 14:11:31 + Updated from global requirements 6f88759 2014-11-18 11:36:19 + Updated from global requirements f9d0b94 2014-11-17 18:47:25 -0500 Flesh out the README edfa12c 2014-11-12 06:01:14 + Imported Translations from Transifex 5fd894b 2014-11-05 08:35:00 + Updated from global requirements 28b8ad2 2014-10-24 09:28:41 -0400 Add pbr to installation requirements b49d38c 2014-10-22 19:16:44 + Updated from global requirements 2f53838 2014-10-11 15:56:09 + Updated from global requirements afb541d 2014-10-08 22:49:07 +0200 Remove extraneous vim editor configuration comments c32959f 2014-10-03 06:07:24 + Imported Translations from Transifex 9ccefd8 2014-10-02 16:18:01 -0400 Support building wheels (PEP-427) 72836d0 2014-10-01 16:50:40 +0200 Fix coverage testing 7ee3b0f 2014-10-01 08:16:10 -0400 Expose sizelimit option to config generator 7846039 2014-09-30 06:39:25 + Imported Translations from Transifex e18de4a 2014-09-26 06:00:56 + Imported Translations from Transifex 7874cf9 2014-09-19 08:51:01 + Updated from global requirements d7bdf52 2014-09-18 06:04:53 + Imported Translations from Transifex 3679023 2014-09-16 18:30:18 +0200 Remove oslo-incubator fixture Diffstat (except docs and test files) - README.rst | 5 +- openstack-common.conf | 1 - .../de/LC_MESSAGES/oslo.middleware-log-error.po| 27 +++ .../locale/de/LC_MESSAGES/oslo.middleware.po | 27 +++ .../en_GB/LC_MESSAGES/oslo.middleware-log-error.po | 27 +++ .../locale/en_GB/LC_MESSAGES/oslo.middleware.po| 27 +++ .../fr/LC_MESSAGES/oslo.middleware-log-error.po| 27 +++ .../locale/fr/LC_MESSAGES/oslo.middleware.po | 27 +++ .../locale/oslo.middleware-log-critical.pot| 20 + .../locale/oslo.middleware-log-error.pot | 25 +++ .../locale/oslo.middleware-log-info.pot| 20 + .../locale/oslo.middleware-log-warning.pot | 20 + oslo/__init__.py | 2 - .../openstack/common/fixture/__init__.py | 0 oslo/middleware/openstack/common/fixture/config.py | 85 -- oslo/middleware/opts.py| 45 oslo/middleware/sizelimit.py | 30 +--- requirements.txt | 5 +- setup.cfg | 9 ++- test-requirements.txt | 9 ++- 21 files changed, 334 insertions(+), 109 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 414bdf6..275fa4f 100644 --- a/requirements.txt +++ b/requirements.txt @@ -4,0 +5 @@ +pbr=0.6,!=0.7,1.0 @@ -6,2 +7,2 @@ Babel=1.3 -oslo.config=1.4.0.0a3 -oslo.i18n=0.3.0 # Apache-2.0 +oslo.config=1.4.0 # Apache-2.0 +oslo.i18n=1.0.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 506a33d..c5c0328 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -8,4 +8,5 @@ mock=1.0 -oslosphinx=2.2.0.0a2 -oslotest=1.1.0.0a2 -sphinx=1.1.2,!=1.2.0,1.3 -testtools=0.9.34 +oslosphinx=2.2.0 # Apache-2.0 +oslotest=1.2.0 # Apache-2.0 +sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 +testtools=0.9.36,!=1.2.0 +coverage=3.6 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-tooz release 0.8.0 (liberty)
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] bad release note emails
Some of the repos I was trying to generate release notes from, especially the python-fooclient repos, don't have the data in the README.rst files needed for the script to work. As a result, some of the emails are blank. I'm working on fixing that, sorry for the noise. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.db release 1.2.0 (liberty)
We are amped to announce the release of: oslo.db 1.2.0: oslo.db library For more details, please see the git log history below and: http://launchpad.net/oslo/+milestone/1.2.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo Changes in oslo.db 1.1.0..1.2.0 --- f740e3b 2014-11-28 06:01:27 + Imported Translations from Transifex ca1ad56 2014-11-21 17:05:34 +0200 Make test_models pass on py3 549ba15 2014-11-21 12:32:04 +0200 Repair include_object to accommodate new objects 10e8d15 2014-11-20 19:26:22 +0200 Add table name to foreign keys diff ddd11df 2014-11-20 14:11:24 + Updated from global requirements 2269848 2014-11-19 19:46:04 +0200 Handle Galera deadlock on SELECT FOR UPDATE 4b2058b 2014-11-19 16:02:42 +0200 Add exception filter for _sqlite_dupe_key_error b6d363d 2014-11-19 15:21:20 +0200 Add info on how to run unit tests 7f755bf 2014-11-18 16:05:01 +0200 Ensure is_backend_avail() doesn't leave open connections c54d3a9 2014-11-18 11:36:12 + Updated from global requirements 2099177 2014-11-08 12:58:23 + Add pbr to installation requirements 135701b 2014-10-27 21:21:10 -0700 Fix python3.x scoping issues with removed 'de' variable Diffstat (except docs and test files) - CONTRIBUTING.rst | 39 +++ .../locale/en_GB/LC_MESSAGES/oslo.db-log-info.po | 8 ++-- oslo.db/locale/fr/LC_MESSAGES/oslo.db-log-error.po | 56 ++ oslo.db/locale/fr/LC_MESSAGES/oslo.db-log-info.po | 33 + .../locale/fr/LC_MESSAGES/oslo.db-log-warning.po | 40 oslo/db/sqlalchemy/exc_filters.py | 21 ++-- oslo/db/sqlalchemy/session.py | 10 ++-- oslo/db/sqlalchemy/test_migrations.py | 2 +- oslo/db/sqlalchemy/utils.py| 3 +- requirements.txt | 1 + test-requirements-py2.txt | 2 +- test-requirements-py3.txt | 2 +- 15 files changed, 233 insertions(+), 35 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index cc50660..f8a0d8c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -4,0 +5 @@ +pbr=0.6,!=0.7,1.0 diff --git a/test-requirements-py2.txt b/test-requirements-py2.txt index 13cea90..ac5c18a 100644 --- a/test-requirements-py2.txt +++ b/test-requirements-py2.txt @@ -19 +19 @@ testscenarios=0.4 -testtools=0.9.36 +testtools=0.9.36,!=1.2.0 diff --git a/test-requirements-py3.txt b/test-requirements-py3.txt index 4f195da..58b9a3d 100644 --- a/test-requirements-py3.txt +++ b/test-requirements-py3.txt @@ -18 +18 @@ testscenarios=0.4 -testtools=0.9.36 +testtools=0.9.36,!=1.2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslotest release 1.6.0 (liberty)
We are stoked to announce the release of: oslotest 1.6.0: Oslo test framework For more details, please see the git log history below and: http://launchpad.net/oslotest/+milestone/1.6.0 Please report issues through launchpad: http://bugs.launchpad.net/oslotest Changes in oslotest 1.5.1..1.6.0 9116088 2015-04-16 18:09:08 + Uncap library requirements for liberty 1542d8c 2015-04-04 02:39:46 -0400 Cleanup README.rst and setup.cfg 2478170 2015-04-03 16:43:21 +0200 mockpatch: factorize code d0d6528 2015-04-03 14:13:03 + Update to latest hacking 88ea8c1 2015-03-21 00:17:19 + Updated from global requirements fd60b9c 2015-03-12 14:31:54 +0100 mockpatch: fix a potential race condition Diffstat (except docs and test files) - README.rst| 3 ++- oslotest/mockpatch.py | 47 +-- setup.cfg | 2 +- test-requirements.txt | 4 ++-- 4 files changed, 22 insertions(+), 34 deletions(-) Requirements updates diff --git a/test-requirements.txt b/test-requirements.txt index 5a845ba..d6f80b3 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -5 +5 @@ -hacking=0.9.2,0.10 +hacking=0.10.0,0.11 @@ -14 +14 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-neutronclient release 2.5.0 (liberty)
We are pumped to announce the release of: python-neutronclient 2.5.0: CLI and Client Library for OpenStack Networking For more details, please see the git log history below. Changes in python-neutronclient 2.4.0..2.5.0 2f0fc2c 2015-04-16 18:13:29 + Uncap library requirements for liberty Diffstat (except docs and test files) - requirements.txt | 8 test-requirements.txt | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 12f89a0..b7a9ee1 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ argparse -cliff=1.10.0,1.11.0 # Apache-2.0 +cliff=1.10.0 # Apache-2.0 @@ -9,3 +9,3 @@ netaddr=0.7.12 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 -oslo.serialization=1.4.0,1.5.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index b910353..1c395de 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -12,2 +12,2 @@ mock=1.0 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 -oslotest=1.5.1,1.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-glanceclient release 0.18.0 (liberty)
We are gleeful to announce the release of: python-glanceclient 0.18.0: OpenStack Image API Client Library For more details, please see the git log history below and: http://launchpad.net/python-glanceclient/+milestone/0.18.0 Please report issues through launchpad: http://bugs.launchpad.net/python-glanceclient Changes in python-glanceclient 0.17.0..0.18.0 - 8b4456a 2015-04-16 18:13:00 + Uncap library requirements for liberty 76c9f68 2015-04-14 10:00:51 +0200 Add unit tests for log_curl_request bd0aa06 2015-04-11 11:04:23 + Fix https stack trace on python 3.4 client c698b4e 2015-04-11 11:03:54 + Fix client when using no ssl compression 64a1a0f 2015-04-11 11:00:19 + Add SSL cert verification regression tests c730266 2015-04-11 00:02:22 +1200 Omit 'locations' as image-create parameter a6234d1 2015-04-02 06:15:48 + Creating task with invalid property crashes in py3 fd2f989 2015-03-28 14:22:49 +1100 Don't accept *args for client e386e44 2015-03-28 14:21:51 +1100 Stub authentication requests rather than plugins 27f70bb 2015-03-28 14:19:52 +1100 Remove keystoneclient mocks 02b1a05 2015-03-28 14:16:00 +1100 Replace mox in tests with requests-mock 90407d9 2015-03-27 19:03:48 +0300 Expose 'is_base' schema property attribute 2c08b40 2015-03-26 12:42:36 + Validate tag name when filtering for images 13b5a5a 2015-03-26 12:42:18 + Remove redundant FakeSchemaAPI __init__ method c149a94 2015-03-22 17:26:55 +0530 glance image-show now have --human-readable option 42d7548 2015-03-19 20:53:54 -0600 Test unit for checking update active images 6d864ef 2015-03-19 10:24:34 +0100 Correct help messages for image-update command f272ab3 2015-02-16 11:09:00 +1100 Generate API documentation a1bb3eb 2014-11-26 12:20:40 -0600 Use any instead of False in generator Diffstat (except docs and test files) - glanceclient/client.py| 9 ++ glanceclient/common/https.py | 11 +- glanceclient/common/utils.py | 4 +- glanceclient/v1/client.py | 4 +- glanceclient/v1/shell.py | 6 +- glanceclient/v2/client.py | 4 +- glanceclient/v2/images.py | 15 ++- glanceclient/v2/schemas.py| 21 ++- glanceclient/v2/shell.py | 9 +- glanceclient/v2/tasks.py | 2 +- requirements.txt | 8 +- test-requirements.txt | 5 +- tox.ini | 2 +- 25 files changed, 608 insertions(+), 471 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index c34e04a..7245e72 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8 +8 @@ PrettyTable=0.7,0.8 -python-keystoneclient=1.0.0 +python-keystoneclient=1.1.0 @@ -12,3 +12,3 @@ warlock=1.0.1,2 -six=1.7.0 -oslo.utils=1.2.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 +six=1.9.0 +oslo.utils=1.4.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 06cb4aa..b0e7f67 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -8 +7,0 @@ discover -mox3=0.7.0 @@ -10 +9 @@ mock=1.0 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -13,0 +13,2 @@ testtools=0.9.36,!=1.2.0 +fixtures=0.3.14 +requests-mock=0.6.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-magnumclient release 0.1.0 (liberty)
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.middleware release 0.2.0 (liberty)
We are glad to announce the release of: oslo.middleware 0.2.0: Oslo Middleware library For more details, please see the git log history below and: http://launchpad.net/oslo/+milestone/0.2.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo Changes in oslo.middleware 0.1.0..0.2.0 --- 7baf57a 2014-11-20 14:11:31 + Updated from global requirements 6f88759 2014-11-18 11:36:19 + Updated from global requirements f9d0b94 2014-11-17 18:47:25 -0500 Flesh out the README edfa12c 2014-11-12 06:01:14 + Imported Translations from Transifex 5fd894b 2014-11-05 08:35:00 + Updated from global requirements 28b8ad2 2014-10-24 09:28:41 -0400 Add pbr to installation requirements b49d38c 2014-10-22 19:16:44 + Updated from global requirements 2f53838 2014-10-11 15:56:09 + Updated from global requirements afb541d 2014-10-08 22:49:07 +0200 Remove extraneous vim editor configuration comments c32959f 2014-10-03 06:07:24 + Imported Translations from Transifex 9ccefd8 2014-10-02 16:18:01 -0400 Support building wheels (PEP-427) 72836d0 2014-10-01 16:50:40 +0200 Fix coverage testing 7ee3b0f 2014-10-01 08:16:10 -0400 Expose sizelimit option to config generator 7846039 2014-09-30 06:39:25 + Imported Translations from Transifex e18de4a 2014-09-26 06:00:56 + Imported Translations from Transifex 7874cf9 2014-09-19 08:51:01 + Updated from global requirements d7bdf52 2014-09-18 06:04:53 + Imported Translations from Transifex 3679023 2014-09-16 18:30:18 +0200 Remove oslo-incubator fixture Diffstat (except docs and test files) - README.rst | 5 +- openstack-common.conf | 1 - .../de/LC_MESSAGES/oslo.middleware-log-error.po| 27 +++ .../locale/de/LC_MESSAGES/oslo.middleware.po | 27 +++ .../en_GB/LC_MESSAGES/oslo.middleware-log-error.po | 27 +++ .../locale/en_GB/LC_MESSAGES/oslo.middleware.po| 27 +++ .../fr/LC_MESSAGES/oslo.middleware-log-error.po| 27 +++ .../locale/fr/LC_MESSAGES/oslo.middleware.po | 27 +++ .../locale/oslo.middleware-log-critical.pot| 20 + .../locale/oslo.middleware-log-error.pot | 25 +++ .../locale/oslo.middleware-log-info.pot| 20 + .../locale/oslo.middleware-log-warning.pot | 20 + oslo/__init__.py | 2 - .../openstack/common/fixture/__init__.py | 0 oslo/middleware/openstack/common/fixture/config.py | 85 -- oslo/middleware/opts.py| 45 oslo/middleware/sizelimit.py | 30 +--- requirements.txt | 5 +- setup.cfg | 9 ++- test-requirements.txt | 9 ++- 21 files changed, 334 insertions(+), 109 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 414bdf6..275fa4f 100644 --- a/requirements.txt +++ b/requirements.txt @@ -4,0 +5 @@ +pbr=0.6,!=0.7,1.0 @@ -6,2 +7,2 @@ Babel=1.3 -oslo.config=1.4.0.0a3 -oslo.i18n=0.3.0 # Apache-2.0 +oslo.config=1.4.0 # Apache-2.0 +oslo.i18n=1.0.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 506a33d..c5c0328 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -8,4 +8,5 @@ mock=1.0 -oslosphinx=2.2.0.0a2 -oslotest=1.1.0.0a2 -sphinx=1.1.2,!=1.2.0,1.3 -testtools=0.9.34 +oslosphinx=2.2.0 # Apache-2.0 +oslotest=1.2.0 # Apache-2.0 +sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 +testtools=0.9.36,!=1.2.0 +coverage=3.6 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.db release 1.2.0 (liberty)
We are tickled pink to announce the release of: oslo.db 1.2.0: oslo.db library For more details, please see the git log history below and: http://launchpad.net/oslo/+milestone/1.2.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo Changes in oslo.db 1.1.0..1.2.0 --- f740e3b 2014-11-28 06:01:27 + Imported Translations from Transifex ca1ad56 2014-11-21 17:05:34 +0200 Make test_models pass on py3 549ba15 2014-11-21 12:32:04 +0200 Repair include_object to accommodate new objects 10e8d15 2014-11-20 19:26:22 +0200 Add table name to foreign keys diff ddd11df 2014-11-20 14:11:24 + Updated from global requirements 2269848 2014-11-19 19:46:04 +0200 Handle Galera deadlock on SELECT FOR UPDATE 4b2058b 2014-11-19 16:02:42 +0200 Add exception filter for _sqlite_dupe_key_error b6d363d 2014-11-19 15:21:20 +0200 Add info on how to run unit tests 7f755bf 2014-11-18 16:05:01 +0200 Ensure is_backend_avail() doesn't leave open connections c54d3a9 2014-11-18 11:36:12 + Updated from global requirements 2099177 2014-11-08 12:58:23 + Add pbr to installation requirements 135701b 2014-10-27 21:21:10 -0700 Fix python3.x scoping issues with removed 'de' variable Diffstat (except docs and test files) - CONTRIBUTING.rst | 39 +++ .../locale/en_GB/LC_MESSAGES/oslo.db-log-info.po | 8 ++-- oslo.db/locale/fr/LC_MESSAGES/oslo.db-log-error.po | 56 ++ oslo.db/locale/fr/LC_MESSAGES/oslo.db-log-info.po | 33 + .../locale/fr/LC_MESSAGES/oslo.db-log-warning.po | 40 oslo/db/sqlalchemy/exc_filters.py | 21 ++-- oslo/db/sqlalchemy/session.py | 10 ++-- oslo/db/sqlalchemy/test_migrations.py | 2 +- oslo/db/sqlalchemy/utils.py| 3 +- requirements.txt | 1 + test-requirements-py2.txt | 2 +- test-requirements-py3.txt | 2 +- 15 files changed, 233 insertions(+), 35 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index cc50660..f8a0d8c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -4,0 +5 @@ +pbr=0.6,!=0.7,1.0 diff --git a/test-requirements-py2.txt b/test-requirements-py2.txt index 13cea90..ac5c18a 100644 --- a/test-requirements-py2.txt +++ b/test-requirements-py2.txt @@ -19 +19 @@ testscenarios=0.4 -testtools=0.9.36 +testtools=0.9.36,!=1.2.0 diff --git a/test-requirements-py3.txt b/test-requirements-py3.txt index 4f195da..58b9a3d 100644 --- a/test-requirements-py3.txt +++ b/test-requirements-py3.txt @@ -18 +18 @@ testscenarios=0.4 -testtools=0.9.36 +testtools=0.9.36,!=1.2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslotest release 1.3.0 (liberty)
We are excited to announce the release of: oslotest 1.3.0: OpenStack test framework For more details, please see the git log history below and: http://launchpad.net/oslotest/+milestone/1.3.0 Please report issues through launchpad: http://bugs.launchpad.net/oslotest Changes in oslotest 1.2.0..1.3.0 2568413 2014-11-20 14:11:42 + Updated from global requirements 30925bd 2014-11-18 11:36:30 + Updated from global requirements 47afc62 2014-11-05 08:35:07 + Updated from global requirements 230f8e3 2014-10-24 09:31:39 -0400 Add pbr to installation requirements fa1f130 2014-10-22 01:19:49 -0400 Clean up the docs for oslo_debug_helper Diffstat (except docs and test files) - requirements.txt| 3 ++- 2 files changed, 19 insertions(+), 6 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 01d1947..125b54e 100644 --- a/requirements.txt +++ b/requirements.txt @@ -4,0 +5 @@ +pbr=0.6,!=0.7,1.0 @@ -11 +12 @@ testscenarios=0.4 -testtools=0.9.34 +testtools=0.9.36,!=1.2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.rootwrap release 1.4.0 (liberty)
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side
On 04/21/2015 11:35 AM, Hayes, Graham wrote: From: Jay Pipes [jaypi...@gmail.com] The existing --os-compute-api-version CLI option should be made to take: * 2 * \d+.\d+ * latest And nothing else. Yes - please don't add a flag to the cli (or the python bindings for that matter) Isn't a cli flag exactly what Jay was describing? Speaking as someone who spends a lot of time interaction with different clouds, based on different versions of OpenStack and develops on top of tip of master clouds - the thought of trying to remember what micro versions are enabled on the cloud I am currently testing / working on is terrifying. This should be done via discovery. If a call requires a micro-version that is not deployed - return an error. I haven't had the pleasure(?) of needing to do this, but wouldn't you need to know what API versions are available before you try to do some task? (In order to know what actions are available, or what parameters to expect to be returned.) As I understand it, Jay's proposal is that if you don't specify a version you get the default (currently version 2, I think), if you do specify a version you get that version, and if you specify latest then you get the most recent version that the server knows about. Chris __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] debtcollector release 0.4.0 (liberty)
We are satisfied to announce the release of: debtcollector 0.4.0: A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non- destructive manner. For more details, please see the git log history below and: http://launchpad.net/debtcollector/+milestone/0.4.0 Please report issues through launchpad: http://bugs.launchpad.net/debtcollector Changes in debtcollector 0.3.0..0.4.0 - 62a75d7 2015-04-16 17:49:16 + Uncap library requirements for liberty 3afa864 2015-04-10 17:37:16 -0700 No longer need to workaround six issue/bug 3eddc93 2015-04-08 10:35:17 -0700 Add pypi download + version badges cd3e5d8 2015-03-21 00:08:07 + Updated from global requirements Diffstat (except docs and test files) - README.rst | 8 debtcollector/moves.py | 8 +--- requirements.txt | 2 +- test-requirements.txt | 4 ++-- 5 files changed, 14 insertions(+), 11 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 6af7f18..827fc3b 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8 +8 @@ six=1.9.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 8592bde..031650a 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11,2 +11,2 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] cliff release 1.11.0 (liberty)
We are delighted to announce the release of: cliff 1.11.0: Command Line Interface Formulation Framework For more details, please see the git log history below and: https://launchpad.net/python-cliff/+milestone/1.11.0 Please report issues through launchpad: https://bugs.launchpad.net/python-cliff Changes in cliff 1.10.1..1.11.0 --- 3b138fe 2015-04-18 13:12:20 +0200 Catch and ignore error when locale can not be set f558d9e 2015-04-16 17:47:46 + Uncap library requirements for liberty 40da955 2015-03-21 00:08:05 + Updated from global requirements c7462f8 2015-03-10 16:35:58 +1100 Update links to setuptools doc. 91f5ad3 2015-03-06 12:28:04 -0600 Pass user command text to the Command object 299fbb7 2015-02-20 17:45:55 + Change the argument passed to __init__ for help Diffstat (except docs and test files) - README.rst | 2 +- cliff/app.py| 11 +-- cliff/command.py| 3 ++- cliff/display.py| 5 +++-- cliff/help.py | 3 ++- requirements.txt| 2 +- test-requirements.txt | 2 +- 9 files changed, 25 insertions(+), 10 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 754a591..0bc229b 100644 --- a/requirements.txt +++ b/requirements.txt @@ -10 +10 @@ six=1.9.0 -stevedore=1.1.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index ebb6880..af151ba 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -9 +9 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.context release 0.3.0 (liberty)
We are jubilant to announce the release of: oslo.context 0.3.0: Oslo Context library For more details, please see the git log history below and: http://launchpad.net/oslo.context/+milestone/0.3.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.context Changes in oslo.context 0.2.0..0.3.0 95c031d 2015-04-16 18:02:15 + Uncap library requirements for liberty 6ac5cc2 2015-04-04 02:02:41 -0400 Standardize setup.cfg summary for oslo libs 2d6b2d6 2015-04-03 13:57:40 + Update to latest hacking abfc021 2015-03-26 11:00:56 + Updated from global requirements 7cc81aa 2015-03-05 14:50:48 -0500 fix bug tracker link Diffstat (except docs and test files) - README.rst| 2 +- setup.cfg | 2 +- test-requirements.txt | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) Requirements updates diff --git a/test-requirements.txt b/test-requirements.txt index 7793b38..0d0e2e5 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -5,2 +5,2 @@ -hacking=0.9.1,0.10 -oslotest=1.2.0 # Apache-2.0 +hacking=0.10.0,0.11 +oslotest=1.5.1 # Apache-2.0 @@ -10 +10 @@ coverage=3.6 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] keystonemiddleware release 1.6.0 (liberty)
We are overjoyed to announce the release of: keystonemiddleware 1.6.0: Middleware for OpenStack Identity For more details, please see the git log history below. Changes in keystonemiddleware 1.5.0..1.6.0 -- 04a6a9f 2015-04-16 17:53:57 + Uncap library requirements for liberty 452bf87 2015-04-16 16:32:37 +1000 Remove retry parameter 90edbc8 2015-04-14 15:01:39 + Fix s3_token middleware parsing insecure option 1150d04 2015-04-08 18:58:41 + Updated from global requirements 809967f 2015-04-08 02:42:23 + Pull echo service out of auth_token. abcdbb3 2015-04-05 16:12:43 + Fix typos in keystonemiddleware bafd958 2015-03-16 14:24:47 +1100 Rename requests mock object in testing 8e1bba1 2015-03-15 08:36:44 -0500 Update auth_token config docs 71fc24e 2015-03-14 18:45:56 +0800 Crosslink to other sites that are owned by Keystone 50c2baf 2015-03-13 08:59:15 -0500 Move _memcache_pool into auth_token fec6f62 2015-03-11 17:03:54 -0500 Move unit tests into tests.unit Diffstat (except docs and test files) - keystonemiddleware/_memcache_pool.py | 184 -- keystonemiddleware/auth_token/__init__.py | 86 +- keystonemiddleware/auth_token/_cache.py|4 +- keystonemiddleware/auth_token/_memcache_pool.py| 184 ++ keystonemiddleware/echo/__init__.py|0 keystonemiddleware/echo/__main__.py|7 + keystonemiddleware/echo/service.py | 46 + keystonemiddleware/s3_token.py |3 +- .../unit/auth_token/test_auth_token_middleware.py | 2760 +++ requirements.txt |8 +- test-requirements-py3.txt |8 +- test-requirements.txt |8 +- 40 files changed, 5041 insertions(+), 4968 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index b207833..0a4ff4b 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7 +7 @@ iso8601=0.1.9 -oslo.config=1.9.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 @@ -9,3 +9,3 @@ oslo.context=0.2.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.serialization=1.2.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements-py3.txt b/test-requirements-py3.txt index ff9e614..9a33730 100644 --- a/test-requirements-py3.txt +++ b/test-requirements-py3.txt @@ -11,4 +11,4 @@ pycrypto=2.6 -oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 -oslo.messaging=1.6.0 # Apache-2.0 -requests-mock=0.5.1 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 +oslo.messaging=1.8.0 # Apache-2.0 +requests-mock=0.6.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 55d21d5..e36b86e 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -12,4 +12,4 @@ pycrypto=2.6 -oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 -oslo.messaging=1.6.0 # Apache-2.0 -requests-mock=0.5.1 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 +oslo.messaging=1.8.0 # Apache-2.0 +requests-mock=0.6.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.i18n release 0.1.0 (liberty)
We are thrilled to announce the release of: oslo.i18n HEAD: oslo.i18n library For more details, please see the git log history below and: http://launchpad.net/oslo/+milestone/HEAD Please report issues through launchpad: http://bugs.launchpad.net/oslo Changes in oslo.i18n 0.1.0..HEAD 166f4a5 2014-07-13 12:35:19 -0700 Document how to add import exceptions a4fc251 2014-07-13 12:35:15 -0700 Remove mention of Message objects from public docs d648097 2014-06-05 22:20:35 +0200 Setup for translation Diffstat (except docs and test files) - oslo.i18n/locale/oslo.i18n.pot | 29 + oslo/i18n/_gettextutils.py | 5 - oslo/i18n/log.py | 12 +--- 4 files changed, 77 insertions(+), 8 deletions(-) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] on supporting multiple implementations of tripleo-heat-templates
On Fri, 2015-04-17 at 15:21 +0200, Giulio Fidente wrote: Hi, the Heat/Puppet implementation of the Overcloud deployment seems to be surpassing in features the Heat/Elements implementation. The changes for Ceph are an example, the Puppet based version is already adding features which don't have they counterpart into Elements based. Recently we started working on the addition of Pacemaker into the Overcloud, to monitor the services and provide a number of 'auto healing' features, and again this is happening in the Puppet implementation only (at least for now) so I think the gap will become bigger. Given we support different implementations with a single top-level template [1], to keep other templates valid we're forced to propagate the params into the Elements based templates as well, even though there is no use for these there, see for example [2]. This was done intentionally when adding the new puppet templates. The idea was that tripleo-heat-templates was defining a high level interface that could be used to provision and configure a cloud with multiple backends (tripleo-image-elements and or puppet being the current options). It was actually a bit more work to do it this way but the idea is that we are refining our interfaces to be more generic and correct. In doing the puppet work we actually discovered lots of data that was being copied into various roles that wasn't needed. And having the working tripleo-image-elements implementation to begin with was also a great help to speed the puppet stuff along. The extra work itself is not of great concern but I wonder if it wouldn't make sense to deprecate the Elements based templates at this point, instead of keep adding there unused parts? You aren't really adding that many unused parts. Just a parameter here and there right? And this is just to keep the CI jobs happy. With regards to the specific templates for triple-image-elements for configuration long term I'm not sure where they are headed. I don't think there is as much interest in maintaining them so perhaps we should deprecate them... However, I would like to see us maintain the abstractions we have in place in tripleo-heat-templates should another implementation come along besides Puppet. To me this is sort of the essence of TripleO (defining an interface to deploy a cloud). And if you are suggesting we get rid of tripleo-image-elements just so we can then go and remove these abstractions then I think it might be a step in the wrong direction. In other words... regardless of what happens to the maintenance of the tripleo-image-elements (and any associated templates) lets keep a structure that supports multiple backends. Yes, it may cost a bit of extra wiring here and there but I think it is worth the effort. Thoughts? 1. https://github.com/openstack/tripleo-heat-templates/blob/master/overcloud-without-mergepy.yaml 2. https://review.openstack.org/#/c/173773 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] debtcollector release 0.4.0 (liberty)
We are psyched to announce the release of: debtcollector 0.4.0: A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non- destructive manner. For more details, please see the git log history below and: http://launchpad.net/debtcollector/+milestone/0.4.0 Please report issues through launchpad: http://bugs.launchpad.net/debtcollector Changes in debtcollector 0.3.0..0.4.0 - 62a75d7 2015-04-16 17:49:16 + Uncap library requirements for liberty 3afa864 2015-04-10 17:37:16 -0700 No longer need to workaround six issue/bug 3eddc93 2015-04-08 10:35:17 -0700 Add pypi download + version badges cd3e5d8 2015-03-21 00:08:07 + Updated from global requirements Diffstat (except docs and test files) - README.rst | 8 debtcollector/moves.py | 8 +--- requirements.txt | 2 +- test-requirements.txt | 4 ++-- 5 files changed, 14 insertions(+), 11 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 6af7f18..827fc3b 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8 +8 @@ six=1.9.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 8592bde..031650a 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11,2 +11,2 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][lbaas] adding lbaas core
Congratulations Phil! On Apr 21, 2015, at 11:54 AM, Doug Wiegley doug...@parksidesoftware.com wrote: It’s been a week, welcome Phil. Thanks, doug On Apr 13, 2015, at 2:39 PM, Doug Wiegley doug...@parksidesoftware.com wrote: Hi all, I'd like to nominate Philip Toohill as a neutron-lbaas core. Good guy, did a bunch of work on the ref impl for lbaasv2, and and I'll let the numbers[1] speak for themselves. Existing lbaas cores, please vote. All three of us. :-) [1] http://stackalytics.com/report/contribution/neutron-lbaas/30 Thanks, doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: Message signed with OpenPGP using GPGMail __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-cinderclient release 1.2.0 (liberty)
We are tickled pink to announce the release of: python-cinderclient 1.2.0: OpenStack Block Storage API Client Library For more details, please see the git log history below. Changes in python-cinderclient 1.1.1..1.2.0 --- ae03d2a 2015-04-20 15:50:08 + Enable version discovery b4b0eea 2015-04-20 09:44:13 -0600 Remove print statement in unit test 2fa7e1e 2015-04-20 15:10:36 + Add ability to specify path var to testr c8f670e 2015-04-16 18:12:53 + Uncap library requirements for liberty fa8c7e3 2015-04-12 17:02:18 +0530 cinder list now supports filter by tenant de36755 2015-03-31 23:37:18 -0700 Allow cinderclient to handle exception response e5a1304 2015-03-23 21:20:10 -0600 Move unit tests into test directory e2afc01 2015-03-17 14:21:48 + bash_completion now shows only subcommands when subcommand is help 425565b 2015-03-16 18:45:21 + Update to change name for volume type client 0f73c5f 2015-03-16 23:26:22 +0530 cinder list now prints dash '-' when data is None 57c9bf1 2015-03-10 09:45:00 +0530 cinderclient accepts arguments after metadata without -- separator f47f973 2015-03-06 01:45:08 +0530 Updated help on cinder reset-state cli fc7ebb1 2015-02-25 18:51:43 + Adopt CLI sorting argument guidelines c01529f 2015-02-24 16:11:46 +0800 Add missing all-tenants option to transfer-list d76387c 2015-02-12 10:52:17 -0300 Add -d short option for --debug 9176e44 2015-02-10 11:25:31 + Fix volume_transfers import in v2 f9eefcc 2015-02-05 20:19:06 + Updated from global requirements ff3e5a4 2015-02-04 20:25:14 + reset-state should warn that it is DB only e5779d3 2015-01-30 16:50:21 + Expose cinder's scheduler pool API e9e8aab 2015-01-28 13:36:20 -0600 Fix up help message for reset-state call 11e5e4f 2015-01-22 15:11:33 + Add tests for consistency groups and cgsnapshots 0560f78 2015-01-22 14:52:25 + cinder list fails with 'name' sort key 200aeae 2015-01-15 10:56:27 +0800 Remove commented code in cinderclient/v1/volumes.py fdba364 2015-01-13 16:09:34 -0500 Make cinderclient metadata CLI output consistent 0b38d75 2015-01-12 22:58:00 + Leverage openstack.common.importutils import_class 3a97cb2 2015-01-08 12:21:33 + v2 error message grammatical error 1d38426 2015-01-05 16:04:43 -0500 Add command to show pool information for backends b0e4cc1 2014-12-22 02:23:00 + Client output is not sorted by --sort_key 6f8c235 2014-12-19 13:26:21 -0500 Add support for os-volume-type-access extension bc2b8bf 2014-12-17 07:27:38 -0800 Added type description for volume type client 7783767 2014-12-09 11:41:27 -0600 Don't use sessions if third party plugin is used 6f66494 2014-12-05 03:30:39 + Workflow documentation is now in infra-manual 5920994 2014-12-04 02:20:59 + List all the request items when the list is over osapi_max_limit d9da860 2014-12-03 16:39:23 -0500 Allow CG quota to be showed and updated 7a50182 2014-12-01 02:43:52 + Add the parameter bypass_url to the cinder client a68ba94 2014-12-01 02:16:44 + Use newer features from keystoneclient 4ccb70a 2014-11-30 19:37:10 +0200 Support Volume Backup Quota 713e331 2014-11-27 21:48:14 + Updated from global requirements 616b982 2014-11-25 12:39:17 -0600 Add ability to create volume from image by image name ac9ef2b 2014-11-25 15:14:09 + Remove cinderclient/tests from coverage report 029a776 2014-11-25 01:28:54 + Fix 'search_opts' error with backup delete command 542a675 2014-11-17 16:33:07 +0530 Remove unused methods from utils.py 384b882 2014-10-27 14:41:54 + Fix incorrect variable name a6b434e 2014-10-24 11:57:42 -0400 cinderclient does not retry with TimeoutException 122bf5b 2014-10-24 15:43:04 + Adds tty password entry for cinderclient d202875 2014-10-09 15:22:49 -0400 Don't git ignore .mailmap and .testr.conf e76f06b 2014-10-08 17:00:51 -0400 gitignore /.* 6f5fd37 2014-10-08 19:30:10 +0400 Add profiling support to cinderclient 20df1cb 2014-10-02 15:24:01 -0400 Fix volume name support of unmanage and replication commands 1cb1350 2014-10-02 14:58:19 + Simplify cinder manage command args 41f5835 2014-10-01 14:34:13 -0600 Add swap and it's variants to gitignore 1dc8081 2014-09-24 20:03:58 -0400 Docstring of unmanage subcommand is missing 5bf13e1 2014-09-19 10:35:35 -0400 Remove Python 2.4 compat shim b03d1e1 2014-09-13 09:40:00 +0200 Stop using intersphinx f7d391e 2014-09-09 18:40:31 + client HTTPClient __init__ fails if auth_url None 17e4d6c 2014-09-08 11:31:22 + Fixed typos found by RETF rules 4a7014a 2014-08-29 00:09:43 -0700 Ability to pass metadata during snapshot create cebd81e 2014-07-23 12:35:33 + Fix comment in tearDown() 31a7ae5 2014-07-03 15:06:51 +0800 Use immutable arg rather mutable arg 05d9232 2014-07-01 14:53:54 +0800 Add CONTRIBUTING.rst Diffstat (except docs and test files) - .coveragerc|2 +- .gitignore
Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!
Hi Ramy, Will there be any discussions of this issue on the Vancouver Summit? Lenny Verkhovsky SW Engineer, Mellanox Technologies From: Nikolay Fedotov (nfedotov) [mailto:nfedo...@cisco.com] Sent: Tuesday, April 21, 2015 8:10 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution! Hello Ramy Take me in account ☺ We used puppet modules located in system-config to install zuul and nodepool. Also there were a lot manual configuration. Maybe someday there will be a “green button” to set it up in moment. Thanks! From: Asselin, Ramy [mailto:ramy.asse...@hp.com] Sent: Monday, April 20, 2015 8:17 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution! All Third-Party CI operators: We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed open-source solutions. Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution. If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us. We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4]. For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/ If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5]. Thanks! Ramy [1] https://wiki.openstack.org/wiki/ThirdPartySystems [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html [3] https://storyboard.openstack.org/#!/story/2000101 [4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z [5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] django_openstack_auth release 1.3.0 (liberty)
We are delighted to announce the release of: django_openstack_auth 1.3.0: Django authentication backend for use with OpenStack Identity For more details, please see the git log history below and: https://launchpad.net/django-openstack-auth/+milestone/1.3.0 Please report issues through launchpad: https://bugs.launchpad.net/django-openstack-auth Changes in django_openstack_auth 1.2.0..1.3.0 - 3a8d34f 2015-04-21 14:51:17 + Update README to work with release tools 03446e8 2015-04-20 06:03:10 + Imported Translations from Transifex 8657c04 2015-04-19 06:02:29 + Imported Translations from Transifex 866471a 2015-04-17 06:03:00 + Imported Translations from Transifex 1786833 2015-04-16 17:50:31 + Uncap library requirements for liberty Diffstat (except docs and test files) - README.rst| 9 + openstack_auth/locale/ar/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ca/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/cs/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/de/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/en_AU/LC_MESSAGES/django.po | 12 +++- openstack_auth/locale/en_GB/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/es/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/es_MX/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fi_FI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fr/LC_MESSAGES/django.po| 9 + openstack_auth/locale/hi/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/it/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ko_KR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/ne/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/nl_NL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pa_IN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pl_PL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pt/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/pt_BR/LC_MESSAGES/django.po | 18 ++ openstack_auth/locale/ru/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/sl_SI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/sr/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/tr_TR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/uk/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/zh_CN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/zh_TW/LC_MESSAGES/django.po | 6 +++--- requirements.txt | 2 +- test-requirements.txt | 2 +- 29 files changed, 98 insertions(+), 92 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 8116201..bdbd4b5 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ Django=1.4.2,1.8 -oslo.config=1.9.3,1.10.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index c8c6a3b..58cab54 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] # release 1.3.0 (liberty)
We are stoked to announce the release of: django_openstack_auth 1.3.0: Django authentication backend for use with OpenStack Identity For more details, please see the git log history below and: https://launchpad.net/django-openstack-auth/+milestone/1.3.0 Please report issues through launchpad: https://bugs.launchpad.net/django-openstack-auth Changes in django_openstack_auth 1.2.0..1.3.0 - 3a8d34f 2015-04-21 14:51:17 + Update README to work with release tools 03446e8 2015-04-20 06:03:10 + Imported Translations from Transifex 8657c04 2015-04-19 06:02:29 + Imported Translations from Transifex 866471a 2015-04-17 06:03:00 + Imported Translations from Transifex 1786833 2015-04-16 17:50:31 + Uncap library requirements for liberty Diffstat (except docs and test files) - README.rst| 9 + openstack_auth/locale/ar/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ca/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/cs/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/de/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/en_AU/LC_MESSAGES/django.po | 12 +++- openstack_auth/locale/en_GB/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/es/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/es_MX/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fi_FI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/fr/LC_MESSAGES/django.po| 9 + openstack_auth/locale/hi/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/it/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/ko_KR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/ne/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/nl_NL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pa_IN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pl_PL/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/pt/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/pt_BR/LC_MESSAGES/django.po | 18 ++ openstack_auth/locale/ru/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/sl_SI/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/sr/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/tr_TR/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/uk/LC_MESSAGES/django.po| 6 +++--- openstack_auth/locale/zh_CN/LC_MESSAGES/django.po | 6 +++--- openstack_auth/locale/zh_TW/LC_MESSAGES/django.po | 6 +++--- requirements.txt | 2 +- test-requirements.txt | 2 +- 29 files changed, 98 insertions(+), 92 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 8116201..bdbd4b5 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ Django=1.4.2,1.8 -oslo.config=1.9.3,1.10.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index c8c6a3b..58cab54 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-heatclient release 0.5.0 (liberty)
We are tickled pink to announce the release of: python-heatclient 0.5.0: OpenStack Orchestration API Client Library For more details, please see the git log history below and: http://launchpad.net/python-heatclient/+milestone/0.5.0 Please report issues through launchpad: http://bugs.launchpad.net/python-heatclient Changes in python-heatclient 0.4.0..0.5.0 - 7c70bcf 2015-04-20 13:42:26 + correction in function names under test_resource 77204a3 2015-04-16 18:13:03 + Uncap library requirements for liberty 6b08533 2015-04-02 10:40:01 +1300 Make README.rst comply with expected format 65a1c78 2015-04-01 16:55:17 +0200 Remove the deprecated shell commands Diffstat (except docs and test files) - README.rst | 16 ++-- heatclient/v1/shell.py | 161 - requirements.txt | 6 +- test-requirements.txt | 4 +- 6 files changed, 16 insertions(+), 181 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index b8eaca6..a290a65 100644 --- a/requirements.txt +++ b/requirements.txt @@ -10,3 +10,3 @@ PrettyTable=0.7,0.8 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 -oslo.serialization=1.4.0,1.5.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index cc3962d..50abc48 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -13,2 +13,2 @@ mox3=0.7.0 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 -oslotest=1.5.1,1.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.vmware release 0.12.0 (liberty)
We are tickled pink to announce the release of: oslo.vmware 0.12.0: Oslo VMware library For more details, please see the git log history below and: http://launchpad.net/oslo.vmware/+milestone/0.12.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.vmware Changes in oslo.vmware 0.11.1..0.12.0 - 9338d7f 2015-04-16 18:10:45 + Uncap library requirements for liberty 46f2327 2015-04-04 02:30:40 -0400 Cleanup README.rst and setup.cfg bc146a3 2015-04-03 14:11:39 + Update to latest hacking 0f73e5d 2015-03-25 06:04:48 + Imported Translations from Transifex 6d8594a 2015-03-24 07:30:29 -0700 Revert VMWare NSXv: Common components 9b57b13 2015-03-21 00:17:14 + Updated from global requirements 3879e83 2015-03-20 16:14:43 + Move pylint dependency to tox.ini 8445b49 2015-03-20 03:35:11 -0700 Move exception related tests to new module Diffstat (except docs and test files) - README.rst |2 +- .../locale/fr/LC_MESSAGES/oslo.vmware-log-info.po | 10 +- oslo.vmware/locale/fr/LC_MESSAGES/oslo.vmware.po | 81 +- oslo.vmware/locale/oslo.vmware-log-info.pot|8 +- oslo.vmware/locale/oslo.vmware.pot | 131 +-- oslo_vmware/network/__init__.py|0 oslo_vmware/network/nsx/__init__.py|0 oslo_vmware/network/nsx/nsxv/__init__.py |0 oslo_vmware/network/nsx/nsxv/api/__init__.py |0 oslo_vmware/network/nsx/nsxv/api/api.py| 598 -- oslo_vmware/network/nsx/nsxv/api/api_helper.py | 117 -- oslo_vmware/network/nsx/nsxv/common/__init__.py|0 oslo_vmware/network/nsx/nsxv/common/exceptions.py | 97 -- oslo_vmware/network/nsx/nsxv/objects/__init__.py |0 .../network/nsx/nsxv/objects/edge_cfg_obj.py | 67 -- .../network/nsx/nsxv/objects/loadbalancer.py | 392 --- .../network/nsx/nsxv/test_nsxv_loadbalancer.py | 98 -- requirements-py3.txt | 12 +- requirements.txt | 12 +- setup.cfg |2 +- test-requirements.txt |5 +- tox.ini|3 + 30 files changed, 158 insertions(+), 2947 deletions(-) Requirements updates diff --git a/requirements-py3.txt b/requirements-py3.txt index fba2804..ab96725 100644 --- a/requirements-py3.txt +++ b/requirements-py3.txt @@ -5 +5 @@ -stevedore=1.1.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 @@ -14,3 +14,3 @@ six=1.9.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.serialization=1.2.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 @@ -23 +23 @@ suds-jurko=0.6 -eventlet=0.16.1 +eventlet=0.16.1,!=0.17.0 @@ -27 +27 @@ urllib3=1.8.3 -oslo.concurrency=1.4.1 # Apache-2.0 +oslo.concurrency=1.8.0 # Apache-2.0 diff --git a/requirements.txt b/requirements.txt index 4b4b2bb..807bcfc 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7 +7 @@ pbr=0.6,!=0.7,1.0 -stevedore=1.1.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 @@ -16,3 +16,2 @@ six=1.9.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.serialization=1.2.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 @@ -25,2 +24 @@ suds=0.4 -eventlet=0.16.1 -httplib2=0.7.5 +eventlet=0.16.1,!=0.17.0 @@ -29 +27 @@ urllib3=1.8.3 -oslo.concurrency=1.4.1 # Apache-2.0 +oslo.concurrency=1.8.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index cfaa103..5346047 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -6,2 +6 @@ -hacking=0.9.2,0.10 -pylint=1.3.0 # GNU GPL v2 +hacking=0.10.0,0.11 @@ -24 +23 @@ coverage=3.6 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] tooz release 0.15.0 (liberty)
We are happy to announce the release of: tooz 0.15.0: Coordination library for distributed systems. For more details, please see the git log history below and: http://launchpad.net/python-tooz/+milestone/0.15.0 Please report issues through launchpad: http://bugs.launchpad.net/python-tooz/ Changes in tooz 0.14.0..0.15.0 -- e4bbade 2015-04-18 11:25:34 -0700 Fix param name to be its right name bed46b8 2015-04-17 17:58:23 -0700 Replace more instance(s) of exception chaining with helper 3b619de 2015-04-18 00:52:34 + Just use staticmethod functions to create _dumps/_loads a039cb0 2015-04-16 18:15:34 + Uncap library requirements for liberty 5f92ace 2015-04-15 17:31:21 -0700 Link AOF to redis persistence docs a890d34 2015-04-15 08:56:47 -0700 Add exception docs to developer docs edd499f 2015-04-14 23:26:12 -0700 Add + use helper to raise + chain exceptions 15e659f 2015-04-14 15:51:35 -0700 Allow the acquired file to be closed manually a0980f8 2015-04-14 19:34:50 + Updated from global requirements e21f7af 2015-04-13 18:45:27 -0700 Silence logs + errors when stopping and group membership lost 6aabfbe 2015-04-13 15:30:47 -0700 Make and use a thread safe pymemcache client subclass 270ad93 2015-04-13 14:13:39 -0700 Handle errors that come out of pymemcache better 44131d0 2015-04-13 15:45:14 + Use rst inline code structure + link to sentinel Diffstat (except docs and test files) - requirements-py3.txt| 10 ++-- requirements.txt| 8 +-- test-requirements.txt | 9 +-- tooz/coordination.py| 39 tooz/drivers/file.py| 4 ++ tooz/drivers/ipc.py | 4 +- tooz/drivers/memcached.py | 143 +++- tooz/drivers/mysql.py | 12 +++- tooz/drivers/pgsql.py | 8 ++- tooz/drivers/redis.py | 45 +++--- tooz/drivers/zookeeper.py | 72 -- tooz/locking.py | 10 +++- tooz/utils.py | 9 +-- 16 files changed, 422 insertions(+), 76 deletions(-) Requirements updates diff --git a/requirements-py3.txt b/requirements-py3.txt index c9c1428..b61b75b 100644 --- a/requirements-py3.txt +++ b/requirements-py3.txt @@ -6 +6 @@ Babel=1.3 -stevedore=1.3.0,1.4.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 @@ -10,2 +10,2 @@ kazoo=1.3.1 -pymemcache=1.2 -zake=0.1.6 +pymemcache=1.2 # Apache 2.0 License +zake=0.1.6 # Apache-2.0 @@ -13,2 +13,2 @@ msgpack-python=0.4.0 -retrying=1.2.3,!=1.3.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +retrying=1.2.3,!=1.3.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/requirements.txt b/requirements.txt index 287692d..e995b54 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ Babel=1.3 -stevedore=1.3.0,1.4.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 @@ -10 +10 @@ kazoo=1.3.1 -pymemcache=1.2 +pymemcache=1.2 # Apache 2.0 License @@ -13 +13 @@ msgpack-python=0.4.0 -retrying=1.2.3,!=1.3.0 +retrying=1.2.3,!=1.3.0 # Apache-2.0 @@ -15 +15 @@ futures=2.1.6 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 0e02724..56264a1 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -8 +8 @@ discover -mock=1.0 # only needed on python 3.3 +mock=1.0 @@ -10 +10 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -17,2 +17,3 @@ psycopg2 -PyMySQL=0.6.2 -sysv_ipc=0.6.8 +PyMySQL=0.6.2 # MIT License +sysv_ipc=0.6.8 # BSD License +fixtures=0.3.14 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver
Can you please investigate and comment here on this thread as to why your CI is failing for all patches? If this is not resolved, your driver will not be re-added, and ignoring requests to investigate CI failures will increase the chances of your driver being removed in future, without notice. Setting up a CI system is not a box ticking exercise, it requires monitoring and maintenance. If that is not possible then you are not yet in a position to be added back into cinder. On 21 Apr 2015 19:32, Diem Tran diem.t...@oracle.com wrote: On 04/21/2015 01:01 PM, Mike Perez wrote: On 09:57 Apr 21, Mike Perez wrote: On 15:47 Apr 20, Diem Tran wrote: Hi Mike, Oracle ZFSSA iSCSI CI is now reporting test results. It is configured to run against the ZFSSA iSCSI driver. You can see the results here: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z Below are some patchsets that the CI reports: https://review.openstack.org/#/c/168424/ https://review.openstack.org/#/c/168419/ https://review.openstack.org/#/c/175247/ https://review.openstack.org/#/c/175077/ https://review.openstack.org/#/c/163706/ I would like to kindly request you and the core team to get the Oracle ZFSSA iSCSI driver re-integrated back to the Cinder code base. If there is anything else you need from the CI and the driver, please do let me know. This was done on 4/8: https://review.openstack.org/#/c/170770/ My mistake this was only the NFS driver. The window to have drivers readded in Kilo has long past. Please see: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html This will have to be readded in Liberty only at this point. Thank you for your reply. Could you please let me know the procedure needed for the driver to be readded to Liberty? Specifically, will you be the one who upload the revert patchset, or it is the driver maintainer's responsibility? Diem. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [oslo]
All, I created a patch that would introduce a new behavior in how oslo.config matches StrOpt choice values. https://review.openstack.org/#/c/167025/ I’m emailing the mailing list to get a consensus on whether the approach is the correct one. Historically oslo.config matches given StrOpt values to choices in a case sensitive manner. But this patch would make that match case insensitive. This should make it slightly easier for deployers so they don’t have to worry about specifying the correct capitalization. But the drawback is that this change will not allow having choices with the same characters but different capitalization. For example (this would not be allowed): cfg.StrOpt(‘foo_opt’, choices=(‘FOO’, ‘foo’) help=‘blah’) I doubt we have any cases of above, but correct me if I’m wrong. Another suggested alternative was to have a new flag on StrOpt to specify whether the matching is case sensitive or insensitive. This avoids the issue above, but means the deployer must take note of whether the option is case insensitive or insensitive. Let me know your thoughts. Thanks __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side
On 04/20/2015 06:30 PM, Claudiu Belu wrote: Hello, So, AFAIK, there is currently a problem with this. If you make a request for, let's say v2.2 microversion, you will want to execute: nova --os-compute-api-version 2.2 keypair-list But, from my experience, that does not work as expected. Instead of the plugins/v3/ module, it is executed the old contrib/ module, which is not expected. (Also, I've checked, the request header contains X-OpenStack-Compute-API-Version, it is ignored) The only way to get it right (at least in devstack) is to execute: nova --service-type computev21 --os-compute-api-version 2.2 keypair-list So, if I understand Jay correctly, only service-type 'compute' should exist and if any microversion is requested, that particular microversion should be executed. Currently, it doesn't behave like this... so.. Houston, we have a problem. :) Best regards, Claudiu From: Jay Pipes [jaypi...@gmail.com] Sent: Sunday, April 19, 2015 3:45 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side Andrey, thanks for posing these important questions. My thoughts inline. On 04/10/2015 07:30 AM, Andrey Kurilin wrote: Hi all! I working on implementation of support microversions in novaclient. Patches are ready for review, but there is one opened question: what we should do with v2.1 endpoint(computev21 service type)? compute is a default value of service type and keystone returns v2 api endpoint for it(at least in devstack), so version header will be ignored on API side. On the one hand, each deployment can have it's own configuration of service catalog and endpoints, so default value of service type should be strict and support as much deployments as we can. On the other hand, dependency of service type for microversion feature is not good and end-users should not take care about choice of correct service type when they want to execute simple command. Correct. Possible solutions: 1. leave everything as is: use --service-type computev21 for each microversioned command It was a mistake to put any version information in *any* of the service types. The service type should be compute and only compute. The version negotiation should be handled entirely separately via the X-OpenStack-Compute-API-Version HTTP header sent from the client. 2. move default value of service type to environment variables(default value is hardcoded in novaclient code now) I don't see any reason to do that, no. 3. add additional option --compute-api-type. Proposed etherpad by Christopher Yeoh https://etherpad.openstack.org/p/novaclient_microversions_design . Implementation is already finished - https://review.openstack.org/#/c/167577/ . This proposal still requires addition cli option, but compute-api-type looks more user-friendly -1. There should be no additional option. The API microversion should be negotiated via the X-OpenStack-Compute-API-Version HTTP header and only via that. The existing --os-compute-api-version CLI option should be made to take: * 2 * \d+.\d+ * latest And nothing else. Best, -jay Current implementation uses compute as default value for service type. Patches are pass all gates, except stable branches and ready for review: * https://review.openstack.org/#/c/169378/ - deprecate v1.1 and remove references to v3 in code * https://review.openstack.org/#/c/152569/ - Implements 'microversions' api type - Part 1 (usage of nova.api.openstack.api_version_request:APIVersionRequest class with https://review.openstack.org/#/c/169292/ ) * https://review.openstack.org/#/c/167408/ - Implements 'microversions' api type - Part 2 (adds new decorators and substitution mechanism using nova.api.openstack.versioned_method ) * https://review.openstack.org/#/c/136458/ - Implementation of 2.2 microversion -- Best regards, Andrey Kurilin. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Yes - please don't add a flag to the cli (or the python bindings for that matter) Speaking as someone who spends a lot of time interaction with different clouds, based on different versions of OpenStack and develops on top of tip of master clouds - the thought of trying to remember what micro versions are
Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver
On 04/21/2015 01:01 PM, Mike Perez wrote: On 09:57 Apr 21, Mike Perez wrote: On 15:47 Apr 20, Diem Tran wrote: Hi Mike, Oracle ZFSSA iSCSI CI is now reporting test results. It is configured to run against the ZFSSA iSCSI driver. You can see the results here: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z Below are some patchsets that the CI reports: https://review.openstack.org/#/c/168424/ https://review.openstack.org/#/c/168419/ https://review.openstack.org/#/c/175247/ https://review.openstack.org/#/c/175077/ https://review.openstack.org/#/c/163706/ I would like to kindly request you and the core team to get the Oracle ZFSSA iSCSI driver re-integrated back to the Cinder code base. If there is anything else you need from the CI and the driver, please do let me know. This was done on 4/8: https://review.openstack.org/#/c/170770/ My mistake this was only the NFS driver. The window to have drivers readded in Kilo has long past. Please see: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html This will have to be readded in Liberty only at this point. Thank you for your reply. Could you please let me know the procedure needed for the driver to be readded to Liberty? Specifically, will you be the one who upload the revert patchset, or it is the driver maintainer's responsibility? Diem. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver
On 13:38 Apr 21, Diem Tran wrote: On 04/21/2015 01:01 PM, Mike Perez wrote: On 09:57 Apr 21, Mike Perez wrote: On 15:47 Apr 20, Diem Tran wrote: Hi Mike, Oracle ZFSSA iSCSI CI is now reporting test results. It is configured to run against the ZFSSA iSCSI driver. You can see the results here: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z Below are some patchsets that the CI reports: https://review.openstack.org/#/c/168424/ https://review.openstack.org/#/c/168419/ https://review.openstack.org/#/c/175247/ https://review.openstack.org/#/c/175077/ https://review.openstack.org/#/c/163706/ I would like to kindly request you and the core team to get the Oracle ZFSSA iSCSI driver re-integrated back to the Cinder code base. If there is anything else you need from the CI and the driver, please do let me know. This was done on 4/8: https://review.openstack.org/#/c/170770/ My mistake this was only the NFS driver. The window to have drivers readded in Kilo has long past. Please see: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html This will have to be readded in Liberty only at this point. Thank you for your reply. Could you please let me know the procedure needed for the driver to be readded to Liberty? Specifically, will you be the one who upload the revert patchset, or it is the driver maintainer's responsibility? You're more than welcome to propose the patch now to Cinder master. I was just doing the reverts in Kilo to keep things moving. -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.concurrency release 1.9.0 (liberty)
We are delighted to announce the release of: oslo.concurrency 1.9.0: Oslo Concurrency library For more details, please see the git log history below and: http://launchpad.net/oslo.concurrency/+milestone/1.9.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.concurrency Changes in oslo.concurrency 1.8.0..1.9.0 4d7dce2 2015-04-19 01:17:43 +0200 Add binary parameter to execute and ssh_execute c05c8c3 2015-04-18 00:11:28 +0200 Port processutils to Python 3 f366bd2 2015-04-16 17:45:40 + Uncap library requirements for liberty e3c2419 2015-04-10 17:45:03 +0200 Move fixtures to test-requirements.txt fa415de 2015-04-11 00:56:02 +1000 Fix test_as_root* tests to work when run as root d04cf66 2015-04-07 21:09:17 + Add pypi download + version badges fe84d2a 2015-04-04 02:01:33 -0400 Standardize setup.cfg summary for oslo libs e6f5e19 2015-03-24 06:04:39 + Imported Translations from Transifex 9f949fd 2015-03-21 00:16:47 + Updated from global requirements a0549bf 2015-03-20 16:03:21 -0400 Remove tools/run_cross_tests.sh from openstack-common.conf Diffstat (except docs and test files) - README.rst | 10 +- openstack-common.conf | 1 - .../LC_MESSAGES/oslo.concurrency-log-error.po | 32 .../locale/en_GB/LC_MESSAGES/oslo.concurrency.po | 56 --- oslo_concurrency/processutils.py | 52 +- requirements.txt | 7 +- setup.cfg | 2 +- test-requirements.txt | 7 +- 12 files changed, 317 insertions(+), 72 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 1fcebea..cf4758d 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8,4 +8,3 @@ iso8601=0.1.9 -fixtures=0.3.14 -oslo.config=1.9.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index e715139..0fb38b7 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -6 +6 @@ hacking=0.10.0,0.11 -oslotest=1.2.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -8,0 +9 @@ futures=2.1.6 +fixtures=0.3.14 @@ -11 +12 @@ futures=2.1.6 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -14 +15 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -eventlet=0.16.1 +eventlet=0.16.1,!=0.17.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.config release 1.11.0 (liberty)
We are glad to announce the release of: oslo.config 1.11.0: Oslo Configuration API For more details, please see the git log history below and: http://launchpad.net/oslo.config/+milestone/1.11.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.config Changes in oslo.config 1.10.0..1.11.0 - 2e32e58 2015-04-16 17:56:05 + Uncap library requirements for liberty Diffstat (except docs and test files) - requirements.txt | 2 +- test-requirements.txt | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index f560a0e..3e21533 100644 --- a/requirements.txt +++ b/requirements.txt @@ -9 +9 @@ six=1.9.0 -stevedore=1.3.0,1.4.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index a23ab6e..27f6050 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -13 +13 @@ testtools=0.9.36,!=1.2.0 -oslotest=1.5.1,1.6.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -22 +22 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -25 +25 @@ oslosphinx=2.5.0,2.6.0 # Apache-2.0 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.context release 0.3.0 (liberty)
We are satisfied to announce the release of: oslo.context 0.3.0: Oslo Context library For more details, please see the git log history below and: http://launchpad.net/oslo.context/+milestone/0.3.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.context Changes in oslo.context 0.2.0..0.3.0 95c031d 2015-04-16 18:02:15 + Uncap library requirements for liberty 6ac5cc2 2015-04-04 02:02:41 -0400 Standardize setup.cfg summary for oslo libs 2d6b2d6 2015-04-03 13:57:40 + Update to latest hacking abfc021 2015-03-26 11:00:56 + Updated from global requirements 7cc81aa 2015-03-05 14:50:48 -0500 fix bug tracker link Diffstat (except docs and test files) - README.rst| 2 +- setup.cfg | 2 +- test-requirements.txt | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) Requirements updates diff --git a/test-requirements.txt b/test-requirements.txt index 7793b38..0d0e2e5 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -5,2 +5,2 @@ -hacking=0.9.1,0.10 -oslotest=1.2.0 # Apache-2.0 +hacking=0.10.0,0.11 +oslotest=1.5.1 # Apache-2.0 @@ -10 +10 @@ coverage=3.6 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.i18n release 0.1.0 (liberty)
We are content to announce the release of: oslo.i18n HEAD: oslo.i18n library For more details, please see the git log history below and: http://launchpad.net/oslo/+milestone/HEAD Please report issues through launchpad: http://bugs.launchpad.net/oslo Changes in oslo.i18n 0.1.0..HEAD 166f4a5 2014-07-13 12:35:19 -0700 Document how to add import exceptions a4fc251 2014-07-13 12:35:15 -0700 Remove mention of Message objects from public docs d648097 2014-06-05 22:20:35 +0200 Setup for translation Diffstat (except docs and test files) - oslo.i18n/locale/oslo.i18n.pot | 29 + oslo/i18n/_gettextutils.py | 5 - oslo/i18n/log.py | 12 +--- 4 files changed, 77 insertions(+), 8 deletions(-) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)
This touches on many of the aspects of the Ops tagging to be discussed in Vancouver. What are the criteria for - An operator to consider a PoC for a new function ? We look for RDO packaging, Puppet configuration and ops/end user documentation. - An operator offering function to their end users in test (I.e. This works well enough to see if there is an end user benefit to justify the operations cost) ? - An operator to offer this in production (I.e. The operator deploys the code and makes it available to the end users) ? This implies scaling, upgradability, etc. and commits to a sustainable roadmap (with the community) I really appreciate the reflections going on here since the worst case scenario for us is that the end users of the cloud become dependent on a component and finding that the community is not self sustaining. Tagging allows the operator to make an informed decision given their user community and assess the risk vs benefit. Tim On 4/21/15, 2:51 PM, Ryan Brown rybr...@redhat.com wrote: On 04/20/2015 07:12 PM, Steve Baker wrote: On 21/04/15 11:01, Angus Salkeld wrote: On Tue, Apr 21, 2015 at 8:38 AM, Fox, Kevin M kevin@pnnl.gov mailto:kevin@pnnl.gov wrote: As an Op, a few things that come to mind in that category are: * RDO packaging (stated earlier). If its not easy to install, its not going to be deployed as much. I haven't installed it yet, because I haven't had time to do much other then yum install it... * Horizon UI * Heat Resources. (Some basic stuff like create/delete queue to go along with the stack. also link #1 below) Here you go: https://github.com/openstack/heat/tree/master/contrib/heat_zaqar One thing we need to do in Vancouver is come up with criteria for moving resources from contrib into the main tree. Previously this was whether the project was integrated. As a starter I would suggest something like: 1. project is in the openstack git namespace 2. the client library is synced with global-requirements.txt 3. the resources are complete enough to be useful in template authoring We need to think about potential for integration testing in the gate too. I think scenario/functional tests should be table stakes to graduate a resource from contrib/ . Horizon has a discovery aspect to it. If users don't know a service is available, its hard for them to use it. Even with the most simple UI of Create/Delete/List queues, discovery is handled. Absolutely agreed. Especially in a service like Zaqar where the vast majority of usage isn't by humans in a web interface, the horizon bit becomes mostly a dashboard/auditing/testing destination instead of a primary interface. [snip] -- Ryan Brown / Software Engineer, Openstack / Red Hat, Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.concurrency release 1.9.0 (liberty)
We are tickled pink to announce the release of: oslo.concurrency 1.9.0: Oslo Concurrency library For more details, please see the git log history below and: http://launchpad.net/oslo.concurrency/+milestone/1.9.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.concurrency Changes in oslo.concurrency 1.8.0..1.9.0 4d7dce2 2015-04-19 01:17:43 +0200 Add binary parameter to execute and ssh_execute c05c8c3 2015-04-18 00:11:28 +0200 Port processutils to Python 3 f366bd2 2015-04-16 17:45:40 + Uncap library requirements for liberty e3c2419 2015-04-10 17:45:03 +0200 Move fixtures to test-requirements.txt fa415de 2015-04-11 00:56:02 +1000 Fix test_as_root* tests to work when run as root d04cf66 2015-04-07 21:09:17 + Add pypi download + version badges fe84d2a 2015-04-04 02:01:33 -0400 Standardize setup.cfg summary for oslo libs e6f5e19 2015-03-24 06:04:39 + Imported Translations from Transifex 9f949fd 2015-03-21 00:16:47 + Updated from global requirements a0549bf 2015-03-20 16:03:21 -0400 Remove tools/run_cross_tests.sh from openstack-common.conf Diffstat (except docs and test files) - README.rst | 10 +- openstack-common.conf | 1 - .../LC_MESSAGES/oslo.concurrency-log-error.po | 32 .../locale/en_GB/LC_MESSAGES/oslo.concurrency.po | 56 --- oslo_concurrency/processutils.py | 52 +- requirements.txt | 7 +- setup.cfg | 2 +- test-requirements.txt | 7 +- 12 files changed, 317 insertions(+), 72 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 1fcebea..cf4758d 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8,4 +8,3 @@ iso8601=0.1.9 -fixtures=0.3.14 -oslo.config=1.9.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index e715139..0fb38b7 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -6 +6 @@ hacking=0.10.0,0.11 -oslotest=1.2.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -8,0 +9 @@ futures=2.1.6 +fixtures=0.3.14 @@ -11 +12 @@ futures=2.1.6 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -14 +15 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -eventlet=0.16.1 +eventlet=0.16.1,!=0.17.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-troveclient release 1.1.0 (liberty)
We are chuffed to announce the release of: python-troveclient 1.1.0: Client library for OpenStack DBaaS API For more details, please see the git log history below. Changes in python-troveclient 1.0.9..1.1.0 -- 738479e 2015-04-16 18:13:46 + Uncap library requirements for liberty 5125628 2015-04-08 09:11:13 + Fixes unit-test in troveclient 0fed50e 2015-03-23 16:12:59 +0900 Add test to DatastoreVersionMembers de77518 2015-03-21 00:18:07 + Updated from global requirements Diffstat (except docs and test files) - requirements.txt | 2 +- test-requirements.txt| 4 +- 7 files changed, 102 insertions(+), 54 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 744bcf9..a87acea 100644 --- a/requirements.txt +++ b/requirements.txt @@ -9 +9 @@ simplejson=2.2.0 -oslo.utils=1.2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index dcbe47a..6c5f39f 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -7,2 +7,2 @@ discover -oslosphinx=2.2.0 # Apache-2.0 -requests-mock=0.5.1 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +requests-mock=0.6.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] stevedore release 1.4.0 (liberty)
We are pleased to announce the release of: stevedore 1.4.0: Manage dynamic plugins for Python applications For more details, please see the git log history below and: https://launchpad.net/python-stevedore/+milestone/1.4.0 Please report issues through launchpad: https://bugs.launchpad.net/python-stevedore Changes in stevedore 1.3.0..1.4.0 - b347780 2015-04-16 18:14:59 + Uncap library requirements for liberty 0e44799 2015-03-21 00:18:26 + Updated from global requirements Diffstat (except docs and test files) - test-requirements.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Requirements updates diff --git a/test-requirements.txt b/test-requirements.txt index 6075428..9d75458 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11,2 +11,2 @@ discover -oslotest=1.2.0 # Apache-2.0 -oslosphinx=2.2.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-cliff release 0.8.0 (liberty)
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Fwd: Integration Gerrit with Launchpad
Heya, On 20 April 2015 at 00:26, Kaneko Takehiro myphone...@gmail.com wrote: Hi, I'm managing a stackforge project and want to integrate Gerrit with Launchpad. Links; Git: https://git.openstack.org/cgit/stackforge/rack/ Launchpad: https://launchpad.net/python-rack Project name 'rack' is duplicated in Launchpad so I named our project 'python-rack'. How can I integrate Gerrit with Launchpad in this case? If rack is more popular and existing lp rack project is dead/dormant (and it looks like it is dormant). One can file a question on launchpad asking to rename and take over the project name, if you wish to have rack name on launchpad. -- Regards, Dimitri. Pura Vida! https://clearlinux.org Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.middleware release 1.1.0 (liberty)
We are overjoyed to announce the release of: oslo.middleware 1.1.0: Oslo Middleware library For more details, please see the git log history below and: http://launchpad.net/oslo.middleware/+milestone/1.1.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.middleware Changes in oslo.middleware 1.0.0..1.1.0 --- 2abb286 2015-04-16 18:06:11 + Uncap library requirements for liberty 027dd34 2015-04-08 18:28:13 -0700 Add CORS Middleware for Oslo. eff065e 2015-04-03 14:03:10 + Update to latest hacking a8f4e82 2015-03-21 00:17:03 + Updated from global requirements Diffstat (except docs and test files) - oslo_middleware/__init__.py| 2 + oslo_middleware/cors.py| 240 + oslo_middleware/opts.py| 7 +- requirements.txt | 6 +- test-requirements.txt | 6 +- 8 files changed, 1028 insertions(+), 7 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 95059c6..b488bbd 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7 +7 @@ Babel=1.3 -oslo.config=1.9.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 @@ -9 +9 @@ oslo.context=0.2.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 @@ -11 +11 @@ six=1.9.0 -stevedore=1.1.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index c5c0328..52cc789 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -6 +6 @@ fixtures=0.3.14 -hacking=0.9.2,0.10 +hacking=0.10.0,0.11 @@ -8,2 +8,2 @@ mock=1.0 -oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-keystoneclient-kerberos release 0.2.0 (liberty)
We are eager to announce the release of: python-keystoneclient-kerberos 0.2.0: Kerberos authentication for the OpenStack clients For more details, please see the git log history below and: http://launchpad.net/python-keystoneclient/+milestone/0.2.0 Please report issues through launchpad: http://bugs.launchpad.net/python-keystoneclient Changes in python-keystoneclient-kerberos 0.1.4..0.2.0 -- adf5897 2015-04-16 18:13:16 + Uncap library requirements for liberty Diffstat (except docs and test files) - requirements.txt | 2 +- test-requirements.txt | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index b604bb6..d598b7d 100644 --- a/requirements.txt +++ b/requirements.txt @@ -6 +6 @@ pbr=0.6,!=0.7,1.0 -python-keystoneclient=1.0.0 +python-keystoneclient=1.1.0 diff --git a/test-requirements.txt b/test-requirements.txt index 4ff26ac..7569eb2 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ python-subunit=0.0.18 -requests-mock=0.5.1 # Apache-2.0 +requests-mock=0.6.0 # Apache-2.0 @@ -12,2 +12,2 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-novaclient release 2.24.0 (liberty)
We are chuffed to announce the release of: python-novaclient 2.24.0: Client library for OpenStack Compute API For more details, please see the git log history below. Changes in python-novaclient 2.23.0..2.24.0 --- ccff3d3 2015-04-20 13:52:38 +0300 Remove all imports from oslo namespace c4d2f92 2015-04-17 05:36:27 + Fix typo on class Client sample 9799353 2015-04-16 18:13:32 + Uncap library requirements for liberty 88beed1 2015-04-01 08:35:39 +0530 Combine test cases for checking nova limits response d614dbc 2015-03-31 20:16:14 +0300 Fix repr of FloatingIPBulk 038c0dc 2015-03-26 16:36:12 +0800 Fix comments on metadata number limitation 4cef067 2015-03-26 12:09:27 +0530 Corrected help for nova boot when attaching block device 0343dff 2015-03-25 12:15:40 +1030 Removes reference to v3 nova api from novaclient docs 1c39f8f 2015-03-21 19:27:36 +0800 Don't record time when self.timing is False 025bcfb 2015-03-21 00:17:56 + Updated from global requirements 8679eed 2015-03-19 22:58:17 +0800 Revert 'Remove image to local block device mapping' Diffstat (except docs and test files) - novaclient/client.py | 29 +++ novaclient/i18n.py | 6 ++-- novaclient/shell.py| 41 ++ .../unit/fixture_data/security_group_rules.py | 2 +- novaclient/utils.py| 26 -- novaclient/v2/client.py| 6 ++-- novaclient/v2/flavors.py | 2 +- novaclient/v2/floating_ips.py | 3 ++ novaclient/v2/floating_ips_bulk.py | 14 +--- novaclient/v2/servers.py | 16 ++--- novaclient/v2/shell.py | 11 +++--- requirements.txt | 6 ++-- test-requirements.txt | 6 ++-- 32 files changed, 198 insertions(+), 105 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index bc729cf..9fe2b95 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7,3 +7,3 @@ iso8601=0.1.9 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.serialization=1.2.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index acdbc24..6790cc6 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11 +11 @@ mock=1.0 -requests-mock=0.5.1 # Apache-2.0 +requests-mock=0.6.0 # Apache-2.0 @@ -13 +13 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -17 +17 @@ testtools=0.9.36,!=1.2.0 -tempest-lib=0.3.0 +tempest-lib=0.4.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-manilaclient release 1.1.0 (liberty)
We are pumped to announce the release of: python-manilaclient 1.1.0: Client library for OpenStack Manila API. For more details, please see the git log history below. Changes in python-manilaclient 1.0.4..1.1.0 --- 163c34f 2015-04-16 18:13:26 + Uncap library requirements for liberty Diffstat (except docs and test files) - requirements.txt | 6 +++--- test-requirements.txt | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index b973fc0..64a94ff 100644 --- a/requirements.txt +++ b/requirements.txt @@ -10,3 +10,3 @@ iso8601=0.1.9 -oslo.config=1.9.3,1.10.0 # Apache-2.0 -oslo.serialization=1.4.0,1.5.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index cdd51e7..5935882 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -14 +14 @@ ordereddict -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.log release 1.1.0 (liberty)
We are thrilled to announce the release of: oslo.log 1.1.0: oslo.log library For more details, please see the git log history below and: http://launchpad.net/oslo.log/+milestone/1.1.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.log Changes in oslo.log 1.0.0..1.1.0 a45d56c 2015-04-16 18:04:22 + Uncap library requirements for liberty 33f051f 2015-03-25 20:40:47 + Add link to Logging Guidelines 8ad47ba 2015-03-25 19:24:20 + Expose opts entry point for version_utils fd58202 2015-03-25 19:24:20 + Switch from oslo.config to oslo_config 2d46053 2015-03-25 19:24:20 + Remove oslo.log code and clean up versionutils API 0a512b9 2015-03-25 19:24:20 + Remove code that moved to oslo.i18n f635dbd 2015-03-25 19:24:20 + Enhance versionutils.deprecated to work with classes 93db0ec 2015-03-25 19:24:20 + Add Kilo release name to versionutils 7f263be 2015-03-25 19:24:20 + Allow deprecated decorator to specify no plan for removal 14d1d9e 2015-03-25 19:24:20 + Add JUNO as a target to versionutils module 30e7c5b 2015-03-25 19:24:20 + pep8: fixed multiple violations 7bee814 2015-03-25 19:24:20 + Use oslotest instead of common test module 54d64a0 2015-03-25 19:24:20 + Use hacking import_exceptions for gettextutils._ 0e829c0 2015-03-25 19:24:20 + fixed typos e141593 2015-03-25 19:24:20 + Fix violations of H302:import only modules 3e3c7bb 2015-03-25 19:24:20 + Adds decorator to deprecate functions and methods f6923e3 2015-03-25 19:24:20 + Remove vim header ce726f1 2015-03-25 19:24:20 + Add `versionutils` for version compatibility checks 7f6db3a 2015-03-21 08:23:17 -0500 Default to True for use-syslog-rfc-format 68af49e 2015-03-21 00:16:58 + Updated from global requirements c084b9d 2015-03-10 14:38:40 + Restore automatic unicode conversion 35e51bc 2015-03-10 13:56:27 + Add migration notes Diffstat (except docs and test files) - openstack/common/versionutils.py | 260 +++ oslo_log/_options.py | 8 +- oslo_log/log.py | 17 +++ requirements.txt | 8 +- test-requirements.txt| 4 +- 8 files changed, 730 insertions(+), 12 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 54ada9b..f38fc04 100644 --- a/requirements.txt +++ b/requirements.txt @@ -9 +9 @@ iso8601=0.1.9 -oslo.config=1.9.0 # Apache-2.0 +oslo.config=1.9.3 # Apache-2.0 @@ -11,3 +11,3 @@ oslo.context=0.2.0 # Apache-2.0 -oslo.i18n=1.3.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 -oslo.serialization=1.2.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 0fab2b3..b551d65 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -13 +13 @@ testtools=0.9.36,!=1.2.0 -oslotest=1.2.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -22 +22 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!
On 04/20/2015 04:39 PM, Sukhdev Kapur wrote: Hi Ramy, While I agree, in principal, with this line of thinking and goal, my concern will be how much extra work is it going to create for existing CI owners? Our Ci system has been stable for a long time, and we put in a good amount of effort to get it to that point. Our CI is not based upon zuul framework. Zuul was still under discussion at the time when we put together our CI. We use Jenkins as front end, along with Gerrit triggers, and AWS for posting/preserving results/log. We have dedicated back-end servers for testing. My paranoia at this point will be to learn a new framework, risk breaking things and taking a huge effort to get things stabilized - without much additional ROI. Am I overreacting here or does my argument makes sense? I wonder how many folks will be in that camp? Sukhdev Hi Sukhdev: What is being offered is an opportunity to pool efforts for those who wish to participate. There is no pressure to participate if you are concerned that you would compromise the integrity of a stable system. You and others that have put in so much work are to be lauded for your commitment to your goal, thank you. Ramy's efforts in no way are an attempt to degrade the stability you have created. Part of the exhaustion level folks feel in this space, at all points in the spectrum, is the cost of maintenance. In infra we are constantly dealing with problems from operators and it would reduce the burden on us, as well as reduce the tension on operators, if we had a solution that was easier to maintain. The more people running the same structure, the easier any one issue is to solve (hopefully). The goal is once the structure is in place that OpenStack's Infra would also consume it, enabling common bugs to be discovered and fixed upstream. Noone is forced to participate nor are they going to be forced to operate this structure. This is simply a chance to work together on a direction which infra would very much like to see in place. Thanks Sukhdev, Anita. On Sun, Apr 19, 2015 at 10:17 PM, Asselin, Ramy ramy.asse...@hp.com wrote: All Third-Party CI operators: We’ve got 85 Third Party CI systems registered in the wiki[1], all of them running a variety of closed open-source solutions. Instead of individually maintaining all those similar solutions, let’s join together and collectively maintain a single solution. If that sounds good to you, there’s an Infra-spec that’s been approved [2] to refactor much of what the Infrastructure team uses for the upstream “Jenkins” CI to be more easily reusable by many of us. We’ve got stories defined [3], and a few patches submitted. We’re using the gerrit-topic “downstream-puppet” [4]. For example, we’ve got the first part under review for the “Log Server”, which creates your own version of http://logs.openstack.org/ If anyone is interested in migrating towards a common solution, reply, or ping me IRC (asselin) on Freenode #openstack-infra, or join some of the third party ci meetings [5]. Thanks! Ramy [1] https://wiki.openstack.org/wiki/ThirdPartySystems [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html [3] https://storyboard.openstack.org/#!/story/2000101 [4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z [5] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Nova] Reviewers please watch the check-tempest-dsvm-cells job now
It's been a long road but due to the hard work of bauzas and melwitt the cells Tempest check job should now be green for changes that don't break cells. The job has been red for a long time so it's likely that people don't think about it much. I would ask that until we can get the confidence to make it voting please take notice when it's red and investigate or bring it to the attention of one of us in #openstack-nova. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.serialization release 1.5.0 (liberty)
We are satisfied to announce the release of: oslo.serialization 1.5.0: Oslo Serialization library For more details, please see the git log history below and: http://launchpad.net/oslo.serialization/+milestone/1.5.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.serialization Changes in oslo.serialization 1.4.0..1.5.0 -- 6665672 2015-04-16 11:27:46 -0700 Expose base msgpack exceptions so users don't need to import b2c235e 2015-04-16 18:08:08 + Uncap library requirements for liberty 4ada51b 2015-04-14 21:09:14 + More docstring cleanups/tweaks 58c1f29 2015-04-14 14:08:23 -0700 Add docstring(s) to handler registry(s) 5b4e919 2015-04-07 18:16:48 -0700 Add pypi download + version badges d6782d9 2015-04-04 02:25:32 -0400 Cleanup README.rst and setup.cfg c7898c2 2015-03-31 17:29:41 -0700 Make the msgpackutils handlers more extendable ef8657f 2015-03-21 00:17:09 + Updated from global requirements Diffstat (except docs and test files) - README.rst | 11 +- oslo_serialization/jsonutils.py| 16 +- oslo_serialization/msgpackutils.py | 380 +++-- requirements.txt | 2 +- setup.cfg | 2 +- test-requirements.txt | 6 +- 9 files changed, 330 insertions(+), 131 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 06e2755..ff4e573 100644 --- a/requirements.txt +++ b/requirements.txt @@ -17 +17 @@ iso8601=0.1.9 -oslo.utils=1.2.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index af6a92e..ee6d133 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ sphinx=1.1.2,!=1.2.0,!=1.3b1,1.3 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 @@ -12 +12 @@ oslosphinx=2.2.0 # Apache-2.0 -oslotest=1.2.0 # Apache-2.0 +oslotest=1.5.1 # Apache-2.0 @@ -14 +14 @@ simplejson=2.2.0 -oslo.i18n=1.3.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] oslo.versionedobjects release 0.2.0 (liberty)
We are excited to announce the release of: oslo.versionedobjects 0.2.0: Oslo Versioned Objects library For more details, please see the git log history below and: http://launchpad.net/oslo.versionedobjects/+milestone/0.2.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.versionedobjects Changes in oslo.versionedobjects 0.1.1..0.2.0 - 23d15eb 2015-04-16 18:10:19 + Uncap library requirements for liberty cfe2cd7 2015-04-04 02:05:55 -0400 Standardize setup.cfg summary for oslo libs 29ac0fc 2015-04-03 14:08:13 + Update to the latest version of hacking ae5558f 2015-03-28 11:16:59 -0400 Copy the default value for field 2ccb13a 2015-03-21 00:17:16 + Updated from global requirements 1a6bea7 2015-03-19 13:57:45 -0400 New config group for oslo_versionedobjects Diffstat (except docs and test files) - oslo_versionedobjects/__init__.py | 13 -- oslo_versionedobjects/base.py | 7 +++-- oslo_versionedobjects/exception.py | 8 +++--- oslo_versionedobjects/fields.py | 3 ++- requirements-py3.txt| 21 --- requirements.txt| 19 -- setup.cfg | 2 +- test-requirements.txt | 9 --- tox.ini | 2 +- 10 files changed, 78 insertions(+), 46 deletions(-) Requirements updates diff --git a/requirements-py3.txt b/requirements-py3.txt index dd838b4..b24d76c 100644 --- a/requirements-py3.txt +++ b/requirements-py3.txt @@ -1,2 +1,5 @@ -eventlet=0.16.1 -six=1.7.0 +# The order of packages is significant, because pip processes them in the order +# of appearance. Changing the order has an impact on the overall integration +# process, which may cause wedges in the gate later. +eventlet=0.16.1,!=0.17.0 +six=1.9.0 @@ -4,5 +7,5 @@ Babel=1.3 -oslo.concurrency=1.4.1 # Apache-2.0 -oslo.context=0.1.0 # Apache-2.0 -oslo.messaging=1.4.0,!=1.5.0 -oslo.serialization=1.2.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.concurrency=1.8.0 # Apache-2.0 +oslo.context=0.2.0 # Apache-2.0 +oslo.messaging=1.8.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 @@ -10,2 +13,2 @@ iso8601=0.1.9 -oslo.log=0.1.0 -oslo.i18n=1.3.0 # Apache-2.0 +oslo.log=1.0.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 diff --git a/requirements.txt b/requirements.txt index 87ccf48..c889c07 100644 --- a/requirements.txt +++ b/requirements.txt @@ -1 +1,4 @@ -six=1.7.0 +# The order of packages is significant, because pip processes them in the order +# of appearance. Changing the order has an impact on the overall integration +# process, which may cause wedges in the gate later. +six=1.9.0 @@ -3,5 +6,5 @@ Babel=1.3 -oslo.concurrency=1.4.1 # Apache-2.0 -oslo.context=0.1.0 # Apache-2.0 -oslo.messaging=1.4.0,!=1.5.0 -oslo.serialization=1.2.0 # Apache-2.0 -oslo.utils=1.2.0 # Apache-2.0 +oslo.concurrency=1.8.0 # Apache-2.0 +oslo.context=0.2.0 # Apache-2.0 +oslo.messaging=1.8.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 @@ -9,2 +12,2 @@ iso8601=0.1.9 -oslo.log=0.1.0 -oslo.i18n=1.3.0 # Apache-2.0 +oslo.log=1.0.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 8915308..368b46b 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,2 +1,5 @@ -hacking=0.5.6,0.8 -oslotest=1.2.0 # Apache-2.0 +# The order of packages is significant, because pip processes them in the order +# of appearance. Changing the order has an impact on the overall integration +# process, which may cause wedges in the gate later. +hacking=0.10.0,0.11 +oslotest=1.5.1 # Apache-2.0 @@ -5 +8 @@ testtools=0.9.36,!=1.2.0 -oslosphinx=2.2.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-ceilometerclient release 1.2.0 (liberty)
We are delighted to announce the release of: python-ceilometerclient 1.2.0: OpenStack Telemetry API Client Library For more details, please see the git log history below. Changes in python-ceilometerclient 1.1.0..1.2.0 --- 220371b 2015-04-16 18:12:50 + Uncap library requirements for liberty 16880fc 2015-04-02 18:43:25 +0800 print user friendly error message for alarm update time constraints Diffstat (except docs and test files) - ceilometerclient/v2/alarms.py | 5 +++-- requirements.txt | 8 test-requirements.txt | 2 +- 4 files changed, 25 insertions(+), 7 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 6ff32c2..bbeb1b6 100644 --- a/requirements.txt +++ b/requirements.txt @@ -7,3 +7,3 @@ iso8601=0.1.9 -oslo.i18n=1.5.0,1.6.0 # Apache-2.0 -oslo.serialization=1.4.0,1.5.0 # Apache-2.0 -oslo.utils=1.4.0,1.5.0 # Apache-2.0 +oslo.i18n=1.5.0 # Apache-2.0 +oslo.serialization=1.4.0 # Apache-2.0 +oslo.utils=1.4.0 # Apache-2.0 @@ -14 +14 @@ six=1.9.0 -stevedore=1.3.0,1.4.0 # Apache-2.0 +stevedore=1.3.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 953bfe9..99e1c7c 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -10 +10 @@ mock=1.0 -oslosphinx=2.5.0,2.6.0 # Apache-2.0 +oslosphinx=2.5.0 # Apache-2.0 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [release] python-openstackclient release 1.1.0 (liberty)
We are gleeful to announce the release of: python-openstackclient 1.1.0: OpenStack Command-line Client For more details, please see the git log history below and: https://launchpad.net/python-openstackclient/+milestone/1.1.0 Please report issues through launchpad: https://bugs.launchpad.net/python-openstackclient Changes in python-openstackclient 1.0.3..1.1.0 -- 3c7b518 2015-04-20 11:23:15 -0600 Handle the pagination for image list 3284384 2015-04-20 06:04:10 + Imported Translations from Transifex 00eeb35 2015-04-19 02:41:04 -0400 remove unnecessary conditionals e85971b 2015-04-19 01:43:40 -0400 Update the docs for new nic options 6e70139 2015-04-18 23:04:53 -0500 Begin documenting --os-cloud 5649695 2015-04-18 23:04:51 -0500 Add --os-cloud support 0e61e5f 2015-04-18 06:04:12 + Imported Translations from Transifex 6c4f815 2015-04-17 13:37:44 -0400 Re-organize functional tests 4c107e6 2015-04-17 10:14:57 -0700 Role operations should not require list object permission 15bc2cc 2015-04-17 07:54:05 -0600 Print warning on authentication error d363068 2015-04-17 14:20:37 +0200 Fix skipped image create attribute location attr 5780606 2015-04-16 18:13:36 + Uncap library requirements for liberty f43c1f7 2015-04-15 22:40:52 -0500 Defer client imports 459526e 2015-04-15 21:17:00 -0400 Better help for --nic in create server 8bd8a8d 2015-04-15 01:42:00 -0400 Add support to specify volume quotas per volume type a0fe37e 2015-04-13 16:21:50 -0600 Add warning message if unknown version supplied 0d68987 2015-04-07 23:53:31 -0700 Fix session timing 77e3fba 2015-04-03 02:26:22 -0400 Add support for showing limits of a specific project ec4ef5f 2015-04-02 12:59:34 -0500 Suppress warnings user can't fix e60bf28 2015-04-02 11:21:07 +1100 Use glanceclient's inbuilt images find f6bd2fa 2015-03-31 18:38:53 + Updated from global requirements 894fe6c 2015-03-31 06:05:13 + Imported Translations from Transifex 6a9d6af 2015-03-30 11:53:17 -0400 Add support to remote_id 6c224f5 2015-03-19 23:49:02 -0700 Add project and domain params to network create 7628510 2015-03-19 14:02:50 -0400 Add a doc about authenticating against v3 6214344 2015-03-19 13:54:19 -0400 Add the ability to set and unset flavor properties 8e92dfc 2015-03-17 23:44:53 +0100 Use cliff deferred help instead of homemade one a9d1e3d 2015-03-11 19:16:18 +1100 Base TokenEndpoint plugin on keystoneclient's be3cbd2 2014-11-14 17:01:49 -0600 Look harder to find DevStack Diffstat (except docs and test files) - examples/common.py | 8 + examples/object_api.py | 17 +- examples/osc-lib.py| 14 +- functional/harpoon.sh | 9 +- openstackclient/api/auth.py| 166 +++-- openstackclient/api/auth_plugin.py | 21 +- openstackclient/common/clientmanager.py| 24 +- openstackclient/common/limits.py | 29 +- openstackclient/common/quota.py| 12 +- openstackclient/common/session.py | 50 ++ openstackclient/common/timing.py | 10 +- openstackclient/compute/client.py | 20 +- openstackclient/compute/v2/flavor.py | 78 ++- openstackclient/compute/v2/server.py | 11 +- openstackclient/identity/common.py | 59 +- openstackclient/identity/v3/group.py | 7 +- openstackclient/identity/v3/identity_provider.py | 68 +- openstackclient/identity/v3/project.py | 3 +- openstackclient/identity/v3/role.py| 81 +-- openstackclient/identity/v3/role_assignment.py | 17 +- openstackclient/identity/v3/trust.py | 9 +- openstackclient/identity/v3/user.py| 9 +- openstackclient/image/client.py| 56 +- openstackclient/image/v1/image.py | 14 +- openstackclient/image/v2/image.py | 12 +- openstackclient/network/v2/network.py | 21 + openstackclient/shell.py | 115 +-- openstackclient/volume/client.py | 20 +- .../de/LC_MESSAGES/python-openstackclient.po | 266 --- .../locale/python-openstackclient.pot | 226 +++--- .../zh_TW/LC_MESSAGES/python-openstackclient.po| 767 + requirements.txt | 15 +- setup.cfg | 2 + test-requirements.txt | 6 +- 68 files changed, 3145 insertions(+), 1139 deletions(-) Requirements updates diff --git a/requirements.txt b/requirements.txt index 97d06c4..b8712eb 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8 +8 @@ Babel=1.3 -cliff=1.7.0 # Apache-2.0 +cliff=1.10.0 # Apache-2.0 @@ -10,4 +10,5 @@
Re: [openstack-dev] [all][releases] upcoming library releases to unfreeze requirements in master
Excerpts from Doug Hellmann's message of 2015-04-21 13:11:09 -0400: I'm working on releasing a *bunch* of libraries, including clients, from their master branches so we can thaw the requirements list for the liberty cycle. As with any big operation, this may be disruptive. I apologize in advance if it is, but we cannot thaw the requirements without making the releases so we need them all. Here's the full list, in the form of the release script I am running, in case you start seeing issues and want to check if you were affected: OK, this is all done. I have verified that all of the libraries are on PyPI and I have sent the release notes (sometimes several copies, at no extra charge to you -- seriously, sorry about the noise). Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [docs] Networking Guide Doc Day - April 23rd
Nice idea. Looked at the TOC page, pretty much covering variants of neutron nuts bolts. Shall we include DNS into TOC somewhere? Regards, Yatin On Tue, Apr 21, 2015 at 10:22 AM, Guo, Ruijing ruijing@intel.com wrote: Hi, Edgar Some docs are still in private branch. Can we move to public branch for reviewing submitting patches? Thanks, -Ruijing *From:* Edgar Magana [mailto:edgar.mag...@workday.com] *Sent:* Saturday, April 18, 2015 2:25 AM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* [openstack-dev] [neutron] [docs] Networking Guide Doc Day - April 23rd Hello Folks, I would like to invite all available contributors to help us to complete the OpenStack Networking Guide. We are having a Networking Doc Day on April 23rd in order to review the current guide and make a big push on its content. Let’s use both the Neutron and Docs IRC channels: #openstack-neutron #openstack-doc All the expected content is being described in the TOC: https://wiki.openstack.org/wiki/NetworkingGuide/TOC Information for Doc contributors in here: https://wiki.openstack.org/wiki/Documentation/HowTo#Edit_OpenStack_RST_and.2For_DocBook_documentation We have prepared an etherpad to coordinate who is doing what: https://etherpad.openstack.org/p/networking-guide There are so many ways you can contribute: - Assign to yourself one of the available chapters - Review the current content and open bugs if needed - Review the existing gerrit commit if you are familiar with the information - Be available on IRC to answer some questions about configuration details or functionality - Cheering at the contributors! Do not hesitate in contacting me for any questions. Cheers! Edgar Magana IRC: emagana emag...@gmail.com edgar.mag...@workday.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] TC Candidacy
confirmed On 04/21/2015 04:47 AM, Flavio Percoco wrote: Greetings, I'm announcing my candidacy for the Technical Comitee Elections. I wish I could say I've served as a TC member before but I haven't. However, there's always a first time for everything, isn't there? I'd like for Liberty to be that chance for me to be honored with a seat in OpenStack's Technical Comitee. I believe I've been part of OpenStack's community long enough to know how it works, the mechanisms behind it and I believe I have a good feeling of where it should be headed. Here are some things that I'd love to help achieving as part of my work as a TC member: # Paradise's doors have been opened but no maps of it have been drawn: During the last cycles, the TC members have done an amazing job on helping make our community more welcoming. The bar for inclusion has be lowered to the point where projects are welcomed to join it as long as they meet the minimum requirements established in our governance repo. I believe this is an amazing step for our community but we're not there yet. Unfortunately, opening our doors does not do the trick. In order to keep this openness honest, we also need to provide a better support for the projects that are joining our community. Therefore, I'd like to help moving the big tent effort forward and start laying down the bases that will help providing support to projects and guide them especially in moments where decisions like this[0] need to be taken. [0] http://lists.openstack.org/pipermail/openstack-dev/2015-April/061967.html # Help with clearing the path where OpenStack is headed For better or for worse, one of the question I've been asked more often, in the last couple of months, is: Is OpenStack there yet? What's next? OpenStack is a cloud provider and as such it should strive to cover enough use-cases to make cloud consumers'/providers' lives simpler. There's more to a cloud than just compute, storage and networking. There's more to cloud than just orchestration and meetering. As part of my role as a TC member, I'd like to help our community grow in other areas that might not be considered required but that are still important for our mission. # Deployments / Ops OpenStack has come a long way on making deployments easier but again, we're not there yet. With the new governance model, we won't just see new *aaS services joining but also new tools[0] that are meant to help with OpenStack's installation and maintenance. Along the lines of what I said in my point #2, I believe having tools to install OpenStack is great but there's more to an OpenStack deployment than just that. There's monitoring, upgrades, migrations, etc. As part of my journey as a TC member (hopefully), I'd like to help these projects by exploring and gathering the needs and feedback from our community so we can guide these amazing efforts towards the right solution that OpenStack needs. I believe OpenStack is taking giant steps towards a great success but we need to be careful not to skip important things in between those steps. I'd like to use my knowledge from my involvement in several areas throughout OpenStack (and outside it) to help OpenStack moving forward at the same - or at a better - pace. Thanks for your consideration, Flavio P.S: If you're thinking. Wait, this guy is nuts. He ran for 2 PTL positions and he now wants to run for a TC position. Is he crazy? One answer to that could be, Yes. However, just to make sure it's clear to everyone my current time situation, I'd like to share that I'm just Zaqar's PTL - Nikhil is Glance's PTL - and my current commitments allow me for dedicating to this position the time it requires. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: OpenPGP digital signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)
On 04/20/2015 07:12 PM, Steve Baker wrote: On 21/04/15 11:01, Angus Salkeld wrote: On Tue, Apr 21, 2015 at 8:38 AM, Fox, Kevin M kevin@pnnl.gov mailto:kevin@pnnl.gov wrote: As an Op, a few things that come to mind in that category are: * RDO packaging (stated earlier). If its not easy to install, its not going to be deployed as much. I haven't installed it yet, because I haven't had time to do much other then yum install it... * Horizon UI * Heat Resources. (Some basic stuff like create/delete queue to go along with the stack. also link #1 below) Here you go: https://github.com/openstack/heat/tree/master/contrib/heat_zaqar One thing we need to do in Vancouver is come up with criteria for moving resources from contrib into the main tree. Previously this was whether the project was integrated. As a starter I would suggest something like: 1. project is in the openstack git namespace 2. the client library is synced with global-requirements.txt 3. the resources are complete enough to be useful in template authoring We need to think about potential for integration testing in the gate too. I think scenario/functional tests should be table stakes to graduate a resource from contrib/ . Horizon has a discovery aspect to it. If users don't know a service is available, its hard for them to use it. Even with the most simple UI of Create/Delete/List queues, discovery is handled. Absolutely agreed. Especially in a service like Zaqar where the vast majority of usage isn't by humans in a web interface, the horizon bit becomes mostly a dashboard/auditing/testing destination instead of a primary interface. [snip] -- Ryan Brown / Software Engineer, Openstack / Red Hat, Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] neutron DB upgrade
On 21 April 2015 at 14:25, Guo, Ruijing ruijing@intel.com wrote: Somebody can help me to understand why neutron DB is needed upgrade even in refresh installation unlike other components. From my understanding, DB upgrade is risky and needed when upgrade. Alembic is a fairly reliable tool for managing DB upgrades. Also there are enough tests in place to ensure the sanity of each db migration and that the DB schema is always in sync with business logic's data model. Release A should have schema A and Release B should have schema B. This will make really difficult doing testing during the development cycle. While all interim migrations added during the release cycle can be squashed into a single migration provided at release time, this action will probably transform a relatively safe process into a risky one, as there will be little time to react to issues introduced by that single migration. Only upgrade A to B need to upgrade DB. This is what happens for most users. However there still are a few which more or less closely follow trunk - that is to say they're not tied to any specific release. Also, this does not apply to developers and CI (which is ultimately one of the principal tools we use to ensure what we deliver is not completely rubbish). In the same time, can we separate neutron DB as vendor DB non-vendor DB? We had vendor or plugin specific migrations until Juno. When he had these kind of conditional migrations doing DB upgrades was very risky. DB schema management has become a lot simpler and safer since we unified the schema. However, as a part of the vendor plugin split out there will be eventually a next step where all vendor-specific tables are moved into their own dbs. Are tables for plugins which are not ML2 causing you any problem? 1. For that case, we can upgrade vendor DB if we use some vendor scenario. 2. we already separate vendor code from neutron code base. Thanks, -Ruijing __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] neutron DB upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/21/2015 02:25 PM, Guo, Ruijing wrote: Somebody can help me to understand why neutron DB is needed upgrade even in refresh installation unlike other components. refresh installation == minor version upgrade for a stable release? No, it should not require db upgrade, it's forbidden to backport patches that involve db migration to stable releases. From my understanding, DB upgrade is risky and needed when upgrade. Release A should have schema A and Release B should have schema B. Only upgrade A to B need to upgrade DB. In the same time, can we separate neutron DB as vendor DB non-vendor DB? Not sure what you mean. Neutron does not distinguish between deployment scenarios in terms of db schema. It's always the same (at least that's the case since Juno). /Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVNkrxAAoJEC5aWaUY1u576fAIAOMjencFLoSVfYv/1sJgds2W 5mPdQM5yMlGHR18fI9FSjA41BItOsPknppl9YtwrxNHN3h8VyTWDkSSQanMBDfgE jkGEP2NG6ZFIfCQHwKTJ8c3VPxPEVBc0k4Nj6qC2mC1Rp4gIqGkmTFuo5xK9jm0g C0qqZzNzh7yag0yKFb6XM/2mkk/DReMIqVJQ3WkIBim8EfAq/CXrZsxkz33mj0wn G9uWtKEnmi0/U2/ZLrNcGSVTiHsj3qtBYSW/cPZOhjPcCAynYJmKcR56ipwe8CXk 3mQcsQWQpeNuW5tX6LMnImDrVdEEnulT2W/2PCZtYgQgTfswfmF/mSr4/s2Ogm4= =yVaY -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)
On 21/04/15 08:51 -0400, Ryan Brown wrote: On 04/20/2015 07:12 PM, Steve Baker wrote: Absolutely agreed. Especially in a service like Zaqar where the vast majority of usage isn't by humans in a web interface, the horizon bit becomes mostly a dashboard/auditing/testing destination instead of a primary interface. The above sounds correct to me for most of the cases. However, I can see horizon being used to configured notifications/subscriptions. Cheers, Flavio -- @flaper87 Flavio Percoco pgpotm7AjKs5M.pgp Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [mistral] Break_on in Retry policy
Any more suggestions/thoughts here? Dmitri? More words: succeed-on / fail-on, success-expr / error-expr. -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Are routed TAP interfaces (and DHCP for them) in scope for Neutron?
Is it compatible with overlapping IPs? i.e. Will it give two different VMs the same IP address if the reservations are setup that way? If not, this approach won't work for many use cases so I think you will probably just have to write a new DHCP agent that operates in this distributed fashion. I haven't yet had any responses to this, so reflagging it in case it was just missed in the helter skelter of activity that is the openstack-dev mailing list... On the other hand, if I need to describe more clearly what I'm on about, please don't be afraid to say that! Any comments and steer would be appreciated, even if they're more of a high level gut feel, than an exhaustive treatment. Thanks, Neil On 16/04/15 15:12, Neil Jerram wrote: I have a Neutron DHCP agent patch whose purpose is to launch dnsmasq with options such that it works (= provides DHCP service) for TAP interfaces that are _not_ bridged to the DHCP interface (ns-XXX). For the sake of being concrete, this involves: - creating the ns-XXX interface as a dummy, instead of as a veth pair - launching dnsmasq with --bind-dynamic --listen=ns-XXX --listen=tap* --bridge-interface=ns-XXX,tap* - not running in a separate namespace - running the DHCP agent on every compute host, instead of only on the network node - using the relevant subnet's gateway IP on the ns-XXX interface (on every host), instead of allocating a different IP for each ns-XXX interface. I proposed a spec for this in the Kilo cycle [1], but it didn't get enough traction, and I'm now wondering what to do with this work/function. Specifically, whether to look again at integrating it into Neutron during the Liberty cycle, or whether to maintain an independent DHCP agent for my project outside the upstream Neutron tree. I would very much appreciate any comments or advice on this. For answering that last question, I suspect the biggest factor is whether routed TAP interfaces - i.e. forms of networking implementation that rely on routing data between VMs instead of bridging it - is in scope for Neutron, at all. If it is, I understand that there could be a lot more detail to work on, such as how it meshes with other Neutron features such as DVR and the IPAM work, and that it might end up being quite different from the blueprint linked below. But it would be good to know whether this would ultimately be in scope and of interest for Neutron at all. Please do let me now what you think. Many thanks, Neil [1] https://blueprints.launchpad.net/neutron/+spec/dhcp-for-routed-ifs __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance] Why no DB index on sort parameters
On 21/04/15 12:17 +0530, Ajaya Agrawal wrote: Hi All, I see that glance supports arbitrary sort parameters and the default is created_at while listing images. Is there any reason why we don't have index over these fields? If we have an index over these fields then we would avoid a full table scan to do sorting. IMO at least the created_at field should have an index on it. I don't think there's an actual reason, OTOH. I'd recommend proposing a patch and wait for the reviews there. :) Flavio -- @flaper87 Flavio Percoco pgp3yiNZiCDnJ.pgp Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)
On 20/04/15 13:39 -0700, Vipul Sabhaya wrote: On Mon, Apr 20, 2015 at 12:07 PM, Fox, Kevin M kevin@pnnl.gov wrote: Another parallel is Manilla vs Swift. Both provides something like a share for users to store files. The former is a multitenant api to provision non multitenant file shares. The latter is a multitenant api to provide file sharing. Cue is a multitenant api to provision non multitenant queues. Zaqar is an api for a multitenant queueing system. They are complimentary services. Agreed, it’s not an either/or, there is room for both. While Cue could provision Zaqar, it doesn’t make sense, since it is already multi-tenant. As has been said, Cue’s goal is to bring non-multi-tenant message brokers to the cloud. On the question of adoption, what confuses me is why the measurement of success of a project is whether other OpenStack services are integrating or not. Zaqar exposes an API that seems best fit for application workloads running on an OpenStack cloud. The question should be raised to operators as to what’s preventing them from running Zaqar in their public cloud, distro, or whatever. Looking at other services that we consider to be successful, such as Trove, we did not attempt to integrate with other OpenStack projects. Rather, we solved the concerns that operators had. FWIW, the team is not messuring the success of the project on whether it's integrated with other services or not. The adoption in all possible areas play key parts in every project's life. While it's amazing that RDO - and I believe Ubuntu is packaging too, Zigo, correct me, pls - has support for it, I don't think that's enough for the project to go anywhere. The use cases of this project, from a *provider* point of view are very specific - you either want to sell/use queues or you don't - and similar to SQS's. The fact that many folks miss is that SQS itself is being used *internally* in AWS for other things that I'm not going to get into. This is true not just for SQS, SNS but also for several other services they provide. Thankfully enough, we've folloed the same lead of using the things we've created. For instance, Trove uses nova for vms, Nova uses Cinder for block devices, etc, etc, etc. This needs to happen for Zaqar too. This will help the project mature with feedback from the real world. This will give deployers enough confidence that the project is needed and it'll also drive some attention towards the project. Comparing Trove and Zaqar as services won't, ever, give a good result. They have different uses-cases, users base and types of APIs - data vs control. Not to mention they both went through different processes in very different periods of our community (Integrated/big tent, etc). Flavio Thanks, Kevin From: Ryan Brown [rybr...@redhat.com] Sent: Monday, April 20, 2015 11:38 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?) On 04/20/2015 02:22 PM, Michael Krotscheck wrote: What's the difference between openstack/zaqar and stackforge/cue? Looking at the projects, it seems like zaqar is a ground-up implementation of a queueing system, while cue is a provisioning api for queuing systems that could include zaqar, but could also include rabbit, zmq, etc... If my understanding of the projects is correct, the latter is far more versatile, and more in line with similar openstack approaches like trove. Is there a use case nuance I'm not aware of that warrants duplicating efforts? Because if not, one of the two should be retired and development focused on the other. Note: I do not have a horse in this race. I just feel it's strange that we're building a thing that can be provisioned by the other thing. Well, with Trove you can provision databases, but the MagnetoDB project still provides functionality that trove won't. The Trove : MagnetoDB and Cue : Zaqar comparison fits well. Trove provisions one instance of X (some database) per tenant, where MagnetoDB is one instance (collection of hosts to do database things) that serves many tenants. Cue's goal is I have a not-very-multitenant message bus (rabbit, or whatever) and makes that multitenant by provisioning one per tenant, while Zaqar has a single install (of as many machines as needed) to support messaging for all cloud tenants. This enables great stuff like cross-tenant messaging, better physical resource utilization in sparse-tenant cases, etc. As someone who wants to adopt Zaqar, I'd really like to see it continue as a project because it provides things other message broker approaches don't. -- Ryan Brown / Software Engineer, Openstack / Red Hat, Inc. __ OpenStack Development Mailing List (not for
[openstack-dev] TC Candidacy
Greetings, I'm announcing my candidacy for the Technical Comitee Elections. I wish I could say I've served as a TC member before but I haven't. However, there's always a first time for everything, isn't there? I'd like for Liberty to be that chance for me to be honored with a seat in OpenStack's Technical Comitee. I believe I've been part of OpenStack's community long enough to know how it works, the mechanisms behind it and I believe I have a good feeling of where it should be headed. Here are some things that I'd love to help achieving as part of my work as a TC member: # Paradise's doors have been opened but no maps of it have been drawn: During the last cycles, the TC members have done an amazing job on helping make our community more welcoming. The bar for inclusion has be lowered to the point where projects are welcomed to join it as long as they meet the minimum requirements established in our governance repo. I believe this is an amazing step for our community but we're not there yet. Unfortunately, opening our doors does not do the trick. In order to keep this openness honest, we also need to provide a better support for the projects that are joining our community. Therefore, I'd like to help moving the big tent effort forward and start laying down the bases that will help providing support to projects and guide them especially in moments where decisions like this[0] need to be taken. [0] http://lists.openstack.org/pipermail/openstack-dev/2015-April/061967.html # Help with clearing the path where OpenStack is headed For better or for worse, one of the question I've been asked more often, in the last couple of months, is: Is OpenStack there yet? What's next? OpenStack is a cloud provider and as such it should strive to cover enough use-cases to make cloud consumers'/providers' lives simpler. There's more to a cloud than just compute, storage and networking. There's more to cloud than just orchestration and meetering. As part of my role as a TC member, I'd like to help our community grow in other areas that might not be considered required but that are still important for our mission. # Deployments / Ops OpenStack has come a long way on making deployments easier but again, we're not there yet. With the new governance model, we won't just see new *aaS services joining but also new tools[0] that are meant to help with OpenStack's installation and maintenance. Along the lines of what I said in my point #2, I believe having tools to install OpenStack is great but there's more to an OpenStack deployment than just that. There's monitoring, upgrades, migrations, etc. As part of my journey as a TC member (hopefully), I'd like to help these projects by exploring and gathering the needs and feedback from our community so we can guide these amazing efforts towards the right solution that OpenStack needs. I believe OpenStack is taking giant steps towards a great success but we need to be careful not to skip important things in between those steps. I'd like to use my knowledge from my involvement in several areas throughout OpenStack (and outside it) to help OpenStack moving forward at the same - or at a better - pace. Thanks for your consideration, Flavio P.S: If you're thinking. Wait, this guy is nuts. He ran for 2 PTL positions and he now wants to run for a TC position. Is he crazy? One answer to that could be, Yes. However, just to make sure it's clear to everyone my current time situation, I'd like to share that I'm just Zaqar's PTL - Nikhil is Glance's PTL - and my current commitments allow me for dedicating to this position the time it requires. -- @flaper87 Flavio Percoco pgpNpjDJV55fq.pgp Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)
On 04/21/2015 09:56 AM, Flavio Percoco wrote: FWIW, the team is not messuring the success of the project on whether it's integrated with other services or not. The adoption in all possible areas play key parts in every project's life. While it's amazing that RDO - and I believe Ubuntu is packaging too, Zigo, correct me, pls - has support for it, I don't think that's enough for the project to go anywhere. As per this: http://packages.ubuntu.com/search?keywords=zaqarsearchon=namessuite=allsection=all Ubuntu doesn't have it. I haven't worked on it (yet), though if you are saying it's ready, I may give it a try. Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver
Diem Can you please look at why the Oracle CI is failing on every patch? Currently it appears you *do not* have working CI and *are not* eligible to be merged back in. Given we (Cinder core) set a second deadline for the 'nearly there' CI systems which you missed, and your CI is still not working, I don't expect you to get into the RC. On 21 April 2015 at 02:53, Diem Tran diem.t...@oracle.com wrote: Hi Mike, Could you please take a look at the results and consider re-integrating the driver? We the Oracle ZFSSA team would like to target the Kilo RC deadline if possible. Thank you, Diem. On 4/20/15 3:47 PM, Diem Tran wrote: Hi Mike, Oracle ZFSSA iSCSI CI is now reporting test results. It is configured to run against the ZFSSA iSCSI driver. You can see the results here: https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z Below are some patchsets that the CI reports: https://review.openstack.org/#/c/168424/ https://review.openstack.org/#/c/168419/ https://review.openstack.org/#/c/175247/ https://review.openstack.org/#/c/175077/ https://review.openstack.org/#/c/163706/ I would like to kindly request you and the core team to get the Oracle ZFSSA iSCSI driver re-integrated back to the Cinder code base. If there is anything else you need from the CI and the driver, please do let me know. Thank you, Diem. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra][cinder] Could you please re-consider Oracle ZFSSA iSCSI Driver
Duncan Thomas wrote: Can you please look at why the Oracle CI is failing on every patch? Currently it appears you *do not* have working CI and *are not* eligible to be merged back in. Given we (Cinder core) set a second deadline for the 'nearly there' CI systems which you missed, and your CI is still not working, I don't expect you to get into the RC. Also from a Kilo release management perspective the hard limit for any feature (re)addition was RC1, which was released about 10 days ago. -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Cross-Project meeting, Tue April 21st, 21:00 UTC
Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting today at 21:00 UTC, with the following agenda: * api-wg discussion * The following guidelines have been reached consensus within the api-wg and we'd like them to be reviewed by the CPLs ** tagging guidelines [1] ** Guidelines on using date and time format [2] * openstack-specs discussion * Supported messaging drivers policy [3] * Design Summit scheduling * Final Design Summit slot layout [4] * Introducing Cheddar * Open discussion announcements * Any Kilo release red flags ? [1] https://review.openstack.org/155620 [2] https://review.openstack.org/159892 [3] https://review.openstack.org/#/c/174105/ [4] https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit?usp=sharing See you there ! For more details on this meeting, please see: https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
