Hey Michele,
sounds simple, at least on surface. Waiting for the details this afternoon then I’ll let you know if I think I can do it! Sent with Notion Mail <https://www.notion.so/product/mail> On Mon, 08 Dec 2025 08:20:33 GMT Michele Sciabarra <[email protected]> wrote: Hi Federico, I am going to write a detailed issue how to perform the task by today Basically this is what we need to do. - looks in ./olaris the ~/.ops/$OPS_BRANCH/olaris for the opsroot - we should add also ~/.ops/olaris as a source to be used if there are not the previous - in the build add a step to clone apache/openservleress-task and embed them in the binarise using go support for embedded fs - at startup, if there is not a ~/.ops/olaris, extract it from the embedded tasks If you like the task I can assign to you. Michele Sciabarra | CEO m: +44 747 984 8388 e: [email protected] l: https://linkedin.com/in/msciab Nuvolaris Inc | 1209 Orange Street , Wilmington DE www.nuvolaris.io [image: linkedin icon] <https://www.linkedin.com/company/nuvolaris-io> [image: youtube icon] <http://bit.ly/nuvtube> [image: twitter icon] <https://twitter.com/NuvolarisIo> On Mon, 8 Dec 2025 at 00:56, Federico Zambelli <[email protected]> wrote: > Hi Michele, roger that. > > How do you plan about embedding Tasks into the CLI? Do you wanna embed all > of them, or just a specific subset? > > > > Sent with Notion Mail <https://www.notion.so/product/mail> > > On Sun, 07 Dec 2025 19:46:13 GMT Michele Sciabarra <[email protected]> > wrote: > > Hello all, let me explain the structure of the project: > > We have apache/openserverless that is the main repo, and links all the > subrepos with submodules. > > Essentially OpenServerless is an operator that deploys an instance of > openserverless and it is coordinated by the cli ops, that also takes care > also of building kubernetes clusters. > > All the images are referenced in ops in opsroot..json and runtimes.json. > There are many images, some are the openwhisk images, others are runtime > images custom built. > > Essentially a complete build is: > - building all the images (openwhisk, operator, runtimes, and related > components like the streamer or the devcontainer) and push them in a well > know registry > - build the cli and use it to deploy in any kubernetes, starting from the > kind cluster. > > Now, we already build all the images and deploy them in the apache docker > hub registry. So a simple release is as easy as building the cli and > ensuring all the image references apache images. > > A full source release may involve adding a script that builds all the > images in a designated registry. It is possible to do a > > git clone http://github.com/apache/openserverless --recurse-submodules > > getting all the sources, then create a tar.gz, then that .tar.gz can be > unpacked somewhere, even in an air gapped environment but with a > <registry> > available (that is mandatory) > > Then with: ./build.sh [<registry>] > > we build all the images and push then on the registry, build the cli with > the references to those images and get a cli so doing > ./ops setup mini > > will build and deploy openserverless in an air gapped environment > > In order to do that we need 2 things to do first: > > - do a simple change to the cli so it can embed its tasks. Currently it > always download them from github, but we should "freeze" some tasks inside > so it is self contained and can work without accessing the network > > - parametrize the builds so we can push them in a local registry > > So let's start fixing those things to prepare for the release. > > > Michele Sciabarra | CEO > > m: +44 747 984 8388 > e: [email protected] > l: https://linkedin.com/in/msciab > Nuvolaris Inc | 1209 Orange Street , Wilmington DE > www.nuvolaris.io [image: linkedin icon] > <https://www.linkedin.com/company/nuvolaris-io> [image: youtube icon] > <http://bit.ly/nuvtube> [image: twitter icon] > <https://twitter.com/NuvolarisIo> > >
