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] [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

[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] [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: >

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

[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

[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

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] [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] 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

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] [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 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] [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] [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] 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] 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] [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] [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

[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] -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

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

[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] 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

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?)

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] [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] 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] [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.

[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] [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

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] 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] [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

<    1   2