[openstack-dev] [Blazar] Schedule for Denver virtual PTG

Dear Blazar folks, As we discussed in previous weekly meetings, Blazar team will have virtual PTG meetup for Queens cycle because some of core members can't come there. The schedule and topics is available in the etherpad page[1] For the attendances of the PTG, the team reserves a room for t

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Tue, Sep 5, 2017 at 11:35 PM, Giulio Fidente wrote: [...] > slightly OT but notable mention, scenario001/container is also the one > gating Ceph via ceph-ansible currently :D > > ... soon to convert scenario004/container as well Really good work Giulio and John to make that happen, thanks agai

Re: [openstack-dev] [tripleo] pingtest vs tempest

On 09/05/2017 09:26 PM, Emilien Macchi wrote: > On Wed, Apr 5, 2017 at 1:49 PM, Emilien Macchi wrote: > [...] > >> == Solutions >> >> 1) Switch pingtest to Tempest run on some specific tests, with feature >> parity of what we had with pingtest. >> For example, we could imagine to run the scenario

[openstack-dev] [Blazar] Blazar 0.3.0 (pike) released

Hello everyone, A new release of Blazar project for Pike cycle was released last week. The release is tagged with 0.3.0 tag in each Blazar's repository. The quick summary of the release is following: * support the new instance reservation * support horizon dashboard * support fine-grained API

Re: [openstack-dev] [Tacker] Virtual Meetup Schedule poll

+1. Updated the poll. Best Regards, Trinath Somanchi | NXP | HSDC, INDIA From: Dharmendra Kushwaha [mailto:dharmendra.kushw...@nectechnologies.in] Sent: Wednesday, September 06, 2017 11:41 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Tacker] Vir

[openstack-dev] [Tacker] Virtual Meetup Schedule poll

Hi all, As we agreed to proceed with our virtual PTG meetup for Queens on 14th September. I have created 3 timeslots for meetup, Please vote for the time slots as per your availability: https://beta.doodle.com/poll/wkn6phxvnc8r66sv Please do it by Saturday, 9th September. Please let me know if

Re: [openstack-dev] [all] [oslo] schedule for Denver PTG is ready !

Thanks! That should work. We have a couple things set up with the baremetal/VM SIG [0] during that time, but I don't think there is a set schedule for that SIG anyway. We should be able to go through some of those topics on Tuesday if we don't get to them on Monday. [0] https://etherpad.openstack.

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

That worked :) Thanks a lot Ifat. I see the cpu alarm reported in vitrage now :). ( and in the /tmp/python-notifications.dump file that volodomyr helped me with ) Only final issue is that the vitrage alarm does not clear when I see the clear notification ( ? severity 4 ? )in /tmp/python-notifica

Re: [openstack-dev] [ironic] Team dinner at the PTG?

Thanks Julia, for taking this on. I'm actually fine if we take a cab to wherever, it seems like the PTG is in some sort of 'dead' zone wrt great food for large groups :-( Having said that, stapleton-caseys works for me, especially if they take reservations. My personal preference is for sushi sin

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Wed, Apr 5, 2017 at 1:49 PM, Emilien Macchi wrote: [...] > == Solutions > > 1) Switch pingtest to Tempest run on some specific tests, with feature > parity of what we had with pingtest. > For example, we could imagine to run the scenarios that deploys VM and > boot from volume. It would test t

[openstack-dev] [ptls] 1 Week Out PTG Reminders

Hello :) I wanted to send one more reminder before the week disappears and we are all in Denver. *PTGbot* If you don't already have PTGbot powers[1], drop by the #openstack-ptg channel and ping me/fungi/ttx/clarkb to get them :) If you aren't attending the PTG, then whoever is moderating should h

[openstack-dev] September 8 Early Bird Registration Deadline - OpenStack Summit Sydney

Hi everyone, Friendly reminder that this Friday, September 8, at 11:59pm Pacific Time (September 9 at 6:59 UTC) is the deadline to purchase passes for the OpenStack Summit in Sydney at the early bird price, which saves you 50% off full price passes. Register NOW

[openstack-dev] [tripleo] no meeting next week

We don't run the weekly meeting during the PTG, so next meeting is scheduled for September 19th. Safe travels, -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [Panko] Ways to go through events in the order they appear in database

On 05/09/17 09:27 AM, Jay Pipes wrote: > > Why not sort by created date/timestamp? Wouldn't that give you the same > behaviour (for the most part). we actually do that by default currently. the issue Mikhail ran into was because the timestamp we store is the timestamp of the message, not the t

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

On Sep 5, 2017, at 10:53 AM, Doug Hellmann wrote: > > Excerpts from Boden Russell's message of 2017-09-05 11:25:34 -0600: >> >> On 9/5/17 11:03 AM, Doug Hellmann wrote: >>> Is eventlet being initialized (or partially initialized) when a module >>> from the application is imported for the auto-ge

Re: [openstack-dev] summit free passes

Hi William, You will get a code if you check in at the Denver PTG. If you attended the Atlanta PTG, you should have already received a code. Either code is for a 100% discount, but must be used by October 27. Please let us know if yo have further questions. Thanks! Jimmy William M Edmonds

Re: [openstack-dev] [tripleo] Add support for Neutron NSX driver

Thanks Emilien and Ben. The situation is exactly as what Ben mentioned. The feature patches have been merged in Pike. But it is broken and we are trying to fix it. If we can backport it to Pike where the feature has been originally introduced, that would be great. Here are the patches that cherry-

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

Excerpts from Boden Russell's message of 2017-09-05 11:25:34 -0600: > > On 9/5/17 11:03 AM, Doug Hellmann wrote: > > Is eventlet being initialized (or partially initialized) when a module > > from the application is imported for the auto-generated API > > documentation? > More than likely :) > But

Re: [openstack-dev] [tripleo] Add support for Neutron NSX driver

On Tue, Sep 5, 2017 at 10:16 AM, Ben Nemec wrote: > > > On 09/04/2017 11:50 PM, Emilien Macchi wrote: >> >> On Fri, Sep 1, 2017 at 2:37 PM, Tong Liu wrote: >>> >>> Hi, >>> >>> In pike release, we added supported for Neutron NSX driver in TripleO [1] >>> by >>> the following patches. This will ena

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

On 09/04/2017 07:48 AM, Stephen Finucane wrote: On Mon, 2017-09-04 at 11:51 +, Gary Kotton wrote: On 9/4/17, 11:18 AM, "Stephen Finucane" wrote: Nova has a feature whereby it will provide instance host names that cloud- init can extract and use inside the guest, i.e. this won't happe

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

On 9/5/17 11:03 AM, Doug Hellmann wrote: > Is eventlet being initialized (or partially initialized) when a module > from the application is imported for the auto-generated API > documentation? More than likely :) But even if they are, what's the fix/workaround? ___

Re: [openstack-dev] [puppet][puppet-ceph]

On Tue, Sep 5, 2017 at 6:47 AM Mohammed Naser wrote: > On Tue, Sep 5, 2017 at 4:15 AM, Emil Enemærke wrote: > > Hi, > > > > I have stated using the puppet-ceph module for deploying ceph, and have > > noticed a heavy use of exec in fx define 'ceph::osd' > > (https://github.com/openstack/puppet-ce

Re: [openstack-dev] [tripleo] Add support for Neutron NSX driver

On 09/04/2017 11:50 PM, Emilien Macchi wrote: On Fri, Sep 1, 2017 at 2:37 PM, Tong Liu wrote: Hi, In pike release, we added supported for Neutron NSX driver in TripleO [1] by the following patches. This will enable TripleO overcloud deployment to use vmware_nsx as Neutron core_plugin. https:

Re: [openstack-dev] [docs][neutron] checking link integrity in the gate

Excerpts from Boden Russell's message of 2017-09-05 10:51:09 -0600: > We've (neutron) run into a few cases where our doc links become > outdated/invalid and are dead. These dead links are not detected in the > doc build today, but is something we might be interested in enabling. > > I'm no sphinx

[openstack-dev] summit free passes

It has been stated that attending the PTG will get you a free code for the summit. Is that still true even though the PTG falls after the early registration deadline in this case, or will it simply be a discount of the early-registration cost? Similarly, would someone with a free registration co

[openstack-dev] [docs][neutron] checking link integrity in the gate

We've (neutron) run into a few cases where our doc links become outdated/invalid and are dead. These dead links are not detected in the doc build today, but is something we might be interested in enabling. I'm no sphinx expert, but best I can tell that's done with the "linkcheck" builder [1]. I've

Re: [openstack-dev] [puppet] Add Mohammed Naser to cores

I think it's not unreasonable to give core rights to the PTL :) On 09/05/2017 05:42 PM, Alex Schultz wrote: Hey folks, I'm writing to ask that we add mnaser to the cores list for the puppet modules. He's been a user and contributor for some time and is also the new PTL. Let me know if there a

Re: [openstack-dev] [puppet] Add Mohammed Naser to cores

+1 - thanks for stepping up and all your contributions :-) On Tue, Sep 5, 2017 at 8:45 AM, Iury Gregory wrote: > +1 =) > And also Tks for running for PTL Mohammed > > On Sep 5, 2017 12:43, "Alex Schultz" wrote: >> >> Hey folks, >> >> I'm writing to ask that we add mnaser to the cores list for th

Re: [openstack-dev] [ptg][interop][refstack][all][ironic][cinder]RefStack and Interop WG PTG Agenda

On 9/4/2017 3:04 AM, Dmitry Tantsur wrote: On 09/01/2017 07:07 PM, Chris Hoge wrote: The RefStack and Interop WG teams will host a small work room on Monday and Tuesday at the PTG. We would like for projects interested in the interop guideline expansion to participate in guiding the developmen

Re: [openstack-dev] [puppet] Add Mohammed Naser to cores

+1 =) And also Tks for running for PTL Mohammed On Sep 5, 2017 12:43, "Alex Schultz" wrote: > Hey folks, > > I'm writing to ask that we add mnaser to the cores list for the puppet > modules. He's been a user and contributor for some time and is also > the new PTL. Let me know if there are any

Re: [openstack-dev] [tripleo] question about healthcheck

On Sun, Sep 3, 2017 at 7:44 PM, Emilien Macchi wrote: > Can someone explain me (sorry for the dumb question) why do we force > healthcheck to be positive when deploying TripleO containers? > > healthcheck: > test: /bin/true > > https://github.com/openstack/tripleo-heat-templates/blob/master/do

[openstack-dev] [puppet] Add Mohammed Naser to cores

Hey folks, I'm writing to ask that we add mnaser to the cores list for the puppet modules. He's been a user and contributor for some time and is also the new PTL. Let me know if there are any objections. Thanks, -Alex __ O

Re: [openstack-dev] [nova] [neutron] Should we continue providing FQDNs for instance hostnames?

FYI, code in Octavia that checks for the extensions you could borrow: https://github.com/openstack/octavia/blob/master/octavia/network/drivers/neutron/base.py#L49 On Mon, Sep 4, 2017 at 11:18 PM, Gary Kotton wrote: > > > On 9/4/17, 3:47 PM, "Stephen Finucane" wrote: > > On Mon, 2017-09-04 at

Re: [openstack-dev] [all][nova][neutron][qa][panko][blazar]: OpenStack meets ETSI NFV workshop on 12.09.2017

