To add more flexibility, variability and increase testing capacity we would like to move QAM cloud nodes from physical machines(in NUE) into virtual environment.

With many Proof of Concepts (PoCs) going on for SUSE Cloud, the development team has observed that we have no clear path on how Sales Engineers (SEs) and sometimes dedicated support engineers (xSE) can receive technical support to successfully complete the projects, often leading to escalation calls and even firefighting on-site visits by developers. Goal of that project is to come up with a best practice guide and to eventually set expectations on what's possible from a development point of view. Results should be documented in a central internal location and announced to all relevant parties.

In order to have complete cloud experience on Power platform it needs some missing pieces to be available: * SLEShammer image (SLE11-> SLE12)

During the last CSM workshop we identified the need to have a good way to share the images we use for testing. We have documented the requirements and the current status in this wiki page (we even have a diagram). So analysis is done... it's time for action. The solution should be relatively easy to implement using our portfolio of solutions. Coordinating all the potential users should be easier during Hackweek, specially since I'll be in Nuremberg (and I can physically chase most people ;-) ).

OpenStack is, undoubtedly, a really huge ecosystem of cooperative services. Rally is a benchmarking tool that answers the question: “How does OpenStack work at scale?”. To make this possible, Rally automates and unifies multi-node OpenStack deployment, cloud verification, benchmarking & profiling. Rally does it in a pluggable way, making it possible to check whether OpenStack is going to work well on, say, a 1k-servers installation under high load. Thus it can be used as a basic tool for an OpenStack CI/CD system that would continuously improve its SLA, performance, and stability. <img src="https://wiki.openstack.org/w/images/thumb/e/ee/Rally-Actions.png/850px-Rally-Actions.png" width="700">

make crowbar+openstack work on openSUSE Leap 42.2 part of this is setting up public CI. For that, we need to port mkcloud to work on Debian.

OpenFaaS - Functions as a Service Get familiar with one of the hottest topics for this year: https://www.openfaas.com/

Since SUSE Manager doesn't scale out and stacking it into another pyramid of susemanagers won't help here, the real architectural changes needs to be done to achieve true scale-out of this product. This hackweek project is about how to Turn SUSE Manager into a cluster. Areas to be tackled:

This project aims to run VMs in a CaaSP 4 cluster using kubevirt and a libvirt+qemu container (aka compute container) based on SLES15 SP1/2. Compute containers based on openSUSE Leap15.1 and SLES15 SP1 already available in registry.opensuse.org and registry.suse.com respectively. VMs can be deployed to the cluster but there are several functional problems that need investigating, e.g. accessing the VM's serial and VNC consoles, proper network access, etc.

Project Description

The goal of this project is to create a lightweight multi-cloud metadata CLI for Public Cloud environments. There are cloud specific packages that exist but they all have different API and many are developed in Python which is quite heavy for cloud images, especially containers. Leveraging a compiled language will help with keeping the CLI lightweight.