The Autoware Foundation
Replies: 0 comments 7 replies
-
@LalithVipulananthan Thank you for your summary, but I believe this isn't true. So before that, we should define what benefits we'd like to provide to the users by introducing My proposal is to list up use cases. |
Beta Was this translation helpful? Give feedback.
-
|
@LalithVipulananthan The first step is to have a CI/CD which splits the monolithic Autoware container into smaller containers based on features, e.g., map, sensing, localization, etc, and then manage these smaller containers using an orchestrator (K3s). Software development can still be done in a monolithic Autoware container with SDK and all necessary tool chains, but be deployed as a microservice. I'm not sure what is meant by "taking down the entire system"? |
Beta Was this translation helpful? Give feedback.
-
|
@kasperornmeck @LalithVipulananthan I've meant that in Autoware.Auto, generally you need to restart all of nodes (take down the entire system) even if you want to restart one. Because most of the demos run from a single launch file and hard to shut down / restart a single node from there. Because there is no For that we need to implement Managed Nodes. When I was making these remarks, I was talking about the things we lack in Autoware.Auto in general, not specifically related to OpenAD Kit. |
Beta Was this translation helpful? Give feedback.
-
|
@xmfcx |
Beta Was this translation helpful? Give feedback.
-
|
@kasperornmeck Yes it would. But we will implement Managed Nodes regardless to enable fine control over the nodes. |
Beta Was this translation helpful? Give feedback.
-
|
@xmfcx @kasperornmeck Thank you for your comments. You will have to forgive my ignorance on the subject, but Kasper mentioned "using a microservices way of deployment", is this something that Autoware is capable of right now or is additional development work required? If the latter, very roughly speaking how much time would be required to do that work? In either case, does the AS WG plan to implement Managed Nodes as a priority, and if so how long might that work take? |
Beta Was this translation helpful? Give feedback.
-
|
@LalithVipulananthan Not sure regarding Managed Nodes. |
Beta Was this translation helpful? Give feedback.
-
One of the objectives for the Open AD Kit is to deliver a microservice based architecture for Autoware to enable cloud native devops and cloud-to-edge service orchestration
(note that this image was taken from a presentation at the start of the Open AD Kit WG in July 2021, so predates Autoware Core/Universe)
However, I understand that this is no small task and that are a number of challenges involved with applying the microservices paradigm to Autoware. Thus, the purpose of this discussion is to better understand the nature and scale of those challenges so that we can begin to break them down into smaller, more approachable tasks.
As an example, during the 2022/01/26 Open AD Kit WG meeting, @xmfcx mentioned that:
If the ability to monitor and take down individual nodes must be in place first as part of developing a microservices architecture, very roughly what would need to be done to put that functionality in place and what would be the next steps?
I am hoping that @mitsudome-r and @kasperornmeck can also add to this discussion as we get started, but I would also like for other members of the WG and of the AWF community to contribute their thoughts and opinions too!
Beta Was this translation helpful? Give feedback.
All reactions