[GitHub] [cloudstack-documentation] Pearl1594 commented on pull request #142: Added basic and advanced customization sections to the primate doc

[GitBox]

Pearl1594 commented on pull request #142:
URL: 
https://github.com/apache/cloudstack-documentation/pull/142#issuecomment-671193819


   Looks good



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 #142: Added basic and advanced customization sections to the primate doc

[GitBox]

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


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr142
   
   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 #142: Added basic and advanced customization sections to the primate doc

[GitBox]

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


   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] Pearl1594 commented on pull request #142: Added basic and advanced customization sections to the primate doc

[GitBox]

Pearl1594 commented on pull request #142:
URL: 
https://github.com/apache/cloudstack-documentation/pull/142#issuecomment-671182311


   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-primate] blueorangutan commented on pull request #572: Fixing Edit ACL

[GitBox]

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


   Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian 
:heavy_check_mark:archive.
   QA: http://primate-qa.cloudstack.cloud:8080/client/pr/572 (JID-3012)



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] blueorangutan commented on pull request #572: Fixing Edit ACL

[GitBox]

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


   @davidjumani a Jenkins job has been kicked to build primate packages. I'll 
keep you posted as I make progress.



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] davidjumani opened a new pull request #572: Fixing Edit ACL

[GitBox]

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


   Fixes #570 
   
   Adding defensive checks for form values and refactoring



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] davidjumani commented on pull request #572: Fixing Edit ACL

[GitBox]

davidjumani commented on pull request #572:
URL: 
https://github.com/apache/cloudstack-primate/pull/572#issuecomment-671157333


   @blueorangutan package



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: [PROPOSAL] boot from network template on XenServer

[Rohit Yadav]

Hi PL,

Good to hear from you!

If you've a use-case where templates are created/hosted separately and may 
change often, could your use-case work by extending the direct-download feature 
for XenServer?
Here are some links for the KVM support:

http://docs.cloudstack.apache.org/en/latest/adminguide/templates.html#bypassing-secondary-storage-for-kvm-templates
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Bypass+Secondary+Storage+%28Direct+Download%29+on+KVM
https://www.shapeblue.com/cloudstack-feature-first-look-direct-download-agnostic-of-the-storage-provider/



Regards.


From: Pierre-Luc Dion 
Sent: Saturday, August 8, 2020 20:06
To: dev@cloudstack.apache.org ; Serge Nassar 
; Siddhartha Kattoju 
Subject: [PROPOSAL] boot from network template on XenServer

Hi guys, it's been a while!

I'd like to know what would be the path to follow within the community to
submit a feature into cloudstack, but also to review our proposal on
offering a template that boots from the network.

Basic idea, is that there is some workload, specially for XenDesktop where
desktop images are hosted on a PVS server, to ease support of that workload
in cloudstack, it kind of make sense that a Instance would boot from the
network and load is root volume image from the PVS server. So what we
recently tried in a VPC model, is to add a configuration at the VPC level
to define the IP address of a TFTP server so the DHCP of the VR push the
next_server ip defined in the VPC config, then we create a template where
the URL is to boot file path on the tftp server that can reside outside of
a vpc. At the VM creation using this template, the boot order of the
instance on XenServer is to boot from the network and the root volume
created is an empty volume that can be used as ephemeral or storage for
caching.

Cheers,

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

Re: apidocs build failure

[Rohit Yadav]

Thanks Sina, we'll review and merge soon.


Regards.


From: Sina Kashipazha 
Sent: Saturday, August 8, 2020 17:49
To: dev@cloudstack.apache.org 
Subject: Re: apidocs build failure

Hi Rohit,

I created the following pr that fixed the apidoc issue in Mac.

https://github.com/apache/cloudstack/pull/4253 



Kind Regards,
Sina


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

> On 11 Jun 2020, at 05:47, Rohit Yadav  wrote:
>
> I think you've found the difference in BSD vs GNU/Linux sed on Mac 
> (https://github.com/apache/cloudstack/pull/3312). One way to fix on Macs 
> could be to install GNU sed using brew.
> Pull requests are welcome Sina!
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Sina Kashipazha 
> Sent: Wednesday, June 10, 2020 01:58
> To: dev@cloudstack.apache.org 
> Subject: Re: apidocs build failure
>
> Hi Rohit,
>
> Thanks for your suggestion to run the build command manually. I found the 
> problem. Build script of apidocs used the sed inline replacement option, 
> which has a different signature in MAC OS. I added '' after -i option of sed 
> command in the below lines, and it fixed my problem.
>
> https://github.com/apache/cloudstack/blob/fbfab5b5ebe1dba1000abbe30a8703c4d2f9d371/tools/apidoc/build-apidoc.sh#L64
>  
> 
> https://github.com/apache/cloudstack/blob/fbfab5b5ebe1dba1000abbe30a8703c4d2f9d371/tools/apidoc/build-apidoc.sh#L65
>  
> 
>
> More information:
>
> https://stackoverflow.com/questions/7573368/in-place-edits-with-sed-on-os-x?rq=1
>  
> 
> https://stackoverflow.com/questions/5694228/sed-in-place-flag-that-works-both-on-mac-bsd-and-linux
>  
> 
>
> Kind Regards,
> Sina
>
>
> On 2020/06/09 03:07:49, Rohit Yadav  wrote:
>> Hi Sina,>
>>
>>
>>
>> Are you seeing this on latest master? You can debug what's causing failure 
>> by either running the mvn command for -pl tools/apidocs, or run the command 
>> manually:>
>>
>> https://github.com/apache/cloudstack/blob/master/tools/apidoc/pom.xml#L63>
>>
>>
>>
>> It could a jdk/java issue, you may install jenv and add jdk8 or jdk11 
>> installed (depending on which branch you're on, for 4.14 and master use 
>> jdk11 for example).>
>>
>>
>>
>>
>>
>> Regards,>
>>
>>
>>
>> Rohit Yadav>
>>
>>
>>
>> Software Architect, ShapeBlue>
>>
>>
>>
>> https://www.shapeblue.com>
>>
>>
>>
>> >
>>
>> From: Sina Kashipazha >
>>
>> Sent: Tuesday, June 9, 2020 02:03>
>>
>> To: dev@cloudstack.apache.org >
>>
>> Subject: apidocs build failure>
>>
>>
>>
>> Hi,>
>>
>>
>>
>> I have trouble building apidocs on mac (see below). Any idea?>
>>
>>
>>
>> Kind Regards,>
>>
>> Sina>
>>
>>
>>
>> [INFO] Apache CloudStack apidocs .. FAILURE [ 31.185 
>> s]>
>>
>> [INFO] Apache CloudStack marvin ... SKIPPED>
>>
>> [INFO] Apache CloudStack DevCloud4  SKIPPED>
>>
>> [INFO] Apache CloudStack DevCloud-KVM . SKIPPED>
>>
>> [INFO] 
>> >
>>
>> [INFO] BUILD FAILURE>
>>
>> [INFO] 
>> >
>>
>> [INFO] Total time: 22:03 h>
>>
>> [INFO] Finished at: 2020-06-08T21:01:37+02:00>
>>
>> [INFO] Final Memory: 132M/450M>
>>
>> [INFO] 
>> >
>>
>> [ERROR] Failed to execute goal 
>> org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project 
>> cloud-apidoc: Command execution failed. Process exited with an error: 1 
>> (Exit value: 1) -> [Help 1]>
>>
>> [ERROR]>
>>
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
>> switch.>
>>
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.>
>>
>> [ERROR]>
>>
>> [ERROR] For more information about the errors and possible solutions, please 
>> read the following articles:>
>>
>> [ERROR] [Help 1] 
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException>
>>
>> [ERROR]>
>>
>> [ERROR] After correcting the problems, you can resume the build with the 
>> command>
>>
>> [ERROR]   mvn  -rf :cloud-apidoc>
>>
>>
>>
>>
>>
>> rohit.ya...@shapeblue.com >
>>
>> www.shapeblue.com>
>>
>> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK>
>>
>> @shapeblue>
>>
>>>
>>