Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

+1 Best regards, Alexey Stepanov. чт, 8 сент. 2016 г., 12:19 Bulat Gaifullin : > +1 > > Regards, > Bulat Gaifullin > Mirantis Inc. > > > > On 08 Sep 2016, at 12:05, Georgy Kibardin wrote: > > +1 > > On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky

Re: [openstack-dev] [oslo] [telemetry] [requirements] [FFE] Oslo.db 4.13.2

On Thu, Sep 08, 2016 at 09:21:57AM -0500, Matthew Thode wrote: > Ya that makes sense, the patch can be altered to just block 4.13.1,2 > (assuming 4.13.3 really does fix it) I feel like we've gotten ourselves (well at least I'm confused) about what we're trying to achieve here. It seem to be the

[openstack-dev] What's Up, Doc? 9 September

Hi everyone, Only four weeks to go until Newton! Andreas, Brian, Olga, and I met with our new release managers Olena and Alex a few days ago, and we're all ready and waiting with bated breath to get started on the release. Don't forget that you can contact any of us (or just send mail to the

[openstack-dev] [L2-Gateway] L2 Gateway Device xxx could not be found

Hi All, I try to use l2 gateway. Use one node install devstack, and another node as gateway installing ovs 2.5.0 The devstack running neutron-l2gateway-agent and neutron-server with l2gateway plugin. file /etc/neutron/l2gateway_agent.ini looks like, "node-82" is the gateway node hostname.

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

On Thu, Sep 08, 2016 at 07:37:40PM -0500, Matt Riedemann wrote: > The former IMO, a high severity bug fix trumps a translation. Note that some > projects are translated on the stable branches too, I know this is the case > for Nova. > > If it's a user-facing change, like an error message in the

Re: [openstack-dev] what permission is required to create a Keystone trust

Yes, thanks. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] venting -- OpenStack wiki reCAPTCHA

On 2016-09-09 01:10:15 + (+), Bhandaru, Malini K wrote: > Is it just me who likes to hit the save button often? > It gets tedious proving often that you are not a robot. Wiki > reCAPTCHA likes proof even if saves are spaced less than a minute > apart! > Wiki Gods, hear my plea! I

[openstack-dev] venting -- OpenStack wiki reCAPTCHA

Is it just me who likes to hit the save button often? It gets tedious proving often that you are not a robot. Wiki reCAPTCHA likes proof even if saves are spaced less than a minute apart! Wiki Gods, hear my plea! Regards, Malini

Re: [openstack-dev] [puppet] today was a bad day for CI

On Thu, Sep 8, 2016 at 8:15 PM, Emilien Macchi wrote: > I'm writing this email because it's end of day for me and I want our > community know the status of our CI. > > I spent my day trying to bring our CI back and we found new blockers > almost at every hour: >

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Sep. 9 2016

1) Roll Call 2) Unit Test Progress 3) Bifrost/Ironic Integration 4) OPNFV: Daisy4nfv CI Framework Progress 5) Bare Metal Deployment(PXE/IPMI) Status Update 6) Bare Metal Related DB Development Status Update B.R., Zhijiang

[openstack-dev] [Neutron][Nova][Infra] Linuxbridge job bump

Folks, This morning we merged the switch to Xenial for the Linuxbridge job. However, we overlooked the fact that the job configuration hardcodes eth0 as one of the variables needed by the Neutron linux bridge driver [2]. That led to failures like [3]. We have a number of changes in the works to

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On 08/09/2016 06:17, Chris Dent wrote: > On Thu, 8 Sep 2016, Flavio Percoco wrote: > >> To be honest, I think you're expressing in a negative way something >> that was thought in a positive way. The motivation to write the >> principles down is to help the community with the help from the >>

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

