[openstack-dev] [infra]help on the description update in github repository

Hello, The short project description of Tricircle is: "Tricircle is to provide networking automation across Neutron." in http://git.openstack.org/cgit/openstack/tricircle/ the official repository. But the description in the mirrored github

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Le 2016-12-01 01:25, Tony Breeds a écrit : So right now I think the answer is still no we can't uncap it. To the best of my knowledge monasca still suffers a substatial performance decrease and the switch from sync to async producers isn't desired for them. Joe wrote this all up in:

Re: [openstack-dev] "tempest.lib.common.ssh AuthenticationException: Authentication failed." error when run“tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_ser

Hi, gamnn, Thanks for you advice. As far, the following cases are failed due to the SSH issue in our test. 1.{0} tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_server_name [369.207581s] ... FAILED 2.{0}

[openstack-dev] [Horizon] [Keystone] cross-project meeting Thursday 1st December 2000UTC

Hi folks, The next Keystone/Horizon cross-project meeting is this Thursday, 1st December at 2000UTC in #openstack-meeting-cp The agenda is https://etherpad.openstack.org/p/ocata-keystone-horizon Please update that document if you're working on one of the items. Richard

[openstack-dev] [QA] Meeting Thursday Dec 1st at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, Dec 1st at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_December_1st_2016_.280900_UTC.29

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

So, voting end has arrived. We voted yay and yay it is. Now every team will vote for their own cores:) Let me know if you have any questions about that please. Regards, Michal On 30 November 2016 at 16:26, Ken Wronkiewicz (kewronki) wrote: > +1 :) > > On 11/16/16, 10:23 AM,

[openstack-dev] [kolla] propose to remove COPY_ONCE feature

Kolla has a config_strategy option during deployment. it supports COPY_ONCE and COPY_ALWAYS. which means whether copy the configuration files defined in config.json again during starting containers. COPY_ALWAYS: copy all configuration files always during every start ( default value

Re: [openstack-dev] [nimble] Weekly meeting canceled this week (1/12/2016)

Wish u a Happy Bug Smash BR, YunTongJin 2016-11-30 22:09 GMT+08:00 Zhenguo Niu : > Hello team, > > I'll cancel tomorrow's IRC meeting due to Bug Smash activities. > > See you all on next meeting! > > -- > Best Regards, > Zhenguo Niu > >

[openstack-dev] [kolla] migrate from heka to fluentd

Heka is deprecated, and its alternative has been talked many times. Finally, Kolla team reach an agreement on this. kolla-ansible implementation will migrate from Heka to Fluentd. ( kolla-kubernetes is using Fluentd ) Fluentd will be a good choice, which is maturity enough and part of CNCF[1].

Re: [openstack-dev] [kolla] Kolla-ansible is available

On Thu, Dec 1, 2016 at 4:39 AM, Fox, Kevin M wrote: > So, longer term, I'd really like to see a set of smaller pieces of > gate'ness that co-check each other. > ​yes this is neccessary.​ > > one gate that periodically checks that kolla:trunk builds (nightly?) sans >

Re: [openstack-dev] [OpenStack-docs] [osa] [docs] OpenStack-Ansible deploy guide live!

On 01/12/16 01:03, Alexandra Settle wrote: > Hi everyone, > > > > I am really pleased to announce that the OpenStack-Ansible Deployment Guide > is now available on the docs.o.o website! You can view it in all its glory > here: http://docs.openstack.org/project-deploy-guide/newton/ > > >

[openstack-dev] [nova] Third party CIs running nova-network need to be disabled on master branch changes

https://review.openstack.org/#/c/403855/ is working it's way through the gate and should merge soon. Once that lands, CI jobs using nova-network without cells v1 are going to fail because nova-network will fail to start. We've handled the upstream CI jobs for this transition on the master

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Wed, Nov 30, 2016 at 08:13:44PM +0100, Mehdi Abaakouk wrote: > > > Le 2016-11-30 19:11, Nadya Shakhat a écrit : > > Hi all, > > > > This one [1] is used very intensively actually :) It is not merged > > because > > we cannot just upgrade python-kafka version because of Monasca. We had > >

Re: [openstack-dev] [oslo] Should we drop kafka driver ?

On 11/30/16, 4:45 PM, "Joshua Harlow" wrote: >Mehdi Abaakouk wrote: >> Hi, >> >> I think my subject is clear :) , but I will add some facts that can help >> to the decision: >> * It uses only deprecated python-kafka API [1] [2] >> * It's not python3 compatible [3] >> * We

[openstack-dev] [Zun] Propose a change of Zun core membership

Hi Zun cores, I am going to propose the following change of the Zun core reviewers team: + Pradeep Kumar Singh (pradeep-singh-u) - Vivek Jain (vivek-jain-openstack) Pradeep was proven to be a significant contributor to Zun. He ranked first at the number of commits, and his patches were

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 30 November 2016 at 12:16, Steve Martinelli wrote: > This happened to us for keystone-specs [1]. I settled on removing the > reference to the README.rst from the doc folder. You can do the same by > removing [2]. > > [1] https://review.openstack.org/#/c/402878/ > [2]

Re: [openstack-dev] [kolla] Pruning Kolla-Kubernetes core reviewers

++ sdake, inc0 On Wed, Nov 30, 2016 at 5:49 PM, Steven Dake (stdake) wrote: > Hello folks, > > > > Michal (inc0) is the PTL of Kolla. He has asked me to send this message > since it was my agreement with the community in the Austin Design Summit > when I served as Kolla PTL

[openstack-dev] [kolla] Pruning Kolla-Kubernetes core reviewers

Hello folks, Michal (inc0) is the PTL of Kolla. He has asked me to send this message since it was my agreement with the community in the Austin Design Summit when I served as Kolla PTL that people that participate in the implementation of the kolla-kubernetes deliverable at the start of the

Re: [openstack-dev] [neutron][networking-vpp] RPM packaging and dependencies

Hi Tim, The spec file is currently hosted here: https://git.opnfv.org/apex/tree/build/rpm_specs/networking-vpp.spec And yes, I'm also looking into packaging python-etcd as well, this (as well as all the other dependencies) will need to be packaged if we want to push networking-vpp into RDO.

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

+1 :) On 11/16/16, 10:23 AM, "Michał Jastrzębski" wrote: Hello, In light of recent events (kolla-kubernetes becoming thriving project, kolla-ansible being split) I feel we need to change of core reviewer election process. Currently Kolla was

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

On 29 November 2016 at 16:21, Michał Jastrzębski wrote: > Hello team! > > I'd like to propose to add zhubingbing to kolla (and kolla-ansible) > core teams. He did great job reviewing code during last couple of > months. > > Consider this proposal +1 from me, voting will be open

Re: [openstack-dev] [Congress] Magnum_driver

Hi Ruben, What you're doing is correct. The downside is that it creates a new commit for every change you make, and all of those commits show up on gerrit. In OpenStack (and other projects I've seen that use Gerrit for code reviews) you squash those commits into 1 change so that it's easier for

[openstack-dev] [tripleo] Requesting files from the overcloud from the undercloud

Hey folks, So I'm in the process of evaluating options for implementing the capture-environment-status-and-logs[0] blueprint. At the moment my current plan is to implement a mistral workflow to execute the sosreport to bundle the status and logs up on the requested nodes. I'm leveraging a

Re: [openstack-dev] [kolla] Kolla-ansible is available

So, longer term, I'd really like to see a set of smaller pieces of gate'ness that co-check each other. one gate that periodically checks that kolla:trunk builds (nightly?) sans modification. As the containers themselves depend on a lot of packages/repositories outside of kolla's control and

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

This happened to us for keystone-specs [1]. I settled on removing the reference to the README.rst from the doc folder. You can do the same by removing [2]. [1] https://review.openstack.org/#/c/402878/ [2] https://github.com/openstack/neutron-lib/blob/master/doc/source/readme.rst On Wed, Nov 30,

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 30 November 2016 at 08:53, Michael Johnson wrote: > Hi Flavio, > > These tags don't seem to be rendering/laying out well for octavia: > https://github.com/openstack/octavia/blob/master/README.rst > > Any pointers to get this corrected or is this part of the backend >

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 11/30/2016 06:54 PM, Jeremy Stanley wrote: > On 2016-11-30 09:12:18 -0600 (-0600), Anne Gentle wrote: >> On Tue, Nov 29, 2016 at 2:53 PM, Jeremy Stanley wrote: > [...] >>> Perhaps they wanted to publish documentation to the >>> docs.openstack.org site? That's traditionally

Re: [openstack-dev] [oslo] Can we uncap python-kafka ?

Le 2016-11-30 19:11, Nadya Shakhat a écrit : Hi all, This one [1] is used very intensively actually :) It is not merged because we cannot just upgrade python-kafka version because of Monasca. We had some talks in their channel, but no results still. I suggest the following: 1. On our side

Re: [openstack-dev] [osa] [docs] OpenStack-Ansible deploy guide live!

On Wed, Nov 30, 2016 at 09:24:19AM -0600, Major Hayden wrote: :On 11/30/2016 09:03 AM, Alexandra Settle wrote: :> I am really pleased to announce that the OpenStack-Ansible Deployment Guide is now available on the docs.o.o website! You can view it in all its glory here:

Re: [openstack-dev] [ptl][release] ocata release management communication

[Resending without the PTLs in CC because it got my mail stuck in the spam filters] I'm struggling to find good info on when the adjusted PTL nomination cycle starts. I've checked here: https://releases.openstack.org/ocata/schedule. html#pike-ptls-self-nomination but it looks like the

Re: [openstack-dev] [Openstack-operators] Destructive / HA / fail-over scenarios

Adam, So Rally actually field the gap specified in that video. Now there are so called "Hooks" that allows you to trigger other tools/code during the load (after some amount of time or on specific iteration) Basically reliability testing & load testing during upgrades can be implemented as a

Re: [openstack-dev] [oslo] Should we drop kafka driver ?

Hi all, This one [1] is used very intensively actually :) It is not merged because we cannot just upgrade python-kafka version because of Monasca. We had some talks in their channel, but no results still. I suggest the following: 1. On our side we will update this change 2. I will ping Monasca

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 2016-11-30 09:12:18 -0600 (-0600), Anne Gentle wrote: > On Tue, Nov 29, 2016 at 2:53 PM, Jeremy Stanley wrote: [...] > > Perhaps they wanted to publish documentation to the > > docs.openstack.org site? That's traditionally only been allowed by > > the Docs team for official

Re: [openstack-dev] [neutron] broken linuxbridge gate

Hey all, Sorry for screwing up the gate - thankfully with the linuxbridge job being in the check queue for DevStack we'll prevent me from making any more oopsies. -- Sean M. Collins __ OpenStack Development Mailing List

Re: [openstack-dev] [monasca][oslo] (Re: [oslo] Should we drop kafka driver ?)

On Wed, Nov 30, 2016 at 05:44:25PM +0100, Mehdi Abaakouk wrote: Also, capping libraries is always a bad idea, this is one more example of why. The lib was capped due to an python-kafka upstream bugs and not API breakage. Something like != 1.0.0 would be sufficient. I have proposed to uncap

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Hi Flavio, These tags don't seem to be rendering/laying out well for octavia: https://github.com/openstack/octavia/blob/master/README.rst Any pointers to get this corrected or is this part of the backend rendering work you mentioned in the keystone message above? Michael On Wed, Nov 30, 2016

[openstack-dev] cancelled Re: [ironic] Ironic-qa meeting canceled this week (Nov 23rd)