Hi, We can try to squeeze it into the schedule. Can you collect your discussion topics to an etherpad so we can decide on the timing of the timeslot? Br, Gerg0 From: Mikhail Fedosin [mailto:mfedo...@gmail.com] Sent: Tuesday, September 5, 2017 3:46 PM To: OpenStack Development Mailing List (not

[openstack-dev] [nova] [placement] Modeling SR-IOV with nested resource providers

For example, I have SR-IOV PF with four ports (P_i), two of them are connected to one switch (SW_1) and other two to another (SW_2). I would like to get VFs from distinct ports connected to distinct switches (more details can be found in spec [1]), how it can be modeled with nested resource provide

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

>For the record, oslo.config already reads /etc/neutron/neutron.conf Yeah, I think this is the only reason it even manages to get some of the correct configuration (loading a core plugin at all). >Also for the record, I consider not being able to load existing split >configuration files a regres

[openstack-dev] [ironic] PTG schedule (preliminary version)

Hi all! We're close to finalizing our schedule, and the current version can be seen at https://etherpad.openstack.org/p/ironic-queens-ptg. I've created four etherpads per block of topics for our notes: https://etherpad.openstack.org/p/ironic-queens-ptg-ongoing-work https://etherpad.openstack.o

Re: [openstack-dev] [oslo][oslo.db][keystone] A POC of Keystone over CockroachDB

On 09/04/2017 11:06 AM, Ronan-Alexandre Cherrueau wrote: > Hi folks, > > Recently in the Inria's Discovery initiative[1], we got in touch with > CockroachLabs guys with an idea: make Keystone supports CockorachDB. So > we give it a try and you can find a very first result on our GitHub[2]. > The

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

On Mon, Sep 4, 2017 at 8:07 AM, Kevin Benton wrote: > #2 would be preferable as well just because we have so many guides/distros > mentioning the different file locations. I'm not familiar with mod_wsgi > enough to know if it's possible. > > Another 3rd option may be to edit the oslo config constr

Re: [openstack-dev] [Openstack-dev][keystone][AAA] Unable to log in to DLUX UI using keystone created users

To authenticate to keystone directly, you'll need to make an authentication request to the identity API endpoint. We have documentation describing the process [0] and what the request should look like. This can also be done using python-openstackclient [1][2]. [0] https://developer.openstack.org/

[openstack-dev] [kolla] kolla 5.0.0.0rc1 (pike)

Hello everyone, A new release candidate for kolla for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kolla/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally rel

Re: [openstack-dev] [puppet][puppet-ceph]

On Tue, Sep 5, 2017 at 4:15 AM, Emil Enemærke wrote: > Hi, > > I have stated using the puppet-ceph module for deploying ceph, and have > noticed a heavy use of exec in fx define 'ceph::osd' > (https://github.com/openstack/puppet-ceph/blob/master/manifests/osd.pp). Is > there a reason for not writi

Re: [openstack-dev] [all][nova][neutron][qa][panko][blazar]: OpenStack meets ETSI NFV workshop on 12.09.2017

Yes, It will be even better! I can record a demo and publish it before the meeting. Could you schedule a short talk about IFA007 during the workshop? Best regards, Mikhail Fedosin On Fri, Sep 1, 2017 at 5:30 PM, Csatari, Gergely (Nokia - HU/Budapest) < gergely.csat...@nokia.com> wrote: > Hi, >

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

Hi Greg, There is an exception in vitrage-graph, since the configuration for devstack-vitrage/cpu/0 was not found. Please verify that your collectd_conf.yaml looks like that: collectd: - collectd_host: devstack-vitrage/cpu/0 type: name: - collectd_host: … If this doesn’t help, please s

Re: [openstack-dev] [Panko] Ways to go through events in the order they appear in database

On 09/05/2017 08:44 AM, gordon chung wrote: On 04/09/17 11:17 AM, Mikhail Kebich wrote: Hello Gordon, Any feedback? Did you get a chance to take a look at the cursor api prototype? Thanks, Mike On Wed, Aug 30, 2017 at 6:00 PM, Mikhail Kebich wrote: On Wed, Aug 30, 2017 at 4:22 PM, gordon ch

Re: [openstack-dev] [skip-level-upgrades][upgrades] Denver PTG room & etherpad

On 21-08-17 15:56:53, Lee Yarwood wrote: > Hello all, > > This is a brief announcement to highlight that there will be a skip > level upgrades room again at the PTG in Denver. I'll be chairing the > room and have seeded the etherpad below with a few goal and topic ideas. > I'd really welcome addit

[openstack-dev] [kolla] kolla-ansible 5.0.0.0rc1 (pike)

Hello everyone, A new release candidate for kolla-ansible for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kolla-ansible/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

Re: [openstack-dev] [infra][docs] Why Manila api-ref doc isn't published?

Sigh. [3] https://review.openstack.org/#/c/495326/1/www/.htaccess@52 On 09/05/2017 07:30 AM, Eric Fried wrote: > Agree with everything fungi has said here. > > Per > https://git.openstack.org/cgit/openstack/service-types-authority/tree/README.rst#n97 > we want the official service type to be sin

Re: [openstack-dev] [Panko] Ways to go through events in the order they appear in database

On 04/09/17 11:17 AM, Mikhail Kebich wrote: > Hello Gordon, > > Any feedback? Did you get a chance to take a look at the cursor api prototype? > > Thanks, > Mike > > On Wed, Aug 30, 2017 at 6:00 PM, Mikhail Kebich > wrote: >> On Wed, Aug 30, 2017 at 4:22 PM, gordon chung wrote: >>> ah, i see. i

Re: [openstack-dev] [infra][docs] Why Manila api-ref doc isn't published?

Agree with everything fungi has said here. Per https://git.openstack.org/cgit/openstack/service-types-authority/tree/README.rst#n97 we want the official service type to be singular rather than plural. And per the doc migration movement, we want the API references to live at standard URLs based on

Re: [openstack-dev] [all] [oslo] schedule for Denver PTG is ready !

Lance, I just update the schedule in [1] and add your new proposal topic in the schedule, kindly let me know when you're available, then we can rearrange your topics if you still have conflicts :-) [1] https://etherpad.openstack.org/p/oslo-ptg-queens 2017-09-02 6:16 GMT+08:00 Lance Bragstad : >

Re: [openstack-dev] [all] connecting nova notification users and developers

On 04/09/17 09:55 PM, Lingxian Kong wrote: > ​Hi Gordon, does Aodh rely on Ceilometer to receive events or it could > receive notifications directly from other services?​ yes. Ceilometer normalises the message into something Aodh can understand. (that's how it behaves currently) -- gord _

Re: [openstack-dev] [nova][scheduling] Can VM placement consider the VM network traffic need?

Interesting timeing Would love to talk about this at the ptg. Comments inline. Regards sean > -Original Message- > From: Balazs Gibizer [mailto:balazs.gibi...@ericsson.com] > Sent: Tuesday, September 5, 2017 8:23 AM > To: OpenStack Development Mailing List (not for usage questions) > > Cc

Re: [openstack-dev] [oslo][oslo.serialization]

Tom, it's good to backport the fix into previous branch. I just cherry-pick the fix in https://review.openstack.org/#/c/500781/ I will release new version of oslo.serialization for branch stable/ocata. 2017-09-04 22:15 GMT+08:00 Tom STAPPAERTS : > Hi guys, > > We are having an issue when tryin

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

Did you look into setting config files in an env var? That seemed like the best bet given that #2 is out. On Mon, Sep 4, 2017 at 8:19 AM, Mohammed Naser wrote: > On Mon, Sep 4, 2017 at 11:07 AM, Kevin Benton wrote: > > #2 would be preferable as well just because we have so many > guides/distros

Re: [openstack-dev] [all] connecting nova notification users and developers

Novajoin[1] uses notifications to detect when an instance is provisioned and register it to FreeIPA (in short). I added it to the etherpad accordingly. We're not yet using versioned notifications. [1] https://review.openstack.org/#/admin/projects/openstack/novajoin On Wed, Aug 30, 2017 at 5:30

[openstack-dev] [puppet][puppet-ceph]

Hi, I have stated using the puppet-ceph module for deploying ceph, and have noticed a heavy use of exec in fx define 'ceph::osd' ( https://github.com/openstack/puppet-ceph/blob/master/manifests/osd.pp). Is there a reason for not writing this define as an ensurable type/provider? Otherwise I will f

Re: [openstack-dev] [all] connecting nova notification users and developers

Hi, Vitrage holds a topology graph with all resources in the system and the relationships between them, for fault correlation purposes[1]. It uses notifications from Nova (as well as from other components) to update its internal state[2]. It is important for us to get immediate notifications

Re: [openstack-dev] [neutron] mod_wsgi support (pike bug?)

As a note, in OSP we also include configuration directories and things alike: https://review.rdoproject.org/r/gitweb?p=openstack/neutron-distgit.git;a=blob;f=neutron-server.service;h=e68024cb9dc06e474b1ac9473bff93c3d892b4d6;hb=48a9d1aa77506d0c60d5bc448b7c5c303083aa68#l8 Config directories make it

Re: [openstack-dev] [neutron] mod_wsgi support (pike bug?)

Why do we need to put all the configuration in a single file? That would be a big big change to deployers. It'd be great if we can think of an alternate solution. (not sure how that's being handled for other services though). Best regards, Miguel Ángel. On Mon, Sep 4, 2017 at 3:01 PM, Kevin Bent

Re: [openstack-dev] [nova][scheduling] Can VM placement consider the VM network traffic need?

On Mon, Sep 4, 2017 at 9:11 PM, Jay Pipes wrote: On 09/01/2017 04:42 AM, Rua, Philippe (Nokia - FI/Espoo) wrote: > Will it be possible to include network bandwidth as a resource in Nova scheduling, for VM placement decision? Yes. See here for a related Neutron spec that mentions Placement: h