Open Stack

Hi,
Could you please  point to the issue with taas?

Regards
Lajos (lajoskatona)

Sam Morrison <sorrison at gmail.com> ezt írta (időpont: 2020. szept. 9., Sze,
0:44):

>
>
> On 8 Sep 2020, at 3:13 pm, Sam Morrison <sorrison at gmail.com> wrote:
>
> Hi Yamamoto,
>
>
> On 4 Sep 2020, at 6:47 pm, Takashi Yamamoto <yamamoto at midokura.com> wrote:
>
>
> i'm talking to our infra folks but it might take longer than i hoped.
> if you or someone else can provide a public repo, it might be faster.
> (i have looked at launchpad PPA while ago. but it didn't seem
> straightforward given the complex build machinary in midonet.)
>
>
> Yeah that’s no problem, I’ve set up a repo with the latest midonet debs in
> it and happy to use that for the time being.
>
>
>
> I’m not sure why the pep8 job is failing, it is complaining about pecan
> which makes me think this is an issue with neutron itself? Kinda stuck on
> this one, it’s probably something silly.
>
>
> probably.
>
>
> Yeah this looks like a neutron or neutron-lib issue
>
>
>
> For the py3 unit tests they are now failing due to db migration errors in
> tap-as-a-service, l2-gateway and vpnaas issues I think caused by neutron
> getting rid of the liberty alembic branch and so we need to squash these on
> these projects too.
>
>
> this thing? https://review.opendev.org/#/c/749866/
>
>
> Yeah that fixed that issue.
>
>
> I have been working to get everything fixed in this review [1]
>
> The pep8 job is working but not in the gate due to neutron issues [2]
> The py36/py38 jobs have 2 tests failing both relating to tap-as-a-service
> which I don’t really have any idea about, never used it. [3]
>
>
> These are failing because of this patch on tap-as-a-service
>
> https://opendev.org/x/tap-as-a-service/commit/8332a396b1b046eb370c0cb377d836d0c6b6d6ca
>
> Really have no idea how this works, does anyone use tap-as-a-service with
> midonet and can help me fix it, else I’m wondering if we disable tests for
> taas and make it an unsupported feature for now.
>
> Sam
>
>
>
> The tempest aio job is working well now, I’m not sure what tempest tests
> were run before but it’s just doing what ever is the default at the moment.
> The tempest multinode job isn’t working due to what I think is networking
> issues between the 2 nodes. I don’t really know what I’m doing here so any
> pointers would be helpful. [4]
> The grenade job is also failing because I also need to put these fixes on
> the stable/ussuri branch to make it work so will need to figure that out too
>
> Cheers,
> Sam
>
> [1] https://review.opendev.org/#/c/749857/
> [2]
> https://zuul.opendev.org/t/openstack/build/e94e873cbf0443c0a7f25ffe76b3b00b
> [3]
> https://b1a2669063d97482275a-410cecb8410320c66fb802e0a530979a.ssl.cf5.rackcdn.com/749857/18/check/openstack-tox-py36/0344651/testr_results.html
> [4]
> https://zuul.opendev.org/t/openstack/build/61f6dd3dc3d74a81b7a3f5968b4d8c72
>
>
>
>
>
>
> I can now start to look into the devstack zuul jobs.
>
> Cheers,
> Sam
>
>
> [1] https://github.com/NeCTAR-RC/networking-midonet/commits/devstack
> [2] https://github.com/midonet/midonet/pull/9
>
>
>
>
> On 1 Sep 2020, at 4:03 pm, Sam Morrison <sorrison at gmail.com> wrote:
>
>
>
> On 1 Sep 2020, at 2:59 pm, Takashi Yamamoto <yamamoto at midokura.com> wrote:
>
> hi,
>
> On Tue, Sep 1, 2020 at 1:39 PM Sam Morrison <sorrison at gmail.com> wrote:
>
>
>
>
> On 1 Sep 2020, at 11:49 am, Takashi Yamamoto <yamamoto at midokura.com>
> wrote:
>
> Sebastian, Sam,
>
> thank you for speaking up.
>
> as Slawek said, the first (and probably the biggest) thing is to fix the
> ci.
> the major part for it is to make midonet itself to run on ubuntu
> version used by the ci. (18.04, or maybe directly to 20.04)
> https://midonet.atlassian.net/browse/MNA-1344
> iirc, the remaining blockers are:
> * libreswan (used by vpnaas)
> * vpp (used by fip64)
> maybe it's the easiest to drop those features along with their
> required components, if it's acceptable for your use cases.
>
>
> We are running midonet-cluster and midolman on 18.04, we dropped those
> package dependencies from our ubuntu package to get it working.
>
> We currently have built our own and host in our internal repo but happy to
> help putting this upstream somehow. Can we upload them to the midonet apt
> repo, does it still exist?
>
>
> it still exists. but i don't think it's maintained well.
> let me find and ask someone in midokura who "owns" that part of infra.
>
> does it also involve some package-related modifications to midonet repo,
> right?
>
>
>
> Yes a couple, I will send up as as pull requests to
> https://github.com/midonet/midonet today or tomorrow
>
> Sam
>
>
>
>
>
> I’m keen to do the work but might need a bit of guidance to get started,
>
> Sam
>
>
>
>
>
>
>
> alternatively you might want to make midonet run in a container. (so
> that you can run it with older ubuntu, or even a container trimmed for
> JVM)
> there were a few attempts to containerize midonet.
> i think this is the latest one: https://github.com/midonet/midonet-docker
>
> On Fri, Aug 28, 2020 at 7:10 AM Sam Morrison <sorrison at gmail.com> wrote:
>
>
> We (Nectar Research Cloud) use midonet heavily too, it works really well
> and we haven’t found another driver that works for us. We tried OVN but it
> just doesn’t scale to the size of environment we have.
>
> I’m happy to help too.
>
> Cheers,
> Sam
>
>
>
> On 31 Jul 2020, at 2:06 am, Slawek Kaplonski <skaplons at redhat.com> wrote:
>
> Hi,
>
> Thx Sebastian for stepping in to maintain the project. That is great news.
> I think that at the beginning You should do 2 things:
> - sync with Takashi Yamamoto (I added him to the loop) as he is probably
> most active current maintainer of this project,
> - focus on fixing networking-midonet ci which is currently broken - all
> scenario jobs aren’t working fine on Ubuntu 18.04 (and we are going to move
> to 20.04 in this cycle), migrate jobs to zuulv3 from the legacy ones and
> finally add them to the ci again,
>
> I can of course help You with ci jobs if You need any help. Feel free to
> ping me on IRC or email (can be off the list).
>
> On 29 Jul 2020, at 15:24, Sebastian Saemann <Sebastian.Saemann at netways.de>
> wrote:
>
> Hi Slawek,
>
> we at NETWAYS are running most of our neutron networking on top of midonet
> and wouldn't be too happy if it gets deprecated and removed. So we would
> like to take over the maintainer role for this part.
>
> Please let me know how to proceed and how we can be onboarded easily.
>
> Best regards,
>
> Sebastian
>
> --
> Sebastian Saemann
> Head of Managed Services
>
> NETWAYS Managed Services GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
> Tel: +49 911 92885-0 | Fax: +49 911 92885-77
> CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB25207
> https://netways.de | sebastian.saemann at netways.de
>
> ** NETWAYS Web Services - https://nws.netways.de **
>
>
> —
> Slawek Kaplonski
> Principal software engineer
> Red Hat
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200909/b7840ae9/attachment.html>