I am in process of creating the wiki in the wiki repo and adding more info to all the docs and more info about the network itself. I will try to clear this up in the docs, but if there is anything else you guys can think of, please feel free to message me or reply here, Thank you.
Hi, just login via ssh to your t2.large instance. be sure you have pip installed ansible there with boto and boto3 pip installed too. Then put your hosts file in the cloned bootnode directory. your hosts file must contain only this (for bootnode): [bootnode]
then go to etc/ssh folder using mc(or other) and copy your ssh_host_key_rsa.pub file to /files folder with renaming it to admins.pub, after this run ansible-playbook -i hosts site.yml as root
Must be done).
Check for by ansible added instances during your final setup and and kill them. There can be automatic misusing security group for bootnode user, so you can also check that.
Hi, am using both AWS and Scaleway PoA Network bootnode instances. While serving same as author above mentioned problem I found that it’s very easy(and cost effective, because each time you get an error running playbook on your local machine playbook generates an instance on AWS, so you need to stop unnecessary inst) to run ansible playbook on host system directly
To setup bootnode on Scaleway you need to add security group,group policy rules and ubuntu user manually . It takes about 2 min and then we can run ansible playbook for install bn. ) To be able to instantly deploy PoA Network bootnode on Scaleway hosting(Europe) you also need to comment this:
in your site.yml file(line 29).
I am not sure what you are talking about with bootnode-access, I didn’t have to do anything like that unless it is specific to Scaleway. You need to create a user (easier to just use ubuntu or change the name top of site.yml) and that user needs sudo privileges WITHOUT password and need to manually put the SSH keys on the remote machine ubuntu user.
Create a new file in
directory and add
ubuntu ALL=(ALL) NOPASSWD:ALL
Put SSH keys in
on remote machine with the private key being local
I will have a full guide on setting up Non-AWS virtual machines on a cloud service in the github wiki soon. After the machine is setup, you do not need to run the first playbook, only the site.yml playbook after commenting out the AWS options for secret keys. etc and finishing your config & hosts file. I am not sure if this is where your problem lies, lmk.
Yes, Scaleway has it’s specific API, for full automation for SC hosting playbook need to use uri module to be able to create security groups on SC or adding users to host machine. But it isnt a problem, simply do not use security group creation options in site yml and create them manually for 2 min))) Hope this info about SC was helpful for your Non-AWS wiki. For me i prefer to run playbook directly on host machine. )