search

weaveworks / ignite

Ignite a Firecracker microVM
https://ignite.readthedocs.org
Apache License 2.0
3.49k stars 228 forks source link

Support Chef's Test Kitchen infrastructure requirements. #238

Open taqtiqa-mark opened 5 years ago

taqtiqa-mark commented 5 years ago

Would weaveworks support any changes/issues required in the course of creating a Test Kitchen plugin that provides a driver, transport, and provisioner for rapid cookbook testing and VM development using Ignite and Chef Infra Client.

This would likely be a hybrid of Kitchen-Docker and Kitchen-Dokken.

The benefit is an environment one step closer to the production environment. Example at the moment Docker/Dokken cannot support Test Kitchen service tests.

luxas commented 5 years ago

Yes, this seems like a good use case. We'd be happy to receive such contributions, or see community projects implementing this. What I don't understand is if this kind of integration requires any code changes to Ignite. Can you clarify this please?

taqtiqa-mark commented 5 years ago

I can't say whether ignite changes are required. This was to gauge whether you do view this as an important use case. For example, the use case will often be developer machines - often laptops, often mac and even windows. Another use case that may generate issues/reports is CI environments: TravisCI, CircleCI etc etc.

luxas commented 5 years ago

I have no previous knowledge of Chef's Test Kitchen; hence I can't comment really on this specific use-case. Without knowing, I suppose that it should work with Ignite without code changes in ignite, really.

One of the primary goals of ignite is fast VM booting for testing, CI, dev, as well as k8s cluster lifecycle.