1. Security clearance

    Security clearance

    As part of the public administration, some MET positions require a security clearance. Please read more about clarence at NSM Web pages, especially the frequently asked questions page - Google translated for your convenience.

    Short summary:

    1. Norwegian citizens are eligible for a deterministic security clearance process
    2. Citizens of countries Norway has personnel security collaboration with (NATO countries, Schengen countries, countries Norway extends a great deal of trust to) are eligible for a deterministic security clearance process
    3. Citizens of countries Norway does not have a personnel security collaboration agreement with might never obtain a Norwegian security clearance, or the clarence process may take years to conclude
    4. If investigations of your person record evaluated to not comply with clearance requirements you may be denied clarence regardless of your citizenship

    If you belong to category 3 or 4, and the position require security clearance, we will discourage you from applying for the ...


  2. MET Norway open Clos Data Center Network

    Open Clos Data Center Network

    In 2015, MET Norway needed to replace an old core switch based network. Instead of replacing it, we defined the network as legacy infrastructure, and we invested in an open Clos leaf/spine network to be ready for SDN in connection to the OpenStack based production MET Cloud.

    MET Norway purchased 14 Juniper QFX5100-24Q 40Gbit switches with aggregate backbone capacity of 1.2Tbits. The new data center network is pure layer 3, L2 does not extend outside each leaf switch.


    EBGP is used between all leafs and spines. EBGP is also used between the border leafs and GWs. BGP peers are configured to only accept specific routes, they will also only send specified routes.


    We're using OSPF between leafs and zone switches (see illustration). This is redistributed into bgp in order to connected the openstack network with the rest of the cloud ...


  3. Google Web App using Spreadsheet

    Best of both worlds (Spreadsheet and dynamic Web interface)

    Managing information is a challenge. Often times you end up pasting information into a Spreadsheet, you try to make a system out of the madness.. Google comes along offering you an online (Google) Spreadsheet - so you can share your Spreadsheet with colleges! Your co-workers can help you out, thats nice, but you risk ending up with a mess! Just maybe you are better off limiting access to messing up the somewhat valuable Google Spreadsheet data to a smaller group of colleges, while less involved colleagues collaborate via a simple Web based user interface? As Google Spreadsheets are Web based by nature, attaching a Web interface is not far away. This is how you do it:

    Create a Google Spreadsheet

    This one you will have to figure out yourself :) (drive.google.com -> "New" -> "Sheets")

    Name the spreadsheet (replace "Untitled project" with a ...


  4. OpenStack Ceilometer basics

    The Ceilometer

    Ceilometer - OpenStack Telemetry

    OpenStack uses Ceilometer to measure Cloud usage.

    Telemetry is nice, as infrastructure utilization gets visible to users, developers, project leaders, management and to the IT department for utilization and budgetary purposes.

    Telemetry for OpenStack

    Getting telemetry from OpenStack quickly changed from optimism to frustration. OpenStack has all of these really nice APIs you can use to query all kinds of information, but there is no mature project for setting it in a system - and we really do not want to start writing a Cloud accounting system from scratch.

    Simple start - the API

    How to utilize the API could be better documented. Let's walk through the basics.

    First you need to get a token:

    . openrc    # openrc sets a number of useful variables
    echo $OS_AUTH_URL

    Get and store the adminURL in the ADMIN_URL variable (using quick and dirty method):

    ADMIN_URL=`curl -s -X ...


Page 1 / 1