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

Simplify Anbox Cloud appliance blueprint #63

Merged
merged 2 commits into from
Dec 9, 2024

Conversation

morphis
Copy link
Contributor

@morphis morphis commented Sep 24, 2024

See commit messages for details.

Latest version doesn't need Juju or the separate amc snap anymore and
only the anbox-cloud-appliance snap is required.
@morphis morphis force-pushed the simplify-anbox-cloud branch from 57962fb to d4a2569 Compare September 24, 2024 06:54
We use memfd's for a long time now and ashmem support is entirely
dropped.
@morphis morphis force-pushed the simplify-anbox-cloud branch from d4a2569 to d280ebb Compare September 25, 2024 19:40
Copy link
Contributor

@Sploder12 Sploder12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems cloud-init is timing out in CI. I don't think these changes would increase the launch time, correct? Rather, this seems like an existing issue. I wonder if we should increase the timeout?

@morphis
Copy link
Contributor Author

morphis commented Oct 31, 2024

@Sploder12 No, the changes should not necessarily increase time spent during the installation. We install less snaps and the new appliance snap is smaller than the old one (100MB vs 160MB).

The timeout you mention is within a workflow?

@Sploder12
Copy link
Contributor

@morphis Yes, the timeout can be found in v1/anbox-cloud-appliance.yaml

@Sploder12
Copy link
Contributor

Hey @morphis, what's the status on this?

@Sploder12 Sploder12 merged commit c08c18f into canonical:main Dec 9, 2024
3 of 5 checks passed
@morphis
Copy link
Contributor Author

morphis commented Dec 12, 2024

@Sploder12 sorry, for my late reply. Thanks for merging! Do you still want me to fix anything?

@Sploder12
Copy link
Contributor

No worries, it only had issues with CI so it's good now. Local testing revealed no issues!

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