Create a Cloud-Native policy engine with notifying capabilities to optimize resource usage
a project by gbazzotti
Updated about 2 months ago. 1 hackers ♥️. 1 follower.

Description

The goal of this project is to begin the initial phase of development of an all-in-one Cloud-Native Policy Engine that notifies resource owners when their resources infringe predetermined policies. This was inspired by a current issue in the CES-SRE Team where other solutions seemed to not exactly correspond to the needs of the specific workloads running on the Public Cloud Team space.

The initial architecture can be checked out on the Repository listed under Resources.

Among the features that will differ this project from other monitoring/notification systems:

  • Pre-defined sensible policies written at the software-level, avoiding a learning curve by requiring users to write their own policies
  • All-in-one functionality: logging, mailing and all other actions are not required to install any additional plugins/packages
  • Easy account management, being able to parse all required configuration by a single JSON file
  • Eliminate integrations by not requiring metrics to go through a data-agreggator

Goals

  • Create a minimal working prototype following the workflow specified on the documentation
  • Provide instructions on installation/usage
  • Work on email notifying capabilities

Resources

Join this project

Looking for hackers with the skills:

golang cloud aws

This project is part of:

Hack Week 25

Activity

  • about 2 months ago: baldarn liked this project.
  • 2 months ago: gbazzotti started this project.
  • 2 months ago: gbazzotti added keyword "golang" to this project.
  • 2 months ago: gbazzotti added keyword "cloud" to this project.
  • 2 months ago: gbazzotti added keyword "aws" to this project.
  • 2 months ago: gbazzotti originated this project.


    • Comments

    • gbazzotti
      about 2 months ago by gbazzotti | Reply

      Development Update: this week has been great for development, with many changes to the core architecture being noticed as required to depart from the original vision to enhance core functionality. Several packages were introduced to modularize the project to make it easier to develop new policies, such as logging config, errors, policies and utils.

      Key functional updates include the implementation of email sending capabilities through SES, the addition of notify and version commands, and refinements to identity checks and JSON marshalling.

    • gbazzotti
      about 1 month ago by gbazzotti | Reply

      Final HackWeek Development Update: today was a very productive day with the e-mail template being updated, as well as adding a lot of documentation regarding the current policies, different installation methods and overall general housekeeping changes to put the program to the test.

      Although HackWeek is over, this project really made me get in touch with something I'm passionate about and that I think I could create value and save a lot of time for my team, so I will definitely keep working on this project for months to come and try to make it a used tool by the SRE teams across CES. Next steps will be to prevent emails going to spam by configuring DKIM, developing new policies to fit the needs of those who test the tool, and using GoReleaser to automatically create new binary releases

    Similar Projects

    Create a go module to wrap happy-compta.fr by cbosdonnat

    Description

    https://happy-compta.fr is a tool for french work councils simple book keeping. While it does the job, it has no API to work with and it is tedious to enter loads of operations.

    Goals

    Write a go client module to be used as an API to programmatically manipulate the tool.

    Writing an example tool to load data from a CSV file would be good too.

    terraform-provider-feilong by e_bischoff

    Project Description

    People need to test operating systems and applications on s390 platform. While this is straightforward with KVM, this is very difficult with z/VM.

    IBM Cloud Infrastructure Center (ICIC) harnesses the Feilong API, but you can use Feilong without installing ICIC(see 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 z/VM system.

    Goal for Hackweek 23

    I would like 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.

    Goals for Hackweek 25

    Modernization, maturity, and maintenance: support for SLES 16 and openTofu, new API calls, fixes...

    Resources

    Outcome

    Contribute to terraform-provider-libvirt by pinvernizzi

    Description

    The SUSE Manager (SUMA) teams' main tool for infrastructure automation, Sumaform, largely relies on terraform-provider-libvirt. That provider is also widely used by other teams, both inside and outside SUSE.

    It would be good to help the maintainers of this project and give back to the community around it, after all the amazing work that has been already done.

    If you're interested in any of infrastructure automation, Terraform, virtualization, tooling development, Go (...) it is also a good chance to learn a bit about them all by putting your hands on an interesting, real-use-case and complex project.

    Goals

    • Get more familiar with Terraform provider development and libvirt bindings in Go
    • Solve some issues and/or implement some features
    • Get in touch with the community around the project

    Resources

    Q2Boot - A handy QEMU VM launcher by amanzini

    Description

    Q2Boot (Qemu Quick Boot) is a command-line tool that wraps QEMU to provide a streamlined experience for launching virtual machines. It automatically configures common settings like KVM acceleration, virtio drivers, and networking while allowing customization through both configuration files and command-line options.

    The project originally was a personal utility in D, now recently rewritten in idiomatic Go. It lives at repository https://github.com/ilmanzo/q2boot

    Goals

    Improve the project, testing with different scenarios , address issues and propose new features. It will benefit of some basic integration testing by providing small sample disk images.

    Updates

    • Dec 1, 2025 : refactor command line options, added structured logging. Released v0.0.2
    • Dec 2, 2025 : added external monitor via telnet option
    • Dec 4, 2025 : released v0.0.3 with architecture auto-detection
    • Dec 5, 2025 : filing new issues and general polishment. Designing E2E testing

    Resources

    Rewrite Distrobox in go (POC) by fabriziosestito

    Description

    Rewriting Distrobox in Go.

    Main benefits:

    • Easier to maintain and to test
    • Adapter pattern for different container backends (LXC, systemd-nspawn, etc.)

    Goals

    • Build a minimal starting point with core commands
    • Keep the CLI interface compatible: existing users shouldn't notice any difference
    • Use a clean Go architecture with adapters for different container backends
    • Keep dependencies minimal and binary size small
    • Benchmark against the original shell script

    Resources

    • Upstream project: https://github.com/89luca89/distrobox/
    • Distrobox site: https://distrobox.it/
    • ArchWiki: https://wiki.archlinux.org/title/Distrobox