Re: [openwisp] How do I install and configure OpenWISP?

[Oliver Kraitschy]

Hello,

Am Mon, Jul 04, 2022 at 07:35:37PM -0700 schrieb Turritopsis Dohrnii Teo En 
Ming:
> Subject: How do I install and configure OpenWISP?
> 
> Are there any excellent and well-written documentation for doing so?

Please take a look at https://openwisp.io/docs/index.html

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/YsPSyAXdhVEcwgX6%40obelix.okraits.de.

Re: [openwisp] File path shouldn't be allowed to be empty #166

[Oliver Kraitschy]

Hi balaji,

I don't know which bug you are referring to because you didn't mention the
repository. But I suggest to reply to the issue on Github to discuss any
details.

Greetings,
Oliver

On Sun, Oct 18, 2020 at 11:38:38PM -0700, balaji wrote:
> I am trying to understand and probably this bug "File path shouldn't be 
> allowed to be empty #166", opened by nemesisdesign.
> 
> Can you please provide more details like, 
> 
> which file path is referred to here?
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/openwisp/04dd688e-467c-4e9d-ae71-e506e3fa1344n%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20201019064638.GA7990%40obelix.okraits.de.

Re: [openwisp] First release of openwisp-notifications

[Oliver Kraitschy]

Hello Gagan,

congratulations and thank you for your great work!

Greetings,
Oliver

On Wed, Sep 02, 2020 at 04:48:20PM -0700, Gagan Deep wrote:
> 
> 
> I am delighted to share that OpenWISP Notifications 0.1.0 has been officially 
> released  after 
> months of work. If you are curious about the new notification module, you 
> can check out the "OpenWISP Notifications Release 0.1.0 
> "
>  
> blog which explores different features packed in OpenWISP Notifications. 
> Through this module, notifications/alerts will become an integral feature 
> of OpenWISP with coming releases. Try out OpenWISP Notifications and share 
> your valuable feedback with us.
> 
> Release Blog: 
> https://medium.com/@pandafy/openwisp-notifications-release-0-1-0-b0640f019df5
> 
> OpenWISP Notifications on PyPI: 
>  https://pypi.org/project/openwisp-notifications/0.1/ 
> 
> 
> OpenWISP Notifications' Documentation: 
> https://github.com/openwisp/openwisp-notifications#openwisp-notifications
> 
> Stay tuned for more features coming to OpenWISP Notifications.
> 
> Best, 
> 
> Gagan Deep
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/openwisp/22e9db85-fe79-4495-a426-3214c590a801n%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200903063021.GE27812%40obelix.okraits.de.

Re: [openwisp] "database is locked" with the django development server

[Oliver Kraitschy]

On Thu, Aug 20, 2020 at 12:11:12AM -0700, pni...@gmail.com wrote:
> "access the database with any other tool"  MM... i think i have opened 
> database with PyCharm sometime, but it have testes in four different 
> installations, two of them remotes which i dont have opened.

Well, I also had this issue in the past and I think it was either when I
had the development server running and was accessing the database with
sqlitebrowser at the same time or when I was interacting with the app
through several browser tabs at the same time.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200820071520.GB27812%40obelix.okraits.de.

Re: [openwisp] "database is locked" with the django development server

[Oliver Kraitschy]

On Wed, Aug 19, 2020 at 11:56:22PM -0700, pni...@gmail.com wrote:
> Yes, I googled, but there are no many processes, only test server.
> It always fails, even when kill and reload test server, It doesn't matter 
> what I try to delete.
> Tested on windows and ubuntu.

Do you access the database with any other tool (sqlitebrowser for
example)? Does the server process have write access to the directory where
the database file is?

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200820070120.GA27812%40obelix.okraits.de.

[openwisp] Re: Proposal: automating setup and upgrade of development environment

[Oliver Kraitschy]

Additionally, an ansible playbook is harder to read and to maintain than a 
shellscript. It's also harder to implement a certain logic.

Am Freitag, 22. Mai 2020 00:06:30 UTC+2 schrieb Oliver Kraitschy:
>
> Am Montag, 18. Mai 2020 20:44:50 UTC+2 schrieb Federico Capoano:
>>
>> Hi everyone,
>>
>> so just to wrap this up, these are the points I got from this discussion:
>>
>> - there's some consensus on using ansible to set up the development 
>> environment
>>
>>  
> I doubt that ansible is the right tool. It's mostly for administration and 
> configuration management. But we want to set up and manage a local 
> development environment. Most people will run the tool either locally on 
> their machine or in a virtual machine.I think there are faster tools for 
> that job. I would prefer a shellscript or a makefile in combination with a 
> shellscript. Idempotence can be easily achieved through the logic in the 
> shellscript.
>
> Just my two cents :-)
>
> Greetings,
> Oliver
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/f79a4200-d750-4fb9-b393-a8b767d11857%40googlegroups.com.

[openwisp] Re: Proposal: automating setup and upgrade of development environment

[Oliver Kraitschy]

Am Montag, 18. Mai 2020 20:44:50 UTC+2 schrieb Federico Capoano:
>
> Hi everyone,
>
> so just to wrap this up, these are the points I got from this discussion:
>
> - there's some consensus on using ansible to set up the development 
> environment
>
>  
I doubt that ansible is the right tool. It's mostly for administration and 
configuration management. But we want to set up and manage a local 
development environment. Most people will run the tool either locally on 
their machine or in a virtual machine.I think there are faster tools for 
that job. I would prefer a shellscript or a makefile in combination with a 
shellscript. Idempotence can be easily achieved through the logic in the 
shellscript.

Just my two cents :-)

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/a996412c-080a-4ec5-b1b6-b6df9cc99489%40googlegroups.com.

Re: [openwisp] Proposal: automating setup and upgrade of development environment

[Oliver Kraitschy]

On Wed, Apr 15, 2020 at 09:20:23AM -0500, Federico Capoano wrote:
> 
> You've been focused on the controller functionality.
> 
> The other modules bring other set of dependencies (radius,
> openwisp-monitoring).

That's true. There are some modules we don't have in our environment.
> 
> It would be really great to have a procedure that installs everything (with
> flags to disable what is not needed) and a firmware image as well which has
> everything (so one can also try the complete feature set on OpenWRT, being
> a physical device or a VM).
> It will take a while to get there but we can start gradually.

That would be really handy. I would vote for an image for virtualbox to be
independent of a physical device and to be able to cover the whole feature
set. If somebody has a physical device, he can install openwisp-config on
it anyway (if it's OpenWrt based of course).

> The feature set of OpenWISP is quite big and the problem is that most users
> are not aware of it. Automating the development environment could also push
> us and new contributors to document everything.

The reproducibility will be better too because there won't be such a big
diversity in dev environments anymore, hopefully.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200416054129.GA32514%40okWS.

Re: [openwisp] Proposal: automating setup and upgrade of development environment

[Oliver Kraitschy]

On Tue, Apr 14, 2020 at 09:33:48AM -0500, Federico Capoano wrote:

> The only thing not convincing to me was Pipfile, my experience with it was
> not great (I didn't feel it simplified my work) and I did not adopt it in
> my everyday workflow.

We chose pipenv because it sounded like the new standard way of managing
dependencies and virtual environment. I guess that's good marketing by
Kennetz Reitz :-)
In reality, it has its flaws. The dependency resolution is sometimes
fragile and it downloads a lot of stuff although it could look it up on
PyPi.
I don't know if we would choose pipenv again for the next project. Maybe
we would just work with requirements files, pip and venv/virtualenv/etc -
all the included tools.

> Regarding the system dependencies to run all the modules, do you manage
> those by hand or have you automated those as well?

For the development machines, we didn't automate the installation of those
packages. It's mainly the dependencies of openwisp-controller which need
to be installed manually once.

I'm not sure if we should put such a dev environment into openwisp-utils.
It could also be handled as a separate repository so that openwisp-utils
doesn't come with stuff some people don't want. And we could maintain the
environment independently.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200415053843.GA19303%40okWS.

Re: [openwisp] Proposal: automating setup and upgrade of development environment

[Oliver Kraitschy]

On Mon, Apr 06, 2020 at 10:56:09AM -0500, Federico Capoano wrote:
> I think it's time to invest in the automation of the initial setup of the
> development environment.
> 
> Here's what I do.

Hi Federico,

this is a good idea. To continue the brainstorming, I'll describe what we
use here.

Our OWM (OpenWISP Manager) consists of the following pieces:

- a file 'modules':
   contains a list of the names of all OpenWISP repositories and, for
   each repository, the following shell variables
- URL of our fork of the repository
- URL of the upstream repository, for pull requests
- branch to use, e.g. master
- sha of the commit to use

- a Pipfile which installs local copies of the repositories in the modules
  file, plus development packages and any additional packages

- a directory 'django' which contains:
- manage.py
- a directory 'openwisp2' with the files settings.py, urls.py, wsgi.py
  and __init__.py

- a makefile with the following targets (commands):
- prepare: create a build directory, clone all repositories specified
  in the modules file into build/sources - using the given URL, branch
  and commit; copy Pipfile, manage.py and the directory 'openwisp2'
  into build/
- build: with pipenv, create a virtual environment in the build/
  directory, install the packages from the Pipfile and thus all deps;
  with manage.py, do makemigrations, migrate and createsuperuser
- run: with manage.py, launch runserver using the given settings.py
  and urls.py
- clean: remove the virtual environment, delete the build directory

- a directory 'scripts' with scripts which do the work:
- create directories, copy the files
- clone the repositories and add remotes "origin" and "pullrequest"
- create and install the virtual environment, create and fill the
  database
- run the application
- remove virtual environment and build directory

To be able to easily handle customizations and pending pull requests, we
have another directory 'patches' with subdirectories for the various
OpenWISP repositories. It contains patches which get applied by
"make prepare", after the repositories have been cloned.

I'm looking forward to hear your thoughts about our dev environment.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200414110611.GA3434%40okWS.

Re: [openwisp] Push protocol in place of Pull configuration

[Oliver Kraitschy]

Hi Amit,

it's in the admin index page - see the attached screenshot. You'll need
openwisp-controller >= 0.4.0.

Greetings,
Oliver

On Fri, Mar 20, 2020 at 02:31:58AM -0700, Amit Goyal wrote:
> Hi Oliver 
> 
> Thanks for prompt reply. 
> 
> Where I can find "Network Device Credentials" in openwisp ? 
> 
> Regards
> Amit

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200320095535.GA23262%40okWS.

Re: [openwisp] Push protocol in place of Pull configuration

[Oliver Kraitschy]

Hello Amit,

openwisp-controller has a connections feature which allows to push the
configuration to a device.
Under "Network Device Credentials" you need to define credentials which are
then used to connect to the devices via SSH to push the configuration.

For the connections feature it's also necessary that a celery worker is
running for the background jobs. See 
https://github.com/openwisp/openwisp-controller#id1

Unfortunately, I don't know about any documentation for this feature.

Greetings,
Oliver

On Thu, Mar 19, 2020 at 11:39:46PM -0700, Amit Goyal wrote:
> Hi 
> 
> Presently OpenWisp device pull configuration from openwisp and update 
> conflagration on their side . 
> Does OpenWisp support push configuration where we can push changes to 
> openwisp Device . 
> 
> Please share if there any such implementation already exist in openwisp . 
> 
> 
> Regards
> Amit
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/openwisp/71d2e803-3bc7-4cff-829b-591f5e9a0e6b%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200320073740.GA1806%40okWS.

Re: [openwisp] Impact of USE_TZ = False or True

[Oliver Kraitschy]

Hello Amit,

see the explanation in the django documentation:

https://docs.djangoproject.com/en/3.0/ref/settings/#std:setting-USE_TZ
https://docs.djangoproject.com/en/3.0/ref/settings/#std:setting-TIME_ZONE
https://docs.djangoproject.com/en/3.0/ref/settings/#time-zone

Greetings,
Oliver

On Thu, Mar 19, 2020 at 01:20:07AM -0700, Amit Goyal wrote:
> Hi 
> 
> There is variable USE_TZ = False in setting.py. What is impact of this if 
> set to False or True. 
> I tried both value but could not see any differnce in openwisp .
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/openwisp/18c4e5d9-a299-41ee-990e-29b73dae3e54%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200319082657.GA20110%40okWS.

Re: [openwisp] Regarding GSOC 2020 -Participant at OpenWISP

[Oliver Kraitschy]

Welcome to the list,

please start by reading the documentation: http://openwisp.io/docs/

Especially:

http://openwisp.io/docs/developer/contributing.html
http://openwisp.io/docs/developer/google-summer-of-code.html

Greetings,
Oliver

Am 13.03.20 um 20:46 schrieb Devang Sharma:

Hello Team,

I am Devang Sharma, a Senior Year Computer Science Engineering UG from 
the GGSIP University.


I am a Full Stack Developer and Data Scientist with 2 Years of hands-on 
experience in Analysis, Development and Implementation with solid 
Programming expertise in C/C++, Python, OO Methodologies with a 
demonstrated history of working in the Internet Industry.


LinkedIn: https://www.linkedin.com/in/devang25/

I am new to the community and I am interested in working on the 
*OpenWISP Notifications Module* project for GSoC 2020.


I have read through the project idea and found it very interesting. 
Please for a guide on how to get started on this.


Thanks.

Mailtrack 
 
	Sender notified by
Mailtrack 
 
14/03/20, 01:16:00 	


--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/CAPPk4W-XEPPGKEjX%2B2CEVaNdgLFFzY5tqwUF82xg2ikzoinqaA%40mail.gmail.com 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/1aadd109-316a-c299-3f7f-6c0c80847609%40okraits.de.

Re: [openwisp] using device context with static ip definition

[Oliver Kraitschy]

On Wed, Feb 05, 2020 at 05:15:43PM -0300, João Henrique Albuquerque wrote:
> 
> About the signal on device creation, I should probably do it under the DB
> I'm using, right?
> E.g, when a new entry is made to the config_device tables update the field
> with context straight to the backend of the application.

https://docs.djangoproject.com/en/3.0/ref/signals/#post-save

That signal is emitted if an instance of a model class has been saved. You
can then check if it was an instance of the Device model class and if yes,
determine the ip to use and fill the device context accordingly.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200205203901.GA7980%40idefix.

Re: [openwisp] Firmware Backups and Device SSH

[Oliver Kraitschy]

Hi Colton,

On Wed, Jan 15, 2020 at 03:15:45PM -0600, Colton Conor wrote:

> Can you reboot a device remotely?
> Can you ssh into the device remotely through the OpenSSL tunnel?

A basic implementation to use ssh to execute commands on the device has
been done, right now only to update the configuration instantly:

https://github.com/openwisp/openwisp-controller/issues/30

Further usecases like rebooting a device or executing other commands need
to be implemented.

> Can you upgrade firmware remotely?

This is a similar usecase which has to be implemented.
> 
> If openwisp is not good for this task, then what do you recommend?

I implemented firmware upgrades through openwisp-config with the help of a
hook script:

https://github.com/openwisp/openwisp-config/issues/83

This is what we are using right now.

Greetings,

Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200116075014.GA19622%40okWS.

[openwisp] Feature request: display license(s) in the server webinterface

[Oliver Kraitschy]

Hello everybody,

I would like to add a page to the OpenWISP server webinterface where the
license(s) of the components of the OpenWISP server are displayed. I need
this to due to license compliance.

What do you think - is this a feature for the upstream project? I guess it
wouldn't hurt.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20200110120433.GA4752%40okWS.

Re: [openwisp] HELP! - openwisp full install -

[Oliver Kraitschy]

Hi,

typing "openwisp documentation" into Google leads me to

http://openwisp.io/docs/index.html

What is missing in the Ansible usage tutorial?

Greetings,
Oliver

Am 10.12.19 um 19:05 schrieb badr abhir:
Hi everyone , can someone please help me and send me a good&full 
documentation on how to install openwisp ,
PS: i followed the steps given on 
https://github.com/openwisp/ansible-openwisp2#usage-tutorial , its seems 
something is missing..

Thanks


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/fce52cb3-c22e-0b6a-905a-18887da7b7c4%40okraits.de.

Re: [openwisp] Re: Google Code-In 2019

[Oliver Kraitschy]

On Fri, Nov 08, 2019 at 03:13:51AM -0800, Ajay Tripathi wrote:

> In order to let Natural selection run it's course, do you think it's a good 
> idea that we should have more tasks related to our codebase than tasks like 
> "Install Linux", "Learn Django". I mean, I see the importance of some 
> instances of simple tasks but if we focus on codebase related tasks I think 
> it'll be more inviting for students we are targeting for -- students who 
> are interested in coding and can be future mentors.

Very good idea, Ajay. I second this.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20191108125035.GA22661%40okWS.

Re: [openwisp] Google Code-In 2019

[Oliver Kraitschy]

Am 25.10.19 um 00:36 schrieb Federico Capoano:

On Thu, Oct 24, 2019 at 2:57 PM Oliver Kraitschy 
>

<mailto:oli...@okraits.de>> wrote:
I agree with your points. But why not rather focus on good students
instead of trying to train many students?

I think as an organization we should be fair, I'm not sure we can decide 
to prioritize some students over others, it doesn't something that would 
make all the students happy.

Natural selection will do its course anyway.


Well, I guess we mean the same thing :-)

Sure I understand that, your contribution was very helpful anyway, and I 
thank you very much for that.


Thank you very much, you're very kind :-)

Greetings,
Oliver

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/ff3b2ee4-9e2b-4579-1ef5-ef28b4169a75%40okraits.de.

Re: [openwisp] Additional possibilities to control the configuration update process

[Oliver Kraitschy]

Am 18.10.19 um 18:30 schrieb Federico Capoano:


Nevertheless I'd like to have some more control over the update process:

- defining the order in which those templates are applied (for
example to first upload a file to the device and then use it in the
configuration)

By dragging templates up or down you can define the order in which they 
are merged to generate the final configuration.


Do you mean the order to apply it on the device?


Am I correct that this does basically define the priority of the templates?
Yes, I rather mean the order in which to apply the templates on the 
device. For example, if one template contains a requirement for another 
template, then the order would make sure that the first template is 
applied before the second template gets rolled out.



- have some logic to define a set of devices the templates are
applied to:
   - only apply a template to a specific device model (hardware)
   - only apply a template to devices who run a specific firmware
version (field operating system)
   - only apply a template to devices which have a serial number
within a certain range
   - only apply a template to devices which are within a certain ip
range
   - only apply a template to devices which fulfill the opposite of
a condition

I'd be happy to hear your thoughts and opinions on this.


At the moment I think the best thing is to implement this with django 
signals.
You could tag templates with something like "firmware2.1" or 
"ip-192.168.255.255", then connect a signal to the post_save of the 
Device model, you check the information you're interested in, for 
example, ip range, and then you look for templates tagged with that 
range and you assign them to the Device if necessary.


This kind of implementation does not need to change the core of OpenWISP 
and if we find out that more people need this and in the future we may 
design something that is already included.


What do you think?


That sounds like a way to go. I'll have a look at that approach when I 
have the time. Right now this topic doesn't have a high priority but I 
wanted to discuss it early enough. Thank you :-)


Greetings,
Oliver

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/e03fd650-e7dd-95ff-82e1-925070c22636%40okraits.de.

Re: [openwisp] Google Code-In 2019

[Oliver Kraitschy]

Hi Federico,

I agree with your points. But why not rather focus on good students 
instead of trying to train many students?


I can't participate as a mentor, though. I was not happy with the effort 
I could come up with (due to time constraints) the last time. So I'd 
rather not participate as a mentor at all than participate with little 
impact.


I'm happy if I can contribute code as part of my work and provide 
assistance in the chat and on the mailing list. But in my free time, I 
don't really have time currently to do productive open source stuff 
because of family life.


I hope you understand that.

Greetings,
Oliver

Am 20.10.19 um 18:43 schrieb Federico Capoano:

Hi everyone,

we are applying again as a mentoring organization for the Google Code-In 
2019.


This year I want to propose that our main goals should be:

- train as many students as we can, with the goal that they may become 
mentors in the future

- keep improving OpenWISP and fixing bugs
- improve the work done during GSoC by our GSoC students
- improve our documentation further (although in my experience it's 
pretty hard for new students to write good docs)


What do you think about these? Is there anything you would add or remove?

I want to put particular importance on the first point, because one of 
the main complaints given by our students in the past editions was the 
number of available mentors. If we can increase the amount of competent 
mentors, we will be able to train more students and multiply our impact 
on Open Source.


If you're interested in participating as a mentor, please fill this form:
https://docs.google.com/forms/d/e/1FAIpQLSczt_VDztWZ7ZYnuoZoNpdIjWXiTH2iVFShLzeZs1Vi0DmGcg/viewform 



Best
Federico

--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/CAERYH6Wd4mo%2BSJe8aRD5wX%3DArY7hdLq53v6neHAeC1Kc8Fw1zA%40mail.gmail.com 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/50c26238-2b3b-a4ba-184a-bb00e6e78f66%40okraits.de.

[openwisp] Additional possibilities to control the configuration update process

[Oliver Kraitschy]

Hello everyone,

I'd like to propose and discuss additional possibilities to further control 
the configuration update process with OpenWISP.

Right now the configuration for a device can be defined (AFAIK):

- directly in the device config
- in templates which are enabled in the device config
- in templates which contain a tag included in the client config on the 
device
- in templates enabled by default

Nevertheless I'd like to have some more control over the update process:

- defining the order in which those templates are applied (for example to 
first upload a file to the device and then use it in the configuration)
- have some logic to define a set of devices the templates are applied to:
  - only apply a template to a specific device model (hardware)
  - only apply a template to devices who run a specific firmware version 
(field operating system)
  - only apply a template to devices which have a serial number within a 
certain range
  - only apply a template to devices which are within a certain ip range
  - only apply a template to devices which fulfill the opposite of a 
condition

I'd be happy to hear your thoughts and opinions on this.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/3db32a82-a067-4ad8-9e87-08a1c32bdee7%40googlegroups.com.

Re: [openwisp] Create organisation with fixed seceret key during start of openwisp

[Oliver Kraitschy]

Hello Amit,

you can create an organisation with a concrete shared secret with the 
common django methods for providing initial data:


https://docs.djangoproject.com/en/2.2/howto/initial-data/

Greetings,
Oliver

Am 03.10.19 um 07:12 schrieb Amit Goyal:

Hi

We want to create organisation with fixed secret key during openwisp 
start up as we can create superuser during startup .

Is it possible to do ? Please let me know details .

Thanks
Amit

--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/feb00a8c-03db-4784-a951-e43d81cd0150%40googlegroups.com 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/732f55bc-ecb1-0d62-d35a-a3bd612a4615%40okraits.de.

Re: [openwisp] openwisp with HTTPS

[Oliver Kraitschy]

On Mon, Aug 26, 2019 at 05:06:35AM -0700, Amit Goyal wrote:
> Hi
> 
> How to run openwisp with HTTPS security ? 
> Please share details if any .
> 
> Amit

Hello Amit,

OpenWISP is based on the Django web framework which means that you can use
the common setups used to run Django applications.

For example, I use Gunicorn as the application http server and nginx as
the reverse proxy with SSL enabled..

Greetings,

Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20190826134121.ojyuqgemtpbr33x3%40idefix.

Re: [openwisp] Problem during auto-registration

[Oliver Kraitschy]

On Sun, Aug 11, 2019 at 05:13:16PM -0700, matteo fedeli wrote:
> HTTP/1.1 400 Bad Request
> Server: nginx/1.14.0 (Ubuntu)
> Date: Wed, 07 Aug 2019 18:25:10 GMT
> Content-Type: text/plain
> Content-Length: 164
> Connection: keep-alive
> X-Openwisp-Controller: true
> X-Frame-Options: SAMEORIGIN
> 
> {
> "mac_address": [
> "Device with this Mac address already exists."
> ]
> }
> 
> Why? it isn't true! My domain is openwisp.planet.bn it's a reserved word?

Hello Matteo,

the error message is about the mac address, not about the hostname. Please
check if your device / the mac address of your device doesn't already
exist on the OpenWISP server.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20190812045941.mjil57ha76ubkoj5%40okWS.

Re: [openwisp] Problem during auto-registration

[Oliver Kraitschy]

On Wed, Aug 07, 2019 at 11:58:32AM -0700, matteo fedeli wrote:
> Hi, I trying to connect my openwrt AP (18.06.4) to my production server but 
> i get registration failed:
> 
> logread -f | grep wisp
> > Wed Aug  7 20:51:51 2019 daemon.info openwisp: OpenWISP config agent 
> > started
> > Wed Aug  7 20:51:51 2019 daemon.info openwisp: Registering device...
> > Wed Aug  7 20:51:52 2019 daemon.err openwisp: Registration failed! }

Hi Matteo,

I recently had the problem that registration failed because some
registration parameter was not valid - in my case it was a hostname with a
'_' in it.

Check /tmp/openwisp/registration_parameters for the registration
parameters.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20190808050846.rm354ihxdzfhwwpy%40okWS.

Re: [openwisp] LDAP integration with Openwisp

[Oliver Kraitschy]

On Thu, Jul 25, 2019 at 11:56:06PM -0700, Amit Goyal wrote:
 
> Is LDAP integration possible with OpenWisp ? Can you share some details for
> this ? 
> 
> Regards
> Amit 

Hello Amit,

you can use django-auth-ldap to add LDAP support to Django:

https://pypi.org/project/django-auth-ldap/

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/20190726194818.aspdyw2pa57zopq6%40idefix.

[openwisp] Re: Need Help to Start Contributing for GSOC 2019

[Oliver Kraitschy]

Hi there,

the documentation should get you started:

http://openwisp.io/docs/

Greetings,
Oliver

Am Donnerstag, 10. Januar 2019 11:24:21 UTC+1 schrieb varsha kukreja:
>
> I would like to contribute to the open source community ..I have majorly 
> worked on backend on 2 college sponsored projects and working currently on 
> a project by Government Organization. I have fair knowledge in Javascript, 
> NodeJs, Typescript, Spring Boot, Laravel , Docker and apache thrift. It 
> woukd be great if could if someone could help me get started
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[openwisp] Re: Google Code-in 2018 wrap up

[Oliver Kraitschy]

Hello everybody,

congratulations to both students and mentors for their effort to learning 
new things and helping others to learn new things and of course to bring 
the OpenWISP project forward!

I hope to see a lot of you again on the mailing list and in the chat!

Greetings,
Oliver

Am Mittwoch, 12. Dezember 2018 13:07:49 UTC+1 schrieb Federico Capoano:
>
> Dear friends,
>
> the Google Code-In 2018 contest is almost over (only about 5 hours 
> remaining), and we got excellent results, both in qualitative terms and in 
> quantitative terms.
>
> I want to thank all the students who participated with us and put a lot of 
> effort, learned a lot and have also learned to be patient with waiting for 
> their mentors to find time to review their work and help.
>
> A special thanks goes to all our mentors that made this possible, students 
> you should be really thankful to them!
>
> *I want to announce that we want to invite some of our best students to 
> become part of our organization on github* so they can keep contributing 
> and be recognized for the work they do.
> Since a most of the students that contribute during the Google Programs do 
> not continue contributing afterwards, I do not want to keep adding 
> "dormient" (eg: inactive) members to our organization, so I encourage the 
> students who really care about the project to keep participating in their 
> free time, as the rest of us here.
> I think open source is a passion, caring to share your work for the 
> benefit of humanity, not only something you do if you are rewarded with 
> prizes (as in GCI) or money (as in GSoC).
> Those who will keep contributing will become part of our organization and 
> will gradually receive more permissions to manage things on their own if 
> they want to do so.
> We mentors will keep helping students, which after GCI won't be students 
> anymore but contributors and peers, although with a more relaxed pace.
>
> In the next weeks we will slow down a bit in order to rest and recover, 
> this GCI was exhausting, we had about *950 students* who completed at 
> least 1 task with *a total of over 1900 tasks completed*.
> We are *just 9 mentors*, what we achieved is really *incredible*, we 
> would never have achieved this without *Alessia Ventani* and *Ajay 
> Tripathi*, just the two of them mentored over 1500 tasks!
> *So a super special mega thanks must go to them!*
>
> And of course *thanks to Google for facilitating this*.
>
> Keep up the good work friends!
> 2 more years at this rhythm and I believe the OpenWISP community will have 
> achieved most of the goals of the project 
> !
>
> Best regards
> Federico Capoano
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[openwisp] Re: GSoC 2019

[Oliver Kraitschy]

Hi Jude,

welcome to the OpenWISP community!

Please start by reading the documentation:

http://openwisp.io/docs/

