[openstack-dev] [api] REST limitations and GraghGL inception?

[Gilles Dubreuil]

Hi,

Remember Boston's Summit presentation [1] about GraphQL [2] and how it 
addresses REST limitations.
I wonder if any project has been thinking about using GraphQL. I haven't 
find any mention or pointers about it.


GraphQL takes a complete different approach compared to REST. So we can 
finally forget about REST API Description languages 
(OpenAPI/Swagger/WSDL/WADL/JSON-API/ETC) and HATEOS (the hypermedia 
approach which doesn't describe how to use it).


So, once passed the point where 'REST vs GraphQL' is like comparing SQL 
and no-SQL DBMS and therefore have different applications, there are no 
doubt the complexity of most OpenStack projects are good candidates for 
GraphQL.


Besides topics such as efficiency, decoupling, no version management 
need there many other powerful features such as API Schema out of the 
box and better automation down that track.


It looks like the dream of a conduit between API services and consumers 
might have finally come true so we could move-on an worry about other 
things.


So has anyone already starting looking into it?

[1] 
https://www.openstack.org/videos/boston-2017/building-modern-apis-with-graphql

[2] http://graphql.org



__
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] Vitrage graph error

[MinWookKim]

Hello Ifat,

 

The problem is resolved. :)

 

Thank you.

 

Best Regards,

Minwook.

 

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] 
Sent: Sunday, April 29, 2018 3:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Vitrage] Vitrage graph error

 

Hi Minwook,

 

The following change should fix your problem:

https://review.openstack.org/#/c/564471/

 

Let me know if it helped.

 

Thanks,

Ifat

 

From: MinWookKim  >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
 >
Date: Tuesday, 24 April 2018 at 10:59
To: "'OpenStack Development Mailing List (not for usage questions)'"
 >
Subject: Re: [openstack-dev] [Vitrage] Vitrage graph error

 

Hello Ifat, 

 

I have not checked the alarm yet. (I think it does not work.)

 

However, i confirmed that the entity graph and the topology do not work.

 

Additionally, the CLI does not seem to work either.

 

I'll check it out with you. : )

 

Thank you.

 

Best Regards,

Minwook.

 

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] 
Sent: Tuesday, April 24, 2018 4:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Vitrage] Vitrage graph error

 

Hi Minwook,

 

Is the problem only in the Entity Graph? Do the Alarms view and the
Topology view work?

And what about the CLI?

 

I’ll check it and get back to you.

 

Thanks,

Ifat

 

 

From: MinWookKim  >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
 >
Date: Monday, 23 April 2018 at 16:02
To: "'OpenStack Development Mailing List (not for usage questions)'"
 >
Subject: [openstack-dev] [Vitrage] Vitrage graph error

 

Hello Vitrage team,

 

A few days ago I used Devstack to install the Openstack master version,
which included Vitrage.

 

However, I found that the Vitrage graph does not work on the
Vitrage-dashboard.

 

The state of all Vitrage components is active.

 

Could you check it once?

 

Thanks.

 

Best Regards,

 

Minwook.

<>__
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] [Openstack-operators] [nova] Default scheduler filters survey

[Ed Leafe]

On Apr 29, 2018, at 1:34 PM, Artom Lifshitz  wrote:
> 
> Based on that, we can definitely say that SameHostFilter and
> DifferentHostFilter do *not* belong in the defaults. In fact, we got
> our defaults pretty spot on, based on this admittedly very limited
> dataset. The only frequently occurring filter that's not in our
> defaults is AggregateInstanceExtraSpecsFilter.

Another data point that might be illuminating is: how many sites use a custom 
(i.e., not in-tree) filter or weigher? One of the original design tenets of the 
scheduler was that we did not want to artificially limit what people could use 
to control their deployments, but inside of Nova there is a lot of confusion as 
to whether anyone is using anything but the included filters.

So - does anyone out there rely on a filter and/or weigher that they wrote 
themselves, and maintain outside of OpenStack?

-- Ed Leafe







signature.asc
Description: Message signed with OpenPGP
__
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] [ironic] Monthly bug day?

[Michael Turek]

Awesome! If everyone doesn't mind the short notice, we'll have it again 
this Thursday @ 1:00 PM to 3:00 PM UTC.


I can provide video conferencing through hangouts here https://goo.gl/xSKBS4
Let's give that a shot this time!

We can adjust times, tooling, and regular agenda over the next couple 
meetings and see where we settle. If anyone has any questions or 
suggestions, don't hesitate to reach out to me!


Thanks,
Mike Turek 


On 4/25/18 12:11 PM, Julia Kreger wrote:

On Mon, Apr 23, 2018 at 12:04 PM, Michael Turek
 wrote:


What does everyone think about having Bug Day the first Thursday of every
month?

All for it!

__
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] [nova] Default scheduler filters survey

[Artom Lifshitz]

Thanks everyone for your input!

I wrote a small Python script [1] to present all your responses in an
understandable format. Here's the output:

Filters common to all deployments: {'ComputeFilter',
'ServerGroupAntiAffinityFilter'}

Filter counts (out of 9 deployments):
ServerGroupAntiAffinityFilter9
ComputeFilter9
AvailabilityZoneFilter   8
ServerGroupAffinityFilter8
AggregateInstanceExtraSpecsFilter8
ImagePropertiesFilter8
RetryFilter  7
ComputeCapabilitiesFilter5
AggregateCoreFilter  4
RamFilter4
PciPassthroughFilter 3
AggregateRamFilter   3
CoreFilter   2
DiskFilter   2
AggregateImagePropertiesIsolation2
SameHostFilter   2
AggregateMultiTenancyIsolation   1
NUMATopologyFilter   1
AggregateDiskFilter  1
DifferentHostFilter  1

Based on that, we can definitely say that SameHostFilter and
DifferentHostFilter do *not* belong in the defaults. In fact, we got
our defaults pretty spot on, based on this admittedly very limited
dataset. The only frequently occurring filter that's not in our
defaults is AggregateInstanceExtraSpecsFilter.

[1] https://gist.github.com/notartom/0819df7c3cb9d02315bfabe5630385c9

On Fri, Apr 27, 2018 at 8:10 PM, Lingxian Kong  wrote:
> At Catalyst Cloud:
>
> RetryFilter
> AvailabilityZoneFilter
> RamFilter
> ComputeFilter
> AggregateCoreFilter
> DiskFilter
> AggregateInstanceExtraSpecsFilter
> ImagePropertiesFilter
> ServerGroupAntiAffinityFilter
> SameHostFilter
>
> Cheers,
> Lingxian Kong
>
>
> On Sat, Apr 28, 2018 at 3:04 AM Jim Rollenhagen 
> wrote:
>>
>> On Wed, Apr 18, 2018 at 11:17 AM, Artom Lifshitz 
>> wrote:
>>>
>>> Hi all,
>>>
>>> A CI issue [1] caused by tempest thinking some filters are enabled
>>> when they're really not, and a proposed patch [2] to add
>>> (Same|Different)HostFilter to the default filters as a workaround, has
>>> led to a discussion about what filters should be enabled by default in
>>> nova.
>>>
>>> The default filters should make sense for a majority of real world
>>> deployments. Adding some filters to the defaults because CI needs them
>>> is faulty logic, because the needs of CI are different to the needs of
>>> operators/users, and the latter takes priority (though it's my
>>> understanding that a good chunk of operators run tempest on their
>>> clouds post-deployment as a way to validate that the cloud is working
>>> properly, so maybe CI's and users' needs aren't that different after
>>> all).
>>>
>>> To that end, we'd like to know what filters operators are enabling in
>>> their deployment. If you can, please reply to this email with your
>>> [filter_scheduler]/enabled_filters (or
>>> [DEFAULT]/scheduler_default_filters if you're using an older version)
>>> option from nova.conf. Any other comments are welcome as well :)
>>
>>
>> At Oath:
>>
>> AggregateImagePropertiesIsolation
>> ComputeFilter
>> CoreFilter
>> DifferentHostFilter
>> SameHostFilter
>> ServerGroupAntiAffinityFilter
>> ServerGroupAffinityFilter
>> AvailabilityZoneFilter
>> AggregateInstanceExtraSpecsFilter
>>
>> // jim
>>
>> __
>> 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
>



-- 
--
Artom Lifshitz
Software Engineer, OpenStack Compute DFG

__
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] [All][Election] Last days for Rocky TC Election Voting!

[Jeremy Stanley]

We are coming down to the last hours for voting in the TC
election. Voting ends 2018-04-30 (Monday) at 23:45 UTC.

Search your gerrit preferred email address[0] for the following subject:
 Poll: Rocky TC Election

That is your ballot and links you to the voting application. Please
vote. If you have voted, please encourage your colleagues to vote.

Candidate statements are linked to the names of all confirmed
candidates:
http://governance.openstack.org/election/#rocky-tc-candidates

What to do if you don't see the email and have a commit in at least
one of the official programs projects[1]:
  * check the trash of your gerrit Preferred Email address[0], in
case it went into trash or spam
  * wait a bit and check again, in case your email server is a bit slow
  * find the sha of at least one commit from the program project
repos[1] and email the election officials[2].

If we can confirm that you are entitled to vote, we will add you
to the voters list and you will be emailed a ballot.

Please vote!

Thank you,

[0] Sign into review.openstack.org: Go to Settings > Contact
Information. Look at the email listed as your Preferred Email.
That is where the ballot has been sent.
[1] 
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml?id=apr-2018-elections
[2] http://governance.openstack.org/election/#election-officials

-- 
Jeremy Stanley, Election Official


signature.asc
Description: PGP signature
__
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] [OpenStackAnsible] Tag repos as newton-eol

[Jean-Philippe Evrard]

Hello,

> I'd like to phase out openstack/openstack-ansible-tests and
> openstack/openstack-ansible later.

Now that we had the time to bump the roles in openstack-ansible, and
adapt the tests, we can now EOL the rest of newton, i.e.:
openstack/openstack-ansible and openstack/openstack-ansible-tests.

Thanks for the help again Tony!
JP

__
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] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

[Michał Jastrzębski]

strong +1 from me! Great work Mark!

On 29 April 2018 at 03:16, Steven Dake (stdake)  wrote:
> +1
>
>
>
>
>
>
>
> From: Jeffrey Zhang 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> 
> Date: Thursday, April 26, 2018 at 5:32 PM
> To: OpenStack Development Mailing List 
> Subject: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard
> (mgoddard) as kolla core member
>
>
>
> Kolla core reviewer team,
>
> It is my pleasure to nominate
>
> mgoddard for kolla core team.
>
> Mark has been working both upstream and downstream with kolla and
> kolla-ansible for over two years, building bare metal compute clouds with
> ironic for HPC. He's been involved with OpenStack since 2014. He started
> the kayobe deployment project which complements kolla-ansible. He is
> also the most active non-core contributor for last 90 days[1]
>
> Consider this nomination a +1 vote from me
>
> A +1 vote indicates you are in favor of
>
> mgoddard as a candidate, a -1
> is a
>
> veto. Voting is open for 7 days until
>
> May
>
>
>
> 4
>
> th, or a unanimous
> response is reached or a veto vote occurs.
>
> [1] http://stackalytics.com/report/contribution/kolla-group/90
>
>
>
> --
>
> Regards,
>
> Jeffrey Zhang
>
> Blog: http://xcodest.me
>
>
> __
> 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] Vitrage graph error

[Afek, Ifat (Nokia - IL/Kfar Sava)]

Hi Minwook,

The following change should fix your problem:
https://review.openstack.org/#/c/564471/

Let me know if it helped.

Thanks,
Ifat

From: MinWookKim 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Tuesday, 24 April 2018 at 10:59
To: "'OpenStack Development Mailing List (not for usage questions)'" 

Subject: Re: [openstack-dev] [Vitrage] Vitrage graph error

Hello Ifat,

I have not checked the alarm yet. (I think it does not work.)

However, i confirmed that the entity graph and the topology do not work.

Additionally, the CLI does not seem to work either.

I'll check it out with you. : )

Thank you.

Best Regards,
Minwook.

From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com]
Sent: Tuesday, April 24, 2018 4:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Vitrage] Vitrage graph error

Hi Minwook,

Is the problem only in the Entity Graph? Do the Alarms view and the Topology 
view work?
And what about the CLI?

I’ll check it and get back to you.

Thanks,
Ifat


From: MinWookKim >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, 23 April 2018 at 16:02
To: "'OpenStack Development Mailing List (not for usage questions)'" 
>
Subject: [openstack-dev] [Vitrage] Vitrage graph error

Hello Vitrage team,

A few days ago I used Devstack to install the Openstack master version, which 
included Vitrage.

However, I found that the Vitrage graph does not work on the Vitrage-dashboard.

The state of all Vitrage components is active.

Could you check it once?

Thanks.

Best Regards,

Minwook.
__
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