Re: [openstack-dev] [Fuel][Plugins] add health check for plugins

Hi, Totally agree with you Andrey, other use cases could be : -for Ironic plugin, add test to validate that Ironic is properly deploy -for LMA plugin check that metric and log are properly collect, that elk, nagios or grafana dashboard are accessible -for cinder netapp multi backend, check that di

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

Le 25/09/2015 16:12, Andrew Laski a écrit : On 09/24/15 at 03:13pm, James Penick wrote: At risk of getting too offtopic I think there's an alternate solution to doing this in Nova or on the client side. I think we're missing some sort of OpenStack API and service that can handle this. N

Re: [openstack-dev] [oslo] nominating Brant Knudson for Oslo core

+1 for Brant Victor Le 24/09/2015 19:12, Doug Hellmann a écrit : Oslo team, I am nominating Brant Knudson for Oslo core. As liaison from the Keystone team Brant has participated in meetings, summit sessions, and other discussions at a level higher than some of our own core team members. He i

Re: [openstack-dev] [murano] Outreachy: Interest in contributing to open-source

Hi Yolande, welcome to OpenStack and open source! We gladly introduce you with Murano project! Topic 'Implementation of tagging heat stacks, created by murano' is already taken, but we can offer you another one after talking to you about what you are interesting in. You can go to #murano channe

[openstack-dev] [mistral] Cancelling team meeting today (09/28/2015)

Mistral Team, We’re cancelling today’s team meeting because a number of key members won’t be able to attend. The next one is scheduled for 5 Oct. Best Regards, Nikolay Makhotkin @Mirantis Inc. __ OpenStack Development Maili

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On Wed, Sep 23 2015, Julien Danjou wrote: […] > I'm willing to clear that out and come with specs and patches if that > can help. :) Following-up on myself, I went ahead and I wrote a more complete version of the current proxy middleware we have – which also supports RFC7239: https://review.

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

As already mentioned, we need to pass [] (an empty list) rather than None as allowed_address_pairs. At the moment it is not supported in Neutron CLI. This review https://review.openstack.org/#/c/218551/ is trying to fix this problem. Akihiro 2015-09-28 15:51 GMT+09:00 shihanzhang : > I don't s

Re: [openstack-dev] [Fuel][Plugins] add health check for plugins

I just realized I missed this thread when Andrey responded to it – apologies! I was thinking of things like – confirming VMware username and password are accurate, confirming that SSL certificate chain is valid, etc. – some of these are not plugin based, but I think there is value in enabling bo

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

The trouble with putting more intelligence in the clients is that there are more clients than just the one we provide, and the more smarts we require in the clients, the more divergence of functionality we're likely to see. Also, bugs and slowly percolating bug fixes. On 28 Sep 2015 11:27, "Sylvain

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

Le 25/09/2015 17:00, Julien Danjou a écrit : If we wanted to enforce that, we would just have to write a bot setting -1 automatically. I'm getting tired of seeing people doing bots' jobs in Gerrit. It may also help to enhance "git review -s" to install a local post-commit hook to warn if the c

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

Le 28/09/2015 11:23, Duncan Thomas a écrit : The trouble with putting more intelligence in the clients is that there are more clients than just the one we provide, and the more smarts we require in the clients, the more divergence of functionality we're likely to see. Also, bugs and slowly

[openstack-dev] [Sahara] Data locality when reading from Swift in MapReduce

Link: https://openstack.nimeyo.com/60317/?show=60317#q60317 From: lukas I'm using the hadoop-swiftfs from the sahara-extra project to read input from Swift during my MapReduce jobs. The hadoop version I am using is 2.6.0 and this already came with the hadoop-openstack additions. I set fs.swift.

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 26/09, Morgan Fainberg wrote: > As a core (and former PTL) I just ignored commit message -1s unless there is > something majorly wrong (no bug id where one is needed, etc). > > I appreciate well formatted commits, but can we let this one go? This > discussion is so far into the meta-bike-she

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

IMO those checks should be automated, as we automate pep8 checks on our python code. I agree, that if we have a rule for this, we should follow it, but it's a waste of time reviewing and enforcing this manually. Best regards. Miguel Ángel. Gorka Eguileor wrote: On 26/09, Morgan Fainberg wrot

[openstack-dev] [Horizon] Horizon Productivity Suggestion

