<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	
	<channel>
		<title>SjaakLaan.nl</title>
		<link>http://www.sjaaklaan.nl/index.php</link>
		<description>Visie op IT infrastructuur, architectuur en security</description>
		<language>en</language>
		<managingEditor>sjaak.laan@gmail.com</managingEditor>
                <copyright>Copyright 2010</copyright>
		<generator>Pivot Pivot - 1.40.1: 'Dreadwind'</generator>
		<pubDate>Thu, 26 Aug 2010 10:46:01 +0200</pubDate>
		<ttl>60</ttl>
		
		
		
		
		<item>
			<title>Revised Infrastructure Model</title>
			<link>http://www.sjaaklaan.nl/pivot/entry.php?id=142</link>
			<comments>http://www.sjaaklaan.nl/pivot/entry.php?id=142#comm</comments>
                        <description><![CDATA[ <p>
In <a href="http://www.sjaaklaan.nl/pivot/entry.php?id=4"  target='_blank'>one of the first posts</a> on this website I presented an Infrastructure Model. For <a href="http://www.sjaaklaan.nl/pivot/entry.php?id=141"  target='_blank'>the book I am writing</a>, this infrastructure model is used as a basis for describing infrastructures. Because the original infrastructure model was created back four years ago i felt is was time for an upgrade on the model. This article (as part of&nbsp;my book) describes the revised infrastructure model. 
</p>
<p>
No generally accepted definition of IT infrastructure exists and many people have different ideas about what IT infrastructures consists of. For developers, infrastructure is the platform to run their applications on. For network managers, infrastructure is the collection of all network equipment. For systems administrators, infrastructure is all equipment they manage and for the architect it is the basic layer to build the business services on. Because everyone has a different idea on what infrastructure is, we introduce the following definition of IT infrastructure: 
</p>
<p align="center">
<em>IT infrastructure is the total set of foundation components that enables applications to function</em> 
</p>
<p>
The following model can be used to visualize the various components. 
</p>
<p>
<!-- error: You haven't included [[ thickbox:head ]] in your templates. --><p style="text-align:center;"><a href="http://www.sjaaklaan.nl/images/infrastructure_model_framework.jpg"  class="thickbox" title="" rel="entry-142"  target='_blank'><img src="http://www.sjaaklaan.nl/images/infrastructure_model_framework.thumb.jpg" border="1" alt="" title=""  class='pivot-popupimage'/></a></p>

<p>
(click to enlarge) 
</p>
<p>
This model shows the components from which an infrastructure is built (the horizontal planes). This stack of components is the basis on which applications can run. Part of the infrastructure is located in the data center, another part is located at the work place. 
</p>
<p>
Vertically, three infrastructure specific non-functional attributes are shown. These attributes are valid for every component in the infrastructure. The non-functional attributes are security, availability and performance. Although many other non-functional attributes can be defined, these three are almost always very important in infrastructure architectures. 
</p>
<p>
All parts of the infrastructure are maintained by performing systems management. 
</p>
<p>
<u><strong><em>Infrastructure components in the data center</em>&nbsp;</strong></u> 
</p>
<p>
<u>Facilities </u>
</p>
<p>
The basis of all IT is hardware that is located in a data center facilities. The facilities layer includes electricity and cooling, raised floors, fire detection and prevention, physical security, backbone cabling, etc. 
</p>
<p>
<u>Racks and enclosures </u>
</p>
<p>
Located in the facilities are server racks. These racks contain the IT equipment. Blade based equipment is located in enclosures that are placed in the racks. This layer encompasses cabling, patching, labeling, (redundant) power supplies, etc. 
</p>
<p>
<u>Servers </u>
</p>
<p>
Servers are the main components in any data center. They include CPUs, memory, local storage, BIOS, expansion slots and ports, etc. 
</p>
<p>
<u>Networking</u> 
</p>
<p>
The network is a very important part of any infrastructure. Dependent on the environment the network can be very complex. It contains routers, switches, NAT, Firewalls, WAN, LAN, dial-in, Internet access, VPN's, etc. 
</p>
<p>
<u>Storage </u>
</p>
<p>
Most servers have internal storage, but usually storage these days is external. The storage component contains DAS, NAS, SAN, FC-AL, iSCSI, etc. Also backup and recovery solutions, and ILM and ECM are part of storage. 
</p>
<p>
<u>Virtualization </u>
</p>
<p>
On the hardware the operating systems can be installed, but nowadays most hardware is virtualized first. The virtualization layer can be on machine level (creating virtual machines on which operating systems are installed), workstation virtualization (like VDI or terminal server solutions), storage virtualization (like disk arrays and virtual LUNs) and network virtualization (like virtual LANs - VLANs). 
</p>
<p>
<u>Operating Systems </u>
</p>
<p>
Virtual servers run operating systems (OS's). The most popular operating systems are Microsoft Windows, Linux, UNIX and Apple OSX. However, there are a large amount of other operating systems, usually meant for special purposes, like real-time operating systems, or operating systems for embedded systems. Part of this layer is the way the OS's are deployed, tuning OS parameters, as well as management of users, groups, rights and drivers. 
</p>
<p>
<u>Infrastructure services </u>
</p>
<p>
The infrastructure services layer consists of services like DNS, DHCP, Directory services, mail agents, etc. 
</p>
<p>
<u><strong><em>Workstations</em></strong></u> 
</p>
<p>
Workstations are the devices used by end users to work with applications. Workstations include PCs, laptops and mobile devices. 
</p>
<p>
<u><strong>Peripherals </strong></u>
</p>
<p>
Any hardware device remotely attached to a computer (either a workstation or a server) is called a peripheral. Typical peripherals are printers, models, scanners, fingerprint readers or CAM machines. 
</p>
<p>
<u><strong><em>Non-functional attributes (verticals) </em></strong></u>
</p>
<p>
<u>Security </u>
</p>
<p>
IT Security spans all components. IT security is a very large knowledge area. For infrastructure, it concerns mostly about technical solutions, like VPN, IDS, Access Control, Biometrics, Encryption, etc. Procedural security is mostly used in system administration. It spans creating users, access rights, and security demands for new hardware and software. 
</p>
<p>
<u>Availability </u>
</p>
<p>
Availability contains areas like backup and restore, Disaster recovery, Failover, high availability clustering, Load balancing and replication. 
</p>
<p>
<u>Performance </u>
</p>
<p>
The performance of an IT infrastructure is almost always very important and consists of areas like scalability, virtualization and high performance clusters. 
</p>
<p>
<em><u><strong>System Administration </strong></u></em>
</p>
<p>
An important aspect is the administration of the environment. This includes procedures for taking systems and applications in production, maintaining systems and troubleshooting. Usually ITIL is used as a methodology for system administration.</p> ]]></description>
			<guid isPermaLink="false">142@www.sjaaklaan.nl</guid>
			<category>default</category>
			<pubDate>Tue, 17 Aug 2010 00:00:00 +0200</pubDate>
		</item>
		
		
		
		<item>
			<title>Vertrouwen in enterprise architecten</title>
			<link>http://www.sjaaklaan.nl/pivot/entry.php?id=138</link>
			<comments>http://www.sjaaklaan.nl/pivot/entry.php?id=138#comm</comments>
                        <description><![CDATA[ <p>
<em>Enterprise architecten zijn pas echt van toegevoegde waarde binnen een onderneming als ze voldoende vertrouwen hebben van de business.</em> 
</p>
<p>
De business moet er zeker van zijn dat de enterprise architect luistert naar hun wensen en deze altijd als basis gebruikt voor het vormgeven van het IT landschap. Pas als de architect dit meerdere malen in de praktijk heeft bewezen te doen zal hij als vanzelf worden geconsulteerd bij wijzigingen in de business(doelstellingen). 
</p>
<p>
Natuurlijk is het de taak van de enterprise architect om de business ook te adviseren over de optimale inzet van IT voor het bereiken van business doelstellingen. Wensen vanuit de business leiden soms tot IT oplossingen die kostentechnisch (zowel op de korte als lagere termijn) niet meer in verhouding staan tot de business benefits. 
</p>
<p>
Het is de taak van de enterprise architect de business hierover te informeren en te zoeken naar meer effici&euml;ntere oplossingen.</p> ]]></description>
			<guid isPermaLink="false">138@www.sjaaklaan.nl</guid>
			<category>default</category>
			<pubDate>Fri, 06 Aug 2010 08:46:00 +0200</pubDate>
		</item>
		
		
		
		<item>
			<title>Book on Infrastructure Architecture</title>
			<link>http://www.sjaaklaan.nl/pivot/entry.php?id=141</link>
			<comments>http://www.sjaaklaan.nl/pivot/entry.php?id=141#comm</comments>
                        <description><![CDATA[ <p>
A&nbsp;few months ago I started writing on a book on Infrastructure Architecture. From the introduction text of the book: 
</p>
<p>
<em>With <u>Infrastructure</u> I mean all hardware, software and systems management needed to support IT applications. Infrastructure <u>Architecture</u> is the overall design of the complete IT infrastructure. </em>
</p>
<p>
<em>The book explains how infrastructure architecture works, the specific issues when designing and implementing IT infrastructures and how to address them. It provides practical solutions and examples for infrastructure architects and provides background information for IT managers, solution architects, system managers and others. </em>
</p>
<p>
<em>The book does not provide in-depth details on IT infrastructure components like servers, routers, switches and operating systems, nor does it explain details about protocols like TCP/IP, HTTP and other technical issues. Instead a more holistic view is chosen. All infrastructure components are described as one infrastructure ecosystem providing the fundament for applications running on it. </em>
</p>
<p>
<em>A short description of ITIL based systems management is provided, especially focused on managing the infrastructural parts of an IT system. </em>
</p>
<p>
<em>Infrastructures are complex by nature and provide many non- functional functions for building IT solutions on top of it. Non-functional attributes like performance, availability and security are key to a good infrastructure that provides the basis for running high performance, highly available and secure applications. Apart from these three most important attributes all other non-functional attributes of the ISO 9126 norm are described in this book, including tips on how to address them in an infrastructure design. </em>
</p>
<p>
I found that there is no such nook available on the market today.&nbsp;Writing this book provides me with the opportunity to publish the knowledge and experience I have gained over the years. Apart from that much research is done to refresh my&nbsp; knowledge and to get all details right. At this moment only 15% of the main text is finished, so I have a long way to go. I expect&nbsp;I need at least a year to finish the book, and probably more. 
</p>
<p>
I am planning to publish parts of the books on this website, both to give you a sneak preview, and to invite you&nbsp;to reply to me on the published subjects and text. My email address is in the right hand column...</p> ]]></description>
			<guid isPermaLink="false">141@www.sjaaklaan.nl</guid>
			<category>default</category>
			<pubDate>Wed, 14 Jul 2010 11:55:00 +0200</pubDate>
		</item>
		
		
		
		<item>
			<title>Guru4Pro - Cloud computing</title>
			<link>http://www.sjaaklaan.nl/pivot/entry.php?id=137</link>
			<comments>http://www.sjaaklaan.nl/pivot/entry.php?id=137#comm</comments>
                        <description><![CDATA[ <p>
Gisteravond heb ik <a href="http://www.sjaaklaan.nl/pivot/entry.php?id=129"  target='_blank'>deze presentatie</a> gegeven over cloud computing. Er waren ongeveer 20 aanwezigen op de warme zomeravond in Amstelveen. De reacties van het publiek waren overwegend positief. Er ontstond meerdere malen een leuke discussie over de voor- en nadelen van de cloud.
</p>
<p>
Mocht u het gemist hebben - geen nood: ik kom het verhaal op aanvraag graag bij uw organisatie ook eens vertellen! Mijn email adres staat in de rechterbalk.</p> ]]></description>
			<guid isPermaLink="false">137@www.sjaaklaan.nl</guid>
			<category>default</category>
			<pubDate>Thu, 01 Jul 2010 15:40:00 +0200</pubDate>
		</item>
		
		
		
	</channel>
</rss>
