[DISCUSS] Next CloudMonkey release v6.1.0

[Rohit Yadav]

All,

It's been over a year since the last CloudMonkey (cmk) release. While cmk 
appears to stable (given no major complains) we've had a few fixes since the 
last release and we must work on a release in near future (likely after 4.14 
and Primate tech preview).

I've triaged a few issues for the next v6.1.0 milestone, kindly provide any 
feedback, comments on this thread and report issues/feature requests here 
https://github.com/apache/cloudstack-cloudmonkey/issues

Thanks.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

[GitHub] [cloudstack-cloudmonkey] rhtyd commented on issue #57: cmk 6 - Provide Docker file and publish to Docker hub

[GitBox]

rhtyd commented on issue #57:
URL: 
https://github.com/apache/cloudstack-cloudmonkey/issues/57#issuecomment-626110138


   @synergiator https://hub.docker.com/r/apache/cloudstack-cloudmonkey/builds 
is available now



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] borisstoyanov opened a new issue #279: [BUG] Copy ISO Form does not discover values in fields. Also they seem to be displayed as API attributes

[GitBox]

borisstoyanov opened a new issue #279:
URL: https://github.com/apache/cloudstack-primate/issues/279


   **Describe the bug**
   Fields are not populated when selecting copy iso
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Go to ISOs
   2. Select an iso
   3. Click on Copy ISO
   4. See that fields are not autodiscovering Source and destination and fields 
are displayed and api call attributes names 
   
   ![Screenshot 2020-04-02 at 16 50 
53](https://user-images.githubusercontent.com/13551960/78257494-96e20280-7502-11ea-9c4f-2320a234edda.png)
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on issue #279: [BUG] Copy ISO Form does not discover values in fields. Also they seem to be displayed as API attributes

[GitBox]

rhtyd commented on issue #279:
URL: 
https://github.com/apache/cloudstack-primate/issues/279#issuecomment-626108379


   @borisstoyanov @vladimirpetrov please test latest master and close. The UX 
is changed slightly as follows:
   - the copy and delete buttons are now part of the zones tab for template/iso 
similar to old UI
   - there's a new template/iso filter drop down near search bar for 
template/iso list views
   - Kindly test template/iso register and upload features as well



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on pull request #284: template/iso actions in zones tab and template/iso filter in list view

[GitBox]

rhtyd commented on pull request #284:
URL: 
https://github.com/apache/cloudstack-primate/pull/284#issuecomment-626107779


   Reviewed and fixed. Tested:
   - Iso and template registration, fixes in form component
   - Filter by for template/iso
   - Copy and delete command for template/iso with job polling
   - Go to preview page on deletion of template/iso with a single zone



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on pull request #284: template/iso actions in zones tab and template/iso filter in list view

[GitBox]

rhtyd commented on pull request #284:
URL: 
https://github.com/apache/cloudstack-primate/pull/284#issuecomment-626107660


   remark @shwstppr - this was an untested PR, actions didn't work or show 
errors/success without doing proper polling.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Wei ZHOU]

Sorry Andrija,

I saw his pull request just now:
https://github.com/apache/cloudstack/pull/4064

-Wei

On Fri, 8 May 2020 at 23:20, Wei ZHOU  wrote:

> Hi Andrija,
>
> Yes. the lease time non-primary nics is "infiniteh" which should be
> "infinite". The user have fixed the issue and verified it. They will create
> pull request tomorrow I think.
>
> -Wei
>
>
> On Fri, 8 May 2020 at 16:55, Andrija Panic 
> wrote:
>
>> Hi Wei, is this the one?
>>
>> Fix dhcp infinite lease time #3913
>>
>> Can you share more on the issue?
>>
>> Thanks,
>> Andrija
>>
>> On Fri, 8 May 2020, 16:50 Wei ZHOU,  wrote:
>>
>> > -1
>> >
>> > a guy found an issue in pr #3913. He will create a pr.
>> >
>> > -Wei
>> >
>> > On Wed, 6 May 2020 at 22:45, Andrija Panic 
>> > wrote:
>> >
>> > > Hi All,
>> > >
>> > > I've created a 4.14.0.0 release (RC2), with the following artefacts up
>> > for
>> > > testing and a vote:
>> > >
>> > > Git Branch and Commit SH:
>> > >
>> > >
>> >
>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
>> > > Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
>> > >
>> > > Source release (checksums and signatures are available at the same
>> > > location):
>> > > https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
>> > >
>> > > PGP release keys (signed using 3DC01AE8):
>> > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> > >
>> > > The vote will be open until 12th May 2020.
>> > >
>> > > For sanity in tallying the vote, can PMC members please be sure to
>> > indicate
>> > > "(binding)" with their vote?
>> > >
>> > > [ ] +1 approve
>> > > [ ] +0 no opinion
>> > > [ ] -1 disapprove (and reason why)
>> > >
>> > > Additional information:
>> > >
>> > > For users' convenience, I've built packages from
>> > > 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository
>> > here:
>> > > http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
>> > > Debian/generic, both with noredist support)
>> > > and here
>> > >
>> > >
>> >
>> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
>> > > (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
>> > >
>> > > The release notes are still work-in-progress, but for the upgrade
>> > > instructions (including the new systemVM templates) you may refer to
>> the
>> > > following URL:
>> > >
>> >
>> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
>> > >
>> > > 4.14.0.0 systemVM templates are available from here:
>> > > http://download.cloudstack.org/systemvm/4.14/
>> > >
>> > > NOTES on issues fixed in this RC2 release:
>> > >
>> > > (these do *NOT* require a full retest if you were testing RC1 already
>> -
>> > > just if you were affected by these 2 issues):
>> > > -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone
>> in
>> > > db.properties, fixes only new installations of 4.14, while for the
>> > upgrade
>> > > process the documentation has been upgraded accordingly in
>> > > https://github.com/apache/cloudstack-documentation/pull/112/files)
>> > > -  https://github.com/apache/cloudstack/pull/4057   (fix regression
>> > where
>> > > one could not delete a snapshot created from a volume on Local
>> storage)
>> > >
>> > > Regards,
>> > >
>> > > Andrija Panić
>> > >
>> >
>>
>

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Wei ZHOU]

Hi Andrija,

Yes. the lease time non-primary nics is "infiniteh" which should be
"infinite". The user have fixed the issue and verified it. They will create
pull request tomorrow I think.

-Wei


On Fri, 8 May 2020 at 16:55, Andrija Panic  wrote:

> Hi Wei, is this the one?
>
> Fix dhcp infinite lease time #3913
>
> Can you share more on the issue?
>
> Thanks,
> Andrija
>
> On Fri, 8 May 2020, 16:50 Wei ZHOU,  wrote:
>
> > -1
> >
> > a guy found an issue in pr #3913. He will create a pr.
> >
> > -Wei
> >
> > On Wed, 6 May 2020 at 22:45, Andrija Panic 
> > wrote:
> >
> > > Hi All,
> > >
> > > I've created a 4.14.0.0 release (RC2), with the following artefacts up
> > for
> > > testing and a vote:
> > >
> > > Git Branch and Commit SH:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
> > > Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
> > >
> > > Source release (checksums and signatures are available at the same
> > > location):
> > > https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
> > >
> > > PGP release keys (signed using 3DC01AE8):
> > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > >
> > > The vote will be open until 12th May 2020.
> > >
> > > For sanity in tallying the vote, can PMC members please be sure to
> > indicate
> > > "(binding)" with their vote?
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Additional information:
> > >
> > > For users' convenience, I've built packages from
> > > 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository
> > here:
> > > http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
> > > Debian/generic, both with noredist support)
> > > and here
> > >
> > >
> >
> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
> > > (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
> > >
> > > The release notes are still work-in-progress, but for the upgrade
> > > instructions (including the new systemVM templates) you may refer to
> the
> > > following URL:
> > >
> >
> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
> > >
> > > 4.14.0.0 systemVM templates are available from here:
> > > http://download.cloudstack.org/systemvm/4.14/
> > >
> > > NOTES on issues fixed in this RC2 release:
> > >
> > > (these do *NOT* require a full retest if you were testing RC1 already -
> > > just if you were affected by these 2 issues):
> > > -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone
> in
> > > db.properties, fixes only new installations of 4.14, while for the
> > upgrade
> > > process the documentation has been upgraded accordingly in
> > > https://github.com/apache/cloudstack-documentation/pull/112/files)
> > > -  https://github.com/apache/cloudstack/pull/4057   (fix regression
> > where
> > > one could not delete a snapshot created from a volume on Local storage)
> > >
> > > Regards,
> > >
> > > Andrija Panić
> > >
> >
>

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Andrija Panic]

Hi Wei, is this the one?

Fix dhcp infinite lease time #3913

Can you share more on the issue?

Thanks,
Andrija

On Fri, 8 May 2020, 16:50 Wei ZHOU,  wrote:

> -1
>
> a guy found an issue in pr #3913. He will create a pr.
>
> -Wei
>
> On Wed, 6 May 2020 at 22:45, Andrija Panic 
> wrote:
>
> > Hi All,
> >
> > I've created a 4.14.0.0 release (RC2), with the following artefacts up
> for
> > testing and a vote:
> >
> > Git Branch and Commit SH:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
> > Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
> >
> > PGP release keys (signed using 3DC01AE8):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > The vote will be open until 12th May 2020.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> indicate
> > "(binding)" with their vote?
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Additional information:
> >
> > For users' convenience, I've built packages from
> > 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository
> here:
> > http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
> > Debian/generic, both with noredist support)
> > and here
> >
> >
> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
> > (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
> >
> > The release notes are still work-in-progress, but for the upgrade
> > instructions (including the new systemVM templates) you may refer to the
> > following URL:
> >
> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
> >
> > 4.14.0.0 systemVM templates are available from here:
> > http://download.cloudstack.org/systemvm/4.14/
> >
> > NOTES on issues fixed in this RC2 release:
> >
> > (these do *NOT* require a full retest if you were testing RC1 already -
> > just if you were affected by these 2 issues):
> > -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone in
> > db.properties, fixes only new installations of 4.14, while for the
> upgrade
> > process the documentation has been upgraded accordingly in
> > https://github.com/apache/cloudstack-documentation/pull/112/files)
> > -  https://github.com/apache/cloudstack/pull/4057   (fix regression
> where
> > one could not delete a snapshot created from a volume on Local storage)
> >
> > Regards,
> >
> > Andrija Panić
> >
>

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Wei ZHOU]

-1

a guy found an issue in pr #3913. He will create a pr.

-Wei

On Wed, 6 May 2020 at 22:45, Andrija Panic  wrote:

> Hi All,
>
> I've created a 4.14.0.0 release (RC2), with the following artefacts up for
> testing and a vote:
>
> Git Branch and Commit SH:
>
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
> Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
>
> PGP release keys (signed using 3DC01AE8):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 12th May 2020.
>
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Additional information:
>
> For users' convenience, I've built packages from
> 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository here:
> http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
> Debian/generic, both with noredist support)
> and here
>
> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
> (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
>
> The release notes are still work-in-progress, but for the upgrade
> instructions (including the new systemVM templates) you may refer to the
> following URL:
> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
>
> 4.14.0.0 systemVM templates are available from here:
> http://download.cloudstack.org/systemvm/4.14/
>
> NOTES on issues fixed in this RC2 release:
>
> (these do *NOT* require a full retest if you were testing RC1 already -
> just if you were affected by these 2 issues):
> -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone in
> db.properties, fixes only new installations of 4.14, while for the upgrade
> process the documentation has been upgraded accordingly in
> https://github.com/apache/cloudstack-documentation/pull/112/files)
> -  https://github.com/apache/cloudstack/pull/4057   (fix regression where
> one could not delete a snapshot created from a volume on Local storage)
>
> Regards,
>
> Andrija Panić
>

Re: [DISCUSS] Primate - publishing release and docs

[Riepl, Gregor (SWISS TXT)]

Hi Rohit,

Let me comment on just a few of the topics:

> Release cycle

I think we should definitely have a daily/nightly build, at least as long as a 
lot of changes are incoming.

I'm think along the lines of a parallel installation, so all versions can be 
tested and users still get a fallback in case of bugs:
- Stable legacy UI (included in cloudstack-management-server, as long as it's 
available)
- Stable new UI (alongside legacy UI, updated manually)
- Beta test from nightly (updated by an automated script)

> Versioning

Nightlies should not bear a release version, IMHO.
Something like cloudstack-primate-nightly-20200506.x86_64.rpm would be enough.
These should be built and published automatically, and no voting should take 
place.

When an actual stable/beta release is made, it should only contain the version 
and not the date, such as cloudstack-primate-0.4.0.x86_64.rpm
These could be voted on, depending on how often they're released.

> Package types and documentation

I'm in favour of supplying all three types of packages, and adding installation 
instructions for all three.
For the container variant, it may also make sense to provide an example 
Kubernetes manifest. In can contribute that if desired.

Regards,
Gregor

From: Rohit Yadav 
Sent: 08 May 2020 12:21
To: dev ; Sven Vogel 
Cc: us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - publishing release and docs

Hi Daan,

Thanks for replying and participating. Some points:

  *   The document links within Primate is a different topic than the docs for 
Primate itself, the scope of current discussion is limited to documentation for 
Primate. The doc link within Primate would be done against the 1.0/GA 
milestone, it would require going through all the sections/APIs against the 
current CloudStack docs and put a link (or part of it).
  *   The documentation for Primate currently won't be huge, perhaps a single 
long page would do (to explain how to install).
  *   Primate would be a separately installable package and installing 
cloudstack-management won't automatically trigger installing it (at least in 
the tech preview, we can discuss how we handle longer term starting with GA/1.0 
later).
  *   We've setup automation for all kinds of packaging formats/channels (we 
already have that for rpm/deb and archive formats, except for dockerhub hosting 
which is in discussion with ASF infra). I think publishing artifacts should be 
quick and mostly automated.
  *   Github has a new feature called Github packages for each repo, where one 
can host things like npm, docker packages etc. We can explore this feature.
On a Github release wrt a git tag, we can upload an artifact (I've seen many 
projects doing this).
  *   On releasing without voting, my thought and preference is that as our 
users test Primate, and report bugs and until GA/1.0 we fix those issues, 
implement missing feature users get faster fixes via a "preview" or "testing" 
or "beta" release channel periodically (deb/rpms repos, archives, docker 
container builds).

Doing this would require that we agree on this strategy, without a single 
tag/version but a set of releases (with a timestamp, so packages would look 
like cloudstack-primate-$version-$date). So effectively we're saying - let's 
release the tech preview without doing an official release (which would mean a 
fix git tag/version). This is where the discussion of a single tech preview 
release vs rolling tech preview release would come in.

Looking forward to more feedback from our dev/user community and of course our 
VP @Sven Vogel who has been a major Primate-SIG 
collaborator. Thanks.

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Daan Hoogland 
Sent: Thursday, May 7, 2020 12:34
To: dev 
Cc: us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - publishing release and docs

Hey Rohit,
This is a lot to take in at once. We have discussed some of those off line
but let me give my initial answers to your discussion points inline.
Hopefully those more directly involved and with more at stake can give some
input as well.

On Wed, May 6, 2020 at 3:03 PM Rohit Yadav 
wrote:

> All,
>
> With this thread I want to start a discussion around:
>
>   *   How do we host/publish technical preview release
>   *   How do we host/publish technical preview documentation (release
> notes, setup/install instructions)
>
> To set the expectation:
>
>   *   This thread limits discussion wrt technical preview (beta).
>   *   Plan we've already agreed, just to recap: 

...

>   *   References:
>  *   Voting thread: https://markmail.org/message/tblrbrtew6cvrusr
>  *   Proposal:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>  *   Discussion thread: https://markmail.org/message/z6fuvw4regig7aqb
>
...

>   *   Outstanding issues wrt 

[GitHub] [cloudstack-primate] onitake commented on issue #249: [BUG] Incorrect user name shown in top right corner

[GitBox]

onitake commented on issue #249:
URL: 
https://github.com/apache/cloudstack-primate/issues/249#issuecomment-625822909


   If you can't reproduce it, then it might in fact be related to LDAP account 
association.
   
   I can reproduce it in our environment every time. The LDAP user I logged in 
as is simply "lost" after login, and I only see the account's name and profile 
link.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] DaanHoogland commented on pull request #120: remove-environment.properties-note

[GitBox]

DaanHoogland commented on pull request #120:
URL: 
https://github.com/apache/cloudstack-documentation/pull/120#issuecomment-625823110


   ah  than



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #120: remove-environment.properties-note

[GitBox]

andrijapanicsb commented on pull request #120:
URL: 
https://github.com/apache/cloudstack-documentation/pull/120#issuecomment-625820008


   This was added back in the days of i.e. 4.5 or 4.6, etc, when it was 