Hi folks, I¹m wondering if we could try marking out a small 2-3 minute slot at the start of each weekly meeting to highlight Critical/ High bugs that have code up for review, as well as important blueprints that have code up for review. These would be blueprints for features that were identified a

Re: [openstack-dev] [all][stable][release][horizon] 2015.1.2

On 25/09/15 15:39, Ihar Hrachyshka wrote: > I see you have three people in the horizon-stable-maint team only. > Have you considered expanding the team with more folks? In > neutron, we have five people in the stable-maint group. Good suggestion! In horizon, we just have a very few cores being

Re: [openstack-dev] [mistral] Cancelling team meeting today (09/28/2015)

Hi, guys, We will have a 7 days holiday in China, which is National Day, from Oct. 1 to Oct. 7. So, I'll miss the next team meeting :( On Mon, Sep 28, 2015 at 4:46 PM, Nikolay Makhotkin wrote: > Mistral Team, > > We’re cancelling today’s team meeting because a number of key members won’t > be ab

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 28 September 2015 at 12:35, Sylvain Bauza wrote: > About the maintenance burden, I also consider that patching clients is far > more easier than patching an API unless I missed something. > > I think I very much disagree there - patching a central installation is much, much easier than getting

Re: [openstack-dev] Murano code flow for custom development and combining murano with horizon in devstack