On 9/8/2016 7:05 PM, Ravi, Goutham wrote: Hi, I was looking for some clarity around backports of bug fixes that qualify the stable branch policy [1]. What is the policy if the fix introduces a new

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On 08/09/16 04:46, Matt Riedemann wrote: > On 9/7/2016 11:33 AM, Jim Rollenhagen wrote: >> >> I like this. As someone that has been PTL for multiple cycles, it is >> incredibly stressful trying to finish the release, start planning for the >> next one, manage summit planning, etc. I'd love to have

[openstack-dev] [puppet] today was a bad day for CI

I'm writing this email because it's end of day for me and I want our community know the status of our CI. I spent my day trying to bring our CI back and we found new blockers almost at every hour: https://review.openstack.org/367551 1) Add 2GB swap by default Add some swap when running CI jobs,

[openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

Hi, I was looking for some clarity around backports of bug fixes that qualify the stable branch policy [1]. What is the policy if the fix introduces a new translatable string or modifies an existing one? The

Re: [openstack-dev] [oslo] [telemetry] [requirements] [FFE] Oslo.db 4.13.3

2016-09-08 19:33 GMT+02:00 Mehdi Abaakouk : > > > Le 2016-09-08 16:21, Matthew Thode a écrit : >>> >>> Once it’s in, we’ll trigger another oslo.db release. > > > The release change is ready: https://review.openstack.org/#/c/367482/ > > I have tested it against Gnocchi we don't

[openstack-dev] [sahara] Newton doc review kickoff

Hi Saharans, It's time to review our documentation again, in the time-honored tradition of our people. The etherpad to track this effort is here: https://etherpad.openstack.org/p/sahara-doc-days To assign a document to yourself to review, please add your IRC handle and update the status of the

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On 07/09/16 12:04 PM, Sean Dague wrote: > On 09/07/2016 11:43 AM, Thierry Carrez wrote: >> Hi everyone, >> >> As you probably know by now, starting with the Boston event in 2017, the >> Summit will happen further away from the release day and more around the >> middle of the next development

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

> On Sep 8, 2016, at 12:49 PM, Matt Riedemann > wrote: > > On 9/8/2016 6:42 AM, Sean Dague wrote: >> On 09/08/2016 05:00 AM, Thierry Carrez wrote: >>> Sean Dague wrote: >> >>> So... the difference between your proposal and mine is: you force the >>> PTL to be the

Re: [openstack-dev] [tripleo] what's up in upgrades?

On Thu, Sep 8, 2016 at 4:18 PM, David Moreau Simard wrote: > How long does the upgrade job take ? undercloud upgrade is a matter of 10 min max. overcloud upgrade will be much more, I don't have metrics right now. matbu maybe? > > David Moreau Simard > Senior Software Engineer |

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

Excerpts from John Griffith's message of 2016-09-08 14:13:14 -0600: > On Thu, Sep 8, 2016 at 12:49 PM, Matt Riedemann > wrote: > > > On 9/8/2016 6:42 AM, Sean Dague wrote: > > > >> On 09/08/2016 05:00 AM, Thierry Carrez wrote: > >> > >>> Sean Dague wrote: > >>> > >>

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On 08/09/16 09:13 AM, Chris Dent wrote: > The truth, for me, is that I agree with most of the things in the > document. What is problematic for me is that I know a lot of people > who will not. Because of the ordering of the process and the > presumption of the document they will simply choose

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On 9/8/16 7:42 AM, Sean Dague wrote: > On 09/08/2016 05:00 AM, Thierry Carrez wrote: >> Sean Dague wrote: > >> So... the difference between your proposal and mine is: you force the >> PTL to be the release steward (rather than having a choice there), and >> introduce a delay between election

Re: [openstack-dev] [nova] Bug team meeting

Markus discussed the issue with both Timofey and myself, and we agreed that based on my involvement with the bugs team it made more sense to have me to take it over. Timofey has agreed to run the 0800 UTC EU meeting and I'll run the 1800 UTC US/APAC meeting. As Kashya pointed out, having more

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

Good comment and I have an answer inline. On 9/8/16 2:41 PM, Hongbin Lu wrote: > >> -Original Message- >> From: Thierry Carrez [mailto:thie...@openstack.org] >> Sent: September-08-16 5:00 AM >> To: openstack-dev@lists.openstack.org >> Subject: Re: [openstack-dev] [all] Timeframe for

Re: [openstack-dev] [tripleo] what's up in upgrades?

On Thu, Sep 8, 2016 at 2:27 PM, Emilien Macchi wrote: > What's up in upgrades? > > 1) Undercloud: Mitaka to Newton > > We just approved a patch in openstack-infra/tripleo-ci that test > undercloud upgrades. > I don't think we should make it vote as for now it's quite >

[openstack-dev] [magnum] Fedora Atomic image that supports kubernetes external load balancer (for stable/mitaka)

Does anyone have a pointer to a Fedora Atomic image that works with stable/mitaka Magnum, and supports the kubernetes external load balancer feature [1]? I'm trying to test the kubernetes external load balancer feature with stable/mitaka Magnum. However, when I try to bring up a load-balanced

[openstack-dev] [Congress] Stack trace returned to end user bug

All -- https://bugs.launchpad.net/congress/+bug/1620868 I stepped through the code with the pdb. I can't find anything wrong in the CongressException code. The traceback is being added by oslo_messaging/rpc/server.py in _process_incoming This call that is throwing an exception: res =

Re: [openstack-dev] [cinder] moving driver to open source

On 2016-09-08 23:41:42 +0300 (+0300), Duncan Thomas wrote: > Despite the fact I've appeared to be slightly disagreeing with John in the > IRC discussion on this subject, you've summarised my concern very well. I'm > not convinced that these support tools need to be open source, but they >

Re: [openstack-dev] [cinder] moving driver to open source

On 8 September 2016 at 20:17, John Griffith wrote: > On Thu, Sep 8, 2016 at 11:04 AM, Jeremy Stanley wrote: > > > > they should be able to simply install it and its free dependencies >> and get a working system that can communicate with

[openstack-dev] [OSSN-0073] Horizon dashboard leaks internal information through cookies

Horizon dashboard leaks internal information through cookies --- ### Summary ### When horizon is configured, its URL contains the IP address of the internal URL of keystone, as the default value for the identity service is "internalURL".[1] The cookie "login_region" will be set to the value

Re: [openstack-dev] [tripleo] what's up in upgrades?

How long does the upgrade job take ? David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Thu, Sep 8, 2016 at 2:27 PM, Emilien Macchi wrote: > What's up in upgrades? > > 1) Undercloud: Mitaka to Newton > > We just approved a

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On Thu, Sep 8, 2016 at 12:49 PM, Matt Riedemann wrote: > On 9/8/2016 6:42 AM, Sean Dague wrote: > >> On 09/08/2016 05:00 AM, Thierry Carrez wrote: >> >>> Sean Dague wrote: >>> >> >> >>> So... the difference between your proposal and mine is: you force the >>> PTL to

Re: [openstack-dev] [ironic] Future of cleaning when in maintenance mode

On 8 Sep 2016 10:12 a.m., "Dmitry Tantsur" wrote: > > On 09/07/2016 05:25 PM, Dmitry Tantsur wrote: >> >> Hi all! >> >> Today while playing with my installation I noticed that we do try to run >> cleaning for nodes in maintenance mode. This leads to a somewhat >> confusing

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

On 09/08/2016 09:04 AM, Andrew Laski wrote: > > > On Thu, Sep 8, 2016, at 07:18 AM, Sean Dague wrote: >> On 09/07/2016 07:34 PM, Andrew Laski wrote: >>> >>> >>> On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote: On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote: 3) core

