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: Release Notes

[Paul Angus]

Thanks Will, this works great!



Kind regards,

Paul Angus

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://raw.githubusercontent.com/cloudops/media/master/cloudops.png]<https://goo.gl/NYZ8KK>


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

On Wed, Jan 3, 2018 at 2:15 PM, Will Stevens 
<wstev...@cloudops.com<mailto: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://raw.githubusercontent.com/cloudops/media/master/cloudops.png]<https://goo.gl/NYZ8KK>

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

Thanks guys!







Kind regards,



Paul Angus



paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
@shapeblue




From: williamstev...@gmail.com<mailto:williamstev...@gmail.com> 
[mailto:williamstev...@gmail.com<mailto:williamstev...@gmail.com>] On Behalf Of 
Will Stevens
Sent: 03 January 2018 16:01
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Cc: Paul Angus <paul.an...@shapeblue.com<mailto: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://raw.githubusercontent.com/cloudops/media/master/cloudops.png]<https://goo.gl/NYZ8KK>



On Wed, Jan 3, 2018 at 10:57 AM, Rafael Weingärtner 
<rafaelweingart...@gmail.com<mailto: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<mailto: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<mailto: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]

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

[Paul Angus]

Thanks guys!



Kind regards,

Paul Angus

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://raw.githubusercontent.com/cloudops/media/master/cloudops.png]<https://goo.gl/NYZ8KK>


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

On Wed, Jan 3, 2018 at 10:57 AM, Rafael Weingärtner 
<rafaelweingart...@gmail.com<mailto: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<mailto: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<mailto: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  |
> >
> 

Re: Release Notes

[Will Stevens]

  | 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  |
> > >
> > > | |  ||
> > > |  | connect hosts
>   |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2109`_ | CLOUDSTACK-9922_   | Bug
> > > | Major| Unable  to use 8081 port for Load balancing
>   |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#2044`_ | CLOUDSTACK-9877_   | Improvement
> > > | Major| remove fully cloned deleted templates from primary
> storage |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | master  | `#1959`_ | CLOUDSTACK-9786_   | Bug
> > > | Major| API reference guide entry for associateIpAddress needs a
>  |
> > >
> > > | |  ||
> > > |  | fix
>   |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > > | 4.10*   | `#2176`_ ||
> > > |  | Travis: use oraclejdk8 for 4.10+
>  |
> > >
> > > +-+--++-
> > > --+--+--
> > > --+
> > >
> > >
> > >
> > > .. _`#2211`: https://github.com/apache/cloudstack/pull/2211
> > >
> > > .. _CLOUDSTACK-10013: https://issues.apache.org/
> > > jira/browse/CLOUDSTACK-10013
> > >
> > > .. _`#2359`: https://github.com/apache/cloudstack/pull/2359
> > >
> > > .. _`#2124`: https://github.com/apache/cloudstack/pull/2124
> > >
> > > .. _CLOUDSTACK-9432: https://issues.apache.org/
> > jira/browse/CLOUDSTACK-9432
> > >
> > > .. _`#1981`: https://github.com/apache/cloudstack/pull/1981
> > >
> > > .. _CLOUDSTACK-9806: https://issues.apache.org/
> > jira/browse/CLOUDSTACK-9806
> > >
> > > .. _`#2005`: https://github.com/apache/cloudstack/pull/2005
> > >
> > > .. _CLOUDSTACK-9450: https://issues.apache.org/
> > jira/browse/CLOUDSTACK-9450
> > >
> > > .. _`#2004`: https://github.com/apache/cloudstack/pull/2004
> > >
> > > .. _CLOUDSTACK-9832: https://issues.apache.org/
> > jira/browse/CLOUDSTACK-9832
> > >
> > > .. _`#2238`: https://github.com/apache/cloudstack/

Re: Release Notes

[Rafael Weingärtner]

-+--
> > --+
> >
> > | 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  |
> >
> > | |  ||
> > |  | connect hosts  |
> >
> > +-+--++-
> > --+--+--
> > --+
> >
> > | master  | `#2109`_ | CLOUDSTACK-9922_   | Bug
> > | Major| Unable  to use 8081 port for Load balancing|
> >
> > +-+--++-
> > --+--+--
> > --+
> >
> > | master  | `#2044`_ | CLOUDSTACK-9877_   | Improvement
> > | Major| remove fully cloned deleted templates from primary storage |
> >
> > +-+--++-
> > --+--+--
> > --+
> >
> > | master  | `#1959`_ | CLOUDSTACK-9786_   | Bug
> > | Major| API reference guide entry for associateIpAddress needs a   |
> >
> > | |  ||
> > |  | fix|
> >
> > +-+--++-
> > --+--+--
> > --+
> >
> > | 4.10*   | `#2176`_ ||
> > |  | Travis: use oraclejdk8 for 4.10+   |
> >
> > +-+--++-
> > --+--+--
> > --+
> >
> >
> >
> > .. _`#2211`: https://github.com/apache/cloudstack/pull/2211
> >
> > .. _CLOUDSTACK-10013: https://issues.apache.org/
> > jira/browse/CLOUDSTACK-10013
> >
> > .. _`#2359`: https://github.com/apache/cloudstack/pull/2359
> >
> > .. _`#2124`: https://github.com/apache/cloudstack/pull/2124
> >
> > .. _CLOUDSTACK-9432: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9432
> >
> > .. _`#1981`: https://github.com/apache/cloudstack/pull/1981
> >
> > .. _CLOUDSTACK-9806: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9806
> >
> > .. _`#2005`: https://github.com/apache/cloudstack/pull/2005
> >
> > .. _CLOUDSTACK-9450: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9450
> >
> > .. _`#2004`: https://github.com/apache/cloudstack/pull/2004
> >
> > .. _CLOUDSTACK-9832: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9832
> >
> > .. _`#2238`: https://github.com/apache/cloudstack/pull/2238
> >
> > .. _CLOUDSTACK-10053: https://issues.apache.org/
> > jira/browse/CLOUDSTACK-10053
> >
> > .. _`#2268`: https://github.com/apache/cloudstack/pull/2268
> >
> > .. _CLOUDSTACK-10081: https://issues.apache.org/
> > jira/browse/CLOUDSTACK-10081
> >
> > .. _`#2054`: https://github.com/apache/cloudstack/pull/2054
> >
> > .. _CLOUDSTACK-9886: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9886
> >
> > .. _`#2109`: https://github.com/apache/cloudstack/pull/2109
> >
> > .. _CLOUDSTACK-9922: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9922
> >
> > .. _`#2044`: https://github.com/apache/cloudstack/pull/2044
> >
> > .. _CLOUDSTACK-9877: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9877
> >
> > .. _`#1959`: https://github.com/apache/cloudstack/pull/1959
> >
> > .. _CLOUDSTACK-9786: https://issues.apache.org/
> jira/browse/CLOUDSTACK-9786
> >
> > .. _`#2176`: https://github.com/apache/cloudstack/pull/2176
> >
> >
> >
> >
> >
> > Kind regards,
> >

Re: Release Notes

[Will Stevens]

  | connect hosts  |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2109`_ | CLOUDSTACK-9922_   | Bug
> | Major| Unable  to use 8081 port for Load balancing|
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#2044`_ | CLOUDSTACK-9877_   | Improvement
> | Major| remove fully cloned deleted templates from primary storage |
>
> +-+--++-
> --+--+--
> --+
>
> | master  | `#1959`_ | CLOUDSTACK-9786_   | Bug
> | Major| API reference guide entry for associateIpAddress needs a   |
>
> | |  ||
> |  | fix|
>
> +-+--++-
> --+--+--
> --+
>
> | 4.10*   | `#2176`_ ||
> |  | Travis: use oraclejdk8 for 4.10+   |
>
> +-+--++-
> --+--+--
> --+
>
>
>
> .. _`#2211`: https://github.com/apache/cloudstack/pull/2211
>
> .. _CLOUDSTACK-10013: https://issues.apache.org/
> jira/browse/CLOUDSTACK-10013
>
> .. _`#2359`: https://github.com/apache/cloudstack/pull/2359
>
> .. _`#2124`: https://github.com/apache/cloudstack/pull/2124
>
> .. _CLOUDSTACK-9432: https://issues.apache.org/jira/browse/CLOUDSTACK-9432
>
> .. _`#1981`: https://github.com/apache/cloudstack/pull/1981
>
> .. _CLOUDSTACK-9806: https://issues.apache.org/jira/browse/CLOUDSTACK-9806
>
> .. _`#2005`: https://github.com/apache/cloudstack/pull/2005
>
> .. _CLOUDSTACK-9450: https://issues.apache.org/jira/browse/CLOUDSTACK-9450
>
> .. _`#2004`: https://github.com/apache/cloudstack/pull/2004
>
> .. _CLOUDSTACK-9832: https://issues.apache.org/jira/browse/CLOUDSTACK-9832
>
> .. _`#2238`: https://github.com/apache/cloudstack/pull/2238
>
> .. _CLOUDSTACK-10053: https://issues.apache.org/
> jira/browse/CLOUDSTACK-10053
>
> .. _`#2268`: https://github.com/apache/cloudstack/pull/2268
>
> .. _CLOUDSTACK-10081: https://issues.apache.org/
> jira/browse/CLOUDSTACK-10081
>
> .. _`#2054`: https://github.com/apache/cloudstack/pull/2054
>
> .. _CLOUDSTACK-9886: https://issues.apache.org/jira/browse/CLOUDSTACK-9886
>
> .. _`#2109`: https://github.com/apache/cloudstack/pull/2109
>
> .. _CLOUDSTACK-9922: https://issues.apache.org/jira/browse/CLOUDSTACK-9922
>
> .. _`#2044`: https://github.com/apache/cloudstack/pull/2044
>
> .. _CLOUDSTACK-9877: https://issues.apache.org/jira/browse/CLOUDSTACK-9877
>
> .. _`#1959`: https://github.com/apache/cloudstack/pull/1959
>
> .. _CLOUDSTACK-9786: https://issues.apache.org/jira/browse/CLOUDSTACK-9786
>
> .. _`#2176`: https://github.com/apache/cloudstack/pull/2176
>
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>
> *From:* Paul Angus
> *Sent:* 29 December 2017 07:19
> *To:* 'Will Stevens' <wstev...@cloudops.com>
> *Cc:* dev@cloudstack.apache.org
> *Subject:* RE: Release Notes
>
>
>
> Thanks Will!
>
>
>
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
>
>
> *From:* williamstev...@gmail.com [mailto:williamstev...@gmail.com
> <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'

RE: Release Notes

[Paul Angus]

|
+-+--++---+--++
| 4.10*   | `#2176`_ ||   | 
 | Travis: use oraclejdk8 for 4.10+   |
+-+--++---+--++

.. _`#2211`: https://github.com/apache/cloudstack/pull/2211
.. _CLOUDSTACK-10013: https://issues.apache.org/jira/browse/CLOUDSTACK-10013
.. _`#2359`: https://github.com/apache/cloudstack/pull/2359
.. _`#2124`: https://github.com/apache/cloudstack/pull/2124
.. _CLOUDSTACK-9432: https://issues.apache.org/jira/browse/CLOUDSTACK-9432
.. _`#1981`: https://github.com/apache/cloudstack/pull/1981
.. _CLOUDSTACK-9806: https://issues.apache.org/jira/browse/CLOUDSTACK-9806
.. _`#2005`: https://github.com/apache/cloudstack/pull/2005
.. _CLOUDSTACK-9450: https://issues.apache.org/jira/browse/CLOUDSTACK-9450
.. _`#2004`: https://github.com/apache/cloudstack/pull/2004
.. _CLOUDSTACK-9832: https://issues.apache.org/jira/browse/CLOUDSTACK-9832
.. _`#2238`: https://github.com/apache/cloudstack/pull/2238
.. _CLOUDSTACK-10053: https://issues.apache.org/jira/browse/CLOUDSTACK-10053
.. _`#2268`: https://github.com/apache/cloudstack/pull/2268
.. _CLOUDSTACK-10081: https://issues.apache.org/jira/browse/CLOUDSTACK-10081
.. _`#2054`: https://github.com/apache/cloudstack/pull/2054
.. _CLOUDSTACK-9886: https://issues.apache.org/jira/browse/CLOUDSTACK-9886
.. _`#2109`: https://github.com/apache/cloudstack/pull/2109
.. _CLOUDSTACK-9922: https://issues.apache.org/jira/browse/CLOUDSTACK-9922
.. _`#2044`: https://github.com/apache/cloudstack/pull/2044
.. _CLOUDSTACK-9877: https://issues.apache.org/jira/browse/CLOUDSTACK-9877
.. _`#1959`: https://github.com/apache/cloudstack/pull/1959
.. _CLOUDSTACK-9786: https://issues.apache.org/jira/browse/CLOUDSTACK-9786
.. _`#2176`: https://github.com/apache/cloudstack/pull/2176


Kind regards,

Paul Angus


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

From: Paul Angus
Sent: 29 December 2017 07:19
To: 'Will Stevens' <wstev...@cloudops.com>
Cc: dev@cloudstack.apache.org
Subject: RE: Release Notes

Thanks Will!



Kind regards,

Paul Angus

From: williamstev...@gmail.com<mailto: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<mailto:paul.an...@shapeblue.com>>
Cc: dev@cloudstack.apache.org<mailto: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://raw.githubusercontent.com/cloudops/media/master/cloudops.png]<https://goo.gl/NYZ8KK>

On Thu, Dec 28, 2017 at 12:01 PM, Paul Angus 
<paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>> wrote:
Cheers – enjoy the snow!



Kind regards,

Paul Angus


paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
@shapeblue



From: williamstev...@gmail.com<mailto:williamstev...@gmail.com> 
[mailto: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<mailto:paul.an...@shapeblue.com>>
Cc: dev@cloudstack.apache.org<mailto: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<mailto: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<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://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>

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

[Rohit Yadav]

Paul,


Last time when I updated the notes for 4.9.x I made a new script that reads the 
data/commits from pull requests and git commits. Git commits are by far the 
most reliable way to get list of resolved CLOUDSTACK- issues and link to 
PRs, the general idea is to get git log between two tags say git log 
4.10.0.0..HEAD as a log/txt files and use the script to generate the list of 
resolved issues table:


https://github.com/apache/cloudstack-docs-rn/blob/master/utils/issues.py


I'll further simplify and update this script soon.


- Rohit

<https://cloudstack.apache.org>




From: Paul Angus <paul.an...@shapeblue.com>
Sent: Friday, December 29, 2017 12:48:35 PM
To: Will Stevens
Cc: dev@cloudstack.apache.org
Subject: RE: Release Notes

Thanks Will!



Kind regards,

Paul Angus

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://raw.githubusercontent.com/cloudops/media/master/cloudops.png]<https://goo.gl/NYZ8KK>


paul.an...@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
  
 

On Thu, Dec 28, 2017 at 12:01 PM, Paul Angus 
<paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>> wrote:
Cheers – enjoy the snow!



Kind regards,

Paul Angus


paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
@shapeblue



From: williamstev...@gmail.com<mailto:williamstev...@gmail.com> 
[mailto: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<mailto:paul.an...@shapeblue.com>>
Cc: dev@cloudstack.apache.org<mailto: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<mailto: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<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://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<mailto:pd...@cloudops.com>]
Sent: 26 December 2017 16:00
To: dev@cloudstack.apache.org<mailto: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<mailto: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<mailto:paul.an...@shap

RE: Release Notes

[Paul Angus]

Thanks Will!



Kind regards,

Paul Angus

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://raw.githubusercontent.com/cloudops/media/master/cloudops.png]<https://goo.gl/NYZ8KK>


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

On Thu, Dec 28, 2017 at 12:01 PM, Paul Angus 
<paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>> wrote:
Cheers – enjoy the snow!



Kind regards,

Paul Angus


paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
@shapeblue



From: williamstev...@gmail.com<mailto:williamstev...@gmail.com> 
[mailto: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<mailto:paul.an...@shapeblue.com>>
Cc: dev@cloudstack.apache.org<mailto: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<mailto: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<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://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<mailto:pd...@cloudops.com>]
Sent: 26 December 2017 16:00
To: dev@cloudstack.apache.org<mailto: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<mailto: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<mailto:paul.an...@shapeblue.com>
> www.shapeblue.com<http://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

[Paul Angus]

Cheers – enjoy the snow!



Kind regards,

Paul Angus

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<mailto: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<mailto:paul.an...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




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<mailto:pd...@cloudops.com>]
Sent: 26 December 2017 16:00
To: dev@cloudstack.apache.org<mailto: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<mailto: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<mailto:paul.an...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 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" <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  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 <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  WC2N 4HSUK @shapeblue
> >
> >
> >
> >
>

RE: Release Notes

[Paul Angus]

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 <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  WC2N 4HSUK @shapeblue
>
>
>
>

Re: Release Notes

[Pierre-Luc Dion]

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: release notes

[Erik Weber]

@daan: looking at the pull request for CLOUDSTACK-8545 (out of band
migration) at https://github.com/apache/cloudstack/pull/466/files it seems
to call the setting `router.reboot.when.migrated`, could you verify which
one to use?

at line 71 and 73 in the patch it also introduces two new configkeys
(routerVersionCheckEnabled
and UseExternalDnsServers), is that a glip or intentional? if a glip, will
it cause problems?

-- 
Erik

On Thu, Jun 25, 2015 at 8:14 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 no, though that's debatable: one fix is that adding the same public
 key to a domain under a different name no longer works. It is a fix
 for retrieving keys consistently. retrieving the second name would
 return the key with the first name. Now it can not be entered twice
 anymore it will always return the same public key / name pair.

 Not sure if this is worth mentioning in the rn, but it is to reporter
 so why not.

 On Thu, Jun 25, 2015 at 8:08 AM, Erik Weber terbol...@gmail.com wrote:
  Gotcha, should add that.
 
  Are there any API changes that you know of in 4.4.4?
 
  --
  Erik
 
  On Thu, Jun 25, 2015 at 8:06 AM, Daan Hoogland daan.hoogl...@gmail.com
  wrote:
 
  I'll have a look, For the upgrade instructions 4.4.3 should work best.
 
  The only gotcha for people from 4.4.3 that I know of is a setting
  router.reboot.when.outofband.migrated. hte default 'false' gives old
  behavior. 'true' gives the 4.4.3 behavior.
 
 
  On Thu, Jun 25, 2015 at 12:20 AM, Erik Weber terbol...@gmail.com
 wrote:
   initial version at
 https://github.com/apache/cloudstack-docs-rn/pull/23
  
   it's getting late here, if anyone want's to pick it up feel free to
 fork
   and continue.
  
   --
   Erik
  
   On Wed, Jun 24, 2015 at 11:33 PM, Erik Weber terbol...@gmail.com
  wrote:
  
   in the perfect world I guess we would all be laying on a beach
 somewhere
   sunny
  
   i'll bring these `issues` to another thread for discussion
  
   any upgrade instructions for 4.4.4, or is it ok to stay with the
 upgrade
   from 4.4.1 instructions?
  
   --
   Erik
  
   On Wed, Jun 24, 2015 at 11:18 PM, Daan Hoogland 
  daan.hoogl...@gmail.com
   wrote:
  
   yes, you are right, but in a perfect world we wouldn't have any
 issues
  ;)
  
   I'd say mark them as 'assorted improvements on xxx-yyy'
  
   On Wed, Jun 24, 2015 at 11:15 PM, Erik Weber terbol...@gmail.com
  wrote:
i'm working my way through the git commits that reference jira
  issues to
mark them as fixed in 4.4.4
it isn't always straight forward though, as sometimes commits are
improvements to existing issues that has already been released.
   
take CLOUDSTACK-6181 for instance, it was released with 4.4.0, but
  has
commits in 4.4.4 that improves it.
in a perfect world I guess those commits really should have been
   separate
issues
   
--
Erik
   
   
   
On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland 
   daan.hoogl...@gmail.com
wrote:
   
btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well
   
On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland 
   daan.hoogl...@gmail.com
wrote:
 there is the git log

 On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber 
 terbol...@gmail.com
  
wrote:
 There's only one issue (CLOUDSTACK-8537) with fix version
 4.4.4
   marked
as
 resolved in Jira.

 I'm guessing that's wrong, so who know what's been fixed?

 --
 Erik

 On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland 
daan.hoogl...@gmail.com
 wrote:

 Someone feeling the urge to write release notes for 4.4.4?
  Looking
   for
 a volunteer.

 --
 Daan




 --
 Daan
   
   
   
--
Daan
   
  
  
  
   --
   Daan
  
  
  
 
 
 
  --
  Daan
 



 --
 Daan

Re: release notes

[Erik Weber]

I added a section for both out of band migration/reboots, and duplicate ssh
keys in the ``what's new`` section

-- 
Erik

On Thu, Jun 25, 2015 at 8:14 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 no, though that's debatable: one fix is that adding the same public
 key to a domain under a different name no longer works. It is a fix
 for retrieving keys consistently. retrieving the second name would
 return the key with the first name. Now it can not be entered twice
 anymore it will always return the same public key / name pair.

 Not sure if this is worth mentioning in the rn, but it is to reporter
 so why not.

 On Thu, Jun 25, 2015 at 8:08 AM, Erik Weber terbol...@gmail.com wrote:
  Gotcha, should add that.
 
  Are there any API changes that you know of in 4.4.4?
 
  --
  Erik
 
  On Thu, Jun 25, 2015 at 8:06 AM, Daan Hoogland daan.hoogl...@gmail.com
  wrote:
 
  I'll have a look, For the upgrade instructions 4.4.3 should work best.
 
  The only gotcha for people from 4.4.3 that I know of is a setting
  router.reboot.when.outofband.migrated. hte default 'false' gives old
  behavior. 'true' gives the 4.4.3 behavior.
 
 
  On Thu, Jun 25, 2015 at 12:20 AM, Erik Weber terbol...@gmail.com
 wrote:
   initial version at
 https://github.com/apache/cloudstack-docs-rn/pull/23
  
   it's getting late here, if anyone want's to pick it up feel free to
 fork
   and continue.
  
   --
   Erik
  
   On Wed, Jun 24, 2015 at 11:33 PM, Erik Weber terbol...@gmail.com
  wrote:
  
   in the perfect world I guess we would all be laying on a beach
 somewhere
   sunny
  
   i'll bring these `issues` to another thread for discussion
  
   any upgrade instructions for 4.4.4, or is it ok to stay with the
 upgrade
   from 4.4.1 instructions?
  
   --
   Erik
  
   On Wed, Jun 24, 2015 at 11:18 PM, Daan Hoogland 
  daan.hoogl...@gmail.com
   wrote:
  
   yes, you are right, but in a perfect world we wouldn't have any
 issues
  ;)
  
   I'd say mark them as 'assorted improvements on xxx-yyy'
  
   On Wed, Jun 24, 2015 at 11:15 PM, Erik Weber terbol...@gmail.com
  wrote:
i'm working my way through the git commits that reference jira
  issues to
mark them as fixed in 4.4.4
it isn't always straight forward though, as sometimes commits are
improvements to existing issues that has already been released.
   
take CLOUDSTACK-6181 for instance, it was released with 4.4.0, but
  has
commits in 4.4.4 that improves it.
in a perfect world I guess those commits really should have been
   separate
issues
   
--
Erik
   
   
   
On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland 
   daan.hoogl...@gmail.com
wrote:
   
btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well
   
On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland 
   daan.hoogl...@gmail.com
wrote:
 there is the git log

 On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber 
 terbol...@gmail.com
  
wrote:
 There's only one issue (CLOUDSTACK-8537) with fix version
 4.4.4
   marked
as
 resolved in Jira.

 I'm guessing that's wrong, so who know what's been fixed?

 --
 Erik

 On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland 
daan.hoogl...@gmail.com
 wrote:

 Someone feeling the urge to write release notes for 4.4.4?
  Looking
   for
 a volunteer.

 --
 Daan




 --
 Daan
   
   
   
--
Daan
   
  
  
  
   --
   Daan
  
  
  
 
 
 
  --
  Daan
 



 --
 Daan

Re: release notes

[Erik Weber]

Got it, updated the docs accordingly.

Thanks Daan

On Thu, Jun 25, 2015 at 11:27 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 9ced57551de5e1d62f2f7eb286440931bb6de262 uses the correct name, it was
 changed to be more clarifying

 The other two where moved from the implementation to the interface. no
 behavioral change.

 On Thu, Jun 25, 2015 at 8:59 AM, Erik Weber terbol...@gmail.com wrote:
  I added a section for both out of band migration/reboots, and duplicate
 ssh
  keys in the ``what's new`` section
 
  --
  Erik
 
  On Thu, Jun 25, 2015 at 8:14 AM, Daan Hoogland daan.hoogl...@gmail.com
  wrote:
 
  no, though that's debatable: one fix is that adding the same public
  key to a domain under a different name no longer works. It is a fix
  for retrieving keys consistently. retrieving the second name would
  return the key with the first name. Now it can not be entered twice
  anymore it will always return the same public key / name pair.
 
  Not sure if this is worth mentioning in the rn, but it is to reporter
  so why not.
 
  On Thu, Jun 25, 2015 at 8:08 AM, Erik Weber terbol...@gmail.com
 wrote:
   Gotcha, should add that.
  
   Are there any API changes that you know of in 4.4.4?
  
   --
   Erik
  
   On Thu, Jun 25, 2015 at 8:06 AM, Daan Hoogland 
 daan.hoogl...@gmail.com
   wrote:
  
   I'll have a look, For the upgrade instructions 4.4.3 should work
 best.
  
   The only gotcha for people from 4.4.3 that I know of is a setting
   router.reboot.when.outofband.migrated. hte default 'false' gives
 old
   behavior. 'true' gives the 4.4.3 behavior.
  
  
   On Thu, Jun 25, 2015 at 12:20 AM, Erik Weber terbol...@gmail.com
  wrote:
initial version at
  https://github.com/apache/cloudstack-docs-rn/pull/23
   
it's getting late here, if anyone want's to pick it up feel free to
  fork
and continue.
   
--
Erik
   
On Wed, Jun 24, 2015 at 11:33 PM, Erik Weber terbol...@gmail.com
   wrote:
   
in the perfect world I guess we would all be laying on a beach
  somewhere
sunny
   
i'll bring these `issues` to another thread for discussion
   
any upgrade instructions for 4.4.4, or is it ok to stay with the
  upgrade
from 4.4.1 instructions?
   
--
Erik
   
On Wed, Jun 24, 2015 at 11:18 PM, Daan Hoogland 
   daan.hoogl...@gmail.com
wrote:
   
yes, you are right, but in a perfect world we wouldn't have any
  issues
   ;)
   
I'd say mark them as 'assorted improvements on xxx-yyy'
   
On Wed, Jun 24, 2015 at 11:15 PM, Erik Weber 
 terbol...@gmail.com
   wrote:
 i'm working my way through the git commits that reference jira
   issues to
 mark them as fixed in 4.4.4
 it isn't always straight forward though, as sometimes commits
 are
 improvements to existing issues that has already been released.

 take CLOUDSTACK-6181 for instance, it was released with 4.4.0,
 but
   has
 commits in 4.4.4 that improves it.
 in a perfect world I guess those commits really should have
 been
separate
 issues

 --
 Erik



 On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland 
daan.hoogl...@gmail.com
 wrote:

 btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well

 On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland 
daan.hoogl...@gmail.com
 wrote:
  there is the git log
 
  On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber 
  terbol...@gmail.com
   
 wrote:
  There's only one issue (CLOUDSTACK-8537) with fix version
  4.4.4
marked
 as
  resolved in Jira.
 
  I'm guessing that's wrong, so who know what's been fixed?
 
  --
  Erik
 
  On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland 
 daan.hoogl...@gmail.com
  wrote:
 
  Someone feeling the urge to write release notes for 4.4.4?
   Looking
for
  a volunteer.
 
  --
  Daan
 
 
 
 
  --
  Daan



 --
 Daan

   
   
   
