Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party

Hi- Its nice to have CI operators meetings. I'm from India, Its okay for me for 05:00AM UTC on Tuesdays. -- Trinath Somanchi - B39208 [email protected] | extn: 4048 -Original Message- From: Anita Kuno [mailto:[email protected]] Sent: Tuesday, December 02, 2014 1:37 AM

Re: [openstack-dev] [stable] New config options, no default change

>>> What is the text that should be included in the commit messages to make >>> sure that it is picked up for release notes? >> I'm not sure anyone tracks commit messages to create release notes. Let's use existing DocImpact tag, I'll add check for this in the release scripts. But I prefer if you

Re: [openstack-dev] [stable] Re: [neutron] the hostname regex pattern fix also changed behaviour :(

>> With the change, will existing instances work as before? > > Yes, this cuts straight to the heart of the matter: What's the purpose of > these validation checks? Specifically, if someone is using an "invalid" > hostname that passed the previous check but doesn't pass an improved/updated > chec

Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party

HI, Thanks Anita for pushing it. We will be able to be much more involved if meetings would be earlier. We're located in Israel, so Mondays anytime between 8:00 - 16:00, will be ideal for us. Nurit -Original Message- From: [email protected] [mailto:trinath.soman...@freesca

[openstack-dev] [Keystone] creadential API example BUG?

Hi all, I want to confirm that about the examples of the credential api that described at the following URL. http://docs.openstack.org/api/openstack-identity-service/3/content/create-credential-post-credentials.html I tried to request to our keystone server using the request example described

Re: [openstack-dev] [Keystone] creadential API example BUG?

On Tue, Dec 02, 2014 at 09:10:01AM +, Mizutani, Michiyuki wrote: > > Hi all, > > I want to confirm that about the examples of the credential api that > described at the following URL. > > http://docs.openstack.org/api/openstack-identity-service/3/content/create-credential-post-credentials.h

Re: [openstack-dev] [glance] Deprecating osprofiler option 'enabled' in favour of 'profiler_enabled'

On 02/12/14 12:16 +0800, Zhi Yan Liu wrote: Why not change other services instead of glance? I see one reason is "glance is the only one service use this option name", but to me one reason to keep it as-it in glance is that original name makes more sense due to the option already under "profiler"

Re: [openstack-dev] sqlalchemy-migrate call for reviews

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 It's weird: we run python33 job for gate but not checks. Adding Cyril Roelandt who ported the library to py3 to CC. On 01/12/14 23:40, Thomas Goirand wrote: > On 12/01/2014 06:19 PM, Ihar Hrachyshka wrote: >> Indeed, the review queue is non-responsi

Re: [openstack-dev] [Keystone] creadential API example BUG?

Hi Steven, Thank you for your quick response. The following document is correct as credential API of ec2tokens, isn't it? http://developer.openstack.org/api-ref-identity-v3.html So, I was confuse about specifying to request body of credential API. Thanks again! > -Original Message- > F

Re: [openstack-dev] [TripleO] mid-cycle details final draft

Clint Byrum wrote: > Hello! I've received confirmation that our venue, the HP offices in > downtown Seattle, will be available for the most-often-preferred > least-often-cannot week of Feb 16 - 20. > > Our venue has a maximum of 20 participants, but I only have 16 possible > attendees now. Please

[openstack-dev] [sahara] client 0.7.6 release

Sahara folks, we have python-saharaclient version 0.7.6 release. The main changes are: * support for server-side API filtering added to the client * client know checks both data-processing and data_processing endpoint types More info: https://launchpad.net/python-saharaclient/0.7.x/0.7.6 Thanks

[openstack-dev] [Murano] - Install Guide

Hi All, I am new to Murano and trying to integrate with Openstack Juno. Any build guides or help would be appreciated. Warm Regards, Raghavendra Lad IDC-IC-P-Capability Infrastructure Consulting, Infrastructure Services - Accenture Operations Mobile - +91 9880040919

Re: [openstack-dev] [qa] Should it be allowed to attach 2 interfaces from the same subnet to a VM?

Hello Danny, I think so. Any special concern with a VM using more than one port on a subnet? andrea On 2 December 2014 at 02:04, Danny Choi (dannchoi) wrote: > Hi, > > When I attach 2 interfaces from the same subnet to a VM, there is no error > returned and > both interfaces come up. > > lab@tm

Re: [openstack-dev] [glance] Deprecating osprofiler option 'enabled' in favour of 'profiler_enabled'

> -Original Message- > From: Flavio Percoco [mailto:[email protected]] > Sent: 02 December 2014 09:45 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [glance] Deprecating osprofiler option 'enabled' > in favour of 'profiler_enabled' > > On

Re: [openstack-dev] [Keystone] creadential API example BUG?

On Tue, Dec 02, 2014 at 10:17:46AM +, Mizutani, Michiyuki wrote: > Hi Steven, > > Thank you for your quick response. > > The following document is correct as credential API of ec2tokens, isn't it? > http://developer.openstack.org/api-ref-identity-v3.html Yes, the example in http://developer

[openstack-dev] [stable] Call for testing: 2014.2.1 candidate tarballs

Hi all, We are scheduled to publish 2014.2.1 on Thursday Dec 4th for Ceilometer, Cinder, Glance, Heat, Horizon, Keystone, Neutron, Nova, Sahara and Trove. We'd appreciate anyone who could test the candidate 2014.2.1 tarballs, which include all changes aside from any pending freeze exceptions:

Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party

Thanks for starting this discussion Anita. The existing meeting time on Monday has never worked well for me. We could follow what other working groups have done, having alternating meeting times to accommodate everyone. I propose that we have 2 meetings of Third-party CI Ops, alternating weeks: W

Re: [openstack-dev] [glance] Deprecating osprofiler option 'enabled' in favour of 'profiler_enabled'

On Tue, Dec 02, 2014 at 12:16:44PM +0800, Zhi Yan Liu wrote: > Why not change other services instead of glance? I see one reason is > "glance is the only one service use this option name", but to me one > reason to keep it as-it in glance is that original name makes more > sense due to the option a

Re: [openstack-dev] [Keystone] creadential API example BUG?

Hi Steven, Thank you for your reply. > Looks OK, although the example blob is not JSON serialized, despite teh > description saying "JSON-serialized dictionary". I think the API will > tolerate either format though. I understand somehow. Credential API that will be called from the Heat that fo

Re: [openstack-dev] [glance] Deprecating osprofiler option 'enabled' in favour of 'profiler_enabled'

I totally agreed to make it to be consistent cross all projects, so I propose to change other projects. But I think keeping it as-it is clear enough for both developer and operator/configuration, for example: [profiler] enable = True instead of: [profiler] profiler_enable = True Tbh, the "prof

[openstack-dev] [horizon] [ux] Changing how the modals are closed in Horizon

Hello, Horizoneers and UX-ers! The default behavior of modals in Horizon (defined in turn by Bootstrap defaults) regarding their closing is to simply close the modal once user clicks somewhere outside of it (on the backdrop element below and around the modal). This is not very convenient for the m

Re: [openstack-dev] [TripleO] [CI] Cinder/Ceph CI setup

On 11/27/2014 02:23 PM, Derek Higgins wrote: On 27/11/14 10:21, Duncan Thomas wrote: I'd suggest starting by making it an extra job, so that it can be monitored for a while for stability without affecting what is there. we have to be careful here, adding an extra job for this is probably the s

Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party

1800UTC should generally work for Europe. The only issue is that it falls right around dinner time. It is however a good timing since most of the night hours fall over the pacific ocean. Therefore I tend to agree with Joshua's proposal since with that time range most of the night hours would fall

[openstack-dev] [stable] Exception proposals for 2014.2.1

Hi all, here are exception proposal I have collected when preparing for the 2014.2.1 release, stable-maint members please have a look! General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to include in the release. https://review.openstack.o

[openstack-dev] [Fuel][Nailgun]Problems with auto-reloading

Hi folks, today we encountered a problem caused by auto-reload feature and our code-organisation. The problem is that web.py tries reloading modules at some point and while it does that it expects that modules could be reloaded in any order without raising any errors. Unfortunately for Nailgun

Re: [openstack-dev] [Fuel][Nailgun]Problems with auto-reloading

I don't even remember if/when autoreloading worked correctly. +1 for disabling this feature. 2014-12-02 16:23 GMT+03:00 Roman Prykhodchenko : > Hi folks, > > today we encountered a problem caused by auto-reload feature and our > code-organisation. > The problem is that web.py tries reloading mod

[openstack-dev] [tempest] tearDownClass usage in scenario tests

I’ve noticed that in scenario tests only the OfficialClientTest in manager.py has a tearDownClass and was wondering if there is a reason for that? In my scenario tests I need to ensure a particular connection gets closed after the test runs. This connection is setup in setUpClass so it makes se

[openstack-dev] [TripleO] Alternate meeting time

Months ago, I pushed for us to alternate meeting times to something that was friendlier to me, so we started doing alternate weeks at 0700UTC. That worked well for me, but wasn't working so well for a few people in Europe, so we decided to give 0800UTC a try. Then DST changes happened, and wiki pag

[openstack-dev] [Fuel][Nailgun] Web framework

Hi all, Some time ago we had a discussion about moving Nailgun to new web framework [1]. There was comparison [2] of two possible options: Pecan [3] and Flask [4]. We came to conclusion that we need to move Nailgun on some alive web framework instead of web.py [5] (some of the reasons: [6]) but t

[openstack-dev] [Manila] Manila project use-cases

Hello Manila Team, We identified use cases for Manila during an internal workshop with our operators. I would like to share them with you and update the wiki [1] since it seems to be outdated. Before that I would like to gather feedback and you might help me with identifying things that aren’t im

Re: [openstack-dev] [TripleO] Alternate meeting time

On 02/12/14 16:10, James Polley wrote: > Months ago, I pushed for us to alternate meeting times to something that > was friendlier to me, so we started doing alternate weeks at 0700UTC. > That worked well for me, but wasn't working so well for a few people in > Europe, so we decided to give 0800UTC

Re: [openstack-dev] [TripleO] Alternate meeting time

On 02/12/14 14:10, James Polley wrote: > Months ago, I pushed for us to alternate meeting times to something that > was friendlier to me, so we started doing alternate weeks at 0700UTC. > That worked well for me, but wasn't working so well for a few people in > Europe, so we decided to give 0800UTC

Re: [openstack-dev] [horizon] REST and Django

On 12/02/2014 12:39 AM, Richard Jones wrote: On Mon Dec 01 2014 at 4:18:42 PM Thai Q Tran > wrote: I agree that keeping the API layer thin would be ideal. I should add that having discrete API calls would allow dynamic population of table. However, I will ma

Re: [openstack-dev] [neutron] force_gateway_on_subnet, please don't deprecate

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/12/14 21:19, Kyle Mestery wrote: > On Mon, Dec 1, 2014 at 6:12 AM, Assaf Muller > wrote: >> >> >> - Original Message - >>> >>> My proposal here, is, _let’s not deprecate this setting_, as >>> it’s a valid use case of a gateway confi

Re: [openstack-dev] [qa] Should it be allowed to attach 2 interfaces from the same subnet to a VM?

- Original Message - > From: "Danny Choi (dannchoi)" > To: [email protected] > > Hi, > > When I attach 2 interfaces from the same subnet to a VM, there is no error > returned and > both interfaces come up. > > lab@tme211:/opt/stack/logs$ nova interface-attach --net-id >

Re: [openstack-dev] [tempest] tearDownClass usage in scenario tests

Hello Rich, in the latest tempest we made two significant changes compared to the version you're using. We dropped the use of official clients from scenario tests (and OfficialClientTest has been replaced by ScenarioTest). And we introduced resource_setup and resource_cleanup in the test base cla

Re: [openstack-dev] [Fuel][Nailgun] Web framework

Hi, Sebastian, Thank you for raising this topic again. Yes, indeed, we need to move out from web.py as soon as possible and there are a lot of reasons why we should do it. But this topic is not about "Why", this topic is about "Flask or Pecan". Well, currently Fuel uses both of this frameworks:

Re: [openstack-dev] [stable] Exception proposals for 2014.2.1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/12/14 14:22, Alan Pevec wrote: > Hi all, > > here are exception proposal I have collected when preparing for > the 2014.2.1 release, stable-maint members please have a look! > > > General: cap Oslo and client library versions - sync from >

[openstack-dev] oslo.rootwrap 1.4.0 released

The Oslo team is pleased to announce the release of oslo.rootwrap 1.4.0. This is primarily a bug fix and test-requirements update release: $ git log --abbrev-commit --pretty=oneline --no-merges 1.3.0..1.4.0 2c43df7 Updated from global requirements 62d7322 Updated from global requirements 8c39d15 C

[openstack-dev] oslo.utils 1.1.0 released

The Oslo team is pleased to announce the release of oslo.utils 1.1.0. This release includes several bug fixes as well as many other changes. For more details, please see the git log history below and https://launchpad.net/oslo.utils/+milestone/1.1.0 Please report issues through launchpad: https:/

Re: [openstack-dev] [TripleO] Alternate meeting time

On 12/02/2014 03:45 PM, Derek Higgins wrote: On 02/12/14 14:10, James Polley wrote: Months ago, I pushed for us to alternate meeting times to something that was friendlier to me, so we started doing alternate weeks at 0700UTC. That worked well for me, but wasn't working so well for a few people

Re: [openstack-dev] [TripleO] Alternate meeting time

On Tue, Dec 2, 2014 at 3:22 PM, marios wrote: > On 02/12/14 16:10, James Polley wrote: > > Months ago, I pushed for us to alternate meeting times to something that > > was friendlier to me, so we started doing alternate weeks at 0700UTC. > > That worked well for me, but wasn't working so well for

[openstack-dev] [python-novaclient] Status of novaclient V3

Hi! While working on fixing wrong import in novaclient v3 shell, I have found that a lot of commands, which are listed in V3 shell(novaclient.v3.shell), are broken, because appropriate managers are missed from V3 client(novaclient.V3.client.Client). Template of error is "ERROR (AttributeError): '

Re: [openstack-dev] [TripleO] Alternate meeting time

On 02/12/14 15:12, Giulio Fidente wrote: > On 12/02/2014 03:45 PM, Derek Higgins wrote: >> On 02/12/14 14:10, James Polley wrote: >>> Months ago, I pushed for us to alternate meeting times to something that >>> was friendlier to me, so we started doing alternate weeks at 0700UTC. >>> That worked we

Re: [openstack-dev] [TripleO] Alternate meeting time

On Tue, Dec 2, 2014 at 4:12 PM, Giulio Fidente wrote: > On 12/02/2014 03:45 PM, Derek Higgins wrote: > >> On 02/12/14 14:10, James Polley wrote: >> >>> Months ago, I pushed for us to alternate meeting times to something that >>> was friendlier to me, so we started doing alternate weeks at 0700UTC

Re: [openstack-dev] [glance] Deprecating osprofiler option 'enabled' in favour of 'profiler_enabled'

Except for the fact that the person who implemented this was told to change the option name in other projects because it conflicted with a different option. We can keep this if we’re worried about being too obvious (to the point of becoming the Department of Redundancy Department) with our naming.

[openstack-dev] oslo.i18n 1.1.0 released

The Oslo team is pleased to announce the release of oslo.i18n 1.1.0. For more details, please see the git log history below and https://launchpad.net/oslo.i18n/+milestone/1.1.0 Please report issues through launchpad: https://launchpad.net/oslo.i18n $ git log --no-color --oneline --no-merges 1.0.0

Re: [openstack-dev] [Fuel][Nailgun] Web framework

For what it's worth in terms of "production-ready", pecan is mostly just webob under the hood, and has been used pretty extensively at DreamHost in high-traffic environments (we use pecan to handle *all* customer signups for our entire product line at DreamHost). Not to mention the other major Ope

Re: [openstack-dev] [Manila] Manila project use-cases

Hello Marc, Here, I tried to cover mentioned use cases with "implemented or not" notes: 1) Implemented, but details of implementation are different for different share drivers. 2) Not clear for me. If you mean possibility to mount one share to any amount of VMs, then yes. 3) Nova is used only in

