Project Description

The wasm ecosystem is becoming more mature and feature rich. With this, I'd like to allow developers to run their code in wasm without needing to know how to set up their tooling or build the binary. Because of this, I think it would be interesting to extend cloud native buildpacks so you can build wasm-oci images in any of the platforms that support buildpacks.

Currently, there is no work being done on this other than that I've done some limited research and opened up a ticket upstream (https://github.com/buildpacks/lifecycle/issues/820)

Goal for this Hackweek

By the end of the week, I'd like to either have a POC of a builder image using the forked cloud native lifecycle or have some areas of research to take forward.

Resources

Main repo to fork and work on (then ask to merge back upstream): https://github.com/buildpacks/lifecycle Wasm image spec: https://github.com/solo-io/wasm/blob/master/spec/README.md Buildpack builder that may come in useful: https://github.com/agracey/metabuildpack

Looking for hackers with the skills:

go golang kubernetes containers wasm webassembly

This project is part of:

Hack Week 21

Activity

  • about 3 years ago: paulgonin liked this project.
  • over 3 years ago: ecandino liked this project.
  • over 3 years ago: atgracey added keyword "go" to this project.
  • over 3 years ago: atgracey added keyword "golang" to this project.
  • over 3 years ago: atgracey added keyword "kubernetes" to this project.
  • over 3 years ago: atgracey added keyword "containers" to this project.
  • over 3 years ago: atgracey added keyword "wasm" to this project.
  • over 3 years ago: atgracey added keyword "webassembly" to this project.
  • over 3 years ago: atgracey originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    terraform-provider-feilong by e_bischoff

    Project Description

    People need to test operating systems and applications on s390 platform.

    Installation from scratch solutions include:

    • just deploy and provision manually add-emoji (with the help of ftpboot script, if you are at SUSE)
    • use s3270 terminal emulation (used by openQA people?)
    • use LXC from IBM to start CP commands and analyze the results
    • use zPXE to do some PXE-alike booting (used by the orthos team?)
    • use tessia to install from scratch using autoyast
    • use libvirt for s390 to do some nested virtualization on some already deployed z/VM system
    • directly install a Linux kernel on a LPAR and use kvm + libvirt from there

    Deployment from image solutions include:

    • use ICIC web interface (openstack in disguise, contributed by IBM)
    • use ICIC from the openstack terraform provider (used by Rancher QA)
    • use zvm_ansible to control SMAPI
    • connect directly to SMAPI low-level socket interface

    IBM Cloud Infrastructure Center (ICIC) harnesses the Feilong API, but you can use Feilong without installing ICIC, provided you set up a "z/VM cloud connector" into one of your VMs following this schema.

    What about writing a terraform Feilong provider, just like we have the terraform libvirt provider? That would allow to transparently call Feilong from your main.tf files to deploy and destroy resources on your system/z.

    Other Feilong-based solutions include:

    • make libvirt Feilong-aware
    • simply call Feilong from shell scripts with curl
    • use zvmconnector client python library from Feilong
    • use zthin part of Feilong to directly command SMAPI.

    Goal for Hackweek 23

    My final goal is to be able to easily deploy and provision VMs automatically on a z/VM system, in a way that people might enjoy even outside of SUSE.

    My technical preference is to write a terraform provider plugin, as it is the approach that involves the least software components for our deployments, while remaining clean, and compatible with our existing development infrastructure.

    Goals for Hackweek 24

    Feilong provider works and is used internally by SUSE Manager team. Let's push it forward!

    Let's add support for fiberchannel disks and multipath.

    Possible goals for Hackweek 25

    Modernization, maturity, and maintenance.