Thanks Ivan, will check your patch soon.
2018-06-05 22:59 GMT+09:00 Akihiro Motoki :
> This is an important step to drop nose and nosehtmloutput :)
> We plan to switch the test runner and then re-enable integration tests
> (with selenium) for cross project testing.
First off, sorry for being late to response.
Looking at your comment,
your environment is Newton & AFAIK Newton is EOL, even if you will wait for
the fix, it will not be delivered to Newton.
Current my concern is that your raised issue may happen in Queens
Thank you for your contributions!
> Ivan Kolodyazhny,
> On Wed, Mar 28, 2018 at 5:18 PM, Kaz Shinohara <ksnhr.t...@gmail.com> wrote:
>> Hi Ivan & Horizon folks
>> AFAIK, Horizon team had conclusion
Keiichi Hikita / keiichi.hik...@gmail.com
Please give me a shout, if we are not on same page or any concern.
2018-03-21 22:29 GMT+09:00 Kaz Shinohara <ksnhr.t...@gmail.com>:
> Hi Ivan, Akihiro,
> Thanks for your kind arrangement.
> Looking forward to h
rizon-plugin core to xstatic-core
>> (4) Split core membership into per-repo basis (perhaps too complicated!!)
>> My current vote is (2) as xstatic-core needs to understand what is xstatic
>> and how it is maintained.
d 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 <ksnhr.t...@gmail.com>:
>> Hi Ivan, Horizon folks,
>> Now totally 8 xstatic-
e, Mar 13, 2018 at 6:41 PM, Ivan Kolodyazhny <e...@e0ne.info> wrote:
>> Hi Kaz,
>> Thanks for cleaning this up. I put +1 on both of these patches
>> Ivan Kolodyazhny,
>> On Tue, Mar 13, 201
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.
snow any more :P
2018-03-04 22:22 GMT+09:00 Thomas Goirand <z...@debian.org>:
> On 03/02/2018 07:28 PM, Kaz Shinohara wrote:
>> Hi Thomas(zigo),
>> I found an issue which is included in
>> https://review.openstack.org/#/c/548924/ (you did c
I found an issue which is included in
https://review.openstack.org/#/c/548924/ (you did cherry pick last
In short, this issue makes it impossible to install heat-dashboard..
I landed fix for this. https://review.openstack.org/#/c/549214/
Could you kindly pick up this
Hi Rico & team,
Thanks a lot for the schedule.
See you soon in Dublin :)
2018-02-24 20:53 GMT+09:00 Rico Lin :
> Dear all
> I can’t wait for see you all in Dublin.
> I put a draft version of PTG schedule in .
> We might change schedule after
> the links in a single place for readers, so you’ll want to upload to
> youtube/vimeo/etc and then send.
> Anne Bertucio
> Marketing and Certification, OpenStack Foundation
> a...@openstack.org | 206-992-7961
> On Feb 15, 2018, at 8:03
I'm wondering if I can send a demo video for heat-dashboard which is a
new feature in Queens.
Is there any format of the video ?
2018-02-16 8:09 GMT+09:00 Anne Bertucio :
> Hi all,
> We’re getting the Queens Release communications ready, and I’ve
Hope you and your family have good holidays:)
I have one thing hopefully before your off.
Looks heat-dashboard does not have stable/queens branch yet.
I got an indication about this from Horizon core and they are waiting for
that heat-dashboard will have it.
(we want to drop django <=
2017-12-06 23:30 GMT+09:00 Kaz Shinohara <ksnhr.t...@gmail.com>:
> Hi Akihiro, Horizon team,
> Thanks a lot for your help as always:)
>>> Thanks for updating the horizon patch. Is it ready to merge from the
to heat to heat-dashboard launchpad
> project last week.
> IIRC about 25 bugs were forwarded. I hope heat-dashboard team can
> investigate them.
> 2017-12-06 15:46 GMT+09:00 Akihiro Motoki <amot...@gmail.com>:
>> Hi Kaz,
2017-11-29 12:39 GMT+09:00 Kaz Shinohara <ksnhr.t...@gmail.com>:
> Hi Akihiro,
> Thanks for your quick response!
> As you requested, we will check & update your patch to slit out heat
> support from Horizon repo.
>> We are planning to land heat-dashboard in queens-2, hopefully we will
>> fix any issue until then.
>> Your cooperation will be highly appreciated.
>> Kaz Shinohara
put your comment on
this etherpad, we will respond to them.
We are planning to land heat-dashboard in queens-2, hopefully we will
fix any issue until then.
Your cooperation will be highly appreciated.
s! will pick up this later :)
2017-10-27 0:27 GMT+09:00 Akihiro Motoki <amot...@gmail.com>:
> Hi Kaz,
> Thanks for sharing the current status of heat-dashboard.
> Queens-2 sounds a reasonable milestone.
> I summarize the near-future be
them after we will safely land heat-dashboard in queens-2.
2017-10-25 11:47 GMT+09:00 Akihiro Motoki <amot...@gmail.com>:
> Hi Heat dashboard team,
> I noticed heat-dashboard repository was created.
> I have several questions from horizon side.
16, 2017 at 10:09 AM, Kaz Shinohara <ksnhr.t...@gmail.com> wrote:
>> Hi Rabi,
>> I still takes `deferred _auth_method=password` behalf of trusts because we
>> don't enable trusts in the Keystone side due to some internal reason.
>> The issues what y
o take password auth, it would
>>> be too tricky for them to introduce it, therefore I agree your 2nd option.
>>> If we will remove the `deferred_auth_method=password` from heat.conf,
>>> should we keep `deferred_auth_method` self or will replace it to a n
2017-06-16 14:11 GMT+09:00 Rabi Mishra <ramis...@redhat.com>:
> Hi All,
> As we know, 'deferred_auth_method=trusts' being the default, we use
> trust_auth_plugin whenever a resource requires deferred_auth (any resource
>(Wednesdays at 1500 UTC in #openstack-meeting-5) :)
I will join too.
2017-05-16 1:10 GMT+09:00 Steven Hardy <sha...@redhat.com>:
> On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
> > Hi Steve,
I like it too.
We should keep them updated according to the latest spec and actual use
2017-05-13 13:00 GMT+09:00 Foss Geek <thefossg...@gmail.com>:
> Hi Lance, I am also interested to assisting you on this.
Mail list logo