a long bumpy road to the clouds: freenest and the skynest project
TRANSCRIPT
A LONG BUMPY ROAD TO THE CLOUDS
FREENEST AND THE SKYNEST PROJECTILKKA TURUNEN
IMAGE BY: WOLFGANG STAUD / FLICKR
• Ilkka Turunen• B.Sc(eng) (projected 2011), Software engineering• Certified ScrumMaster (Since May 2011)• Lead developer in a project called SkyNEST• Involved in the Cloud Software Program• Buzzwords: Cloud technologies, LEAN work methods
WHO IS THIS STRANGE GUY AND WHAT’S HE ON ABOUT ANYWAY?
http://www.linkedin.com/in/ilkkaturunen
@ilkkaturunen
• FreeNEST– What it is– What can you do with it– Challenges with developing OSS
• The SkyNEST Project– How we work– What we have learned– How our project evolves
WHAT’S THIS PRESENTATION ALL ABOUT
THE SKYNEST -PROJECTCUTTING EDGE RESEARCH AND DEVELOPMENT
IN THE FIELD OF CLOUD TECHNOLOGYIMAGE BY: VOX_EFX / FLICKR
CLOUD SOFTWARE PROGRAM
Gives funding toSHOKs
Organized in programs
CSW-partners
http://www.tivit.fi/fi/cloudsoftware
SOFTWARE AND THE SKYNEST PROJECT TEAM (CORE)
Jouni Huotari
Team leader and Project manager
Pasi Manninen
Mobile programming
Hannu Luostarinen
Head of Software Eng. Programme
Kari NiemiHead of Media
Engineering Programme
Juha Peltomäki
Web programming
Esa Salmikangas
Software engineering
Marko “NarsuMan” Rintamäki
NEST Concept Architect
Ilkka TurunenLead Developer
FreeNEST
Student teams
Tapani ÄijänenPrincipal lecturer
Lutakko Living Lab
SKYNEST ORGANISATION AT A GLANCE
SkyNEST Core
DD
TT CT
LP
EA
SkyNEST Core
observes
• Succesful reference projects• OpenStack based test implementations• Employed about 20+ students• FreeNEST Releases and development• Networking with the industry• Internationally significant knowledge of cloud
technologies– > Also already transferred to students via teaching (new
courses)
PROJECT ACHIEVEMENTS
”SO WHAT IS IT ANYWAY?”
”a nest for a project”
”free as in free beer”
(bad analogy for FLOSS in general)
Virtual Work Area
VIRTUAL WORK AREA
• Google Docs• Office 360• Atlassian JIRA• Microsoft Team
Foundation Server• Our FreeNEST
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: Wikipedia ALM-article
Tasks
Defects
Knowledge
Change
Service Desk
ProjectManagement
CommunicationInventory
Reporting
Brain storming
UserManagement
Risks
(Linux) Operating SystemVirtualization Infrastructure: Public Cloud / Private
Cloud / USB Stick / Workstation computer / Traditional servers
SurveyTesting
Database System
”Building a nest for a project team
and the customer”
Version control
02.05.2023
24.8.2007: NEST-ix 1.0
2009: NEST 1.2
2008: NEST 1.1
FIRST IDEA 1.5.2006
2010: NEST 1.3 dev-1
HISTORY
2011: FreeNEST 1.3
Alpha
SOFTWARE
http://rubiks.wikia.com/wiki/Rubik%27s_Cube
Real Organization?Ideal Organization?
DOMAIN SPECIFIC WORK AREA, BUT SAME BUSINESS CONTROL LAYER
“What could be feasible for different kinds of project working?”
Virtual Work AreaFor software development
Virtual Work AreaFor General Project
Management
Virtual Work AreaConstruction Project
Business Logic Business Logic Business Logic
Core Organization
ProjectContext 2
ExternalTeam
Context
ProjectContext 1
CustomerOrganization2
SubcontractorExternal
ProjectContext 4
COREOrganization
D
Deliversonly
CustomerOrganization1
ProjectContext 3
D
D D
D
D
I
BUILDING A PROJECTOUR TEAMS AND HOW THEY CAME TO
BE
Initial DirtyDozen team Marko Rintamäki – Product Owner
Ilkka Turunen – Scrum MasterAki Huttunen – GIT implementation Samuli Lager – Package ManagementJukka Perkka - LDAP Authentication
Simo Juhajoki – FOSWIKI PluginsRiku Hokkanen – Testlink + Foswiki Plugins
Teemu Myller – VAADIN GIT integrationJoni Katajamäki – VAADIN GIT integration
Jarkko Aalto – Robot FrameworkMarko Silokunnas - Community work
Image copyright: MGM
Planning sessionSPRINT1 week
PROJECT MODEL: ”SCUM”
Learning Curve team
Ari KarhunenYoussef Benamar
Hiski KarhinenTeemu Ojala
Juuso NieminenKari Kiiskinen
Tuomo StambweskiPasi Hyvönen
Taneli Hartikainen+1TEAM
Planning sessionSPRINT1 week
KANBAN
”SCUM+BAN”
ELECTRICAL ART
+1TEAM
http://beachhead.labranet.jamk.fi/wiki/CaseStories/CaseStoryElectricalArtTeam
Planning sessionSPRINT1 week
KANBAN KANBAN
Some reorganization happened
Image by: Liz (perspicacious.org) /FLICKR
NEW DIRTYDOZEN
Image copyright: MGM
ELECTRICAL ART
http://beachhead.labranet.jamk.fi/wiki/CaseStories/CaseStoryElectricalArtTeam
TESTING TEAM
Sprint PlanningUser stories
SPRINT2 weeks
Sprint PlanningTasks Sprint Review
Sprint Retrospective
KANBAN
KANBAN
NEW DIRTY DOZEN
Image copyright: MGM
TESTING TEAM
ELECTRICAL ART
http://beachhead.labranet.jamk.fi/wiki/CaseStories/CaseStoryElectricalArtTeam
INFRA TEAM
NEW FEATURE TEAM
KANBAN
KANBAN
2X SCRUM + 2X KANBAN
SOFTWARE AND CONTENT LICENSESWHAT 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
WELL THEN, WHY SHOULD I CARE?
Four freedoms 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 great power in numbers
HOWEVER, SOMETHING NEEDS TO ENSURE THE RIGHTS TO THE SOFTWARE OR CONTENT
LICENSES PROVIDE THIS LEGAL SAFETYImage by: Ilya Boyandin/FLICKR
“A license is simply a contractual agreement between the copyright owner
and the copyright user granting permission for use of the copyright
work”
• 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
• Includes actual law text, and human readable info sheet• Used by:
– Al Jazeera– Wikipedia– DeviantART– Blender Foundation
• Many versions of same base license:– Attribution– Non-commercial– No derivative works– 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 contains numerous licenses:– GPL v2– Modified BSD– BSD-derivatives
• All the license text of indidual software must remain with distribution
• Includes handy license information page
FREENEST AND LICENSES
INTEGRATING SOFTWARE ACROSS LICENSES
• GNU GPL does not permit linking between GPL and non-GPL-software– Dynamic script languages on the web are not considered
to ”link” anything– Make sure licenses match– GNU GPL site has a good list
• CLIENTS:– OSS does not vendor lock client to one specific provider
• VENDORS:Toimittaja: – R&D Resources can sometimes be smaller, since they
might not need to handle all the scope of the software. – HOWEVER, it does not mean the vendor can trust on the
community to do everything for it. • DEVELOPERS: – Reference work for the Developer’s portfolio– Vendors often look for new employees in communities
SO WHAT GOOD IS THIS ALL ANYWAY?
• MOST IMPORTANTLY: References, references, references– Usually there are no NDAs. A student can easily prove
what she has done.• Real work with concerete impact • Potentially international visibility• Allows you to focus on your professional skillset
WHY STUDENTS SHOULD TAKE PART IN OPEN SOURCE
THE FUTURE VISION
EVERYTHING AS A SERVICE
WHAT IF…
Image by: tshein/FLICKR
AWAY FROM….
Towards:networks of projects communicating with each other
Image by: GE HEALTHCARE /FLICKR
Customer Organization
#1
ENTERPRISE 3.0?
CORE ORGANIZATION
Y-Generation
Project #1
Project #2
Project #3
Customer Organization
#2
3rd Provider
Virtual Work Area
Business Control
3rd provider
SERVICE SLICE LAYER PICTURE
FIRE
WAL
L /A
UTH
ENTI
CATI
ON
Customer Organization
#1
Visibility
Visibilit
y
Visibility
Project Information Stream(passive + active information)
OSLC - API
”Master” CellNoSQL,XML,JSON - Database
PROJECT 1 PROJECT 2 PROJECT 3
ORGANIZATIONAL INFORMATION
”Passive Dissemination” Analyzes
PROJECT DATA
AnalyzesReports
Information
The end & QuestionsImage by: ajari /FLICKR