A Long Bumpy Road to the Clouds: FreeNEST and the SkyNEST Project

A long bumpy road to the clouds
Freenest and the skynest project
Ilkka turunen
IMAGE BY: WOLFGANG STAUD / FLICKR

Ilkka Turunen
B.Sc(eng) (projected 2011), Software engineering
CertifiedScrumMaster (SinceMay 2011)
Leaddeveloper in a projectcalled SkyNEST
Involved in the Cloud Software Program
Buzzwords: Cloudtechnologies, LEAN workmethods
Who is thisstrangeguy and what’s he on aboutanyway?
http://www.linkedin.com/in/ilkkaturunen
@ilkkaturunen
ilkka.turunen@jamk.fi

FreeNEST
Whatit is
Whatcanyoudo with it
Challenges with developing OSS
The SkyNEST Project
How wework
Whatwehavelearned
How ourprojectevolves
What’sthispresentationallabout

The skynest-project
Cuttingedgeresearch and developMent in the field of cloudtechnology
IMAGE BY: VOX_EFX / FLICKR

Cloud Software Program
Givesfunding to
SHOKs
Organized in programs
http://www.tivit.fi/fi/cloudsoftware
CSW-partners

Software and the SkyNEST project team (core)
HannuLuostarinen
Headof Software Eng. Programme
Tapani Äijänen
Principal lecturer
Jouni Huotari
Team leader and Project manager
Pasi Manninen
Mobile programming
Juha Peltomäki
Web programming
Esa Salmikangas
Software engineering
Kari Niemi
Headof Media
Engineering Programme
Ilkka Turunen
LeadDeveloper
FreeNEST
Marko “NarsuMan” Rintamäki
NEST Concept Architect
Studentteams

Skynestorganisation at a glance
DD
EA
LP
TT
CT
observes
SkyNEST Core
SkyNEST Core
LutakkoLivingLab

Succesfulreferenceprojects
OpenStack basedtestimplementations
Employedabout 20+ students
FreeNEST Releases and development
Networking with the industry
Internationallysignificantknowledge of cloudtechnologies
> Alsoalreadytransferred to students via teaching (new courses)
Project achievements

”SoWhat is itanyway?”

”a nest for a project”

”free as in freebeer”
(badanalogy for FLOSS in general)

VIRTUAL WORK AREA
Google Docs
Office 360
Atlassian JIRA
Microsoft Team Foundation Server
Our FreeNEST
Virtual Work Area

Application lifecycle management
”ALM is the marriage of business management to software engineering made possible by tools that facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management”
Source: WikipediaALM-article

”Building a nest
for a project team and the customer”
Project
Management
Reporting
Inventory
User
Management
Communication
Service Desk
Tasks
Risks
Brain
storming
Defects
Survey
Testing
Knowledge
Version control
Change
Database
System
(Linux) Operating System
VirtualizationInfrastructure: Public Cloud / PrivateCloud / USB Stick/ Workstation computer / Traditionalservers
27.9.2011

History
2011: FreeNEST 1.3 Alpha
2010: NEST 1.3 dev-1
2009: NEST 1.2
2008: NEST 1.1
FIRST IDEA 1.5.2006
24.8.2007: NEST-ix 1.0

Software

Real Organization?
Ideal Organization?
http://rubiks.wikia.com/wiki/Rubik%27s_Cube

DomainSpecificWork Area, butsame business control layer
Core Organization
Business Logic
Business Logic
Business Logic
Virtual Work Area
For software development
Virtual Work Area
Construction Project
Virtual Work Area
For General Project Management
“What could be feasible for different kinds of project working?”

Customer
Organization1
Project
Context 3
Project
Context 2
Customer
Organization2
Project
Context 4
Project
Context 1
D
D
Subcontractor
External
D
D
Delivers
only
CORE
Organization
D
External
Team
Context
D
I

Building a project
Ourteams and howtheycame to be

InitialDirtyDozenteam
Marko Rintamäki – Product Owner
Ilkka Turunen – ScrumMaster
Aki Huttunen – GIT implementation
Samuli Lager – Package Management
Jukka Perkka- LDAP Authentication
Simo Juhajoki– FOSWIKI Plugins
Riku Hokkanen – Testlink + FoswikiPlugins
Teemu Myller– VAADIN GIT integration
Joni Katajamäki – VAADIN GIT integration
Jarkko Aalto – Robot Framework
Marko Silokunnas - Communitywork
Image copyright: MGM

Planning session
SPRINT
1 week
Project model: ”Scum”

Learning Curveteam
Ari Karhunen
YoussefBenamar
Hiski Karhinen
Teemu Ojala
Juuso Nieminen
Kari Kiiskinen
Tuomo Stambweski
Pasi Hyvönen
Taneli Hartikainen
+1
TEAM

Planning session
SPRINT
1 week
KANBAN
”Scum+ban”

ElectricalArt
+1
TEAM
http://beachhead.labranet.jamk.fi/wiki/CaseStories/CaseStoryElectricalArtTeam

Planning session
SPRINT
1 week
KANBAN
KANBAN

Image by: Liz (perspicacious.org) /FLICKR
Somereorganizationhappened

