FluxTuna 0.0.4 → 0.0.5

data/test/data/bayeux/Labs/Lab3/L3_DNS.yaml

@@ -0,0 +1 @@
+title: Lab 3

data/test/data/bayeux/Labs/Labs.byx

@@ -0,0 +1 @@
+[h1 Labs]

data/test/data/bayeux/Labs/Labs.yaml

@@ -0,0 +1 @@
+title: Course Labs

data/test/data/bayeux/Resources/Resources.byx

@@ -0,0 +1,91 @@
+[h1 Resources]
+
+[h2 Network Guides]
+
+This module focus on mixed networks, running both special purpose operating
+systems such as Cisco's IOS to the more general Unix and Windows server and
+client systems. Behind the lectures and labs, we will be using a single
+network to explore the themes and technologies used in this module. This
+network is based on a semi-fictional company called Myertor.
+
+[h2 Operating System Guides]
+
+Although we will be using both Windows and Unix operating systems in the labs,
+we won't go into many details of the installation or administration of either.
+
+[h2 Recommended Texts]
+
+[h3 Course Site]
+
+For this course, we will not be using a 'core text'. Instead, each lab and
+lecture will have a link to relevant information either in this module site,
+or elsewhere. However, this will be the [e basic] information. Networking is a
+vast topic, and we will deliberately move through quite big topics at a fair
+pace.
+
+You might, therefore, want to supplement your reading with other texts that
+deal with the same material in different ways, or in greater depth. We have
+therefore selected three books (actually two books and a series) to help guide
+your reading around the topics introduced here. Where appropriate, you will
+find links to these three books from topics in the module site. You do not
+have to read anything from these books: but your understanding of the topic
+and the module will be greatly enhanced if you do. You may also find some of
+the lab exercises easier as well, as some of these books provide alternative
+methods and tools for some of the experiments we will do in the networking
+labs.
+
+[h3 Textbooks]
+
+If you want to supplement your understanding of material presented in this
+course, we strongly recommend The TCP/IP Guide by Charles Kozierok. We will be
+using the electronic version, available
+[link from the author|http://www.tcpipguide.com/order+the+guide.htm]. All the
+page numbers to [e The TCP/IP Guide] in the module site will refer version 3
+of this text.
+
+You can also obtain a paper copy of The TCP/IP Guide, the relevant details are
+
+[quote]
+Charles Kozierok, [e The TCP/IP Guide], No Starch Press, US (May 2005), ISBN 159327047X
+[end]
+
+You can order a copy from Blackwells, or this books is also available [link
+from
+Amazon|http://www.amazon.co.uk/exec/obidos/tg/detail/-/159327047X/qid=1126278702/sr=8-1/ref=pd_bbs_1?v=glance&s=books&n=507846].
+
+[medskip]
+
+Many of you will have met Andrew Tanenbaum's Computer networks from earlier modules, so we will include references to this text where appropriate. The full reference to this text is
+
+[quote]
+Andrew Tanenbaum, [e Computer networks], Prentice Hall; 3rd edition (March 6, 1996), ISBN 0133499456
+[end]
+
+Library Record: [link http://catalogue.shu.ac.uk/record=b1370370a]
+
+If you really want a copy, this can also be ordered from Blackwells if you want, or Amazon. Tanenbaum is also very widely available second hand, so you should be able to pick up a copy relatively cheaply if you want to.
+
+We will also be making use of Richard Stevens TCP/IP Illustrated: full reference
+
+[quote]
+W. Richard Stevens, [e TCP/IP Illustrated, Volume 1: The Protocols],  Addison Wesley, 1994. ISBN: 0-201-63346-9
+
+W. Richard Stevens, [e TCP/IP Illustrated, Volume 2: The Implementation],  Addison Wesley, 1995. ISBN 0-201-63354-X.
+[end]
+
+Stevens is especially useful for those involved in writing programs operating over TCP/IP networks, but is also good for those who want an in-depth look at the bottom layers of modern operating systems. Unless you're feeling rich, we don't recommend you buy these books. Instead consult the on-line version available from the library
+
+Library Record: [http://catalogue.shu.ac.uk/record=b1502121a]
+
+For many of the low-level details of networking technology, you need to read
+[e Data and Computer Communications] by William Stallings. This book has a
+large number of editions: we will be using the 8th edition available in the
+library. You can readily find earlier editions of this book second-hand: for
+most of the topics we are interested in, the earlier editions will be fine.
+The full reference to this book is
+
+[quote]
+William Stallings, [e Data and computer communications], Prentice Hall; 8th edition (2007), ISBN 0132433109
+[end]
+
+Library Record: [http://catalogue.shu.ac.uk/record=b1459158a]

data/test/data/bayeux/Resources/Resources.yaml

@@ -0,0 +1 @@
+title: Resources

data/test/data/bayeux/Welcome.byx

@@ -0,0 +1,49 @@
+[h1 Introduction]
+
+[h2 Overview]
+
+Welcome to the [e Introduction to Networks] short course. In this course we
+will look at a number of core technologies and protocols in modern networks: focusing on the ones you are most likely to meet in a modern business. Our aim is to give you a broad understanding of how modern ([ac TCPIP]) networks work, how they are build, and how they are maintained.
+
+Modern networks are complicated systems, requiring the expertise of a broad range of specialists from a range of disciplines. We will not attempt to go too far into any particular speciality ---instead we will step back and look at how the whole systems works. Understanding how all the different layers, protocols and pieces of a network fits together is usually the hardest task: and the most useful background if you do decide to take a particular aspect further. 
+
+[h2 Learning Material]
+
+Most of the material you will need for this course  is available on (or at least linked from) the BlackBoard site. In addition to the BlackBoard site we will also use a number of other resources from the Learning Centre, which you can read about [link here|>Resources].
+
+One key resource will be the course textbook
+
+[bib FitzGerald:Business]
+
+several copies of which can be found in the Learning Centre. A number of different editions of this book exist, and all of the last few editions should be useful. We will be using the 9th Edition, however, as the reference edition: so all the page numbers, chapter reference, etc. that can be found on this site refer to that edition.
+
+[h2 Labs and Seminars]
+
+During the semester, we will cover six broad topics, with each topic centred around a single lab. Each lab [e will] take longer than the allocated amount of time, and so will be divided into two. The [e core tasks] focus on the most relevant technologies (and skills), and you should be able to complete them during the allocated lab time. The [e extended tasks] will have to be done in your own time, and introduce material, techniques and technologies that we will not have time for within the formal teaching hours. 
+
+Broadly the six topic areas we will cover are (chapter numbers refer to [cite FitzGerald:Business])
+
+[dl]
+[item Local Area Networks (Chapter 6 and 7):
+  [e Local Area Networks] are often the most critical resource for a business (and therefore usually the one we get called on most to manage). In modern networks many of the technologies that you find on a [e Local Area Network] also have variants on bigger networks (especially Ethernet) and in many cases run exactly the same protocols (e.g. [ac IP]). Local networks therefore make a very good starting point for our exploration of modern networking technologies.]
+
+[item The Internet: Connecting Local Networks (Chapters 8--10):
+  In the first block we will focus on Ethernet, as the 'characteristic' protocol of 'small' networks. We did, though, briefly look at the [ac IP] which characterises groups of networks (or internetworks). [ac IP] is a very important protocol for most modern networks, both large and small, and we will look at the main features of both [ac IPv4] and [ac IPv6] in this block. Some of the more complex details (especially dynamic routing), will be left for later.]
+
+[item Digression: The Domain Name System (Chapter 5, pp. 159--165):
+  Although both [ac IP] and Ethernet are very important from a network point-of-view, most network users (both human and application) rely heavily on a [e secondary] protocol for locating hosts on the network. That protocol is the [acl DNS], which often takes a bit of time to understand, as it sits [e alongside] the 'core' [ac TCPIP] protocols. So while the [ac DNS] is not, technically, part of the [ac TCPIP] protocols, very few networks work correctly until it is configured properly. Many of the security techniques and network management technologies also rely on the [ac DNS], so understanding how it works is a key skill. Unfortunately [cite FitzGerald:Business] only outlines the basics of the [ac DNS], so we will diverge from the textbook for a short section of the course.]
+
+[item Network Management: The Network Side (Chapter 13):
+  Network management glues your understanding of all the various pieces of the network puzzle together, hopefully allowing you to find, analyse and fix problems within the networks under your management. Network management is also a big topic in its own right, but both the topic and the tools are important enough for us to spend the next two blocks of work on. In the first block we will look at tools which help us understand the lowest layers of the network: focusing on protocol decoders, and especially WireShark. Even if you don't manage your own network, these tools are very useful in their own right (and indeed, you will also make use of them in other modules).]
+
+[item Network Management: Services (Chapter 5, Chapter 13):
+  The other side of network management steps back from the details of bytes, packets, and networks; looking instead at how all these pieces fit together to provide [e services] to users or other services on the network. This also gives us an opportunity to look at the higher levels of the network stack, and particularly the [e transport] layer (and protocols) that usually sit on-top of [ac IP]. We will not go very far into the complexities of [ac TCP], [ac UDP] and friends: again we will keep the focus on the [e why] rather than the [e how].]
+
+[item Putting it All Together:
+ Our last block looks at a single service, [ac SMTP], from the network to the service side. This should give you an opportunity to understand both [ac SMTP] in a bit more detail, but more importantly to act as an example of the things we have been covering in this short course.]
+
+[end]
+
+The six labs will be also be spread over two weeks, which should give you enough time to both complete the core tasks and to ask any questions. We will also be asking questions in the second week (usually based around the questions dotted throughout each lab), to make sure you understand what we are doing…
+
+The six blocks will also be complemented by a series of activities, which we will do during the 'lecture' hour. All of these activities will cover much the same ground as the textbook, but in a very condensed format. Reading ahead is therefore [e strongly] advised.

data/test/data/bayeux/Welcome.yaml

@@ -0,0 +1 @@
+title: Welcome

data/test/data/data_test.rb

@@ -0,0 +1,29 @@
+# Copyright (c) 2010-2011 David Love
+#
+# Permission to use, copy, modify, and/or distribute this software for 
+# any purpose with or without fee is hereby granted, provided that the 
+# above copyright notice and this permission notice appear in all copies.
+#
+# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES 
+# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 
+# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR 
+# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 
+# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 
+# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 
+# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+#
+
+# @author David Love
+
+require "flux_tuna"
+
+# 
+# The {Test::Data} module does not contain any tests, as such, but instead
+# collects together the classes that provide data to other tests. These may
+# be 'boilerplate' classes containing pre-prepared data, or stub classes used
+# for low-level testing
+#
+module Test::Data
+
+end
+

data/test/dir_walk/create_witness_test.rb

@@ -0,0 +1,39 @@
+# Copyright (c) 2010-2011 David Love
+#
+# Permission to use, copy, modify, and/or distribute this software for 
+# any purpose with or without fee is hereby granted, provided that the 
+# above copyright notice and this permission notice appear in all copies.
+#
+# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES 
+# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 
+# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR 
+# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 
+# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 
+# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 
+# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+#
+
+# @author David Love
+
+# 
+# This test suite checks we can create the relevant witness objects
+#
+module Test::Witness
+  
+  # Include the standard witness classes
+  include FluxTuna::Witness
+
+  # Check that we can instantiate a directory walker
+  context "Create a DirFileWitness object" do
+    setup { DirFileWitness.new }
+    asserts_topic.kind_of(FluxTuna::Witness::DirFileWitness)
+  end
+  
+  # Create a walker for the test data
+  context "Create a DirFileWitness object" do
+    setup { DirFileWitness.new }
+    asserts("directory walker"){ topic.shatter("test/data/bayeux/**/*.byx") }
+  end
+
+end
+

data/test/init_test.rb

@@ -0,0 +1,26 @@
+# Copyright (c) 2009 Denis Defreyne, 2010-2011 David Love
+#
+# Permission to use, copy, modify, and/or distribute this software for 
+# any purpose with or without fee is hereby granted, provided that the 
+# above copyright notice and this permission notice appear in all copies.
+#
+# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES 
+# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 
+# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR 
+# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 
+# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 
+# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 
+# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+#
+
+# @author David Love
+
+require "riot"
+
+# 
+# All the tests for RedAdmiral live in the {Test} module, to make it easier
+# to find them, and to establish the relationships between tests
+#
+module Test
+end
+

metadata

@@ -2,7 +2,7 @@
 name: FluxTuna
 version: !ruby/object:Gem::Version 
   prerelease: 
-  version: 0.0.4
+  version: 0.0.5
 platform: ruby
 authors: 
 - David Love
@@ -143,9 +143,30 @@ files:
 - README.rdoc
 - Rakefile
 - VERSION
-- lib/FluxTuna.rb
-- test/helper.rb
-- test/test_FluxTuna.rb
+- lib/bind/bind.rb
+- lib/core/core.rb
+- lib/core/name_trie.rb
+- lib/flux_tuna.rb
+- lib/mutate/mutate.rb
+- lib/shatter/shatter.rb
+- lib/witness/abstract_witness.rb
+- lib/witness/dir_file_witness.rb
+- lib/witness/witness.rb
+- test/data/bayeux/Labs/Lab1/L1_Internet.byx
+- test/data/bayeux/Labs/Lab1/L1_Internet.yaml
+- test/data/bayeux/Labs/Lab2/L2_StaticR.byx
+- test/data/bayeux/Labs/Lab2/L2_StaticR.yaml
+- test/data/bayeux/Labs/Lab3/L3_DNS.byx
+- test/data/bayeux/Labs/Lab3/L3_DNS.yaml
+- test/data/bayeux/Labs/Labs.byx
+- test/data/bayeux/Labs/Labs.yaml
+- test/data/bayeux/Resources/Resources.byx
+- test/data/bayeux/Resources/Resources.yaml
+- test/data/bayeux/Welcome.byx
+- test/data/bayeux/Welcome.yaml
+- test/data/data_test.rb
+- test/dir_walk/create_witness_test.rb
+- test/init_test.rb
 has_rdoc: true
 homepage: http://github.com/dlove24/FluxTuna
 licenses: 
@@ -160,7 +181,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
-      hash: 943490751486551603
+      hash: 1763852741682151417
       segments: 
       - 0
       version: "0"

data/test/helper.rb

@@ -1,18 +0,0 @@
-require 'rubygems'
-require 'bundler'
-begin
-  Bundler.setup(:default, :development)
-rescue Bundler::BundlerError => e
-  $stderr.puts e.message
-  $stderr.puts "Run `bundle install` to install missing gems"
-  exit e.status_code
-end
-require 'test/unit'
-require 'shoulda'
-
-$LOAD_PATH.unshift(File.join(File.dirname(__FILE__), '..', 'lib'))
-$LOAD_PATH.unshift(File.dirname(__FILE__))
-require 'FluxTuna'
-
-class Test::Unit::TestCase
-end

data/test/test_FluxTuna.rb

@@ -1,7 +0,0 @@
-require 'helper'
-
-class TestFluxtuna < Test::Unit::TestCase
-  should "probably rename this file and start testing for real" do
-    flunk "hey buddy, you should probably rename this file and start testing for real"
-  end
-end