[openstack-dev] oslo.vmware 0.8.0 released

The Oslo team is pleased to announce the release of oslo.vmware 0.8.0. For more details, please see the git log history below and https://launchpad.net/oslo.vmware/+milestone/0.8.0 Please report issues through launchpad: https://launchpad.net/oslo.vmware $ git log --no-color --oneline --no-merges

[openstack-dev] [neutron] Changes to the core team

Now that we're in the thick of working hard on Kilo deliverables, I'd like to make some changes to the neutron core team. Reviews are the most important part of being a core reviewer, so we need to ensure cores are doing reviews. The stats for the 180 day period [1] indicate some changes are needed

Re: [openstack-dev] [stable] New config options, no default change

On 12/02/2014 02:31 AM, Alan Pevec wrote: What is the text that should be included in the commit messages to make sure that it is picked up for release notes? I'm not sure anyone tracks commit messages to create release notes. Let's use existing DocImpact tag, I'll add check for this in the r

Re: [openstack-dev] [stable] Exception proposals for 2014.2.1

On 12/02/2014 07:22 AM, Alan Pevec wrote: Hi all, here are exception proposal I have collected when preparing for the 2014.2.1 release, stable-maint members please have a look! General: cap Oslo and client library versions - sync from openstack/requirements stable/juno, would be good to inclu