Re: [openstack-dev] [poll][kolla] Name of baremetal role/group

On 9/8/2016 2:21 AM, Martin André wrote: On Wed, Sep 7, 2016 at 11:58 PM, Steven Dake (stdake) wrote: Sean, I’d recommend deploy-hosts (I assume this is the bootstrap renamed?) +1 I also like deploy-host better than the other proposed names. Can we update the poll to

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On 9/8/2016 6:42 AM, Sean Dague wrote: On 09/08/2016 05:00 AM, Thierry Carrez wrote: Sean Dague wrote: So... the difference between your proposal and mine is: you force the PTL to be the release steward (rather than having a choice there), and introduce a delay between election and start of

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

> -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: September-08-16 5:00 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all] Timeframe for future elections & > "Release stewards" > > Sean Dague wrote: > > On 09/07/2016 12:27 PM,

[openstack-dev] [Openstack] OpenStack Newton B3 for Ubuntu 16.04 LTS and Ubuntu 16.10

Hi All, The Ubuntu OpenStack team is pleased to announce the general availability of OpenStack Newton B3 milestone in Ubuntu 16.10 and for Ubuntu 16.04 LTS via the Ubuntu Cloud Archive. Ubuntu 16.04 LTS You can enable the Ubuntu Cloud Archive pocket for OpenStack Newton

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On Thu, Sep 8, 2016 at 6:13 AM, Chris Dent wrote: > > That is, it thinks of itself as an existing truth to be ratified. > Gah! YES!! Exactly this! Well said! And this attitude keeps getting echoed again and again from the current oligarchy TC! "We know what OpenStack

