[GitHub] [cloudstack-documentation] DaanHoogland commented on a change in pull request #145: Modified project details - role based users in projects

[GitBox]

DaanHoogland commented on a change in pull request #145:
URL: 
https://github.com/apache/cloudstack-documentation/pull/145#discussion_r468376042



##
File path: source/adminguide/projects.rst
##
@@ -32,17 +32,33 @@ You can configure CloudStack to allow any user to create a 
new project,
 or you can restrict that ability to just CloudStack administrators. Once
 you have created a project, you become that project’s administrator, and
 you can add others within your domain to the project. CloudStack can be
-set up either so that you can add people directly to a project, or so
-that you have to send an invitation which the recipient must accept.
-Project members can view and manage all virtual resources created by
-anyone in the project (for example, share VMs). A user can be a member
-of any number of projects and can switch views in the CloudStack UI to
-show only project-related information, such as project VMs, fellow
-project members, project-related alerts, and so on.
-
-The project administrator can pass on the role to another project
-member. The project administrator can also add more members, remove
-members from the project, set new resource limits (as long as they are
+set up to either add people directly to a project, or to send an
+invitation which the recipient must accept. Project members can view
+and manage all virtual resources created by anyone in the project
+(for example, share VMs). A user can be a member of any number of projects
+and can switch views in the CloudStack UI to show only project-related 
information,
+such as project VMs, fellow project members, project-related alerts, and so on.
+
+From CloudStack 4.15 onwards, it is possible for a project to have
+multiple project administrators and to add/invite specific users of
+an account to a project in addition to adding accounts. By means of
+Project Roles associated with a user or an account of the project,
+it is possible to restrict access of users in a project, i.e., in
+addition to account-level roles, one can further restrict access to
+operations (or APIs) by associating a project-level role to the
+user or account.
+
+**NOTE:** Project Roles work over Account level Roles. If a user/account is
+added to a project without a project role, it would imply that the
+user / account added will have access to all APIs that are made available
+by the Account level role. If there are no specific deny rules in the
+project role, it would again fallback onto the account-level role to decide
+whether the user has permissions to perform a specific action.
+

Review comment:
   i would like to see a second note to make clear that a user's rights can 
not be widened in comparison to their account role but only restricted.

##
File path: source/adminguide/projects.rst
##
@@ -280,36 +296,21 @@ feature is enabled in the cloud as described in `“Setting
 Up Invitations” <#setting-up-invitations>`_. If the invitations feature is
 not turned on, use the procedure in Adding Project Members From the UI.
 
-#. Log in to the CloudStack UI.
+#. Log in to the CloudStack Primate UI.
 
 #. In the left navigation, click Projects.
 
-#. In Select View, choose Projects.
-
 #. Click the name of the project you want to work with.
 
-#. Click the Invitations tab.
+#. Click on the `Add Account to Project` button. This will have 2 tabs, one to 
add account to the project and the other to add a user to the project. Here, we 
can specify the:
 
-#. In Add by, select one of the following:
+  - account or user and/or email id of the user to be invited,
+  - (Optional) the Role i.e, Admin or Regular that the user is to be added 
as, defualts to Regular role,
+  - (Optional) the Project role specifying the list of APIs the user is 
allowed/ denied access to
 
-   #. Account – The invitation will appear in the user’s Invitations tab
-  in the Project View. See Using the Project View.
+   You can invite only people who have an account in this cloud within the 
same domain as the project. However, you can send the invitation to any email 
address.
 
-   #. Email – The invitation will be sent to the user’s email address.
-  Each emailed invitation includes a unique code called a token
-  which the recipient will provide back to CloudStack when accepting
-  the invitation. Email invitations will work only if the global
-  parameters related to the SMTP server have been set. See
-  `“Setting Up Invitations” <#setting-up-invitations>`_.
-
-#. Type the user name or email address of the new member you want to
-   add, and click Invite. Type the CloudStack user name if you chose
-   Account in the previous step. If you chose Email, type the email
-   address. You can invite only people who have an account in this cloud
-   within the same domain as the project. However, you can send the
-   invitation to any email address.
-
-#. To view and manage the invitations you have sent, return to this tab.
+5. To

[GitHub] [cloudstack-documentation] Pearl1594 commented on a change in pull request #145: Modified project details - role based users in projects

[GitBox]

Pearl1594 commented on a change in pull request #145:
URL: 
https://github.com/apache/cloudstack-documentation/pull/145#discussion_r468380481



##
File path: source/adminguide/projects.rst
##
@@ -280,36 +296,21 @@ feature is enabled in the cloud as described in `“Setting
 Up Invitations” <#setting-up-invitations>`_. If the invitations feature is
 not turned on, use the procedure in Adding Project Members From the UI.
 
-#. Log in to the CloudStack UI.
+#. Log in to the CloudStack Primate UI.
 
 #. In the left navigation, click Projects.
 
-#. In Select View, choose Projects.
-
 #. Click the name of the project you want to work with.
 
-#. Click the Invitations tab.
+#. Click on the `Add Account to Project` button. This will have 2 tabs, one to 
add account to the project and the other to add a user to the project. Here, we 
can specify the:
 
-#. In Add by, select one of the following:
+  - account or user and/or email id of the user to be invited,
+  - (Optional) the Role i.e, Admin or Regular that the user is to be added 
as, defualts to Regular role,
+  - (Optional) the Project role specifying the list of APIs the user is 
allowed/ denied access to
 
-   #. Account – The invitation will appear in the user’s Invitations tab
-  in the Project View. See Using the Project View.
+   You can invite only people who have an account in this cloud within the 
same domain as the project. However, you can send the invitation to any email 
address.
 
-   #. Email – The invitation will be sent to the user’s email address.
-  Each emailed invitation includes a unique code called a token
-  which the recipient will provide back to CloudStack when accepting
-  the invitation. Email invitations will work only if the global
-  parameters related to the SMTP server have been set. See
-  `“Setting Up Invitations” <#setting-up-invitations>`_.
-
-#. Type the user name or email address of the new member you want to
-   add, and click Invite. Type the CloudStack user name if you chose
-   Account in the previous step. If you chose Email, type the email
-   address. You can invite only people who have an account in this cloud
-   within the same domain as the project. However, you can send the
-   invitation to any email address.
-
-#. To view and manage the invitations you have sent, return to this tab.
+5. To view and manage the invitations you have sent, return to this tab.

Review comment:
   done





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 a change in pull request #145: Modified project details - role based users in projects

[GitBox]

Pearl1594 commented on a change in pull request #145:
URL: 
https://github.com/apache/cloudstack-documentation/pull/145#discussion_r468380657



##
File path: source/adminguide/projects.rst
##
@@ -32,17 +32,33 @@ You can configure CloudStack to allow any user to create a 
new project,
 or you can restrict that ability to just CloudStack administrators. Once
 you have created a project, you become that project’s administrator, and
 you can add others within your domain to the project. CloudStack can be
-set up either so that you can add people directly to a project, or so
-that you have to send an invitation which the recipient must accept.
-Project members can view and manage all virtual resources created by
-anyone in the project (for example, share VMs). A user can be a member
-of any number of projects and can switch views in the CloudStack UI to
-show only project-related information, such as project VMs, fellow
-project members, project-related alerts, and so on.
-
-The project administrator can pass on the role to another project
-member. The project administrator can also add more members, remove
-members from the project, set new resource limits (as long as they are
+set up to either add people directly to a project, or to send an
+invitation which the recipient must accept. Project members can view
+and manage all virtual resources created by anyone in the project
+(for example, share VMs). A user can be a member of any number of projects
+and can switch views in the CloudStack UI to show only project-related 
information,
+such as project VMs, fellow project members, project-related alerts, and so on.
+
+From CloudStack 4.15 onwards, it is possible for a project to have
+multiple project administrators and to add/invite specific users of
+an account to a project in addition to adding accounts. By means of
+Project Roles associated with a user or an account of the project,
+it is possible to restrict access of users in a project, i.e., in
+addition to account-level roles, one can further restrict access to
+operations (or APIs) by associating a project-level role to the
+user or account.
+
+**NOTE:** Project Roles work over Account level Roles. If a user/account is
+added to a project without a project role, it would imply that the
+user / account added will have access to all APIs that are made available
+by the Account level role. If there are no specific deny rules in the
+project role, it would again fallback onto the account-level role to decide
+whether the user has permissions to perform a specific action.
+

Review comment:
   Added relevant details





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 #145: Modified project details - role based users in projects

[GitBox]

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


   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 #145: Modified project details - role based users in projects

[GitBox]

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


   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 #145: Modified project details - role based users in projects

[GitBox]

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


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr145
   
   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 #145: Modified project details - role based users in projects

[GitBox]

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


   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 #145: Modified project details - role based users in projects

[GitBox]

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


   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 #145: Modified project details - role based users in projects

[GitBox]

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


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr145
   
   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-primate] rhtyd merged pull request #572: Fixing Edit ACL

[GitBox]

rhtyd merged pull request #572:
URL: https://github.com/apache/cloudstack-primate/pull/572


   



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 issue #570: Error when editing firewall rule

[GitBox]

rhtyd closed issue #570:
URL: https://github.com/apache/cloudstack-primate/issues/570


   



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 #575: Adding Account Switcher for SAML Accounts

[GitBox]

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


   @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

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #575: Adding Account Switcher for SAML Accounts

[GitBox]

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


   @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] rhtyd merged pull request #569: Adding development docs

