coprs/buildsystems

July 26, 2012

If you’ve been following my blog you’ve probably seen most of what I’m working on. However, at the request of my manager (hi Tom!) I wanted to collect what I’ve been working on and why. So I decided to put the pieces together on the fedora wiki:

https://fedoraproject.org/wiki/User:Skvidal/BuildSystem

If you’d like to help or to discuss email me or discuss on the fedora buildsys list.

Advertisements

fudcon day 1

January 14, 2012

a. infrastructure staging will perish:

1. Kill staging branch – identify what we want from staging to be in our ‘master’
branch.
a. copy staging branch to a subdir
b. kill staging branch
c. copy in pieces we care about a bit at a time – as needed.
2. move all .stg. boxes to ‘production’ puppet environment.
3. all boxes we maintain are ‘production’ from a configtest/pkging standpoing
4. app development moves to partial silos and/or openshift to do their code testing
then moved to production like a normal app deployment – rpm + config changes.

b. 2fa will start being implemented for users of sudo

c. if we are very good, smolt will find a new home. Maybe in openshift?

d. happy to meet pknirsch the guy in charge of the packaging team and hear of his evil plans to make my (and many other people’s) lives better.

Been seeing a lot of random spam from known people on gmail accounts recently. People whose accounts got phished or brute-force-cracked or what-not.

I’d like to suggest folks using gmail look HARD at using this:

http://www.google.com/support/accounts/bin/static.py?page=guide.cs&guide=1056283&topic=1056284

it’s easy to setup and once you have it in place you’ve just made things much, much harder for folks to abuse. Not impossible, you’re not completely safe. But you are in a better position than you were before.

(caveat please don’t blame me b/c the guy in this video desperately needs to shave, it drove me nuts, too)

 

canary?

May 4, 2011

or is it a canard?

or is it maybe a red fish?

so hard to tell these days.

just ignore this.

Recording this for posterity – in case I forget.

date +%F --date=@`rpm -qa --qf '%{installtime}\n' | sort -nr | tail -1`



ipv4 addresses

February 3, 2011

I’ll get back to fudcon recap in a bit – but I wanted to ask a silly question about ipv4 addresses:

 

Why are people worried about address exhaustion in ipv4? If you take a look through the class-a allocations you’ll notice that 6 of the class As are allocated to the US department of Defense in one form or another.

So I’ve got to ask: why does the military need to have 96 million public, routable, ip addresses?

96 million seems like a largish number to me.

It is, in fact, 1 ip for roughly every 3 americans.

If they are giving an ip to every device they have, I could sorta understand it – but I really don’t want them giving public, routable, ips to everyone of them, especially the weapons. 🙂

in the same vein – someone could explain to me why mit needs  16 million addresses? What do they have 1000 public devices per student/prof/staff? Somehow I doubt that.

boggles my mind.

 

This is a note to all companies or projects or people considering working on some sort of  systems administration tool or platform or interface.

USE PYTHON

Here’s why:

Red Hat

Canonical

Sun

Google

These companies use python for an OVERWHELMING number of items in their sysadmin/build/deploy/maintenance tooling. A massive amount of their code is already in python. They can work with it, you can import their modules, and you don’t have to yet another frelling language installed just to maintain your systems.

So when confronted with a choice of a language don’t think about it anymore than python.