Re: [openstack-dev] [Fuel][Nailgun] Web framework

On 12/02/2014 09:55 AM, Igor Kalnitsky wrote: > Hi, Sebastian, > > Thank you for raising this topic again. > > [snip] > > Personally, I'd like to use Flask instead of Pecan, because first one > is more production-ready tool and I like its design. But I believe > this should be resolved by voting

[openstack-dev] oslo.concurrency 0.3.0 released

The Oslo team is pleased to announce the release of oslo.concurrency 0.3.0. This release includes a number of fixes for problems found during the initial adoptions of the library, as well as some functionality improvements. For more details, please see the git log history below and https://launch

Re: [openstack-dev] [neutron] Changes to the core team

> On Dec 2, 2014, at 10:59 AM, Kyle Mestery wrote: > > First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from > neutron-core. Bob and Nachi have been core members for a while now. > They have contributed to Neutron over the years in reviews, code and > leading sub-teams. I'd like t

[openstack-dev] cliff 1.9.0 released

The Oslo team is pleased to announce release 1.9.0 of cliff. This is primarily a bug-fix release, but does include a requirements update. For more details, please see the git log history below and https://launchpad.net/python-cliff/+milestone/1.9.0 Please report issues through launchpad: https

Re: [openstack-dev] [horizon] [ux] Changing how the modals are closed in Horizon

I like David's approach, but having two modals (one for the form, one for the confirmation) on top of each other is a bit weird and would require constant checks for input. We already have three ways to close the dialog today: via the cancel button, X button, and ESC key. It's more important to me

Re: [openstack-dev] [qa] Should it be allowed to attach 2 interfaces from the same subnet to a VM?

Hi Andrea, Though both interfaces come up, only one will response to the ping from the neutron router. When I disable it, then the second one will response to ping. So it looks like only one interface is useful at a time. My question is is there any useful case for this, I.e. Why would you do th

Re: [openstack-dev] [neutron] Changes to the core team

I am happy with the proposed change in the core team. Many thanks to the outgoing members and a warm welcome to hell (err core team) to Henry and Kevin! Salvatore Il 02/dic/2014 17:20 "Mark McClain" ha scritto: > > > On Dec 2, 2014, at 10:59 AM, Kyle Mestery wrote: > > > > First of all, I'm pr

Re: [openstack-dev] [neutron] Changes to the core team

Congrats to Henry and Kevin, +1! ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] oslosphinx 2.3.0 released

The Oslo team is pleased to announce release 2.3.0 of oslosphinx. This release includes bug fixes, new features, and updated requirements. For more details, please see the git log history below and http://launchpad.net/oslosphinx/+milestone/2.3.0 Please report issues through launchpad: http://

Re: [openstack-dev] [neutron] Changes to the core team

Assuming I still have a vote, I vote +1 for adding Henry and Kevin, both of whom I am confident will do a great job as core reviewer. I'd ask people to consider voting against dropping me from core (and I vote -1 on that if I get a vote). During Juno, my plan was to balance my time between neu

Re: [openstack-dev] [tempest] tearDownClass usage in scenario tests

I see - looks like the repro I¹m based off of hasn¹t keep up with the latest. I¹ll have to look at the ScenarioTest. Thanks Rich On 12/2/14, 9:54 AM, "Andrea Frittoli" wrote: >Hello Rich, > >in the latest tempest we made two significant changes compared to the >version you're using. > >We d

[openstack-dev] oslotest 1.3.0 released

The Oslo team is pleased to announce release 1.3.0 of oslotest. This release is primarily to update the dependencies for the library. 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.la

[openstack-dev] oslo.config 1.5.0 released

The Oslo team is pleased to announce release 1.5.0 of oslo.config. This is primarily a bug-fix release, but does include requirements changes. For more details, please see the git log history below and http://launchpad.net/oslo/+milestone/1.5.0 Please report issues through launchpad: http://bu

Re: [openstack-dev] [TripleO] [CI] Cinder/Ceph CI setup

On 11/27/2014 07:23 AM, Derek Higgins wrote: > On 27/11/14 10:21, Duncan Thomas wrote: >> I'd suggest starting by making it an extra job, so that it can be >> monitored for a while for stability without affecting what is there. > > we have to be careful here, adding an extra job for this is probab

