Re: [openstack-dev] 答复: [heat] glance v2 support?

On Tue, Jan 10, 2017 at 10:41 PM, Clint Byrum wrote: > Excerpts from Zane Bitter's message of 2017-01-10 15:28:04 -0500: >> location is a required property: >> >> http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Glance::Image >> >> The resource type

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi, Ifat If I understand it correctly, your concerns are mainly on same alarm from different monitor, but not "suspect" status as discussed in another thread. On Tue, Jan 10, 2017 at 10:21 PM Afek, Ifat (Nokia - IL) < ifat.a...@nokia.com> wrote: Hi Yinliyin, At first I thought that changing

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

The library final release is really soon, and we are still blocked on this topic. If this is not solved, we will release one more time an unusable driver in oslo.messging. I want to remember that people current uses the kafka driver in production with 'downstream patches' ready since 1 years to

Re: [openstack-dev] Which service is using port 8778?

On Tue, Dec 20, 2016 at 4:46 PM, Ghanshyam Mann < ghanshyam.m...@nectechnologies.in> wrote: [snip] > But OpenStack port used by services are maintained here[3], may be it will > be good for each project to add their port in this list. > [snip] > ..[3]

Re: [OpenStack-Infra] timeout, shells and ansible 2.2

On 01/11/2017 04:53 PM, Ian Wienand wrote: > The thing is, ansible 2.0.2.0 seems to do all the ssh stuff very > differently so this doesn't appear to happen. I tell a lie; this same thing actually happens with 2.0.2.0 I'm wondering if just nobody has run "run_all.sh" by hand (on a terminal)

[OpenStack-Infra] timeout, shells and ansible 2.2

So I'm trying to test ansible 2.2.1-rc3 on puppetmaster. If as root you try # /root/ianw/ansible/bin/activate # ansible 2.2.1-rc3 venv # /root/ianw/run_all.sh # run_all but with --check to dry-run You should see the problem. ansible-playbook just stops; when you take a look at the wait

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

Thanks Emilien and Giulio for your valuable feedback. I will start working towards finalizing the workbook and the actions required. > would you be able to join the PTG to help us with the session on the > overcloud settings optimization? I will come back on this, as I have not planned for it

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On 11/01/17 12:33, Anne Gentle wrote: On Tue, Jan 10, 2017 at 10:25 PM, Tom Fifield > wrote: On 11/01/17 12:21, Anne Gentle wrote: On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On Tue, Jan 10, 2017 at 10:25 PM, Tom Fifield wrote: > On 11/01/17 12:21, Anne Gentle wrote: > >> >> >> On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield > > wrote: >> >> On 11/01/17 04:07, Andreas Jaeger wrote: >> >> In

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On Tue, Jan 10, 2017 at 10:21 PM, Anne Gentle wrote: > > > On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield wrote: > >> On 11/01/17 04:07, Andreas Jaeger wrote: >> >>> In case of any problems, please report them as reply to this email or >>>

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On 11/01/17 12:21, Anne Gentle wrote: On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield > wrote: On 11/01/17 04:07, Andreas Jaeger wrote: In case of any problems, please report them as reply to this email or directly on

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On Tue, Jan 10, 2017 at 10:13 PM, Tom Fifield wrote: > On 11/01/17 04:07, Andreas Jaeger wrote: > >> In case of any problems, please report them as reply to this email or >> directly on #openstack-infra. >> > > 404 pages are missing styling: > > I think I can fix this by

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On 11/01/17 04:07, Andreas Jaeger wrote: In case of any problems, please report them as reply to this email or directly on #openstack-infra. 404 pages are missing styling: eg http://docs.openstack.org/kilo/networking-guide/scenario_legacy_lb.html Also, getting a ton of 404s in my regular

[openstack-dev] [blazar] Yesterday's meeting summary

Hi blazar folks, I share a summary of yesterday's blazar meeting because some parts of a meeting log was lost due to a bot failure. # Action items 1. Share information about PTG if there are any update. (All) 2. List ideas for a presentation at Boston Summit

Re: [openstack-dev] [infra][devstack-gate][all]support multi-region gate environment

If there is environment variable to define the role of each node, it's good. To support multi-region devstack gate/check job, we have to configure the localrc for each node of different role, for example: for the second region node, need to configure it to use the primary node's

Re: [Openstack-operators] RabbitMQ 3.6.x experience?

On Tue, Jan 10, 2017 at 4:08 PM, Sam Morrison wrote: > > > On 10 Jan 2017, at 11:04 pm, Tomáš Vondra wrote: > > > > The version is 3.6.2, but the issue that I believe is relevant is still > not fixed: > >

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

[openstack-dev] [infra] placement job is busted in stable/newton (NO MORE HOSTS LEFT)

I'm trying to sort out failures in the placement job in stable/newton job where the tests aren't failing but it's something in the host cleanup step that blows up. Looking here I see this:

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Sad to know that you will step down from Neutron PTL. Had several f2f talk with you, and got lots of valuable feedback from you. Thanks a lot! Best Regards Chaoyi Huang (joehuang) From: Armando M. [arma...@gmail.com] Sent: 09 January 2017 22:11 To: OpenStack

[openstack-dev] [kolla-ansible] Am I doing this wrong?

Hello Kolla/Kolla-ansible peoples. I have been trying to take kolla/kolla-ansible and use it to start moving our existing openstack deployment into containers. At the same time also trying to fix some of the problems that we created with our previous deployment work (everything was in

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

On 01/04/2017 09:13 AM, Saravanan KR wrote: Hello, The aim of this mail is to ease the DPDK deployment with TripleO. I would like to see if the approach of deriving THT parameter based on introspection data, with a high level input would be feasible. Let me brief on the complexity of certain

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

On 01/04/2017 09:13 AM, Saravanan KR wrote: Hello, The aim of this mail is to ease the DPDK deployment with TripleO. I would like to see if the approach of deriving THT parameter based on introspection data, with a high level input would be feasible. Let me brief on the complexity of certain

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Armando Appreciate your efforts, leadership and guidance. -Louis From: Armando M. [mailto:arma...@gmail.com] Sent: Monday, January 09, 2017 6:11 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] PTL nominations deadline and

Re: [Openstack-operators] RabbitMQ 3.6.x experience?

> On 10 Jan 2017, at 11:04 pm, Tomáš Vondra wrote: > > The version is 3.6.2, but the issue that I believe is relevant is still not > fixed: > https://github.com/rabbitmq/rabbitmq-management/issues/41 > Tomas > Yeah we found this version unusable, 3.6.5 hasn’t had any

Re: [openstack-dev] 答复: [heat] glance v2 support?

Excerpts from Thomas Herve's message of 2017-01-10 22:15:45 +0100: > On Tue, Jan 10, 2017 at 9:28 PM, Zane Bitter wrote: > > On 10/01/17 14:17, Tim Bell wrote: > >> > >> > >>> On 10 Jan 2017, at 17:41, Zane Bitter >>> > wrote: >

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Hey Armando, Too bad we can't pick on you anymore :-) On a serious note, thanks for the leadership you brought to the Neutron team and the project. Your contributions will always be appreciated. Look forward to continue to work with you. regards.. -Sukhdev On Mon, Jan 9, 2017 at 6:11 AM,

Re: [openstack-dev] [QA][Nova]Making gate-tempest-dsvm-full-devstack-plugin-ceph-ubuntu-xenial non voting

On 1/10/2017 10:02 AM, Jordan Pittier wrote: Hi, I don't know if you've noticed but the gate-tempest-dsvm-full-devstack-plugin-ceph-ubuntu-xenial job has a high rate of false negative. I've queried Gerrit and analysed all the "Verified -2" messages left by Jenkins (i.e Gate failure) for the last

[OpenStack-Infra] Gerrit downtime on Thursday 2017-01-12 at 20:00 UTC

Hi everyone, On Thursday, January 12th from approximately 20:00 through 20:30 UTC Gerrit will be unavailable while we complete project renames. Currently, we plan on renaming the following projects: Nomad -> Cyborg - openstack/nomad -> openstack/cyborg Nimble -> Mogan - openstack/nimble

[openstack-dev] Gerrit downtime on Thursday 2017-01-12 at 20:00 UTC

Hi everyone, On Thursday, January 12th from approximately 20:00 through 20:30 UTC Gerrit will be unavailable while we complete project renames. Currently, we plan on renaming the following projects: Nomad -> Cyborg - openstack/nomad -> openstack/cyborg Nimble -> Mogan - openstack/nimble

Re: [openstack-dev] [Openstack-operators] [nova] [placement] Which service is using port 8778?

We use virtual hosts, haproxy runs on our VIP at port 80 and port 443 (SSL) (with keepalived to make sure it’s always running) and we use `use_backend` to send to the appropriate backend, more information here:

[openstack-dev] [Congress] Installation/Deployment Docs

Hi all. While looking at the installation docs in preparation for scripting and testing Congress installation (https://bugs.launchpad.net/congress/+bug/1651928), I noticed there are installation instructions in two places: 1) For Users: Congress Introduction and Installation; and 2) For

Re: [Openstack-operators] [openstack-dev] [nova] [placement] Which service is using port 8778?

We use virtual hosts, haproxy runs on our VIP at port 80 and port 443 (SSL) (with keepalived to make sure it’s always running) and we use `use_backend` to send to the appropriate backend, more information here:

Re: [openstack-dev] [kolla] [heat] [ironic] Common sessions at PTG

I'll be there all week, so I can attend later sessions. Thanks, Kevin From: Michał Jastrzębski [inc...@gmail.com] Sent: Tuesday, January 10, 2017 12:49 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla]

Re: [Openstack-operators] [openstack-dev] [nova] [placement] Which service is using port 8778?

On Tue, Jan 10, 2017 at 6:00 AM, Andy McCrae wrote: > Sorry to resurrect a few weeks old thread, but I had a few questions. > >> >> Yes, we should stop with the magic ports. Part of the reason of >> switching over to apache was to alleviate all of that. >> >> -Sean

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

On Tue, Jan 10, 2017 at 6:00 AM, Andy McCrae wrote: > Sorry to resurrect a few weeks old thread, but I had a few questions. > >> >> Yes, we should stop with the magic ports. Part of the reason of >> switching over to apache was to alleviate all of that. >> >> -Sean

Re: [openstack-dev] [ironic] Policy for deprecating metric names

Hi all, There was consensus at this week's IRC meeting that the best thing to do here is simply to require a release note when metric names change. [0] I have a patch up to add this to the existing metrics documentation, so feel free to voice any concerns there:

Re: [openstack-dev] 答复: [heat] glance v2 support?

Excerpts from Zane Bitter's message of 2017-01-10 15:28:04 -0500: > On 10/01/17 14:17, Tim Bell wrote: > > > >> On 10 Jan 2017, at 17:41, Zane Bitter >> > wrote: > >> > >> On 10/01/17 05:25, Flavio Percoco wrote: > >>> > >>> > I'd recommend

Re: [openstack-dev] 答复: [heat] glance v2 support?

On Tue, Jan 10, 2017 at 9:28 PM, Zane Bitter wrote: > On 10/01/17 14:17, Tim Bell wrote: >> >> >>> On 10 Jan 2017, at 17:41, Zane Bitter >> > wrote: >>> >>> On 10/01/17 05:25, Flavio Percoco wrote: > I'd

Re: [openstack-dev] [kolla] [heat] [ironic] Common sessions at PTG

Hey Emilien, Thanks for starting this, I think it makes a lot of sense for us to sit in same room for few sessions. So Kolla will have it's sessions in first half of week, so unfortunately there is no overlap, hence I don't expect Kolla community to be well represented. I don't know yet if

Re: [openstack-dev] 答复: [heat] glance v2 support?

On 10/01/17 14:17, Tim Bell wrote: On 10 Jan 2017, at 17:41, Zane Bitter > wrote: On 10/01/17 05:25, Flavio Percoco wrote: I'd recommend Heat to not use locations as that will require deployers to either enable them for everyone or have a

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On Tue, Jan 10, 2017 at 2:07 PM, Andreas Jaeger wrote: > On 2017-01-03 20:43, Andreas Jaeger wrote: > > we discussed in today's infra meeting to move forward as follows: > > > > 1) update some missing content since a few projects haven't published > >content since we started:

Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server

On 2017-01-03 20:43, Andreas Jaeger wrote: > we discussed in today's infra meeting to move forward as follows: > > 1) update some missing content since a few projects haven't published >content since we started: >http://users.suse.com/~aj/missing-docs.tar.bz2 is a copy from >docs.o.o

[openstack-dev] [kolla] [heat] [ironic] Common sessions at PTG

Greetings folks, I've asked to TripleO folks to propose design sessions for next PTG in Atlanta and mention if some of them would need horizontal collaboration with some other projects. So far it has been the case for Heat, Ironic and Kolla: https://etherpad.openstack.org/p/tripleo-ptg-pike I

Re: [OpenStack-Infra] docs.openstack.com excessive INODE consumption

Tony, we've brought up a replacement for docs.openstack.org and developer.openstack.org and are in the final steps of switching over docs.openstack.org. Current state is: 1) We have switched over the much smaller developer.o.o site and this works fine. 2) Later today, we're switching over the

Re: [openstack-dev] [cinder] generic volume groups and consistency groups

Hi, Just want give an update on the work to migrate consistency groups to generic volume groups. The migration script and code in CG APIs to handle migrating CGs to groups are all merged. This has an impact on drivers already supporting consistency groups. A group type named

Re: [Openstack-operators] Ansible-driven management of Dell server BIOS and RAID config

We’ve had a wonderful experience with Molecule and testing roles with it, I really think it’s one of the best tools out there. It’s also useful for testing, `molecule converge` and you have a full dev env that you can reconverge till you get to the state you want. > On Jan 10, 2017, at 2:15

Re: [openstack-dev] 答复: [heat] glance v2 support?

On 10 Jan 2017, at 17:41, Zane Bitter > wrote: On 10/01/17 05:25, Flavio Percoco wrote: I'd recommend Heat to not use locations as that will require deployers to either enable them for everyone or have a dedicate glance-api node for Heat. If

Re: [openstack-dev] [tc][kolla] Adding new deliverables

I created CIVS poll with options we discussed. Every core member should get link to poll voting, if that's not the case, please let me know. On 5 January 2017 at 19:07, Britt Houser (bhouser) wrote: > I think you’re giving a great example of my point that we’re not yet at >

Re: [Openstack-operators] Ansible-driven management of Dell server BIOS and RAID config

On a similar note, if you’re looking to test Ansible roles, have a look at molecule. https://molecule.readthedocs.io On January 10, 2017 at 7:42:02 AM, Stig Telfer (stig.openst...@telfer.org) wrote: Hi All - We’ve just published the sources and a detailed writeup for some new tools for

Re: [openstack-dev] [tc][all] Feedback from driver maintainers about future of driver projects

Thanks for working on this stevemar. In the future, could we find a way to send such a survey to a broader audience? I'm not on a Cinder driver maintainer list, but I work closely with our driver maintainers and the OpenStack community, so I might be able to respond more reliably to surveys like

Re: [openstack-dev] [os-ansible-deployment] Periodic job in infra to test upgrades?

Andy McCrae wrote: > The work we can do now, which if you're able to help with would be really > great, is: > > Plan how we execute the actual job - at the moment the aio is run through a > script (scripts/gate-check-commit.sh) - the upgrade test would have to hook > into this (using the

Re: [OpenStack-Infra] Nodepool config file structure

On Mon, Jan 9, 2017, at 01:58 PM, James E. Blair wrote: > cor...@inaugust.com (James E. Blair) writes: > > >> Yup, I think this makes sense and avoids duplicate image data. One other > >> similarish use case that I don't think this addresses that we should > >> consider is the one we had in

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

On Wed, Jan 4, 2017 at 3:13 AM, Saravanan KR wrote: > Hello, > > The aim of this mail is to ease the DPDK deployment with TripleO. I > would like to see if the approach of deriving THT parameter based on > introspection data, with a high level input would be feasible. > > Let

Re: [OpenStack-Infra] [infra][picasso] request to add PTL to -core and -release groups

On Tue, Jan 10, 2017, at 09:14 AM, Derek Schultz wrote: > Hi all, > > PTL for project Picasso[1] here. Is this the proper forum to request to > be > added to the picasso-core and picasso-release groups? The email assigned > to > my Gerrit account is schultz.de...@gmail.com. Thanks in advance. >

[openstack-dev] [architecture] Return of the Arch-WG meeting -- Two proposals up for discussion

https://wiki.openstack.org/wiki/Meetings/Arch-WG With the US holidays over and people returning to their IRC clients, we'll be holding another Architecture Working Group meeting this Thursday at 2000 UTC. In preparation, I thought I'd put this out there so people can come armed with information

Re: [OpenStack-Infra] Nodepool config file structure

On Mon, Jan 09, 2017 at 01:58:14PM -0800, James E. Blair wrote: > cor...@inaugust.com (James E. Blair) writes: > > >> Yup, I think this makes sense and avoids duplicate image data. One other > >> similarish use case that I don't think this addresses that we should > >> consider is the one we had

[OpenStack-Infra] [infra][picasso] request to add PTL to -core and -release groups

Hi all, PTL for project Picasso[1] here. Is this the proper forum to request to be added to the picasso-core and picasso-release groups? The email assigned to my Gerrit account is schultz.de...@gmail.com. Thanks in advance. [1] https://launchpad.net/picasso Regards, Derek Schultz

Re: [openstack-dev] [cinder] [infra] drbdmanage is no more GPL2

On 2017-01-10 09:44:06 -0600 (-0600), Sean McGinnis wrote: [...] > It doesn't look like much has changed here. There has been one commit > that only slightly modified the new license: [1] > > IANAL, and I don't want to make assumption on what can and can't be > done, so looking to other more

Re: [openstack-dev] [nova] [placement] Ocata upgrade procedure and problems when it's optional in Newton

Le 10/01/2017 14:49, Sylvain Bauza a écrit : > Aloha folks, > > Recently, I was discussing with TripleO folks. Disclaimer, I don't think > it's only a TripleO related discussion but rather a larger one for all > our deployers. > > So, the question I was asked was about how to upgrade from

Re: [Openstack] Download file from swift extremely slow

Hello Steve, On 09.01.2017 23:27, Steve Martinelli wrote: > Thanks for the hint Clay, we merged > https://review.openstack.org/#/c/417892/ - expect this issue to be > fixed in OpenStackClient 3.7.0. unfortunately the fix didn't help - the issue is still there. I left a comment in the bugreport,

Re: [openstack-dev] [puppet] Virtual midcycle/sprint - Jan 11/12

On Tue, Jan 10, 2017 at 07:45:28AM -0700, Alex Schultz wrote: > On Tue, Dec 6, 2016 at 12:32 PM, Alex Schultz wrote: > > Hey everyone, > > > > We're going to be running a small midcycle/sprint on January 11-12, > > 2017 in #puppet-openstack on freenode. We will be reviewing

Re: [openstack-dev] 答复: [heat] glance v2 support?

On 10/01/17 05:25, Flavio Percoco wrote: I'd recommend Heat to not use locations as that will require deployers to either enable them for everyone or have a dedicate glance-api node for Heat. If not use location, do we have other options for user? What should user to do before create a

[Openstack-operators] minutes for openstack operators meetups team meeting 2017-1-10

Meeting ended Tue Jan 10 16:00:54 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 11:00 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetups_team/2017/ops_meetups_team.2017-01-10-15.02.html 11:01 AM Minutes (text):

Re: [openstack-dev] [tripleo][ui] FYI, the tripleo-ui package is currently broken

On 9 January 2017 at 13:20, Julie Pichon wrote: > On 6 January 2017 at 14:52, Julie Pichon wrote: >> Hi folks, >> >> Just a heads-up that the DLRN "current"/dev package for the Tripleo UI >> is broken in Ocata and will cause the UI to only show a blank

[Openstack] glance backend ceph swift api

Hi, >From Newton release glance s3 backend was dropped. We were successfully using it, because we already have ceph s3 service. We need to switch and ceph swift api looks like good candidate., but for that to work we need to configure glance to use auth v1 (swift_store_auth_version). I would

Re: [openstack-dev] [cinder] [infra] drbdmanage is no more GPL2

On Mon, Dec 12, 2016 at 07:58:17AM +0100, Mehdi Abaakouk wrote: > Hi, > > I have recently seen that drbdmanage python library is no more GPL2 but > need a end user license agreement [1]. > > Is this compatible with the driver policy of Cinder ? > > [1] >

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Those are sad news for starting this year. First of all, grazie for being the PTL of Neutron during these last releases. When I started contributing to neutron, I noticed that this community is so vibrant and passioned, that this energy needs to be properly addressed and you have demonstrated

[Openstack-operators] Ansible-driven management of Dell server BIOS and RAID config

Hi All - We’ve just published the sources and a detailed writeup for some new tools for Ansible-driven management of Dell iDRAC BIOS and RAID configuration: https://www.stackhpc.com/ansible-drac.html The code’s up on Github and Ansible Galaxy. It should fit neatly into any infrastructure

Re: [openstack-dev] [ironic] User survey question

On Fri, Jan 6, 2017 at 8:11 AM, Dmitry Tantsur wrote: > On 01/04/2017 07:43 PM, Mario Villaplana wrote: > >> >> > > - What's been your most frustrating or difficult experience with ironic? >> > > I wanted to suggest this ^^^ question as well, thanks Mario. > FYI, this is

[Openstack-operators] Mitaka to Newton Provider network issues

Hi All, We are currently on the process of upgrading from Mitaka to Newton, and on the upgraded compute nodes we lost all connectivity on provider networks. After digging through the ovs and ovs agent, we found that if we have only ONE provider network configured everything works as

Re: [openstack-dev] [Openstack] [mentoring] Discuss mentor/mentee experience in Boston?

Hello, I am openstack intern for the outreachy program(December 2016 - March 2017).I would love to share the experience of learning and working with experienced and motivated mentor and the communication shared by them. Regards,Namrata Sitlani From: Barrett, Carol L

Re: [Openstack] [networking-sfc] SFC in BITW or L2 mode

If thats the case then does it only support L3 mode as of now? My experiment suggest same. With this limitation, it won't be possible to any L2/BITW network functions. On Tue, Jan 10, 2017 at 12:59 PM, Vikram Choudhary wrote: > networking-sfc doesn't care about the VNF

Re: [openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

On 10 Jan 2017, at 15:21, gordon chung > wrote: On 10/01/17 07:27 AM, Julien Danjou wrote: On Mon, Jan 09 2017, William M Edmonds wrote: I started the conversation on IRC [5], but wanted to send this to the mailing list and see if others have

[openstack-dev] [QA][Nova]Making gate-tempest-dsvm-full-devstack-plugin-ceph-ubuntu-xenial non voting

Hi, I don't know if you've noticed but the gate-tempest-dsvm-full-devstack-plugin-ceph-ubuntu-xenial job has a high rate of false negative. I've queried Gerrit and analysed all the "Verified -2" messages left by Jenkins (i.e Gate failure) for the last 30 days. (script is here [1]). On project

Re: [openstack-dev] [infra][devstack-gate][all]support multi-region gate environment

joehuang wrote: > In multi-region environment(for example, two regions RegionOne and > RegionTwo), KeyStone will be shared in RegionOne and RegionTwo, so the > primary node and subnode should use different role, one role to enable the > keystone, while another role is to use the keystone in

[openstack-dev] [keystone] etherpad for ptg

keystoners, here is the link to the etherpad for the ptg: https://etherpad.openstack.org/p/keystone-pike-ptg here is a link to other project etherpads: https://wiki.openstack.org/wiki/PTG/Pike/Etherpads I'll announce this in our meeting today also. - steve

Re: [Openstack-operators] [puppet] Virtual midcycle/sprint - Jan 11/12

On Tue, Dec 6, 2016 at 12:32 PM, Alex Schultz wrote: > Hey everyone, > > We're going to be running a small midcycle/sprint on January 11-12, > 2017 in #puppet-openstack on freenode. We will be reviewing the work > items for Ocata and doing some bug triage. Feel free to add

Re: [openstack-dev] [puppet] Virtual midcycle/sprint - Jan 11/12

On Tue, Dec 6, 2016 at 12:32 PM, Alex Schultz wrote: > Hey everyone, > > We're going to be running a small midcycle/sprint on January 11-12, > 2017 in #puppet-openstack on freenode. We will be reviewing the work > items for Ocata and doing some bug triage. Feel free to add

Re: [openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

On 10/01/17 07:27 AM, Julien Danjou wrote: > On Mon, Jan 09 2017, William M Edmonds wrote: > >> I started the conversation on IRC [5], but wanted to send this to the >> mailing list and see if others have thoughts/concerns here and figure out >> what we should do about this going forward. > >

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi Yinliyin, At first I thought that changing the deduced to be a property on the alarm might help in solving your use case. But now I think most of the problems will remain the same: * It won’t solve the general problem of two different monitors that raise the same alarm * It won’t

Re: [openstack-dev] [tc][goals] Microversions in OpenStack projects

Excerpts from LAM, TIN's message of 2017-01-09 21:43:55 +: > As noted in [1], "Add microversion to REST APIs" is one of the cross-project > community goals. Given the scope and the fact there is still discussion on > what "microversion" means to each project and the exact technical >

[openstack-dev] [nova] [placement] Ocata upgrade procedure and problems when it's optional in Newton

Aloha folks, Recently, I was discussing with TripleO folks. Disclaimer, I don't think it's only a TripleO related discussion but rather a larger one for all our deployers. So, the question I was asked was about how to upgrade from Newton to Ocata for the Placement API when the deployer is not

Re: [openstack-dev] [tc][all] Feedback from driver maintainers about future of driver projects

Hey Neil, it's entirely possible I missed some folks. Feel free to reply to this thread. I'll include some of the preamble and questions from my original note. - The TC has come up with two strategies for clarification: (1) Make sure external drivers are properly listed and discoverable on

[openstack-dev] [networking-sfc] Limitation on port chains + flow classifiers

Hi networking-sfc, While working on the SFC Graphs patch, I observed the following limitation when creating port-chains: http://paste.openstack.org/show/594387/. My objective was to have 2 port-chains acting on the same classification of traffic but from different logical source ports - my

Re: [openstack-dev] ovsdpdk mitaka

Hi In mitaka all support for ovs-dpdk was merged upstream into the standard neutron openvswitch agent and ml2 driver. The networking-ovs-dpdk-agent was removed in liberty and the ml2 driver was removed in mitaka. For mitaka+ networking-ovs-dpdk primarily provides a devstack plugin to compile

Re: [openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

On Mon, Jan 09 2017, William M Edmonds wrote: > I started the conversation on IRC [5], but wanted to send this to the > mailing list and see if others have thoughts/concerns here and figure out > what we should do about this going forward. Nothing? The code has not been removed, it has been

Re: [openstack-dev] ovsdpdk mitaka

Hi Santosh. There is a getting started guide in the networking-ovs-dpdk project that should be of some help.[1] It’s written for Ubuntu 14.04, but the master branch/ stable newton is for Ubuntu 16.04. Regards. David. [1]

Re: [openstack-dev] [nova] nova-api-metadata managing firewall

2017-01-10 4:33 GMT+01:00 Sam Morrison : > Hi nova-devs, > > I raised a bug about nova-api-metadata messing with iptables on a host > > https://bugs.launchpad.net/nova/+bug/1648643 > > It got closed as won’t fix but I think it could do with a little more > discussion. > >

[Openstack-operators] [scientific][scientific-wg] Reminder: Scientific WG meeting Tuesday 2100 UTC

Greetings all - We have a Scientific WG IRC meeting on Tuesday at 2100 UTC on channel #openstack-meeting. The agenda is available here[1] and full IRC meeting details are here[2]. This week we’d like get our calendars out and talk about upcoming events for 2017, in particular anything that

Re: [openstack-dev] [nova] Inconsistency of parameter type in Nova API Reference

On 01/10/2017 01:39 AM, Takashi Natsume wrote: > Hi Nova developers. > > In Nova API Reference(*1), > the following parameters' values are 'null' in HTTP request body samples. > And their parameter types are defined as 'string'. > > * 'confirmResize' parameter in "Confirm Resized Server

[openstack-dev] [cinder] PTG planning etherpad

Hi, PTG planning etherpad wasn't advertised on the list, so I'm linking it below. It's still pretty empty, so I guess it's time to start filling it up. https://etherpad.openstack.org/p/ATL-cinder-ptg-planning Thanks, Michal

Re: [Openstack-operators] [User-committee] User Survey: Pre-launch check

Hi Heidi, In the Answers for "Which OpenStack Network (Neutron) drivers are you using?" (box E80), I think you should delete "Modular Layer 2 Plugin (ML2)". ML2 is an implementation option (and the strongly recommended one) for the vendors (including me) who provide networking drivers; it is not

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

I very much agree with Nate's comment here, and have particularly appreciated our discussions in connection with networking-calico. I look forward to your continuing involvement and help, even if not as PTL. Thanks Armando! On Mon, Jan 9, 2017 at 4:02 PM Nate Johnston

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Sorry to resurrect a few weeks old thread, but I had a few questions. > Yes, we should stop with the magic ports. Part of the reason of > switching over to apache was to alleviate all of that. > > -Sean > Is this for devstack specifically? I can see the motivation for Devstack, since it

Re: [openstack-dev] [tc][all] Feedback from driver maintainers about future of driver projects

Hi Steve, On Tue, Jan 10, 2017 at 7:35 AM Steve Martinelli wrote: > In preparation for the next TC meeting, a survey was sent out to driver > maintainers, here is a summary of the feedback that was gathered. > Did you send that survey to me, for networking-calico? I'm

Re: [openstack-dev] 答复: [heat] glance v2 support?

On 10/01/17 08:59 +, Huangtianhua wrote: -邮件原件- 发件人: Flavio Percoco [mailto:fla...@redhat.com] 发送时间: 2017年1月10日 15:34 收件人: OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] [heat] glance v2 support? On 10/01/17 12:35 +0530, Rabi Mishra wrote: On

[openstack-dev] [all] List of all Pike PTG Etherpads

Hi everyone, As suggested by notmyname on IRC, I created a wiki page listing all the Atlanta PTG room planning etherpads, for easier reference: https://wiki.openstack.org/wiki/PTG/Pike/Etherpads I tried to find all the ones mentioned on the ML so far, but I certainly missed some, so feel free

[openstack-dev] 答复: [heat] glance v2 support?

-邮件原件- 发件人: Flavio Percoco [mailto:fla...@redhat.com] 发送时间: 2017年1月10日 15:34 收件人: OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] [heat] glance v2 support? On 10/01/17 12:35 +0530, Rabi Mishra wrote: >On Mon, Jan 9, 2017 at 4:45 PM, Flavio Percoco

Re: [openstack-dev] [heat] glance v2 support?

On Tue, Jan 10, 2017 at 1:03 PM, Flavio Percoco wrote: > On 10/01/17 12:35 +0530, Rabi Mishra wrote: > >> On Mon, Jan 9, 2017 at 4:45 PM, Flavio Percoco wrote: >> >> On 06/01/17 09:34 +0530, Rabi Mishra wrote: >>> >>> On Fri, Jan 6, 2017 at 4:38 AM, Emilien

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

On 09/01/17 19:39 +0200, Andrey Kurilin wrote: On Mon, Jan 9, 2017 at 6:37 PM, Flavio Percoco wrote: On 09/01/17 17:55 +0200, Andrey Kurilin wrote: Hi, Flavio! Does it possible to create badges per project release? mmh, it's currently not possible. Could you

  1   2   >