Re: Welcoming Mike as the new Apache CloudStack VP

[Marc-Aurèle Brothier]

Thanks for the work Wido, and congrats Mike

On Tue, Mar 27, 2018 at 6:31 AM, Jayapal Uradi  wrote:

> Congratulations, Milke!
>
> -Jayapal
>
> > On Mar 27, 2018, at 2:38 AM, Nitin Kumar Maharana  accelerite.com> wrote:
> >
> > Congratulations, Mike!!
> >
> > -
> > Nitin
> > On 26-Mar-2018, at 7:41 PM, Wido den Hollander > wrote:
> >
> > Hi all,
> >
> > It's been a great pleasure working with the CloudStack project as the
> > ACS VP over the past year.
> >
> > A big thank you from my side for everybody involved with the project in
> > the last year.
> >
> > Hereby I would like to announce that Mike Tutkowski has been elected to
> > replace me as the Apache Cloudstack VP in our annual VP rotation.
> >
> > Mike has a long history with the project and I am are happy welcome him
> > as the new VP for CloudStack.
> >
> > Welcome Mike!
> >
> > Thanks,
> >
> > Wido
> >
> > 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: ConfigDrive status

[Jayapal Uradi]

Hi Nux,

It is developed only for advanced zone shared network (offering without any 
services).
This feature is developed on xenserver, kvm and vmware hypervisor.

It can be extended to other networks.

-Jayapal
> On Mar 26, 2018, at 9:56 PM, Nux!  wrote:
> 
> Thanks for all the feedback, I'll do some reading then.
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "ilya musayev" 
>> To: "dev" 
>> Sent: Monday, 26 March, 2018 17:03:30
>> Subject: Re: ConfigDrive status
> 
>> Lucian
>> 
>> We reported 3-4 issues with config drive. It’s being worked on. It does
>> work - but not per agreed upon specifications.
>> 
>> See below
>> 
>> 
>> https://issues.apache.org/jira/browse/CLOUDSTACK-10287
>> https://issues.apache.org/jira/browse/CLOUDSTACK-10288
>> https://issues.apache.org/jira/browse/CLOUDSTACK-10289
>> https://issues.apache.org/jira/browse/CLOUDSTACK-10290
>> 
>> Regards
>> Ilya
>> 
>> On Mon, Mar 26, 2018 at 8:58 AM Dag Sonstebo 
>> wrote:
>> 
>>> Hi Lucian,
>>> 
>>> I’m maybe not the right person to answer this – but my understanding is it
>>> only kicks in when you have a network offering without a VR, at which point
>>> the metadata etc. is presented as the config drive. Happy to be corrected
>>> on this.
>>> 
>>> We did however have a really major gotcha 18 months ago – when a customer
>>> did a CloudStack upgrade and ended up with new unexpected config drives
>>> causing changes to all the VMware disk controller addressing – meaning VMs
>>> wouldn’t boot, couldn’t see disks, etc. If you use VMware I would test
>>> beforehand.
>>> 
>>> Regards,
>>> Dag Sonstebo
>>> Cloud Architect
>>> ShapeBlue
>>> 
>>> On 26/03/2018, 14:50, "Nux!"  wrote:
>>> 
>>>Hi,
>>> 
>>>I am interested in the ConfigDrive feature.
>>>Before I potentially waste time on it, is anyone around here using it
>>> or can clarify whether it's usable or not or gotchas etc?
>>> 
>>>Regards,
>>>Lucian
>>> 
>>>--
>>>Sent from the Delta quadrant using Borg technology!
>>> 
>>>Nux!
>>>www.nux.ro
>>> 
>>> 
>>> 
>>> dag.sonst...@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>>> @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: Welcoming Mike as the new Apache CloudStack VP

[Jayapal Uradi]

Congratulations, Milke!

-Jayapal

> On Mar 27, 2018, at 2:38 AM, Nitin Kumar Maharana 
>  wrote:
> 
> Congratulations, Mike!!
> 
> -
> Nitin
> On 26-Mar-2018, at 7:41 PM, Wido den Hollander 
> > wrote:
> 
> Hi all,
> 
> It's been a great pleasure working with the CloudStack project as the
> ACS VP over the past year.
> 
> A big thank you from my side for everybody involved with the project in
> the last year.
> 
> Hereby I would like to announce that Mike Tutkowski has been elected to
> replace me as the Apache Cloudstack VP in our annual VP rotation.
> 
> Mike has a long history with the project and I am are happy welcome him
> as the new VP for CloudStack.
> 
> Welcome Mike!
> 
> Thanks,
> 
> Wido
> 
> 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: Dockerizing Cloudstack package builders

[Khosrow Moossavi]

Thanks for the feedback Wido.

I, personally, wouldn't put them in *cloudstack* repo itself, since these
are complementary tools. To me it would
make more sense to put them under apache/ namespace on GitHub as we already
have bunch of apache/cloudstack-*
repos. And under apache/ or cloudstackl/ namespace on Docker Hub (whichever
makes more sense).

If community agrees with going forward with this proposal, I would be more
than happy to transfer ownership of
the GH and DH repos I created.

That's actually a great point. I was assuming these are going to be used by
only developers/maintainers which have

the source code at their disposals. I'm gonna wait for others
feedback/suggestions before enhancing this though.

On Mon, Mar 26, 2018 at 3:28 PM, Wido den Hollander  wrote:

>
>
> On 03/26/2018 06:21 PM, Khosrow Moossavi wrote:
> > Hi community
> >
> > To make building Cloudstack's RPM or DEB packages more easily, portable
> and
> > reduce the need to
> > have a *correct* hardware to build them, I've Dockerized them. This is
> > essentially a follow up of what
> > Wido had done (only for deb packages though).
> >
>
> Very nice! I didn't have the time to work on this, but it kept popping
> up. I'd love to have a automated builder on download.cloudstack.org
> which does this for us automatically.
>
> > The proposed Builders can be found here[1] and here[2] on Github and
> > here[3] and here[4] on Docker Hub.
> >
>
> Cool!
>
> > I would appreciate it if you can give your feedback of them and if need
> be,
> > promote them on the official wiki/doc/repo.
> >
>
> Getting them on a official repo should be possible I think, we could put
> them in the /packaging directory of our main repo. Or maybe request a
> second repo called 'cloudstack-docker' or something.
>
> Right now I see that your builder wants to have the cloudstack source
> ready to be used (just as I did), but how about adding the option where
> it downloads a tarball from the website if no source and just a version
> is provided? Or it can do a git clone from Github and check out a
> specific tag/version.
>
> Again, very much appreciated!
>
> Wido
>
> > [1]: https://github.com/khos2ow/cloudstack-rpm-builder
> > [2]: https://github.com/khos2ow/cloudstack-deb-builder
> > [3]: https://hub.docker.com/r/khos2ow/cloudstack-deb-builder/
> > [4]: https://hub.docker.com/r/khos2ow/cloudstack-rpm-builder/
> >
> > Thanks
> >
> > Khosrow Moossavi
> >
> > Cloud Infrastructure Developer
> >
> > t 514.447.3456
> >
> > 
> >
>

Re: Welcoming Mike as the new Apache CloudStack VP

[Nitin Kumar Maharana]

Congratulations, Mike!!

-
Nitin
On 26-Mar-2018, at 7:41 PM, Wido den Hollander 
> wrote:

Hi all,

It's been a great pleasure working with the CloudStack project as the
ACS VP over the past year.

A big thank you from my side for everybody involved with the project in
the last year.

Hereby I would like to announce that Mike Tutkowski has been elected to
replace me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him
as the new VP for CloudStack.

Welcome Mike!

Thanks,

Wido

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: Welcoming Mike as the new Apache CloudStack VP

[Rohit Yadav]

Congrats and welcome Mike!



- Rohit






From: Wido den Hollander 
Sent: Monday, March 26, 2018 7:41:02 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Welcoming Mike as the new Apache CloudStack VP

Hi all,

It's been a great pleasure working with the CloudStack project as the
ACS VP over the past year.

A big thank you from my side for everybody involved with the project in
the last year.

Hereby I would like to announce that Mike Tutkowski has been elected to
replace me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him
as the new VP for CloudStack.

Welcome Mike!

Thanks,

Wido

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

Re: Dockerizing Cloudstack package builders

[Wido den Hollander]

On 03/26/2018 06:21 PM, Khosrow Moossavi wrote:
> Hi community
> 
> To make building Cloudstack's RPM or DEB packages more easily, portable and
> reduce the need to
> have a *correct* hardware to build them, I've Dockerized them. This is
> essentially a follow up of what
> Wido had done (only for deb packages though).
> 

Very nice! I didn't have the time to work on this, but it kept popping
up. I'd love to have a automated builder on download.cloudstack.org
which does this for us automatically.

> The proposed Builders can be found here[1] and here[2] on Github and
> here[3] and here[4] on Docker Hub.
> 

Cool!

> I would appreciate it if you can give your feedback of them and if need be,
> promote them on the official wiki/doc/repo.
> 

Getting them on a official repo should be possible I think, we could put
them in the /packaging directory of our main repo. Or maybe request a
second repo called 'cloudstack-docker' or something.

Right now I see that your builder wants to have the cloudstack source
ready to be used (just as I did), but how about adding the option where
it downloads a tarball from the website if no source and just a version
is provided? Or it can do a git clone from Github and check out a
specific tag/version.

Again, very much appreciated!

Wido

> [1]: https://github.com/khos2ow/cloudstack-rpm-builder
> [2]: https://github.com/khos2ow/cloudstack-deb-builder
> [3]: https://hub.docker.com/r/khos2ow/cloudstack-deb-builder/
> [4]: https://hub.docker.com/r/khos2ow/cloudstack-rpm-builder/
> 
> Thanks
> 
> Khosrow Moossavi
> 
> Cloud Infrastructure Developer
> 
> t 514.447.3456
> 
> 
> 

Re: Welcoming Mike as the new Apache CloudStack VP

[David Mabry]

Congrats Mike!

On 3/26/18, 12:04 PM, "Andrija Panic"  wrote:

Congratulations Mike !




On 26 March 2018 at 18:46, Ron Wheeler 
wrote:

>
> Congratulations Mike!
>
> Ron
>
> On 26/03/2018 10:11 AM, Wido den Hollander wrote:
>
>> Hi all,
>>
>> It's been a great pleasure working with the CloudStack project as the
>> ACS VP over the past year.
>>
>> A big thank you from my side for everybody involved with the project in
>> the last year.
>>
>> Hereby I would like to announce that Mike Tutkowski has been elected to
>> replace me as the Apache Cloudstack VP in our annual VP rotation.
>>
>> Mike has a long history with the project and I am are happy welcome him
>> as the new VP for CloudStack.
>>
>> Welcome Mike!
>>
>> Thanks,
>>
>> Wido
>>
>>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>


-- 

Andrija Panić

Re: Welcoming Mike as the new Apache CloudStack VP

[Andrija Panic]

Congratulations Mike !




On 26 March 2018 at 18:46, Ron Wheeler 
wrote:

>
> Congratulations Mike!
>
> Ron
>
> On 26/03/2018 10:11 AM, Wido den Hollander wrote:
>
>> Hi all,
>>
>> It's been a great pleasure working with the CloudStack project as the
>> ACS VP over the past year.
>>
>> A big thank you from my side for everybody involved with the project in
>> the last year.
>>
>> Hereby I would like to announce that Mike Tutkowski has been elected to
>> replace me as the Apache Cloudstack VP in our annual VP rotation.
>>
>> Mike has a long history with the project and I am are happy welcome him
>> as the new VP for CloudStack.
>>
>> Welcome Mike!
>>
>> Thanks,
>>
>> Wido
>>
>>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwhee...@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>


-- 

Andrija Panić

Re: [VOTE] Move to Github issues

[Parth Patel]

+1

On Mon, 26 Mar 2018 at 21:25 Glenn Wagner 
wrote:

> +1
>
> glenn.wag...@shapeblue.com
> www.shapeblue.com
> Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape
> Town  7129South Africa
> @shapeblue
>
>
>
>
> -Original Message-
> From: David Mabry 
> Sent: Monday, 26 March 2018 4:51 PM
> To: dev@cloudstack.apache.org
> Cc: users 
> Subject: Re: [VOTE] Move to Github issues
>
> +1
>
> On 3/26/18, 8:05 AM, "Will Stevens"  wrote:
>
> +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 cwik
> i
> 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: Welcoming Mike as the new Apache CloudStack VP

[Ron Wheeler]

Congratulations Mike!

Ron
On 26/03/2018 10:11 AM, Wido den Hollander wrote:

Hi all,

It's been a great pleasure working with the CloudStack project as the
ACS VP over the past year.

A big thank you from my side for everybody involved with the project in
the last year.

Hereby I would like to announce that Mike Tutkowski has been elected to
replace me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him
as the new VP for CloudStack.

Welcome Mike!

Thanks,

Wido



--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

Re: Welcoming Mike as the new Apache CloudStack VP

[Gabriel Beims Bräscher]

Congratulations Mike!

Thank you for all the hard work Will.

2018-03-26 13:33 GMT-03:00 Giles Sirett :

> Wido - thanks for all of your hard work on the project.
>
> Mike - many congratulations
>
> Kind regards
> Giles
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Wido den Hollander 
> Sent: 26 March 2018 15:11
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: Welcoming Mike as the new Apache CloudStack VP
>
> Hi all,
>
> It's been a great pleasure working with the CloudStack project as the ACS
> VP over the past year.
>
> A big thank you from my side for everybody involved with the project in
> the last year.
>
> Hereby I would like to announce that Mike Tutkowski has been elected to
> replace me as the Apache Cloudstack VP in our annual VP rotation.
>
> Mike has a long history with the project and I am are happy welcome him as
> the new VP for CloudStack.
>
> Welcome Mike!
>
> Thanks,
>
> Wido
>

RE: Welcoming Mike as the new Apache CloudStack VP

[Paul Angus]

Thank you Wido & welcome Mike


Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Giles Sirett  
Sent: 26 March 2018 17:33
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: RE: Welcoming Mike as the new Apache CloudStack VP

Wido - thanks for all of your hard work on the project.

Mike - many congratulations

Kind regards
Giles

giles.sir...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 


-Original Message-
From: Wido den Hollander 
Sent: 26 March 2018 15:11
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Welcoming Mike as the new Apache CloudStack VP

Hi all,

It's been a great pleasure working with the CloudStack project as the ACS VP 
over the past year.

A big thank you from my side for everybody involved with the project in the 
last year.

Hereby I would like to announce that Mike Tutkowski has been elected to replace 
me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him as the 
new VP for CloudStack.

Welcome Mike!

Thanks,

Wido

RE: Welcoming Mike as the new Apache CloudStack VP

[Giles Sirett]

Wido - thanks for all of your hard work on the project.

Mike - many congratulations

Kind regards
Giles

giles.sir...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Wido den Hollander  
Sent: 26 March 2018 15:11
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Welcoming Mike as the new Apache CloudStack VP

Hi all,

It's been a great pleasure working with the CloudStack project as the ACS VP 
over the past year.

A big thank you from my side for everybody involved with the project in the 
last year.

Hereby I would like to announce that Mike Tutkowski has been elected to replace 
me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him as the 
new VP for CloudStack.

Welcome Mike!

Thanks,

Wido

Re: ConfigDrive status

[Nux!]

Thanks for all the feedback, I'll do some reading then.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "ilya musayev" 
> To: "dev" 
> Sent: Monday, 26 March, 2018 17:03:30
> Subject: Re: ConfigDrive status

> Lucian
> 
> We reported 3-4 issues with config drive. It’s being worked on. It does
> work - but not per agreed upon specifications.
> 
> See below
> 
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-10287
> https://issues.apache.org/jira/browse/CLOUDSTACK-10288
> https://issues.apache.org/jira/browse/CLOUDSTACK-10289
> https://issues.apache.org/jira/browse/CLOUDSTACK-10290
> 
> Regards
> Ilya
> 
> On Mon, Mar 26, 2018 at 8:58 AM Dag Sonstebo 
> wrote:
> 
>> Hi Lucian,
>>
>> I’m maybe not the right person to answer this – but my understanding is it
>> only kicks in when you have a network offering without a VR, at which point
>> the metadata etc. is presented as the config drive. Happy to be corrected
>> on this.
>>
>> We did however have a really major gotcha 18 months ago – when a customer
>> did a CloudStack upgrade and ended up with new unexpected config drives
>> causing changes to all the VMware disk controller addressing – meaning VMs
>> wouldn’t boot, couldn’t see disks, etc. If you use VMware I would test
>> beforehand.
>>
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>>
>> On 26/03/2018, 14:50, "Nux!"  wrote:
>>
>> Hi,
>>
>> I am interested in the ConfigDrive feature.
>> Before I potentially waste time on it, is anyone around here using it
>> or can clarify whether it's usable or not or gotchas etc?
>>
>> Regards,
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>>
>>
>> dag.sonst...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>>
>>
>>

Dockerizing Cloudstack package builders

[Khosrow Moossavi]

Hi community

To make building Cloudstack's RPM or DEB packages more easily, portable and
reduce the need to
have a *correct* hardware to build them, I've Dockerized them. This is
essentially a follow up of what
Wido had done (only for deb packages though).

The proposed Builders can be found here[1] and here[2] on Github and
here[3] and here[4] on Docker Hub.

I would appreciate it if you can give your feedback of them and if need be,
promote them on the official wiki/doc/repo.

[1]: https://github.com/khos2ow/cloudstack-rpm-builder
[2]: https://github.com/khos2ow/cloudstack-deb-builder
[3]: https://hub.docker.com/r/khos2ow/cloudstack-deb-builder/
[4]: https://hub.docker.com/r/khos2ow/cloudstack-rpm-builder/

Thanks

Khosrow Moossavi

Cloud Infrastructure Developer

t 514.447.3456

Re: ConfigDrive status

[ilya musayev]

Lucian

We reported 3-4 issues with config drive. It’s being worked on. It does
work - but not per agreed upon specifications.

See below


https://issues.apache.org/jira/browse/CLOUDSTACK-10287
https://issues.apache.org/jira/browse/CLOUDSTACK-10288
https://issues.apache.org/jira/browse/CLOUDSTACK-10289
https://issues.apache.org/jira/browse/CLOUDSTACK-10290

Regards
Ilya

On Mon, Mar 26, 2018 at 8:58 AM Dag Sonstebo 
wrote:

> Hi Lucian,
>
> I’m maybe not the right person to answer this – but my understanding is it
> only kicks in when you have a network offering without a VR, at which point
> the metadata etc. is presented as the config drive. Happy to be corrected
> on this.
>
> We did however have a really major gotcha 18 months ago – when a customer
> did a CloudStack upgrade and ended up with new unexpected config drives
> causing changes to all the VMware disk controller addressing – meaning VMs
> wouldn’t boot, couldn’t see disks, etc. If you use VMware I would test
> beforehand.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 26/03/2018, 14:50, "Nux!"  wrote:
>
> Hi,
>
> I am interested in the ConfigDrive feature.
> Before I potentially waste time on it, is anyone around here using it
> or can clarify whether it's usable or not or gotchas etc?
>
> Regards,
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: Welcoming Mike as the new Apache CloudStack VP

[Dag Sonstebo]

Thanks for the hard work Wido and welcome + congratulations Mike!

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 26/03/2018, 15:11, "Wido den Hollander"  wrote:

Hi all,

It's been a great pleasure working with the CloudStack project as the
ACS VP over the past year.

A big thank you from my side for everybody involved with the project in
the last year.

Hereby I would like to announce that Mike Tutkowski has been elected to
replace me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him
as the new VP for CloudStack.

Welcome Mike!

Thanks,

Wido



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Welcoming Mike as the new Apache CloudStack VP

[ilya musayev]

Welcome Mike, thank you Wido!

On Mon, Mar 26, 2018 at 8:59 AM Simon Weller 
wrote:

> Thanks for all of your hard work Wido, we really appreciate it.
>
>
> Congratulations Mike!
>
>
> - Si
>
> 
> From: Wido den Hollander 
> Sent: Monday, March 26, 2018 9:11 AM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: Welcoming Mike as the new Apache CloudStack VP
>
> Hi all,
>
> It's been a great pleasure working with the CloudStack project as the
> ACS VP over the past year.
>
> A big thank you from my side for everybody involved with the project in
> the last year.
>
> Hereby I would like to announce that Mike Tutkowski has been elected to
> replace me as the Apache Cloudstack VP in our annual VP rotation.
>
> Mike has a long history with the project and I am are happy welcome him
> as the new VP for CloudStack.
>
> Welcome Mike!
>
> Thanks,
>
> Wido
>

Re: Welcoming Mike as the new Apache CloudStack VP

[Simon Weller]

Thanks for all of your hard work Wido, we really appreciate it.


Congratulations Mike!


- Si


From: Wido den Hollander 
Sent: Monday, March 26, 2018 9:11 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Welcoming Mike as the new Apache CloudStack VP

Hi all,

It's been a great pleasure working with the CloudStack project as the
ACS VP over the past year.

A big thank you from my side for everybody involved with the project in
the last year.

Hereby I would like to announce that Mike Tutkowski has been elected to
replace me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him
as the new VP for CloudStack.

Welcome Mike!

Thanks,

Wido

Re: ConfigDrive status

[Dag Sonstebo]

Hi Lucian,

I’m maybe not the right person to answer this – but my understanding is it only 
kicks in when you have a network offering without a VR, at which point the 
metadata etc. is presented as the config drive. Happy to be corrected on this.

We did however have a really major gotcha 18 months ago – when a customer did a 
CloudStack upgrade and ended up with new unexpected config drives causing 
changes to all the VMware disk controller addressing – meaning VMs wouldn’t 
boot, couldn’t see disks, etc. If you use VMware I would test beforehand. 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 26/03/2018, 14:50, "Nux!"  wrote:

Hi,

I am interested in the ConfigDrive feature.
Before I potentially waste time on it, is anyone around here using it or 
can clarify whether it's usable or not or gotchas etc?

Regards,
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

RE: [VOTE] Move to Github issues

