Re: [openstack-dev] [horizon][neutron][lbaas] Horizon support for neutron-lbaas v2

Hi Vivek and LBaaS folks, I added [horizon] tag so that Horizon folks can be aware of this thread. Before jumping into LBaaS specific topic, let me share the current effort As you may know, Horizon team itself is exploring a way how to make development of each panel fast and smooth. - One exampl

Re: [openstack-dev] [Senlin] TOSCA Reference Material

Thanks, Julio, for sharing this. Regards, Qiming On Tue, Jul 14, 2015 at 12:08:39PM -0500, Julio E Ruano wrote: > Hi All, > > I just wanted to share where all of the TOSCA reference material is > accessible. It is maintained through an OASIS TC here -> > https://www.oasis-open.org/committees/

Re: [openstack-dev] [swift] [ceilometer] Ceilometer log dir permissions bust swift proxy

On 14/07/15 11:05, Mark Kirkwood wrote: On 13/07/15 06:44, Emilien Macchi wrote: Yeah, I guess I should raise a bug with Ubuntu so it (maybe) gets sorted out. However in the meantime we may have to work around it by amending the dir permissions in puppet (the alternative - rolling our own pac

Re: [openstack-dev] [neutron] - Proposing Miguel Angel Ajo for the Control Plane core team

Congratulations Miguel :-) -Original Message- From: Miguel Angel Ajo [mailto:mangel...@redhat.com] Sent: Tuesday, July 14, 2015 7:45 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] - Proposing Miguel Angel Ajo for the Control Pl

Re: [openstack-dev] [neutron][security-group] rules for filter mac-addresses

Can i understand the use case for that? What i don't get it is how will you know the MAC for a new created instance via HEAT so you can set at the same time the SG based on MAC? On Tue, Jul 14, 2015 at 12:29 PM, yan_xing...@163.com wrote: > Thank you, Kevin. > I search the blueprint about thi

Re: [openstack-dev] [mistral] A new BP - Support large datasets being passed

Moshe, thanks for addressing this. I think we need to implement this BP in this cycle (actually asap) as I think it can potentially create problems with real usage now. So I fully support it. One thing we need to do is to see what other columns (besides listed out in BP) should also be transfor

Re: [openstack-dev] [Heat] conditional resource exposure - second thoughts

Like to share my opinions as below: Resource-type-list/resource-type-show: Once the role based resource exposure is enabled, based on the user's role, I believe, (s)he would expect to see those deployed resource-types, which are authorized. And wanted to know if that resource-type is ava

Re: [openstack-dev] [testing] moving testrepository *outside* the tox venv

On 13 July 2015 at 06:19, Mike Bayer wrote: > > > On 7/11/15 6:04 AM, Robert Collins wrote: >> >> Wearing my upstream hat, testr is *still* intended to be used differently >> than OpenStack is doing. Running all the tests for all python versions at >> once in parallel is the sort of thing testr is

[openstack-dev] 答复: [Heat] conditional resource exposure - second thoughts

-邮件原件- 发件人: Zane Bitter [mailto:zbit...@redhat.com] 发送时间: 2015年7月15日 3:35 收件人: openstack-dev@lists.openstack.org 主题: Re: [openstack-dev] [Heat] conditional resource exposure - second thoughts On 14/07/15 14:34, Pavlo Shchelokovskyy wrote: > Hi Heaters, > > currently we already expose to

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

One drawback to virt_type if not seen in the context of the acceptable values, is that it should be set to values like libvirt, xen, ironic, etc. That might actually be good. Instead of using the values 'vm' or 'baremetal', we use the name of the nova virt driver, and interpret those to be vm or

Re: [openstack-dev] [Congress] New IRC meeting time

I'm happy to see that. btw, is the day on Tuesday? best regard, masa On 2015/07/15 9:52, Zhou, Zhenzan wrote: Glad to see this change. Thanks for the supporting for developers in Asia☺ BR Zhou Zhenzan From: Tim Hinrichs [mailto:t...@styra.com] Sent: Wednesday, July 15, 2015 02:14 To: OpenSta

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

