...
- zoom https://zoom.us/my/hyperledger.community rocket chat https://chat.hyperledger.org/channel/cello
- Ongoing Jira task https://jira.hyperledger.org/projects/CE/issues/CE-188?filter=allopenissues
- Open Patchset for review https://gerrit.hyperledger.org/r/#/q/project:cello+status:open
- Project Wiki Page https://wiki.hyperledger.org/projects/cello
Agenda
- Recent resolved issues (: https://jira.hyperledger.org/issues/?filter=12743;
- Tong will present the quarterly report in next week's TSC meeting, welcome to help review.
- Containerizing agent call using python container client library (SDK)
Attendee
Please input your name before the meeting
- @Baohua Yang
- hightall
- @tong li
- @Luke Chan
- @DuPeng
Minutes
- Tong Li (Deactivated) suggest to isolate the authentication and authorization part, i.e., let nginx or other web proxy to help do authentication. While hightall think the API server can handle both. The existing solution is not that flexible, but can be taken as the first milestone.
- Peng Du Luke Chan and Mingming Tian proposed their thoughts, too.
- Tong Li (Deactivated) suggest let each agent run inside container:
- Pros: No need to use python to write the agent code, any language can be taken, even with command line tool.
- Cons: May introduce latency during agent call, and may need to consider how to secure the container call, and let the container has credential when start up.
- Question TBD: the container will be server-less or work as daemon?