Forward the next hackathon session and add cinder tag :)
-- Forwarded message -
From: Fred Li
Date: 2018年6月12日周二 下午4:40
Subject: [openstack-dev] OpenStack Hackathon for Rocky release
To: OpenStack Development Mailing List (not for usage questions) <
thx guys , patch has been submitted at
https://review.openstack.org/574927
On Wed, Jun 13, 2018 at 8:09 AM Clark Boylan wrote:
> On Tue, Jun 12, 2018, at 4:59 PM, Sean McGinnis wrote:
> > On 06/12/2018 06:01 PM, Zhipeng Huang wrote:
> > > Hi Doug,
> > >
> > > Thanks for raising this, we will
On Tue, Jun 12, 2018, at 4:59 PM, Sean McGinnis wrote:
> On 06/12/2018 06:01 PM, Zhipeng Huang wrote:
> > Hi Doug,
> >
> > Thanks for raising this, we will check it out
> >
>
> Clark was sharped eyed enough to point out that setuptools does not
> accept regexes for
> data files. So it would
On 06/12/2018 06:01 PM, Zhipeng Huang wrote:
Hi Doug,
Thanks for raising this, we will check it out
Clark was sharped eyed enough to point out that setuptools does not
accept regexes for
data files. So it would appear this:
Ok, I was able to login to the fuel instance with the default r00tme password,
but I still can’t configure the fuel master and enable the web service. It also
has a default IP of 10.20.0.1 but even if i could access that I think it’s
still useless without having ran the setup.
Any ideas?
Hi Doug,
Thanks for raising this, we will check it out
On Wed, Jun 13, 2018 at 6:32 AM Doug Hellmann wrote:
> Excerpts from zuul's message of 2018-06-12 21:57:02 +:
> > Build failed.
> >
> > - release-openstack-python
>
Excerpts from Zane Bitter's message of 2018-06-12 17:52:24 -0400:
> On 12/06/18 11:41, Michael Johnson wrote:
> > I think we should continue with option 1.
> >
> > It is an indicator that a project is active in OpenStack and is
> > explicit about which code should be used together.
> >
> > Both
Excerpts from zuul's message of 2018-06-12 21:57:02 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/2c/2ca19224a22541ceccf74c6f760ee40a2c90fed2/pre-release/release-openstack-python/124b5be/
> : FAILURE in 6m 45s
> - announce-release announce-release : SKIPPED
>
HTML: https://anticdent.org/tc-report-18-24.html
Here's TC Report 24. The last one was 4 weeks ago, itself following
a gap. In the intervening time new TC members (Graham Hayes,
Mohammed Naser, and Zane Bitter) and a new Chair (Doug Hellman) have
found their feet very well, we had a successful
Hi all,
It was working previously, but on a freshly-made VM and a fuel-community 11.0
iso the installer completes and reboots the vm but at no point was I presented
with the fuel setup TUI to setup my networking or set passwords, etc. It’s
inaccessible because I don’t know what the root
On 12/06/18 11:41, Michael Johnson wrote:
I think we should continue with option 1.
It is an indicator that a project is active in OpenStack and is
explicit about which code should be used together.
Both of those statements hold no technical water, but address the
"human" factor of "What is
On 11/06/18 18:49, Zane Bitter wrote:
It's had a week to percolate (and I've seen quite a few people viewing
the etherpad), so here is the review:
https://review.openstack.org/574479
In response to comments, I moved the change to the Project Team Guide
instead of the Contributor Guide (since
I would like to create a version of the jobs that run as part of
lib-forward-testing (legacy-tempest-dsvm-neutron-src) that works under
python 3. I'm not sure the best way to proceed, since that's a legacy
job.
I'm not sure I'm familiar enough with the job to port it to be
zuulv3 native and allow
Excerpts from Michael Johnson's message of 2018-06-12 08:41:57 -0700:
> I think we should continue with option 1.
>
> It is an indicator that a project is active in OpenStack and is
> explicit about which code should be used together.
>
> Both of those statements hold no technical water, but
Hello,
I was unable to get anti-affinity to work in Sahara. The logs were
reporting a Heat error that u'' was not a valid UUID. Upon further
investigation, I think I found several errors in the
`sahara/service/heat/templates.py` file. I'm working with Sahara 7.0.0 but
the master branch still
Welcome to the twenty-fourth 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:
I wanted to provide an update on some next steps around config-download/Ansible
and TripleO. Now that we've completed transitioning to config-download by
default in Rocky, some might be wondering where we're going next.
1. Standalone roles.
The idea here is to refactor the ansible tasks lists
On Mon, Jun 11, 2018 at 2:53 AM, Thierry Carrez wrote:
>
> 2bis/ Like 2, but only create the branch when needed
>
> Same as the previous one, except that rather than proactively create the
> stable branch around release time, we'd wait until the branch is actually
> needed to create it.
>
This
On Tue, Jun 12, 2018 at 11:21 AM James Slagle
wrote:
> On Tue, Jun 12, 2018 at 11:03 AM, Jiří Stránský wrote:
> > On 12.6.2018 15:06, James Slagle wrote:
> >>
> >> On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin
> >> wrote:
> >>>
> >>> Greetings,
> >>>
> >>> I wanted to let everyone know that
I think we should continue with option 1.
It is an indicator that a project is active in OpenStack and is
explicit about which code should be used together.
Both of those statements hold no technical water, but address the
"human" factor of "What is OpenStack?", "What do I need to deploy?",
Doug Hellmann wrote:
> If an epic is just a list of stories, doesn't that make it a worklist?
Worklists are one way to do epics. In prior discussion about epics, a
number of people have raised the idea that an epic contains more than just a
list of stories, but also connective narrative
On Tue, Jun 12, 2018 at 11:03 AM, Jiří Stránský wrote:
> On 12.6.2018 15:06, James Slagle wrote:
>>
>> On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin
>> wrote:
>>>
>>> Greetings,
>>>
>>> I wanted to let everyone know that we have a keystone only deployment and
>>> upgrade job in check
On 12.6.2018 15:06, James Slagle wrote:
On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin wrote:
Greetings,
I wanted to let everyone know that we have a keystone only deployment and
upgrade job in check non-voting. I'm asking everyone in TripleO to be
mindful of this job and to help make sure
On Tue, Jun 12, 2018 at 7:46 AM, Doug Hellmann
wrote:
> Excerpts from Dean Troyer's message of 2018-06-12 09:28:48 -0500:
> > On Mon, Jun 11, 2018 at 5:02 PM, Emilien Macchi
> wrote:
> > > While I agree with Doug that we assume good faith and hope for the
> best, I
> > > personally think we
Matt,
The end goal is that certificate validation will always occur alongside
signature validation, but we wanted there to be an upgrade path that would
allow signature validation to continue to work until certificate validation was
set up. See the first paragraph of the proposed change in
HI,
I am using OpenvSwitch 2.6.1
I would like to know, How we can backup and restore ovsdb in the controller
and compute nodes.
I think, ovsdb not in cluster mode, So we have to take backup from all
controller and compute nodes.
Please let me know if you have any idea.
$ ovsdb-server -V
HI,
I am using OpenvSwitch 2.6.1
I would like to know, How we can backup and restore ovsdb in the controller
and compute nodes.
I think, ovsdb not in cluster mode, So we have to take backup from all
controller and compute nodes.
Please let me know if you have any idea.
$ ovsdb-server -V
Excerpts from Dean Troyer's message of 2018-06-12 09:28:48 -0500:
> On Mon, Jun 11, 2018 at 5:02 PM, Emilien Macchi wrote:
> > While I agree with Doug that we assume good faith and hope for the best, I
> > personally think we should help them (what we're doing now) but also make
> > sure we DO
On Mon, Jun 11, 2018 at 5:02 PM, Emilien Macchi wrote:
> While I agree with Doug that we assume good faith and hope for the best, I
> personally think we should help them (what we're doing now) but also make
> sure we DO NOT set a precedent. We could probably learn from this situation
> and
Excerpts from Matt Riedemann's message of 2018-06-11 18:00:12 -0500:
> On 6/11/2018 3:31 PM, Doug Hellmann wrote:
> > As we shift teams over to Storyboard, we have another opportunity
> > to review the processes and to decide how to use the new tool. Some
> > teams with lightweight processes will
On 2018-06-12 09:00:47 -0500 (-0500), Matt Riedemann wrote:
[...]
> In this scenario, if the user fails to provide trusted certs when
> creating or rebuilding a server, it's going to result in a build
> abort exception (NoValidHost) from the compute. Is that the
> intention?
[...]
It's at least
Just a heads up that there's a summary of the "Organizational
diversity tag" thread for the openstack-dev ML starting here:
http://lists.openstack.org/pipermail/openstack-dev/2018-June/131399.html
Among other things, the follow-up discussion of the summary asks
whether operators/deployers find
On 6/11/2018 6:00 PM, Matt Riedemann wrote:
On 6/11/2018 3:31 PM, Doug Hellmann wrote:
As we shift teams over to Storyboard, we have another opportunity
to review the processes and to decide how to use the new tool. Some
teams with lightweight processes will be able to move directly with
Sylvain and I were reviewing https://review.openstack.org/#/c/479949/
today and I'm at least a bit confused over how the
enable_certificate_validation config option is meant to be used.
The current logic during driver.spawn() on the compute is going to be:
if the user supplied trusted certs
On 12/06/18 15:25 +0200, Kendall Nelson wrote:
Yes! I can definitely set Manila up in storyboard-dev. I'll get the imports
done before the end of the week :)
-Kendall (diablo_rojo)
Thanks much!
On Tue, 12 Jun 2018, 2:53 pm Tom Barron, wrote:
On 12/06/18 10:57 +0200, Kendall Nelson
On Tue, Jun 12, 2018 at 1:07 PM Thierry Carrez
wrote:
> Neil Jerram wrote:
> >> The issue is that the current method (which uses a formula to apply
> >>single-vendor and diverse-affiliation tags) is not working so well
> >>anymore, with lots of low-activity projects quickly flapping
Yes! I can definitely set Manila up in storyboard-dev. I'll get the imports
done before the end of the week :)
-Kendall (diablo_rojo)
On Tue, 12 Jun 2018, 2:53 pm Tom Barron, wrote:
> On 12/06/18 10:57 +0200, Kendall Nelson wrote:
> >Another option for playing around things- I am happy to do a
On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin wrote:
> Greetings,
>
> I wanted to let everyone know that we have a keystone only deployment and
> upgrade job in check non-voting. I'm asking everyone in TripleO to be
> mindful of this job and to help make sure it continues to pass as we move it
On 12/06/18 11:44 +0200, Thierry Carrez wrote:
Hi!
We had a decently-sized thread on how to better track organizational
diversity, which I think would benefit from a summary.
The issue is that the current method (which uses a formula to apply
single-vendor and diverse-affiliation tags) is
On 12/06/18 10:57 +0200, Kendall Nelson wrote:
Another option for playing around things- I am happy to do a test migration
and populate our storyboard-dev instance with your real data from lp. The
last half a dozen teams we have migrated have been handled this way.
Can we do this for manila?
On 2018-06-11 17:55:24 -0500 (-0500), Matt Riedemann wrote:
> On 6/11/2018 3:23 PM, Jeremy Stanley wrote:
> > If you recall the "specs" experiment years
> > ago, a few teams tried mildly different solutions for moving from LP
> > blueprints with random wiki page links to tracking specifications in
Neil Jerram wrote:
The issue is that the current method (which uses a formula to apply
single-vendor and diverse-affiliation tags) is not working so well
anymore, with lots of low-activity projects quickly flapping between
states.
I think you need to explore and state much more
FWIW, as an outside observer of this conversation:
On Tue, Jun 12, 2018 at 10:46 AM Thierry Carrez
wrote:
>
> The issue is that the current method (which uses a formula to apply
> single-vendor and diverse-affiliation tags) is not working so well
> anymore, with lots of low-activity projects
Hi team
As I'm not available to host our meeting this week, would like to ask if
there Are any issues we should target or discuss this week?
If there is none I suggest we skip meeting this week.
--
May The Force of OpenStack Be With You,
*Rico Lin*irc: ricolin
Hi!
We had a decently-sized thread on how to better track organizational
diversity, which I think would benefit from a summary.
The issue is that the current method (which uses a formula to apply
single-vendor and diverse-affiliation tags) is not working so well
anymore, with lots of
Another option for playing around things- I am happy to do a test migration
and populate our storyboard-dev instance with your real data from lp. The
last half a dozen teams we have migrated have been handled this way.
Playing around with StoryBoard ahead of time is a really good idea because
it
Hi all OpenStackers,
Since April 2015, there have been 7 OpenStack Bug Smash events in
China. If you are interested, please visit [1].
Now, the 8th OpenStack bug smash is coming. Intel, Huawei, Tecent and
CESI will host this event. Just to highlight, this event is changed to
Open Source
Thanks for the patch Zane :)
-Kendall (diablo_rojo)
On Mon, Jun 11, 2018 at 3:50 PM Zane Bitter wrote:
> On 04/06/18 10:13, Zane Bitter wrote:
> > On 31/05/18 14:35, Julia Kreger wrote:
> >> Back to the topic of nitpicking!
> >>
> >> I virtually sat down with Doug today and we hammered out the
Hey all,
Is there any way to configure Oslo db to perform sql write (update/delete)
on a different db server than for read only?
I can only see connection string.
Thanks.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Doug Hellmann wrote:
[...]
The release team used to (help) manage the launchpad series data.
We stopped doing that a long time ago, as Jeremy pointed out, because
it was not useful to *the release team* in the way we were managing
the releases. We stopped tracking blueprints and bug fixes to try
Hello everyone,
I configured ocata with three vm backends
and one proxy
when a storage backends goes down, proxy continues to redirect write
requests to it. Is is the default behaviour ?
Please, could anyone help me ?
I expect proxy does not redirect write request to a shutdown node
automatically.
51 matches
Mail list logo
