Well?

I'm down.

Potential listener here...

Tag for tomorrow.

Bump, because it's tomorrow.

Tomorrow is tomorrow.

You shut your whore mouth!

I know there was a thread a while back about contributing for a talk or something..is this part of that, or not related at all? I just got out of the joint from a 90 day time out so i don't remember.
 

Just a random idea that popped in my head.

A podcast might be easier to pull off as the conference idea proved to be challenging because everyone has really difficult schedules to work with.

Yep. Plus, we can maintain persec.

Tag again for tomorrow.

I would listen

Until that day then?

I would also subscribe.

We could make it a half/half tech and guns discussion or a straight up tech discussion.

I'd love to help folks secure their shit, and pass along some gun knowledge too.

That being said, it would be awesome to work with Subnet, given that he don't put with no shit, and would call me out when I'm wrong - which is often.

It'd be even more fun drunk.

I'll ponder these potential show notes Tomorrow™.

Tomorrow is tomorrow.

Truth is, I'm honestly not sure how I want the show to go.

Well setup a meeting with your executive producer and hash it out.

Oh God.  No VoIP discussion.  I seriously hate the fuckers that have anything to do with me having to talk on the phone.




I'd love to talk about my current adventures in enterprise SDN/Cloud R&D for a household-name IT company but I'm not sure how much I'm allowed to discuss.  I need to ask that question. There is some SERIOUSLY cool shit coming down the pipe (pun intended) for those of you/us involved in enterprise networking/cloud/infrastructure and data center operations. Having 10 GbE and 40 GbE fabrics at the low/mid-end and the upper end being racks filled with pre-production/prototype high density 100 GbE switches just for scale, performance, and load testing of controllers and apps is damned cool.  That's just one L2/L3 aspect of the overall R&D infrastructure.  We are building and testing the complete data-center/cloud environments as they are envisioned by the various industry working groups and alliances.

Working on projects and technologies with partners at Microsoft, VMWare, RedHat, Websense, Intel, Qosmos, Radware, Aruba, etc. has really opened my eyes to the fact that all of the *aaS's, security, networking, virtualization (and bare metal clouds), traditional infrastructure components, OS's, and so on are changing and becoming more interoperable in some fundamental, powerful, and fascinating ways.

I've also transitioned from management back to infrastructure architecture/engineering and I'm a happy happy boy for it.  So, my outlook (for now) has gone from jaded and cynical to wide-eyed and motivated for the first time in well over a decade.

***I really really hate the term "cloud".  I have to use it as a descriptor of complex and converged environments daily though....

I would be down. Maybe a recorded google hangouts type chat we could have a panel discussions on a particular topic with a moderator?

Hangouts actually might be a good idea.  Lots of options on how to do it.

Yep. We've used them to great effect on these types of things before. I was never involved in the setup though.

They sound like shit.

yeah, you would care about that.  

I think most of the rest of us wouldn't be too worried about it...  

I don't think there is much setup.  Somebody send me a gmail address and let's see what it takes to get this up and running.

tag for updates..


I'd certainly be interested in listening to the discussion/lecture (whichever form it takes)..

We seriously need to hang out.

First tech show idea - how to make sure your podcast has polished, professional audio and doesn't sound like shit.

And that's why you're the man for the job. I know less than zero about audio quality.

Honestly we solved that problem with my TS server, at least I thought.

Here we go with Codecs and compression ratios and protocols and all that stuff no one understands but the voice guys.  Secretly, we're all a little curious how it all works.  I predict it will be the least admitted-to podcast download ever.

I can't argue with that at all.  

I'm more a "get the information out" kind of guy -- don't spend a lot of time on the presentation or the polish (though I know how to), but get the info out as the priority.

Same.

You know you're a geek when your reports are in plain text files.

My reports are distributed as L^AT_EX source. And they come with a Makefile.

Come to California and I'll take you in to the development data center labs.  There's an all-white (even the Chatsworth cabinet is 100% white ) SAN prototype that is filled with prototype controllers and some kind of "new" SSD based drives that are supposed to be considerably faster than anything on the market at any price level.  A global Japanese company is working with our storage teams on it and they have moved all the controller engineers and software developers to CA while it's being built and tested.  It's a couple years from market.  I want to see how much porn I can intercept and transfer to it and how fast.



I have a feeling I'll be coming back here and deleting this but oh well.  I have never seen a single sign or confidentiality document about any of the stuff I've mentioned.

I also need infrastructure engineers that can design, build, configure, and deploy the following at a very high level of expertise:

Linux-based Infrastructure Services
High level knowledge of IP network design and concepts, subnetting, supernetting/CIDR, VLSM, etc.
SAN (Fibre Channel, iSCSI, and physical/logical switching fabrics and software/firmware).  Need to be familiar with Brocade, Cisco, HP, NetApp, EMC, Hitachi etc.
Routing and Switching - Familiarity with Cisco, HP/H3C, Brocade, Aruba, CLI for all, support, and configuration into VERY advanced topologies and requirements (often global in scope)
VLAN trunking via 802.1q along with stack/bond/aggregation concepts like IRF and LACP/LAG and to a lesser extent EtherChannel port groups.
IPS/DPI/Firewalls (Cisco, Tipping Point, Juniper, Citrix, ArcSight, etc...), software/app plug-ins for SDN, and general security best practices knowledge.
Network traffic inspection, monitoring, and analysis using a variety of tools from Wireshark up to proprietary and custom apps.
Traffic simulation - Various IXIA models.
ESXi/Vsphere and Hyper-V with some Xen and KVM sprinkled in.  
Mininet and similar network simulators to validate flows and controller revision code before loading to data center regression lab systems.
Knowledge of Python a plus
All aspects of Windows Server technologies and infrastructure components/services (the usual, AD, DNS, DHCP, WSUS, SCCM, etc.)  focusing on 2012 and 2016 with some legacy 2008 VM's and physical boxes.
Familiarity with Ubuntu Enterprise offerings, RHEL, HLinux, UX, etc.
Familiarity with concepts of development stages, DevOps, troubleshooting, bug identification, monitoring, and an ability to work closely with software developers, engineers, and testers
OpenStack **
Knowledge of OpenFlow a great thing **
Knowledge of OpenDaylight a great thing **

**  Not necessary but the hire will become extremely knowledgeable if not a SME just by daily interaction, exposure, and training.

This is just what I could come up with off the top of my head.  There's a lot more.  It is easily the most intense and large-scale series of operational projects and data-centers I've ever seen.  We are ordering $4,000,000 of equipment per quarter just to keep up with the variety of customer environments that we have to simulate and troubleshoot.  We also maintain sandboxes for the biggest customers and partners for them to trial run all their network and application delivery systems with custom/new software before they deploy it to their production environments.

In a nutshell, if it's used in Enterprise infrastructures, topologies, stacks, data-centers, public/private/hybrid clouds, carriers, you name it, we have to be able to build and test it in those environments on their flavor of hardware.  One day it's FibreChannel, Brocade and HP C7000's along with several racks of L2/L3 and VMWare systems simulating large LAN/WAN environments and the next day it's Verizon regional/sub carrier networks and 14 racks of top end network and com gear along with the physical and virtual systems to support their applications and traffic concerns with the next generation of network and software capabilities.

It's probably time for me to stop hijacking....  I'm just into what I do.  No more monkey suits and expensive shoes.  The learning curve has been STEEP but I've never enjoyed myself more.



ETA:  Oh yeah... MRV L1 switches are the bees knees.  I want to move to them extensively but the 6 figure price tags are a lot to swallow for being able to reconfigure entire layer 1 structures (on the fly) remotely and with control software/scripting.  No more physically moving/terminating, plugging fiber, copper, and DACs, in the DC's.

I'm not quite that bad.  I've done it before, but not as a rule and not for a long time.

It was so bad that I even took my notes that way. My automata prof called me out on it one day (he always used overhead transparencies and a marker) and said "What is it that you're always typing?" "Hang on, lemme render it"

Ok, now you're just being a mega-nerd just because....well... you can.

He asked me if I was interested in taking the official notes for the class. I said "What's it pay?" "Uh.. nothing" "Nope."

is today tomorrow? I would try to listen on the reg if it was a scheduled time. preferably in the later evening weeknights.

We seriously SERIOUSLY need to hang out.

I'd have some serious studying/labbing to do, but i bet i could squeak by until i got up to speed.





 

Would I have to move to California?  

As an avid podcast consumer with a long commute, I would say that good audio quality is important when listening in a car.  Some of my favorite shows are recorded in potato quality and make it very hard to hear while driving.  

Any show that has guests record their own audio track (when possible) sound waaaay better than the skype/hangout/whatever track.  Then compress that shit to the max so I can hear it.

No Agenda uses Skype to link the hosts and they have the best audio quality of just about any podcast I've listened to.