Doug recently introduced the template publish-to-pypi-python3 and used
it for all official projects. It only has a minimal python3 usage
(calling setup.py sdist bdist_wheel) that should work with any repo.
Thus, I pushed a a series of changes up - see
On 11/2/2018 2:22 PM, Eric Fried wrote:
Based on a (long) discussion yesterday [1] I have put up a patch [2]
whereby you can set [compute]resource_provider_association_refresh to
zero and the resource tracker will never* refresh the report client's
provider cache. Philosophically, we're removing
I've completely wiped the node and reinstalled it, and the problem still
persists. I can't ping instances on other compute nodes, or ping the DHCP
ports. Instances don't get addresses or metadata when started on this node.
From: Marcio Prado
Sent: 11/1/18 9:51 AM
To:
All-
Based on a (long) discussion yesterday [1] I have put up a patch [2]
whereby you can set [compute]resource_provider_association_refresh to
zero and the resource tracker will never* refresh the report client's
provider cache. Philosophically, we're removing the "healing" aspect of
the
Hello folks.
Here is an update for today. I crated a draft [0], and spend some time
with building LaTeX with live-updating for the compiled PDF... The
latter is only informational, if someone wants to contribute, please
follow the instructions listed by the link (hint: you need no to have
any
# Keystone Team Update - Week of 29 October 2018
## News
### Berlin Summit
Somewhat quiet week as we've been getting into summit prep mode. We'll have two
forum sessions, one for operator feedback[1] and one to discuss Keystone as an
IdP Proxy[2]. We'll have our traditional project update[3]
On Fri, Nov 2, 2018 at 9:39 AM Dan Prince wrote:
>
> I pushed a patch[1] to update our containerized deployment
> architecture docs yesterday. There are 2 new fairly useful sections we
> can leverage with TripleO's stepwise deployment. They appear to be
> used somewhat sparingly so I wanted to
The Diversity and Inclusion WG is still looking for your assistance in
reaching and including data from as many members of our community as
possible.
We revised the Diversity Survey that was originally distributed to the
Community in the Fall of 2015 and reached out in August with our new
survey.
On 11/1/18 4:44 PM, Jay Bryant wrote:
On Thu, Nov 1, 2018, 10:44 AM Rambo wrote:
Hi,all
Recently, I use the nfs driver as the cinder-backup backend, when I
use it to backup the volume snapshot, the result is return the
NotImplementedError[1].And the nfs.py doesn't has the
On 11/1/2018 7:22 PM, Kendall Nelson wrote:
We've made a lot of progress in StoryBoard-land over the last couple of
releases cleaning up bugs, fixing UI annoyances, and adding features
that people have requested. All along we've also continued to migrate
projects as they've become unblocked.
Thanks! We have been slow to update our docs. I did put up a blog post
about these sections of the templates [1], in case folks find that useful.
[1] http://jaormx.github.io/2018/dissecting-tripleo-service-templates-p2/
On 11/2/18 3:39 PM, Dan Prince wrote:
> I pushed a patch[1] to update our
I pushed a patch[1] to update our containerized deployment
architecture docs yesterday. There are 2 new fairly useful sections we
can leverage with TripleO's stepwise deployment. They appear to be
used somewhat sparingly so I wanted to get the word out.
The first is 'deploy_steps_tasks' which
Hi,
There does seem to be something currently wonky with SSL &
oslo.messaging. I'm looking into it now.
And there's this recently reported issue:
https://bugs.launchpad.net/oslo.messaging/+bug/1800957
In the above bug something seems to have broken SSL between ocata and
pike. The current
Hi Gokhan,
There's been a flurry of folks reporting issues recently related to pike
and SSL. See:
https://bugs.launchpad.net/oslo.messaging/+bug/1800957
and
https://bugs.launchpad.net/oslo.messaging/+bug/1801011
I'm currently working on this - no status yet.
As a test would it be possible to
HTML: https://anticdent.org/placement-update-18-44.html
Good morning, it's placement update time.
# Most Important
Lately attention has been primarily on specs, database migration
tooling, and progress on documentation. These remain the important
areas.
# What's Changed
* [Placement
Dear Nova Community,
I want to announce the new focal point for Nova s390x libvirt/kvm.
Please welcome "Cathy Zhang” to the Nova team. She and her team will be
responsible for maintaining the s390x libvirt/kvm Thirdparty CI [1] and any
s390x specific code in nova and os-brick.
I personally
16 matches
Mail list logo
