Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support subnets, CIDRs, segments in SG generation #174

Open
zivnevo opened this issue Jul 23, 2024 · 5 comments · May be fixed by #216
Open

Support subnets, CIDRs, segments in SG generation #174

zivnevo opened this issue Jul 23, 2024 · 5 comments · May be fixed by #216
Labels
enhancement New feature or request

Comments

@zivnevo
Copy link
Member

zivnevo commented Jul 23, 2024

No description provided.

@zivnevo zivnevo added the enhancement New feature or request label Jul 23, 2024
@YairSlobodin1
Copy link
Member

@zivnevo do you mean segments of instances/nifs?

@zivnevo
Copy link
Member Author

zivnevo commented Sep 12, 2024

I'm not quite sure what we meant here. Are segments of other types (subnets, cidrs) supported in SG synthesis?

@YairSlobodin1
Copy link
Member

I'm not quite sure what we meant here. Are segments of other types (subnets, cidrs) supported in SG synthesis?

segments are not supported in SG synthesis

@zivnevo
Copy link
Member Author

zivnevo commented Sep 12, 2024

I think we want to support segments of all types: subnets, cidrs, instances and nifs. I can't really tell which is more important.
@kyorav , any insights?

@kyorav
Copy link
Collaborator

kyorav commented Sep 12, 2024

I have no idea how to prioritize.
Note that we chose the word "segment" because it was meant for subnets and cidrs. Sets of instances and NIFs would not be called segments, but I guess they could be useful all the same...?

@YairSlobodin1 YairSlobodin1 linked a pull request Oct 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants