[GitHub] [cloudstack-primate] blueorangutan commented on pull request #330: Add unmanage VM button

[GitBox]

blueorangutan commented on pull request #330:
URL: 
https://github.com/apache/cloudstack-primate/pull/330#issuecomment-635110792


   Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian 
:heavy_check_mark:archive. JID-1946



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] utchoang commented on a change in pull request #364: Add boottype and bootmode to VM instance

[GitBox]

utchoang commented on a change in pull request #364:
URL: https://github.com/apache/cloudstack-primate/pull/364#discussion_r431549452



##
File path: src/views/compute/DeployVM.vue
##
@@ -80,6 +80,25 @@
 :options="keyboardSelectOptions"
   >
 
+
+  
+
+  {{ bootType.description }}
+
+  
+
+
+  
+
+  {{ bootMode.description }}
+
+  
+

Review comment:
   @rhtyd Do you think about this? Because on 
https://github.com/apache/cloudstack/blob/d4b537efa7ed27ef88b735a22493808b61529186/ui/scripts/ui-custom/instanceWizard.js.
 I don't see any description for show/hidden of boot type & bootmode





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 #130: vsphere 6.7u3-u3f crash notice

[GitBox]

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


   will be fwd merged to 4.14 and 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-documentation] ACSGitBot commented on pull request #130: vsphere 6.7u3-u3f crash notice

[GitBox]

ACSGitBot commented on pull request #130:
URL: 
https://github.com/apache/cloudstack-documentation/pull/130#issuecomment-634942264


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr130
   
   Build Log Output:
   
   
   No log errors found to report.



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] ACSGitBot commented on pull request #130: vsphere 6.7u3-u3f crash notice

[GitBox]

ACSGitBot commented on pull request #130:
URL: 
https://github.com/apache/cloudstack-documentation/pull/130#issuecomment-634941127


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



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] ACSGitBot removed a comment on pull request #130: vsphere 6.7u3-u3f crash notice

[GitBox]

ACSGitBot removed a comment on pull request #130:
URL: 
https://github.com/apache/cloudstack-documentation/pull/130#issuecomment-634937684







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 removed a comment on pull request #130: vsphere 6.7u3-u3f crash notice

[GitBox]

andrijapanicsb removed a comment on pull request #130:
URL: 
https://github.com/apache/cloudstack-documentation/pull/130#issuecomment-634936648


   requesting docbuild



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] ACSGitBot commented on pull request #130: vsphere 6.7u3-u3f crash notice

[GitBox]

ACSGitBot commented on pull request #130:
URL: 
https://github.com/apache/cloudstack-documentation/pull/130#issuecomment-634937684


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr130
   
   Build Log Output:
   
   
   No log errors found to report.



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 opened a new pull request #130: vsphere 6.7u3-u3f crash notice

[GitBox]

andrijapanicsb opened a new pull request #130:
URL: https://github.com/apache/cloudstack-documentation/pull/130


   



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] ACSGitBot commented on pull request #130: vsphere 6.7u3-u3f crash notice

[GitBox]

ACSGitBot commented on pull request #130:
URL: 
https://github.com/apache/cloudstack-documentation/pull/130#issuecomment-634936695


   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   



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 #130: vsphere 6.7u3-u3f crash notice

[GitBox]

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


   requesting docbuild



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 RC3

[Riepl, Gregor (SWISS TXT)]

Thank you, Andrija!

We will keep that in mind when we upgrade to 6.7.

From: Andrija Panic 
Sent: 20 May 2020 23:02
To: users 
Cc: dev 
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC3

@gregor - the legacy should be fine with UEFI (what I had run on some of my
laptops); UEFI is not a problem, happens with 4.13 also, any VirtualBox OVA
file will cause the issue

###
To conclude the ISSUE, based on my few hour testing today:

- happens when you deliberately use VirtualBox OVA template with vSphere
(who and why would do that, is another topic..), in ACS 4.13.x and
4.14/master

...out of which...:

- does NOT happen with vCenter 6.0 and 6.5 (confirmed by Daan/Bobby),
proper OVF parsing takes place and an error message is generated in ACS logs
- NOT tested:   6.7 / 6.7 U1xxx / 6.7 U2xxx (i.e. not tested with any
variant < 6.7 U3)
- issues happen with vCenter 6.7 U3  / U3a / U3b / U3f - these were
explicitly tested by me and some vCenter services would crash (though still
appearing as running) - the problem is solved by restarting (most?)
services - namely "VMware afd Service" will trigger other services to
restart (dependency) and after a while vCenter is UP again (I could not
find which exact service (single one) might be the issue)
- Worth mentioning this was observed on vCenter on Windows Server, not the
VCSA appliance

-  seems FINE - NO ISSUES with vCenter 6.7 U3g (the latest 6.7 U3 variants
at the moment - build 16046470 from 28.04.2020) and the VM deployment fails
gracefully with a proper error message of not being able to create SPEC
file based on the (bad) OVF.


Since the issue is solved in the (current) latest vSphere 6.7 U3g variant,
I will make sure to have the proper warning message on both 4.13.1 and
4.14.0.0 Release notes documentation (4.13 is when we started supporting
vSphere 6.7 and the same issue present here)

I'll proceed tomorrow with releasing 4.14 based on the voting done so far.

Thanks

On Wed, 20 May 2020 at 22:09, Marcus  wrote:

> I would say, if it is proven that this happens with existing released
> CloudStack versions, with or without the UEFI feature, against a specific
> VMware release with a specific broken template, then it becomes an
> environment issue and shouldn't block the release.  In this case it would
> not matter if we tried to revert the feature, or if we did or did not
> release 4.14, the users who would hit this would be hitting this now in
> live environments, with the released versions of CloudStack.
>
> To be clear, I'm not 100% certain this is exactly what Bobby was saying,
> but if this is the case then I think it should not block us.
>
> On Wed, May 20, 2020 at 1:00 AM Riepl, Gregor (SWISS TXT) <
> gregor.ri...@swisstxt.ch> wrote:
>
> > Hi everyone
> >
> > Sorry for the late response, but I have a few concerns:
> >
> >
> >   *   As Bobby stated, this bug seems to only occur with VMware 6.7+, and
> > it sounds to me like they should take action on it. Does someone track
> this
> > with VMware?
> >   *   Do I understand correctly that the issue only occurs when the image
> > is set to UEFI mode, but the VM is configured as Legacy Boot in
> CloudStack?
> > How would this combination even work? I think CloudStack should either
> > reject such a mismatch or autocorrect it. Or at least display a warning
> to
> > the user.
> >   *   If the bug can break vCenter (if only temporarily), there should
> > definitely some sort of safeguard around it, even if it isn't a proper
> fix
> > or workaround.
> >
> > Regards,
> > Gregor
> > 
> > From: Andrija Panic 
> > Sent: 19 May 2020 21:11
> > To: users 
> > Cc: dev@cloudstack.apache.org 
> > Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC3
> >
> > Hi all,
> >
> > In my humble opinion, we should release 4.14 as it is (considering we
> have
> > enough votes), but we'll further investigate the actual/behind-the-scene
> > root-cause for the vSphere 6.7 harakiri (considering 6.0 and 6.5 are not
> > affected) - this is possibly a VMware bug and we'll certainly try to
> > address it.
> >
> > If I don't hear any more concerns or -1 votes until tomorrow morning CET
> > time, I will proceed with concluding the voting process and crafting the
> > release.
> >
> > Thanks,
> > Andrija
> >
> > On Tue, 19 May 2020 at 19:23, Pavan Kumar Aravapalli <
> > pavankuma...@accelerite.com> wrote:
> >
> > > Thank you Bobby and Daan for the update. However I have not encountered
> > > such issue while doing dev test with Vmware 5.5 & 6.5.
> > >
> > >
> > >
> > >
> > >
> > > Regards,
> > >
> > > Pavan Aravapalli.
> > >
> > >
> > > 
> > > From: Daan Hoogland 
> > > Sent: 19 May 2020 20:56
> > > To: users 
> > > Cc: dev@cloudstack.apache.org 
> > > Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC3
> > >
> > > Thanks Bobby,
> > > All, I've been closely working 