Hi, murano-dashboard works the same way any other horizon dashboard does. I’m not quite sure, what you meant by «combined and showed under one tab», could you please elaborate? If you’re asking about debugging — you can install murano-dashboard locally and configure it to use remote cloud (i.e.

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/28/2015 05:01 AM, Julien Danjou wrote: > On Wed, Sep 23 2015, Julien Danjou wrote: > > > […] > >> I'm willing to clear that out and come with specs and patches if that >> can help. :) > > Following-up on myself, I went ahead and I wrote a more complete version > of the current proxy middl

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 09/25/2015 08:16 PM, Monty Taylor wrote: > On 09/25/2015 06:37 PM, Chris Hoge wrote: >> >>> On Sep 25, 2015, at 10:12 AM, Andrew Laski >> > wrote: >>> >>> I understand that reasoning, but still am unsure on a few things. >>> >>> The direction seems to be moving towards

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 09/27/2015 08:43 AM, Doug Hellmann wrote: > Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: >> On Sep 25, 2015, at 1:56 PM, Doug Hellmann wrote: >>> >>> Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: >> >> Ah. Thanks for bringing that up, because I think

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 2015-09-28 11:47, Gorka Eguileor wrote: On 26/09, Morgan Fainberg wrote: As a core (and former PTL) I just ignored commit message -1s unless there is something majorly wrong (no bug id where one is needed, etc). I appreciate well formatted commits, but can we let this one go? This discussi

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 28 September 2015 at 12:10, Sean Dague wrote: > On 09/27/2015 08:43 AM, Doug Hellmann wrote: >> Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: >>> On Sep 25, 2015, at 1:56 PM, Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +:

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

Please help, its not working: root@openstack-latest-kilo-28-09-2015-masoom:/opt/stack/devstack# neutron port-show 2d1bfe12-7db6-4665-9c98-6b9b8a043af9 +---+-+ | Field | Value

[openstack-dev] [nova] Liberty and Nova Specs, Blueprints and Design Summit for Mitaka

Hi, A quick update on where we are at. Liberty - Its time to give RC1 an good test. We need to keep our eyes out for release blockers, using this tag: https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential We will need an new tag on or after 8th October, to include transl

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 28/09, Andreas Jaeger wrote: > On 2015-09-28 11:47, Gorka Eguileor wrote: > >On 26/09, Morgan Fainberg wrote: > >>As a core (and former PTL) I just ignored commit message -1s unless there > >>is something majorly wrong (no bug id where one is needed, etc). > >> > >>I appreciate well formatted c

[openstack-dev] [puppet] weekly meeting #53

Hello! 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-20150929 Feel free to add any additional items you'd like to discuss. If our schedule allows it, we'll make bug triage during the

[openstack-dev] [ptls] Asserting that your projects follow at least the base deprecation policy

Hi everyone, Last week at the Technical Committee meeting, following the discussion on this mailing-list a few weeks ago, we finally passed a definition[1] for a standard base deprecation policy for OpenStack projects. [1] http://governance.openstack.org/reference/tags/assert_follows-standard-dep

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza > wrote: About the maintenance burden, I also consider that patching clients is far more easier than patching an API unless I missed something. I think I very mu

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

Excerpts from John Garbutt's message of 2015-09-28 12:32:53 +0100: > On 28 September 2015 at 12:10, Sean Dague wrote: > > On 09/27/2015 08:43 AM, Doug Hellmann wrote: > >> Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: > >>> On Sep 25, 2015, at 1:56 PM, Doug Hellmann wrote: >

[openstack-dev] [Solum] Proposal to change weekly IRC meeting time

Hi team, In last week's IRC meeting [1], we discussed about changing our weekly IRC meeting time from current time of 2100 UTC to 1700 UTC to, (a) avoid conflict with the cross-project meeting, and (b) accommodate participants from India/Asia. I have submitted a WIP review [2] to make this cha

Re: [openstack-dev] [murano] Outreachy: Interest in contributing to open-source

Hi Yolande, Welcome! Glad to hear you already have a project/mentor in mind. Ekaterina will help you with your first contribution and on picking a task for your internship application. Please let me know if I can help on how to setup your contributor accounts/development environment, or with the a

Re: [openstack-dev] [TripleO] tripleo.org theme

On Fri, Sep 25, 2015 at 8:34 AM, Dan Prince wrote: > It has come to my attention that we aren't making great use of our > tripleo.org domain. One thing that would be useful would be to have the > new tripleo-docs content displayed there. It would also be nice to have > quick links to some of our u

Re: [openstack-dev] [glance] [infra] [neutron] [swift] [trove] [zaqar] [murano] [docs] Outreachy: selecting a project to contribute to

Hi Twinkle, Welcome! Please join us in #openstack-opw channel on irc.freenode.org. We can chat about different projects and helping you get started with OpenStack. Best, Victoria 2015-09-26 11:19 GMT-03:00 Anne Gentle : > Hi Twinkle, > > Welcome! Thanks for your interest. If you have time, sto

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza mailto:sba...@redhat.com>> wrote: About the maintenance burden, I also consider that patching clients is far more easier than patching an API unless

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

This is even not working: root@openstack-latest-kilo-28-09-2015-masoom:/opt/stack/devstack/accrc/admin# neutron port-update e5b05961-e5d0-481b-bbd0-2ce4bbd9ea64 --allowed-address-pairs type=list [] action=clear AllowedAddressPair must contain ip_address root@openstack-latest-kilo-28-09-2015-mas

[openstack-dev] [all] Proposed Mitaka release schedule

Hi everyone, You can find the proposed release schedule for Mitaka here: https://wiki.openstack.org/wiki/Mitaka_Release_Schedule That places the end release on April 7, 2016. It's also worth noting that in an effort to maximize development time, this schedule reduces the time between Feature Fre

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza mailto:sba...@redhat.com>> wrote: About the maintenance burden, I also consider that patching clients is

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/2015 10:11 AM, Andrew Laski wrote: > On 09/28/15 at 08:50am, Monty Taylor wrote: >> On 09/28/2015 07:58 AM, Sylvain Bauza wrote: >> >> Specifically, I want "nova boot" to get me a VM with an IP address. I >> don't want it to do fancy orchestration - I want it to not need fancy >> orchestr

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. In other timezones the meeting is at: EST 08:00 (Tue) Japan 21:00 (Tue) China 20:00 (Tue) United Kingdom 13:00 (Tue) The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meeti

[openstack-dev] [devstack] Is there a way to configure devstack for one flat external network using Kilo, Neutron?

Is there a way to configure devstack to install Neutron such that there is just one network and that is an external network and Nova can create Compute Instances on it, using projects of Kilo vintage? Thanks, Mike __ Open

Re: [openstack-dev] [all] Proposed Mitaka release schedule

Hi Thierry, Thank you for sharing this information with us so early. One comment/question from me about FinalClientLibraryRelease: Could we make client release at least one week later after M-3 milestone? It will give us more chances to have features landed into the client if they were merged lat

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

> From: Monty Taylor > To: Sylvain Bauza , "OpenStack Development > Mailing List (not for usage questions)" > Date: 09/28/2015 09:54 AM > Subject: Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how > to handle AZ bug 1496235?) > > ... > Specifically, I want "nova boot" to get me a VM w

[openstack-dev] [election] [tc] Candidacy for Technical Committee

