14
Platform for Desires Do not seek to follow in the footsteps of the wise. Seek what they sought. Matsuo Basho

Edmund Sutcliffe - Who do you think you are: Why Naming is Important?

Embed Size (px)

Citation preview

Platform for Desires

Do not seek to followin the footsteps of the wise.Seek what they sought.

Matsuo Basho

Pets V Cattle

Concrete Lifebelts

Hero Culture

Identify Everything

If the names are unknown knowledge of the things also perishes

Carolus Linnaeus

Naming Standards – Current Direction

– Several inconsistent namespaces

– Silo-ed fiefdoms of control and understanding (Heroes)

– Totally human processes

– No shared understanding

– Lack of agility

– No consistent abstraction model

– Results in - Operating Cost!

Intel DeviceNaming

Windows SystemNaming

ServiceNaming

ClusterNaming

ApplianceNaming

CertificateNamingApplication

Identity

Ontology

Element Component of a device, which will not function without the device

Device Something physical which can be switched on/off

Host An instance of an OS (IOS, Unix, Windows, VMWARE ESX..)

File System A repository of organised state presented as files and directories.

Cluster n+1 hosts that increase availability for the instantiation of capabilities

Application A collection of program binaries to perform a specific function

Package Ability to perform designated activities to achieve specified results

Naming Standards – Current Direction

– Enterprise wide naming standard

– Encompassing all components

– Physical & Logical

– Consistent Rules

– Fixed format to enable automation

– Service names that are easily re-pointed

– Fixed relationships

– DNS sub-domains for location and environment

– By looking up DNS you can see what host or cluster a service is on

A-Record Element

A-Record Device

C-Name Management Interface

A-Record Host

A-Record Cluster

C-Name Service

OS Username

Package

OS Groupname

Application

OS Username is a member of OS Groupname

C-Names linked to relevant DNS A-Records

Suffix added for host management

Servicename and package identity name are the same

Worked Example

Naming Standards – ImplicationsImplications of not doing this

● Un-necessarily complex support and troubleshooting

● Un-necessary complexity in change events

● Inflexibility in the system linkages

● Many hands to do light work!

Implications of doing this

• Short term effort to syndicate this change (architecture)

• Short term effort to implement this change (mostly implementation teams)

• Long term efficiency benefits

• Long term system flexibility improvements

• Reduced inertia to change

• Decreased operating costs

• Better understanding of relationships

Standardize Measures

If the names are unknown knowledge of the things also perishes

Carolus Linnaeus

Classification of Data

Identity tells you whereClassify EventsReport on the Classifications Unclassified Events mapping

Federate Logging

Event ClassificationsHardware Hardware and environmental: Network Errors, Device

Up, Temperature

OS Virtualized OS resources: Paging Rate, CPU and Memory Usage, allocate swap/create processes

Module Code and Runtime : unhandled exception, malloc failure, unable to write to file

Data Capability level data:. null account, divide by zero, unable to find key, unable to find file

Session Component interaction: Couldn’t connect, unable to open ODBC, Session Dropped

Transaction Logical units of work: these are of monetary value or of regulatory interest

Security Exception event; seen across all classifications.

Edmund J. Sutcliffe

<[email protected]><http://panic.fluff.org>+44 (0) 7976 938841