[openstack-dev] [hyperv] No Hyper-V meeting on 05/10/2017

Hello, There won't be any Hyper-V meeting today, on May 5th, due to the OpenStack summit. If you are attending the Summit in Boston and wish to meetup and discuss any features or future plans for Hyper-V, you can reply and we'll schedule a meeting this week. Best regards, Claudiu Belu ___

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On 05/09/2017 07:59 PM, Joshua Harlow wrote: Matt Riedemann wrote: On 5/8/2017 1:10 PM, Octave J. Orgeron wrote: I do agree that scalability and high-availability are definitely issues for OpenStack when you dig deeper into the sub-components. There is a lot of re-inventing of the wheel when yo

Re: [openstack-dev] [tripleo][ui] another i18n proposal for heat templates 'description' help strings

On 9.5.2017 17:01, Florian Fuchs wrote: On Mon, May 8, 2017 at 10:20 AM, Peng Wu wrote: Hi Julie, I generated one example javascript file containing the translatable strings. URL: https://pwu.fedorapeople.org/openstack-i18n/tripleo/tripleo-heat -templates.js And the code to generat

[openstack-dev] [tripleo][ci] Upgrade CI job for O->P (containerization)

Hi all, the upgrade job which tests Ocata -> Pike/master upgrade (from bare-metal to containers) just got a green flag from the CI [1]. I've listed the remaining patches we need to land at the very top of the container CI etherpad [2], please let's get them reviewed and landed as soon as we

[openstack-dev] [tripleo] Tripleo tempest results in openstack-health

Hello, Since last week, we have two periodic tripleo jobs running full tempest run upstream with tripleo-quickstart: The first job runs tempest against ocata release [1] The second job runs tempest against master release [2] Good news is on ocata, we are having full tempest run with 100% pass mo

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

On 5/9/2017 1:11 PM, Waines, Greg wrote: I am looking for guidance on where to propose some “_VM Heartbeat / Health-check Monitoring_” functionality that I would like to contribute to openstack. Briefly, “_VM Heartbeat / Health-check Monitoring_” · is optionally enabled thru a Nova fl

[openstack-dev] [mistral] Project Update Slides

Here is a link to the slides used during the project update session from this morning. https://goo.gl/I3ufIi - Ryan -- RYAN BRADY SENIOR SOFTWARE ENGINEER Red Hat Inc rbr...@redhat.comT: (919)-890-8925 IM: rbrady @redhatway

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

It is well-written here in OPNFV artifact: http://artifacts.opnfv.org/availability/review/33475/development_overview/index.html Br, Tuan/Nokia On Wed, May 10, 2017 at 3:49 PM, Matt Riedemann wrote: > On 5/9/2017 1:11 PM, Waines, Greg wrote: > >> I am looking for guidance on where to propose s

Re: [openstack-dev] [tripleo][ci] Upgrade CI job for O->P (containerization)

On Wed, May 10, 2017 at 9:26 AM, Jiří Stránský wrote: > Hi all, > > the upgrade job which tests Ocata -> Pike/master upgrade (from bare-metal > to containers) just got a green flag from the CI [1]. > > I've listed the remaining patches we need to land at the very top of the > container CI etherpa

[openstack-dev] Ocata - Networking OVN - option "neutron_sync_mode = repair" looks broken

Hello, I'm playing with Networking OVN, and planning to deploy it into production in a couple weeks. After deploying everything and starting using OVN, with Floating IPs, multiple compute nodes and everything else, I can say that it looks awesome! Way better than "neutron-*-agents". However,

[openstack-dev] [tripleo] [CI] HA and non-HA OVB jobs are now running with Quickstart

Hi, all In addition to multinode jobs, we migrated today part of OVB jobs to use quickstart. We had before OVB ha and OVB nonha jobs and together with migrating them to use quickstart we merged them into one job. It's called now: - gate-tripleo-ci-centos-7-ovb-ha-oooq and will be voting job inst

Re: [openstack-dev] [all] Project On-Boarding Info Collection

On Mon, May 08, 2017 at 06:57:38PM +, Kendall Nelson wrote: >Hello! > >If you are running a project onboarding session and have etherpads/slides/ >etc you are using to educate new contributors  please send them to me! I >am collecting all the resources you are sharing into a s

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

Dmitry Tantsur wrote: On 05/09/2017 07:59 PM, Joshua Harlow wrote: Matt Riedemann wrote: On 5/8/2017 1:10 PM, Octave J. Orgeron wrote: I do agree that scalability and high-availability are definitely issues for OpenStack when you dig deeper into the sub-components. There is a lot of re-inventi

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

