Closed iwanbk closed 1 month ago
Please don't start working on anything before planning these tickets
Please don't start working on anything before planning these tickets
if what you mean by "working" is coding, then sure.
Here is my 2 cents on this issue:
The point is: ZOS doesn't need to change to support this, this is all supported by current primitives. Adding a new workload type or primitive for each feature will just make the code unmanageable and unnecessary complicated
ZOS doesn't need to change to support this, this is all supported by current primitives. Adding a new workload type or primitive for each feature will just make the code unmanageable and unnecessary complicated
Thanks for the input. I think it is similar with what @xmonader said in the Telegram.
So, what steps need to be done @muhamadazmy @xmonader ?
zsocks
repo with binary uploaded every releaseflists
? My initial plan was to add script to bins
package of zos
, but i think there is other way?We use some github actions to automatically create flists for applications. You can check the zos github worklflows for inspiration.
Simply your github action first build your binary(s) then the flist action that packs it and upload it to the hub. Simple as that.
Once it's on the hub, it can be used to create workloads on the grid.
check docs for action here
Once it's on the hub, it can be used to create workloads on the grid.
where i can find the docs to create the workload?
Closing this as it's beyond the scope of zos
Is your feature request related to a problem? Please describe
Give ability for the users to connect to the internet through SOCKS5 proxy
Describe the solution you'd like
By using
zsocks
as the proxy, which is based on fast-socks5 (https://github.com/dizda/fast-socks5)The rough plan:
Detailed plan (WIP):
zsocks
binary on github release tozsocks
repo assetszsocks
to flistszsocks
to network subsystem ofzos
as optional service