New Dirtydozen

ElectricalArt

TestingTeam

Sprint Planning
User stories
Sprint Planning
Tasks
Sprint Review
SPRINT
2weeks
Sprint Retrospective
KANBAN
KANBAN

New Dirtydozen

TestingTeam

ElectricalArt

Infrateam

New Feature Team

KANBAN
KANBAN
2x Scrum + 2x kanban

Software and content Licenses
What they are and why you should care

Licenses are very important
OSS != Single license or philosophy
Most Popular ones (most also present in FreeNEST):
GPL v2
GPL v3
AGPL
Creative Commons
3-clause BSD (”Modified BSD”)
Apache License
Mozilla License
Wellthen, Whyshould I care?

Fourfreedoms of FLOSS:
-The freedom to run the program
-The freedom to study the program, and
to adapt it to your needs. Access to the
source code is therefore precondition
-The freedom to redistribute the
program, so you can help others
-The freedom to release improvements,
so everyone benefits. Again, access to
the source code is a precondition.

There is greatpower in numbers

However, something needs to ensure the rights to the software or content
Licenses provide this legal safety
Image by: Ilya Boyandin/FLICKR

“A license is simply a contractual agreementbetweenthecopyrightownerandthecopyrightusergrantingpermissionforuseofthecopyrightwork”

Created initially by Richard Stallman in 1989
Gives anyone the right to use, copy, to change or to distribute works licensed under it
However, changes must be distributed
The same license must remain
> improvements by others can be used
> and reused
Three versions so far
Most used OSS License
GNU General public license
Image by: NICOBZH/FLICKR
http://www.gnu.org/copyleft/gpl.html

GNU Lesser General Public License
Compromise between BSD and GPL
Primarily used for software libraries
GNU Affero General Public License
Designed to close a loophole, where by using but not distributing software, the demand for distribution is not fulfilled. Otherwise nearly identical to GPLv3
Example: Modified GPL software that is offered to the public as a Service (from the Cloud)
LGPL and Agpl

License for content, not for software
Text, images, drawings
Includesactuallawtext, and humanreadable info sheet
Usedby:
AlJazeera
Wikipedia
DeviantART
BlenderFoundation
Manyversions of samebaselicense:
Attribution
Non-commercial
No derivativeworks
Etc….
Creative commons

A family of permissive free software licenses
First version written in University of California circa 1977
Most used version is the 3-clause license:
Redistribution and use in source and binary, with or without modification, are permitted provided that:
The license is always distributed with the work
All advertising material mentioning usage of software must display an acknowledgment to the original organization and copyright holder
The names of either the organization nor the contributors can be used in endorsements promoting derived works
Bsd licenses

FreeNEST containsnumerouslicenses:
GPL v2
Modified BSD
BSD-derivatives
All the licensetext of indidual software mustremain with distribution
Includeshandylicenseinformationpage
FreeNEST and licenses

Integrating software Acrosslicenses
GNU GPL doesnot permit linkingbetween GPL and non-GPL-software
Dynamicscriptlanguages on the webarenotconsidered to ”link” anything
Make sure licensesmatch
GNU GPL sitehas a goodlist

CLIENTS:
OSS doesnotvendorlockclient to onespecificprovider
VENDORS:Toimittaja:
R&D Resources cansometimesbesmaller, sincetheymightnotneed to handleall the scope of the software.
HOWEVER, itdoesnotmean the vendorcantrust on the community to doeverything for it.
DEVELOPERS:
Referencework for the Developer’s portfolio
Vendorsoften look for new employees in communities
Sowhatgood is thisallanyway?

MOST IMPORTANTLY: References, references, references
Usuallythereare no NDAs. A studentcaneasilyprovewhatshehasdone.
Real work with concereteimpact
Potentially international visibility
Allowsyou to focus on yourprofessionalskillset
Whystudentsshouldtakepart in open source

The Futurevision
Everything as a service

Whatif…
Image by: tshein/FLICKR

Awayfrom….

Towards:
networksof projectscommunicating
with eachother
Image by: GE HEALTHCARE /FLICKR

Customer
Organization #1
Enterprise 3.0?
Project #1
CORE
ORGANIZATION
Y-Generation
3rd Provider
Project #2
Project #3
Customer
Organization #2

SERVICE SLICE LAYER PICTURE
Business Control
Visibility
Customer
Organization #1
Visibility
FIREWALL /AUTHENTICATION
Virtual Work Area
Visibility
3rd provider

Organizationalinformation
”Master” Cell
Information
NoSQL,XML,
JSON - Database
”PassiveDissemination” Analyzes
Project InformationStream
(passive + activeinformation)
Project data
Analyzes
Reports
OSLC - API
PROJECT 1
PROJECT 2
PROJECT 3

The end & Questions
Image by: ajari /FLICKR

A Long Bumpy Road to the Clouds: FreeNEST and the SkyNEST Project

by ilkkaturunen

Accessibility

Categories

Upload Details

Usage Rights

2 Embeds 2

Statistics

A Long Bumpy Road to the Clouds: FreeNEST and the SkyNEST Project Presentation Transcript

http://www.techgig.com	1
http://www.linkedin.com	1