Re: [openstack-dev] Suspected SPAM - Re: [vitrage] Nominating Yujun Zhang to Vitrage core

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Congrats ☺

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
Sent: Monday, June 26, 2017 11:31 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Suspected SPAM - Re: [openstack-dev] [vitrage] Nominating Yujun Zhang 
to Vitrage core

Hi,

I added Yujun Zhang to the vitrage-core team. Yujun, Welcome ☺

Best Regards,
Ifat.

From: דני אופק <dany.of...@gmail.com<mailto:dany.of...@gmail.com>>
Date: Monday, 26 June 2017 at 11:00

+1

On Mon, Jun 26, 2017 at 7:45 AM, Weyl, Alexey (Nokia - IL/Kfar Sava) 
<alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>> wrote:
+1

> -Original Message-
> From: Afek, Ifat (Nokia - IL/Kfar Sava) 
> [mailto:ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>]
> Sent: Sunday, June 25, 2017 3:18 PM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
>
> Hi,
>
> I’d like to nominate Yujun Zhang to the Vitrage core team.
>
> In the last year Yujun has made a significant contribution in Vitrage[1], both
> by adding new features and by reviewing other people’s work. He has an
> extensive knowledge of the Vitrage architecture and code, and I believe he
> would make a great addition to our team.
>
> Best Regards,
> Ifat.
>
> [1]
> https://review.openstack.org/#/q/owner:zhang.yujunz%2540zte.com.cn+pr
> ojects:openstack/vitrage+is:merged
>

__
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

[openstack-dev] [Vitrage] New service in Vitrage

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Hi,

We have added a new service to Vitrage, called vitrage-collector.

Vitrage-collector is part of our HA (High Availability) solution.

At the moment, until we'll finish to write the history, after restarting the 
vitrage-graph you have to restart the vitrage-collector as well.

BR,
Alexey :)
__
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

Re: [openstack-dev] Suspected SPAM - [vitrage] Nominating Yujun Zhang to Vitrage core

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

+1

> -Original Message-
> From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
> Sent: Sunday, June 25, 2017 3:18 PM
> To: OpenStack Development Mailing List (not for usage questions)
> 
> Subject: Suspected SPAM - [openstack-dev] [vitrage] Nominating Yujun
> Zhang to Vitrage core
> 
> Hi,
> 
> I’d like to nominate Yujun Zhang to the Vitrage core team.
> 
> In the last year Yujun has made a significant contribution in Vitrage[1], both
> by adding new features and by reviewing other people’s work. He has an
> extensive knowledge of the Vitrage architecture and code, and I believe he
> would make a great addition to our team.
> 
> Best Regards,
> Ifat.
> 
> [1]
> https://review.openstack.org/#/q/owner:zhang.yujunz%2540zte.com.cn+pr
> ojects:openstack/vitrage+is:merged
> 
> 
> __
> 
> 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
__
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

Re: [openstack-dev] [vitrage] Gate issues

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Hi,

The gate problem was solved.

The problem wasn’t with the setuptools, but with a change that was pushed to 
the project-config (a change that was also pushed to other projects 
configurations as well).

Due to that problem the vitrage was enabled twice.

BR,
Alexey Weyl

From: Yujun Zhang (ZTE) [mailto:zhangyujun+...@gmail.com]
Sent: Thursday, June 01, 2017 6:15 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [vitrage] Gate issues

We have encountered similar issue also in OPNFV.

It seems to be a problem of setuptools 36.0.0 and it is now removed from pypi. 
Hope it resolves the vitrage gate tests as well.

See discussion in https://github.com/pypa/setuptools/issues/1042


On Thu, Jun 1, 2017 at 11:08 PM Afek, Ifat (Nokia - IL/Kfar Sava) 
> wrote:
Hi,

Note that we are currently having problems with the Vitrage gate tests, related 
to python-setuptools. Other projects experience similar problems. We hope to 
fix it by the beginning of next week.

Best Regards,
Ifat.


__
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
--
Yujun Zhang
__
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

Re: [openstack-dev] Suspected SPAM - Re: [vitrage] about "is_admin" in ctx

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Hi,

Yes the ‘is_admin_project’ represent the tenant.

I have tried to use many different users which are part of the admin, alt_demo, 
nova, vitrage, new_tenant that I have created and they all returned the 
is_admin_project=True.

At the moment as I said only the admin user will be able to see the 
all-tenants, although this is not correct, and there are other users has the 
permissions to see all-tenants as well.

We have added a new tab in horizon under the admin tab, where those who has 
permission to see that tab can see the vitrages all-tenants.

In our case only the Admin at the moment will actually see all the entities.

Alexey

From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Sent: Wednesday, May 17, 2017 12:24 PM
To: Weyl, Alexey (Nokia - IL/Kfar Sava) <alexey.w...@nokia.com>
Cc: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev]Suspected SPAM - Re: [vitrage] about  "is_admin" in 
ctx


Hi Alexey,

Currently we use 'is_admin' as 'is_admin_project'[1], right?

I think the 'is_admin_project' represent the tenant , not be related to user.

So why 'is_admin_project' alaways return 'True' with all of the user and 
tenants is the issue.

What about a user which is not ＇admin' but have the 'admin' role?

Should the user with 'admin' role see all  all-tenants?


[1] 
https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94



Ｔｈａｎｋｓ~



BR,

dwj




Original Mail
Sender:  ＜alexey.w...@nokia.com＞;
To:  ＜openstack-dev@lists.openstack.org＞;
Date: 2017/05/15 22:49
Subject: Re: [openstack-dev]Suspected SPAM - Re:  [vitrage] about  "is_admin" 
in ctx


Wenjuan,

Sorry it took me so long to answer due to the Boston Summit.

After making some more checks in order to make it sure, the results are the 
following:

1.  The context that we use has 2 properties regarding admin (is_admin, 
is_admin_project).

2.  The is_admin property regards whether the user that has done the 
inquiry is the admin or not. So the only way it is True is if the user is  
admin.

3.  The is_admin_project I thought will represent the tenant of the user, 
but from all of the user and tenants that I have used, it laways returned  me 
True.

4.  Due to that I have decided to use the is_admin property in the context 
to indicate whether the user can see all-tenants or not.

5.  This is not a perfect solution because also users such as 
nova/cinder/all project names seems to be able to see the admin tab. In our 
case  what will happen is that although in the UI we have the admin tab for 
those users, the data we will show in the vitrage tab is not of all the tenants 
but this specific tenant.

Alexey

From: Weyl, Alexey (Nokia - IL/Kfar Sava) [mailto:alexey.w...@nokia.com]
Sent: Tuesday, April 25, 2017 3:10 PM
To: OpenStack Development Mailing List (not for usage questions) 
＜openstack-dev@lists.openstack.org＞
Subject: Suspected SPAM - Re: [openstack-dev] [vitrage] about  "is_admin" in ctx

Hi Wenjuan,

This is a good question, I need to check it a bit more thoroughly.

It’s just that at the moment we are preparing for the Boston Openstack Summit 
and thus it will take me a bit more time to answer that.

Sorry for the delay.

Alexey ☺

From: dong.wenj...@zte.com.cn<mailto:dong.wenj...@zte.com.cn> 
[mailto:dong.wenj...@zte.com.cn]
Sent: Friday, April 21, 2017 11:08 AM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [vitrage] about  "is_admin" in ctx


Hi all,

I'm a little confused about the "is_amdin" in ctx.

From the 
hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73),
  "is_admin" means admin user,.

But we define the macro as "admin project"( 
https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94
  ). But in my opinion,  it should be the admin role. Correct me if i'm wrong 
:).



BR,

dwj










__
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

Re: [openstack-dev] Suspected SPAM - Re: [vitrage] about "is_admin" in ctx

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Hi Wenjuan,

Sorry it took me so long to answer due to the Boston Summit.

After making some more checks in order to make it sure, the results are the 
following:

1.   The context that we use has 2 properties regarding admin (is_admin, 
is_admin_project).

2.   The is_admin property regards whether the user that has done the 
inquiry is the admin or not. So the only way it is True is if the user is admin.

3.   The is_admin_project I thought will represent the tenant of the user, 
but from all of the user and tenants that I have used, it laways returned me 
True.

4.   Due to that I have decided to use the is_admin property in the context 
to indicate whether the user can see all-tenants or not.

5.   This is not a perfect solution because also users such as 
nova/cinder/all project names seems to be able to see the admin tab. In our 
case what will happen is that although in the UI we have the admin tab for 
those users, the data we will show in the vitrage tab is not of all the tenants 
but this specific tenant.

Alexey

From: Weyl, Alexey (Nokia - IL/Kfar Sava) [mailto:alexey.w...@nokia.com]
Sent: Tuesday, April 25, 2017 3:10 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Suspected SPAM - Re: [openstack-dev] [vitrage] about  "is_admin" in ctx

Hi Wenjuan,

This is a good question, I need to check it a bit more thoroughly.

It’s just that at the moment we are preparing for the Boston Openstack Summit 
and thus it will take me a bit more time to answer that.

Sorry for the delay.

Alexey ☺

From: dong.wenj...@zte.com.cn<mailto:dong.wenj...@zte.com.cn> 
[mailto:dong.wenj...@zte.com.cn]
Sent: Friday, April 21, 2017 11:08 AM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [vitrage] about  "is_admin" in ctx


Hi all,

I'm a little confused about the "is_amdin" in ctx.

From the 
hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73),
 "is_admin" means admin user,.

But we define the macro as "admin project"( 
https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94
 ). But in my opinion,  it should be the admin role. Correct me if i'm wrong :).



BR,

dwj






__
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

Re: [openstack-dev] [vitrage] about "is_admin" in ctx

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Hi Wenjuan,

This is a good question, I need to check it a bit more thoroughly.

It’s just that at the moment we are preparing for the Boston Openstack Summit 
and thus it will take me a bit more time to answer that.

Sorry for the delay.

Alexey ☺

From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Sent: Friday, April 21, 2017 11:08 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [vitrage] about  "is_admin" in ctx


Hi all,

I'm a little confused about the "is_amdin" in ctx.

From the 
hook(https://github.com/openstack/vitrage/blob/master/vitrage/api/hooks.py#L73),
 "is_admin" means admin user,.

But we define the macro as "admin project"( 
https://github.com/openstack/vitrage/blob/master/vitrage/api_handler/apis/base.py#L94
 ). But in my opinion,  it should be the admin role. Correct me if i'm wrong :).



BR,

dwj






__
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

Re: [openstack-dev] [ALU] Re: [vitrage] vitrage Resource API

[Weyl, Alexey (Nokia - IL/Kfar Sava)]

Hi Dong,

At the beginning that API was a mock, and then when the Vitrage started to 
work, we haven’t implemented the API and thus we can’t show an API in the 
client that doesn’t work.

In order to implement that API it also needs to support Multi tenancy.

Alexey

From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Sent: Tuesday, March 21, 2017 2:46 AM
To: trinath.soman...@nxp.com
Cc: openstack-dev@lists.openstack.org
Subject: [ALU] Re: [openstack-dev] [vitrage] vitrage Resource API


No, in the implemention of these APIs．

see 
https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/resource.py#L47






Original Mail
Sender:  ＜trinath.soman...@nxp.com＞;
To:  ＜openstack-dev@lists.openstack.org＞; ＜openstack-dev@lists.openstack.org＞;
Date: 2017/03/21 00:50
Subject: Re: [openstack-dev] [vitrage] vitrage Resource API


Outlook for iOS


From: dong.wenj...@zte.com.cn 
＜dong.wenj...@zte.com.cn＞
Sent: Monday, March 20, 2017 2:49:57 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [vitrage] vitrage Resource API


Hi All,



I noticed that the APIs of `resource list` and `resource show`  were mocked.

Is  there any backgroud for the mock or the API is not necessary?



BR,

dwj








__
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