You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 15, 2022. It is now read-only.
use kd link for installing klient on connected vms #8514
Which will also install kd and make it possible to sudo kd update. We would also have only one way for installing klient which will greatly reduce maintenance cost.
We should also ensure a managed klient installed via kd link shows up on the sidebar, I've tested it on current production and it does not show up. It shows up, I was not patient enough.
In the long term we should enable the auto-updates. (/cc @leeola)
On a second though it's possible to enable autoupdate for connected vms only - #8515.
However it would be nice to have only one way to install klient.
Ideally I would move the whole functionality from bash scripts to the binary (either kd or klient - kd currently is able to install klient) and store kite keys and whole configuration in boltdb (related #8509).
so, will kd installer provide the same functionality with klient installer? I mean will it start running klient and register the machine to kontrol automatically? or do user need to do something else after installation?
Right both kd and klient installers do the same - they both register machine to kontrol and start klient. The only difference is that no managed jMachine doc is created for klient kontrol (as there's no managed machine modal for kd that does this I guess).
I'm going to rework machine registration with #8548, so taking the opportunity I could also make kontrol insert managed jMachine doc so user machine shows on the sidebar. This way separate "connected machine" or "your own machine" modal becomes obsolete. Moreover we have only one way of installing klient.
That would be perfect, we shouldn't provide two different ways to install same thing. Add your own machine modal was doing the check on kontrol to get the latest register machine that we still may need to update the machine list or we can send a notification to trigger reload for machines otherwise they won't see the machine on their sidebars until they reload.
We can still use the existing modal for that request but we will provide kd installer instead so it should work as is (I assume) because currently that modal is querying kontrol and if founds a new machine then it requests from backend to create the JMachine document.
No relationship is required only requirement is that the users list of JMachine document needs to be proper for the active user and group.
The kontrol.register method should create a jMachine managed document with newly registered KD Daemon. This way we could get rid of connected VM modal and connect external vms just by installing kd.
Activity
rjeczalik commentedon Jul 21, 2016
On a second though it's possible to enable autoupdate for connected vms only - #8515.
However it would be nice to have only one way to install klient.
Ideally I would move the whole functionality from bash scripts to the binary (either kd or klient - kd currently is able to install klient) and store kite keys and whole configuration in boltdb (related #8509).
wdyt? (/cc @cihangir @szkl)
rjeczalik commentedon Jul 27, 2016
connected vm link does not work for ubuntu
16.04, using kd link instead would have fixed thatgokmen commentedon Jul 29, 2016
so, will kd installer provide the same functionality with klient installer? I mean will it start running klient and register the machine to kontrol automatically? or do user need to do something else after installation?
rjeczalik commentedon Jul 29, 2016
Right both kd and klient installers do the same - they both register machine to kontrol and start klient. The only difference is that no managed jMachine doc is created for klient kontrol (as there's no managed machine modal for kd that does this I guess).
I'm going to rework machine registration with #8548, so taking the opportunity I could also make kontrol insert managed jMachine doc so user machine shows on the sidebar. This way separate "connected machine" or "your own machine" modal becomes obsolete. Moreover we have only one way of installing klient.
wdyt?
gokmen commentedon Jul 29, 2016
That would be perfect, we shouldn't provide two different ways to install same thing. Add your own machine modal was doing the check on kontrol to get the latest register machine that we still may need to update the machine list or we can send a notification to trigger reload for machines otherwise they won't see the machine on their sidebars until they reload.
gokmen commentedon Jul 29, 2016
Should I update the installer link to use the proposed one? Will it work as expected for now or do I need to wait for your updates on that?
rjeczalik commentedon Jul 29, 2016
Probably you'd need to wait, since right now installing kd won't make your vm appear in sidebar (I guess there's no manage doc created?).
What kind of relationships do we need in mongo in order to make a vm appear in sidebar under the Managed VMs?
gokmen commentedon Jul 29, 2016
We can still use the existing modal for that request but we will provide kd installer instead so it should work as is (I assume) because currently that modal is querying kontrol and if founds a new machine then it requests from backend to create the
JMachinedocument.No relationship is required only requirement is that the users list of
JMachinedocument needs to be proper for the active user and group.rjeczalik commentedon Jul 29, 2016
So if we just replace the link with the kd one it'll work out of the box and no need for kontrol to create jMachine docs, correct?
gokmen commentedon Jul 29, 2016
@rjeczalik yes, if that kd install scripts registers the machine we're good to go.
rjeczalik commentedon Jul 29, 2016
Let's do this 🎉
6 remaining items
leeola commentedon Sep 1, 2016
I think the "Koding Connector Service" debian package is having issues with Ubuntu 14 now, lots of error cases. Can we bump this up in priority?
Also, @rjeczalik do you think #8935 blocks this? I know you mentioned it, but what are your thoughts?
rjeczalik commentedon Nov 21, 2016
The
kontrol.registermethod should create a jMachine managed document with newly registered KD Daemon. This way we could get rid of connected VM modal and connect external vms just by installing kd./cc @gokmen
gokmen commentedon Jun 6, 2017
@rjeczalik this is the only change required
but we do have a weird error with installer;
so, I couldn't try it out for the rest of the flow.
gokmen commentedon Aug 10, 2017
@rjeczalik can you check this out again? ^^
rjeczalik commentedon Aug 10, 2017
@gokmen Do I need to do anything special to reproduce it? I've just tried the new url and it works.
gokmen commentedon Aug 10, 2017
if it's working then we can apply the patch I provided and close the issue I believe.
client: update kd install url
client: update kd install url