kolla-ansible

RFE: configure proxy settings before deploy

  1. Series victoria
  2. Bug #1829586
Bug #1829586 reported by Yang Youseok
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
In Progress
Wishlist
Yang Youseok
Ussuri
Triaged
Wishlist
Yang Youseok
Victoria
In Progress
Wishlist
Yang Youseok
kolla-ansible 11.1.0 "victoria"

Bug Description

Although kolla-ansible is a complete solution which deployers does not have many things to change to achieve their own infra, there is one thing that I felt unsatisfactory. Proxy.

At a glance, I think it's reasonable to let the deployer do proxy their own but I think proxy is one of the most troublesome things to provision package so adding configuration for proxy is not a bad idea.

Especially for private cloud, I think it's very common to have a proxy server in their company infra this feature provide a big convenience to them.

For the implementation, I think precheck step or some other initial step is suitable and playbook looks like this (https://github.com/pgkehle/ansible-proxy-setup/blob/master/tasks/main.yml). From my experience, apt / pip / git are enough for right now, if community continue to manage it, it will be complete solution.

Revision history for this message
Mark Goddard (mgoddard) wrote :

Hi, thanks for the feature request. We have these variables for configuring http proxy for magnum and glance:

container_http_proxy
container_https_proxy

This is quite minimal though.

Any support added would need to go in the bootstrap-servers command - this is where we configure the host. Is this something you are prepared to work on?

Revision history for this message
Yang Youseok (ileixe) wrote :

No, I did not start to work yet. I want to make sure the feature is needed or not. Could you mind to change the status if you think it's nice to make?

Revision history for this message
Mark Goddard (mgoddard) wrote :

If it is something that you need in order to use kolla-ansible with a proxy, I think we should support it. Before you start work, I'd be interested to see a high level description of the changes you think we need to make.

Changed in kolla-ansible:
status: New → Triaged
Revision history for this message
Yang Youseok (ileixe) wrote :

@Mark

Sorry for being late. Here is my initial thought to implement

1. Add new variable to 'all.yml' http(s)_proxy
2. Use the variable when defined at 'bootstrap-servers' stage for git, apt, pip modules.

This is quite similar to other deployment system (https://github.com/kubernetes-sigs/kubespray/blob/master/roles/bootstrap-os/tasks/bootstrap-debian.yml)

And the drawbacks of this compared to adding ENVIRONMENT variable for each modules are obviously that it affect the deployed node itself. However from my current understanding, there is no way to apply http_proxy variable some programs (dockerd, apt...) via shell environment and it's difficult to depend the shell variables since each programs has their own implementation about "http_proxy"

Please give me your thought about it.

Thanks

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

Fix proposed to branch: master
Review: https://review.opendev.org/692006

Changed in kolla-ansible:
assignee: nobody → Yang Youseok (ileixe)
status: Triaged → In Progress
Mark Goddard (mgoddard)
Changed in kolla-ansible:
importance: Undecided → Medium
Mark Goddard (mgoddard)
Changed in kolla-ansible:
milestone: 11.0.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.