There you will find information on how to get started and how to contribute.

Greetings,
Oliver

Am Samstag, 8. Dezember 2018 23:24:14 UTC+1 schrieb temj...@gmail.com:
>
> Hi all,
>
>
> I am Jude Tem Efume, I am very interested in contributing to your projects 
> as a developer.
>
> I would also like to be part of your community of developers, and 
> contribute as a student/developer in Google summer of Code 2019.
>
> Please I would like to know the steps to follow to be successful at this.
>
>
>
> Best regards
> Jude Tem
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[openwisp] Re: GCI Task : Learn how to install Freeradius

[Oliver Kraitschy]

Hi,

I didn't find the task so I don't know what the task description is.

But freeradius is available as a package from the debian repositories:

https://packages.debian.org/search?keywords=freeradius

I hope that helps.

Greetings,
Oliver

Am Donnerstag, 29. November 2018 00:45:42 UTC+1 schrieb mrfzy_:
>
> Hi , I want to ask some question
>
> Where i can get the repository of freeradius 3.0? i thought it was on the 
> reguler package in debian repo where i can get it?
>
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Growth: organizational changes needed

[Oliver Kraitschy]

Hi Marco,

that's great news! Thank you for the support!

Greetings,
Oliver

Am Montag, 19. November 2018 23:27:04 UTC+1 schrieb marco.cappellacci:
>
> Hi community!
>
> I totally agree with you Federico.
> I'm glad to inform you about that:
> The University of Urbino, the organization I work for, will provide a 
> virtual machine to install discourse.
> I'm working on It!
>
>
>
> Il giorno dom 18 nov 2018 alle ore 14:40 Federico Capoano <
> federico...@gmail.com > ha scritto:
>
>> I'll try to be brief because I don't want to use too much of your time.
>>
>> The community is growing and some of the ways which were working up to 
>> now are not working so well anymore.
>>
>> Here's how I propose to address the issues, let me know what you think.
>>
>> *Git repositories: branch protection and write access*
>>
>> I just implemented the following change: most of the important 
>> repositories of the OpenWISP 2 modules and documentation have their master 
>> branch protected to avoid accidental damage.
>>
>> I added a core development team on github which has write access to most 
>> of these repositories but won't be allowed to push to master without going 
>> through a pull request review.
>>
>> The core development team on github will be "liquid", we can add new 
>> active contributors and remove contributors who are not active anymore 
>> often.
>>
>> *Discussions*
>>
>> I'm not sure that as we grow this mailing list is the best tool to 
>> communicate. Sure it's comfortable for me but I'm not sure for new 
>> contributors if it is so for the following reasons:
>>
>> - many people are receiving all emails and as the volume of discussion 
>> increases many will most probably stop reading or unsubscribe
>> - some new subscribers are not used to mailing list and are probably not 
>> aware of the fact that they should limit their communications to the bare 
>> minimum
>> - I believe some users/contrbutors are mainly interested in one specific 
>> area of OpenWISP and would probably prefer to receive updates of new 
>> discussions that are only relevant to that area
>>
>> That's why I'm starting to consider the option of using discourse 
>> , which seems to be working well in the 
>> OpenWRT community (and other communities as well).
>>
>> This change would likely require time before we implement it correctly. A 
>> considerable amount of work would be needed to do it, not just because we'd 
>> have to install and maintain a discourse instance, but also because this 
>> change should be reflected in the website / documentation, users would have 
>> to be imported (not sure how that plays out with privacy regulations), the 
>> structure / categories and rules of the eventual new discourse instance 
>> should be created before completing such a move. 
>>
>> Best
>> Federico
>>
>> -- 
>> 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.
>>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Re: Growth: organizational changes needed

[Oliver Kraitschy]

Am Sonntag, 18. November 2018 22:21:20 UTC+1 schrieb Federico Capoano:

At the moment I think any core dev can review but only admins or specific 
> people can merge.
> For example, you have permission to merge in the openwisp-config repo.
>
> As some contributors specialize in some repositories I want to distribute 
> the responsibilities more and more.
> I just want to be sure everyone that gets to that point understands how 
> important it is to properly review, test and improve patches because I know 
> from experience that merging patches in a lighthearted way can lead to 
> unexpected problems and bugs in very bad moments, eg: usually while we are 
> traveling, busy with personal issues or worse on vacation..
>

I can only fully support this, it totally makes sense. 

 One thing I forgot to add, discourse allow replying via email, so for 
> those who like mailing lists it should change much.
>

You mean it shouldn't change much? 

I would have liked to buy it but the price is not cheap (entry level is 100 
> USD / month) so I think for that price it's better to host it at the moment.
>

I can understand that. Do you have the possibility to host it somewhere or 
would you need to rent a server for it?

Greetings
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[openwisp] Re: Growth: organizational changes needed

[Oliver Kraitschy]

Hi Federico,

On Sun, Nov 18, 2018 at 05:40:44AM -0800, Federico Capoano wrote:
>
> I just implemented the following change: most of the important 
repositories of
> the OpenWISP 2 modules and documentation have their master branch 
protected to
> avoid accidental damage.
>
> I added a core development team on github which has write access to most 
of
> these repositories but won't be allowed to push to master without going 
through
> a pull request review.

Does every PR have to be reviewed by you or can members of the core
development team review each other's PRs? Just thinking about the load on
you :-)

> The core development team on github will be "liquid", we can add new 
active
> contributors and remove contributors who are not active anymore often.

Thank you for adding me - I'm feeling honored once more :-)

> [Disadvantages/shortcomings of the mailing list]

I agree with all the things you said.

> That's why I'm starting to consider the option of using discourse, which 
seems
> to be working well in the OpenWRT community (and other communities as 
well).

I have no experience with Discourse but it seems to be the best forum
software out there. I did some investigation for such a software some time
ago and Discourse seemed to be the best choice. Unfortunately it's only
available as a docker image.

> This change would likely require time before we implement it correctly. A
> considerable amount of work would be needed to do it, not just because 
we'd
> have to install and maintain a discourse instance, but also because this 
change
> should be reflected in the website / documentation, users would have to be
> imported (not sure how that plays out with privacy regulations), the 
structure
> / categories and rules of the eventual new discourse instance should be 
created
> before completing such a move.

Would you host the instance somewhere yourself or let somebody else do the
hosting? I'm just thinking about the obligations which come with hosting
such a platform.

An option would be to not migrate the user accounts but to ask users to
register at the new forum if interested - that would also clean up the
userbase.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Re: openwisp-config feature Discussion: increase check interval after initial configuration

[Oliver Kraitschy]

Hi Federico,

that's my impression as well.

I will have a look as soon as I have the time.

Greetings,
Oliver

On Fri, Oct 19, 2018 at 03:38:13PM +0200, Federico Capoano wrote:
> I guess the reload_service function in the init.d script is not working as
> expected :(
> 
> 
> Il ven 19 ott 2018, 13:21 Oliver Kraitschy  ha scritto:
> 
> On Thu, Oct 18, 2018 at 09:31:35AM -0700, Federico Capoano wrote:
> 
> > the easiest way you can do what you want is to have a template in
> OpenWISP
> > which modifies the interval of the agent with the following template
> (flagged
> > as default):
> >
> > {
> >     "openwisp": [
> >         {
> >             "config_name": "controller",
> >             "config_value": "http",
> >             "interval": 43200
> >         }
> >     ]
> > }
> 
> Hi Federico,
> 
> did you test this? I just tried this but it doesn't work as expected.
> 
> When a new device is registered at the controller, the template is applied
> and the interval in the openwisp config is set to the value defined in the
> template.
> But the new interval is not used until I manually restart
> openwisp-config.
> 
> Greetings,
> Oliver
> 
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Re: openwisp-config feature Discussion: increase check interval after initial configuration

[Oliver Kraitschy]

On Thu, Oct 18, 2018 at 09:31:35AM -0700, Federico Capoano wrote:

> the easiest way you can do what you want is to have a template in OpenWISP
> which modifies the interval of the agent with the following template (flagged
> as default):
> 
> {
>     "openwisp": [
>         {
>             "config_name": "controller",
>             "config_value": "http",
>             "interval": 43200
>         }
>     ]
> }

Hi Federico,

did you test this? I just tried this but it doesn't work as expected.

When a new device is registered at the controller, the template is applied
and the interval in the openwisp config is set to the value defined in the
template.
But the new interval is not used until I manually restart
openwisp-config.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Re: openwisp-config feature Discussion: increase check interval after initial configuration

[Oliver Kraitschy]

Hi Federico,

yes, this looks like an easy and quick solution. I feel stupid because I
haven't thought of that.

I will try it out.

Thank you very much!

Greetings,
Oliver

On Thu, Oct 18, 2018 at 09:31:35AM -0700, Federico Capoano wrote:
> Hi Oliver,
> 
> the easiest way you can do what you want is to have a template in OpenWISP
> which modifies the interval of the agent with the following template (flagged
> as default):
> 
> {
>     "openwisp": [
>         {
>             "config_name": "controller",
>             "config_value": "http",
>             "interval": 43200
>         }
>     ]
> }
> 
> This way, when a device is flashed, it will use the value you set in the
> firmware image, which would be 120 seconds if you haven't edited the default.
> The agent will keep on trying to register itself to the server until it
> succeeds, once it succeeds it will download the configuration from the server
> immediately and merge it with the local configuration, which means the 
> interval
> value would be changed to the value you want.
> 
> Easy, no change of code required and if you want to change the interval value
> in the future you can do it easily from the template.
> 
> I hope this helps.
> Federico

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] GCI pre-kickoff sprint!

[Oliver Kraitschy]

On Thu, Oct 18, 2018 at 05:48:09PM -0700, Federico Capoano wrote:
 
> This is an invite for everyone to take part in the Google Code-In Sprint we
> will be holding from Friday (late-afternoon and evening) 19 of October until
> Sunday 21 of October (til the evening).

Hi Federico,

unfortunately I probably won't be able to help this weekend.

Tomorrow is our annual running/mountainbike/inliner event where I'm doing
the IT (I guess I mentioned it some time in the chat). We already have
almost 800 participants and about 150 more will be registering today and
tomorrow on site :-) So I have a decent responsibility that everything
will go well.

Maybe I will appear in the chat in the evenings so I can catch up with how
the sprint is going.

I wish everybody participating a lot of fun and a lot of progress! :-)

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Re: openwisp-config feature Discussion: increase check interval after initial configuration

[Oliver Kraitschy]

On Mon, Oct 15, 2018 at 07:45:58AM -0700, Edoardo Putti wrote:
> 
> As long as it is not representable as NetJSON you will not be able to add this
> feature easily
> without modifying the openwisp-config daemon. Maybe you can get away with a
> post
> configuration update hook but I don't have experience in that.

Yes, that is logical. There may be even more benefits of having NetJSON support
for openwisp-config.
> 
> To really make it simple (1h top) you just have to package your configuration
> for openwisp
> and distribute that as a feed. Once you install the daemon also install your
> package
> and you are done, you have both the agent and the configuration for the agent.
> 
> Also when the system boot the agent will always check for updates so 
> everything
> is just
> a reboot away.

That is already happening as we have our own firmware images with our
configuration.

It still would be nice to have the possibility to modify
the check interval dynamically, either automatically by the agent or
directed by the controller.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Re: openwisp-config feature Discussion: increase check interval after initial configuration

[Oliver Kraitschy]

On Mon, Oct 15, 2018 at 02:34:17AM -0700, Edoardo Putti wrote:

> 
> This can be achieved easily by configuring the agent on the device
> 
> Change the `interval` value in `/etc/config/openwisp`
> to 43200 and you are done

Hello Edoardo,

I would prefer that the interval of the agent is changed automatically
by some logic in the agent or in the controller.

Would you want to change the interval of the agent on hundreds or thousands
of devices by hand? ;-)

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[openwisp] openwisp-config feature Discussion: increase check interval after initial configuration

[Oliver Kraitschy]

Hi everyone,

I'd like to discuss a possible new feature.

In our usecase the devices are configured after they have been installed
at their location. After that, the configuration is rarely changed.

Thus it would make sense to increase the check interval for configuration
changes after the first/initial configuration update has been done.

An example procedure would look like this:

- The device is installed at the location
- The device is registered at its OpenWISP controller
- The device checks for configuration updates every 60 seconds
- The first configuration update is done
- The check interval is set to 43200 seconds
- The device checks for configuration updates twice a day

What do you guys think about that?

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Device id, key, name and vendor-specific device fields

[Oliver Kraitschy]

On Thu, Oct 04, 2018 at 10:42:02AM +0200, Federico Capoano wrote:
> I think default settings similar to these below would give the best result, 
> the
> hardware ID field id is disabled and not shown by default but it's required if
> enabled and that can be changed if needed:
> 
> HARDWARE_ID_ENABLED = getattr(settings,
> 'DJANGO_NETJSONCONFIG_HARDWARE_ID_ENABLED', False)
> # defaults
> HARDWARE_ID_OPTIONS = {
>     'blank': not HARDWARE_ID_ENABLED,
>     'label': _('serial number'),
>     'help_text': _('some helpful text here'),
>     'maxlength': 32
> }
> HARDWARE_ID_OPTIONS.update(getattr(settings,
> 'DJANGO_NETJSONCONFIG_HARDWARE_ID_OPTIONS', {}))
> 
> # model field then is initialized like:
> hardware_id = CharField(**HARDWARE_ID_OPTIONS)

Ok, I'm fine with that :-)

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Device id, key, name and vendor-specific device fields

[Oliver Kraitschy]

On Tue, Oct 02, 2018 at 01:45:14AM -0700, Federico Capoano wrote:

> So what about 3 new django settings:
> 
> - enable hardware_id field
> 
> So we should assume that if it's enabled it will also be required?

I wasn't thinking about that distinction. If it isn't required in any
case, it could be enabled by default which means that the setting is about
wether is is required or not, not enabled or not - the user (or
openwisp-config) is free to provide a value but he doesn't need to provide
a value.

What do you think?

> I'd start with creating issues by summarizing what we discussed here on
> github. 

Thank you for creating the issues!

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Device id, key, name and vendor-specific device fields

[Oliver Kraitschy]

On Mon, Oct 01, 2018 at 11:20:16AM +0200, Federico Capoano wrote:

> The human readable label and the help text of the field should be 
> configurable,
> by default we could use something like "Serial number", but it can be modified
> to use a different term depending on the context where it is used.
> 
> In my opinion this feature should be deactivated by by default and shown only
> when a specific setting is turned on.

So what about 3 new django settings:

- enable hardware_id field
- label text for hardware_id field
- help text for hardware_id field

>   • it should be shown and be editable in the add device page, shown right
> before or right after the name field 

How is a new device entry created manually referenced by openwisp-config?
With the generated key which must be added to the openwisp-config
configuration? Or is this behaviour supposed to be changing with the
hardware_id field? I guess not.

>   • it should be shown and (probably) readonly in change device page, shown
> right before or right after the name field

Yes, I vote for a readonly field after device creation. This elimintates
device manipulation and often the hardware_id is not modifiable anyway.

I'm fine with all of this so far and could work on this.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Device id, key, name and vendor-specific device fields

[Oliver Kraitschy]

On Sun, Sep 30, 2018 at 01:28:27PM +0200, Federico Capoano wrote:

> That is really great news, I will make sure to help you in this process.

You're already at it - thank you for your help all the time :-)

> My understanding is that in your case you would like to show the serial number
> in the UI instead of the hostname, is this understanding correct? If not could
> you explain what your specific goal is? 

Yes, the serial number should be used as the unique name for the device in
the UI and it should also be possible to search for a specific device by
serial number.

> In chat you mentioned that you needed the key to be generated from the serial
> number, right?

Yes, it would make sense and be logical because in our case the serial
number is the unique device identifier. The downside is that for devices
which are created manually with django-netjsonconfig, the key is not
generated from the mac address (or from the serial number).

> I think we should add a new field dedicated to store some sort of hardware ID.
> The reason is that other use cases have come up needing the same thing, I'm
> talking specifically about the device EUI in LoRa / IoT.

Yes, or generally speaking, some user-definable field which can be filled
by a script on the client side.

> Before focusing too much on technical details, could you explain what your 
> need
> is regarding this serial number? For example:
> 
> Our hardware has a unique serial number which we use for identification and
> internal purposes, we would like to:
> 
>   • see this serial number as prominent identification in the admin
>   • be able to search devices in the admin by their serial number
>   • have the device automatically register its serial number without the need
> of manual intervention
>   • have the key field of the device generated from this serial number because
> we consider it more reliable and secure than doing so with the mac address

Yes, all of this :-) The serial number is assigned when the device is
built and is used throughout the whole process - in provisioning, in all
communication with our customers and also internally.

And I think this is also what Aaron meant and would like to have.


Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[openwisp] Device id, key, name and vendor-specific device fields

[Oliver Kraitschy]

Hello everybody,

at our company, we are doing preparations to move over to OpenWISP.


Our devices have a unique serial number which is currently used as the
unique identifier of a device. So I'm thinking about how to integrate that
with OpenWISP.


In the OpenWISP controller, a device currently has the following fields:

- id: randomly generated upon device registration/creation
- key: generated by openwisp-config based on the shared secret and the MAC
  address of a specific interface (default eth0)
- mac_address: MAC address of the interface mentioned above
- name: hostname of the device (or MAC as fallback)

The name is also used in django-netjsonconfig as the device identifier
whenever a list of devices is displayed. Additionally, the name is
read-write which means that the hostname of the device can be changed
through django-netjsonconfig.


To integrate all of this, I'm proposing the following:

- On the controller the hostname should be a field of its own, independent
  from the name of the device, so people can set different values for the
  hostname of the device and the name of the device on the controller
- In the configuration of openwisp-config there should be an option to
  define a command or script to get the initial value for the name of the
  device on the controller (default hostname - in our case a command to
  get the serial number)
- there might be the requirement to add another unique identifier for the
  device on the controller, a department number, some address, etc (which
  can be displayed in the devices listing or used for searching devices).
  Maybe the notes field can be used for this


What do you think about this?

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Create wifi-iface without interface

[Oliver Kraitschy]

On Sat, Sep 22, 2018 at 08:48:28AM -0700, JeroenR wrote:
> Hi Guys,
> 
> Awesome project!
> 
> Why can't we create a wifi-iface without an interface?
 
Hi,

this is rather an OpenWrt question than an OpenWISP question :-)

I would argue that you need an interface because most services use an
interface, not a wifi interface :-)

The documentation on wifi interfaces

https://openwrt.org/docs/guide-user/network/wifi/basic#wifi_interfaces

states that the option network (OpenWISP uses the option ifname instead)
is required for a wifi interface. Which is what you mentioned - you need
to reference an interface for this wifi interface.

Additionally, you need an interface anyway to configure the IP address,
may it be a static address or assigned via DHCP.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: [openwisp] Re: Google Code-In 2018: ROCK ON!

[Oliver Kraitschy]

Hi Federico,

You could add a task for the migration to pipenv to the list if you think it is 
suitable.

Greetings,
Oliver

 Ursprüngliche Nachricht 
Von: Federico Capoano  
Datum:14.09.2018  15:37  (GMT+01:00) 
An: OpenWISP  
Betreff: [openwisp] Re: Google Code-In 2018: ROCK ON! 

To anyone wanting to help: please be active in the chat and help us to fill the 
spreadsheet with the task samples.

The application deadline is on monday.

Federico
-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Google Code-In 2018: ROCK ON!

[Oliver Kraitschy]

On Tue, Sep 11, 2018 at 09:31:42PM +0200, Oliver Kraitschy wrote:

> As proposed, I will try to migrate one project and then we'll see how that
> turns out.

For the record, here is the PR:

https://github.com/openwisp/openwisp-controller/pull/38

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] New website online!

[Oliver Kraitschy]

Congratulations and thank you to you both for your hard and great work!

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Google Code-In 2018: ROCK ON!

[Oliver Kraitschy]

On Tue, Sep 11, 2018 at 12:18:05PM -0700, Federico Capoano wrote:

> The requirements file is read by the setup.py (eg: check this out) so probably
> also that would have to be changed.

Sure, I will have a look at that.

> I wonder if pipenv is supported yet by requirements.io, that service is pretty
> useful to monitor which dependencies are outdated or insecure.

http://shiningpanda.com/pipenv-support.html

It seems they already support it. Those two files they mention are called
'Pipfile' and Pipfile.lock', though.

> For sure we can have a task that asks the beginners to install pipenv and 
> start
> using it (instead of virtualenv).

As proposed, I will try to migrate one project and then we'll see how that
turns out.

Greetings,
Oliver

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [openwisp] Google Code-In 2018: ROCK ON!

[Oliver Kraitschy]

On Tue, Sep 11, 2018 at 08:41:51PM +0200, Federico Capoano wrote:

> @okraits: sounds like a great time to start upgrading to pipenv! In practice
> what would the task consist in?
> Do we have to change the code of each project or what?

For each project, we basically have to replace requirements.txt with a
Pipfile and update the README accordingly. I have to check if there is
anything more to do (for example, to not break pip packaging), but those
are the main steps AFAIK.

I can come up with a PR for one project as an example, to get an
understanding of the needed effort, ok?

BTW, I didn't find it right now, but pipenv is actually the tool
recommended by python.org for virtual environments. There's also a
tutorial available:

https://packaging.python.org/tutorials/managing-dependencies/#managing-dependencies

Greetings,
Oliver