I am going to propose a third option: 3. virt_type I have concerns about option 1 and 2, because “instance_type” and flavor was used interchangeably before [1]. If we use “instance_type” to indicate “vm” or “baremetal”, it may cause confusions. [1] https://blueprints.launchpad.net/nova/+spec/f

[openstack-dev] [Nova] Virtual device role tagging

Hello, I'd like to get the conversation started around a spec that my colleague Dan Berrange has proposed to the backlog. The spec [1] solves the problem of passing information about virtual devices into an instance. For example, in an instance with multiple network interfaces, each connected to

[openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

Hi Magnum Guys, I want to raise this question through ML. In this patch https://review.openstack.org/#/c/200401/ For some old history reason, we use platform to indicate 'vm' or 'baremetal'. This seems not proper for that, @Adrian proposed nova_instance_type, and someone prefer other names,

Re: [openstack-dev] [Congress] New IRC meeting time

Glad to see this change. Thanks for the supporting for developers in Asia☺ BR Zhou Zhenzan From: Tim Hinrichs [mailto:t...@styra.com] Sent: Wednesday, July 15, 2015 02:14 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Congress] New IRC meeting time To

Re: [openstack-dev] [Fuel] Being spammed by bugs when assigned to whole fuel team

Thank you. I think I resolved this with new filter matching exact "You received this bug notification because you are a member of". If I'm subscribed directly to the bug, there is another message is used by LP like "You received this bug notification because you are subscribed to the bug report. *h

Re: [openstack-dev] [Heat] [app-catalog] conditional resource exposure - second thoughts

Yeah. Sounds reasonable. I just wanted to raise the discussion since one might affect the implementation of the other. In fact, thinking through it more, having the validate template api be restricted to just what the specific instance of heat can do actually might help play a part in the solu

[openstack-dev] [neutron] Service Chain project IRC meeting agenda

Hi everyone, Below are some items we plan to discuss in the next IRC meeting. Please add more topics you would like to discuss if any. Thanks, Cathy * Spec update for addressing new comments, and review * SFC CLI client and Horizon Client dependency on base Neutron CLI and Horizon

Re: [openstack-dev] [Fuel] Separate repo for Fuel Agent

Thanks Vladimir. Let's ensure to get it done sooner than later (this might require to be tested in custom ISO..) - we are approaching FF, and I expect growing queues of patches to land... On Tue, Jul 14, 2015 at 6:03 AM Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Dear colleagues, > >

Re: [openstack-dev] [Fuel] New Criteria for UX bugs

Sounds good to start, we can always adjust later if needed. I actually changed one doc bug priority already using this criteria. On Fri, Jul 10, 2015 at 5:42 AM Jay Pipes wrote: > On 07/09/2015 06:14 PM, Andrew Woodward wrote: > > We often have bugs which create really poor User eXperience (UX)

Re: [openstack-dev] [Heat] [app-catalog] conditional resource exposure - second thoughts

A feedback mechanism for users is obviously a "good thing", but IMO, not germane to the threads original purpose of how and when to expose supported resources in Heat. I cannot imagine us implementing such a feature directly. This may be a good discussion to have in the context of app catalog ex

Re: [openstack-dev] [magnum] Tom Cammann for core

Thanks team, happy to be here :) Tom > On 14 Jul 2015, at 23:02, Adrian Otto wrote: > > Tom, > > It is my pleasure to welcome you to the magnum-core group. We are happy to > have you on the team. > > Regards, > > Adrian > >> On Jul 9, 2015, at 7:20 PM, Adrian Otto wrote: >> >> Team, >> >

[openstack-dev] [cinder] Vedams' DotHill, Lenovo and HP MSA CIs are Unstable

These three CIs are unstable and the drivers are in danger of being removed from the Liberty release since the maintainer has not communicated any maintenance happening. http://paste.openstack.org/show/375584/ http://paste.openstack.org/show/375585/ http://paste.openstack.org/show/375586/ I will

Re: [openstack-dev] [Heat] [app-catalog] conditional resource exposure - second thoughts

Without a feedback loop of some kind, how does one solve issues like the following: * Operator decides users don't need neutron NaaS because its "too complicated and users don't need it" (Seen on the mailing list multiple times) * Software developer writes cloud templates that deploys software t