Hi all, I'm writing to let you know I would like to run for Technical Committee again this term. Here is my candidacy statement for your review. I have worked at Rackspace on the OpenStack collection of projects for five years now, working primarily on documentation. Rackspace is one of the foun

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

Le 28/09/2015 16:19, Sean Dague a écrit : On 09/28/2015 10:11 AM, Andrew Laski wrote: On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Specifically, I want "nova boot" to get me a VM with an IP address. I don't want it to do fancy orchestration - I w

[openstack-dev] [nova][infra] Intel NFV CI, testing hugepages, numa topology, cpu pinning

Hi cores et al, As discussed briefly with Jay Pipes in Vancouver, we were about to provide CI and tests for features such as: hugepages, cpu pinning, numa topology. We since worked on NFV CI here at Intel. The work on the CI and tests is now completed. A few details about the CI and tests. * CI

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/26/2015 12:04 AM, Joshua Harlow wrote: +1 from me, although I thought heat was supposed to be this thing? Maybe there should be a 'warm' project or something ;) Or we can call it 'bbs' for 'building block service' (obviously not bulletin board system); ask said service to build a set of b

[openstack-dev] [ceilometer] OpenStack Telemetry user survey

Hello, The OpenStack Telemetry (aka Ceilometer) team would like to collect feedback and information from its user base in order to drive future improvements to the project. To do so, we have developed a survey. It should take about 15min to complete. Questions are fairly technical, so please

Re: [openstack-dev] [murano] Murano code flow for custom development and combining murano with horizon in devstack

Thanks Kirill. Would adding "[murano]” to the subject line suffice or pls let me know if there is a separate mailing list for murano? Let me try to clarify what I am asking over here. So we have all these panels - 'Compute', 'Network', etc on Horizon dashboard. If I add another panel like 'Exampl

Re: [openstack-dev] [Barbican][Security] Automatic Certificate Management Environment

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Rob, I agree that the ACME standard is very interesting, but I'm also pretty new to it. And by pretty new I mean I just started reading it after I saw your email. :) There has been interest in adding support for Let's Encrypt as a Barbican back

[openstack-dev] [puppet] Moving puppet-ceph to the Openstack big tent

Hi, puppet-ceph currently lives in stackforge [1] which is being retired [2]. puppet-ceph is also mirrored on the Ceph Github organization [3]. This version of the puppet-ceph module was created from scratch and not as a fork of the (then) upstream puppet-ceph by Enovance [4]. Today, the version b

Re: [openstack-dev] [murano] Murano code flow for custom development and combining murano with horizon in devstack

Hi 1) adding [murano] would definitely suffice 2) Seems that you want to combine some of the murano panels under your own dashboard, right? (I do not really see why would you want to do that, but still). I believe that it is possible. You can look at muranodashboard/dashboard.py file. It defin

[openstack-dev] [election][tc] TC Candidacy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Greetings Stackers! I'm announcing my candidacy for the Technical Committee Elections. Those of you who have been involved in OpenStack most likely know me, as I was part of the original team from Rackspace that created OpenStack in 2010. For the pa

Re: [openstack-dev] [TripleO] tripleo.org theme

On 2015-09-28 09:43:37 -0400 (-0400), James Slagle wrote: > Would the content of tripleo-docs be exactly the same as what is > published at http://docs.openstack.org/developer/tripleo-docs/ ? > > I think it probably should be, and be updated on every merged commit. > If that's not the case, I thin

[openstack-dev] [Infra] Meeting Tuesday September 29th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday September 29th[0], at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone i

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

Are you reading our reply comments? At the moment, there is no way to set allowed-address-pairs to an empty list by using neutron CLI. When action=clear is passed, type=xxx, list=true and specified values are ignored and None is sent to the server. Thus you cannot set allowed-address-pairs to [] wi

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/15 at 10:19am, Sean Dague wrote: On 09/28/2015 10:11 AM, Andrew Laski wrote: On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Specifically, I want "nova boot" to get me a VM with an IP address. I don't want it to do fancy orchestration - I wa

Re: [openstack-dev] [fuel] PTL & Component Leads elections

