Hi Julia,
I don't mind to update the ironic spec [1]. Unfortunately, I wasn't in the PTG
but I had a sync meeting with Isuku.
As I see it there is 2 use-cases:
1. Running the neutron ovs agent in the smartnic
2. Running the neutron super ovs agent which manage the ovs running on the
smar
Dear networking Stackers,
During the recent PTG in Denver, we discussed measures to prevent patches
merged in the Neutron repo breaking Stadium and related networking projects
in general. We decided to implement the following:
1) For Stadium projects, we want to add non-voting jobs to the Neutron
Hi,
Yes, this also matches the recollection of the joint conversation in
Denver. Please look at the "Ironic x-project discussion - Smartnics"
section in
http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html
Regards
Miguel
On Thu, Sep 27, 2018 at 1:31 PM Julia Kreger
w
Nova, cinder and tempest run the nova-multiattach job in their check and
gate queues. The job was added in Queens and was a specific job because
we had to change the ubuntu cloud archive we used in Queens to get
multiattach working. Since Rocky, devstack defaults to a version of the
UCA that wo
On Sat, Sep 29, 2018 at 12:02 PM Ed Leafe wrote:
> On Sep 28, 2018, at 12:19 PM, Chris Dent wrote:
> > I don't think placement should be concerned about temporal aspects
> > of traits. If we can't write a web service that can handle setting
> > lots of traits every second of every day, we should
On Sep 28, 2018, at 12:19 PM, Chris Dent wrote:
>
> I don't think placement should be concerned about temporal aspects
> of traits. If we can't write a web service that can handle setting
> lots of traits every second of every day, we should go home. If
> clients of placement want to set weird tr
On Sep 29, 2018, at 10:40 AM, Jay Pipes wrote:
>
>> So here it is. Two of the top influencers in placement, one saying we
>> shouldn't overload traits, the other saying we shouldn't add a primitive
>> that would obviate the need for that. Historically, this kind of
>> disagreement seems to result
On 09/28/2018 04:36 PM, Eric Fried wrote:
So here it is. Two of the top influencers in placement, one saying we
shouldn't overload traits, the other saying we shouldn't add a primitive
that would obviate the need for that. Historically, this kind of
disagreement seems to result in an impasse: nei
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> == Things We Learned This Week ==
>>
>> When we updated the tox.ini settings for jobs like pep8 and release
>> notes early in the Rocky session we only touched some of the official
>> repositories. I'll be working on making a list of the ones we
Hi Training Team,
Based on the votes on the Doodle poll below we will have our ad-hoc meeting
__next Friday (October 5) 1600 UTC__.
Hangouts link for the call:
https://hangouts.google.com/call/BKnvu7e72uB_Z-QDHDF2AAEI
If you’re available for the Berlin training as mentor and haven’t signed up
On Fri, 28 Sep 2018 at 22:07, melanie witt wrote:
> On Fri, 28 Sep 2018 15:42:23 -0500, Eric Fried wrote:
> > On 09/28/2018 09:41 AM, Balázs Gibizer wrote:
> >>
> >>
> >> On Fri, Sep 28, 2018 at 3:25 PM, Eric Fried wrote:
> >>> It's time somebody said this.
> >>>
> >>> Every time we turn a corne
To add some context around what I suspect is the reason for the most recent
incarnation of this debate, many Ironic users have a requirement to be able
to influence the configuration of a server at deploy time, beyond the
existing supported mechanisms. The classic example is hardware RAID - the
abi
On 9/27/18 10:04 AM, Frode Nordahl wrote:
Hello docs team,
What would it take to re-generate the indices for Deployment Guides on
the published Queens [0] and Rocky [1] docs pages?
It seems that the charms project has missed the index for those releases
due to some issues which now has been
13 matches
Mail list logo