Re: [openstack-dev] [Cinder] FFE Request: Re-add Quobyte Cinder Driver

On 17:44 Jul 14, Silvan Kaiser wrote: > Hello Cinder Community! > I'd like to request a feature freeze exception for change [1], re-adding the > Quobyte driver to Cinder. > > The driver was removed in change [2] due to missing CI activity [3], it was > originally added in the kilo release [4]. >

Re: [openstack-dev] [magnum] Tom Cammann for core

Tom, It is my pleasure to welcome you to the magnum-core group. We are happy to have you on the team. Regards, Adrian > On Jul 9, 2015, at 7:20 PM, Adrian Otto wrote: > > Team, > > Tom Cammann (tcammann) has become a valued Magnum contributor, and consistent > reviewer helping us to shape

Re: [openstack-dev] [Heat] [app-catalog] conditional resource exposure - second thoughts

Making users complain to admins that may have little to no control over what is and isn't available isn't a healthy strategy for user experience. Purposefully engineering hardship to try and influence operators to "do the right thing" in someone else's opinion sounds pretty counter productive to

Re: [openstack-dev] [Heat] [app-catalog] conditional resource exposure - second thoughts

We're kind of debating the same thing for the app catalog. Do we show templates that don't work on a given cloud since they wont work, potentially making useful tools hard to discover, or do we view it as an opportunity for users to complain to their admins that they need X feature in order to d

Re: [openstack-dev] Juno Compute RPC v3.33 Endpoint Error when the Controller is running rabbitMQ v3.4.2

3rd posting Hi Experts, I have a three node Juno system running on Ubuntu 14.04. On the compute node I keep getting the following Endpoint does not support RPC version 3.33 to caller error when I launch a Nova instance. The Controller is running rabbitMQ v3.4.2. So I do not understand why the

Re: [openstack-dev] [Openstack][nova] proxy quota/limits info from neutron

On 7/14/2015 3:43 PM, Cale Rath wrote: Hi, I created a patch to fail on the proxy call to Neutron for used limits, found here: https://review.openstack.org/#/c/199604/ This patch was done because of this: http://docs.openstack.org/developer/nova/project_scope.html?highlight=proxy#no-more-api-

Re: [openstack-dev] [Keystone] Symbol not found: _BIO_new_CMS

Also for the sake of future googlers: we gave up on supporting keystone development in OS X a release or two ago due to the increasing number of workarounds like this that we had to track (a few of which impacted the code base itself, and were thus dropped). On Tue, Jul 14, 2015 at 3:42 PM, Kirill

Re: [openstack-dev] [nova] Reminder: July 16 is non-priority feature proposal freeze

On 14 July 2015 at 18:40, Ed Leafe wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 07/14/2015 05:52 AM, John Garbutt wrote: > >> Please note, the non-priority feature freeze is on: July 30 So technically both are correct, neither are complete, oops: https://wiki.openstack.org/wi

Re: [openstack-dev] [Horizon] Liberty Mid Cycle Meetup

Hello everybody, Just a reminder about the mid-cycle next week. If you haven’t already, please add your name to the list[0] of people coming so we have a final head count on ordering morning / afternoon snacks. If your name is on the list and you aren’t coming, please remove it or indicate tha

[openstack-dev] [Openstack][nova]

Hi, I created a patch to fail on the proxy call to Neutron for used limits, found here: https://review.openstack.org/#/c/199604/ This patch was done because of this: http://docs.openstack.org/developer/nova/project_scope.html?highlight=proxy#no-more-api-proxies

Re: [openstack-dev] [Keystone] Symbol not found: _BIO_new_CMS

Just for the sake of future googlers. I’ve encountered the same problem (with horizon actually) and managed to solve it. 1) install and link latest openssl from homebrew: brew update && brew install openssl && brew link --force openssl 2) run tox, it fails. 3) manually activate the environment y

Re: [openstack-dev] [Cinder] python-cinderclient functional tests

I've added this topic to the meeting agenda [1] [1] https://wiki.openstack.org/wiki/CinderMeetings#Next_meeting Regards, Ivan Kolodyazhny On Mon, Jul 13, 2015 at 10:23 PM, Matthew Treinish wrote: > On Mon, Jul 13, 2015 at 12:04:05PM -0700, Mike Perez wrote: > > On 16:28 Jul 10, Ivan Kolodyazhn

