Open shn-hmn opened 5 years ago
Hi @shn-hmn , very thankful for your suggestion, we will solve it ASAP.
BTW, because opensds-installer
also supports deployment from container, so you can change one field called install_from
in group_vars/common.yml
. Looking forward to your replies.
Thank you for quick response. I will try your suggestion. I forgot the mention this last time, but I choose "cinder" for "enabled_backend".
If the cinder
is enabled, you need to install it manually, which may be a bit difficult for new developers to setup. So I suggest lvm
, ceph
or cinder_standalone
be easier.
Thank you for the advise. I would like to setup environment for testing/evaluating purpose, besides for development environment. It's not urgent problem, so I would appreciate if the installer could support proxy in the future.
Adding to backlog for analysis and resolution in the next release.
Hi @shn-hmn san,
Allowing docker to access the Internet through proxy require putting files like the following.
[Service]
Environment="HTTPS_PROXY=http://YOUR_PROXY_IP_ADDRESS:PROXY_PORT/"
[Service]
Environment="HTTP_PROXY=http://YOUR_PROXY_IP_ADDRESS:PROXY_PORT/"
If your company's proxy requires authentication, you need to add 'USER:PASS@' in front of the YOUR_PROXY_ADDRESS
At the moment, opensds-installer ansible asks users to install docker manually. So, users need to create the above files (and reload the docker daemon).
Do you think it useful making ansible playbook installing docker too?
Also, as for programs that refer 'http_proxy' and 'https_proxy' environment variables, I think no_proxy environment variable configuration is also important.
Added upstream for salt installer: https://github.com/saltstack-formulas/docker-formula/pull/265
Hi, I'm Shinya Hamano from Fujitsu.
Is your feature request related to a problem? Please describe. Our network environment is under proxy, and it causes several problems during install. Especially, ansible/docker related scripts in the procedure of "OpenSDS Local Cluster Installation through Ansible On Ubuntu" is hard to fix by myself, because apt-get or some component using network is running in directly-downloaded containers.
Describe the solution you'd like There is "host_ip" configuration in the install procedure. Is it possible that proxy(http_proxy, https_proxy) input would be added?
Describe alternatives you've considered If it is possible to refer to the container image to be used for installation, it may works.
Additional context Japanese companies’ network often use proxy, so I think there will be similar problems from now on. I would be greatful if you consider to support proxy on the installation procedure. By the way, as develop environment, we have successfully set up OpenSDS via "Run Containerized OpenSDS Service for Testing" procedure.