1,027 karma · joined May 25, 2012
Software / Infrastructure Architect @ Udemy
Previously: Principal Engineer @ Microsoft Azure, Distinguished Member of Technical Staff @ Verizon, Master Engineer @ SUSE Senior Engineer @ Hewlett Packard Enterprise
ex - PTL for OpenStack Designate (DNS Project) (https://docs.openstack.org/designate/latest/)
ex - Member of the OpenStack Technical Committee
[ my public key: https://keybase.io/grahamhayes; my proof: https://keybase.io/grahamhayes/sigs/-W5bXnllXeYREBziC7KFYkLfh0caT8KLU6d7mQ20Tdw ]
The engineering team inside SUSE are exceptional - they do amazing things, and build really interesting features. The product planning / joined up thinking / visionary direction is where they fall down. As a sibling pointed out they have worked on some really interesting stuff, but (when I was there in any case) failed to pull it together into something that could have been outstanding.
Heart, Mind and Soul of the Open Source community is possibly a bit of hyperbole.
and - SUSE is (slightly) older than RedHat, so I am not sure you can say RedHat inspired them :)
IBM was inspired by RedHat's earnings (pre acquisition, open source in IBM was .... interesting ... ) and their ability to have a relevant product in the cloud space.
- on a side note - OpenStack and Kubernetes are not competitors, they are quite complementary collections of applications, that both have their place in a modern open source infrastructure.
K8S has a lot less moving parts - a couple of binaries / containers and etcd. The issue start coming up when you go beyond the single control plane node, and want a HA API.
I am pretty sure that the rules about IAP make it very clear you have to charge the same price on and off the app store.
They make money, that is not up for debate.
(and yes, I know, their platform, their rules, etc etc, but nothing about that says people cannot fight it, and make it politically difficult to let them bleed money from people for a very basic service.)
1 - I have never used basecamp, or looked into it, so YMMV
Apple. Google. Microsoft. Samsung.
> Who wants an app that you can’t do anything with when you download it?
People who want a client for their email service?
Hell, fastmail is even an email app, that has no in app purchases, and doesn't work without an account. (and is in the app store)
(There is a separate rant about using github stars as a metric of, well, anything, but thats a thing for a different day)
Yeah, it is cool - https://opendev.org/ is done that way, as is some of the wikimedia labs infrastructure
I am not certified either - I have just worked in places with ITIL inspired processes, but I can really see a way they can move forward with tools like terraform / pulumi / ansible and git
Ideally the same tool can be run locally and in CI (with the same invocation commands) so that an Op can run tests locally, and even see the potential diff, before putting it up for review.
The advantage of this approach is you can see a diff, and use standard tooling like git / pr reviews to approve changes in day to day, and when the world is on fire, someone can break the glass and run it locally.
Never underestimate the value of peer review on a change to the infra - there is a reason things like ITIL exist, and we should learn from them.
Please no. Don't make running a stateful service a requirement for tooling people need to use when the world is on fire. Or needs to load 40Mb of JS to rebuild a deployment, and works only on Chrome 46.012.2039465. Ops/SRE/DevOps/SysAdmin/SysOps/etc are different, and have optimised things to reduce the amount of dependancies.
(I know I am definitely not the target audience for the page)
1 -
# GitHub
if allof(exists "X-github-recipient",
header :regex "List-Id" "<([a-z_0-9-]+)\.([a-z_0-9-]+)[.@]") {
set :lower "organisation" "${2}";
set :lower "repo" "${1}";
fileinto :create "INBOX.GitHub Code Review.${organisation}.${repo}";
stop;
}It is fine, unless you do a lot of back ports or bug fixes for older releases, at which point the version branches are very useful.
Microsoft Azure Global E2E^2 is hiring for two teams in Dublin, Ireland.
Both of the teams: the job says Senior, but we are hiring at all bands.
Team A: The team is responsible for running workloads on Azure and using them to ensure the customer experience is a good one. This role will be building out the infrastructure to collect the telemetry from these applications, and mine the data collected for insights into the Azure platform, and ensuring the whole system stays up and running so that the test workloads can keep pushing data in. There will be an element of on call work - but the on call rota will be spread across 2 time zones, which means reasonable on call hours.
Experience in running a production high volume metrics ingestion system is a plus, along with a steady hand for when things break.
Team 1: This team is responsible for building end to end tested reference architecture for Azure, and is currently working on a reference multi tenant container hosting platform based on Kubernetes (both AKS for in cloud, and upstream K8S for edge / remote sites). The aim is to open source the work.
Upstream open source experience (in any open source IaaS stack, or IaaS management tools like terraform / ansible) is definitely a plus, along with experience in regulated environments (banking, telco or government).
Both teams - apply using this advert: https://careers.microsoft.com/us/en/job/785404/Senior-Softwa...
Any questions - graham(dot)hayes(at)microsoft(dot)com, or via the link above.
e.g. - the latest RC of a project I maintain is L10-14 on https://opendev.org/openstack/releases/src/branch/master/del...
by committing that file, the tooling chooses the right commit, does a tag, and builds the python tarballs, and puts them on releases.openstack.org, and for the client libraries, it pushes them to pypi.
it avoids a lot of the footguns of special scripts in repos, while allowing an easy release process.
Why?
Great software - Linux - is not paid, and it is taking over the hosting world, and the IOT world.
GNU is great software. nano / pico is great software. python is great software. .NET is great software. it is all open source.
That is one hell of a hot take. RedHat, SUSE, Canonical, would all probably disagree. (also, fwiw, so would I - I have been working on Open Source software for 5+ years, and have been paid for it for the entire time)
> as most are either contract workers or just volunteers
The linux kernel called, said something about having a large amount of fully paid, long term staff.
I get it, you don't like free software - but there is plenty of free software that people are paid to maintain and develop, and it has been a great benefit to software development as a result. Even paid for software is probably using some open source components, (runtimes, languages, compilers, libraries to name a few of them).
I like the idea from the talk of just blocking them outright.
So very (and unfortunately) true. However they also have no power to make you do the thing they need straight away, or ever.
> Even if you put hard work in it, you sacrifice a bit of your life.
And this is bad. We need to move the needle away from this. It is incredibly exclusionary
I am a younger person, no kids, in a job where I was able to negotiate for open source maintenance time. By making "sacrifice" a requirement it makes it off putting for someone with kids, or working in a job that has them working long hours, or working multiple jobs.
> But the user, well, they just are what they are, software can't fix that.
No, software can't fix it. but highlighting the problem, and letting people possibly see what they are doing is not useful may change the user.
I have been a maintainer of a project for a long time, and I get everything from people pinging me in our IRC channel, to DMing me, to asking if I give them my skype ID so I can call into a bridge to help them debug an issue at midnight. We need to highlight this is not OK.
Personally, I really like the PowerDNS rule for open source support [1] - it sets expectations, and the base requirements from someone looking for help.
> the success, at least to me, was measured by the number of users
That is a valid metric, but just one. I personally measured the success of the project based on what people were using it (e.g. I would rather wikimedia vs 20 startups), but that metric is really person specific.
1 - https://blog.powerdns.com/2016/01/18/open-source-support-out...
An maxed out z8 is $50k - but that is way over what most people need, or you can do with a Mac Pro
If you look at other manafacturers - you can get insane performance for much cheaper.
2 x AMD Epycs (64 cores per CPU, 128 cores / 256 threads in the box) 1TB RAM 2x2TB SSD 2 x Quadro RTX 6000
Is $38,000. It is not even in the same sport, let alone league as the mac pro
Juju (linked below), OpenStack-Ansible, or openstack helm all make deployment possible.
The end user story has been pretty consistent for a while, with additions for newer features, and high performance hardware always in the pipeline.
A lot of the horror stories from the early days were people expecting free, fire and forget ESXi - which it is not.
1 - I have been a project team lead on one of the sub projects for ~ 4 years, and more recently sit on the Technical Committee.
VMS clusters were (and modern equivalents are) awesome, but they have a different speed of innovation / development.
It is a trade off - perfect uptime, but that new feature could take a year, or 99.9% uptime, but it can be written and deployed tomorrow.