[openstack-dev] [qa] identity v3 issue causing non-admin job to fail

Now that the tempest periodic jobs are back (thanks infra!), I was looking into the real failures. It seems the main one is caused by the fact that the v3 check for primary creds fails if 'admin_domain_name' in the identity section is None, which it is when devstack configures tempest for non-a

Re: [openstack-dev] [Openstack] Rescinding the M name decision

Thanks Lauren. Mi taco es su taco. On Tue, Jul 14, 2015 at 12:53 PM, Lauren Sell wrote: > Good news. After finalizing the trademark checks and giving the community > time to weigh in, Mitaka will be the name of the M release. > > Thanks again for the great discussion around this topic, and for t

Re: [openstack-dev] [Heat] conditional resource exposure - second thoughts

On 14/07/15 14:34, Pavlo Shchelokovskyy wrote: Hi Heaters, currently we already expose to the user only resources for services deployed in the cloud [1], and soon we will do the same based on whether actual user roles allow creating specific resources [2]. Here I would like to get your opinion o

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

On 07/14/2015 10:29 AM, Ihar Hrachyshka wrote: > On 07/14/2015 12:33 AM, Thomas Goirand wrote: >> I missed this announce... > >> On 07/02/2015 05:32 AM, Jeremy Stanley wrote: >>> Per the Icehouse EOL discussion[1] last month, now that the >>> final 2014.1.5 release[2] is behind us I have followed

Re: [openstack-dev] [all][tests] Fix it friday! [mock failure in CI]

On 14 July 2015 at 22:41, Kevin Benton wrote: > Oh, no I didn't. By the time I got around to it I saw 264 and figured that > would cover the issue. Ok - could you check? 1.1.3 has issue 264 fixed, and I'd like to fix this one too, if its still an issue. Bonus points for checking against 3.5's uni

Re: [openstack-dev] [all][tests] Fix it friday! [mock failure in CI]

On 13 July 2015 at 13:04, Dave McCowan (dmccowan) wrote: > Has anyone else seen this error with the new mock? > > 'self' parameter lacking default value > > > My function under test runs correctly, but then Mock throws this TypeError > when comparing the parameters in assert_calls_with(). > >

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

On 07/14/2015 03:55 AM, Jeremy Stanley wrote: > On 2015-07-14 00:33:52 +0200 (+0200), Thomas Goirand wrote: > [...] >> I believe I asked you about 10 times to keep these branches alive, so >> that distributions could work together on a longer support, even without >> a CI behind it. > > And the pr

Re: [openstack-dev] [Heat] conditional resource exposure - second thoughts

On 07/14/2015 02:46 PM, Clint Byrum wrote: > Excerpts from Pavlo Shchelokovskyy's message of 2015-07-14 11:34:37 -0700: >> Hi Heaters, >> >> currently we already expose to the user only resources for services >> deployed in the cloud [1], and soon we will do the same based on whether >> actual user

Re: [openstack-dev] OpenStack Mitaka (三鷹) - Our next release name has been selected

On 7/14/15, 13:47, "Monty Taylor" wrote: >Hi everybody! > >Ok. There is nothing more actually useful I can say that isn't in the >subject line. As I mentioned previously, the preliminary results from >our name election are here: > >http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8d

Re: [openstack-dev] [Openstack] Rescinding the M name decision

Good news. After finalizing the trademark checks and giving the community time to weigh in, Mitaka will be the name of the M release. Thanks again for the great discussion around this topic, and for the willingness to be responsive to the concerns of fellow community members. > On Jul 9, 2015

[openstack-dev] OpenStack Mitaka (三鷹) - Our next release name has been selected

Hi everybody! Ok. There is nothing more actually useful I can say that isn't in the subject line. As I mentioned previously, the preliminary results from our name election are here: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc As you are all probably aware by now, as a fol

Re: [openstack-dev] [Heat] conditional resource exposure - second thoughts

Excerpts from Pavlo Shchelokovskyy's message of 2015-07-14 11:34:37 -0700: > Hi Heaters, > > currently we already expose to the user only resources for services > deployed in the cloud [1], and soon we will do the same based on whether > actual user roles allow creating specific resources [2]. Her

