I'm a bit confused about openwisp...

[matteo fedeli]

Hi at all,

by reading this tutorial (https://github.com/openwisp/ansible-openwisp2) I don't understand how can I do to install and configure the "Production Server". Instead the "local machine" need only to complete the installation of production server?

Regarding the access point, what the difference between the explanation on the documentation (http://openwisp.io/docs/user/configure-device.html#install-openwisp-config-on-your-openwrt-instance) and the luci-openwisp? (https://github.com/openwisp/luci-openwisp). With luci I resetted the ap because the login page redirected to a blank page...

Finally, one more question, The web Interface about server allow to edit everything type of configuration or something by terminal or code?

Thanks and I Hope is a good english!

[Marco Giuntini]

Hi Matteo,

Basecally ansible-openwisp2 is a ansible-playbook to install and configure OpenWIPS2 via ansible.

"Production Server" is the server where you want to host Openwisp2 server (must need public ipv4/ipv6 and FQDN)

"Local Machine" is the machine where you are going to run the ansible-playbook, this could be a linux machine with ansible installed. 

Regards,

--
Marco Giuntini

GTalk: marco.g...@gmail.com

Skype: hispanico70420

Twitter: @Hispanico81

PGP Key ID: BD774009

--
You received this message because you are subscribed to the Google Groups "OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Federico Capoano]

Hi Matteo and welcome,

On Monday, September 17, 2018 at 11:55:21 AM UTC+2, matteo fedeli wrote:

Hi at all,

by reading this tutorial (https://github.com/openwisp/ansible-openwisp2) I don't understand how can I do to install and configure the "Production Server". Instead the "local machine" need only to complete the installation of production server?

 

ansible-openwisp2 is basically a deploy script.

You launch it from a laptop, workstation or a continuous integration server like jenkins or gitlab, we refer to these as the "local machine".

The script targets another machine, usually a server, which in the tutorial we refer to as the "production server".

You need to install ansible on your local machine, create the playbook file and the inventory file (a filed called hosts).

Ensure you correctly configure authentication so the SSH agent can authenticate successfully into the production server.

Regarding the access point, what the difference between the explanation on the documentation (http://openwisp.io/docs/user/configure-device.html#install-openwisp-config-on-your-openwrt-instance) and the luci-openwisp? (https://github.com/openwisp/luci-openwisp). With luci I resetted the ap because the login page redirected to a blank page...

Regarding how to connect OpenWRT to OpenWISP, refer to this page: http://openwisp.io/docs/user/configure-device.html

Luci-openwisp is used for a different purpose, as written in its README:

The goal of this project is to provide a limited web interface for LEDE / OpenWRT so that users can configure only the bare minimum in order for their device to connect to the OpenWISP 2 Controller.

Use this web interface only if you have a similar use case, otherwise you should keep the default LEDE / OpenWRT interface (luci-mod-admin-full).

Luci-openwisp is useful if you want to preinstall your firmware on devices, then give the device to somebody who is in charge of placing it into a building or on a rooftop and they only need to configure a couple of things, nothing more. I don't think this is your use case.

 

Finally, one more question, The web Interface about server allow to edit everything type of configuration or something by terminal or code?

I don't understand this last question well. I'll try to reply anyway according to my interpretation.

The web interface of OpenWISP allows you to change the configuration of the devices and/or prepare configuration templates for recurring configurations.

The web-interface allows a limited set of configuration options to be defined, but you can still go into advanced mode and overcome this limit, so with OpenWISP you can potentially prepare any type of configuration which is supported by OpenWRT and one of its packages.

Check the videos on our website to see some examples.

I hope this helps!

Federico

[matteo fedeli]

Perfect! Thanks Marco and Federico... So, in a  real production server (not virtualized), what should I do? I see nothing in the tutorial... Only:

1. Choose and install a linux distribution

2. Set a static ip

3. enable SSH server

it's enough?

[Federico Capoano]

First of all, using a physical server (not virtualized) is not a good idea, let me warn you:

• a physical server is harder to upgrade: you have to wipe out the entire system, install a new one and reinstall openwisp; with a virtualized infrastructure you can prepare a new VM and switch when ready
• keep in mind OpenWISP is designed to be connected to the internet and have a public IP; it can work also in a local setting with no public IP, but you will have some issues (you can't get a valid SSL cert, you can't have an OpenVPN server where all the devices outside of the same l2 network where OpenWISP is installed can connect to)
• the performance penalty of using a virtualized system instead of a physical server is so negligible that basically nowadays everyone runs OpenWISP in a virtualized architecture (and sooner or later we will move to a dockerized infrastructure)

That said, the procedure doesn't change, the steps are the same.

We assume the server has a linux distribution of the supported ones, has the network and OpenSSH server configured.

Federico

[matteo fedeli]

This system will be already virtualized... I will install on a hypervisor such as VMware, RHV or Ovirt with some servers... For this motivation I want physical installation, my idea is create a virtual machine reserved for this... Is bad idea?

Il giorno lunedì 17 settembre 2018 11:55:21 UTC+2, matteo fedeli ha scritto:

[Federico Capoano]

No is not a bad idea, ultimately is up to you, both VM and bare metal will work.

--