[openstack-dev] [octavia] amphora fails to send request to members

Hi, all, I created a lb whose vip is 10.0.1.4. When requesting the vip, i cannot receive the responses. Hence, I console in the amphora and trace packets handled by eth0 in the amphora-haproxy network namespace. The detailed info is as follows.

Re: [openstack-dev] Building Openstack Trove Images

Hi Ian, We have installed Openstack Pike on Cent OS7 and we want to build mysql image in order to use with Trove. I have tried out most of the references that are available on the internet however, it’s just not working out for me. For now, kindly can share some detailed references and a brief

[openstack-dev] [vitrage] send notification when update vertex

Hi dan, I use Vitrage master branch to test 'host_down' scenario.. When scenario_evaluator match the ''host_down_alarm_on_host" scenario and Do 'mark_down' action, Process update the vertex in entity graph and then should send the notification. But currently, it didn't send the

[openstack-dev] [tripleO] building overcloud image with opendaylight

Hi all, We are now working on to support the OVS hardware offload with opendaylight deployment. First setup we want to deploy triple with just opendaylight mechanism driver. I have some question regarding the deployment: 1 . As I understand from the documentation the we need to build overcloud

Re: [openstack-dev] Building Openstack Trove Images

On 11/07/2017 05:40 PM, Ritesh Vishwakarma wrote: > as the *dib-lint* file is there instead of the mentioned > *disk-image-create *and when executed just verifies the other > elements. Those instructions unfortunately look out of date for master diskimage-builder. I will try to get a minute to

Re: [openstack-dev] Building Openstack Trove Images

++Looping my fellow engineer. On Wed, Nov 8, 2017 at 2:34 AM, Amrith Kumar wrote: > Ritesh, > > Your answers don't help me understand the problems you are having. So > let's try this instead. > > 1. What (exact) version of OpenStack are you using? Is it from upstream or

Re: [openstack-dev] [Nova] Moving the virt_mkfs flags to privsep

That does work for me, except it means I'll still need to port it to privsep to hit my goal of no rootwrap in Queens. I can live with that. Michael On Wed, Nov 8, 2017 at 4:54 PM, Matt Riedemann wrote: > On 11/8/2017 12:24 PM, Michael Still wrote: > >> Hi, >> >> a really

Re: [openstack-dev] [neutron][networking-odl]

On Wed, Nov 8, 2017 at 3:15 PM, Bhatia, Manjeet S wrote: > > >> -Original Message- >> From: Takashi Yamamoto [mailto:yamam...@midokura.com] >> Sent: Tuesday, November 7, 2017 10:13 PM >> To: Bhatia, Manjeet S >> Cc:

Re: [openstack-dev] [neutron][networking-odl]

> -Original Message- > From: Takashi Yamamoto [mailto:yamam...@midokura.com] > Sent: Tuesday, November 7, 2017 10:13 PM > To: Bhatia, Manjeet S > Cc: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [neutron][networking-odl] > > hi, > > On

Re: [openstack-dev] [neutron][networking-odl]

hi, On Thu, Nov 2, 2017 at 9:01 AM, Bhatia, Manjeet S wrote: > Hello Neutrinos, > > > > I’ve been trying service profile flavors for L3 in neutron to register the > driver, > > the method I’ve been using is below > > > > I have this added to neutron.conf > >

Re: [openstack-dev] [nova][neutron] How do you use the instance IP filter?

On 10/27/2017 1:23 PM, Matt Riedemann wrote: Nova has had this long-standing known performance issue if you're filtering a large number of instances by IP. The instance IPs are stored in a JSON blob in the database so we don't do filtering in SQL. We pull the instances out of the database,

Re: [openstack-dev] [Nova] Moving the virt_mkfs flags to privsep

On 11/8/2017 12:24 PM, Michael Still wrote: Hi, a really really long time ago (think 2011), we added support in Nova for configuring the mkfs commands that are run for new ephemeral disks using the virt_mkfs command. The current implementation is in nova/virt/disk/api.py for your reading

Re: [openstack-dev] [tripleo] Nominate akrivoka for tripleo-validations core

On Mon, Nov 6, 2017 at 6:32 AM, Honza Pokorny wrote: > Hello people, > > I would like to nominate Ana Krivokapić (akrivoka) for the core team for > tripleo-validations. She has really stepped up her game on that project > in terms of helpful reviews, and great patches. > >