Re: [openstack-dev] [magnum] The way magnum-conductor communicates with k8s master

From: Adrian Otto mailto:adrian.o...@rackspace.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, July 14, 2015 at 11:11 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-d

[openstack-dev] [Heat] conditional resource exposure - second thoughts

Hi Heaters, currently we already expose to the user only resources for services deployed in the cloud [1], and soon we will do the same based on whether actual user roles allow creating specific resources [2]. Here I would like to get your opinion on some of my thoughts regarding behavior of resou

Re: [openstack-dev] [magnum][bp] Power Magnum to run on metal withHyper

Peng, On Jul 13, 2015, at 8:37 PM, Peng Zhao mailto:p...@hyper.sh>> wrote: Thanks Adrian! Hi, all, Let me recap what is hyper and the idea of hyperstack. Hyper is a single-host runtime engine. Technically, Docker = LXC + AUFS Hyper = Hypervisor + AUFS where AUFS is the Docker image. I do not

[openstack-dev] [Congress] New IRC meeting time

To better accommodate the active contributors, we're moving our IRC meeting to 2300 UTC = 4p Pacific = 7p Eastern #openstack-meeting-3 Hope to see you there! Tim __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [magnum] The way magnum-conductor communicates with k8s master

On Jul 13, 2015, at 8:40 PM, Steven Dake (stdake) mailto:std...@cisco.com>> wrote: From: "OTSUKA, Motohiro" mailto:yuany...@oeilvert.org>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, July 13, 2015 at 8:11 PM

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2015 01:46 AM, Perry, Sean wrote: -Original Message- From: Doug Hellmann [mailto:d...@doughellmann.com] Sent: Monday, July 13, 2015 3:41 PM To: openstack-dev Subject: Re: [openstack-dev] [all] Time to remove

Re: [openstack-dev] [neutron] Should we document the using of "device:owner" of the PORT ?

Yes please. This would be a good starting point. I also think that the ability of editing it, as well as the value it could be set to, should be constrained. As you have surely noticed, there are several code path which rely on an appropriate value being set in this attribute. This means a user c

[openstack-dev] [mistral] A new BP - Support large datasets being passed

Hey, I have created a new BP "Support large datasets being passed" [1]. You comments / suggestion / approval are most welcome. [1] - https://blueprints.launchpad.net/mistral/+spec/support-large-datasets __ OpenStack Developme

Re: [openstack-dev] [requirements][all] policy on approving constraint changes

On 2015-07-14 11:12:03 -0400 (-0400), Doug Hellmann wrote: > At one point Robert proposed that we change the policy for approving > constraint changes like https://review.openstack.org/#/c/201408/ to > allow a single reviewer to approve it, assuming the tests were green. > Is that our current polic

Re: [openstack-dev] [nova] Reminder: July 16 is non-priority feature proposal freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/14/2015 05:52 AM, John Garbutt wrote: > Please note, the non-priority feature freeze is on: July 30 Exception: subject and body not in agreement. :) - -- - -- Ed Leafe -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - ht

Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?

On 7/14/2015 5:51 AM, Markus Zoeller wrote: Markus Zoeller/Germany/IBM@IBMDE wrote on 07/10/2015 03:55 [...] So you have a bunch of bugs that are Confirmed (or Triaged) + an assignee set. I would argue that you need to separate two cases: the bug had no activity for the last 60 days: assign

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Thanks Akihiro. Currently lbaas panels are part of horizon repo. If there is a easy way to de-couple lbaas dashboard from horizon? I think that will simplify development efforts. What does it take to separate lbaas dashboard from horizon? Thanks, Vivek From: Akihiro Motoki mailto:amot...@gmail.

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

1600utc on Thursday (9am PDT Thursday) works for me. Can we use #openstack-lbaas channel ? I have committed under development lbaas v2 horizon code to my public github and will move it to neutron-lbaas: https://github.com/openstack/neutron-lbaas Thanks, Vivek From: Doug Wiegley mailto:doug..

[openstack-dev] [app-catalog] IRC Meeting Thursday July 16th at 17:00UTC

