Looking To Live in France ?

Thought we would give you a preview of our home here in Brittany, western France.

If you seek the quiet life with a possible opportunity to provide local temporary accommodations, then look here: http://fabulousbrittanyhome.fr/

 

Enjot the french life-style here in Brittany, France

Wonderfully large home for your family or a football team :-D

Screenshot 2014-08-13 23.45.21

IETF – Internet Engineering Task Force Documents

 


Screenshot 2014-08-13 23.45.21

Internet Engineering Task Force Docs

Completely forgot this was written several years ago to access all the IETF documents. It was Oct. 2012, and the tons of IETF documents were/are online for public consumption.

This app runs on Google App Engine  and has been running for several years. It stills has daily hits so if you need to review or research features and engineering documents about how th einternet came into being, then look here: http://ietf-document-index.appspot.com

Cloud Foundry Performance Testing

Have been wondering for sometime how we can measure the overall response of a known Cloud Foundry PaaS target. What kind of metrics can we use ?

As a first attempt, let’s review the PAT tool as reviewed by Dr. Nic. Look here: https://blog.starkandwayne.com/2014/08/02/ask-pat-how-long-does-it-take-to-push-apps/

and if you are really keen, you can hack your own version of PAT from the Github repo here: https://github.com/cloudfoundry-incubator/pat

My ideas involved a test harness to hit several/many CF targets simultaneously and let it all run for a few days. This would give a larger overview across a wider time span. We could see the highs and lows using some metrics – which times of day are bad/good – which days of the week are good ?  Do background tasks on the target CF influence or results ? Are they doing backups while we push our app to them ?

Maybe another test harness to bang our app on each CF target every n seconds/minutes/days ?

Then we could publish those metrics so we all have a better of of which PaaS is rubbish like CloudBees and which ones are sterling like IBM BlueMix and Anynines.com :-)

 

 

cropped-xperimental5h.png

Asciidoctor Admonition Icons Missing

Been writing some reference documents in my new ‘best friend’ – the asciidoctor markup syntax. For some time now i get puzzled when i want an admonition icon to appear in my document but it won’t. Ok my markup looks good to me and i have installed the ruby asciidoctor version:

jnorthr@jnorthr-EC548AA-ABU-a1128-uk:~/Desktop$ asciidoctor -V
Asciidoctor 0.1.4 [http://asciidoctor.org]

So a typical document like this works fine except that the beautiful image icons do not show up. I thought at first i had to lug around a folder of ./images/icon/*.png and all that stuff but it irked me somewhat.

My text of

= Notes About Asciidoc Sample Applications
jnorthr <jim.northrop@orange.fr>
v1.0, 2014-06-01 updated 7 June 2014

:icons: font

NOTE: Asciidoctor now supports font-based admonition icons, powered by Font Awesome!

== Overview

Caelyf lacks a template servlet for markup documents written using the asciidoctor markup syntax.

== Sample Application

You can find most of our sample applications on our github anynines account at https://github.com/anynines/[https://github.com/anynines/]. 

WARNING: You will need to signup with a cloud foundry PaaS provider before running any of these samples.

looks ok and renders as html quite nicely.


sample1


 

So that’s not what i need is it ? Where are my awesome icons ? Well, it turns out that i needed to add a bit of code to pull down the awesome.css stylesheet that has all the magic. So on the line just above


:icons: font

I added a passthru comment that renders in the final html document. That passthru comment looks like:

 

v1.0, 2014-06-01 updated 7 June 2014

++++
<link rel="stylesheet"  href="http://cdnjs.cloudflare.com/ajax/libs/font-awesome/3.1.0/css/font-awesome.min.css">
++++

:icons: font

So we need an external css link specification between the document date line and the icons font line. See my <LINK code above, and yes you do need to include ++++ lines above and below it too.

If you put that line into your .adoc script, so should experience the joy and pleasure of visible awesome fonts for all asciidoctor admonitions !   :)

sample3

 


Gradle Properties in Cloud Foundry Closure

See notes here: https://github.com/cloudfoundry/cf-java-client/blob/master/cloudfoundry-gradle-plugin/README.md

1. according to gradle documentation, we can put our PaaS cloud foundry target credentials into

~/.gradle/gradle.properties

like this:

cf.username=’men@work.com’

with single quotes. If we do that, we get this result:

:template-project:cf-login
 Authenticating to 'https://api.run.pivotal.io' with username ''men@work.com''
 POST request for "https://login.run.pivotal.io/oauth/token" resulted in 401 (Unauthorized); invoking error handler
 :template-project:cf-login FAILED

FAILURE: Build failed with an exception.

but removing the single quotes makes it work.

NOTE: Gripe !! the credentials in gradle.properties take precedence over those declared in our gradle script closure !!! So if we deploy the same app to several different PaaS targets we can not declare credentials in gradle.properties we just need a build.gradle script for each PaaS target  :-P

2. plugin cf-push where there is already an existing service leaves orphan services that were originally attached. Is this because of the “rediscloud-${randomWord}” random word declaration in the cloud foundry closure ?
3. same as 2. but also looses the uri as there is no/or a faulty rebind of uri to our app

 

4. cf-push of new app that does not already exist appears to work, correctly builds services and binds the uri correctly.

 

5. also note that ~/.gradle/gradle.properties needs a password too, so:

cf.password=porkypig