jump to navigation

Machine Learning Advances.. January 8, 2015

Posted by Marty Wolfe in Uncategorized.
add a comment

A really great Ted talk on how machine learning algorithms are seemingly moving towards AI.  I know it’s a loaded term, but once you watch what can be done in mere minutes with mounds of data, it goes well beyond “big data” and “analytics” as we currently use the terms


Docker vs. Rocket January 5, 2015

Posted by Marty Wolfe in Uncategorized.
add a comment

Docker is one of the most interesting capabilities out there. I see it as a way to be hypervisor agnostic. This is important since it enables “Hybrid IT” in a real-world way. You also need a network fabric across various providers of course, but Docker gives you the upper layers of the solution.

There’s a lot of discussion on how CoreOS has a viable competitor and that the Docker deployment model is getting to complex. Combined with some recent security flaws in the Docker platform you have to be cautious. I still see this though as the right way to go.

The CEO of Joyent has a good blog post..


.. where he lays out how to think about this fork that’s occurring. Keep your eye on this since it’s gonna play out in the first half of 2015.

Interesting Article: “.. How To Hide From The NSA” January 5, 2015

Posted by Marty Wolfe in Uncategorized.
add a comment

It’s important to keep track on how to secure your communications. Especially important in the corporate world.


Lotus Notes Temp Directory on Mac OSX December 8, 2014

Posted by Marty Wolfe in Uncategorized.
add a comment

I now have my Macbook Pro Retina (late 2013) model.. I bought it refurb.. and it’s great.

Here at IBM we use Lotus Notes v9 and one of the constant challenges is where Notes will store temporary files.  On the Mac it is just as convoluted as on Windows, but I found this blog post which helped me find a recent file (thought I had lost it.).  Worth bookmarking..


Knowing If A Workload Should Move To The Cloud November 20, 2014

Posted by Marty Wolfe in cloud.

After going through many IT transformations, migrating many different types of applications “to the cloud”, I took all those experiences and created a checklist.

Lots of checklists out there of course.. but I always come back to these 10 core points. So here’s my list, hope it helps, and I welcome your comments and recommendations.

In this list, each numbered item is a “domain” or “focus area”.. essentially a topic you must address and question when trying to figure the impacts of moving a workload to the Cloud. You might find that it’s just too challenging or too much trouble or you’ll find that even though there’s a good amount of effort, the overall value to your group, organization, or business outweighs the effort required.

These are not in order of importance.. they are all pretty important. Stream of consciousness thinking based on having done this many times.

Security and Compliance Focused on topics such as encryption, key management, regulatory compliance, compensating controls, intrusion detection, and auditing

  • Does the data need to be encrypted in flight or at rest (or both)? Do the transactions need to be encrypted?
  • Who will own management of encryption keys?
  • What types of auditing (e.g. level of detail or specific compliance) need to be supported once the workload is deployed?
  • What level of monitoring needs to be recorded and stored?
  • Will special intrusion detection (at the network, storage, and compute layers). What are the regulatory and/or compliance requirements (including FDA, HIPPA, PCI, FFIEC, etc.)?
  • Does the data need to stay within country and/or locale and does this include both application data and management system data?
  • Now that we are moving into the Cloud, are there compensating controls and/or reporting that can be put in place to achieve same result?
Capacity Capacity requirements (the initial capacity needs) and capacity management (the needs during steady state) are some of the first things to understand including how much compute, storage, and network capacity is required

  • What initial capacity is needed to get the system initially up and running (understanding that you can scale up later) ?
  • What is the steady state capacity needed?
  • If the workload is re-engineered / re-architected when moving into a Cloud environment, how do the capacity requirements change?
  • What are the different levels of capacity needed for development, test, QA, and production?
Connectivity The method for connecting from the existing enterprise network to a Cloud provider (like IBM’s SoftLayer) needs to be defined

  • What amount of bandwidth will be required for development, test, QA, and production deployments?
  • Are clients on the current network allowed direct workstation VPN client connectivity to an off-premise Cloud or must they go through a corporate VPN?
  • Is an IPSEC VPN required between the client and the IBM network?
  • Will the current environment and the target (cloud) environment be co-located in the same data center?
  • Will parts of the workload/application be located in different cloud data centers and across different Cloud providers? (e.g. leading to Hybrid Cloud)
Services Management (ITSM) Defining how incidents, problems, and changes (requests) are handled now that the workload will be running in the Cloud

  • What is the process/workflow needed to support incident, problem, and change management once a workload is deployed into a Cloud environment?
  • How do these processes need to change in development, test, QA, and Production contexts? (Experience tells us there will surely be changes needed especially in a “Hybrid Cloud” scenario
  • Monitoring – How will monitoring be performed and who will have access to the monitoring data?
Managed Services This topic is focused on providing management and oversight and is tightly linked to services management

  • Does corporate IT want full management from a vendor or partial “a la carte” management? (e.g. such as software patch management for a specific set of Cloud workloads, etc)
  • Will the vendor’s managed services (outsourcing) team be managing deployment of workloads to a single Cloud vendor or multiple ?
  • Metering – How will the use of the Cloud be measured? How does the client wanted to be charged? Will there be a need for an internal chargeback within the client’s environment?
  • Will the managed services vendor have visibility to the data or only ping, power, and pipe?
Performance Determining the level of performance (scalability, reliability, availability, etc) required once in the Cloud will guide many other decisions

  • When moved to the Cloud, will the same level of performance be required in development, test, QA, and/or production use cases?
  • How is performance measured?
  • Who will execute performance testing and will the same scripts and use cases be used once the workload is moved to the Cloud?
Roles and Access Focused on consumability and access of the workload once it’s deployed into a Cloud environment

  • Who will be accessing the workload? business users? IT administrators? Developers? Third party vendors?
  • How will each user group access the workload? via API? via UI? via Reporting? via status provided by S.O. ?
  • How will access and status of the workload be detemrined? Who will have access to monitoring data and how will they access it?
  • How will ID’s and the management of user IDs be managed and governed?
Data The ownership and location of data is vitally important

  • What is the location of data and how is that different as it relates to development, test, QA, and production?
  • Will the data be located separately from the application? (if yes, does that require it’s own secure connection?)
  • Is the data in scope of any specific compliance and/or regulatory requirements?
  • Who will own the data?
Deployment Model Where will the workload be deployed?

  • Is off-premise or on-premise required?
  • Does the workload map to existing items in the CMS or SoftLayer catalog?
  • Will this be BYOL?
  • Will it be deployed to a single or multiple environment(s)?
Workload Architecture and Integration The architecture of the workload and it’s external dependencies are important to know up front

  • Does the workload require integrations/connections to systems or data sources in other cloud or non-cloud environments?
  • Is the architecture of the workload ‘cloud ready’, ‘cloud native’, or requiring dedicated hardware, network, and storage resources?
    Will the application and data be separated or co-located?


The 7 Patterns of Cloud Migration October 10, 2014

Posted by Marty Wolfe in Uncategorized.
add a comment

An article I posted in 2013, still holds true.


Encrypt Your gmail !! October 3, 2014

Posted by Marty Wolfe in Uncategorized.
add a comment

In addition to gmail’s existing https default, there’s more to do to secure your messages..


We Used Pencils In Years Past.. January 8, 2013

Posted by Marty Wolfe in Uncategorized.
add a comment

I was looking through an old tackle box I used to store various electronic parts and such while in engineering school.  One of the things I found was a flow chart ruler given to me in the early 80’s by a retired nuclear engineer.  I was quite young, and didn’t even consider I would ever work at IBM.


Tracking the Trackers. June 9, 2012

Posted by Marty Wolfe in Uncategorized.
add a comment

Pretty interesting talk on tracking technology and methods.

Maps of my travels.. May 20, 2012

Posted by Marty Wolfe in Uncategorized.
add a comment

I entered the foursquare .kml feed into Google Maps and it built a picture.  Quite neat.









Click for bigger version.