[GitHub] [cloudstack-documentation] rhtyd commented on a change in pull request #29: Fix the string to sign

[GitBox]

rhtyd commented on a change in pull request #29: Fix the string to sign
URL: 
https://github.com/apache/cloudstack-documentation/pull/29#discussion_r272058361
 
 

 ##
 File path: source/developersguide/dev.rst
 ##
 @@ -255,7 +255,7 @@ encoding:
 
 .. parsed-literal::
   
-   >>> 
sig_str='&'.join(['='.join([k.lower(),urllib.quote_plus(request[k].lower().replace('+','%20'))])for
 k in sorted(request.iterkeys())]) 
+   >>> 
sig_str='&'.join(['='.join([k.lower(),urllib.quote_plus(request[k]).lower().replace('+','%20')])for
 k in sorted(request.iterkeys())]) 
 
 Review comment:
   For reference, this is how cloudmonkey (python version) does it: 
https://github.com/apache/cloudstack-cloudmonkey/blob/5.3/cloudmonkey/requester.py#L203


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


With regards,
Apache Git Services

CloudStack NoVNC solution in Leaseweb

[Wei ZHOU]

Hello CloudStack developers and users,

We (as leaseweb) would like to share our NoVNC solution on our cloudstack
platforms with the CloudStack community . The feature was implemented in
2012 and we have made some changes since that. We have used it for more
than 7 years and it is very stable.

Unlike the pull request submitted by sachinnitw1317 (
https://github.com/apache/cloudstack/pull/2204 ) ,which is based on the
novnc as the front end (different from the cloudstack) and the java
websocket proxy (same as cloudstack) in console proxy vm (cpvm), we use
modified novnc and websockify to launch a websockify proxy in cpvm .

Here are some technical details:

(1) We use two open source projects: noVNC (https://github.com/novnc/noVNC
, 0.6.2) and websockify (https://github.com/novnc/websockify ,latest)
(2) We modified websockify so we can launch it without the target
server/port and token.
(3) We reuse the 'path' in novnc and websockify to pass some necessary vm
informations from cloudstack to novnc and websockify. path is encrypted in
cpvm / java, which contains target server,target port, vnc password, client
ip and timestamp. When a new client comes, websockify will decrypt 'path'
to get the vm informations above, and check if the client ip matches and
the timestamp has not expired.
(4) We moved the server/client initialization from novnc(js) to
websockify(python). When a new client comes, websockify will create a
websocket connection to the target server and port ,then check the protocol
version and authentication scheme, use the password in step (3) in vnc
authentication .
(5) Add a global setting in cloudstack for encryption in java and
decryption in websockify.

Compared to the cloudstack native console (ajax/java websocket proxy) and
the novnc console purposed in PR 2204 (novnc /java websocket proxy) , we
believe that the novnc console based on websockifty (written in python) is
more efficient than the consoles based on java websocket proxy.

If you have any questions or concerns, please feel free to ask. If nobody
objects, we will port our changes to cloudstack 4.11.2 LTS and submit a
pull request on cloudstack github, so everyone who is interested can merge
and build it in his/her fork and test it .

Considering that novnc and websockify are both open source projects, and we
also use some open source code (such as in pyDes.py VNC password
authentication) , it would be appreciated if anyone can help us on software
licensing issues.


Kind regards,

Wei Zhou
Principal Cloud Engineer
LEASEWEB

RE: Update Cloudstack 4.12.0.0 documentation

[Paul Angus]

@Gabriel Beims Bräscher

Have you set up an account on readthedocs.org?  can you send me you username 
please.

paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Paul Angus  
Sent: 03 April 2019 18:54
To: dev@cloudstack.apache.org
Subject: RE: Update Cloudstack 4.12.0.0 documentation

I can add you, but it'll be tomorrow now.  If you move the tag, for 4.12.0.0 it 
should automatically build.


paul.an...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
  
 


-Original Message-
From: Gabriel Beims Bräscher 
Sent: 03 April 2019 18:28
To: dev 
Subject: Update Cloudstack 4.12.0.0 documentation

Hello folks,

I have updated the documentation for 4.12.0.0 in the cloudstack-documentation 
project [1]. However, to synchronize the Apache CloudStack documentation [2] 
with [1] it is needed to run a build in readthedocs.org (if I am not mistaken).

I don't have enough "Karma" to access readthedocs.org to run the build; 
therefore, I need some help on this one from anyone that can log in and run the 
build :)

Does anyone know how such "Karma" is being provided?

Please correct me if I am missing any step on this build.
Thanks!

[1] https://github.com/apache/cloudstack-documentation/tree/4.12.0.0
[2] http://docs.cloudstack.apache.org

Re: CloudStack NoVNC solution in Leaseweb

[Fariborz Navidan]

Hello,

It's a great and valuable job because we have already observed that noVNC
integrated into control panels such as Virtualizor has great speed and
efficiency in comparison with CloudStack's native console proxy
implementation. Especially noVNC is more comfortable when user is on on a
low speed or high latency internet connection.

We were looking forward to investigate current CPVM and try to integrate
noVNC. It's pleasure to us that this has already been implemented and hope
we can take advantage of it in near future.

Best regards

On Thu, Apr 4, 2019 at 12:34 PM Wei ZHOU  wrote:

> Hello CloudStack developers and users,
>
> We (as leaseweb) would like to share our NoVNC solution on our cloudstack
> platforms with the CloudStack community . The feature was implemented in
> 2012 and we have made some changes since that. We have used it for more
> than 7 years and it is very stable.
>
> Unlike the pull request submitted by sachinnitw1317 (
> https://github.com/apache/cloudstack/pull/2204 ) ,which is based on the
> novnc as the front end (different from the cloudstack) and the java
> websocket proxy (same as cloudstack) in console proxy vm (cpvm), we use
> modified novnc and websockify to launch a websockify proxy in cpvm .
>
> Here are some technical details:
>
> (1) We use two open source projects: noVNC (https://github.com/novnc/noVNC
> , 0.6.2) and websockify (https://github.com/novnc/websockify ,latest)
> (2) We modified websockify so we can launch it without the target
> server/port and token.
> (3) We reuse the 'path' in novnc and websockify to pass some necessary vm
> informations from cloudstack to novnc and websockify. path is encrypted in
> cpvm / java, which contains target server,target port, vnc password, client
> ip and timestamp. When a new client comes, websockify will decrypt 'path'
> to get the vm informations above, and check if the client ip matches and
> the timestamp has not expired.
> (4) We moved the server/client initialization from novnc(js) to
> websockify(python). When a new client comes, websockify will create a
> websocket connection to the target server and port ,then check the protocol
> version and authentication scheme, use the password in step (3) in vnc
> authentication .
> (5) Add a global setting in cloudstack for encryption in java and
> decryption in websockify.
>
> Compared to the cloudstack native console (ajax/java websocket proxy) and
> the novnc console purposed in PR 2204 (novnc /java websocket proxy) , we
> believe that the novnc console based on websockifty (written in python) is
> more efficient than the consoles based on java websocket proxy.
>
> If you have any questions or concerns, please feel free to ask. If nobody
> objects, we will port our changes to cloudstack 4.11.2 LTS and submit a
> pull request on cloudstack github, so everyone who is interested can merge
> and build it in his/her fork and test it .
>
> Considering that novnc and websockify are both open source projects, and we
> also use some open source code (such as in pyDes.py VNC password
> authentication) , it would be appreciated if anyone can help us on software
> licensing issues.
>
>
> Kind regards,
>
> Wei Zhou
> Principal Cloud Engineer
> LEASEWEB
>

Re: CloudStack NoVNC solution in Leaseweb

[Rohit Yadav]

 Hi Wei,


Great to hear from you on this. Yes, it been a long time on the previous noVNC 
integration attempt by our GSoC student. The 4.11 branch is LTS and cannot 
accept new features, please use master (4.13) for the PR you'll submit. I can 
help with reviewing and testing.


The noVNC project has moved to 1.0.0 stable 
(https://github.com/novnc/noVNC/releases/tag/v1.0.0), do you think it would be 
difficult to adapt the stable 1.0.0 version and not use the old 0.6.2 release? 
Does your implementation also support secured websocket (using a tls 
certificate)?


To keep things turn-key, does it make sense to use C-based websockify or write 
our own Java based implementation that is in-built in the console proxy agent? 
I would prefer to reuse the java agent otherwise session/IP based 
authentication without checking with cloudstack may lead to some security issue.


Licensing:

We can ask for experts on the list and on asf-legal for advice but in my 
opinion we only need to ensure that the new licenses of the packages wrt the 
feature are compatible with Apache 2.0, largely allows redistributing (via 
systemvm.iso or a via new systemvmtemplate) with modifications:


1.0.0 license:https://github.com/novnc/noVNC/blob/v1.0.0/LICENSE.txt (MPL, BSD 
and MIT)

0.6.2 license: https://github.com/novnc/noVNC/blob/v0.6.2/LICENSE.txt (MPL, 
BSD, LGPL 3.0, Apache 2.0, MIT)


The main license is MPL and I think it allows for that: 
https://tldrlegal.com/license/mozilla-public-license-2.0-(mpl-2)


Other references:

https://tldrlegal.com/license/bsd-3-clause-license-(revised)
https://tldrlegal.com/license/gnu-lesser-general-public-license-v3-(lgpl-3)
https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)

https://tldrlegal.com/license/mit-license


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Wei ZHOU 
Sent: Thursday, April 4, 2019 1:34:24 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org; 
w.z...@global.leaseweb.com
Subject: CloudStack NoVNC solution in Leaseweb

Hello CloudStack developers and users,

We (as leaseweb) would like to share our NoVNC solution on our cloudstack
platforms with the CloudStack community . The feature was implemented in
2012 and we have made some changes since that. We have used it for more
than 7 years and it is very stable.

Unlike the pull request submitted by sachinnitw1317 (
https://github.com/apache/cloudstack/pull/2204 ) ,which is based on the
novnc as the front end (different from the cloudstack) and the java
websocket proxy (same as cloudstack) in console proxy vm (cpvm), we use
modified novnc and websockify to launch a websockify proxy in cpvm .

Here are some technical details:

(1) We use two open source projects: noVNC (https://github.com/novnc/noVNC
, 0.6.2) and websockify (https://github.com/novnc/websockify ,latest)
(2) We modified websockify so we can launch it without the target
server/port and token.
(3) We reuse the 'path' in novnc and websockify to pass some necessary vm
informations from cloudstack to novnc and websockify. path is encrypted in
cpvm / java, which contains target server,target port, vnc password, client
ip and timestamp. When a new client comes, websockify will decrypt 'path'
to get the vm informations above, and check if the client ip matches and
the timestamp has not expired.
(4) We moved the server/client initialization from novnc(js) to
websockify(python). When a new client comes, websockify will create a
websocket connection to the target server and port ,then check the protocol
version and authentication scheme, use the password in step (3) in vnc
authentication .
(5) Add a global setting in cloudstack for encryption in java and
decryption in websockify.

Compared to the cloudstack native console (ajax/java websocket proxy) and
the novnc console purposed in PR 2204 (novnc /java websocket proxy) , we
believe that the novnc console based on websockifty (written in python) is
more efficient than the consoles based on java websocket proxy.

If you have any questions or concerns, please feel free to ask. If nobody
objects, we will port our changes to cloudstack 4.11.2 LTS and submit a
pull request on cloudstack github, so everyone who is interested can merge
and build it in his/her fork and test it .

Considering that novnc and websockify are both open source projects, and we
also use some open source code (such as in pyDes.py VNC password
authentication) , it would be appreciated if anyone can help us on software
licensing issues.


Kind regards,

Wei Zhou
Principal Cloud Engineer
LEASEWEB

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: Add Cloudstack 4.12.0.0 on www.apache.org/dyn/closer.lua/cloudstack/

[Rohit Yadav]

Gabriel,


Yes, create an account of readthedocs.org (rtd) website and share your 
username/id with us. I'll add you to the project.

With respect to making changes, this is how we generally do it:


- Create ACS major version specific branch, such as 4.12 (forward merge changes 
to master, which would be for ACS master:4.13.0.0-SNAPSHOT)

- Once you're happy with all changes, create a tag on 4.12 such as 4.12.0.0 and 
push on the github ASF repo

- Once you've access on rtd project, you can go to admin and enable privacy 
(allow it) for 4.12.0.0 tag and build it. Usually RTD will build any tag you 
push.

- In case you think there are further changes necessary wrt 4.12.0.0, you'll 
need to delete old tag, re-tag it on 4.12 branch and repeat the process.



Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Gabriel Beims Bräscher 
Sent: Wednesday, April 3, 2019 6:17:03 PM
To: dev
Subject: Re: Add Cloudstack 4.12.0.0 on 
www.apache.org/dyn/closer.lua/cloudstack/

Thanks for the info Rohit! I will update the cloudstack-www 'asf-site'
branch with the correct source code link for 4.12.0.0.

Another question, regarding the documentation. How do I update the
CloudStack documentation [1] with the content of 4.12.0.0 [2]?
Do I need access to readthedocs.org?

Thanks!

[1] http://docs.cloudstack.apache.org
[2] https://github.com/apache/cloudstack-documentation/tree/4.12.0.0

Em qua, 3 de abr de 2019 às 09:28, Rohit Yadav 
escreveu:

> Gabriel,
>
>
> Once you've moved the candidate artifacts to releases, ASF infra will
> automatically mirror the release artifact except for checksum/signature
> files.
>
> I see that 4.12.0.0 is already moved at the correct path:
> https://dist.apache.org/repos/dist/release/cloudstack/releases/4.12.0.0/
>
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Gabriel Beims Br?scher 
> Sent: Wednesday, April 3, 2019 5:43:33 PM
> To: dev
> Subject: Add Cloudstack 4.12.0.0 on
> www.apache.org/dyn/closer.lua/cloudstack/
>
> Hello folks,
>
> I have updated the cloudstack.apache.org; however, I pointed the source
> link for 4.12.0.0 to [1]. Other releases (as 4.11.2.0 and CloudMonkey
> 6.0.0) point first to [2].
>
> How does it work to add a release source code to
> http://www.apache.org/dyn/closer.lua/cloudstack/releases/
> <
> http://www.apache.org/dyn/closer.lua/cloudstack/releases/cloudmonkey-6.0.0/apache-cloudstack-cloudmonkey-6.0.0-src.tar.bz2
> >
> ?
>
> Regards,
> Gabriel.
>
> [1]
>
> https://dist.apache.org/repos/dist/release/cloudstack/releases/4.12.0.0/apache-cloudstack-4.12.0.0-src.tar.bz2
> [2]
>
> http://www.apache.org/dyn/closer.lua/cloudstack/releases/cloudmonkey-6.0.0/apache-cloudstack-cloudmonkey-6.0.0-src.tar.bz2
> [3] http://www.apache.org/dyn/closer.lua/cloudstack/releases/
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

[GitHub] [cloudstack-documentation] DaanHoogland commented on issue #29: Fix the string to sign

[GitBox]

DaanHoogland commented on issue #29: Fix the string to sign
URL: 
https://github.com/apache/cloudstack-documentation/pull/29#issuecomment-479831867
 
 
   @cl-k-takahashi very clear, thank you.


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


With regards,
Apache Git Services

Re: CloudStack NoVNC solution in Leaseweb

[Rohit Yadav]

Great, thanks Wei. Looking forward to your PR.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Wei Zhou 
Sent: Thursday, April 4, 2019 3:20:13 PM
To: Rohit Yadav; dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: RE: CloudStack NoVNC solution in Leaseweb


Hi Rohit,



There are lots of changes between noVNC 1.0.0 and stable/0.6. Our codes is not 
compatible with noVNC 1.0.0. We can submit two pull requests, one with novnc 
stable/0.6 to cloudstack 4.11.2 LTS so 4.11.2 users can test it, another one 
with novnc 1.0.0 to cloudstack 4.13.



When CPVM starts and connects to management server, mgt server will send the 
cert/key to CPVM so CPVM saves them to local files, websockify proxy server is 
launched with the cert/key files.



The novnc console url is generated by cloudstack so session check is same as 
current cloudstack console. The url times out after 5 minutes and only the ip 
to cloudstack can access the url. I think there is no security issue with this 
part. The key used for 'path' encryption and decryption is sent from mgt server 
to CPVM and saved in websockify proxy as plain text, that might be a potential 
security issue. We use AES/rijndael to encrypt/decrypt the 'path' and DES in 
vnc password authentication, which should be secure.



We have tested PR 2204, we think python-based websockify is more stable and 
efficient than java-based websocket proxy. We did not test C-based websockify 
so I cannot say which one is better.



Thanks a lot for the information you provided.







​Kind regards,​


Wei Zhou

Principal Cloud Engineer
Leaseweb Global B.V.


[cid:image878037.png@B351532D.3F4F059A]  +31 20 316 
0230

[cid:image878221.png@7A321129.163EE812]  +31 6 1585 
5099

[cid:image661172.png@8CEF6C15.C2EE41B6]  
w.z...@global.leaseweb.com

[cid:image139378.png@A9FBC6D6.EBC749A7]  
www.leaseweb.com



[cid:image530862.png@A44EFC4A.18FE2535]

[cid:image925709.png@0BE69682.191C9591]
Luttenbergweg 8 ,   1101 EC Amsterdam   ,   
Netherlands


[Facebook]

[LinkedIn]

[Twitter]



Leaseweb is the brand name under which the various independent Leaseweb 
companies operate. Each company is a separate and distinct entity that provides 
services in a particular geographic area. Leaseweb Global B.V. does not provide 
third-party services. Please see www.leaseweb.com/en/legal for more information.




From: Rohit Yadav 
Sent: donderdag 4 april 2019 11:09
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org; Wei Zhou 

Subject: Re: CloudStack NoVNC solution in Leaseweb



 Hi Wei,



Great to hear from you on this. Yes, it been a long time on the previous noVNC 
integration attempt by our GSoC student. The 4.11 branch is LTS and cannot 
accept new features, please use master (4.13) for the PR you'll submit. I can 
help with reviewing and testing.



The noVNC project has moved to 1.0.0 stable 
(https://github.com/novnc/noVNC/releases/tag/v1.0.0), do you think it would be 
difficult to adapt the stable 1.0.0 version and not use the old 0.6.2 release? 
Does your implementation also support secured websocket (using a tls 
certificate)?



To keep things turn-key, does it make sense to use C-based websockify or write 
our own Java based implementation that is in-built in the console proxy agent? 
I would prefer to reuse the java agent otherwise session/IP based 
authentication without checking with cloudstack may lead to some security issue.



Licensing:

We can ask for experts on the list and on asf-legal for advice but in my 
opinion we only need to ensure that the new licenses of the packages wrt the 
feature are compatible with Apache 2.0, largely allows redistributing (via 
systemvm.iso or a via new systemvmtemplate) with modifications:



1.0.0 license:https://github.com/novnc/noVNC/blob/v1.0.0/LICENSE.txt (MPL,

BSD and MIT)

0.6.2 license: https://github.com/novnc/noVNC/blob/v0.6.2/LICENSE.txt (MPL, 
BSD, LGPL 3.0, Apache 2.0, MIT)



The main license is MPL and I think it allows for that: 
https://tldrlegal.com/license/mozilla-public-license-2.0-(mpl-2)



Other references:

https://tldrlegal.com/license/bsd-3-clause-license-(revised)
https://tldrlegal.com/license/gnu-lesser-general-public-license-v3-(lgpl-3)
https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)

https://tldrlegal.com/license/mit-license



Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com
www.shapeblue.com
@shapeblue






From: Wei ZHOU mailto:ustcweiz...@gmail.com>>
Sent: Thursday, April 4, 2019 1:34:24 PM
To: dev@cloudstack.apache.org; 
us...@cloudsta

Re: Update Cloudstack 4.12.0.0 documentation

[Gabriel Beims Bräscher]

Username: gabrielbrascher.

Thanks, Paul!

Em qui, 4 de abr de 2019 às 05:11, Paul Angus 
escreveu:

> @Gabriel Beims Bräscher
>
> Have you set up an account on readthedocs.org?  can you send me you
> username please.
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Paul Angus 
> Sent: 03 April 2019 18:54
> To: dev@cloudstack.apache.org
> Subject: RE: Update Cloudstack 4.12.0.0 documentation
>
> I can add you, but it'll be tomorrow now.  If you move the tag, for
> 4.12.0.0 it should automatically build.
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Gabriel Beims Bräscher 
> Sent: 03 April 2019 18:28
> To: dev 
> Subject: Update Cloudstack 4.12.0.0 documentation
>
> Hello folks,
>
> I have updated the documentation for 4.12.0.0 in the
> cloudstack-documentation project [1]. However, to synchronize the Apache
> CloudStack documentation [2] with [1] it is needed to run a build in
> readthedocs.org (if I am not mistaken).
>
> I don't have enough "Karma" to access readthedocs.org to run the build;
> therefore, I need some help on this one from anyone that can log in and run
> the build :)
>
> Does anyone know how such "Karma" is being provided?
>
> Please correct me if I am missing any step on this build.
> Thanks!
>
> [1] https://github.com/apache/cloudstack-documentation/tree/4.12.0.0
> [2] http://docs.cloudstack.apache.org
>

Re: Add Cloudstack 4.12.0.0 on www.apache.org/dyn/closer.lua/cloudstack/

[Gabriel Beims Bräscher]

Thanks, Rohit. I answered Paul as well on the 'Update Cloudstack 4.12.0.0
documentation' email thread.
Username: gabrielbrascher.

Cheers


Em qui, 4 de abr de 2019 às 06:29, Rohit Yadav 
escreveu:

> Gabriel,
>
>
> Yes, create an account of readthedocs.org (rtd) website and share your
> username/id with us. I'll add you to the project.
>
> With respect to making changes, this is how we generally do it:
>
>
> - Create ACS major version specific branch, such as 4.12 (forward merge
> changes to master, which would be for ACS master:4.13.0.0-SNAPSHOT)
>
> - Once you're happy with all changes, create a tag on 4.12 such as
> 4.12.0.0 and push on the github ASF repo
>
> - Once you've access on rtd project, you can go to admin and enable
> privacy (allow it) for 4.12.0.0 tag and build it. Usually RTD will build
> any tag you push.
>
> - In case you think there are further changes necessary wrt 4.12.0.0,
> you'll need to delete old tag, re-tag it on 4.12 branch and repeat the
> process.
>
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Gabriel Beims Bräscher 
> Sent: Wednesday, April 3, 2019 6:17:03 PM
> To: dev
> Subject: Re: Add Cloudstack 4.12.0.0 on
> www.apache.org/dyn/closer.lua/cloudstack/
>
> Thanks for the info Rohit! I will update the cloudstack-www 'asf-site'
> branch with the correct source code link for 4.12.0.0.
>
> Another question, regarding the documentation. How do I update the
> CloudStack documentation [1] with the content of 4.12.0.0 [2]?
> Do I need access to readthedocs.org?
>
> Thanks!
>
> [1] http://docs.cloudstack.apache.org
> [2] https://github.com/apache/cloudstack-documentation/tree/4.12.0.0
>
> Em qua, 3 de abr de 2019 às 09:28, Rohit Yadav 
> escreveu:
>
> > Gabriel,
> >
> >
> > Once you've moved the candidate artifacts to releases, ASF infra will
> > automatically mirror the release artifact except for checksum/signature
> > files.
> >
> > I see that 4.12.0.0 is already moved at the correct path:
> > https://dist.apache.org/repos/dist/release/cloudstack/releases/4.12.0.0/
> >
> >
> >
> > Regards,
> >
> > Rohit Yadav
> >
> > Software Architect, ShapeBlue
> >
> > https://www.shapeblue.com
> >
> > 
> > From: Gabriel Beims Br?scher 
> > Sent: Wednesday, April 3, 2019 5:43:33 PM
> > To: dev
> > Subject: Add Cloudstack 4.12.0.0 on
> > www.apache.org/dyn/closer.lua/cloudstack/<
> http://www.apache.org/dyn/closer.lua/cloudstack/>
> >
> > Hello folks,
> >
> > I have updated the cloudstack.apache.org; however, I pointed the source
> > link for 4.12.0.0 to [1]. Other releases (as 4.11.2.0 and CloudMonkey
> > 6.0.0) point first to [2].
> >
> > How does it work to add a release source code to
> > http://www.apache.org/dyn/closer.lua/cloudstack/releases/
> > <
> >
> http://www.apache.org/dyn/closer.lua/cloudstack/releases/cloudmonkey-6.0.0/apache-cloudstack-cloudmonkey-6.0.0-src.tar.bz2
> > >
> > ?
> >
> > Regards,
> > Gabriel.
> >
> > [1]
> >
> >
> https://dist.apache.org/repos/dist/release/cloudstack/releases/4.12.0.0/apache-cloudstack-4.12.0.0-src.tar.bz2
> > [2]
> >
> >
> http://www.apache.org/dyn/closer.lua/cloudstack/releases/cloudmonkey-6.0.0/apache-cloudstack-cloudmonkey-6.0.0-src.tar.bz2
> > [3] http://www.apache.org/dyn/closer.lua/cloudstack/releases/
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

RE: Update Cloudstack 4.12.0.0 documentation

[Paul Angus]

Youre added @Gabriel Beims Bräscher – you should 
see cloudstack-documentation under your ‘projects’

From: Gabriel Beims Bräscher 
Sent: 04 April 2019 13:02
To: Paul Angus 
Cc: dev@cloudstack.apache.org
Subject: Re: Update Cloudstack 4.12.0.0 documentation

Username: gabrielbrascher.

Thanks, Paul!

Em qui, 4 de abr de 2019 às 05:11, Paul Angus 
mailto:paul.an...@shapeblue.com>> escreveu:
@Gabriel Beims Bräscher

Have you set up an account on readthedocs.org?  can you 
send me you username please.

paul.an...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Paul Angus mailto:paul.an...@shapeblue.com>>
Sent: 03 April 2019 18:54
To: dev@cloudstack.apache.org
Subject: RE: Update Cloudstack 4.12.0.0 documentation

I can add you, but it'll be tomorrow now.  If you move the tag, for 4.12.0.0 it 
should automatically build.


paul.an...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue




-Original Message-
From: Gabriel Beims Bräscher mailto:gabrasc...@gmail.com>>
Sent: 03 April 2019 18:28
To: dev mailto:dev@cloudstack.apache.org>>
Subject: Update Cloudstack 4.12.0.0 documentation

Hello folks,

I have updated the documentation for 4.12.0.0 in the cloudstack-documentation 
project [1]. However, to synchronize the Apache CloudStack documentation [2] 
with [1] it is needed to run a build in readthedocs.org 
(if I am not mistaken).

I don't have enough "Karma" to access readthedocs.org 
to run the build; therefore, I need some help on this one from anyone that can 
log in and run the build :)

Does anyone know how such "Karma" is being provided?

Please correct me if I am missing any step on this build.
Thanks!

[1] https://github.com/apache/cloudstack-documentation/tree/4.12.0.0
[2] http://docs.cloudstack.apache.org

Re: Update Cloudstack 4.12.0.0 documentation

[Gabriel Beims Bräscher]

Thanks, @Paul Angus !

Em qui, 4 de abr de 2019 às 10:54, Paul Angus 
escreveu:

> Youre added @Gabriel Beims Bräscher  – you should
> see cloudstack-documentation under your ‘projects’
>
>
>
> *From:* Gabriel Beims Bräscher 
> *Sent:* 04 April 2019 13:02
> *To:* Paul Angus 
> *Cc:* dev@cloudstack.apache.org
> *Subject:* Re: Update Cloudstack 4.12.0.0 documentation
>
>
>
> Username: gabrielbrascher.
>
>
> Thanks, Paul!
>
>
>
> Em qui, 4 de abr de 2019 às 05:11, Paul Angus 
> escreveu:
>
> @Gabriel Beims Bräscher
>
> Have you set up an account on readthedocs.org?  can you send me you
> username please.
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
>
> -Original Message-
> From: Paul Angus 
> Sent: 03 April 2019 18:54
> To: dev@cloudstack.apache.org
> Subject: RE: Update Cloudstack 4.12.0.0 documentation
>
> I can add you, but it'll be tomorrow now.  If you move the tag, for
> 4.12.0.0 it should automatically build.
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Gabriel Beims Bräscher 
> Sent: 03 April 2019 18:28
> To: dev 
> Subject: Update Cloudstack 4.12.0.0 documentation
>
> Hello folks,
>
> I have updated the documentation for 4.12.0.0 in the
> cloudstack-documentation project [1]. However, to synchronize the Apache
> CloudStack documentation [2] with [1] it is needed to run a build in
> readthedocs.org (if I am not mistaken).
>
> I don't have enough "Karma" to access readthedocs.org to run the build;
> therefore, I need some help on this one from anyone that can log in and run
> the build :)
>
> Does anyone know how such "Karma" is being provided?
>
> Please correct me if I am missing any step on this build.
> Thanks!
>
> [1] https://github.com/apache/cloudstack-documentation/tree/4.12.0.0
> [2] http://docs.cloudstack.apache.org
>
>

[ANNOUNCEMENT] Apache CloudStack 4.12.0.0 non-LTS Release

[Gabriel Beims Bräscher]

The Apache CloudStack project is pleased to announce the release of the
CloudStack 4.12.0.0. The CloudStack version 4.12.0.0 is a 4.12 non-LTS
release, adding multiple features for those who want to access a fresh
CloudStack prior to the next LTS. The release 4.12.0.0 combines 12 months
of work and adds +200 commits, with multiple new features and fixes.

Apache CloudStack is an integrated Infrastructure-as-a-Service (IaaS)
software platform that allows users to build feature-rich public and
private cloud environments. CloudStack includes an intuitive user interface
and rich API for managing the compute, networking, software, and storage
resources. The project became an Apache top level project in March, 2013.

More information about Apache CloudStack can be found at:
http://cloudstack.apache.org/

# Documentation

What's new in CloudStack 4.12.0.0
http://docs.cloudstack.apache.org/en/4.12.0.0/releasenotes/about.html

The 4.12.0.0 release notes include a full list of corrected issues, as well
as upgrade instructions from previous versions of Apache CloudStack, and
can be found at:
http://docs.cloudstack.apache.org/en/4.12.0.0/upgrading/index.html

The official installation, administration and API documentation for each
release are available on our Documentation Page:
http://docs.cloudstack.apache.org/en/4.12.0.0/

# Downloads

The official source code for the 4.12.0.0 release can be downloaded from
our downloads page:
http://cloudstack.apache.org/downloads.html

The official source code release can be downloaded from:
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:
https://download.cloudstack.org/