> On 18 Sep 2015, at 04:39, Sergey Lukjanov wrote: > > > Time line: > > PTL elections > * September 18 - September 28, 21:59 UTC: Open candidacy for PTL position > * September 29 - October 8: PTL elections Just a reminder that we have a deadline for candidates today. Regards, -- Tomasz 'Zen'

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 28/09/15 05:47, Gorka Eguileor wrote: On 26/09, Morgan Fainberg wrote: As a core (and former PTL) I just ignored commit message -1s unless there is something majorly wrong (no bug id where one is needed, etc). I appreciate well formatted commits, but can we let this one go? This discussion

[openstack-dev] [Designate] Topics for Design Summit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, Just a reminder that this etherpad is still nearly empty :). https://etherpad.openstack.org/p/designate-design-summit-tokyo Can we try and get a few more topics so we can talk about it on Wednesday? Thanks, Graham - -- Graham Hayes Softw

Re: [openstack-dev] [devstack] Is there a way to configure devstack for one flat external network using Kilo, Neutron?

On Mon, Sep 28, 2015 at 7:08 AM, Mike Spreitzer wrote: > Is there a way to configure devstack to install Neutron such that there is > just one network and that is an external network and Nova can create Compute > Instances on it, using projects of Kilo vintage? Mike, this might help, I have a scr

[openstack-dev] [puppet][murano] Launchpad project created

Hi all, as you know murano started creating puppet manifests. They are located at the corresponding repository [1] And this is just a notification, that the separate project [2]to track puppet-related activities is

Re: [openstack-dev] [all] Proposed Mitaka release schedule

Excerpts from Ivan Kolodyazhny's message of 2015-09-28 17:41:46 +0300: > Hi Thierry, > > Thank you for sharing this information with us so early. One > comment/question from me about FinalClientLibraryRelease: > > Could we make client release at least one week later after M-3 milestone? > It will

[openstack-dev] [election] [tc] TC candidacy

I'd like to submit my candidacy for the TC Election. I've been involved with OpenStack since the beginning of the Folsom release. We may have worked together on parts of Nova, Tempest, DevStack, Grenade, or in generally debugging failures in the upstream gate in OpenStack. Or from things like the

Re: [openstack-dev] [puppet] Moving puppet-ceph to the Openstack big tent

On 09/28/2015 08:31 AM, David Moreau Simard wrote: > puppet-ceph currently lives in stackforge [1] which is being retired > [2]. puppet-ceph is also mirrored on the Ceph Github organization [3]. > This version of the puppet-ceph module was created from scratch and > not as a fork of the (then) upst

[openstack-dev] [ironic] [javascript] ironic-webclient seeks more reviewers and contributors

Hey everyone! The ironic webclient is finally moving forward again, however we're at that odd stage where most of the ironic team is Awesome Python and Hardware types, and we're lacking reviewers able to keep an eye on our Angular Javascript code. In the interest of not creating an echo chamber ov

[openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

I've always thought it was a bit strange to require new drivers to merge by milestone 1. I think I understand the motivations of the policy. The main motivation was to free up reviewers to review "other things" and this policy guarantees that for 75% of the release reviewers don't have to revie

Re: [openstack-dev] [Fuel] Code review process in Fuel and related issues

Hi Mike, thanks, now it's clear. On Thu, Sep 3, 2015 at 9:19 AM, Mike Scherbakov wrote: > Thank you all for the feedback. > > > Dims - > > > 1) I'd advise to codify a proposal in fuel-specs under a 'policy' > directory > > I think it's great idea and I'll do it. > > > > 2) We don't have SME term

Re: [openstack-dev] [TripleO] tripleo.org theme

On Fri, 2015-09-25 at 12:31 -0500, Ben Nemec wrote: > On 09/25/2015 07:34 AM, Dan Prince wrote: > > It has come to my attention that we aren't making great use of our > > tripleo.org domain. One thing that would be useful would be to have > > the > > new tripleo-docs content displayed there. It wou

Re: [openstack-dev] [TripleO] tripleo.org theme

On Mon, 2015-09-28 at 09:43 -0400, James Slagle wrote: > On Fri, Sep 25, 2015 at 8:34 AM, Dan Prince > wrote: > > It has come to my attention that we aren't making great use of our > > tripleo.org domain. One thing that would be useful would be to have > > the > > new tripleo-docs content displaye

Re: [openstack-dev] [Congress] hands on lab

Hi Alex, I went through the HOL. Some feedback... 1. When starting up, it paused for a while showing the following messages. Maybe that caused the issues I mention below. Waiting for network configuration... Waiting up to 60 more seconds for network configuration... 2. Maybe spell out the fi