--
Daan
   
   
   
  
  
  
   --
   Daan
  
 
 
 
  --
  Daan
 



 --
 Daan

Re: release notes

[Erik Weber]

Gotcha, should add that.

Are there any API changes that you know of in 4.4.4?

-- 
Erik

On Thu, Jun 25, 2015 at 8:06 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 I'll have a look, For the upgrade instructions 4.4.3 should work best.

 The only gotcha for people from 4.4.3 that I know of is a setting
 router.reboot.when.outofband.migrated. hte default 'false' gives old
 behavior. 'true' gives the 4.4.3 behavior.


 On Thu, Jun 25, 2015 at 12:20 AM, Erik Weber terbol...@gmail.com wrote:
  initial version at https://github.com/apache/cloudstack-docs-rn/pull/23
 
  it's getting late here, if anyone want's to pick it up feel free to fork
  and continue.
 
  --
  Erik
 
  On Wed, Jun 24, 2015 at 11:33 PM, Erik Weber terbol...@gmail.com
 wrote:
 
  in the perfect world I guess we would all be laying on a beach somewhere
  sunny
 
  i'll bring these `issues` to another thread for discussion
 
  any upgrade instructions for 4.4.4, or is it ok to stay with the upgrade
  from 4.4.1 instructions?
 
  --
  Erik
 
  On Wed, Jun 24, 2015 at 11:18 PM, Daan Hoogland 
 daan.hoogl...@gmail.com
  wrote:
 
  yes, you are right, but in a perfect world we wouldn't have any issues
 ;)
 
  I'd say mark them as 'assorted improvements on xxx-yyy'
 
  On Wed, Jun 24, 2015 at 11:15 PM, Erik Weber terbol...@gmail.com
 wrote:
   i'm working my way through the git commits that reference jira
 issues to
   mark them as fixed in 4.4.4
   it isn't always straight forward though, as sometimes commits are
   improvements to existing issues that has already been released.
  
   take CLOUDSTACK-6181 for instance, it was released with 4.4.0, but
 has
   commits in 4.4.4 that improves it.
   in a perfect world I guess those commits really should have been
  separate
   issues
  
   --
   Erik
  
  
  
   On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland 
  daan.hoogl...@gmail.com
   wrote:
  
   btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well
  
   On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland 
  daan.hoogl...@gmail.com
   wrote:
there is the git log
   
On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber terbol...@gmail.com
 
   wrote:
There's only one issue (CLOUDSTACK-8537) with fix version 4.4.4
  marked
   as
resolved in Jira.
   
I'm guessing that's wrong, so who know what's been fixed?
   
--
Erik
   
On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland 
   daan.hoogl...@gmail.com
wrote:
   
Someone feeling the urge to write release notes for 4.4.4?
 Looking
  for
a volunteer.
   
--
Daan
   
   
   
   
--
Daan
  
  
  
   --
   Daan
  
 
 
 
  --
  Daan
 
 
 



 --
 Daan

Re: release notes

[Erik Weber]

i'm working my way through the git commits that reference jira issues to
mark them as fixed in 4.4.4
it isn't always straight forward though, as sometimes commits are
improvements to existing issues that has already been released.

take CLOUDSTACK-6181 for instance, it was released with 4.4.0, but has
commits in 4.4.4 that improves it.
in a perfect world I guess those commits really should have been separate
issues

-- 
Erik



On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well

 On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland daan.hoogl...@gmail.com
 wrote:
  there is the git log
 
  On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber terbol...@gmail.com
 wrote:
  There's only one issue (CLOUDSTACK-8537) with fix version 4.4.4 marked
 as
  resolved in Jira.
 
  I'm guessing that's wrong, so who know what's been fixed?
 
  --
  Erik
 
  On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland 
 daan.hoogl...@gmail.com
  wrote:
 
  Someone feeling the urge to write release notes for 4.4.4? Looking for
  a volunteer.
 
  --
  Daan
 
 
 
 
  --
  Daan



 --
 Daan