(Apologies for the re-send, missed the appropriate tag on the subject line!) Hello! Our next OpenStack App Catalog meeting will take place this Thursday July 16th at 17:00 UTC in #openstack-meeting-3 The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog Please add ag

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Another option is to create a project under openstack. designate-dashboard project takes this approach, and the core team of the project is both horizon-core and designate-core. We can do the similar approach. Thought? I have one question. Do we have a separate place forever or do we want to merge

[openstack-dev] [Senlin] TOSCA Reference Material

Hi All, I just wanted to share where all of the TOSCA reference material is accessible. It is maintained through an OASIS TC here -> https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca The latest relevant spec is available here -> https://www.oasis-open.org/committees/download.p

[openstack-dev] Meeting Thursday July 16th at 17:00UTC

Hello! Our next OpenStack App Catalog meeting will take place this Thursday July 16th at 17:00 UTC in #openstack-meeting-3 The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog Please add agenda items if there's anything specific you would like to discuss. For this w

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

inline... On 7/8/15, 8:23 AM, "Bogdan Dobrelya" wrote: >>> On 6/12/15, 3:55 PM, "Clint Byrum" wrote: >>> >>> > >>> >> >>> > >>> >I think you missed "it is not tested in the gate" as a root cause for >>> >some of the ambiguity. Anecdotes and bug reports are super important >>>for >>> >knowing

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Can we setup a short IRC meeting to sync up on details? 1600utc on thursday, maybe? Other? Thanks, doug > On Jul 13, 2015, at 4:02 PM, Praveen Yalagandula > wrote: > > Hi Vivek, > > I can help on this effort. Thanks for leading this! > > We had done some work to add "Certificates" support

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

I’d be good submitting it to the neutron-lbaas repo, under a horizon/ directory. We can iterate there, and talk with the Horizon team about how best to integrate. Would that work? Thanks, doug > On Jul 13, 2015, at 3:05 PM, Jain, Vivek wrote: > > Hi German, > > We integrated UI with LBaaS v2

Re: [openstack-dev] [magnum] Magnum Midcycle Event Scheduling Doodle Poll closes July 7th

Team, Thanks everyone for your feedback. The Magnum Midcycle for the Liberty release will be held on 2015-08-05 and 2015-08-06. I look forward to seeing you all there. Regards, Adrian Otto On Jul 1, 2015, at 11:03 AM, Steven Dake (stdake) mailto:std...@cisco.com>> wrote: Apologies for doubl

Re: [openstack-dev] [puppet] First Sprint proposal

We decided during our weekly meeting that the Sprint will happen virtually on IRC on Wed 9/2 – Fri 9/4. We will use #openstack-sprint (freenode) IRC channel and Google Hangout / Bluejeans if needed. We made progress on defining an agenda: https://etherpad.openstack.org/p/puppet-liberty-mid-cycle

Re: [openstack-dev] [puppet] weekly meeting #42

On 07/13/2015 09:23 AM, Emilien Macchi wrote: > Hello Puppet masters! > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150714 > > Please ad

Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core

Thanks very much all it's a privilege. Look forward to continuing to help out as much as possible; please feel free to drop me a line on IRC or email any time. -Paul On 14/07/15 17:01, Steven Dake (stdake) wrote: Well that is unanimous. Welcome to the core team Paul! Regards -steve From:

Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core

Well that is unanimous. Welcome to the core team Paul! Regards -steve From: "Daneyon Hansen (danehans)" mailto:daneh...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, July 14, 2015 at 8:56 AM To: "

Re: [openstack-dev] [Cinder] Quobyte Cinder Driver revert?

Thanks for the hint, Ramy! I did talk about this a longer time ago in the 3rdParty weekly but it was hard to for people to help as it was an issue quite specific to our setup. On other occasions, however, that meeting has been greatly helpful and I recommend it, too! Silvan 2015-07-07 6:01 GMT+02

[openstack-dev] [Cinder] FFE Request: Re-add Quobyte Cinder Driver

Hello Cinder Community! I'd like to request a feature freeze exception for change [1], re-adding the Quobyte driver to Cinder. The driver was removed in change [2] due to missing CI activity [3], it was originally added in the kilo release [4]. We've been able to remove the CI's issues and it ha

Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core

