Re: [PROPOSE] Combining Apache CloudStack Documentation

2018-07-25 Thread Rohit Yadav 
+1 I like it, I'm okay with release notes being a separate (version specific) 
document/website.


- Rohit






From: Paul Angus 
Sent: Tuesday, July 24, 2018 2:55:26 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [PROPOSE] Combining Apache CloudStack Documentation

Hi All,

We currently have four sources of documentation [1]. Which make managing the 
documentation convoluted, and worse, make navigating and searching the 
documentation really difficult.

I have taken the current documentation and combined them into one repo, then 
created 7 sections:

CloudStack Concepts and Terminology
Quick Installation Guide
Installation Guide
Usage Guide
Developers Guide
Plugins Guide
Release Notes

I haven't changed any of the content, but I've moved some of it around to make 
more sense (to me).  You can see the result on RTD [2]

I'd like to PROPOSE to move this demo version of the documentation over to the 
Apache repos and make it THE documentation source, update the website, and mark 
the current repos/sites as archive data.

[1]
https://github.com/apache/cloudstack-docs.git 
 is a bit of a dodge-podge of 
resources
https://github.com/apache/cloudstack-docs-install.git is the install guide
https://github.com/apache/cloudstack-docs-admin.git is the current admin manual.
https://github.com/apache/cloudstack-docs-rn.git is the release notes for 
individual releases

[2]  https://beta-cloudstack-docs.readthedocs.io/en/latest/

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




rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

Re: [GitHub] rafaelweingartner commented on a change in pull request #2761: Add managed storage pool constraints to MigrateWithVolume API method

2018-07-25 Thread Tutkowski, Mike 
That is correct (that is how the old behavior worked).

On 7/25/18, 2:56 PM, "GitBox"  wrote:

rafaelweingartner commented on a change in pull request #2761: Add managed 
storage pool constraints to MigrateWithVolume API method
URL: https://github.com/apache/cloudstack/pull/2761#discussion_r205259766
 
 

 ##
 File path: 
engine/orchestration/src/main/java/com/cloud/vm/VirtualMachineManagerImpl.java
 ##
 @@ -2282,7 +2282,7 @@ protected void migrate(final VMInstanceVO vm, final 
long srcHostId, final Deploy
  * Create the mapping of volumes and storage pools. If the user did 
not enter a mapping on her/his own, we create one using {@link 
#getDefaultMappingOfVolumesAndStoragePoolForMigration(VirtualMachineProfile, 
Host)}.
  * If the user provided a mapping, we use whatever the user has 
provided (check the method {@link 
#createMappingVolumeAndStoragePoolEnteredByUser(VirtualMachineProfile, Host, 
Map)}).
  */
-private Map 
getPoolListForVolumesForMigration(VirtualMachineProfile profile, Host 
targetHost, Map volumeToPool) {
+protected Map 
getPoolListForVolumesForMigration(VirtualMachineProfile profile, Host 
targetHost, Map volumeToPool) {
 
 Review comment:
   Ok, so to summarize. If the VM has two volumes, you want to be able to 
define the migration for one of them and the other that was not specified 
should be taken care by ACS. Is that it? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services