I seem to recall list discussion on this quite a ways back. I think most of it
happened on the Docs ml, though. Maybe Juno/Kilo timeframe? If possible, it
would be good to search over the code bases for places it was called to see its
current footprint. I'm pretty sure it was the docs folks
I seem to recall list discussion on this quite a ways back. I think most of it
happened on the Docs ml, though. Maybe Juno/Kilo timeframe? If possible, it
would be good to search over the code bases for places it was called to see its
current footprint. I'm pretty sure it was the docs folks
Oh, very definitely +1000
--
Rochelle Grober Rochelle Grober
M: +1-6508889722(preferred)
E: rochelle.gro...@huawei.com<mailto:rochelle.gro...@huawei.com>
2012实验室-硅谷研究所技术规划及合作部
2012 Laboratories-Silicon Valley Technology Planning &
C
Oh, very definitely +1000
--
Rochelle Grober Rochelle Grober
M: +1-6508889722(preferred)
E: rochelle.gro...@huawei.com<mailto:rochelle.gro...@huawei.com>
2012实验室-硅谷研究所技术规划及合作部
2012 Laboratories-Silicon Valley Technology Planning &
C
Sounds like an important discussion to have with the operators in Denver.
Should put this on the schedule for the Ops meetup.
--Rocky
> -Original Message-
> From: Matt Riedemann [mailto:mriede...@gmail.com]
> Sent: Thursday, September 06, 2018 1:59 PM
> To: OpenStack Development Mailing
Sounds like an important discussion to have with the operators in Denver.
Should put this on the schedule for the Ops meetup.
--Rocky
> -Original Message-
> From: Matt Riedemann [mailto:mriede...@gmail.com]
> Sent: Thursday, September 06, 2018 1:59 PM
> To: OpenStack Development Mailing
Zane Bitter wrote:
> On 31/05/18 14:35, Julia Kreger wrote:
> > Back to the topic of nitpicking!
> >
> > I virtually sat down with Doug today and we hammered out the positive
> > aspects that we feel like are the things that we as a community want
> > to see as part of reviews coming out of this
minds for the discussion. And yes, this is a
discussion to see if we are interested, and only if there is interest, how to
move forward.
--Rocky
From: Lance Bragstad [mailto:lbrags...@gmail.com]
Sent: Friday, May 18, 2018 2:03 PM
To: Rochelle Grober <rochelle.gro...@huawei.com>; opensta
minds for the discussion. And yes, this is a
discussion to see if we are interested, and only if there is interest, how to
move forward.
--Rocky
From: Lance Bragstad [mailto:lbrags...@gmail.com]
Sent: Friday, May 18, 2018 2:03 PM
To: Rochelle Grober <rochelle.gro...@huawei.com>; opensta
Thierry Carrez [mailto:thie...@openstack.org]
>
> Graham Hayes wrote:
> > Any additional background on why we allowed LCOO to operate like this
> > would help a lot.
>
The group was started back when OPNFV was first getting involved with
OpenStack. Many of the members came from that
collection of those who are already doing the job without title.
Thanks and see you next week.
--rocky
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Rochelle Grober
Sr. Staff Architect, Open Source
Office Phone:408-330-5472
Email:rochelle.gro...@
Doug Hellmann wrote:
> I would like for us to collect some more data about what efforts teams are
> making with encouraging new contributors, and what seems to be working or
> not. In the past we've done pretty well at finding new techniques by
> experimenting within one team and then adapting the
It could be *really* useful if you could include the date (month/year would be
good enough)of the last significant patch (not including the reformat to
Openstackdocstheme). That could give folks a great stick in the mud for what
"past" is for the spec. It might even incent some to see if
Submission is no longer anonymous, but the results are not public, still. The
submitter decides whether the guideline results are public, but if they do,
only the guideline tests are made public. If the submitter does not actively
select public availability for the test results, all results
> -Original Message-
> From: Matt Riedemann [mailto:mriede...@gmail.com]
> Sent: Thursday, March 01, 2018 4:19 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [DriverLog] DriverLog future
>
> On 3/1/2018 10:44 AM, Ilya Shakhat wrote:
> >
> > For those who do
Armando,
You’ve been great for Neutron. It’s sad to see you have to cut back, but it’s
great to hear you aren’t totally leaving.
Thank you for all of your hard work. You’ve brought Neutron along quite
nicely. I’d also like to thank you for all of your help with the stadium
projects. Your
MISTAKE!!!
Ooops. I’m sorry. Please ignore.
--Rocky
From: Rochelle Grober
Sent: Monday, November 20, 2017 5:23 PM
To: Farhad Sunavala <farhad.sunav...@huawei.com>; Zhiqiang Yang
<zhiqiang.y...@huawei.com>
Cc: OpenStack Development Mailing List (not for usage questions)
&l
.
Thanks,
--Rocky
From: Farhad Sunavala
Sent: Monday, November 20, 2017 4:54 PM
To: Zhiqiang Yang <zhiqiang.y...@huawei.com>
Cc: Rochelle Grober <rochelle.gro...@huawei.com>
Subject: Help needed with Fusion SPhere
Hi Rocky,
Henry from SW lab wanted to know who has worked with Fusion Sp
First off, let me say I think this is a tremendous idea. And, it's perfect for
the SIG concept.
Next, see inline:
Thierry Carrez wrote:
> Andrea Frittoli wrote:
> > [...]
> > during the last summit in Sydney we discussed the possibility of
> > creating an OpenStack quality assurance special
First off, let me say I think this is a tremendous idea. And, it's perfect for
the SIG concept.
Next, see inline:
Thierry Carrez wrote:
> Andrea Frittoli wrote:
> > [...]
> > during the last summit in Sydney we discussed the possibility of
> > creating an OpenStack quality assurance special
> -Original Message-
> From: Erik McCormick [mailto:emccorm...@cirrusseven.com]
> Sent: Tuesday, November 14, 2017 4:25 PM
> To: Rochelle Grober <rochelle.gro...@huawei.com>
> Cc: OpenStack Development Mailing List (not for usage questions)
> <openstack-...@list
> -Original Message-
> From: Erik McCormick [mailto:emccorm...@cirrusseven.com]
> Sent: Tuesday, November 14, 2017 4:25 PM
> To: Rochelle Grober <rochelle.gro...@huawei.com>
> Cc: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@list
Folks,
This discussion and the people interested in it seem like a perfect application
of the SIG process. By turning LTS into a SIG, everyone can discuss the issues
on the SIG mailing list and the discussion shouldn't end up split. If it turns
into a project, great. If a solution is found
Folks,
This discussion and the people interested in it seem like a perfect application
of the SIG process. By turning LTS into a SIG, everyone can discuss the issues
on the SIG mailing list and the discussion shouldn't end up split. If it turns
into a project, great. If a solution is found
Clint Byrum wrote:
> Excerpts from Jonathan Proulx's message of 2017-09-26 16:01:26 -0400:
> > On Tue, Sep 26, 2017 at 12:16:30PM -0700, Clint Byrum wrote:
> >
> > :OpenStack is big. Big enough that a user will likely be fine with
> > learning :a new set of tools to manage it.
> >
> > New users in
Might I suggest a PTG activity such as an evening docathon?
Drinks and Docs
Everyone welcome to locate in some convenient location to review/test docs,
converse and plan for the next dev cycle with Docs folks. It might not be
doable at this late date for Pike, but I suspect there may be some
The meeting is an online video/voice/collaboration meeting. By clicking the
link: https://welink-meeting.zoom.us/j/317491860 you will go to a page that
will download the zoom client installation package. Install that, run it and
put the meeting ID in where asked. Zoom works all over the
And I'd just like to point out, when was the last time you tried to find info
contained in some etherpad on our etherpad server without having the etherpad's
exact name? Either searched for a specific etherpad or for info you knew was
somewhere on an etherpad somewhere on the
Thanks for the clarification. Yeah. No interop interaction to see here.
These are not the api's you are looking for;-)
I think Chris Dent's response about extending the gabbi based tests is great.
I'm a firm believer in never discouraging anyone from writing more tests,
especially when
> From: Matt
> On 6/21/2017 7:04 AM, Shewale, Bhagyashri wrote:
> > I would like to write functional tests to check the exact req/resp
> > for each placement API for all supported versions similar
> >
> > to what is already done for other APIs under
> >
OK. So, our naming is like branding. We are techies -- not good at marketing.
But, gee, the foundation has a marketing team. And they end up fielding a lot
of the confusing questions from companies not deeply entrenched in the
OpenStack Dev culture. Perhaps it would be worth explaining
In many ways, having the PWG at the PTG is a great idea. The only problem with
that is that the PWG and the InteropWG would overlap in the current way the PTG
is arranged. Having both at the same place is great for synergy, but having
them at the same times is not :( We actually have a
I wanted to make sure this got out to as much of the community as soon as
possible. This "new base service" will be part of Pike. This means that etcd
will be a requirement for Pike installations and beyond.
Most of you won't need to take any immediate actions, but knowing the plans for
your
From: Ildiko
> On 2017. May 23., at 15:43, Sean McGinnis
> wrote:
> >
> > On Mon, May 22, 2017 at 05:50:50PM -0500, Anne Gentle wrote:
> >> On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis
> >>
> >> wrote:
> >>
> >>>
> >>> [snip]
> >>>
> >>
> >> Hey
and multi cloud
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Rochelle Grober
Sr. Staff Architect, Open Source
Office Phone:408-330-5472
Email:rochelle.gro...@huawei.com
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用
From: Duncan Thomas
> On 18 May 2017 at 22:26, Rochelle Grober <rochelle.gro...@huawei.com>
> wrote:
> > If you're going to use --distance, then you should have specific values
> (standard definitions) rather than operator defined:
> > And for that matter, is there som
From: Matt Riedemann
> On 5/15/2017 2:28 PM, Edmund Rhudy (BLOOMBERG/ 120 PARK) wrote:
> > Hi all,
> >
> > I'd like to follow up on a few discussions that took place last week
> > in Boston, specifically in the Compute Instance/Volume Affinity for
> > HPC session
> >
I arrive Sunday afternoon and leave Friday morning, so you can bracket and
schedule your drink buying ;-)
My view of Rocky is that of a *solid* base to build on. One that withstands
the ravages of storms and squalls. So, I look forward to helping to reinforce
and expand the stability of
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Rochelle Grober
Sr. Staff Architect, Open Source
Office Phone:408-330-5472
Email:rochelle.gro...@huawei.com
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散
I know that some cyborg folks and nova folks are planning to be there. Now we
need to drive some ops folks.
Sent from HUAWEI AnyOffice
From:Blair Bethwaite
To:openstack-dev@lists.openstack.org,openstack-oper.
Date:2017-04-25 08:24:34
Subject:[openstack-dev] [scientific][nova][cyborg] Special
Matt Riedemann, Monday, April 10, 2017 1:41 PM
On 4/10/2017 2:55 PM, Dean Troyer wrote:
>
> The TC meetings are held in IRC and that may somewhat mitigate the
> issue for non-native English speakers, but I've had problems myself
> keeping up at times with the flurry of comments. In any case,
On April 14, 2017 1:23 PM Jay Pipes wrote:
On 04/12/2017 02:15 PM, Sean Dague wrote:
> On 04/12/2017 01:38 PM, Monty Taylor wrote:
>> On 04/12/2017 11:21 AM, Joshua Harlow wrote:
>>> Just a question, not meant as anything bad against shade,
>>>
>>> But would effort be better spent on
Welcome!
And, of course, writing tests that demonstrate some of those more difficult
open bugs would help make sure they don't resurface once fixed ;-) so, if you
can't get a handle yet on the intricacies of the the code that contains the
issue, you still might be able to demonstrate the
Sorry for top posting, but this is likely the best place...
I wanted to provide an update from the Ops midcycle about related topics around
this.
The operators here are in general agreement that translation is not needed, but
they are also very interested in the possibility of getting some of
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Rochelle Grober
Sr. Staff Architect, Open Source
Office Phone:408-330-5472
Email:rochelle.gro...@huawei.com
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本
Looks great to me.
--Rocky
From: Catherine Cuong Diep [mailto:cd...@us.ibm.com]
Sent: Monday, February 06, 2017 4:25 PM
To: OpenStack Dev Mailer
Subject: [openstack-dev] Refstack - final mascot
Hello RefStack team,
Please see RefStack mascot in Heidi's note
Well, uh, how about Jazz hands? Open, waving hands are pretty universally
friendly and it would look more like a dancing bear which brings the music
aspect bac a bit.
Sorry for butting in, but I couldn resist...
--Rocky
-Original Message-
From: Miles Gould [mailto:mgo...@redhat.com]
There was a driver thread about snapshot management test failures. It appears
there is a config option that changed for devstack from false to true, causing
the cinder drivers all sorts of issues. Here is the email that discusses the
change and its effects on cinder drivers:
YEES!
-Original Message-
From: Tom Fifield [mailto:t...@openstack.org]
Sent: Monday, January 16, 2017 3:48 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] PTG? / Was (Consistent Versioned Endpoints)
On 14/01/17 04:07, Joshua Harlow wrote:
>
> Sometimes I almost
Sorry for top posting, but exchange
Automation is our friend. Define the structure/naming of the release repo
patches such that when they merge, they auto generate the governance patch and
submit it. It gives you time to run a cycle and see how things work and what a
more elegant
a blog post on the OpenStack sore might be good. superuser? there are folks
reading this who can help
Sent from HUAWEI AnyOffice
From:Lance Bragstad
To:OpenStack Development Mailing List (not for usage
questions),openstack-operat...@lists.openstack.org,
Date:2016-11-03 08:11:20
Subject:Re:
a blog post on the OpenStack sore might be good. superuser? there are folks
reading this who can help
Sent from HUAWEI AnyOffice
From:Lance Bragstad
To:OpenStack Development Mailing List (not for usage
questions),openstack-operators@lists.openstack.org,
Date:2016-11-03 08:11:20
Subject:Re:
ed a "public" cloud.
>
> On Fri, Sep 23, 2016 at 3:54 PM, Rochelle Grober <
> rochelle.gro...@huawei.com<mailto:rochelle.gro...@huawei.com>> wrote:
>
>> Hi Matt,
>>
>>
>>
>> At considerable risk of heading down a rabbit hole... h
Hi Matt,
At considerable risk of heading down a rabbit hole... how are you defining
"public" cloud for these purposes?
Cheers,
Blair
Any cloud that provides a cloud to a thirdparty in exchange for money. So,
rent a VM, rent a collection of vms, lease a fully operational cloud spec'ed to
Hey folks!
Do you know about the Interop Challenge? Well, here's a way to learn about it
and and participate if you like...
"The interop challenge was started in July 2016 to create a set of common
workloads/tests to be executed across multiple OpenStack distributions and/or
cloud deployment
I have no vote, but my nonvote is a hearty +1
Tony is amazing.
--Rocky
-Original Message-
From: Amrith Kumar [mailto:amr...@tesora.com]
Sent: Tuesday, September 06, 2016 10:56 AM
To: d...@doughellmann.com
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
Thank you, Doug. Yes, if the DefCore guidelines have any of these tests, the
tests used by DefCore will need to be run beyond EOL of Newton as the DefCore
tests last longer than the EOL timeframe. But, first we should check which
tests need to be capped and whether they are part of a/some
Just an FYI that might be the reason for the 14400:
1440 is the number of minutes in a day. 14400 would be tenths of minutes in a
day of number of 6second chunks (huh???)
So, the number was picked to divide files in human logical, not computer
logical chunks.
--Rocky
-Original
Umm, I see a major contribution area not included here:
OpenStack community meetup organizers. I know some sink a large amount of time
scheduling and organizing at least one a month, some two or more. These
organizers are critical for getting info out on OpenStack and familiarizing
their
repository is: http://git.openstack.org/cgit/openstack/osops-tools-contrib/
FYI, there are also: osops-tools-generic, osops-tools-logging,
osops-tools-monitoring, osops-example-configs and osops-coda
Wish I could help more,
--Rocky
-Original Message-
From: Joshua Harlow
repository is: http://git.openstack.org/cgit/openstack/osops-tools-contrib/
FYI, there are also: osops-tools-generic, osops-tools-logging,
osops-tools-monitoring, osops-example-configs and osops-coda
Wish I could help more,
--Rocky
-Original Message-
From: Joshua Harlow
Perhaps the right way to schedule these bug smashes is to do it at the same
time as the release scheduling is determined. Decide on a fixed time within
the release cycle (it's been just after M3/feature freeze a few times) and when
the schedule is put together, the bugsmash is part of the
Well, you could stick with the wine bottle analogy and go with a bigger size:
Jeroboam
Methuselah
Salmanazar
Balthazar
Nabuchadnezzar
--Rocky
-Original Message-
From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com]
Sent: Wednesday, June 01,
FYI.
If you don't comment, you can't complain when they don't address your needs.
--Rocky
-Original Message-
From: Thierry Carrez [mailto:thie...@openstack.org]
Sent: Wednesday, May 11, 2016 8:28 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] Collecting our wiki use
But, the original spelling of the landing site is Plimoth Rock. There were
still highway signs up in the 70's directing folks to "Plimoth Rock"
--Rocky
Who should know about rocks ;-)
-Original Message-
From: Brian Haley [mailto:brian.ha...@hpe.com]
Sent: Monday, May 02, 2016 3:12 PM
The Ops session on the taxonomy of failure can use some input even before the
session itself!
The etherpad is here:
https://etherpad.openstack.org/p/AUS-ops-Taxonomy-of-Failures
And has a brief outline on some of info we'd like to gather. There is also a
google spreadsheet here:
Bryan,
Check out refstack.openstack.org and https://github.com/openstack/refstack
The refstack project provides a client which enables anyone to run tempest
tests on their own clouds. It is flexible, with options for selecting all or
specific test sets, or specific tests and also has an
There is currently a cross project specification under review that changes how
and where the config files are written for an OpenStack installation. If
config options and how they are presented to you are important to you, I
strongly suggest you go out , read the spec/review and comment on
Hi folks.
I'm chiming in here from a systems engineering perspective. I recently
discovered that OpenStack-client is trying to build cross-project consistency
into its design. As such, it is opinionated, but this is good. The glance
team might consider also consulting the OSC team to ensure
Cross posting to the Ops ML as one/some of them might have a test cloud like
this.
Operators:
If you respond to this thread, please only respond to the openstack-dev list?
They could use your input;-)
--Rocky
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent:
Cross posting to the Ops ML as one/some of them might have a test cloud like
this.
Operators:
If you respond to this thread, please only respond to the openstack-dev list?
They could use your input;-)
--Rocky
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent:
Left a comment on the doodle.
Could you double-check the dates? Most of the days and times listed are
already past.
--Rocky
From: Shamail Tahir [mailto:itzsham...@gmail.com]
Sent: Wednesday, March 30, 2016 10:36 AM
To: openstack-operators; commun...@lists.openstack.org;
(Inline because the mail formatted friendly this time)
From: Tim Bell March 17, 2016 11:26 AM:
On 17/03/16 18:29, "Sean Dague" wrote:
>On 03/17/2016 11:57 AM, Markus Zoeller wrote:
>
>> Suggested action items:
>>
>> 1. I close the open wish list items older than 6 months (=138
+1 Here's another not counting vote and cheer!
--Rocky
+1 for Tony! (my vote does not count, but still wanted to cheer!)
-- Dims
On Fri, Mar 18, 2016 at 4:38 PM, Anita Kuno wrote:
> On 03/18/2016 04:11 PM, Matt Riedemann wrote:
>> I'd like to propose tonyb for
(Sorry for the top post. It was this or bottom post because of company choice
of email systems)
Integration tests, corner cases, negative tests. Lots of names that don't have
clear definitions in this discussion. But, it seems like the collection of
"negative tests" include both functional
Don't quote me on this, but the tool that generates the dev docs is the one the
docs team for the config ref use to generate that document.
And they have been looped in on the upcoming improvements.
--Rocky
-Original Message-
From: Matthew Treinish [mailto:mtrein...@kortar.org]
Sent:
There is also a bit of info on cells from the Manchester meetup in the Large
Deployment team ether pad:
https://etherpad.openstack.org/p/MAN-ops-Large-Deployment-Team
I've added the link to the cells etherpad.
--Rocky
___
OpenStack-operators mailing
Hey, folks. Two things about the agenda.
I can handle the "OSOps - what is it, where is it going, what you can do"
presentation. There might be one other from the group, but if not, it's mine.
Also, instead of the OSOps working session, I'd like to propose:
A session on config opts and what
I'm not a voting member of the Oslo team, but a BIG
+1
>From me.
--Rocky
-Original Message-
From: Joshua Harlow [mailto:harlo...@fastmail.com]
Sent: Thursday, January 28, 2016 11:38 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [oslo]
At the Tokyo summit, there was a working session that addressed how to log the
request-id chain. The etherpad for that is [0]
A spec needs to be written and implementation details need some hashing out,
but the approach should provide a way to track the originating request through
each logged
Devananda van der Veen, on January 21, 2016 5:14 PM wrote:
On Wed, Jan 20, 2016 at 9:53 AM, Flavio Percoco
> wrote:
Greetings,
At the Tokyo summit, we discussed OpenStack's development themes in a
cross-project session. In this session a group of
Any chance you could make the Monday meeting a few hours later? Japan and
China are still mostly in bed then, but two hours would allow both to
participate.
--Rocky
> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Wednesday, December 16, 2015
Congratulations, Matt!
Condolences to Erno, but he's already said he's still part of the team.
I'm looking forward to the IRC meetings and and also what the team becomes.
--Rocky
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info]
> Sent: Wednesday, December 09, 2015
Getting ready to eat lots of turkey
--Rocky
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
++
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: Thursday, November 19, 2015 1:52 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [openstack][openstack-operators] IRC
> meeting(s)
>
> JJ Asghar wrote:
> > I've been seeing
Thanks both Armando and Matt!
I am cross posting this to the operators' list (as the main post -- operators,
simple reply and no spam to dev).
The logging tag should be a tag in all projects. I'm glad it's already there
in Neutron. And, this sort of feedback is exactly what we need operators
Sorry this doesn't thread properly, but cut and pasted out of the digest...
> As providing OpenStack community with understandable recommendations
> and instructions on performant OpenStack cloud deployments is part of
> Performance Team mission, I'm kindly asking you to share your
>
Thanks both Armando and Matt!
I am cross posting this to the operators' list (as the main post -- operators,
simple reply and no spam to dev).
The logging tag should be a tag in all projects. I'm glad it's already there
in Neutron. And, this sort of feedback is exactly what we need operators
Again, my plea to leave the Juno repository on git.openstack.org, but locked
down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade
testing purposes, python2.6 is not needed as any cloud would have to upgrade
python before upgrading to kilo. The testing could/should be
I would like to make a plea that while Juno is locked down so as no changes can
be made against it, the branch remains on the git.openstack.org site. Please?
One area that could be better investigated with the branch in place is upgrade.
Kilo will continue to get patches, as will Liberty, so
+1
I think that as OpenStack's customer base grows, this is going to become more
and more important, and will get the pain of users not getting updates will
increase enough that there *will* be a group of engineers willing to do not
only backports and releases, but bugfixes in trunk and gate
Hey operators and other users (and devs),
We've got a number of logging sessions scheduled for the Summit.
I'm collecting up information on the summit logging etherpad:
https://etherpad.openstack.org/p/TYO-ops-logging
and it will get fleshed out a lot more during the flight;-)
Two goals of
Could you put this in the devref? Or getting started or something so this info
isn't lost and new devs will be educated?
Thanks!
--Rocky
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: Tuesday, October 13, 2015 2:44 AM
> To: openstack-dev@lists.openstack.org
>
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info]
> Sent: Wednesday, October 07, 2015 3:48 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [tc] naming N and O releases nowish
>
> On 10/07/2015 06:22 PM, Monty Taylor wrote:
> > On 10/07/2015
Hello People!
I am tossing one of my hats into the ring to run for TC. Yes, I believe you
could call me a "diversity candidate" as I'm not much of a developer any more,
but I think my skills would be a great addition to the excellent people who are
on the TC (past and present).
My background:
Doug Hellmann wrote:
Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +:
> On Sep 25, 2015, at 1:24 PM, Brian Rosmaita
> wrote:
> >
> > I'd like to clarify something.
> >
> > On 9/25/15, 12:16 PM, "Mark Voelker" wrote:
> >
Just wanted to point out that if you dig a little in Postman's website, it
looks like all the base code is on github, and appears to be under the Apache
license. I didn't check the jetpacks, but I suspect those might be
proprietary bits.
Tripp, Travis S wrote on Monday, August 10, 2015
In line (at the bottom)
From: Devananda van der Veen [mailto:devananda@gmail.com]
Sent: Friday, June 19, 2015 12:40
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header
On Wed, Jun 17, 2015 at 7:31 AM
Adam pointed to this url as a proposal for the namespaces:
https://wiki.openstack.org/wiki/URLs
How about this gets turned into a cross project spec or part of a larger one
with the stuff in this ML thread? Then we can get the projects aware and
buying into this little slice of sanity.
--Rocky
I'd also like to point out that if the state of the projects has encouraged
*new* contributors to OpenStack, then their contributions will likely take a
couple to a few months to become visible in a significant way in the
statistics. Two to three months to get your first merge is extremely
1 - 100 of 138 matches
Mail list logo