> 
> To the new comers: welcome!
> Last year we had many people joining only to mentor GCI students. It was nice
> to have some helping hands but these new mentors needed training as well and
> that added even more burdened to our already burdened contributors.
> In order to avoid adding even more burden to the stable contributors I advise
> to get involved in OpenWISP, once you understand how OpenWISP works and you
> show that you are able to contribute it will be natural for you to become
> mentor.
> The people of Google Open Source Program Office explicitly advised me to avoid
> accepting mentors who don't have experience and knowledge of the project.
> 
> Federico
> 
> 
> 
> On Tue, Sep 11, 2018 at 6:52 AM Oliver Kraitschy  wrote:
> 
> Hi Federico,
> 
> I just had an idea for for a possible task for someone already a bit
> familiar how developing with python works.
> 
> The python community is slowly moving from using virtualenv (or
> virtualenvwrapper or other derivatives) and requirements.txt files to 
> using
> pipenv and pipfiles.
> 
> pipenv is a tool written by Kenneth Reitz (author of the well known
> requests library) which manages both virtual environments and package
> dependencies:
> 
> https://pipenv.readthedocs.io/en/latest/
> 
> I think pipenv would make it easier both for beginners and intermediates 
> to
> get started with OpenWISP development. So I think we should migrate our
> projects to using pipfiles and pipenv. pipenv even creates an equivalent
> Pipfile if it encounters an existing requirements.txt file!
> 
> What do you think about it?
> 
> Greetings,
> Oliver
> 
> On Wed, Aug 29, 2018 at 10:51:41PM +0200, Federico Capoano wrote:
> > Hi everyone,
> >
> > I think the last Google Code-In was great for our community, it pushed 
> us
> to
> > improve our documentation, fix a lot of issues, add new features and
> helped us
> > to grow our community.
> > Moreover, one of the winners, Aarnav is still very actively helping us 
> to
> > improve and grow.
> >
> > Last year the main complaints we had from students was that there 
> weren't
> > enough mentors to help out, it would be wonderful if this year we could
> fix
> > this by expanding our pool of mentors!
> > The mentor who will be voted the best by students will win a trip to San
> > Francisco to meet the GCI winners at Google Headquarters in San 
> Francisco
> and
> > or Mountain View (this year we visited both offices).
> > The privileged mentor chosen by students will stay in a great hotel, eat
> great
> > food, attend to very interesting presentations given by Google employees
> about
> > interesting topics (this year they talked about Kubernetees, Open source
> > licenses, AI, self-drived cars and many more incredibly cutting-edge and
> > interesting topics).
> > This year they let us eat in the Mountain View HQ with the rest of the
> > employees, it was a really nice experience, it felt a bit like being in
> "The
> > Interns" movie EHEH.
> >
> > If you're interested in helping us out please read on, below is the
> official
> > communication from the Google crew.
> >
> > Federico
> >
> > -- Forwarded message -
> > From: 'sttaylor' via Google Summer of Code Mentors List <
> > google-summer-of-code-mentors-l...@googlegroups.com>
> > Date: Wed, Aug 29, 2018 at 9:35 PM
> > Subject: [GSoC Mentors] Google Code-in 2018 is on - org apps open Sept
> 6-17
> > To: Google Summer of Code Mentors List <
> > goo

Re: [openwisp] Google Code-In 2018: ROCK ON!

[Oliver Kraitschy]

Hi Federico,

I just had an idea for for a possible task for someone already a bit
familiar how developing with python works.

The python community is slowly moving from using virtualenv (or
virtualenvwrapper or other derivatives) and requirements.txt files to using
pipenv and pipfiles.

pipenv is a tool written by Kenneth Reitz (author of the well known
requests library) which manages both virtual environments and package
dependencies:

https://pipenv.readthedocs.io/en/latest/

I think pipenv would make it easier both for beginners and intermediates to
get started with OpenWISP development. So I think we should migrate our
projects to using pipfiles and pipenv. pipenv even creates an equivalent
Pipfile if it encounters an existing requirements.txt file!

What do you think about it?

Greetings,
Oliver

On Wed, Aug 29, 2018 at 10:51:41PM +0200, Federico Capoano wrote:
> Hi everyone,
> 
> I think the last Google Code-In was great for our community, it pushed us to
> improve our documentation, fix a lot of issues, add new features and helped us
> to grow our community.
> Moreover, one of the winners, Aarnav is still very actively helping us to
> improve and grow.
> 
> Last year the main complaints we had from students was that there weren't
> enough mentors to help out, it would be wonderful if this year we could fix
> this by expanding our pool of mentors!
> The mentor who will be voted the best by students will win a trip to San
> Francisco to meet the GCI winners at Google Headquarters in San Francisco and
> or Mountain View (this year we visited both offices).
> The privileged mentor chosen by students will stay in a great hotel, eat great
> food, attend to very interesting presentations given by Google employees about
> interesting topics (this year they talked about Kubernetees, Open source
> licenses, AI, self-drived cars and many more incredibly cutting-edge and
> interesting topics).
> This year they let us eat in the Mountain View HQ with the rest of the
> employees, it was a really nice experience, it felt a bit like being in "The
> Interns" movie EHEH.
> 
> If you're interested in helping us out please read on, below is the official
> communication from the Google crew.
> 
> Federico
> 
> -- Forwarded message -
> From: 'sttaylor' via Google Summer of Code Mentors List <
> google-summer-of-code-mentors-l...@googlegroups.com>
> Date: Wed, Aug 29, 2018 at 9:35 PM
> Subject: [GSoC Mentors] Google Code-in 2018 is on - org apps open Sept 6-17
> To: Google Summer of Code Mentors List <
> google-summer-of-code-mentors-l...@googlegroups.com>
> 
> 
> 
> Hello GSoC mentors,
> 
> We are pleased to announce Google Code-in (GCI) 2018, the 9th consecutive year
> of our contest for pre-university students ages 13-17. Please be aware GCI 
> will
> start about a month earlier this year than in previous years - the contest
> starts for students October 23rd!
> 
> The GCI timeline, FAQs, Rules and flyers have been updated on the contest 
> site.
> 
> Organizations -- If you would like to apply for the 2018 program please start
> thinking about the tasks you would like students to work on and reach out to
> your community members to ask if they would like to be mentors for the 
> program.
> Organization applications open for GCI orgs next week on Thursday, September
> 6th, and close less than 2 weeks later on Monday, September 17th. We will
> announce organizations on Tuesday, September 18th giving orgs 5 weeks to 
> create
> their tasks before the contest begins on October 23rd.
> 
> The major changes for GCI 2018 are:
> 
>   • Orgs will evaluate the 20 students completing the most tasks with their 
> org
> when deciding on finalists and winners
> 
>   • Orgs will choose 6 finalists (instead of 5)
> 
>   • We have renamed the User Interface category to Design
> 
>   • Students will have to wait until Google reviews their Parental Consent 
> form
> before they can claim their first task. This will slow things down but it
> is a requirement to be able to continue the program.
> 
>   • No tasks asking for personal information about students will be allowed
> (this includes tasks asking for students to introduce themselves with info
> like what country they are from, or photos of the students, etc.).
> 
> We are looking to continue the growth of this program and reach a record 
> number
> of teenagers this year! Read more on today’s blog post.
> 
> If you have any questions about Google Code-in please contact us at 
> gci-supp...@google.com
> 
> Best,
> 
> Stephanie and Mary
> 
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this