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

2023 10 16/net #93

Merged
merged 4 commits into from
Nov 2, 2023
Merged

2023 10 16/net #93

merged 4 commits into from
Nov 2, 2023

Conversation

hallyn
Copy link
Contributor

@hallyn hallyn commented Oct 18, 2023

No description provided.

@hallyn hallyn requested a review from raharper October 18, 2023 13:47
layers/install/load-mos-modules Outdated Show resolved Hide resolved
layers/provision/zot.service Outdated Show resolved Hide resolved
pkg/provider/kvm.go Outdated Show resolved Hide resolved
tests/helpers.bash Outdated Show resolved Hide resolved
tests/vmhelpers.bash Outdated Show resolved Hide resolved
@hallyn hallyn force-pushed the 2023-10-16/net branch 8 times, most recently from 82bc473 to 9f0b7d4 Compare October 28, 2023 02:55
@hallyn hallyn marked this pull request as ready for review October 28, 2023 03:01
@hallyn hallyn marked this pull request as draft October 28, 2023 03:18
@hallyn
Copy link
Contributor Author

hallyn commented Oct 28, 2023

Ah - pkg/provider/kvm.go is hard-coding the port forwarding into the template. We need a generic way to handle this. So 'trust launch vm1 10.0.2.2:5000/machine/zotservice:1.0.0' should be told to pass a port in to the vm's port 80. Marking this PR 'draft' again until we have some fix for that.

@hallyn hallyn force-pushed the 2023-10-16/net branch 11 times, most recently from b4e914a to 3494823 Compare October 29, 2023 22:02
@hallyn hallyn marked this pull request as ready for review October 30, 2023 02:09
@hallyn hallyn force-pushed the 2023-10-16/net branch 3 times, most recently from 7c21435 to 8f55ad4 Compare October 30, 2023 14:48
@hallyn hallyn marked this pull request as draft November 1, 2023 15:19
@hallyn
Copy link
Contributor Author

hallyn commented Nov 1, 2023

I'd like to merge this, but we have to first remove the hard-coded vm port forward rules from 'trust launch'. So either I need to accept optional yaml as a 'trust launch' argument, or probably i should just edit the vm definition (either after initial definition, or after install and before first run) to add the network definition.

Closes project-machine#4
Closes project-machine#7

Implement 'mos boot' which activates all services.

Implement a 'simple' network type for services, which
isolates a service in a netns with a simple veth on the
lxcbr0, with specified host ports forwarded into the
container.

layers/install: add a zot service layer which uses the
simple network.

Have test/launch.bats test connection to zot in
network-namespaced container.

update to v0.0.17 bootkit for 4M firmware
kvm provider: specify bootindex 'off' for nics
add a hidden subcommand to verify an install.yaml

github ci - give 'make test' more time

Signed-off-by: Serge Hallyn <[email protected]>
As suggested by Ryan.

Signed-off-by: Serge Hallyn <[email protected]>
disable tdp_mmu in kvm
enale dump_invalid_vmcs=Y in kvm_intel

This appears to be causing (nested) vm crashes

Signed-off-by: Serge Hallyn <[email protected]>
@hallyn hallyn marked this pull request as ready for review November 1, 2023 21:04
@hallyn
Copy link
Contributor Author

hallyn commented Nov 1, 2023

Ok - I've dropped the hacky network definition from trust launch, so I do think this is ready to merge.

@hallyn hallyn merged commit d0a26d1 into project-machine:main Nov 2, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants