Re: [Openstack-operators] [User-committee] User Committee elections

2017-02-17 Thread Edgar Magana
Congratulations to our elected User Committee Members! This is a huge achievement for the UC. We all together we are going to make huge impact in OpenStack. Looking forward to working with you Shamail and Melvin. Chris, Yih Leong and Maish, I want to thank you for being part of our efforts. We

Re: [Openstack-operators] [User-committee] User Committee elections

2017-02-17 Thread Shamail
> On Feb 17, 2017, at 7:39 PM, Melvin Hillsman wrote: > > Thank you to everyone who voted, the election committee, and the others who > ran. I consider it an honor and privilege and am looking forward to the > coming days. +1, well said! > > -- > Melvin Hillsman > Ops Technical Lead > OpenSt

Re: [Openstack-operators] [User-committee] User Committee elections

2017-02-17 Thread Melvin Hillsman
Thank you to everyone who voted, the election committee, and the others who ran. I consider it an honor and privilege and am looking forward to the coming days. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Lea

Re: [Openstack-operators] [User-committee] User Committee elections

2017-02-17 Thread Lauren Sell
Congrats Shamail and Melvin! And many thanks to all of the candidates who stepped up to run; it was a very strong group! Finally, thank you Matt and Matt for running the election :) On February 17, 2017 6:11:18 PM Matt Jarvis wrote: Hi All I'm very pleased to announce the results of the

[Openstack-operators] User Committee elections

2017-02-17 Thread Matt Jarvis
Hi All I'm very pleased to announce the results of the first User Committee elections, which closed at 21.59UTC on the 17th February 2017. The two candidates elected to the User Committee are Melvin Hillsman and Shamail Tahir. Congratulations to Melvin and Shamail, I know they will both do an ex

Re: [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

2017-02-17 Thread Alex Schultz
Top posting this thread because we're entering the Pike cycle. So as we enter Pike, we are officially dropping support for Puppet 3. We managed to not introduce any puppet 4 only requirements for the puppet OpenStack modules during the Ocata cycle. The Ocata modules[0] are officially the last cy

Re: [Openstack-operators] Openstack and Ceph

2017-02-17 Thread Alex Hübner
Are these nodes connected to a dedicated or a shared (in the sense there are other workloads running) network switches? How fast (1G, 10G or faster) are the interfaces? Also, how much RAM are you using? There's a rule of thumb that says you should dedicate at least 1GB of RAM for each 1 TB of raw d

Re: [Openstack-operators] Openstack Ceph Backend and Performance Information Sharing

2017-02-17 Thread Warren Wang
@Vahric, FYI, if you use directio, instead of sync (like a database is is default configured for), you will just be using the RBD cache. Look at the latency on your numbers. It is lower than is possible for a packet to traverse the network. You'll need to use sync=1 if you want to see what the perf

Re: [Openstack-operators] pip problems with openstack-ansible deployment

2017-02-17 Thread Kris G. Lindgren
I don't run OSAD, however did you confirm that on your repo server that you can actually download the files via a curl/wget call, locally and remotely? I see you show the files exist, but don't see anything confirming that the web server is actually serving them. I have seen things under apach

Re: [Openstack-operators] Please give your opinion about "openstack server migrate" command.

2017-02-17 Thread David Medberry
Replying more to the "thread" and stream of thought than a specific message. 1) Yes, it is confusing. Rikimaru's description is more or less what I believe. 2) Because it is confusing, I continue to use NovaClient commands instead of OpenstackClient I don't know what drove the creation of the Ope

Re: [Openstack-operators] Openstack Ceph Backend and Performance Information Sharing

2017-02-17 Thread Luis Periquito
There is quite some information missing: how much RAM do the nodes have? What SSDs? What Kernel (there has been complaints of a performance regression on 4.4+). You also never state how you have configured the OSDs, their journals, filestore or bluestore, etc... You never specify how you're acces

Re: [Openstack-operators] Please give your opinion about "openstack server migrate" command.

2017-02-17 Thread Rikimaru Honjo
Hi Marcus, On 2017/02/17 15:05, Marcus Furlong wrote: On 17 February 2017 at 16:47, Rikimaru Honjo wrote: Hi all, I found and reported a unkind behavior of "openstack server migrate" command when I maintained my environment.[1] But, I'm wondering which solution is better. Do you have opinions

[Openstack-operators] pip problems with openstack-ansible deployment

2017-02-17 Thread Danil Zhigalin (Europe)
I noticed one error in my previous explanation. I am running Ubuntu 14.04 LTS, not 16.04. Danil Zhigalin Technical Consultant Tel: +49 211 1717 1260 Mob: +49 174 151 8457 danil.zhiga...@dimensiondata.com Derendorfer Allee 26, Düsseldorf, North Rhine-Westphalia, 40476, Germany. For more inf

[Openstack-operators] pip problems with openstack-ansible deployment

2017-02-17 Thread Danil Zhigalin (Europe)
Hello everyone, Context: openstact-ansible: stable/newton OS: ubuntu 16.04 LTS I am having trouble completing my deployment due to pip errors. I have a 2 node setup and one separate deployment node. One of the nodes I am using to host all controller, network and storage functions and another