What is Brine?

Simply put: A build system for Salt Formulas

The Vision

I started Brine years ago when I worked for another company to help people get started building Salt Formulas without requring them know Salt or read our internal Style Guide for writing Formulas. The original scope was small and so rather than being a build system, it is currently more of a Salt Formula initializer. However, I do see a need in the Salt community for something a but more than just an initializer. I think Brine can fill that gap.

Why Rewrite at all?

the current implementation of Brine is written in Python. This is mostly because Salt is in Python and I can somewhat write Python myself. Also I was around many, many people who knew Python very well.

Why Rewrite in Go?

Someone I worked with when I was working on Brine, build a tool to make it easier to work with GPG encrypted Pillar. In that tool, I see ways Brine to be able to integrate and leverage what he built.

Also, I here are some other reasons I want to work on this in Go:

  • I have not really had a chance to write any Go in about two years and I didn't know much to begin with, so I'd like to re-familiarize myself with the language while building something that I already know what I expect from a working implementation.
  • Statically-linked binary makes it easy for people to get started with Brine.
  • Go's strong community.

Looking for hackers with the skills:

salt saltstack buildsystem golang brine

This project is part of:

Hack Week 17

Activity

  • about 7 years ago: mbrugger liked this project.
  • about 7 years ago: Druonysus liked this project.
  • about 7 years ago: Druonysus added keyword "salt" to this project.
  • about 7 years ago: Druonysus added keyword "saltstack" to this project.
  • about 7 years ago: Druonysus added keyword "buildsystem" to this project.
  • about 7 years ago: Druonysus added keyword "golang" to this project.
  • about 7 years ago: Druonysus added keyword "brine" to this project.
  • about 7 years ago: Druonysus started this project.
  • about 7 years ago: Druonysus 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.