[Openstack-operators] [Pike][Keystone] Multiple Keystone Endpoints?

2017-10-26 Thread Andy Wojnarek
Hi, Is it possible to have both v2.0 and v3 endpoints for Keystone? I’m trying to integrate a backup software into Swift, and it requires Keystone 2.0. I added the new endpoints fine, but I’m getting authentication/authorization errors: My Endpoints gvicopnstk01:~ # openstack endpoint list | gr

Re: [Openstack-operators] [magnum] issue using magnum on Pike

2017-10-03 Thread Andy Wojnarek
Group, LLC mobile 717.856.6901 | andy.wojna...@theatsgroup.com On 10/3/17, 4:37 AM, "Spyros Trigazis" wrote: cc Andy Wojnarek and Erik McCormick On 3 October 2017 at 10:32, Spyros Trigazis wrote: > Hello, > > It looks like the new docker modu

Re: [Openstack-operators] [magnum] issue using magnum on Pike

2017-09-29 Thread Andy Wojnarek
n that build? -Erik On Sep 29, 2017 8:59 AM, "Andy Wojnarek" mailto:andy.wojna...@theatsgroup.com>> wrote: So I started a fresh install of Pike on OpenSuSE in my test lab at work, and I’m having a hard time getting Magnum to work. I’m getting this error on Cluster Create: htt

[Openstack-operators] [magnum] issue using magnum on Pike

2017-09-29 Thread Andy Wojnarek
So I started a fresh install of Pike on OpenSuSE in my test lab at work, and I’m having a hard time getting Magnum to work. I’m getting this error on Cluster Create: http://paste.openstack.org/show/622304/ (AttributeError: 'module' object has no attribute 'APIClient') I’m running OpenSuSE 42.

Re: [Openstack-operators] [cinder] unable to copy an image to a new volume on Ocata

2017-05-27 Thread Andy Wojnarek
After a few hours of debugging, I found that I did not have sysfsutils installed, and it was causing it to fail to using iscsi (not configured). Interesting that it did not log as an ERROR, instead in DEBUG. Thanks, Andy From: Andrew Wojnarek Date: Saturday, May 27, 2017 at 11:45 AM To: "opens

[Openstack-operators] [cinder] unable to copy an image to a new volume on Ocata

2017-05-27 Thread Andy Wojnarek
Hi, So I’m trying to integrate Cinder and IBM Storwize into my cloud in my lab and I’m running into an issue. I can create volumes (empty), no problem – but when I try and copy an image to that volume on creation I get an error: ImageCopyFailure: Failed to copy image to volume: Bad or unexpecte

Re: [Openstack-operators] Cannot launch instances on Ocata.

2017-05-17 Thread Andy Wojnarek
| andy.wojna...@theatsgroup.com Galileo Performance Explorer Blog <http://galileosuite.com/blog/> Offers Deep Insights for Server/Storage Systems On 5/17/17, 6:35 PM, "Andy Wojnarek" wrote: Thanks! I see my endpoints had controller:8778/placement, and that appears to be

Re: [Openstack-operators] Cannot launch instances on Ocata.

2017-05-17 Thread Andy Wojnarek
penstack.org/en/question/102256/how-to-configure-placement-service-for-compute-node-on-ocata/ or here: https://docs.openstack.org/developer/nova/placement.html I'm assuming that service spits out its own log. IF so, is there anything in it?

Re: [Openstack-operators] Cannot launch instances on Ocata.

2017-05-17 Thread Andy Wojnarek
heduler.log (controller) and the nova-compute.log (compute). You can look for your request ID and then go forward from there. Those should shed some more light on what the issue is -Erik On Wed, May 17, 2017 at 5:09 PM, Andy Wojnarek wrote: > Hi, > >

[Openstack-operators] Cannot launch instances on Ocata.

2017-05-17 Thread Andy Wojnarek
Hi, I have a new Openstack cloud running in our lab, but I am unable to launch instances. This is Ocata running on Ubuntu 16.04.2 Here are the errors I am getting when trying to launch an instance: On my controller node in log file /var/log/nova/nova-conductor.log 2017-05-17 16:48:33.656 2654 E