Dispatches¶

Introducing the Platform Services Controller Interface in vCenter Server 6.0 Update 1

Back in March, we introduced vSphere 6.0 and the new architecture for vCenter Server. With this new architecture you learned about the Platform Services Controller, a new functional component of vCenter that moves beyond just Single Sign-On to include additional platform services such as:

• Licensing Service
• Certificate Authority (VMCA)
• Certificate Store (VECS)
• Lookup Service for Component Registrations

In the 6.0 release, administration and configuration of the Platform Service Controller was primarily performed by an SSH session, the vSphere Web Client and selecting the node in System Configuration, or through the Direct Console User Interface of the appliance.

In vCenter Server 6.0 Update 1, we're excited to introduce the next stage of the administration with the Platform Services Controller Interface, a fully HTML5-based interface to administer and configure many of the services that run on the PSC.

Confessions of an Energy Consciousness Mind

I have a confession.

My data center kit has been using too much energy.

Having kit available at my disposable is great, but I have been wasting this resource when it's not required by my workloads. And if there's one thing I try to be conscious of, it's energy consumption. Just ask my kids who I chase from room to room turning off lights, screens, and the lot when they aren't using them.

But why not in the data center? Did you know that hosts typically use 60%+ of their peak power when idle?

Until recently, I had overlooked configuring my kit to use the vSphere Distributed Power Management ("DPM") feature to manage power consumption and save energy.

With the release of vSphere 6.0 it's a good time to review and take deeper look into the capabilities and benefits of this feature.

Customization of vRealize Automation 6.2.x Email Notifications

User Experience ("UX") focuses on the intimate understanding of your users. What is it that they need or desire, what do they value, what are their abilities, as well as their limitations?

As you embark upon the journey to the software-defined data center (SDDC), think and architect in terms of the user experience in addition to "boxes and arrows."

• What are the desired UX outcomes for those consuming the service(s)?

• Have you considered the UX in terms of its usefulness, usability, desirability, accessibility, credibility, and its value?

In addition to fundamental tenant and business group designs, entitlements and service catalogue designs, one such area for UX consideration is the messages provided to those consuming services of the software-defined data center.

For a moment, imagine you are providing automated infrastructure delivery to multiple business segments of a large media and entertainment organization, each with their own distinct brand. The segments are built upon their individual brand and identity.

• Do you centrally brand the service that you offer or do you tailor the service to each tenant business segment?

• How would this change if instead the services were used to provide automated infrastructure delivery only to your IT Operations team and not direct end users?

On an Organization's Cultural DNA

Have you ever stopped to think about what makes working for your organization appealing?

Perhaps you have wondered why you feel that you are on a different frequency than the rest of the organization?

When Yahoo recently announced that Marissa Mayer would become the Chief Executive Officer there was a great deal of commentary - both speculation and excitement. One remark from Netscape co-founder Marc Anderson I found to be particularly insightful and compelling. Anderson stated that Yahoo had appointed a "product-centered CEO" in Mayer rather staying the course with an interim "sales-centric CEO."

Anderson's insight highlights the fundamentals of what an organization wants to be and the how its culture supports the philosophy. It's apparent in every industry that there are successful organizations with different or even unique philosophies and cultural structures. Take for example the "technology market' in which EMC is known for its sales culture; Google for its scientific engineering culture; Amazon for its supply-chain culture; HP and Xerox for their operational cultures; and of course, Apple for its design and marketing cultures. I have personally have customers in markets that have cultures defined by customer experience as well as healing ministries.

On Principles of Applications

As discussed previously, principles are high level statements of the fundamental values that guide business and technology decision-making and activities and are the foundation for architecture, standards, and policy development. Principles are stable enough to withstand technological and process changes but timely enough to maintain a clear relevancy with markets, policy, program, and management changes.

Principles consist of the principle statement, rationale, and implications. Though the wording for principles should remain consistent, the rational and implications will evolve over time, as an organization responds to factors such as the current IT environment, internal initiatives, external forces and markets, and changes in mission, vision, and strategic plan.

In my prior role as an Enterprise Architect, I used the following Principles for the foundation of the Enterprise Applications. Even with the changes in the industry since I last wrote these  - public, private and hybrid cloud computing, dev-ops, etc - these principles have been steadfast.