[GitBox]

rhtyd merged pull request #569:
URL: https://github.com/apache/cloudstack-primate/pull/569


   



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 #569: Adding development docs

[GitBox]

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


   LGTM



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 issue #361: [FEATURE] Fresh install onboarding

[GitBox]

rhtyd closed issue #361:
URL: https://github.com/apache/cloudstack-primate/issues/361


   



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 #566: a few issues.

[GitBox]

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


   Ping @gaaray2k - we're unable to reproduce any issues wrt #1 - if you're 
unable to provide steps to reproduce issue, then can we close this?



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 #361: [FEATURE] Fresh install onboarding

[GitBox]

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


   Has PR



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 #571: [BUG] Creating Basic Type Zone not supported in primate UI ?

[GitBox]

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


   @a31amit We've been discussing deprecating basic zone in future release of 
CloudStack, all features of a basic zone are available with an Advance zone; 
for example, deploy an Advanced zone with SG or with only shared networks. For 
newer deployments, we want to promote users to only use Advanced zones (through 
UI, APIs and old UI will still continue to support deploying basic zone). 
References:
   https://github.com/apache/cloudstack/pull/2720
   https://github.com/apache/cloudstack/pull/2748
   
   Due to this in the new UI, Primate, we've not added support for adding a 
basic zone via the zone deployment wizard, however, any existing basic zone 
will continue to work with Primate. If there is a reason why it must be 
supported, please start a discussion thread on the CloudStack dev mailing list.



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 #556: German translation

[GitBox]

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


   Ping @onitake @svenvogel @utchoang 



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 #575: Adding Account Switcher for SAML Accounts

[GitBox]

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


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



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 #320: Explore Test Automation

[GitBox]

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


   Thanks @utchoang I'll merge this soon after the last few open PRs towards 
1.0/GA milestone
   @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

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #320: Explore Test Automation

[GitBox]

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


   @rhtyd 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] blueorangutan commented on pull request #320: Explore Test Automation

[GitBox]

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


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



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 #575: Adding Account Switcher for SAML Accounts

[GitBox]

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


   @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

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #575: Adding Account Switcher for SAML Accounts

[GitBox]

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


   @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 commented on pull request #574: Adding metrics cell coloring based on threshold

[GitBox]

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


   @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,

Thanks for explaining - you're correct the direct download for templates 
feature is to bypass secondary storage.


Regards.


From: Pierre-Luc Dion 
Sent: Monday, August 10, 2020 23:59
To: dev@cloudstack.apache.org 
Cc: Serge Nassar ; Siddhartha Kattoju 
Subject: Re: [PROPOSAL] boot from network template on XenServer

Hi Rohit,

It is actually not quite the same.  the boot from network we are working on
is for a use case where the boot volume is on a streaming server basically,
so we need instance to boot from network to load the OS from that streaming
server basically. The template that would be created in CloudStack would
just refer to which FILENAME on the TFTP server would be used to boot. the
TFTP server IP would be defined at the VPC level.


the feature you describe for KVM is basically a way to register a regular
full template but send it directly to the PrimaryStorage instead of having
it in the Secondary Storage first, correct ?

Cheers,

On Sun, Aug 9, 2020 at 11:33 AM Rohit Yadav 
wrote:

> 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 <
> snas...@cloud.ca>; 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
>
>
>
>

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

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #575: Adding Account Switcher for SAML Accounts

[GitBox]

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


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



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: Unable to ping secondary NIC ip of a VM in VPC

[Rakesh Venkatesh]

Wei,

This was the test done on ubuntu os. The initial issue was found on windows
vm.

Even if it can be solved by adding some config inside the vm, do we need to
do every time we delete/add additional NIC's to vm? That will be extra work
all the time right?

On Mon, Aug 10, 2020 at 5:43 PM Wei ZHOU  wrote:

> Hi Rakesh,
>
> It is not a bug. you need to configure the networks inside vm. for example
> /etc/network/interfaces in old ubuntu versions or /etc/netplan in newer
> ubuntu versions.
>
> -Wei
>
> On Monday, 10 August 2020, Rakesh Venkatesh 
> wrote:
>
> > Hello Thomas
> >
> >
> > Thanks for the reply. It looks like the NIC is not configured properly in
> > VM. I dont see IP 10.10.2.23 being configured
> >
> > # ip a
> > 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
> > default qlen 1
> > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > inet 127.0.0.1/8 scope host lo
> >valid_lft forever preferred_lft forever
> > inet6 ::1/128 scope host
> >valid_lft forever preferred_lft forever
> > 2: eth0:  mtu 1500 qdisc pfifo_fast
> state
> > UP group default qlen 1000
> > link/ether 02:00:78:24:00:01 brd ff:ff:ff:ff:ff:ff
> > inet 10.10.1.51/24 brd 10.10.1.255 scope global eth0
> >valid_lft forever preferred_lft forever
> > inet6 fe80::78ff:fe24:1/64 scope link
> >valid_lft forever preferred_lft forever
> > 3: eth1:  mtu 1500 qdisc noop state DOWN group
> default
> > qlen 1000
> > link/ether 02:00:1f:ed:00:0e brd ff:ff:ff:ff:ff:ff
> >
> >
> >
> > I removed the secondary NIC, stopped the vm, added secondary NIC and
> > started the VM. The extra NIC is still not configured in VM.
> > Is this a bug?
> >
> > On Mon, Aug 10, 2020 at 4:46 PM Thomas Joseph 
> > wrote:
> >
> > > Hello Venkatesh,
> > >
> > > I'm guessing from the output provided that you have tried to ping the
> ip
> > > from the VR.
> > > Have you checked if the NIC is up on the VM?
> > >  you can run tcpdump on the related VM to check if the icmp packets are
> > > reaching the VM.
> > >
> > > Regards
> > > Thomas
> > >
> > > On Mon, 10 Aug 2020, 8:06 pm Rakesh Venkatesh, <
> > www.rakeshv@gmail.com>
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > I have created a VPC with three tiers in it (tier1, tier2. tier3)
> using
> > > > cloudstack 4.14.0.0 version with Ubuntu16 as OS for mgt, agent
> > > > I created a VM in tier1 and I am able to ping its IP address
> > > >
> > > > # ping 10.10.1.51
> > > > PING 10.10.1.51 (10.10.1.51): 56 data bytes
> > > > 64 bytes from 10.10.1.51: icmp_seq=0 ttl=64 time=2.273 ms
> > > > 64 bytes from 10.10.1.51: icmp_seq=1 ttl=64 time=1.690 ms
> > > > ^C--- 10.10.1.51 ping statistics ---
> > > >
> > > >
> > > > After adding secondary NIC to vm from tier2 or tier3 then I am not
> able
> > > to
> > > > ping that IP address.
> > > >
> > > > # ping 10.10.2.23
> > > > PING 10.10.2.23 (10.10.2.23): 56 data bytes
> > > > 92 bytes from 10.10.2.254: Destination Host Unreachable
> > > > 92 bytes from 10.10.2.254: Destination Host Unreachable
> > > > 92 bytes from 10.10.2.254: Destination Host Unreachable
> > > > 92 bytes from 10.10.2.254: Destination Host Unreachable
> > > > ^C--- 10.10.2.23 ping statistics ---
> > > >
> > > >
> > > >
> > > > Dchphost content
> > > >
> > > > # cat /etc/dhcphosts.txt
> > > > 02:00:72:36:00:01,10.10.2.83,tier12,infinite
> > > > 02:00:2f:16:00:0c,set:10_10_2_23,10.10.2.23,tier11,infinite
> > > > 02:00:78:24:00:01,10.10.1.51,tier11,infinite
> > > >
> > > >
> > > >
> > > > Dhcpopts content
> > > >
> > > >
> > > > # cat /etc/dhcpopts.txt
> > > > 10_10_2_23,3
> > > > 10_10_2_23,6
> > > > 10_10_2_23,15
> > > >
> > > >
> > > > I don't see any errors in /var/log/cloud.log on VR when secondary nic
> > is
> > > > added.
> > > > Is there any other I can troubleshoot this or look for logs?
> > > >
> > > > --
> > > > Thanks and regards
> > > > Rakesh
> > > >
> > >
> >
> >
> > --
> > Thanks and regards
> > Rakesh venkatesh
> >
>


-- 
Thanks and regards
Rakesh venkatesh

[GitHub] [cloudstack-primate] rhtyd commented on pull request #574: Adding metrics cell coloring based on threshold

[GitBox]

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


   @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

[GitHub] [cloudstack-primate] rhtyd commented on a change in pull request #574: Adding metrics cell coloring based on threshold

[GitBox]

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



##
File path: src/components/view/ListView.vue
##
@@ -537,4 +593,16 @@ export default {
 }
 
   }
+
+  .alert-notification-threshold {
+background-color: rgba(255, 231, 175, 0.75);
+color: #e87900;
+padding: 10%;

Review comment:
   @davidjumani instead of percentage should we say 10px?





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] gaaray2k commented on issue #566: a few issues.

[GitBox]

gaaray2k commented on issue #566:
URL: 
https://github.com/apache/cloudstack-primate/issues/566#issuecomment-671874863


   I'll do this today



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

[DISCUSS] Primate review and testing wrt 1.0/GA

[Rohit Yadav]

All,

Here's the latest update on Primate:

  *   We've completed execution of full test plans on Primate and addresses 
issues/bugs:
https://github.com/apache/cloudstack-primate/issues?q=is%3Aissue+is%3Aclosed+label%3Atesting+test+plan
  *   Overall we think we've reached feature parity against old UI and Primate 
is stable
  *   Milestone link (mostly new features from CloudStack master/4.15 
outstanding): https://github.com/apache/cloudstack-primate/milestone/2

Actions and collaboration requested wrt Primate 1.0/GA milestone:

  *   Kindly review and test latest Primate master in your environments. For 
convenience daily builds from master are available here: (rpm, deb and archive)
  *   http://download.cloudstack.org/primate/testing/master/
  *   Review the Primate install/customisation doc PR: 
https://github.com/apache/cloudstack-documentation/pull/142
  *   Users can review/verify or contribute translations, see Nicolas's email 
thread on this topic before: https://markmail.org/message/2lzmseg2atyt2ayf
  *   Devs can go through the development guide and participate in development: 
https://github.com/apache/cloudstack-primate/blob/master/docs/development.md

Thanks and regards.

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

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #573: Adding onboarding dashboard

[GitBox]

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


   @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 commented on pull request #573: Adding onboarding dashboard

[GitBox]

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


   @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

[GitHub] [cloudstack-primate] davidjumani commented on a change in pull request #574: Adding metrics cell coloring based on threshold

[GitBox]

davidjumani commented on a change in pull request #574:
URL: https://github.com/apache/cloudstack-primate/pull/574#discussion_r468504917



##
File path: src/components/view/ListView.vue
##
@@ -537,4 +593,16 @@ export default {
 }
 
   }
+
+  .alert-notification-threshold {
+background-color: rgba(255, 231, 175, 0.75);
+color: #e87900;
+padding: 10%;

Review comment:
   px works fine for a larger screen but percentage works better when with 
mobile!





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 a change in pull request #574: Adding metrics cell coloring based on threshold

[GitBox]

davidjumani commented on a change in pull request #574:
URL: https://github.com/apache/cloudstack-primate/pull/574#discussion_r468504917



##
File path: src/components/view/ListView.vue
##
@@ -537,4 +593,16 @@ export default {
 }
 
   }
+
+  .alert-notification-threshold {
+background-color: rgba(255, 231, 175, 0.75);
+color: #e87900;
+padding: 10%;

Review comment:
   px works fine for a larger screen but percentage works better when with 
mobile and regular screen sizes!





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-671889693


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

[GitBox]

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


   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 #573: Adding onboarding dashboard

[GitBox]

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


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



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-671890700


   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-671892112


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

[GitBox]

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


   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 #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-671893126


   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] GabrielBrascher commented on a change in pull request #145: Modified project details - role based users in projects

[GitBox]

GabrielBrascher commented on a change in pull request #145:
URL: 
https://github.com/apache/cloudstack-documentation/pull/145#discussion_r468536864



##
File path: source/adminguide/projects.rst
##
@@ -32,17 +32,38 @@ You can configure CloudStack to allow any user to create a 
new project,
 or you can restrict that ability to just CloudStack administrators. Once
 you have created a project, you become that project’s administrator, and
 you can add others within your domain to the project. CloudStack can be
-set up either so that you can add people directly to a project, or so
-that you have to send an invitation which the recipient must accept.
-Project members can view and manage all virtual resources created by
-anyone in the project (for example, share VMs). A user can be a member
-of any number of projects and can switch views in the CloudStack UI to
-show only project-related information, such as project VMs, fellow
-project members, project-related alerts, and so on.
-
-The project administrator can pass on the role to another project
-member. The project administrator can also add more members, remove
-members from the project, set new resource limits (as long as they are
+set up to either add people directly to a project, or to send an
+invitation which the recipient must accept. Project members can view
+and manage all virtual resources created by anyone in the project
+(for example, share VMs). A user can be a member of any number of projects
+and can switch views in the CloudStack UI to show only project-related 
information,
+such as project VMs, fellow project members, project-related alerts, and so on.
+
+From CloudStack 4.15 onwards, it is possible for a project to have
+multiple project administrators and to add/invite specific users of
+an account to a project in addition to adding accounts. By means of
+Project Roles associated with a user or an account of the project,
+it is possible to restrict access of users in a project, i.e., in
+addition to account-level roles, one can further restrict access to
+operations (or APIs) by associating a project-level role to the
+user or account. However, If an account has already been added, one will not
+be able to associate a role a specific user of that account.
+
+**NOTE:** Project Roles work over Account level Roles. If a user/account is
+added to a project without a project role, it would imply that the
+user / account added will have access to all APIs that are made available
+by the Account level role. If there are no specific deny rules in the
+project role, it would again fallback onto the account-level role to decide
+whether the user has permissions to perform a specific action. It is also to be
+noted that Project roles are restricictive in nature, i.e., to say that, one 
may

Review comment:
   restricictive :arrow_right: restrictive

##
File path: source/adminguide/projects.rst
##
@@ -32,17 +32,38 @@ You can configure CloudStack to allow any user to create a 
new project,
 or you can restrict that ability to just CloudStack administrators. Once
 you have created a project, you become that project’s administrator, and
 you can add others within your domain to the project. CloudStack can be
-set up either so that you can add people directly to a project, or so
-that you have to send an invitation which the recipient must accept.
-Project members can view and manage all virtual resources created by
-anyone in the project (for example, share VMs). A user can be a member
-of any number of projects and can switch views in the CloudStack UI to
-show only project-related information, such as project VMs, fellow
-project members, project-related alerts, and so on.
-
-The project administrator can pass on the role to another project
-member. The project administrator can also add more members, remove
-members from the project, set new resource limits (as long as they are
+set up to either add people directly to a project, or to send an
+invitation which the recipient must accept. Project members can view
+and manage all virtual resources created by anyone in the project
+(for example, share VMs). A user can be a member of any number of projects
+and can switch views in the CloudStack UI to show only project-related 
information,
+such as project VMs, fellow project members, project-related alerts, and so on.
+
+From CloudStack 4.15 onwards, it is possible for a project to have
+multiple project administrators and to add/invite specific users of
+an account to a project in addition to adding accounts. By means of
+Project Roles associated with a user or an account of the project,
+it is possible to restrict access of users in a project, i.e., in
+addition to account-level roles, one can further restrict access to
+operations (or APIs) by associating a project-level role to the
+user or account. However, If an account has already been added, one will not

Review comment:
   `However, If` :arrow_right: `Ho

[GitHub] [cloudstack-documentation] GabrielBrascher commented on pull request #145: Modified project details - role based users in projects

[GitBox]

GabrielBrascher commented on pull request #145:
URL: 
https://github.com/apache/cloudstack-documentation/pull/145#issuecomment-671915031


   @Pearl1594 @DaanHoogland Is this still draft or can we put it into "Ready 
for review"?



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 #145: Modified project details - role based users in projects

[GitBox]

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


   @GabrielBrascher I've addressed your comments. Thanks for pointing them out.



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 #145: Modified project details - role based users in projects

[GitBox]

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


   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 #145: Modified project details - role based users in projects

[GitBox]

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


   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 commented on pull request #145: Modified project details - role based users in projects

[GitBox]

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


   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr145
   
   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-primate] gaaray2k closed issue #566: a few issues.

[GitBox]

gaaray2k closed issue #566:
URL: https://github.com/apache/cloudstack-primate/issues/566


   



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 pull request #556: German translation

[GitBox]

utchoang commented on pull request #556:
URL: 
https://github.com/apache/cloudstack-primate/pull/556#issuecomment-672417662


   @svenvogel Do you think you need to change something more?



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] a31amit commented on issue #571: [BUG] Creating Basic Type Zone not supported in primate UI ?

[GitBox]

a31amit commented on issue #571:
URL: 
https://github.com/apache/cloudstack-primate/issues/571#issuecomment-672485721


   @rhtyd Thanks for the explaining. I don't have any reason to use BasicZone 
If I could do the same thing with AdvancedZone. just a thought that may be 
having the same info in the release or additional deprecation docs would help 
users more. 



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 #548: Add storage policies field for DiskOffering and Primary storage creation Forms

[GitBox]

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


   @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

[GitHub] [cloudstack-primate] davidjumani commented on pull request #326: Form to Migrate data between Image stores

[GitBox]

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


   @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

[GitHub] [cloudstack-primate] blueorangutan commented on pull request #548: Add storage policies field for DiskOffering and Primary storage creation Forms

[GitBox]

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


   @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] blueorangutan commented on pull request #326: Form to Migrate data between Image stores

[GitBox]

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


   @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] blueorangutan commented on pull request #548: Add storage policies field for DiskOffering and Primary storage creation Forms

[GitBox]

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


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



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 #326: Form to Migrate data between Image stores

[GitBox]

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


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



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