Re: [openstack-dev] [stable] New config options, no default change

- Original Message - > From: "Alan Pevec" > To: "Jay Bryant" , "OpenStack Development > Mailing List (not for usage questions)" > > >>> What is the text that should be included in the commit messages to make > >>> sure that it is picked up for release notes? > >> I'm not sure anyone trac

Re: [openstack-dev] [qa] Should it be allowed to attach 2 interfaces from the same subnet to a VM?

- Original Message - > From: "Danny Choi (dannchoi)" > To: [email protected] > > Hi Andrea, > > Though both interfaces come up, only one will response to the ping from the > neutron router. > When I disable it, then the second one will response to ping. > So it looks like

Re: [openstack-dev] [Manila] Manila project use-cases

I does 2 mean something like: Have new manilla share unionfs under the hood, with the existing storage mounted too, so you can switch all clients over to manilla, then migrate the data, then remove the old storage/unionfs live? Thanks, Kevin From: Valeriy Ponomar

Re: [openstack-dev] [neutron] Changes to the core team

+1 from me for all the changes. I appreciate the work from all four of these excellent contributors. I'm happy to welcome Henry and Kevin as new core reviewers. I also look forward to continuing to work with Nachi and Bob as important members of the community. Carl On Tue, Dec 2, 2014 at 8:59

Re: [openstack-dev] [Manila] Manila project use-cases

Kevin, Just for clarification - there is no support of UnionFS in Manila for the moment. "Migration" of shares from one storage to another is not supported in Manila for the moment, even on level of interfaces. All possible "movements" of data are out of Manila. On Tue, Dec 2, 2014 at 6:59 PM, Fo

[openstack-dev] oslo.middleware 0.2.0 released

The Oslo team is pleased to announce release 0.2.0 of oslo.middleware. This is primarily a bug-fix release, but does include requirements changes. For more details, please see the git log history below and https://launchpad.net/oslo.middleware/kilo/0.2.0 Please report issues through launchpad

[openstack-dev] [Solum] Solum Team Meeting Time Change

Solum Team, As agreed in today’s team meeting, we are shifting our meetings to 2100 UTC on Tuesdays in #openstack-meeting-alt. We are ending our alternating meeting schedule for now. For scheduling specifics, please see: https://wiki.openstack.org/wiki/Meetings/Solum Regards, Adrian Otto

[openstack-dev] oslo.messaging 1.5.0 released

The Oslo team is pleased to announce the release of oslo.messaging 1.5.0. This release includes a number of fixes about rabbit driver timeout that was not always respected, starts using kombu API instead of custom code when it's possible. It also introduces the first ZMQ unit tests. And ZMQ an

[openstack-dev] [neutron][lbaas] Kilo Midcycle Meetup

Per the meeting, put together an etherpad here: https://etherpad.openstack.org/p/lbaas-kilo-meetup I would like to get the location and dates finalized ASAP (preferrably the next couple of days). We'll also try to do the same as the neutron and octava meetups for remote attendees. __

Re: [openstack-dev] [qa] Should it be allowed to attach 2 interfaces from the same subnet to a VM?

Excerpts from Danny Choi (dannchoi)'s message of 2014-12-02 08:34:07 -0800: > Hi Andrea, > > Though both interfaces come up, only one will response to the ping from the > neutron router. > When I disable it, then the second one will response to ping. > So it looks like only one interface is usefu

Re: [openstack-dev] [Mistral] Event Subscription

Renat, I agree with the two methods you proposed. On processing the events, I was thinking a separate entity. But you gave me an idea, how about a system action for publishing the events that the current executors can run? Alternately, instead of making HTTP calls, what do you think if mistral

Re: [openstack-dev] [CI]Setup CI system behind proxy

Could you please clarify? Do you mean you want to setup everything behind a proxy? or do you mean you want to setup just gerrit behind a proxy? On Mon, Dec 1, 2014 at 6:26 PM, thanh le giang wrote: > Dear all > > I have set up a CI system successfully with directly access to internet. > Now I

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On Tue, Dec 2, 2014 at 1:49 AM, Clint Byrum wrote: > Excerpts from Anant Patil's message of 2014-11-30 23:02:29 -0800: > > On 27-Nov-14 18:03, Murugan, Visnusaran wrote: > > > Hi Zane, > > > > > > > > > > > > At this stage our implementation (as mentioned in wiki > > >

Re: [openstack-dev] oslo.concurrency 0.3.0 released

We've discovered a couple of problems as a result of this release. pep8 in most/all of the projects using oslo.concurrency is failing due to the move out of the oslo namespace package and the fact that hacking doesn't know how to handle it, and nova unit tests are failing due to a problem with the

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

Yes, that's the synchronization block for which we use the stack lock. Currently, a thread spin waits to acquire the lock to enter this critical section. I don't really know how to do application level transaction. Is there an external library for that? AFAIK, we cannot switch from DB transaction

Re: [openstack-dev] oslo.concurrency 0.3.0 released

One of the changes in this release was a move from using the “oslo” namespace to using a non-namespaced package “oslo_concurrency”. We included some shims to allow imports to work correctly, but the hacking rule to verify whether an import is actually a module was not recognizing these shims cor

Re: [openstack-dev] [neutron] Changes to the core team

Hi folks Congrats! Henry and Kevin. I'll keep contributing the community, but Thank you for working with me as core team :) Best Nachi 2014-12-03 2:05 GMT+09:00 Carl Baldwin : > +1 from me for all the changes. I appreciate the work from all four > of these excellent contributors. I'm happy to

Re: [openstack-dev] [CI]Setup CI system behind proxy

Hi, I want to setup everything behind proxy, but i am stuck at step configure zuul connect to gerrit. I can't find any option to set proxy on zuul.conf file. Thanks 2014-12-03 1:00 GMT+07:00 Zaro : > Could you please clarify? Do you mean you want to setup everything behind > a proxy? or do yo

Re: [openstack-dev] [Fuel][Nailgun] Web framework

Hello all, I actually tried to use Pecan and even created a couple of PoCs, but there due to historical reasons of how our API is organized it will take much more time to implement all workarounds we need to issues Pecan doesn't solve out of the box, like working with non-RESTful URLs, reverse URL

Re: [openstack-dev] [keystone][oslo] Handling contexts and policy enforcement in services

On 12/01/2014 09:09 AM, Doug Hellmann wrote: On Nov 30, 2014, at 8:51 PM, Jamie Lennox wrote: TL;DR: I think we can handle most of oslo.context with some additions to auth_token middleware and simplify policy enforcement (from a service perspective) at the same time. There is currently a push

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

On 12/02/2014 03:46 PM, Clint Byrum wrote: 1) Conform all o-r-c scripts to the logging standards we have in OpenStack, or write new standards for diskimage-builder and conform them to those standards. Abolish non-conditional xtrace in any script conforming to the standards. Honestly in the list

[openstack-dev] [nova] [libvirt] enabling per node filtering of mempage sizes

Hi all I have submitted a small blueprint to allow filtering of available memory pages Reported by libvirt. https://blueprints.launchpad.net/nova/+spec/libvirt-allowed-mempage-sizes I believe that this change is small enough to not require a spec as per http://docs.openstack.org/developer/nova/

[openstack-dev] [oslo][qa] Moving the hacking project under the QA program

The hacking project is currently managed by the Oslo team. Normally Joe Gordon handles all of the release work, and so I haven’t bothered to look at how the Launchpad project is set up or how the branches are managed before today. However, today’s issue with oslo.concurrency resulted in a need t

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

Excerpts from Anant Patil's message of 2014-12-02 10:37:31 -0800: > Yes, that's the synchronization block for which we use the stack lock. > Currently, a thread spin waits to acquire the lock to enter this critical > section. > > I don't really know how to do application level transaction. Is ther

Re: [openstack-dev] [Fuel][Nailgun] Web framework

This sounds more like you need to pay off technical debt and clean up your API. Michael On Tue Dec 02 2014 at 10:58:43 AM Nikolay Markov wrote: > Hello all, > > I actually tried to use Pecan and even created a couple of PoCs, but > there due to historical reasons of how our API is organized it

Re: [openstack-dev] [oslo][qa] Moving the hacking project under the QA program

On Tue, Dec 2, 2014 at 9:48 PM, Doug Hellmann wrote: > The hacking project is currently managed by the Oslo team. Normally Joe > Gordon handles all of the release work, and so I haven’t bothered to look > at how the Launchpad project is set up or how the branches are managed > before today. Howev

Re: [openstack-dev] [Fuel][Nailgun] Web framework

Michael, we already solved all issues I described, and I just don't want to solve them once again after moving to another framework. Also, I think, nothing of these wishes contradicts with good API design. On Tue, Dec 2, 2014 at 10:49 PM, Michael Krotscheck wrote: > This sounds more like you need

Re: [openstack-dev] [stable] New config options, no default change

> Will the bugs created by this end up in the openstack-manuals project (which > I don't think is the right place for them in this case) or has it been set up > to create them somewhere else (or not at all) when the commits are against > the stable branches? Docs team, how do you handle DocImpa

[openstack-dev] [infra] Gerrit downtime on Dec 6 for project renames

Hi, on Saturday, Dec 6 at 16:00 UTC Gerrit will be unavailable for about 30 minutes while we rename some projects. Existing reviews, project watches, etc, should all be carried over. So far, we have the following list of projects to rename: * stackforge/heat-translator -> openstack/heat-translato

Re: [openstack-dev] [stable] New config options, no default change

On Tue, Dec 2, 2014 at 2:59 PM, Alan Pevec wrote: > > Will the bugs created by this end up in the openstack-manuals project > (which I don't think is the right place for them in this case) or has it > been set up to create them somewhere else (or not at all) when the commits > are against the sta

Re: [openstack-dev] [stable] New config options, no default change

- Original Message - > From: "Anne Gentle" > To: "OpenStack Development Mailing List (not for usage questions)" > > > On Tue, Dec 2, 2014 at 2:59 PM, Alan Pevec wrote: > > > > Will the bugs created by this end up in the openstack-manuals project > > (which I don't think is the right p

Re: [openstack-dev] [OpenStack-docs] [stable] New config options, no default change

On Tue, Dec 2, 2014 at 3:44 PM, Steve Gordon wrote: > - Original Message - > > From: "Anne Gentle" > > To: "OpenStack Development Mailing List (not for usage questions)" < > [email protected]> > > > > On Tue, Dec 2, 2014 at 2:59 PM, Alan Pevec wrote: > > > > > > Will the

[openstack-dev] [Telco][NFV] Framing use case contributions

Hi all, Based on last week's conversation [1] I have tried to update the use cases page to remove the emphasis on requirements/solutions and focus on the "what" and "why" and to provide some guidance as to initial scope to help those wishing to submit use cases in framing them. Please review a

  1   2   >