Just a quick recap from our call with Yasith earlier today: Had a good chat with Yasith about how RADIX works and how people build out OODT applications from RADIX ( https://cwiki.apache.org/confluence/display/OODT/RADiX+Powered+By+OODT)
General Docker build plan is as follows: * Users can deploy a standard RADIX build and optionally choose the Docker profile at build time to build docker images from it * Docker will be optional not standard * RADIX will allow users to define the image tag names for easy tagging and pushing to docker hub or similar * In the GSOC version we will focus on single deployments of each component not clustered up using ZK or similar we will stick that in the TODO list Once built the end target is Kubernetes, both MiniKube and full Kubernetes. Docker Compose may be used for interim testing and validation. A few deploy methods exist for validation: Standard deploy yams for K8S Helm Chart Or via a custom Kubernetes Operator similar to ArangoDB ( https://github.com/arangodb/kube-arangodb) -- Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891. All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email.