Re: [openstack-dev] [Congress] Congress Usecases VM

When I tried to import the image, it gave me an error. Could not create the imported medium '/Users/tim/VirtualBox VMs/Congress_Usecases/Congress_Usecases_SEPT_25_2015-disk1.vmdk' . VMDK: Compressed image is corrupted '/Congress_Usecases_SEPT_25_2015-disk1.vmdk' (VERR_ZIP_CORRUPTED). Tim On

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

I can definitely see your logic, but we've a history in cinder of vendors trying to cram drivers in at the last minute which we very much wanted to stop dead. I might suggest that the second milestone, rather than the first might be a better one to dedicate to driver reviews... An interesting thin

Re: [openstack-dev] [TripleO] tripleo.org theme

On Mon, 2015-09-28 at 16:04 +, Jeremy Stanley wrote: > On 2015-09-28 09:43:37 -0400 (-0400), James Slagle wrote: > > Would the content of tripleo-docs be exactly the same as what is > > published at http://docs.openstack.org/developer/tripleo-docs/ ? > > > > I think it probably should be, and

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On Mon, Sep 28, 2015 at 11:29 AM, Ben Swartzlander wrote: > I've always thought it was a bit strange to require new drivers to merge > by milestone 1. I think I understand the motivations of the policy. The > main motivation was to free up reviewers to review "other things" and this > policy guar

[openstack-dev] [Fuel] Fuel PTL Candidacy

Fuelers I am glad that Fuel is becoming more open as a project and is heading towards Openstack BigTent which should allow our project to scale and become one of the default OpenStack installers not only for a fraction of end users but for a significant amount of OpenStack developers also. Althoug

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On Mon, Sep 28, 2015 at 12:11 PM, Duncan Thomas wrote: > I can definitely see your logic, but we've a history in cinder of vendors > trying to cram drivers in at the last minute which we very much wanted to > stop dead. I might suggest that the second milestone, rather than the first > might be a

Re: [openstack-dev] [neutron] congrats to armax!

On 25 September 2015 at 17:03, Ryan Moats wrote: > First, congratulations to armax on being elected PTL for Mitaka. Looking > forward to Neutron improving over the next six months. > > Second thanks to everybody that voted in the election. Hopefully we had > something close to 100% turnout, becau

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On 09/28/2015 10:29 AM, Ben Swartzlander wrote: I've always thought it was a bit strange to require new drivers to merge by milestone 1. I think I understand the motivations of the policy. The main motivation was to free up reviewers to review "other things" and this policy guarantees that for

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Sep 21) - Open: 135 (-1). 9 new (+2), 36 in progress (-5), 0 critical, 7 high (-5) and 9 incomplete - Nova bugs with Ironic tag: 2

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On 09/28/2015 02:42 PM, Walter A. Boring IV wrote: On 09/28/2015 10:29 AM, Ben Swartzlander wrote: I've always thought it was a bit strange to require new drivers to merge by milestone 1. I think I understand the motivations of the policy. The main motivation was to free up reviewers to review

[openstack-dev] Openvswitch agent unit tests

Hello, I'm new developer who want to start contributing to neutron. I have some small experience with neutron already but I didn't do anything which I could push to upstream for now. So I searched for some bug on launchpad and I found such bug which I took: https://bugs.launchpad.net/neutron/+bug/

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On Sep 28, 2015, at 9:03 AM, Doug Hellmann wrote: > > Excerpts from John Garbutt's message of 2015-09-28 12:32:53 +0100: >> On 28 September 2015 at 12:10, Sean Dague wrote: >>> On 09/27/2015 08:43 AM, Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: >>

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

>I see a clear line between something that handles the creation of all ancillary resources needed to boot a VM and then the creation of the VM itself. I agree. To me the line is the difference between creating a top level resource, and adding a host to that resource. For example, I do expect a to

[openstack-dev] [all] devstack default worker changes

We used to default to using the mysqldb driver in devstack, which is a C binding that is not eventlet aware. This means that any time a db query is executed the entire greenlet is blocked. This behavior meant that in devstack (and in oslo.concurrency) default number of workers for things like API s

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On Mon, Sep 28, 2015 at 12:13:04PM -0600, John Griffith wrote: > On Mon, Sep 28, 2015 at 11:29 AM, Ben Swartzlander > wrote: > > > I've always thought it was a bit strange to require new drivers to merge > > by milestone 1. I think I understand the motivations of the policy. The > > main motivati