Hi, In Monday's ironic meeting [1], we decided to cancel the QA meetings. --ruby [1] from 17:49:21, http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-11-28-17.00.log.html From: Jim Rollenhagen Reply-To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 11/30/2016 10:39 AM, Steve Martinelli wrote: Refresh (not from cache)? Ugh, yeah that was it. Sorry for the noise. On Wed, Nov 30, 2016 at 11:23 AM, Ben Nemec > wrote: On 11/30/2016 10:19 AM, Jason Rist wrote: On

Re: [openstack-dev] [oslo] Should we drop kafka driver ?

Mehdi Abaakouk wrote: Hi, I think my subject is clear :) , but I will add some facts that can help to the decision: * It uses only deprecated python-kafka API [1] [2] * It's not python3 compatible [3] * We still don't have kafka testing in gate So, one year after the driver introduction, this

Re: [openstack-dev] [oslo] Should we drop kafka driver ?

Le 2016-11-30 17:45, Joshua Harlow a écrit : IMHO, not just yet, dims and I have been trying to use this driver recently (for notifications only in my case) and I am more than willing to try to get the changes needed to get this into a healthy state (from my understanding dims and friends have

Re: [openstack-dev] [monasca][oslo] (Re: [oslo] Should we drop kafka driver ?)

Le 2016-11-30 16:56, Davanum Srinivas a écrit : Problem is with Monasca team having concerns with later python-kafka versions https://bugs.launchpad.net/oslo.messaging/+bug/1639264 Good point, the bug is 1 month old, but the issue is known since 7 months. At this point I think if we want

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Refresh (not from cache)? On Wed, Nov 30, 2016 at 11:23 AM, Ben Nemec wrote: > > > On 11/30/2016 10:19 AM, Jason Rist wrote: > >> On 11/30/2016 11:18 AM, Ben Nemec wrote: >> >>> >>> >>> On 11/30/2016 03:34 AM, Flavio Percoco wrote: >>> On 25/11/16 13:46 +,

Re: [openstack-dev] [designate] Meeting this week

Sounds good to me. Enjoy your meeting :) Tim Simmons From: Hayes, Graham Sent: Wednesday, November 30, 2016 10:25 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [designate] Meeting this

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 11/30/2016 11:18 AM, Ben Nemec wrote: > > > On 11/30/2016 03:34 AM, Flavio Percoco wrote: > > On 25/11/16 13:46 +, Amrith Kumar wrote: > >> Flavio, > >> > >> I see a number of patches[1] which have been landed on this project > >> but I find > >> that at least the ones that were landed for

[openstack-dev] [designate] Meeting this week

Hi All, There is an unexpected internal meeting today that conflicts with the IRC meeting. As a result, I will not be available to chair, and I think that the other HPE team members will also be unavailable. I suggest that we postpone for this week? Thanks, Graham

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 11/30/2016 10:19 AM, Jason Rist wrote: On 11/30/2016 11:18 AM, Ben Nemec wrote: On 11/30/2016 03:34 AM, Flavio Percoco wrote: On 25/11/16 13:46 +, Amrith Kumar wrote: Flavio, I see a number of patches[1] which have been landed on this project but I find that at least the ones that

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 11/30/2016 03:34 AM, Flavio Percoco wrote: On 25/11/16 13:46 +, Amrith Kumar wrote: Flavio, I see a number of patches[1] which have been landed on this project but I find that at least the ones that were landed for Trove, and a random sampling of the others all to be different from

[openstack-dev] [neutron][networking-vpp] RPM packaging and dependencies

Hi Feng, In the review reverting the db compatibility patch [1] you mentioned that we could change the RPM spec for packaging networking-vpp and that the spec resides in another repo. Could you point to that repo? I was assuming you (or someone) had created it in RDO but I don’t see a

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

+1 > On 16 Nov 2016, at 19:23, Michał Jastrzębski wrote: > > Hello, > > In light of recent events (kolla-kubernetes becoming thriving project, > kolla-ansible being split) I feel we need to change of core reviewer > election process. > > Currently Kolla was single core team.

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

On 27 November 2016 at 20:50, Takashi Yamamoto wrote: > On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: > > Hi > > > > As of today, the project neutron-vpnaas is no longer part of the neutron > > governance. This was a decision reached after the

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

