Re: [NOTICE] Remove branches 4.1l10n, 4.2-*, 4.3.0-forward, and 4.4-* from Apache CloudStack official repository

[Rafael Weingärtner]

The following branches were removed from our official repository.


   - 4.1l10n
   - 4.2-forward
   - 4.2-workplace
   - 4.3.0-forward
   - 4.4-automation
   - 4.4-forward
   - 4.4-forward-iam
   - 4.4-forward-iam-disabled

Thanks for the understanding.


On Thu, Mar 22, 2018 at 7:27 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Final warning, these branches will be deleted today 17:00 (UTC-03:00). If
> you disagree, please do so before the deadline.
>
>
> On Tue, Mar 13, 2018 at 11:33 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
>> Following the protocol defined in [1], this is the notice email regarding
>> the removal branches from Apache CloudStack official repository. The Jira
>> ticket for the branches removal is https://issues.apache.org/jira
>> /browse/CLOUDSTACK-10324. The branches that will be removed are the
>> following:
>>
>>- 4.1l10n
>>- 4.2-forward
>>- 4.2-workplace
>>- 4.3.0-forward
>>- 4.4-automation
>>- 4.4-forward
>>- 4.4-forward-iam
>>- 4.4-forward-iam-disabled
>>
>>
>> If you have objections, please do share your concerns before the
>> deletion. The removal will happen on 22/March/2018.
>> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Clean
>> +up+old+and+obsolete+branches+protocol
>>
>> --
>> Rafael Weingärtner
>>
>
>
>
> --
> Rafael Weingärtner
>



-- 
Rafael Weingärtner

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

[Wido den Hollander]

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 host agent may be secured while it communicates to the 
>> management server, the live VM migration still happens on insecure tcp 
>> connection.
>>
>>
>> It is proposed to re-use the existing mechanism introduced in 4.11 and 
>> re-use host certificates that are used to secure a KVM host to secure 
>> libvirt for allowing secured TLS-enabled VM migration. Further, the UI may 
>> be enhanced to discover unsecured KVM hosts and allow securing (or 
>> renewal/provisioning of certificates) through a button. Please find the FS 
>> for the proposed enhancement:
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Secure+Live+VM+Migration+for+KVM
>>
> 
> Seems good! As long as we make sure that only cloudstack-setup-agent
> touches the libvirt config files I'm good with it.
> 
> Many people (like us) have the libvirt config files managed through a
> tool like Salt/Puppet/Chef and don't like it when daemons suddenly start
> changing configuration files.
> 
> But this looks good to me!
> 
> Wido
> 
>>
>> - Rohit
>>
>> 
>>
>>
>>
>> rohit.ya...@shapeblue.com
>> 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: 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



On Thu, Mar 22, 2018 at 10:59 AM, Khosrow Moossavi 
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 
> 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
> >
> > 
> >
> > 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"  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*
> > > >
> > > >
> > > > * *
> > > >
> > >
> >
>

Re: Marketing CCC Montreal

[Khosrow Moossavi]

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 
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
>
> 
>
> On Thu, Mar 22, 2018 at 10:49 AM, Khosrow Moossavi  >
> 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"  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*
> > >
> > >
> > > * *
> > >
> >
>

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



On Thu, Mar 22, 2018 at 10:49 AM, Khosrow Moossavi 
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"  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*
> >
> >
> > * *
> >
>

Re: Marketing CCC Montreal

[Khosrow Moossavi]

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"  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*
>
>
> * *
>

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*


* *

Re: [NOTICE] Remove branches 4.1l10n, 4.2-*, 4.3.0-forward, and 4.4-* from Apache CloudStack official repository

[Rafael Weingärtner]

 Final warning, these branches will be deleted today 17:00 (UTC-03:00). If
you disagree, please do so before the deadline.


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

> Following the protocol defined in [1], this is the notice email regarding
> the removal branches from Apache CloudStack official repository. The Jira
> ticket for the branches removal is https://issues.apache.org/
> jira/browse/CLOUDSTACK-10324. The branches that will be removed are the
> following:
>
>- 4.1l10n
>- 4.2-forward
>- 4.2-workplace
>- 4.3.0-forward
>- 4.4-automation
>- 4.4-forward
>- 4.4-forward-iam
>- 4.4-forward-iam-disabled
>
>
> If you have objections, please do share your concerns before the deletion.
> The removal will happen on 22/March/2018.
> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> Clean+up+old+and+obsolete+branches+protocol
>
> --
> Rafael Weingärtner
>



-- 
Rafael Weingärtner

Re: [DISCUSS] new way of github working

[Rafael Weingärtner]

These last two months I have experimented working with both ways
(maintaining the merge commit and squashing and merging). When I
experimented using “squash+merge”, the only time I was maintaining the
merge commit is during merge-forwards.

I liked working with “squash+merge” approach. This allowed me to split my
PRs into multiple commits, which facilitates for reviewers. For instance,
it is interesting to split code changes and formatting ones. Moreover,
during the review of the PR, we can create a history of changes that were
created because of reviews. Then, when everything is ready to be merged, we
can squash everything (using Github UI), and merge the PR as a single
commit. Of course, to adopt this method we need to present single changes
per PR. Meaning, a PR should not address multiple issues at the same time.

One thing we need to change though. When merging forward we must customize
the “forward merge” message. Otherwise, we end up with a bunch of commits
that have the same commit title (e.g. “merge 4.11”). We can use messages
such as “Froward merge # from ”, and then add in the body
of the commit the title of the commit that was used to merge the
#.

What do you guys think? Let’s finalize this discussion and define a
standard to adopt. Then, I can change the merging tools (are people using
them after we moved to Github?) accordingly (if needed). I can also update
the merge document that is on our wiki page.

On Mon, Jan 15, 2018 at 6:47 PM, Rene Moser  wrote:

>
>
> On 01/15/2018 09:06 PM, Rafael Weingärtner 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 …
>
> +1 to allow merge commits on master branch to keep history of a series
> of patches when they help to understand the change.
>
> René
>
>
>


-- 
Rafael Weingärtner

Re: Notice that Gabriel Bräscher now works at PCextreme

[Nux!]

Great news, well done!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Wido den Hollander" 
> To: "dev" 
> Cc: gabrasc...@gmail.com
> Sent: Tuesday, 20 March, 2018 13:50:57
> Subject: Notice that Gabriel Bräscher now works at PCextreme

> Hi,
> 
> Just wanted to let you know that Gabriel Bräscher started working at
> PCextreme this week.
> 
> He'll be committing and developing on CloudStack for PCextreme and the
> community.
> 
> Just so everybody knows that we are colleagues now.
> 
> Let's make CloudStack even better!
> 
> Wido

Re: New committer: Dag Sonstebo

[Nux!]

Congrats :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "John Kinsella" 
> To: "dev" 
> Sent: Tuesday, 20 March, 2018 13:58:22
> Subject: New committer: Dag Sonstebo

> The Project Management Committee (PMC) for Apache CloudStack has
> invited Dag Sonsteboto become a committer and we are pleased to
> announce that he has accepted.
> 
> I’ll take a moment here to remind folks that being an ASF committer
> isn’t purely about code - Dag has been helping out for quite a while
> on users@, and seems to have a strong interest around ACS and the
> community. We welcome this activity, and encourage others to help
> out as they can - it doesn’t necessarily have to be purely code-related.
> 
> Being a committer enables easier contribution to the project since
> there is no need to go via the patch submission process. This should
> enable better productivity.
> 
> Please join me in welcoming Dag!
> 
> John