osrf / cloudsim-sim Goto Github PK

Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).

Now the team_container should be able to listen to topics on the simulator, but I am having trouble talking to the simulator using my example Dockerfile:

https://github.com/scpeters/src_field_computer_test/blob/master/Dockerfile

When I open the keyboard teleop script in srcsim, it creates a publisher, but waits forever for subscribers:

[INFO] [WallTime: 1493683829.078667] [325.193000] waiting for subscribers: /ihmc_ros/valkyrie/control/arm_trajectory, /ihmc_ros/valkyrie/control/footstep_list, /ihmc_ros/valkyrie/control/head_trajectory, /ihmc_ros/valkyrie/control/neck_trajectory, /left_hand_position_controller/command, /right_hand_position_controller/command

From the simulator side, it is able to see the publisher at 192.168.2.10 on port 38915:

$ rostopic info /right_hand_position_controller/command
Type: std_msgs/Float64MultiArray

Publishers: 
 * /keyboard_teleop (http://192.168.2.10:38915/)

Subscribers: 
 * /controller_manager_ip_172_31_22_178_818_3547366887314429827 (http://192.168.2.1:46671/)

but is unable to curl that:

$ curl http://192.168.2.10:38915
curl: (7) Failed to connect to 192.168.2.10 port 38915: Connection refused

Using host network on the team_container allowed fixed this problem, though I'm not sure if host networking will be used when the traffic shaper is in place.

Thanks to @tfoote for the debugging help.

Original report (archived issue) by Tully Foote (Bitbucket: Tully Foote, GitHub: tfoote).

When I download the ssh keys for each machine it would be convenient if they were named uniquely. Right now they're all keys.zip which means I get keys (N).zip in my download folder.

Optimally they'd be able to be scoped by the roundname, and computer name. something like
round_name__payload0__keys.zip to make it clear what the zip file represents.

This would also be great for the OCU vpn tarballs. They're currently all just client_vpn.tar.gz.

This is particularly valuable as the dynamically generated keys from past rounds will want to be cleared out once the round is over.

For useability it would be great to generate a ssh_config file that embeds the keyname, known_hosts and creates a simple hostname. Such that the users will use the following.
ssh -F round_name_team/ssh_config payload1 or ssh -F roundname_payload0 payload0 and it will got through.

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

Sometimes, the console output of the running process contains errors, such as
'undefined'.

There is a workaround to change undefinedGazebo into Gazebo, but it is not a practical solution.

server/simulations.js

Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

Basically, talk to gz-simulationq and add websocket communication

Original report (archived issue) by Brian Gerkey (Bitbucket: Brian Gerkey, GitHub: gerkey).

At least things like this need to change:

We could add more hardcoded lines like that, or we could have cloudsim-widgets pass in more configuration data and then respond to that.

Original report (archived issue) by Hugo Boyer (Bitbucket: hugomatic, GitHub: hugomatic).

When granting permission to a resource "gzserver" that does not exist, the message is:

#!python
"[email protected]" has insufficient priviledges to manage "Bob" access for "gzserver"

But it would be better if it was something like: the resource does not exist.

Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).

My example field computer Docker file opens a simple http server on port 8000:

https://github.com/scpeters/src_field_computer_test/blob/master/Dockerfile

@clalancette helped me with the following iptables command that would route port 8000 from the vpn to the team_container:

$ sudo iptables -A PREROUTING -t nat -d 192.168.2.10 -p tcp --dport 8000 -j DNAT --to-destination 172.17.0.2:8000

Do we want to allow a range of ports for the teams? Also, I'm not sure if this networking setup will change when we add the traffic shaper.