Dane,
I’ve heard Yolanda has done good work on making disk image builder build fedora
atomic properly consistently. This may work better than the current image
building tools available with atomic if you need to roll your own. Might try
pinging her on irc for advice if you get jammed up
ACTION: we should make sure workarounds are advertised better
ACTION: we should have some document about "when cells"?
This is a difficult question to answer because "it depends." It's akin
to asking "how many nova-api/nova-conductor processes should I run?"
Well, what hardware is being used,
Hi All,
I think the current meeting times i.e. 08:00 UTC and 15:00 UTC on
alternate weeks are working well for us. Though 15:00 UTC is little late
for me, I propose we continue with the same for this cycle.
With the geographical spread of the team, it's difficult to arrive at a
time that suits
On Wed, Sep 28, 2016 at 11:10:52AM +0800, xiangxinyong wrote:
> Hi guys,
>
>
> When i setup OpenStack by devstack,
> I have got an error message "nova-api did not start".
>
>
> [Call Trace]
> ./stack.sh:1242:start_nova_api
> /home/edison/devstack/lib/nova:802:die
> [ERROR]
Hi guys,
When i setup OpenStack by devstack,
I have got an error message "nova-api did not start".
[Call Trace]
./stack.sh:1242:start_nova_api
/home/edison/devstack/lib/nova:802:die
[ERROR] /home/edison/devstack/lib/nova:802 nova-api did not start
Error on exit
World dumping... see
Hi Armando,
Thank you for your cheking.
networking-ofagent are ready for retirement in the Newton.
But ryu-team still will maintain stable/liberty and stable/mitaka
release.
So we will keep repository till EOL of mitaka.
Also zuul and requirement bot will not run for master branch of ofagent
On 2016/09/28 10:18, Armando M. wrote:
Hi Neutrinos,
I wanted to double check with you the state of these following projects:
- networking-ofagent
I think that ofagent is ready for retirement. I have seen the
declaration as "OFAgent is decomposed and deprecated in the Mitaka
cycle." in
Hi,
We have weekly Nova API meeting today. The meeting is being held Wednesday
UTC1300 and irc channel is #openstack-meeting-4.
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Please feel free to add items to the agenda.
Thanks
Time is running out to nominate for an award!!
https://openstackfoundation.formstack.com/forms/community_contributor_award_nomination_form
On 21/09/16 02:43, Kendall Nelson wrote:
Hello all,
I’m pleased to announce the next round of community contributor awards!
Similar to the Austin Summit,
Hello everyone,
The release candidate for networking-ovn for the end of the Newton
cycle is available! You can find the RC2 source code tarball at:
https://tarballs.openstack.org/networking-ovn/networking-ovn-1.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
On 16-09-27 09:18 PM, Armando M. wrote:
Hi Neutrinos,
I wanted to double check with you the state of these following projects:
- networking-ofagent
- python-neutron-pd-driver
It's my understanding that they are ready for retirement or thereabouts.
Please confirm, and I'll kick off the
Hi Neutrinos,
I wanted to double check with you the state of these following projects:
- networking-ofagent
- python-neutron-pd-driver
It's my understanding that they are ready for retirement or thereabouts.
Please confirm, and I'll kick off the countdown sequence [1].
Cheers,
Armando
[1]
On Wed, Sep 28, 2016 at 6:21 AM, Jiahao Liang <
jiahao.li...@oneconvergence.com> wrote:
>
>
> On Tue, Sep 27, 2016 at 5:35 PM, Rabi Mishra wrote:
>
>> On Wed, Sep 28, 2016 at 1:01 AM, Zane Bitter wrote:
>>
>>> On 27/09/16 15:11, Jiahao Liang wrote:
>>>
On Tue, Sep 27, 2016 at 5:35 PM, Rabi Mishra wrote:
> On Wed, Sep 28, 2016 at 1:01 AM, Zane Bitter wrote:
>
>> On 27/09/16 15:11, Jiahao Liang wrote:
>>
>>> Hello all,
>>>
>>> I am trying to use heat to launch lb resources with Octavia as backend.
>>>
Hi folks,
The summit is less than a month away and it's the time of the year where we
need to plan for design summit sessions.
This time we are going for 10 fishbowl sessions, plus Friday [0].
We will break down sessions in three separate tracks as we did the last two
summits. Each track will
On 9/20/2016 11:16 AM, Daniel P. Berrange wrote:
NB the bug was non-deterministic and rare, even in the gate, so the
real test is whether it gets past the gate 20 times in a row :-)
Regards,
Daniel
It was about a 25% job failure rate in the gate when we disabled live
snapshots with the
On Wed, Sep 28, 2016 at 1:01 AM, Zane Bitter wrote:
> On 27/09/16 15:11, Jiahao Liang wrote:
>
>> Hello all,
>>
>> I am trying to use heat to launch lb resources with Octavia as backend.
>> The template I used is
>> from
Hi All,
We've 3 Fish-bowl and 6 WR slots available this summit for the design
sessions. We're collecting the session ideas on this[1] etherpad. Please
add any other topic/ideas, that you would like to be included.
We'll discuss these in this/next week team meetings to prioritize them.
[1]
On 9/20/2016 9:22 AM, Dan Smith wrote:
I'll also see about writing up some docs about the expected workflow
here. Presumably that needs to go in some fancy docs and not into the
devref, right? Can anyone point me to where that should go?
--Dan
I'd think something in here:
Hi Timur,
Thanks for picking this up, that is interesting for me.
2016-09-22 5:58 GMT-07:00 Timur Nurlygayanov :
>
> we have an idea to create the test suite with destructive/HA and advanced
> end-user scenarios for the OpenStack clusters. This test suite will
On Tue, Sep 27, 2016, at 05:54 PM, Sean Dague wrote:
> On 09/27/2016 05:45 PM, Andrew Laski wrote:
> >
> >
> > On Tue, Sep 27, 2016, at 04:43 PM, Matthew Treinish wrote:
> >
>
> I definitely can see the value in having machine parsable log stats in
> our
> artifacts, but
On Fri, Sep 23, 2016, at 05:04 PM, Clark Boylan wrote:
> Earlier this month there was a thread on replacing stud in devstack for
> the tls-proxy service [0]. Over the last week or so a bunch of work has
> happened around this so I figured I would send an update.
>
> Tempest passes against
On 09/27/2016 05:45 PM, Andrew Laski wrote:
>
>
> On Tue, Sep 27, 2016, at 04:43 PM, Matthew Treinish wrote:
>
I definitely can see the value in having machine parsable log stats in
our
artifacts, but I'm not sure where project specific pieces would come
from. But,
This is my candidacy for a position on the OpenStack Technical
Committee.
https://review.openstack.org/378054
For those who don't know me, it has been 4 years that I have been
consistently working on OpenStack to make deployments production-ready:
- Puppet OpenStack core contributor, and ex-PTL
Hello everyone,
A new release candidate for neutron for the end of the Newton cycle
is available! You can find the source code tarballs at:
https://tarballs.openstack.org/neutron-dynamic-routing/neutron-dynamic-routing-9.0.0.0rc2.tar.gz
On Tue, Sep 27, 2016, at 04:43 PM, Matthew Treinish wrote:
> > >
> > > I definitely can see the value in having machine parsable log stats in
> > > our
> > > artifacts, but I'm not sure where project specific pieces would come
> > > from. But,
> > > given that hypothetical I would say as long
Sergey Belous wrote on 09/26/2016 07:36:17 AM:
> From: Sergey Belous
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 09/26/2016 07:38 AM
> Subject: [openstack-dev] [OSC] Bug, spec, BP
On Tue, Sep 27, 2016 at 03:32:17PM -0400, Andrew Laski wrote:
>
>
> On Tue, Sep 27, 2016, at 02:40 PM, Matthew Treinish wrote:
> > On Tue, Sep 27, 2016 at 01:03:35PM -0400, Andrew Laski wrote:
> > >
> > >
> > > On Tue, Sep 27, 2016, at 12:39 PM, Matthew Treinish wrote:
> > > > On Tue, Sep 27,
Hi Matt,
Introduction of using subnetpools in devstack [1] is causing issues like
'Connection to proxy timed out. ' in our setup. We are working on it and
will update ML soon. Thanks for pinging.
[1] https://review.openstack.org/#/c/356026/
>-Original Message-
>From: Matt
Kevin Benton wrote:
There is no side effect other than log noise and a delayed reload? I
don't see why a revert would be appropriate.
I looked at the logs and the issue seems to be that the process isn't
tracked correctly the first time it starts.
grep for the
Hi,
We have a Design Summit next month, and now we are trying to get ideas
for QA sessions.
There is an etherpad for ideas and it is good if writing your ideas on that:
https://etherpad.openstack.org/p/ocata-qa-summit-topics
After getting ideas, we will arrange them into available slots for QA
On Tue, Sep 27, 2016, at 02:40 PM, Matthew Treinish wrote:
> On Tue, Sep 27, 2016 at 01:03:35PM -0400, Andrew Laski wrote:
> >
> >
> > On Tue, Sep 27, 2016, at 12:39 PM, Matthew Treinish wrote:
> > > On Tue, Sep 27, 2016 at 11:36:07AM -0400, Andrew Laski wrote:
> > > > Hello all,
> > > >
> >
On 27/09/16 15:11, Jiahao Liang wrote:
Hello all,
I am trying to use heat to launch lb resources with Octavia as backend.
The template I used is
from
https://github.com/openstack/heat-templates/blob/master/hot/lbaasv2/lb_group.yaml.
Following are a few observations:
1. Even though Listener
By coincidence I've just written up a spec [1] that proposes an
admittedly very generic mechanism to solve this problem. I was coming
at it from the perspective of keeping the relative order of PCI device
addresses constant across evacuations. In that spec, I propose letting
the virt driver store
We are chuffed to announce the release of:
django_openstack_auth 2.4.1: Django authentication backend for use
with OpenStack Identity
This release is part of the newton stable release series.
With source available at:
http://git.openstack.org/cgit/openstack/django_openstack_auth/
With
I'd like to throw my hat into the ring for the TC. I've been involved
in OpenStack since 2012. We may have interacted when working on Nova,
Devstack, Grenade, debugging the gate, or other areas of the broader
OpenStack project.
Upgrades are one of the things I'm passionate about in
OpenStack. The
Hello all,
I am trying to use heat to launch lb resources with Octavia as backend. The
template I used is from
https://github.com/openstack/heat-templates/blob/master/hot/lbaasv2/lb_group.yaml
.
Following are a few observations:
1. Even though Listener was created with ERROR status, heat will
There is no side effect other than log noise and a delayed reload? I don't
see why a revert would be appropriate.
I looked at the logs and the issue seems to be that the process isn't
tracked correctly the first time it starts.
grep for the following:
ea141299-ce07-4ff7-9a03-7a1b7a75a371',
On 2016-09-27 11:45:14 -0700 (-0700), Travis McPeak wrote:
> There is a private security bug about it right now too. No, not all XML
> libraries are immune now.
https://launchpad.net/bugs/1625402 which I've just now declassified.
--
Jeremy Stanley
signature.asc
Description: Digital signature
I am announcing my candidacy for a position on the OpenStack Technical
Committee.
I have served on the Technical Committee for the last three years and
as PTL of the Release Management team for the Mitaka and Newton
cycles. I will be PTL for the Release Management team again for
Ocata.
Before
There is a private security bug about it right now too. No, not all XML
libraries are immune now.
On Tue, Sep 27, 2016 at 11:36 AM, Dave Walker wrote:
>
>
> On 27 September 2016 at 19:19, Sean Dague wrote:
>
>> On 09/27/2016 01:24 PM, Travis McPeak wrote:
>>
On Tue, Sep 27, 2016 at 01:03:35PM -0400, Andrew Laski wrote:
>
>
> On Tue, Sep 27, 2016, at 12:39 PM, Matthew Treinish wrote:
> > On Tue, Sep 27, 2016 at 11:36:07AM -0400, Andrew Laski wrote:
> > > Hello all,
> > >
> > > Recently I noticed that people would look at logs from a Zuul née
> > >
Ack, and thanks for the summary Ihar,
I will have a look on it tomorrow morning, please update this thread
with any progress.
On Tue, Sep 27, 2016 at 8:22 PM, Ihar Hrachyshka wrote:
> Hi all,
>
> so we started getting ‘Address already in use’ when trying to start dnsmasq
On 27 September 2016 at 11:29, Miguel Angel Ajo Pelayo
wrote:
> Ack, and thanks for the summary Ihar,
>
> I will have a look on it tomorrow morning, please update this thread
> with any progress.
>
>
>
> On Tue, Sep 27, 2016 at 8:22 PM, Ihar Hrachyshka
On 27 September 2016 at 19:19, Sean Dague wrote:
> On 09/27/2016 01:24 PM, Travis McPeak wrote:
> > There are several attacks (https://pypi.python.org/pypi/defusedxml#id3)
> > that can be performed when XML is parsed from untrusted input.
> > DefusedXML offers safe alternatives
I wish I did not need to write such emails late in the evening. Added
missing [neutron] tag.
Ihar Hrachyshka wrote:
Hi all,
so we started getting ‘Address already in use’ when trying to start
dnsmasq after the previous instance of the process is killed with kill
On 2016-09-27 19:12:36 +0100 (+0100), Daniel P. Berrange wrote:
[...]
> There is one extra complication in that alot of upstream CI jobs currently
> use Trusty VMs, although things are increasingly migrating to Xenial based
> images. Clearly if we drop Trusty support in Nova for Pike, then the CI
Hi all,
so we started getting ‘Address already in use’ when trying to start dnsmasq
after the previous instance of the process is killed with kill -9. Armando
spotted it today in logs for: https://review.openstack.org/#/c/377626/ but
as per logstash it seems like an error we saw before
On 09/27/2016 01:24 PM, Travis McPeak wrote:
> There are several attacks (https://pypi.python.org/pypi/defusedxml#id3)
> that can be performed when XML is parsed from untrusted input.
> DefusedXML offers safe alternatives to XML parsing libraries but is not
> currently part of global
In the Newton release we increased the min required libvirt to 1.2.1
and min QEMU to 1.5.3 We did not set any "next" versions for Ocata,
so Ocata will not be changing.
I think we should consider increasing min versions in the Pike release
though to let us cut out more back-compatibility code for
On Tue, Sep 27, 2016 at 2:05 PM, Assaf Muller wrote:
>
>
> On Tue, Sep 27, 2016 at 12:18 PM, Timur Nurlygayanov <
> tnurlygaya...@mirantis.com> wrote:
>
>> Hi milan,
>>
>> we have measured the test coverage for OpenStack components with
>> coverage.py tool [1]. It is very easy
On Tue, Sep 27, 2016 at 12:18 PM, Timur Nurlygayanov <
tnurlygaya...@mirantis.com> wrote:
> Hi milan,
>
> we have measured the test coverage for OpenStack components with
> coverage.py tool [1]. It is very easy tool and it allows measure the
> coverage by lines of code and etc. (several metrics
We already debated this in https://review.openstack.org/#/c/311857/
All the lessons learned from DefusedXML was already incorporated in
various python packages. You can test this theory out by using the
test xml(s) in DefusedXML if you wish.
Also note that there have been no changes to the
On 2016-09-27 10:24:02 -0700 (-0700), Travis McPeak wrote:
> There are several attacks (https://pypi.python.org/pypi/defusedxml#id3)
> that can be performed when XML is parsed from untrusted input. DefusedXML
> offers safe alternatives to XML parsing libraries but is not currently part
> of
ChangBo Guo wrote:
Hi ALL,
We will release Newton in Oct 6, and we have been working hard to fix
bugs and prepare the release. I think it's good time to
review good ideas. As we discussed in the Oslo weekly meeting [1], we
would like to proposal an event of Oslo specs review weeks(Sept27 - Oct
There are several attacks (https://pypi.python.org/pypi/defusedxml#id3)
that can be performed when XML is parsed from untrusted input. DefusedXML
offers safe alternatives to XML parsing libraries but is not currently part
of global requirements.
I propose adding DefusedXML to global requirements
On Tue, Sep 27, 2016 at 10:40:34AM -0600, Chris Friesen wrote:
> On 09/27/2016 10:17 AM, Matthew Booth wrote:
>
> > I think we should be able to create a domain, but once created we should
> > never
> > redefine a domain. We can do adding and removing devices dynamically using
> > libvirt's
On Tue, Sep 27, 2016, at 12:39 PM, Matthew Treinish wrote:
> On Tue, Sep 27, 2016 at 11:36:07AM -0400, Andrew Laski wrote:
> > Hello all,
> >
> > Recently I noticed that people would look at logs from a Zuul née
> > Jenkins CI run and comment something like "there seem to be more
> > warnings
Sorry for the top post - fyi, i've submitted a review for OpenStackSalt
https://review.openstack.org/#/c/377906/
-- Dims
On Mon, Sep 26, 2016 at 2:58 AM, Flavio Percoco wrote:
> On 22/09/16 17:15 -0400, Anita Kuno wrote:
>>
>> On 16-09-21 01:11 PM, Doug Hellmann wrote:
>>>
On 09/27/2016 10:17 AM, Matthew Booth wrote:
I think we should be able to create a domain, but once created we should never
redefine a domain. We can do adding and removing devices dynamically using
libvirt's apis, secure in the knowledge that libvirt will persist this for us.
When we upgrade
On Tue, Sep 27, 2016 at 11:36:07AM -0400, Andrew Laski wrote:
> Hello all,
>
> Recently I noticed that people would look at logs from a Zuul née
> Jenkins CI run and comment something like "there seem to be more
> warnings in here than usual." And so I thought it might be nice to
> quantify that
On Tue, Sep 27, 2016 at 05:17:29PM +0100, Matthew Booth wrote:
> Currently the libvirt driver (mostly) considers the nova db canonical. That
> is, we can throw away libvirt's domain XML at any time and recreate it from
> Nova. Anywhere that doesn't assume this is a bug, because whatever
>
On 09/27/2016 06:19 AM, John Davidge wrote:
>> Hmm, I disagree about that. I think that experience actually *has* shown
>> us that there is a single set of rules that can/should be applied to all
>> projects that wish to be called an OpenStack project.
>
> We may have to agree to disagree here.
I would like to announce my candidacy for a position on the Technical
Committee.
I work for Dell EMC with over a decade (quite a bit over, but I don't want to
think about that) in storage and software development. I have been involved in
OpenStack since the Icehouse cycle and have served as the
Hi milan,
we have measured the test coverage for OpenStack components with
coverage.py tool [1]. It is very easy tool and it allows measure the
coverage by lines of code and etc. (several metrics are available).
[1] https://coverage.readthedocs.io/en/coverage-4.2/
On Tue, Sep 27, 2016 at 1:06
Currently the libvirt driver (mostly) considers the nova db canonical. That
is, we can throw away libvirt's domain XML at any time and recreate it from
Nova. Anywhere that doesn't assume this is a bug, because whatever
direction we choose we don't need 2 different sources of truth. The
thinking
On Tue, Sep 27, 2016, at 11:59 AM, Ian Cordasco wrote:
> On Tue, Sep 27, 2016 at 10:36 AM, Andrew Laski wrote:
> > Hello all,
> >
> > Recently I noticed that people would look at logs from a Zuul née
> > Jenkins CI run and comment something like "there seem to be more
> >
On 27/09/16 06:19, John Davidge wrote:
Having Stackforge as a separate Github organization and set of
>repositories was a maintenance nightmare due to the awkwardness of
>renaming projects when they "moved into OpenStack".
There's no reason that this would need a separate github structure, just
On 09/27/2016 11:36 AM, Andrew Laski wrote:
> Hello all,
>
> Recently I noticed that people would look at logs from a Zuul née
> Jenkins CI run and comment something like "there seem to be more
> warnings in here than usual." And so I thought it might be nice to
> quantify that sort of thing so
Excerpts from milanisko k's message of 2016-09-27 12:30:09 +:
> Hello Stackers!
>
> The ironic inspector project keeps track of introspection finished_at time
> stamps.
> We're just discussing how to reasonably query time ranges over the API[1]
> to serve matching introspection statuses to
On Tue, Sep 27, 2016 at 10:36 AM, Andrew Laski wrote:
> Hello all,
>
> Recently I noticed that people would look at logs from a Zuul née
> Jenkins CI run and comment something like "there seem to be more
> warnings in here than usual." And so I thought it might be nice to
>
Hello all,
Recently I noticed that people would look at logs from a Zuul née
Jenkins CI run and comment something like "there seem to be more
warnings in here than usual." And so I thought it might be nice to
quantify that sort of thing so we didn't have to rely on gut feelings.
So I threw
Thanks for all guys.
So we have reached an agreement now. We will mark the fedora deprecated now
( Newton ), and plan to drop it in O cycle.
On Fri, Sep 23, 2016 at 6:05 PM, Haïkel wrote:
> 2016-09-21 16:34 GMT+02:00 Steven Dake (stdake) :
> >
> >
>
Voting time is up.
Then Debian will stay in Kolla and anyone is welcome to toke over the
maintain work.
But if Debian is out of maintaining in next cycle, we will try to remove it
again. :)
On Fri, Sep 23, 2016 at 3:53 PM, Christian Berendt <
bere...@betacloud-solutions.de> wrote:
> > On 22 Sep
On 27/09/2016 01:36, Ryan Petrello wrote:
> Apologies for the trouble this caused. As Dave mentioned, this change
> warranted a new major version of pecan, and I missed it. I've reverted the
> offending commit and re-released a new version of pecan (1.2.1) to PyPI:
>
>
On 2016-09-27 16:54, Ruby Loo wrote:
> Hi,
>
>
>
> Thanks to the huge efforts put in by Mathieu Mitchell (mat128) and Jay
> Faulkner (JayF), we've moved ironic's install guide from the developer
> documentation to the official openstack site [1]. Isn't it a beauty? :D
>
>
>
> Please update
On 2016-09-27 17:02, Andreas Jaeger wrote:
> On 2016-09-27 16:54, Ruby Loo wrote:
>> Hi,
>>
>>
>>
>> Thanks to the huge efforts put in by Mathieu Mitchell (mat128) and Jay
>> Faulkner (JayF), we've moved ironic's install guide from the developer
>> documentation to the official openstack site
Hello everyone,
A new release candidate for heat for the end of the Newton cycle
is available! You can find the source code tarball at:
https://tarballs.openstack.org/heat/heat-7.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this candidate
Hi,
Thanks to the huge efforts put in by Mathieu Mitchell (mat128) and Jay Faulkner
(JayF), we've moved ironic's install guide from the developer documentation to
the official openstack site [1]. Isn't it a beauty? :D
Please update your bookmarks to point to the new location, and help us
Also, as part of this reminder. If you add a proposal to the etherpad, please
put your name/NIC next to it so we know who added it/is going to lead it.
Bruno, I added your name to #12 & 13 :)
Thanks,
--ruby
From: Jim Rollenhagen
Reply-To: "OpenStack Development
Hello Jim and ironicers,
Jim Rollenhagen said on Tue, Sep 27, 2016 at 09:47:03AM -0400:
Just a reminder to add your summit session proposals to our etherpad:
https://etherpad.openstack.org/p/ironic-ocata-summit
I have added the 2 topics I've been working on since some time and for
which I'd
On Tue, Sep 27, 2016 at 9:57 AM, Loo, Ruby wrote:
> Hi Yuriy,
>
>
>
> Thanks for bringing this up. I'm good with your list, with the exception of
> driver_info and instance_info. I'm on the fence with these two. If we assume
> that any secrets will be bleep'd out (configdrives
On Tue, Sep 27, 2016 at 9:49 AM, Joshua Hesketh
wrote:
> Hey Emilien,
>
> Sorry I missed those, I didn't take my script back far enough. I've tidied
> up as far back as diablo :-).
yeah, old stuff :)
> I could only see the fix_image_version branch on puppet-tempest,
Hello Everyone,
On behalf of the Heat Translator team, I am pleased to announce the 0.6.0
PyPI release of heat-translator which can be downloaded from
https://pypi.python.org/pypi/heat-translator
This release includes several enhancements:
Python 3.5 support
Auto deployment of translated
Hey Emilien,
Sorry I missed those, I didn't take my script back far enough. I've tidied
up as far back as diablo :-).
I could only see the fix_image_version branch on puppet-tempest, but I've
tidied that up anyway.
Let me know if I'm missed anything else.
Cheers,
Josh
On Tue, Sep 27, 2016 at
On 27/09/2016 08:42, Kelam, Koteswara Rao wrote:
> Jenkins for openstack/designate is failing for latest patches. Py27,
> py34 and py35 are failing continuously.
>
> gate-designate-python27-db-ubuntu-xenial
>
Hi Yuriy,
Thanks for bringing this up. I'm good with your list, with the exception of
driver_info and instance_info. I'm on the fence with these two. If we assume
that any secrets will be bleep'd out (configdrives won't be there), is there
other information there that might be useful? I'm not
After some IRC discussion
(http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2016-09-27.log.html#t2016-09-27T13:31:42),
I'm +1 to this base payload, too.
I vote we do this, and we can always update later if operators chime
in with additional use cases that should be
Hey friends,
Just a reminder to add your summit session proposals to our etherpad:
https://etherpad.openstack.org/p/ironic-ocata-summit
Unless I hear of an earlier deadline from summit planning folks, I'd like
to have these locked in by October 14 (as I'm out the week before summit).
This means
I'm seeing a pretty high failure rate with some of the Intel NFV CI jobs
today, the pattern looks like a pypi mirror issue getting packages to
setup tempest:
http://intel-openstack-ci-logs.ovh/94/375894/2/check/tempest-dsvm-intel-nfv-xenial/a0bffb3/logs/devstacklog.txt.gz
2016-09-27
Hello everyone,
The release candidate(s) for Sahara for the end of the Newton cycle
are available! You can find the RC2 source code tarballs at:
https://tarballs.openstack.org/sahara/sahara-5.0.0.0rc2.tar.gz
https://tarballs.openstack.org/sahara-dashboard/sahara-dashboard-5.0.0.0rc2.tar.gz
Hi all,
Sorry for the late mail, but I have to cancel the meeting today.
Thanks,
Moshe Levi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hello Stackers!
The ironic inspector project keeps track of introspection finished_at time
stamps.
We're just discussing how to reasonably query time ranges over the API[1]
to serve matching introspection statuses to the user.
Wikipedia[2] mentions the ISO8601 time interval specification (and
Hi Josh,
Thanks a lot for your help !
I've noticed some of them still have stale branches, example:
https://github.com/openstack/puppet-keystone/branches with essex and folsom
or https://github.com/openstack/puppet-nova/branches with diablo!
(yeah very old :-))
also puppet-cinder, puppet-glance,
Hi Emilien,
I've removed all of the old branches on the specified repos and created
tags in their place. Let me know if there are any problems.
Cheers,
Josh
On Mon, Sep 26, 2016 at 3:51 PM, Emilien Macchi wrote:
> Greatings Infra,
>
> This is an official request to remove
Hi,
there is a discussion starting in comment on
https://review.openstack.org/#/c/321865/
I agree with Ruby Loo proposal about a base node payload.
Currently we have these node's fields exposed via API (in alphabetical
order):
"chassis_uuid", "clean_step", "console_enabled", "created_at",
Thanks for the questions Jay, answers inline.
On 9/26/16, 8:39 PM, Jay Pipes wrote:
>Who decides what is integral to OpenStack and what merely "enhances" it,
>though? The TC? The DefCore group? The Board of Directors? One might say
>all three groups have a say in defining what "is OpenStack", no?
Hi,
On Tue, Sep 27, 2016 at 11:43 AM, milanisko k wrote:
> Dear Stackers,
> I'd like to gather some overview on the $Sub: is there some infrastructure
> in place to gather such stats? Are there any groups interested in it? Any
> plans to establish such infrastructure?
>
I am
Hi, all
with Dereks help we set up OVB dev environment on rh1/rh2 clouds, which
allow developers to run their patches in real CI environment and debug
their issues there. In case you have a problem with your patch on CI and
locally it works - you can reproduce and debug it on this environment.
Dear Stackers,
I'd like to gather some overview on the $Sub: is there some infrastructure
in place to gather such stats? Are there any groups interested in it? Any
plans to establish such infrastructure?
Thanks!
milan
PS: I used to maintain a tool[1] that once collect multi-node integration
test
1 - 100 of 107 matches
Mail list logo