Hi Sandaruwan, Thanks for sharing the Google document. IMO it needs to include more detailed information about the project plan (may be not the implementation details but the approach). What you have currently written is not sufficient.
At this stage you might not need to spend time on designing the API methods. The core requirement of this project would be to analyze and propose a solution for managing the software update process in Stratos. We might need to design a sequence diagram to describe the entire flow. We may also need to consider introducing new events in Messaging component to handle the process. Up to the point where an event is sent to the cartridge instance to trigger the software update process should be able to handle in the same way for both Puppet based and Docker based cartridges. As the first step try to run Stratos with Mock IaaS/Kubernetes, this would allow you to understand how it works. Then try to analyze the lifecycle of the cartridge instance (member). Thereafter analyze and see how we can change the member's lifecycle to support software update process. At this point draw a diagram to illustrate the eventing model. Hope this would help. Thanks Imesh On Tue, Mar 10, 2015 at 1:25 AM, Sandaruwan Nanayakkara < [email protected]> wrote: > Hi Imesh, > > I have created a Google Doc with information regarding the project. > Google Doc > <https://docs.google.com/document/d/1Ep2EwLubQnAv0bQGXE2ynwIDrRFCtMnCZ1E52KtzUH4/edit?usp=sharing> > > Please inform any if there is anything to add. > > Thanks > Sandaruwan > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
