Hello everyone,
A new release candidate for sahara-image-elements for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/sahara-image-elements/
Unless release-critical issues are found that warrant a release
candidate respin,
Hello everyone,
A new release candidate for sahara-dashboard for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/sahara-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hello everyone,
A new release candidate for sahara for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/sahara/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Hello everyone,
A new release candidate for glance for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/glance/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Thanks for the notification!
Blazar has already support the versioned notification. It consumes the
service.update type notification internally. And I checked the feature
works only with the versioned one.
best regards,
Masahito
On 2018/08/09 18:41, Balázs Gibizer wrote:
Dear Nova
On Thu, Aug 09, 2018 at 08:00:13PM -0600, Wesley Hayutin wrote:
> On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
>
> > On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> > wrote:
> > > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> > >> Ahoy folks,
> > >>
> > >> I think
On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote:
> On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann
> wrote:
> > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> >> Ahoy folks,
> >>
> >> I think it's time we come up with some basic rules/patterns on where
> >> code lands when
Hello everyone,
A new release candidate for networking-bgpvpn for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-bgpvpn/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hello everyone,
A new release candidate for networking-odl for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-odl/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello everyone,
A new release candidate for neutron-vpnaas for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron-vpnaas/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello everyone,
A new release candidate for networking-sfc for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-sfc/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello everyone,
A new release candidate for neutron-dynamic-routing for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron-dynamic-routing/
Unless release-critical issues are found that warrant a release
candidate
Hello everyone,
A new release candidate for networking-midonet for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-midonet/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hello everyone,
A new release candidate for networking-bagpipe for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-bagpipe/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hello everyone,
A new release candidate for networking-ovn for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-ovn/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello everyone,
A new release candidate for neutron for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be
Hello everyone,
A new release candidate for neutron-fwaas for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron-fwaas/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Resending the below since several projects using ReadTheDocs appear to have
missed this. If your project publishes docs to ReadTheDocs, please follow these
steps to avoid job failures.
On Fri, Aug 03, 2018 at 02:20:40PM +1000, Ian Wienand wrote:
> Hello,
>
> tl;dr : any projects using the
Hello everyone,
A new release candidate for congress-dashboard for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hello everyone,
A new release candidate for congress for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be
Hello everyone,
A new release candidate for nova_powervm for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/nova-powervm/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will
Hello everyone,
A new release candidate for networking-powervm for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/networking-powervm/
Unless release-critical issues are found that warrant a release
candidate respin, this
Dear L3 sub-team members,
On August 16th I will be on a business trip and other team members will be
off on vacation. As a consequence, we will cancel our weekly meeting that
day. We will resume at the usual time on the August 23rd
Best regards
Miguel
Dear Neutron team members,
Tomorrow I will be on an airplane during the drivers team meeting time and
one team member is off on vacation. Next week, two of our team members will
be off on vacation. As a consequence, Let's cancel the meetings on August
10th and 17th. We will resume normally on the
Hello everyone,
A new release candidate for ceilometer-powervm for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/ceilometer-powervm/
Unless release-critical issues are found that warrant a release
candidate respin, this
You have done such amazing things with the program! We appreciate
everything you do :) Enjoy the little extra spare time.
-Kendall (daiblo_rojo)
On Tue, Aug 7, 2018 at 4:48 PM Victoria Martínez de la Cruz <
victo...@vmartinezdelacruz.com> wrote:
> Hi all,
>
> I'm reaching you out to let you
On Thu, Aug 09, 2018 at 05:20:53PM -0400, Doug Hellmann wrote:
> Excerpts from Tony Breeds's message of 2018-08-08 14:39:30 +1000:
> > Hello all,
> > With the PTL elections behind us it's time to start looking at the
> > TC election. Our charter[1] says:
> >
> > The election is held no
It appears this is to do with Keystone v3-created users not having any role
assignment by default. Big thanks to lbragstad for helping me to
understand this on IRC; he also provided this link as historical context
for this situation: https://bugs.launchpad.net/keystone/+bug/1662911.
In detail, I
On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann wrote:
> Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
>> Ahoy folks,
>>
>> I think it's time we come up with some basic rules/patterns on where
>> code lands when it comes to OpenStack related Ansible roles and as we
>>
Excerpts from Tony Breeds's message of 2018-08-08 14:39:30 +1000:
> Hello all,
> With the PTL elections behind us it's time to start looking at the
> TC election. Our charter[1] says:
>
> The election is held no later than 6 weeks prior to each OpenStack
> Summit (on or before ‘S-6’
Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> Ahoy folks,
>
> I think it's time we come up with some basic rules/patterns on where
> code lands when it comes to OpenStack related Ansible roles and as we
> convert/export things. There was a recent proposal to create an
>
Hi Alex,
I am very much in favour of what you're bringing up. We do have
multiple projects that leverage Ansible in different ways and we all
end up doing the same thing at the end. The duplication of work is
not really beneficial for us as it takes away from our use-cases.
I believe that
Ahoy folks,
I think it's time we come up with some basic rules/patterns on where
code lands when it comes to OpenStack related Ansible roles and as we
convert/export things. There was a recent proposal to create an
ansible-role-tempest[0] that would take what we use in
On Wed, Aug 1, 2018 at 11:15 AM, Ben Nemec wrote:
> Hi,
>
> I'm having an issue with no valid host errors when starting instances and
> I'm struggling to figure out why. I thought the problem was disk space,
> but I changed the disk_allocation_ratio and I'm still getting no valid
> host. The
Excerpts from Tony Breeds's message of 2018-08-01 10:32:50 +1000:
[snip]
> Need appointment : 8 (Dragonflow Freezer Loci Packaging_Rpm RefStack
>Searchlight Trove Winstackers)
To summarize the situation for these teams as it stands now:
Omer Anson
On 8/9/2018 1:30 PM, Graham Hayes wrote:
You could just send the deprecation notice, and we could deprecate
designate-sink if no one came forward to update it - that seems fairer
to push the burden on to the people who actually use the feature, not
other teams maintaining legacy stuff. Does that
Hello everyone,
A new release candidate for heat for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/heat/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Hello everyone,
A new release candidate for cinder for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/cinder/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
On 09/08/2018 15:27, Matt Riedemann wrote:
> On 8/9/2018 8:44 AM, Graham Hayes wrote:
>> Designate has no plans to swap or add support for the new interface in
>> the near or medium term - we are more than willing to take patches, but
>> we do not have the people power to do it ourselves.
>>
>>
On 8/9/2018 12:53 PM, Lance Bragstad wrote:
I could have sworn I created a bug in oslo.policy for this at one
point for the same reason Jay mentions it, but I guess not.
This?https://bugs.launchpad.net/oslo.policy/+bug/1421863
Not unless I was time traveling (note the date that was
Excerpts from Lance Bragstad's message of 2018-08-09 12:55:52 -0500:
>
> On 08/09/2018 12:48 PM, Doug Hellmann wrote:
> > Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500:
> >> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
> >>> Excerpts from Jay Pipes's message of 2018-08-08
On 08/09/2018 12:48 PM, Doug Hellmann wrote:
> Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500:
>> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
>>> Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
For evidence, see:
On 08/09/2018 12:18 PM, Matt Riedemann wrote:
> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
>> Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
>>> For evidence, see:
>>>
>>>
Excerpts from zuul's message of 2018-08-09 17:23:01 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/84/84135048cb372cbd11080fc27151949cee4e52d1/pre-release/release-openstack-python/095990b/
> : FAILURE in 8m 57s
> - announce-release announce-release : SKIPPED
>
Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500:
> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
> > Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
> >> For evidence, see:
> >>
> >>
On 8/9/2018 12:18 PM, Matt Riedemann wrote:
We could simply, on the nova side, add a warnings filter to only log
this once.
Let's see if this works:
https://review.openstack.org/#/c/590445/
--
Thanks,
Matt
__
Hey Jirka!
I wasn't aware of the other options available. Basically yes, you now just
need to upload a tarball of the templates to swift. You can see in the
client:
-tarball.tarball_extract_to_swift_container(
-swift_client, tmp_tarball.name, container_name)
+
On 8/9/2018 11:47 AM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
For evidence, see:
http://logs.openstack.org/41/590041/1/check/tempest-full-py3/db08dec/controller/logs/screen-placement-api.txt.gz?level=WARNING
thousands of these are filling the logs
Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
> For evidence, see:
>
> http://logs.openstack.org/41/590041/1/check/tempest-full-py3/db08dec/controller/logs/screen-placement-api.txt.gz?level=WARNING
>
> thousands of these are filling the logs with WARNING-level log messages,
>
On 2018-08-09 11:41:38 +0200 (+0200), Balázs Gibizer wrote:
[...]
> There is a list of projects (we know of) consuming the legacy
> interface and we would like to know if any of these projects plan
> to switch over to the new interface in the foreseeable future so
> we can make a well informed
Greetings OpenStack community,
As is our recent custom, short meeting this week. Our main topic of
conversation was discussing the planning etherpad [7] for the API-SIG gathering
at the Denver PTG. If you will be there, and have topics of interest, please
add them to the etherpad.
There
Excerpts from Andrey Kurilin's message of 2018-08-09 13:35:53 +0300:
> Hi Doug!
>
> I'm ready to port our job to openstack-zuul-jobs repo, but I expect that
> Community will not accept it.
>
> The result of rally unittests is different between environments with python
> 3.7 final release and
Hello Kollegues, Koalas and Koalines,
I feel I should do the same, as my work sadly doesn't involve Kolla,
or OpenStack for that matter, any more.
It has been a wonderful time and serving Kolla community as core and
PTL is achievement I'm most proud of and I thank you all for giving me
this
Hello everyone,
A new release candidate for keystone for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/keystone/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be
Hello everyone,
A new release candidate for manila for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
?Kollians,
Thanks for the kind words.
I do plan to stay involved in the OpenStack community - specifically targeting
governance and will definitely be around - irc - mls - summits - etc :)
Cheers
-steve
From: Surya Singh
Sent: Wednesday, August 8, 2018
I'd like to create a non-admin project and user that are able to do
nova.images.list(), in a Queens install. IIUC, all users should be able to
do that. I'm afraid I'm pretty lost and would appreciate any help.
Define a function to test whether a particular set of credentials can do
Welcome to the twenty-eightiest edition of a weekly update in TripleO world!
The goal is to provide a short reading (less than 5 minutes) to learn
what's new this week.
Any contributions and feedback are welcome.
Link to the previous version:
Related to below, here is the current list of deliverables waiting for an RC1
release (as of August 9, 15:30 UTC):
barbican
ceilometer-powervm
cinder
congress-dashboard
congress
cyborg
designate-dashboard
designate
glance
heat
masakari-monitors
masakari
networking-bagpipe
networking-bgpvpn
Development Focus
-
Teams should be working on any release critical bugs that would require another
RC before the final release, and thinking about plans for Stein.
General Information
---
Any cycle-with-milestones projects that missed the RC1 deadline should
On 8/9/2018 8:44 AM, Graham Hayes wrote:
Designate has no plans to swap or add support for the new interface in
the near or medium term - we are more than willing to take patches, but
we do not have the people power to do it ourselves.
Some of our users do use the old interface a lot -
On 8/9/2018 4:41 AM, Balázs Gibizer wrote:
* Masakari - I'm not sure Masakari depends on nova notifications or not
From a quick look, it looks like masakari does not rely on nova's
rpc-based notifications and instead registers and listens for libvirt
guest events directly (ceilometer's
Designate has no plans to swap or add support for the new interface in
the near or medium term - we are more than willing to take patches, but
we do not have the people power to do it ourselves.
Some of our users do use the old interface a lot - designate-sink
is quite heavily embeded in some
barbican and novajoin done.
On Mon, 2018-08-06 at 19:23 +0900, Ghanshyam Mann wrote:
> Hi All,
>
> Tempest patch [1] removes the deprecated config option for volume v1
> API and it has dependency on may plugins. I have proposed the patches
> to each plugins using that option [2] to stop using
Hello everyone,
A new release candidate for blazar for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/blazar/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
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
Hello everyone,
A new release candidate for mistral-dashboard for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/mistral-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hello everyone,
A new release candidate for mistral-extra for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/mistral-extra/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello everyone,
A new release candidate for mistral for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/mistral/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be
Hi team, I would like to nominate Zhuo Tang (ztang) for tricircle core member.
ztang has actively joined the discussion of feature development in our offline
meeting and has participated in contribute important blueprints since Rocky,
like network deletion reliability and service function
Hello everyone,
A new release candidate for octavia-dashboard for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/octavia-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hello everyone,
A new release candidate for octavia for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/octavia/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be
Hello everyone,
A new release candidate for neutron-lbaas for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron-lbaas/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hello everyone,
A new release candidate for trove for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/trove/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Hello everyone,
A new release candidate for neutron-lbaas-dashboard for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/neutron-lbaas-dashboard/
Unless release-critical issues are found that warrant a release
candidate
We have a small project (novajoin) that still relies on unversioned
notifications. Thanks for the notification, I hope we can migrate to
versioned notifications by Stein.
On Thu, Aug 9, 2018 at 12:41 PM, Balázs Gibizer wrote:
> Dear Nova notification consumers!
>
>
> The Nova team made progress
Hello everyone,
A new release candidate for trove-dashboard for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/trove-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this
Hi Doug!
I'm ready to port our job to openstack-zuul-jobs repo, but I expect that
Community will not accept it.
The result of rally unittests is different between environments with python
3.7 final release and python 3.7.0~b3 .
There is at least one failed test at python 3.7.0~b3 which is not
Hi All,
Please find the Nova API highlights of this week.
Weekly Office Hour:
===
What we discussed this week:
- Discussed on granular policy spec to update that as default roles are present
now.
- Discussed keypair quota usage bug. and only doc update can be done for now.
Hi Andrey,
Thanks it worked.
On Thu, Aug 9, 2018 at 3:10 PM, Andrey Kurilin
wrote:
> Hi Goutham!
>
> There are 2 issues which can result in such error:
>
> 1) You did not read change log for Rally (see
> https://github.com/openstack/rally/blob/master/CHANGELOG.rst, all
> versions are included
Dear Nova notification consumers!
The Nova team made progress with the new versioned notification
interface [1] and it is almost reached feature parity [2] with the
legacy, unversioned one. So Nova team will discuss on the upcoming PTG
the deprecation of the legacy interface. There is a list
Hi Goutham!
There are 2 issues which can result in such error:
1) You did not read change log for Rally (see
https://github.com/openstack/rally/blob/master/CHANGELOG.rst, all versions
are included there). We do not provide in-tree OpenStack plugins started
from Rally 1.0.0 .You need to install
On 2018-08-09 10:10, Frank Kloeker wrote:
> Hello,
>
> maybe you missed it, translation import jobs are back today. Please
> merge "Imported Translations from Zanata" as soon as possible so we can
> move fast forward with Rocky translation.
> If you have already branched to stable/rocky please
Hello,
maybe you missed it, translation import jobs are back today. Please
merge "Imported Translations from Zanata" as soon as possible so we can
move fast forward with Rocky translation.
If you have already branched to stable/rocky please aware that we
releasenotes translation manage only
Hi Rally Team,
I have been trying to setup rally version v1.1.0
I could successfully install rally but when i try to create the deployment
i am getting this error
*ubuntu@ubuntu:~$ rally deployment create --file=existing.json
--name=existing*
*Env manager got invalid spec:*
* ["There is
85 matches
Mail list logo
