[loci] How to add some agent to loci images
Hello, Jean. I tried to add lbaas-agent and fwaas-agent to official loci neutron image. To pass openstack-helm gate test, I need lbaas-agent and fwaas-agent. I found your openstack source repository is repository: 172.17.0.1:5000/loci/requirements Please let me know I can I add lbaas-agent and fwaas-agent to official loci neutron image. Thanks, Siri
Except in a few instances, Loci aims to generically build OpenStack service images and has pretty robust scripts that will allow you to build the containers without modification of the project. In the instance of neutron-fwaas, you can easily build the service following the instructions in README.md[1] in the Loci repository. Just set `PROJECT=neutron-fwaas` and tag appripriately. The major caveat is the build for that project is not gate tested (although I've managed to complete a build of it in my own environment). You could do the same thing similarly for neutron-lbaas, but please be aware that for a number of reasons neutron-lbaas project has been deprecated[2], and you should instead prefer to use Octavia as the official replacement for it. Thanks, Chris [1] http://git.openstack.org/cgit/openstack/loci/tree/README.md [2] https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation
On Dec 5, 2018, at 5:30 PM, SIRI KIM <shiriul.lol@gmail.com> wrote:
Hello, Jean.
I tried to add lbaas-agent and fwaas-agent to official loci neutron image. To pass openstack-helm gate test, I need lbaas-agent and fwaas-agent.
I found your openstack source repository is repository: 172.17.0.1:5000/loci/requirements
Please let me know I can I add lbaas-agent and fwaas-agent to official loci neutron image.
Thanks, Siri
I have added [openstack-helm] since this might be cross-project issue. our objetive: add neutron-lbaas & neutron-fwaas chart to openstack-helm upstream. problem: we need this loci image to push lbaas and fwaas chart into upstream repo. In order to pass osh gating, we need to have neutron-lbaas & neutron-fwaas agent image available for openstack-helm project. My question was not about how to build loci image locally, but what would be the best way to make these two images (lbaas and fwaas) available for openstack-helm project. Please kindly guide me here. :) thanks PS. This link is added openstack-helm neutron-lbaas. https://review.openstack.org/#/c/609299/ 2018년 12월 7일 (금) 오전 4:54, Chris Hoge <chris@openstack.org>님이 작성:
Except in a few instances, Loci aims to generically build OpenStack service images and has pretty robust scripts that will allow you to build the containers without modification of the project. In the instance of neutron-fwaas, you can easily build the service following the instructions in README.md[1] in the Loci repository. Just set `PROJECT=neutron-fwaas` and tag appripriately. The major caveat is the build for that project is not gate tested (although I've managed to complete a build of it in my own environment).
You could do the same thing similarly for neutron-lbaas, but please be aware that for a number of reasons neutron-lbaas project has been deprecated[2], and you should instead prefer to use Octavia as the official replacement for it.
Thanks, Chris
[1] http://git.openstack.org/cgit/openstack/loci/tree/README.md [2] https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation
On Dec 5, 2018, at 5:30 PM, SIRI KIM <shiriul.lol@gmail.com> wrote:
Hello, Jean.
I tried to add lbaas-agent and fwaas-agent to official loci neutron image. To pass openstack-helm gate test, I need lbaas-agent and fwaas-agent.
I found your openstack source repository is repository: 172.17.0.1:5000/loci/requirements
Please let me know I can I add lbaas-agent and fwaas-agent to official loci neutron image.
Thanks, Siri
On Fri, 2018-12-07 at 10:21 +0900, SIRI KIM wrote:
our objetive: add neutron-lbaas & neutron-fwaas chart to openstack- helm upstream. problem: we need this loci image to push lbaas and fwaas chart into upstream repo. In order to pass osh gating, we need to have neutron- lbaas &
neutron-fwaas agent image available for openstack-helm project.
Yeah this seems more an OSH issue on how to properly leverage's LOCI feature (and publishing a series of images) than a request to LOCI directly I'd say :) I am currently refactoring how OSH is building LOCI images, but the idea of it would be pretty generic. It would be extensible by having a few extra environment variables before calling the build script (which basically do a series of docker builds). In those environment variables you could pass which projects to build, which variables to pass to LOCI (for example, "build me an octavia image with x"), what would be the registry of your choice. The result would be an updated/published image of your choice (on your dockerhub's user for example), which could then be used in your chart. Note: I don't think it's a good idea to build lbaas nowadays, as it's kinda the past :) Regards, Jean-Philippe Evrard (evrardjp)
On Mon, Dec 10, 2018 at 8:11 PM Jean-Philippe Evrard < jean-philippe@evrard.me> wrote:
On Fri, 2018-12-07 at 10:21 +0900, SIRI KIM wrote:
our objetive: add neutron-lbaas & neutron-fwaas chart to openstack- helm upstream. problem: we need this loci image to push lbaas and fwaas chart into upstream repo. In order to pass osh gating, we need to have neutron- lbaas &
neutron-fwaas agent image available for openstack-helm project.
Yeah this seems more an OSH issue on how to properly leverage's LOCI feature (and publishing a series of images) than a request to LOCI directly I'd say :)
Hi, I do agree that this seems OSH issue, I will bring this up on osh weekly meeting. :) Thanks. -- *Jaesuk Ahn*, Ph.D. Software R&D Center, SK Telecom
participants (4)
-
Chris Hoge
-
Jaesuk Ahn
-
Jean-Philippe Evrard
-
SIRI KIM