search

c0c0n3 / kitt4sme.live

On a mission to bring AI to the shop floor: https://kitt4sme.eu/
MIT License
1 stars 28 forks source link

ssh password for VM #201

Open INVENTIOai opened 1 year ago

INVENTIOai commented 1 year ago

Describe the bug

A clear and concise description of what the bug is.

What is the password to enter in ssh in prebuild vm kitt4sme.collab-cloud.eu? in: https://github.com/c0c0n3/kitt4sme.live/blob/main/docs/bootstrap.md

after build the virtual machine, say to enter in ssh with follow command: ssh martel@kitt4sme.collab-cloud.eu

but after a password is required

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error
    • create vm kitt4sme.collab-cloud.eu
    • ssh martel@kitt4sme.collab-cloud.eu
    • Password?

Expected behavior

A clear and concise description of what you expected to happen. default password in documentation

Additional context

Add any other context about the problem here.

c0c0n3 commented 1 year ago

Hi @INVENTIOai :-)

The SSH password mentioned in the bootstrap procedure is that Kitt4sme developers use to connect to the cluster where we run our own cloud instance. You, as an open call dev (I'm guessing you are), have to provision your own hardware/OS where to install the Kitt4sme cluster. So you'll have your own SSH credentials---if you use SSH to connect to your cluster.

Sadly, the bootstrap documentation is utterly confusing at the moment since it tries to cater for both Kitt4sme devs and open calls. We should really have separate documents to cater for each target audience. We'll try improving the docs, thank you again for reporting this, much appreciated.

@karikolehmainen, @kostasgrevenitis if we rewrite the docs, then we should consider this issue as well which is similar in spirit

INVENTIOai commented 1 year ago

If the procedure of setup with virtual machine is no more valid ( #202), I suppose this shall be not a issue anymore.

c0c0n3 commented 1 year ago

Hi @INVENTIOai :-)

I'm reopening this issue b/c we have to streamline our docs. We need to publish an up-to-date document that explains how open call devs can install and customise the platform...