Re: Introduction

[Will Stevens]

Great to have you supporting.  Welcome Jamie...

Cheers,

*Will Stevens*
Chief Technology Officer
t 514.447.3456 x1301

<https://goo.gl/NYZ8KK>


On Thu, May 12, 2022 at 10:23 AM Jamie Pell 
wrote:

> Hi all,
>
> I've recently started working with Ivet and helping her out with some of
> the community marketing for the CloudStack community - so just wanted to
> say hi to everybody.
>
> Ivet has recently gone on maternity leave so I'm going to be interacting
> on the mailing lists regularly now. I'm very much looking forward to
> getting to know some of the great members of the community and am open to
> any guidance anybody may have for me. I'm going to be picking up organising
> of CCC this year amongst other tasks.
>
> Kind regards,
>
>
>
>

Re: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Simon Weller

[Will Stevens]

Congrats Simon.  Well deserved for sure.  You have been a force of
dedication for the community and I am really happy to see you taking on
this role.

Cheers,

*Will Stevens*
Chief Technology Officer
t 514.447.3456 x1301

<https://goo.gl/NYZ8KK>


On Thu, Mar 17, 2022 at 12:30 PM Giles Sirett 
wrote:

> Many Congratulations Simon
>
> Gabriel - thank you so much for your hard work over the last year - you'll
> be a difficult act to follow!!
>
> Kind Regards
> Giles
>
>
>
>
> -Original Message-
> From: Nicolas Vazquez 
> Sent: 17 March 2022 12:45
> To: us...@cloudstack.apache.org; dev 
> Subject: Re: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project -
> Simon Weller
>
> Congratulations Simon! And thanks Gabriel for your great work!
>
> Regards,
> Nicolas Vazquez
> 
> From: Gabriel Beims Bräscher 
> Sent: Thursday, March 17, 2022 6:55:26 AM
> To: users ; dev 
> Subject: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Simon
> Weller
>
> Hello, all CloudStack community!
>
> It gives me great pleasure to announce that the ASF board last night
> accepted our PMC's nomination of Simon Weller as the next PMC Chair / VP of
> the Apache CloudStack project.
>
> I would like to thank everyone for the support I've received over the past
> year.
> It was a great honor being the PMC Chair of this amazing project/community!
>
> To Simon, my sincere congratulations, and I wish you success in the new
> role!
> Very well deserved!
>
> Please join me in congratulating Simon, the CloudStack PMC Chair / VP.
>
> Best Regards,
> Gabriel Bräscher.
>
>
>
>
>

Re: CloudStack Collaboration Conference: The Agenda is Live

[Will Stevens]

Just to follow up on Ivet's email.

The schedule has been updated on the official website as well:
http://cloudstackcollab.org/#schedule

If you see any issues or changes you would like to make to your talk,
please email me and I will update the website accordingly.

Additionally, I don't have pictures for everyone, so if you are in
incognito mode, feel free to send me along your details.  Also, if I am
missing speakers, let me know as well.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Fri, Oct 1, 2021 at 9:08 AM Ivet Petrova 
wrote:

> Hi again,
>
> Quick edit on previous email: The agenda will be visible for everyone
> after you register for the event.
> We will be very soon also posting the agenda on the official event website.
> But for now, please register to check all talks. And be sure you will be
> more than excited :)
>
> Kind regards,
>
>
>
>
> On 1 Oct 2021, at 14:56, Ivet Petrova  ivet.petr...@shapeblue.com>> wrote:
>
> Hi All,
>
> I am very excited to share that we have just published the agenda for the
> CloudStack Collaboration Conference!
> The full schedule + talks + info for speakers can be found here:
> https://events.hubilo.com/cloudstack-collaboration-conference/sessions
>
> Our target is to make the biggest online event for our community ever. So
> be sure you register now:
> https://events.hubilo.com/cloudstack-collaboration-conference/register
>
>
> Kind regards,
>
>
>

Re: CloudStack Collaboration Conference 2021 (9-12 November) - Call For Speakers

[Will Stevens]

Giles, if you wouldn't mind, I think it would be generally appreciated if
you organized a small committee of people to review the talks as you have
in the past.

Thanks for all the hard work everyone.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Fri, Jul 16, 2021 at 6:56 AM Giles Sirett 
wrote:

> Hi Ivet - this is great - thank you for getting this going. As much as I'd
> prefer to actually *see* everybody, an online conference is a very good
> second best
>
> Great to see the CFP open already. However, I notice that there's no
> deadline on the CFP - from experience we need a deadline to focus people 
> . I'd suggest a deadline in September
>
> In terms of sifting and selecting the talks (which we can only do once the
> deadline is passed) , I'm happy to help. In previous years we've set up a
> small committee formed of PMC members (although there is no specific
> requirement to do so)  - I'm happy to work with the PMC to build a similar
> group for this year - would you like me to do that ?
>
> Kind regards
> Giles
>
>
>
>
> -Original Message-
> From: Ivet Petrova 
> Sent: 16 July 2021 11:26
> To: dev@cloudstack.apache.org
> Subject: CloudStack Collaboration Conference 2021 (9-12 November) - Call
> For Speakers
>
> Hello everyone,
>
> I am happy to announce that our community will organise the CloudStack
> Collaboration Conference as a Virtual Event.
> The event will happen from 9th of November to 12th of November 2021.
> We will work to update the website and do an online registration, which
> will be announced in the next several weeks.
>
> Meanwhile, I would like to announce a Call for Speakers. Bellow you can
> find a form, where you can submit your talk. The agenda is vital for our
> event success. At this event we target to collect a wider audience of
> people, who are users, but also companies, which consider what cloud
> orchestration to use currently.
> https://forms.gle/YGaQkcpF4yzkSSQ99
>
> Any volunteers to join the selection process of the talks?
>
>
> Kind regards,
>
>
>
>
>

Re: [DISCUSS] Terraform CloudStack provider

[Will Stevens]

Thanks for following up on this Rohit.

On Thu., Apr. 15, 2021, 4:53 a.m. Rohit Yadav, 
wrote:

> Hi All,
>
> Update - Peter and I had a call with Chris from Hashicorp to discuss the
> issue. They've agreed to relicense their terraform provider codebase to
> Apache License v2.0, following which we should be able to continue any
> further development, maintenance, and releases by the Apache CloudStack
> project much like the kubernetes provider codebase.
>
> I'll start a vote thread on the same shortly.
>
>
> Regards.
>
> 
> From: Rohit Yadav 
> Sent: Tuesday, March 30, 2021 14:52
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org 
> Subject: Re: [DISCUSS] Terraform CloudStack provider
>
> Hi Peter,
>
> I had explored the migration of repo, but before we do that we need to get
> the original authors to relicense the codebase to Apache License v2.0. I'll
> discuss this with Hashicorp authors and report back soon.
>
>
> Regards.
>
> 
> From: peter.murysh...@zv.fraunhofer.de 
> Sent: Monday, March 29, 2021 21:04
> To: dev@cloudstack.apache.org ;
> us...@cloudstack.apache.org 
> Subject: AW: [DISCUSS] Terraform CloudStack provider
>
> Hi all,
>
> are there any updates regarding this topic i.e. migration of HashiCorp
> Terraform provider to Apache CloudStack, either registering it in
> HashiCorp's registry?
>
> kind regards
> Peter
> 
> Von: Rohit Yadav 
> Gesendet: Freitag, 29. Januar 2021 17:14:05
> An: Will Stevens; dev@cloudstack.apache.org
> Cc: users; Niclas Lindblom; Pierre-Luc Dion
> Betreff: Re: [DISCUSS] Terraform CloudStack provider
>
> Hi Wido, Will, PL, all,
>
> I think I can setup a repository and request ASF infra (who prefers a JIRA
> ticket) to enable PR/issue on it, anybody has an objection to a new
> apache/cloudstack-terraform repo to maintain the provider plugin?
>
>
> Regards.
>
> 
> From: Will Stevens 
> Sent: Friday, January 29, 2021 19:49
> To: dev@cloudstack.apache.org 
> Cc: users ; Rohit Yadav <
> rohit.ya...@shapeblue.com>; Niclas Lindblom ;
> Pierre-Luc Dion 
> Subject: Re: [DISCUSS] Terraform CloudStack provider
>
> Hey PLD,
> You may want to tune into this. I think you may be maintaining a fork
> based on this code, but I am not positive.
>
> On Fri., Jan. 29, 2021, 6:07 a.m. Wido den Hollander,  <mailto:w...@widodh.nl>> wrote:
>
>
> On 28/01/2021 10:55, Rohit Yadav wrote:
> > Agree we can ask that.
> >
>
> Is infra from ASF the place to ask this?
>
> Wido
>
> >
> > Regards.
> >
> > 
> > From: Wido den Hollander mailto:w...@widodh.nl>>
> > Sent: Wednesday, January 27, 2021 15:35
> > To: Niclas Lindblom  niclas_lindb...@icloud.com>>; us...@cloudstack.apache.org us...@cloudstack.apache.org>  us...@cloudstack.apache.org>>
> > Cc: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org> <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> > Subject: Re: [DISCUSS] Terraform CloudStack provider
> >
> >
> >
> > On 1/27/21 12:18 AM, Niclas Lindblom wrote:
> >> I can confirm that the Terraform plugin is working if it is already
> installed, since it was archived it no longer automatically downloads when
> applying unless manually installed.
> >>
> >>  From the Hashicorp website, it appears it was archived when they moved
> all plugins to their registry and needs an owner and an email to Hashicorp
> to be moved into to the registry and supported again when running
> Terraform. I use it regularly but haven’t got the technical skills to
> maintain the code so been hoping this would be resolved.
> >>
> >
> > I mailed Hashicorp to ask about this:
> >
> > "Thanks for reaching out. The provider was archived because we launched
> > the Terraform Registry last year which allows vendors to host and
> > publish their own providers. We'd be happy to work with you to transfer
> > the repository over to a CloudStack Github organization where you can
> > build and publish releases to the registry.
> >
> > We'd also like to have CloudStack join our Technology partnership
> > program so I can mark your Terraform provider as verified."
> >
> > So I think we don't need to do much technology-wise.
> >
> > I don't use Terraform and don't have a major stake in it, but I would
> > hate to see the Provider being removed from Terraform.
> >
> > Should we request ht

Re: Cloudstack developer training

[Will Stevens]

Nice work team. This is an awesome contribution to the community.

Will

On Fri., Feb. 26, 2021, 10:43 a.m. Giles Sirett, 
wrote:

> Hi all
>
> One of the biggest challenges with Cloudstack is learning its architecture
> and codebase  - its big and its complicated. Onboarding new software
> engineers can be a daunting process.
> For the last 2 years, we at ShapeBlue have built up a set of resources to
> help us with onboarding on new engineers who will be working on Cloudstack.
>
> This has evolved into a self-study course that we call "hackerbook"- the
> logic being that it's a training course that gets engineers hands-on
> hacking in the code ASAP.  It's a mix of videos, exercises and other
> resources.
>
> Today, we've opensourced this resource in order to make it available to
> anybody who may want to learn to develop on Cloudstack.
>
> Feedback and improvement PRs will be warmly accepted
>
> Its currently sitting in a shapeblue repo, happy to move under ASF if
> anybody thinks that's important
>
> https://github.com/shapeblue/hackerbook
>
> Happy Hacking
>
> Kind regards
> Giles
>
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] Terraform CloudStack provider

[Will Stevens]

I have no objection to that.

On Fri., Jan. 29, 2021, 11:14 a.m. Rohit Yadav, 
wrote:

> Hi Wido, Will, PL, all,
>
> I think I can setup a repository and request ASF infra (who prefers a JIRA
> ticket) to enable PR/issue on it, anybody has an objection to a new
> apache/cloudstack-terraform repo to maintain the provider plugin?
>
>
> Regards.
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
> --
> *From:* Will Stevens 
> *Sent:* Friday, January 29, 2021 19:49
> *To:* dev@cloudstack.apache.org 
> *Cc:* users ; Rohit Yadav <
> rohit.ya...@shapeblue.com>; Niclas Lindblom ;
> Pierre-Luc Dion 
> *Subject:* Re: [DISCUSS] Terraform CloudStack provider
>
> Hey PLD,
> You may want to tune into this. I think you may be maintaining a fork
> based on this code, but I am not positive.
>
> On Fri., Jan. 29, 2021, 6:07 a.m. Wido den Hollander, 
> wrote:
>
>
>
> On 28/01/2021 10:55, Rohit Yadav wrote:
> > Agree we can ask that.
> >
>
> Is infra from ASF the place to ask this?
>
> Wido
>
> >
> > Regards.
> >
> > 
> > From: Wido den Hollander 
> > Sent: Wednesday, January 27, 2021 15:35
> > To: Niclas Lindblom ;
> us...@cloudstack.apache.org 
> > Cc: dev@cloudstack.apache.org 
> > Subject: Re: [DISCUSS] Terraform CloudStack provider
> >
> >
> >
> > On 1/27/21 12:18 AM, Niclas Lindblom wrote:
> >> I can confirm that the Terraform plugin is working if it is already
> installed, since it was archived it no longer automatically downloads when
> applying unless manually installed.
> >>
> >>  From the Hashicorp website, it appears it was archived when they moved
> all plugins to their registry and needs an owner and an email to Hashicorp
> to be moved into to the registry and supported again when running
> Terraform. I use it regularly but haven’t got the technical skills to
> maintain the code so been hoping this would be resolved.
> >>
> >
> > I mailed Hashicorp to ask about this:
> >
> > "Thanks for reaching out. The provider was archived because we launched
> > the Terraform Registry last year which allows vendors to host and
> > publish their own providers. We'd be happy to work with you to transfer
> > the repository over to a CloudStack Github organization where you can
> > build and publish releases to the registry.
> >
> > We'd also like to have CloudStack join our Technology partnership
> > program so I can mark your Terraform provider as verified."
> >
> > So I think we don't need to do much technology-wise.
> >
> > I don't use Terraform and don't have a major stake in it, but I would
> > hate to see the Provider being removed from Terraform.
> >
> > Should we request https://github.com/apache/cloudstack-terraform at
> > infra and then host the Provider there?
> >
> > Wido
> >
> >> Niclas
> >>
> >>
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >> On 26 Jan 2021, at 18:33, christian.nieph...@zv.fraunhofer.de wrote:
> >>>
> >>>
> >>>
> >>>> On 26. Jan 2021, at 10:45, Wido den Hollander  wrote:
> >>>>
> >>>>
> >>>>
> >>>> On 1/26/21 10:40 AM, christian.nieph...@zv.fraunhofer.de wrote:
> >>>>> On 25. Jan 2021, at 12:40, Abhishek Kumar <
> abhishek.ku...@shapeblue.com> wrote:
> >>>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> Terraform CoudStack provider by Hashicorp is archived here
> https://github.com/hashicorp/terraform-provider-cloudstack
> >>>>>>
> >>>>>> Is anyone using or maintaining it?
> >>>>>
> >>>>> We are also using it heavily and are somewhat worried about the
> module being archived.
> >>>>
> >>>> Agreed. But do we know why this has been done? What needs to be done
> to
> >>>> un-archive it?
> >>>>
> >>>> If it's just a matter of some love and attention we can maybe arrange
> >>>> something.
> >>>>
> >>>> Is it technically broken or just abandoned?
> >>>
> >>> This is just an educated guess, but given that we're not experiencing
> any technical issues, I believe it has just been abandoned.
>

Re: [DISCUSS] Terraform CloudStack provider

[Will Stevens]

Hey PLD,
You may want to tune into this. I think you may be maintaining a fork based
on this code, but I am not positive.

On Fri., Jan. 29, 2021, 6:07 a.m. Wido den Hollander, 
wrote:

>
>
> On 28/01/2021 10:55, Rohit Yadav wrote:
> > Agree we can ask that.
> >
>
> Is infra from ASF the place to ask this?
>
> Wido
>
> >
> > Regards.
> >
> > 
> > From: Wido den Hollander 
> > Sent: Wednesday, January 27, 2021 15:35
> > To: Niclas Lindblom ;
> us...@cloudstack.apache.org 
> > Cc: dev@cloudstack.apache.org 
> > Subject: Re: [DISCUSS] Terraform CloudStack provider
> >
> >
> >
> > On 1/27/21 12:18 AM, Niclas Lindblom wrote:
> >> I can confirm that the Terraform plugin is working if it is already
> installed, since it was archived it no longer automatically downloads when
> applying unless manually installed.
> >>
> >>  From the Hashicorp website, it appears it was archived when they moved
> all plugins to their registry and needs an owner and an email to Hashicorp
> to be moved into to the registry and supported again when running
> Terraform. I use it regularly but haven’t got the technical skills to
> maintain the code so been hoping this would be resolved.
> >>
> >
> > I mailed Hashicorp to ask about this:
> >
> > "Thanks for reaching out. The provider was archived because we launched
> > the Terraform Registry last year which allows vendors to host and
> > publish their own providers. We'd be happy to work with you to transfer
> > the repository over to a CloudStack Github organization where you can
> > build and publish releases to the registry.
> >
> > We'd also like to have CloudStack join our Technology partnership
> > program so I can mark your Terraform provider as verified."
> >
> > So I think we don't need to do much technology-wise.
> >
> > I don't use Terraform and don't have a major stake in it, but I would
> > hate to see the Provider being removed from Terraform.
> >
> > Should we request https://github.com/apache/cloudstack-terraform at
> > infra and then host the Provider there?
> >
> > Wido
> >
> >> Niclas
> >>
> >>
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> > @shapeblue
> >
> >
> >
> >> On 26 Jan 2021, at 18:33, christian.nieph...@zv.fraunhofer.de wrote:
> >>>
> >>>
> >>>
>  On 26. Jan 2021, at 10:45, Wido den Hollander  wrote:
> 
> 
> 
>  On 1/26/21 10:40 AM, christian.nieph...@zv.fraunhofer.de wrote:
> > On 25. Jan 2021, at 12:40, Abhishek Kumar <
> abhishek.ku...@shapeblue.com> wrote:
> >>
> >> Hi all,
> >>
> >> Terraform CoudStack provider by Hashicorp is archived here
> https://github.com/hashicorp/terraform-provider-cloudstack
> >>
> >> Is anyone using or maintaining it?
> >
> > We are also using it heavily and are somewhat worried about the
> module being archived.
> 
>  Agreed. But do we know why this has been done? What needs to be done
> to
>  un-archive it?
> 
>  If it's just a matter of some love and attention we can maybe arrange
>  something.
> 
>  Is it technically broken or just abandoned?
> >>>
> >>> This is just an educated guess, but given that we're not experiencing
> any technical issues, I believe it has just been abandoned.
> >>>
> >>> Christian
> >>>
> >>>
> 
>  Wido
> 
> >
> >> We're aware of Ansible CloudStack module (
> https://docs.ansible.com/ansible/latest/scenario_guides/guide_cloudstack.html)
> but are there any other alternatives of Terraform that you may be using
> with CloudStack?
> >
> > The ansible module is working quite well. However, one of the
> advantage of terraform imho is that one can easily destroy defined
> infrastructure with one command, while with ansible 'the destrcution' needs
> to be implemented in the playbook. Another advantage is that (at least)
> Gitlab can now maintain terraform states, which quite nicely supports
> GitOps approaches.
> >
> > Cheers, Christian
> >
> >>
> >> Regards,
> >> Abhishek
> >>
> >> abhishek.ku...@shapeblue.com
> >> www.shapeblue.com
> >> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> >> @shapeblue
> >>
> >>
> >>
> >
> >>>
> >>
> >
>

Re: Billing cloudstack

[Will Stevens]

Hey Lucian,
We built CloudMC for this (and other reasons).  It supports billing in a
multi-level multi-tenant environment, such as resellers.  It handles the
consumption, pricing and metering, but doesn't hook into an invoicing
system (currently) as we have found that every customer has a
unique invoicing system.  CloudMC is in production, delivering cloud
products for a few different telcos, some of which are based on CloudStack.

If you would like more information, I can help set that up, but here is a
link for now: https://www.cloudmc.cloudops.com/

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Mon, Aug 17, 2020 at 11:34 AM  wrote:

> Hi,
>
> For the folks running and billing their own Cloudstacks, what do you
> use? Looking for a nice self-service solution (billing perspective).
> We run Ubersmith for other things, but it's not great with Cloudstack.
> I noticed HostBill has a module for it. Any opinions on this?
>
> Other ideas welcome, thanks!
>
> Lucian
>

Re: [VOTE] Primate as modern UI for CloudStack

[Will Stevens]

+1 (binding)

On Mon, Oct 7, 2019, 7:31 AM Rohit Yadav  wrote:

> All,
>
> The feedback and response has been positive on the proposal to use Primate
> as the modern UI for CloudStack [1] [2]. Thank you all.
>
> I'm starting this vote (to):
>
>   *   Accept Primate codebase [3] as a project under Apache CloudStack
> project
>   *   Create and host a new repository (cloudstack-primate) and follow
> Github based development workflow (issues, pull requests etc) as we do with
> CloudStack
>   *   Given this is a new project, to encourage cadence until its feature
> completeness the merge criteria is proposed as:
>  *   Manual testing against each PR and/or with screenshots from the
> author or testing contributor, integration with Travis is possible once we
> get JS/UI tests
>  *   At least 1 LGTM from any of the active contributors, we'll move
> this to 2 LGTMs when the codebase reaches feature parity wrt the
> existing/old CloudStack UI
>  *   Squash and merge PRs
>   *   Accept the proposed timeline [1][2] (subject to achievement of goals
> wrt Primate technical release and GA)
>  *   the first technical preview targetted with the winter 2019 LTS
> release (~Q1 2020) and release to serve a deprecation notice wrt the older
> UI
>  *   define a release approach before winter LTS
>  *   stop taking feature FRs for old/existing UI after winter 2019 LTS
> release, work on upgrade path/documentation from old UI to Primate
>  *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019),
> but still ship old UI with a final deprecation notice
>  *   old UI codebase removed from codebase in winter 2020 LTS release
>
> The vote will be up for the next two weeks to give enough time for PMC and
> the community to gather consensus and still have room for questions,
> feedback and discussions. The results to be shared on/after 21th October
> 2019.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> [1] Primate Proposal:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>
> [2] Email thread reference:
> https://markmail.org/message/z6fuvw4regig7aqb
>
> [3] Primate repo current location: https://github.com/shapeblue/primate
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] Short "marketing" video project

[Will Stevens]

I am +1 to an ACS youtube channel.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Fri, Oct 4, 2019 at 9:46 AM Giles Sirett 
wrote:

> I love the video Andrija
>
> Very good point Julia - we also have a whole of catalogue community video
> content hosted in the Shapeblue channel - simply because there was nowhere
> else to put it
> For CCC the last  2 years,  we've worked with Rich Bowen to get conference
> talks into the Apache channel, but that’s only really fits  because CCC has
> been part of Apachecon (i.e. it wouldn’t work for "how to" videos) ,etc
>
> If we have people who are creating video content for the project such as
> this , it would probably make sense to create an ACS youtube channel.
>
> Any objections ?
>
> From a practicality side, access to this would need to work in a similar
> way to the ACS twitter account: the account owner is a PMC email address,
> allowing password resets from the PMC as a group. The actual login
> credentials  then held by a small subset of people who actually publish.
>
> This is a bigger decsison than Andrijas one specific  video IMO and should
> have its own discuss thread , but keen to see initial thoughts here first
>
>
>
>
>
> Kind regards
> Giles
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Andrija Panic 
> Sent: 03 October 2019 18:58
> To: Apache CloudStack Marketing 
> Cc: users ; dev 
> Subject: Re: [DISCUSS] Short "marketing" video project
>
> I believe I saw that video - very nice work Julia.
>
> I believe, by (very) lazy consensus (a.k.a. if no objections), that I will
> add that video to the main web site.
>
> Cheers
> Andrija
>
>
> On Thu, 3 Oct 2019 at 14:56, Julia Simon  wrote:
>
> > Hi,
> >
> > We ran in to this issue a few years ago when we hosted the CloudStack
> > Collab. Videos from that are on our (CloudOps) youtube channel, since
> > there wasn't another place to publish them.
> > Julia
> >
> > On Tue, Oct 1, 2019 at 10:21 AM Andrija Panic
> > 
> > wrote:
> >
> >> Hi guys,
> >>
> >> this is a little project I've been experimenting last 2 weeks and is
> >> **temporarily** located on the ShapeBlue channel.
> >>
> >> https://youtu.be/k3uD69fajCU
> >>
> >> Do you have any ideas where we can publish this, in more "official",
> >> CloudStack way?
> >>
> >> I was thinking about putting this on the main website
> >> http://cloudstack.apache.org
> >>
> >> Comments, objections, ideas?
> >>
> >> Best,
> >> Andrija
> >>
> >>
> >
> > --
> >
> > *Julia Simon*Responsable principale du marketing *| *Senior Marketing
> > Manager t 514.447.3456 ext. 1103 c 514.993.6661
> >
> > <https://goo.gl/NYZ8KK>
> >
> >
> >
>
>
> --
>
> Andrija Panić
>

Re: [DISCUSS] CloudStack Kubernetes Service plugin

[Will Stevens]

We see huge demand for K8s in our customer base. Just a note...

On Wed, Sep 25, 2019, 4:03 AM Nux!  wrote:

> Do you guys see high demand for K8s?
>  From where I'm looking it seems to be going the way of Openstack, loads
> of hype, overcomplicated, near-impossible to upgrade.
> Not sure if it's worth investing resources for this.
>
> Lucian
>
> ---
> Sent from the Delta quadrant using Borg technology!
>
> On 2019-09-24 07:41, Abhishek Kumar wrote:
> > Hi all,
> >
> > I would like to propose developing a plugin for Kubernetes integration
> > in CloudStack, can be named CloudStack Kubernetes Service plugin.
> > I've written down an initial design document for it here,
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service
> > Please review and provide your thoughts and suggestions.
> >
> > Regards,
> >
> >
> > Abhishek Kumar
> >
> > Software Engineer
> >
> > ShapeBlue
> >
> > abhishek.ku...@shapeblue.com
> >
> > www.shapeblue.com
> >
> > abhishek.ku...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
>

Re: CloudStack Kubernetes Provider

[Will Stevens]

I am fine with it...

On Sun, Jul 21, 2019, 11:04 AM Rohit Yadav 
wrote:

> Hi Gregor,
>
>
> The repository is up now to receive contributions:
>
> https://github.com/apache/cloudstack-kubernetes-provider
>
>
> PMCs - ping, any thoughts on contributions? Can Gregor or any interested
> parties simply send a pull request based on the old provider codebase that
> is under Apache License v2.0 (
> https://github.com/kubernetes/kubernetes/tree/release-1.15/pkg/cloudprovider/providers/cloudstack
> )?
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Riepl, Gregor (SWISS TXT) 
> Sent: Thursday, July 11, 2019 3:15:12 PM
> To: priv...@cloudstack.apache.org ;
> dev@cloudstack.apache.org 
> Cc: us...@cloudstack.apache.org 
> Subject: Re: CloudStack Kubernetes Provider
>
> Hi Rohit,
>
> > One of the community contributors from SwissTxt Gregor Riepl
> > (@onitake) have also offered to contribute their provider (which is
> > already under the Apache v2.0 license) which they have based on the
> > original provider:
> >
> https://github.com/kubernetes/enhancements/issues/672#issuecomment-510353660
>
> This CCM is actually based on the old code in
> >
>
> https://github.com/kubernetes/kubernetes/tree/release-1.15/pkg/cloudprovider/providers/cloudstack
>
> We removed some stuff that is not relevant for a standalone controller
> and added a few patches that were not accepted upstream due to the
> deprecation.
>
> There's still some open issues, if you look at the tracker at
> https://github.com/swisstxt/cloudstack-cloud-controller-manager/issues
>
> Issue #9 in particular needs fixing, or the controller will be a bit
> difficult to deploy in a generic k8s environment.
>
> > PMCs - If Gregor wants to donate their changes based on the
> > old/original provider to CloudStack, is there a formal donation
> > process that he/swisstxt needs to be used or a simple pull request
> > can be sent?
>
> We're open to any suggestions.
> You can also simply fork the Github repo and start from there. ☺
>
> Regards,
> Gregor
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

Re: Using S3/Minio as the only secondary storage

[Will Stevens]

If Syed can't fill in the blanks sufficiently for you when you talk to him
later today, let me know and I will set up a call and loop in the team on
our side who have more details and we can walk through our experience and
knowledge on the topic.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Wed, Jul 17, 2019 at 9:30 AM Jean-Francois Nadeau 
wrote:

> Thanks Will,
>
> I remember having the discussion with Pierre-Luc on his use of Swift for
> templates.  I was curious about the differences on S3 vs Swift for SS since
> looking at the CS UI when it comes to setting up an S3 image store... the
> NFS staging is optional.  And this make sense to me if your object storage
> is fast and accessible locally,  why the need for staging/caching.The
> documentation could mention if it is possible to use S3 secondary and
> nothing else,  starting with if SSVM templates can be uploaded to a
> bucket.I will certainly ask Syed later today :)
>
> best
>
> Jfn
>
> On Wed, Jul 17, 2019 at 6:59 AM Will Stevens 
> wrote:
>
> > Hey JF,
> > We use the Swift object store as the storage backend for secondary
> > storage.  I have not tried the S3 integration, but the last time I looked
> > at the code for this (admittedly, a long time ago) the Swift and s3 logic
> > was more intertwined than I liked. The CloudOps/cloud.ca team had to do
> a
> > lot of work to get the Swift integration to a reasonable working state. I
> > believe all of our changes have been upstreamed quite some time ago. I
> > don't know if anyone is doing this for the S3 implementation.
> >
> > I can't speak to the S3 implementation because I have not looked at it
> in a
> > very long time, but the Swift implementation requires a "temporary NFS
> > staging area" that essentially acts kind of like a buffer between the
> > object store and primary storage when templates and such are used by the
> > hosts.
> >
> > I think Pierre-Luc and Syed have a clearer picture of all the moving
> > pieces, but that is a quick summary of what I know without digging in.
> >
> > Hope that helps.
> >
> > Cheers,
> >
> > Will
> >
> > On Tue, Jul 16, 2019, 10:24 PM Jean-Francois Nadeau <
> > the.jfnad...@gmail.com>
> > wrote:
> >
> > > Hello Everyone,
> > >
> > > I was wondering if it was common or even recommended to use an S3
> > > compatible storage system as the only secondary storage provider ?
> > >
> > > The environment is 4.11.3.0 with KVM (Centos 7.6),  and our tier1
> storage
> > > solution also provides an S3 compatible object store (apparently Minio
> > > under the hood).
> > >
> > > I have always used NFS to install the SSVM templates and the install
> > script
> > > (cloud-install-sys-tmplt) only takes a mount point.  How, if possible,
> > > would I proceed with S3 only storage ?
> > >
> > > best,
> > >
> > > Jean-Francois
> > >
> >
>

Re: Using S3/Minio as the only secondary storage

[Will Stevens]

Hey JF,
We use the Swift object store as the storage backend for secondary
storage.  I have not tried the S3 integration, but the last time I looked
at the code for this (admittedly, a long time ago) the Swift and s3 logic
was more intertwined than I liked. The CloudOps/cloud.ca team had to do a
lot of work to get the Swift integration to a reasonable working state. I
believe all of our changes have been upstreamed quite some time ago. I
don't know if anyone is doing this for the S3 implementation.

I can't speak to the S3 implementation because I have not looked at it in a
very long time, but the Swift implementation requires a "temporary NFS
staging area" that essentially acts kind of like a buffer between the
object store and primary storage when templates and such are used by the
hosts.

I think Pierre-Luc and Syed have a clearer picture of all the moving
pieces, but that is a quick summary of what I know without digging in.

Hope that helps.

Cheers,

Will

On Tue, Jul 16, 2019, 10:24 PM Jean-Francois Nadeau 
wrote:

> Hello Everyone,
>
> I was wondering if it was common or even recommended to use an S3
> compatible storage system as the only secondary storage provider ?
>
> The environment is 4.11.3.0 with KVM (Centos 7.6),  and our tier1 storage
> solution also provides an S3 compatible object store (apparently Minio
> under the hood).
>
> I have always used NFS to install the SSVM templates and the install script
> (cloud-install-sys-tmplt) only takes a mount point.  How, if possible,
> would I proceed with S3 only storage ?
>
> best,
>
> Jean-Francois
>

Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0

[Will Stevens]

+1 for keeping 4.11.3.0 and rereleasing...

On Mon, Jun 24, 2019, 10:38 AM Gabriel Beims Bräscher 
wrote:

> +1 on keeping the release name as 4.11.3.0.
>
> Em seg, 24 de jun de 2019 às 11:27, Wei ZHOU 
> escreveu:
>
> > I vote for 4.11.3.0
> >
> > -Wei
> >
> >
> >
> > Paul Angus  于2019年6月24日周一 下午3:43写道：
> >
> > > Hi,
> > >
> > > Does anyone have any strong views on whether we should look to nullify
> > > 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
> > >
> > > Many thanks
> > >
> > >
> > > Paul Angus
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > paul.an...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> > > -Original Message-
> > > From: Rohit Yadav 
> > > Sent: 24 June 2019 12:13
> > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > > Thanks for sharing Gregor. My/our bad, I was suspicious of how the
> > > templates were setup based on your emails and did not think what you
> > shared
> > > could be something to do with the DB upgrade path bug.
> > >
> > >
> > > Regards,
> > >
> > > Rohit Yadav
> > >
> > > Software Architect, ShapeBlue
> > >
> > > https://www.shapeblue.com
> > >
> > > 
> > > From: Riepl, Gregor (SWISS TXT) 
> > > Sent: Monday, June 24, 2019 3:23:23 PM
> > > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > >
> > > > https://github.com/apache/cloudstack/pull/3417
> > > >
> > > >
> > > > The issue only affects 4.11.2.0 users for which the upgrade path does
> > > > not run (a noop upgrade path runs) and it does not automatically fix
> > > > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> > > > mentioned workaround steps on the PR.
> > >
> > > This sounds pretty much exactly like the issue we had...
> > >
> > >
> > >
> >
> https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> > >
> > >
> > >
> >
>

Re: CCC NA19 - talk selection

[Will Stevens]

I can help with this. I will be getting the CCC website up later this week
as well.

Cheers,

Will

On Mon, May 20, 2019, 5:45 AM Giles Sirett 
wrote:

> Hi all
> The CFP for Cloudstack Collab  (http://us.cloudstackcollab.org/) has now
> closed.
> We've had a good number of submissions which now need to be sifted and
> selected
>
> In previous years, we've done this by getting a small  "selection
> committee" together. My suggestion is that we do the same this year
>
> So, we need some volunteers
>
> Please, can anybody who like to help with this step forward now!
>
> We have to get the agenda together by 3 June, so time is tight
>
>
> Kind regards
> Giles
>
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

Re: CloudStack and SDN

[Will Stevens]

Regarding the existing OpenContrail code that is in CloudStack.  It is
currently not functional.  That said, Juniper is in the process of
transferring OpenContrail to the Linux Foundation Networking under the new
brand of Tungsten Fabric (TF).

We (CloudOps) have been supporting this transition at both the governance
and technical levels, and are actively supporting the reboot of that
project.

It would be interesting to review what the best integration architecture
would look like and scope the integration details.  The TF community has
been focusing quite a bit on the cloud-native (container) deployment
scenarios, but there are a number of architectures which are possible.  One
of the interesting things about the TF project is their ability to connect
together legacy networks with newer network overlays (such as cloud-native
networking).  If others are interested in integrating TF into CloudStack
again, I would be willing to support that initiative in the ways I can.

At the recent Open Networking Summit (ONS), I demoed the ability to expand
a service mesh between two different Kubernetes cloud regions with the
ability to do policy management across the hybrid cloud deployment.  I used
Tungsten Fabric and Consul Connect for the overlay networking, and I used
CloudStack (with S2S VPN to connect the regions) as the networking underlay
for the demo.

Demo Recording:
https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/ons-demo/tf_consul_ons_demo.mp4

If others are interested in getting involved in the TF project and how we
could re-implement an integration between ACS and TF, I would be willing to
support that effort.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Thu, Apr 18, 2019 at 1:42 PM Simon Weller 
wrote:

> Juniper contributed a plugin for Contrail quite a number of years ago.
> With that project now under the umbrella of the Linux Foundation (along
> with Open Daylight), it would be nice to see some of us start to explore
> the open options and see if we could move some better integrations forward.
> With Nokia pulling the Nuage plugin, there are no full SDN options
> available any longer and I think that's unfortunate for the project at
> large.
>
> -Si
>
> 
> From: Sergey Levitskiy 
> Sent: Wednesday, April 17, 2019 3:40 PM
> To: dev@cloudstack.apache.org
> Cc: users
> Subject: Re: CloudStack and SDN
>
> Nicira NVP/NSX is very outdated and doesn’t support latest NSX.
>
> On 4/17/19, 1:22 AM, "Andrija Panic"  wrote:
>
> Simplest one that actually works (call it SDN if you like) - VXLAN.
>
> A few others with various implementation states and all hypervisor
> dependent:
> Nicira NVP / Vmware NSX
> Midonet
> Various tunneling protocols
>
>
> On Wed, 17 Apr 2019 at 09:46, Haijiao <18602198...@163.com> wrote:
>
> >
> >
> > Noted Nuage's decision on ceasing SDN plugin for CloudStack. Just
> > wondering is there any other SDN solutoin can be integrated with
> CloudStack
> > ?
> >
> >
> > Thanks !
> >
> >
> > Regards,
> >
> >
>
> --
>
> Andrija Panić
>
>
>

Re: Any plan for 4.11 LTS extension ?

[Will Stevens]

Yes. This seems right to me.

The LTS release was introduced for exactly the purpose of giving
organizations with production deployments a predictable and stable path for
upgrades. There has to be a reasonably sized window for adoption of the new
LTS release before the previous one can be abandoned.

I think what Rene posted is a good guide. If we have other documentation
which specifies specific dates (which may be outdated), we may want to go
through and update to inspire more confidence in the LTS versions and the
expected upgrade path/window.

Cheers,

Will


On Sat, Mar 16, 2019, 11:37 AM Rene Moser  wrote:

>
>
> On 3/14/19 10:48 AM, Giles Sirett wrote:
> > Hi Haijiao
> >
> > I would *expect*  4.13.0 (LTS) to be released in Q2, which  will
> supersede the 4.11 branch as the current LTS branch
>
> btw...
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS:
>
> "LTS releases starting with the first major release will be supported
> for a minimum of 6 months after next LTS release or a total period of 24
> months, whichever is greater"
>
> --> next LTS Q2 2019 + 6 months = 4.11 LTS ends Q4 2019
>
> Just my 2 cents
>
> René
>

Re: CloudStack Collab Conference Brazil

[Will Stevens]

Let me know if there is any update to the wording on
http://br.cloudstackcollab.org/#schedule that you would like me to update.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Thu, Feb 7, 2019 at 1:41 PM Marco Sinhoreli <
marco.sinhor...@shapeblue.com> wrote:

> Hello Rafael,
>
> Nice to hear that the CCC will land in Brazil – thank you for getting this
> going.
>
> As you know, I’m based in Brazil and offer to help you as much as required.
>
> I know a lot of cloudstack users here so can help to get people to submit
> talks and getting them along to the conference.
>
> Cheers,
>
> Marco Sinhoreli
> marco.sinhor...@shapeblue.com
> mobile: +55 21 98276 3636
>
> Av. Brigadeiro Faria Lima, 3144 - 2º andar – Jardim
> Paulistano, São Paulo, SP, Brasil, 01451-000
> Phone: + 55 11 3568-2877
> http://www.shapeblue.com/ | twitter: @shapeblue
>
> Em 07/02/2019 14:08, "Rafael Weingärtner" 
> escreveu:
>
> Instructions to submit a talk proposal (regarding the track name)?
> It was fixed already. Now, when someone goes there, there is the
> "CloudStack Collab" option.
>
> On Thu, Feb 7, 2019 at 2:05 PM Will Stevens 
> wrote:
>
> > If you can provide the instructions, I will update the CCC site.
> Otherwise,
> > Rafael you could create a PR which I can merge and deploy to the CCC
> site.
> >
> > Thanks Giles...
> >
> > Cheers,
> >
> > Will
> >
> > On Thu, Feb 7, 2019, 10:26 AM Rafael Weingärtner <
> > rafaelweingart...@gmail.com wrote:
> >
> > > Hey Giles, I will try to answer you inline.
> > >
> > > Some questions from me:
> > > >
> > > 1. how many speaker slots did you agree for the CCC part of the
> event
> > (i.e.
> > > > how many talks are required)?
> > > >
> > > As we discussed in the PMC, we ended up with a one day track
> focused on
> > > CloudStack. This translates to 7 (50min.) talks. By the number of
> people
> > I
> > > talked to, I would say that we will have way more talks than slots
> :((
> > >
> > > >
> > > > 2. You mention CFP closes 11 Febuary, and it seems from the
> website
> > that
> > > > speakers should submit their talks through
> > > > http://cfp-flp.thedevconf.com.br/
> > > >  However, there is no track listed as CCC. There is a "cloud
> computing"
> > > > track. Is that the one to use ?  It may make sense to tell
> people on
> > the
> > > > CCC site which track to use
> > > >
> > >
> > > It was in their backlog to fix. I just checked, and it is fixed
> now.
> > >
> > > On Thu, Feb 7, 2019 at 7:10 AM Giles Sirett <
> giles.sir...@shapeblue.com>
> > > wrote:
> > >
> > > > This is great to see Rafael  - well done to you and Mike for
> getting
> > this
> > > > rolling
> > > >
> > > > Some questions from me:
> > > > 1. how many speaker slots did you agree for the CCC part of the
> event
> > > > (i.e. how many talks are required)?
> > > > 2. You mention CFP closes 11 Febuary, and it seems from the
> website
> > that
> > > > speakers should submit their talks through
> > > > http://cfp-flp.thedevconf.com.br/
> > > >  However, there is no track listed as CCC. There is a "cloud
> computing"
> > > > track. Is that the one to use ?  It may make sense to tell
> people on
> > the
> > > > CCC site which track to use
>     > > >
> > > >
> > > > Kind regards
> > > > Giles
> > > >
> > > > giles.sir...@shapeblue.com
> > > > www.shapeblue.com
> > > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > > >
> > > > -Original Message-
> > > > From: Rafael Weingärtner 
> > > > Sent: 04 February 2019 20:37
> > > > To: dev 
> > > > Cc: users 
> > > > Subject: Re: CloudStack Collab Conference Brazil
> > > >
> > > > Ah Will, sorry for that. I m

Re: CloudStack Collab Conference Brazil

[Will Stevens]

If you can provide the instructions, I will update the CCC site. Otherwise,
Rafael you could create a PR which I can merge and deploy to the CCC site.

Thanks Giles...

Cheers,

Will

On Thu, Feb 7, 2019, 10:26 AM Rafael Weingärtner <
rafaelweingart...@gmail.com wrote:

> Hey Giles, I will try to answer you inline.
>
> Some questions from me:
> >
> 1. how many speaker slots did you agree for the CCC part of the event (i.e.
> > how many talks are required)?
> >
> As we discussed in the PMC, we ended up with a one day track focused on
> CloudStack. This translates to 7 (50min.) talks. By the number of people I
> talked to, I would say that we will have way more talks than slots :((
>
> >
> > 2. You mention CFP closes 11 Febuary, and it seems from the website that
> > speakers should submit their talks through
> > http://cfp-flp.thedevconf.com.br/
> >  However, there is no track listed as CCC. There is a "cloud computing"
> > track. Is that the one to use ?  It may make sense to tell people on the
> > CCC site which track to use
> >
>
> It was in their backlog to fix. I just checked, and it is fixed now.
>
> On Thu, Feb 7, 2019 at 7:10 AM Giles Sirett 
> wrote:
>
> > This is great to see Rafael  - well done to you and Mike for getting this
> > rolling
> >
> > Some questions from me:
> > 1. how many speaker slots did you agree for the CCC part of the event
> > (i.e. how many talks are required)?
> > 2. You mention CFP closes 11 Febuary, and it seems from the website that
> > speakers should submit their talks through
> > http://cfp-flp.thedevconf.com.br/
> >  However, there is no track listed as CCC. There is a "cloud computing"
> > track. Is that the one to use ?  It may make sense to tell people on the
> > CCC site which track to use
> >
> >
> > Kind regards
> > Giles
> >
> > giles.sir...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Rafael Weingärtner 
> > Sent: 04 February 2019 20:37
> > To: dev 
> > Cc: users 
> > Subject: Re: CloudStack Collab Conference Brazil
> >
> > Ah Will, sorry for that. I meant to reference the cloudstackcollab
> > website, but pressed the send button too fast ;)
> >
> > On Mon, Feb 4, 2019 at 6:31 PM Will Stevens 
> wrote:
> >
> > > We will try to keep the website, http://br.cloudstackcollab.org/, up
> > > to date with the details of the event as new information is available.
> > > I just figured I would mention that since Rafael didn't mention it in
> > his email.
> > > :)
> > >
> > > Cheers,
> > >
> > > *Will Stevens*
> > > Chief Technology Officer
> > > c 514.826.0190
> > >
> > > <https://goo.gl/NYZ8KK>
> > >
> > >
> > > On Mon, Feb 4, 2019 at 3:29 PM Rafael Weingärtner <
> > > rafaelweingart...@gmail.com> wrote:
> > >
> > > > The first CloudStack Collab Conference Brazil is going to be held in
> > > > Florianopolis, in April 2019. It is being run through The Developer
> > > > Conference (TDC) <http://www.thedevelopersconference.com.br/en> in
> > > Brazil.
> > > > When you register <http://br.cloudstackcollab.org/#register> you
> > > > will be redirected to the *TDC* website.
> > > >
> > > > TDC runs a series of conferences every year in Brazil
> > > > (Florianopolis, São Paulo, and  Porto Alegre). They have been running
> > for over a decade now.
> > > > TDC conferences cover a broad range of topics, from management 3.0,
> > > > software development, Programming languages (Java, Python, Ruby, and
> > > > so one), Cloud, and so on. Their average number of attendees is
> > > > about ~4000 per TDC event. Therefore, this event is a great
> > > > opportunity for enthusiasts, technicians, and vendors to show
> > > > themselves and meet with different IT communities.
> > > >
> > > > For people from our community, it is an opportunity not just to
> > > participate
> > > > in CloudStack Collab Brazil
> > > > <
> > > >
> > > http://www.thedevelopersconference.com.br/tdc/2019/florianopolis/trilh
> > > a-cloud-stack-colab
> > > > >,
> > > > but also to join this amazing conference in Brazil. The call for
> > > > paper

Re: CloudStack Collab Conference Brazil

[Will Stevens]

We will try to keep the website, http://br.cloudstackcollab.org/, up to
date with the details of the event as new information is available.  I just
figured I would mention that since Rafael didn't mention it in his email.
:)

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Mon, Feb 4, 2019 at 3:29 PM Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> The first CloudStack Collab Conference Brazil is going to be held in
> Florianopolis, in April 2019. It is being run through The Developer
> Conference (TDC) <http://www.thedevelopersconference.com.br/en> in Brazil.
> When you register <http://br.cloudstackcollab.org/#register> you will be
> redirected to the *TDC* website.
>
> TDC runs a series of conferences every year in Brazil (Florianopolis, São
> Paulo, and  Porto Alegre). They have been running for over a decade now.
> TDC conferences cover a broad range of topics, from management 3.0,
> software development, Programming languages (Java, Python, Ruby, and so
> one), Cloud, and so on. Their average number of attendees is about ~4000
> per TDC event. Therefore, this event is a great opportunity for
> enthusiasts, technicians, and vendors to show themselves and meet with
> different IT communities.
>
> For people from our community, it is an opportunity not just to participate
> in CloudStack Collab Brazil
> <
> http://www.thedevelopersconference.com.br/tdc/2019/florianopolis/trilha-cloud-stack-colab
> >,
> but also to join this amazing conference in Brazil. The call for papers
> (CFP)
> <
> http://www.thedevelopersconference.com.br/tdc/2019/florianopolis/call4papers-en
> >
> is open through 11 February 2019 (Hard deadline). People are also welcome
> to submit talks to other tracks.  Speakers will receive free registration
> for the entire conference. The cost per track is BRL 165 (~45 USD).
> Therefore, there is no single price for the conference; you only pay for
> what you need. This price is for the early birds, prices will rise up on 12
> February. After 12 February, the prices will rise to BRL 220, and later on
> 26 March, to BRL 290.
>
> The event where CloudStack Collab will take place is TDC Florianopolis,
> which will be held in Florianopolis between 23-27  of April 2019.
> Florianopolis is the capital of Brazil’s Santa Catarina state, which is
> often called “the best place to live in Brazil”. Florianopolis is a
> thriving destination for its perfect beaches, excellent surfing, amazing
> seafood, and juxtaposition of a modern megacity with 16th-century colonial
> fortresses and relaxed markets and parks. For more information please visit
> Florianopolis <http://turismo.sc.gov.br/en/destinos/grande-florianopolis/
> >.
> So, do not miss the opportunity to submit your talks, and to share with
> your friends. Let’s make the most of the first CloudStack Collab Brazil!
>
> One note to this event, depending on your nationality, a tourist visa may
> be required or exempted. The ultimate authority on whether you need a visa
> or not is the Brazilian Consulate in your country.
>
> If you guys have problems, doubts or suggestions, please feel free to mail
> me.
>

Re: SSL offload in the VR

[Will Stevens]

It may have been Syed who added that API in order to add support for ssl
offload on the netscaler years ago. I remember he had to add the ability to
manage ssl certificates in ACS, so it is possible it was part of that.  I
am guessing though.

On Wed, Nov 21, 2018, 3:27 AM Paul Angus  Thanks @Pierre-Luc Dion and @jaya...@apache.org,
>
> My 'problem' is that being able to add an SSL cert to a VR loadbalancer
> has appeared from nowhere in the 4.11 branch. (easiest explained with a
> screen snip):
>
> https://imgur.com/a/r7zxA0b
>
> ... which led me to finding the assignCertToLoadBalancer API.
>
> I can't find a specific PR for it, or anything in the cwiki, and nothing
> in our read-the-docs...
> So I'm trying to find the author, so we can back fit some documentation,
> rather than trying to reverse engineer it out of the code/trial and error.
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Jayapal Uradi 
> Sent: 21 November 2018 04:31
> To: dev@cloudstack.apache.org
> Subject: Re: SSL offload in the VR
>
> What I remember is ssl offload feature  added for netscaler  and
> assignCertToLoadBalancer API added during that time.
>
> -Jayapal
>
> > On 21-Nov-2018, at 5:06 AM, Pierre-Luc Dion  wrote:
> >
> > Hey Paul, I'm not aware the vr support ssl offload. What you are
> > trying to achieve, there might be a work around.
> >
> > Le mar. 20 nov. 2018 07 h 08, Paul Angus  a
> > écrit :
> >
> >> Apologies if my GitHub foo has abandoned me (it wouldn’t me the first
> >> time);
> >>
> >> I searched for files which contained the API command
> >> ‘assignCertToLoadBalancer’ and found ‘AssignCertToLoadBalancerCmd.java’
> >>
> >> According to the history it was first committed as part of PR #2283
> >> “CLOUDSTACK-10105: Use maven standard project structure in all
> >> projects” [1]
> >>
> >>
> >> https://github.com/apache/cloudstack/commits/1d05fead49f5c856257a741b
> >> 07122f5633d2e359/api/src/main/java/org/apache/cloudstack/api/command/
> >> user/loadbalancer/AssignCertToLoadBalancerCmd.java
> >>
> >> again, sorry if I’ve misread or misinterpreted the history…
> >>
> >> Kind regards,
> >>
> >> Paul Angus
> >>
> >> From: Marc-Aurèle Brothier 
> >> Sent: 20 November 2018 11:23
> >> To: Paul Angus 
> >> Cc: dev@cloudstack.apache.org
> >> Subject: Re: SSL offload in the VR
> >>
> >> Hi Paul,
> >>
> >> What made you think so? I haven’t pushed any change related to the
> >> VR. At Exoscale, we removed the VR entirely instead and moved the
> >> services down at the HV level.
> >>
> >> Kind regards,
> >> Marc-Aurèle
> >>
> >>
> >> paul.an...@shapeblue.com
> >> www.shapeblue.com
> >> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> >>
> >>
> >>
> >> On 20 Nov 2018, at 09:04, Paul Angus  >> paul.an...@shapeblue.com>> wrote:
> >> Hi Marc-Aurèle,
> >>
> >> As far as I can tell, I believe that you added the ability to upload
> >> an SSL certificate to the VR in 4.11 I can’t find any user
> >> documentation for it in our Wiki or the in read-the-docs.
> >> I guess it’s something that you use at Exoscale, could you do a pull
> >> request to cloudstack-documentation or forward me some documentation
> >> which I can then add to the users documentation.
> >>
> >>
> >> Kind regards,
> >>
> >> Paul Angus
> >>
> >>
> >> paul.an...@shapeblue.com
> >> www.shapeblue.com
> >> @shapeblue
> >>
> >>
> >>
> >>
>
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is
> the property of Accelerite, a Persistent Systems business. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Accelerite, a Persistent Systems business does not accept any
> liability for virus infected mails.
>

Re: Ansible 2.7: CloudStack related changes and future

[Will Stevens]

Sorry to see you go Rene.  You have been an amazing contributor to this
community and you will be missed.

I wish you the best in your new adventures.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Wed, Oct 10, 2018 at 9:33 AM Nux!  wrote:

> Thanks for all your efforts, Rene!
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Rene Moser" 
> > To: "users" , "dev" <
> dev@cloudstack.apache.org>
> > Sent: Monday, 8 October, 2018 12:43:17
> > Subject: Ansible 2.7: CloudStack related changes and future
>
> > Hi all
> >
> > First, please note I am leaving my current job by the end of November
> > and I don't see that CloudStack will play any role in my professional
> > future.
> >
> > As a result, I official announce the end of my maintenance for the
> > Ansible CloudStack modules with the release of Ansible v2.8.0 in spring
> > 2019.
> >
> > If anyone is interested to take over, please let me know so I can
> > officially introduce him/her to the Ansible community.
> >
> > Thanks for all the support and joy I have had with CloudStack and the
> > community!
> >
> > Ansible v2.7.0 is released with the following, CloudStack related
> changes:
> >
> > David Passante (1):
> >  cloudstack: new module cs_disk_offering (#41795)
> >
> > Rene Moser (4):
> >  cs_firewall: fix idempotence and tests for cloudstack v4.11 (#42458)
> >  cs_vpc: fix disabled or wrong vpc offering taken (#42465)
> >  cs_pod: workaround for 4.11 API break (#43944)
> >  cs_template: implement update and revamp (#37015)
> >
> > Yoan Blanc (1):
> >  cs instance root_disk size update resizes the root volume (#43817)
> >
> > nishiokay (2):
> >  [cloudstack] fix cs_host example (#42419)
> >  Update cs_storage_pool.py (#42454)
> >
> >
> > Best wishes
> > René
>

Re: [DISCUSS] deployment planner improvement

[Will Stevens]

If I remember correctly, we see similar issues on VMware.  Marcus, have you
seen similar behavior on VMware?  I think I remember us having to manually
vMotion a lot of VMs very often...

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Thu, Sep 6, 2018 at 2:34 PM Pierre-Luc Dion  wrote:

> Hi,
>
> I'm working with a University in Montreal and we are looking at working
> together to improve the deployment planner. Mainly for post VM.CREATE
> tasks.
> Because  what we observed with cloudstack, in our case with XenServer,
> overtime, a cluster will become unbalanced in therm of workload, vm HA will
> move VMs all over the the cluster which cause hotspot inside a cluster.
> Also, when performing maintenance  xenmotion of VM spread them in the
> cluster but does not consider host usage and at the end of a maintenance it
> require manual operation to repopulate VMs on the last host updated.  OS
> preference not taken into account  except for VM.CREATE.
>
> So,
> I'd like to work on improving VMs dispersion during and post outage and
> maintenances. when a cluster resources are added or removed.
>
> Would you have any more requirement, we will document a feature spec in the
> wiki which I believe it's still a requirement ?
>
> Does using KVM have similar issues over time?
>
> I don't think it would make sense to cloudstack to automatically take
> decision on moving VMs but for now create report of recommended action to
> do and provide steps to do them. tbd.
>
> Cheers,
>
> PL
>

Register for ApacheCon Montreal - TODAY!!!

[Will Stevens]

Hey Everyone,
With the event just over two weeks away, we have a special offer for you.
If you are coming to the event and you want to bring some additional
colleagues or customers, now is the time.

I have been working with the ApacheCon team at the Apache Foundation who
are organizing the event to help make this conference affordable to
everyone.  They have been very generous in offering a discount code on
registration to help support our community.

$375 USD!!! -
https://www.eventbrite.com/e/apachecon-north-america-2018-registration-43200327342?discount=TCPBW18

Reach out to your colleagues and customers and invite them to the event.

Looking forward to seeing you all in a couple weeks.

Cheers,

*Will Stevens*


* <http://ca.cloudstackcollab.org/>*

Re: Kubernetes cloud provider

[Will Stevens]

That is part of it. The bigger issue is, who is maintaining that code?

On Wed, Sep 5, 2018, 6:10 AM Rafael Weingärtner 
wrote:

> So, it is a matter of getting the code from one repository and sending to
> other under Kubernetes org in Github?
>
> On Wed, Sep 5, 2018 at 5:20 AM, Sebastien Goasguen 
> wrote:
>
> > On Tue, Sep 4, 2018 at 11:28 PM Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Hi Sebastian,
> > >
> > > I read the thread there, but I did not understand it. What do they need
> > > from us?
> > > We should work with to maintain this integration.
> > >
> > >
> > They are going to remove it from the core kubernetes code base. Ideally
> it
> > should go in another repo in the kubernetes github org like
> > https://github.com/kubernetes/cloud-provider-openstack
> >
> > If nobody pick this up and gets involved, the provider will just
> disappear.
> >
> > You could also put it in github.com/cloudstack-extras or something out
> of
> > the kubernetes maintained code base
> >
> >
> >
> > > On Tue, Sep 4, 2018 at 3:18 AM, Sebastien Goasguen 
> > > wrote:
> > >
> > >> Hi all, it has been a while.
> > >>
> > >> Please see this:
> > >>
> > >> https://github.com/kubernetes/kubernetes/pull/68199
> > >>
> > >> I don't know if anyone is using it but if we don't reply the
> cloudstack
> > >> controller in kubernetes might get removed from the upstream.
> > >>
> > >> -seb
> > >>
> > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: Github Issues

[Will Stevens]

Github is the platform that is most comfortable for most users and
developers to collaborate.  Everyone knows it, regardless of their
background, so it opens our community to a wider group of people. Those are
my thoughts anyway...

Will

On Wed, Jul 18, 2018, 2:10 PM Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> There is something else that might be worth mentioning.  Since we moved to
> Github, it seems that the project is attracting more people. I mean, it
> seems that there are new players coming and reporting issues and opening
> PRs.
>
> I might be totally mistaken though.
>
>
> On Wed, Jul 18, 2018 at 3:07 PM, Will Stevens 
> wrote:
>
> > +1 to access to better automation and integration.
> >
> > On Wed, Jul 18, 2018, 12:16 PM Rene Moser  wrote:
> >
> > > Hi
> > >
> > > On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote:
> > > > Hi Paul,
> > > >
> > > > My 2 cents on the topic.
> > > >
> > > > people are commenting on issues when it should by the PR and
> vice-versa
> > > >>
> > > >
> > > > I think this is simply due to the fact that with one login you can do
> > > both,
> > > > versus before you had to have a JIRA login which people might have
> > tried
> > > to
> > > > avoid, preferring using github directly, ensuring the conversation
> will
> > > > only be on the PR. Most of the issues in Jira didn't have any
> > > conversation
> > > > at all.
> > > >
> > > > But I do feel also the pain of searching the issues on github as it's
> > > more
> > > > free-hand than a jira system. At the same time it's easier and
> quicker
> > to
> > > > navigate, so it ease the pain at the same time ;-)
> > > > I would say that the current labels isn't well organized to be able
> to
> > > > search like in jira but it could. For example any label has a prefix
> > > > describing the jira attribute type (component, version, ...) Then a
> bot
> > > > scanning the issue content could set some of them as other open
> source
> > > > project are doing. The bad thing here is that you might end up with
> too
> > > > many labels. Maybe @resmo can give his point of view on how things
> are
> > > > managed in Ansible (https://github.com/ansible/ansible/pulls - lots
> of
> > > > labels, lots of issues and PRs). I don't know if that's a solution
> but
> > > > labels seem the only way to organize things.
> > >
> > > Personally, I don't care much if jira or github issues. Github issues
> > > worked pretty well for me so far.
> > >
> > > However, We don't use all the things that make the work easier with
> > > github issues. I assume we invested much more efforts in making "jira"
> > > the way we wanted, now we assume that github just works?
> > >
> > > The benefit about github issues is, that it has an extensive api which
> > > let you automate. There are many helpful tools making our life easier.
> > >
> > > Let a bot do the issue labeling, workflowing, and user guiding and even
> > > merging PR after ci passed when 2 comments have LGTM.
> > >
> > > Look at https://github.com/kubernetes/kubernetes e.g.
> > >
> > > Short: If we want to automate things and evolve, github may be the
> > > better platform, if we want to keep things manual, then jira is
> probably
> > > more suitable.
> > >
> > > Regards
> > > René
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: Github Issues

[Will Stevens]

+1 to access to better automation and integration.

On Wed, Jul 18, 2018, 12:16 PM Rene Moser  wrote:

> Hi
>
> On 07/17/2018 02:01 PM, Marc-Aurèle Brothier wrote:
> > Hi Paul,
> >
> > My 2 cents on the topic.
> >
> > people are commenting on issues when it should by the PR and vice-versa
> >>
> >
> > I think this is simply due to the fact that with one login you can do
> both,
> > versus before you had to have a JIRA login which people might have tried
> to
> > avoid, preferring using github directly, ensuring the conversation will
> > only be on the PR. Most of the issues in Jira didn't have any
> conversation
> > at all.
> >
> > But I do feel also the pain of searching the issues on github as it's
> more
> > free-hand than a jira system. At the same time it's easier and quicker to
> > navigate, so it ease the pain at the same time ;-)
> > I would say that the current labels isn't well organized to be able to
> > search like in jira but it could. For example any label has a prefix
> > describing the jira attribute type (component, version, ...) Then a bot
> > scanning the issue content could set some of them as other open source
> > project are doing. The bad thing here is that you might end up with too
> > many labels. Maybe @resmo can give his point of view on how things are
> > managed in Ansible (https://github.com/ansible/ansible/pulls - lots of
> > labels, lots of issues and PRs). I don't know if that's a solution but
> > labels seem the only way to organize things.
>
> Personally, I don't care much if jira or github issues. Github issues
> worked pretty well for me so far.
>
> However, We don't use all the things that make the work easier with
> github issues. I assume we invested much more efforts in making "jira"
> the way we wanted, now we assume that github just works?
>
> The benefit about github issues is, that it has an extensive api which
> let you automate. There are many helpful tools making our life easier.
>
> Let a bot do the issue labeling, workflowing, and user guiding and even
> merging PR after ci passed when 2 comments have LGTM.
>
> Look at https://github.com/kubernetes/kubernetes e.g.
>
> Short: If we want to automate things and evolve, github may be the
> better platform, if we want to keep things manual, then jira is probably
> more suitable.
>
> Regards
> René
>
>
>
>
>
>

Re: Github Issues

[Will Stevens]

Ron, keep in mind that PRs on Github are different from Issues.  They are
two different features.

There will be a much cleaner, tighter integration between issues and the
solution when everything is on Github.

will

On Tue, Jul 17, 2018, 9:33 AM Ron Wheeler 
wrote:

> I may have voiced my concerns earlier but as a user, I think that JIRA
> issues are easier to follow than PRs.
> - As Paul said an issue may affect more than one version.
> - It may also require more than one PR to fully resolve the issue.
> - Issues tend to be described in terms of a problem that the user would
> recognize while PRs are most often described as what was done to fix the
> problem. The JIRA could be much easier to relate to what the user is
> seeing and more likely to show up in Google.
>
> Ron
> On 17/07/2018 4:53 AM, Paul Angus wrote:
> > Hi All,
> >
> > We have been trialling replacing Jira with Github Issues.   I think that
> we should have a conversation about it before it become the new standard by
> default.
> >
> >  From my perspective, I don't like it.  Searching has become far more
> difficult, categorising has also. When there is a bug fix it can only be
> targeted for a single version, which makes them easy to lose track of, and
> when looking at milestones issues and PRs get jumbled up and people are
> commenting on issues when it should by the PR and vice-versa (yes I've done
> it too).
> > In summary, from an administrative point of view it causes a lot more
> problems than it solves.
> >
> > I yield the floor to hear other people's opinions...
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>

Re: Infra Shutdown (Jenkins?)

[Will Stevens]

So was the box I shutdown being used?  I just want to clarify that.  I can
spin it back up if it is.  I am just trying to understand if anyone is
using it as we are paying for it.  I don't mind continuing to pay for it if
it is used, I just didn't want to pay for something if it was not used.  :)

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Wed, Jun 27, 2018 at 11:46 AM Pierre-Luc Dion 
wrote:

> Hi Rohit, Will,
>
> I have a backup of the jenkins.xml but it's from a while back, it
> shouldn't  have changed much since recent work was done on
> builds.cloudstack.org and github if not mistaking.
> We also provide an alternative: https://builds.cloudstack.org/ hosted on
> cloud.ca
>
>
>
> On Wed, Jun 27, 2018 at 11:35 AM Rohit Yadav 
> wrote:
>
> > Will, you may take the xml jenkings config backup of the jenkins box if
> > possible.
> >
> > Regards.
> >
> > Get Outlook for Android<https://aka.ms/ghei36>
> >
> > 
> > From: Will Stevens 
> > Sent: Wednesday, June 27, 2018 7:38:48 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Infra Shutdown (Jenkins?)
> >
> > Hey All,
> > I am guessing since I have not heard anyone scream that this infra was
> not
> > used.  I will be blowing these resources away by the end of the week if
> no
> > one is using these resources.
> >
> > Cheers,
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > <https://goo.gl/NYZ8KK>
> >
> >
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> > On Fri, Jun 22, 2018 at 8:40 AM Will Stevens 
> > wrote:
> >
> > > Hey Everyone,
> > > So CloudOps took over paying for a Citrix AWS account a couple years
> ago
> > > which apparently has VMs which is supporting the ACS community.  This
> > > account has been costing us about $500/month, so we want to make sure
> the
> > > VMs are actually used.
> > >
> > > I am shutting down the following VMs and if things stop working, please
> > > let me know...
> > >
> > > - jenkins.cloudstack.org | IP: 75.101.146.23 | KeyPair: davidnalley
> > > - deb build large | IP: 54.242.16.44 | KeyPair: edison
> > > -  | IP: 54.90.178.215 | KeyPair: davidnalley
> > > - PEOPLE AND FPASTE | IP: 107.21.237.59 | KeyPair: davidnalley
> > >
> > > If any of these VMs mean anything to you, please reach out to me.  I
> > can't
> > > justify paying for them if I don't know they are used.
> > >
> > > Thanks,
> > >
> > > *Will Stevens*
> > > Chief Technology Officer
> > > c 514.826.0190
> > >
> > > <https://goo.gl/NYZ8KK>
> > >
> >
>

Re: Infra Shutdown (Jenkins?)

[Will Stevens]

Hey All,
I am guessing since I have not heard anyone scream that this infra was not
used.  I will be blowing these resources away by the end of the week if no
one is using these resources.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Fri, Jun 22, 2018 at 8:40 AM Will Stevens  wrote:

> Hey Everyone,
> So CloudOps took over paying for a Citrix AWS account a couple years ago
> which apparently has VMs which is supporting the ACS community.  This
> account has been costing us about $500/month, so we want to make sure the
> VMs are actually used.
>
> I am shutting down the following VMs and if things stop working, please
> let me know...
>
> - jenkins.cloudstack.org | IP: 75.101.146.23 | KeyPair: davidnalley
> - deb build large | IP: 54.242.16.44 | KeyPair: edison
> -  | IP: 54.90.178.215 | KeyPair: davidnalley
> - PEOPLE AND FPASTE | IP: 107.21.237.59 | KeyPair: davidnalley
>
> If any of these VMs mean anything to you, please reach out to me.  I can't
> justify paying for them if I don't know they are used.
>
> Thanks,
>
> *Will Stevens*
> Chief Technology Officer
> c 514.826.0190
>
> <https://goo.gl/NYZ8KK>
>

Infra Shutdown (Jenkins?)

[Will Stevens]

Hey Everyone,
So CloudOps took over paying for a Citrix AWS account a couple years ago
which apparently has VMs which is supporting the ACS community.  This
account has been costing us about $500/month, so we want to make sure the
VMs are actually used.

I am shutting down the following VMs and if things stop working, please let
me know...

- jenkins.cloudstack.org | IP: 75.101.146.23 | KeyPair: davidnalley
- deb build large | IP: 54.242.16.44 | KeyPair: edison
-  | IP: 54.90.178.215 | KeyPair: davidnalley
- PEOPLE AND FPASTE | IP: 107.21.237.59 | KeyPair: davidnalley

If any of these VMs mean anything to you, please reach out to me.  I can't
justify paying for them if I don't know they are used.

Thanks,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

Re: [PROPOSE] Backup and Recovery Framework

[Will Stevens]

Thanks for clarifying Nicolas.  I just wanted to make sure that there
wasn't any confusion in this conversation as a 'snapshot' has different
meanings to different people/vendors, so I wanted to make sure we were all
on the same page.

BTW, for what it is worth, I love this initiative.  This is an important
feature integration which I know a LOT of organizations will appreciate.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Thu, Jun 7, 2018 at 12:57 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> First of all, the framework is agnostic of any backup vendor/provider. It
> just provides the way to communicate with the provider to allow users to
> backup their VMs.
>
>
> Will is right, backups are not the same as snapshots, I got confused with
> the Veeam backup which starts from taking a snapshot to generate the
> backup. The way they are generated are up to each vendor, and it is not
> relevant to the framework. Sorry for the confusion, we are also introducing
> the Veeam plugin in top of this framework.
>
>
> So, in terms of this framework, it does not matter what a backup is, we
> just keep a reference to an existing backup on each vendor.
>
>
> I would also like to state that this framework is not using a snapshot
> mechanism for backups in CloudStack. It is just providing interfaces and
> mechanisms for vendors/providers plugins in CloudStack. Implementation of
> each plugin should be relevant to the vendor and any backup handling will
> be external to CloudStack.
>
>
> I think that the diagram in the FS could explain what the task of the
> framework is:
> https://cwiki.apache.org/confluence/download/attachments/85476500/Backup%20and%20Recovery%20UML.png?version=1=1528367734183=v2.
> The framework simply allows management server to communicate with backup
> and recovery vendors/providers. To allow CloudStack communication with an
> specific vendor, a plugin should be implemented for it (as we are doing
> with Veeam for example).
>
>
> Please let me know if it is still confusing and I'll try to explain better
>
> 
> From: Todd Pigram 
> Sent: Thursday, June 7, 2018 12:11:18 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSE] Backup and Recovery Framework
>
> Now outside of our ACS, I use Veeam for vCloud and vSphere and use Alike
> for our XS pools. Inside ACS, the VMs use MaxBackup
>
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
> On Thu, Jun 7, 2018 at 11:09 AM, Todd Pigram  wrote:
>
> > I agree completely. That is why I use inside VM backup products
> currently.
> >
> > On Thu, Jun 7, 2018 at 11:07 AM, Will Stevens 
> > wrote:
> >
> >> I have not been following this thread entirely, but I would not count on
> >> our snapshot mechanism for backups.  If something like Veeam is used,
> then
> >> an agent is in play and that agent will quiesce the running processes,
> >> such
> >> as MySQL.  This is important in order to do backup and DR as you will
> lose
> >> transactions in memory and can potentially have a corrupted backup.
> >>
> >> Snapshots are not backups!!!
> >>
> >> *Will Stevens*
> >> Chief Technology Officer
> >> c 514.826.0190
> >>
> >> <https://goo.gl/NYZ8KK>
> >>
> >>
> >> On Thu, Jun 7, 2018 at 10:13 AM Rafael Weingärtner <
> >> rafaelweingart...@gmail.com> wrote:
> >>
> >> > Ok, now I start to understand.  So, we will be handling snapshots and
> >> they
> >> > will be sent to a third-party system.
> >> >
> >> > Now let’s proceed. If I configure this “feature” with external=false.
> >> What
> >> > does it do? Nothing? I mean, what is the purpose of this “external”
> >> > parameter?
> >> >
> >> >
> >> > On Thu, Jun 7, 2018 at 4:09 PM, Nicolas Vazquez <
> >> > nicolas.vazq...@shapeblue.com> wrote:
> >> >
> >> > > Its format may depend on the provider, but under the hood it is a
> >> > snapshot
> >> > > which can be full or incremental and it is copied and stored in a
> >> backup
> >> > > repository in one of the backup servers. For example, if you use
> >> Veeam,
> >> > you
> >> > > will find your backups stored as .vbk (for full backups) and .vib
> (for
> >> > > incremental backups). It is the task of the backup provider to
> create
> >> and
> >> > > move these files t

Re: [PROPOSE] Backup and Recovery Framework

[Will Stevens]

Yes, this is important to note as most people don't understand this
detail.  It is VERY important to this discussion though.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Thu, Jun 7, 2018 at 11:10 AM Todd Pigram  wrote:

> I agree completely. That is why I use inside VM backup products currently.
>
> On Thu, Jun 7, 2018 at 11:07 AM, Will Stevens 
> wrote:
>
> > I have not been following this thread entirely, but I would not count on
> > our snapshot mechanism for backups.  If something like Veeam is used,
> then
> > an agent is in play and that agent will quiesce the running processes,
> such
> > as MySQL.  This is important in order to do backup and DR as you will
> lose
> > transactions in memory and can potentially have a corrupted backup.
> >
> > Snapshots are not backups!!!
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > <https://goo.gl/NYZ8KK>
> >
> >
> > On Thu, Jun 7, 2018 at 10:13 AM Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Ok, now I start to understand.  So, we will be handling snapshots and
> > they
> > > will be sent to a third-party system.
> > >
> > > Now let’s proceed. If I configure this “feature” with external=false.
> > What
> > > does it do? Nothing? I mean, what is the purpose of this “external”
> > > parameter?
> > >
> > >
> > > On Thu, Jun 7, 2018 at 4:09 PM, Nicolas Vazquez <
> > > nicolas.vazq...@shapeblue.com> wrote:
> > >
> > > > Its format may depend on the provider, but under the hood it is a
> > > snapshot
> > > > which can be full or incremental and it is copied and stored in a
> > backup
> > > > repository in one of the backup servers. For example, if you use
> Veeam,
> > > you
> > > > will find your backups stored as .vbk (for full backups) and .vib
> (for
> > > > incremental backups). It is the task of the backup provider to create
> > and
> > > > move these files to the backup repository.
> > > >
> > > > 
> > > > From: Rafael Weingärtner 
> > > > Sent: Thursday, June 7, 2018 10:39:35 AM
> > > > To: dev
> > > > Subject: Re: [PROPOSE] Backup and Recovery Framework
> > > >
> > > > Ok, there are a lot of things, which are kind of blurry to me. So,
> > let’s
> > > > try to go step by step.
> > > >
> > > > Let me ask again. What is a backup of the VM? You mention
> > restore-point.
> > > > What is it? Is it a snapshot in the hypervisor (complete/partial
> > > snapshot)?
> > > > If it is not a snapshot,  what is it then? Are you installing some
> > agent
> > > in
> > > > the VM and then copying/mirroring the files in the VM’s file system?
> > > >
> > > > On Thu, Jun 7, 2018 at 3:26 PM, Nicolas Vazquez <
> > > > nicolas.vazq...@shapeblue.com> wrote:
> > > >
> > > > > Hi Daniel and Rafael,
> > > > >
> > > > >
> > > > > I have updated the diagram picture on the FS, please let me know if
> > the
> > > > > problem persists.
> > > > >
> > > > >
> > > > > @<mailto:daniel.herrm...@zv.fraunhofer.de>Daniel you are right
> about
> > > > > restoring VMs, please let me update the FS. Regarding your
> question,
> > we
> > > > > have considered the backups as a first class citizens, meaning
> that a
> > > > > backup would continue existing unless its originating VM has been
> > > > > removed/expunged. This way, listBackups API method would list them
> in
> > > > order
> > > > > to allow a user to restore a deleted VM from a backup.
> > > > >
> > > > >
> > > > > @Rafael the idea of the Dummy provider is simply returning the
> > expected
> > > > > entities from a backup provider. For example, the BackupManager
> could
> > > ask
> > > > > the BackupProvider to list its backups and would expect a list of
> > > > backups.
> > > > > As the Dummy Provider implements the BackupProvider interface, it
> has
> > > its
> > > > > own implementation of listBackups() method and simply returns some
> > mock
> > > > > entities to the Backup Manager. It d

Re: [PROPOSE] Backup and Recovery Framework

[Will Stevens]

I have not been following this thread entirely, but I would not count on
our snapshot mechanism for backups.  If something like Veeam is used, then
an agent is in play and that agent will quiesce the running processes, such
as MySQL.  This is important in order to do backup and DR as you will lose
transactions in memory and can potentially have a corrupted backup.

Snapshots are not backups!!!

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Thu, Jun 7, 2018 at 10:13 AM Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Ok, now I start to understand.  So, we will be handling snapshots and they
> will be sent to a third-party system.
>
> Now let’s proceed. If I configure this “feature” with external=false. What
> does it do? Nothing? I mean, what is the purpose of this “external”
> parameter?
>
>
> On Thu, Jun 7, 2018 at 4:09 PM, Nicolas Vazquez <
> nicolas.vazq...@shapeblue.com> wrote:
>
> > Its format may depend on the provider, but under the hood it is a
> snapshot
> > which can be full or incremental and it is copied and stored in a backup
> > repository in one of the backup servers. For example, if you use Veeam,
> you
> > will find your backups stored as .vbk (for full backups) and .vib (for
> > incremental backups). It is the task of the backup provider to create and
> > move these files to the backup repository.
> >
> > 
> > From: Rafael Weingärtner 
> > Sent: Thursday, June 7, 2018 10:39:35 AM
> > To: dev
> > Subject: Re: [PROPOSE] Backup and Recovery Framework
> >
> > Ok, there are a lot of things, which are kind of blurry to me. So, let’s
> > try to go step by step.
> >
> > Let me ask again. What is a backup of the VM? You mention restore-point.
> > What is it? Is it a snapshot in the hypervisor (complete/partial
> snapshot)?
> > If it is not a snapshot,  what is it then? Are you installing some agent
> in
> > the VM and then copying/mirroring the files in the VM’s file system?
> >
> > On Thu, Jun 7, 2018 at 3:26 PM, Nicolas Vazquez <
> > nicolas.vazq...@shapeblue.com> wrote:
> >
> > > Hi Daniel and Rafael,
> > >
> > >
> > > I have updated the diagram picture on the FS, please let me know if the
> > > problem persists.
> > >
> > >
> > > @<mailto:daniel.herrm...@zv.fraunhofer.de>Daniel you are right about
> > > restoring VMs, please let me update the FS. Regarding your question, we
> > > have considered the backups as a first class citizens, meaning that a
> > > backup would continue existing unless its originating VM has been
> > > removed/expunged. This way, listBackups API method would list them in
> > order
> > > to allow a user to restore a deleted VM from a backup.
> > >
> > >
> > > @Rafael the idea of the Dummy provider is simply returning the expected
> > > entities from a backup provider. For example, the BackupManager could
> ask
> > > the BackupProvider to list its backups and would expect a list of
> > backups.
> > > As the Dummy Provider implements the BackupProvider interface, it has
> its
> > > own implementation of listBackups() method and simply returns some mock
> > > entities to the Backup Manager. It does not store any backup, it simply
> > > creates them in execution time and returns them.
> > >
> > >
> > > From the CloudStack point of view, Backups are stored externally, on
> the
> > > Backup and Recovery provider servers and are handled by them. We keep
> > track
> > > of the existing backups in the Backup provider. Implementation may
> depend
> > > on the Backup and Recovery provider, would consist on snapshots, but
> are
> > > handled by the provider and not by CloudStack.
> > >
> > >
> > > Backup policies are created on the Backup and Recovery provider and
> > > provide retention options and periods as well as backup times. For
> > example,
> > > the provider may expose Golden, Silver and Bronze policies and have
> > > different options for each of them.
> > >
> > >
> > > The 'external' parameter on the listBackupPolicies API method would
> only
> > > ask the Backup and Recovery provider to list their policies if it is
> set
> > to
> > > true. If it is not set, or set to false, it just simply returns the
> > > existing mapped policies in CloudStack. Initially, CloudStack does not
> > > store any backup policy, those should be imported/map

Re: PR 2670: Removing an old, unused NetApp plug-in

[Will Stevens]

+1

On Wed, May 23, 2018, 3:03 PM Gabriel Beims Bräscher, 
wrote:

> I am +1 on removing it.
>
> > On May 23, 2018 at 8:59 PM Paul Angus  wrote:
> >
> >
> > +1
> >
> > There's a NetApp Jar in the nodist which is related I think - be nice to
> get rid of that too.
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Tutkowski, Mike 
> > Sent: 23 May 2018 19:53
> > To: dev@cloudstack.apache.org
> > Subject: PR 2670: Removing an old, unused NetApp plug-in
> >
> > Hi everyone,
> >
> > I opened the following PR today:
> >
> > https://github.com/apache/cloudstack/pull/2670
> >
> > There is an old, what we believe to be unused, NetApp plug-in in the
> CloudStack codebase that I’d like to remove.
> >
> > I’m sending this e-mail out for the following reasons:
> >
> >
> > 1) To see if, by chance, anyone is actually using this plug-in.
> >
> > 2) To direct any potential code reviewers to this PR, where I have
> placed a couple questions about my commit.
> >
> > To be absolutely clear here, this has nothing to do with any of the
> SolidFire plug-ins (only an old NetApp plug-in that hasn’t been updated in
> years and is probably not being used by anyone).
> >
> > Thanks,
> > Mike
>

Re: Snapshots only on Primary Storage feature

[Will Stevens]

I think reverting the change in 4.11.1 is probably a good idea.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Fri, May 18, 2018 at 2:52 PM ilya musayev <ilya.mailing.li...@gmail.com>
wrote:

> Perhaps bring it back into 4.11.1?
>
> On Fri, May 18, 2018 at 9:28 AM Suresh Kumar Anaparti <
> sureshkumar.anapa...@gmail.com> wrote:
>
> > Si / Will,
> >
> > That is just FYI, if anyone uses VMware with that flag set to false. I'm
> > neither against the feature nor telling to rip that out.
> >
> > You are correct, the PR 2081 supports KVM and Xen as the volume snapshots
> > are directly supported on them and backup operation is not tightly
> coupled
> > with the create operation.
> >
> > -Suresh
> >
> > On Fri, May 18, 2018 at 7:38 PM, Simon Weller <swel...@ena.com.invalid>
> > wrote:
> >
> > > There are plenty of features in ACS that are particular to a certain
> > > hypervisor (or hypervisor set), including VMware specific items.
> > >
> > > It was never claimed this feature worked across all hypervisors. In
> > > addition to that, the default was to leave the existing functionality
> > > exactly the way it was originally implemented and if a user wished to
> > > change the functionality they could via a global config variable.
> > >
> > > Your original spec for PR 2081 in confluence states that the PR was
> > > targeted towards KVM and Xen, so I'm confused as to why VMware is even
> > > being mentioned here.
> > >
> > >
> > > This is a major feature regression that a number of
> organizations/service
> > > providers are relying on and it wasn't called out when the PR was
> > submitted.
> > >
> > >
> > > 
> > > From: Will Stevens <wstev...@cloudops.com>
> > > Sent: Friday, May 18, 2018 6:12 AM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: Snapshots only on Primary Storage feature
> > >
> > > Just because it does not work for VMware should not a reason to rip out
> > the
> > > functionality for other hypervisors where it is being used though.
> > >
> > > I know we also have the requirement that snapshots are not
> automatically
> > > replicated to secondary storage, so this feature is useful to us.
> > >
> > > I don't understand the rational for removing the feature just because
> it
> > > does not work on VMware.
> > >
> > > On Fri, May 18, 2018, 6:27 AM Suresh Kumar Anaparti, <
> > > sureshkumar.anapa...@gmail.com> wrote:
> > >
> > > > Si,
> > > >
> > > > The PR# 1697 with the global setting *snapshot.backup.rightafter** -
> > > > false* doesn't
> > > > work for VMware as create snapshot never takes a snapshot in Primary
> > > pool,
> > > > it just returns the snapshot uuid. The backup snapshot does the
> > complete
> > > > job - creates a VM snapshot with the uuid, extracts and exports the
> > > target
> > > > volume to secondary. On demand backup snapshot doesn't work as there
> is
> > > no
> > > > snapshot in primary. Also, there'll be only one entry with Primary
> > store
> > > > role in snapshot_store_ref, which is the latest snapshot taken for
> that
> > > > volume.
> > > >
> > > > -Suresh
> > > >
> > > > On Fri, May 18, 2018 at 1:03 AM, Simon Weller
> <swel...@ena.com.invalid
> > >
> > > > wrote:
> > > >
> > > > > The whole point of the original PR was to optionally disable this
> > > > > functionality.
> > > > >
> > > > > We don't expose views of the backup state to our customers (we have
> > our
> > > > > own customer interfaces) and it's a large waste of space for us to
> be
> > > > > backing up tons of VM images when we have a solid primary storage
> > > > > infrastructure that already has lots of resiliency.
> > > > >
> > > > >
> > > > > I guess we're going to have to revisit this again before we can
> > > consider
> > > > > rebasing on 4.11.
> > > > >
> > > > > 
> > > > > From: Suresh Kumar Anaparti <sureshkumar.anapa...@gmail.com>
> > > > > Sent: Thursday, May 17, 2018 2:21 PM
> > > > > To: dev

Re: Snapshots only on Primary Storage feature

[Will Stevens]

Just because it does not work for VMware should not a reason to rip out the
functionality for other hypervisors where it is being used though.

I know we also have the requirement that snapshots are not automatically
replicated to secondary storage, so this feature is useful to us.

I don't understand the rational for removing the feature just because it
does not work on VMware.

On Fri, May 18, 2018, 6:27 AM Suresh Kumar Anaparti, <
sureshkumar.anapa...@gmail.com> wrote:

> Si,
>
> The PR# 1697 with the global setting *snapshot.backup.rightafter** -
> false* doesn't
> work for VMware as create snapshot never takes a snapshot in Primary pool,
> it just returns the snapshot uuid. The backup snapshot does the complete
> job - creates a VM snapshot with the uuid, extracts and exports the target
> volume to secondary. On demand backup snapshot doesn't work as there is no
> snapshot in primary. Also, there'll be only one entry with Primary store
> role in snapshot_store_ref, which is the latest snapshot taken for that
> volume.
>
> -Suresh
>
> On Fri, May 18, 2018 at 1:03 AM, Simon Weller 
> wrote:
>
> > The whole point of the original PR was to optionally disable this
> > functionality.
> >
> > We don't expose views of the backup state to our customers (we have our
> > own customer interfaces) and it's a large waste of space for us to be
> > backing up tons of VM images when we have a solid primary storage
> > infrastructure that already has lots of resiliency.
> >
> >
> > I guess we're going to have to revisit this again before we can consider
> > rebasing on 4.11.
> >
> > 
> > From: Suresh Kumar Anaparti 
> > Sent: Thursday, May 17, 2018 2:21 PM
> > To: dev
> > Subject: Re: Snapshots only on Primary Storage feature
> >
> > Hi Si,
> >
> > No. not possible to disable the backup to secondary. It copies the volume
> > snapshot to secondary in a background thread using asyncBackup param (set
> > to true) and allows other operations during that time.
> >
> > I understand that the backup was on demand when any operations are
> > performed on the snapshot. But, backup during that time may take
> > considerable time (depending on the snapshot size and the network
> > bandwidth), which can result in the job timeout and the User may assume
> > that it is already Backed up based on its state, unless it is documented.
> >
> > -Suresh
> >
> > On Fri, May 18, 2018 at 12:23 AM, Simon Weller 
> > wrote:
> >
> > > Suresh,
> > >
> > >
> > > With this new merged  PR, is it possible to disable the backup to
> > > secondary completely? I can't tell from the reference spec and we're
> not
> > on
> > > a 4.10/4.11 base yet.
> > >
> > > For the record, in the instances where a volume or template from
> snapshot
> > > was required, the backup image was copied on demand to secondary.
> > >
> > > In an ideal world, secondary storage wouldn't even be involved in most
> of
> > > these options, instead using the native clone features of the
> underlying
> > > storage.
> > >
> > >
> > > - Si
> > >
> > > 
> > > From: Suresh Kumar Anaparti 
> > > Sent: Thursday, May 17, 2018 1:37 PM
> > > To: dev@cloudstack.apache.org
> > > Cc: Nathan Johnson
> > > Subject: Re: Snapshots only on Primary Storage feature
> > >
> > > Hi Glen / Si,
> > >
> > > In PR# 1697, the global setting *snapshot.backup.rightafter* if set to
> > > true, it'll be the default behaviour and snapshot is copied to the
> > > secondary storage. If set to false, then the snapshot state transitions
> > are
> > > mocked and Snapshot would be in BackedUp state even though it is not
> > really
> > > in Secondary storage, which doesn't make sense. Also, that will enable
> to
> > > create a volume or template from the snapshot, which will obviously
> fail.
> > >
> > > This behavior was changed with the PR
> > > https://github.com/apache/cloudstack/pull/2081. There is a clear
> > > separation
> > > of create and backup volume snapshot operations. The global setting
> > > *snapshot.backup.rightafter* has been removed in PR# 2081.
> > >
> > > -Suresh
> > >
> > > On Thu, May 17, 2018 at 8:40 PM, Simon Weller  >
> > > wrote:
> > >
> > > > Glen,
> > > >
> > > >
> > > > This feature was implemented in 4.9 by my colleague Nathan Johnson.
> > You
> > > > enable it by changing the global setting  snapshot.backup.rightafter
> to
> > > > false.
> > > >
> > > >
> > > > The PR is reference here: https://github.com/apache/
> > cloudstack/pull/1697
> > > >
> > > >
> > > > We have the exact same use case as you, as we also use Ceph.
> > > >
> > > >
> > > > - Si
> > > >
> > > >
> > > > 
> > > > From: Glen Baars 
> > > > Sent: Thursday, May 17, 2018 9:46 AM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Snapshots only on Primary Storage 

Re: Snapshots only on Primary Storage feature

[Will Stevens]

PLD, please review.  We also need the backup to secondary to be optional/on
demand for our latest implementation plans.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>


On Thu, May 17, 2018 at 3:22 PM Suresh Kumar Anaparti <
sureshkumar.anapa...@gmail.com> wrote:

> Hi Si,
>
> No. not possible to disable the backup to secondary. It copies the volume
> snapshot to secondary in a background thread using asyncBackup param (set
> to true) and allows other operations during that time.
>
> I understand that the backup was on demand when any operations are
> performed on the snapshot. But, backup during that time may take
> considerable time (depending on the snapshot size and the network
> bandwidth), which can result in the job timeout and the User may assume
> that it is already Backed up based on its state, unless it is documented.
>
> -Suresh
>
> On Fri, May 18, 2018 at 12:23 AM, Simon Weller <swel...@ena.com.invalid>
> wrote:
>
> > Suresh,
> >
> >
> > With this new merged  PR, is it possible to disable the backup to
> > secondary completely? I can't tell from the reference spec and we're not
> on
> > a 4.10/4.11 base yet.
> >
> > For the record, in the instances where a volume or template from snapshot
> > was required, the backup image was copied on demand to secondary.
> >
> > In an ideal world, secondary storage wouldn't even be involved in most of
> > these options, instead using the native clone features of the underlying
> > storage.
> >
> >
> > - Si
> >
> > 
> > From: Suresh Kumar Anaparti <sureshkumar.anapa...@gmail.com>
> > Sent: Thursday, May 17, 2018 1:37 PM
> > To: dev@cloudstack.apache.org
> > Cc: Nathan Johnson
> > Subject: Re: Snapshots only on Primary Storage feature
> >
> > Hi Glen / Si,
> >
> > In PR# 1697, the global setting *snapshot.backup.rightafter* if set to
> > true, it'll be the default behaviour and snapshot is copied to the
> > secondary storage. If set to false, then the snapshot state transitions
> are
> > mocked and Snapshot would be in BackedUp state even though it is not
> really
> > in Secondary storage, which doesn't make sense. Also, that will enable to
> > create a volume or template from the snapshot, which will obviously fail.
> >
> > This behavior was changed with the PR
> > https://github.com/apache/cloudstack/pull/2081. There is a clear
> > separation
> > of create and backup volume snapshot operations. The global setting
> > *snapshot.backup.rightafter* has been removed in PR# 2081.
> >
> > -Suresh
> >
> > On Thu, May 17, 2018 at 8:40 PM, Simon Weller <swel...@ena.com.invalid>
> > wrote:
> >
> > > Glen,
> > >
> > >
> > > This feature was implemented in 4.9 by my colleague Nathan Johnson.
> You
> > > enable it by changing the global setting  snapshot.backup.rightafter to
> > > false.
> > >
> > >
> > > The PR is reference here:
> https://github.com/apache/cloudstack/pull/1697
> > >
> > >
> > > We have the exact same use case as you, as we also use Ceph.
> > >
> > >
> > > - Si
> > >
> > >
> > > 
> > > From: Glen Baars <g...@onsitecomputers.com.au>
> > > Sent: Thursday, May 17, 2018 9:46 AM
> > > To: dev@cloudstack.apache.org
> > > Subject: Snapshots only on Primary Storage feature
> > >
> > >
> > > Hello Devs,
> > >
> > >
> > >
> > > I have been thinking about a feature request and want to see what
> people
> > > think about the use case.
> > >
> > >
> > >
> > > We use KVM + Ceph RBD as storage.
> > >
> > >
> > >
> > > Currently, when a client takes a snapshot, Cloudstack takes a Ceph
> > > snapshot and then uses qemu-img to export to secondary storage. This
> > > creates a full backup of the server. Clients want to use this as a
> daily
> > > snapshot and it isn’t feasible due to the space requirements.
> > >
> > >
> > >
> > > We would like create the snapshot only on primary storage. It is
> > > replicated offsite and fault tolerant. I can see that the download
> > snapshot
> > > and create template features may be an issue.
> > >
> > >
> > >
> > > I have seen the below features in the recent releases and wondered if
> > this
&

Re: Community opinion regarding Apache events banner in CloudStack's website

[Will Stevens]

I vote 4

On Wed, Apr 18, 2018, 7:13 AM Rafael Weingärtner, <
rafaelweingart...@gmail.com> wrote:

> I am confused as well. Here goes a link with all image suggestions [1]. The
> tally so far is the following:
>
>- Option 1  (banner in the middle of the main CloudStack section)- 1
>vote (Rafael)
>- Option 2  (a new section called “Apache events”)- 1 vote (Gabriel)
>- Option 3 (Banner aligned right and under CloudMonkey image – we can
>apply some improvements suggested by Nitin here) – 8 votes (Dag, Swen,
>Stephan, Boris, Ron, Grégorie, Nitin, Mauricio)
>- Option 4  (aligned left) – 1 vote (Nicolás)
>
>
> [1] https://drive.google.com/open?id=1dqjPI2PBZ3hvKr2eEWaH3Fj_hLhXUxvB
>
> On Wed, Apr 18, 2018 at 8:06 AM, Will Stevens <wstev...@cloudops.com>
> wrote:
>
> > Can we list the options and their voting numbers?  I am a bit confused
> > right now.
> >
> > I like the one that is left aligned under the text and keeps the logo on
> > the right full size.
> >
> > On Tue, Apr 17, 2018, 10:41 PM Nitin Maharana, <nitin.mahar...@gmail.com
> >
> > wrote:
> >
> > > +1 for the third option. I think It would even look good if we adjust
> the
> > > vertical alignment of the word "Apache CloudStack" to center.
> > >
> > > On Wed, Apr 18, 2018 at 12:12 AM, Rafael Weingärtner <
> > > rafaelweingart...@gmail.com> wrote:
> > >
> > > > Third option (suggested by Dag) -
> > > > https://drive.google.com/open?id=16FEu9tD1HZqwxLp2lrnUBmsuRJNLpDqU
> > > >
> > > > On Tue, Apr 17, 2018 at 3:39 PM, Dag Sonstebo <
> > > dag.sonst...@shapeblue.com>
> > > > wrote:
> > > >
> > > > > Hi Rafael – in my opinion you need it fairly prominent so people
> > notice
> > > > it
> > > > > – so option 1, but maybe put it underneath the CloudMonkey logo on
> > the
> > > > > right hand side?
> > > > >
> > > > > Regards,
> > > > > Dag Sonstebo
> > > > > Cloud Architect
> > > > > ShapeBlue
> > > > >
> > > > > On 17/04/2018, 19:35, "Rafael Weingärtner" <
> > > rafaelweingart...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > Ah damm.. I forgot about the file stripping in our mailing
> list.
> > > > > Sorry guys. Here they go.
> > > > >
> > > > > - first one:
> > > > > https://drive.google.com/open?id=1vSqni_GEj3YJjuGehxe-_
> > dnrNqQP7x8y
> > > > >
> > > > > - second one:
> > > > >
> https://drive.google.com/open?id=1LEmt9g5ceAUeTuc2a1Cb4uctOwyz5
> > eQ8
> > > > >
> > > > > On Tue, Apr 17, 2018 at 3:31 PM, Dag Sonstebo <
> > > > > dag.sonst...@shapeblue.com>
> > > > > wrote:
> > > > >
> > > > > > The white one is quite nice ☺
> > > > > >
> > > > > > Joking aside – looks like they got stripped from your email
> > > Rafael.
> > > > > >
> > > > > > Regards,
> > > > > > Dag Sonstebo
> > > > > > Cloud Architect
> > > > > > ShapeBlue
> > > > > >
> > > > > > From: Rafael Weingärtner <rafaelweingart...@gmail.com>
> > > > > > Reply-To: "dev@cloudstack.apache.org" <
> > dev@cloudstack.apache.org
> > > >
> > > > > > Date: Tuesday, 17 April 2018 at 19:13
> > > > > > To: users <us...@cloudstack.apache.org>, dev <
> > > > > dev@cloudstack.apache.org>
> > > > > > Subject: Community opinion regarding Apache events banner in
> > > > > CloudStack's
> > > > > > website
> > > > > >
> > > > > > Hello folks,
> > > > > > I am trying to work out something to put Apache events banner
> > on
> > > > our
> > > > > > website. So far I came up with two proposals. Which one of
> them
> > > do
> > > > > you guys
> > > > > > prefer?
> > > > > > First one:
> > > > > > [cid:ii_jg3zjco00_162d4ce7db0cd3da]
> > > > > >
> > > > > >
> > > > > > Second:
> > > > > > [cid:ii_jg3zk0e01_162d4cefaef3a1ce]
> > > > > >
> > > > > > --
> > > > > > Rafael Weingärtner
> > > > > >
> > > > > > dag.sonst...@shapeblue.com
> > > > > > www.shapeblue.com
> > > > > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > > > > @shapeblue
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Rafael Weingärtner
> > > > >
> > > > >
> > > > >
> > > > > dag.sonst...@shapeblue.com
> > > > > www.shapeblue.com
> > > > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > > > @shapeblue
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Rafael Weingärtner
> > > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: Community opinion regarding Apache events banner in CloudStack's website

[Will Stevens]

Can we list the options and their voting numbers?  I am a bit confused
right now.

I like the one that is left aligned under the text and keeps the logo on
the right full size.

On Tue, Apr 17, 2018, 10:41 PM Nitin Maharana, 
wrote:

> +1 for the third option. I think It would even look good if we adjust the
> vertical alignment of the word "Apache CloudStack" to center.
>
> On Wed, Apr 18, 2018 at 12:12 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Third option (suggested by Dag) -
> > https://drive.google.com/open?id=16FEu9tD1HZqwxLp2lrnUBmsuRJNLpDqU
> >
> > On Tue, Apr 17, 2018 at 3:39 PM, Dag Sonstebo <
> dag.sonst...@shapeblue.com>
> > wrote:
> >
> > > Hi Rafael – in my opinion you need it fairly prominent so people notice
> > it
> > > – so option 1, but maybe put it underneath the CloudMonkey logo on the
> > > right hand side?
> > >
> > > Regards,
> > > Dag Sonstebo
> > > Cloud Architect
> > > ShapeBlue
> > >
> > > On 17/04/2018, 19:35, "Rafael Weingärtner" <
> rafaelweingart...@gmail.com>
> > > wrote:
> > >
> > > Ah damm.. I forgot about the file stripping in our mailing list.
> > > Sorry guys. Here they go.
> > >
> > > - first one:
> > > https://drive.google.com/open?id=1vSqni_GEj3YJjuGehxe-_dnrNqQP7x8y
> > >
> > > - second one:
> > > https://drive.google.com/open?id=1LEmt9g5ceAUeTuc2a1Cb4uctOwyz5eQ8
> > >
> > > On Tue, Apr 17, 2018 at 3:31 PM, Dag Sonstebo <
> > > dag.sonst...@shapeblue.com>
> > > wrote:
> > >
> > > > The white one is quite nice ☺
> > > >
> > > > Joking aside – looks like they got stripped from your email
> Rafael.
> > > >
> > > > Regards,
> > > > Dag Sonstebo
> > > > Cloud Architect
> > > > ShapeBlue
> > > >
> > > > From: Rafael Weingärtner 
> > > > Reply-To: "dev@cloudstack.apache.org"  >
> > > > Date: Tuesday, 17 April 2018 at 19:13
> > > > To: users , dev <
> > > dev@cloudstack.apache.org>
> > > > Subject: Community opinion regarding Apache events banner in
> > > CloudStack's
> > > > website
> > > >
> > > > Hello folks,
> > > > I am trying to work out something to put Apache events banner on
> > our
> > > > website. So far I came up with two proposals. Which one of them
> do
> > > you guys
> > > > prefer?
> > > > First one:
> > > > [cid:ii_jg3zjco00_162d4ce7db0cd3da]
> > > >
> > > >
> > > > Second:
> > > > [cid:ii_jg3zk0e01_162d4cefaef3a1ce]
> > > >
> > > > --
> > > > Rafael Weingärtner
> > > >
> > > > dag.sonst...@shapeblue.com
> > > > www.shapeblue.com
> > > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> > >
> > >
> > > dag.sonst...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Rafael Weingärtner
> >
>

ACS based clouds in Russia

[Will Stevens]

Hello All,
We need to build an application deployment in Russia and I am looking for
an ACS based cloud to build it on.  Does anyone know of any ACS based IaaS
clouds in Russia?

Thanks,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

Re: [DISCUSS] CloudMonkey 6.0.0-alpha (about six years after initial version in 2012)

[Will Stevens]

+1. It has been a great tool for years.  Looking forward to the golang
version.

On Apr 10, 2018 7:59 AM, "Rohit Yadav"  wrote:

All,


Few months ago, I started porting the current code to be compatible with
both Python2 and Python3 to make it run with both Python2 (for older
systems such as CentOS6 etc) and Python3 (for newer platforms). The work
was not a success, another problem was that cloudmonkey was not easy to
install and required several dependencies that would certainly fail on
older systems with Python 2.6.x.


Considering all things, I started working on an experimental golang port
[2] and happy to announce that the initial alpha version shows a lot of
promise and is 5-20x faster than the python based cli [1]. The compiled
binary runs on several targets, including windows [1].


I cannot commit to a timeline/release date yet but the aim of this thread
is to discuss and propose the simplification of the CLI which may require
removal of some features and some breaking changes may be introduced:


- Make json the default output format

- Remove coloured output

- Remove unpopular, least user output formats? xml, default (line-separate
key=value), table?

- Remove `set` options: color, expires, (custom) prompt

- Remove `paramcompletion` option, this will be true/enabled by default

- Remove signature version and expires (I'm not sure why this is needed or
used)

- Remove history_file, cache_file, log_file options, use the default paths
in folder at (user's  home directory)/.cloudmonkey.

- Remove shell based execution from interactive interpreter mode (using !
or shell keywords)

- Remove support for CloudStack older than 4.5, i.e. it won't be tested
against older cloudstacks.

- Remove a default API cache with the client, for a fresh env without any
~/.cloudmonkey/cache; users can run `sync` command against a management
server.

- Interactive API parameter completion in CLI mode: the current API
parameter completion requires the user to manually copy/paste the uuids, or
autocomplete by typing parts of the uuids/option.

- Improve how maps are passed.

- Good to have: bash/zsh completion.


Please share your thoughts, and objections (especially if you're using the
proposed features to be removed in version 6.x).


[1] https://twitter.com/rhtyd/status/983448788059770882

[2] https://github.com/rhtyd/cmk


- Rohit





rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

Re: Committee to Sort through CCC Presentation Submissions

[Will Stevens]

gt;
> >> > > On 4/1/18, 9:18 AM, "Ron Wheeler" <
> rwhee...@artifact-software.com>
> >> > wrote:
> >> > >
> >> > > How many people have signed up to be reviewers?
> >> > >
> >> > > I don't think that scheduling is part of the review
> process and
> >> > that
> >> > > can
> >> > > be done by the person/team "organizing" ApacheCon on
> behalf of
> >> > the PMC.
> >> > >
> >> > > To me review is looking at content for
> >> > > - relevance
> >> > > - quality of the presentations (suggest fixes to
> content,
> >> > English,
> >> > > graphics, etc.)
> >> > > This should result in a consensus score
> >> > > - Perfect - ready for prime time
> >> > > - Needs minor changes as documented by the reviewers
> >> > > - Great topic but needs more work - perhaps a reviewer
> could
> >> > volunteer
> >> > > to work with the presenter to get it ready if chosen
> >> > > - Not recommended for topic or content reasons
> >> > >
> >> > > The reviewers could also make non-binding
> recommendations about
> >> > the
> >> > > balance between topics - marketing(why Cloudstack),
> >> > > Operations/implementation, Technical details, Roadmap,
> etc.
> >> > based on
> >> > > what they have seen.
> >> > >
> >> > > This should be used by the organizers to make the
> choices and
> >> > organize
> >> > > the program.
> >> > > The organizers have the final say on the choice of
> presentations
> >> > and
> >> > > schedule
> >> > >
> >> > > Reviewers are there to help the process not control it.
> >> > >
> >> > > I would be worried that you do not have enough
> reviewers rather
> >> > than
> >> > > too
> >> > > many.
> >> > > Then the work falls on the PMC and organizers.
> >> > >
> >> > > When planning meetings, I would recommend that you
> clearly
> >> > separate the
> >> > > roles and only invite the reviewers to the meetings
> about
> >> > review. Get
> >> > > the list of presentation to present to the reviewers
> and decide
> >> > if
> >> > > there
> >> > > are any instructions that you want to give to reviewers.
> >> > > I would recommend that you keep the organizing group
> small.
> >> > Membership
> >> > > should be set by the PMC and should be people that are
> committed
> >> > to the
> >> > > ApacheCon project and have the time. The committee can
> request
> >> > help for
> >> > > specific tasks from others in the community who are not
> on the
> >> > > committee.
> >> > >
> >> > > I would also recommend that organizers do not do
> reviews. They
> >> > should
> >> > > read the finalists but if they do reviews, there may be
> a
> >> > suggestion of
> >> > > favouring presentations that they reviewed. It also
> ensures that
> >> > the
> >> > > organizers are not getting heat from rejected
> presenters - "it
> >> > is the
> >> > > reviewers fault you did not get selected".
> >> > >
> >> > > My advice is to get as many reviewers as you can so
> that no one
> >> > is
> >> > > essential and each reviewer has a limited number of
> >> > presentations to
> >> > > review but each presentation gets reviewed by multiple
> people.
> >> > Also
> >> >

Re: Committee to Sort through CCC Presentation Submissions

[Will Stevens]

In the past the committee was chosen as a relatively small group in order
to make it easier to manage feedback.  In order to make it fair to everyone
in the community, I would suggest that instead of doing it with a small
group, we do it out in the open on a scheduled call.

We will have to get a list of the talks that are CloudStack specific from
ApacheCon, but that should be possible.

Once we have the talks selected, then a smaller number of us can work on
setting up the actual ordering and the details.

I have been quite involved so far.  Giles and I have been organizing the
sponsors, website and dealing with ApacheCon so far.  Obviously, Mike is
also working on this as well.

I think we are headed in the right direction on this.

Cheers,

Will

On Mar 31, 2018 11:49 PM, "Tutkowski, Mike" 
wrote:

Hi Ron,

I am definitely open to working this however makes the most sense.

It looks like Will’s e-mail indicates that the process I suggested has been
followed in the past (which is how I recall, as well).

Let’s make sure I understood Will correctly.

Will – Are you, in fact, indicating that what I was suggesting is how we
have reviewed the CFP in the past? If so, are you able to address Ron’s
concerns?

Also, Will – I am not sure about a hackathon. Let’s chat with Giles once
he’s back from vacation since he’s been the most involved with organizing
the CloudStack track within ApacheCon.

Thanks!

Mike


On 3/31/18, 9:00 PM, "Ron Wheeler"  wrote:

I am not sure about your concern in that case.
I am not sure why people not interested in Cloudstack would volunteer as
reviewers and want to pick bad presentations.

I would be more worried that there are not enough good presentations
proposed rather than some meritorious presentation will get rejected due
to "outsiders" voting it down in favour of less useful presentations.

It may be tricky to get balance if that means taking "bad" proposals
that can not be fixed that cover topics that are in areas that are not
otherwise covered at the expense of great presentations that are in
areas with many choices.

We should wait to see how many presentations have to be rejected and the
number of reviewers before getting too exercised over the loyalty of
reviewers.

Getting more reviewers is likely the most effective way to see that a
wider range of topics is covered.

Ron

On 31/03/2018 7:15 PM, Tutkowski, Mike wrote:
> Hi Ron,
>
>  From what I understand, the CloudStack proposals will be mixed in
with all of the ApacheCon proposals.
>
> In the past when I’ve participated in these CloudStack panels to
review proposals, we had to compare each proposal against the others to
arrive at a balance of topics (i.e. not all networking focused, not all
XenServer focused, etc.) and to suggest improvements for proposals that we
did not accept for other reasons.
>
>  From what I understand (but Giles can comment further on this), we
have a track at ApacheCon and will need to fill it with X number of
presentations. To do this, it seems like a CloudStack-focused panel would
be a good approach, but I am definitely open to another approach. We don’t
want to exclude anyone (in or out of the CloudStack Community) who might
like to provide input. Anyone who is interested would, of course, be free
to join us in combing through the proposals.
>
> We don’t need to get started on this right away. The CFP just closed
yesterday. Let’s wait for feedback from Giles (who is currently on
vacation) and go from there.
>
> Thanks!
> Mike
>
> On 3/31/18, 6:59 AM, "Ron Wheeler" 
wrote:
>
>  Is this a real concern?
>  Why would a large number of Apache contributors who are not
interested
>  in Cloudstack (enough to outvote those "part of the Cloudstack
>  community") get involved as reviewers
>
>  Reviewing involves some commitment of time so I am hard pressed
to guess
>  why some Apache contributor would volunteer to do the work in
order to
>  veto a presentation that they have not yet seen or have no
interest in
>  seeing.
>
>  Are we guaranteed a fixed number of hours of presentations or is
the
>  review process part of the allocation of overall time?
>
>  On what basis can some group veto a presentation?
>  That would seem to be a very strong action and I would hope that
it
>  requires a strong reason.
>
>  OTOH if a large??? number of Apache contributors (regardless of
their
>  affiliation) say that a presentation has serious issues or very
limited
>  interest, that would seem to be a red flag that the presentation
>  requires improvement or needs to be dropped in favour of another
>  Cloudstack presentation, if it can not be 

Re: Committee to Sort through CCC Presentation Submissions

[Will Stevens]

Ya Mike, this is the way we have done it in the past and it works well.
Anyone interested can join us, and we will setup a call to review the talks
on a specific date. Then go from there.

Do we know what the second day will be yet?  I have to try to figure out a
venue (hackathon?) for a third day, but I need a date.

Will

On Sat, Mar 31, 2018, 7:16 PM Tutkowski, Mike, 
wrote:

> Hi Ron,
>
> From what I understand, the CloudStack proposals will be mixed in with all
> of the ApacheCon proposals.
>
> In the past when I’ve participated in these CloudStack panels to review
> proposals, we had to compare each proposal against the others to arrive at
> a balance of topics (i.e. not all networking focused, not all XenServer
> focused, etc.) and to suggest improvements for proposals that we did not
> accept for other reasons.
>
> From what I understand (but Giles can comment further on this), we have a
> track at ApacheCon and will need to fill it with X number of presentations.
> To do this, it seems like a CloudStack-focused panel would be a good
> approach, but I am definitely open to another approach. We don’t want to
> exclude anyone (in or out of the CloudStack Community) who might like to
> provide input. Anyone who is interested would, of course, be free to join
> us in combing through the proposals.
>
> We don’t need to get started on this right away. The CFP just closed
> yesterday. Let’s wait for feedback from Giles (who is currently on
> vacation) and go from there.
>
> Thanks!
> Mike
>
> On 3/31/18, 6:59 AM, "Ron Wheeler"  wrote:
>
> Is this a real concern?
> Why would a large number of Apache contributors who are not interested
> in Cloudstack (enough to outvote those "part of the Cloudstack
> community") get involved as reviewers
>
> Reviewing involves some commitment of time so I am hard pressed to
> guess
> why some Apache contributor would volunteer to do the work in order to
> veto a presentation that they have not yet seen or have no interest in
> seeing.
>
> Are we guaranteed a fixed number of hours of presentations or is the
> review process part of the allocation of overall time?
>
> On what basis can some group veto a presentation?
> That would seem to be a very strong action and I would hope that it
> requires a strong reason.
>
> OTOH if a large??? number of Apache contributors (regardless of their
> affiliation) say that a presentation has serious issues or very limited
> interest, that would seem to be a red flag that the presentation
> requires improvement or needs to be dropped in favour of another
> Cloudstack presentation, if it can not be fixed.
>
> We should also be aware that this is an opportunity to "market"
> Cloudstack to the broader Apache community.
> Outside reviewers might have valuable input into how presentations can
> attract new adopters or be clearer to the broader DevOps community.
> We also need to remember that we do have an active community and other
> opportunities during the year to present presentations that do not get
> selected for this conference.
>
> If their is a real fear that a lot of "outsiders" are going to disrupt
> the review process, a more reasonable response would seem to be to get
> more reviewers from the community.
>
> I have volunteered already.
>
> Ron
>
> On 30/03/2018 11:11 PM, Tutkowski, Mike wrote:
> > Hi Rafael,
> >
> > It’s a little bit tricky in our particular situation. Allow me to
> explain:
> >
> > As you are likely aware, the CloudStack Collaboration Conference
> will be held as a track in the larger ApacheCon conference in Montreal this
> coming September.
> >
> > It is true, as you say, that anyone who wishes to do so can
> contribute to reviewing the CFP for ApacheCon.
> >
> > What is a bit of a concern, however, is that we might get certain
> CloudStack CFP proposals vetoed by people who are not, per se, a part of
> our community.
> >
> > That being the case, I have contacted the organizers for ApacheCon
> to see if there is some way we can section off the CloudStack CFP from the
> larger ApacheCon CFP for review purposes.
> >
> > Assuming we can do this, the panel that I am proposing here would
> handle this review task.
> >
> > I hope that helps clarify the situation.
> >
> > Thanks!
> > Mike
> >
> > On 3/30/18, 8:38 AM, "Rafael Weingärtner" <
> rafaelweingart...@gmail.com> wrote:
> >
> >  Are we going to have a separated review process?
> >
> >  I thought anybody could go here [1] and apply for a reviewer
> position and
> >  start reviewing. Well, that is what I did. I have already
> reviewed some
> >  CloudStack proposals (of course I did not review mines). After
> asking to
> >  review presentations, Rich has 

Re: Committee to Sort through CCC Presentation Submissions

[Will Stevens]

I can support this.

Cheers,

Will

On Tue, Mar 27, 2018, 12:39 PM Tutkowski, Mike, 
wrote:

> Hi everyone,
>
> As you may be aware, this coming September in Montreal, the CloudStack
> Community will be hosting the CloudStack Collaboration Conference:
>
> http://ca.cloudstackcollab.org/
>
> Even though the event is six months away, we are on a tight schedule with
> regards to the Call For Participation (CFP):
>
> https://www.apachecon.com/acna18/schedule.html
>
> If you are interested in submitting a talk, please do so before March 30th.
>
> That being said, as usual, we will have need of a small committee to sort
> through these presentation submissions.
>
> If you are interested in helping out in this process, please reply to this
> message.
>
> Thanks!
> Mike
>

Re: [VOTE] Move to Github issues

[Will Stevens]

+1

On Mon, Mar 26, 2018, 5:51 AM Nicolas Vazquez, <
nicolas.vazq...@shapeblue.com> wrote:

> +1
>
> 
> From: Dag Sonstebo 
> Sent: Monday, March 26, 2018 5:06:29 AM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 07:33, "Rohit Yadav"  wrote:
>
> All,
>
> Based on the discussion last week [1], I would like to start a vote to
> put
> the proposal into effect:
>
> - Enable Github issues, wiki features in CloudStack repositories.
> - Both user and developers can use Github issues for tracking issues.
> - Developers can use #id references while fixing an existing/open
> issue in
> a PR [2]. PRs can be sent without requiring to open/create an issue.
> - Use Github milestone to track both issues and pull requests towards a
> CloudStack release, and generate release notes.
> - Relax requirement for JIRA IDs, JIRA still to be used for historical
> reference and security issues. Use of JIRA will be discouraged.
> - The current requirement of two(+) non-author LGTMs will continue for
> PR
> acceptance. The two(+) PR non-authors can advise resolution to any
> issue
> that we've not already discussed/agreed upon.
>
> For sanity in tallying the vote, can PMC members please be sure to
> indicate
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Vote will be open for 120 hours. If the vote passes the following
> actions
> will be taken:
> - Get Github features enabled from ASF INFRA
> - Update CONTRIBUTING.md and other relevant cwiki pages.
> - Update project website
>
> [1] https://markmail.org/message/llodbwsmzgx5hod6
> [2]
> https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/
>
> Regards,
> Rohit Yadav
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
>

Re: Marketing CCC Montreal

[Will Stevens]

Hahaha...  Right...  I didn't notice it was THAT wrong.  :P

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Thu, Mar 22, 2018 at 10:59 AM, Khosrow Moossavi <kmooss...@cloudops.com>
wrote:

> Well whatever the dates it will not be in May, it will be in September!
>
>
>
>
> On Thu, Mar 22, 2018 at 10:55 AM, Will Stevens <wstev...@cloudops.com>
> wrote:
>
> > The dates are somewhat unclear, so its not really 'wrong' yet.  We know
> we
> > start on the 24th.  We are not sure what the second day we will get from
> > ApacheCon is yet.  I am working on getting a space together for a
> hackathon
> > day on either the 25th or 26th depending on what the second day we get
> from
> > ApacheCon is, so there are still some logistics in play still.
> >
> > I am advertising the 24-26th in the absence of official details as I am
> > confident I can get another space online for a hackathon day.  More
> details
> > will be available once we get details from ApacheCon and I work out a
> space
> > for the hackathon.
> >
> > I hope that is not too difficult to understand.
> >
> > Cheers,
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > <https://goo.gl/NYZ8KK>
> >
> > On Thu, Mar 22, 2018 at 10:49 AM, Khosrow Moossavi <
> kmooss...@cloudops.com
> > >
> > wrote:
> >
> > > Somehow related, the tweet sent out earlier today, has the date wrong.
> > >
> > > https://twitter.com/CloudStack/status/976819870426902530?s=19
> > >
> > >
> > > On Mar 22, 2018 10:37, "Will Stevens" <sw...@apache.org> wrote:
> > >
> > > > Hey Everyone,
> > > > We need your help to promote the visibility of the CCC conference we
> > are
> > > > running later this year in September.
> > > >
> > > > I have put together an information website to help us promote the
> CCC:
> > > > http://ca.cloudstackcollab.org/
> > > >
> > > > I will keep the website updated with additional detail as we get more
> > > > information.
> > > >
> > > > *PLEASE NOTE: Call For Papers closes on March 30th.  Please get your
> > > topics
> > > > in ASAP.*  On that note, make sure the title of your talk includes
> the
> > > word
> > > > 'CloudStack' so we are able to get the talk in the correct CCC track.
> > > >
> > > > Additionally, in order to get more visibility for the event, please
> > > > consider adding the following footer to your email signature (ideally
> > > > linking to the CCC site).  The footer is available here:
> > > > http://ca.cloudstackcollab.org/img/ccc_mtl_footer.png
> > > >
> > > > Let us know if you have any questions...
> > > >
> > > > *Will Stevens*
> > > >
> > > >
> > > > * <http://ca.cloudstackcollab.org/>*
> > > >
> > >
> >
>

Re: Marketing CCC Montreal

[Will Stevens]

The dates are somewhat unclear, so its not really 'wrong' yet.  We know we
start on the 24th.  We are not sure what the second day we will get from
ApacheCon is yet.  I am working on getting a space together for a hackathon
day on either the 25th or 26th depending on what the second day we get from
ApacheCon is, so there are still some logistics in play still.

I am advertising the 24-26th in the absence of official details as I am
confident I can get another space online for a hackathon day.  More details
will be available once we get details from ApacheCon and I work out a space
for the hackathon.

I hope that is not too difficult to understand.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Thu, Mar 22, 2018 at 10:49 AM, Khosrow Moossavi <kmooss...@cloudops.com>
wrote:

> Somehow related, the tweet sent out earlier today, has the date wrong.
>
> https://twitter.com/CloudStack/status/976819870426902530?s=19
>
>
> On Mar 22, 2018 10:37, "Will Stevens" <sw...@apache.org> wrote:
>
> > Hey Everyone,
> > We need your help to promote the visibility of the CCC conference we are
> > running later this year in September.
> >
> > I have put together an information website to help us promote the CCC:
> > http://ca.cloudstackcollab.org/
> >
> > I will keep the website updated with additional detail as we get more
> > information.
> >
> > *PLEASE NOTE: Call For Papers closes on March 30th.  Please get your
> topics
> > in ASAP.*  On that note, make sure the title of your talk includes the
> word
> > 'CloudStack' so we are able to get the talk in the correct CCC track.
> >
> > Additionally, in order to get more visibility for the event, please
> > consider adding the following footer to your email signature (ideally
> > linking to the CCC site).  The footer is available here:
> > http://ca.cloudstackcollab.org/img/ccc_mtl_footer.png
> >
> > Let us know if you have any questions...
> >
> > *Will Stevens*
> >
> >
> > * <http://ca.cloudstackcollab.org/>*
> >
>

Marketing CCC Montreal

[Will Stevens]

Hey Everyone,
We need your help to promote the visibility of the CCC conference we are
running later this year in September.

I have put together an information website to help us promote the CCC:
http://ca.cloudstackcollab.org/

I will keep the website updated with additional detail as we get more
information.

*PLEASE NOTE: Call For Papers closes on March 30th.  Please get your topics
in ASAP.*  On that note, make sure the title of your talk includes the word
'CloudStack' so we are able to get the talk in the correct CCC track.

Additionally, in order to get more visibility for the event, please
consider adding the following footer to your email signature (ideally
linking to the CCC site).  The footer is available here:
http://ca.cloudstackcollab.org/img/ccc_mtl_footer.png

Let us know if you have any questions...

*Will Stevens*


* <http://ca.cloudstackcollab.org/>*

Re: CFP- Cloudstack collab conference 2018

[Will Stevens]

I don't even see a CloudStack reference on their site right now, so I am
not sure where that would go.  Are you basically saying that we should ask
that the CloudStack Collab be added to their site and pointed to our site?

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Wed, Mar 21, 2018 at 9:00 AM, Kevin A. McGrail <kmcgr...@apache.org>
wrote:

> +planners
>
> One thing I would add if Rich thinks it is ok would be a link added to
> apachecon.com to  http://cloudstackcollab.org/?
>
> Regards,
> KAM
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
>
> On Tue, Mar 20, 2018 at 6:44 PM, Will Stevens <wstev...@cloudops.com>
> wrote:
>
>> It is a bit quick and dirty, but I have updated the CloudStack
>> Collaboration Conference websites.
>>
>> Here is the parent site: http://cloudstackcollab.org/
>>
>> Here is the site for this specific event: http://ca.cloudstackcollab.org/
>>
>> I have setup the 'Sponsor' button to basically do a `mailto` the PMC
>> list.  I don't have a better solution than that for now.
>>
>> Also, I have defined the dates as what I expect them to be, but we don't
>> know them for sure yet.
>>
>> I setup the hashtag of #ccc2018mtl which follows a similar format as some
>> previous hashtags for the event.
>>
>> I have tried to setup the 'Speaker' and 'Schedule' details with as much
>> appropriate info as I can.
>>
>> Let me know if you see things that are wrong or you would like changes.
>> I basically built the site while I sat in a meeting this afternoon, so it
>> is not perfect or very extensive, but it covers the main pieces it needs to.
>>
>> Thoughts?
>>
>> *Will Stevens*
>> Chief Technology Officer
>> c 514.826.0190 <(514)%20826-0190>
>>
>> <https://goo.gl/NYZ8KK>
>>
>> On Mon, Mar 19, 2018 at 6:18 AM, Giles Sirett <giles.sir...@shapeblue.com
>> > wrote:
>>
>>> All
>>> CFP - CLOUDSTACK COLLAB 2018 - DEADLINE 30 MARCH
>>>
>>> We have an agreement in principle to co-locate this years Cloudstack
>>> conference with Apachecon
>>> Montreal  24-25 September
>>> https://www.apachecon.com/
>>> As last year in Miami, we will be having a "conference in a conference"
>>> - so tickets will allow people to experience the whole Apachecon event
>>>
>>> There are still some details still to work out (on the name, exact
>>> format and exactly what facilities we can have), but the key thing right
>>> now  is to get talks  submitted. We're using the Apachecon CFP:
>>> https://www.apachecon.com/acna18/
>>>
>>> I apologise for the short notice, but the CFP closes on March 30.
>>> There is no way to tell the CFP that you are submitting something
>>> specifically for Cloudstack - so please tag your talk title with
>>> "[Cloudstack]:talk name"
>>>
>>> There is lots to do around sponsorship, exact format, etc but the key
>>> deadline this stage is to get plenty of talks submitted
>>>
>>> Other things worth considering:
>>>
>>>   1.  We will need a panel to sift/select talks. Wido led on this last
>>> year. MikeT, do you want to lead this year ?
>>>   2.  It will be important that we encourage interested companies to
>>> help sponsor the event. Anybody who think their company may sponsor, please
>>> ping Kevin A. McGrail kmcgr...@apache.org<mailto:kmcgr...@apache.org>
>>>
>>> Kind regards
>>> Giles
>>>
>>>
>>> giles.sir...@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London  WC2N
>>> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
>>> 4HSUK
>>> @shapeblue
>>>
>>>
>>>
>>>
>>
>

Re: CFP- Cloudstack collab conference 2018

[Will Stevens]

It is a bit quick and dirty, but I have updated the CloudStack
Collaboration Conference websites.

Here is the parent site: http://cloudstackcollab.org/

Here is the site for this specific event: http://ca.cloudstackcollab.org/

I have setup the 'Sponsor' button to basically do a `mailto` the PMC list.
I don't have a better solution than that for now.

Also, I have defined the dates as what I expect them to be, but we don't
know them for sure yet.

I setup the hashtag of #ccc2018mtl which follows a similar format as some
previous hashtags for the event.

I have tried to setup the 'Speaker' and 'Schedule' details with as much
appropriate info as I can.

Let me know if you see things that are wrong or you would like changes.  I
basically built the site while I sat in a meeting this afternoon, so it is
not perfect or very extensive, but it covers the main pieces it needs to.

Thoughts?

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Mon, Mar 19, 2018 at 6:18 AM, Giles Sirett <giles.sir...@shapeblue.com>
wrote:

> All
> CFP - CLOUDSTACK COLLAB 2018 - DEADLINE 30 MARCH
>
> We have an agreement in principle to co-locate this years Cloudstack
> conference with Apachecon
> Montreal  24-25 September
> https://www.apachecon.com/
> As last year in Miami, we will be having a "conference in a conference" -
> so tickets will allow people to experience the whole Apachecon event
>
> There are still some details still to work out (on the name, exact format
> and exactly what facilities we can have), but the key thing right now  is
> to get talks  submitted. We're using the Apachecon CFP:
> https://www.apachecon.com/acna18/
>
> I apologise for the short notice, but the CFP closes on March 30.
> There is no way to tell the CFP that you are submitting something
> specifically for Cloudstack - so please tag your talk title with
> "[Cloudstack]:talk name"
>
> There is lots to do around sponsorship, exact format, etc but the key
> deadline this stage is to get plenty of talks submitted
>
> Other things worth considering:
>
>   1.  We will need a panel to sift/select talks. Wido led on this last
> year. MikeT, do you want to lead this year ?
>   2.  It will be important that we encourage interested companies to help
> sponsor the event. Anybody who think their company may sponsor, please ping
> Kevin A. McGrail kmcgr...@apache.org<mailto:kmcgr...@apache.org>
>
> Kind regards
> Giles
>
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: Cloudstack collab conference 2018

[Will Stevens]

Sorry.  I thought I had responded to this thread.  I will get the websites
sorted out in the next couple days...

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Tue, Mar 13, 2018 at 4:56 PM, Tutkowski, Mike <mike.tutkow...@netapp.com>
wrote:

> I am personally good with this venue and what it provides us. The dates
> look good, as well.
>
> On 3/13/18, 3:01 AM, "Giles Sirett" <giles.sir...@shapeblue.com> wrote:
>
> All
> I've been speaking with Rich Bowen about the feasibility of holding
> another Cloudstack Collaboration Conference in conjunction with Apachecon
>
> https://www.apachecon.com/acna18/schedule.html
> Apachecon is 24-27 September, Montreal
>
>
> Rich has said that we can have a room for Monday 24th  + one other day
> (I'm, hoping that would be Tuesday) , so CCC could be 24-25 September
>
> We could probably squeeze in 20 talks across the 2 days and would look
> to bolt on a hackathon at the end on Wednesday 26th (if Apachecon isn't
> able to accommodate the hackathon, we do know a friendly company in
> Montreal who *may* be able to host that)
>
> WE NEED TO MOVE QUICKLY: The CFP for apachecon is already open and
> closes March 30
> So, I'd like to get a broad feeling here of support to do this
>
>
> Theres not much needed to make this happen:
>
>   1.  Confirm with Rich that we want to do this
>   2.  Get http://cloudstackcollab.org/ updated - volunteers needed
>   3.  Point our community at the exisiting CFP  - and then help on the
> submissions process - volunteers needed
>   4.  Promote, etc
>
>
> Kind regards
> Giles
>
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
>
>

Re: Cloudstack metrics, usage collection and reporting?

[Will Stevens]

Ya, we have done some of our own instrumentation, but it has been more
'around' CloudStack than integrating directly into it (so far).  That said,
I think PLD has plans to start working on some initiatives inside ACS, but
I will let him speak to that.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Tue, Mar 20, 2018 at 2:11 PM, Nux! <n...@li.nux.ro> wrote:

> That sounds cool, haven't heard about this project.
>
> My first thought was whether we can input cloud usage data into
> elasticsearch or something like this, seems close enough.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Will Stevens" <wstev...@cloudops.com>
> > To: "dev" <dev@cloudstack.apache.org>, "Pierre-Luc Dion" <
> pd...@cloudops.com>
> > Cc: "users" <us...@cloudstack.apache.org>
> > Sent: Tuesday, 20 March, 2018 10:35:48
> > Subject: Re: Cloudstack metrics, usage collection and reporting?
>
> > PLD, this is a thread you will likely be interested in. I know you have
> > done a lot with OpenTSDB and are looking at adding metrics to the VR.
> >
> > On Mar 20, 2018 6:22 AM, "Nux!" <n...@li.nux.ro> wrote:
> >
> >> Prometheus and the ACS plugin are quite cool, I could see them being
> quite
> >> handy, thanks to whoever built it! :-)
> >>
> >> Has anyone had a go at putting cloud usage data into some of these new
> >> trendy shiny toys? I'd be most interested in network/traffic stats.
> >>
> >> Regards,
> >> Lucian
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> - Original Message -
> >> > From: "Paul Angus" <paul.an...@shapeblue.com>
> >> > To: "users" <us...@cloudstack.apache.org>, "dev" <
> >> dev@cloudstack.apache.org>
> >> > Sent: Thursday, 8 March, 2018 14:56:25
> >> > Subject: RE: Cloudstack metrics, usage collection and reporting?
> >>
> >> > 
> >> >
> >> >
> >> > Kind regards,
> >> >
> >> > Paul Angus
> >> >
> >> > paul.an...@shapeblue.com
> >> > www.shapeblue.com
> >> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> >> > @shapeblue
> >> >
> >> >
> >> >
> >> >
> >> > -Original Message-
> >> > From: Nux! <n...@li.nux.ro>
> >> > Sent: 08 March 2018 14:52
> >> > To: dev <dev@cloudstack.apache.org>
> >> > Cc: users <us...@cloudstack.apache.org>
> >> > Subject: Re: Cloudstack metrics, usage collection and reporting?
> >> >
> >> > Thanks!
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
> >> >
> >> > - Original Message -
> >> >> From: "Paul Angus" <paul.an...@shapeblue.com>
> >> >> To: "users" <us...@cloudstack.apache.org>
> >> >> Cc: "dev" <dev@cloudstack.apache.org>
> >> >> Sent: Thursday, 8 March, 2018 14:36:10
> >> >> Subject: RE: Cloudstack metrics, usage collection and reporting?
> >> >
> >> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> CloudStack+Metr
> >> >> ics+Exporter+for+Prometheus
> >> >>
> >> >>
> >> >> Kind regards,
> >> >>
> >> >> Paul Angus
> >> >>
> >> >> paul.an...@shapeblue.com
> >> >> www.shapeblue.com
> >> >> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> -Original Message-
> >> >> From: Nux! <n...@li.nux.ro>
> >> >> Sent: 08 March 2018 14:23
> >> >> To: users <us...@cloudstack.apache.org>
> >> >> Cc: dev <dev@cloudstack.apache.org>
> >> >> Subject: Cloudstack metrics, usage collection and reporting?
> >> >>
> >> >> Hi folks,
> >> >>
> >> >> I was looking at the state of metrics, usage stats of Cloudstack and
> >> >> integration in various tools, for monitoring, billing and so on.
> Nothing
> >> >> exciting came up.
> >> >> Is anyone doing or heard of interesting stuff with this? Maybe some
> >> >> Prometheus, Elasticsearch, Grafana or anything else?
> >> >>
> >> >>
> >> >> --
> >> >> Sent from the Delta quadrant using Borg technology!
> >> >>
> >> >> Nux!
> >> > > www.nux.ro
>

Re: Cloudstack metrics, usage collection and reporting?

[Will Stevens]

PLD, this is a thread you will likely be interested in. I know you have
done a lot with OpenTSDB and are looking at adding metrics to the VR.

On Mar 20, 2018 6:22 AM, "Nux!"  wrote:

> Prometheus and the ACS plugin are quite cool, I could see them being quite
> handy, thanks to whoever built it! :-)
>
> Has anyone had a go at putting cloud usage data into some of these new
> trendy shiny toys? I'd be most interested in network/traffic stats.
>
> Regards,
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Paul Angus" 
> > To: "users" , "dev" <
> dev@cloudstack.apache.org>
> > Sent: Thursday, 8 March, 2018 14:56:25
> > Subject: RE: Cloudstack metrics, usage collection and reporting?
>
> > 
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Nux! 
> > Sent: 08 March 2018 14:52
> > To: dev 
> > Cc: users 
> > Subject: Re: Cloudstack metrics, usage collection and reporting?
> >
> > Thanks!
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "Paul Angus" 
> >> To: "users" 
> >> Cc: "dev" 
> >> Sent: Thursday, 8 March, 2018 14:36:10
> >> Subject: RE: Cloudstack metrics, usage collection and reporting?
> >
> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Metr
> >> ics+Exporter+for+Prometheus
> >>
> >>
> >> Kind regards,
> >>
> >> Paul Angus
> >>
> >> paul.an...@shapeblue.com
> >> www.shapeblue.com
> >> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: Nux! 
> >> Sent: 08 March 2018 14:23
> >> To: users 
> >> Cc: dev 
> >> Subject: Cloudstack metrics, usage collection and reporting?
> >>
> >> Hi folks,
> >>
> >> I was looking at the state of metrics, usage stats of Cloudstack and
> >> integration in various tools, for monitoring, billing and so on. Nothing
> >> exciting came up.
> >> Is anyone doing or heard of interesting stuff with this? Maybe some
> >> Prometheus, Elasticsearch, Grafana or anything else?
> >>
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> > > www.nux.ro
>

Re: [DISCUSS] Relax strict requirement of JIRA ID for PRs

[Will Stevens]

Ron, for this I think we would be using Github Issues if we were not using
Jira.  Essentially all of the project information would be found in the
same place rather than the user having to discover all the different
systems that we use to track things and then try to make sense of it.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Wed, Mar 14, 2018 at 10:04 AM, Ron Wheeler <
rwhee...@artifact-software.com> wrote:

> I am not a Cloudstack developer and generally have no interest in PRs.
> If I have a problem, I want to search the Jira
>  - What was the symptom  - is it related to the problem that I am having -
> may not be exactly the same but might be related
>  - How was it reproduced - is this related to what I am trying to do - can
> I change my configuration decisions to avoid the issue
>  - What remedies were considered - could any of these have side effects
> that could account for my issue
>  - Why was the specific fix chosen - is my problem an edge case that was
> created or ignored by this decision
>  - Is there any discussion that could help me decide if my problem is
> related.
>  - Is there any info in the discussion that educates me to a point where I
> know what tests to run to refine my understanding my issue.
>  - What are the side-effects of the fix.
>  - Was it back ported
>  - What issues were discovered during backporting
>
> I am not sure that a PR will be much use to a sysadmin if the issue is
> non-trivial.
> If we ask people creating PRs to add all the things that a sysadmin
> requires, PRs may get too difficult to make.
>
> OTOH, I agree with Paul that PRs without Jira issues for doc updates and
> corrections that do *not affect functionality* would not make life too
> difficult and might encourage people to fix doc problems, clean code and
> update libraries.
>
> Ron
>
>
> On 14/03/2018 7:25 AM, Paul Angus wrote:
>
>> Oh boy! Where to start
>>
>> Ok, so wrt Rohit's original point, I'm a +1 for doc updates and very
>> trivial stuff a GOOD & COMPLETE title and summary in a PR probably suffices.
>>
>> Wrt Jira, for keeping track of *un*implemented changes and *un*fixed bugs
>> - I think that it (or something similar) is a must.  Which shouldn't leave
>> much to be honest.  As some point a person has decided to make a code
>> change or has found a bug, right then the 'thing', by definition, falls
>> into one of the above categories.
>>
>>
>>
>> Kind regards,
>>
>> Paul Angus
>>
>> paul.an...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>>
>>
>> -Original Message-
>> From: Daan Hoogland <daan.hoogl...@gmail.com>
>> Sent: 14 March 2018 10:05
>> To: dev <dev@cloudstack.apache.org>
>> Subject: Re: [DISCUSS] Relax strict requirement of JIRA ID for PRs
>>
>> Let me add to the below that I do think a ticketing system is a big help
>> for keeping track of *un*implemented changes and *un*fixed bugs.
>>
>> On Wed, Mar 14, 2018 at 11:04 AM, Daan Hoogland <daan.hoogl...@gmail.com>
>> wrote:
>>
>> Boris, I hate to be strongly opinionated but I have to violently
>>> disagree with you on some things here;
>>>
>>> On Wed, Mar 14, 2018 at 9:48 AM, Boris Stoyanov <
>>> boris.stoya...@shapeblue.com> wrote:
>>>
>>> Hi all,
>>>>
>>>> I do understand your point as developers if you want to fix something
>>>> just open the PR and not deal with any extra details like JIRA
>>>> tickets and etc, but I must say that JIRA tickets are quite often
>>>> looked up from users as they experience an issue.
>>>>
>>> ​It is not more or less effort for users to look up github PRs than
>>> Jira tickets. They still need to be clever about search terms and
>>> still might miss out.
>>> ​
>>>
>>>
>>> Let’s say we’ve fixed an annoying UI bug in master and there’s no
>>>> ticket for it in JIRA. As a user, if you try to search for this
>>>> particular issue where would you go? In JIRA or GitHub? How would you
>>>> know which release to pickup if you’re just an infrastructure guy and
>>>> not following Github.
>>>>
>>>> ​What is following here and why not Github but Jira.​ ​
>>>
>>>
>>> Tracking every change with such tool is proven good practice in SDLC,
>>>>
>>> ​No it is not. Absolutely not. That is what we have revision control
>>> systems for. Your good pra

Re: [DISCUSS] Relax strict requirement of JIRA ID for PRs

[Will Stevens]

To add another $0.02 to this conversation, beyond what I posted above.

Ideally, in my humble opinion, we would use Github Issues for issues that
do not currently have code associated with it.  Jira is currently being
used for this and it is useful for users to be able to flag bugs without
knowing how to solve them.  I believe this would require that issues be
turn on for the repo and the details of the issue be pushed to one of our
apache mailing lists.

One of the reasons why Jira has remained in play and we have not gone with
Github Issues in the past was due to security related issues.  I don't
believe we have the ability in Github to have private issues, which I
believe use use in Jira to handle security/CVE related issues.  This is
something we may have to solve for if we do leverage Github Issues, but I
will lets someone closer to how that all goes down comment and confirm or
deny this.

If we could use Github Issues and Github PRs as the only location for
issues and development, I think that would make contribution more
approachable and easier to convey to users.

Those are my additional thoughts...

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Tue, Mar 13, 2018 at 10:11 AM, Syed Ahmed <sah...@cloudops.com> wrote:

> I agree with the relaxation as Rohit pointed out. At this point we should
> ask if Jira is really needed. Most people here I believe agree that it is
> not. The only reason we have Jira is to track releases. This could easily
> be replicated in GitHub as I see that GitHub is the place where we all
> collaborate. I would be completely in if we use GitHub issues and like it
> with Jira as we do with our PRs.
>
>
> On Tue, Mar 13, 2018 at 10:03 AM Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > I was checking and for some reason ACS does not have an issue tab (
> > https://github.com/apache/cloudstack/issues). It might be some
> > configuration in the repository.
> >
> > On Tue, Mar 13, 2018 at 10:54 AM, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > What do you mean by issue? PR or issue (Github issue)?
> > >
> > > On Tue, Mar 13, 2018 at 10:53 AM, Daan Hoogland <
> daan.hoogl...@gmail.com
> > >
> > > wrote:
> > >
> > >> right, also when an issue is created?
> > >>
> > >>
> > >> On Tue, Mar 13, 2018 at 2:50 PM, Rafael Weingärtner <
> > >> rafaelweingart...@gmail.com> wrote:
> > >>
> > >> > We already have. All messages on ACS' GH go to commits@c.a.o
> > >> >
> > >> > On Tue, Mar 13, 2018 at 10:49 AM, Daan Hoogland <
> > >> daan.hoogl...@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > Ok, one issue there is Apache foundation rules. If we copy every
> > thing
> > >> > into
> > >> > > jira or the mail list we are fine, where ever we have our
> > discussions.
> > >> > The
> > >> > > only thing is that we need a Apache hosted record. (as in not
> > github)
> > >> > >
> > >> > > On Tue, Mar 13, 2018 at 2:09 PM, Rafael Weingärtner <
> > >> > > rafaelweingart...@gmail.com> wrote:
> > >> > >
> > >> > > > I prefer the workflow in Github as you guy, but to be fair with
> > Jira
> > >> > > ticket
> > >> > > > system I mentioned it.
> > >> > > >
> > >> > > > @Marc, yes Jira can facilitate a lot the management. However, we
> > do
> > >> not
> > >> > > use
> > >> > > > it fully. In our workflow, there is no planning/roadmap for the
> > next
> > >> > > > release per se. Things seem to work in an ad-hoc fashion. On the
> > >> other
> > >> > > > hand, when you need to break down milestones into
> > >> issues/tickets/tasks
> > >> > > and
> > >> > > > then divide them into sprints, and manage a team of developers,
> > the
> > >> > > > oversight provided by Jira system is very good; specially, when
> > >> issues
> > >> > > > start to take more than a single sprint to finish.
> > >> > > >
> > >> > > > On Tue, Mar 13, 2018 at 9:44 AM, Marc-Aurèle Brothier <
> > >> > ma...@exoscale.ch
> > >> > > >
> > >> > > > wrote:
> > >> > > >
> > >> > > > > @rafael, y

Re: [DISCUSS] Relax strict requirement of JIRA ID for PRs

[Will Stevens]

I am +1 to relaxing the requirement of Jira ticket.

Rafael, what do you mean when you say "Jira tickets are used to register
changes"?

I think ever since 4.9 the actual PRs included in the code are the source
of truth for the changes in the actual code (at least from a release notes
perspective).  This is why the release notes can show changes that only
have PRs and no Jira ticket.  At least my release notes generator is built
that way.  I think Rohit has built a similar release notes generator, so I
can't speak to his version...

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Tue, Mar 13, 2018 at 6:42 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Marc, yes Jira tickets are used to register changes. However, what Rohit
> and others (including me) are noticing is that there are certain types of
> changes (minor/bureaucracy) that do not require Jira tickets. The issue is
> the wording “change”. What consist of a change that is worth mentioning in
> the release notes? Everything we do in a branch is a change towards a
> release, but not everything is useful for operators/administrators to see.
>
> I would say that to fix bugs, introduce new features, extend existing
> features, introduce a major change in the code such as that standard maven
> thing that you did, they all required Jira tickets to track the discussion
> and facilitate the management. On the other side of the spectrum, we have
> things such as removing dead/unused code, opening a new version (creating
> the upgrade path that we still use for the DB), fix a description in an API
> method, and so on. Moreover, the excessive use of Jira tickets leads to
> hundreds of Jira tickets that we do not know that status of. We have quite
> a big number of tickets opened that could be closed. This has been worse;
> we are improving as time goes by.
>
> I would say that to make this more transparent to others (especially
> newcomers), we need to discuss it, then write it down to make it
> transparent the way we are working.
>
> On Tue, Mar 13, 2018 at 6:59 AM, Marc-Aurèle Brothier <ma...@exoscale.ch>
> wrote:
>
> > That's a good idea, because people are more and more used to only create
> PR
> > on github, and it would be helpful to be more explanatory on the way we
> > work to push changes. I still think we should encourage the use of the
> > github milestone as Rohit did with the 4.11.0 (
> > https://github.com/apache/cloudstack/milestone/3?closed=1) to list the
> > changes in the release notes with the help of the labels to tag the PRs
> > instead of relying on the jira ticket (it requires to have another
> login).
> >
> > As far as I can remember, the JIRA tickets are used to list the changes
> of
> > a release, but nothing else. Or am I missing something?
> >
> > Marc-Aurèle
> >
> > On Tue, Mar 13, 2018 at 9:57 AM, Rohit Yadav <rohit.ya...@shapeblue.com>
> > wrote:
> >
> > > All,
> > >
> > >
> > > To make it easier for people to contribute changes and encourage
> > > PR/contributions, should we relax the requirement of a JIRA ticket for
> > pull
> > > requests that solve trivial/minor issues such as doc bugs, build fixes
> > etc?
> > > A JIRA ticket may still be necessary for new features and non-trivial
> > > bugfixes or changes.
> > >
> > >
> > > Another alternative could be to introduce a CONTRIBUTING.md [1] that
> > > explains the list of expected things to contributors when they send a
> PR
> > > (for example, a jira id, links to fs or other resources, a short
> summary
> > > and long description, test results etc).
> > >
> > >
> > > Thoughts?
> > >
> > >
> > > [1] https://help.github.com/articles/setting-guidelines-
> > > for-repository-contributors/
> > >
> > >
> > > - Rohit
> > >
> > > <https://cloudstack.apache.org>
> > >
> > >
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: Releases in Progress

[Will Stevens]

My point was simply that if it has good ranking already, we should update
the page so we can put relevant information there so it can be easily
found.  Just trying to leverage it in our favor is all.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Mon, Feb 5, 2018 at 10:34 PM, Ron Wheeler <rwhee...@artifact-software.com
> wrote:

> SEO ranking is great but putting up stuff from 3 or 4 releases in the past
> blows away all of the SEO benefit when someone actually goes to the page.
> The reader is left with the impression that the product is not actively
> supported (actively developed but not supported)
>
> I am not sure that SEO raking makes any difference when the number of
> alternative search results is so small.
> How many "products" will rank ahead of Cloudstack for virtualization
> orchestration?
>
> Is there a list of search keywords for which we want to get a high ranking?
> Who are the competitors and what keywords should they win?
>
> Ron
>
>
>
> On 05/02/2018 4:13 PM, Will Stevens wrote:
>
>> As a project, especially around the topic of 'releases', I assume we
>> should
>> leverage any SEO placement we can use.  I don't have specific content I
>> think we should put there, but if it is well placed, it would make sense
>> that we put some detail on the page.  We don't have to, but I figured I
>> would mention it.
>>
>> *Will Stevens*
>> Chief Technology Officer
>> c 514.826.0190
>>
>> <https://goo.gl/NYZ8KK>
>>
>> On Mon, Feb 5, 2018 at 4:07 PM, Daan Hoogland <daan.hoogl...@gmail.com>
>> wrote:
>>
>> no one had made use of it since the RM for 4.4 (no who was that again) We
>>> can undelete if you wish. I copied the only worthwhile page to the HOWTO
>>> articles.
>>>
>>> On Mon, Feb 5, 2018 at 10:02 PM, Will Stevens <wstev...@cloudops.com>
>>> wrote:
>>>
>>> Is there a reason we deleted it and didn't just update it?  It would have
>>>> been good to take advantage of the SEO that page already had working for
>>>>
>>> us
>>>
>>>> and just update the content to represent the latest details.  No?
>>>>
>>>> *Will Stevens*
>>>> Chief Technology Officer
>>>> c 514.826.0190
>>>>
>>>> <https://goo.gl/NYZ8KK>
>>>>
>>>> On Mon, Feb 5, 2018 at 4:00 PM, Daan Hoogland <daan.hoogl...@gmail.com>
>>>> wrote:
>>>>
>>>> deleted
>>>>>
>>>>> On Fri, Feb 2, 2018 at 2:05 PM, Ron Wheeler
>>>>>
>>>> <rwheeler@artifact-software.
>>>
>>>> com>
>>>>> wrote:
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Relea
>>>>>> ses+in+Progress is old and needs to be update to talk about ACS 4.10,
>>>>>> 4.11 and 4.12.
>>>>>>
>>>>>> Ron
>>>>>>
>>>>>> --
>>>>>> Ron Wheeler
>>>>>> President
>>>>>> Artifact Software Inc
>>>>>> email: rwhee...@artifact-software.com
>>>>>> skype: ronaldmwheeler
>>>>>> phone: 866-970-2435, ext 102
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> Daan
>>>>>
>>>>>
>>>
>>> --
>>> Daan
>>>
>>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>

Re: Releases in Progress

[Will Stevens]

Search Engine Optimization.  Basically, placement of the page in google
searches...

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Mon, Feb 5, 2018 at 4:18 PM, Daan Hoogland <daan.hoogl...@gmail.com>
wrote:

> I read over that acronym, and "
> What does *SEO* stand for?
>
> Your abbreviation search returned 39 meanings
> ", so can you explain Steve?
>
> On Mon, Feb 5, 2018 at 10:13 PM, Will Stevens <wstev...@cloudops.com>
> wrote:
>
> > As a project, especially around the topic of 'releases', I assume we
> should
> > leverage any SEO placement we can use.  I don't have specific content I
> > think we should put there, but if it is well placed, it would make sense
> > that we put some detail on the page.  We don't have to, but I figured I
> > would mention it.
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > <https://goo.gl/NYZ8KK>
> >
> > On Mon, Feb 5, 2018 at 4:07 PM, Daan Hoogland <daan.hoogl...@gmail.com>
> > wrote:
> >
> > > no one had made use of it since the RM for 4.4 (no who was that again)
> We
> > > can undelete if you wish. I copied the only worthwhile page to the
> HOWTO
> > > articles.
> > >
> > > On Mon, Feb 5, 2018 at 10:02 PM, Will Stevens <wstev...@cloudops.com>
> > > wrote:
> > >
> > > > Is there a reason we deleted it and didn't just update it?  It would
> > have
> > > > been good to take advantage of the SEO that page already had working
> > for
> > > us
> > > > and just update the content to represent the latest details.  No?
> > > >
> > > > *Will Stevens*
> > > > Chief Technology Officer
> > > > c 514.826.0190
> > > >
> > > > <https://goo.gl/NYZ8KK>
> > > >
> > > > On Mon, Feb 5, 2018 at 4:00 PM, Daan Hoogland <
> daan.hoogl...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > deleted
> > > > >
> > > > > On Fri, Feb 2, 2018 at 2:05 PM, Ron Wheeler
> > > <rwheeler@artifact-software.
> > > > > com>
> > > > > wrote:
> > > > >
> > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Relea
> > > > > > ses+in+Progress is old and needs to be update to talk about ACS
> > 4.10,
> > > > > > 4.11 and 4.12.
> > > > > >
> > > > > > Ron
> > > > > >
> > > > > > --
> > > > > > Ron Wheeler
> > > > > > President
> > > > > > Artifact Software Inc
> > > > > > email: rwhee...@artifact-software.com
> > > > > > skype: ronaldmwheeler
> > > > > > phone: 866-970-2435, ext 102
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Daan
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Daan
> > >
> >
>
>
>
> --
> Daan
>

Re: Releases in Progress

[Will Stevens]

As a project, especially around the topic of 'releases', I assume we should
leverage any SEO placement we can use.  I don't have specific content I
think we should put there, but if it is well placed, it would make sense
that we put some detail on the page.  We don't have to, but I figured I
would mention it.

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Mon, Feb 5, 2018 at 4:07 PM, Daan Hoogland <daan.hoogl...@gmail.com>
wrote:

> no one had made use of it since the RM for 4.4 (no who was that again) We
> can undelete if you wish. I copied the only worthwhile page to the HOWTO
> articles.
>
> On Mon, Feb 5, 2018 at 10:02 PM, Will Stevens <wstev...@cloudops.com>
> wrote:
>
> > Is there a reason we deleted it and didn't just update it?  It would have
> > been good to take advantage of the SEO that page already had working for
> us
> > and just update the content to represent the latest details.  No?
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > <https://goo.gl/NYZ8KK>
> >
> > On Mon, Feb 5, 2018 at 4:00 PM, Daan Hoogland <daan.hoogl...@gmail.com>
> > wrote:
> >
> > > deleted
> > >
> > > On Fri, Feb 2, 2018 at 2:05 PM, Ron Wheeler
> <rwheeler@artifact-software.
> > > com>
> > > wrote:
> > >
> > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Relea
> > > > ses+in+Progress is old and needs to be update to talk about ACS 4.10,
> > > > 4.11 and 4.12.
> > > >
> > > > Ron
> > > >
> > > > --
> > > > Ron Wheeler
> > > > President
> > > > Artifact Software Inc
> > > > email: rwhee...@artifact-software.com
> > > > skype: ronaldmwheeler
> > > > phone: 866-970-2435, ext 102
> > > >
> > > >
> > >
> > >
> > > --
> > > Daan
> > >
> >
>
>
>
> --
> Daan
>

Re: Releases in Progress

[Will Stevens]

Is there a reason we deleted it and didn't just update it?  It would have
been good to take advantage of the SEO that page already had working for us
and just update the content to represent the latest details.  No?

*Will Stevens*
Chief Technology Officer
c 514.826.0190

<https://goo.gl/NYZ8KK>

On Mon, Feb 5, 2018 at 4:00 PM, Daan Hoogland <daan.hoogl...@gmail.com>
wrote:

> deleted
>
> On Fri, Feb 2, 2018 at 2:05 PM, Ron Wheeler <rwheeler@artifact-software.
> com>
> wrote:
>
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Relea
> > ses+in+Progress is old and needs to be update to talk about ACS 4.10,
> > 4.11 and 4.12.
> >
> > Ron
> >
> > --
> > Ron Wheeler
> > President
> > Artifact Software Inc
> > email: rwhee...@artifact-software.com
> > skype: ronaldmwheeler
> > phone: 866-970-2435, ext 102
> >
> >
>
>
> --
> Daan
>

Re: [DISCUSS] new way of github working

[Will Stevens]

If the new approach is adopted, we will likely have to change the
functionality of the 'tools' here:
https://github.com/apache/cloudstack/tree/master/tools/git

Especially 'git-pr' creates merges with the "would be deprecated" style, so
we will probably want to adapt our tracked tooling to conform with any new
styles we adopt.

Cheers,

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Jan 15, 2018 at 3:06 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Daan,
>
> Now that master is open for merges again, can we get a feedback here? It
> might be interesting to find a consensus and a standardize way of working
> for everybody before we start merging things in master again …
>
>
>
> On Mon, Jan 8, 2018 at 8:40 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > This might be my lack of expertise in Git (Github). I like the merge
> > commits (when merging a PR) because I can easily find the date when
> > something has been introduced to the code base. Of course, this can also
> be
> > achieved through Jira tickets and Github PRs history. This means I would
> > not mind adopting the merge and squash option on Github.
> >
> > On the other hand, regarding the second issue, I prefer the philosophy of
> > single commit PRs; otherwise, it feels pretty hard to track what was
> > introduced by a PR then. I recall seeing PRs with 100+ commits laying
> > around, and I confess that I cannot find myself in the middle of that
> > mayhem..
> >
> > Daan, could you provide more insights on the benefits of having a commit
> > per change in a PR?
> >
> > On Mon, Jan 8, 2018 at 7:30 PM, Daan Hoogland <
> daan.hoogl...@shapeblue.com
> > > wrote:
> >
> >> Marc-Aurèle and Rafael, I mean both. I know we used to require the
> first,
> >> to create the release notes in a concise way and we used to ban the
> other
> >> because it leads to unnavigable revision trees. But now that squash and
> >> merge is a functionality of github one might argue that it doesn’t
> matter
> >> anymore. Personally, I am against squashing persé, in any case. I am not
> >> the law (other than during some triathlons) so we jointly might decide
> >> differently.
> >>
> >> On 08/01/2018, 16:50, "Nicolas Vazquez" <nicolas.vazq...@shapeblue.com>
> >> wrote:
> >>
> >> The same as Rafael described. If it is the second case I would
> prefer
> >> rebasing the target branch and push force instead of including merge
> >> commits in a PR
> >>
> >> Obtener Outlook para Android<https://aka.ms/ghei36>
> >>
> >> 
> >> From: williamstev...@gmail.com <williamstev...@gmail.com> on behalf
> >> of Will Stevens <wstev...@cloudops.com>
> >> Sent: Monday, January 8, 2018 11:34:42 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: [DISCUSS] new way of github working
> >>
> >> Just a note Daan.  If a PR is merged with the `git pr ` tool in
> >> our
> >> utilities folder, it will automatically include the merge commit.
> >> Figured
> >> I should mention that...
> >>
> >> *Will Stevens*
> >> CTO
> >>
> >> <https://goo.gl/NYZ8KK>
> >>
> >> On Mon, Jan 8, 2018 at 8:26 AM, Marc-Aurèle Brothier <
> >> ma...@exoscale.ch>
> >> wrote:
> >>
> >> > Same opinion as Rafael described.
> >> >
> >> > On Mon, Jan 8, 2018 at 11:30 AM, Rafael Weingärtner <
> >> > rafaelweingart...@gmail.com> wrote:
> >> >
> >> > > I did not fully understand what you meant.
> >> > >
> >> > > Are you talking about the merge commit that can be created when
> a
> >> PR is
> >> > > merged? Or, are you talking about a merge commit that is added
> to
> >> a PR
> >> > when
> >> > > a conflict is solved by its author(s)?
> >> > >
> >> > >
> >> > > I do not have problems with the first type of merge commits.
> >> However, I
> >> > > think we should not allow the second type to get into our code
> >> base.
> >> > >
> >> > > On Mon, Jan 8, 2018 at 7:45 AM, Daan Hoogland <
> >> daan.hoogl...@gmail.com>
> >> > > wrote:

Re: [PROPOSE] EOL for supported OSes & Hypervisors

[Will Stevens]

I like this initiative.  I think this would be valuable to set an
expectation around supportability.

Cheers,

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Thu, Jan 11, 2018 at 12:11 PM, Paul Angus <paul.an...@shapeblue.com>
wrote:

> I've cross-posted this as it ultimately effects users more than developers.
>
> I've created a wiki page with the EOL dates from the respective 'vendors'
> of our main supported hypervisors and mgmt. server OSes.
> I've taken End Of Life to be the end of 'mainstream' support i.e. the
> point at which updates to packages will no longer be available.  And part
> of the discussion should be whether this EOL date should be moved out to
> consider end of security patching instead.
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> WIP+-+UNOFFICIAL+-+PROPOSAL+-+EOL+Dates
>
> I would like to propose, that as part of the release notes for the
> forthcoming 4.11 release and as a general announcement, that we declare
> that:
>
>
>   *   For any OSes/Hypervisors that are already EOL - we will no longer
> test/support them from the first release after June 2018 (6 months from
> now). And they will be removed from codebase (mainly the database) in the
> first release after Sept 2018 (9 months from now).
>   *   We set End Of Support dates and Removal from Code dates for the
> remaining OSes/Hypervisors.  I propose that End Of Support should be the
> first release after EOL from the vendor, with code removal taking place in
> the first release which occurs after 6 months from 'vendor' EOL date.
>
> Thoughts please
>
>
> Kind regards,
>
> Paul Angus
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

RE: Release Notes

[Will Stevens]

Perfect. Thanks for confirming. 

On Jan 8, 2018 11:26 AM, "Paul Angus" <paul.an...@shapeblue.com> wrote:

Thanks Will, this works great!







Kind regards,



Paul Angus



paul.an...@shapeblue.com
www.shapeblue.com
@shapeblue




*From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com] *On
Behalf Of *Will Stevens
*Sent:* 03 January 2018 19:32
*To:* Paul Angus <paul.an...@shapeblue.com>
*Cc:* dev@cloudstack.apache.org
*Subject:* Re: Release Notes



Paul,

Please note that this tool only considers PR merges, so if a commit is made
directly against master, it will not show up in this list as it did not
have an associated PR.



Also, it may be worth noting that some PRs (like this one:
https://github.com/apache/cloudstack/pull/2211) are actually made up of
many different changes.  The different changes will all be associated with
that single PR.



One other thing.  I believe you are probably using the following (correctly
for now) as the branches:

"--branches":"4.9,4.10,master"

​However, when we do the real release notes, we will want to do it after
the 4.11 branch is cut and will want to run it with the following:

"--branches":"4.9,4.10,4.11"

​I hope that makes sense.  Let me know if you have any questions.



​Cheers,​


*Will Stevens*

CTO



<https://goo.gl/NYZ8KK>



On Wed, Jan 3, 2018 at 2:15 PM, Will Stevens <wstev...@cloudops.com> wrote:

​Hey Paul,

You can pull down the latest code and everything should be working now: ​
https://github.com/swill/generate_acs_rn



I updated the tool to handle PRs merged through Github since I was
originally only handling PRs which were merged through the `git pr `
utility tool we had as part of our old process.



Let me know if you have any questions or issues.  Thanks for pointing out
this issue...  :)



Cheers,


*Will Stevens*

CTO



<https://goo.gl/NYZ8KK>



On Wed, Jan 3, 2018 at 11:09 AM, Paul Angus <paul.an...@shapeblue.com>
wrote:

Thanks guys!







Kind regards,



Paul Angus



paul.an...@shapeblue.com
www.shapeblue.com
@shapeblue




*From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com] *On
Behalf Of *Will Stevens
*Sent:* 03 January 2018 16:01
*To:* dev@cloudstack.apache.org
*Cc:* Paul Angus <paul.an...@shapeblue.com>
*Subject:* Re: Release Notes



Thanks Rafael!



I am working on it now and will see if I can get a working version sorted
in the next hour or so.  The PR number is in the commit, but just not in
the format I was expecting.  It is at the end of the line in the format
(#.).



I will have something soon.


*Will Stevens*

CTO



<https://goo.gl/NYZ8KK>



On Wed, Jan 3, 2018 at 10:57 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

I believe people are "merging" without the merge commit now that we are
using the Gitbox experiment.
When merging (I think most people are using the button in Github) there is
an option to merge without creating a merge commit, and I think this is
what happening.

On Wed, Jan 3, 2018 at 1:55 PM, Will Stevens <wstev...@cloudops.com> wrote:

> Hey Paul,
> Unfortunately, it looks as though we have recently changed the way we are
> handling merging code.  Instead of merging the PRs through Github, we seem
> to be doing something else.  This means that we don't have the "Merge pull
> request #2359 from ..." lines on all the merges anymore.
>
> I will see if I can adapt the script to handle both the old and current
way
> we are merging the PRs.
>
> Cheers,
>
> *Will Stevens*
> CTO
>
> <https://goo.gl/NYZ8KK>

>
> On Wed, Jan 3, 2018 at 9:37 AM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
> > Hey there Will,
> >
> >
> >
> > Happy New Year to you!
> >
> >
> >
> > I seem to be getting a very truncated list.  I’m using
> > 9d2893d44a3c3a4829be0964cc991272c1d13e4d as the commit sha for the last
> > release. And github token is obviously working.
> >
> >
> >
> > Any ideas ?
> >
> >
> >
> >
> >
> > .. cssclass:: table-striped table-bordered table-hover
> >
> >
> >
> > +-+--++-
> > --+--+--
> > --+
> >
> > | Branches| Github   | Jira   | Type
> > | Priority | Description
|
> >
> > +=+==++=
> > ==+==+==
> > ==+
> >
&g

Re: [DISCUSS] new way of github working

[Will Stevens]

Just a note Daan.  If a PR is merged with the `git pr ` tool in our
utilities folder, it will automatically include the merge commit.  Figured
I should mention that...

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Jan 8, 2018 at 8:26 AM, Marc-Aurèle Brothier <ma...@exoscale.ch>
wrote:

> Same opinion as Rafael described.
>
> On Mon, Jan 8, 2018 at 11:30 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > I did not fully understand what you meant.
> >
> > Are you talking about the merge commit that can be created when a PR is
> > merged? Or, are you talking about a merge commit that is added to a PR
> when
> > a conflict is solved by its author(s)?
> >
> >
> > I do not have problems with the first type of merge commits. However, I
> > think we should not allow the second type to get into our code base.
> >
> > On Mon, Jan 8, 2018 at 7:45 AM, Daan Hoogland <daan.hoogl...@gmail.com>
> > wrote:
> >
> > > Devs,
> > >
> > > I see a lot of merge master to branch commits appearing on PRs. This is
> > > against prior (non-hard) agreements on how we work. It is getting to be
> > the
> > > daily practice so;
> > > How do we feel about
> > > 1. not using merge commits anymore?
> > > 2. merging back as a way of solving conflicts?
> > > and
> > > Do we need to make a policy of it or do we let it evolve, at the risk
> of
> > > having more hard to track feature/version matrices?
> > >
> > > --
> > > Daan
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>

Re: Release Notes

[Will Stevens]

Paul,
Please note that this tool only considers PR merges, so if a commit is made
directly against master, it will not show up in this list as it did not
have an associated PR.

Also, it may be worth noting that some PRs (like this one:
https://github.com/apache/cloudstack/pull/2211) are actually made up of
many different changes.  The different changes will all be associated with
that single PR.

One other thing.  I believe you are probably using the following (correctly
for now) as the branches:

"--branches":"4.9,4.10,master"

​However, when we do the real release notes, we will want to do it after
the 4.11 branch is cut and will want to run it with the following:

"--branches":"4.9,4.10,4.11"

​I hope that makes sense.  Let me know if you have any questions.

​Cheers,​

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Wed, Jan 3, 2018 at 2:15 PM, Will Stevens <wstev...@cloudops.com> wrote:

> ​Hey Paul,
> You can pull down the latest code and everything should be working now: ​
> https://github.com/swill/generate_acs_rn
>
> I updated the tool to handle PRs merged through Github since I was
> originally only handling PRs which were merged through the `git pr `
> utility tool we had as part of our old process.
>
> Let me know if you have any questions or issues.  Thanks for pointing out
> this issue...  :)
>
> Cheers,
>
> *Will Stevens*
> CTO
>
> <https://goo.gl/NYZ8KK>
>
> On Wed, Jan 3, 2018 at 11:09 AM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
>> Thanks guys!
>>
>>
>>
>>
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Paul Angus
>>
>>
>>
>> paul.an...@shapeblue.com
>> www.shapeblue.com
>> @shapeblue
>>
>>
>>
>>
>> *From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com] *On
>> Behalf Of *Will Stevens
>> *Sent:* 03 January 2018 16:01
>> *To:* dev@cloudstack.apache.org
>> *Cc:* Paul Angus <paul.an...@shapeblue.com>
>> *Subject:* Re: Release Notes
>>
>>
>>
>> Thanks Rafael!
>>
>>
>>
>> I am working on it now and will see if I can get a working version sorted
>> in the next hour or so.  The PR number is in the commit, but just not in
>> the format I was expecting.  It is at the end of the line in the format
>> (#.).
>>
>>
>>
>> I will have something soon.
>>
>>
>> *Will Stevens*
>>
>> CTO
>>
>>
>>
>> <https://goo.gl/NYZ8KK>
>>
>>
>>
>> On Wed, Jan 3, 2018 at 10:57 AM, Rafael Weingärtner <
>> rafaelweingart...@gmail.com> wrote:
>>
>> I believe people are "merging" without the merge commit now that we are
>> using the Gitbox experiment.
>> When merging (I think most people are using the button in Github) there is
>> an option to merge without creating a merge commit, and I think this is
>> what happening.
>>
>> On Wed, Jan 3, 2018 at 1:55 PM, Will Stevens <wstev...@cloudops.com>
>> wrote:
>>
>> > Hey Paul,
>> > Unfortunately, it looks as though we have recently changed the way we
>> are
>> > handling merging code.  Instead of merging the PRs through Github, we
>> seem
>> > to be doing something else.  This means that we don't have the "Merge
>> pull
>> > request #2359 from ..." lines on all the merges anymore.
>> >
>> > I will see if I can adapt the script to handle both the old and current
>> way
>> > we are merging the PRs.
>> >
>> > Cheers,
>> >
>> > *Will Stevens*
>> > CTO
>> >
>> > <https://goo.gl/NYZ8KK>
>>
>> >
>> > On Wed, Jan 3, 2018 at 9:37 AM, Paul Angus <paul.an...@shapeblue.com>
>> > wrote:
>> >
>> > > Hey there Will,
>> > >
>> > >
>> > >
>> > > Happy New Year to you!
>> > >
>> > >
>> > >
>> > > I seem to be getting a very truncated list.  I’m using
>> > > 9d2893d44a3c3a4829be0964cc991272c1d13e4d as the commit sha for the
>> last
>> > > release. And github token is obviously working.
>> > >
>> > >
>> > >
>> > > Any ideas ?
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > .. cssclass:: table-striped table-bordered table-hover
>> > >
>> > >
>> > >
>> > > +-+--+--

Re: Release Notes

[Will Stevens]

​Hey Paul,
You can pull down the latest code and everything should be working now: ​
https://github.com/swill/generate_acs_rn

I updated the tool to handle PRs merged through Github since I was
originally only handling PRs which were merged through the `git pr `
utility tool we had as part of our old process.

Let me know if you have any questions or issues.  Thanks for pointing out
this issue...  :)

Cheers,

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Wed, Jan 3, 2018 at 11:09 AM, Paul Angus <paul.an...@shapeblue.com>
wrote:

> Thanks guys!
>
>
>
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>
> *From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com] *On
> Behalf Of *Will Stevens
> *Sent:* 03 January 2018 16:01
> *To:* dev@cloudstack.apache.org
> *Cc:* Paul Angus <paul.an...@shapeblue.com>
> *Subject:* Re: Release Notes
>
>
>
> Thanks Rafael!
>
>
>
> I am working on it now and will see if I can get a working version sorted
> in the next hour or so.  The PR number is in the commit, but just not in
> the format I was expecting.  It is at the end of the line in the format
> (#.).
>
>
>
> I will have something soon.
>
>
> *Will Stevens*
>
> CTO
>
>
>
> <https://goo.gl/NYZ8KK>
>
>
>
> On Wed, Jan 3, 2018 at 10:57 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> I believe people are "merging" without the merge commit now that we are
> using the Gitbox experiment.
> When merging (I think most people are using the button in Github) there is
> an option to merge without creating a merge commit, and I think this is
> what happening.
>
> On Wed, Jan 3, 2018 at 1:55 PM, Will Stevens <wstev...@cloudops.com>
> wrote:
>
> > Hey Paul,
> > Unfortunately, it looks as though we have recently changed the way we are
> > handling merging code.  Instead of merging the PRs through Github, we
> seem
> > to be doing something else.  This means that we don't have the "Merge
> pull
> > request #2359 from ..." lines on all the merges anymore.
> >
> > I will see if I can adapt the script to handle both the old and current
> way
> > we are merging the PRs.
> >
> > Cheers,
> >
> > *Will Stevens*
> > CTO
> >
> > <https://goo.gl/NYZ8KK>
>
> >
> > On Wed, Jan 3, 2018 at 9:37 AM, Paul Angus <paul.an...@shapeblue.com>
> > wrote:
> >
> > > Hey there Will,
> > >
> > >
> > >
> > > Happy New Year to you!
> > >
> > >
> > >
> > > I seem to be getting a very truncated list.  I’m using
> > > 9d2893d44a3c3a4829be0964cc991272c1d13e4d as the commit sha for the
> last
> > > release. And github token is obviously working.
> > >
> > >
> > >
> > > Any ideas ?
> > >
> > >
> > >
> > >
> > >
> > > .. cssclass:: table-striped table-bordered table-hover
> > >
> > >
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | Branches| Github   | Jira   | Type
> > > | Priority | Description
>   |
> > >
> > > +=+==++=
> > > ==+==+==
> > > ==+
> > >
> > > | master  | `#2211`_ | CLOUDSTACK-10013_  | Bug
> > > | Major| Migrate to Debian9 systemvmtemplate
>   |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2359`_ ||
> > > |  | doc: replace virutal by virtual (typo)
>  |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2124`_ | CLOUDSTACK-9432_   | Bug
> > > | Critical | Dedicate Cluster to Domain always creates an affinity
>   |
> > >
> > > | |  ||
> > >  

Re: Release Notes

[Will Stevens]

Thanks Rafael!

I am working on it now and will see if I can get a working version sorted
in the next hour or so.  The PR number is in the commit, but just not in
the format I was expecting.  It is at the end of the line in the format
(#.).

I will have something soon.

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Wed, Jan 3, 2018 at 10:57 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> I believe people are "merging" without the merge commit now that we are
> using the Gitbox experiment.
> When merging (I think most people are using the button in Github) there is
> an option to merge without creating a merge commit, and I think this is
> what happening.
>
> On Wed, Jan 3, 2018 at 1:55 PM, Will Stevens <wstev...@cloudops.com>
> wrote:
>
> > Hey Paul,
> > Unfortunately, it looks as though we have recently changed the way we are
> > handling merging code.  Instead of merging the PRs through Github, we
> seem
> > to be doing something else.  This means that we don't have the "Merge
> pull
> > request #2359 from ..." lines on all the merges anymore.
> >
> > I will see if I can adapt the script to handle both the old and current
> way
> > we are merging the PRs.
> >
> > Cheers,
> >
> > *Will Stevens*
> > CTO
> >
> > <https://goo.gl/NYZ8KK>
> >
> > On Wed, Jan 3, 2018 at 9:37 AM, Paul Angus <paul.an...@shapeblue.com>
> > wrote:
> >
> > > Hey there Will,
> > >
> > >
> > >
> > > Happy New Year to you!
> > >
> > >
> > >
> > > I seem to be getting a very truncated list.  I’m using
> > > 9d2893d44a3c3a4829be0964cc991272c1d13e4d as the commit sha for the
> last
> > > release. And github token is obviously working.
> > >
> > >
> > >
> > > Any ideas ?
> > >
> > >
> > >
> > >
> > >
> > > .. cssclass:: table-striped table-bordered table-hover
> > >
> > >
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | Branches| Github   | Jira   | Type
> > > | Priority | Description
>   |
> > >
> > > +=+==++=
> > > ==+==+==
> > > ==+
> > >
> > > | master  | `#2211`_ | CLOUDSTACK-10013_  | Bug
> > > | Major| Migrate to Debian9 systemvmtemplate
>   |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2359`_ ||
> > > |  | doc: replace virutal by virtual (typo)
>  |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2124`_ | CLOUDSTACK-9432_   | Bug
> > > | Critical | Dedicate Cluster to Domain always creates an affinity
>   |
> > >
> > > | |  ||
> > >   |  | group owned by the root domain
> > > |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#1981`_ | CLOUDSTACK-9806_   | New Feature
> > > | Major| Nuage domain template selection per VPC
>   |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2005`_ | CLOUDSTACK-9450_   | Improvement
> > > | Major| Network Offering for VPC based on DB flag
>   |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2004`_ | CLOUDSTACK-9832_   | Improvement
> > > | Major  

Re: Release Notes

[Will Stevens]

Hey Paul,
Unfortunately, it looks as though we have recently changed the way we are
handling merging code.  Instead of merging the PRs through Github, we seem
to be doing something else.  This means that we don't have the "Merge pull
request #2359 from ..." lines on all the merges anymore.

I will see if I can adapt the script to handle both the old and current way
we are merging the PRs.

Cheers,

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Wed, Jan 3, 2018 at 9:37 AM, Paul Angus <paul.an...@shapeblue.com> wrote:

> Hey there Will,
>
>
>
> Happy New Year to you!
>
>
>
> I seem to be getting a very truncated list.  I’m using
> 9d2893d44a3c3a4829be0964cc991272c1d13e4d as the commit sha for the last
> release. And github token is obviously working.
>
>
>
> Any ideas ?
>
>
>
>
>
> .. cssclass:: table-striped table-bordered table-hover
>
>
>
> +-+--++-
> --+--+--
> --+
>
> | Branches| Github   | Jira   | Type
> | Priority | Description|
>
> +=+==++=
> ==+==+==
> ==+
>
> | master  | `#2211`_ | CLOUDSTACK-10013_  | Bug
> | Major| Migrate to Debian9 systemvmtemplate|
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2359`_ ||
> |  | doc: replace virutal by virtual (typo) |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2124`_ | CLOUDSTACK-9432_   | Bug
> | Critical | Dedicate Cluster to Domain always creates an affinity  |
>
> | |  ||
>   |  | group owned by the root domain
> |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#1981`_ | CLOUDSTACK-9806_   | New Feature
> | Major| Nuage domain template selection per VPC|
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2005`_ | CLOUDSTACK-9450_   | Improvement
> | Major| Network Offering for VPC based on DB flag  |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2004`_ | CLOUDSTACK-9832_   | Improvement
> | Major| Do not assign public IP NIC to the VPC VR when the VPC |
>
> | |  ||
> |  | offering does not contain VpcVirtualRouter as a SourceNat  |
>
> | |  ||
> |  | provider   |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2238`_ | CLOUDSTACK-10053_  | Improvement
> | Major| Performance improvement: Caching of external id's  |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2268`_ | CLOUDSTACK-10081_  | Bug
> | Major| CloudUtils getDevInfo function only checks for KVM |
>
> | |  ||
> |  | bridgePort and not OVS |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2054`_ | CLOUDSTACK-9886_   | Bug
> | Major| After restarting cloudstack-management , It takes time to  |
>
> | |  ||
> |

Re: Release Notes

[Will Stevens]

Hey Paul,
Let me know if you have any questions about the generation of the Fixed
Issues or the API Changes using my scripts.

Cheers,

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Fri, Dec 29, 2017 at 2:18 AM, Paul Angus <paul.an...@shapeblue.com>
wrote:

> Thanks Will!
>
>
>
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>
> *From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com] *On
> Behalf Of *Will Stevens
> *Sent:* 28 December 2017 23:35
> *To:* Paul Angus <paul.an...@shapeblue.com>
> *Cc:* dev@cloudstack.apache.org
> *Subject:* Re: Release Notes
>
>
>
> Hey Paul,
>
> Sorry, I don't think I have had a chance to get this fully integrated with
> an 'apache' or 'cloudstack' repo yet, but here is the tool I wrote for
> generating sections of the RN.
>
>
>
> https://github.com/swill/generate_acs_rn
>
>
>
> For the API changes, you will have to utilize the work that Pierre-Luc has
> done.
>
>
>
> I tried to make sure the README was solid, so please let me know if
> anything is not clear so I can improve the documentation.  I think I am
> still the only person who has used this set of tools (I did it for these
> sections of the 4.10 release as well).  I can do it again if you want, but
> it would be a good idea to get someone else's eyes on this work as well.
>
>
>
> Let me know if you have any questions.
>
>
>
> Cheers and happy holidays,
>
>
>
> *Will Stevens*
>
> CTO
>
>
>
> <https://goo.gl/NYZ8KK>
>
>
>
> On Thu, Dec 28, 2017 at 12:01 PM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
> Cheers – enjoy the snow!
>
>
>
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>
> *From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com] *On
> Behalf Of *Will Stevens
> *Sent:* 28 December 2017 15:43
> *To:* Paul Angus <paul.an...@shapeblue.com>
> *Cc:* dev@cloudstack.apache.org
> *Subject:* RE: Release Notes
>
>
>
> I am heading out to ski right now as I am on holiday. I will get you
> pointed in the right direction when I get back in.
>
>
>
> On Dec 28, 2017 7:31 AM, "Paul Angus" <paul.an...@shapeblue.com> wrote:
>
> Thanks Pierre-Luc  (Happy Christmas)
>
> Hey Will... how do you do about extracting the extra stuff from github?
>
> thanks
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 26 December 2017 16:00
> To: dev@cloudstack.apache.org
> Subject: Re: Release Notes
>
> The way I was doing RN and generating  fixed issues and known issues list,
> was by doing JIRA filters for each of them, then you use "./utils/jira.py"
> from cloudstack-docs-rn
> to generate a markdown formated list that you cut/paste in relevant RN
> page.  This require Jira issues to be updated on Open/close  state, also
> the Fix Version and Affected to be fully up to date. With recent use of
> Gitbhub, I'm not sure how Jira is up to date now.  Will did use something
> else to extract data from commit comments, but I don't know how he did it.
>
> Hope this help a little...
>
>
> Cheers,
>
>
>
>
> On Thu, Dec 21, 2017 at 12:38 PM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
> >
> > Hi guys I'm hoping to get a head start on release notes over Xmas. I
> > believe some guys have come up with a tool which gets human readable
> > what's new and known issues...
> >
> > Could someone point me in the right direction please.
> >
> > (And merry Christmas and a happy new year to everyone)
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> 4HSUK @shapeblue
> >
> >
> >
> >
>
>
>

Re: Release Notes

[Will Stevens]

Hey Paul,
Sorry, I don't think I have had a chance to get this fully integrated with
an 'apache' or 'cloudstack' repo yet, but here is the tool I wrote for
generating sections of the RN.

https://github.com/swill/generate_acs_rn

For the API changes, you will have to utilize the work that Pierre-Luc has
done.

I tried to make sure the README was solid, so please let me know if
anything is not clear so I can improve the documentation.  I think I am
still the only person who has used this set of tools (I did it for these
sections of the 4.10 release as well).  I can do it again if you want, but
it would be a good idea to get someone else's eyes on this work as well.

Let me know if you have any questions.

Cheers and happy holidays,

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Thu, Dec 28, 2017 at 12:01 PM, Paul Angus <paul.an...@shapeblue.com>
wrote:

> Cheers – enjoy the snow!
>
>
>
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>
> *From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com] *On
> Behalf Of *Will Stevens
> *Sent:* 28 December 2017 15:43
> *To:* Paul Angus <paul.an...@shapeblue.com>
> *Cc:* dev@cloudstack.apache.org
> *Subject:* RE: Release Notes
>
>
>
> I am heading out to ski right now as I am on holiday. I will get you
> pointed in the right direction when I get back in.
>
>
>
> On Dec 28, 2017 7:31 AM, "Paul Angus" <paul.an...@shapeblue.com> wrote:
>
> Thanks Pierre-Luc  (Happy Christmas)
>
> Hey Will... how do you do about extracting the extra stuff from github?
>
> thanks
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 26 December 2017 16:00
> To: dev@cloudstack.apache.org
> Subject: Re: Release Notes
>
> The way I was doing RN and generating  fixed issues and known issues list,
> was by doing JIRA filters for each of them, then you use "./utils/jira.py"
> from cloudstack-docs-rn
> to generate a markdown formated list that you cut/paste in relevant RN
> page.  This require Jira issues to be updated on Open/close  state, also
> the Fix Version and Affected to be fully up to date. With recent use of
> Gitbhub, I'm not sure how Jira is up to date now.  Will did use something
> else to extract data from commit comments, but I don't know how he did it.
>
> Hope this help a little...
>
>
> Cheers,
>
>
>
>
> On Thu, Dec 21, 2017 at 12:38 PM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
> >
> > Hi guys I'm hoping to get a head start on release notes over Xmas. I
> > believe some guys have come up with a tool which gets human readable
> > what's new and known issues...
> >
> > Could someone point me in the right direction please.
> >
> > (And merry Christmas and a happy new year to everyone)
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N=gmail=g>
> 4HSUK @shapeblue
> >
> >
> >
> >
>
>

RE: Release Notes

[Will Stevens]

I am heading out to ski right now as I am on holiday. I will get you
pointed in the right direction when I get back in.

On Dec 28, 2017 7:31 AM, "Paul Angus"  wrote:

> Thanks Pierre-Luc  (Happy Christmas)
>
> Hey Will... how do you do about extracting the extra stuff from github?
>
> thanks
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: 26 December 2017 16:00
> To: dev@cloudstack.apache.org
> Subject: Re: Release Notes
>
> The way I was doing RN and generating  fixed issues and known issues list,
> was by doing JIRA filters for each of them, then you use "./utils/jira.py"
> from cloudstack-docs-rn
> to generate a markdown formated list that you cut/paste in relevant RN
> page.  This require Jira issues to be updated on Open/close  state, also
> the Fix Version and Affected to be fully up to date. With recent use of
> Gitbhub, I'm not sure how Jira is up to date now.  Will did use something
> else to extract data from commit comments, but I don't know how he did it.
>
> Hope this help a little...
>
>
> Cheers,
>
>
>
>
> On Thu, Dec 21, 2017 at 12:38 PM, Paul Angus 
> wrote:
>
> >
> > Hi guys I'm hoping to get a head start on release notes over Xmas. I
> > believe some guys have come up with a tool which gets human readable
> > what's new and known issues...
> >
> > Could someone point me in the right direction please.
> >
> > (And merry Christmas and a happy new year to everyone)
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> >
> >
> >
> >
>

Re: [PROPOSE] RM for 4.11

[Will Stevens]

You have my support as RM Rohit. Thanks for stepping up.

Everything in this email looks pretty good.

Cheers,

Will

On Nov 29, 2017 5:15 AM, "Rohit Yadav"  wrote:

Hi All,

I’d like to put myself forward as release manager for 4.11. The 4.11
releases will be the next major version LTS release since 4.9 and will be
supported for 20 months per the LTS manifesto [2] until 1 July 2019.

Daan Hoogland and Paul Angus will assist during the process and all of us
will be the gatekeepers for reviewing/testing/merging the PRs, others will
be welcome to support as well.

As a community member, I will try to help get PRs reviewed, tested and
merged (as would everyone else I hope) but with an RM hat on I would like
to see if we can make that role less inherently life-consuming and put the
onus back on the community to get stuff done.

Here the plan:
1. As RM I put forward the freeze date of the 8th of January 2018, hoping
for community approval.
2. After the freeze date (8th Jan) until GA release, features will not be
allowed and fixes only as long as there are blocker issues outstanding.
Fixes for other issues will be individually judged on their merit and risk.
3. RM will triage/report critical and blocker bugs for 4.11 [4] and
encourage people to get them fixed.
4. RM will create RCs and start voting once blocker bugs are cleared and
baseline smoke test results are on par with previous 4.9.3.0/4.10.0.0 smoke
test results.
5. RM will allocate at least a week for branch stabilization and testing.
At the earliest, on 15th January, RM will put 4.11.0.0-rc1 for voting from
the 4.11 branch, and master will be open to accepting new features.
6. RM will repeat 3-5 as required. Voting/testing of -rc2, -rc3 and so on
will be created as required.
7. Once vote passes - RM will continue with the release procedures [1].

In conjunction with that, I also propose and put forward the date of 4.12
cut-off as 4 months [3] after GA release of 4.11 (so everyone knows when
the next one is coming hopefully giving peace of mind to those who have
features which would not make the proposed 4.11 cut off).

I’d like the community (including myself and colleagues) to:
- Up to 8th January, community members try to review, test and merge as
many fixes as possible, while super-diligent to not de-stabilize the master
branch.
- Engage with gatekeepers to get your PRs reviewed, tested and merged
(currently myself, Daan and Paul, others are welcome to engage as well). Do
not merge the PRs
- A pull request may be reverted where the author(s) are not responding and
authors may be asked to re-submit their changes after taking suitable
remedies.
- Find automated method to show (at a glance) statuses of PRs with respect
to:
  · Number of LGTMs
  · Smoke tests
  · Functional tests
  · Travis tests passing
  · Mergeability
- Perform a weekly run of a component-test matrix against the master branch
before Jan 8th cut off (based on current hypervisors including basic (KVM)
and advanced networking).
- Continue to fix broken tests.

Thoughts, feedback, comments?

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure
[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
[3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
[4] The current list of blocker and critical bugs currently stands as per
the following list:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%
20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%
22In%20Progress%22%2C%20Reopened)%20AND%20priority%
20in%20(Blocker%2C%20Critical)%20AND%20affectedVersion%20in%
20(4.10.0.0%2C%204.10.1.0%2C%204.11.0.0%2C%20Future)%
20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Regards,
Rohit Yadav

Re: CloudStack LTS EOL date?

[Will Stevens]

Paul, I thought a 'big mouth' was a prerequisite for the RM position.
Isn't that the only reason I was the 4.9 RM?  :P

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Wed, Nov 22, 2017 at 11:39 AM, Paul Angus <paul.an...@shapeblue.com>
wrote:

> HI All,
>
> The current LTS cycle is based on having an LTS release twice a year (at
> the time of design, ACS releases were coming out monthly).
>
> So, twice a year (nominally, January and July) we take the then current
> version of CloudStack, and declare that an LTS version, for which would we
> would then backport fixes for a period of up to 2 years.  Thereby giving
> end users a version of CloudStack which would receive bug fixes for an
> extended period.
>
> This year however, the current version in January was the same as the
> current version in July, therefore 4.9 became the 'July' LTS as well as
> January LTS and therefore 4.9 will be supported until summer 2019 (hence
> the 4.9.3 release)
>
> I and a number of my colleagues remain committed to continue to support
> 'LTS' releases in this fashion (there just wasn't anything really to
> 'announce' in July), which may be why people think that nothing is
> happening.
>
> With 2 LTS releases a year (6 months apart), 'next LTS +6 months' would
> only be 12 months from release.  Which I think is really too short a period
> for the majority of enterprises.  Although we haven't written it this way,
> the current scheme gives a EOL of 'next LTS + 18 months'.
>
> So, I'm in favour of leaving things as they are.   The wiki page looks
> like it needs updating to be clearer (I'm happy to do that)
>
>
> But I DO think that we should start a new thread asking for a 4.11 RM
> volunteer to get things going.   (I'm guessing y'all don't what my big
> mouth in that position).
>
>
> Kind regards,
>
> Paul Angus
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Ivan Kudryavtsev [mailto:kudryavtsev...@bw-sw.com]
> Sent: 21 November 2017 14:00
> To: dev@cloudstack.apache.org
> Subject: Re: CloudStack LTS EOL date?
>
> Hello, it sounds very reasonable. The more lifecycle information the
> better for adopters.
>
> 21 нояб. 2017 г. 8:56 ПП пользователь "Marc-Aurèle Brothier - Exoscale" <
> ma...@exoscale.ch> написал:
>
> > It makes more sense to me too.
> >
> >
> > On Tue, 2017-11-21 at 12:04 +0100, Rene Moser wrote:
> > > Hi all
> > >
> > > The current LTS release is 4.9 which is EOL in June 2018 according
> > > to https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
> > >
> > > AFAIK there are no works planed for a new LTS. The release pace has
> > > slown down (the high pace and leaving users behind fixes was the
> > > reason for the LTS).
> > >
> > > I am still pro LTS but in my opinion we should have defined the EOL
> > > in relation of the successor LTS release date: "The EOL of the
> > > current LTS is +6 months after the next LTS release."
> > >
> > > Small example:
> > >
> > > Current LTS 4.9
> > > Next LTS 4.1x release on 01.04. --> LTS 4.9 is 01.10.
> > >
> > > Does this make sense? Other suggestions?
> > >
> > > Regards
> > > René
> >
>

Re: 4.10 release announcement?

[Will Stevens]

In this case it is sphinx and not middleman, but I spent a lot of time on
the README in the past to make sure the contribution details are clear, so
if anything is not clear please highlight the details.

Cheers,

Will

On Mon, Aug 28, 2017 at 8:22 AM, Rohit Yadav <rohit.ya...@shapeblue.com>
wrote:

> Rajani,
>
>
> Yes middleman is used, kindly see the build/run scripts in the repository
> for details.
>
>
> - Rohit
> --
> *From:* Rajani Karuturi <raj...@apache.org>
> *Sent:* Sunday, August 20, 2017 6:47:14 AM
> *To:* Will Stevens
> *Cc:* Rohit Yadav; Wido den Hollander; dev@cloudstack.apache.org
> *Subject:* Re: 4.10 release announcement?
>
> Middleman is used only for website I think. For doc sites it's different.
>
> ~Rajani
>
> Sent from phone.
>
> On 18 Aug 2017 8:11 pm, "Will Stevens" <williamstev...@gmail.com> wrote:
>
> > The HTML is built using a build script in the repo locally by the person
> > who suggests a change. The build script actually uses middleman to
> generate
> > the html. The generated HTML is tracked in the pull requests so merges
> > result in updates to the published content.
> >
> > The readme should be up to date and the details should be clear, but I
> > have not looked in a little while.
> >
> > I am on vacation right now, but I can check the details when I am back.
> >
> > Cheers,
> >
> > Will
> >
> > On Aug 18, 2017 2:32 AM, "Rajani Karuturi" <raj...@apache.org> wrote:
> >
> > Hi Wido/Will,
> >
> > Do you know how the html is generated for readthedocs? Is that through
> any
> > jenkins job? I think if atleast release notes are ready, we can make an
> > annoucement.
> >
> >
> > ~ Rajani
> >
> > http://cloudplatform.accelerite.com/
> >
> >
> > On August 14, 2017 at 12:55 PM, Rajani Karuturi (raj...@apache.org)
> wrote:
> >
> >
> > I updated the downloads section of the website.
> >
> >
> > The following items are pending:
> >
> > apidocs needs to be added at http://cloudstack.apache.org/api.html
> >
> > install docs needs a 4.10 version at http://docs.cloudstack.apache.
> > org/projects/cloudstack-installation/en/4.10/
> >
> > admin docs needs a 4.10 version at http://docs.cloudstack.apache.
> > org/projects/cloudstack-administration/en/4.10/
> >
> > release notes html needs to be updated with already updated source at
> > http://docs.cloudstack.apache.org/projects/cloudstack-releas
> > e-notes/en/4.10/
> >
> >
> > uff.. we have lots of documentation. We should club them all to one repo
> > and one url.
> >
> >
> > Thanks,
> >
> > ~ Rajani
> >
> > http://cloudplatform.accelerite.com/
> >
> >
> > On August 14, 2017 at 11:37 AM, Rajani Karuturi (raj...@apache.org)
> wrote:
> >
> >
> > I merged the release notes PR[1]. Do we need to do something else for the
> > changes to reflect on the docs site[2]?
> >
> >
> > Downloads section of the website also needs to be updated.
> >
> >
> > I am sending out a draft announcement to marketing@
> >
> >
> > [1] https://github.com/apache/cloudstack-docs-rn/tree/4.10
> >
> > [2] http://docs.cloudstack.apache.org/projects/cloudstack-releas
> > e-notes/en/4.10/
> >
> >
> > Thanks,
> >
> > ~ Rajani
> >
> > http://cloudplatform.accelerite.com/
> >
> >
> > On August 12, 2017 at 1:25 AM, Rohit Yadav (rohit.ya...@shapeblue.com)
> > wrote:
> >
> >
> > Thanks Simon,
> >
> >
> > Overall, LGTM.
> >
> >
> > - Rohit
> >
> > *From:* Simon Weller <swel...@ena.com.INVALID>
> > *Sent:* Friday, August 11, 2017 7:56:52 PM
> > *To:* Rajani Karuturi; dev@cloudstack.apache.org
> > *Cc:* Wido den Hollander
> > *Subject:* Re: 4.10 release announcement?
>
> >
> > Thanks Rohit.
> >
> >
> >
> > i've modified the list based on that.
> >
> >
> > - IPV6 support for basic networking
> > - Virtio-Scsi disk controller support for KVM
> > - Ability to disable primary storage to secondary storage backups for
> > snapshots
> > - VMSnapshot (including memory) support for KVM on NFS
> > - RBD snapshot backups to secondary are now QCOW2 rather than raw to save
> > space
> > - Strongwan VPN Improvements
> > - Nuage VSP SDN Plugin: Shared networks support, Guest DNS support,
> > Source- and Static-nat to Under

Re: 4.10 release announcement?

[Will Stevens]

The HTML is built using a build script in the repo locally by the person
who suggests a change. The build script actually uses middleman to generate
the html. The generated HTML is tracked in the pull requests so merges
result in updates to the published content.

The readme should be up to date and the details should be clear, but I have
not looked in a little while.

I am on vacation right now, but I can check the details when I am back.

Cheers,

Will

On Aug 18, 2017 2:32 AM, "Rajani Karuturi"  wrote:

Hi Wido/Will,

Do you know how the html is generated for readthedocs? Is that through any
jenkins job? I think if atleast release notes are ready, we can make an
annoucement.


~ Rajani

http://cloudplatform.accelerite.com/


On August 14, 2017 at 12:55 PM, Rajani Karuturi (raj...@apache.org) wrote:


I updated the downloads section of the website.


The following items are pending:

apidocs needs to be added at http://cloudstack.apache.org/api.html

install docs needs a 4.10 version at http://docs.cloudstack.apache.
org/projects/cloudstack-installation/en/4.10/

admin docs needs a 4.10 version at http://docs.cloudstack.apache.
org/projects/cloudstack-administration/en/4.10/

release notes html needs to be updated with already updated source at
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.10/


uff.. we have lots of documentation. We should club them all to one repo
and one url.


Thanks,

~ Rajani

http://cloudplatform.accelerite.com/


On August 14, 2017 at 11:37 AM, Rajani Karuturi (raj...@apache.org) wrote:


I merged the release notes PR[1]. Do we need to do something else for the
changes to reflect on the docs site[2]?


Downloads section of the website also needs to be updated.


I am sending out a draft announcement to marketing@


[1] https://github.com/apache/cloudstack-docs-rn/tree/4.10

[2] http://docs.cloudstack.apache.org/projects/cloudstack-
release-notes/en/4.10/


Thanks,

~ Rajani

http://cloudplatform.accelerite.com/


On August 12, 2017 at 1:25 AM, Rohit Yadav (rohit.ya...@shapeblue.com)
wrote:


Thanks Simon,


Overall, LGTM.


- Rohit

*From:* Simon Weller 
*Sent:* Friday, August 11, 2017 7:56:52 PM
*To:* Rajani Karuturi; dev@cloudstack.apache.org
*Cc:* Wido den Hollander
*Subject:* Re: 4.10 release announcement?

Thanks Rohit.



i've modified the list based on that.


- IPV6 support for basic networking
- Virtio-Scsi disk controller support for KVM
- Ability to disable primary storage to secondary storage backups for
snapshots
- VMSnapshot (including memory) support for KVM on NFS
- RBD snapshot backups to secondary are now QCOW2 rather than raw to save
space
- Strongwan VPN Improvements
- Nuage VSP SDN Plugin: Shared networks support, Guest DNS support, Source-
and Static-nat to Underlay and support for Nuage VSP 4.0
- Significant performances improvements related to Virtual Router Deployment
- Force power off/stop support for KVM, VMware and XenServer
- Lots of bug fixes and performance improvements




From: Rohit Yadav 
Sent: Friday, August 11, 2017 12:51 PM
To: Rajani Karuturi; dev@cloudstack.apache.org
Cc: Wido den Hollander
Subject: Re: 4.10 release announcement?

The power off operation (or force stop flag in deployVM API) on VM is
supported for all KVM, VMware and XenServer.


- Rohit


From: Simon Weller 
Sent: Friday, August 11, 2017 2:31:52 PM
To: Rajani Karuturi; dev@cloudstack.apache.org
Cc: Wido den Hollander
Subject: Re: 4.10 release announcement?

Rajani,


Great job on this release!


Wido,


Here are few more items for the feature list. I've combined those already
mentioned as well.


- IPV6 support for basic networking
- Virtio-Scsi disk controller support for KVM
- Ability to disable primary storage to secondary storage backups for
snapshots
- VMSnapshot (including memory) support for KVM on NFS
- RBD snapshot backups to secondary are now QCOW2 rather than raw to save
space
- Strongwan VPN Improvements
- Nuage VSP SDN Plugin: Shared networks support, Guest DNS support, Source-
and Static-nat to Underlay and support for Nuage VSP 4.0
- Significant performances improvements related to Virtual Router Deployment
- KVM force stop support
- Lots of bug fixes and performance improvements

Can those that submitted other features please continue to add to this
list? This will also help with the release notes.

- Si




From: Wido den Hollander 
Sent: Friday, August 11, 2017 5:07 AM
To: Rajani Karuturi; dev@cloudstack.apache.org
Subject: Re: 4.10 release announcement?


> Op 11 augustus 2017 om 11:56 schreef Rajani Karuturi :
>
>
> Yes the packages are pushed. Status is still the same as my
> previous update.
>

Ok!

> api changes and fixed issues are available at
> https://github.com/apache/cloudstack-docs-rn/pull/30

Re: access to github

[Will Stevens]

You have to copy the whole link (including the < and >) in order for you to
get the article.  It is kind of stupid that they include those chars in the
url, but oh well.  Just clicking on that link will not work (apparently).
I will be at the office in a few minutes and I will help you out.

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Aug 7, 2017 at 8:12 AM, Pierre-Luc Dion <pd...@cloudops.com> wrote:

> Hi Will,
>
> Not sure what  was visible  with the Pony mail link, doesn't seams to work.
> but anyway , I'll check for the gitbox projet,
> There is some PRs I'd like to merge into the documentation.
>
> Thanks !
>
>
>
> *Pierre-Luc DION*
> Architecte de Solution Cloud | Cloud Solutions Architect
> t 855.652.5683
>
> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, Aug 2, 2017 at 8:45 PM, Will Stevens <williamstev...@gmail.com>
> wrote:
>
> > Here you go.
> >
> > https://lists.apache.org/thread.html/9fb5894da34e2cc383b2f9b01ab239
> > fd7a5131b90f67c282560ffc5f@
> > 
> >
> > On Aug 2, 2017 8:42 PM, "Will Stevens" <williamstev...@gmail.com> wrote:
> >
> > > You have to 2FA enabled in your GitHub account and register for the
> > gitbox
> > > project to be able to commit to that. But you can create a PR for now
> > and I
> > > can work with you to make sure you get your committee access setup.
> > >
> > > On Aug 2, 2017 8:39 PM, "Will Stevens" <williamstev...@gmail.com>
> wrote:
> > >
> > >> I think your looking for this. No?
> > >>
> > >> https://github.com/apache/cloudstack-docs-admin
> > >>
> > >> On Aug 2, 2017 8:37 PM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> His there a particular process to follow to have access to github for
> > >>> documentation projects?
> > >>> Could it be possible Github is not a mirror anymore since the apache
> > repo
> > >>> [1] doesn't seams to exist ?
> > >>>
> > >>> [1] git://git.apache.org/cloudstack-docs-admin.git
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Pierre-Luc
> > >>>
> > >>
> >
>

Re: access to github

[Will Stevens]

Here you go.

https://lists.apache.org/thread.html/9fb5894da34e2cc383b2f9b01ab239fd7a5131b90f67c282560ffc5f@


On Aug 2, 2017 8:42 PM, "Will Stevens" <williamstev...@gmail.com> wrote:

> You have to 2FA enabled in your GitHub account and register for the gitbox
> project to be able to commit to that. But you can create a PR for now and I
> can work with you to make sure you get your committee access setup.
>
> On Aug 2, 2017 8:39 PM, "Will Stevens" <williamstev...@gmail.com> wrote:
>
>> I think your looking for this. No?
>>
>> https://github.com/apache/cloudstack-docs-admin
>>
>> On Aug 2, 2017 8:37 PM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote:
>>
>>> Hi,
>>>
>>> His there a particular process to follow to have access to github for
>>> documentation projects?
>>> Could it be possible Github is not a mirror anymore since the apache repo
>>> [1] doesn't seams to exist ?
>>>
>>> [1] git://git.apache.org/cloudstack-docs-admin.git
>>>
>>> Thanks,
>>>
>>> Pierre-Luc
>>>
>>

Re: access to github

[Will Stevens]

You have to 2FA enabled in your GitHub account and register for the gitbox
project to be able to commit to that. But you can create a PR for now and I
can work with you to make sure you get your committee access setup.

On Aug 2, 2017 8:39 PM, "Will Stevens" <williamstev...@gmail.com> wrote:

> I think your looking for this. No?
>
> https://github.com/apache/cloudstack-docs-admin
>
> On Aug 2, 2017 8:37 PM, "Pierre-Luc Dion" <pd...@cloudops.com> wrote:
>
>> Hi,
>>
>> His there a particular process to follow to have access to github for
>> documentation projects?
>> Could it be possible Github is not a mirror anymore since the apache repo
>> [1] doesn't seams to exist ?
>>
>> [1] git://git.apache.org/cloudstack-docs-admin.git
>>
>> Thanks,
>>
>> Pierre-Luc
>>
>

Re: access to github

[Will Stevens]

I think your looking for this. No?

https://github.com/apache/cloudstack-docs-admin

On Aug 2, 2017 8:37 PM, "Pierre-Luc Dion"  wrote:

> Hi,
>
> His there a particular process to follow to have access to github for
> documentation projects?
> Could it be possible Github is not a mirror anymore since the apache repo
> [1] doesn't seams to exist ?
>
> [1] git://git.apache.org/cloudstack-docs-admin.git
>
> Thanks,
>
> Pierre-Luc
>

Re: DISCUSS : Vmware to Cloudstack migration support

[Will Stevens]

If you are going from VMware to CloudStack Managed VMware, this is
something I have done quite a bit.  I even built a tool to do this:
https://github.com/swill/migrate2cs

This is not a polished product.  Well, it is pretty polished once you get
it setup, but the setup is a bit complicated to get started.

If you would like to use it, let me know and I will do what I can to get
you setup.

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Thu, Jul 13, 2017 at 9:52 AM, Shreya Nair <shreya.n...@opcito.com> wrote:

> Hello,
>
> *An update to the migration task:*
>
> We have installed Cloudstack onto a vm on VMware to work around the
> cross-hypervisor migration issue. Now the underlying hypervisor would be
> the ESXi server for both setups (VMware and Cloudstack).
>
> Currently, we create the corresponding equivalent infrastructure on
> CloudStack wrt vmware setup.  We create a zone, pod, cluster and host set
> up with the underlying network infrastructure. However, while setting up
> the storage (Primary storage at cluster-wide scope and Secondary storage at
> zone-wide) the documentation mentions the following warnings:
>
>
>- *Primary storage warning:*
>   - When using preallocated storage for primary storage, be sure there
>   is nothing on the storage (ex. you have an empty SAN volume or
> an empty NFS
>   share). Adding the storage to CloudStack will destroy any existing
> data.
>- *Secondary storage warning:*
>   - Ensure that nothing is stored on the server. Adding the server to
>   CloudStack will destroy any existing data.
>
>
> We have obtained the mysql dump of the datastore of the source VM on
> VMware. The datastore, as you may be aware, is a logical container that
> holds virtual machine files and other files necessary for VM operations. As
> such, it may be logically mapped to the Secondary storage setup in the
> CloudStack infrastructure.
>
> Would it be possible to use the mysql dump from source to update the
> Secondary storage?
>
> Thanks & Regards,
>
> Shreya
>
> On Fri, Jul 7, 2017 at 4:04 PM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
> > Maybe you should try qemu-img instead.
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> > From: Shreya Nair [mailto:shreya.n...@opcito.com]
> > Sent: 07 July 2017 11:30
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
> > Cc: Vinay Patil <vinay.pa...@opcito.com>; Siddheshwar More <
> > siddheshwar.m...@opcito.com>
> > Subject: Re: DISCUSS : Vmware to Cloudstack migration support
> >
> > Hi Paul,
> > We explored the XenConvert solution. The XenConvert utility has been
> > retired from XenServer 6.2 and upward. So the only solution would be
> using
> > an old copy or trial version of Xen Conversion Manager.
> >
> > Instead of the qemu-img utility, we used the VirtualBox VBoxManage.exe to
> > support conversion of *.VMDK file to VHD. This VHD file was used to
> create
> > a CS template and create an instance. However, the VM was unable to mount
> > the drives as it was unable to find xvdXX partitions
> >
> >
> > I get the following error on CS instance on boot:
> > [Inline image 2]
> >
> > and the logs shows us this:
> >
> > You might have to change the root from /dev/hd[a-d] to /dev/xvd[a-d]
> >
> >
> >
> > However, on using lsblk command on the source vmware instance, we
> realized
> > that the partitions on SCSI storage devices (Used by vmware) are named as
> > /dev/sdXX while Xen supports /dev/xvdXX.
> > [Inline image 1]
> >
> > Note: VMware tools has been removed from VM prior to migration
> >
> >
> >
> > Thanks & Regards,
> >
> > Shreya
> >
> > On Thu, Jul 6, 2017 at 12:17 AM, Paul Angus <paul.an...@shapeblue.com<
> > mailto:paul.an...@shapeblue.com>> wrote:
> > There used to be a XenConvert utility that you do that conversion for
> > you.  I'm not sure that its about anymore, but a bit of googling might
> dig
> > up a copy.
> >
> > Alternatively there are linux and Windows versions of qemu-img convert ,
> > which usually does a pretty good job of disk image conversions
> >
> > Otherwise you could use a P2V backup/recovery tool with an agent that
> runs
> > inside your VMs
> >
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@sh

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Will Stevens]

Thanks Rohit.

On Jul 12, 2017 6:32 AM, "Rohit Yadav" <rohit.ya...@shapeblue.com> wrote:

Hi Will,


I'm not sure what you want, but the scripts/files are here:

https://github.com/shapeblue/Trillian/tree/master/Ansible/roles


- Rohit


From: Will Stevens <williamstev...@gmail.com>
Sent: 11 July 2017 17:47:06
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10

Can you link the appropriate config files so we can review the
configuration?  Thanks...



On Jul 11, 2017 8:05 AM, "Rohit Yadav" <rohit.ya...@shapeblue.com> wrote:

Will, I'll be on holidays next week and have tight schedules this month.
I'll ping Paul if he has bandwidth to contribute them.


- Rohit

________
From: Will Stevens <williamstev...@gmail.com>
Sent: 11 July 2017 16:41:41
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10

Pierre-Luc is asking because he has been the only person contributing to
the upgrade documentation released with the new releases since around 4.4.

Rohit, would you be able to contribute an upgrade path for CentOS6
installations in the documentation for the 4.10 release?

On Jul 11, 2017 5:59 AM, "Rohit Yadav" <rohit.ya...@shapeblue.com> wrote:

> PL - yes Trillian has tested with CentOS6 + JDK8 with 4.10.0.0/master+.
>
> JRE/JDK8 are available in additional repositories on CentOS6 so at least
> for 4.10.0.0 (already votes, to be announced) we cannot deprecate it.
> However, we can discuss that for 4.11.0.0 and onwards. However, I think
> unless we're breaking major compatibilities such as API, upgrades etc. we
> should not call the next release 5.x.
>
>
> - Rohit
>
> 
> From: Pierre-Luc Dion <pdion...@apache.org>
> Sent: 10 July 2017 18:51:33
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10
>
> In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
> to provide some instruction on how to install it, and is there anyone that
> tested 4.10 packages on CentOS6 ?
>
> Cheers,
>
> On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
> > I would suggest that this would justify a 5.0 release.. might be a good
> > time to get in any other major changes
> >
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> > Sent: 09 July 2017 13:46
> > To: dev@cloudstack.apache.org
> > Subject: [DISCUSS] drop support for CentOS6 with 4.10
> >
> > Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> > management-server and usage ?
> >
> > all the Upgrade path tests I've made was by creating new management
> server
> > on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> > install well on centos7 and I'm not away somebody test them on centos6.
> >
> > Should we call a vote on this?  I'm writing the upgrade part of the
> > release notes and I would focus on centos7 only. we should also update
> our
> > Quick Install Guide...
> >
> >
> > Thanks,
> >
> > PL
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

rohit.ya...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

Re: Developer Guide - Current Setup Guide?

[Will Stevens]

So this is the guide I always used to follow.  I think it is very outdated
as well:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack

I feel like both of these guides are pretty limited because it does not
cover an integration with any hypervisor, so you may be able to build ACS,
but you won't be able to do any real dev since you won't be able to spin
new VMs or anything like that.

The latest thing I have done for putting together a setup similar to this,
is documented here: https://github.com/swill/apachecon2016

Here are the slides:
https://github.com/swill/apachecon2016/blob/master/slides.pdf

This is not ideal either, but if you are troubleshooting the installation
process, it may help shed some light on the topic.

Also, a good resource for the setup is here as well:
https://github.com/apache/cloudstack/blob/master/.travis.yml

Not sure any of this helps...



*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Jul 10, 2017 at 4:43 PM, Alex Hitchins <a...@alexhitchins.com>
wrote:

> Great - the setup guide I'm following is : https://cwiki.apache.org/
> confluence/display/CLOUDSTACK/Setting+up+CloudStack+
> Development+Environment+on+Linux
>
> I have got a pull request open for the git repo readme, however it's
> breaking the build (somehow!). That is this one :
> https://github.com/apache/cloudstack/pull/2170
>
>
>
>
> Alexander Hitchins
> 
> E: a...@alexhitchins.com
> W: alexhitchins.com
> M: 07788 423 969
> T: 01892 523 587
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 10 July 2017 21:30
> To: dev@cloudstack.apache.org
> Subject: RE: Developer Guide - Current Setup Guide?
>
> Perfect. I will review that set of docs after I finish the one I am
> working on and we will go from there.
>
> Can you link the doc you are referencing?
>
> On Jul 10, 2017 4:21 PM, "Alex Hitchins" <a...@alexhitchins.com> wrote:
>
> > Thanks Will, very kind of you.
> >
> > I will try and get as far along as I can and keep notes of things I
> > notice along the way.
> >
> > Alexander Hitchins
> > 
> > E: a...@alexhitchins.com
> > W: alexhitchins.com
> > M: 07788 423 969
> > T: 01892 523 587
> >
> > -Original Message-
> > From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> > Behalf Of Will Stevens
> > Sent: 10 July 2017 20:49
> > To: dev@cloudstack.apache.org
> > Subject: Re: Developer Guide - Current Setup Guide?
> >
> > Alex, I have been slowly started getting through some of the
> > documentation that is out of date and will be adding some PRs with
> > changes.  I have not looked at that specific guide yet, so I will have
> > to review that one to be any help.  I will see what I can do to help
> > this week.  You can ping me directly if you have specific questions
> > and I will try to help.  Or ask on https://apachecloudstack.slack.com/
> > and get more real time support from more of us.
> >
> > *Will Stevens*
> > CTO
> >
> > <https://goo.gl/NYZ8KK>
> >
> > On Mon, Jul 10, 2017 at 1:58 PM, Alex Hitchins <a...@alexhitchins.com>
> > wrote:
> >
> > > This sounds like it isn't needed currently, correct?
> > >
> > > I will see if I can locate my confluence credentials, sure I had
> > > these circa 2013!
> > >
> > > Do I assume the broader answer to my question is that this is the
> > > most up to date resource? I see another person ask noob question so
> > > wondered if I had missed something.
> > >
> > > If anyone with cloudstack chops has a spare 10 minutes to look over
> > > the current guide with me I'd be more than happy to work the changes
> > > back in to the wiki. I'll even hand over all rights to Apache.
> > >
> > > > On 10 Jul 2017, at 18:29, Ron Wheeler
> > > > <rwhee...@artifact-software.com>
> > > wrote:
> > > >
> > > > You may want to own the wiki content as well as the software.
> > > >
> > > > A company may want to quote the wiki or incorporate some of it
> > > > into
> > > their documentation without having to get the rights from each
> > > person who contributed to the page.
> > > >
> > > >
> > > > Even more complicated if someone posts a design or an enhancement
> > > > and
> > > then claims to own it and patent it.
> > > >
> > > > It is good practice to make sure that Apache owns it all (code

Re: [DISCUSS] upgrade to 4.11

[Will Stevens]

Oh ok.  DB upgrade, not a new skeleton for the upgrade path between version
(hypervisors, etc...).

My bad.  :)

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Tue, Jul 11, 2017 at 9:41 AM, Daan Hoogland <daan.hoogl...@shapeblue.com>
wrote:

> No I am creating the upgrade code for the next version.
> (schema-41000to41100 and upgrade java class)
>
> On 11/07/17 15:29, "williamstev...@gmail.com on behalf of Will Stevens" <
> williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
>
> Not sure I have an answer for that.  Are you creating a PR to this set
> of
> documentation or where are you working?
> https://github.com/apache/cloudstack-docs-rn/tree/
> master/source/upgrade
>
> *Will Stevens*
> CTO
>
> <https://goo.gl/NYZ8KK>
>
> On Tue, Jul 11, 2017 at 9:15 AM, Daan Hoogland <
> daan.hoogl...@shapeblue.com>
> wrote:
>
> > Devs,
> >
> > I am busy creating the skeleton upgrade code for our next version
> (working
> > name 4.11). Are we still supporting all direct upgrades from 2.x
> onward or
> > should we only assume upgrade paths from 4.y onwards?
> >
> > Tnx,
> >
> > daan.hoogl...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>
>
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] upgrade to 4.11

[Will Stevens]

Not sure I have an answer for that.  Are you creating a PR to this set of
documentation or where are you working?
https://github.com/apache/cloudstack-docs-rn/tree/master/source/upgrade

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Tue, Jul 11, 2017 at 9:15 AM, Daan Hoogland <daan.hoogl...@shapeblue.com>
wrote:

> Devs,
>
> I am busy creating the skeleton upgrade code for our next version (working
> name 4.11). Are we still supporting all direct upgrades from 2.x onward or
> should we only assume upgrade paths from 4.y onwards?
>
> Tnx,
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Will Stevens]

Can you link the appropriate config files so we can review the
configuration?  Thanks...



On Jul 11, 2017 8:05 AM, "Rohit Yadav" <rohit.ya...@shapeblue.com> wrote:

Will, I'll be on holidays next week and have tight schedules this month.
I'll ping Paul if he has bandwidth to contribute them.


- Rohit


From: Will Stevens <williamstev...@gmail.com>
Sent: 11 July 2017 16:41:41
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10

Pierre-Luc is asking because he has been the only person contributing to
the upgrade documentation released with the new releases since around 4.4.

Rohit, would you be able to contribute an upgrade path for CentOS6
installations in the documentation for the 4.10 release?

On Jul 11, 2017 5:59 AM, "Rohit Yadav" <rohit.ya...@shapeblue.com> wrote:

> PL - yes Trillian has tested with CentOS6 + JDK8 with 4.10.0.0/master+.
>
> JRE/JDK8 are available in additional repositories on CentOS6 so at least
> for 4.10.0.0 (already votes, to be announced) we cannot deprecate it.
> However, we can discuss that for 4.11.0.0 and onwards. However, I think
> unless we're breaking major compatibilities such as API, upgrades etc. we
> should not call the next release 5.x.
>
>
> - Rohit
>
> 
> From: Pierre-Luc Dion <pdion...@apache.org>
> Sent: 10 July 2017 18:51:33
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10
>
> In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
> to provide some instruction on how to install it, and is there anyone that
> tested 4.10 packages on CentOS6 ?
>
> Cheers,
>
> On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus <paul.an...@shapeblue.com>
> wrote:
>
> > I would suggest that this would justify a 5.0 release.. might be a good
> > time to get in any other major changes
> >
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> > Sent: 09 July 2017 13:46
> > To: dev@cloudstack.apache.org
> > Subject: [DISCUSS] drop support for CentOS6 with 4.10
> >
> > Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> > management-server and usage ?
> >
> > all the Upgrade path tests I've made was by creating new management
> server
> > on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> > install well on centos7 and I'm not away somebody test them on centos6.
> >
> > Should we call a vote on this?  I'm writing the upgrade part of the
> > release notes and I would focus on centos7 only. we should also update
> our
> > Quick Install Guide...
> >
> >
> > Thanks,
> >
> > PL
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Will Stevens]

Pierre-Luc is asking because he has been the only person contributing to
the upgrade documentation released with the new releases since around 4.4.

Rohit, would you be able to contribute an upgrade path for CentOS6
installations in the documentation for the 4.10 release?

On Jul 11, 2017 5:59 AM, "Rohit Yadav"  wrote:

> PL - yes Trillian has tested with CentOS6 + JDK8 with 4.10.0.0/master+.
>
> JRE/JDK8 are available in additional repositories on CentOS6 so at least
> for 4.10.0.0 (already votes, to be announced) we cannot deprecate it.
> However, we can discuss that for 4.11.0.0 and onwards. However, I think
> unless we're breaking major compatibilities such as API, upgrades etc. we
> should not call the next release 5.x.
>
>
> - Rohit
>
> 
> From: Pierre-Luc Dion 
> Sent: 10 July 2017 18:51:33
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10
>
> In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
> to provide some instruction on how to install it, and is there anyone that
> tested 4.10 packages on CentOS6 ?
>
> Cheers,
>
> On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus 
> wrote:
>
> > I would suggest that this would justify a 5.0 release.. might be a good
> > time to get in any other major changes
> >
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> > Sent: 09 July 2017 13:46
> > To: dev@cloudstack.apache.org
> > Subject: [DISCUSS] drop support for CentOS6 with 4.10
> >
> > Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> > management-server and usage ?
> >
> > all the Upgrade path tests I've made was by creating new management
> server
> > on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> > install well on centos7 and I'm not away somebody test them on centos6.
> >
> > Should we call a vote on this?  I'm writing the upgrade part of the
> > release notes and I would focus on centos7 only. we should also update
> our
> > Quick Install Guide...
> >
> >
> > Thanks,
> >
> > PL
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

RE: Developer Guide - Current Setup Guide?

[Will Stevens]

Perfect. I will review that set of docs after I finish the one I am working
on and we will go from there.

Can you link the doc you are referencing?

On Jul 10, 2017 4:21 PM, "Alex Hitchins" <a...@alexhitchins.com> wrote:

> Thanks Will, very kind of you.
>
> I will try and get as far along as I can and keep notes of things I notice
> along the way.
>
> Alexander Hitchins
> 
> E: a...@alexhitchins.com
> W: alexhitchins.com
> M: 07788 423 969
> T: 01892 523 587
>
> -Original Message-
> From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> Behalf Of Will Stevens
> Sent: 10 July 2017 20:49
> To: dev@cloudstack.apache.org
> Subject: Re: Developer Guide - Current Setup Guide?
>
> Alex, I have been slowly started getting through some of the documentation
> that is out of date and will be adding some PRs with changes.  I have not
> looked at that specific guide yet, so I will have to review that one to be
> any help.  I will see what I can do to help this week.  You can ping me
> directly if you have specific questions and I will try to help.  Or ask on
> https://apachecloudstack.slack.com/ and get more real time support from
> more of us.
>
> *Will Stevens*
> CTO
>
> <https://goo.gl/NYZ8KK>
>
> On Mon, Jul 10, 2017 at 1:58 PM, Alex Hitchins <a...@alexhitchins.com>
> wrote:
>
> > This sounds like it isn't needed currently, correct?
> >
> > I will see if I can locate my confluence credentials, sure I had these
> > circa 2013!
> >
> > Do I assume the broader answer to my question is that this is the most
> > up to date resource? I see another person ask noob question so
> > wondered if I had missed something.
> >
> > If anyone with cloudstack chops has a spare 10 minutes to look over
> > the current guide with me I'd be more than happy to work the changes
> > back in to the wiki. I'll even hand over all rights to Apache.
> >
> > > On 10 Jul 2017, at 18:29, Ron Wheeler
> > > <rwhee...@artifact-software.com>
> > wrote:
> > >
> > > You may want to own the wiki content as well as the software.
> > >
> > > A company may want to quote the wiki or incorporate some of it into
> > their documentation without having to get the rights from each person
> > who contributed to the page.
> > >
> > >
> > > Even more complicated if someone posts a design or an enhancement
> > > and
> > then claims to own it and patent it.
> > >
> > > It is good practice to make sure that Apache owns it all (code,
> > > docs,
> > test cases, enhancements, patches)  and that you can use it all
> > without legal problems under the Apache license.
> > >
> > >
> > > Ron
> > >
> > >> On 10/07/2017 12:23 PM, Daan Hoogland wrote:
> > >> Why do you say that Ron? You need one to become a committer. for
> > >> the wiki we need to recognise you as a contributor. I think you
> > >> need no more.
> > >>
> > >> On Mon, Jul 10, 2017 at 5:10 PM, Ron Wheeler
> > >> <rwhee...@artifact-software.com> wrote:
> > >>> Alex,
> > >>> Do you have a CLA on file with Apache.
> > >>> You should have one to contribute to the wiki.
> > >>>
> > >>> Ron
> > >>>
> > >>>> On 10/07/2017 10:42 AM, Daan Hoogland wrote:
> > >>>> create your account on cwiki and we can give you access
> > >>>>
> > >>>> On Sun, Jul 9, 2017 at 12:10 AM, Alex Hitchins
> > >>>> <a...@alexhitchins.com
> > >
> > >>>> wrote:
> > >>>>> Please let me know if there is anything I can do to help with this.
> > >>>>>
> > >>>>> I have an open PR on the repo readme.md, minor documentation
> > >>>>> change
> > but
> > >>>>> somehow is breaking the build. My guess is it's something
> > >>>>> unrelated
> > on
> > >>>>> master.
> > >>>>>
> > >>>>>> On 8 Jul 2017, at 22:37, Will Stevens
> > >>>>>> <williamstev...@gmail.com>
> > wrote:
> > >>>>>>
> > >>>>>> We need to amend. As of 4.10 we are on jdk 8.
> > >>>>>>
> > >>>>>> I will have to review it and see what needs to be done to bring
> > >>>>>> it
> > up to
> > >&

Re: Developer Guide - Current Setup Guide?

[Will Stevens]

Alex, I have been slowly started getting through some of the documentation
that is out of date and will be adding some PRs with changes.  I have not
looked at that specific guide yet, so I will have to review that one to be
any help.  I will see what I can do to help this week.  You can ping me
directly if you have specific questions and I will try to help.  Or ask on
https://apachecloudstack.slack.com/ and get more real time support from
more of us.

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Jul 10, 2017 at 1:58 PM, Alex Hitchins <a...@alexhitchins.com>
wrote:

> This sounds like it isn't needed currently, correct?
>
> I will see if I can locate my confluence credentials, sure I had these
> circa 2013!
>
> Do I assume the broader answer to my question is that this is the most up
> to date resource? I see another person ask noob question so wondered if I
> had missed something.
>
> If anyone with cloudstack chops has a spare 10 minutes to look over the
> current guide with me I'd be more than happy to work the changes back in to
> the wiki. I'll even hand over all rights to Apache.
>
> > On 10 Jul 2017, at 18:29, Ron Wheeler <rwhee...@artifact-software.com>
> wrote:
> >
> > You may want to own the wiki content as well as the software.
> >
> > A company may want to quote the wiki or incorporate some of it into
> their documentation without having to get the rights from each person who
> contributed to the page.
> >
> >
> > Even more complicated if someone posts a design or an enhancement and
> then claims to own it and patent it.
> >
> > It is good practice to make sure that Apache owns it all (code, docs,
> test cases, enhancements, patches)  and that you can use it all without
> legal problems under the Apache license.
> >
> >
> > Ron
> >
> >> On 10/07/2017 12:23 PM, Daan Hoogland wrote:
> >> Why do you say that Ron? You need one to become a committer. for the
> >> wiki we need to recognise you as a contributor. I think you need no
> >> more.
> >>
> >> On Mon, Jul 10, 2017 at 5:10 PM, Ron Wheeler
> >> <rwhee...@artifact-software.com> wrote:
> >>> Alex,
> >>> Do you have a CLA on file with Apache.
> >>> You should have one to contribute to the wiki.
> >>>
> >>> Ron
> >>>
> >>>> On 10/07/2017 10:42 AM, Daan Hoogland wrote:
> >>>> create your account on cwiki and we can give you access
> >>>>
> >>>> On Sun, Jul 9, 2017 at 12:10 AM, Alex Hitchins <a...@alexhitchins.com
> >
> >>>> wrote:
> >>>>> Please let me know if there is anything I can do to help with this.
> >>>>>
> >>>>> I have an open PR on the repo readme.md, minor documentation change
> but
> >>>>> somehow is breaking the build. My guess is it's something unrelated
> on
> >>>>> master.
> >>>>>
> >>>>>> On 8 Jul 2017, at 22:37, Will Stevens <williamstev...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> We need to amend. As of 4.10 we are on jdk 8.
> >>>>>>
> >>>>>> I will have to review it and see what needs to be done to bring it
> up to
> >>>>>> date.
> >>>>>>
> >>>>>> On Jul 8, 2017 4:46 PM, "Alex Hitchins" <a...@alexhitchins.com>
> wrote:
> >>>>>>
> >>>>>> Asking as I want to be sure I'm getting myself setup correctly.
> >>>>>>
> >>>>>> I appreciate setup guides may not necessitate lots of amendments
> however
> >>>>>> 4
> >>>>>> years seemed a long time to go with nothing. Are we still on JDK 6
> for
> >>>>>> example?
> >>>>>>
> >>>>>> More than happy to amend Confluence with updates as I come across
> them.
> >>>>>>
> >>>>>>
> >>>>>> Alexander Hitchins
> >>>>>> 
> >>>>>> E: a...@alexhitchins.com
> >>>>>> W: alexhitchins.com
> >>>>>> M: 07788 423 969
> >>>>>> T: 01892 523 587
> >>>>>>
> >>>>>> -Original Message-
> >>>>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> >>>>>> Sent: 07 July 2017 21:08
> >>>>>> To: dev <dev@cloudstack.apache.org>
> >

Re: Developer Guide - Current Setup Guide?

[Will Stevens]

It is worth asking people to sign those even if they are not a committer,
but they are actively contributing to the wiki.  So if that is your point,
then I agree that is probably a good idea Ron...

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Jul 10, 2017 at 2:32 PM, Ron Wheeler <rwhee...@artifact-software.com
> wrote:

> https://www.apache.org/licenses/icla.pdf should be filled in and
> submitted.
> It covers all Apache projects so you only do it once. It specifically
> mentions documentation.
>
> It is also important to note that if a contributor works for a company and
> works on Apache projects on company time or has signed an employment
> agreement that gives the employer rights to all work that they do while
> they are employed, Apache needs a corporate CLA
> https://www.apache.org/licenses/cla-corporate.txt wherein the corporation
> cedes the rights to Apache.
> Unfortunately the PMC needs to trust the individual contributors to be
> aware of the status of the rights to their work and do the right thing.
> If you suspect that a contributor is in this situation, it is worth asking
> the questions about their employment and getting a CCLA signed.
>
> These are not onerous but are a sign that a project takes its work
> seriously and intends to have people integrate their products into
> production environments without having to worry about legal entanglements.
>
> Ron
>
>
> On 10/07/2017 1:58 PM, Alex Hitchins wrote:
>
>> This sounds like it isn't needed currently, correct?
>>
>> I will see if I can locate my confluence credentials, sure I had these
>> circa 2013!
>>
>> Do I assume the broader answer to my question is that this is the most up
>> to date resource? I see another person ask noob question so wondered if I
>> had missed something.
>>
>> If anyone with cloudstack chops has a spare 10 minutes to look over the
>> current guide with me I'd be more than happy to work the changes back in to
>> the wiki. I'll even hand over all rights to Apache.
>>
>> On 10 Jul 2017, at 18:29, Ron Wheeler <rwhee...@artifact-software.com>
>>> wrote:
>>>
>>> You may want to own the wiki content as well as the software.
>>>
>>> A company may want to quote the wiki or incorporate some of it into
>>> their documentation without having to get the rights from each person who
>>> contributed to the page.
>>>
>>>
>>> Even more complicated if someone posts a design or an enhancement and
>>> then claims to own it and patent it.
>>>
>>> It is good practice to make sure that Apache owns it all (code, docs,
>>> test cases, enhancements, patches)  and that you can use it all without
>>> legal problems under the Apache license.
>>>
>>>
>>> Ron
>>>
>>> On 10/07/2017 12:23 PM, Daan Hoogland wrote:
>>>> Why do you say that Ron? You need one to become a committer. for the
>>>> wiki we need to recognise you as a contributor. I think you need no
>>>> more.
>>>>
>>>> On Mon, Jul 10, 2017 at 5:10 PM, Ron Wheeler
>>>> <rwhee...@artifact-software.com> wrote:
>>>>
>>>>> Alex,
>>>>> Do you have a CLA on file with Apache.
>>>>> You should have one to contribute to the wiki.
>>>>>
>>>>> Ron
>>>>>
>>>>> On 10/07/2017 10:42 AM, Daan Hoogland wrote:
>>>>>> create your account on cwiki and we can give you access
>>>>>>
>>>>>> On Sun, Jul 9, 2017 at 12:10 AM, Alex Hitchins <a...@alexhitchins.com
>>>>>> >
>>>>>> wrote:
>>>>>>
>>>>>>> Please let me know if there is anything I can do to help with this.
>>>>>>>
>>>>>>> I have an open PR on the repo readme.md, minor documentation change
>>>>>>> but
>>>>>>> somehow is breaking the build. My guess is it's something unrelated
>>>>>>> on
>>>>>>> master.
>>>>>>>
>>>>>>> On 8 Jul 2017, at 22:37, Will Stevens <williamstev...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> We need to amend. As of 4.10 we are on jdk 8.
>>>>>>>>
>>>>>>>> I will have to review it and see what needs to be done to bring it
>>>>>>>> up to
>>>>>>>> date.
>>>>>>>>
>>>

Re: Developer Guide - Current Setup Guide?

[Will Stevens]

While I agree with some of your points Ron, we also need to make sure that
we are setup to be able to take advantage of motivated people contributing
(especially around documentation) without first requiring that they become
a committer.  That is a bit of a chicken and egg problem because no one
will accept a new committer with zero activity, so if we didn't give this
type of access, then an interested contributor would never be able to
support the project in the ways know how.

We need as much support on the supporting documentation as we can get, and
we don't have the convenience of mechanisms like 'pull requests' on wiki
content.

My 0.02$ anyway...

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Jul 10, 2017 at 1:29 PM, Ron Wheeler <rwhee...@artifact-software.com
> wrote:

> You may want to own the wiki content as well as the software.
>
> A company may want to quote the wiki or incorporate some of it into their
> documentation without having to get the rights from each person who
> contributed to the page.
>
>
> Even more complicated if someone posts a design or an enhancement and then
> claims to own it and patent it.
>
> It is good practice to make sure that Apache owns it all (code, docs, test
> cases, enhancements, patches)  and that you can use it all without legal
> problems under the Apache license.
>
>
> Ron
>
>
> On 10/07/2017 12:23 PM, Daan Hoogland wrote:
>
>> Why do you say that Ron? You need one to become a committer. for the
>> wiki we need to recognise you as a contributor. I think you need no
>> more.
>>
>> On Mon, Jul 10, 2017 at 5:10 PM, Ron Wheeler
>> <rwhee...@artifact-software.com> wrote:
>>
>>> Alex,
>>> Do you have a CLA on file with Apache.
>>> You should have one to contribute to the wiki.
>>>
>>> Ron
>>>
>>> On 10/07/2017 10:42 AM, Daan Hoogland wrote:
>>>
>>>> create your account on cwiki and we can give you access
>>>>
>>>> On Sun, Jul 9, 2017 at 12:10 AM, Alex Hitchins <a...@alexhitchins.com>
>>>> wrote:
>>>>
>>>>> Please let me know if there is anything I can do to help with this.
>>>>>
>>>>> I have an open PR on the repo readme.md, minor documentation change
>>>>> but
>>>>> somehow is breaking the build. My guess is it's something unrelated on
>>>>> master.
>>>>>
>>>>> On 8 Jul 2017, at 22:37, Will Stevens <williamstev...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> We need to amend. As of 4.10 we are on jdk 8.
>>>>>>
>>>>>> I will have to review it and see what needs to be done to bring it up
>>>>>> to
>>>>>> date.
>>>>>>
>>>>>> On Jul 8, 2017 4:46 PM, "Alex Hitchins" <a...@alexhitchins.com>
>>>>>> wrote:
>>>>>>
>>>>>> Asking as I want to be sure I'm getting myself setup correctly.
>>>>>>
>>>>>> I appreciate setup guides may not necessitate lots of amendments
>>>>>> however
>>>>>> 4
>>>>>> years seemed a long time to go with nothing. Are we still on JDK 6 for
>>>>>> example?
>>>>>>
>>>>>> More than happy to amend Confluence with updates as I come across
>>>>>> them.
>>>>>>
>>>>>>
>>>>>> Alexander Hitchins
>>>>>> 
>>>>>> E: a...@alexhitchins.com
>>>>>> W: alexhitchins.com
>>>>>> M: 07788 423 969
>>>>>> T: 01892 523 587
>>>>>>
>>>>>> -Original Message-
>>>>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>>>>> Sent: 07 July 2017 21:08
>>>>>> To: dev <dev@cloudstack.apache.org>
>>>>>> Subject: Re: Developer Guide - Current Setup Guide?
>>>>>>
>>>>>> Why do you ask, Alex? Is something not working?
>>>>>>
>>>>>> Biligual auto correct use.  Read at your own risico
>>>>>>
>>>>>> On 7 Jul 2017 9:54 pm, "Alex Hitchins" <a...@alexhitchins.com> wrote:
>>>>>>>
>>>>>>> Hello all,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I note this was last amended 2013, is there a better/more recent
>>>>>>> resource for the aspiring CloudStack developer?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
>>>>>>> Setting+up+CloudStack
>>>>>>> +Development+Environment+on+Linux
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Alexander Hitchins
>>>>>>>
>>>>>>> 
>>>>>>>
>>>>>>> E: a...@alexhitchins.com
>>>>>>>
>>>>>>> W: alexhitchins.com
>>>>>>>
>>>>>>> M: 07788 423 969
>>>>>>>
>>>>>>> T: 01892 523 587
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>> --
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwhee...@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>>
>>
>>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>

Re: Developer Guide - Current Setup Guide?

[Will Stevens]

This is what he means:
https://www.apache.org/dev/new-committers-guide.html#cla

I don't know that it is required for wiki access, but someone probably does
understand those details.


On Jul 10, 2017 12:44 PM, "Alex Hitchins" <a...@alexhitchins.com> wrote:

Sorry, CLA?

Is this the licence? I don't believe I do have one personally. I believe I
may have an account for the wiki still, will see if I can resurrect it.

Happy to amend the wiki, it is just the process of finding what is out of
date by trial and error.

The PR I have open, that should be very separate from the wiki though, no?

> On 10 Jul 2017, at 16:10, Ron Wheeler <rwhee...@artifact-software.com>
wrote:
>
> Alex,
> Do you have a CLA on file with Apache.
> You should have one to contribute to the wiki.
>
> Ron
>
>> On 10/07/2017 10:42 AM, Daan Hoogland wrote:
>> create your account on cwiki and we can give you access
>>
>>> On Sun, Jul 9, 2017 at 12:10 AM, Alex Hitchins <a...@alexhitchins.com>
wrote:
>>> Please let me know if there is anything I can do to help with this.
>>>
>>> I have an open PR on the repo readme.md, minor documentation change but
somehow is breaking the build. My guess is it's something unrelated on
master.
>>>
>>>> On 8 Jul 2017, at 22:37, Will Stevens <williamstev...@gmail.com> wrote:
>>>>
>>>> We need to amend. As of 4.10 we are on jdk 8.
>>>>
>>>> I will have to review it and see what needs to be done to bring it up
to
>>>> date.
>>>>
>>>> On Jul 8, 2017 4:46 PM, "Alex Hitchins" <a...@alexhitchins.com> wrote:
>>>>
>>>> Asking as I want to be sure I'm getting myself setup correctly.
>>>>
>>>> I appreciate setup guides may not necessitate lots of amendments
however 4
>>>> years seemed a long time to go with nothing. Are we still on JDK 6 for
>>>> example?
>>>>
>>>> More than happy to amend Confluence with updates as I come across them.
>>>>
>>>>
>>>> Alexander Hitchins
>>>> 
>>>> E: a...@alexhitchins.com
>>>> W: alexhitchins.com
>>>> M: 07788 423 969
>>>> T: 01892 523 587
>>>>
>>>> -Original Message-
>>>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>>>> Sent: 07 July 2017 21:08
>>>> To: dev <dev@cloudstack.apache.org>
>>>> Subject: Re: Developer Guide - Current Setup Guide?
>>>>
>>>> Why do you ask, Alex? Is something not working?
>>>>
>>>> Biligual auto correct use.  Read at your own risico
>>>>
>>>>> On 7 Jul 2017 9:54 pm, "Alex Hitchins" <a...@alexhitchins.com> wrote:
>>>>>
>>>>> Hello all,
>>>>>
>>>>>
>>>>>
>>>>> I note this was last amended 2013, is there a better/more recent
>>>>> resource for the aspiring CloudStack developer?
>>>>>
>>>>>
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
>>>>> Setting+up+CloudStack
>>>>> +Development+Environment+on+Linux
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Alexander Hitchins
>>>>>
>>>>> 
>>>>>
>>>>> E: a...@alexhitchins.com
>>>>>
>>>>> W: alexhitchins.com
>>>>>
>>>>> M: 07788 423 969
>>>>>
>>>>> T: 01892 523 587
>>>>>
>>>>>
>>>>>
>>>>>
>>
>>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>

RE: Developer Guide - Current Setup Guide?

[Will Stevens]

We need to amend. As of 4.10 we are on jdk 8.

I will have to review it and see what needs to be done to bring it up to
date.

On Jul 8, 2017 4:46 PM, "Alex Hitchins"  wrote:

Asking as I want to be sure I'm getting myself setup correctly.

I appreciate setup guides may not necessitate lots of amendments however 4
years seemed a long time to go with nothing. Are we still on JDK 6 for
example?

More than happy to amend Confluence with updates as I come across them.


Alexander Hitchins

E: a...@alexhitchins.com
W: alexhitchins.com
M: 07788 423 969
T: 01892 523 587

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: 07 July 2017 21:08
To: dev 
Subject: Re: Developer Guide - Current Setup Guide?

Why do you ask, Alex? Is something not working?

Biligual auto correct use.  Read at your own risico

On 7 Jul 2017 9:54 pm, "Alex Hitchins"  wrote:

> Hello all,
>
>
>
> I note this was last amended 2013, is there a better/more recent
> resource for the aspiring CloudStack developer?
>
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> Setting+up+CloudStack
> +Development+Environment+on+Linux
>
>
>
>
>
>
>
>
>
> Alexander Hitchins
>
> 
>
> E: a...@alexhitchins.com
>
> W: alexhitchins.com
>
> M: 07788 423 969
>
> T: 01892 523 587
>
>
>
>

ACS Release Note Generation

[Will Stevens]

Hey All,
I just sent Rajani a more detailed email including the actual output, but I
figured I might as well send out a more general email to let everyone know
about this work.

https://github.com/swill/generate_acs_rn

When I was the 4.9 RM, I added the ability to output the API changes in a
JSON format [1] in addition to the existing TXT format.  I did this so I
could use this output to script the formatting of the respective release
notes.

Today I finally got around to releasing the code I had written to produce
the 'API Changes' [2] and 'Fixed Issues' [3] sections of the release notes,
so I figured I would let people know about it.

Please feel free to offer suggestions or open Pull Requests if you would
like changes.

Cheers,

Will

[1] https://github.com/apache/cloudstack/pull/1658
[2]
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.9.0/api-changes.html
[3]
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.9.0/fixed_issues.html

Re: [DISCUSS] Extending Marvin Smoketest Suite

[Will Stevens]

I would like to see better testing of 'projects' as well, it is almost
entirely untested.

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Fri, Jul 7, 2017 at 7:05 AM, Boris Stoyanov <boris.stoya...@shapeblue.com
> wrote:

> Hi all,
>
> I’ve started up this improvement, which is to extend Marvin smoketests
> with some more tests. I’ve indicated a few tests from the component tests
> that I think would be really good to have into smoketests, like for example
> Usage tests ( we don’t have any currently).
> https://issues.apache.org/jira/browse/CLOUDSTACK-9989
>
>
> Here’s a list of items that I think are suitable candidates:
> test_accounts.py - There are no tests for accounts/users in the current
> suite
> test_host_maintenance.py - We have received reports for multiple failures
> around moving VMs away from a Host set for Maintenance.
> test_regions.py - there are no tests for this in the current suite
> test_usage.py - No tests and this is quite vital to public and private
> cloud providers, CloudStack users rely on this usage metrics and we should
> be testing this on a daily basis.
>
> In the JIRA ticket I’ve added up more details against each group of tests
> since there are some with problems at this stage.
>
> Can you guys please review and add more areas that you would like to be
> smoke tested as part of each PR in the community repo?
>
> Thanks
> Boris Stoyanov
>
> boris.stoya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

[Will Stevens]

I have added Syed to this.  He has done some initial review to get a port
to KVM working, but I am not sure how far he got yet.

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Mon, Jul 3, 2017 at 2:26 PM, Paul Angus <paul.an...@shapeblue.com> wrote:

> I will take an action to look at trillian on KVM.  There's nothing
> explicit or implicit in trillian itself that it requires vmware as long as
> we can trunk the guest VLANs and virtualise the hypervisors.
>
> ________
> From: Will Stevens <wstev...@cloudops.com>
> Sent: 3 Jul 2017 2:06 am
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] - Releases, Project Management & Funding Thereof
>
> Sorry, I have been keeping up with these threads while on vacation at a
> campsite.  :)  Finally back to a computer.
>
> Yes, ideally we would have more people actually committing code and
> validating the PRs are ready for merge.  Right now, we have VERY limited CI
> setups, so we are bottlenecked on the ability to actually test the PRs in a
> timely fashion.  This leads to PRs sitting for a week at a time in some
> 'phase' of the process.  This means that the developers get pushed off to
> other items to pay the bills and it then causes a lag everywhere.  Because
> of this, the RM has basically had to fill the role of making sure
> everything is moving and understanding and unblocking the different PRs as
> they move through the review/test/commit phases.
>
> Yes, we need more reviewers.  That is very true.
>
> Also true, is that we need more CI environments.  I would love to see
> Trillian be able to be run on KVM on a developers laptop to at least test
> the core components.  We could then start to standardize the dev/test cycle
> for developers so we can start focusing on a 'minimum support feature
> set'.  We could also hopefully leverage the developers setups to run CI
> overnight if they choose to participate (or at least their own PRs).  If we
> could standardize well enough to push the workload to the edge, I think we
> would end up with more active rigs in the game.
>
> I personally feel that if we can put the CI on rails and standardize our
> dev environment, a lot of our 'we need an full time RM' problems go away.
> However, I do think we will need a full time RM for at least a year to be
> able to shepherd that into existence though.
>
> *Will Stevens*
> CTO
>
> <https://goo.gl/NYZ8KK>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> On Sun, Jul 2, 2017 at 8:06 PM, Syed Ahmed <sah...@cloudops.com> wrote:
>
> > Agree with Ron about this being a role of the commiter but in what I have
> > seen, it is mostly the RM who has to run around and ask for updates/make
> > sure fixes are done.
> >
> > Part of the problem also is that there is a lack of reviewers. We've had
> > some issues recently [1] which were code which was committed was not
> > properly reviewed and later lead to problems. Having a RM and some core
> > reviewers is essential to maintain quality and sanity of the release.
> >
> > I also agree with testing on a known setup with known parameters. The
> > community can pool resources for hardware and Trillian can be used as the
> > CI framework. There was supposedly hadware donated by Citrix to the ASF.
> > Anyone know what happened to that?
> >
> > [1] https://github.com/apache/cloudstack/pull/1834
> >
> >
> > On Sun, Jul 2, 2017 at 9:55 AM, Ron Wheeler <rwheeler@artifact-software.
> > com>
> > wrote:
> >
> > > I think you are describing the roles of all of the committers
> > >
> > > Is it normal at Apache for the RM to be doing all of this stuff?
> > >
> > > I would expect that the RM has a QC role in these activities but others
> > > are doing the work.
> > >
> > > Ron
> > >
> > >
> > > On 01/07/2017 7:18 PM, Will Stevens wrote:
> > >
> > >> Oh, and if a system VM is touched, then you have to add in a new
> system
> > VM
> > >> build and install into the CI setup prior to testing...
> > >>
> > >> On Jul 1, 2017 6:41 PM, wrote:
> > >>
> > >> Which is part of the reason the RM job is hard and time consuming.
> > >> - checking the PRs have the appropriate tests.
> > >> - updating the CI to include the new tests.
> > >> - run and report CI for the PR (with very limited CI infra community
> > >> wide).
> > >> - chase PR authors to get their PRs to a point where you are happy

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

[Will Stevens]

Sorry, I have been keeping up with these threads while on vacation at a
campsite.  :)  Finally back to a computer.

Yes, ideally we would have more people actually committing code and
validating the PRs are ready for merge.  Right now, we have VERY limited CI
setups, so we are bottlenecked on the ability to actually test the PRs in a
timely fashion.  This leads to PRs sitting for a week at a time in some
'phase' of the process.  This means that the developers get pushed off to
other items to pay the bills and it then causes a lag everywhere.  Because
of this, the RM has basically had to fill the role of making sure
everything is moving and understanding and unblocking the different PRs as
they move through the review/test/commit phases.

Yes, we need more reviewers.  That is very true.

Also true, is that we need more CI environments.  I would love to see
Trillian be able to be run on KVM on a developers laptop to at least test
the core components.  We could then start to standardize the dev/test cycle
for developers so we can start focusing on a 'minimum support feature
set'.  We could also hopefully leverage the developers setups to run CI
overnight if they choose to participate (or at least their own PRs).  If we
could standardize well enough to push the workload to the edge, I think we
would end up with more active rigs in the game.

I personally feel that if we can put the CI on rails and standardize our
dev environment, a lot of our 'we need an full time RM' problems go away.
However, I do think we will need a full time RM for at least a year to be
able to shepherd that into existence though.

*Will Stevens*
CTO

<https://goo.gl/NYZ8KK>

On Sun, Jul 2, 2017 at 8:06 PM, Syed Ahmed <sah...@cloudops.com> wrote:

> Agree with Ron about this being a role of the commiter but in what I have
> seen, it is mostly the RM who has to run around and ask for updates/make
> sure fixes are done.
>
> Part of the problem also is that there is a lack of reviewers. We've had
> some issues recently [1] which were code which was committed was not
> properly reviewed and later lead to problems. Having a RM and some core
> reviewers is essential to maintain quality and sanity of the release.
>
> I also agree with testing on a known setup with known parameters. The
> community can pool resources for hardware and Trillian can be used as the
> CI framework. There was supposedly hadware donated by Citrix to the ASF.
> Anyone know what happened to that?
>
> [1] https://github.com/apache/cloudstack/pull/1834
>
>
> On Sun, Jul 2, 2017 at 9:55 AM, Ron Wheeler <rwheeler@artifact-software.
> com>
> wrote:
>
> > I think you are describing the roles of all of the committers
> >
> > Is it normal at Apache for the RM to be doing all of this stuff?
> >
> > I would expect that the RM has a QC role in these activities but others
> > are doing the work.
> >
> > Ron
> >
> >
> > On 01/07/2017 7:18 PM, Will Stevens wrote:
> >
> >> Oh, and if a system VM is touched, then you have to add in a new system
> VM
> >> build and install into the CI setup prior to testing...
> >>
> >> On Jul 1, 2017 6:41 PM, wrote:
> >>
> >> Which is part of the reason the RM job is hard and time consuming.
> >> - checking the PRs have the appropriate tests.
> >> - updating the CI to include the new tests.
> >> - run and report CI for the PR (with very limited CI infra community
> >> wide).
> >> - chase PR authors to get their PRs to a point where you are happy they
> >> are
> >> not breaking master
> >> - rinse repeat for 200+ PRs...
> >>
> >> On Jul 1, 2017 6:34 PM, "Will Stevens" <williamstev...@gmail.com>
> wrote:
> >>
> >> Yes, we can totally reject PRs until we are happy with the associated
> >> tests.
> >>
> >> On Jul 1, 2017 5:48 PM, "Alex Hitchins" <a...@alexhitchins.com> wrote:
> >>
> >> Out of interest, are there any guidelines/rules in place to reject PR's
> >>> without unit tests?
> >>>
> >>>
> >>>
> >>>
> >>> Alexander Hitchins
> >>> 
> >>> E: a...@alexhitchins.com
> >>> W: alexhitchins.com
> >>> M: 07788 423 969
> >>> T: 01892 523 587
> >>>
> >>> -Original Message-
> >>> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> >>> Sent: 30 June 2017 21:58
> >>> To: dev@cloudstack.apache.org
> >>> Subject: RE: [DISCUSS] - Releases, Project Management & Funding Thereof
> >>>
> >>> Taken from a talk on CloudS