Hi all,
Due to the low activity on our weekly meeting, I would like to raise this
question again.
Do we want a new meeting day and/or time? I'm available any day except
Tuesday and Wednesday. I'm going to get some feedback before I create a
new poll.
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.i
Akihiro Motoki writes:
> Hi,
>
> Horizon logging depends on Django configuration which supports full python
> logging [1].
> [1] does not provide enough examples.
> Perhaps [2] will help you (though I haven't tested it).
Based on https://docs.djangoproject.com/en/2.1/topics/logging/ it looks
lik
Hi,
Horizon logging depends on Django configuration which supports full python
logging [1].
[1] does not provide enough examples.
Perhaps [2] will help you (though I haven't tested it).
[1] https://docs.djangoproject.com/en/2.0/topics/logging/
[2]
https://www.simonkrueger.com/2015/05/27/logging-d
Hi!
For most openstack parts (e.g. Aodh, Cinder, Glance, Heat, Ironic, Keystone,
Neutron, Nova) it was easy to get logs to syslog.
For example for Heat something similar to this (into file
templates/heat.conf.j2):
# Syslog usage
{% if heat_syslog_enabled %}
use_syslog = True
syslog_log_facilit
Hi team,
Let's skip the meeting tomorrow due to the OpenStack Summit.
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.
Greetings, Horizon team!
As you may be aware, I've been working with other folks in the community
on documenting a vision for OpenStack clouds (formerly known as the
'Technical Vision') - essentially to interpret the mission statement in
long-form, in a way that we can use to actually help guid
Hi Tony,
I like the idea to get functional tests instead of tempest. We can extend
our functional tests to plugins.
Personally, I don't have a strong opinion on what way we should go forward.
I'll support any community decision which helps us to get cross projects CI
up and running.
Regards,
Iva
Hi,
The python3-xstatic-bootstrap-datepicker Debian package runtime depends
on libjs-twitter-bootstrap-datepicker which itself depends on
libjs-twitter-bootstrap, which is produced by the twitter-bootstrap
source package. The twitter-bootstrap will go away from Debian Buster,
as per https://bugs.d
On Wed, Oct 17, 2018 at 04:18:26PM +0300, Ivan Kolodyazhny wrote:
> Hi all,
>
> We discussed this topic at PTG both with Horizon and other teams. Sounds
> like everybody is interested to have some cross-project CI jobs to verify
> that plugins are not broken with the latest Horizon changes.
>
> T
Hi Ivan,
As Octavia PTL I have no issue with adding a tempest-plugin repository
for the octavia-dashboard. I think we have had examples with the main
tempest tests and plugins where trying to do a suite of tests in one
repository becomes messy.
We may also want to consider doing a horizon-tempest
On 10/17/2018 9:24 AM, Ivan Kolodyazhny wrote:
As you may know, unfortunately, Horizon doesn't support all features
provided by APIs. That's why we created feature gaps list [1].
I'd got a lot of great conversations with projects teams during the PTG
and we tried to figure out what should be
Hi teams,
As you may know, unfortunately, Horizon doesn't support all features
provided by APIs. That's why we created feature gaps list [1].
I'd got a lot of great conversations with projects teams during the PTG and
we tried to figure out what should be done prioritize these tasks. It's
really
Hi all,
We discussed this topic at PTG both with Horizon and other teams. Sounds
like everybody is interested to have some cross-project CI jobs to verify
that plugins are not broken with the latest Horizon changes.
The initial idea was to use tempest plugins for this effort like we do for
Horizo
Hi Jea-Min,
I filed a bug [1] and proposed a fix for it [2]
[1] https://bugs.launchpad.net/horizon/+bug/1796312
[2] https://review.openstack.org/608274
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Tue, Oct 2, 2018 at 6:55 AM Jea-Min Lim wrote:
> Thanks for the reply.
>
> If you need
Thanks for working on it, Shu.
Let's unblock gates and find a better long-term solution
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Mon, Oct 1, 2018 at 7:55 PM Duc Truong wrote:
> Hi Shu,
>
> Thanks for proposing your fix. It looks good to me. I have submitted
> a similar patch for
Thanks for the reply.
If you need any detailed information, let me know.
Regards,
2018년 10월 1일 (월) 오후 6:53, Ivan Kolodyazhny 님이 작성:
> Hi Jea-Min,
>
> Thank you for your report. I'll check the manual and fix it asap.
>
>
> Regards,
> Ivan Kolodyazhny,
> http://blog.e0ne.info/
>
>
> On Mon, Oct
Hi Shu,
Thanks for proposing your fix. It looks good to me. I have submitted
a similar patch for senlin-dashboard to unblock the broken gate test [1].
[1] https://review.openstack.org/#/c/607003/
Regards,
Duc (dtruong)
On Fri, Sep 28, 2018 at 2:24 AM Shu M. wrote:
>
> Hi Ivan,
>
> Thank you
Hi Jea-Min,
Thank you for your report. I'll check the manual and fix it asap.
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Mon, Oct 1, 2018 at 9:38 AM Jea-Min Lim wrote:
> Hello everyone,
>
> I`m following a tutorial of Building a Dashboard using Horizon.
> (link:
> https://docs.ope
Hello everyone,
I`m following a tutorial of Building a Dashboard using Horizon.
(link:
https://docs.openstack.org/horizon/latest/contributor/tutorials/dashboard.html#tutorials-dashboard
)
However, provided custom management command doesn't create boilerplate
code.
I typed tox -e manage -- startd
Hi Ivan,
Thank you for your help to our plugins and sorry for bothering you.
I found problem on installing horizon in "post-install", e.g. we should
install horizon with upper-constraints.txt in "post-install".
I proposed patch[1] in zun-ui, please check it. If we can merge this, I
will expand it
Hi,
Unfortunately, this issue affects some of the plugins too :(. At least
gates for the magnum-ui, senlin-dashboard, zaqar-ui and zun-ui are broken
now. I'm working both with project teams to fix it asap. Let's wait if [5]
helps for senlin-dashboard and fix all the rest of plugins.
[5] https://
Hi all,
Patch [1] is merged and our gates are un-blocked now. I went throw review
list and post 'recheck' where it was needed.
We need to cherry-pick this fix to stable releases too. I'll do it asap
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Mon, Sep 24, 2018 at 11:18 AM Ivan Kolody
Hi team,
Unfortunately, horizon gates are broken now. We can't merge any patch due
to the -1 from CI.
I don't want to disable tests now, that's why I proposed a fix [1].
We'd got released some of XStatic-* packages last week. At least new
XStatic-jQuery [2] breaks horizon [3]. I'm working on a ne
Hi team,
Some time ago we've found an issue that there is no simple way to test
Horizon plugin locally with the current version of Horizon [1], [2].
It leads to the situation when plugins developers use the latest released
Horizon version instead of the latest master during new features
developme
Hi team,
A lot of us will attend PTG in Denver next week so we skip the meeting on
9/12.
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
Hi team,
Since we're at the beginning of Stein release cycle, I think it's a good
time to do some cleanup in our core teams.
First of all, I would like to say a big Thank you to everybody who
contributed as Core Reviewer to Horizon.
Unfortunately, some people became inactive as reviewers during
Hello everyone,
A new release candidate for horizon for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/horizon/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formall
Hello everyone,
A new release candidate for horizon for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/horizon/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formall
Hi team,
I'll be on PTO next week. Are we OK to cancel the next meeting?
I remember that next week is a deadline for RC1, so I'm going to propose a
patch to release it
a bit later next week: Tuesday or Wednesday.
In an emergency case, please, reach me via e-mail because I'll have a
limited inter
Hi team,
I've created an etherpad [1] to gather topics for PTG discussions in
Denver.
Please, do not hesitate to add any topic you think is valuable even you
won't
attend PTG.
I hope to see all of you in September!
[1] https://etherpad.openstack.org/p/horizon-ptg-planning-denver-2018
Regards
Hi Doug,
We discussed this option a bit too. Maybe we need to think about this again.
>From my point of view, it would be better to keep current release model for
now,
because we've got a very small amount of active horizon contributors, so
current release
model helps us deliver the project in ti
Fixed horizon tag in the subject :(
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Mon, Jun 18, 2018 at 4:11 PM, Ivan Kolodyazhny wrote:
> Hi team,
>
> As you may know, Horizon uses both Python and JavaScript dependencies as
> well. All of our JS dependencies are packed into the xstatic-*
Excerpts from Ivan Kolodyazhny's message of 2018-06-13 18:01:26 +0300:
> Hi team,
>
> Last week on the Horizon meeting we discussed [1] possible options for
> Horizon release model to address current issues for plugins maintainers.
> Some background could be found here [2].
>
> The main issue is
Hi team,
Last week on the Horizon meeting we discussed [1] possible options for
Horizon release model to address current issues for plugins maintainers.
Some background could be found here [2].
The main issue is that we should have some stable API for plugins and be
able to release it as needed.
Some of our xstatic packages require an elaborate build process, as they
use various javascript-based tools to do the build. In this case, it's more
than just minification — it's macros and includes, basically a
pre-processor, and it would be very hard to re-create that in Python. Thus,
we did some
2018年6月6日(水) 11:54 Xinni Ge :
> Hi, akihiro and other guys,
>
> I understand why minified is considered to be non-free, but I was confused
> about the statement
> "At the very least, a non-minified version should be present next to the
> minified version" [1]
> in the documentation.
>
> Actually i
Hi, akihiro and other guys,
I understand why minified is considered to be non-free, but I was confused
about the statement
"At the very least, a non-minified version should be present next to the
minified version" [1]
in the documentation.
Actually in existing xstatic repo, I observed several min
Thanks Ivan, will check your patch soon.
Regards,
Kaz(Heat)
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.
>
> In add
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.
In addition, we horizon team are trying to minimize gate breakage in
horizon plugins for recent changes (this and django 2.
Excerpts from Ivan Kolodyazhny's message of 2018-06-05 16:32:22 +0300:
> Hi team,
>
> In Horizon, we're going to get rid of unsupported Nose and use Django Test
> Runner instead of it [1]. Nose has some issues and limitations which blocks
> us in our testing improvement efforts.
>
> Nose has diff
Hi team,
In Horizon, we're going to get rid of unsupported Nose and use Django Test
Runner instead of it [1]. Nose has some issues and limitations which blocks
us in our testing improvement efforts.
Nose has different test discovery mechanism than Django does. So, there was
a chance to break some
Hi,
Sorry for re-using the ancient ML thread.
Looking at recent xstatic-* repo reviews, I am a bit afraid that
xstatic-cores do not have a common understanding on the principle of
xstatic packages.
I hope all xstatic-cores re-read "Packing Software" in the horizon
contributor docs [1], especially
2018年6月3日(日) 10:56 Chuck Short :
> Hi
>
> On Sat, Jun 2, 2018 at 9:50 PM, Akihiro Motoki wrote:
>
>> Updates on Django 2.0 support.
>>
>> * 18 of 29 affected repositories now support Django 2.0
>> * 4 repositories have pending patches.
>> * 3 repositories below need help from individual project t
Hi
On Sat, Jun 2, 2018 at 9:50 PM, Akihiro Motoki wrote:
> Updates on Django 2.0 support.
>
> * 18 of 29 affected repositories now support Django 2.0
> * 4 repositories have pending patches.
> * 3 repositories below need help from individual project teams as I don't
> have actual running environ
Updates on Django 2.0 support.
* 18 of 29 affected repositories now support Django 2.0
* 4 repositories have pending patches.
* 3 repositories below need help from individual project teams as I don't
have actual running environments of them.
* heat-dashboard https://review.openstack.org/#/c/567
On 05/30/2018 04:13 PM, Ivan Kolodyazhny wrote:
> Hi Thomas,
>
>
> As my python3-xstatic-font-awesome removes the embedded fonts
>
>
> It sounds like you broke xstatic-* packages for Debian and use something
> we don't test with Horizon at all.
>
> Speaking about Rocky/master version, our
Hi Thomas,
> As my python3-xstatic-font-awesome removes the embedded fonts
It sounds like you broke xstatic-* packages for Debian and use something we
don't test with Horizon at all.
Speaking about Rocky/master version, our upper-constraint
XStatic-Font-Awesome===4.7.0.0 [1]. We don't test hor
Hi Radomir,
I'm adding the debian bug as Cc.
On 05/28/2018 08:35 AM, Radomir Dopieralski wrote:
> I did a quick search for all the glyphs we are using:
>
> ~/dev/horizon(master)> ag 'fa-' | egrep -o 'fa-[a-z-]*' | sort | uniq
> fa-
> fa-angle-left
> [...]
Thanks for your investigation.
I did a
I did a quick search for all the glyphs we are using:
~/dev/horizon(master)> ag 'fa-' | egrep -o 'fa-[a-z-]*' | sort | uniq
fa-
fa-angle-left
fa-angle-right
fa-arrow-down
fa-arrow-up
fa-asterisk
fa-b
fa-bars
fa-bolt
fa-bug
fa-calculator
fa-calendar
fa-caret-down
fa-caret-up
fa-check
fa-chevron-dow
Hi Horizon team!
I'm not sure if you're aware of that, but the upstream authors of
fontawesome decided it was a good idea to break everyone. See this
Debian bug entry:
https://bugs.debian.org/899124
So, what happened is that fontawesome-webfont has been split into 3 sets
of fonts: solid, regular
Hi all,
Some of the team will be attending the OpenStack summit in Vancouver,
so I am canceling the weekly IRC meeting for the 23rd.
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
__
OpenStack Development Mailing List (no
On 05/14/2018 03:30 PM, Akihiro Motoki wrote:
> Is Python 3 ever used for mod_wsgi? Does the WSGI setup code honor
> the variable that tells devstack to use Python 3?
>
>
> Ubuntu 16.04 provides py2 and py3 versions of mod_wsgi (libapache2-mod-wsgi
> and libapache2-mod-wsgi-py3) and as a
Excerpts from Ivan Kolodyazhny's message of 2018-05-14 22:20:42 +0300:
> Hi all,
>
> From the Horizon's perspective, it would be good to support Django 1.11 as
> long as we can since it's an LTS release [2].
> Django 2.0 support is also extremely important because of it's the first
> step in a pyt
Hi all,
>From the Horizon's perspective, it would be good to support Django 1.11 as
long as we can since it's an LTS release [2].
Django 2.0 support is also extremely important because of it's the first
step in a python3-only environment and step forward on supporting
next Django 2.2 LTS release w
2018年5月14日(月) 21:42 Doug Hellmann :
> Excerpts from Akihiro Motoki's message of 2018-05-14 18:52:55 +0900:
> > 2018年5月12日(土) 3:04 Doug Hellmann :
> >
> > > Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> > > > Hi zigo and horizon plugin maintainers,
> > > >
> > > > Horizon i
Excerpts from Akihiro Motoki's message of 2018-05-14 18:52:55 +0900:
> 2018年5月12日(土) 3:04 Doug Hellmann :
>
> > Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> > > Hi zigo and horizon plugin maintainers,
> > >
> > > Horizon itself already supports Django 2.0 and horizon unit
2018年5月12日(土) 3:04 Doug Hellmann :
> Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> > Hi zigo and horizon plugin maintainers,
> >
> > Horizon itself already supports Django 2.0 and horizon unit test covers
> > Django 2.0 with Python 3.5.
> >
> > A question to all is whether
On 05/11/2018 05:14 PM, Akihiro Motoki wrote:
> Hi zigo and horizon plugin maintainers,
>
> Horizon itself already supports Django 2.0 and horizon unit test covers
> Django 2.0 with Python 3.5.
>
> A question to all is whether we change the upper bound of Django from
> <2.0 to <2.1.
> My proposal
Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> Hi zigo and horizon plugin maintainers,
>
> Horizon itself already supports Django 2.0 and horizon unit test covers
> Django 2.0 with Python 3.5.
>
> A question to all is whether we change the upper bound of Django from <2.0
>
Hi zigo and horizon plugin maintainers,
Horizon itself already supports Django 2.0 and horizon unit test covers
Django 2.0 with Python 3.5.
A question to all is whether we change the upper bound of Django from <2.0
to <2.1.
My proposal is to bump the upper bound of Django to <2.1 in Rocky-2.
(Not
Hi,
It has been decided that, in Debian, we'll switch to Django 2.0 after
Buster will be released. Buster is to be frozen next February. This
means that we have roughly one more year before Django 1.x goes away.
Hopefully, Horizon will be ready for it, right?
Hoping this helps,
Cheers,
Thomas G
Hi team,
Due to the Victory Day, I won't be able to chair the meeting this week.
After a short conversation in the IRC, we decided to skip this meeting.
Feel free to add your topic to
https://wiki.openstack.org/wiki/Meetings/Horizon and see you next week!
Regards,
Ivan Kolodyazhny,
http://blog.e0
Matt, thank you for all your efforts!
I'm going to work on Horizon blueprint soon to get it implemented in Rocky
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Wed, Apr 25, 2018 at 4:57 PM, Matt Riedemann wrote:
> I wanted to advertise the need for some help in adding multiattach volume
I wanted to advertise the need for some help in adding multiattach
volume support to Horizon. There is a blueprint tracking the changes
[1]. I started the ball rolling with [2] but there is more work to do,
listed in the work items section of the blueprint.
[2] was I think my first real code c
On 2018-04-23 21:45, Sean McGinnis wrote:
> See below for logs from a failed xstatic release job. It appears something is
> not set up right with this job.
>
> "can't open file 'xstatic_check_version.py': [Errno 2] No such file or
> directory"
>
> I missed it initially, but this release did not a
See below for logs from a failed xstatic release job. It appears something is
not set up right with this job.
"can't open file 'xstatic_check_version.py': [Errno 2] No such file or
directory"
I missed it initially, but this release did not actually contain any functional
change, so I think it is
Hi horizon plugin developers,
As I announced in the quoted mail, Rocky-1 was released and mox is NOT
prepared in the horizon test helpers by default now [1].
If your horizon plugin still depends on mox, please ensure to set use_mox =
True in your test classes.
> 2) After Rocky-1, use_mox of opens
Hi,
It's just a reminder that we've got our meeting today at 15.00UTC at
openstack-meeting-alt channel.
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Mon, Apr 16, 2018 at 12:01 PM, Ivan Kolodyazhny wrote:
> Hi team,
>
> Please be informed that Horizon meeting time has been changed [1].
Hi team,
Please be informed that Horizon meeting time has been changed [1]. We'll
have our weekly meetings at 15.00 UTC starting this week at
'openstack-meeting-alt' channel. We had to change meeting channel too due
to the conflict with others.
[1] https://review.openstack.org/#/c/560979/
Regar
Hi all,
Let me introduce my proposal about Horizon testing improvements[1]. We
started this discussion at the last PTG [2] and had a good conversation at
the previous meeting [3].
The idea is simple: to have CI that verifies Horizon changes across
supported plugins. As a side-effect of this activ
Hi Radomir, Ivan,
Thanks a lot for your advice.
I will update the xstatic files just as the upstream.
As for the customized lines, I will try to find a better way to solve it,
maybe override the original functions inside the project.
Best regards,
Xinni
On Tue, Apr 10, 2018 at 4:58 AM, Ivan Kolo
Hi, Xinni,
I absolutely agree with Radomir. We should keep xstatic files without
modifications. We don't know if they are used outside of OpenStack or not,
so they should be the same as NPM packages
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Mon, Apr 9, 2018 at 12:32 PM, Radomir Dopie
The whole idea about xstatic files is that they are generic, not specific
to Horizon or OpenStack, usable by other projects that need those static
files. In fact, at the time we started using xstatic, it was being used by
the MoinMoin wiki project (which is now dead, sadly). The modifications you
m
Hello, team.
Sorry for talking about xstatic repo for so many times.
I didn't realize xstatic repositories should be provided with exactly the
same file as upstream, and should have talked about it at very first.
I modified several upstream files because some of them files couldn't be
used direc
Hi team,
It's a friendly reminder that we've got voting open [1] until next meeting.
If you would like to attend Horizon meetings, please, select comfortable
options for you.
[1] https://doodle.com/poll/ei5gstt73d8v3a35
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Wed, Mar 21, 2018 at 6
Hi Xinni,
There is no need that you push a tag manually for official deliverables.
You can propose a patch to openstack/releases repository.
Horizon PTL or release liaison (at now both Ivan) can confirm it and the
release team will approve it.
Once it is approved, a release tag will be added and a
Hi Xinni,
Please, send me a list of packages which should be released.
In general, release-* groups are different from core-*. We should discuss
how to go forward with it
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Wed, Apr 4, 2018 at 8:34 AM, Xinni Ge wrote:
> Hi Ivan and other Hori
Hi Ivan and other Horizon team member,
Thanks for adding us into xstatic-core group.
But I still need your opinion and help to release the newly-added xstatic
packages to pypi index.
Current `xstatic-core` group doesn't have the permission to PUSH SIGNED
TAG, and I cannot release the first non-tr
Hi Ivan,
Thank you very much.
I've confirmed that all of us have been added to xstatic-core.
As discussed, we will focus on the followings what we added for
heat-dashboard, will not touch other xstatic repos as core.
xstatic-angular-material
xstatic-angular-notify
xstatic-angular-uuid
xstatic-a
Hi Kuz,
Don't worry, we're on the same page with you. I added both you, Xinni and
Keichii to the xstatic-core group. Thank you for your contributions!
Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
On Wed, Mar 28, 2018 at 5:18 PM, Kaz Shinohara wrote:
> Hi Ivan & Horizon folks
>
>
> AFAIK,
Hi Ivan & Horizon folks
AFAIK, Horizon team had conclusion that you will add the specific
members to xstatic-core, correct ?
Can I ask you to add the following members ?
# All of tree are heat-dashboard core.
Kazunori Shinohara / ksnhr.t...@gmail.com #myself
Xinni Ge / xinni.ge1...@gmail.com
Kei
On 3/14/18 6:59 PM, Tony Breeds wrote:
> On Thu, Mar 15, 2018 at 07:16:11AM +0900, Akihiro Motoki wrote:
>> (1) it makes difficult to run tests in local environment
>> We have only released version of neutron/horizon on PyPI. It means
>> PyPI version (i.e. queens) is installed when we run tox in o
Hi team,
As was discussed at PTG, usually we've got a very few participants on our
weekly meetings. I hope, mostly it's because of not comfort meeting time
for many of us.
Let's try to re-schedule Horizon weekly meetings and get more attendees
there. I've created a doodle for it [1]. Please, vote
Hi Ivan, Akihiro,
Thanks for your kind arrangement.
Looking forward to hearing your decision soon.
Regards,
Kaz
2018-03-21 21:43 GMT+09:00 Ivan Kolodyazhny :
> HI Team,
>
> From my perspective, I'm OK both with #2 and #3 options. I agree that #4
> could be too complicated for us. Anyway, we've
HI Team,
>From my perspective, I'm OK both with #2 and #3 options. I agree that #4
could be too complicated for us. Anyway, we've got this topic on the
meeting agenda [1] so we'll discuss it there too. I'll share our decision
after the meeting.
[1] https://wiki.openstack.org/wiki/Meetings/Horizon
Hi Kaz and Ivan,
Yeah, it is worth discussed officially in the horizon team meeting or the
mailing list thread to get a consensus.
Hopefully you can add this topic to the horizon meeting agenda.
After sending the previous mail, I noticed anther option. I see there are
several options now.
(1) Kee
Hi Akihiro,
Thanks for your comment.
The background of my request to add us to xstatic-core comes from
Ivan's comment in last PTG's etherpad for heat-dashboard discussion.
https://etherpad.openstack.org/p/heat-dashboard-ptg-rocky-discussion
Line135, "we can share ownership if needed - e0ne"
Jus
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-c
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" in
Hi horizon plugin developers,
As you know, mox-removal is one of the community goal in Rocky and
horizon team is working on removing usage of mox [1].
This mail announces the plan of dropping mox dependencies in horizon
test helpers (horizon.test.helpers.TestCase and/or
openstack_dashboard.test.h
kolla install openstack packages through master tarball file on kolla
master branch[0]. like
pip install -c upper-constraints.txt neutron-master.tar.gz
On stable branch, kolla install through neutron tag tarball. so it should
work.
But i think there will be also some issue here. How about i wan
On 2018-03-16 11:49, Jeffrey Zhang wrote:
> Now it breaks the kolla's master branch jobs. And have to remove the
> "horizon"
> and "neutron" in the upper-constraints.txt file. check[1][2].
>
> i wanna know what's the correct way to install horizon develop
> branch with upper-constraints.txt file?
Now it breaks the kolla's master branch jobs. And have to remove the
"horizon"
and "neutron" in the upper-constraints.txt file. check[1][2].
i wanna know what's the correct way to install horizon develop
branch with upper-constraints.txt file?
[1] https://review.openstack.org/#/c/549456/4/docker
Excerpts from Thomas Morin's message of 2018-03-15 10:15:38 +0100:
> Hi Doug,
>
> Doug Hellmann, 2018-03-14 23:42:
> > We keep doing lots of infra-related work to make it "easy" to do
> > when it comes to
> > managing dependencies. There are three ways to address the issue
> > with horizon and n
On 2018-03-15 10:05, Thomas Morin wrote:
> Hi Andreas, all,
>
> Andreas Jaeger, 2018-03-14 20:46:
>> Note that thanks to the tox-siblings feature, we really continue to
>> install neutron and horizon from git - and not use the versions in the
>> global-requirements constraints file.
>
> This addr
Hi Doug,
Doug Hellmann, 2018-03-14 23:42:
> We keep doing lots of infra-related work to make it "easy" to do
> when it comes to
> managing dependencies. There are three ways to address the issue
> with horizon and neutron, and none of them involve adding features
> to pbr.
>
> 1. Things that ar
Hi Andreas, all,
> Note that thanks to the tox-siblings feature, we really continue to
> install neutron and horizon from git - and not use the versions in
> the global-requirements constraints file.
This addresses my main concern, which was that by removing
tools/tox_install.sh we would end up no
Excerpts from Tony Breeds's message of 2018-03-15 11:59:00 +1100:
> On Thu, Mar 15, 2018 at 07:16:11AM +0900, Akihiro Motoki wrote:
> > The current version of proposed patches which drops tox_install.sh
> > works in our CI. Even if we have neutron>=12.0.0 (queens) or
> > horizon>=13.0.0 (queens), i
On Thu, Mar 15, 2018 at 07:16:11AM +0900, Akihiro Motoki wrote:
> The current version of proposed patches which drops tox_install.sh
> works in our CI. Even if we have neutron>=12.0.0 (queens) or
> horizon>=13.0.0 (queens), if we have "required-projects" in zuul v3
> config, tox-sibling role ensure
On Wed, Mar 14, 2018 at 10:25:49PM +, Chris Dent wrote:
> On Thu, 15 Mar 2018, Akihiro Motoki wrote:
>
> > (1) it makes difficult to run tests in local environment
> > We have only released version of neutron/horizon on PyPI. It means
> > PyPI version (i.e. queens) is installed when we run tox
1 - 100 of 2083 matches
Mail list logo