Re: [openstack-dev] [tripleo] Nominate akrivoka for tripleo-validations core

On Mon, Nov 6, 2017 at 2:32 PM, Honza Pokorny wrote: > Hello people, > > I would like to nominate Ana Krivokapić (akrivoka) for the core team for > tripleo-validations. She has really stepped up her game on that project > in terms of helpful reviews, and great patches. > > With

[openstack-dev] [TripleO] Next steps for pre-deployment workflows (e.g derive parameters)

Hi all, Today I had a productive hallway discussion with jtomasek and stevebaker re $subject, so I wanted to elaborate here for the benefit of those folks not present. Hopefully we can get feedback on the ideas and see if it makes sense to continue and work on some patches: The problem under

Re: [openstack-dev] Upstream LTS Releases

On Nov 8, 2017 1:52 PM, "James E. Blair" wrote: Erik McCormick writes: > On Tue, Nov 7, 2017 at 6:45 PM, James E. Blair wrote: >> Erik McCormick writes: >> >>> The concept, in general, is to

Re: [openstack-dev] [tripleo] Nominate akrivoka for tripleo-validations core

+1, great work Ana! út 7. 11. 2017 v 1:33 odesílatel Honza Pokorny napsal: > Hello people, > > I would like to nominate Ana Krivokapić (akrivoka) for the core team for > tripleo-validations. She has really stepped up her game on that project > in terms of helpful reviews, and

Re: [openstack-dev] Upstream LTS Releases

Erik McCormick writes: > On Tue, Nov 7, 2017 at 6:45 PM, James E. Blair wrote: >> Erik McCormick writes: >> >>> The concept, in general, is to create a new set of cores from these >>> groups, and use 3rd party CI to

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, Nov 7, 2017 at 4:59 PM, Emilien Macchi wrote: > Yes. Thanks for reformulate with better words. > Just to be clear, I want to transform the scenarios into single-node > jobs that deploy the SAME services (using composable services) from > the undercloud, using the new

[openstack-dev] [Nova] Moving the virt_mkfs flags to privsep

Hi, a really really long time ago (think 2011), we added support in Nova for configuring the mkfs commands that are run for new ephemeral disks using the virt_mkfs command. The current implementation is in nova/virt/disk/api.py for your reading pleasure. I'm battling a little with how to move

Re: [openstack-dev] Upstream LTS Releases

Erik McCormick wrote: > This morning at the Sydney Summit we had a very well attended and very > productive session about how to go about keeping a selection of past > releases available and maintained for a longer period of time (LTS). > > There was agreement in the room that this could be

Re: [openstack-dev] Upstream LTS Releases

On Tue, Nov 7, 2017 at 6:45 PM, James E. Blair wrote: > Erik McCormick writes: > >> The concept, in general, is to create a new set of cores from these >> groups, and use 3rd party CI to validate patches. There are lots of >> details to be worked

Re: [openstack-dev] Upstream LTS Releases

Erik McCormick writes: > The concept, in general, is to create a new set of cores from these > groups, and use 3rd party CI to validate patches. There are lots of > details to be worked out yet, but our amazing UC (User Committee) will > be begin working out the

Re: [openstack-dev] [all][deployment][kolla][tripleo][osa] Service diagnostics task force

Michał Jastrzębski wrote: Hello my dearest of communities, During deployment tools session on PTG we discussed need for deep health checking and metering of running services. It's very relevant in context of containers (especially k8s) and HA. Things like watchdog, heartbeats

[openstack-dev] Upstream LTS Releases

Hello Ops folks, This morning at the Sydney Summit we had a very well attended and very productive session about how to go about keeping a selection of past releases available and maintained for a longer period of time (LTS). There was agreement in the room that this could be accomplished by

Re: [openstack-dev] [tripleo]

On Wed, Nov 8, 2017 at 9:54 AM, Wesley Hayutin wrote: [...] > There are already several upgrade jobs defined in the experimental queue > that can be triggered with "check rdo experimental" > Let's iterate on those, and then make them full 3rd party check jobs. > We talked

Re: [openstack-dev] [tripleo]

On Tue, Nov 7, 2017 at 5:47 PM, Emilien Macchi wrote: > On Wed, Nov 8, 2017 at 9:29 AM, Wesley Hayutin > wrote: > > Greetings, > > > > I'd like to propose we remove the upgrade jobs that are consistently > failing > > from the upstream infrastructure and

Re: [openstack-dev] [tripleo]