[Glenn Wagner]

+1 

glenn.wag...@shapeblue.com 
www.shapeblue.com
Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape Town  
7129South Africa
@shapeblue
  
 


-Original Message-
From: David Mabry  
Sent: Monday, 26 March 2018 4:51 PM
To: dev@cloudstack.apache.org
Cc: users 
Subject: Re: [VOTE] Move to Github issues

+1

On 3/26/18, 8:05 AM, "Will Stevens"  wrote:

+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: Welcoming Mike as the new Apache CloudStack VP

[Glenn Wagner]

Congrats Mike , Awesome news 

Regards
Glenn


glenn.wag...@shapeblue.com 
www.shapeblue.com
Winter Suite, 1st Floor, The Avenues, Drama Street, Somerset West, Cape Town  
7129South Africa
@shapeblue
  
 


-Original Message-
From: Wido den Hollander  
Sent: Monday, 26 March 2018 4:11 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Welcoming Mike as the new Apache CloudStack VP

Hi all,

It's been a great pleasure working with the CloudStack project as the ACS VP 
over the past year.

A big thank you from my side for everybody involved with the project in the 
last year.

Hereby I would like to announce that Mike Tutkowski has been elected to replace 
me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him as the 
new VP for CloudStack.

Welcome Mike!

Thanks,

Wido

Re: [VOTE] Move to Github issues

[David Mabry]

+1

On 3/26/18, 8:05 AM, "Will Stevens"  wrote:

+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: [VOTE] Move to Github issues

[Khosrow Moossavi]

+1


On Mon, Mar 26, 2018 at 9:05 AM, Will Stevens  wrote:

> +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: [VOTE] Move to Github issues

[Marc-Aurèle Brothier]

+1

On Mon, Mar 26, 2018 at 3:05 PM, Will Stevens  wrote:

> +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
> >
> >
> >
> >
>

Welcoming Mike as the new Apache CloudStack VP

[Wido den Hollander]

Hi all,

It's been a great pleasure working with the CloudStack project as the
ACS VP over the past year.

A big thank you from my side for everybody involved with the project in
the last year.

Hereby I would like to announce that Mike Tutkowski has been elected to
replace me as the Apache Cloudstack VP in our annual VP rotation.

Mike has a long history with the project and I am are happy welcome him
as the new VP for CloudStack.

Welcome Mike!

Thanks,

Wido

ConfigDrive status

[Nux!]

Hi,

I am interested in the ConfigDrive feature.
Before I potentially waste time on it, is anyone around here using it or can 
clarify whether it's usable or not or gotchas etc?

Regards,
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: [VOTE] Move to Github issues

[Simon Weller]

+1 (binding).



From: Rohit Yadav 
Sent: Monday, March 26, 2018 1:33 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [VOTE] Move to Github issues

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

Re: [VOTE] Move to Github issues

[Syed Ahmed]

+1
On Mon, Mar 26, 2018 at 6:05 AM Will Stevens  wrote:

> +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: [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: [VOTE] Move to Github issues

[Nicolas Vazquez]

+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: [VOTE] Move to Github issues

[Rafael Weingärtner]

+1

On Mon, Mar 26, 2018 at 5:06 AM, Dag Sonstebo 
wrote:

> +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
>
>
>
>


-- 
Rafael Weingärtner

Re: [VOTE] Move to Github issues

[Dag Sonstebo]

+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
  
 

Re: [VOTE] Move to Github issues

[Boris Stoyanov]

+1

> On 26 Mar 2018, at 10:21, Nux!  wrote:
> 
> +1
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> 
boris.stoya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

- Original Message -
>> From: "Rohit Yadav" 
>> To: "dev" , "users" 
>> Sent: Monday, 26 March, 2018 07:33:08
>> Subject: [VOTE] Move to Github issues
> 
>> 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

Re: [VOTE] Move to Github issues

[Nux!]

+1

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Rohit Yadav" 
> To: "dev" , "users" 
> Sent: Monday, 26 March, 2018 07:33:08
> Subject: [VOTE] Move to Github issues

> 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

Re: [VOTE] Move to Github issues

[Rene Moser]

+1

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

[Rohit Yadav]

All, I've started a voting thread for the proposal.


Please do vote and share any thoughts, questions that we've not already 
discussed. Thanks.


- Rohit






From: Rohit Yadav 
Sent: Friday, March 23, 2018 6:54:55 PM
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: Re: [DISCUSS] Relax strict requirement of JIRA ID for PRs

Thanks all for your feedback. Since it's been positive so far, I'll start a 
vote on Monday to formalize this.

In the meanwhile, please keep sharing your feedback and opinion. Thanks (and 
happy weekends).


- Rohit






From: Syed Ahmed 
Sent: Thursday, March 22, 2018 12:51:01 AM
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: Re: [DISCUSS] Relax strict requirement of JIRA ID for PRs

+1 To Rohit’s suggestion
On Wed, Mar 21, 2018 at 11:35 AM Khosrow Moossavi 
wrote:

> Thanks Rohit, that's a really great sum-up of proposition!
>
> According to the private issue topic, as far as I understand, we don't have
> any private issue per se, unless they are security, vulnerability
> or CVE related and the process of reporting them -being really private
> until they are fixed- are well-defined. So I would say the mentioned
> security@ ML and have an interim ticket in Jira or the ML itself works and
> when the fix is out, for sake of archive, the issue can be created
> in GH and set as closed right away.
>
>
>
> On Wed, Mar 21, 2018 at 6:38 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > I think that works as well. Let's see what others think about it.
> >
> > On Wed, Mar 21, 2018 at 4:15 AM, Rohit Yadav 
> > wrote:
> >
> > > Thanks Rafael for your inputs. You're right about access control
> > > limitation on Github.
> > >
> > >
> > > However, I think having another repository to track security stuff can
> > add
> > > overhead (and to manage its custom ACLs with INFRA, as all cloudstack*
> > > repos are allowed access to all PMC/committers now).
> > >
> > >
> > > Users are advised to report security issues on security@, so how about
> > we
> > > continue to use JIRA for security issues (logging, tracking, and
> > > discussions) and limit the proposed change to just moving to Github
> > issues
> > > as a first step?
> > >
> > >
> > > - Rohit
> > >
> > > 
> > >
> > >
> > >
> > > 
> > > From: Rafael Weingärtner 
> > > Sent: Tuesday, March 20, 2018 11:46:32 PM
> > > To: dev
> > > Cc: us...@cloudstack.apache.org
> > > Subject: Re: [DISCUSS] Relax strict requirement of JIRA ID for PRs
> > >
> > > It looks like you have done all of the homework here. If it comes to a
> > > vote, I am +1 on migrating issues to Github, and even the Wiki in the
> > > future.  The Github would be able to pretty much provide everything
> that
> > we
> > > have in both Wiki and Jira. Therefore, it feels better to work on a
> > single
> > > platform than to spread information across them. However, we still have
> > one
> > > problem. The security issues/tickets in Jira. How can we manage them in
> > > Github? As far as I know, there is no way to control the access to
> > certain
> > > issues/tickets in Github.
> > >
> > > To tackle that problem with security issues we could open a ticket with
> > > Github; and in the meantime, we could set up a private repository in
> the
> > > Apache organization to hold the security issues (e.g.
> > cloudstack-security).
> > >
> > >
> > > Thanks Rohit.
> > >
> > >
> > >
> > > On Mon, Mar 19, 2018 at 7:58 AM, Rohit Yadav <
> rohit.ya...@shapeblue.com>
> > > wrote:
> > >
> > > > (I've cc-ed user ML to gather feedback from users for this email as
> > > well.)
> > > > All,
> > > > Thank you for your feedbacks, discussions, and suggestions. I have
> > tried
> > > > to take on board all the feedback from the discussion and I propose
> the
> > > > following:
> > > > # Problem
> > > > Let me summarize the problems we're facing and propose some solution
> > > > (which may require voting) in the next section:
> > > > - Search:
> > > > The source of truth is in the git repository (Github or asf mirror),
> > > > however, our issue tracking and wiki systems are different. Therefore
> > any
> > > > task requires us to move back and forth between these various
> > > > portals/systems. As an example - a contributor trying to find whether
> > an
> > > > issue was fixed, requires them to search both JIRA, Github for pull
> > > > requests or commits (and sometimes the release notes and MLs).
> > > > - Audience/Platform:
> > > > From an audience's perspective, the user ML and JIRA issue are for
> > users
> > > > to be able to reach the community and seek help with a bug or
> request a
> > > new
> > > > feature.
> > > > The dev 

Re: [VOTE] Move to Github issues

[Wido den Hollander]

+1

On 03/26/2018 08:33 AM, 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
> 

[VOTE] Move to Github issues

[Rohit Yadav]

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

Re: [DISCUSS] Enhancement: Use CA framework to enable secured live KVM VM migration

[Rohit Yadav]

Hi Wido,


Try this: 
https://github.com/apache/cloudstack/pull/2505/commits/9e6bd8aedb7e3a555bcb64e9220b9facb5aef879


CloudStack attempts to make a libvirt connection to the host's private ip using 
the qemu+tls:// uri to detect if libvirtd if running with tls enabled or not 
(default tls port 16514). This check does not involve reading libvirtd's config 
file.


For an already added/connected KVM host, the certificates are renewed via 
cmd-answer pattern and not ssh-based provisioning. SSH-based certificate 
provisioning is only used when adding a new host.


The CA framework uses a ca strictness global setting to ascertain whether the 
clients connecting to a management need to present certificates or not. This 
global setting is true only for fresh deployments, otherwise false for 
upgraded/existing ones. If this setting is true in your env, but you don't have 
certificates setup on KVM hosts, management server won't allow that agent to 
connect; if it is false, there will be no issues.


For out-of-band addition of host such as yours, you can either use a sudoer 
user [1] to add a KVM host, or implement your own workflow, for example:


Call the provisionCertificate API (let's say from the KVM host) and passing 
suitable API arguments such as the host's hostname, ips etc. From the response, 
save the files (cloud.crt, cloud.key and cloud.ca.crt) and create the keystore 
(cloud.jks, save its passphrase in agent.properties file) at agent's 
/etc/cloudstack/agent. For reference, you can see how the keystore scripts do 
this [2].


[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+non-root+user+to+add+KVM+hypervisor

[2] https://github.com/apache/cloudstack/tree/master/scripts/util



- Rohit






From: Wido den Hollander 
Sent: Saturday, March 24, 2018 4:42:45 PM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Enhancement: Use CA framework to enable secured live KVM 
VM migration



On 03/23/2018 11:21 AM, Rohit Yadav wrote:
> Wido - fair point, considering this I'll add some notes in our release notes. 
> With the suggested change, during pkg upgrade libvirtd will not be 
> reconfigured:
>
> https://github.com/shapeblue/cloudstack-apple/pull/65/commits/9dd93ee3c7b0a31cbd262a51aaed2b325decfbd8
>

404 ;)

>
> Instead, KVM hosts that don't meet following conditions will show up as 
> 'unsecure' when they connect to management server:
>
> - Host does not have certificates setup at /etc/cloudstack/agent
>
> - Host's libvirtd is not tls enabled with any provisioned certificate
>

How are you going to check the last part? Would you have the cloudstack
agent read the libvirt config files? That might not work as you might
have SELinux or AppArmor preventing that.

I don't know you can ask libvirt that information when connected to it.

>
> The admin can then simply choose to provision certificate to secure 
> 'unsecure' hosts post upgrade via api or the newly added button. This process 
> will provision (or renew) certificates, configure only tls settings in 
> libvirtd and restart libvirtd and then restart the agent. See the PR for 
> details. Thanks.
>

Yes, but that will SSH to the hosts, correct? We for example don't have
SSH from the mgmt server enabled and only populate agent.properties on
the KVM hosts when we add them to CloudStack.

Wido

>
>
> - Rohit
>
> 
>
>
>
> 
> From: Wido den Hollander 
> Sent: Thursday, March 22, 2018 10:14:31 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Enhancement: Use CA framework to enable secured live 
> KVM VM migration
>
>
>
> On 03/21/2018 10:06 AM, Rohit Yadav wrote:
>> Thanks Wido for your comments.
>>
>>
>> Yes, for any changes to libvirtd the proposal is to re-use 
>> cloudstack-setup-agent which in fact reconfigures libvirtd config at the 
>> time of the addition of host and also configure iptables rule. As part of 
>> upgrading a KVM agent, the post-install script (part of deb/rpm pkg) can 
>> also run the same to secure libvirt tls configuration only on KVM hosts that 
>> have any existing certificates/keystore.
>>
>
> Hmm, we might want to be careful with a postinst. I'm not against it
> being handled by a postinst, but we should watch out with overwriting
> config files without the user knowing.
>
> Wido
>
>>
>> - Rohit
>>
>> 
>>
>>
>>
>> 
>> From: Wido den Hollander 
>> Sent: Wednesday, March 21, 2018 1:38:19 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [DISCUSS] Enhancement: Use CA framework to enable secured live 
>> KVM VM migration
>>
>>
>>
>> On 03/21/2018 08:05 AM, Rohit Yadav wrote:
>>> All,
>>>
>>>
>>> With the introduction of a native CA framework in CloudStack, with 4.11+ it 
>>> will be used to secure addition of KVM hosts and agents (cpvm, ssvm). 
>>> However, the KVM