cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjeev N (JIRA)" <>
Subject [jira] [Reopened] (CLOUDSTACK-2695) [Object_Store_Refactor]UI: Provisioning object storage(S3 based secondary storage) can't be at zone level
Date Wed, 17 Jul 2013 13:45:08 GMT


Sanjeev N reopened CLOUDSTACK-2695:

Hi Jessica,
I agree with your previous comment , however each zone creation asks for the secondary storage
and if the user wants to use s3 again(Assuming already s3 is added ) he/she has to provide
s3 details in each zone creation wizard. Without giving s3 details in the zone, there is no
way to proceed to complete zone creation process.
So adding s3 storage should be in region wizard, and zone wizard should have NFS Cache storage
creation wizard.
> [Object_Store_Refactor]UI:  Provisioning object storage(S3 based secondary storage) can't
be at zone level
> ----------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2695
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>         Environment: Build from object_store branch
>            Reporter: Sanjeev N
>            Assignee: Jessica Wang
>            Priority: Critical
>             Fix For: 4.2.0
>         Attachments: create_S3_based_secondaryStorage_notAtZoneLevel.jpg
> Provisioning object storage can't be at zone level.
> 1.With current CS implementation , Regions is self created.
> 2.Provisioning object storage is at zone level but it should be at region level.
> 3.If the user creates multiple zones then user has to provide s3 object store details
in each zone . Since s3 is a region level storage, adding s3 should also be at region level
rather than at zone level.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message