Hi all,
I'm late in sending this announement, but I'm glad to see several projects
have already requested EOL releases to make it trivial and obvious where to
apply the tag.
I'm proposing to EOL all projects that meet one or more of the following
criteria:
- The project is openstack-dev/devst
> On 2017. Apr 12., at 3:18, Monty Taylor wrote:
>
> On 04/10/2017 04:41 PM, Chris Dent wrote:
>> On Mon, 10 Apr 2017, Matt Riedemann wrote:
>>
>>> This might also tie back in with what cdent was mentioning, and if the
>>> flurry of conversation during a TC meeting throws people off, maybe
>>>
What about the TLS-Everywhere job? (ovb-fakeha-caserver) it's currently
running on the periodic queue.
Are there plans to work on that one? or will it be left running with the
classic script? If it can be taken into account, I can help out with it if
I can pair work with someone that knows the ovb
Hi all,
Proposed topics for the next congress irc meeting are tracked in this
etherpad: https://etherpad.openstack.org/p/congress-meeting-topics
Feel free to add additional topics and/or comment on existing ones. Thanks!
_
Hi, all
just another point to think about transition of periodic jobs:
firstly, we need featureset files for them,
secondly, when we combined ha and nonha job, it should be also one job in
periodic jobs, which contains now ha, nonha, updates,
because of all above, I think we will still need 2 jobs
>
>> Reliability is the key for them. But for the services and
>> applications that are built on top of this base? I'd like to see
>> allowing them a much more open approach: let them develop in whatever
>> language they like, release when they feel the timing is right, and
>> define their own CI
Hi All,
> So my question is the following: if elected, how much time do you think
> you'll be able to dedicate to Technical Committee affairs (reviewing
> proposed changes and pushing your own) ?
As a member of the OpenStack Foundation staff I have 100% of my time dedicated
to the community let
On 4/1/2017 6:07 PM, Kevin Bringard (kevinbri) wrote:
I agree with Mr. Pipes. I’ve not used that API ever and I’ve no recollection of
anyone asking about it nor am I aware of anyone who actually uses it. I vote to
deprecate.
Thanks for the feedback Kevin.
Here is the spec:
https://review.o
Just a heads-up (while it was mentioned during the TripleO weekly meeting):
We managed to release TripleO pike-1 early this week. This is really
awesome to see the progress we have made and that we continue to do on
the release side. We are continuously improving ourselves and I think
we can be pr
On Wed, Apr 12, 2017 at 02:54:30AM +, joehuang wrote:
> Hello,
>
> I heard the one platform vision in OpenStack now and then: One platform for
> virtual machines, containers and bare metal.
>
> I also learned that there are some groups working on making Kubernets being
> able to manage virt
Hi blazar team,
Tempest gate job is now activated by the patch[1], but now it's always
fails because of syntax error in the tempest job. I'm sorry to brake
reviews.
I'm also pushing the patch[2] to fix the problem. If you have time,
please take a look for the patch.
1. https://review.op
Hello,
I heard the one platform vision in OpenStack now and then: One platform for
virtual machines, containers and bare metal.
I also learned that there are some groups working on making Kubernets being
able to manage virtual machines. Except running containers in virtual machine,
there is al
Hi,
I think (a) is also good from TaaS dashboard.
Regards,
Kaz
From: Akihiro Motoki
Subject: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we
like to have horizon dashboard for neutron stadium projects?
Date: Tue, 11 Apr 2017 00:09:10 +0900
> Hi neutrinos (and horizoners),
On Wed, Apr 12, 2017 at 3:24 AM, Matt Riedemann wrote:
> On 4/11/2017 4:29 AM, Ghanshyam Mann wrote:
>>
>> Hi All,
>>
>> There is tempest tests for compute baremetal GET nodes tests[1]. This
>> tests involve ironic and nova. Ironic to create baremetal nodes and
>> then GET nodes using nova APIs.
>
Hey neutrinos,
It is the time. We need to show something to others. That's why, it's
called [1] Milestone.
I've prepared release [2] for all neutron deliverables. This time,
thanks to synchronized release schedule, and gathering most of
networking projects under neutron umbrella, we have pretty hug
On Tue, Apr 04, 2017 at 01:02:59PM -0400, Paul Belanger wrote:
> Greetings,
>
> Recently we've been running into some issues keeping our EPEL mirror properly
> sync'd. We are working to fix this, however we'd also like to do the
> following:
>
> Stop enabling EPEL mirror by default
> https:/
I'm reading through mgagne's spec to support attached volume size
extension callbacks in Nova [1] and the question that comes up is what
happens when the backend compute does not support this, either because
it's too old (Ocata) or the virt driver does not support the event?
The spec is target
On Apr 10, 2017 1:02 PM, "John Garbutt" wrote:
On 10 April 2017 at 11:31, .
With ironic I thought everything is "passed through" by default,
because there is no virtualization in the way. (I am possibly
incorrectly assuming no BIOS tricks to turn off or re-assign PCI
devices dynamically.)
It'
On 11 April 2017 at 11:08, Russell Bryant wrote:
>
>
> On Mon, Apr 10, 2017 at 4:49 PM, Martinx - ジェームズ <
> thiagocmarti...@gmail.com> wrote:
>
>>
>>
>> On 8 April 2017 at 00:37, Martinx - ジェームズ
>> wrote:
>>
>>> Guys,
>>>
>>> I manage to deploy Ocata on Ubuntu 16.04 with OVN for the first time
On Apr 11, 2017, at 12:48 PM, Jay Pipes wrote:
>> The IaaS parts
>> (and yes, I know that just which parts these are is a whole debate in
>> itself) should be rock-solid, slow-moving, and, well, boring.
>
> A fine idea. Unfortunately, what the majority of end users keep asking for is
> yet mor
On 04/11/2017 02:00 PM, Giulio Fidente wrote:
On Tue, 2017-04-11 at 16:50 +0200, Jan Provaznik wrote:
On Mon, Apr 10, 2017 at 6:55 PM, Ben Nemec
wrote:
On 04/10/2017 03:22 AM, Jan Provaznik wrote:
Well, on second thought it might be possible to make the Storage
network
only routable within o
On Tue, Apr 11, 2017 at 1:21 PM, Matt Riedemann wrote:
> On 4/11/2017 2:52 AM, Alex Xu wrote:
>
>> We talked about remove the quota-class API for multiple times
>> (http://lists.openstack.org/pipermail/openstack-dev/2016-July/099218.html
>> )
>>
>> I guess we can deprecate the entire quota-class
On Tue, 2017-04-11 at 16:50 +0200, Jan Provaznik wrote:
> On Mon, Apr 10, 2017 at 6:55 PM, Ben Nemec
> wrote:
> > On 04/10/2017 03:22 AM, Jan Provaznik wrote:
> > Well, on second thought it might be possible to make the Storage
> > network
> > only routable within overcloud Neutron by adding a bri
On 4/11/2017 4:29 AM, Ghanshyam Mann wrote:
Hi All,
There is tempest tests for compute baremetal GET nodes tests[1]. This
tests involve ironic and nova. Ironic to create baremetal nodes and
then GET nodes using nova APIs.
Nova only provides GET APIs for baremetal nodes which are already
deprecat
On 4/11/2017 2:52 AM, Alex Xu wrote:
We talked about remove the quota-class API for multiple times
(http://lists.openstack.org/pipermail/openstack-dev/2016-July/099218.html)
I guess we can deprecate the entire quota-class API directly.
I had a spec proposed to deprecate the os-quota-class-set
On 04/10/2017 04:41 PM, Chris Dent wrote:
On Mon, 10 Apr 2017, Matt Riedemann wrote:
This might also tie back in with what cdent was mentioning, and if the
flurry of conversation during a TC meeting throws people off, maybe
the minutes should be digested after the meeting in the mailing list.
I
On 04/10/2017 02:26 PM, Ed Leafe wrote:
On Apr 10, 2017, at 4:16 AM, Thierry Carrez
wrote:
If there was ONE thing, one initiative, one change you will
actively push in the six months between this election round and the
next, what would it be ?
Just one? If I had to choose, I would like to see
Are there any implications for the end user experience by going to different
repos (such as requiring dedicated menu items)?
Tim
From: "Sridar Kandaswamy (skandasw)"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, 11 April 2017 at 17:01
To: "OpenStack D
Hi Jay, Dmitry,
>I strongly challenge the assertion made here that inspection is only
useful in scheduling contexts.
Ok i agree that scheduling is not the only purpose of inspection but it is
one of the main aspect of inspection.
>There are users who simply want to know about their hardware, and
Akihiro,
Option (a) would have my vote.
- Louis
-Original Message-
From: Akihiro Motoki [mailto:amot...@gmail.com]
Sent: Monday, April 10, 2017 8:09 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we
like to have ho
On 04/11/2017 05:28 PM, Jay Faulkner wrote:
On Apr 11, 2017, at 12:54 AM, Nisha Agarwal wrote:
Hi John,
With ironic I thought everything is "passed through" by default,
because there is no virtualization in the way. (I am possibly
incorrectly assuming no BIOS tricks to turn off or re-assign
> On Apr 11, 2017, at 12:54 AM, Nisha Agarwal
> wrote:
>
> Hi John,
>
> >With ironic I thought everything is "passed through" by default,
> >because there is no virtualization in the way. (I am possibly
> >incorrectly assuming no BIOS tricks to turn off or re-assign PCI
> >devices dynamically.
On Mon, Apr 10, 2017 at 4:49 PM, Martinx - ジェームズ
wrote:
>
>
> On 8 April 2017 at 00:37, Martinx - ジェームズ
> wrote:
>
>> Guys,
>>
>> I manage to deploy Ocata on Ubuntu 16.04 with OVN for the first time
>> ever, today!
>>
>> It looks very, very good... OVN L3 Router is working, OVN DHCP
>> working
Hi All:
>From and FWaaS perspective - we also think (a) would be ideal.
Thanks
Sridar
From: Kevin Benton mailto:ke...@benton.pub>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, April 10, 2017 at 4:20 PM
To: OpenStack List
mailto:openstack-dev@lists.opensta
i think that we the format proposed on
https://review.openstack.org/#/c/454691/1
we would be ok
giving my +1 there
cheers
2017-04-11 10:45 GMT-03:00 Monty Taylor :
> Sweet - so - each repo should have release and component (if I understand
> those right) - is there additional info that we shoul
On Mon, Apr 10, 2017 at 6:55 PM, Ben Nemec wrote:
> I'm not really an expert on composable roles so I'll leave that to someone
> else, but see my thoughts inline on the networking aspect.
>
> On 04/10/2017 03:22 AM, Jan Provaznik wrote:
>>
>> 2) define a new VIP (for IP failover) and 2 networks fo
GREAT SUCCESS !!!
2017-04-11 10:51 GMT-03:00 Melvin Hillsman :
> Hey everyone,
>
> Just a reminder that the meetups team will be meeting today 4/11 at 1500UTC
>
> Agenda: https://etherpad.openstack.org/p/ops-meetups-team
>
>
> https://www.worldtimebuddy.com/?qm=1&lid=100,1816670,
> 2147714,469906
Hi!
Just as a follow up to my email yesterday, tests are now passing. Many thanks
Rob for helping me out with this on IRC!
If anyone else comes across this error message developing panels in horizon, my
solution was that I wasn’t making the correct modules available with just
beforeEach(module
Hey everyone,
Just a reminder that the meetups team will be meeting today 4/11 at 1500UTC
Agenda: https://etherpad.openstack.org/p/ops-meetups-team
https://www.worldtimebuddy.com/?qm=1&lid=100,1816670,2147714,4699066&h=100&date=2017-4-11&sln=15-16
https://www.worldtimebuddy.com/?qm=1&lid=100,26
Sweet - so - each repo should have release and component (if I
understand those right) - is there additional info that we should include?
Like - in the multi-file approach, it's a set of directories with files
of the form:
release/component.json -> contains versions[]
And the single file, it
Hi Norbert,
my biggest concern with the workflow you've shown is that in the meantime
it would be possible to create undeletable stacks / stacks that leave
resources behind after being deleted. As the biggest challenge is usually
in updates (if it is not UpdateReplace) I'd suggest implementing cre
Changing the size to a float creates rounding issues, and means
changes to the db, the api definition, and changes to every single
client and client library out there, for very little gain.
On 10 April 2017 at 04:41, jun zhong wrote:
> I agree with you extend might be one way to solve the problem
Monty thx so much
basically we have following structure
Release ->Component ->Version
so i think that we could consume this pretty easily, only caveat is that we
still to add from our side, Release and Component data, but i guess that is
doable
thx u so much !!! i will take a look to bot
Hi everyone,
Me and two of my colleagues are working on adding Neutron Trunk support
to Heat. One of us working on the resource implementation, one on the
unit tests and one on the functional tests. But all of these looks like
a big chunk of work so I'm wondering how can we divide them into sm
Hey all,
We've got the project-navigator-data repo created and there are two
proposals up for what the content should look like.
Could TC folks please add openstack/project-navigator-data to your watch
lists, and go review:
https://review.openstack.org/#/c/454688
https://review.openstack.or
Hi all!
We agreed to proceed with planning of our virtual meetup in the end of April /
beginning of May. Please vote for days and time slots when you're available:
https://doodle.com/poll/p6rydi6stinqzfrz. Please do it by FRIDAY, Apr 14. (sorry
for short notice, but I'm on PTO next week. I'm a
Thanks for raising this point!
On Tue, Apr 11, 2017 at 5:34 AM Ghanshyam Mann
wrote:
> Hi All,
>
> There is tempest tests for compute baremetal GET nodes tests[1]. This
> tests involve ironic and nova. Ironic to create baremetal nodes and
> then GET nodes using nova APIs.
> Nova only provides GE
Hi All,
There is tempest tests for compute baremetal GET nodes tests[1]. This
tests involve ironic and nova. Ironic to create baremetal nodes and
then GET nodes using nova APIs.
Nova only provides GET APIs for baremetal nodes which are already
deprecated [2].
As nova baremetal APIs are deprecated
Thierry Carrez wrote:
> So my question is the following: if elected, how much time do you think
> you'll be able to dedicate to Technical Committee affairs (reviewing
> proposed changes and pushing your own) ?
Keep track of the technical direction of OpenStack is an important part
of my role at th
Matt Riedemann wrote:
> Thanks Chris. This reminded me of something I wanted to ask about, to
> all TC members, or those running for a seat.
>
> Lots of projects have alternating meeting times to accommodate
> contributors in different time zones, especially Europe and Asia.
>
> The weekly TC mee
Dear List,
I am trying to do SLO upload of large object. The naming convention of the
segmentswill include a timestamp. The scenario I tried is described below:1.
Created container 2. Used CURL command to upload segments.3. Uploaded the
manifest file. Result looks some what like this
# swift l
Hi John,
>With ironic I thought everything is "passed through" by default,
>because there is no virtualization in the way. (I am possibly
>incorrectly assuming no BIOS tricks to turn off or re-assign PCI
>devices dynamically.)
Yes with ironic everything is passed through by default.
>So I am ass
We talked about remove the quota-class API for multiple times (
http://lists.openstack.org/pipermail/openstack-dev/2016-July/099218.html)
I guess we can deprecate the entire quota-class API directly.
2017-04-07 18:19 GMT+08:00 Chen CH Ji :
> Version 2.35 removed most deprecated output like float
On 10/04/17 13:52 -0500, Matt Riedemann wrote:
Lots of projects have alternating meeting times to accommodate
contributors in different time zones, especially Europe and Asia.
The weekly TC meeting, however, does not.
I have to assume this has come up before and if so, why hasn't the TC
adopt
54 matches
Mail list logo
