Codius v1.2.5 is out! View https://medium.com/codius/codiusd-1-2-0-upgrading-and-websocket-support-42f712a0cee9 for details. Having trouble? Try the post at https://ilp-ix.link/1-2-1-selftest-fix/ from @WilcoC_gitlab
Need to read docs, no time
Still at it .. So many friggin chains on that Kubernetes-firewall. Impossible to tailor a allow-rule :(
Guess the ILP-connector is obsolete?
I'm not sure exactly (re: changes to ilp connector implementations)
I think the primary hurdle is having a btp uplink at all for moneyd to connect to: https://forum.interledger.org/t/community-call-september-18th-2019/753/3
My understanding is that ilp wallets will start offering btp access to their users (as opposed to connecting moneyd to public connectors https://github.com/interledgerjs/moneyd-uplink-xrp/blob/master/connector_list.json#L3)
I think the primary hurdle is having a btp uplink at all for moneyd to connect to: https://forum.interledger.org/t/community-call-september-18th-2019/753/3
My understanding is that ilp wallets will start offering btp access to their users (as opposed to connecting moneyd to public connectors https://github.com/interledgerjs/moneyd-uplink-xrp/blob/master/connector_list.json#L3)
I'm also looking into having a variation of codius that uses web monetization so that the host only needs an ilp payment pointer (and no moneyd!)
Coil is here to stay I guess we can agree on 😁
Since secret is not known for xrptipbot-users
latest k3s includes local storage and network policy support, which means codius setup no longer needs to install local-path-provisioner and calico
https://github.com/rancher/k3s/releases/tag/v0.10.0
That said, I'm actually working on codius setup instructions for installing on an already running kubernetes cluster without all of the
https://github.com/rancher/k3s/releases/tag/v0.10.0
That said, I'm actually working on codius setup instructions for installing on an already running kubernetes cluster without all of the
sed shortcuts in the current install script. Then I hope to update the zero-to-codius script (with k3s) accordingly
@wilsonianb if you're running on packet, we helped implement the container storage interfaces (CSI). Here's the helm template https://github.com/ovrclk/disco/tree/master/layer1/csi/packet
Quick end of year update:
Codius development is still waiting on payment verification functionality being implemented by ILP wallets, which will be probably be based on this spec: https://github.com/adrianhopebailie/open-payments
In the meantime, I've also been working on:
-deploying Codius workloads as a serverless knative service paid for with web monetization https://github.com/wilsonianb/c8s/projects/1
-getting Kata containers easier to set up on k3s for Codius sandboxing kata-containers/packaging#823
Happy holidays!
Codius development is still waiting on payment verification functionality being implemented by ILP wallets, which will be probably be based on this spec: https://github.com/adrianhopebailie/open-payments
In the meantime, I've also been working on:
-deploying Codius workloads as a serverless knative service paid for with web monetization https://github.com/wilsonianb/c8s/projects/1
-getting Kata containers easier to set up on k3s for Codius sandboxing kata-containers/packaging#823
Happy holidays!
I'm assuming that by each "smart contract takes up 512MB" they are talking about storage and not RAM?
See the stats at https://codiushosts.com to see capacity of contracts to Memory
Hello gents, I had a host a while ago (Centos7, Ngnx, hyperd setup) but shut it down to setup clustering labs. I wanted to see if anything has been updated? I know last time I talked with sheetz automated deployments and windows server support was supposed to on the horizon, has this happened or is still the same setup since it’s release?
What’s up kevking btw good to still see you around and on the grind.
here's the latest thinking on what serverless codius will look like
https://wilsonianb.github.io/diagrams/c8s-deploy
https://wilsonianb.github.io/diagrams/c8s-proxy
https://wilsonianb.github.io/diagrams/c8s-deploy
https://wilsonianb.github.io/diagrams/c8s-proxy
the specifics on how the payment verification happens will depend on the https://openpayments.dev/ spec (and it being implemented by interledger wallets)
Actually.... codius hosts will likely be verifying payments with ILP STREAM receipts interledger/rfcs#568 (instead of the previously mentioned open payments API)
Here's the latest flows for deploying and accessing codius services using receipts
https://wilsonianb.github.io/diagrams/codius-deploy
https://wilsonianb.github.io/diagrams/codius-proxy
Here's the latest flows for deploying and accessing codius services using receipts
https://wilsonianb.github.io/diagrams/codius-deploy
https://wilsonianb.github.io/diagrams/codius-proxy
after installing master i try to install worker with sudo k3s agent --server https://myserver:6443 --token ${NODE_TOKEN}
they not appear with get node i see that the token file has server and not node like i see in some docu. if i check the worker with sudo k3s kubectl get node they appear as master, some idea?
they not appear with get node i see that the token file has server and not node like i see in some docu. if i check the worker with sudo k3s kubectl get node they appear as master, some idea?
curl -sfL https://get.k3s.io | K3S_URL=https://192.168.1.8:6443 K3S_TOKEN=K1056a31fc457716b4b41f372ec20c183584a4bfcea69db7ed88903b3355125351b::server:0581527deec67c7939e3d8ef501f4b96 sh -
still hop to find friends who help us, we are in africa and situation is bad enough, don't forget us
hi @michelcameroon
I just tried installing a master and worker for the first time in a while.
master:
worker (using the token in
the worker is then visible on the master:
I just tried installing a master and worker for the first time in a while.
master:
curl -sfL https://get.k3s.io | sh -worker (using the token in
/var/lib/rancher/k3s/server/node-token):curl -sfL https://get.k3s.io | K3S_URL=https://<master-ip/domain>:6443 K3S_TOKEN=XXX::server:XXX sh -the worker is then visible on the master:
kubectl get node
NAME STATUS ROLES AGE VERSION
server.suidoc.net Ready master 7m15s v1.17.4+k3s1
node.suidoc.net Ready <none> 10s v1.17.4+k3s1
Yes, development is still ongoing
Interledger STREAM receipts are nearly ready, which will allow Codius hosts to verify payment
interledgerjs/ilp-protocol-stream#133
I'm currently working on a kubernetes custom resource definition for codius deployments
https://github.com/wilsonianb/codius-crd-operator
it will be moved to the codius github org when it's ready
Interledger STREAM receipts are nearly ready, which will allow Codius hosts to verify payment
interledgerjs/ilp-protocol-stream#133
I'm currently working on a kubernetes custom resource definition for codius deployments
https://github.com/wilsonianb/codius-crd-operator
it will be moved to the codius github org when it's ready
@michelcameroon I'd recommend the #k3s channel in the rancher slack or opening a github issue for troubleshooting k3s
https://slack.rancher.io/
https://github.com/rancher/k3s/issues
https://slack.rancher.io/
https://github.com/rancher/k3s/issues
