Monday, August 29, 2011

The Downside of Ownership


A common term used in organizations these days is “ownership”.  Someone needs to take ownership of a support call, ownership of a project, ownership of a service.  Ownership not in the mode of the box-hugger of old, but rather the term implies a responsibility, or a duty.  A duty to the organization, to the client.  This thing we’ve given you ownership of is important dammit, and you’d better make sure that you live up to your obligations.

And there is the heart of the problem for me.  Obligation.

For a period of years, I had ownership of the network at the educational institution where I worked (and am still employed for two more months).  This was more literal than the term usually implies, because for some of those years, due to budgetary issues, the difficulties of recruiting personnel to regional areas and other factors, I was the only Senior Network Engineer and often the only network engineer period.  I designed and implemented two generations of the network, implemented wireless, remote access services, authentication services, maintained DNS, DHCP and who knows what else.  I owned the network.  Or at least I knew it like the back of my hand – where the old and new gear was, where the single points of failure were, the IP addresses of practically every switch.

As the organizational reliance on the network grew, my sense of obligation grew.  Times were that the old HP router would lock up, and the old hands would wait until after lunch before sauntering over and rebooting it.  Not any more.  The network became critical to the operation of the enterprise, but the budget and personnel were not commensurate to that importance.  Now I could guarantee a phone call would arrive within 30 seconds of an outage.

Now many of my colleagues could simply switch off, deal with the issues in the morning.  “Hey, the organization cares not a jot for the unpaid overtime you do; they will exploit that; you owe them nothing”.  That was something I was not able to do.  I built this thing, I owned it, felt responsible for it.  I felt that an outage was a reflection on me.  Never mind that someone dug up a cable run somewhere, I should have been able to magic up a redundant path for which there had been no budget.  My fault.  The network was critical to operations at the organization.  People started work at 8:00.  So I needed to make sure things were working at 7:00.  So I would need to get up at 6:00 to check things and get them fixed if needed.  What if an alert came in overnight?  I began not turning my phone off at night, despite the dread that the ring tone engendered.  Any hour, the beep that indicated an email had to be heeded and checked.

This began a repeating cycle of stress and health issues.  I was like a deathly ghost haunting the corridors of the IT building at all hours, sending emails to my colleagues at 3 a.m., calling them from my sick bed asking if they had seen the outage alert that had just come in.  For the past several years, my life consisted of waking up at 4:00, checking logs, going to work at 6:00, working to 5:00 or later, coming home, logging in, watching the email listening to the phone, and getting to sleep after midnight.  My ownership of the network was, literally consuming my existence, and destroying my health.  People would tell me that it wasn’t that important, get a hobby, do something else.  But, once you are in that rut, and the psychological pull of the sense of obligation is so strong, it is hard to see a way out.

There are other manifestations, too.  An obsession with functionality; not wanting to make changes lest something break.  This resulted in a type of paralysis which impeded the forward momentum of projects.  An obsession with testing and prototyping and wanting to make any change in the dead of night – heaven forfend that a user was impacted.

This all had a detrimental effect, not only on me, but on the team around me, and on the organization.  Projects dragged, and I could see that people were reluctant to engage with me for fear of making things worse.

Even now, after resigning in April, and five months into seven months of long service leave, the pull of the place is not quite gone.  The sense of attachment is getting less and less, but it is still there, lurking in the background.  The projects I started which I didn’t finish, the documentation I didn’t complete and the knowledge that is locked in my head; all the little details and foibles and twenty years of history.  And it can all come back to the front of your mind when you get the phone call five months into your leave that starts, “Hi – sorry to bother you, but…”   Like it did today.

So ownership is not necessarily a bad thing.  In my case, the confluence of a misplaced sense of obligation to only full-time employer I have known for most of my working life, a proprietary feeling towards that which I built and some underlying personal psychological predisposition to stress conspired to turn that ownership against me.  When I start looking for work again in the new year, I hope that I am able to recognise the signs and guard against the temptations to take ownership too far.

I waited far too long to wake up this time.  I am determined to not make the same mistakes again.

Sunday, August 28, 2011

Librarian 3

This was a long process, but I was taking a break from the study over the weekend, so there was not much else to do.  Take a look and let me know what you think.  I'm not going to write much, but I think it looks fine.  I can see areas that need improvement, and I might do some touching up later.


I did do some freehand for the text in the books.  I also drybrushed some grey to give depth and on the white robe material.


The is not much detail on the left side that I hadn't previously done on the first librarian post.


So there it is.  A lot of detail, and a lot of close concentration.

Saturday, August 27, 2011

Librarian 2

This morning, I spent a couple of hours painting the Librarian's staff and right arm.


Going to take a break now and do some more study.  Have to think about which next part to tackle.


I am having to learn a whole new level of patience.

Friday, August 26, 2011

Librarian 1

With today being my 39th birthday, I took a bit of a break from the study.  I had a session with the personal trainer, and I seem to have done something to my right wrist. Luckily, I'm left-handed, which meant that I could do a bit of painting.  I thought I might try something a little challenging, so I began work on a Librarian.

This is my first metal miniature, and it came in three pieces.  I undercoated them separately the other day, blocking out the joins with masking tape so I could work on the detail unimpeded.  I spent two and a half hours painting the left arm carrying a book.

 
I began with the gold parts on the book and shoulder.  Next, I did the green of the bookmark and silver on the pendant.  Next, the white on the pages, which was then drybrushed with Bleached Bone and brown to give an aged look.  Some brown in the centre of the book adds some depth.  After the pages, I did the red "leather" of the book.  I tried to make the red a bit "rough" to give a bit of texture.  I'm not sure yet if I am going to attempt a bit of freehand work to at text to the page.


I then did the white of the banner on the shoulder.  This was overlaid with some Bleached Bone to give some texture, but it doesn't show up too well in the photo.  Then red on the purity seals and silver on the chain.  I chose green as the shoulder colour, although technically it should be blue for an Ultramarine, but I thought the colour stands out.  (This photo and the next were taken, then rotated, which is why the light seems to be coming from a funny place)


Lastly I did the arm.  The silver part is the un-coated area to attach to the main piece.  Note that the fine detail on the back of the book will be practically invisible once it is attached.

This was painstaking and careful work.  I have a feeling this librarian will be a fairly lengthy project to do in between study.


An idea of scale.


Saturday, August 20, 2011

Devastator Squad 5

A Slightly different approach with the Devastator Squad Sergeant.  Only dusty on the lower legs, and a light drybrushing on the backpack.


Not sure how well I did the face and hair.  I think it came out alright.


No rocks on this base, rather three clumps of grass.


So that is the Devastator Squad complete.  Below is a picture of the three Space Marines on the desert sand bases.


And finally the whole Squad.


It would have been nice if I had all of them on the same base design, and all with similar weathering, but I think this is a good group all the same.  I have another full Tactical Squad of Space Marines, so I will do some more experimenting with them.

Devastator Squad 4

This morning was laundry day, so while waiting for the spin cycles, I did the fourth member of the Devastator Squad.  This Marine is wielding a heavy bolter.  I made a more aggressive weathering on this one, and coupled with the desert base, I think it looks fine.





Only one to go in this squad, the squad sergeant.

Thursday, August 18, 2011

Devastator Squad 3a

Today, after spending a while messing about with Spanning Tree Protocol, and before I head off to a torture session with the personal trainer, I have done some work on the base of the Space Marine with the Missile Launcher.


To get a desert-style look, I got some modelling sand and model railway grass  from Toyworld of all places, and a small piece of quartz.  The grass is "autumn" style to give it a dry look.  I painted the existing base piece he is kneeling on with Bleached Bone, which seems to match the sand quite well.

There are a couple of places where I will need to touch up a little bit of PVA glue and add a bit more sand.  The piece of quartz may not bond well with the PVA, and I may need to replace it with superglue.  We will see.





Personally, I think it looks better than plain grass.  I'm not particularly creative and so I am not a good judge, but I am happy with it as a first attempt. The store has sands in different colours, so maybe I need to experiment a bit with the look.  They have different grass shades as well.  If I was building an army, I would try to make the bases consistent.  I will probably make the remainder of the bases of the Devastator Squad this same colour, with pale weathering and light desert sand.  My next one I may try something different.

Let me know what you think.

Tuesday, August 16, 2011

Devastator Squad 3

The next Devastator Squad member, with the missile launcher, I used to experiment again.  I used a drybrushing of white over blue to create a "weathered" appearance and creating highlights on the edges of the armour.  I have not finished the base, and the photos are a bit dark because of low light when I took the pictures.


You can see the extreme highlight on the elbow and right leg (from the Marine's perspective) and the weathered appearance of the blue, particularly on the legs and arms.  The detail is also brought out on the helmet.

Deybrushing Boltgun Metal over black gives the edges on the launcher highlights and and overall weathered appearance.  Drybrushing Mithril Silver over the launcher tube gives that part a bright highlight.

And again, the weathered look on the legs.

The weathering is clear in the last image.  Note the underside of the left leg is "clean".  I am going to colour that when I do the base.  I am going to do something a little different with the base, but I need to go to the store first to get some stuff.  You can see the weathered and highlighted areas on the helmet, backpack and launcher.

It is a first attempt at some weathering and highlights.  I think it gives the Marine a more natural look than the pristine paintwork I've been doing.  Let me know what you think.

Sunday, August 14, 2011

Devastator Squad 2

Today I painted the second of the Devastator Squad.  This Marine has a multi-melta.  I took a slightly different approach with this one.  I used a fine detail brush exclusively, even for the blue areas, and attempted some finer control  I tried to get just the one coat of blue in most places, so that later touch-ups weren't a fourth or fifth layer.

I also tried some new things. The weapon was left black, and I drybrushed the Boltgun Metal over the top.  I then used Mithril Silver on the weapon end and the skull detail.  The black hoses to the backpack, I drybrushed the Boltgun metal on edges to give the hoses some highlight detail.  The scroll on the front of the weapon was layered.  I used Scorched Brown, then Bleached Bone, followed by white to give it a textured look with highlights.  I used Shining Gold on the hanging piece, and brown for the ropes.


All in all, I a pretty happy with the way this turned out.  A am going to try some shading and blending on the power armour in the next couple of Marines.  That will need a trip to the store, though.  I'm going to try to do a bit of painting now and then, but tomorrow (Monday) I am going to start into my CCIE study for the written exam.  I'm going to see how long a chapter of the guide takes, and then do up a schedule so I can get to the written exam in the next few weeks.  So painting will be for relaxation and breaks, or when the study gets a bit much.


Devatator Squad 1

Even though I am going to swing into study mode for the CCIE, I still have some Space Marines to paint.  Here is a Devastator Squad Space Marine with a plasma gun.


Friday, August 12, 2011

Q-in-Q from GNS3

Following on from the previous post stating my intentions, I have been messing about with GNS3, the graphical front-end to Dynamips and Dynagen.  GNS3 is great for simulating Cisco routers, however it cannot easily do the same for switches, as much of the functionality of switches is performed in custom silicon.

I did all of my routing lab preparation for the CCNP using GNS3, and am looking to do the same for the CCIE.  However, what to do about switches?  Well, I'll have to buy some.  Which means I'll need to connect the simulated routers to the real world.  There are many posts elsewhere about how to do it, so I am going to just put up a quick post about Q-in-Q, and connecting GNS3 to a set of real-word switches and extending layer 2 between them.

First, connecting GNS3 to the real world.  I am running GNS3 on Ubuntu in a VMWare Workstation guest OS.  So, first, I bridged the eth0 of the VM to the ethernet interface on my laptop.  The only limitation I can see going forward here is that I can't seem to increase the MTU of the guest OS eth0.  Any VMWare/Linux gurus out there, let me know, but when I search, it appears it can be done in VMWare Workstation.  It shouldn't be a problem unless I start punting around large packets.

My laptop has a Broadcom chipset, and once I got underway, I was experiencing problems because the interface was dropping the VLAN tags.  I found that I had to edit the registry (host OS is Windows 7) and search for (what should be the only instance of):

TxCoalescing Ticks

And in the same place, add a new String Value:
PreserveVlanInfoInRxPacket

with a value of "1".

If you have a different ethernet chipset, you may need to sort this out, too.  Anyhow, next I connected my laptop ethernet to a 3560 switch, which is connected to a 2960 switch where my target test PC is located.  The 2960 has a VLAN for the PC, VLAN 5.  This is the "client" VLAN to be tunnelled to the router.

Now, in GNS3, I connected a generic switch to the real ethernet interface with an 802.1q trunk.  Then a router, connected to an access port, VLAN 7.  VLAN 7 is going to be the host VLAN carrying the tunneled client VLAN(s) for this router (R3 in the diagram; R1 and R2 are shut down).

On the router, R3, I create a subinterface tagged with the "client" VLAN, VLAN 5.  Now, for the Q-in-Q magic.  The port on the 2960 connecting to the 3560 is configured as a normal trunking port, carrying the client VLAN.  On the 3560, the port is configured as a dot1q-tunnel port, with the access VLAN of 7 (the host VLAN).  So essentially what is happening as a packet is sent from the target PC is the following:

  • The PC sends a frame and it arrives on the 2960.  This is on an access port, VLAN 5.
  • The 2960 forwards the frame to the 3560 via the dot1q trunk, adding the VLAN 5 tag.
  • The 3560 recieves this frame on its Q-in-Q interface.  A second VLAN tag is added to the existing frame, VLAN 7.  This frame is then forwarded to the GNS3 virtual switch.
  • The GNS3 ethernet switch receives the frame on the dot1q trunk, and strips the VLAN 7 tag from the frame.  This leaves a dot1q frame tagged with VLAN 5.  This is forwarded to the router, which accepts it on the subinterface.
In the reverse direction:

  • The router sends a frame, tagged with VLAN 5 to the GNS3 ethernet switch.  The switch adds the VLAN 7 tag and forwards it to the 3560.
  • The 3560 receives the frame, strips the VLAN 7 tag and forwards it to the 2960.
  • The 2960 strips the VLAN 5 tag and forwards the frame to the PC.
In a proper Q-in-Q tunnel situation, switches at either end of a provider cloud would add and remove tages, but here, essentially the GNS3 router and switch are doing a VLAN hopping-type thing.  Security admins everywhere are having palpitations.

And there you have it.  In addition, som l2protocol-tunnel commands allow the router and switch to seem adjacent.  In some cases, especially with GNS3 this does not hold, but it seems to work OK.  So, here is the topology of the GNS3, and the configuration (click to enlarge).





And the result from the router pinging the PC:

Router#ping 10.7.7.7

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.7.7.7, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 4/18/40 ms
Router#ping 10.7.7.7
 And the CDP, showing the adjacency of the virtual router and 2960 switch:

Router#sho cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
bldg-a-cc.9bc0   Fas 0/0            173          S I      WS-C2960P Gig 0/1

And on the switch:

bldg-a-cc.9bc0#sho cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
                  D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
Router           Gig 0/1           149             R S I  3725      Fas 0/0

So there you have it a Q-in-Q connection from GNS3 to some real switches.  And to prove (although you still need to take my word for it) that I actually have switches, here there are.

A Decision Not Taken Lightly

Since I completed my CCNP a couple of weeks ago, I have been contemplating my next certification step.  I have nine weeks of my paid long service left before I officially stop being employed, but I decided that that should not be any kind of cut-off, as I have plenty of time to find work after that.  I considered stopping with the CCNP, as that is what most employers seem to regard highly anyway and I might just take it as a win and move on.

That didn't seem to appeal, and in any case a broader set of certs or the CCIE would open other doors in the employment space.  So the question came down to whether I should plough ahead and attempt the CCIE or do some other specializations, like wireless, voice or security.  The design track seems appealing, and I even had a look outside the Cisco space at the Juniper certification track.  I bought the CCIE certification guide, and a couple of the specialization Cisco Press books.  I consulted with a few people about which path I might go, and everyone seemed to have different opinions, and it really came down to what I was looking for out of the experience.

So what am I looking for?  Marketability of the certifications is one concern, but in reality that is not the major concern.  In the end, given the time I currently have, I think I want a challenge.

So my decision is this.  Unless a particularly attractive job offer comes along in the interim, I am going to take the rest of 2011 and attempt the Route & Switch CCIE.  I am setting myself a timeline of four or five weeks from today to pass the CCIE written exam, and then to attempt the lab in December or January, depending upon the availability.  I have scribbled out a bit of a budget, and I am going to look buy a couple of 3560 switches for lab practice, but I am going to use GNS3/Dynamips to do the router side.

Everyone says that the CCIE is very difficult and challenging.  I want to try it to see if my network skillz really are any good.  I am never going to get a better time to try it.  I was looking at travelling overseas later this year, and as part of the experience, I am considering delaying that and going to take the lab exam in the Cisco Mecca of San Jose (although in reality, I'll probably book in for it in Sydney).  Also, as the time approaches for the lab, there are some excellent boot camps available to prep for the exam.

I'm setting myself a tight timeline, and I am fully aware that many, if not most people don't pass the lab on the first attempt.  But now I've made the decision, I'm quite excited that I have a plan for the rest of the year - CCIE study, gym to try and get down near 100 kg, and then to look for work.  I do have a bit of regret that I didn't follow on and get my PhD.  I'm not going to let the opportunity pass me by to give the CCIE a go.

Monday, August 8, 2011

Networking Nerds


For the past few months I've been listening to the Packet Pushers Podcast.  News, new gear, tech, security.  Go check them out.  They are awesome.


Sunday, August 7, 2011

Twilight of the American Century

It has been a while since I posted a soap-box article, so in the wake of the S&P downgrade of the US credit rating, I thought I'd make a comment on the erosion of the American experiment.

On the evening of July 21st, I watched on television the landing of the Space Shuttle Atlantis.  It was the last flight of the Shuttle program, leaving the American space program without a means of sending humans into orbit.  As budgets are cut and enthusiasm wanes, I began to seriously contemplate that the United States may never send a person into space again without subcontracting the job to Russia, China or a private company.  This was a passing thought, and I consigned it to the recesses of my mind.  However, the goings-on in Washington D.C. and across the rest of the US over the past few months have led me to think that this is not such an unreasonable thought.

And the Shuttle program's demise is a metaphor for what I see across the US.  Government is bad, public spending is evil, and nobody wants to pay for anything through taxes.  The Shuttle program employs over 3000 contractors and government workers.  These people are now losing their jobs.  By October, only 1000 will be left, converting the Shuttles into museum pieces.  Turning the lights out.  And so it is with this deficit reduction farce which was recently completed, with savage cuts in spending and no revenue increases.  Far from creating jobs, this will mean government shedding jobs, as has been happening in States, cities and towns across the US.  No new taxes at any cost.  Never mind that the wealthy and corporations are sitting on their money.

The new euphemism for the rich is that they are "job creators" and taxing them a higher rate would disincentivise hiring.  So last month, Cisco Systems, who is sitting on piles of cash outside the US, taxable at 35%, is lobbying to bring that money back almost tax-free; a so-called "tax holiday"; and in the meantime has announced a cut of over 6000 jobs.  One in ten of their worldwide workforce.  The reason they are laying people off?  People aren't buying.  Why not?  Because they have no jobs, or they have tightened their belts.  The only reason to hire more workers is because there is demand for something you have to sell.  Companies aren't buying.  Consumers aren't buying.  Cutting taxes on Ford won't give them an incentive to hire more people if people aren't buying their cars.  It just serves to increase the company's profit.  So the argument that tax rates must be cut and government spending must be cut to improve the economy defies logic.  And the Republicans are now advocating an amendment to the US Constitution which would mandate a balanced budget.  This is insane.  Sure, debt can be a bad thing.  Is US debt out of control?  Perhaps.  But consider this.  It is not as bad as Greece, and even with a $14 trillion debt, the credit rating was still triple-A.  Why?  Because a big as that debt number is, the government can raise revenue and service that debt.  So in bad times when nobody is buying and nobody is hiring, government is the only entity who can create demand and stimulate the economy.

A perfect example of the dysfunction at the heart of US government had to be the FAA shutdown this past month.  For ideological reasons, Republican Senators blocked the re-authorisation of the FAA budget.  Four thousand workers were furloughed.  Safety inspectors were coming in to work without pay to do their critical jobs.  But, because the FAA was shut down, $30 million a day in taxes were not being collected, reducing revenue.  At the same time, infrastructure projects were put on hold, putting between seventy and ninety thousand construction workers out of a job.  So there you have it.  Lower taxes, people out of work, infrastructure not maintained and safety potentially compromised.  And who benefits?  Well, until they were shamed into refunding the taxes to consumers, the airlines had raised prices, kept the taxes and pocketed the cash.  So in addition to the economic impact of the shutdown, corporations made more profits, and Joe Average gets screwed.

But governments must provide some services and they must be paid for.  So what is happening?  Well, in this example, local government is raising parking fees and fines.  State government is raising tolls and fees on things such as getting a birth certificate.  In some places, parking revenues now are competing with property taxes as the main source of revenue.  Call them fees or fines, but these are taxes.  And they are taxes on the people who can least afford the increases.  Increase corporate taxes or the top marginal rate or progressive property taxation on the value of the property?  Hell no.  But slug the shopper who has no choice but to use the parking meter, the commuter who has to use the bridge?  No problem.

And again, regular people bear the brunt.  Layoff of teachers, police, city workers.  Cities tearing up the tarmac roads because they are expensive to maintain.  Turning out the streetlights to save on electricity.

What is happening to the US?  Well, the tactic must be working for someone, as the same tactics of vitriolic and utterly negative response by business and the opposition to the carbon tax proposal here are just unhinged.  I personally don't know if a carbon tax is the right approach or whether it will work.  But it seems that the disease of believing that any tax increase is an assault on freedom, liberty and who knows what else is spreading.  This is a dangerous road to go down.  Nobody like paying taxes, and nobody likes their taxes to be seen to be misused or mis-spent.  But they are necessary to maintain society and the standard of living people have come to expect.

Welcome to the end of the American Century.  Hastened by the principle that government of the people, by the people and for the people, is a bad thing if you have to pay for it, and the sooner is perishes from the Earth, the better.

Saturday, August 6, 2011

Terminator Squad 6

At last, it is complete.  Today I spent around five hours painting the Terminator Squad Sergeant.  I really tried to make this one as good as I could.  For the most part, I am fairly happy with it.  However, I can see the flaws in my technique.  That is a good thing, however, as it can only make me better to know where I can improve.

So here it is.  The images in this post are not reduced; I wanted the best resolution possible.  Click on the images for larger versions.


Some of the freehand on the banner is a bit rough, and again the chest emblem was a little too filled in by the undercoat.  I am happy about the detail on the power sword, storm bolter and the face.  It is not super-obvious, but I did put some writing on the banner plaque; uses a thin felt-tipped pen, and then covered with the gloss varnish.


I tried some of the layering techniques to try to get some definition in the facial features.  I think it is fine, but the technique needs some work.

So, there it is.  The Terminator Squad is complete.  I have a Devastator Squad (standard Space Marines with heavy weapons) in the box, but I think I will take a little break from painting.  Let me know what you think.

Thursday, August 4, 2011

Terminator Squad 5

So with the light fading today, and this afternoon's gym session beckoning, I have just completed the fourth member of the Terminator Squad.  This Space Marine is equipped with a storm bolter, power fist and with a missile launcher.

I was a bit disappointed with the chest detail.  It seems I got quite a lot of fill-in with the undercoat, and it did not come out as well as I hoped (the photo makes it look better than naked eye).  I made the missile tips yellow instead of the black or red you usually see.  I finished them off with a coat of gloss varnish to bring them out.


On the back, I tried to keep the hinges boltgun metal, and the skulls white.


So with just the sergeant to go now, the Terminator Squad is coming together.  I am learning a lot.  The Terminators are slightly larger than the standard Space Marine, and can be a bit more forgiving for the unsteady of hand.  But I think my technique is improving as I go.

Terminator Squad 4

The third member of the Terminator Squad was completed today.  This one wields a heavy flamer and a power fist.  I always seem to have difficulty with the shoulder-mounted decals; they never seems to quite sit down right, no matter how much I try.  Blending the edges doesn't seem to quite work.


On the other hand, I was quite pleased with the detail on this one; perhaps a slight improvement over the other two so far.  I also tried out a new colour called Burnished Gold for the wreath on the left arm.  A slightly muted shade compared to the Shining Gold colour.  I took the photos before the PVA glue was fully dry, so there is a bit of stray grass on the legs that I need to clean off.


So  now three are done, just two to go.  Next I will be doing the Terminator with the missile launcher pack.  So far, I think the squad is coming together nicely.

Tuesday, August 2, 2011

Terminator Squad 3

This morning I completed the second of the Terminator Squad.  This Space Marine has a power fist and an assault cannon.  Some nice fine detail on the right shoulder pad.  I chose to do the text and edging in gold, although white may have looked more consistent? 




So two down, three to go for this Terminator Squad.