Re: [openstack-dev] Need help on this neutron-server start error with vmware_nsx plugin enable

[Tong Liu]

Hi Enoch,

There are two issues here.
1. Plugin 'vmware_nsx.plugin.NsxDvsPlugin' cannot be found.
This could be resolved by changing core_plugin to 'vmware_nsxv' as the
entry point for vmware_nsxv is defined as vmware_nsxv.
2. No module named neutron_fwaas.db.firewall
It looks like you are missing firewall module. Can you try to install
neutron_fwaas module either from rpm or from repo?

Thanks,
Tong

On Fri, Jul 13, 2018 at 4:10 AM Enoch Huangfu  wrote:

> env:
> openstack queen version on centos7
> latest vmware_nsx plugin rpm installed: python-networking-vmware-nsx-12.0.1
>
> when i modify 'core_plugin' value in [default] section of
> /etc/neutron/neutron.conf from ml2 to vmware_nsx.plugin.NsxDvsPlugin, then
> try to start neutron-server with command 'systemctl start neutron-server'
> on control node, the log shows:
>
> 2018-07-13 17:57:50.802 25653 INFO neutron.manager [-] Loading core
> plugin: vmware_nsx.plugin.NsxDvsPlugin
> 2018-07-13 17:57:51.017 25653 DEBUG neutron_lib.callbacks.manager [-]
> Subscribe:  > rbac-policy before_create
> subscribe
> /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:41
> 2018-07-13 17:57:51.017 25653 DEBUG neutron_lib.callbacks.manager [-]
> Subscribe:  > rbac-policy before_update
> subscribe
> /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:41
> 2018-07-13 17:57:51.017 25653 DEBUG neutron_lib.callbacks.manager [-]
> Subscribe:  > rbac-policy before_delete
> subscribe
> /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:41
> 2018-07-13 17:57:51.366 25653 DEBUG neutron_lib.callbacks.manager [-]
> Subscribe: 
> router_gateway before_create subscribe
> /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:41
> 2018-07-13 17:57:51.393 25653 DEBUG neutron_lib.callbacks.manager [-]
> Subscribe:  > rbac-policy before_create
> subscribe
> /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:41
> 2018-07-13 17:57:51.394 25653 DEBUG neutron_lib.callbacks.manager [-]
> Subscribe:  > rbac-policy before_update
> subscribe
> /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:41
> 2018-07-13 17:57:51.394 25653 DEBUG neutron_lib.callbacks.manager [-]
> Subscribe:  > rbac-policy before_delete
> subscribe
> /usr/lib/python2.7/site-packages/neutron_lib/callbacks/manager.py:41
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime [-] Error
> loading class by alias: NoMatches: No 'neutron.core_plugins' driver found,
> looking for 'vmware_nsx.plugin.NsxDvsPlugin'
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime Traceback
> (most recent call last):
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime   File
> "/usr/lib/python2.7/site-packages/neutron_lib/utils/runtime.py", line 46,
> in load_class_by_alias_or_classname
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime
>  namespace, name, warn_on_missing_entrypoint=False)
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime   File
> "/usr/lib/python2.7/site-packages/stevedore/driver.py", line 61, in __init__
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime
>  warn_on_missing_entrypoint=warn_on_missing_entrypoint
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime   File
> "/usr/lib/python2.7/site-packages/stevedore/named.py", line 89, in __init__
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime
>  self._init_plugins(extensions)
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime   File
> "/usr/lib/python2.7/site-packages/stevedore/driver.py", line 113, in
> _init_plugins
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime
>  (self.namespace, name))
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime NoMatches:
> No 'neutron.core_plugins' driver found, looking for
> 'vmware_nsx.plugin.NsxDvsPlugin'
> 2018-07-13 17:57:51.442 25653 ERROR neutron_lib.utils.runtime
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime [-] Error
> loading class by class name: ImportError: No module named
> neutron_fwaas.db.firewall
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime Traceback
> (most recent call last):
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime   File
> "/usr/lib/python2.7/site-packages/neutron_lib/utils/runtime.py", line 52,
> in load_class_by_alias_or_classname
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime
>  class_to_load = importutils.import_class(name)
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime   File
> "/usr/lib/python2.7/site-packages/oslo_utils/importutils.py", line 30, in
> import_class
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime
>  __import__(mod_str)
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime   File
> "/usr/lib/python2.7/site-packages/vmware_nsx/plugin.py", line 24, in
> 
> 2018-07-13 17:57:51.443 25653 ERROR neutron_lib.utils.runtime from
> vmware_nsx.plugins.nsx import plugin as nsx
> 

