search

openweave / happy

Happy is a tool for lightweight orchestration of simulated network topologies used for development and testing of IOT home area networks
Apache License 2.0
45 stars 22 forks source link

JSON file path is not match between Get Start and openweave-code #8

Open hevakelcj opened 5 years ago

hevakelcj commented 5 years ago

When I study happy follow page below: https://codelabs.developers.google.com/codelabs/happy-weave-getting-started/#7

I found that loading pre-defined topology with access point (AP) and service nodes command is not correct. this is what it says: $ weave-state-load ~/happy/topologies/thread_wifi_ap_service.json And the implementation should be: $ weave-state-load ~/happy/topologies/standalone/thread_wifi_ap_service.json

Corresponding, $ weave-state-load ~/happy/topologies/thread_wifi_ap_internet.json Should be: $ weave-state-load ~/happy/topologies/dynamic/thread_wifi_ap_internet.json

Vyrastas commented 5 years ago

Hi @hevakelcj -

I'm unable to replicate this. When I follow the installation and setup instructions detailed on the Get Started page of that Codelab, the commands you reference work as written. The topologies in the happy repo are all in the topologies directory. They are only split into dynamic and standalone for the sample topologies included with the openweave-core repo, but the Codelab is designed to use the ones included with happy only.