On Wed, Nov 8, 2017 at 9:29 AM, Wesley Hayutin wrote: > Greetings, > > I'd like to propose we remove the upgrade jobs that are consistently failing > from the upstream infrastructure and instead focus our efforts in RDO > Software Factory. > > The jobs listed in

Re: [openstack-dev] [tripleo]

On 11/07/2017 03:29 PM, Wesley Hayutin wrote: > Greetings, > > I'd like to propose we remove the upgrade jobs that are consistently > failing from the upstream infrastructure and instead focus our efforts in > RDO Software Factory. > > The jobs listed in https://review.openstack.org/#/c/518405/

[openstack-dev] [tripleo]

Greetings, I'd like to propose we remove the upgrade jobs that are consistently failing from the upstream infrastructure and instead focus our efforts in RDO Software Factory. The jobs listed in https://review.openstack.org/#/c/518405/ are consistently failing after being reviewed by myself and

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Wed, Nov 8, 2017 at 3:30 AM, James Slagle wrote: > On Sun, Nov 5, 2017 at 7:01 PM, Emilien Macchi wrote: >> On Mon, Oct 2, 2017 at 5:02 AM, Dan Prince wrote: >> [...] >> >>> -CI resources: better use of CI resources. At the PTG

Re: [openstack-dev] Building Openstack Trove Images

Ritesh, Your answers don't help me understand the problems you are having. So let's try this instead. 1. What (exact) version of OpenStack are you using? Is it from upstream or a vendor, if it is the latter, which vendor? 2. What database (exact version) are you trying to create an image for? 3.

[openstack-dev] [charms] nominating admcleod for core openstack charmer

Hi OpenStack Charmers, I'd like to nominate Andrew McLeod (admcleod) to be promoted as a core reviewer for the OpenStack Charms project. I trust Andrew's judgement in code review and collaboration with other core reviewers. Please take this to the next IRC meeting for discussion and

[openstack-dev] [QA] No team meeting tomorrow

Hello team, since a few of us will either still be in Sydney or travelling back, I'm cancelling the meeting tomorrow Nov 9 at 17UTC. Cheers, Andrea Frittoli (andreaf) __ OpenStack Development Mailing List (not for usage

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. CI migration to

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Sun, Nov 5, 2017 at 7:01 PM, Emilien Macchi wrote: > On Mon, Oct 2, 2017 at 5:02 AM, Dan Prince wrote: > [...] > >> -CI resources: better use of CI resources. At the PTG we received >> feedback from the OpenStack infrastructure team that our upstream

[openstack-dev] [Octavia] networking issues

Dear colleagues, while trying to setup Octavia, I faced the problem of connecting amphora agent to VIP network. *Environment: *Octavia 1.0.1 (installed by using "pip install") Openstack Pike: - Nova 16.0.1 - Neutron 11.0.1 - Keystone 12.0.0 *Topology of testbed:*    

Re: [openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

Correction, tomorrow 11/08/2017 On Tue, Nov 7, 2017 at 4:31 PM, Arx Cruz wrote: > Hello > > We are going to have a TripleO CI Community meeting tomorrow 11/07/2017 > at 1 pm UTC time. > The meeting is going to happen on BlueJeans [1] and also on IRC on > #tripleo channel. >

[openstack-dev] [tripleo] Please do not approve or recheck anything not related to CI alert bugs

Hey Folks So we're at 24+ hours again in the gate[0] and the queue only continues to grow. We currently have 6 ci/alert bugs[1]. Please do not approve of recheck anything that isn't related to these bugs. I will most likely need to go through the queue and abandon everything to clear it up as we

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

Hello We are going to have a TripleO CI Community meeting tomorrow 11/07/2017 at 1 pm UTC time. The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo channel. After that, we will hold Office Hours starting at 4PM UTC in case someone from community have any questions related

[openstack-dev] Unable to communicate with an instance

Hi I created an instance using OpenStack. Then, we set up Floating IP and added a rule enabling ping command and ssh command. However, it can not communicate with the instance. As I looked it up, the DHCP agent was not running on the Compute node. Also, the OpenvSwitch agent was not started.

[openstack-dev] [watcher] Watcher weekly team meeting cancelled on November 8th

Watcher team, We will cancel the coming weekly meeting due to Sydney Summit. Best Regards, __ Alexander Chadin signature.asc Description: Message signed with OpenPGP __ OpenStack Development Mailing List (not