[openstack-dev] [tripleo] what's up in upgrades?

What's up in upgrades? 1) Undercloud: Mitaka to Newton We just approved a patch in openstack-infra/tripleo-ci that test undercloud upgrades. I don't think we should make it vote as for now it's quite experimental. Though I'm wondering if we should move it to the check pipeline as non-voting

[openstack-dev] [release] Release countdown for week R-3, 12 - 16 Sept -- Release Candidate Deadline

Focus - All teams should be wrapping up their work to prepare release candidates for the end of Newton. General Notes - The release candidate deadline for Newton releases is 15 Sept. All projects following cycle-based release models that want to include a deliverable in Newton

[openstack-dev] [OSSN-0069] Host machine exposed to tenant networks via IPv6

Host machine exposed to tenant networks via IPv6 --- ### Summary ### New interfaces created by Neutron in the default namespace, were done so without disabling IPv6 link-local addresses. This resulted in instances gaining the ability to directly access the host OS, therefore breaking guest

Re: [openstack-dev] [oslo] [telemetry] [requirements] [FFE] Oslo.db 4.13.3

Le 2016-09-08 16:21, Matthew Thode a écrit : Once it’s in, we’ll trigger another oslo.db release. The release change is ready: https://review.openstack.org/#/c/367482/ I have tested it against Gnocchi we don't have any issue anymore. Thanks all! -- Mehdi Abaakouk mail: sil...@sileht.net

Re: [openstack-dev] [cinder] moving driver to open source

