Thoughts on CloudStack while starting as new VP

[Sebastien Goasguen <ru...@gmail.com>]

Dear members of the CloudStack community,

Last week the Apache Software Foundation board unanimously voted a resolution to make me the new VP of Apache CloudStack. This came after a unanimous vote of the CloudStack PMC and is regular process of our community as described in our bylaws.

I am excited to take on this new role after two amazing VP (Chip and Hugo) since CloudStack came to the ASF. Many thanks to them and especially Hugo for the work he has done in the past year.

The ASF is setup so that the governance of a project really belongs to the community itself. CloudStack is what we all make it to be, we all have equal footing when time comes to develop the code, create events, take decisions and so on. As VP I do not have a special say in our direction. This governance model is in stark contrast with other open source project that follow more of a benevolent dictator model. I mention this as a bit of disclaimer and to re-enforce the fact that while I have views about what we should do, they are my personal views and that they do not represent any sorts of official roadmaps, and that anyone is welcome to disagree :)

In Budapest, we had a great conference. Chip and I showed several CloudStack use cases. Our user base is strong with over 300 production deployments. Our community is large and diverse with 2000 people on the mailing lists, but we need to keep advocating for CloudStack, make it an even greater software and grow our community. At the very least this helps us learn from each other, better our own skills and our employers IT infrastructure. At the very best AWS switches to CloudStack :)

So here are some food for thoughts that will hopefully excite you, want to get engage, talk about CloudStack and bring on board your friends:

On the code:
-----------------
- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board
We have successfully moved to GitHub pull requests, we should stop using RB
- 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
I am going to push for IP clearance of ec2stack and gstack to get them under ASF governance.
- Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
- 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).
This could become a type of release artifact that could be easily continuously built.


On the ecosystem:
-------------------------
We have a really strong ecosystem. From configuration management tools, API wrappers, PaaS plugins etc.
We need to feature our ecosystem clearly on our website, support it and keep on growing it as new technologies emerge.

Things that come to mind:
- Push to get our Ansible module into the Ansible core
- Publish “official” chef recipes to deploy CloudStack
- Identify and publish “official” Puppet recipes
- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
- Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
- Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
- Work actively on up to date integration with CloudFoundry

On documentation:
-------------------------
I and couple others successfully moved our docs to the Read The Docs service. This was a first great move but we need to finish the job.
We need to rethink our documentation tree, maybe merge all guides in one, correct the docs, create a new theme for it.
This is an easy area to contribute to if you are using cloudstack. Just send a pull request (click on the top right ribbon).
If you don’t know how, then it will teach you how to use github, great exercise.
We also need to routinely build the multi languages support.

On Events:
-------------------------
We have at least four great events coming in 2015. Austin, Seattle, Tokyo and Dublin.
Let’s meet at one of those events.
Let’s submit a talk or a poster, tell everyone about the great stuff you are doing with CloudStack.
If you are in a position at your company to sponsor the event, please do, we need your help to make those great events.
Open Source is about collaboration and sharing, so let’s meet around the globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)


Finally on the Website:
-------------------------
We can live without a website, but having a good one is a great way to showcase our community and our work.
The current website is an improvement to what it was before but we need to do much much better.
I recently did a small experiment and we could use github page. There is now a gh-pages branch in our repo.
Anyone can actually contribute to that branch and it will rebuild a site automatically.
If we could find a great web designer in our community, we could rebuild our site and make it a very modern, polished site that would attract even more people.
It’s an easy one, it just needs someone to step up and do it.

There is much more to this list, It is almost a brain dump. I figure that if we could work on those five areas and improve them, even just a bit, our project would be so much stronger. Some of them are easy, it’s just a question of sitting down and doing it.

So while I cannot tell you what to do, and cannot assign people to some of these tasks. I encourage you to look at that list and see if there is an area or a thought that strikes your mind and excites you. If there is, the only think I ask is that you send a pull request or at the very least an email to tell the rest of us what you are doing.

To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid software in production but we also want to work on the latest cool technologies. I think we can do both, and if we can do something that is both cool and rock solid in prod than we will have that amazing feeling of accomplishment and doing great work

Let’s keep on making CloudStack great in the coming year and let’s have fun doing it,

-Sebastien
@sebgoa

Re: Thoughts on CloudStack while starting as new VP

[Reuven Cohen <re...@citrix.com>]

Congrats and well deserved!

@rUv

On 2015-03-23, 7:15 AM, "Sebastien Goasguen" <ru...@gmail.com> wrote:

>Dear members of the CloudStack community,
>
>Last week the Apache Software Foundation board unanimously voted a
>resolution to make me the new VP of Apache CloudStack. This came after a
>unanimous vote of the CloudStack PMC and is regular process of our
>community as described in our bylaws.
>
>I am excited to take on this new role after two amazing VP (Chip and
>Hugo) since CloudStack came to the ASF. Many thanks to them and
>especially Hugo for the work he has done in the past year.
>
>The ASF is setup so that the governance of a project really belongs to
>the community itself. CloudStack is what we all make it to be, we all
>have equal footing when time comes to develop the code, create events,
>take decisions and so on. As VP I do not have a special say in our
>direction. This governance model is in stark contrast with other open
>source project that follow more of a benevolent dictator model. I mention
>this as a bit of disclaimer and to re-enforce the fact that while I have
>views about what we should do, they are my personal views and that they
>do not represent any sorts of official roadmaps, and that anyone is
>welcome to disagree :)
>
>In Budapest, we had a great conference. Chip and I showed several
>CloudStack use cases. Our user base is strong with over 300 production
>deployments. Our community is large and diverse with 2000 people on the
>mailing lists, but we need to keep advocating for CloudStack, make it an
>even greater software and grow our community. At the very least this
>helps us learn from each other, better our own skills and our employers
>IT infrastructure. At the very best AWS switches to CloudStack :)
>
>So here are some food for thoughts that will hopefully excite you, want
>to get engage, talk about CloudStack and bring on board your friends:
>
>On the code:
>-----------------
>- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
>Board
>We have successfully moved to GitHub pull requests, we should stop using
>RB
>- 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
>I am going to push for IP clearance of ec2stack and gstack to get them
>under ASF governance.
>- Several Cloud Providers have unveiled new CloudStack UI, maybe it¹s
>time we do the same.
>- 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).
>This could become a type of release artifact that could be easily
>continuously built.
>
>
>On the ecosystem:
>-------------------------
>We have a really strong ecosystem. From configuration management tools,
>API wrappers, PaaS plugins etc.
>We need to feature our ecosystem clearly on our website, support it and
>keep on growing it as new technologies emerge.
>
>Things that come to mind:
>- Push to get our Ansible module into the Ansible core
>- Publish ³official² chef recipes to deploy CloudStack
>- Identify and publish ³official² Puppet recipes
>- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
>- Finally cleanup cloud-init support for CloudStack, this is preventing
>us from having upstream centOS templates.
>- Publish playbooks/recipes to deploy workloads on CloudStack (think
>Hadoop, Spark, Kubernetes)
>- Work actively on up to date integration with CloudFoundry
>
>On documentation:
>-------------------------
>I and couple others successfully moved our docs to the Read The Docs
>service. This was a first great move but we need to finish the job.
>We need to rethink our documentation tree, maybe merge all guides in one,
>correct the docs, create a new theme for it.
>This is an easy area to contribute to if you are using cloudstack. Just
>send a pull request (click on the top right ribbon).
>If you don¹t know how, then it will teach you how to use github, great
>exercise.
>We also need to routinely build the multi languages support.
>
>On Events:
>-------------------------
>We have at least four great events coming in 2015. Austin, Seattle, Tokyo
>and Dublin.
>Let¹s meet at one of those events.
>Let¹s submit a talk or a poster, tell everyone about the great stuff you
>are doing with CloudStack.
>If you are in a position at your company to sponsor the event, please do,
>we need your help to make those great events.
>Open Source is about collaboration and sharing, so let¹s meet around the
>globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker
>:)
>
>
>Finally on the Website:
>-------------------------
>We can live without a website, but having a good one is a great way to
>showcase our community and our work.
>The current website is an improvement to what it was before but we need
>to do much much better.
>I recently did a small experiment and we could use github page. There is
>now a gh-pages branch in our repo.
>Anyone can actually contribute to that branch and it will rebuild a site
>automatically.
>If we could find a great web designer in our community, we could rebuild
>our site and make it a very modern, polished site that would attract even
>more people.
>It¹s an easy one, it just needs someone to step up and do it.
>
>There is much more to this list, It is almost a brain dump. I figure that
>if we could work on those five areas and improve them, even just a bit,
>our project would be so much stronger. Some of them are easy, it¹s just a
>question of sitting down and doing it.
>
>So while I cannot tell you what to do, and cannot assign people to some
>of these tasks. I encourage you to look at that list and see if there is
>an area or a thought that strikes your mind and excites you. If there is,
>the only think I ask is that you send a pull request or at the very least
>an email to tell the rest of us what you are doing.
>
>To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
>solid software in production but we also want to work on the latest cool
>technologies. I think we can do both, and if we can do something that is
>both cool and rock solid in prod than we will have that amazing feeling
>of accomplishment and doing great work
>
>Let¹s keep on making CloudStack great in the coming year and let¹s have
>fun doing it,
>
>-Sebastien
>@sebgoa
>

Re: Thoughts on CloudStack while starting as new VP

[Rene Moser <ma...@renemoser.net>]

Hi Sebastien

Congrats from me too! I like your thoughts! Especially the cleanup and
polish part.

On 23.03.2015 15:15, Sebastien Goasguen wrote:

> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
+1

> Things that come to mind:
> - Push to get our Ansible module into the Ansible core

Working on that as you know. I do some polish and cleanup atm and my
plan is to make a PR after the release of Ansible 1.9. We are having a
rc2 going on, so it won't be too far away.

Anyone is welcome helping me out!
https://github.com/resmo/ansible-cloudstack

Yours
René

Re: Thoughts on CloudStack while starting as new VP

[Marco Sinhoreli <ma...@shapeblue.com>]

Sebastien,


About documentation, now transifex uses fragmented texts and it creates
some times no sense texts translated. My suggestion is get together the
text blocks but I think it will be a hard work to reorganize code and
transifex. Another thing is support UTF-8 to supports special characters
in others languages.

Best regards,

Marco Sinhoreli
Consultant Manager




Phone: +55 21 2586 6390 | Fax: +55 21 2586 6002 | Mobile: +55 21 99159
4713 | Mobile: +55 21 98276 3636
Praia de Botafogo 501, bloco 1 - sala 101, Botafogo, Rio de Janeiro, RJ -
Brazil - CEP 22250-040
marco.sinhoreli@shapeblue.com | www.shapeblue.com
<http://www.shapeblue.com/> | Twitter:@shapeBlue
<https://twitter.com/#!/shapeblue>








On 23/03/15 11:15, "Sebastien Goasguen" <ru...@gmail.com> wrote:

>Dear members of the CloudStack community,
>
>Last week the Apache Software Foundation board unanimously voted a
>resolution to make me the new VP of Apache CloudStack. This came after a
>unanimous vote of the CloudStack PMC and is regular process of our
>community as described in our bylaws.
>
>I am excited to take on this new role after two amazing VP (Chip and
>Hugo) since CloudStack came to the ASF. Many thanks to them and
>especially Hugo for the work he has done in the past year.
>
>The ASF is setup so that the governance of a project really belongs to
>the community itself. CloudStack is what we all make it to be, we all
>have equal footing when time comes to develop the code, create events,
>take decisions and so on. As VP I do not have a special say in our
>direction. This governance model is in stark contrast with other open
>source project that follow more of a benevolent dictator model. I mention
>this as a bit of disclaimer and to re-enforce the fact that while I have
>views about what we should do, they are my personal views and that they
>do not represent any sorts of official roadmaps, and that anyone is
>welcome to disagree :)
>
>In Budapest, we had a great conference. Chip and I showed several
>CloudStack use cases. Our user base is strong with over 300 production
>deployments. Our community is large and diverse with 2000 people on the
>mailing lists, but we need to keep advocating for CloudStack, make it an
>even greater software and grow our community. At the very least this
>helps us learn from each other, better our own skills and our employers
>IT infrastructure. At the very best AWS switches to CloudStack :)
>
>So here are some food for thoughts that will hopefully excite you, want
>to get engage, talk about CloudStack and bring on board your friends:
>
>On the code:
>-----------------
>- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
>Board
>We have successfully moved to GitHub pull requests, we should stop using
>RB
>- 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
>I am going to push for IP clearance of ec2stack and gstack to get them
>under ASF governance.
>- Several Cloud Providers have unveiled new CloudStack UI, maybe it¹s
>time we do the same.
>- 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).
>This could become a type of release artifact that could be easily
>continuously built.
>
>
>On the ecosystem:
>-------------------------
>We have a really strong ecosystem. From configuration management tools,
>API wrappers, PaaS plugins etc.
>We need to feature our ecosystem clearly on our website, support it and
>keep on growing it as new technologies emerge.
>
>Things that come to mind:
>- Push to get our Ansible module into the Ansible core
>- Publish ³official² chef recipes to deploy CloudStack
>- Identify and publish ³official² Puppet recipes
>- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
>- Finally cleanup cloud-init support for CloudStack, this is preventing
>us from having upstream centOS templates.
>- Publish playbooks/recipes to deploy workloads on CloudStack (think
>Hadoop, Spark, Kubernetes)
>- Work actively on up to date integration with CloudFoundry
>
>On documentation:
>-------------------------
>I and couple others successfully moved our docs to the Read The Docs
>service. This was a first great move but we need to finish the job.
>We need to rethink our documentation tree, maybe merge all guides in one,
>correct the docs, create a new theme for it.
>This is an easy area to contribute to if you are using cloudstack. Just
>send a pull request (click on the top right ribbon).
>If you don¹t know how, then it will teach you how to use github, great
>exercise.
>We also need to routinely build the multi languages support.
>
>On Events:
>-------------------------
>We have at least four great events coming in 2015. Austin, Seattle, Tokyo
>and Dublin.
>Let¹s meet at one of those events.
>Let¹s submit a talk or a poster, tell everyone about the great stuff you
>are doing with CloudStack.
>If you are in a position at your company to sponsor the event, please do,
>we need your help to make those great events.
>Open Source is about collaboration and sharing, so let¹s meet around the
>globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker
>:)
>
>
>Finally on the Website:
>-------------------------
>We can live without a website, but having a good one is a great way to
>showcase our community and our work.
>The current website is an improvement to what it was before but we need
>to do much much better.
>I recently did a small experiment and we could use github page. There is
>now a gh-pages branch in our repo.
>Anyone can actually contribute to that branch and it will rebuild a site
>automatically.
>If we could find a great web designer in our community, we could rebuild
>our site and make it a very modern, polished site that would attract even
>more people.
>It¹s an easy one, it just needs someone to step up and do it.
>
>There is much more to this list, It is almost a brain dump. I figure that
>if we could work on those five areas and improve them, even just a bit,
>our project would be so much stronger. Some of them are easy, it¹s just a
>question of sitting down and doing it.
>
>So while I cannot tell you what to do, and cannot assign people to some
>of these tasks. I encourage you to look at that list and see if there is
>an area or a thought that strikes your mind and excites you. If there is,
>the only think I ask is that you send a pull request or at the very least
>an email to tell the rest of us what you are doing.
>
>To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
>solid software in production but we also want to work on the latest cool
>technologies. I think we can do both, and if we can do something that is
>both cool and rock solid in prod than we will have that amazing feeling
>of accomplishment and doing great work
>
>Let¹s keep on making CloudStack great in the coming year and let¹s have
>fun doing it,
>
>-Sebastien
>@sebgoa
>

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Sally Khudairi <sk...@apache.org>]

Wow --Sebastien! That looks like a well-thought-out plan.
I know that there's been a lot of energy put towards making Apache CloudStack an even better project. Here's to continued building from strength to strength --hats off to all involved! I'll be at ApacheCon and happy to meet up should you need anything.
Warmly,Sally

      From: Sebastien Goasguen <ru...@gmail.com>
 To: dev@cloudstack.apache.org; users@cloudstack.apache.org; marketing@cloudstack.apache.org 
 Sent: Monday, 23 March 2015, 10:15
 Subject: Thoughts on CloudStack while starting as new VP
   
Dear members of the CloudStack community,

Last week the Apache Software Foundation board unanimously voted a resolution to make me the new VP of Apache CloudStack. This came after a unanimous vote of the CloudStack PMC and is regular process of our community as described in our bylaws.

I am excited to take on this new role after two amazing VP (Chip and Hugo) since CloudStack came to the ASF. Many thanks to them and especially Hugo for the work he has done in the past year.

The ASF is setup so that the governance of a project really belongs to the community itself. CloudStack is what we all make it to be, we all have equal footing when time comes to develop the code, create events, take decisions and so on. As VP I do not have a special say in our direction. This governance model is in stark contrast with other open source project that follow more of a benevolent dictator model. I mention this as a bit of disclaimer and to re-enforce the fact that while I have views about what we should do, they are my personal views and that they do not represent any sorts of official roadmaps, and that anyone is welcome to disagree :)

In Budapest, we had a great conference. Chip and I showed several CloudStack use cases. Our user base is strong with over 300 production deployments. Our community is large and diverse with 2000 people on the mailing lists, but we need to keep advocating for CloudStack, make it an even greater software and grow our community. At the very least this helps us learn from each other, better our own skills and our employers IT infrastructure. At the very best AWS switches to CloudStack :)

So here are some food for thoughts that will hopefully excite you, want to get engage, talk about CloudStack and bring on board your friends:

On the code:
-----------------
- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board
We have successfully moved to GitHub pull requests, we should stop using RB
- 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
I am going to push for IP clearance of ec2stack and gstack to get them under ASF governance.
- Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
- 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).
This could become a type of release artifact that could be easily continuously built.


On the ecosystem:
-------------------------
We have a really strong ecosystem. From configuration management tools, API wrappers, PaaS plugins etc.
We need to feature our ecosystem clearly on our website, support it and keep on growing it as new technologies emerge.

Things that come to mind:
- Push to get our Ansible module into the Ansible core
- Publish “official” chef recipes to deploy CloudStack
- Identify and publish “official” Puppet recipes
- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
- Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
- Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
- Work actively on up to date integration with CloudFoundry

On documentation:
-------------------------
I and couple others successfully moved our docs to the Read The Docs service. This was a first great move but we need to finish the job.
We need to rethink our documentation tree, maybe merge all guides in one, correct the docs, create a new theme for it.
This is an easy area to contribute to if you are using cloudstack. Just send a pull request (click on the top right ribbon).
If you don’t know how, then it will teach you how to use github, great exercise.
We also need to routinely build the multi languages support.

On Events:
-------------------------
We have at least four great events coming in 2015. Austin, Seattle, Tokyo and Dublin.
Let’s meet at one of those events.
Let’s submit a talk or a poster, tell everyone about the great stuff you are doing with CloudStack.
If you are in a position at your company to sponsor the event, please do, we need your help to make those great events.
Open Source is about collaboration and sharing, so let’s meet around the globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)


Finally on the Website:
-------------------------
We can live without a website, but having a good one is a great way to showcase our community and our work.
The current website is an improvement to what it was before but we need to do much much better.
I recently did a small experiment and we could use github page. There is now a gh-pages branch in our repo.
Anyone can actually contribute to that branch and it will rebuild a site automatically.
If we could find a great web designer in our community, we could rebuild our site and make it a very modern, polished site that would attract even more people.
It’s an easy one, it just needs someone to step up and do it.

There is much more to this list, It is almost a brain dump. I figure that if we could work on those five areas and improve them, even just a bit, our project would be so much stronger. Some of them are easy, it’s just a question of sitting down and doing it.

So while I cannot tell you what to do, and cannot assign people to some of these tasks. I encourage you to look at that list and see if there is an area or a thought that strikes your mind and excites you. If there is, the only think I ask is that you send a pull request or at the very least an email to tell the rest of us what you are doing.

To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid software in production but we also want to work on the latest cool technologies. I think we can do both, and if we can do something that is both cool and rock solid in prod than we will have that amazing feeling of accomplishment and doing great work

Let’s keep on making CloudStack great in the coming year and let’s have fun doing it,

-Sebastien
@sebgoa


  

Re: Thoughts on CloudStack while starting as new VP

[Ian Rae <ir...@cloudops.com>]

Great overview of important priorities Seb and proof positive of your
qualification in the VP role.