Re: [openstack-dev] Zuul dashboard available

[Tong Liu]

Today, there are lots of zuul jobs timed out and the dashboard is
inaccessible with "proxy error". Can zuul team have a look at it?

Thanks,
Tong

On Mon, Dec 11, 2017 at 9:11 AM, James E. Blair  wrote:

> Hi,
>
> I'd like to draw your attention to a recently added feature in Zuul.
>
> If you visit http://zuulv3.openstack.org/ you will note three tabs at
> the top of the screen (you may need to shift-reload the page): Status,
> Jobs, Builds.  The "Jobs" page shows you a list of all of the jobs in
> the system, along with their descriptions.  And the "Builds" page lists
> the most recent runs.  You can query by pipeline, job, and project.
>
> This may be especially helpful in tracking down builds (and their logs)
> for periodic or other post-merge jobs.
>
> We have a lot of plans to expand on and enhance these pages in the
> future, however, for the next short while, we probably won't be making
> very substantial changes to them as we prepare for the actual Zuul v3.0
> release.
>
> We hope in the mean time, the additional functionality they provide will
> prove useful.
>
> Thanks very much to Tristan Cacqueray and Joshua Hesketh whose work has
> made this possible.
>
> -Jim
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [octavia] Proposing Nir Magnezi as Octavia core reviewer

[Tong Liu]

Congratulations Nir!

On Tue, Oct 10, 2017 at 1:36 PM, Nir Magnezi  wrote:

> Thanks everyone for your votes :-)
> I'm really happy to become a member of this great team!
>
> Nir
>
> On Tue, Oct 10, 2017 at 1:28 AM, Michael Johnson 
> wrote:
>
>> Ok, that is quorum.
>>
>> Congratulations Nir!
>>
>> Michael
>>
>>
>> On Mon, Oct 9, 2017 at 3:18 PM, Adam Harwell  wrote:
>> > +1
>> >
>> >
>> > On Thu, Oct 5, 2017, 05:48 Daniel Mellado 
>> > wrote:
>> >>
>> >> +1
>> >>
>> >> Go, Nir, Go!
>> >>
>> >> congrats!
>> >>
>> >> On 10/05/2017 03:51 AM, German Eichberger wrote:
>> >> > +1
>> >> >
>> >> > Welcome Nir, well earned.
>> >> >
>> >> > German
>> >> >
>> >> > On 10/4/17, 4:28 PM, "Michael Johnson"  wrote:
>> >> >
>> >> > Hello OpenStack folks,
>> >> >
>> >> > I would like to propose Nir Magnezi as a core reviewer on the
>> >> > Octavia project.
>> >> >
>> >> > He has been an active contributor to the Octavia projects for a
>> few
>> >> > releases and has been providing solid patch review comments. His
>> >> > review stats are also in line with other core reviewers.
>> >> >
>> >> > Octavia cores, please reply to this e-mail with your
>> >> > agreement/disagreement to this proposal.
>> >> >
>> >> > Michael
>> >> >
>> >> >
>> >> > 
>> __
>> >> > OpenStack Development Mailing List (not for usage questions)
>> >> > Unsubscribe:
>> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
>> ck-dev
>> >> >
>> >> >
>> >> >
>> >> > 
>> __
>> >> > OpenStack Development Mailing List (not for usage questions)
>> >> > Unsubscribe:
>> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >> >
>> >>
>> >>
>> >> 
>> __
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [devstack] zuulv3 gate status; LIBS_FROM_GIT failures

[Tong Liu]

The workaround [1] has not landed yet. I saw it has +1 workflow but has not
been merged.

Thanks,
Tong
[1] https://review.openstack.org/#/c/508344/

On Mon, Oct 2, 2017 at 6:51 AM, Mehdi Abaakouk  wrote:

> Looks like the LIBS_FROM_GIT workarounds have landed, but I still have
> some issue
> on telemetry integration jobs:
>
>  http://logs.openstack.org/32/508132/1/check/legacy-telemetr
> y-dsvm-integration-ceilometer/e3bd35d/logs/devstacklog.txt.gz
>
>
> On Fri, Sep 29, 2017 at 10:57:34AM +0200, Mehdi Abaakouk wrote:
>
>> On Fri, Sep 29, 2017 at 08:16:38AM +, Jens Harbott wrote:
>>
>>> 2017-09-29 7:44 GMT+00:00 Mehdi Abaakouk :
>>>
 We also have our legacy-telemetry-dsvm-integration-ceilometer broken:

 http://logs.openstack.org/32/508132/1/check/legacy-telemetry
 -dsvm-integration-ceilometer/e185ae1/logs/devstack-gate-
 setup-workspace-new.txt

>>>
>>> That looks similar to what Ian fixed in [1], seems like your job needs
>>> a corresponding patch.
>>>
>>
>> Thanks, I have proposed the same kind of patch for telemetry [1]
>>
>> [1] https://review.openstack.org/508448
>>
>> --
>> Mehdi Abaakouk
>> mail: sil...@sileht.net
>> irc: sileht
>>
>
> --
> Mehdi Abaakouk
> mail: sil...@sileht.net
> irc: sileht
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] stable/pike gate is broken with containers

[Tong Liu]

It is working now. I rebased one patch and the build succeeded.

Emilien, could you please approve the patch again as previous one was lost
after rebase?
https://review.openstack.org/#/c/500794/

Thanks,
Tong

On Sun, Sep 10, 2017 at 5:27 PM, Martin André  wrote:

> On Sun, Sep 10, 2017 at 10:47 PM, Emilien Macchi 
> wrote:
> > Today I found 2 issues:
> >
> > 1) https://bugs.launchpad.net/tripleo/+bug/1716256
> >
> > http://logs.openstack.org/94/500794/2/check-tripleo/gate-
> tripleo-ci-centos-7-ovb-containers-oooq/c3e3945/logs/
> undercloud/home/jenkins/overcloud_prep_containers.log.
> txt.gz#_2017-09-10_14_49_29
> >
> > I think we need this backport: https://review.openstack.org/#/c/502291
> > but it fails here:
> > http://logs.openstack.org/91/502291/1/check-tripleo/gate-
> tripleo-ci-centos-7-ovb-containers-oooq/8140294/logs/
> undercloud/home/jenkins/overcloud_prep_containers.log.
> txt.gz#_2017-09-10_19_42_16
> >
> > We probably missed some other backports. Can anyone familiar with this
> > piece help?
>
> I've replied to the bug, it's an issue with the python-tripleoclient
> package used on the undercloud that is too old and doesn't have the
> code that was merged 10 days ago in the stable/pike branch. Not sure
> what is going on.
>
> > 2) https://bugs.launchpad.net/tripleo/+bug/1716280
> >
> > stable/pike CI deploys Queens containers, tag is missing in Docker
> > Registry. I'm cc'ing dprince because I think he has access to the
> > dockerhub account, in case we need to do any change there.
>
> Here I'm rebuilding the images for pike with the appropriate tag. Once
> this is done we can use the pike tag in CI.
>
> Martin
>
> > Thanks for the help,
> > --
> > Emilien Macchi
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Tong Liu]

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-picked to Pike:
https://review.openstack.org/#/c/500946/
https://review.openstack.org/#/c/500794/
https://review.openstack.org/#/c/500674/

Thanks,
Tong

On Tue, Sep 5, 2017 at 10:32 AM, Emilien Macchi <emil...@redhat.com> wrote:

> On Tue, Sep 5, 2017 at 10:16 AM, Ben Nemec <openst...@nemebean.com> wrote:
> >
> >
> > On 09/04/2017 11:50 PM, Emilien Macchi wrote:
> >>
> >> On Fri, Sep 1, 2017 at 2:37 PM, Tong Liu <lex...@gmail.com> 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://review.openstack.org/#/c/441668/
> >>> https://review.openstack.org/#/c/452047/
> >>> https://review.openstack.org/#/c/452391/
> >>>
> >>> However, there are some critical issues which prevent it from
> functional
> >>> correctly, and we fixed them in master with the following patches.
> >>> https://review.openstack.org/#/c/499395/
> >>> https://review.openstack.org/#/c/498143/
> >>> https://review.openstack.org/#/c/498142/
> >>>
> >>> Can we merged these patches and back port to pike?
> >>
> >>
> >> So if we follow all the rules, it goes against how to we handle stable
> >> branches and release management in general.
> >
> >
> > I don't know that I agree.  These patches are all for a feature that
> merged
> > earlier in Pike, but apparently is broken.  The only real issue I see is
> > that the first one doesn't have a bug reference and thus isn't valid for
> > backport as-is.  That one might need further discussion, but the others
> seem
> > to be legitimate bug fixes.
> >
> > I also don't see any blueprint references, so I'm not sure how that came
> > into the discussion.  Maybe some confusion about the process for FFE's
> vs.
> > bugs?  It doesn't appear to me that a bp should be needed for these
> changes,
> > but maybe I'm missing something.
>
> In that case let's threat them as bug fixes and let's do the backports
> to stable/pike.
>
> >
> >>
> >> Usually what happens is we discuss about blueprints at PTG and then
> >> during the cycle developers implement the blueprints.
> >> Sometimes some blueprint get deferred for some reason (quite often
> >> it's because of overcommit but that's a separated topic) so they can
> >> as for FFE (feature freeze exception), granted by the PTL.
> >>
> >> In your case, it's a bit more complex. You created the blueprint a few
> >> days before final release of Pike and you're asking us to merge the
> >> code AND backport it to Pike.
> >> That's for the facts & context, hope it helps to understand why this
> >> request is tricky.
> >>
> >> Now you're a vendor and you're helping to support your driver, which is
> >> good.
> >>
> >> We'll need to evaluate each commit and see if they are backward
> >> compatible and actually don't beak any interface (because we want our
> >> stable branches stable).
> >>
> >> I'm ok to make an exception if next time you can do a better job in
> >> scheduling the work that will be done during one cycle.
> >> The way we propose blueprint is really lightweight, and in the open,
> >> so really no complication here.
> >>
> >>
> >> For now, most of the team is quite busy on Pike release (and PTG
> >> coming next week), so I'm not sure your patches will be reviewed soon
> >> (if yes, that's good).
> >> For the backports, we'll have to evaluate case by case and see if it's
> >> possible.
> >>
> >> Thanks for your work and we hope our collaboration can happen earlier
> >> the next time.
> >>
> >>> Thanks,
> >>> Tong
> >>> [1] Blueprint:
> >>> https://blueprints.launchpad.net/tripleo/+spec/neutron-nsx-driver
> >>
> >>
> >>
> >
>
>
>
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Tong Liu]

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://review.openstack.org/#/c/441668/
https://review.openstack.org/#/c/452047/
https://review.openstack.org/#/c/452391/

However, there are some critical issues which prevent it from functional
correctly, and we fixed them in master with the following patches.
https://review.openstack.org/#/c/499395/
https://review.openstack.org/#/c/498143/
https://review.openstack.org/#/c/498142/

Can we merged these patches and back port to pike?

Thanks,
Tong
[1] Blueprint:
https://blueprints.launchpad.net/tripleo/+spec/neutron-nsx-driver
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev