Closed despiegk closed 4 years ago
Threebotbuilder builds after release and merges, testing now that everything needed is in there
development_actorsimprovement
branch BuilderBaseClass
in _touch
method
with @BolaNasr Fixing prompt_toolkit
version in InstallTools
as when we install the latest version, it causes an error in the version in the toolkit and it no longer works. consequently, we can't start kosmos with @BolaNasr
Now Threebot builder sandbox works good , still have some issues in startup.toml
While testing Sandbox with @BolaNasr the sonic crashes but we couldn't reproduce this issue, we tested the Sonic installation standalone but it works well and the Threbot builder sandbox also worked well.
Can't be finished but some work can still be done ( add a feature to the threebotbuilder to create flist from this container & upload to hub).
Correct way implemented? To be discussed.
To build the sandbox, we will: 1 - create 3bot container and build everything needed 2 - ldd 3 - rsync the sandbox to a new container. if everything works there, it means the sandbox is indeed complete 4 - remove all uneed parts (for example /var) 5 - create flist of this sandbox
As it's blocking critical issue https://github.com/threefoldtech/home/issues/429, I'll also put to prio_critical. Either dependency to be solved or this one is critical. To be discussed with @zaibon .
I and @BolaNasr were able to get a successful scenario related to the following steps To build the sandbox, we will: 1 - create 3bot container and build everything needed (Done)
kosmos -p "j.builders.apps.threebot.install(reset=True)"
2 - ldd (Done)
kosmos -p 'j.tools.sandboxer.libs_sandbox(path= "/sandbox/bin") '
then we were able to start threebot server successfully
kosmos -p "j.servers.threebot.local_start_default()"
after rsync the sandbox to a new container. and make more tests we found this error
we are blocked in this error we Try 1- sandbox python , threebot and all dependencies 2- make Ldd of all binaries and still have more problems in start kosmos
I and @RafyAmgadBenjamin create new command in jsx threebot-flist
you can create flist by passing
It's your online creds
jsx threebot-flist --app_id Applicationid --secret SECRET --username USER_NAME
then it will upload both flist ( 3bot , 3bot-production)
I and @BolaNasr managed to create a toml
file that was merged with the flist we created from the container to create a new flist
and we were able to start threebot
on zero os container.
use secret in script which is used on top of coreX
@despiegk Do you want us to start the threebot
server using Corex
with a secret?
I have been investigating with @serboctor In how we can start the threebot server using Corex
we have found some issues related to Corex
and we opened these issues to be solved
https://github.com/threefoldtech/jumpscaleX_core/issues/299
https://github.com/threefoldtech/jumpscaleX_core/issues/300
https://github.com/threefoldtech/jumpscaleX_core/issues/301
we tried to work around these issues and finally, we managed to run the threebot
server using Corex
but the mention issues need to be solved.
Updated images of 3bot & 3bor_production by adding .startup.toml
now you can create your flist without merging
jsx threebot-flist --app_id Applicationid --secret SECRET --username USER_NAME
============================================================================ create a JSX script to launch Threebot
cd /sandbox/code/github/threefoldtech/jumpscaleX_threebot/scripts
python3 threebot_launcher.py -i {ID} -s {SECRET} -f {YOUR_FLIST} -p {NODE_IP}
note the branch name !!! remove older branch names, make sure only mods done for this story is in branch
story see threefoldtech/home#465