date:20180319

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

2018-03-19 Thread Akihiro Motoki

Hi Kaz,

These repositories are under horizon project. It looks better to keep the
current core team.
It potentially brings some confusion if we treat some horizon plugin team
specially.
Reviewing xstatic repos would be a small burden, wo I think it would work
without problem even if only horizon-core can approve xstatic reviews.


2018-03-20 10:02 GMT+09:00 Kaz Shinohara :

> Hi Ivan, Horizon folks,
>
>
> Now totally 8 xstatic-** repos for heat-dashboard have been landed.
>
> In project-config for them, I've set same acl-config as the existing
> xstatic repos.
> It means only "xstatic-core" can manage the newly created repos on gerrit.
> Could you kindly add "heat-dashboard-core" into "xstatic-core" like as
> what horizon-core is doing ?
>
> xstatic-core
> https://review.openstack.org/#/admin/groups/385,members
>
> heat-dashboard-core
> https://review.openstack.org/#/admin/groups/1844,members
>
> Of course, we will surely touch only what we made, just would like to
> manage them smoothly by ourselves.
> In case we need to touch the other ones, will ask Horizon team for help.
>
> Thanks in advance.
>
> Regards,
> Kaz
>
>
> 2018-03-14 15:12 GMT+09:00 Xinni Ge :
> > Hi Horizon Team,
> >
> > I reported a bug about lack of ``ADD_XSTATIC_MODULES`` plugin option,
> >  and submitted a patch for it.
> > Could you please help to review the patch.
> >
> > https://bugs.launchpad.net/horizon/+bug/1755339
> > https://review.openstack.org/#/c/552259/
> >
> > Thank you very much.
> >
> > Best Regards,
> > Xinni
> >
> > On Tue, Mar 13, 2018 at 6:41 PM, Ivan Kolodyazhny 
> wrote:
> >>
> >> Hi Kaz,
> >>
> >> Thanks for cleaning this up. I put +1 on both of these patches
> >>
> >> Regards,
> >> Ivan Kolodyazhny,
> >> http://blog.e0ne.info/
> >>
> >> On Tue, Mar 13, 2018 at 4:48 AM, Kaz Shinohara 
> >> wrote:
> >>>
> >>> Hi Ivan & Horizon folks,
> >>>
> >>>
> >>> Now we are submitting a couple of patches to have the new xstatic
> >>> modules.
> >>> Let me request you to have review the following patches.
> >>> We need Horizon PTL's +1 to move these forward.
> >>>
> >>> project-config
> >>> https://review.openstack.org/#/c/551978/
> >>>
> >>> governance
> >>> https://review.openstack.org/#/c/551980/
> >>>
> >>> Thanks in advance:)
> >>>
> >>> Regards,
> >>> Kaz
> >>>
> >>>
> >>> 2018-03-12 20:00 GMT+09:00 Radomir Dopieralski  >:
> >>> > Yes, please do that. We can then discuss in the review about
> technical
> >>> > details.
> >>> >
> >>> > On Mon, Mar 12, 2018 at 2:54 AM, Xinni Ge 
> >>> > wrote:
> >>> >>
> >>> >> Hi, Akihiro
> >>> >>
> >>> >> Thanks for the quick reply.
> >>> >>
> >>> >> I agree with your opinion that BASE_XSTATIC_MODULES should not be
> >>> >> modified.
> >>> >> It is much better to enhance horizon plugin settings,
> >>> >>  and I think maybe there could be one option like
> ADD_XSTATIC_MODULES.
> >>> >> This option adds the plugin's xstatic files in STATICFILES_DIRS.
> >>> >> I am considering to add a bug report to describe it at first, and
> give
> >>> >> a
> >>> >> patch later maybe.
> >>> >> Is that ok with the Horizon team?
> >>> >>
> >>> >> Best Regards.
> >>> >> Xinni
> >>> >>
> >>> >> On Fri, Mar 9, 2018 at 11:47 PM, Akihiro Motoki 
> >>> >> wrote:
> >>> >>>
> >>> >>> Hi Xinni,
> >>> >>>
> >>> >>> 2018-03-09 12:05 GMT+09:00 Xinni Ge :
> >>> >>> > Hello Horizon Team,
> >>> >>> >
> >>> >>> > I would like to hear about your opinions about how to add new
> >>> >>> > xstatic
> >>> >>> > modules to horizon settings.
> >>> >>> >
> >>> >>> > As for Heat-dashboard project embedded 3rd-party files issue,
> >>> >>> > thanks
> >>> >>> > for
> >>> >>> > your advices in Dublin PTG, we are now removing them and
> >>> >>> > referencing as
> >>> >>> > new
> >>> >>> > xstatic-* libs.
> >>> >>>
> >>> >>> Thanks for moving this forward.
> >>> >>>
> >>> >>> > So we installed the new xstatic files (not uploaded as openstack
> >>> >>> > official
> >>> >>> > repos yet) in our development environment now, but hesitate to
> >>> >>> > decide
> >>> >>> > how to
> >>> >>> > add the new installed xstatic lib path to STATICFILES_DIRS in
> >>> >>> > openstack_dashboard.settings so that the static files could be
> >>> >>> > automatically
> >>> >>> > collected by *collectstatic* process.
> >>> >>> >
> >>> >>> > Currently Horizon defines BASE_XSTATIC_MODULES in
> >>> >>> > openstack_dashboard/utils/settings.py and the relevant static
> fils
> >>> >>> > are
> >>> >>> > added
> >>> >>> > to STATICFILES_DIRS before it updates any Horizon plugin
> dashboard.
> >>> >>> > We may want new plugin setting keywords ( something similar to
> >>> >>> > ADD_JS_FILES)
> >>> >>> > to update horizon XSTATIC_MODULES (or directly update
> >>> >>> > STATICFILES_DIRS).
> >>> >>>
> >>> >>> IMHO it is better to allow horizon plugins to add xstatic modules
> >>> >>> through horizon

[openstack-dev] [cinder] Support share backup to different projects?

2018-03-19 Thread TommyLike Hu

Now Cinder can transfer volume (with or without snapshots) to different
projects, and this make it possbile to transfer data across tenant via
volume or image. Recently we had a conversation with our customer from
Germany, they mentioned they are more pleased if we can support transfer
data accross tenant via backup not image or volume, and these below are
some of their concerns:

1. There is a use case that they would like to deploy their
develop/test/product systems in the same region but within different
tenants, so they have the requirment to share/transfer data across tenants.

2. Users are more willing to use backups to secure/store their volume data
since backup feature is more advanced in product openstack version
(incremental backups/periodic backups/etc.).

3. Volume transfer is not a valid option as it's in AZ and it's a
complicated process if we would like to share the data to multiple projects
(keep copy in all the tenants).

4. Most of the users would like to use image for bootable volume only and
share volume data via image means the users have to maintain lots of image
copies when volume backup changed as well as the whole system needs to
differentiate bootable images and none bootable images, most important, we
can not restore volume data via image now.

5. The easiest way for this seems to support sharing backup to different
projects, the owner project have the full authority while shared projects
only can view/read the backups.

6. AWS has the similar concept, share snapshot. We can share it by modify
the snapshot's create volume permissions [1].

Looking forward to any like or dislike or suggestion on this idea accroding
to my feature proposal experience:)

Thanks
TommyLike

[1]:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-modifying-snapshot-permissions.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

47 matches

Mail list logo