Hi Miguel,
Thank you for your help.
I'll use those precious instructions next time.
Cheers,
Gilles
On 16/10/18 1:32 am, Miguel Lavalle wrote:
Hi Gilles,
The merge of master into feature/graphql has been approved:
https://review.openstack.org/#/c/609455. In the future, you can create
your
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
Hi All,
TC office hour is started on #openstack-tc channel. Feel free to reach to us
for anything you want discuss/input/feedback/help from TC.
-gmann
__
OpenStack Development Mailing List (not for usage questions)
Hi,
I was Neutron bug deputy last week. Below is a short summary about
reported bugs.
Note: I will not be at the team meeting this morning, sorry for the late
notice.
-Brian
Critical bugs
-
None
High bugs
-
* https://bugs.launchpad.net/neutron/+bug/1798472 -
On 10/22/18 5:40 PM, Matt Riedemann wrote:
On 10/22/2018 4:35 PM, Adrian Turjak wrote:
The one other open question I have is about the Adjutant change [2]. I
know Adjutant is very new and I'm not sure what upgrades look like for
that project, so I don't really know how valuable adding the
Hi,
Yes, https://github.com/State-of-the-Edge/glossary is a good initiative. Maybe
we should all just start using the terms defined there and contribute if we
have problems with the definitions.
Br,
Gerg0
From: Teresa Peluso
Sent: Friday, October 19, 2018 4:39 PM
To: Csatari, Gergely (Nokia
On Thu, Oct 18, 2018 at 01:17:13PM +, Jeremy Stanley wrote:
> It's been deleted (again) and the suspected fix approved so
> hopefully it won't recur.
Unfortunately the underlying issue is still a mystery. It recurred
once after the suspected fix was merged [1], and despite trying to
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,
Hello Erik,
Could you specify the DNs you used for all certificates just so that I
can rule it out on my side.
You can redact anything sensitive with some to just get the feel on how
it's configured.
Best regards
Tobias
On 10/22/2018 04:47 PM, Erik McCormick wrote:
On Mon, Oct 22, 2018 at
* melanie witt wrote:
> On Fri, 19 Oct 2018 23:21:01 +0800 (GMT+08:00), Boxiang Zhu wrote:
> >
> > The version of my cinder and nova is Rocky. The scope of the cinder spec[1]
> > is only for available volume migration between two pools from the same
> > ceph cluster.
> > If the volume is in-use
Dear Neutron Stadium projects,
In a QA session during the recent PTG in Denver, it was suggested that the
Stadium projects should move their Tempest plugins to a repository of their
own or added to the Neutron Tempest plugin repository (
https://github.com/openstack/neutron-tempest-plugin). The
> I tested a code change that essentially reverts
> https://review.openstack.org/#/c/276861/1/nova/api/metadata/base.py
>
> In other words, with this change metadata tables are not fetched by
> default in API requests. If I understand correctly, metadata is
> fetched in separate queries as the
On Mon, 22 Oct 2018, Chris Dent wrote:
Thus far I'm not hearing any volunteers. If that continues to be the
case, I'll just keep it on bitbucket as that's the minimal change.
As there was some noise that suggested "if you make it use git I
might help", I put it on github:
* melanie witt wrote:
> On Mon, 22 Oct 2018 11:45:55 +0800 (GMT+08:00), Boxiang Zhu wrote:
> > I created a new vm and a new volume with type 'ceph'[So that the volume
> > will be created on one of two hosts. I assume that the volume created on
> > host dev@rbd-1#ceph this time]. Next step is to
On 10/23/18 9:58 AM, Matt Riedemann wrote:
On 10/23/2018 8:09 AM, Ben Nemec wrote:
Can't we just add a noop command like we are for the services that
don't currently need upgrade checks?
We could, but I was also hoping that for most projects we will actually
be able to replace the noop /
I tested a code change that essentially reverts
https://review.openstack.org/#/c/276861/1/nova/api/metadata/base.py
In other words, with this change metadata tables are not fetched by default
in API requests. If I understand correctly, metadata is fetched in separate
queries as the instance
Make sense, Dan.
Thanks so much for your help.
Sergio
On Tue, Oct 23, 2018 at 5:01 PM Dan Smith wrote:
> > I tested a code change that essentially reverts
> > https://review.openstack.org/#/c/276861/1/nova/api/metadata/base.py
> >
> > In other words, with this change metadata tables are not
On Tue, Oct 23, 2018 at 10:20 AM Tobias Urdin wrote:
>
> Hello Erik,
>
> Could you specify the DNs you used for all certificates just so that I
> can rule it out on my side.
> You can redact anything sensitive with some to just get the feel on how
> it's configured.
>
> Best regards
> Tobias
>
On 10/23/2018 8:09 AM, Ben Nemec wrote:
Can't we just add a noop command like we are for the services that don't
currently need upgrade checks?
We could, but I was also hoping that for most projects we will actually
be able to replace the noop / placeholder check with *something* useful
in
On 10/23/2018 1:41 PM, Sean McGinnis wrote:
Yeah, but part of the reason for placeholders was consistency across all of
the services. I guess if there are never going to be upgrade checks in
adjutant then I could see skipping it, but otherwise I would prefer to at
least get the framework in
Hi nova devs,
Have been having a good look into cellsv2 and how we migrate to them (we’re
still on cellsv1 and about to upgrade to queens and still run cells v1 for now).
One of the problems I have is that now all our nova cell database servers need
to respond to API requests.
With cellsv1 our
On 24/10/18 2:09 AM, Ben Nemec wrote:
>
>
> On 10/22/18 5:40 PM, Matt Riedemann wrote:
>> On 10/22/2018 4:35 PM, Adrian Turjak wrote:
The one other open question I have is about the Adjutant change [2]. I
know Adjutant is very new and I'm not sure what upgrades look like for
that
Dear Kolla-ansible team,
I am trying to deploy openstack pike using kolla-ansible 6.1.0 without success.
I am not a python developer so I was wondering whether someone could help
troubleshooting.
[root@openstack-deployment ~]# pip show kolla-ansible
Name: kolla-ansible
Version: 6.1.0
Summary:
Hi All,
TC office hour is started on #openstack-tc channel. Feel free to reach to us
for anything you want discuss/input/feedback/help from TC.
-gmann
__
OpenStack Development Mailing List (not for usage questions)
On Wed, Oct 24, 2018 at 03:23:53AM +, z...@openstack.org wrote:
> Build failed.
>
> - release-openstack-python3
> http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/
> : POST_FAILURE in 2m 18s
So this failed because pypi thinks
On Wednesday, October 24 we will host our next Foundation community
meeting at 8:00 PT / 15:00 UTC. This meeting will focus on an update
on StarlingX, one of the projects in the Edge Computing Strategic Focus
Area.
The full agenda is here:
On Tue, Oct 23, 2018 at 10:30:23AM -0400, Ben Nemec wrote:
>
>
> On 10/23/18 9:58 AM, Matt Riedemann wrote:
> > On 10/23/2018 8:09 AM, Ben Nemec wrote:
> > > Can't we just add a noop command like we are for the services that
> > > don't currently need upgrade checks?
> >
> > We could, but I was
Hi,
Thx Miguel for raising this.
List of tempest plugins is on
https://docs.openstack.org/tempest/latest/plugin-registry.html - if URL for
Your plugin is the same as Your main repo, You should move Your tempest plugin
code.
> Wiadomość napisana przez Miguel Lavalle w dniu
> 23.10.2018, o
Weekly meeting tomorrow will be held tomorrow at the usual time10AM
EST/10PM BJ time
please provide inputs to Sundar's docs if you have the change before the
meeting
https://docs.google.com/spreadsheets/d/179Q8J9qIJNOiVm86K7bWPxo7otTsU18XVCI32V77JaU/edit#gid=0
Let's make our final decision for
I won’t be able to handle the meeting at 8:00 am, so I’d propose to meet at
10:30 am UTC on regular openstack-watcher channel if that’s suitable for you.
Alex Chadin
__
OpenStack Development Mailing List (not for usage
On Wed, 24 Oct 2018 10:54:31 +1100, Sam Morrison wrote:
Hi nova devs,
Have been having a good look into cellsv2 and how we migrate to them
(we’re still on cellsv1 and about to upgrade to queens and still run
cells v1 for now).
One of the problems I have is that now all our nova cell
31 matches
Mail list logo
