Ok - yeah, I'm not sure what the history behind that is either...
I'm mainly curious if that's something we can/should keep or if we are
opposed to dropping 'os' and 'api' from the convention (e.g.
load-balancer:loadbalancer:post as opposed to
os_load-balancer_api:loadbalancer:post) and just
Ok, Thank you very much for your work.
Adam Harwell 于2018年9月15日周六 上午8:26写道：
> It's high priority for me as well, so we should be able to get something
> done very soon, I think. Look for something early next week maybe?
>
> Thanks,
> --Adam
>
> On Thu, Sep 13, 2018, 21:18 Jeff Yang wrote:
Hi,
Based upon the discussion we had at the TC session in the afternoon, I'm
starting to draft a patch to add long term goal mechanism into governance.
It is by no means a complete solution at the moment (still have not thought
through the execution method yet to make sure the outcome), but feel
It's high priority for me as well, so we should be able to get something
done very soon, I think. Look for something early next week maybe?
Thanks,
--Adam
On Thu, Sep 13, 2018, 21:18 Jeff Yang wrote:
> Thanks:
> I found the correlative patch in neutron-lbaas:
>
>
>
> For the candidates who are running for tc seats, please reply to this
> email to indicate if you are open to use certain social media app in
> certain region (like Wechat in China, Line in Japan, etc.), in order to
> reach out to the OpenStack developers in that region and help them to
>
tl;dr: I'm proposing a new parameter to the server stop (and suspend?)
APIs to control if nova shelve offloads the server.
Long form: This came up during the public cloud WG session this week
based on a couple of feature requests [1][2]. When a user stops/suspends
a server, the hypervisor
Hey all,
This is just a heads up that I'll be off-site in Boston for work next
week, so I won't be available on IRC (but I will be replying
asynchronously to IRC messages and emails when I can).
Gibi will be running the nova meeting on Thursday Sep 20 at 1400 UTC.
I'm going to work on the
The Idea has been raising around (from me or from Matt's ML), so I would
like to give people more update on this (in terms of what I have been
raising, what people have been feedbacks, and what init idea I can collect
or I have as actions.
*Why are we doing this?*
The basic concept for this
On Fri, Sep 14, 2018 at 4:22 PM, Jim Rollenhagen
wrote:
> On Thu, Sep 13, 2018 at 9:46 PM, Mathieu Gagné wrote:
>>
>> On Thu, Sep 13, 2018 at 10:14 PM, Doug Hellmann
>> wrote:
>> > Excerpts from Mathieu Gagné's message of 2018-09-13 20:09:12 -0400:
>> >> On Thu, Sep 13, 2018 at 7:41 PM, Doug
On 2018-09-14 13:52:50 -0600 (-0600), Zhipeng Huang wrote:
> This is a joint question from mnaser and me :)
>
> For the candidates who are running for tc seats, please reply to
> this email to indicate if you are open to use certain social media
> app in certain region (like Wechat in China, Line
On Thu, Sep 13, 2018 at 9:46 PM, Mathieu Gagné wrote:
> On Thu, Sep 13, 2018 at 10:14 PM, Doug Hellmann
> wrote:
> > Excerpts from Mathieu Gagné's message of 2018-09-13 20:09:12 -0400:
> >> On Thu, Sep 13, 2018 at 7:41 PM, Doug Hellmann
> wrote:
> >> > Excerpts from Mathieu Gagné's message of
I don't know for sure, but I assume it is short for "OpenStack" and
prefixing OpenStack policies vs. third party plugin policies for
documentation purposes.
I am guilty of borrowing this from existing code examples[0].
[0]
This is a joint question from mnaser and me :)
For the candidates who are running for tc seats, please reply to this email
to indicate if you are open to use certain social media app in certain
region (like Wechat in China, Line in Japan, etc.), in order to reach out
to the OpenStack developers
Hi all,
Follow up the diversity discussion we had in the tc session this morning
[0], I've proposed a resolution on facilitating technical community in
large to engage in global reachout for OpenStack more efficiently.
Your feedbacks are welcomed. Whether this should be a new resolution or not
Hello!
Here are the photos we took this week of various teams :)
https://www.dropbox.com/sh/2pmvfkstudih2wf/AAAGg7c0bYZcWQwKDOKiSwR7a?dl=0
Enjoy!
-the Kendalls (diablo_rojo & wendallkaters)
__
OpenStack Development Mailing
On 3/28/2018 4:35 PM, Jay Pipes wrote:
On 03/28/2018 03:35 PM, Matt Riedemann wrote:
On 3/27/2018 10:37 AM, Jay Pipes wrote:
If we want to actually fix the issue once and for all, we need to
make availability zones a real thing that has a permanent identifier
(UUID) and store that permanent
On 2018-09-11 16:53:05 + (+), Jeremy Stanley wrote:
> On 2018-08-01 08:40:51 -0700 (-0700), James E. Blair wrote:
> > Monty Taylor writes:
> > > On 08/01/2018 12:45 AM, Ian Wienand wrote:
> > > > I'd suggest to start, people with an interest in a channel can
> > > > request +r from an IRC
On Fri, Sep 14, 2018 at 10:20 AM, Elõd Illés wrote:
> Hi,
>
> just a comment: Ocata release is not EOL [1][2] rather in Extended
> Maintenance. Do you really want to EOL TripleO stable/ocata?
>
Yes unless there are any objections. We've already been keeping this
branch alive on life support but
Hi,
just a comment: Ocata release is not EOL [1][2] rather in Extended
Maintenance. Do you really want to EOL TripleO stable/ocata?
[1] https://releases.openstack.org/
[2]
https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html
Cheers,
Előd
On 2018-09-14 09:20,
On 09/14/2018 09:01 AM, Alex Schultz wrote:
> On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar wrote:
>> Hello,
>>
>> As Ocata release is already EOL on 27-08-2018 [1].
>> In TripleO, we are running Ocata jobs in TripleO CI and in promotion
>> pipelines.
>> Can we drop it all the jobs related to
On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar wrote:
> Hello,
>
> As Ocata release is already EOL on 27-08-2018 [1].
> In TripleO, we are running Ocata jobs in TripleO CI and in promotion
> pipelines.
> Can we drop it all the jobs related to Ocata or do we need to keep some jobs
> to support
On Thu, Sep 13, 2018 at 5:46 PM Michael Johnson wrote:
> In Octavia I selected[0] "os_load-balancer_api:loadbalancer:post"
> which maps to the "os--api::" format.
>
Thanks for explaining the justification, Michael.
I'm curious if anyone has context on the "os-" part of the format? I've
seen
Folks,
Sorry for the top post - Those of you that are still at PTG, please feel
free to drop in to the Clear Creek room today.
Thanks,
Dims
On Thu, Sep 13, 2018 at 2:44 PM Jeremy Stanley wrote:
> On 2018-09-12 17:50:30 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > Again, I'm not saying TC
Le jeu. 13 sept. 2018 à 19:29, Naichuan Sun a
écrit :
> Hi, Sylvain,
>
>
>
> Thank you very much for the information. It is pity that I can’t attend
> the meeting.
>
> I have a concern about reshaper in multi-type vgpu support.
>
> In the old vgpu support, we only have one vgpu inventory in root
?Shyam,
Our policy, decided long ago, is that we would work with third party components
(such as plugins) for nova, cinder, neutron, horizon, etc that were proprietary
as long as the code that merges into Kolla specifically is ASL2.
What is your plugin for? if its for nova, cinder, neutron,
Hello,
As Ocata release is already EOL on 27-08-2018 [1].
In TripleO, we are running Ocata jobs in TripleO CI and in promotion pipelines.
Can we drop it all the jobs related to Ocata or do we need to keep some jobs
to support upgrades in CI?
Links:
[1.] https://releases.openstack.org/
Thanks,
Hi all,
We have planned to have our one-day virtual PTG meetup for Stein on below
schedule.
Please find the meeting details:
Schedule: 21st September, 7:00UTC to 11:00UTC
Meeting Channel: https://bluejeans.com/553456496
Etherpad link: https://etherpad.openstack.org/p/Tacker-PTG-Stein
Hi All,
As Stable is no longer a project, I'm no longer a PTL so I don't
really need to do this but ...
I'm going on vacation for 3'ish weeks. I do plan on checking my email
from time-to-time but really if anything comes up that needs urgent
attention you'll need to ping stable-maint-core.
28 matches
Mail list logo
