You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Radhika Puthiyetath <ra...@citrix.com> on 2012/10/03 04:00:45 UTC
RE: [DOC] Documentation for CS 4.0
Hi Jamshid,
I shall submit the patch today.
Regards
-Radhika
From: jamshid69@gmail.com [mailto:jamshid69@gmail.com] On Behalf Of Jamshid Afshar
Sent: Tuesday, October 02, 2012 10:36 PM
To: Radhika Puthiyetath; Jessica Tomechak
Subject: Re: [DOC] Documentation for CS 4.0
Hi Radhika, do you mind submitting the documentation? Here is the updated format.
Thanks,
Jamshid
Using CAStor Storage Back-end with CloudStack 01-OCT-2012
===============================================================================
This document describes how to use a CAStor cluster as the back-end storage
system for a CloudStack S3 front-end. The CAStor back-end storage for
CloudStack extends the existing storage classes and allows the "storage.root"
configuration attribute to point to a CAStor cluster.
For general information about building and using CloudStack, please consult the
standard CloudStack documentation.
Configuration Steps:
-------------------
1. Install CloudStack 4.0 from source by following the instructions (deploydb,
deploy-server, and run) in the INSTALL.txt file..
Tip: You can use the S3 storage system in CloudStack without setting up and
installing the compute (virtual machine) components.
2. Set "enable.s3.api = true" in console and register a user.
https://cwiki.apache.org/CLOUDSTACK/s3-api-in-cloudstack.html
3. Edit the cloud-bridge.properties file and modify the "storage.root"
parameter.
a. Make "storage.root" begin with the key word "castor".
b. Specify a CAStor tenant domain to which content will be written. If the
domain is not specified, the CAStor default domain, specified by the
"cluster" parameter in CAStor's node.cfg file, will be used.
c. Specify a list of some node IP addresses or set "zeroconf" and the
cluster name. When using a static IP list with a large cluster, it is not
necessary to include every node -- only a few in order to initialize the
client software.
d. Optional: The last value is a port number on which to communicate with
the CAStor cluster. If not specified, the default is 80.
Examples:
# Static IP list with optional port
storage.root=castor domain=cloudstack 10.1.1.51 10.1.1.52 10.1.1.53 80
# Zeroconf locator for cluster named "castor.example.com<http://castor.example.com>"
storage.root=castor domain=cloudstack zeroconf=castor.example.com<http://castor.example.com>
4. Create the tenant domain within the CAStor storage cluster. If you omit this
step before attempting to store content, you will get HTTP 412 errors in the
awsapi.log.
Other Information:
-----------------
This code release makes use of the CloudStack server's local disk to spool
files before writing them to CAStor when handling PUT operations. Even so, a
file must be successfully written into the CAStor cluster prior to the return
of a success code to the S3 client in order to ensure correct reporting of the
transaction outcome.
While not implemented in this code release, the S3 multipart file uploads
semantics will be supported in the future. Proper error reporting is produced
if a multipart upload is attempted.
On Fri, Sep 28, 2012 at 10:03 PM, Radhika Puthiyetath <ra...@citrix.com>> wrote:
Hi Jamshid,
Excellent work.
Thank you for reaching out to us.
You can submit the documentation as a patch to the cloudstack community.
Any of us can pick the patch for review, then submit.
The complete information on how you can submit a documentation patch is given at https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+To+Work+With+CloudStack+Documentation. Hope it is helpful.
Alternatively, I can pick this piece of documentation and submit for review. Let us know how we want to go ahead with documentation submission.
-Radhika
From: jamshid69@gmail.com<ma...@gmail.com> [mailto:jamshid69@gmail.com<ma...@gmail.com>] On Behalf Of Jamshid Afshar
Sent: Friday, September 28, 2012 11:49 PM
To: Radhika Puthiyetath
Subject: Re: [DOC] Documentation for CS 4.0
Hi, Radhika. I am Jamshid, I work for Caringo and implemented the adapter which talks to Caringo instead of the file system. How should I submit the documentation? Below is what I've written up for internal use, is that the information you need? CloudStack users can get CAStor and a free license at http://www.caringo.com/company/contact.html.
Installation and configuration
To install you just install and setup CloudStack 4.0 as you normally would (CloudStack 4.0 releases in September). You only need to change storage.root configuration variable to point to CAStor and specify the domain you want streams to be written to. By default storage.root will point to a directory in your file system.
1. Install CloudStack 4.0, e.g. from source by following INSTALL.txt (deploydb, deploy-server, and run). Tip: you don't have to actually setup/install the CloudStack vm or network environment in order to use the S3 storage piece.
2. Set enable.s3.api = true in console and register a user. https://cwiki.apache.org/CLOUDSTACK/s3-api-in-cloudstack.html
3. Change storage.root in cloud-bridge.properties to begin with the word castor. You can specify the domain to which streams will be written, or if domain is not specified it will use the CAStor default domain (the cluster name is the default domain). Then either list some node ip's orzeroconf and the cluster name. The last value is optionally a port (otherwise defaults to 80).
4.
5. #storage.root=/Users/john1/S3-Mount
6. storage.root=castor domain=cloudstack 172.16.78.131 172.16.78.130 80
7. #storage.root=castor domain=cloudstack zeroconf=castor.example.com<http://castor.example.com>
* If the domain has not been created in CAStor, you will get an error 412 in the awsapi.log like this (though client appears to get a 404):
*
* 2012-08-24 16:41:48,656 ERROR [bridge.io.S3CAStorBucketAdapter] (catalina-exec-int-13:null) CAStor unable to create bucket bucket-1345844508 because domain cloudstack does not exist
* 2012-08-24 16:41:48,661 ERROR [bridge.service.S3RestServlet] (catalina-exec-int-13:null) Unexpected exception CAStor unable to create bucket bucket-1345844508: 412
* com.cloud.bridge.service.exception.OutOfStorageException: CAStor unable to create bucket bucket-1345844508: 412
* at com.cloud.bridge.io.S3CAStorBucketAdapter.createContainer(S3CAStorBucketAdapter.java:204)
* at com.cloud.bridge.service.core.s3.S3Engine.allocBucketStorageHost(S3Engine.java:1448)
* ....
* In this initial release, PUT will spool to file system before writing to CAStor.
* Multipart file uploads via the S3 api is not yet implemented.
On Fri, Sep 28, 2012 at 3:54 AM, Radhika Puthiyetath <ra...@citrix.com>> wrote:
> Hello,
>
> I am planning to take up the following feature documentation:
>
> -Niciria Integration
>
> -Caringo
>
> The contact points, please do get in touch with me at the earliest.
>
> I assume that nobody has signed up yet to work on these feature. I can take them up as a priority and complete at the earliest.
>
> Regards
> -Radhika
>
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com<ma...@citrix.com>]
> Sent: Wednesday, September 26, 2012 11:52 PM
> To: cloudstack-dev@incubator.apache.org<ma...@incubator.apache.org>
> Subject: RE: [AFSCS40] Release status for CS 4.0
>
> I took off the users mailing list.
>
> Yes. Just make sure you do it before the next release (date TBD). 4.0 will be delivered on the 4.0 branch so Edison is cherry-picking things over right now so it is okay to start your work of merging into master.
>
> --Alex
>
>> -----Original Message-----
>> From: Vijay Venkatachalam [mailto:Vijay.Venkatachalam@citrix.com<ma...@citrix.com>]
>> Sent: Wednesday, September 26, 2012 8:25 AM
>> To: cloudstack-dev@incubator.apache.org<ma...@incubator.apache.org>; cloudstack-
>> users@incubator.apache.org<ma...@incubator.apache.org>
>> Subject: RE: [AFSCS40] Release status for CS 4.0
>>
>> Hi Alex,
>>
>> All the checkins are currently going to *autoscale* branch.
>> I have to generate 4 more reviews and then it will done.
>> After that, my plan is to rebase autoscale branch against master (with
>> proper unit testing) and send a request for merge. Is this fine?
>>
>> Thanks,
>> Vijay V.
>>
>> > -----Original Message-----
>> > From: Alex Huang [mailto:Alex.Huang@citrix.com<ma...@citrix.com>]
>> > Sent: Wednesday, September 26, 2012 12:39 AM
>> > To: cloudstack-dev@incubator.apache.org<ma...@incubator.apache.org>; cloudstack-
>> > users@incubator.apache.org<ma...@incubator.apache.org>
>> > Subject: RE: [AFSCS40] Release status for CS 4.0
>> >
>> > Ram,
>> >
>> > I see a lot of recent checkins on autoscaling so if code is
>> > completely checked into master, it should go into 4.1 automatically.
>> >
>> > --Alex
>> >
>> > > -----Original Message-----
>> > > From: Ram Ganesh [mailto:Ram.Ganesh@citrix.com<ma...@citrix.com>]
>> > > Sent: Monday, September 24, 2012 10:48 PM
>> > > To: cloudstack-users@incubator.apache.org<ma...@incubator.apache.org>; cloudstack-
>> > > dev@incubator.apache.org<ma...@incubator.apache.org>
>> > > Subject: RE: [AFSCS40] Release status for CS 4.0
>> > >
>> > > Alex,
>> > >
>> > > For AutoScaling is there a process we should follow to bring the
>> > > feature into
>> > > 4.1 release apart from the usual reviews/unit-tests?
>> > >
>> > > Thanks,
>> > > Ram
>> > >
>> > >
>> > > > -----Original Message-----
>> > > > From: Alex Huang [mailto:Alex.Huang@citrix.com<ma...@citrix.com>]
>> > > > Sent: 25 September 2012 07:57
>> > > > To: cloudstack-dev@incubator.apache.org<ma...@incubator.apache.org>
>> > > > Cc: cloudstack-users@incubator.apache.org<ma...@incubator.apache.org>
>> > > > Subject: [AFSCS40] Release status for CS 4.0
>> > > >
>> > > > Hi All,
>> > > >
>> > > > I've been reminded that I've neglected to update the community
>> > > > on the current status for CloudStack 4.0. I apologize for that oversight.
>> > > > From now til the actual release, I will give a daily update on
>> > > > the status. If you feel anything is missing, please let me know
>> > > > and I'll try to include them on the next update.
>> > > >
>> > > > Summary
>> > > > As of 9/24/2012, CloudStack 4.0 release has past code freeze
>> > > > stage (over three weeks ago). A source code branch has been
>> > > > forked and is called 4.0. Nightly build is running on Jenkins on the 4.0 build.
>> > > >
>> > > > Feature List
>> > > > There are two features that missed the 4.0 release.
>> > > > Auto-Scaling and Brocade Plugin. Both are due to having
>> > > > significant code changes due past the code freeze date.
>> > > >
>> > > > Code Readiness
>> > > > - There are ~5 code related reviews on the review board
>> > > > scheduled for 4.0. Most of them are waiting for review and commit.
>> > > > - There are <10 bugs on Jira for the first cut of the release.
>> > > > - Upgrade from previous versions is currently being worked on.
>> > > > Scheduled to be done by the end of the week.
>> > > >
>> > > > License Readiness
>> > > > - Majority of the VM configuration issues have been resolved.
>> > > > There is one remaining wrt rsyslog.conf. Thanks to Chiradeep and Chip.
>> > > > - Technology export issues are still be worked on by David
>> > > > Nalley and AFS legal. This may be a blocking issue.
>> > > > - Licenses need auditing.
>> > > >
>> > > > Doc Readiness
>> > > > The current plan for docs is to write an INSTALL.TXT to give
>> > > > instructions on how to install from source. All docs will be
>> > > > generated to a living document that continues to improve past
>> > > > the release. The link to this living document is to be determined.
>> > > >
>> > > > TODO: Docs need help on the new features in the 4.0 release.
>> > > > Specifically we need help with Niciria Integration and Caringo
>> > > > documentation.
>> > > >
>> > > > QA Status
>> > > > QA is proceeding through the test cycle. It is currently at 45%
>> > > > of completion. The number of bugs generated from the tests have
>> > > > been minimum so the quality of the release currently looks pretty good.
>> > > >
>> > > > Release Plan
>> > > > - The current plan is for QA to complete its test cycle between
>> > > > 9/26- 9/28.
>> > > > - When QA decides the test cycle is read, we will cut a RC1 release.
>> > > > - We are currently pushing to clear bugs generated from the test
>> > > > cycle asap.
>> > > > - After all P1 and P2 bugs are cleared, 4.0 release will be
>> > > > submitted for approval to announce.
>> > > >
>> > > > --Alex
>