[openstack-dev] [release][requirements] changes to the requirements-core team

It has been a while since we've reviewed the requirements-core team members. Since it's the end of the cycle, I did a quick scan of the stats this week and I am proposing some changes based on participation. I spoke with Ghe Rivero and Julien Danjou, both of whom have done good work in the past bu

[openstack-dev] [fuel] PTL Candidacy

I'd like to announce my candidacy as Fuel PTL for the next cycle. It is our very first election, so we are taking our time to make sure we get everything right. We have extended the nomination period to September 28 [0] to give Fuel contributors more time to learn about the OpenStack governance pr

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

Excerpts from Mark Voelker's message of 2015-09-28 19:55:18 +: > On Sep 28, 2015, at 9:03 AM, Doug Hellmann wrote: > > > > Excerpts from John Garbutt's message of 2015-09-28 12:32:53 +0100: > >> On 28 September 2015 at 12:10, Sean Dague wrote: > >>> On 09/27/2015 08:43 AM, Doug Hellmann wrot

Re: [openstack-dev] [all] devstack default worker changes

This is great news indeed, Sean. :) On 09/28/2015 04:02 PM, Sean Dague wrote: We used to default to using the mysqldb driver in devstack, which is a C binding that is not eventlet aware. This means that any time a db query is executed the entire greenlet is blocked. This behavior meant that in d

[openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Tim and Congress folks, I am writing on behalf of the Monasca community and I would like to explore the possibility of holding a joint session during the Tokyo Design Summit. We would like to explore: 1. how to integrate Monasca with Congress so then Monasca can provide metrics, logs and ev

Re: [openstack-dev] Openvswitch agent unit tests

Generally speaking, testing agent methods that interact with the system heavily with unit tests provide very little, and arguably negative value to the project. Mocking internal methods and asserting that they were called is a clear anti-pattern to my mind. In Neutron-land we prefer to test agent c

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

The Neutron team also discussed this in Vancouver, you can see the etherpad here [1]. We talked about the idea of creating a validation suite, and it sounds like that's something we should again discuss in Tokyo for the Mitaka cycle. I think a validation suite would be a great step forward for Neut

[openstack-dev] [Ironic] Preparing for functional testing in Ironic. Will likely break any in-flight patches.

Just to give a heads up to people. I have proposed the following patch: https://review.openstack.org/228612 This moves the tests in ironic/tests/ to ironic/tests/unit/ Likely this patch will break most in-flight patches, so rebasing will be required when this patch goes in. If you have any ques

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Mon, Sep 28, 2015 at 12:40 PM, Zane Bitter wrote: > On 28/09/15 05:47, Gorka Eguileor wrote: > >> On 26/09, Morgan Fainberg wrote: >> >>> As a core (and former PTL) I just ignored commit message -1s unless >>> there is something majorly wrong (no bug id where one is needed, etc). >>> >>> I app

Re: [openstack-dev] [release][requirements] changes to the requirements-core team

All sounds good to me. -Rob On 29 September 2015 at 09:16, Doug Hellmann wrote: > It has been a while since we've reviewed the requirements-core team > members. Since it's the end of the cycle, I did a quick scan of the > stats this week and I am proposing some changes based on participation. >

Re: [openstack-dev] [Ironic] Preparing for functional testing in Ironic. Will likely break any in-flight patches.

On Mon, Sep 28, 2015 at 09:00:07PM +, Villalovos, John L wrote: > Just to give a heads up to people. I have proposed the following patch: > https://review.openstack.org/228612 > > This moves the tests in ironic/tests/ to ironic/tests/unit/ > > Likely this patch will break most in-flight patch

Re: [openstack-dev] [release][requirements] changes to the requirements-core team

On 09/28/2015 04:16 PM, Doug Hellmann wrote: > It has been a while since we've reviewed the requirements-core team > members. Since it's the end of the cycle, I did a quick scan of the > stats this week and I am proposing some changes based on participation. > > I spoke with Ghe Rivero and Julien

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

Excerpts from Morgan Fainberg's message of 2015-09-26 23:36:09 -0700: > As a core (and former PTL) I just ignored commit message -1s unless there is > something majorly wrong (no bug id where one is needed, etc). > > I appreciate well formatted commits, but can we let this one go? This > discus

  1   2   >