Re: release notes

[Erik Weber]

in the perfect world I guess we would all be laying on a beach somewhere
sunny

i'll bring these `issues` to another thread for discussion

any upgrade instructions for 4.4.4, or is it ok to stay with the upgrade
from 4.4.1 instructions?

-- 
Erik

On Wed, Jun 24, 2015 at 11:18 PM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 yes, you are right, but in a perfect world we wouldn't have any issues ;)

 I'd say mark them as 'assorted improvements on xxx-yyy'

 On Wed, Jun 24, 2015 at 11:15 PM, Erik Weber terbol...@gmail.com wrote:
  i'm working my way through the git commits that reference jira issues to
  mark them as fixed in 4.4.4
  it isn't always straight forward though, as sometimes commits are
  improvements to existing issues that has already been released.
 
  take CLOUDSTACK-6181 for instance, it was released with 4.4.0, but has
  commits in 4.4.4 that improves it.
  in a perfect world I guess those commits really should have been separate
  issues
 
  --
  Erik
 
 
 
  On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland daan.hoogl...@gmail.com
 
  wrote:
 
  btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well
 
  On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland 
 daan.hoogl...@gmail.com
  wrote:
   there is the git log
  
   On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber terbol...@gmail.com
  wrote:
   There's only one issue (CLOUDSTACK-8537) with fix version 4.4.4
 marked
  as
   resolved in Jira.
  
   I'm guessing that's wrong, so who know what's been fixed?
  
   --
   Erik
  
   On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland 
  daan.hoogl...@gmail.com
   wrote:
  
   Someone feeling the urge to write release notes for 4.4.4? Looking
 for
   a volunteer.
  
   --
   Daan
  
  
  
  
   --
   Daan
 
 
 
  --
  Daan
 



 --
 Daan

Re: release notes

[Daan Hoogland]

yes, you are right, but in a perfect world we wouldn't have any issues ;)

I'd say mark them as 'assorted improvements on xxx-yyy'

On Wed, Jun 24, 2015 at 11:15 PM, Erik Weber terbol...@gmail.com wrote:
 i'm working my way through the git commits that reference jira issues to
 mark them as fixed in 4.4.4
 it isn't always straight forward though, as sometimes commits are
 improvements to existing issues that has already been released.

 take CLOUDSTACK-6181 for instance, it was released with 4.4.0, but has
 commits in 4.4.4 that improves it.
 in a perfect world I guess those commits really should have been separate
 issues

 --
 Erik



 On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland daan.hoogl...@gmail.com
 wrote:

 btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well

 On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland daan.hoogl...@gmail.com
 wrote:
  there is the git log
 
  On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber terbol...@gmail.com
 wrote:
  There's only one issue (CLOUDSTACK-8537) with fix version 4.4.4 marked
 as
  resolved in Jira.
 
  I'm guessing that's wrong, so who know what's been fixed?
 
  --
  Erik
 
  On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland 
 daan.hoogl...@gmail.com
  wrote:
 
  Someone feeling the urge to write release notes for 4.4.4? Looking for
  a volunteer.
 
  --
  Daan
 
 
 
 
  --
  Daan



 --
 Daan




-- 
Daan

Re: release notes

[Erik Weber]

There's only one issue (CLOUDSTACK-8537) with fix version 4.4.4 marked as
resolved in Jira.

I'm guessing that's wrong, so who know what's been fixed?

-- 
Erik

On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 Someone feeling the urge to write release notes for 4.4.4? Looking for
 a volunteer.

 --
 Daan

Re: release notes

[Daan Hoogland]

btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well

On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland daan.hoogl...@gmail.com wrote:
 there is the git log

 On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber terbol...@gmail.com wrote:
 There's only one issue (CLOUDSTACK-8537) with fix version 4.4.4 marked as
 resolved in Jira.

 I'm guessing that's wrong, so who know what's been fixed?

 --
 Erik

 On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland daan.hoogl...@gmail.com
 wrote:

 Someone feeling the urge to write release notes for 4.4.4? Looking for
 a volunteer.

 --
 Daan




 --
 Daan



-- 
Daan

Re: release notes for 4.4.3

[Daan Hoogland]

Pierre-Luc did push the tag before the announcement. It didn't make it
to github. So did so push the tag to github directly? (thanks for
that)

On Fri, Apr 24, 2015 at 2:21 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
 Hi Daan,

 You’ll require access to the readthedocs site and the release notes project. 
 I’ve published RN 4.4.3 tag yesterday.


-- 
Daan

Re: release notes for 4.4.3

[Rohit Yadav]

Daan - I think I confused you. Let me try again - once you git push the tag to 
wip git repo (also, you cannot push on github since it’s a mirror); you need to 
log into https://readthedocs.org/accounts/login (in case you don’t have an 
account create one and ask Sebastien or any other admin to add you to the 
cloudstack release notes project 
https://readthedocs.org/projects/cloudstack-release-notes/), and select a tag 
you want to publish. The ReadTheDocs hosting service is different and does not 
automatically publish a git tag from the upstream repo.

 On 24-Apr-2015, at 2:43 pm, Daan Hoogland daan.hoogl...@gmail.com wrote:

 Pierre-Luc did push the tag before the announcement. It didn't make it
 to github. So did so push the tag to github directly? (thanks for
 that)

 On Fri, Apr 24, 2015 at 2:21 PM, Rohit Yadav rohit.ya...@shapeblue.com 
 wrote:
 Hi Daan,

 You’ll require access to the readthedocs site and the release notes project. 
 I’ve published RN 4.4.3 tag yesterday.


 --
 Daan

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



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

IaaS Cloud Design  Buildhttp://shapeblue.com/iaas-cloud-design-and-build//
CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
CloudStack Software 
Engineeringhttp://shapeblue.com/cloudstack-software-engineering/
CloudStack Infrastructure 
Supporthttp://shapeblue.com/cloudstack-infrastructure-support/
CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/

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

Re: release notes for 4.4.3

[Rohit Yadav]

Hi Daan,

You’ll require access to the readthedocs site and the release notes project. 
I’ve published RN 4.4.3 tag yesterday.

 On 21-Apr-2015, at 8:59 am, Daan Hoogland daan.hoogl...@gmail.com wrote:

 Can someone link me to a description on how to publish the release
 notes. I did update the site but the link is broken. I think
 Pierre-Luc already prepared them (@Pierre-Luc: did you?)

 AFAICT: this is the last step before sending out an announce.

 regards,
 --
 Daan

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



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

IaaS Cloud Design  Buildhttp://shapeblue.com/iaas-cloud-design-and-build//
CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
CloudStack Software 
Engineeringhttp://shapeblue.com/cloudstack-software-engineering/
CloudStack Infrastructure 
Supporthttp://shapeblue.com/cloudstack-infrastructure-support/
CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/

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

Re: release notes for 4.4.3

[Daan Hoogland]

ok, clear. thanks

On Fri, Apr 24, 2015 at 3:10 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
 Daan - I think I confused you. Let me try again - once you git push the tag 
 to wip git repo (also, you cannot push on github since it’s a mirror); you 
 need to log into https://readthedocs.org/accounts/login (in case you don’t 
 have an account create one and ask Sebastien or any other admin to add you to 
 the cloudstack release notes project 
 https://readthedocs.org/projects/cloudstack-release-notes/), and select a tag 
 you want to publish. The ReadTheDocs hosting service is different and does 
 not automatically publish a git tag from the upstream repo.

 On 24-Apr-2015, at 2:43 pm, Daan Hoogland daan.hoogl...@gmail.com wrote:

 Pierre-Luc did push the tag before the announcement. It didn't make it
 to github. So did so push the tag to github directly? (thanks for
 that)

 On Fri, Apr 24, 2015 at 2:21 PM, Rohit Yadav rohit.ya...@shapeblue.com 
 wrote:
 Hi Daan,

 You’ll require access to the readthedocs site and the release notes 
 project. I’ve published RN 4.4.3 tag yesterday.


 --
 Daan

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



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

 IaaS Cloud Design  Buildhttp://shapeblue.com/iaas-cloud-design-and-build//
 CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
 CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
 CloudStack Software 
 Engineeringhttp://shapeblue.com/cloudstack-software-engineering/
 CloudStack Infrastructure 
 Supporthttp://shapeblue.com/cloudstack-infrastructure-support/
 CloudStack Bootcamp Training 
 Courseshttp://shapeblue.com/cloudstack-training/

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



-- 
Daan

Re: release-notes script: jira.py

[Daan Hoogland]

P-L, when did this last work? Before the JIRA accounts where restricted?

biligual spelling checker used.read at your own risk
Op 18 sep. 2014 14:09 schreef Pierre-Luc Dion pd...@cloudops.com:

 Hi,

 Did anyone tried the script jira.py from cloudstack-docs-rn used to build
 release notes and retrieve jira issues?

 it look like Jira api does not behave as it used to...

 api resonse:
 https://issues.apache.org/jira/rest/api/2/filter/12329271
 expected response from the ui:
 https://issues.apache.org/jira/browse/CLOUDSTACK-7538?filter=12329271

 I will contact INFRA if nobody got it working recently,

 Thanks,

 Pierre-Luc

Re: release-notes script: jira.py

[Pierre-Luc Dion]

Daan,
I've used it for the RN of 4.4.0 so early july.

the newly created filter for 4.4.1 look ok, and the api url is returning
the same output for filter of 4.4.1 and 4.4.0, so look like the Jira API
behavior would have change during the summer.

the issue with INFRA as been closed;
https://issues.apache.org/jira/browse/INFRA-8364

I'll look with Attlassian doc more in depth when I have time...


*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 Thu, Sep 18, 2014 at 9:43 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:

 P-L, when did this last work? Before the JIRA accounts where restricted?

 biligual spelling checker used.read at your own risk
 Op 18 sep. 2014 14:09 schreef Pierre-Luc Dion pd...@cloudops.com:

  Hi,
 
  Did anyone tried the script jira.py from cloudstack-docs-rn used to build
  release notes and retrieve jira issues?
 
  it look like Jira api does not behave as it used to...
 
  api resonse:
  https://issues.apache.org/jira/rest/api/2/filter/12329271
  expected response from the ui:
  https://issues.apache.org/jira/browse/CLOUDSTACK-7538?filter=12329271
 
  I will contact INFRA if nobody got it working recently,
 
  Thanks,
 
  Pierre-Luc