Also, both of you feel free to publish Medium articles on your work or let me know if you want them to get highlighted in other Apache Blogs.
Suresh > On Aug 25, 2023, at 4:39 PM, Praneeth Kumar Chityala > <praneethchityal...@gmail.com> wrote: > > Hi Suresh, > > Sure, I am working on the last piece of integration of the orchestration > agent to consul. I will create a clear article and update it over the weekend. > > Best, > Praneeth > > On Fri, Aug 25, 2023 at 4:25 PM Suresh Marru <sma...@apache.org > <mailto:sma...@apache.org>> wrote: >> Hi Praneeth, >> >> Can you create a child page here and summarize your project - >> https://cwiki.apache.org/confluence/display/AIRAVATA/GSoC+2023 >> >> Suresh >> >>> On Aug 14, 2023, at 2:58 PM, Praneeth Kumar Chityala >>> <praneethchityal...@gmail.com <mailto:praneethchityal...@gmail.com>> wrote: >>> >>> Dear All, >>> >>> I wanted to post an update of the orchestration agent and consul components >>> of the architecture. >>> >>> Orchestration Agent: >>> After multiple considerations came to a conclusion to use nomad as the >>> container orchestration agent >>> Advantages of using nomad are: >>> It can execute docker/container applications with simple json configuration >>> file >>> It can also execute java applications (so we can use MFT without >>> containerizing it) >>> It works with SDKs in many languages and also it has simple http client >>> which makes it web friendly agent >>> Present orchestration agent could connect to Nomad, start/stop job, fetch >>> existing jobs >>> Orchestration agent in available in cybershuttle-server - >>> https://github.com/cyber-shuttle/cybershuttle-server/tree/main/orchestration-agent >>> Consul (message passing): >>> Inspired from the architecture of MFT, used consul as the main service in >>> communications from server to orchestration agent >>> Advantages of consul in this use case: >>> We can easily keep track of all available orchestrations agents (service >>> discovery and availability) >>> We can control access of each orchestration agent with controlled KV store >>> access >>> It makes our server and orchestration agent decoupled which makes huge >>> scope for horizontal scaling when required >>> Consul configurations as in this PR - >>> https://github.com/cyber-shuttle/cybershuttle-server/tree/main/consul >>> ConsulClient of cybershuttle server in this PR - >>> https://github.com/cyber-shuttle/cybershuttle-server/pull/4 >>> As of now consul to server integration is completed >>> >>> Next steps to complete the whole integration: >>> Code integration of consul and orchestration agent >>> Final end to end testing of operation from desktop to server to consul to >>> orchestration agent >>> >>> Please feel free to comment or suggest. >>> >>> Best Regards, >>> Praneeth Chityala >>