Re: Centralised logging capability.

[Sven Vogel]

Hi Sina,

First. Cool feature!

Agree with Daan. This would be absolutely nice to have the possibility to send 
the log files to separate log server. So in the end of the day we have an Heavy 
management server.

Cheers

Sven


__

Sven Vogel
Lead Cloud Solution Architect

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.
> Am 27.05.2020 um 17:43 schrieb Daan Hoogland :
>
> great initiative Sina, I did leave a comment on the PR, about
> configurability.
> in short two worries:
> 1. an operator uses a different log host than the MS (i.e an ip/hostname
> config)
> 2. an operator wants to not use the feature (i.e. a boolean flag)
> I'm not sure how much this would require, but it seems minimal. Of course,
> not opening the port is blocking the feature as well.
>
>
>> On Wed, May 27, 2020 at 3:55 PM Sina Kashipazha
>>  wrote:
>>
>>
>> Centralised logging capability.
>>
>> Our improvements to systemvm allow Cloudstack administrator to access
>> systemvms logs inside the management server. It removes the difficulty of
>> downloading logs from systemvms. They are forwarded to the management
>> server automatically, and administrators can access them in
>> "/var/log/rsyslog/%HOSTNAME%/syslog”.
>>
>>
>> It doesn’t require additional work, rsyslog setups on Cloudstack already.
>> The only thing we have to do is open rsyslog port to receive these logs and
>> tell hypervisors and systemvms to forward them to the management server.
>>
>> Any comments would be highly appreciated.
>>
>> For more information take a look at below issue and pull request:
>> Issue: https://github.com/apache/cloudstack/issues/4093
>> Pull request: https://github.com/apache/cloudstack/pull/4108 <
>> https://github.com/apache/cloudstack/pull/4108>
>>
>> Kind Regards,
>> Sina
>
>
>
> --
> Daan

Re: Centralised logging capability.

[Daan Hoogland]

great initiative Sina, I did leave a comment on the PR, about
configurability.
in short two worries:
1. an operator uses a different log host than the MS (i.e an ip/hostname
config)
2. an operator wants to not use the feature (i.e. a boolean flag)
I'm not sure how much this would require, but it seems minimal. Of course,
not opening the port is blocking the feature as well.


On Wed, May 27, 2020 at 3:55 PM Sina Kashipazha
 wrote:

>
> Centralised logging capability.
>
> Our improvements to systemvm allow Cloudstack administrator to access
> systemvms logs inside the management server. It removes the difficulty of
> downloading logs from systemvms. They are forwarded to the management
> server automatically, and administrators can access them in
> "/var/log/rsyslog/%HOSTNAME%/syslog”.
>
>
> It doesn’t require additional work, rsyslog setups on Cloudstack already.
> The only thing we have to do is open rsyslog port to receive these logs and
> tell hypervisors and systemvms to forward them to the management server.
>
> Any comments would be highly appreciated.
>
> For more information take a look at below issue and pull request:
> Issue: https://github.com/apache/cloudstack/issues/4093
> Pull request: https://github.com/apache/cloudstack/pull/4108 <
> https://github.com/apache/cloudstack/pull/4108>
>
> Kind Regards,
> Sina



-- 
Daan

Centralised logging capability.

[Sina Kashipazha]

Centralised logging capability.
 
Our improvements to systemvm allow Cloudstack administrator to access systemvms 
logs inside the management server. It removes the difficulty of downloading 
logs from systemvms. They are forwarded to the management server automatically, 
and administrators can access them in "/var/log/rsyslog/%HOSTNAME%/syslog”.


