Re: [Openstack-operators] Ops Community Documentation - first anchor point

Also, apologies, if consolidation or reorganizing all these is reasonable, what do you think that would look like; i.e. osops > tools >> contrib >> generic >> monitoring >> logging > docs > example-configs On Wed, May 23, 2018 at 10:26 PM, Melvin Hillsman wrote: > Great

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Great to see this moving. I have some questions/concerns based on your statement Doug about docs.openstack.org publishing and do not want to detour the conversation but ask for feedback. Currently there are a number of repositories under osops-

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Hi Chris, thanks for summarize our session today in Vancouver. As I18n PTL and one of the Docs Core I put Petr in Cc. He is currently Docs PTL, but unfortunatelly not on-site. I couldn't also not get the full history of the story and that's also not the idea to starting finger pointing. As

Re: [Openstack-operators] Ops Community Documentation - first anchor point

You will want to follow the steps of the "project creators' guide" [1]. Not all of them apply, because this is a docs repo and not a code project repo. Let me know if you have questions about which pieces do or do not apply as you go along, and we can work on improving that document as well. The

Re: [Openstack-operators] Ops Community Documentation - first anchor point

I hadn’t got that far in my thoughts. If you’re able to give that a go, then that would be great! Chris Sent from my iPhone > On May 23, 2018, at 6:46 PM, Jonathan D. Proulx wrote: > > > Thanks for kicking this off Chris. > > Were you going to create that new

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Thanks for kicking this off Chris. Were you going to create that new repository? If not I can take on the tasks of learning how and making it happen. -Jon On Wed, May 23, 2018 at 06:38:32PM -0700, Chris Morgan wrote: : Hello Everyone, : In the Ops Community documentation working session

[Openstack-operators] Ops Community Documentation - first anchor point

Hello Everyone, In the Ops Community documentation working session today in Vancouver, we made some really good progress (etherpad here: https://etherpad.openstack.org/p/YVR-Ops-Community-Docs but not all of the good stuff is yet written down). In short, we're going to course correct on

[Openstack-operators] [self-healing] BoF in Vancouver tomorrow

For everyone interested in self-healing infra, come share your experience and your ideas with like-minded stackers, including folks from 10+ projects working together to make OpenStack self-healing a reality! Thursday, May 24, 1:50pm-2:30pm Vancouver Convention Centre West - Level Two - Room 217

[Openstack-operators] Fwd: Follow Up: Private Enterprise Cloud Issues

There was a great turnout at the Private Enterprise Cloud Issues session here in Vancouver. I'll propose a follow-on discussion for Denver PTG as well as trying to sift the data a bit and pre-populate. Look for that sifted data soon. For folks unable to participate locally, the etherpad is here:

Re: [Openstack-operators] Need feedback for nova aborting cold migration function

We are using multiple storage backend / topology on our side ranging from ScaleIO to CEPH passing by local compute host storage (were we need cold storage) and VNX, I have to said that CEPH is our best bet. Since we use it we clearly reduced our outages, allowed our user advanced features such as

[Openstack-operators] OSA migrating existing deployment to OSA

Hi All, Having attened Fast Forward upgrade session and Upgrade SIG this morning in Vancouver I'm convinced my upgrade problem is really a config management problem. I'm runnig an old deprecated config system that worked gread in 2012, but has aged poorly. I've been meaning to move to OSA for a

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

Hi, actually, I didn't know about that option. I'll enable it right now. Testing is done every morning at about 4:00AM ..so I'll know tomorrow morning if it changed anything. Thanks, Radu On Tue, 2018-05-22 at 15:30 +0200, Saverio Proto wrote: Sorry email went out incomplete. Read this: