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

1,398 views

Published on

A general presentation about the the SkyNEST Project at JAMK University of Applied Sciences and it's main product; the FreeNEST Project Platform.

The SkyNEST Project is an ongoing project at JAMK University of Applied sciences in Jyväskylä, Finland, that has already provided internships and thesis subjects for over 20 students and counting. The project is a

Published in: Technology, Business
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
1,398
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
3
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide
  • Jouni: ”As youcansee, the scope of projectdevelopment is verycomplex. Narsu,couldyouexplain …”… Narsu: 1 minuteintroduction … => Jouni: ”NEST managesthisall!”NESTProject Platform v 1.3
  • A Long Bumpy Road to the Clouds: FreeNEST and the SkyNEST Project

    1. 1. A long bumpy road to the clouds<br />Freenest and the skynest project<br />Ilkka turunen<br />IMAGE BY: WOLFGANG STAUD / FLICKR<br />
    2. 2. Ilkka Turunen<br />B.Sc(eng) (projected 2011), Software engineering<br />CertifiedScrumMaster (SinceMay 2011)<br />Leaddeveloper in a projectcalled SkyNEST<br />Involved in the Cloud Software Program<br />Buzzwords: Cloudtechnologies, LEAN workmethods<br />Who is thisstrangeguy and what’s he on aboutanyway?<br />http://www.linkedin.com/in/ilkkaturunen<br />@ilkkaturunen<br />ilkka.turunen@jamk.fi<br />
    3. 3. FreeNEST<br />Whatit is<br />Whatcanyoudo with it<br />Challenges with developing OSS<br />The SkyNEST Project<br />How wework<br />Whatwehavelearned<br />How ourprojectevolves<br />What’sthispresentationallabout<br />
    4. 4. The skynest-project<br />Cuttingedgeresearch and developMent in the field of cloudtechnology<br />IMAGE BY: VOX_EFX / FLICKR<br />
    5. 5. Cloud Software Program<br />Givesfunding to<br />SHOKs<br />Organized in programs<br />http://www.tivit.fi/fi/cloudsoftware<br />CSW-partners<br />
    6. 6.
    7. 7. Software and the SkyNEST project team (core)<br />HannuLuostarinen<br />Headof Software Eng. Programme<br />Tapani Äijänen<br />Principal lecturer<br />Jouni Huotari<br />Team leader and Project manager<br />Pasi Manninen<br />Mobile programming<br />Juha Peltomäki<br />Web programming<br />Esa Salmikangas<br />Software engineering<br />Kari Niemi<br />Headof Media <br />Engineering Programme<br />Ilkka Turunen<br />LeadDeveloper<br />FreeNEST<br />Marko “NarsuMan” Rintamäki<br />NEST Concept Architect<br />Studentteams<br />
    8. 8. Skynestorganisation at a glance<br />DD<br />EA<br />LP<br />TT<br />CT<br />observes<br />SkyNEST Core<br />SkyNEST Core<br />LutakkoLivingLab<br />
    9. 9. Succesfulreferenceprojects<br />OpenStack basedtestimplementations<br />Employedabout 20+ students<br />FreeNEST Releases and development<br />Networking with the industry<br />Internationallysignificantknowledge of cloudtechnologies<br />> Alsoalreadytransferred to students via teaching (new courses) <br />Project achievements<br />
    10. 10. ”SoWhat is itanyway?”<br />
    11. 11. ”a nest for a project”<br />
    12. 12. ”free as in freebeer”<br />(badanalogy for FLOSS in general) <br />
    13. 13. VIRTUAL WORK AREA<br /><ul><li>Google Docs
    14. 14. Office 360
    15. 15. Atlassian JIRA
    16. 16. Microsoft Team Foundation Server
    17. 17. Our FreeNEST</li></ul>Virtual Work Area<br />
    18. 18. Application lifecycle management<br />”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”<br />Source: WikipediaALM-article<br />
    19. 19. ”Building a nest <br />for a project team and the customer”<br />Project<br />Management<br />Reporting<br />Inventory<br />User<br />Management<br />Communication<br />Service Desk<br />Tasks<br />Risks<br />Brain <br />storming<br />Defects<br />Survey<br />Testing<br />Knowledge<br />Version control<br />Change<br />Database<br />System<br />(Linux) Operating System<br />VirtualizationInfrastructure: Public Cloud / PrivateCloud / USB Stick/ Workstation computer / Traditionalservers<br />27.9.2011<br />
    20. 20. History<br />2011: FreeNEST 1.3 Alpha<br />2010: NEST 1.3 dev-1 <br />2009: NEST 1.2<br />2008: NEST 1.1<br />FIRST IDEA 1.5.2006<br />24.8.2007: NEST-ix 1.0<br />
    21. 21. Software<br />
    22. 22.
    23. 23. Real Organization?<br />Ideal Organization?<br />http://rubiks.wikia.com/wiki/Rubik%27s_Cube<br />
    24. 24. DomainSpecificWork Area, butsame business control layer<br />Core Organization<br />Business Logic<br />Business Logic<br />Business Logic<br />Virtual Work Area<br />For software development<br />Virtual Work Area<br />Construction Project<br />Virtual Work Area<br />For General Project Management<br />“What could be feasible for different kinds of project working?”<br />
    25. 25. Customer<br />Organization1<br />Project<br />Context 3<br />Project<br />Context 2<br />Customer<br />Organization2<br />Project<br />Context 4<br />Project<br />Context 1<br />D<br />D<br />Subcontractor<br />External<br />D<br />D<br />Delivers<br />only<br />CORE<br />Organization<br />D<br />External<br />Team<br />Context<br />D<br />I<br />
    26. 26. Building a project<br />Ourteams and howtheycame to be<br />
    27. 27. InitialDirtyDozenteam<br />Marko Rintamäki – Product Owner<br />Ilkka Turunen – ScrumMaster<br />Aki Huttunen – GIT implementation<br />Samuli Lager – Package Management<br />Jukka Perkka- LDAP Authentication<br />Simo Juhajoki– FOSWIKI Plugins<br />Riku Hokkanen – Testlink + FoswikiPlugins<br />Teemu Myller– VAADIN GIT integration<br />Joni Katajamäki – VAADIN GIT integration<br />Jarkko Aalto – Robot Framework<br />Marko Silokunnas - Communitywork<br />Image copyright: MGM<br />
    28. 28. Planning session<br />SPRINT<br />1 week<br />Project model: ”Scum”<br />
    29. 29. Learning Curveteam<br />Ari Karhunen<br />YoussefBenamar<br />Hiski Karhinen<br />Teemu Ojala<br />Juuso Nieminen<br />Kari Kiiskinen<br />Tuomo Stambweski<br />Pasi Hyvönen<br />Taneli Hartikainen<br />+1<br />TEAM<br />
    30. 30. Planning session<br />SPRINT<br />1 week<br />KANBAN<br />”Scum+ban”<br />
    31. 31. ElectricalArt<br />+1<br />TEAM<br />http://beachhead.labranet.jamk.fi/wiki/CaseStories/CaseStoryElectricalArtTeam<br />
    32. 32. Planning session<br />SPRINT<br />1 week<br />KANBAN<br />KANBAN<br />
    33. 33. Image by: Liz (perspicacious.org) /FLICKR <br />Somereorganizationhappened<br />
    34. 34. New Dirtydozen<br />Image copyright: MGM<br />
    35. 35. ElectricalArt<br />http://beachhead.labranet.jamk.fi/wiki/CaseStories/CaseStoryElectricalArtTeam<br />
    36. 36. TestingTeam<br />
    37. 37. Sprint Planning<br />User stories<br />Sprint Planning<br />Tasks<br />Sprint Review<br />SPRINT<br />2weeks<br />Sprint Retrospective<br />KANBAN<br />KANBAN<br />
    38. 38.
    39. 39. New Dirtydozen<br />Image copyright: MGM<br />
    40. 40. TestingTeam<br />
    41. 41. ElectricalArt<br />http://beachhead.labranet.jamk.fi/wiki/CaseStories/CaseStoryElectricalArtTeam<br />
    42. 42. Infrateam<br />
    43. 43. New Feature Team<br />
    44. 44. KANBAN<br />KANBAN<br />2x Scrum + 2x kanban<br />
    45. 45. Software and content Licenses<br />What they are and why you should care<br />
    46. 46. Licenses are very important<br />OSS != Single license or philosophy<br />Most Popular ones (most also present in FreeNEST):<br />GPL v2<br />GPL v3<br />AGPL<br />Creative Commons<br />3-clause BSD (”Modified BSD”)<br />Apache License<br />Mozilla License<br />Wellthen, Whyshould I care?<br />
    47. 47. Fourfreedoms of FLOSS:<br />-The freedom to run the program<br />-The freedom to study the program, and <br />to adapt it to your needs. Access to the <br />source code is therefore precondition<br />-The freedom to redistribute the <br />program, so you can help others<br />-The freedom to release improvements,<br />so everyone benefits. Again, access to<br />the source code is a precondition.<br />
    48. 48. There is greatpower in numbers<br />
    49. 49. However, something needs to ensure the rights to the software or content<br />Licenses provide this legal safety<br />Image by: Ilya Boyandin/FLICKR <br />
    50. 50. “A license is simply a contractual agreementbetweenthecopyrightownerandthecopyrightusergrantingpermissionforuseofthecopyrightwork”<br />
    51. 51. Created initially by Richard Stallman in 1989<br />Gives anyone the right to use, copy, to change or to distribute works licensed under it<br />However, changes must be distributed<br />The same license must remain<br />> improvements by others can be used<br />> and reused<br />Three versions so far<br />Most used OSS License<br />GNU General public license<br />Image by: NICOBZH/FLICKR <br />http://www.gnu.org/copyleft/gpl.html<br />
    52. 52. GNU Lesser General Public License<br />Compromise between BSD and GPL<br />Primarily used for software libraries<br />GNU Affero General Public License<br />Designed to close a loophole, where by using but not distributing software, the demand for distribution is not fulfilled. Otherwise nearly identical to GPLv3<br />Example: Modified GPL software that is offered to the public as a Service (from the Cloud)<br />LGPL and Agpl<br />
    53. 53. License for content, not for software<br />Text, images, drawings<br />Includesactuallawtext, and humanreadable info sheet<br />Usedby:<br />AlJazeera<br />Wikipedia<br />DeviantART<br />BlenderFoundation<br />Manyversions of samebaselicense:<br />Attribution<br />Non-commercial<br />No derivativeworks<br />Etc….<br />Creative commons<br />
    54. 54. A family of permissive free software licenses<br />First version written in University of California circa 1977 <br />Most used version is the 3-clause license:<br />Redistribution and use in source and binary, with or without modification, are permitted provided that:<br />The license is always distributed with the work<br />All advertising material mentioning usage of software must display an acknowledgment to the original organization and copyright holder<br />The names of either the organization nor the contributors can be used in endorsements promoting derived works<br />Bsd licenses<br />
    55. 55. FreeNEST containsnumerouslicenses:<br />GPL v2<br />Modified BSD<br />BSD-derivatives<br />All the licensetext of indidual software mustremain with distribution<br />Includeshandylicenseinformationpage<br />FreeNEST and licenses<br />
    56. 56. Integrating software Acrosslicenses<br />GNU GPL doesnot permit linkingbetween GPL and non-GPL-software<br />Dynamicscriptlanguages on the webarenotconsidered to ”link” anything<br />Make sure licensesmatch<br />GNU GPL sitehas a goodlist<br />
    57. 57. CLIENTS:<br />OSS doesnotvendorlockclient to onespecificprovider<br />VENDORS:Toimittaja: <br />R&D Resources cansometimesbesmaller, sincetheymightnotneed to handleall the scope of the software. <br />HOWEVER, itdoesnotmean the vendorcantrust on the community to doeverything for it. <br />DEVELOPERS: <br />Referencework for the Developer’s portfolio<br />Vendorsoften look for new employees in communities<br />Sowhatgood is thisallanyway?<br />
    58. 58. MOST IMPORTANTLY: References, references, references<br />Usuallythereare no NDAs. A studentcaneasilyprovewhatshehasdone.<br />Real work with concereteimpact<br />Potentially international visibility<br />Allowsyou to focus on yourprofessionalskillset<br />Whystudentsshouldtakepart in open source<br />
    59. 59. The Futurevision<br />Everything as a service<br />
    60. 60. Whatif…<br />Image by: tshein/FLICKR<br />
    61. 61. Awayfrom….<br />
    62. 62. Towards:<br />networksof projectscommunicating<br />with eachother<br />Image by: GE HEALTHCARE /FLICKR <br />
    63. 63. Customer <br />Organization #1<br />Enterprise 3.0?<br />Project #1<br />CORE <br />ORGANIZATION<br />Y-Generation<br />3rd Provider <br />Project #2<br />Project #3<br />Customer <br />Organization #2<br />
    64. 64. SERVICE SLICE LAYER PICTURE<br />Business Control<br />Visibility<br />Customer <br />Organization #1<br />Visibility<br />FIREWALL /AUTHENTICATION<br />Virtual Work Area<br />Visibility<br />3rd provider<br />
    65. 65. Organizationalinformation<br />”Master” Cell<br />Information<br />NoSQL,XML,<br />JSON - Database<br />”PassiveDissemination” Analyzes<br />Project InformationStream<br />(passive + activeinformation)<br />Project data<br />Analyzes<br />Reports<br />OSLC - API<br />PROJECT 1<br />PROJECT 2<br />PROJECT 3<br />
    66. 66. The end & Questions<br />Image by: ajari /FLICKR <br />

    ×