It doesn’t require additional work, rsyslog setups on Cloudstack already. The 
only thing we have to do is open rsyslog port to receive these logs and tell 
hypervisors and systemvms to forward them to the management server.

Any comments would be highly appreciated.
  
For more information take a look at below issue and pull request:
Issue: https://github.com/apache/cloudstack/issues/4093 
Pull request: https://github.com/apache/cloudstack/pull/4108 


Kind Regards,
Sina

Re: [ANNOUNCE] Apache(R) CloudStack(R) Release 4.14 (LTS)

[nux]

Awesome release, thanks!


On 2020-05-26 11:08, Andrija Panic wrote:

Announcing  Apache®  CloudStack®  LTS Release 4.14

The Apache CloudStack project is pleased to announce the release of
CloudStack 4.14. Apache CloudStack 4.14.0.0 is a 4.14 LTS release with 
over

15 major new features, and over 200 enhancements and fixes since 4.13.
Highlights include:

- New modern UI (Project Primate, Technical preview)
- Backup and Recovery framework
- Backup and Recovery Provider for Veeam
- VM ingestion
- L2 network PVLAN enhancements
- CloudStack Kubernetes Service
- UEFI support
- KVM rolling maintenance
- Enable Direct Download for systemVM templates
- VR health checks
- Download logs and diagnostics data from SSVM/CPVM/VRs
- Enable additional configuration metadata to virtual machines

The full list of new features can be found in the project release notes 
at

http://docs.cloudstack.apache.org/en/4.14.0.0/releasenotes/changes.html

# Documentation
The 4.14.0.0 release notes include a full list of changes:
http://docs.cloudstack.apache.org/en/4.14.0.0/releasenotes/changes.html
The CloudStack documentation includes upgrade instructions from 
previous

versions of Apache CloudStack, and can be found at:
http://docs.cloudstack.apache.org/en/4.14.0.0/upgrading/index.html
The official installation, administration and API documentation for 
each of

the releases are available on our documentation page:
http://docs.cloudstack.apache.org/

# Downloads
The official source code for the 4.14.0.0 release can be downloaded 
from

our downloads page:
http://cloudstack.apache.org/downloads.html

In addition to the official source code release, individual 
contributors

have also made convenience binaries available on the Apache CloudStack
download page, and can be found at:
http://download.cloudstack.org/ubuntu/dists/
http://download.cloudstack.org/centos/7/
http://www.shapeblue.com/packages/

Kind regards,

Andrija Panić

[GitHub] [cloudstack-primate] DaanHoogland commented on a change in pull request #364: Add boottype and bootmode to VM instance

[GitBox]

DaanHoogland commented on a change in pull request #364:
URL: https://github.com/apache/cloudstack-primate/pull/364#discussion_r431012633



##
File path: src/views/compute/DeployVM.vue
##
@@ -80,6 +80,25 @@
 :options="keyboardSelectOptions"
   >
 
+
+  
+
+  {{ bootType.description }}
+
+  
+
+
+  
+
+  {{ bootMode.description }}
+
+  
+

Review comment:
   This needs to be for vmware and kvm only i think





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 closed pull request #365: Dummy primate commit - testing submodule

[GitBox]

rhtyd closed pull request #365:
URL: https://github.com/apache/cloudstack-primate/pull/365


   



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 opened a new pull request #366: dummy testing

[GitBox]

rhtyd opened a new pull request #366:
URL: https://github.com/apache/cloudstack-primate/pull/366


   



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 opened a new pull request #365: Dummy primate commit - testing submodule

[GitBox]

rhtyd opened a new pull request #365:
URL: https://github.com/apache/cloudstack-primate/pull/365


   



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] utchoang opened a new pull request #364: Add boottype and bootmode to VM instance

[GitBox]

utchoang opened a new pull request #364:
URL: https://github.com/apache/cloudstack-primate/pull/364


   



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