Saturday, June 28, 2014

I'm very ghetto

I shat out a quick connectwise to KML python script so sales ppl can look at their turf in google earth and etc.  I am a bad person.  Bad in every way.  This will be refined into something I'm not embarrassed of, but I was surprised something like this wasn't on the internet already.

import pyodbc
from geopy.geocoders import Bing
import simplekml
bingkey="lsdfkglksjdfglksfdhlkjghsdlkfjhglskdfjhgsjdgjsjdf"
geolocator = Bing(bingkey)
kml = simplekml.Kml()
conn = pyodbc.connect('Driver=FreeTDS;Server=10.x.x.x;port=1433;uid=sqlreporting;pwd=blabalbalbalablab;database=blerblebleblrblebr')
cur = conn.cursor()
q="""
SELECT Company.Company_Name,Address_Line1,City,State_ID,ZIP
from Company INNER JOIN Company_Address on Company.Company_RecID=Company_Address.Company_RecID
and Company.Company_Status_RecID=1
"""
cur.execute(q)
i=1
for row in cur.fetchall():
        address=''
        company = row[0]
        addressline1 = row[1]
        addresscity = row[2]
        addressstate = row[3]
        addresszip = row[4]
        if (isinstance(addressline1, str) and isinstance(addresscity,str) and isinstance(addressstate,str)):
                address = addressline1 + ' ' + addresscity + ' ' + addressstate
        fulladdress=''
        latitude=''
        longitude=''
        try:
                fulladdress, (latitude, longitude) = geolocator.geocode(address)
        except:
                print("found a bad address: " + company + ' ' + address)
        if (fulladdress != ''):
                print (i, company)
                kml.newpoint(name=company, coords=[(longitude,latitude)])
        i=i+1
kml.save("bigtest.kml")
cur.close()
conn.close()

Friday, June 27, 2014

trailroc 255

new pair showed yesterday.  fit like a glove here in the house.  will run in them later.  the red/black ones are like $120 but the purple/orange can be had for $75.  such is life.

Thursday, June 26, 2014

solving problems methodically

Scope the problem
-give it a name
-can it be measured
-can it be recreated at will
-with what frequency does it occur
-what else is is correlated with
-what is the definition of success
-what tests can be methodically executed to generate data
-how can data be collected
-what variables are involved that can be modified
edit:
-when did it start
-what other changes in may have occurred at or around that time

If you can measure it, you're in good shape.

Monday, June 23, 2014

datacenter crap

A misogynistic mnemonic:

C13-C14 is what you need most of.  C13 is the female end, cuz females are odd.  Hurr durr.

C19-C20 are the other ones, for UCS and HP chassis.  Again, C19 is female.

C14-C15.  Well, there's a notch in the C15 side.  For 4500s and other boxes that think they're going to get hot.

more cisco 4500s in a couple of weeks

Going to run and set up another set of 4500-X switches for a customer in the next couple of weeks.  This is my 3rd set.  I suppose I'll document that for the benefit of the world.

Initial thoughts: always check your airflow, your lead time, and your power cables (c14-15)

CCDP SWITCH thursday

Last test I need for CCDP.  Mainly just poking at the internet for topics and sample questions/labs.  This is a lot of my daily driving at work so I'm not too concerned.

next up, CCDE in August or November, or, maybe VCP->VCAP.  Depends on which impacts employer's vendor relationship most.

run faster

did my 4 mile "from-the-office-to-enger-and-back" @ 9:45 avg pace.  felt good.

ordered a new set of inov-8 trailroc 255 (3rd pair in a row).  Every pair of them I've had is like putting on well worn glove.  It's absurd.  I moved from roclite 315s (after 3 pairs) which required some break in time.  last year I got my new set of trailrocs ~1 week before the curnow tail marathon and went for I think a single 5 mile run in them before taking them out for 26.  My feet were unbothered.

TL;DR, the inov-8 trailroc 255 is the best trail shoe I've ever come across (for me, and what I do).