Once again, the SUSE band is coming together to make music and we're planning a party this time round!!! We have a band name :-)

zypper is magic

A number of experiments suggest that it may be feasible to run zypper from an openSUSE 'live' media against a 'foreign' RPM based OS installation (eg. CentOS) and then 'zypper dup' to openSUSE

In short, give second breath to http://hall.suse.de/bugs/defects.cgi. Long version: Create a generated page reflecting SUSE organizational structure and containing links to useful generated Bugzilla queries and charts like:

Investigate how SUSE Manager will work (in place of Orthos) for managing Provo-based hardware in labs that needs to be shared across multiple organizations.

Currently the Open Container Initiative doesn't specify a distribution protocol or system, and the current "standard" format is the Docker registry protocol. Aside from technical reservations with Docker registry, it is also not an OCI-compliant system and will require a lot of work to integrate it into all of the openSUSE/SUSE tooling. So, a very insane idea I came up with is to convert OCI images to RPMs and then distribute them as simple RPMs. The idea would be to use capabilities (Provides: oci(...)) to implement the different names of images and then also the dependency graph of blobs (which would naturally be de-duplicated).

The purpose would be to have the equivalent of Ubuntu's "apt-get autoremove" functionality. When you install package P, it might draw in dependancies D1, D2, ... Dn automatically.

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project. My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:

Ever left a restaurant wanting to write a review, but thinking it wasn't worth the trouble to tap out all those words on your phone -- you just want to give the place your n stars and provide a few words of praise or condemnation? If only you could press a button to generate a plausible review. If this project happens, you will. We'll use the Yelp API to grab as many reviews of certain types of restaurants as the terms of service allow (I assume "Use any robot, spider, site search/retrieval application, or other automated device, process or means to access, retrieve, scrape, or index any portion of the Site or any Site Content;" doesn't apply to API users -- otherwise it wouldn't be much of an API).

There is a number of possible improvements to the architecture of SUSE Manager / Salt integration that should be investigated in order to improve the reliability and scalability of the backend: 1. Actions are currently scheduled in the minions using the schedule module of Salt. This brings problems with reliability as for instance a minion can be down at the specified schedule time which leads to actions not being executed. Scalability can be an issue as actions being scheduled for many minions might return results to the server at the same time. Instead it might be better to keep control over scheduled actions on the server to allow batching of actions as well as downtimes of minions or even the server. There is a work in progress branch to get started.

Just an excuse to learn more about antlr and parsing in general. Update Implemented a very simple interpreter https://github.com/mateiw/littlebasic

Alexa understands you. Jessy is the same, but you also understand her! :-)

Everyone loves to talk to the computer. Especially if it understands you. :-) So the Amazon Alexa is a hype right now. However, it requires your marriage to Amazon and signing contract to sell your soul in the afterlife: Alexa is nothing but a fancy microphone that sends everything you speak to ̶F̶B̶I̶ ̶a̶n̶d̶ ̶C̶I̶A̶ Amazon cloud so it will access your public API. Yes, and give them your access rights, of course...

In our team, we currently manually deploy our Terraform code (namely, the SUSE Registry at registry.suse.com) from our own PCs. This is error prone, as it would be very easy to override something by mistake. I want to create the appropriate .gitlab-ci.yml file that will:

Let's containerize SUSE Manager! This will open up different (and interesting) scenarios: - From a development perspective: learn about all the components that constitute SUSE Manager