Development process, marketing/`communications, refactoring of secondary
storage and networking, support for Docker/CloudFoundry, Hadoop/Spark and
AWS/OpenStack APIs are on my mind. Sorting through the existing JIRAs and
associated housekeeping will be important to moving forward.

Interested in having CloudOps contribute where we are well positioned to
add value, and definitely up for meeting in Austin!

*Ian Rae*
CEO | PDG
c: *514.944.4008*

*CloudOps** | *Cloud Infrastructure and Networking Solutions
www.cloudops.com *|* 420 rue Guy *|* Montreal *|* Canada *|* H3J 1S6

On Mon, Mar 23, 2015 at 10:15 AM, Sebastien Goasguen <ru...@gmail.com>
wrote:

> Dear members of the CloudStack community,
>
> Last week the Apache Software Foundation board unanimously voted a
> resolution to make me the new VP of Apache CloudStack. This came after a
> unanimous vote of the CloudStack PMC and is regular process of our
> community as described in our bylaws.
>
> I am excited to take on this new role after two amazing VP (Chip and Hugo)
> since CloudStack came to the ASF. Many thanks to them and especially Hugo
> for the work he has done in the past year.
>
> The ASF is setup so that the governance of a project really belongs to the
> community itself. CloudStack is what we all make it to be, we all have
> equal footing when time comes to develop the code, create events, take
> decisions and so on. As VP I do not have a special say in our direction.
> This governance model is in stark contrast with other open source project
> that follow more of a benevolent dictator model. I mention this as a bit of
> disclaimer and to re-enforce the fact that while I have views about what we
> should do, they are my personal views and that they do not represent any
> sorts of official roadmaps, and that anyone is welcome to disagree :)
>
> In Budapest, we had a great conference. Chip and I showed several
> CloudStack use cases. Our user base is strong with over 300 production
> deployments. Our community is large and diverse with 2000 people on the
> mailing lists, but we need to keep advocating for CloudStack, make it an
> even greater software and grow our community. At the very least this helps
> us learn from each other, better our own skills and our employers IT
> infrastructure. At the very best AWS switches to CloudStack :)
>
> So here are some food for thoughts that will hopefully excite you, want to
> get engage, talk about CloudStack and bring on board your friends:
>
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
> Board
> We have successfully moved to GitHub pull requests, we should stop using RB
> - 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
> I am going to push for IP clearance of ec2stack and gstack to get them
> under ASF governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time
> we do the same.
> - 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).
> This could become a type of release artifact that could be easily
> continuously built.
>
>
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools,
> API wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and
> keep on growing it as new technologies emerge.
>
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us
> from having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think
> Hadoop, Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
>
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs
> service. This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one,
> correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just
> send a pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great
> exercise.
> We also need to routinely build the multi languages support.
>
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo
> and Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you
> are doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do,
> we need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the
> globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
>
>
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to
> showcase our community and our work.
> The current website is an improvement to what it was before but we need to
> do much much better.
> I recently did a small experiment and we could use github page. There is
> now a gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site
> automatically.
> If we could find a great web designer in our community, we could rebuild
> our site and make it a very modern, polished site that would attract even
> more people.
> It’s an easy one, it just needs someone to step up and do it.
>
> There is much more to this list, It is almost a brain dump. I figure that
> if we could work on those five areas and improve them, even just a bit, our
> project would be so much stronger. Some of them are easy, it’s just a
> question of sitting down and doing it.
>
> So while I cannot tell you what to do, and cannot assign people to some of
> these tasks. I encourage you to look at that list and see if there is an
> area or a thought that strikes your mind and excites you. If there is, the
> only think I ask is that you send a pull request or at the very least an
> email to tell the rest of us what you are doing.
>
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
> solid software in production but we also want to work on the latest cool
> technologies. I think we can do both, and if we can do something that is
> both cool and rock solid in prod than we will have that amazing feeling of
> accomplishment and doing great work
>
> Let’s keep on making CloudStack great in the coming year and let’s have
> fun doing it,
>
> -Sebastien
> @sebgoa
>
>

Re: Thoughts on CloudStack while starting as new VP

[Nux! <nu...@li.nux.ro>]

Great email, I love the enthusiasm. :-)

I hope we can tick many of those points this year.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Sebastien Goasguen" <ru...@gmail.com>
> To: dev@cloudstack.apache.org, users@cloudstack.apache.org, marketing@cloudstack.apache.org
> Sent: Monday, 23 March, 2015 14:15:47
> Subject: Thoughts on CloudStack while starting as new VP

> Dear members of the CloudStack community,
> 
> Last week the Apache Software Foundation board unanimously voted a resolution to
> make me the new VP of Apache CloudStack. This came after a unanimous vote of
> the CloudStack PMC and is regular process of our community as described in our
> bylaws.
> 
> I am excited to take on this new role after two amazing VP (Chip and Hugo) since
> CloudStack came to the ASF. Many thanks to them and especially Hugo for the
> work he has done in the past year.
> 
> The ASF is setup so that the governance of a project really belongs to the
> community itself. CloudStack is what we all make it to be, we all have equal
> footing when time comes to develop the code, create events, take decisions and
> so on. As VP I do not have a special say in our direction. This governance
> model is in stark contrast with other open source project that follow more of a
> benevolent dictator model. I mention this as a bit of disclaimer and to
> re-enforce the fact that while I have views about what we should do, they are
> my personal views and that they do not represent any sorts of official
> roadmaps, and that anyone is welcome to disagree :)
> 
> In Budapest, we had a great conference. Chip and I showed several CloudStack use
> cases. Our user base is strong with over 300 production deployments. Our
> community is large and diverse with 2000 people on the mailing lists, but we
> need to keep advocating for CloudStack, make it an even greater software and
> grow our community. At the very least this helps us learn from each other,
> better our own skills and our employers IT infrastructure. At the very best AWS
> switches to CloudStack :)
> 
> So here are some food for thoughts that will hopefully excite you, want to get
> engage, talk about CloudStack and bring on board your friends:
> 
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board
> We have successfully moved to GitHub pull requests, we should stop using RB
> - 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
> I am going to push for IP clearance of ec2stack and gstack to get them under ASF
> governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do
> the same.
> - 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).
> This could become a type of release artifact that could be easily continuously
> built.
> 
> 
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools, API
> wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and keep on
> growing it as new technologies emerge.
> 
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us from
> having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop,
> Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
> 
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs service.
> This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one,
> correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just send a
> pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great exercise.
> We also need to routinely build the multi languages support.
> 
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo and
> Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you are
> doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do, we
> need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the globe
> from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
> 
> 
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to showcase
> our community and our work.
> The current website is an improvement to what it was before but we need to do
> much much better.
> I recently did a small experiment and we could use github page. There is now a
> gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site
> automatically.
> If we could find a great web designer in our community, we could rebuild our
> site and make it a very modern, polished site that would attract even more
> people.
> It’s an easy one, it just needs someone to step up and do it.
> 
> There is much more to this list, It is almost a brain dump. I figure that if we
> could work on those five areas and improve them, even just a bit, our project
> would be so much stronger. Some of them are easy, it’s just a question of
> sitting down and doing it.
> 
> So while I cannot tell you what to do, and cannot assign people to some of these
> tasks. I encourage you to look at that list and see if there is an area or a
> thought that strikes your mind and excites you. If there is, the only think I
> ask is that you send a pull request or at the very least an email to tell the
> rest of us what you are doing.
> 
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid
> software in production but we also want to work on the latest cool
> technologies. I think we can do both, and if we can do something that is both
> cool and rock solid in prod than we will have that amazing feeling of
> accomplishment and doing great work
> 
> Let’s keep on making CloudStack great in the coming year and let’s have fun
> doing it,
> 
> -Sebastien
> @sebgoa

Re: Thoughts on CloudStack while starting as new VP

[Jeff Moody <je...@fifthecho.com>]

I was having the same idea the other week. There are some serious 
shortcomings in the current UI (one example is the lack of being able to 
enable/disable SSH key management on templates when registering them).
I think it might be a good idea to radically simplifly the UI that ships 
with ACS and then start a new ACS subproject (like the AWS or GCE API 
proxies) for a new, full-featured UI which could run in a different 
language and have the possibility of running at a different cadence than 
the ACS management system. This would allow UI bugs and features to be 
handled faster (or slower) than the core management server functionality 
and APIs.
It might also be worthwhile to explore building the UI in a different 
language than Java to potentially attract other developers to the ACS 
project who might be more comfortable in Python, Ruby, or NodeJS.

On 03/24/2015 07:47 AM, Alex Hitchins wrote:
> Has the idea of a 'light' UI been discussed? More aimed at end users who we could tailor dialog to and keep it fast and simple.
>
> I could see this as a good starting point to redevelop the whole UI.
>
>
>
>
>> On 24 Mar 2015, at 10:53, Rohit Yadav <ro...@shapeblue.com> wrote:
>>
>> Great proposals Sebastien! Let's AWSAPI, improve code, remove dead code, cleanup JIRA/RB cleanup and move to Github PR.
>>
>> I hope we’ll have a better UIs for ACS users soon!
>>
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.yadav@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
>> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
>> CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Alex Hitchins <al...@alexhitchins.com>]

Has the idea of a 'light' UI been discussed? More aimed at end users who we could tailor dialog to and keep it fast and simple.

I could see this as a good starting point to redevelop the whole UI.




> On 24 Mar 2015, at 10:53, Rohit Yadav <ro...@shapeblue.com> wrote:
> 
> Great proposals Sebastien! Let's AWSAPI, improve code, remove dead code, cleanup JIRA/RB cleanup and move to Github PR.
> 
> I hope we’ll have a better UIs for ACS users soon!
> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.yadav@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
> CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>
> 
> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Rohit Yadav <ro...@shapeblue.com>]

Great proposals Sebastien! Let's AWSAPI, improve code, remove dead code, cleanup JIRA/RB cleanup and move to Github PR.

I hope we’ll have a better UIs for ACS users soon!

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.yadav@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Rohit Yadav <ro...@shapeblue.com>]

Great proposals Sebastien! Let's AWSAPI, improve code, remove dead code, cleanup JIRA/RB cleanup and move to Github PR.

I hope we’ll have a better UIs for ACS users soon!

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.yadav@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Nux! <nu...@li.nux.ro>]

Great email, I love the enthusiasm. :-)

I hope we can tick many of those points this year.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Sebastien Goasguen" <ru...@gmail.com>
> To: dev@cloudstack.apache.org, users@cloudstack.apache.org, marketing@cloudstack.apache.org
> Sent: Monday, 23 March, 2015 14:15:47
> Subject: Thoughts on CloudStack while starting as new VP

> Dear members of the CloudStack community,
> 
> Last week the Apache Software Foundation board unanimously voted a resolution to
> make me the new VP of Apache CloudStack. This came after a unanimous vote of
> the CloudStack PMC and is regular process of our community as described in our
> bylaws.
> 
> I am excited to take on this new role after two amazing VP (Chip and Hugo) since
> CloudStack came to the ASF. Many thanks to them and especially Hugo for the
> work he has done in the past year.
> 
> The ASF is setup so that the governance of a project really belongs to the
> community itself. CloudStack is what we all make it to be, we all have equal
> footing when time comes to develop the code, create events, take decisions and
> so on. As VP I do not have a special say in our direction. This governance
> model is in stark contrast with other open source project that follow more of a
> benevolent dictator model. I mention this as a bit of disclaimer and to
> re-enforce the fact that while I have views about what we should do, they are
> my personal views and that they do not represent any sorts of official
> roadmaps, and that anyone is welcome to disagree :)
> 
> In Budapest, we had a great conference. Chip and I showed several CloudStack use
> cases. Our user base is strong with over 300 production deployments. Our
> community is large and diverse with 2000 people on the mailing lists, but we
> need to keep advocating for CloudStack, make it an even greater software and
> grow our community. At the very least this helps us learn from each other,
> better our own skills and our employers IT infrastructure. At the very best AWS
> switches to CloudStack :)
> 
> So here are some food for thoughts that will hopefully excite you, want to get
> engage, talk about CloudStack and bring on board your friends:
> 
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board
> We have successfully moved to GitHub pull requests, we should stop using RB
> - 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
> I am going to push for IP clearance of ec2stack and gstack to get them under ASF
> governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do
> the same.
> - 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).
> This could become a type of release artifact that could be easily continuously
> built.
> 
> 
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools, API
> wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and keep on
> growing it as new technologies emerge.
> 
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us from
> having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop,
> Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
> 
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs service.
> This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one,
> correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just send a
> pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great exercise.
> We also need to routinely build the multi languages support.
> 
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo and
> Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you are
> doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do, we
> need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the globe
> from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
> 
> 
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to showcase
> our community and our work.
> The current website is an improvement to what it was before but we need to do
> much much better.
> I recently did a small experiment and we could use github page. There is now a
> gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site
> automatically.
> If we could find a great web designer in our community, we could rebuild our
> site and make it a very modern, polished site that would attract even more
> people.
> It’s an easy one, it just needs someone to step up and do it.
> 
> There is much more to this list, It is almost a brain dump. I figure that if we
> could work on those five areas and improve them, even just a bit, our project
> would be so much stronger. Some of them are easy, it’s just a question of
> sitting down and doing it.
> 
> So while I cannot tell you what to do, and cannot assign people to some of these
> tasks. I encourage you to look at that list and see if there is an area or a
> thought that strikes your mind and excites you. If there is, the only think I
> ask is that you send a pull request or at the very least an email to tell the
> rest of us what you are doing.
> 
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid
> software in production but we also want to work on the latest cool
> technologies. I think we can do both, and if we can do something that is both
> cool and rock solid in prod than we will have that amazing feeling of
> accomplishment and doing great work
> 
> Let’s keep on making CloudStack great in the coming year and let’s have fun
> doing it,
> 
> -Sebastien
> @sebgoa

Re: Thoughts on CloudStack while starting as new VP

[Nux! <nu...@li.nux.ro>]

Great email, I love the enthusiasm. :-)

I hope we can tick many of those points this year.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Sebastien Goasguen" <ru...@gmail.com>
> To: dev@cloudstack.apache.org, users@cloudstack.apache.org, marketing@cloudstack.apache.org
> Sent: Monday, 23 March, 2015 14:15:47
> Subject: Thoughts on CloudStack while starting as new VP

> Dear members of the CloudStack community,
> 
> Last week the Apache Software Foundation board unanimously voted a resolution to
> make me the new VP of Apache CloudStack. This came after a unanimous vote of
> the CloudStack PMC and is regular process of our community as described in our
> bylaws.
> 
> I am excited to take on this new role after two amazing VP (Chip and Hugo) since
> CloudStack came to the ASF. Many thanks to them and especially Hugo for the
> work he has done in the past year.
> 
> The ASF is setup so that the governance of a project really belongs to the
> community itself. CloudStack is what we all make it to be, we all have equal
> footing when time comes to develop the code, create events, take decisions and
> so on. As VP I do not have a special say in our direction. This governance
> model is in stark contrast with other open source project that follow more of a
> benevolent dictator model. I mention this as a bit of disclaimer and to
> re-enforce the fact that while I have views about what we should do, they are
> my personal views and that they do not represent any sorts of official
> roadmaps, and that anyone is welcome to disagree :)
> 
> In Budapest, we had a great conference. Chip and I showed several CloudStack use
> cases. Our user base is strong with over 300 production deployments. Our
> community is large and diverse with 2000 people on the mailing lists, but we
> need to keep advocating for CloudStack, make it an even greater software and
> grow our community. At the very least this helps us learn from each other,
> better our own skills and our employers IT infrastructure. At the very best AWS
> switches to CloudStack :)
> 
> So here are some food for thoughts that will hopefully excite you, want to get
> engage, talk about CloudStack and bring on board your friends:
> 
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board
> We have successfully moved to GitHub pull requests, we should stop using RB
> - 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
> I am going to push for IP clearance of ec2stack and gstack to get them under ASF
> governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do
> the same.
> - 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).
> This could become a type of release artifact that could be easily continuously
> built.
> 
> 
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools, API
> wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and keep on
> growing it as new technologies emerge.
> 
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us from
> having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop,
> Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
> 
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs service.
> This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one,
> correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just send a
> pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great exercise.
> We also need to routinely build the multi languages support.
> 
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo and
> Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you are
> doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do, we
> need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the globe
> from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
> 
> 
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to showcase
> our community and our work.
> The current website is an improvement to what it was before but we need to do
> much much better.
> I recently did a small experiment and we could use github page. There is now a
> gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site
> automatically.
> If we could find a great web designer in our community, we could rebuild our
> site and make it a very modern, polished site that would attract even more
> people.
> It’s an easy one, it just needs someone to step up and do it.
> 
> There is much more to this list, It is almost a brain dump. I figure that if we
> could work on those five areas and improve them, even just a bit, our project
> would be so much stronger. Some of them are easy, it’s just a question of
> sitting down and doing it.
> 
> So while I cannot tell you what to do, and cannot assign people to some of these
> tasks. I encourage you to look at that list and see if there is an area or a
> thought that strikes your mind and excites you. If there is, the only think I
> ask is that you send a pull request or at the very least an email to tell the
> rest of us what you are doing.
> 
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid
> software in production but we also want to work on the latest cool
> technologies. I think we can do both, and if we can do something that is both
> cool and rock solid in prod than we will have that amazing feeling of
> accomplishment and doing great work
> 
> Let’s keep on making CloudStack great in the coming year and let’s have fun
> doing it,
> 
> -Sebastien
> @sebgoa

Re: Thoughts on CloudStack while starting as new VP

[Marco Sinhoreli <ma...@shapeblue.com>]

Sebastien,


About documentation, now transifex uses fragmented texts and it creates
some times no sense texts translated. My suggestion is get together the
text blocks but I think it will be a hard work to reorganize code and
transifex. Another thing is support UTF-8 to supports special characters
in others languages.

Best regards,

Marco Sinhoreli
Consultant Manager




Phone: +55 21 2586 6390 | Fax: +55 21 2586 6002 | Mobile: +55 21 99159
4713 | Mobile: +55 21 98276 3636
Praia de Botafogo 501, bloco 1 - sala 101, Botafogo, Rio de Janeiro, RJ -
Brazil - CEP 22250-040
marco.sinhoreli@shapeblue.com | www.shapeblue.com
<http://www.shapeblue.com/> | Twitter:@shapeBlue
<https://twitter.com/#!/shapeblue>








On 23/03/15 11:15, "Sebastien Goasguen" <ru...@gmail.com> wrote:

>Dear members of the CloudStack community,
>
>Last week the Apache Software Foundation board unanimously voted a
>resolution to make me the new VP of Apache CloudStack. This came after a
>unanimous vote of the CloudStack PMC and is regular process of our
>community as described in our bylaws.
>
>I am excited to take on this new role after two amazing VP (Chip and
>Hugo) since CloudStack came to the ASF. Many thanks to them and
>especially Hugo for the work he has done in the past year.
>
>The ASF is setup so that the governance of a project really belongs to
>the community itself. CloudStack is what we all make it to be, we all
>have equal footing when time comes to develop the code, create events,
>take decisions and so on. As VP I do not have a special say in our
>direction. This governance model is in stark contrast with other open
>source project that follow more of a benevolent dictator model. I mention
>this as a bit of disclaimer and to re-enforce the fact that while I have
>views about what we should do, they are my personal views and that they
>do not represent any sorts of official roadmaps, and that anyone is
>welcome to disagree :)
>
>In Budapest, we had a great conference. Chip and I showed several
>CloudStack use cases. Our user base is strong with over 300 production
>deployments. Our community is large and diverse with 2000 people on the
>mailing lists, but we need to keep advocating for CloudStack, make it an
>even greater software and grow our community. At the very least this
>helps us learn from each other, better our own skills and our employers
>IT infrastructure. At the very best AWS switches to CloudStack :)
>
>So here are some food for thoughts that will hopefully excite you, want
>to get engage, talk about CloudStack and bring on board your friends:
>
>On the code:
>-----------------
>- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
>Board
>We have successfully moved to GitHub pull requests, we should stop using
>RB
>- 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
>I am going to push for IP clearance of ec2stack and gstack to get them
>under ASF governance.
>- Several Cloud Providers have unveiled new CloudStack UI, maybe it¹s
>time we do the same.
>- 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).
>This could become a type of release artifact that could be easily
>continuously built.
>
>
>On the ecosystem:
>-------------------------
>We have a really strong ecosystem. From configuration management tools,
>API wrappers, PaaS plugins etc.
>We need to feature our ecosystem clearly on our website, support it and
>keep on growing it as new technologies emerge.
>
>Things that come to mind:
>- Push to get our Ansible module into the Ansible core
>- Publish ³official² chef recipes to deploy CloudStack
>- Identify and publish ³official² Puppet recipes
>- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
>- Finally cleanup cloud-init support for CloudStack, this is preventing
>us from having upstream centOS templates.
>- Publish playbooks/recipes to deploy workloads on CloudStack (think
>Hadoop, Spark, Kubernetes)
>- Work actively on up to date integration with CloudFoundry
>
>On documentation:
>-------------------------
>I and couple others successfully moved our docs to the Read The Docs
>service. This was a first great move but we need to finish the job.
>We need to rethink our documentation tree, maybe merge all guides in one,
>correct the docs, create a new theme for it.
>This is an easy area to contribute to if you are using cloudstack. Just
>send a pull request (click on the top right ribbon).
>If you don¹t know how, then it will teach you how to use github, great
>exercise.
>We also need to routinely build the multi languages support.
>
>On Events:
>-------------------------
>We have at least four great events coming in 2015. Austin, Seattle, Tokyo
>and Dublin.
>Let¹s meet at one of those events.
>Let¹s submit a talk or a poster, tell everyone about the great stuff you
>are doing with CloudStack.
>If you are in a position at your company to sponsor the event, please do,
>we need your help to make those great events.
>Open Source is about collaboration and sharing, so let¹s meet around the
>globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker
>:)
>
>
>Finally on the Website:
>-------------------------
>We can live without a website, but having a good one is a great way to
>showcase our community and our work.
>The current website is an improvement to what it was before but we need
>to do much much better.
>I recently did a small experiment and we could use github page. There is
>now a gh-pages branch in our repo.
>Anyone can actually contribute to that branch and it will rebuild a site
>automatically.
>If we could find a great web designer in our community, we could rebuild
>our site and make it a very modern, polished site that would attract even
>more people.
>It¹s an easy one, it just needs someone to step up and do it.
>
>There is much more to this list, It is almost a brain dump. I figure that
>if we could work on those five areas and improve them, even just a bit,
>our project would be so much stronger. Some of them are easy, it¹s just a
>question of sitting down and doing it.
>
>So while I cannot tell you what to do, and cannot assign people to some
>of these tasks. I encourage you to look at that list and see if there is
>an area or a thought that strikes your mind and excites you. If there is,
>the only think I ask is that you send a pull request or at the very least
>an email to tell the rest of us what you are doing.
>
>To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
>solid software in production but we also want to work on the latest cool
>technologies. I think we can do both, and if we can do something that is
>both cool and rock solid in prod than we will have that amazing feeling
>of accomplishment and doing great work
>
>Let¹s keep on making CloudStack great in the coming year and let¹s have
>fun doing it,
>
>-Sebastien
>@sebgoa
>

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Sally Khudairi <sk...@apache.org>]

Wow --Sebastien! That looks like a well-thought-out plan.
I know that there's been a lot of energy put towards making Apache CloudStack an even better project. Here's to continued building from strength to strength --hats off to all involved! I'll be at ApacheCon and happy to meet up should you need anything.
Warmly,Sally

      From: Sebastien Goasguen <ru...@gmail.com>
 To: dev@cloudstack.apache.org; users@cloudstack.apache.org; marketing@cloudstack.apache.org 
 Sent: Monday, 23 March 2015, 10:15
 Subject: Thoughts on CloudStack while starting as new VP
   
Dear members of the CloudStack community,

Last week the Apache Software Foundation board unanimously voted a resolution to make me the new VP of Apache CloudStack. This came after a unanimous vote of the CloudStack PMC and is regular process of our community as described in our bylaws.

I am excited to take on this new role after two amazing VP (Chip and Hugo) since CloudStack came to the ASF. Many thanks to them and especially Hugo for the work he has done in the past year.

The ASF is setup so that the governance of a project really belongs to the community itself. CloudStack is what we all make it to be, we all have equal footing when time comes to develop the code, create events, take decisions and so on. As VP I do not have a special say in our direction. This governance model is in stark contrast with other open source project that follow more of a benevolent dictator model. I mention this as a bit of disclaimer and to re-enforce the fact that while I have views about what we should do, they are my personal views and that they do not represent any sorts of official roadmaps, and that anyone is welcome to disagree :)

In Budapest, we had a great conference. Chip and I showed several CloudStack use cases. Our user base is strong with over 300 production deployments. Our community is large and diverse with 2000 people on the mailing lists, but we need to keep advocating for CloudStack, make it an even greater software and grow our community. At the very least this helps us learn from each other, better our own skills and our employers IT infrastructure. At the very best AWS switches to CloudStack :)

So here are some food for thoughts that will hopefully excite you, want to get engage, talk about CloudStack and bring on board your friends:

On the code:
-----------------
- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board
We have successfully moved to GitHub pull requests, we should stop using RB
- 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
I am going to push for IP clearance of ec2stack and gstack to get them under ASF governance.
- Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
- 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).
This could become a type of release artifact that could be easily continuously built.


On the ecosystem:
-------------------------
We have a really strong ecosystem. From configuration management tools, API wrappers, PaaS plugins etc.
We need to feature our ecosystem clearly on our website, support it and keep on growing it as new technologies emerge.

Things that come to mind:
- Push to get our Ansible module into the Ansible core
- Publish “official” chef recipes to deploy CloudStack
- Identify and publish “official” Puppet recipes
- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
- Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
- Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
- Work actively on up to date integration with CloudFoundry

On documentation:
-------------------------
I and couple others successfully moved our docs to the Read The Docs service. This was a first great move but we need to finish the job.
We need to rethink our documentation tree, maybe merge all guides in one, correct the docs, create a new theme for it.
This is an easy area to contribute to if you are using cloudstack. Just send a pull request (click on the top right ribbon).
If you don’t know how, then it will teach you how to use github, great exercise.
We also need to routinely build the multi languages support.

On Events:
-------------------------
We have at least four great events coming in 2015. Austin, Seattle, Tokyo and Dublin.
Let’s meet at one of those events.
Let’s submit a talk or a poster, tell everyone about the great stuff you are doing with CloudStack.
If you are in a position at your company to sponsor the event, please do, we need your help to make those great events.
Open Source is about collaboration and sharing, so let’s meet around the globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)


Finally on the Website:
-------------------------
We can live without a website, but having a good one is a great way to showcase our community and our work.
The current website is an improvement to what it was before but we need to do much much better.
I recently did a small experiment and we could use github page. There is now a gh-pages branch in our repo.
Anyone can actually contribute to that branch and it will rebuild a site automatically.
If we could find a great web designer in our community, we could rebuild our site and make it a very modern, polished site that would attract even more people.
It’s an easy one, it just needs someone to step up and do it.

There is much more to this list, It is almost a brain dump. I figure that if we could work on those five areas and improve them, even just a bit, our project would be so much stronger. Some of them are easy, it’s just a question of sitting down and doing it.

So while I cannot tell you what to do, and cannot assign people to some of these tasks. I encourage you to look at that list and see if there is an area or a thought that strikes your mind and excites you. If there is, the only think I ask is that you send a pull request or at the very least an email to tell the rest of us what you are doing.

To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid software in production but we also want to work on the latest cool technologies. I think we can do both, and if we can do something that is both cool and rock solid in prod than we will have that amazing feeling of accomplishment and doing great work

Let’s keep on making CloudStack great in the coming year and let’s have fun doing it,

-Sebastien
@sebgoa


  

Re: Thoughts on CloudStack while starting as new VP

[Sally Khudairi <sk...@apache.org>]

Wow --Sebastien! That looks like a well-thought-out plan.
I know that there's been a lot of energy put towards making Apache CloudStack an even better project. Here's to continued building from strength to strength --hats off to all involved! I'll be at ApacheCon and happy to meet up should you need anything.
Warmly,Sally

      From: Sebastien Goasguen <ru...@gmail.com>
 To: dev@cloudstack.apache.org; users@cloudstack.apache.org; marketing@cloudstack.apache.org 
 Sent: Monday, 23 March 2015, 10:15
 Subject: Thoughts on CloudStack while starting as new VP
   
Dear members of the CloudStack community,

Last week the Apache Software Foundation board unanimously voted a resolution to make me the new VP of Apache CloudStack. This came after a unanimous vote of the CloudStack PMC and is regular process of our community as described in our bylaws.

I am excited to take on this new role after two amazing VP (Chip and Hugo) since CloudStack came to the ASF. Many thanks to them and especially Hugo for the work he has done in the past year.

The ASF is setup so that the governance of a project really belongs to the community itself. CloudStack is what we all make it to be, we all have equal footing when time comes to develop the code, create events, take decisions and so on. As VP I do not have a special say in our direction. This governance model is in stark contrast with other open source project that follow more of a benevolent dictator model. I mention this as a bit of disclaimer and to re-enforce the fact that while I have views about what we should do, they are my personal views and that they do not represent any sorts of official roadmaps, and that anyone is welcome to disagree :)

In Budapest, we had a great conference. Chip and I showed several CloudStack use cases. Our user base is strong with over 300 production deployments. Our community is large and diverse with 2000 people on the mailing lists, but we need to keep advocating for CloudStack, make it an even greater software and grow our community. At the very least this helps us learn from each other, better our own skills and our employers IT infrastructure. At the very best AWS switches to CloudStack :)

So here are some food for thoughts that will hopefully excite you, want to get engage, talk about CloudStack and bring on board your friends:

On the code:
-----------------
- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board
We have successfully moved to GitHub pull requests, we should stop using RB
- 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
I am going to push for IP clearance of ec2stack and gstack to get them under ASF governance.
- Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
- 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).
This could become a type of release artifact that could be easily continuously built.


On the ecosystem:
-------------------------
We have a really strong ecosystem. From configuration management tools, API wrappers, PaaS plugins etc.
We need to feature our ecosystem clearly on our website, support it and keep on growing it as new technologies emerge.

Things that come to mind:
- Push to get our Ansible module into the Ansible core
- Publish “official” chef recipes to deploy CloudStack
- Identify and publish “official” Puppet recipes
- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
- Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
- Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
- Work actively on up to date integration with CloudFoundry

On documentation:
-------------------------
I and couple others successfully moved our docs to the Read The Docs service. This was a first great move but we need to finish the job.
We need to rethink our documentation tree, maybe merge all guides in one, correct the docs, create a new theme for it.
This is an easy area to contribute to if you are using cloudstack. Just send a pull request (click on the top right ribbon).
If you don’t know how, then it will teach you how to use github, great exercise.
We also need to routinely build the multi languages support.

On Events:
-------------------------
We have at least four great events coming in 2015. Austin, Seattle, Tokyo and Dublin.
Let’s meet at one of those events.
Let’s submit a talk or a poster, tell everyone about the great stuff you are doing with CloudStack.
If you are in a position at your company to sponsor the event, please do, we need your help to make those great events.
Open Source is about collaboration and sharing, so let’s meet around the globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)


Finally on the Website:
-------------------------
We can live without a website, but having a good one is a great way to showcase our community and our work.
The current website is an improvement to what it was before but we need to do much much better.
I recently did a small experiment and we could use github page. There is now a gh-pages branch in our repo.
Anyone can actually contribute to that branch and it will rebuild a site automatically.
If we could find a great web designer in our community, we could rebuild our site and make it a very modern, polished site that would attract even more people.
It’s an easy one, it just needs someone to step up and do it.

There is much more to this list, It is almost a brain dump. I figure that if we could work on those five areas and improve them, even just a bit, our project would be so much stronger. Some of them are easy, it’s just a question of sitting down and doing it.

So while I cannot tell you what to do, and cannot assign people to some of these tasks. I encourage you to look at that list and see if there is an area or a thought that strikes your mind and excites you. If there is, the only think I ask is that you send a pull request or at the very least an email to tell the rest of us what you are doing.

To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid software in production but we also want to work on the latest cool technologies. I think we can do both, and if we can do something that is both cool and rock solid in prod than we will have that amazing feeling of accomplishment and doing great work

Let’s keep on making CloudStack great in the coming year and let’s have fun doing it,

-Sebastien
@sebgoa


  

Re: Thoughts on CloudStack while starting as new VP

[Ian Rae <ir...@cloudops.com>]

Great overview of important priorities Seb and proof positive of your
qualification in the VP role.

Development process, marketing/`communications, refactoring of secondary
storage and networking, support for Docker/CloudFoundry, Hadoop/Spark and
AWS/OpenStack APIs are on my mind. Sorting through the existing JIRAs and
associated housekeeping will be important to moving forward.

Interested in having CloudOps contribute where we are well positioned to
add value, and definitely up for meeting in Austin!

*Ian Rae*
CEO | PDG
c: *514.944.4008*

*CloudOps** | *Cloud Infrastructure and Networking Solutions
www.cloudops.com *|* 420 rue Guy *|* Montreal *|* Canada *|* H3J 1S6

On Mon, Mar 23, 2015 at 10:15 AM, Sebastien Goasguen <ru...@gmail.com>
wrote:

> Dear members of the CloudStack community,
>
> Last week the Apache Software Foundation board unanimously voted a
> resolution to make me the new VP of Apache CloudStack. This came after a
> unanimous vote of the CloudStack PMC and is regular process of our
> community as described in our bylaws.
>
> I am excited to take on this new role after two amazing VP (Chip and Hugo)
> since CloudStack came to the ASF. Many thanks to them and especially Hugo
> for the work he has done in the past year.
>
> The ASF is setup so that the governance of a project really belongs to the
> community itself. CloudStack is what we all make it to be, we all have
> equal footing when time comes to develop the code, create events, take
> decisions and so on. As VP I do not have a special say in our direction.
> This governance model is in stark contrast with other open source project
> that follow more of a benevolent dictator model. I mention this as a bit of
> disclaimer and to re-enforce the fact that while I have views about what we
> should do, they are my personal views and that they do not represent any
> sorts of official roadmaps, and that anyone is welcome to disagree :)
>
> In Budapest, we had a great conference. Chip and I showed several
> CloudStack use cases. Our user base is strong with over 300 production
> deployments. Our community is large and diverse with 2000 people on the
> mailing lists, but we need to keep advocating for CloudStack, make it an
> even greater software and grow our community. At the very least this helps
> us learn from each other, better our own skills and our employers IT
> infrastructure. At the very best AWS switches to CloudStack :)
>
> So here are some food for thoughts that will hopefully excite you, want to
> get engage, talk about CloudStack and bring on board your friends:
>
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
> Board
> We have successfully moved to GitHub pull requests, we should stop using RB
> - 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
> I am going to push for IP clearance of ec2stack and gstack to get them
> under ASF governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time
> we do the same.
> - 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).
> This could become a type of release artifact that could be easily
> continuously built.
>
>
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools,
> API wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and
> keep on growing it as new technologies emerge.
>
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us
> from having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think
> Hadoop, Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
>
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs
> service. This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one,
> correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just
> send a pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great
> exercise.
> We also need to routinely build the multi languages support.
>
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo
> and Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you
> are doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do,
> we need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the
> globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
>
>
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to
> showcase our community and our work.
> The current website is an improvement to what it was before but we need to
> do much much better.
> I recently did a small experiment and we could use github page. There is
> now a gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site
> automatically.
> If we could find a great web designer in our community, we could rebuild
> our site and make it a very modern, polished site that would attract even
> more people.
> It’s an easy one, it just needs someone to step up and do it.
>
> There is much more to this list, It is almost a brain dump. I figure that
> if we could work on those five areas and improve them, even just a bit, our
> project would be so much stronger. Some of them are easy, it’s just a
> question of sitting down and doing it.
>
> So while I cannot tell you what to do, and cannot assign people to some of
> these tasks. I encourage you to look at that list and see if there is an
> area or a thought that strikes your mind and excites you. If there is, the
> only think I ask is that you send a pull request or at the very least an
> email to tell the rest of us what you are doing.
>
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
> solid software in production but we also want to work on the latest cool
> technologies. I think we can do both, and if we can do something that is
> both cool and rock solid in prod than we will have that amazing feeling of
> accomplishment and doing great work
>
> Let’s keep on making CloudStack great in the coming year and let’s have
> fun doing it,
>
> -Sebastien
> @sebgoa
>
>

Re: Thoughts on CloudStack while starting as new VP

[Rohit Yadav <ro...@shapeblue.com>]

Great proposals Sebastien! Let's AWSAPI, improve code, remove dead code, cleanup JIRA/RB cleanup and move to Github PR.

I hope we’ll have a better UIs for ACS users soon!

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.yadav@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Marco Sinhoreli <ma...@shapeblue.com>]

Sebastien,


About documentation, now transifex uses fragmented texts and it creates
some times no sense texts translated. My suggestion is get together the
text blocks but I think it will be a hard work to reorganize code and
transifex. Another thing is support UTF-8 to supports special characters
in others languages.

Best regards,

Marco Sinhoreli
Consultant Manager




Phone: +55 21 2586 6390 | Fax: +55 21 2586 6002 | Mobile: +55 21 99159
4713 | Mobile: +55 21 98276 3636
Praia de Botafogo 501, bloco 1 - sala 101, Botafogo, Rio de Janeiro, RJ -
Brazil - CEP 22250-040
marco.sinhoreli@shapeblue.com | www.shapeblue.com
<http://www.shapeblue.com/> | Twitter:@shapeBlue
<https://twitter.com/#!/shapeblue>








On 23/03/15 11:15, "Sebastien Goasguen" <ru...@gmail.com> wrote:

>Dear members of the CloudStack community,
>
>Last week the Apache Software Foundation board unanimously voted a
>resolution to make me the new VP of Apache CloudStack. This came after a
>unanimous vote of the CloudStack PMC and is regular process of our
>community as described in our bylaws.
>
>I am excited to take on this new role after two amazing VP (Chip and
>Hugo) since CloudStack came to the ASF. Many thanks to them and
>especially Hugo for the work he has done in the past year.
>
>The ASF is setup so that the governance of a project really belongs to
>the community itself. CloudStack is what we all make it to be, we all
>have equal footing when time comes to develop the code, create events,
>take decisions and so on. As VP I do not have a special say in our
>direction. This governance model is in stark contrast with other open
>source project that follow more of a benevolent dictator model. I mention
>this as a bit of disclaimer and to re-enforce the fact that while I have
>views about what we should do, they are my personal views and that they
>do not represent any sorts of official roadmaps, and that anyone is
>welcome to disagree :)
>
>In Budapest, we had a great conference. Chip and I showed several
>CloudStack use cases. Our user base is strong with over 300 production
>deployments. Our community is large and diverse with 2000 people on the
>mailing lists, but we need to keep advocating for CloudStack, make it an
>even greater software and grow our community. At the very least this
>helps us learn from each other, better our own skills and our employers
>IT infrastructure. At the very best AWS switches to CloudStack :)
>
>So here are some food for thoughts that will hopefully excite you, want
>to get engage, talk about CloudStack and bring on board your friends:
>
>On the code:
>-----------------
>- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
>Board
>We have successfully moved to GitHub pull requests, we should stop using
>RB
>- 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
>I am going to push for IP clearance of ec2stack and gstack to get them
>under ASF governance.
>- Several Cloud Providers have unveiled new CloudStack UI, maybe it¹s
>time we do the same.
>- 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).
>This could become a type of release artifact that could be easily
>continuously built.
>
>
>On the ecosystem:
>-------------------------
>We have a really strong ecosystem. From configuration management tools,
>API wrappers, PaaS plugins etc.
>We need to feature our ecosystem clearly on our website, support it and
>keep on growing it as new technologies emerge.
>
>Things that come to mind:
>- Push to get our Ansible module into the Ansible core
>- Publish ³official² chef recipes to deploy CloudStack
>- Identify and publish ³official² Puppet recipes
>- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
>- Finally cleanup cloud-init support for CloudStack, this is preventing
>us from having upstream centOS templates.
>- Publish playbooks/recipes to deploy workloads on CloudStack (think
>Hadoop, Spark, Kubernetes)
>- Work actively on up to date integration with CloudFoundry
>
>On documentation:
>-------------------------
>I and couple others successfully moved our docs to the Read The Docs
>service. This was a first great move but we need to finish the job.
>We need to rethink our documentation tree, maybe merge all guides in one,
>correct the docs, create a new theme for it.
>This is an easy area to contribute to if you are using cloudstack. Just
>send a pull request (click on the top right ribbon).
>If you don¹t know how, then it will teach you how to use github, great
>exercise.
>We also need to routinely build the multi languages support.
>
>On Events:
>-------------------------
>We have at least four great events coming in 2015. Austin, Seattle, Tokyo
>and Dublin.
>Let¹s meet at one of those events.
>Let¹s submit a talk or a poster, tell everyone about the great stuff you
>are doing with CloudStack.
>If you are in a position at your company to sponsor the event, please do,
>we need your help to make those great events.
>Open Source is about collaboration and sharing, so let¹s meet around the
>globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker
>:)
>
>
>Finally on the Website:
>-------------------------
>We can live without a website, but having a good one is a great way to
>showcase our community and our work.
>The current website is an improvement to what it was before but we need
>to do much much better.
>I recently did a small experiment and we could use github page. There is
>now a gh-pages branch in our repo.
>Anyone can actually contribute to that branch and it will rebuild a site
>automatically.
>If we could find a great web designer in our community, we could rebuild
>our site and make it a very modern, polished site that would attract even
>more people.
>It¹s an easy one, it just needs someone to step up and do it.
>
>There is much more to this list, It is almost a brain dump. I figure that
>if we could work on those five areas and improve them, even just a bit,
>our project would be so much stronger. Some of them are easy, it¹s just a
>question of sitting down and doing it.
>
>So while I cannot tell you what to do, and cannot assign people to some
>of these tasks. I encourage you to look at that list and see if there is
>an area or a thought that strikes your mind and excites you. If there is,
>the only think I ask is that you send a pull request or at the very least
>an email to tell the rest of us what you are doing.
>
>To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
>solid software in production but we also want to work on the latest cool
>technologies. I think we can do both, and if we can do something that is
>both cool and rock solid in prod than we will have that amazing feeling
>of accomplishment and doing great work
>
>Let¹s keep on making CloudStack great in the coming year and let¹s have
>fun doing it,
>
>-Sebastien
>@sebgoa
>

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Thoughts on CloudStack while starting as new VP

[Ian Rae <ir...@cloudops.com>]

Great overview of important priorities Seb and proof positive of your
qualification in the VP role.

Development process, marketing/`communications, refactoring of secondary
storage and networking, support for Docker/CloudFoundry, Hadoop/Spark and
AWS/OpenStack APIs are on my mind. Sorting through the existing JIRAs and
associated housekeeping will be important to moving forward.

Interested in having CloudOps contribute where we are well positioned to
add value, and definitely up for meeting in Austin!

*Ian Rae*
CEO | PDG
c: *514.944.4008*

*CloudOps** | *Cloud Infrastructure and Networking Solutions
www.cloudops.com *|* 420 rue Guy *|* Montreal *|* Canada *|* H3J 1S6

On Mon, Mar 23, 2015 at 10:15 AM, Sebastien Goasguen <ru...@gmail.com>
wrote:

> Dear members of the CloudStack community,
>
> Last week the Apache Software Foundation board unanimously voted a
> resolution to make me the new VP of Apache CloudStack. This came after a
> unanimous vote of the CloudStack PMC and is regular process of our
> community as described in our bylaws.
>
> I am excited to take on this new role after two amazing VP (Chip and Hugo)
> since CloudStack came to the ASF. Many thanks to them and especially Hugo
> for the work he has done in the past year.
>
> The ASF is setup so that the governance of a project really belongs to the
> community itself. CloudStack is what we all make it to be, we all have
> equal footing when time comes to develop the code, create events, take
> decisions and so on. As VP I do not have a special say in our direction.
> This governance model is in stark contrast with other open source project
> that follow more of a benevolent dictator model. I mention this as a bit of
> disclaimer and to re-enforce the fact that while I have views about what we
> should do, they are my personal views and that they do not represent any
> sorts of official roadmaps, and that anyone is welcome to disagree :)
>
> In Budapest, we had a great conference. Chip and I showed several
> CloudStack use cases. Our user base is strong with over 300 production
> deployments. Our community is large and diverse with 2000 people on the
> mailing lists, but we need to keep advocating for CloudStack, make it an
> even greater software and grow our community. At the very least this helps
> us learn from each other, better our own skills and our employers IT
> infrastructure. At the very best AWS switches to CloudStack :)
>
> So here are some food for thoughts that will hopefully excite you, want to
> get engage, talk about CloudStack and bring on board your friends:
>
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
> Board
> We have successfully moved to GitHub pull requests, we should stop using RB
> - 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
> I am going to push for IP clearance of ec2stack and gstack to get them
> under ASF governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time
> we do the same.
> - 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).
> This could become a type of release artifact that could be easily
> continuously built.
>
>
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools,
> API wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and
> keep on growing it as new technologies emerge.
>
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us
> from having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think
> Hadoop, Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
>
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs
> service. This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one,
> correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just
> send a pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great
> exercise.
> We also need to routinely build the multi languages support.
>
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo
> and Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you
> are doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do,
> we need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the
> globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
>
>
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to
> showcase our community and our work.
> The current website is an improvement to what it was before but we need to
> do much much better.
> I recently did a small experiment and we could use github page. There is
> now a gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site
> automatically.
> If we could find a great web designer in our community, we could rebuild
> our site and make it a very modern, polished site that would attract even
> more people.
> It’s an easy one, it just needs someone to step up and do it.
>
> There is much more to this list, It is almost a brain dump. I figure that
> if we could work on those five areas and improve them, even just a bit, our
> project would be so much stronger. Some of them are easy, it’s just a
> question of sitting down and doing it.
>
> So while I cannot tell you what to do, and cannot assign people to some of
> these tasks. I encourage you to look at that list and see if there is an
> area or a thought that strikes your mind and excites you. If there is, the
> only think I ask is that you send a pull request or at the very least an
> email to tell the rest of us what you are doing.
>
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
> solid software in production but we also want to work on the latest cool
> technologies. I think we can do both, and if we can do something that is
> both cool and rock solid in prod than we will have that amazing feeling of
> accomplishment and doing great work
>
> Let’s keep on making CloudStack great in the coming year and let’s have
> fun doing it,
>
> -Sebastien
> @sebgoa
>
>

Re: Thoughts on CloudStack while starting as new VP

[Osay Osman Yuuni <oy...@gmail.com>]

First of all congratulations on your appointment.  It is ample recognition
for your work at the project.  I'm delighted with the passion in this
piece.  I for one think you're on the right path.  It is frustrating to
note that everyone who's sat at this table has gotten up filled and content
yet when one looks at the internet there's so little on Cloudstack.  Kind
of reminds me of Novell, good products but poor visibility.  I've followed
with interest the latest developments in infrastructure ala Docker,
kubernetes and CoreOS and every time Cloudstack is last to be served,
thanks to efforts from yourself and other colleagues whose passion for the
project makes you go the extra mile to bring these into the Cloudstack
sphere.

The experience of being last to the table is set to change with this well
thought out plan.  I hope the community will take this in their stride so
that Cloudstack will bring cloud enthusiast salivating to dine at.  Let the
UX gurus come out with a UI that will make ACS stand out and friends with
Kubernetes and CoreOS experience factor in some goodies to help ACS take
the next logical step away from IaaS.  As for configuration management
there have been really good work done by the community but as Seb says, it
all needs to be tied into the ecosystem to make them an integral part of
ACS.  The product is already easy enough to deploy and use but I think
these tools could make it even easier to manage.

Kudos Seb.

Osay

On 23 March 2015 at 16:15, Sebastien Goasguen <ru...@gmail.com> wrote:

> Dear members of the CloudStack community,
>
> Last week the Apache Software Foundation board unanimously voted a
> resolution to make me the new VP of Apache CloudStack. This came after a
> unanimous vote of the CloudStack PMC and is regular process of our
> community as described in our bylaws.
>
> I am excited to take on this new role after two amazing VP (Chip and Hugo)
> since CloudStack came to the ASF. Many thanks to them and especially Hugo
> for the work he has done in the past year.
>
> The ASF is setup so that the governance of a project really belongs to the
> community itself. CloudStack is what we all make it to be, we all have
> equal footing when time comes to develop the code, create events, take
> decisions and so on. As VP I do not have a special say in our direction.
> This governance model is in stark contrast with other open source project
> that follow more of a benevolent dictator model. I mention this as a bit of
> disclaimer and to re-enforce the fact that while I have views about what we
> should do, they are my personal views and that they do not represent any
> sorts of official roadmaps, and that anyone is welcome to disagree :)
>
> In Budapest, we had a great conference. Chip and I showed several
> CloudStack use cases. Our user base is strong with over 300 production
> deployments. Our community is large and diverse with 2000 people on the
> mailing lists, but we need to keep advocating for CloudStack, make it an
> even greater software and grow our community. At the very least this helps
> us learn from each other, better our own skills and our employers IT
> infrastructure. At the very best AWS switches to CloudStack :)
>
> So here are some food for thoughts that will hopefully excite you, want to
> get engage, talk about CloudStack and bring on board your friends:
>
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review
> Board
> We have successfully moved to GitHub pull requests, we should stop using RB
> - 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
> I am going to push for IP clearance of ec2stack and gstack to get them
> under ASF governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time
> we do the same.
> - 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).
> This could become a type of release artifact that could be easily
> continuously built.
>
>
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools,
> API wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and
> keep on growing it as new technologies emerge.
>
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us
> from having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think
> Hadoop, Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
>
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs
> service. This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one,
> correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just
> send a pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great
> exercise.
> We also need to routinely build the multi languages support.
>
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo
> and Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you
> are doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do,
> we need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the
> globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
>
>
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to
> showcase our community and our work.
> The current website is an improvement to what it was before but we need to
> do much much better.
> I recently did a small experiment and we could use github page. There is
> now a gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site
> automatically.
> If we could find a great web designer in our community, we could rebuild
> our site and make it a very modern, polished site that would attract even
> more people.
> It’s an easy one, it just needs someone to step up and do it.
>
> There is much more to this list, It is almost a brain dump. I figure that
> if we could work on those five areas and improve them, even just a bit, our
> project would be so much stronger. Some of them are easy, it’s just a
> question of sitting down and doing it.
>
> So while I cannot tell you what to do, and cannot assign people to some of
> these tasks. I encourage you to look at that list and see if there is an
> area or a thought that strikes your mind and excites you. If there is, the
> only think I ask is that you send a pull request or at the very least an
> email to tell the rest of us what you are doing.
>
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock
> solid software in production but we also want to work on the latest cool
> technologies. I think we can do both, and if we can do something that is
> both cool and rock solid in prod than we will have that amazing feeling of
> accomplishment and doing great work
>
> Let’s keep on making CloudStack great in the coming year and let’s have
> fun doing it,
>
> -Sebastien
> @sebgoa
>
>

Re: Thoughts on CloudStack while starting as new VP

[Remi Bergsma <RB...@schubergphilis.com>]

Congratulations Sebastien!

Totally agree :-) It would really help in speeding up the release cycle and achieve high quality at the same time. 

We should aim for a release every month if you ask me. I know that sounds impossible now, but let's discuss with such a goal in mind and see what we can do together. Because I believe we can do a lot. 

At Schuberg Philis we have two serious production environments (running 4.4.2) that we would like to deploy new versions to often (one after another). That should also be convincing for others to install the release or do the upgrade. If only we find ways to make high quality releases often without regression. Further automating (functional) testing, plus making it easier is only one of the things one can think of.

Definitely willing to help making this successful :-)

We could set up a meeting / hackathon about this in Austin to give it a boost?

Regards, Remi

Sent from my iPhone

> On 24 Mar 2015, at 20:27, Sebastien Goasguen <ru...@gmail.com> wrote:
> 
> 
>> On Mar 24, 2015, at 6:56 PM, Raja Pullela <ra...@citrix.com> wrote:
>> 
>> Very nice, Congratulations Sebastien!  
>> Looking forward to collaborate on list of things you have identified!
> 
> Thanks Raja, it definitely would be great to get your team’s help with JIRA.
> I think we need a strong dedicated effort to clear it up and close all old issues.
> 
> We also need to find a way to develop master better to avoid regressions.
> There was a lot of talk last summer about gitflow or the like, and we should resurrect this with some pragmatic action that we can build on.
> 
> For instance thoughts that I have are to make sure that we develop in ‘development’ branch and leave master alone.
> Then build releases on master through merges.
> 
> Getting you and your team (and everyone else of course) behind such a scheme (TBD still) would be a huge help.
> 
> -sebastien
> 
>> Raja
>> 
>> -----Original Message-----
>> From: Sebastien Goasguen [mailto:runseb@gmail.com] 
>> Sent: Monday, March 23, 2015 7:46 PM
>> To: dev@cloudstack.apache.org; users@cloudstack.apache.org; marketing@cloudstack.apache.org
>> Subject: Thoughts on CloudStack while starting as new VP
>> 
>> Dear members of the CloudStack community,
>> 
>> Last week the Apache Software Foundation board unanimously voted a resolution to make me the new VP of Apache CloudStack. This came after a unanimous vote of the CloudStack PMC and is regular process of our community as described in our bylaws.
>> 
>> I am excited to take on this new role after two amazing VP (Chip and Hugo) since CloudStack came to the ASF. Many thanks to them and especially Hugo for the work he has done in the past year.
>> 
>> The ASF is setup so that the governance of a project really belongs to the community itself. CloudStack is what we all make it to be, we all have equal footing when time comes to develop the code, create events, take decisions and so on. As VP I do not have a special say in our direction. This governance model is in stark contrast with other open source project that follow more of a benevolent dictator model. I mention this as a bit of disclaimer and to re-enforce the fact that while I have views about what we should do, they are my personal views and that they do not represent any sorts of official roadmaps, and that anyone is welcome to disagree :)
>> 
>> In Budapest, we had a great conference. Chip and I showed several CloudStack use cases. Our user base is strong with over 300 production deployments. Our community is large and diverse with 2000 people on the mailing lists, but we need to keep advocating for CloudStack, make it an even greater software and grow our community. At the very least this helps us learn from each other, better our own skills and our employers IT infrastructure. At the very best AWS switches to CloudStack :)
>> 
>> So here are some food for thoughts that will hopefully excite you, want to get engage, talk about CloudStack and bring on board your friends:
>> 
>> On the code:
>> -----------------
>> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board We have successfully moved to GitHub pull requests, we should stop using RB
>> - 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 I am going to push for IP clearance of ec2stack and gstack to get them under ASF governance.
>> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
>> - 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).
>> This could become a type of release artifact that could be easily continuously built.
>> 
>> 
>> On the ecosystem:
>> -------------------------
>> We have a really strong ecosystem. From configuration management tools, API wrappers, PaaS plugins etc.
>> We need to feature our ecosystem clearly on our website, support it and keep on growing it as new technologies emerge.
>> 
>> Things that come to mind:
>> - Push to get our Ansible module into the Ansible core
>> - Publish “official” chef recipes to deploy CloudStack
>> - Identify and publish “official” Puppet recipes
>> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
>> - Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
>> - Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
>> - Work actively on up to date integration with CloudFoundry
>> 
>> On documentation:
>> -------------------------
>> I and couple others successfully moved our docs to the Read The Docs service. This was a first great move but we need to finish the job.
>> We need to rethink our documentation tree, maybe merge all guides in one, correct the docs, create a new theme for it.
>> This is an easy area to contribute to if you are using cloudstack. Just send a pull request (click on the top right ribbon).
>> If you don’t know how, then it will teach you how to use github, great exercise.
>> We also need to routinely build the multi languages support.
>> 
>> On Events:
>> -------------------------
>> We have at least four great events coming in 2015. Austin, Seattle, Tokyo and Dublin.
>> Let’s meet at one of those events.
>> Let’s submit a talk or a poster, tell everyone about the great stuff you are doing with CloudStack.
>> If you are in a position at your company to sponsor the event, please do, we need your help to make those great events.
>> Open Source is about collaboration and sharing, so let’s meet around the globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
>> 
>> 
>> Finally on the Website:
>> -------------------------
>> We can live without a website, but having a good one is a great way to showcase our community and our work.
>> The current website is an improvement to what it was before but we need to do much much better.
>> I recently did a small experiment and we could use github page. There is now a gh-pages branch in our repo.
>> Anyone can actually contribute to that branch and it will rebuild a site automatically.
>> If we could find a great web designer in our community, we could rebuild our site and make it a very modern, polished site that would attract even more people.
>> It’s an easy one, it just needs someone to step up and do it.
>> 
>> There is much more to this list, It is almost a brain dump. I figure that if we could work on those five areas and improve them, even just a bit, our project would be so much stronger. Some of them are easy, it’s just a question of sitting down and doing it.
>> 
>> So while I cannot tell you what to do, and cannot assign people to some of these tasks. I encourage you to look at that list and see if there is an area or a thought that strikes your mind and excites you. If there is, the only think I ask is that you send a pull request or at the very least an email to tell the rest of us what you are doing.
>> 
>> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid software in production but we also want to work on the latest cool technologies. I think we can do both, and if we can do something that is both cool and rock solid in prod than we will have that amazing feeling of accomplishment and doing great work
>> 
>> Let’s keep on making CloudStack great in the coming year and let’s have fun doing it,
>> 
>> -Sebastien
>> @sebgoa
> 

Re: Thoughts on CloudStack while starting as new VP

[Sebastien Goasguen <ru...@gmail.com>]

> On Mar 24, 2015, at 6:56 PM, Raja Pullela <ra...@citrix.com> wrote:
> 
> Very nice, Congratulations Sebastien!  
> Looking forward to collaborate on list of things you have identified!
> 

Thanks Raja, it definitely would be great to get your team’s help with JIRA.
I think we need a strong dedicated effort to clear it up and close all old issues.

We also need to find a way to develop master better to avoid regressions.
There was a lot of talk last summer about gitflow or the like, and we should resurrect this with some pragmatic action that we can build on.

For instance thoughts that I have are to make sure that we develop in ‘development’ branch and leave master alone.
Then build releases on master through merges.

Getting you and your team (and everyone else of course) behind such a scheme (TBD still) would be a huge help.

-sebastien

> Raja
> 
> -----Original Message-----
> From: Sebastien Goasguen [mailto:runseb@gmail.com] 
> Sent: Monday, March 23, 2015 7:46 PM
> To: dev@cloudstack.apache.org; users@cloudstack.apache.org; marketing@cloudstack.apache.org
> Subject: Thoughts on CloudStack while starting as new VP
> 
> Dear members of the CloudStack community,
> 
> Last week the Apache Software Foundation board unanimously voted a resolution to make me the new VP of Apache CloudStack. This came after a unanimous vote of the CloudStack PMC and is regular process of our community as described in our bylaws.
> 
> I am excited to take on this new role after two amazing VP (Chip and Hugo) since CloudStack came to the ASF. Many thanks to them and especially Hugo for the work he has done in the past year.
> 
> The ASF is setup so that the governance of a project really belongs to the community itself. CloudStack is what we all make it to be, we all have equal footing when time comes to develop the code, create events, take decisions and so on. As VP I do not have a special say in our direction. This governance model is in stark contrast with other open source project that follow more of a benevolent dictator model. I mention this as a bit of disclaimer and to re-enforce the fact that while I have views about what we should do, they are my personal views and that they do not represent any sorts of official roadmaps, and that anyone is welcome to disagree :)
> 
> In Budapest, we had a great conference. Chip and I showed several CloudStack use cases. Our user base is strong with over 300 production deployments. Our community is large and diverse with 2000 people on the mailing lists, but we need to keep advocating for CloudStack, make it an even greater software and grow our community. At the very least this helps us learn from each other, better our own skills and our employers IT infrastructure. At the very best AWS switches to CloudStack :)
> 
> So here are some food for thoughts that will hopefully excite you, want to get engage, talk about CloudStack and bring on board your friends:
> 
> On the code:
> -----------------
> - Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board We have successfully moved to GitHub pull requests, we should stop using RB
> - 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 I am going to push for IP clearance of ec2stack and gstack to get them under ASF governance.
> - Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
> - 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).
> This could become a type of release artifact that could be easily continuously built.
> 
> 
> On the ecosystem:
> -------------------------
> We have a really strong ecosystem. From configuration management tools, API wrappers, PaaS plugins etc.
> We need to feature our ecosystem clearly on our website, support it and keep on growing it as new technologies emerge.
> 
> Things that come to mind:
> - Push to get our Ansible module into the Ansible core
> - Publish “official” chef recipes to deploy CloudStack
> - Identify and publish “official” Puppet recipes
> - Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
> - Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
> - Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
> - Work actively on up to date integration with CloudFoundry
> 
> On documentation:
> -------------------------
> I and couple others successfully moved our docs to the Read The Docs service. This was a first great move but we need to finish the job.
> We need to rethink our documentation tree, maybe merge all guides in one, correct the docs, create a new theme for it.
> This is an easy area to contribute to if you are using cloudstack. Just send a pull request (click on the top right ribbon).
> If you don’t know how, then it will teach you how to use github, great exercise.
> We also need to routinely build the multi languages support.
> 
> On Events:
> -------------------------
> We have at least four great events coming in 2015. Austin, Seattle, Tokyo and Dublin.
> Let’s meet at one of those events.
> Let’s submit a talk or a poster, tell everyone about the great stuff you are doing with CloudStack.
> If you are in a position at your company to sponsor the event, please do, we need your help to make those great events.
> Open Source is about collaboration and sharing, so let’s meet around the globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)
> 
> 
> Finally on the Website:
> -------------------------
> We can live without a website, but having a good one is a great way to showcase our community and our work.
> The current website is an improvement to what it was before but we need to do much much better.
> I recently did a small experiment and we could use github page. There is now a gh-pages branch in our repo.
> Anyone can actually contribute to that branch and it will rebuild a site automatically.
> If we could find a great web designer in our community, we could rebuild our site and make it a very modern, polished site that would attract even more people.
> It’s an easy one, it just needs someone to step up and do it.
> 
> There is much more to this list, It is almost a brain dump. I figure that if we could work on those five areas and improve them, even just a bit, our project would be so much stronger. Some of them are easy, it’s just a question of sitting down and doing it.
> 
> So while I cannot tell you what to do, and cannot assign people to some of these tasks. I encourage you to look at that list and see if there is an area or a thought that strikes your mind and excites you. If there is, the only think I ask is that you send a pull request or at the very least an email to tell the rest of us what you are doing.
> 
> To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid software in production but we also want to work on the latest cool technologies. I think we can do both, and if we can do something that is both cool and rock solid in prod than we will have that amazing feeling of accomplishment and doing great work
> 
> Let’s keep on making CloudStack great in the coming year and let’s have fun doing it,
> 
> -Sebastien
> @sebgoa
> 

RE: Thoughts on CloudStack while starting as new VP

[Raja Pullela <ra...@citrix.com>]

Very nice, Congratulations Sebastien!  
Looking forward to collaborate on list of things you have identified!

Raja

-----Original Message-----
From: Sebastien Goasguen [mailto:runseb@gmail.com] 
Sent: Monday, March 23, 2015 7:46 PM
To: dev@cloudstack.apache.org; users@cloudstack.apache.org; marketing@cloudstack.apache.org
Subject: Thoughts on CloudStack while starting as new VP

Dear members of the CloudStack community,

Last week the Apache Software Foundation board unanimously voted a resolution to make me the new VP of Apache CloudStack. This came after a unanimous vote of the CloudStack PMC and is regular process of our community as described in our bylaws.

I am excited to take on this new role after two amazing VP (Chip and Hugo) since CloudStack came to the ASF. Many thanks to them and especially Hugo for the work he has done in the past year.

The ASF is setup so that the governance of a project really belongs to the community itself. CloudStack is what we all make it to be, we all have equal footing when time comes to develop the code, create events, take decisions and so on. As VP I do not have a special say in our direction. This governance model is in stark contrast with other open source project that follow more of a benevolent dictator model. I mention this as a bit of disclaimer and to re-enforce the fact that while I have views about what we should do, they are my personal views and that they do not represent any sorts of official roadmaps, and that anyone is welcome to disagree :)

In Budapest, we had a great conference. Chip and I showed several CloudStack use cases. Our user base is strong with over 300 production deployments. Our community is large and diverse with 2000 people on the mailing lists, but we need to keep advocating for CloudStack, make it an even greater software and grow our community. At the very least this helps us learn from each other, better our own skills and our employers IT infrastructure. At the very best AWS switches to CloudStack :)

So here are some food for thoughts that will hopefully excite you, want to get engage, talk about CloudStack and bring on board your friends:

On the code:
-----------------
- Keep improving quality, remove dead code, cleanup JIRA, cleanup Review Board We have successfully moved to GitHub pull requests, we should stop using RB
- 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 I am going to push for IP clearance of ec2stack and gstack to get them under ASF governance.
- Several Cloud Providers have unveiled new CloudStack UI, maybe it’s time we do the same.
- 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).
This could become a type of release artifact that could be easily continuously built.


On the ecosystem:
-------------------------
We have a really strong ecosystem. From configuration management tools, API wrappers, PaaS plugins etc.
We need to feature our ecosystem clearly on our website, support it and keep on growing it as new technologies emerge.

Things that come to mind:
- Push to get our Ansible module into the Ansible core
- Publish “official” chef recipes to deploy CloudStack
- Identify and publish “official” Puppet recipes
- Build Docker native templates (coreOS, rancherOS, Snappy, Atomic)
- Finally cleanup cloud-init support for CloudStack, this is preventing us from having upstream centOS templates.
- Publish playbooks/recipes to deploy workloads on CloudStack (think Hadoop, Spark, Kubernetes)
- Work actively on up to date integration with CloudFoundry

On documentation:
-------------------------
I and couple others successfully moved our docs to the Read The Docs service. This was a first great move but we need to finish the job.
We need to rethink our documentation tree, maybe merge all guides in one, correct the docs, create a new theme for it.
This is an easy area to contribute to if you are using cloudstack. Just send a pull request (click on the top right ribbon).
If you don’t know how, then it will teach you how to use github, great exercise.
We also need to routinely build the multi languages support.

On Events:
-------------------------
We have at least four great events coming in 2015. Austin, Seattle, Tokyo and Dublin.
Let’s meet at one of those events.
Let’s submit a talk or a poster, tell everyone about the great stuff you are doing with CloudStack.
If you are in a position at your company to sponsor the event, please do, we need your help to make those great events.
Open Source is about collaboration and sharing, so let’s meet around the globe from Sao Paulo to Dublin to Tokyo and talk Cloud, DevOps and Docker :)


Finally on the Website:
-------------------------
We can live without a website, but having a good one is a great way to showcase our community and our work.
The current website is an improvement to what it was before but we need to do much much better.
I recently did a small experiment and we could use github page. There is now a gh-pages branch in our repo.
Anyone can actually contribute to that branch and it will rebuild a site automatically.
If we could find a great web designer in our community, we could rebuild our site and make it a very modern, polished site that would attract even more people.
It’s an easy one, it just needs someone to step up and do it.

There is much more to this list, It is almost a brain dump. I figure that if we could work on those five areas and improve them, even just a bit, our project would be so much stronger. Some of them are easy, it’s just a question of sitting down and doing it.

So while I cannot tell you what to do, and cannot assign people to some of these tasks. I encourage you to look at that list and see if there is an area or a thought that strikes your mind and excites you. If there is, the only think I ask is that you send a pull request or at the very least an email to tell the rest of us what you are doing.

To conclude, we do have a bit of bi-polar syndrome in tech, we need rock solid software in production but we also want to work on the latest cool technologies. I think we can do both, and if we can do something that is both cool and rock solid in prod than we will have that amazing feeling of accomplishment and doing great work

Let’s keep on making CloudStack great in the coming year and let’s have fun doing it,

-Sebastien
@sebgoa