> On 29 Nov 2016, at 17:21, Michał Jastrzębski wrote: > > I'd like to propose to add zhubingbing to kolla (and kolla-ansible) > core teams. He did great job reviewing code during last couple of > months. +1 -- Christian Berendt Chief Executive Officer (CEO) Mail:

[openstack-dev] [neutron][octavia] Neutron LBaaS governance change and Octavia to the big tent

Hi folks, A few hours ago a governance change [1] has been approved by TC members. This means that from now on, the efforts for Load Balancing as a Service efforts rest officially in the hands of the Octavia PTL and the Octavia core team. I will work with the help of the respective core teams to

[openstack-dev] [monasca][oslo] (Re: [oslo] Should we drop kafka driver ?)

Mehdi, Problem is with Monasca team having concerns with later python-kafka versions https://bugs.launchpad.net/oslo.messaging/+bug/1639264 Adding them to the subject line -- Dims On Wed, Nov 30, 2016 at 10:28 AM, Mehdi Abaakouk wrote: > Hi, > > I think my subject is clear

[openstack-dev] [oslo] Should we drop kafka driver ?

Hi, I think my subject is clear :) , but I will add some facts that can help to the decision: * It uses only deprecated python-kafka API [1] [2] * It's not python3 compatible [3] * We still don't have kafka testing in gate So, one year after the driver introduction, this one is still in

Re: [openstack-dev] [osa] [docs] OpenStack-Ansible deploy guide live!

On 11/30/2016 09:03 AM, Alexandra Settle wrote: > I am really pleased to announce that the OpenStack-Ansible Deployment Guide > is now available on the docs.o.o website! You can view it in all its glory > here: http://docs.openstack.org/project-deploy-guide/newton/ > > This now paves the way

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

To add to that, I am currently in the process of adding the driver docs policy guidelines to the Contributor Guide: https://review.openstack.org/#/c/404785/ From: Anne Gentle Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On Tue, Nov 29, 2016 at 2:53 PM, Jeremy Stanley wrote: > On 2016-11-29 20:19:13 + (+), gordon chung wrote: > [...] > > i don't recall why they were moved to be officially under the Telemetry > > umbrella[3] but i remember they weren't allowed to do something if they >

[openstack-dev] [osa] [docs] OpenStack-Ansible deploy guide live!

Hi everyone, I am really pleased to announce that the OpenStack-Ansible Deployment Guide is now available on the docs.o.o website! You can view it in all its glory here: http://docs.openstack.org/project-deploy-guide/newton/ This now paves the way for many other deployment projects to

[openstack-dev] [nimble] Weekly meeting canceled this week (1/12/2016)

Hello team, I'll cancel tomorrow's IRC meeting due to Bug Smash activities. See you all on next meeting! -- Best Regards, Zhenguo Niu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Openstack-operators] Destructive / HA / fail-over scenarios

On Mon, 2016-11-28 at 15:51 +0300, Timur Nurlygayanov wrote: > Hi OpenStack developers and operators, > > we are going to create the test suite for destructive testing of > OpenStack clouds. We want to hear your feedback and ideas > about possible destructive and failover scenarios which we need

Re: [openstack-dev] [tripleo] [ironic] Need to update kernel parameters on local boot

On Tue, Nov 29, 2016 at 10:48 AM, Yolanda Robla Mota wrote: > The problem we have with that is that for changes to take effect we will > need a reboot after it. > This is suboptimal for production environments, where there are large > amount of nodes and with an slow

Re: [openstack-dev] [Congress] Magnum_driver

Hi Tim, what should I do to squash all the commits into a single one? To add the code to review I made: git add git commit git review Isn't it correct? Ruben - Messaggio originale - Da: "Tim Hinrichs" A: "Ruben" Cc:

Re: [openstack-dev] [heat][stable] Fwd: [Openstack-stable-maint] Stable check of openstack/heat failed

On Wed, Nov 30, 2016 at 5:53 PM, Ihar Hrachyshka wrote: > Anyone working on heat stable periodic doc job fix? Any patches to review? > > I see it failing for quite some time for L and M. > > https://review.openstack.org/#/c/404725/ should fix periodic-heat-docs-mitaka. We

[openstack-dev] [heat][stable] Fwd: [Openstack-stable-maint] Stable check of openstack/heat failed

Anyone working on heat stable periodic doc job fix? Any patches to review? I see it failing for quite some time for L and M. > Begin forwarded message: > > From: "A mailing list for the OpenStack Stable Branch test reports." > > Subject:

Re: [openstack-dev] [charms] Barbican + Identity Standalone - AWS

Hey James! We were looking at adding Keystone as a user management backend for Kubernetes. This is a great step forward in making that possible, I noticed the barbican charm in the AWS deploy was "local", are there any major changes to the charm from ~openstack-charmers needed for it to run in

[openstack-dev] ovs-bridge mutiple IPs

Just a quick question: is there any method to assign my ovs-bridge a 2nd IP address including used for OpenStack on network node. The physical interface is added inside the bridge, but I'm unable to assign my bridge an addition IP for a different service , or just like eth0 and eth0:1 Regards,

Re: [openstack-dev] Question about OpenStack release model

hu.zhiji...@zte.com.cn wrote: > I'm running a project which is a OpenStack related project currently. > > My questions is:　Is being part of Big Tent a requirement before a project > can > follow one of those 3 release models(cycle-with-milestones, > cycle-with-intermediary, and cycle-trailing)

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

>I'll let someone from the Neutron team fill in the details behind their >decision, because I don't want to misrepresent them. I can shed a bit of light on this since I'm a core and had been working for a driver vendor at the time of the split. There were a few areas of contention: * Releases

[openstack-dev] [glance] Missing records in "image_locations" table

Hi everyone, A while ago I reported some issues with Glance where image files went missing from the file system. Since then we implemented a monitoring script that regularly verifies the state of every active image in the Glance database, checking that: 1) it has a corresponding record in the

Re: [openstack-dev] [neutron] broken linuxbridge gate

Thanks for catching this. I have taken the liberty to approve the reverts and hopefully this will get the gate back to normal. Thanks Gary From: "Armando M." Reply-To: OpenStack List Date: Wednesday, November 30, 2016 at 1:46 AM To:

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 25/11/16 13:46 +, Amrith Kumar wrote: Flavio, I see a number of patches[1] which have been landed on this project but I find that at least the ones that were landed for Trove, and a random sampling of the others all to be different from what you proposed below[2] in one important aspect.

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

+1 great job 2016-11-30 2:48 GMT+00:00 Steven Dake (stdake) : > +1 from me ☺ > > -Original Message- > From: Michał Jastrzębski > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date:

[openstack-dev] Question about OpenStack release model

Hi All, I'm running a project which is a OpenStack related project currently. My questions is:　Is being part of Big Tent a requirement before a project can follow one of those 3 release models(cycle-with-milestones, cycle-with-intermediary, and cycle-trailing) as described in

Re: [openstack-dev] [gnocchi] influxdb driver gate error

> On 30 Nov. 2016, at 6:23 pm, Mehdi Abaakouk wrote: > > > > Le 2016-11-30 08:06, Sam Morrison a écrit : >> 2016-11-30 06:50:14.969302 | + pifpaf -e GNOCCHI_STORAGE run influxdb >> -- pifpaf -e GNOCCHI_INDEXER run mysql -- ./tools/pretty_tox.sh >> 2016-11-30 06:50:17.399380

Re: [openstack-dev] "tempest.lib.common.ssh AuthenticationException: Authentication failed." error when run“tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_ser

Hi, This is ssh timeout issue happened. I saw many other bugs also related to ssh timeout. There are many other tests doing ssh, all those are passing? And does this tests fail consistently ? (As this tests is not failing on gate) I will suggest to log this as qa bug and provide more log