On Tue, Nov 21 2017, 李田清 wrote:
> right now, ceilometer notification agent can send samples by udp
> publisher..
> But gnocchi can only accept by rest api. Is there a way to use udp to
> accept notification agent's samples that sending by udp?
I'd suggest tracking this here since an
Hi everyone!
I believe all distributions are running unit tests of packages, either
at build time, or later on (for example in autopkgtest). In Debian, it's
done mostly at build time. There it's forbidden to access internet, and
on purpose, Debian buildd servers wont provide internet access when
b
Hi, all
Multiple cells (Nova-Cells-v2) is supported in Pike release.
It is necessary to confirm that existing APIs work appropriately in the
multiple cells environment.
We will post multiple patches, so I created BluePrint[1] to make it easier to
keep track of those patches.
Please check the con
Hi everyone,
Let me welcome Édouard Thuleau (doude) as a new core on
networking-bgpvpn!
Édouard has been following and contributing from the early days, in
particular on the framework and on the API client. He knows the project
well and has done multiple reviews. He also knows about the questions
Hi All,
Networking-odl is not sending bandwidth_limit_rules & dscp_marking_rules along
with the updated qos policy name when I have updated the qos-policy-name from
Vamsi to Krish.
Expected behavior is to have the updated policy name along with
bandwidth_limit_rules & dscp_marking_rules same a
Kubernetes on the overcloud
===
The work on this front started with 2[0][1] patches that some of you might have
seen and then evolved into using the config download mechanism to execute these
tasks as part of the undercloud tasks[2][3] (Thanks a bunch, Jiri, for your work
Hi,
we're currently exploring ways to deploy multiple Ceph clusters in the
overcloud.
Given Ceph is now managed by a ceph-ansible playbook, we can "easily"
deploy multiple Ceph clusters running multiple times the playbook with
different parameters and inventory.
The initial idea to make this co
Hi,
Tomorrow I will attend the bug smash in Wuhan so I will not be able to
chair the weekly meeting. We will resume the meeting next week.
BR
Zhiyuan
--
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questio
Very cool, thanks Sean!
-amrith
On Mon, Nov 20, 2017 at 12:18 PM, Sean McGinnis
wrote:
> Hello PTL's, release liaisons, and all those interested.
>
> The changes on our side to support a release cycle highlights page have
> been
> completed, and things have settled a bit from the Summit activ
Hi all,
I have been trying to deploy Kolla on a virtualized environment with Centos
Docker images using the
stable/pike branch
Deployment fails with -- https://hastebin.com/gubilijecu.vbs
Inventory fail -- https://hastebin.com/etosipegez.pl
extra log -- https://hastebin.com/yudafudegu.go
Docker
Having heard only positive responses, I'm happy to reinstate Nikhil
Komawar as a glance core, with all the rights and privileges
pertaining thereto.
Welcome back, Nikhil!
cheers,
brian
On Thu, Nov 16, 2017 at 8:20 PM, Abhishek Kekane wrote:
> Big +2
> Glad you are back :)
>
> Abhishek
>
> On 17
On 2017-11-21 09:28:20 +0100 (+0100), Thomas Goirand wrote:
[...]
> The only way that I see going forward, is having internet access
> removed from unit tests in the gate, or probably just the above
> variables set.
[...]
Historically, our projects hadn't done a great job of relegating
their "unit
Dear all,
A gentle reminder for our tomorrow meeting at 15:00 UTC
A draft agenda is available at line 1484, you are very welcome to add any item.
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017
Best regards,
ad_rien_
___
Hi,
Here is the status update / focus settings mail for w47
Bugs
[Undecided] https://bugs.launchpad.net/nova/+bug/1535254 illustration
of 'notify_on_state_change' are different from implementation
As the behavior is unchanged in the last 5 years a patch is proposed to
update the documentati
Hi all,
thank you all for your replies.
AFAIU the consensus is leaning towards option 1, so I've proposed a patch
to governance that adds networking-generic-switch under ironic:
https://review.openstack.org/#/c/521894/
(not actually sure how that works / being decided on from TC side, but will
Hi Goutham,
Please share your nova-compute and libvirt logs from
/var/lib/docker/volumes/kolla_logs/_data/nova.
What kolla release is deployed?
If using nested virtualization, is correctly configured to use qemu instead
of kvm?
Regards
2017-11-21 15:37 GMT+01:00 Goutham Pratapa :
> Hi all,
>
>
Hey,
We have been integrating OpenStack Ironic into our own OpenStack Distribution.
Thanks to help from the mailing list, we’ve been able to successfully ‘nova
boot’ a bare metal instance on an ironic node using the pxe_ipmitool drivers.
Thanks again for all the help.
A QUESTION about some futur
This is issue I hit recently. There are staging drivers [1] and there is
virtualbmc [2] to emulate ipmi for virtual machines. I ended up using
pxe_wol_isci driver.
[1] - http://ironic-staging-drivers.readthedocs.io/en/latest/README.html
[2] - https://pypi.python.org/pypi/virtualbmc/1.2.0
On Tue,
Hi Greg,
How do these smaller devices allow you to manage their power state?
Typically you have a side-computer (AKA bare-metal controller) which is
always up so you can talk to it (via IPMI/Redfish/SNMP/ssh) to manage
power state of its big brother.
The pxe_ssh driver is about libvirt VMs simu
> -Original Message-
> From: Jeremy Stanley [mailto:[email protected]]
> Sent: Tuesday, November 21, 2017 3:05 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] Removing internet access from unit test
> gates
>
> On 2017-11-21 09:28:2
On 11/21/2017 04:04 PM, Jeremy Stanley wrote:
> Removing network access from the machines running these jobs won't
> work, of course, because our job scheduling and execution service
> needs to reach them over the Internet to start jobs, monitor
> progress and collect results.
Right.
> As you not
Hello QA Team,
In many of the tempest tests there is a statement[1] that overrides the
tempest.conf value for use_dynamic_credentials.
In the event of an immutable user source, these test cases[2] and the one's
inherited by them will fail.
Can we remove or reduce the scope of the overrides? You
I'm actually pushing this out to a broader list and modifying the title as
well. We need to try and get all operators viewing this (even if they are
also devels, deployers, sigs.)
Feel free to reply to me about spamming lists, but I think we need lots of
eyes on this.
On Tue, Nov 21, 2017 at 9:
Is there a template for this? I wouldn't want to have 12 different
formatting styles for the page (Yes, I'm looking at Amrith and the
blinking red text. grin)
Michael
On Tue, Nov 21, 2017 at 6:28 AM, Amrith Kumar wrote:
> Very cool, thanks Sean!
>
>
> -amrith
>
>
> On Mon, Nov 20, 2017 at 12:1
On Tue, Nov 21, 2017 at 4:47 PM MCCASLAND, TREVOR wrote:
> Hello QA Team,
>
> In many of the tempest tests there is a statement[1] that overrides the
> tempest.conf value for use_dynamic_credentials.
> In the event of an immutable user source, these test cases[2] and the
> one's inherited by them
+1
Congrats, Jun! Thanks for all the hard work. Keep it up.
- Original message -From: Xing Yang To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] 回复： [manila] Nominating Zhong Jun (zhongjun) for ManilacoreDate: Sun, Nov 19, 2017 6:59 PM
:On Tue, Nov 21, 2017 at 9:15 AM, Chris Morgan wrote:
:> The big topic of debate, however, was whether subsequent meetups should be
:> co-located with OpenStack PTG. This is a question for the wider OpenStack
:> operators community.
For people who attend both I thnik this would be a big win, if
Jon,
I think the Foundation staff were very very wary of extending the PTG or
doing dual sites simultaneously due to not saving a thing logistically.
Yes, it would conceivably save travel for folks that need to go to two
separate events (as would the other colo options on the table) but not
saving
Excerpts from Michael Johnson's message of 2017-11-21 08:52:17 -0800:
> Is there a template for this? I wouldn't want to have 12 different
> formatting styles for the page (Yes, I'm looking at Amrith and the
> blinking red text. grin)
>
> Michael
I think just keep it simple and it will be fine (
On Tue, Nov 21, 2017 at 08:52:17AM -0800, Michael Johnson wrote:
> Is there a template for this? I wouldn't want to have 12 different
> formatting styles for the page (Yes, I'm looking at Amrith and the
> blinking red text. grin)
>
> Michael
>
>
There is not a set template for now. Since this
Excerpts from Doug Hellmann's message of 2017-11-20 11:32:53 -0500:
> As we agreed in the new documentation retention policy spec [1], I need
> to restore the stable/mitaka branch for the openstack/openstack-manuals
> repository and then trigger a build of the mitaka version of the guides.
> I have
On Tue, Nov 21, 2017 at 10:10:00AM -0700, David Medberry wrote:
:Jon,
:
:I think the Foundation staff were very very wary of extending the PTG or
:doing dual sites simultaneously due to not saving a thing logistically.
:Yes, it would conceivably save travel for folks that need to go to two
:separat
Aah that’s an interesting idea, using the wake-on-lan technology to solve the
problem of how to power on the server without IPMI.
So how does the solution solve the power-off and reset functions ?
i.e.
· is the deployment image (with IPA) deployed on the ironic node as
soon as it is enr
On 21 Nov 2017 01:19, "Alex Schultz" wrote:
On Thu, Nov 16, 2017 at 12:01 AM, Juan Antonio Osorio
wrote:
> Hello folks!
>
> A few months ago Dan Sneddon and me worked in an ansible role that would
> enable IPSEC for the overcloud [1]. Currently, one would run it as an
extra
> step after the over
Good question about how the smaller devices have their power managed.
Actually stepping back a bit,
i am now thinking that perhaps i am thinking of a USE CASE that is NOT the
typical IRONIC USE CASE.
i.e.
I think the ‘typical’ IRONIC USE CASE is that there are a pool of physical
servers
that ar
Your configuration lost all of its indentation, which makes it extremely
difficult to read. Can you try sending it a different way, maybe
paste.openstack.org?
On 11/16/2017 02:43 AM, Samuel Monderer wrote:
Hi,
I managed to deploy a compute node with ovs-dpdk using two NICs. The
first for th
On Tue, Nov 21, 2017 at 04:41:13PM +, Mooney, Sean K wrote:
>
>
> > -Original Message-
> > From: Jeremy Stanley [mailto:[email protected]]
> > Sent: Tuesday, November 21, 2017 3:05 PM
> > To: OpenStack Development Mailing List (not for usage questions)
> >
> > Subject: Re: [openstack
Dear all
As you might know, `OS::Heat::HARestarter` been deprecate for really long
time. It never really restarts servers (only recreate them), and the code
(and logic) looks really old.
Would like to reach out all users to see if this resource still uses by
anyone.
If it's fine for all, I like to
On 2017-11-21 13:34:57 -0500 (-0500), Paul Belanger wrote:
[...]
> I don't think we'd need to use security groups, we could just
> setup a local firewall ruleset to do this on the node if we
> wanted.
[...]
I considered suggesting that in my original reply, but then realized
that we still have ste
On 2017-11-21 17:46:14 +0100 (+0100), Thomas Goirand wrote:
[...]
> Doing this kind of a patch at first on a few project's tox.ini,
> absolutely! I might even start with Horizon and PBR (yes, there's a
> problem there as well... which I haven't reported yet). Though
> generalizing it to 300+ patche
On Tue, Nov 21, 2017 at 10:59 AM, Waines, Greg
wrote:
> i am now thinking that perhaps i am thinking of a USE CASE that is NOT the
> typical IRONIC USE CASE.
\o/
> i.e.
>
> I think the ‘typical’ IRONIC USE CASE is that there are a pool of physical
> servers
> that are available to run requested
http://paste.openstack.org/show/626557/
On Tue, Nov 21, 2017 at 8:22 PM Ben Nemec wrote:
> Your configuration lost all of its indentation, which makes it extremely
> difficult to read. Can you try sending it a different way, maybe
> paste.openstack.org?
>
> On 11/16/2017 02:43 AM, Samuel Monder
Thanks. Unfortunately I don't see anything obviously wrong with that,
but I'm not a DPDK expert either. Hopefully one of our networking gurus
can chime in and comment on whether this should work.
On 11/21/2017 02:01 PM, Samuel Monderer wrote:
http://paste.openstack.org/show/626557/
On Tue,
Jeremy Stanley writes:
> On 2017-11-21 17:46:14 +0100 (+0100), Thomas Goirand wrote:
> [...]
>> Doing this kind of a patch at first on a few project's tox.ini,
>> absolutely! I might even start with Horizon and PBR (yes, there's a
>> problem there as well... which I haven't reported yet). Though
Dear Neutron team,
Due to the Thanksgiving Holiday in the US, we will cancel our weekly
meeting on November 24th. We will resume normally on the 30th
Regards
__
OpenStack Development Mailing List (not for usage questions)
Uns
On 2017-11-21 13:11:36 -0800 (-0800), James E. Blair wrote:
[...]
> If something like this is desirable, I think tox.ini may be the best
> place for it, as it will cause local test runs to behave the same way as
> in Zuul.
This is a great point, any workarounds which need root privileges
(e.g., ad
Hi all,
I would like to announce the following change to the Zun core reviewers
team.
+ miaohb (miao-hongbao)
- Sheel Rana (ranasheel2000)
Miaohb has been consistently contributed to Zun for a few months. So far,
he has 60 commits in Zun, which ranked on top 3 in the commit metric. I
think his h
Hi,
Any chance the meeting this week to be moved on the Thursday instead?
Cheers,
Gilles
On 17/11/17 03:12, Ed Leafe wrote:
Greetings OpenStack community,
No meeting this week, as people are still straggling back after the Sydney
summit. There will also be no meeting next week, due to the U
+1 for them, includes the new voting schema.
Best regards,
Shu
> -Original Message-
> From: Hongbin Lu [mailto:[email protected]]
> Sent: Wednesday, November 22, 2017 8:16 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Cc: [email protected]
> Subject:
I'm using Openstack Ocata and trying Magnum.
I encountered a lot of problems but I been able to solved many of them.
Now I'm curious about some aspects of Magnum:
¿Do I need a newer version of Magnum to run K8S 1.7? ¿Or I just need to
create a custom fedora-atomic-27? What about RBAC?
¿Any one
On Wed, Nov 22, 2017 at 03:07:33AM +, [email protected] wrote:
> Build failed.
>
> - publish-openstack-javascript-tarball
> http://logs.openstack.org/e5/e5831f230bd29516dc202eb406270604f27e27f9/release/publish-openstack-javascript-tarball/9908482/
> : SUCCESS in 4m 58s
> - release-openstack
Thank you all for the support. I intend to help the Glance community
flourish, again.
cheers
On Tue, Nov 21, 2017 at 10:07 AM, Brian Rosmaita wrote:
> Having heard only positive responses, I'm happy to reinstate Nikhil
> Komawar as a glance core, with all the rights and privileges
> pertaining
On Wed, Nov 22, 2017 at 2:29 AM, Ben Nemec wrote:
> Thanks. Unfortunately I don't see anything obviously wrong with that, but
> I'm not a DPDK expert either. Hopefully one of our networking gurus can
> chime in and comment on whether this should work.
>
> On 11/21/2017 02:01 PM, Samuel Monderer
We had a similar kind of requirement to differentiate parameters
between overcloud compute nodes, like a cluster having DELL and HP
machines have different hardware layout, but DPDK requires the
specific CPU information of a hardware layout to function effectively.
We addressed it by using differ
Indeed, adding Jason in copy.
Do we actually need release-openstack-javascript job?
On Tue, Nov 21, 2017 at 8:27 PM, Tony Breeds wrote:
> On Wed, Nov 22, 2017 at 03:07:33AM +, [email protected] wrote:
>> Build failed.
>>
>> - publish-openstack-javascript-tarball
>> http://logs.openstack.or
Hi nova devs,
Just wanted to ask regarding request zero root disk for boot-from-volume
instances patches [2] [3].
When user boot instance using bootable volume and flavor having non-zero disk_gb
then in that case it considers flavor disk_gb which is incorrect the
calculation of host
disk space.
Hello,
I'm sorry for the late notice. I have moved the meeting one hour later. The new
meeting time is:
Wednesday, 1500 UTC
#openstack-meeting-3
See you there,
Witek
> -Original Message-
> From: Bedyk, Witold
> Sent: Mittwoch, 15. November 2017 17:16
> To: 'OpenStack Development Mai
57 matches
Mail list logo