> > How is this different from the watchdog action flavor extra spec / image > property which already exists? > Yes, understand it is similar to the virtual hardware watchdog of QEMU/KVM. ( I referred to this at end of original mail, with ref: https://libvirt.org/formatdomain.html#elementsWatchd

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

Some other UPDATES on this proposal (from outside the mailing list): · this should probably be based on an ‘image property’ rather than a ‘flavor extraspec’, since it requires code to be included in the guest/VM image, · rather than use a unique virtio-serial link for the Hear

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

On 05/10/2017 01:24 PM, Waines, Greg wrote: With respect to ... where to propose / contribute this functionality, Given that · this may require very little work in NOVA (by using QEMU Guest Agent), and · the fact that the primary result of VM Heartbeating / Health-checking is t

[openstack-dev] [nova][glance][keystone] Philosophy of the service catalog (was: Who needs multiple api_servers?)

After discussion in the Large Deployments Team session this morning, we wanted to follow up on the earlier thread [1,2] about overriding endpoint URLs. That topic is exposing an underlying implication about the purpose of the service catalog. The LDT position is that the service catalog should

Re: [openstack-dev] Ocata - Networking OVN - option "neutron_sync_mode = repair" looks broken

BUG reported: https://bugs.launchpad.net/neutron/+bug/1689880 On 10 May 2017 at 10:49, Martinx - ジェームズ wrote: > Hello, > > I'm playing with Networking OVN, and planning to deploy it into > production in a couple weeks. > > After deploying everything and starting using OVN, with Floating IPs, >

[openstack-dev] [Heat] Heat template example repository

Hi, I would like to introduce myself to the heat team. My name is Lance Haig I currently work for Mirantis doing workload onboarding to openstack. Part of my job is assisting customers with using the new Openstack cloud they have been given. I recently gave a talk with a colleague Florin Stinga

Re: [openstack-dev] [nova][glance][keystone] Philosophy of the service catalog (was: Who needs multiple api_servers?)

I didn't attend the LDT session but agree with the needs and conclusions mentioned here by Mike Dorman. It's important for us to be able to control the data path of our internal servers and overriding the URLs is the method we are currently using. You could do split view DNS but we prefer being ex

Re: [openstack-dev] [tripleo][logging] oslo.log fluentd native logging

On Mon, 2017-04-24 at 07:47 -0400, Joe Talerico wrote: > Hey owls - I have been playing with oslo.log fluentd integration[1] > in > a poc commit here [2]. Enabling the native service logging is nice > and > tracebacks no longer multiple inserts into elastic - there is a > "traceback" key which woul

Re: [openstack-dev] [neutron] - are you attending the Boston summit?

Hi Miguel, I am sorry I have to bail out at the last minute but I could not join the party tonight. Please kindly give my seat to someone else who wants to join. Hope you guys can have fun! Best regards, Lujin From: Miguel Lavalle [mailto:mig...@mlavalle.com] Sent: Tuesday, May 9, 2017 7:18 AM

Re: [openstack-dev] [tripleo][logging] oslo.log fluentd native logging

Excerpts from Dan Prince's message of 2017-05-10 17:41:12 -0400: > On Mon, 2017-04-24 at 07:47 -0400, Joe Talerico wrote: > > Hey owls - I have been playing with oslo.log fluentd integration[1] > > in > > a poc commit here [2]. Enabling the native service logging is nice > > and > > tracebacks no l

Re: [openstack-dev] [neutron] - are you attending the Boston summit?

I will see you guys there... I hope they serve beer/wine :-):-) On Tue, May 9, 2017 at 1:48 PM, Miguel Lavalle wrote: > Dear Neutrinos, > > We have a plan for tomorrow night, Wednesday 10th at 7pm. We are going to > meet at UNO Pizzeria and Grill, 731 Boylston Street Boston, MA 02116, phone > n

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

Hi Greg, If I understand correctly, you would like to add a test that checks if for every VM a heartbeat was retrieved in the last x seconds. Right? Vitrage is not designed to perform such tests. Vitrage datasources retrieve topology (either by polling or by notifications) from services like No

[openstack-dev] [defcore][tempest][refstack]Call for Volunteers for adding aliases For VolumeV2 test cases in DefCore guideline

Hi Team, The recent version of Tempest (at least from v15) has renamed all the previous VolumeV2* test case to Volume*. However the current defcore guideline has not added such alias, which has resulted in error when user wants to use new version of tempest to test. I've submitted one patch [1] t

Re: [openstack-dev] [HA] HA Discussion at Boston Forum

Hi All, This is a quick reminder for HA Forum session at Boston Summit. Thank you all for your comments and effort to make this happen in Boston Summit. Time: Thu 11 , 11:00am-11:40am Location: Hynes Convention Center - Level One - MR 103 Etherpad: https://etherpad.openstack.org/p/BOS-forum-HA