supposed to be added once and it would stay there for the lifetime of that 
linux box.
   If you have i.e. 4.11 installation, that means either a clean install (line 
already there) or someone upgraded from earlier version to 4.11 following the 
docs that say to add that line (line already there/already added).
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Andrija Panic]

Thanks Nicolas, let's aim to fix that one in 4.15!

On Fri, 8 May 2020, 15:03 Nicolas Vazquez,  wrote:

> Hi,
>
> I'm reverting my vote as the issue was already present in 4.13. There is a
> problem casting between java classes that needs fixing but is not a blocker
> for RC2.
>
> Regards,
> Nicolas Vazquez
>
> El vie., 8 may. 2020 a las 1:20, Nicolas Vazquez ( >)
> escribió:
>
> > Here is a fix for the issue above:
> > https://github.com/apache/cloudstack/pull/4062
> >
> > El jue., 7 may. 2020 a las 15:58, Nicolas Vazquez (<
> > nicovazque...@gmail.com>) escribió:
> >
> >> Hi Andrija,
> >>
> >> I have found this issue when testing RC2:
> >> https://github.com/apache/cloudstack/issues/4061, giving -1 atm.
> >>
> >> Regards,
> >> Nicolas Vazquez
> >>
> >> El mié., 6 may. 2020 a las 17:45, Andrija Panic (<
> andrija.pa...@gmail.com>)
> >> escribió:
> >>
> >>> Hi All,
> >>>
> >>> I've created a 4.14.0.0 release (RC2), with the following artefacts up
> >>> for
> >>> testing and a vote:
> >>>
> >>> Git Branch and Commit SH:
> >>>
> >>>
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
> >>> Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
> >>>
> >>> Source release (checksums and signatures are available at the same
> >>> location):
> >>> https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
> >>>
> >>> PGP release keys (signed using 3DC01AE8):
> >>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>>
> >>> The vote will be open until 12th May 2020.
> >>>
> >>> For sanity in tallying the vote, can PMC members please be sure to
> >>> indicate
> >>> "(binding)" with their vote?
> >>>
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove (and reason why)
> >>>
> >>> Additional information:
> >>>
> >>> For users' convenience, I've built packages from
> >>> 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository
> >>> here:
> >>> http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
> >>> Debian/generic, both with noredist support)
> >>> and here
> >>>
> >>>
> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
> >>> (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
> >>>
> >>> The release notes are still work-in-progress, but for the upgrade
> >>> instructions (including the new systemVM templates) you may refer to
> the
> >>> following URL:
> >>>
> >>>
> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
> >>>
> >>> 4.14.0.0 systemVM templates are available from here:
> >>> http://download.cloudstack.org/systemvm/4.14/
> >>>
> >>> NOTES on issues fixed in this RC2 release:
> >>>
> >>> (these do *NOT* require a full retest if you were testing RC1 already -
> >>> just if you were affected by these 2 issues):
> >>> -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone
> in
> >>> db.properties, fixes only new installations of 4.14, while for the
> >>> upgrade
> >>> process the documentation has been upgraded accordingly in
> >>> https://github.com/apache/cloudstack-documentation/pull/112/files)
> >>> -  https://github.com/apache/cloudstack/pull/4057   (fix regression
> >>> where
> >>> one could not delete a snapshot created from a volume on Local storage)
> >>>
> >>> Regards,
> >>>
> >>> Andrija Panić
> >>>
> >>
>

Re: [VOTE] Apache CloudStack 4.14.0.0 RC2

[Nicolas Vazquez]

Hi,

I'm reverting my vote as the issue was already present in 4.13. There is a
problem casting between java classes that needs fixing but is not a blocker
for RC2.

Regards,
Nicolas Vazquez

El vie., 8 may. 2020 a las 1:20, Nicolas Vazquez ()
escribió:

> Here is a fix for the issue above:
> https://github.com/apache/cloudstack/pull/4062
>
> El jue., 7 may. 2020 a las 15:58, Nicolas Vazquez (<
> nicovazque...@gmail.com>) escribió:
>
>> Hi Andrija,
>>
>> I have found this issue when testing RC2:
>> https://github.com/apache/cloudstack/issues/4061, giving -1 atm.
>>
>> Regards,
>> Nicolas Vazquez
>>
>> El mié., 6 may. 2020 a las 17:45, Andrija Panic ()
>> escribió:
>>
>>> Hi All,
>>>
>>> I've created a 4.14.0.0 release (RC2), with the following artefacts up
>>> for
>>> testing and a vote:
>>>
>>> Git Branch and Commit SH:
>>>
>>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.14.0.0-RC20200506T2028
>>> Commit: 377c9c8ab2eecca57b0073065c018fe9a010a520
>>>
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.14.0.0/
>>>
>>> PGP release keys (signed using 3DC01AE8):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>> The vote will be open until 12th May 2020.
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to
>>> indicate
>>> "(binding)" with their vote?
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> Additional information:
>>>
>>> For users' convenience, I've built packages from
>>> 377c9c8ab2eecca57b0073065c018fe9a010a520 and published RC2 repository
>>> here:
>>> http://packages.shapeblue.com/testing/41400rc2/  (CentOS 7 and
>>> Debian/generic, both with noredist support)
>>> and here
>>>
>>> https://download.cloudstack.org/testing/4.14.0.0-RC20200506T2028/ubuntu/bionic/
>>> (Ubuntu 18.04 specific, no noredist support - thanks to Gabriel):
>>>
>>> The release notes are still work-in-progress, but for the upgrade
>>> instructions (including the new systemVM templates) you may refer to the
>>> following URL:
>>>
>>> https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr112/upgrading/index.html
>>>
>>> 4.14.0.0 systemVM templates are available from here:
>>> http://download.cloudstack.org/systemvm/4.14/
>>>
>>> NOTES on issues fixed in this RC2 release:
>>>
>>> (these do *NOT* require a full retest if you were testing RC1 already -
>>> just if you were affected by these 2 issues):
>>> -  https://github.com/apache/cloudstack/pull/4055 (explicit timezone in
>>> db.properties, fixes only new installations of 4.14, while for the
>>> upgrade
>>> process the documentation has been upgraded accordingly in
>>> https://github.com/apache/cloudstack-documentation/pull/112/files)
>>> -  https://github.com/apache/cloudstack/pull/4057   (fix regression
>>> where
>>> one could not delete a snapshot created from a volume on Local storage)
>>>
>>> Regards,
>>>
>>> Andrija Panić
>>>
>>

[GitHub] [cloudstack-primate] rhtyd commented on issue #249: [BUG] Incorrect user name shown in top right corner

[GitBox]

rhtyd commented on issue #249:
URL: 
https://github.com/apache/cloudstack-primate/issues/249#issuecomment-625783001


   Unable to reproduce, closing on this remark. Let's revisit this after tech 
preview.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on pull request #284: view: actions in template/iso zones

[GitBox]

rhtyd commented on pull request #284:
URL: 
https://github.com/apache/cloudstack-primate/pull/284#issuecomment-625781938


   Test issues:
   - Don't poll for async job (both copy and delete operations), notification 
too early
   - should refresh after async job poll, for delete if there are no zones, run 
router.go(-1)
   
   I've added support for template/iso filtering.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] vladimirpetrov commented on issue #199: [BUG] Different list of template images in old and new UI

[GitBox]

vladimirpetrov commented on issue #199:
URL: 
https://github.com/apache/cloudstack-primate/issues/199#issuecomment-625760615


   Fix confirmed, closing the issue.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] vladimirpetrov commented on issue #173: [BUG] Selected instance actions difference between old and new UI

[GitBox]

vladimirpetrov commented on issue #173:
URL: 
https://github.com/apache/cloudstack-primate/issues/173#issuecomment-625759712


   Fix confirmed, closing the issue.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] rhtyd commented on a change in pull request #296: view: fix api error handling

[GitBox]

rhtyd commented on a change in pull request #296:
URL: https://github.com/apache/cloudstack-primate/pull/296#discussion_r422068600



##
File path: src/utils/plugins.js
##
@@ -77,3 +78,35 @@ export const pollJobPlugin = {
   }
 
 }
+
+export const notifierPlugin = {
+
+  install (Vue) {
+Vue.prototype.$notifyError = function (error) {
+  var msg = 'Request Failed'
+  var desc = ''
+  if (error && error.response) {
+if (error.response.status) {
+  msg = `Request Failed (${error.response.status})`
+}
+if (error.message) {
+  desc = error.message
+}
+if (error.response.headers && 'x-description' in 
error.response.headers) {
+  desc = error.response.headers['x-description']
+}
+if (desc === '' && error.response.data) {
+  const responseKey = _.findKey(error.response.data, 'errortext')
+  if (responseKey) {
+desc = error.response.data[responseKey].errortext
+  }
+}
+  }
+  notification.error({
+message: msg,
+description: error && error.response && 'x-description' in 
error.response.headers ? error.response.headers['x-description'] : 
error.message,

Review comment:
   Good catch @shwstppr  - I made a boo-boo while refactoring stuff. Just 
fixed it on master.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-primate] shwstppr commented on a change in pull request #296: view: fix api error handling

[GitBox]

shwstppr commented on a change in pull request #296:
URL: https://github.com/apache/cloudstack-primate/pull/296#discussion_r422066423



##
File path: src/utils/plugins.js
##
@@ -77,3 +78,35 @@ export const pollJobPlugin = {
   }
 
 }
+
+export const notifierPlugin = {
+
+  install (Vue) {
+Vue.prototype.$notifyError = function (error) {
+  var msg = 'Request Failed'
+  var desc = ''
+  if (error && error.response) {
+if (error.response.status) {
+  msg = `Request Failed (${error.response.status})`
+}
+if (error.message) {
+  desc = error.message
+}
+if (error.response.headers && 'x-description' in 
error.response.headers) {
+  desc = error.response.headers['x-description']
+}
+if (desc === '' && error.response.data) {
+  const responseKey = _.findKey(error.response.data, 'errortext')
+  if (responseKey) {
+desc = error.response.data[responseKey].errortext
+  }
+}
+  }
+  notification.error({
+message: msg,
+description: error && error.response && 'x-description' in 
error.response.headers ? error.response.headers['x-description'] : 
error.message,

Review comment:
   @rhtyd shoud this read, `description: desc`?





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSS] Primate - publishing release and docs

[Rohit Yadav]

Hi Daan,

Thanks for replying and participating. Some points:

  *   The document links within Primate is a different topic than the docs for 
Primate itself, the scope of current discussion is limited to documentation for 
Primate. The doc link within Primate would be done against the 1.0/GA 
milestone, it would require going through all the sections/APIs against the 
current CloudStack docs and put a link (or part of it).
  *   The documentation for Primate currently won't be huge, perhaps a single 
long page would do (to explain how to install).
  *   Primate would be a separately installable package and installing 
cloudstack-management won't automatically trigger installing it (at least in 
the tech preview, we can discuss how we handle longer term starting with GA/1.0 
later).
  *   We've setup automation for all kinds of packaging formats/channels (we 
already have that for rpm/deb and archive formats, except for dockerhub hosting 
which is in discussion with ASF infra). I think publishing artifacts should be 
quick and mostly automated.
  *   Github has a new feature called Github packages for each repo, where one 
can host things like npm, docker packages etc. We can explore this feature.
On a Github release wrt a git tag, we can upload an artifact (I've seen many 
projects doing this).
  *   On releasing without voting, my thought and preference is that as our 
users test Primate, and report bugs and until GA/1.0 we fix those issues, 
implement missing feature users get faster fixes via a "preview" or "testing" 
or "beta" release channel periodically (deb/rpms repos, archives, docker 
container builds).

Doing this would require that we agree on this strategy, without a single 
tag/version but a set of releases (with a timestamp, so packages would look 
like cloudstack-primate-$version-$date). So effectively we're saying - let's 
release the tech preview without doing an official release (which would mean a 
fix git tag/version). This is where the discussion of a single tech preview 
release vs rolling tech preview release would come in.

Looking forward to more feedback from our dev/user community and of course our 
VP @Sven Vogel who has been a major Primate-SIG 
collaborator. Thanks.

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Daan Hoogland 
Sent: Thursday, May 7, 2020 12:34
To: dev 
Cc: us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - publishing release and docs

Hey Rohit,
This is a lot to take in at once. We have discussed some of those off line
but let me give my initial answers to your discussion points inline.
Hopefully those more directly involved and with more at stake can give some
input as well.

On Wed, May 6, 2020 at 3:03 PM Rohit Yadav 
wrote:

> All,
>
> With this thread I want to start a discussion around:
>
>   *   How do we host/publish technical preview release
>   *   How do we host/publish technical preview documentation (release
> notes, setup/install instructions)
>
> To set the expectation:
>
>   *   This thread limits discussion wrt technical preview (beta).
>   *   Plan we've already agreed, just to recap: 

...

>   *   References:
>  *   Voting thread: https://markmail.org/message/tblrbrtew6cvrusr
>  *   Proposal:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI
>  *   Discussion thread: https://markmail.org/message/z6fuvw4regig7aqb
>
...

>   *   Outstanding issues wrt 0.5-technical-preview milestone:
> https://github.com/apache/cloudstack-primate/milestone/1
>   *   Oustanding PRs for 0.5-technical-preview:
> https://github.com/apache/cloudstack-primate/pulls?q=is%3Aopen+is%3Apr+no%3Amilestone
>
...

>   1.  Documentation for tech preview:
>
> It is preferred that Primate be developed, maintained and released
> separately from CloudStack. Primate would require its own docs
> website/location for hosting release notes etc. I can think of two ways:
>
>  *   For tech preview, let's just a section/topic on Primate on how
> users can install and use Primate on the docs website:
> http://docs.cloudstack.apache.org/en/latest/primateguide (it does not
> exist, just for example)
> For each CloudStack release, the docs may be updated, including list of
> supported/required versions matrix (both CloudStack and Primate).
> For tech preview, this needs to be on the 4.14.0.0 docs website.
>
>  *   On Github wiki: https://github.com/apache/cloudstack-primate/wiki
> we can maintain a copy of text/pages from above ^^, as well as links on the
> Github release for every git tag. A general guide (agnostic of Primate
> version) could be written/hosted there.
> (similar to CloudStack releases, for example:
> https://github.com/apache/cloudstack/releases/tag/4.13.0.0)
>
I think Primate should be documented by means of help pop-ups with links to
the underlaying API and admin docs. How big do you expect this

[GitHub] [cloudstack-primate] vladimirpetrov commented on issue #51: Show Password after deploying VM

[GitBox]

vladimirpetrov commented on issue #51:
URL: 
https://github.com/apache/cloudstack-primate/issues/51#issuecomment-625724206


   Fix confirmed, working fine.
   
   
![image](https://user-images.githubusercontent.com/12384665/81391522-e4671600-9125-11ea-8c1e-f284652866b9.png)
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] DaanHoogland commented on pull request #120: remove-environment.properties-note

[GitBox]

DaanHoogland commented on pull request #120:
URL: 
https://github.com/apache/cloudstack-documentation/pull/120#issuecomment-625717776


   ok, so is this a remark added for trouble shooting?
   I see your point but also this was added to help some users (actually to 
prevent questions). Is that no longer valid or should it maybe be moved to a 
trouble shooting section instead of deleted?



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] andrijapanicsb commented on pull request #120: remove-environment.properties-note

[GitBox]

andrijapanicsb commented on pull request #120:
URL: 
https://github.com/apache/cloudstack-documentation/pull/120#issuecomment-625704965


   As I wrote... its impossible for that line to be missing in ACS 4.11+  
(tested) as the agent would not connect to mgmt in the first place - so there 
is no reason to even have this premise that it MIGHT be missing in the first 
place - it can't be missing.
   
   With that logic, we could ask users to check any lines in various files. See 
my point? 



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] DaanHoogland commented on pull request #120: remove-environment.properties-note

[GitBox]

DaanHoogland commented on pull request #120:
URL: 
https://github.com/apache/cloudstack-documentation/pull/120#issuecomment-625688121


   > The starting premise "if it doesn't exist" is impossible in the first 
place... (tested on 4.11.0 - agent will never connect if that line is missing 
in the file) - then no need to the warning/message - so removing it from 4.11+ 
Upgrade pages.
   
   I don't see how this is a reason to remove this line. Users need to be 
attended to adding it, right? How is it impossible that a line is missing from 
a conf file? (unless we are adding it in automated fashion.
   
   Should
   ```
   paths.script=/usr/share/cloudstack-common
   ```
   be in `/etc/cloudstack/agent/environment.properties`, than  i see no reason 
for this removal.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org