Rafał Jęczalik
Rafał Jęczalik
Hey @diclee, it's not yet fully fixed - currently it does not work for part of the users which do not have jSession doc in mongo (they logged out explicitely)....
Related https://github.com/koding/koding/issues/10333. Transport for remote.api manages user sessions, so kloud does not need to use the existing ones. Fixing 10333 fixes this problem.
> how are you/we going to support shared machines with the same label? In case of conflicts what about prefixing the label with username to resolve ambiguity? E.g. `kd ssh...
@gokmen I did not troubleshoot it thoroughly, but it looks like kloud's `team.whoami` method is not able to lookup jGroup anymore.
After a quick glance - jMachine doc exists: ``` > db.jMachines.find({"_id": ObjectId("58f4e96af3f6dc681c92c2c7")}).pretty() { "_id" : ObjectId("58f4e96af3f6dc681c92c2c7"), "status" : { "state" : "NotInitialized", "modifiedAt" : ISODate("2017-04-17T16:12:26.387Z") }, "credential" : null, "provisioners"...
Related: https://github.com/koding/koding/issues/8514 (@gokmen can we bump priority on this one?).
Hey @serut! ``` But it just fails on the klient side when the service boots it tries to establish the connection with koding and has problem to found a key...
https://github.com/koding/koding/blob/master/README.development.markdown#deploy-koding-locally
What about `kd tunnel list` (or `kd network list`) instead? ``` $ kd tunnel list apple MACHINE SERVICE PUBLIC PRIVATE apple ssh http://tunnel123.user.koding.me:52332 127.0.0.1:22 apple kite http://tunnel123.user.koding.me/klient/kite 127.0.0.1:56789 apple kites...