Following the opening keynote announcement about Kenai I ventured into a talk on Project Kenai.
With today’s economy, the drive is towards efficiency is certainly a key consideration, it was quoted that dedicated hosting servers only run at 30% efficiency.
An overview again of Cloud Computing
- Economics – Pay as you go,
- Developer Centric – rapid self provisioning, api-driven, faster deployment
- Flexibility – standard services, elastic, on demand, multi-tenant
Types of Clouds
- Public – pay as you go, multi-tenant application and services
- Private – Cloud computing model run within a company’s own data center
- Mixed – Mixed user of public and private clouds according to applications
SmugMug was referenced as a Mixed Cloud example.
Cloud Layers
- Infrastructure as a Services – Basic storage and computer capabilities offer as a service (eg. AWS)
- Platform as a Service – Developer platform with build-in services. e.g. Google App Engine
- Software as Service – applications offered on demand over the network e.g salesforce.com
Some issues raised about this layers included.
- IaaS issues include Service Level, Privacy, Security, Cost of Exit
- PaaS interesting point, one that is the bane of MySQL performance tuning, that is instrumentation
- SaaS nothing you need to download, you take the pieces you need, interact with the cloud. More services simply like doing your Tax online.
Sun offers Project Kenai as well as Zembly.
Project Kenai
- A platform and ecosystem for developers.
- Freely host open source projects and code.
- Connect, community, collaborate and Code with peers
- Eventually easily deploy application/services to “clouds”
Kenai Features
- Code Repository with SVN, Mercurial, or an external repository
- Issue tracking with bugzilla, jira
- collaboration tools such as wiki, forums, mailing lists
- document hosting
- your profile
- administrative role
Within Kenai you can open up to 5 open source projects and various metrics of the respositories, issue trackers, wiki etc.
The benefits were given as the features are integrated into your project, not distributed across different sites. Agile development within the project sees a release every 2 weeks. Integration with NetBeans and Eclipse is underway.
Kenai is targeted as being the core of the next generation of Sun’s collaboration tools. However when I asked for more details about uptake in Sun, it’s only a request, not a requirement for internal teams.
The API’s for the Sun Cloud are at http://kenai.com/projects/suncloudapis.
Event: CommunityOne East in New York, NY.
Presenter: Tori Wieldt, Sun Microsystems
Article Author: Ronald Bradford