华为技术有限公司 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-...@lists.openstack.org,openstack-oper.
Date:2017-04-25 08:24:34
Subject:[openstack-dev] [scientific][nova][cyborg] Special Ha
.html
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Rochelle Grober
Sr. Staff Architect, Open Source
Office Phone:408-330-5472
Email:rochelle.gro...@huawei.com
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、
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
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用
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
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 world
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 t
attempt to serve
--Rocky
> -Original Message-
> From: Erik McCormick [mailto:emccorm...@cirrusseven.com]
> Sent: Tuesday, November 14, 2017 4:25 PM
> To: Rochelle Grober
> Cc: OpenStack Development Mailing List (not for usage questions)
> ; openstack-oper. operat..
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 int
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...@
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 ; openstack-dev
; openstack-operators
; user
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
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
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 w
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 the
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
> experien
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
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
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 t
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 l
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;
user-commit...@lists.o
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: Thursday,
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 both
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:
https://doc
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
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 [mailto:harlo
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 loca
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
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
y requirement that traditionally separates private from public
> clouds. By that definition, Rackspace's Private Cloud offer, where we
> design, deploy and operate a single-tenant cloud on behalf of customers (in
> their data-center or ours) would be considered a "public&quo
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: [open
Hi guys,
I apologize for taking so long to get to this, but I think once we start
meeting, our momentum will build.
I'm cross posting this to dev and operators so anyone who is interested can
participate. I've set up a Doodle to vote on the first set of times (these
happen to work for me and
The Cross Project team meeting discussed the following specs today:
> * Discuss openstack-spec: log guidelines [1]
> * Discuss openstack-spec: OSProfiler [2]
> * Open discussion & announcements
>
> [1] https://review.openstack.org/#/c/132552/
> [2] https://review.openstack.org/#/c/134839/
Hi folks!
Changed the tags a bit because this is a discussion for all projects and
dovetails with logging rationalization/standards/
At the Paris summit, we had a number of session on logging that kept circling
back to Error Codes. But, these codes would not be http codes, rather, as
others h
What I see in this conversation is that we are talking about multiple different
user classes.
Infra-operator needs as much info as possible, so if it is a vendor driver that
is erring out, the dev-ops can see it in the log.
Tenant-operator is a totally different class of user. These guys need
The Log Working Group is a cross project (horizontal) and community group that
is working to rationalize log messages and logging practices across the
OpenStack ecosystem. This has been identified as a big concern within the user
communities. Anyone with an interest in improving logs, logging
Log Working Group is a cross project (horizontal) and community group that is
working to rationalize log messages and logging practices across the OpenStack
ecosystem. This has been identified as a big concern within the user
communities. Anyone with an interest in improving logs, logging and
Hi all,
The first draft of the spec for Log Message Error Codes (from the Log Working
Group) is out for review:
https://review.openstack.org/#/c/172552/
Please comment, and please look for the way forward so that the different
places, ways and reasons errors get reported provide consistency ac
38 matches
Mail list logo