+1 From: "Steven Dake (stdake)" mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, July 13, 2015 at 7:40 PM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstac

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 07/14/2015 11:08 AM, Ian Cordasco wrote: > > > On 7/13/15, 16:19, "Joshua Harlow" wrote: > >> Ian Cordasco wrote: >>> >>> On 7/13/15, 15:09, "Dave Walker" wrote: >>> On 13 Jul 2015 8:52 pm, "Ian Cordasco" wrote: > On 7/13/15, 03:38, "Thierry Carrez" wrote: >> By "co

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/13/15, 16:19, "Joshua Harlow" wrote: >Ian Cordasco wrote: >> >> On 7/13/15, 15:09, "Dave Walker" wrote: >> >>> On 13 Jul 2015 8:52 pm, "Ian Cordasco" >>>wrote: On 7/13/15, 03:38, "Thierry Carrez" wrote: >>> > By "counter-productive", I meant: likely to generate more confusion >

[openstack-dev] [requirements][all] policy on approving constraint changes

At one point Robert proposed that we change the policy for approving constraint changes like https://review.openstack.org/#/c/201408/ to allow a single reviewer to approve it, assuming the tests were green. Is that our current policy, or are we waiting for the integration of constraints with our to

Re: [openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

Excerpts from Jeremy Stanley's message of 2015-07-14 13:08:46 +: > On 2015-07-14 08:38:57 -0400 (-0400), Sean Dague wrote: > > There is trove classification in the projects themselves right? > [...] > > That seems like it should be enough information to know the 2.6 question. > > I got to thin

[openstack-dev] Hyper-V Meeting

Hi All, We still have a lack of quorum today do to summer holidays, so we're postponing until everyone is back. p Peter J. Pouliot CISSP Microsoft Enterprise Cloud Solutions C:\OpenStack New England Research & Development Center 1 Memorial Drive Cambridge, MA 02142 P: 1.(857).4536436 E: ppoul..

[openstack-dev] [docs] [tc] Project and service names

Hi all, Renamed the thread to get some topics in the subject, and I wanted to bring this review to everyone's attention. https://review.openstack.org/#/c/201160/ I will reconsider these guidelines based on feedback. That said, I have done the legwork to ask about legal guidance and I still believ

Re: [openstack-dev] [neutron] Adding results to extension callbacks (ml2 port_update ext handling).

I haven't had a chance to review this patch in detail yet, but am wondering if this is being integrated with ML2 as an extension driver? If so, that should clearly address how dictionaries are extended and input values are validated. If not, why? -Bob On 7/13/15 10:50 PM, Miguel Angel Ajo wro

Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core

On Tue, Jul 14, 2015 at 01:56:16PM +0200, Harm Weites wrote: no-brainer: +1 Op 14-07-15 om 13:19 schreef Ryan Hallisey: +1 I echo all the prior comments. -Ryan - Original Message - From: "Steven Dake (stdake)" To: "OpenStack Development Mailing List (not for usage questions)" Sent

Re: [openstack-dev] [Murano] Versioning of Murano packages and MuranoPL classes

Alexander, do you plan to update the https://review.openstack.org/#/c/140402/  versioning spec? We can possibly try to make it a joint effort, if you like. --  Kirill Zaitsev Murano team Software Engineer Mirantis, Inc On 14 Jul 2015 at 11:34:56, Alexander Tivelkov (ativel...@mirantis.com) wrote

Re: [openstack-dev] Cinder as generic volume manager

On 07/10/2015 12:19 AM, Walter A. Boring IV wrote: > On 07/09/2015 12:21 PM, Tomoki Sekiyama wrote: >> Hi all, >> >> Just FYI, here is a sample script I'm using for testing os-brick which >> attaches/detaches the cinder volume to the host using cinderclient and >> os-brick: >> >> https://gist.githu

Re: [openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

On 2015-07-14 08:38:57 -0400 (-0400), Sean Dague wrote: > There is trove classification in the projects themselves right? [...] > That seems like it should be enough information to know the 2.6 question. I got to thinking through what this might look like, and while filtering down the markers base

Re: [openstack-dev] [Fuel] Separate repo for Fuel Agent

Dear colleagues, New repository [1] has been created. So, please port all your review requests to stackforge/fuel-web related to Fuel Agent to this new repository. Currently, I am testing these two patches https://review.openstack.org/#/c/200595 https://review.openstack.org/#/c/200025. If they wor

Re: [openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

On 2015-07-14 08:38:57 -0400 (-0400), Sean Dague wrote: > There is trove classification in the projects themselves right? [...] > That seems like it should be enough information to know the 2.6 question. Only if it's kept up to date. If we're going to rely on it (not a terrible idea) then we shoul

Re: [openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

On 07/14/2015 08:11 AM, Andrey Kurilin wrote: > Hi! > It looks like novaclient still supports py26 :) At least, there is a > gate-python-novaclient-python26 job. > Also, I checked several commands(boot, *list, delete ) with python 2.6 > env and they work as expected for me. Ah, right fair, my bad.

Re: [openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

On 07/14/2015 08:32 AM, Jeremy Stanley wrote: > On 2015-07-14 07:03:34 -0400 (-0400), Sean Dague wrote: >> I just saw this Nova review come in - >> https://review.openstack.org/#/c/200908 >> >> Why are we merging 2.6 requirements for projects that don't support 2.6? >> That seems potentially confus

Re: [openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

On 2015-07-14 07:03:34 -0400 (-0400), Sean Dague wrote: > I just saw this Nova review come in - > https://review.openstack.org/#/c/200908 > > Why are we merging 2.6 requirements for projects that don't support 2.6? > That seems potentially confusing to end users that now think the project > does,

Re: [openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

Hi! It looks like novaclient still supports py26 :) At least, there is a gate-python-novaclient-python26 job. Also, I checked several commands(boot, *list, delete ) with python 2.6 env and they work as expected for me. On Tue, Jul 14, 2015 at 2:03 PM, Sean Dague wrote: > I just saw this Nova rev

Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core

no-brainer: +1 Op 14-07-15 om 13:19 schreef Ryan Hallisey: +1 I echo all the prior comments. -Ryan - Original Message - From: "Steven Dake (stdake)" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Monday, July 13, 2015 10:40:11 PM Subject: [openstack-dev] [

Re: [openstack-dev] [neutron][security-group] rules for filter mac-addresses

Thank you, Kevin. I search the blueprint about this point in launchpad.net, and got nothing, then register one at: https://blueprints.launchpad.net/neutron/+spec/security-group-mac-rule Yan Xing'an From: Kevin Benton Date: 2015-07-14 18:31 To: OpenStack Development Mailing List (not for us

Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core

+1 I echo all the prior comments. -Ryan - Original Message - From: "Steven Dake (stdake)" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Monday, July 13, 2015 10:40:11 PM Subject: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core Hey folks, I

Re: [openstack-dev] [all][heat][oslo] Public show and validation clients methods

Doug, Terry. Thank you for the feedback. I will create a BP with list of desired public methods and will add all projects to it. Regards, Sergey. On 9 July 2015 at 21:20, Doug Hellmann wrote: > Excerpts from Sergey Kraynev's message of 2015-07-09 18:26:09 +0300: > > Hi community. > > > > I wan

[openstack-dev] [requirements] why merging 2.6 requirements for non 2.6 supporting projects

I just saw this Nova review come in - https://review.openstack.org/#/c/200908 Why are we merging 2.6 requirements for projects that don't support 2.6? That seems potentially confusing to end users that now think the project does, because there are still references in the code. -Sean --

Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?

Markus Zoeller/Germany/IBM@IBMDE wrote on 07/10/2015 03:55 > [...] > > > > So you have a bunch of bugs that are Confirmed (or Triaged) + an > > assignee set. I would argue that you need to separate two cases: > > > > the bug had no activity for the last 60 days: assignee should be removed > > >

[openstack-dev] [nova] Reminder: July 16 is non-priority feature proposal freeze

Hi, Please note, the non-priority feature freeze is on: July 30 Blueprint assignees (as always, but especially now), please update your blueprint to: * NeedsCodeReview, once all your code ready for review * Implemented, once all your code has merged Not doing this, will force me to guess randomly

  1   2   >