On Oct 6, 2017, at 8:21 AM, Chris Dent wrote:
> The extent to which an
> allocation request is not always opaque and the need to be explicit
> about microversions was clarified, so edleafe is going to make some
> adjustments, after first resolving the prerequisite code
>The neutron story is mixed on accessable upgrade, because at least in some
cases, like ovs, upgrade might trigger a network tear down / rebuild that
generates an outage (though typically a pretty small one).
This shouldn't happen. If it does it should be reported as a bug. All
existing OVS flows
There's a couple of options in the object server that are related to how
object data is cached (or generally *not*)
https://github.com/openstack/swift/blob/master/swift/obj/server.py#L921
At scale on dense nodes it becomes challenging to keep all the filesystem
metdata in the page cache, so
On 10/6/2017 1:10 PM, Mathieu Gagné wrote:
I don't think there ever was a technical limitation to add support for it.
See the review comments with the -1 votes on the patches I linked
originally.
There are valid technical reasons for the -1s on those, including on
this one from Paul Murray
Excerpts from Giuseppe de Candia's message of 2017-10-06 13:49:43 -0500:
> Hi Clint,
>
> Isn't user-data by definition available via the Metadata API, which isn't
> considered secure:
> https://wiki.openstack.org/wiki/OSSN/OSSN-0074
>
Correct! The thinking is to account for the MITM attack
I've been chasing something weird I was seeing in devstack when creating
hundreds of instances in a single request where at some limit, things
blow up in an unexpected way during scheduling and all instances were
put into ERROR state. Given the environment I was running in, this
shouldn't have
Hi,
Is there any existing work that leveraging operating system's page cache
for swift?
like many other parallel file systems, lustre, the IO is cached in buffer
and call is returned immediately to user space.
Best,
Jialin
__
Hey all,
The following was done during office hours this week:
Bug #1698455 in OpenStack Identity (keystone): "Install and configure in
Installation Guide: Populate the Identity service database step fails on
CentOS7"
https://bugs.launchpad.net/keystone/+bug/1698455
Triaged and tagged
Bug
Oops! Matt Treinish pointed out i have 6 more months to go :)
Thanks,
Dims
On Fri, Oct 6, 2017 at 8:38 AM, Davanum Srinivas wrote:
> Team,
>
> Please consider my candidacy for Queens. I just realized how time flies,
> reading
> my previous two self nominations [1][2]. As a
Hello,
Since one month is about to pass after Denver PTG.
Here is the status update on the Tempest Plugin split community goals:
List of projects which have already completed the goal:
- Barbican
- Designate
- Horizon
- Keystone
- Kuryr
- Os-win
- Sahara
- Solum
- Watcher
List of projects which
On 2017-10-06 13:49:43 -0500 (-0500), Giuseppe de Candia wrote:
> Isn't user-data by definition available via the Metadata API,
> which isn't considered secure:
> https://wiki.openstack.org/wiki/OSSN/OSSN-0074
[...]
It depends on who you are. If you're the one deploying/running nova
then you can
On 10/06/2017 03:01 AM, Markus Zoeller wrote:
Just a short reminder that rst puts stuff in blockquotes when you're not
careful with the spacing. Example:
* item 1
* item 2
That's in blockquotes because of the 1 blank at the beginning. The
TripleO docs are full with them, which looks a
On 10/06/2017 12:22 PM, Matt Riedemann wrote:
This came up in IRC discussion the other day, but we didn't dig into it
much given we were all (2 of us) exhausted talking about rebuild.
But we have had several bugs over the years where people expect the root
disk to change to a newly supplied
Hi Clint,
Isn't user-data by definition available via the Metadata API, which isn't
considered secure:
https://wiki.openstack.org/wiki/OSSN/OSSN-0074
Or is there a way to specify that certain user-data should only be
available via config-drive (and not metadata api)?
Otherwise, the only
James, thanks for all the information! I will study, try some of this out
and get back to the thread with any more questions or findings.
One topic that may be worth discussing now, is that if we do pass ssh host
keys (including private) via vendordata, then there needs to be a way to
signal to
Many thanks to Jeremy and Clark. We are back on our feet for Mogan.
Thanks,
Dims
On Fri, Oct 6, 2017 at 1:03 PM, Jeremy Stanley wrote:
> On 2017-09-29 00:19:25 -0400 (-0400), Davanum Srinivas wrote:
>> I tried several things, not sure i have enough git-fu to pull this
>> off.
> On Fri, Oct 6, 2017 at 2:02 PM, Chris Friesen
> wrote:
>> On 10/06/2017 11:32 AM, Mathieu Gagné wrote:
>>>
>>> Why not supporting this use case?
>>
>>
>> I don't think anyone is suggesting we support do it, but nobody has stepped
>> up to actually merge a change
I don't think there ever was a technical limitation to add support for it.
I have nothing to back my claims but IIRC, it was more philosophical
points against adding support for it.
--
Mathieu
On Fri, Oct 6, 2017 at 2:02 PM, Chris Friesen
wrote:
> On 10/06/2017
On 10/06/2017 01:22 PM, Matt Riedemann wrote:
> So with all of this in mind, should we at least consider, until at least
> someone owns supporting this, that the API should fail with a 400
> response if you're trying to rebuild with a new image on a volume-backed
> instance? That way it's a fast
On 10/06/2017 11:32 AM, Mathieu Gagné wrote:
Why not supporting this use case?
I don't think anyone is suggesting we support do it, but nobody has stepped up
to actually merge a change that implements it.
I think what Matt is suggesting is that we make it fail fast *now*, and if
someone
On Fri, Oct 6, 2017 at 1:32 PM, Mathieu Gagné wrote:
> Why not supporting this use case?
>
> Same reason as before: A user might wish to keep its IP addresses.
>
> The use cannot do the following to bypass the limitation:
> 1) stop instance
> 2) detach root volume
> 3) delete
On Fri, Oct 6, 2017 at 11:22 AM, Matt Riedemann wrote:
> This came up in IRC discussion the other day, but we didn't dig into it
> much given we were all (2 of us) exhausted talking about rebuild.
>
> But we have had several bugs over the years where people expect the root
>
Why not supporting this use case?
Same reason as before: A user might wish to keep its IP addresses.
The use cannot do the following to bypass the limitation:
1) stop instance
2) detach root volume
3) delete root volume
4) create new volume
5) attach as root
6) boot instance
Last time I tried,
This came up in IRC discussion the other day, but we didn't dig into it
much given we were all (2 of us) exhausted talking about rebuild.
But we have had several bugs over the years where people expect the root
disk to change to a newly supplied image during rebuild even if the
instance is
On 2017-09-29 00:19:25 -0400 (-0400), Davanum Srinivas wrote:
> I tried several things, not sure i have enough git-fu to pull this
> off. For example.
[...]
> remote: ERROR: In commit de26dc69aa28f57512326227a65dc3f9110a7be1
> remote: ERROR: committer email address sleepsonthefl...@gmail.com
>
Yes, job_name_in_report = true did it!
---
Andreas Scheuring (andreas_s)
> On 6. Oct 2017, at 17:01, Andreas Scheuring
> wrote:
>
> Probably it’s the following setting in zuul.conf
>
> job_name_in_report = true
>
> We’ll see if it works out in 1.5h when the
Hi Kim,
Thanks for trying the feature out! There are 2 levels of Neutron
integration with DNS:
1. Integration with Neutron's own internal DNS service. In short, ports
get a DHCP lease from a dnsmasq instance associated to their network. This
dnsmasq instance also assigns DNS attributes
Probably it’s the following setting in zuul.conf
job_name_in_report = true
We’ll see if it works out in 1.5h when the first test succeeded…
Thanks!
---
Andreas Scheuring (andreas_s)
> On 6. Oct 2017, at 12:53, Sean Dague wrote:
>
> On 10/06/2017 04:07 AM, Andreas Scheuring
On 2017-10-05 22:51:31 -0400 (-0400), me...@openstack.org wrote:
[...]
> * setup of Google Webmaster tools (https://www.google.com/webmasters/)
[...]
I'm having a hard time figuring out from that page what exactly
"Google Webmaster tools" is, and under what license it's
distributed. Looks
Hi all!
Here are my notes from the ironic (and a bit of nova) room in Denver.
The same content in a nicely rendered form is on my blog:
http://dtantsur.github.io/posts/ironic-ptg-denver-2017-1.html
http://dtantsur.github.io/posts/ironic-ptg-denver-2017-2.html
Here goes the raw rst-formatted
On Thu, Oct 5, 2017 at 8:50 AM, Kendall Nelson wrote:
[...]
> If you are interested in reserving a spot, just reply directly to me and I
> will put your project on the list. Please let me know if you want one and
> also include the names and emails anyone that will be
I wish to submit my candidacy for election to the OpenStack Technical
Committee. I have never been elected to the Technical Committee before
but, I have never believed that being elected is a requirement to
participate in the deliberations. I have therefore been a frequent
participant and a
Hey just a follow up on this ...
FYI ... it does appear that when UEFI booting a VM, a per-instance copy of the
OVMF_VARS.fd is indeed created.
See below:
root 97276 1 0 Oct05 ?00:01:41 /usr/libexec/qemu-kvm -c
0x0001 -n 4 --proc-type=secondary
Welcome to our regular release countdown email. Hopefully things will settle
down and I'll start getting these out a little earlier.
Development Focus
-
We are just one week away from the first Queens milestone already. Time flies.
Team focus should be on spec approval and
Update 37 is struggling to contain itself, too much code associated
with placement!
# Most Important^wRecent
Discussion last night uncovered some disagreement and confusion over
the content of the Selection object that will be used to send
alternate destination hosts when doing builds. The
I've tried to upgrade my testing environment to ocata but i have the
same issue...
does anybody has an idea?
regards
Kim
Am Freitag, den 29.09.2017, 09:32 +0200 schrieb Kim-Norman Sahm:
> Hi,
>
> i'm currently testing the integration of designate and i found the
> dns integration on neutron:
Team,
Please consider my candidacy for Queens. I just realized how time flies, reading
my previous two self nominations [1][2]. As a TC we have made significant
strides in the last cycle[3] and my contributions have been around how we can
do better working with adjacent communities and getting
On 5.10.2017 22:40, Alex Schultz wrote:
Hey folks,
So I wandered across the policy spec[0] for how we should be handling
unbranched repository reviews and I would like to start a broader
discussion around this topic. We've seen it several times over the
recent history where a change in oooqe
Dear all,
as discussed during the PTG, starting in the Queens cycle we will have a
bug czar.
chandakumar has graciously put his name forward for the role, and he'll be
QA bug czar for the Queens cycle.
Thank you!
The bug czar ensures that all bugs to OpenStack projects under the QA
umbrella are
Folks,
as there have been multiple questions about Inspector that I couldn't
answer due to my PTG absence, I've decided to make it up to You and
organise a virtual inspector-focused PTG call (over some BlueJeans or TBD).
The other Inspector Cores gracefully agreed to. I've selected the times all
Dear all,
Staring next week the QA team will start running office hours be-weekly
(every send week) on Thursdays at 9:00 UTC.
Office hours will happen in the #openstack-qa channel, and we'll use
meetbot there to record info, action and generate dedicated logs.
Several core developers from the QA
On 10/06/2017 04:07 AM, Andreas Scheuring wrote:
> Hi,
> yesterday the nova s390x (zkvm) CI got the permission to vote +1/-1 on
> nova again [3]. Technically it was just an addition the the gerri group
> [1]. Now Jenkins is showing up behind the “Verified” field in the review
> with its +1/-1.
Hi!
This is the weekly summary of Technical Committee initiatives. You can
find the full list of all open topics (updated twice a week) at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
If you are working on something (or plan to work on something) that is
not on the tracker, feel
On Tue, 3 Oct 2017 at 18:15 Doug Hellmann wrote:
> Excerpts from Jesse Pretorius's message of 2017-10-03 15:57:17 +:
> > On 10/3/17, 3:01 PM, "Doug Hellmann" wrote:
> >
> > >> Given that this topic has gone through several cycles of discussion
>
On Thu, Oct 5, 2017 at 11:37 PM, Mike Perez wrote:
> On 15:27 Oct 05, Mike Perez wrote:
> > On 02:59 Oct 05, Puneet Jain wrote:
> > > Hello all,
> > >
> > > I am a graduate student and have intermediate knowledge and huge in
> cloud
> > > computing. I am looking for a project
Hi,
yesterday the nova s390x (zkvm) CI got the permission to vote +1/-1 on nova
again [3]. Technically it was just an addition the the gerri group [1]. Now
Jenkins is showing up behind the “Verified” field in the review with its +1/-1.
However it’s not yet showing up in the long table
Just a short reminder that rst puts stuff in blockquotes when you're not
careful with the spacing. Example:
* item 1
* item 2
That's in blockquotes because of the 1 blank at the beginning. The
TripleO docs are full with them, which looks a bit ugly, to be frank.
This change removes all
A long time ago, a few Canonical employees (Scott Moser was one of them,
forget who else was doing it, maybe Dave Walker and/or Dustin Kirkland)
worked out a scheme for general usage that doesn't require extra plumbing:
* Client generates a small SSH host key locally and pushes it into
user
Thanks!
> On 6. Oct 2017, at 04:25, Ian Wienand wrote:
>
> On 10/06/2017 02:19 AM, Andreas Scheuring wrote:
>> seems like there is some confusing information about the DIB
>> meetings in the wiki [1]. The meeting is alternating between 15:00
>> and 20:00 UTC. But whenever
49 matches
Mail list logo