Hello all, it’s been a while since I posted content here on my own blog, but I do regularly write for several other blogs, including IBM developerWorks Open, IBM OpenTech, Bluemix Dev, and Thoughts on Cloud.
Here are a few recent entries:
- Upcoming open tech conferences: Cloud Foundry, OpenStack, and Docker
- IBM Research talks cloud innovation at OpenStack meetups.
- IBM contributions to OpenStack go beyond the code.
- Cross-origin resource sharing for Bluemix APIs.
- Learn about cloud (or share your expertise) at a local meetup.
If you’re interested on my take in various areas of cloud computing – particularly in the realm of open source – add those feeds to your reader.
Update: A newer version of this post has been published to the IBM Bluemix blog.
For example, if you push an application to Bluemix, the name you provide will be prepended to .mybluemix.net resulting in an address such as:
To illustrate the problem and the solution, consider the simple Ajax application here:
However, if you click the blue box, you’ll initiate a call to a different servlet on that host:
This time the Ajax call will successfully consume data from the service, because the HTTP headers allow services from a different domain to access the servlet.
"POST, GET, DELETE, PUT"
If you need to allow access to all client hostnames, replace the whitelist with a wildcard:
I used Java in this example, but the same HTTP headers apply whether you’re using Ruby, Node.js, PHP, Python or any other runtime.
This week presented yet another opportunity to suggest a proposal to rename the Washington Redskins to something less controversial. As I see it, the “Washington Americans” makes the most sense.
It removes a racial slur from the name, expands the appeal of the team to represent the capital city (as a kid, I thought the team hailed from Washington state), and it requires little – if any – change to the existing uniform and logo.
I’m not sure if I’m the first one who came up with the idea, but I’ve sent messages via the redskins.com feedback form a couple of times over the past 10 years.
Congrats on the win today, and good luck next week at Seattle.
I just wanted to share my thoughts on your team name. I enjoy the history of the team, and the logo and colors. However, every time I hear the word “redskin,” I cringe (and it’s not just because I’m a New York Giants fan :).
My suggestion is to seize the opportunity and rename the team the Washington Americans. You would honor both native-American heritage, and unify that with your home in the nation’s capital.
Just a suggestion. And again, good luck… Unless you face the Giants in the NFC Championship. :)
I wrote a similar note about four years ago through redskins.com, and after watching the prime time Sunday night game last night, I thought I’d write again.
I wanted to share my thoughts on your team name. I enjoy the history of the team, and the logo and colors. However, every time I hear the word “redskin,” I cringe (and it’s not just because I’m a New York Giants fan :).
My suggestion is to seize an opportunity and rename the team the Washington *Americans* without a change to logo or team colors. You’d continue to recognize native-American heritage and team history yet also strengthen the team’s association with your home in the nation’s capital.
Furthermore, by using the name “Americans” by itself, without any hyphenated prefix suggesting exclusion or exception such as “Native-,” makes a statement that all US football fans are united as a single nation with a common history.
Of course, this is just my suggestion. But, in what’s looking to be an off season full of change, I think you have a golden opportunity to break with a negative aspect of the past and look to a greater future of the franchise here.
If you could float the idea by Daniel Snyder I’d very much appreciate it.
I’ve also shared the idea a couple of times on Twitter to a positive reception.
— Captain SaveAHoe (@DrSeaBishop) May 29, 2014
— Dave Winer ☮ (@davewiner) October 30, 2013
Putting aside whoever it was that first came up with the suggestion to rename the team to the Americans, it’s at least a positive starting point to find common ground in this controversy.
It addresses the most offensive part of the name, reduces the cost of change to logo and uniform, and it expands representation of the city and the sport of American Football during this dreadful onslaught of World Cup “football.” :)
I’ve submitted two abstracts for the OpenStack Atlanta conference that happens in May.
- Building the right infrastructure for your OpenStack workloads
After this presentation, you will have a firm grasp of the hardware (and costs) required to build your own OpenStack cloud and the confidence to get started immediately.
- Optimizing OpenStack for large scale Cloud Foundry deployments
After this presentation, you will have a strong grasp of what it takes to optimize OpenStack for Cloud Foundry and a starting point for deploying your own massively scalable PaaS clusters.
The OpenStack project is interesting in that it allows members of the community to weigh in on the topics they’d like to see at the conference.
If you like my presentation topics, please consider voting for them (ideally with 3 stars: “Would Love To See This!”).
To vote, you need to be a member of the OpenStack Foundation. You can join as an individual member for free.
The community review period ends on March 3rd, so please vote today!
IBM recently announced an open cloud architecture, based on OpenStack at the Infrastructure-as-a-Service (server, storage, and network) level, and on Cloud Foundry at the Platform-as-a-Service (runtime, framework, and database) level.
The partnership follows a fifteen year trend at IBM. This strategy to start with – and contribute back to – open source projects benefits IBM, its customers, and the community itself.
- By building on top of an existing open source foundation, IBM can focus its efforts on higher level services tailored to specific customers.
- By generating interest in the technology – and dedicating employees to the open source project – the community and its software is strengthened.
I’m proud to be a part of the work at IBM to build our next generation PaaS on top of Cloud Foundry. We’ve already got 1,000 IBMers running 1,200 apps on it, and we’re growing fast.
As with Apache, Linux, Eclipse, and OpenStack before it, I have have high hopes for Cloud Foundry. It’s good news for IBM customers, and everyone else who can benefit from a free, open source PaaS.
This post is my own and doesn’t necessarily represent IBM’s positions, strategies or opinions.
The NFL’s conference championship (semifinal) games always capture my imagination.
In many cases, it’s where the two best teams in the league face off, even if they still move on to face a weak opponent from the other conference in a largely ceremonial Super Bowl. Most of the San Francisco 49ers and Dallas Cowboy match ups from the early 1990s fall into this category. So these conference games represent the de facto league championship game.
In other cases, there are some teams that just can’t catch a break, like the Cleveland Browns or New York Jets, despite numerous, and often successive, championship game appearances. Without at least a Super Bowl appearance, these teams fall by the wayside of NFL history.
The forgotten championship
In all cases, the loser quickly disappears from the public’s memory – unlike the Super Bowl participants who have at least a moment’s glory on the national stage – despite an excellent season up to that point.
Do you remember how dominant the Browns were in the late 1980s? Or the Los Angeles Rams in the late 1970s?
A second chance at three hours
I often contemplate what NFL history could have looked like, had the NFC and AFC championship games gone the other way and the losers instead advanced to the Super Bowl.
See the full results below, starting with the 1970 season, with the winner shown in bold. I assume the conference that won the real Super Bowl also wins the alternate match up, though admittedly this is unlikely in several match ups. My observations follow the results.
|Super Bowl||AFC team||NFC team|
|V||Oakland Raiders||San Francisco 49ers|
|VI||Baltimore Colts||San Francisco 49ers|
|VII||Pittsburgh Steelers||Dallas Cowboys|
|VII||Oakland Raiders||Dallas Cowboys|
|IX||Oakland Raiders||Los Angeles Rams|
|X||Oakland Raiders||Los Angeles Rams|
|XI||Pittsburgh Steelers||Los Angeles Rams|
|XII||Oakland Raiders||Minnesota Vikings|
|XIII||Houston Oilers||Los Angeles Rams|
|XIV||Houston Oilers||Tampa Bay Buccaneers|
|XV||San Diego Chargers||Dallas Cowboys|
|XVI||San Diego Chargers||Dallas Cowboys|
|XVII||New York Jets||Dallas Cowboys|
|XVIII||Seattle Seahawks||San Francisco 49ers|
|XIX||Pittsburgh Steelers||Chicago Bears|
|XX||Miami Dolphins||Los Angeles Rams|
|XXI||Cleveland Browns||Washington Redskins|
|XXII||Cleveland Browns||Minnesota Vikings|
|XXIII||Buffalo Bills||Chicago Bears|
|XXIV||Cleveland Browns||Los Angeles Rams|
|XXV||Los Angeles Raiders||San Francisco 49ers|
|XXVI||Denver Broncos||Detroit Lions|
|XXVII||Miami Dolphins||San Francisco 49ers|
|XXVIII||Kansas City Chiefs||San Francisco 49ers|
|XXIX||Pittsburgh Steelers||Dallas Cowboys|
|XXX||Indianapolis Colts||Green Bay Packers|
|XXXI||Jacksonville Jaguars||Carolina Panthers|
|XXXII||Pittsburgh Steelers||San Francisco 49ers|
|XXXIII||New York Jets||Minnesota Vikings|
|XXXIV||Jacksonville Jaguars||Tampa Bay Buccaneers|
|XXXV||Oakland Raiders||Minnesota Vikings|
|XXXVI||Pittsburgh Steelers||Philadelphia Eagles|
|XXXVII||Tennessee Titans||Philadelphia Eagles|
|XXXVIII||Indianapolis Colts||Philadelphia Eagles|
|XXXIX||Pittsburgh Steelers||Atlanta Falcons|
|XL||Denver Broncos||Carolina Panthers|
|XLI||New England Patriots||New Orleans Saints|
|XLII||San Diego Chargers||Green Bay Packers|
|XLIII||Baltimore Ravens||Philadelphia Eagles|
|XLIV||New York Jets||Minnesota Vikings|
|XLV||New York Jets||Chicago Bears|
|XLVI||Baltimore Ravens||San Francisco 49ers|
- The New York Giants never reach the Super Bowl. The New England Patriots appear only once (and win).
- The Vikings, Lions, Eagles, Chargers, Oilers, Panthers and Seahawks each win at least one Super Bowl.
- San Francisco still wins 5 Super Bowls, but also loses 3 times. Oakland wins 5 (including 3 in a row, which has never happened in Super Bowl history) and loses two.
- The Browns make it to 3 Super Bowls but lose all of them. The Jets make 4 but win only one.
- There is an expansion team meeting the year after both new teams joined the league, when the Carolina Panthers defeat the Jacksonville Jaguars.
- The Pittsburgh Steelers and Dallas Cowboys still meet two times.
- The Bears go 3-0, representing the best overall Super Bowl record.
- The Buffalo Bills still don’t win a game.
- There are lots of interesting local rivalries. Los Angeles and Oakland, San Francisco and Los Angeles, Pittsburgh and Philadelphia, Philadelphia and Baltimore, Jacksonville and Tampa Bay.
It would also be interesting to consider alternate MVPs, though I’d limit this to quarterbacks, since defensive or special teams players reflect a strong individual performance rather than the overall team strength. Kenny Stabler and Joe Montana would probably lead the MVP tally.
Next Tuesday, June 26th, I’ll be speaking at the New York PHP user group about the project I led to bring the Zend Application Fabric onto IBM’s on-premise private cloud rack, PureSystems, and onto IBM’s public cloud, SmartCloud Enterprise.
I’ll describe the Zend Application Fabric for highly available PHP clusters, and show how its topology is supported by scaling and failover policies built into the IBM platform. I’ll also show how it integrates with the DB2 based Database-as-a-Service.
At the core of the Zend/IBM system is an IBM virtual application pattern (based on the TOSCA standard) that specifies how virtual machines are layed out, which other VMs they should link (or react) to based on life cycle events, and when they should scale up or down.
You will learn how to activate the Zend pattern, customize the topology, set a scaling policy, monitor the infrastructure, tweak the Zend configuration, view IBM elasticity and fault tolerance in action, and perform repeatable deployments using a template.