On Thu, Sep 8, 2016 at 11:04 AM, Jeremy Stanley wrote: > On 2016-09-08 09:32:20 +0100 (+0100), Daniel P. Berrange wrote: > > That policy is referring to libraries (ie, python modules that we'd > > actually "import" at the python level), while the list above seems to be > >

Re: [openstack-dev] [api] [devstack] [ocata] Consistent Endpoint Discovery

Hi Michael, We discussed this at the API-WG meeting today (occurs at 16:00 UTC on Thursdays, #openstack-meeting-3). A point regarding the ‘/’ endpoint and the versions response is made in the microversions guideline

Re: [openstack-dev] [cinder] moving driver to open source

On 2016-09-08 09:32:20 +0100 (+0100), Daniel P. Berrange wrote: > That policy is referring to libraries (ie, python modules that we'd > actually "import" at the python level), while the list above seems to be > referring to external command line tools that we merely invoke from the > python code.

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On Sep 8, 2016, at 8:13 AM, Chris Dent wrote: > The writing is starting from a detailed proposal which, as txx said in > his response to me above, presents itself as a document that is "meant > to document *existing* principles that we operate under but never > documented

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, This week the working group has been discussing an interesting topic raised by Michael Krotscheck on the devel mailing list[7]. This discussion is mainly about how we can create a more consistent API version discovery mechanism across the OpenStack projects, and

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

Hi Adrian, On Thu, 2016-09-08 at 12:58 +1200, Adrian Turjak wrote: > Double api sounds a little terrifying when really there are probably so > many different ways you can already solve this using the services we > already have. > > The thing I don't get is Martin's requirement that "an instance

Re: [openstack-dev] [nova][keystone] auth for new metadata plugins

On 09/01/2016 08:48 PM, Michael Still wrote: On Thu, Sep 1, 2016 at 11:58 AM, Adam Young > wrote: On 08/31/2016 07:56 AM, Michael Still wrote: There is a quick sketch of what a service account might look like at

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On 09/08/2016 06:18 AM, Chris Dent wrote: > > There's a governance proposal in progress at > https://review.openstack.org/#/c/357260/ that I think is worth a > visit by anyone interested in the definition and evolution of > OpenStack's identity and the processes and guidelines used in OpenStack.

Re: [openstack-dev] [neutron] Skip-only tests

On Thu, 2016-09-08 at 10:36 +0200, Andreas Jaeger wrote: >  > Toni, sorry, I wasn't clear. I'm not advocating for this, I wanted to > bring Joe into this discussion to see whether the solution that John > suggested will help them as well - I wanted to broaden the scope of > this since it's not

Re: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

+1 On 8 September 2016 at 06:35, Mauricio Lima wrote: > +1 > > 2016-09-08 5:52 GMT-03:00 Dave Walker : >> >> +1 >> >> Great stuff Christian >> >> On 8 September 2016 at 03:59, Steven Dake (stdake) >> wrote: >>> >>> Kolla core

Re: [openstack-dev] [oslo] [telemetry] [requirements] [FFE] Oslo.db 4.13.2

On 09/08/2016 03:59 AM, Ihar Hrachyshka wrote: > I backported the fix to stable/newton: > https://review.openstack.org/#/c/367221/ > > Once it’s in, we’ll trigger another oslo.db release. > > As for the blocking patch for requirements: > https://review.openstack.org/#/c/365565/, I disagree that

Re: [openstack-dev] [cinder] moving driver to open source

On Thu, Sep 8, 2016 at 2:32 AM, Daniel P. Berrange wrote: > On Thu, Sep 08, 2016 at 10:24:09AM +0200, Thierry Carrez wrote: > > Avishay Traeger wrote: > > > There are a number of drivers that require closed-source tools to > > > communicate with the storage. 3 others that

Re: [openstack-dev] [cinder] moving driver to open source

On 09/06/2016 11:27 AM, Alon Marx wrote: I want to share our plans to open the IBM Storage driver source code. Historically we started our way in cinder way back (in Essex if I'm not mistaken) with just a small piece of code in the community while keeping most of the driver code closed. Since

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

No topic/discussion in our agenda, we cancelled the meeting, see you next week! 2016-09-05 15:39 GMT-03:00 Iury Gregory : > Hi Puppeteers, > > If you have any topic to add for this week, please use the etherpad: >

Re: [openstack-dev] [requirements][FFE] Request to allow os-vif 1.2.1 in upper-constraints for newton

Hi Matt, > This is the FFE to get this change in for newton: > > https://review.openstack.org/#/c/365165/ > > The os-vif 1.2.1 release was a bug fix patch release to get a high priority > bug [1] in for newton that is impacting the neutron linuxbridge job in the > gate [2]. > > So we already have

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

On Wed, Sep 7, 2016, at 08:41 PM, Fox, Kevin M wrote: > Interesting. It kind of sounds like your proposing a sort of... openstack > standard library api api? (yes, double apis) Where you can build up an > api using other api calls and users can rely on those standard > overarching api's to be

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On Thu, 8 Sep 2016, Flavio Percoco wrote: To be honest, I think you're expressing in a negative way something that was thought in a positive way. The motivation to write the principles down is to help the community with the help from the community. No one is pushing anyone's beliefs on anyone.

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

On Thu, Sep 8, 2016, at 07:18 AM, Sean Dague wrote: > On 09/07/2016 07:34 PM, Andrew Laski wrote: > > > > > > On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote: > >> On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote: > >> 3) core functionality should IMO require as few API calls as

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

On Thu, Sep 8, 2016, at 05:48 AM, Kevin Benton wrote: > Why don't you just pre-create the port and associate the floating IP > before booting the instance? Right. It's not difficult to do at all but there's a strong desire to have this be encompassed in a single API call. I think that's a

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On 07/09/16 12:02 -0500, Monty Taylor wrote: On 09/07/2016 11:43 AM, Davanum Srinivas wrote: On Wed, Sep 7, 2016 at 12:35 PM, Ian Cordasco wrote: -Original Message- From: Monty Taylor Reply: OpenStack Development Mailing List (not for

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On 07/09/16 17:43 +0200, Thierry Carrez wrote: Hi everyone, As you probably know by now, starting with the Boston event in 2017, the Summit will happen further away from the release day and more around the middle of the next development cycle. You can find more info on the rationale for that at

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

On 08/09/16 12:18 +0100, Chris Dent wrote: There's a governance proposal in progress at https://review.openstack.org/#/c/357260/ that I think is worth a visit by anyone interested in the definition and evolution of OpenStack's identity and the processes and guidelines used in OpenStack. I'm

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

Chris Dent wrote: > There's a governance proposal in progress at > https://review.openstack.org/#/c/357260/ that I think is worth a > visit by anyone interested in the definition and evolution of > OpenStack's identity and the processes and guidelines used in OpenStack. > > I'm assuming that not

Re: [openstack-dev] [neutron] not passing objects into registered extensions

Ihar Hrachyshka wrote: Hi, we have this latent bug where we pass objects for subnetpools into extension functions. (That was a mistake made when switching to using objects in base db plugin for the resource.) Now, we want to revert to passing db models as we did

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

On 09/08/2016 05:00 AM, Thierry Carrez wrote: > Sean Dague wrote: > So... the difference between your proposal and mine is: you force the > PTL to be the release steward (rather than having a choice there), and > introduce a delay between election and start of authority for the PTL. > > I don't

Re: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

+1 2016-09-08 5:52 GMT-03:00 Dave Walker : > +1 > > Great stuff Christian > > On 8 September 2016 at 03:59, Steven Dake (stdake) > wrote: > >> Kolla core reviewer team, >> >> >> >> It is my pleasure to nominate Christian Berendt for the Kolla core team. >> >>

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

On 09/07/2016 07:34 PM, Andrew Laski wrote: > > > On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote: >> On Thu, 2016-09-08 at 09:34 +1200, Adrian Turjak wrote: >> 3) core functionality should IMO require as few API calls as possible, >> to as few components as possible, while keeping REST

[openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

There's a governance proposal in progress at https://review.openstack.org/#/c/357260/ that I think is worth a visit by anyone interested in the definition and evolution of OpenStack's identity and the processes and guidelines used in OpenStack. I'm assuming that not everyone regularly cruises

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

+1 2016-09-08 13:06 GMT+03:00 Aleksandr Didenko : > +1 > > On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko > wrote: > >> +1 >> >> >> >> >> __ >> OpenStack Development

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

+1 On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko wrote: > +1 > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe:

Re: [openstack-dev] [Horizon][OSC][Nova][Neutron] Launch instance with Floating IP

Why don't you just pre-create the port and associate the floating IP before booting the instance? On Wed, Sep 7, 2016 at 5:58 PM, Adrian Turjak wrote: > Double api sounds a little terrifying when really there are probably so > many different ways you can already solve

Re: [openstack-dev] [nova] Next steps for resource providers work

On Wed, 7 Sep 2016, Sean Dague wrote: As a follow up here, I actually got to the bottom of why the old tests didn't work. This is great, thank you. I'm not quite clear on what the state of things is today. As I left for the night last night there was some debate on changing the

[openstack-dev] [tricircle][all] vote result for API-gateway project name: Trio2o

Hello, And now the vote results for api-gateway are: Trio2o, 8 votes Triangel, 3 votes Trifennal, 2 votes Consider most of our active contributors of Tricircle have already voted for the naming, so Trio2o will be the name for the gateway project. After the name is voted, the preparation for

[openstack-dev] [QA] [Inspector] [Tempest] Problem with paramiko on grenade

Hi folks! We've ran into the problem with paramiko, similar to[1] in Inspector. Our grenade job fails on TestNetworkBasicOps.test_network_basic_ops with [2] or [3] in 90% cases. Looks like reverting fix [4] solves the problem, at least grenade passed few times with reverting patch. But it will

[openstack-dev] [NOVA] why it take long time between the unplug_vif and update port host binding while doing live migrate VM

Hi All: As [1], [2] shows, at the last stage in VM migration, it will call unplug_vifs(), and then migrate_instance_finish(), in which update_port will be called immediately. I think the two steps should be executed without no disturb., but in my test, there is at least 3 seconds between

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

+1 Regards, Bulat Gaifullin Mirantis Inc. > On 08 Sep 2016, at 12:05, Georgy Kibardin wrote: > > +1 > > On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky > wrote: > Hey Fuelers, > > I'd like to nominate Ilya for

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

+1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

+1 On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky wrote: > Hey Fuelers, > > I'd like to nominate Ilya for joining fuel-plugins-core group. He's a > top contributor by both reviews [1] and commits [2] over the past > release cycle. Fuel cores, please share your votes. > > -

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

Sean Dague wrote: > On 09/07/2016 12:27 PM, Thierry Carrez wrote: >> Barrett, Carol L wrote: >>> From: Sean Dague [mailto:s...@dague.net] I think another option would be to run the PTL election early, but just don't have the turn over happen until the master release opens up. The

Re: [openstack-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core

+1 2016-09-08 11:12 GMT+03:00 Vladimir Kozhukalov : > +1 > > Vladimir Kozhukalov > > On Thu, Sep 8, 2016 at 1:55 AM, Maksim Malchuk > wrote: > >> Hello, >> >> I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due to >> his

Re: [openstack-dev] [oslo] [telemetry] [requirements] [FFE] Oslo.db 4.13.2

I backported the fix to stable/newton: https://review.openstack.org/#/c/367221/ Once it’s in, we’ll trigger another oslo.db release. As for the blocking patch for requirements: https://review.openstack.org/#/c/365565/, I disagree that we should block oslo.db 4.13.0, because atm pymysql

[openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

Hey Fuelers, I'd like to nominate Ilya for joining fuel-plugins-core group. He's a top contributor by both reviews [1] and commits [2] over the past release cycle. Fuel cores, please share your votes. - Igor [1] http://stackalytics.com/?module=fuel-plugins=newton=marks [2]

Re: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

+1 Great stuff Christian On 8 September 2016 at 03:59, Steven Dake (stdake) wrote: > Kolla core reviewer team, > > > > It is my pleasure to nominate Christian Berendt for the Kolla core team. > > > > Christian’s output over the last cycle has been fantastic – cracking the >

Re: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

+1 On 08/09/16 03:59, Steven Dake (stdake) wrote: Kolla core reviewer team, It is my pleasure to nominate Christian Berendt for the Kolla core team. Christian’s output over the last cycle has been fantastic – cracking the top 10 reviewer list for the full cycle. His 30 day stats [1]

Re: [openstack-dev] [neutron] Skip-only tests

On 2016-09-08 10:23, Toni Freger wrote: > On Thu, Sep 8, 2016 at 10:52 AM, Andreas Jaeger wrote: >> >> This reminds me of this review for a nova-tempest-staging repository: >> https://review.openstack.org/366091 >> >> Joe seems to face similar challenges that you articulate, John,

Re: [openstack-dev] [cinder] moving driver to open source

On Thu, Sep 08, 2016 at 10:24:09AM +0200, Thierry Carrez wrote: > Avishay Traeger wrote: > > There are a number of drivers that require closed-source tools to > > communicate with the storage. 3 others that I've come across recently: > > > > * EMC VNX: requires Navisphere CLI v7.32 or higher >

Re: [openstack-dev] [neutron] Skip-only tests

On Thu, Sep 8, 2016 at 10:52 AM, Andreas Jaeger wrote: > > This reminds me of this review for a nova-tempest-staging repository: > https://review.openstack.org/366091 > > Joe seems to face similar challenges that you articulate, John, > > Andreas > Hi Andreas, I understand other

Re: [openstack-dev] [cinder] moving driver to open source

Avishay Traeger wrote: > There are a number of drivers that require closed-source tools to > communicate with the storage. 3 others that I've come across recently: > > * EMC VNX: requires Navisphere CLI v7.32 or higher > * Hitachi storage volume driver: requires RAID Manager Ver 01-32-03/01

Re: [openstack-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core

+1 Vladimir Kozhukalov On Thu, Sep 8, 2016 at 1:55 AM, Maksim Malchuk wrote: > Hello, > > I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due to > his significant contribution to the project [1] and [2]. He is the second > reviewer and for the last

Re: [openstack-dev] [ironic] Future of cleaning when in maintenance mode

On 09/07/2016 05:25 PM, Dmitry Tantsur wrote: Hi all! Today while playing with my installation I noticed that we do try to run cleaning for nodes in maintenance mode. This leads to a somewhat confusing result, because we no-op heartbeats for such nodes. So cleaning gets stuck in "clean wait"

Re: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

+1 On Thu, Sep 8, 2016 at 3:23 PM, Martin André wrote: > +1, nice work Christian. > > Martin > > On Thu, Sep 8, 2016 at 4:59 AM, Steven Dake (stdake) > wrote: > > Kolla core reviewer team, > > > > > > > > It is my pleasure to nominate Christian Berendt for

Re: [openstack-dev] [cinder] moving driver to open source

There are a number of drivers that require closed-source tools to communicate with the storage. 3 others that I've come across recently: - EMC VNX: requires Navisphere CLI v7.32 or higher - Hitachi storage volume driver: requires RAID Manager Ver 01-32-03/01 or later for VSP

Re: [openstack-dev] [neutron] Skip-only tests

On 2016-09-08 09:38, John Schwarz wrote: > Hi all, > > The Neutron community has recently started contributing Tempest > scenario tests in the Neutron tree and I'd like to discuss a general > issue we're hitting. Mainly, we're talking about required hardware for > some features and/or VM images

[openstack-dev] [neutron] Skip-only tests

Hi all, The Neutron community has recently started contributing Tempest scenario tests in the Neutron tree and I'd like to discuss a general issue we're hitting. Mainly, we're talking about required hardware for some features and/or VM images that support more features, which makes it hard (or

Re: [openstack-dev] [poll][kolla] Name of baremetal role/group

On Wed, Sep 7, 2016 at 11:58 PM, Steven Dake (stdake) wrote: > Sean, > > > > I’d recommend deploy-hosts (I assume this is the bootstrap renamed?) +1 I also like deploy-host better than the other proposed names. Can we update the poll to include this option? > I’d also add a

  1   2   >