[Openstack-operators] [openstack][openstack-dev][openstack-operators][chef] kitchen-openstack 2.2.0 released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey everyone! I just released 2.2.0[1] of the kitchen-openstack driver. If your curious the CHANGELOG is located here[2]. We're doing great work with kitchen-openstack, and would love to see some more feedback on things the community would support or features. Please put in an issue[3], for a feature request, so we can start the discussion there. If you have any questions or thoughts don't hesitate to reach out. [1]: https://rubygems.org/gems/kitchen-openstack/versions/2.2.0 [2]: https://github.com/test-kitchen/kitchen-openstack/blob/master/CHANGELOG.md#220 [3]: https://github.com/test-kitchen/kitchen-openstack/issues - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWcbXfAAoJEDZbxzMH0+jT5S0P/RRHbahe0rMnzHNuiPtThilg JODMMoHR0MmGsis/n3CSZ4WDez7Ev558Ph7iqx8upuHL3Asa/zreaK4fOlrjvDeW WVopRa0myKVZpTssnQXNP6ZFRWcrr2nQaL8CXkk+r2ULVG64M+b/ekYfGrdOUfuw zcNQoM6Z9vRGflPjD3WDLVDpVw2awRrZQ3AOanpPyxiIZMvVbQodJYnhBXA9pSlQ lXgC9qG/JPhq3VYuAocLofiF8+maIvCUB6EU9i0ddfaqBMyiFrPo9l0RYaNIMQXF f+b1WdDq5vRi8RJSl4v9TEWpaqF+spHpFqA2GS6LSeh1/Wv9R2+/xKS1C1jrAfMn Zh29jb324tpJ6A/783+1C7+Psa6V2d8Su8I0Fr00brWovdhag7pmKliHLyWTA78A a7wQtWohvalzGwjTofOkkbiY4IpIrwESUsOaT1pR+Gk0KZDt+s1+cwiU802IK6u1 eiCbXPOqho0Q0GNglFgVHbk/U2TqG0Z4+KV6utCCqOK9dkVJuGV5RHJ0IddEiXEr fvZbDVIkSozWbSsJBpKZuFOcT/XWc9UUCk/ow1FdlmxDN4o8CUcV5fliM/Y0AjXf Vh+wt9gfQNpv1Svhw+bhtjQiGoy5wkUOfT3QjE7D3Z7DFXcmmZqyh38YEDyiflZw 7Z031uewvalMgHRTeLGm =7kGh -END PGP SIGNATURE- ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack][openstack-dev][openstack-operators][chef] stable/kilo is born!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'd like to announce that we have stamped stable/kilo. I'd like to congratulate everyone who has committed and helped the OpenStack-Chef project get to this milestone. We have made tremendous progress with the limited resources our project has. If you are using or are thinking of using the Chef cookbooks please don't hesitate to come round to #openstack-chef and help out, our project is always looking for feedback. If you don't know, our meeting time is here[1] and most of the cores are available in the channel during US business hours. [1]: https://wiki.openstack.org/wiki/Meetings/ChefCookbook Cheers! - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJV36LqAAoJEDZbxzMH0+jT1OAQAK6p7Z8HfBPiLuAvyWGDhF2Z MOVibLXXTjpZjdvUPwGo/nadVxUH5yZxUndZ8P6rmHcklvK0M6ETL6n3X86Y1rmG JbOf0oi7b2irIG50i+TCSdmhhelpDI/8tg+oFVD27nsTvfz1hNmlFjMNin7N1AD5 yqft1UJOU23B643F6/KCG299thyJviDN0Jgoe3VrKERXpol/1yL63VbNQOsLj6Dq 03hTGOW84qpUK8o+C+/7sxQ5KolrQ6OhYU4IBXafroiFtzeV8ROUX8WsrEtGXwzi RsQk2n0xlENy9XVIyJxKdoZx6VGSqvTKIMyF+9C42rvlBS0aRYUmnDR1u+vdGmWX H1bCUxbam0zG4GZ96GOXJ6xOlay79+qEIQt1svCIFeCxTmmLoFTLjQkAbSR+tf9W Cdys/+Pq2EZA/KG7CIMk6rAl/aveikO/9JoCuzyY7asm2++o0Csc1QoPvJU9MWHY mQHsonsf9MTd3/8cM7H7BnzWcGpbQYokhVwEJBaysqJekIrcJ8I+is87yEV9RuHB GtUCW84z2/+PwDYPSCZH+iE8eqY1Q7xyFRxzceoqZDtEaWjgmv73MTsnAZhza4Il GgdwFmLuk5UeKSfGTA7a5ernvCOHmoGmnD2mXKvqq5KnYw9X2cm69tZ5NiixVTZw baN5uo04PCDLGGzitSPJ =/MCc -END PGP SIGNATURE- ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Chef cookbook
Hi, I've integrated chef with openstack and needed to work on the cookbooks. I wanted to upload a docker and mysql cookbook in specific to the chef-dashboard. I've gone through the supermarket of the chef.io but I just ended up confused. Moreover, when I tried uploading the cookbook it either gave me an error. Could some give me the steps as to how to proceed from the point of bringing the cookbooks to the node, uploading it and adding it to the run list. Thank you! This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-dev][openstack-operators][chef] Thanks again, and we've already made amazing progress since Summit!
All, I’d like to thank everyone that came to the Vancouver Summit and our Official Ops Meeting[1]. Since then we have officially been sanctioned[2] and made amazing progress with true integration testing our cookbooks[3][4], including leveraging Rally[5] for benchmarking. Turns out after the meeting Mark, Jan, Allan, and I sat down and with some conversations with the infra team been able to push our testing without having to build a Jenkins/drone instance. Needless to say this was hugely amazing and shows what happens when we have lines of communication open and a quick feedback loop. I’m excited to see what we can make happen as a community over the next cycle(s). I thought I would drop everyone a note, say that your input has been invaluable and we are making leaps and bounds already. If you’re curious, I’ve put the review in to move from stackforge to openstack officially via infra[6] and it’s slated for next weeks infra meeting[7]. Any relevant update I’ll pass along. If you have any questions or comments, thoughts anything don’t hesitate to reach out and again, thanks again everyone! -JJ [1]: https://etherpad.openstack.org/p/YVR-ops-chef https://etherpad.openstack.org/p/YVR-ops-chef [2]: https://review.openstack.org/#/c/175000/ https://review.openstack.org/#/c/175000/ [3]: https://review.openstack.org/#/c/185085/ https://review.openstack.org/#/c/185085/ [4]: https://review.openstack.org/#/c/185178/ https://review.openstack.org/#/c/185178/ [5]: https://wiki.openstack.org/wiki/Rally https://wiki.openstack.org/wiki/Rally [6]: https://review.openstack.org/#/c/186532/ https://review.openstack.org/#/c/186532/ [7]: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-dev][openstack-operators][chef] OpenStack+Chef is part of the big tent
Hey everyone! I’d like to just drop a note to the list saying thank you and congratulations to our general community. As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us as an official OpenStack project. This is amazing news, and lets keep up the great work! If you have an questions or thoughts please don’t hesitate to reach out. [1]: https://review.openstack.org/#/c/175000/ https://review.openstack.org/#/c/175000/ Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-dev][openstack-operators][chef] OpenStack+Chef is part of the big tent
Congrats and welcome! On May 26, 2015 5:35 PM, JJ Asghar jasg...@chef.io wrote: Hey everyone! I’d like to just drop a note to the list saying thank you and congratulations to our general community. As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us as an official OpenStack project. This is amazing news, and lets keep up the great work! If you have an questions or thoughts please don’t hesitate to reach out. [1]: https://review.openstack.org/#/c/175000/ Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] chef
Hi, Yes, when I issued the command to create a node I was able to view it in my dashboard and also thorough my cli by 'knife openstack server list' command. I'm able to ssh to the node without any problem but the create command gives an error even though the node is created. The next step is the knife bootstrap which gives an error of course. This is what I've tried: Chef-server version for 14.04: chef-server-core_12.0.4-1_amd64.deb and Openstack- Juno version Steps what I've been following are: /etc/hosts 127.0.0.1 localhost # If the localhost is commented the chef-server-ctl reconfigure gets into an error. x.x.x.x chef-server dpkg -i chef-server-core_12.0.4-1_amd64.deb chef-server-ctl reconfigure Note: The error I get when the localhost is commented out is--- Recipe: private-chef::oc_id * runit_service[oc_id] action restart === Error executing action `restart` on resource 'runit_service[oc_id]' === Mixlib::ShellOut::ShellCommandFailed Expected process to exit with [0], but received '1' And even if I do get through this step by uncommenting the section in the /etc/hosts I'm unable to view the GUI of my web server as it reads: Chef Server API This is the main endpoint for all of the Chef APIs. In general, none of these have any HTML representations, and the vast majority of them require that you are sending properly authenticated requests. So while it's neat that you came to visit, you probably won't find what you are looking for here. I restarted all the chef services to make sure they were running and they ran fine. Wondering if it was because I didn't run the command: chef-server ctl install opscode-manage but there was an error similar to the above mentioned error. Therefore I used the package of 11.0.1 of chef-server with my juno openstack following the link: http://www.bogotobogo.com/DevOps/Chef/Chef_Client_Node_Knife_Bootstraping_a_Node_on_EC2_ubuntu_14_04.php The only difference is I've made use of openstack instead of EC2 but at the end I've encountered similar error to what the document has got. Aishwarya Adyanthaya - On May 14, 2015, at 1:21 AM, aishwarya.adyanth...@accenture.com wrote: Hi J, I ran the command 'knife node list' and found the list to be empty while the 'knife client list' command displays chef-validator and chef-webui. It seems like when I was creating the node through knife openstack server create the node got launched successfully in the dashboard and I'm able to ssh the node but the command gives error as: Waiting for sshd to host (x.x.x.x). done Doing old-style registration with the validation key at /root/chef-repo/.chef/chef-validator.pem... Delete your validation key in order to use your user credentials instead Connecting to x.x.x.x FATAL: Check if --bootstrap-protocol and --image-os-type is correct. connection closed by remote host ERROR: Net::SSH::Disconnect: Check if --bootstrap-protocol and --image-os-type is correct. connection closed by remote host The command I'm using to create the node is: knife openstack server create -f 2 -I ubuntu_image -a external_id--network-ids alphanumeric_id -S chef_key -N node_name - I’m at a loss here. If this is a Ubuntu box, neither of the —bootstrap-protocol or the —image-os-type should be even checked. This is also failing because the connection was closed, so thats pointing to your vm on the in your OpenStack instance. Do you have any networking oddities between your workstation and this vm and cloud? Also, i’m hoping that “ubuntu_image” is you scrubbing your UUID, because I’ve seen some issues with using the “easy name” in Juno. I’m pretty sure it was resolved in the 1.0.0 release though. Actually yeah i don’t know what version of the OpenStack are you running against? Is this a major public cloud or is it in-house? I’ve personally tested the knife-openstack 1.1.0 against a couple major public clouds, devstack, and the Chef cookbook built OpenStack instance so I know we have a good coverage. You said you can SSH into the box, that’s good, so also lets take a step back. Can you provision a machine with knife openstack server create? When you do, do you see it pop up in nova list or the horizon dashboard? If so, then we can determine that the creation is working and we can move forward with the network connection and bootstrapping. In very simple terms the bootstrap literally SSHs into the box, pulls down chef, moves up the validation key and then runs chef-client. If you can SSH to it
[Openstack-operators] [openstack-operators][chef] OpenStack-Chef Official Ops Meetup
On May 12, 2015, at 3:00 PM, JJ Asghar jasg...@chef.io wrote: I’d like to announce the OpenStack-Chef Ops Meetup in Vancouver. We have an etherpad[1] going with topics people would like to discuss. I haven’t found a room or space for us yet, but when I do I’ll comment back on this thread and add it to the etherpad, (right now looking at the other declaration of time slots, I think Wednesday 1630 is going to be our best bet) As with the Paris Ops Meetup we had a lot of great questions and use cases discussed but it was very unstructured and I got some negative feedback about that, hence the etherpad. Hey Everyone, so it seems I need to take a step back because I got some wires crossed. Turns out the Ops meetup is our offical meeting space during the Summit which i put on the on the etherpad[1]. I’d like to keep this on topic per the agenda we’ve created on that etherpad. I think this is best, it gives the larger community of OpenStack+Chef users to come together and discuss future plans and questions in a face to face in a real time discussion. Just so we have it documented in this email: the meetup is in Room 217 on Wednesday at 0950am[2]. Though this brings up the topic of the Dev meetup. As the majority of the core members are going to be at the Summit, we still need a time and a place for us to discuss the stable/kilo branching. I propose we find a working space, and just spend an hour or two together. I’ve created a doodle[3] with some time slots, if you could put your ideal time in, including your email address so we can organize off the mailing list. I’ll @core this in the IRC channel too. This is also open to the community as a whole, so if you’d like to post your ideal time don’t hesitate to. If I can ask for a volunteer note-taker to step up and to directly contact me; so when we start the meeting we can just jump in that would me amazing. I can sweeten the deal if you step up with some Chef Swag too ;). Just to follow up on this, I haven’t had anyone step up yet, so if you where thinking about it, please don’t hesitate to reach out. [1]: https://etherpad.openstack.org/p/YVR-ops-chef https://etherpad.openstack.org/p/YVR-ops-chef [2]: http://sched.co/3D8a http://sched.co/3D8a[3]: http://doodle.com/gb4ww6izbwg8k9di http://doodle.com/gb4ww6izbwg8k9di___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] chef
On May 14, 2015, at 1:21 AM, aishwarya.adyanth...@accenture.com wrote: Hi J, I ran the command 'knife node list' and found the list to be empty while the 'knife client list' command displays chef-validator and chef-webui. It seems like when I was creating the node through knife openstack server create the node got launched successfully in the dashboard and I'm able to ssh the node but the command gives error as: Waiting for sshd to host (x.x.x.x).done Doing old-style registration with the validation key at /root/chef-repo/.chef/chef-validator.pem... Delete your validation key in order to use your user credentials instead Connecting to x.x.x.x FATAL: Check if --bootstrap-protocol and --image-os-type is correct. connection closed by remote host ERROR: Net::SSH::Disconnect: Check if --bootstrap-protocol and --image-os-type is correct. connection closed by remote host The command I'm using to create the node is: knife openstack server create -f 2 -I ubuntu_image -a external_id--network-ids alphanumeric_id -S chef_key -N node_name I’m at a loss here. If this is a Ubuntu box, neither of the —bootstrap-protocol or the —image-os-type should be even checked. This is also failing because the connection was closed, so thats pointing to your vm on the in your OpenStack instance. Do you have any networking oddities between your workstation and this vm and cloud? Also, i’m hoping that “ubuntu_image” is you scrubbing your UUID, because I’ve seen some issues with using the “easy name” in Juno. I’m pretty sure it was resolved in the 1.0.0 release though. Actually yeah i don’t know what version of the OpenStack are you running against? Is this a major public cloud or is it in-house? I’ve personally tested the knife-openstack 1.1.0 against a couple major public clouds, devstack, and the Chef cookbook built OpenStack instance so I know we have a good coverage. You said you can SSH into the box, that’s good, so also lets take a step back. Can you provision a machine with knife openstack server create? When you do, do you see it pop up in nova list or the horizon dashboard? If so, then we can determine that the creation is working and we can move forward with the network connection and bootstrapping. In very simple terms the bootstrap literally SSHs into the box, pulls down chef, moves up the validation key and then runs chef-client. If you can SSH to it from the box you run your knife commands from, then there is no reason why this shouldn’t work. Anyway, this is the best i got via email, i’m curious to see if any of this helps you, -JJ ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] chef
Ashwarya, can you try knife node list and knife client list for me? You should see the the machine you’re attempting to create. I’m betting that there is a node like the error says, and you’ll need to do a knife node delete that_server_name then run the bootstrap command again and it should work. -J ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] chef
On May 12, 2015, at 10:06 AM, Abel Lopez alopg...@gmail.com wrote: I think the error comes from your chef server, not openstack API. Have you tried answering N to the overwrite? On May 12, 2015, at 4:48 AM, aishwarya.adyanth...@accenture.com mailto:aishwarya.adyanth...@accenture.com wrote: Hello, I’m trying to integrate chef-server(version 11.0.10) with Ubuntu Openstack. I’m able to create an instance from the chef server in the openstack dashboard but I get an error while trying to bootstrap the node. The error is as described below: root@master:~/chef-repo# knife bootstrap external_ip –i /home/oss/chef_key.pem -x ash --sudo -V INFO: Using configuration from /root/chef-repo/.chef/knife.rb Node exists, overwrite it? (Y/N) y INFO: HTTP Request Returned 405 Method Not Allowed: ERROR: Method Not Allowed Response: I configured security rules in the dashboard by adding http, https, ssh but it doesn’t seem to work. Can someone tell me what I’m doing wrong? Thanks in advance! Aishwarya Adyanthaya Hi! Ashwarya, any chance can you come around to #openstack-chef on freenode? We have a great community there and I’m betting we can help move you forward with your issue. If you’d like to directly ping me i’m j^2 in the channel, and am almost always there. And to parriot what Abel is saying it looks like that issue is related to you not removing the node from your chef server, but we can talk more detail there. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-operators][chef] OpenStack-Chef Ops Meetup
Hey Everyone! I’d like to announce the OpenStack-Chef Ops Meetup in Vancouver. We have an etherpad[1] going with topics people would like to discuss. I haven’t found a room or space for us yet, but when I do I’ll comment back on this thread and add it to the etherpad, (right now looking at the other declaration of time slots, I think Wednesday 1630 is going to be our best bet) As with the Paris Ops Meetup we had a lot of great questions and use cases discussed but it was very unstructured and I got some negative feedback about that, hence the etherpad. I’d like to leverage the etherpad and have a semi-solid agenda so we can hit any major discussion topics that you, the community, would like to discuss. If I can ask for a volunteer note-taker to step up and to directly contact me; so when we start the meeting we can just jump in that would me amazing. I can sweeten the deal if you step up with some Chef Swag too ;). I hope to see you there and don’t hesitate to reach out if you have any relevant questions. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar [1]: https://etherpad.openstack.org/p/YVR-ops-chef https://etherpad.openstack.org/p/YVR-ops-chef ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] chef
Hi, While I try to answer “N” to the overwrite this is what I get: root@master:~/chef-repo# knife bootstrap external_ip –i /home/oss/chef_key.pem -x ash --sudo -V INFO: Using configuration from /root/chef-repo/.chef/knife.rb Node exists, overwrite it? (Y/N) n You said no, so I'm done here. root@master:~/chef-repo# My knife.rb reads like this: log_level :info log_location STDOUT node_name 'ash' client_key '/root/chef-repo/.chef/ash.pem' validation_client_name'chef-validator' validation_key '/root/chef-repo/.chef/chef-validator.pem' chef_server_url 'https://master:443' syntax_check_cache_path '/root/chef-repo/.chef/syntax_check_cache' cookbook_path [ '/root/chef-repo/cookbooks' ] ### Note: If you are not proxying HTTPS to the OpenStack auth port, the scheme should be HTTP knife[:openstack_auth_url] = http://controller:5000/v2.0/tokens; knife[:openstack_username] = admin knife[:openstack_password] = admin knife[:openstack_tenant] = admin root@master:~/chef-repo/.chef# ls admin.pem ash.pem knife.rb syntax_check_cache trusted_certs From: Abel Lopez [mailto:alopg...@gmail.com] Sent: Tuesday, May 12, 2015 8:36 PM To: Adyanthaya, Aishwarya Cc: openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] chef I think the error comes from your chef server, not openstack API. Have you tried answering N to the overwrite? On May 12, 2015, at 4:48 AM, aishwarya.adyanth...@accenture.commailto:aishwarya.adyanth...@accenture.com wrote: Hello, I’m trying to integrate chef-server(version 11.0.10) with Ubuntu Openstack. I’m able to create an instance from the chef server in the openstack dashboard but I get an error while trying to bootstrap the node. The error is as described below: root@master:~/chef-repo# knife bootstrap external_ip –i /home/oss/chef_key.pem -x ash --sudo -V INFO: Using configuration from /root/chef-repo/.chef/knife.rb Node exists, overwrite it? (Y/N) y INFO: HTTP Request Returned 405 Method Not Allowed: ERROR: Method Not Allowed Response: I configured security rules in the dashboard by adding http, https, ssh but it doesn’t seem to work. Can someone tell me what I’m doing wrong? Thanks in advance! Aishwarya Adyanthaya This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.comhttp://www.accenture.com/ ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.orgmailto:OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
