Page History

...

• Keep improving quality, remove dead code
  • coverity scans, sonar etcs. - (sonar requires upgrade)
    
  • Would be nice to see a dashboard to monitor progress or a weekly email to the list
    
    
• Cleanup JIRA
  • JIRA has over 1400 open issues, a lot of them are not up to date.
  • Hold a JIRAthon to close as many as possible
  • Define JIRA best practices
  • Define commit habit of editing CHANGES.md when making a commit
    
    
• We have successfully moved to GitHub pull requests, we should stop using RB
  • 4/6/2015 S. Goasguen got consensus on list, all reviews updated with a note to move to GH PR.
  • 4/17/2015 RB closed but still read only. Announcement email sent to the lists.
  • DONE
    
    
• Simplify the dev process and adopt a new committing system to avoid regressions at all costs.
  • We have talked about this for a long time but have failed had doing something concrete. It is time.
    
    
• Remove the AWSAPI (there is a branch without it right now), we should merge it in master
  • Get IP clearance for ec2stack and gstack to get them under ASF governance.
  • 4/6/2015 I. Duffy started VOTE thread to donate ec2stack and gstack to CloudStack project.
    
    
• Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
  • Talk to exoscale, PCextreme, CloudOps
  • Could we get a donation for a user facing UI
    
    
• Solidify the testing infrastructure, keep Jenkins builds running
  
  
• Brainstorm on the future of CloudStack and IaaS in general. What should CloudStack be in 10 years ?
  • While CloudStack is what it is now, nothing prevents us to re-architect, re-think, re-code it within the current framework.
    
    
• Finally, package the mgt server and the KVM agent as Docker containers
  • Docker is a great portability mechanism. We should embrace Docker as a packaging tool (first) and provide container images for our mgt server (at a minimum).
    • 4/6/2015 PL Dion and S. Goasguen maintainer of the cloudstack org on hub.docker.com
  • This could become a type of release artifact that could be easily continuously built.

...

• Push to get our Ansible module into the Ansible core
  • 4/6/2015. This is really the work of Rene Moser now a CloudStack committeecommitter
    
• Publish "official" ansible playbook to deploy CloudStack
• Publish “official” chef recipes to deploy CloudStack
  • We have quite a few Chef users, we should finish to polish up "official" chef recipes to deploy CloudStack
• Identify and publish “official” Puppet recipes
  • Same with Puppet
    
• Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
  • We already have coreOS ones
• Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
  • Identify the issue with the current cloudstack datasource in cloud-init
• Work on the Terraform driver to support Basic zone
• Work on better jclouds support
  • See Aled Sage email to the list
• Get generic CloudStack driver merged in Docker machine
• Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
  • Getting a cloud is one thing but you need to deploy apps on top it and also deploy platforms
  • Provide ready to use recipes/playbooks to deploy platforms on a cloudstack cloud
  • 4/6/2015. .S. Goasguen I am working on Kubernetes and Mesos ansible playbook
• Work actively on up to date integration with CloudFoundry
  • Cloud foundry is a supporter of the CloudStack days in 2015
  • Let's get an up to date integration with cloudstack done (via terraform of the like)
• Work to get our packages in upstream distros
  • There has been some recent work to improve our deb packages, can we build on that to get in Debian ?

...

On Events:

We have at least four great events coming in 2015. We need leads and a program committer for each of those.

• Austin, April 16th
• Tokyo, June 2nd
• SeattleTokyo, August 20th 
  
• Dublin. October 7-8

Let’s meet at one of those events.

...