[MEETING NOTES - 05/21/2019]
* As the first step of the project, create a new repository from the RADIX build. * Customize it such that it creates Docker Images at “mvn install”, and publishes them to DockerHub at “mvn deploy”. * To achieve this, the first component that should be containerized is OODT file manager, as it contains the least dependencies on other components of OODT. * Maven assembly plugin is used at the "mvn build" stage. Therefore, the docker image creation should happen in a later stage. i.e. “mvn install” stage. * Use the tar.gz file created from the maven assembly plugin as the source for generating the docker image for that component. * The docker image creation should not be enabled by default, and should be designed as an optional output. User should be able to configure the credentials of DockerHub, etc somewhere in the build step. Apologies for taking long to post this update. [PROGRESS UPDATE] So far, I created a new repository (https://github.com/yasithmilinda/oodt-dmb) to implement the project and add the additional build steps needed to create/publish docker images. As the implementation becomes stable, the changed/added files will be added/modified in OODT source code, and this repo could be used as an example implementation of it. If there’s anything that I've misunderstood and/or needs to be changed, do let me know. Thanks! Best, Yasith On May 14, 2019, at 11:17 AM, Tom Barber <[email protected]<mailto:[email protected]>> wrote: Yasith, to get you off to a good start in terms of open source development. Can you please file the issues you expect to work on in the short term in Jira so we can track them. If you do it it’ll ensure that you have enough knowledge rather than us doing it and them not making sense. Tom On 14 May 2019 at 15:12:43, Tom Barber ([email protected]<mailto:[email protected]>) wrote: 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FOODT%2FRADiX%2BPowered%2BBy%2BOODT&data=02%7C01%7Cyasith%40cs.odu.edu%7Cb68c0f2dc95a4254845f08d6d88039ac%7C48bf86e811a24b8a8cb368d8be2227f3%7C0%7C0%7C636934442576304882&sdata=IeQSq5o9ENrEu19VYbrLmjgdlmf2wPttWWb9pDqeoao%3D&reserved=0) 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farangodb%2Fkube-arangodb&data=02%7C01%7Cyasith%40cs.odu.edu%7Cb68c0f2dc95a4254845f08d6d88039ac%7C48bf86e811a24b8a8cb368d8be2227f3%7C0%7C0%7C636934442576304882&sdata=5N%2BhyHJMtVsshsTAGQUHZMNteipGgE%2FgKeM7NZvxHi8%3D&reserved=0) -- 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.
