From tsuyuzaki.kota at lab.ntt.co.jp Fri Jun 1 05:32:18 2018 From: tsuyuzaki.kota at lab.ntt.co.jp (Kota TSUYUZAKI) Date: Fri, 01 Jun 2018 14:32:18 +0900 Subject: [Openstack] Struggling to get the s3 api interface to work with swift. In-Reply-To: References: <2925BD08-5166-4FCB-97D0-84FBA872FFC4@ostorage.com.cn> <5B5E845C-A3D1-436E-BDC9-846257587357@ostorage.com.cn> <5F134369-41C0-4AAA-8E49-8D921AF524FA@ostorage.com.cn> Message-ID: <5B10DA62.9010106@lab.ntt.co.jp> Hi Shyam, You should specify the path starts from bucket. It will be like http://20.20.20.229:8080/testBucket assuming you didn't configure virtual-hosted style. Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578, swift3 doesn't require the account in the path so far as well as actual amazon s3. Best, Kota (2018/05/31 21:33), Shyam Prasad N wrote: > Hi Yuxin, > > Thank you for sharing your configs. > So I've managed to get past the Signature not matching error. > > Now the error is different. InvalidbucketName: > > eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks > --createBucket -- > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket > s3curl: Found the url: host=20.20.20.229; port=8080; > uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=; > s3curl: cname endpoint signing case > s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +0000\n/ > 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket' > s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +0000' -H > 'Authorization: AWS > 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H > 'content-type: ' --data-binary -X PUT > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket > * Trying 20.20.20.229... > * TCP_NODELAY set > * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0) >> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1 >> Host: 20.20.20.229:8080 >> User-Agent: curl/7.58.0 >> Accept: */* >> Date: Thu, 31 May 2018 12:02:57 +0000 >> Authorization: AWS > 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0= >> Content-Length: 0 >> > < HTTP/1.1 400 Bad Request > < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471 > < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471 > < Content-Type: application/xml > < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471 > < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471 > < Date: Thu, 31 May 2018 12:02:57 GMT > < Transfer-Encoding: chunked > * HTTP error before end of send, stop sending > < > > * Closing connection 0 > InvalidBucketNameThe specified bucket is not > valid.tx18266052d5044eb2a3bc7-005b0fe471v1eightkpc at objectstore1:~/s3curl$ > > > My specified endpoint is > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578 > What am I doing wrong? > > Regards, > Shyam > > On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang > wrote: > >> Hi Shyam, >> >> No problem. The output of the commands is attached. >> >> And my test cluster is on Swift v2.15.1 with Swift3 v1.12 >> >> Also, here is the common process when I'm creating an S3 credential and >> using in s3curl. Hope it helps. >> >> 1. Create a user and a project, and assign a proper role. >> >> openstack project create testproject >> openstack user create testuser --password 123 >> openstack role add --project testproject --user testuser _member_ >> >> 2. Check accessibility to swift >> >> create a test-openrc file with above info >> source test-openrc >> swift list >> >> 3.Create a credential >> >> openstack credential create --type ec2 --project testproject testuser >> '{"access": "testaccess", "secret": "testsecret"}' >> >> 4. Use it in s3curl >> >> add the endpoint url to `my @endpoints` in s3curl.pl >> add the credential to .s3curl config file >> >> do `s3curl.pl -i cred_name --debug -- http://endpoint -X GET` >> >> >> >> >> 在 2018年5月25日,18:17,Shyam Prasad N 写道: >> >> Hi Yuxin, >> >> If you don't mind, can you share the output of the following commands in >> your running swift3 setup? >> >> openstack credential list >> openstack ec2 credentials list >> cat /etc/swift/proxy-server.conf >> >> Also, what are the access keys and secret keys that you use? >> I want to make sure that I'm not missing anything in configuration. >> >> Regards, >> Shyam >> >> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N >> wrote: >> >>> Tried that. Unfortunately same error. >>> Is there anything I can do to troubleshoot this? >>> >>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang >>> wrote: >>> >>>> They can be any strings. >>>> >>>> Replace them with whatever you want. >>>> >>>> - Yuxin >>>> >>>> 在 2018年5月25日,14:57,Shyam Prasad N 写道: >>>> >>>> Thanks. I'll try this. >>>> But what values do I use in place of ak and sk? I want to use some >>>> command to get those values, right? >>>> >>>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang >>>> wrote: >>>> >>>>> I created ec2 credentials using command `openstack credential create`. >>>>> >>>>> i.e. >>>>> >>>>> openstack credential create --type ec2 --project proj user '{"access": >>>>> "ak", "secret": "sk”}' >>>>> >>>>> >>>>> It seems the two credentials are not the same thing. >>>>> >>>>> Ref: >>>>> >>>>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/ >>>>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta >>>>> ckEC2credentials.htm >>>>> >>>>> >>>>> 在 2018年5月25日,10:32,Shyam Prasad N 写道: >>>>> >>>>> Yes, I did. >>>>> I don't think this is s3curl related issue, because I tried with python >>>>> AWS SDK, and got the same error. >>>>> >>>>> On Fri, May 25, 2018, 07:42 Yuxin Wang >>>>> wrote: >>>>> >>>>>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl >>>>>> >>>>>> ? >>>>>> >>>>>> i.e. >>>>>> >>>>>> my @endpoints = (‘127.0.0.1’); >>>>>> >>>>>> 在 2018年5月24日,19:48,Shyam Prasad N 写道: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I've been trying to get swift3 to work for several days now. But I >>>>>> haven't managed to get it running. >>>>>> Both with tempauth and keystoneauth, I'm getting the same error: >>>>>> >>>>>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl >>>>>> >>>>>> --id=testerks -- http://127.0.0.1:8080/ >>>>>> >>>>>> >>>>>> SignatureDoesNotMatchThe request >>>>>> signature we calculated does not match the signature you provided. Check >>>>>> your key and signing method.tx >>>>>> a691e7ca97a44d56bc4c2-005b06a292 >>>>>> >>>>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1 >>>>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 - >>>>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - 1527161490.543112040 >>>>>> 1527161490.563107014 - >>>>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - - >>>>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn: >>>>>> txa691e7ca97a44d56bc4c2-005b06a292) >>>>>> >>>>>> eightkpc at objectstore1:~$ cat .s3curl >>>>>> %awsSecretAccessKeys = ( >>>>>> tester => { >>>>>> id => 'test:tester', >>>>>> key => 'testing', >>>>>> }, >>>>>> testerks => { >>>>>> id => 'e6289a1b5692461388d0597a4873d054', >>>>>> key => '88bb706887094696b082f008ba133ad7', >>>>>> }, >>>>>> ); >>>>>> >>>>>> eightkpc at objectstore1:~$ openstack ec2 credentials show >>>>>> e6289a1b5692461388d0597a4873d054 >>>>>> +------------+---------------------------------------------- >>>>>> ------------------------------------------------------------ >>>>>> --------------------------+ >>>>>> | Field | Value >>>>>> >>>>>> | >>>>>> +------------+---------------------------------------------- >>>>>> ------------------------------------------------------------ >>>>>> --------------------------+ >>>>>> | access | e6289a1b5692461388d0597a4873d0 >>>>>> 54 >>>>>> | >>>>>> | links | {u'self': u'http://controller:5000/v3/us >>>>>> ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628 >>>>>> 9a1b5692461388d0597a4873d054'} | >>>>>> | project_id | dc86f7d8787b46158268bd77098b65 >>>>>> 78 >>>>>> | >>>>>> | secret | 88bb706887094696b082f008ba133a >>>>>> d7 >>>>>> | >>>>>> | trust_id | None >>>>>> >>>>>> | >>>>>> | user_id | d7df7b56343b4ea988869fc30efeda >>>>>> 09 >>>>>> | >>>>>> +------------+---------------------------------------------- >>>>>> ------------------------------------------------------------ >>>>>> --------------------------+ >>>>>> >>>>>> Can someone please let me know what is going on? >>>>>> >>>>>> Regards, >>>>>> Shyam >>>>>> _______________________________________________ >>>>>> Mailing list: https://eur03.safelinks.protection.outlook.com/?url= >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 >>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI >>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 >>>>>> Post to : openstack at lists.openstack.org >>>>>> Unsubscribe : https://eur03.safelinks.protection.outlook.com/?url= >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 >>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI >>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> -Shyam >>>> _______________________________________________ >>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f >>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% >>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 >>>> Post to : openstack at lists.openstack.org >>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f >>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% >>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 >>>> >>>> >>>> >>> >>> >>> -- >>> -Shyam >>> >> >> >> >> -- >> -Shyam >> _______________________________________________ >> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= >> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a5c90% >> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910462&sdata=% >> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 >> Post to : openstack at lists.openstack.org >> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= >> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a5c90% >> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910462&sdata=% >> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 >> >> >> >> > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > From nspmangalore at gmail.com Fri Jun 1 05:49:18 2018 From: nspmangalore at gmail.com (Shyam Prasad N) Date: Fri, 1 Jun 2018 11:19:18 +0530 Subject: [Openstack] Struggling to get the s3 api interface to work with swift. In-Reply-To: <5B10DA62.9010106@lab.ntt.co.jp> References: <2925BD08-5166-4FCB-97D0-84FBA872FFC4@ostorage.com.cn> <5B5E845C-A3D1-436E-BDC9-846257587357@ostorage.com.cn> <5F134369-41C0-4AAA-8E49-8D921AF524FA@ostorage.com.cn> <5B10DA62.9010106@lab.ntt.co.jp> Message-ID: Hi Kota, Thanks for the response. When I specify the URL as http://s3server:8080/testbucket, it throws back a SignatureDoesNotMatch error. eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks --createBucket -- http://s3server:8080/testbucket s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; query=; s3curl: cname endpoint signing case s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 +0000\n/s3server/testbucket' s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +0000' -H 'Authorization: AWS 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H 'content-type: ' --data-binary -X PUT http://s3server:8080/testbucket * Trying 20.20.20.229... * TCP_NODELAY set * Connected to s3server (20.20.20.229) port 8080 (#0) > PUT /testbucket HTTP/1.1 > Host: s3server:8080 > User-Agent: curl/7.58.0 > Accept: */* > Date: Fri, 01 Jun 2018 05:47:53 +0000 > Authorization: AWS 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA= > Content-Length: 0 > < HTTP/1.1 403 Forbidden < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09 < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09 < Content-Type: application/xml < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 < Date: Fri, 01 Jun 2018 05:47:53 GMT < Transfer-Encoding: chunked * HTTP error before end of send, stop sending < * Closing connection 0 SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.tx5c2ac9ea26a046ac96e4d-005b10de09 Regards, Shyam On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI < tsuyuzaki.kota at lab.ntt.co.jp> wrote: > Hi Shyam, > > You should specify the path starts from bucket. It will be like > > http://20.20.20.229:8080/testBucket > > assuming you didn't configure virtual-hosted style. > Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_ > dc86f7d8787b46158268bd77098b6578, > swift3 doesn't require the account in the path so far as well as actual > amazon s3. > > Best, > Kota > > (2018/05/31 21:33), Shyam Prasad N wrote: > > Hi Yuxin, > > > > Thank you for sharing your configs. > > So I've managed to get past the Signature not matching error. > > > > Now the error is different. InvalidbucketName: > > > > eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks > > --createBucket -- > > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 > 78/testBucket > > s3curl: Found the url: host=20.20.20.229; port=8080; > > uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=; > > s3curl: cname endpoint signing case > > s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +0000\n/ > > 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket' > > s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +0000' -H > > 'Authorization: AWS > > 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H > > 'content-type: ' --data-binary -X PUT > > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 > 78/testBucket > > * Trying 20.20.20.229... > > * TCP_NODELAY set > > * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0) > >> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1 > >> Host: 20.20.20.229:8080 > >> User-Agent: curl/7.58.0 > >> Accept: */* > >> Date: Thu, 31 May 2018 12:02:57 +0000 > >> Authorization: AWS > > 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0= > >> Content-Length: 0 > >> > > < HTTP/1.1 400 Bad Request > > < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471 > > < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471 > > < Content-Type: application/xml > > < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471 > > < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471 > > < Date: Thu, 31 May 2018 12:02:57 GMT > > < Transfer-Encoding: chunked > > * HTTP error before end of send, stop sending > > < > > > > * Closing connection 0 > > InvalidBucketNameThe specified bucket is > not > > valid.tx18266052d5044eb2a3bc7- > 005b0fe471v1 Error>eightkpc at objectstore1:~/s3curl$ > > > > > > My specified endpoint is > > http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578 > > What am I doing wrong? > > > > Regards, > > Shyam > > > > On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang > > wrote: > > > >> Hi Shyam, > >> > >> No problem. The output of the commands is attached. > >> > >> And my test cluster is on Swift v2.15.1 with Swift3 v1.12 > >> > >> Also, here is the common process when I'm creating an S3 credential and > >> using in s3curl. Hope it helps. > >> > >> 1. Create a user and a project, and assign a proper role. > >> > >> openstack project create testproject > >> openstack user create testuser --password 123 > >> openstack role add --project testproject --user testuser _member_ > >> > >> 2. Check accessibility to swift > >> > >> create a test-openrc file with above info > >> source test-openrc > >> swift list > >> > >> 3.Create a credential > >> > >> openstack credential create --type ec2 --project testproject testuser > >> '{"access": "testaccess", "secret": "testsecret"}' > >> > >> 4. Use it in s3curl > >> > >> add the endpoint url to `my @endpoints` in s3curl.pl > >> add the credential to .s3curl config file > >> > >> do `s3curl.pl -i cred_name --debug -- http://endpoint -X GET` > >> > >> > >> > >> > >> 在 2018年5月25日,18:17,Shyam Prasad N 写道: > >> > >> Hi Yuxin, > >> > >> If you don't mind, can you share the output of the following commands in > >> your running swift3 setup? > >> > >> openstack credential list > >> openstack ec2 credentials list > >> cat /etc/swift/proxy-server.conf > >> > >> Also, what are the access keys and secret keys that you use? > >> I want to make sure that I'm not missing anything in configuration. > >> > >> Regards, > >> Shyam > >> > >> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N > > >> wrote: > >> > >>> Tried that. Unfortunately same error. > >>> Is there anything I can do to troubleshoot this? > >>> > >>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang < > wang.yuxin at ostorage.com.cn> > >>> wrote: > >>> > >>>> They can be any strings. > >>>> > >>>> Replace them with whatever you want. > >>>> > >>>> - Yuxin > >>>> > >>>> 在 2018年5月25日,14:57,Shyam Prasad N 写道: > >>>> > >>>> Thanks. I'll try this. > >>>> But what values do I use in place of ak and sk? I want to use some > >>>> command to get those values, right? > >>>> > >>>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang < > wang.yuxin at ostorage.com.cn> > >>>> wrote: > >>>> > >>>>> I created ec2 credentials using command `openstack credential > create`. > >>>>> > >>>>> i.e. > >>>>> > >>>>> openstack credential create --type ec2 --project proj user > '{"access": > >>>>> "ak", "secret": "sk”}' > >>>>> > >>>>> > >>>>> It seems the two credentials are not the same thing. > >>>>> > >>>>> Ref: > >>>>> > >>>>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/ > >>>>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta > >>>>> ckEC2credentials.htm > >>>>> https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter% > 2Fen%2FSTXKQY_4.1.1%2Fcom.ibm.spectrum.scale.v4r11.adv.doc%2Fbl1adv_ > ConfigureOpenstackEC2credentials.htm&data=02%7C01%7C% > 7Cc6d4af73a0fd4208f9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa > aaaa%7C1%7C0%7C636628292198191185&sdata=cBwi02p2zc3db3%2Bp8PDvrgAZ2% > 2FkqjB6wnuW%2FEt0zWPA%3D&reserved=0> > >>>>> > >>>>> 在 2018年5月25日,10:32,Shyam Prasad N 写道: > >>>>> > >>>>> Yes, I did. > >>>>> I don't think this is s3curl related issue, because I tried with > python > >>>>> AWS SDK, and got the same error. > >>>>> > >>>>> On Fri, May 25, 2018, 07:42 Yuxin Wang > >>>>> wrote: > >>>>> > >>>>>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl > >>>>>> http%3A%2F%2Fs3curl.pl%2F&data=02%7C01%7C%7Cc6d4af73a0fd4208f9ac08d5c20f > 0a30%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0% > 7C636628292198191185&sdata=nr9HL8HskZJ8OwCfpuU2pKg7% > 2FPnzWhTD1b4wEi02o5A%3D&reserved=0> > >>>>>> ? > >>>>>> > >>>>>> i.e. > >>>>>> > >>>>>> my @endpoints = (‘127.0.0.1’); > >>>>>> > >>>>>> 在 2018年5月24日,19:48,Shyam Prasad N 写道: > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I've been trying to get swift3 to work for several days now. But I > >>>>>> haven't managed to get it running. > >>>>>> Both with tempauth and keystoneauth, I'm getting the same error: > >>>>>> > >>>>>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl > >>>>>> http%3A%2F%2Fs3curl.pl&data=02%7C01%7C%7C39742b8c6bf847ee381508d5c16d1b21% > 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636627596701206160&sdata= > lZmKF41unLVD9J1ALYUv8Vkab448NOeGmcWcR56Rgxs%3D&reserved=0> > >>>>>> --id=testerks -- http://127.0.0.1:8080/ > >>>>>> http%3A%2F%2F127.0.0.1%3A8080%2F&data=02%7C01%7C% > 7C39742b8c6bf847ee381508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa > aaaa%7C1%7C0%7C636627596701206160&sdata=CEHEVR1HSpK0ehQ8mmOBA7fmjQsu7v > jqKZda3NYVDWQ%3D&reserved=0> > >>>>>> > >>>>>> SignatureDoesNotMatchThe request > >>>>>> signature we calculated does not match the signature you provided. > Check > >>>>>> your key and signing method.tx > >>>>>> a691e7ca97a44d56bc4c2-005b06a292 > >>>>>> > >>>>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1 > >>>>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 - > >>>>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - > 1527161490.543112040 > >>>>>> 1527161490.563107014 - > >>>>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - - > >>>>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn: > >>>>>> txa691e7ca97a44d56bc4c2-005b06a292) > >>>>>> > >>>>>> eightkpc at objectstore1:~$ cat .s3curl > >>>>>> %awsSecretAccessKeys = ( > >>>>>> tester => { > >>>>>> id => 'test:tester', > >>>>>> key => 'testing', > >>>>>> }, > >>>>>> testerks => { > >>>>>> id => 'e6289a1b5692461388d0597a4873d054', > >>>>>> key => '88bb706887094696b082f008ba133ad7', > >>>>>> }, > >>>>>> ); > >>>>>> > >>>>>> eightkpc at objectstore1:~$ openstack ec2 credentials show > >>>>>> e6289a1b5692461388d0597a4873d054 > >>>>>> +------------+---------------------------------------------- > >>>>>> ------------------------------------------------------------ > >>>>>> --------------------------+ > >>>>>> | Field | Value > >>>>>> > >>>>>> | > >>>>>> +------------+---------------------------------------------- > >>>>>> ------------------------------------------------------------ > >>>>>> --------------------------+ > >>>>>> | access | e6289a1b5692461388d0597a4873d0 > >>>>>> 54 > >>>>>> | > >>>>>> | links | {u'self': u'http://controller:5000/v3/us > >>>>>> ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628 > >>>>>> 9a1b5692461388d0597a4873d054'} | > >>>>>> | project_id | dc86f7d8787b46158268bd77098b65 > >>>>>> 78 > >>>>>> | > >>>>>> | secret | 88bb706887094696b082f008ba133a > >>>>>> d7 > >>>>>> | > >>>>>> | trust_id | None > >>>>>> > >>>>>> | > >>>>>> | user_id | d7df7b56343b4ea988869fc30efeda > >>>>>> 09 > >>>>>> | > >>>>>> +------------+---------------------------------------------- > >>>>>> ------------------------------------------------------------ > >>>>>> --------------------------+ > >>>>>> > >>>>>> Can someone please let me know what is going on? > >>>>>> > >>>>>> Regards, > >>>>>> Shyam > >>>>>> _______________________________________________ > >>>>>> Mailing list: https://eur03.safelinks.protection.outlook.com/?url= > >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 > >>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa > >>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI > >>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 > >>>>>> Post to : openstack at lists.openstack.org > >>>>>> Unsubscribe : https://eur03.safelinks.protection.outlook.com/?url= > >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 > >>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa > >>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI > >>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> -Shyam > >>>> _______________________________________________ > >>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= > >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f > >>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa > >>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% > >>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 > >>>> Post to : openstack at lists.openstack.org > >>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= > >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f > >>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa > >>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% > >>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 > >>>> > >>>> > >>>> > >>> > >>> > >>> -- > >>> -Shyam > >>> > >> > >> > >> > >> -- > >> -Shyam > >> _______________________________________________ > >> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= > >> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a > 5c90% > >> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910462&sdata=% > >> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 > >> Post to : openstack at lists.openstack.org > >> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= > >> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a > 5c90% > >> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910462&sdata=% > >> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 > >> > >> > >> > >> > > > > > > > > > > _______________________________________________ > > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > Post to : openstack at lists.openstack.org > > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > > > > > -- -Shyam -------------- next part -------------- An HTML attachment was scrubbed... URL: From tsuyuzaki.kota at lab.ntt.co.jp Fri Jun 1 08:01:00 2018 From: tsuyuzaki.kota at lab.ntt.co.jp (Kota TSUYUZAKI) Date: Fri, 01 Jun 2018 17:01:00 +0900 Subject: [Openstack] Struggling to get the s3 api interface to work with swift. In-Reply-To: References: <2925BD08-5166-4FCB-97D0-84FBA872FFC4@ostorage.com.cn> <5B5E845C-A3D1-436E-BDC9-846257587357@ostorage.com.cn> <5F134369-41C0-4AAA-8E49-8D921AF524FA@ostorage.com.cn> <5B10DA62.9010106@lab.ntt.co.jp> Message-ID: <5B10FD3C.7080508@lab.ntt.co.jp> Hi Shyam, > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 > +0000\n/s3server/testbucket' It looks like your StringToSign doesn't include correct info for your request.(e.g. resource should be only "/testbucket") See https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html for more info. Your request should be: > * Connected to s3server (20.20.20.229) port 8080 (#0) >> PUT /testbucket HTTP/1.1 >> Host: s3server:8080 >> User-Agent: curl/7.58.0 >> Accept: */* >> Date: Fri, 01 Jun 2018 05:47:53 +0000 >> Authorization: AWS > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA= >> Content-Length: 0 then, the string to sign should include the info corretly. Looking at s3curl code, it looks to fall into cname case? https://github.com/scality/S3/blob/master/tests/functional/s3curl/s3curl.pl#L311-L328 Once I played with s3curl the request with ordinary endpoint signing case worked correctly. Again, I'm not an expert of s3curl so no idea why your setting went to the cname case tho. Best, Kota (2018/06/01 14:49), Shyam Prasad N wrote: > Hi Kota, > > Thanks for the response. > When I specify the URL as http://s3server:8080/testbucket, it throws back a > SignatureDoesNotMatch error. > > eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks > --createBucket -- http://s3server:8080/testbucket > s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; query=; > s3curl: cname endpoint signing case > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 > +0000\n/s3server/testbucket' > s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +0000' -H > 'Authorization: AWS > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H > 'content-type: ' --data-binary -X PUT http://s3server:8080/testbucket > * Trying 20.20.20.229... > * TCP_NODELAY set > * Connected to s3server (20.20.20.229) port 8080 (#0) >> PUT /testbucket HTTP/1.1 >> Host: s3server:8080 >> User-Agent: curl/7.58.0 >> Accept: */* >> Date: Fri, 01 Jun 2018 05:47:53 +0000 >> Authorization: AWS > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA= >> Content-Length: 0 >> > < HTTP/1.1 403 Forbidden > < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09 > < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09 > < Content-Type: application/xml > < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 > < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 > < Date: Fri, 01 Jun 2018 05:47:53 GMT > < Transfer-Encoding: chunked > * HTTP error before end of send, stop sending > < > > * Closing connection 0 > SignatureDoesNotMatchThe request signature we > calculated does not match the signature you provided. Check your key and > signing > method.tx5c2ac9ea26a046ac96e4d-005b10de09 > > Regards, > Shyam > > On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI < > tsuyuzaki.kota at lab.ntt.co.jp> wrote: > >> Hi Shyam, >> >> You should specify the path starts from bucket. It will be like >> >> http://20.20.20.229:8080/testBucket >> >> assuming you didn't configure virtual-hosted style. >> Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_ >> dc86f7d8787b46158268bd77098b6578, >> swift3 doesn't require the account in the path so far as well as actual >> amazon s3. >> >> Best, >> Kota >> >> (2018/05/31 21:33), Shyam Prasad N wrote: >>> Hi Yuxin, >>> >>> Thank you for sharing your configs. >>> So I've managed to get past the Signature not matching error. >>> >>> Now the error is different. InvalidbucketName: >>> >>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks >>> --createBucket -- >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 >> 78/testBucket >>> s3curl: Found the url: host=20.20.20.229; port=8080; >>> uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=; >>> s3curl: cname endpoint signing case >>> s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +0000\n/ >>> 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket' >>> s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +0000' -H >>> 'Authorization: AWS >>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H >>> 'content-type: ' --data-binary -X PUT >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 >> 78/testBucket >>> * Trying 20.20.20.229... >>> * TCP_NODELAY set >>> * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0) >>>> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1 >>>> Host: 20.20.20.229:8080 >>>> User-Agent: curl/7.58.0 >>>> Accept: */* >>>> Date: Thu, 31 May 2018 12:02:57 +0000 >>>> Authorization: AWS >>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0= >>>> Content-Length: 0 >>>> >>> < HTTP/1.1 400 Bad Request >>> < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471 >>> < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471 >>> < Content-Type: application/xml >>> < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471 >>> < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471 >>> < Date: Thu, 31 May 2018 12:02:57 GMT >>> < Transfer-Encoding: chunked >>> * HTTP error before end of send, stop sending >>> < >>> >>> * Closing connection 0 >>> InvalidBucketNameThe specified bucket is >> not >>> valid.tx18266052d5044eb2a3bc7- >> 005b0fe471v1> Error>eightkpc at objectstore1:~/s3curl$ >>> >>> >>> My specified endpoint is >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578 >>> What am I doing wrong? >>> >>> Regards, >>> Shyam >>> >>> On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang >>> wrote: >>> >>>> Hi Shyam, >>>> >>>> No problem. The output of the commands is attached. >>>> >>>> And my test cluster is on Swift v2.15.1 with Swift3 v1.12 >>>> >>>> Also, here is the common process when I'm creating an S3 credential and >>>> using in s3curl. Hope it helps. >>>> >>>> 1. Create a user and a project, and assign a proper role. >>>> >>>> openstack project create testproject >>>> openstack user create testuser --password 123 >>>> openstack role add --project testproject --user testuser _member_ >>>> >>>> 2. Check accessibility to swift >>>> >>>> create a test-openrc file with above info >>>> source test-openrc >>>> swift list >>>> >>>> 3.Create a credential >>>> >>>> openstack credential create --type ec2 --project testproject testuser >>>> '{"access": "testaccess", "secret": "testsecret"}' >>>> >>>> 4. Use it in s3curl >>>> >>>> add the endpoint url to `my @endpoints` in s3curl.pl >>>> add the credential to .s3curl config file >>>> >>>> do `s3curl.pl -i cred_name --debug -- http://endpoint -X GET` >>>> >>>> >>>> >>>> >>>> 在 2018年5月25日,18:17,Shyam Prasad N 写道: >>>> >>>> Hi Yuxin, >>>> >>>> If you don't mind, can you share the output of the following commands in >>>> your running swift3 setup? >>>> >>>> openstack credential list >>>> openstack ec2 credentials list >>>> cat /etc/swift/proxy-server.conf >>>> >>>> Also, what are the access keys and secret keys that you use? >>>> I want to make sure that I'm not missing anything in configuration. >>>> >>>> Regards, >>>> Shyam >>>> >>>> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N >> >>>> wrote: >>>> >>>>> Tried that. Unfortunately same error. >>>>> Is there anything I can do to troubleshoot this? >>>>> >>>>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang < >> wang.yuxin at ostorage.com.cn> >>>>> wrote: >>>>> >>>>>> They can be any strings. >>>>>> >>>>>> Replace them with whatever you want. >>>>>> >>>>>> - Yuxin >>>>>> >>>>>> 在 2018年5月25日,14:57,Shyam Prasad N 写道: >>>>>> >>>>>> Thanks. I'll try this. >>>>>> But what values do I use in place of ak and sk? I want to use some >>>>>> command to get those values, right? >>>>>> >>>>>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang < >> wang.yuxin at ostorage.com.cn> >>>>>> wrote: >>>>>> >>>>>>> I created ec2 credentials using command `openstack credential >> create`. >>>>>>> >>>>>>> i.e. >>>>>>> >>>>>>> openstack credential create --type ec2 --project proj user >> '{"access": >>>>>>> "ak", "secret": "sk”}' >>>>>>> >>>>>>> >>>>>>> It seems the two credentials are not the same thing. >>>>>>> >>>>>>> Ref: >>>>>>> >>>>>>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/ >>>>>>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta >>>>>>> ckEC2credentials.htm >>>>>>> > https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter% >> 2Fen%2FSTXKQY_4.1.1%2Fcom.ibm.spectrum.scale.v4r11.adv.doc%2Fbl1adv_ >> ConfigureOpenstackEC2credentials.htm&data=02%7C01%7C% >> 7Cc6d4af73a0fd4208f9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >> aaaa%7C1%7C0%7C636628292198191185&sdata=cBwi02p2zc3db3%2Bp8PDvrgAZ2% >> 2FkqjB6wnuW%2FEt0zWPA%3D&reserved=0> >>>>>>> >>>>>>> 在 2018年5月25日,10:32,Shyam Prasad N 写道: >>>>>>> >>>>>>> Yes, I did. >>>>>>> I don't think this is s3curl related issue, because I tried with >> python >>>>>>> AWS SDK, and got the same error. >>>>>>> >>>>>>> On Fri, May 25, 2018, 07:42 Yuxin Wang >>>>>>> wrote: >>>>>>> >>>>>>>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl >>>>>>>> > http%3A%2F%2Fs3curl.pl%2F&data=02%7C01%7C%7Cc6d4af73a0fd4208f9ac08d5c20f >> 0a30%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0% >> 7C636628292198191185&sdata=nr9HL8HskZJ8OwCfpuU2pKg7% >> 2FPnzWhTD1b4wEi02o5A%3D&reserved=0> >>>>>>>> ? >>>>>>>> >>>>>>>> i.e. >>>>>>>> >>>>>>>> my @endpoints = (‘127.0.0.1’); >>>>>>>> >>>>>>>> 在 2018年5月24日,19:48,Shyam Prasad N 写道: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I've been trying to get swift3 to work for several days now. But I >>>>>>>> haven't managed to get it running. >>>>>>>> Both with tempauth and keystoneauth, I'm getting the same error: >>>>>>>> >>>>>>>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl >>>>>>>> > http%3A%2F%2Fs3curl.pl&data=02%7C01%7C%7C39742b8c6bf847ee381508d5c16d1b21% >> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636627596701206160&sdata= >> lZmKF41unLVD9J1ALYUv8Vkab448NOeGmcWcR56Rgxs%3D&reserved=0> >>>>>>>> --id=testerks -- http://127.0.0.1:8080/ >>>>>>>> > http%3A%2F%2F127.0.0.1%3A8080%2F&data=02%7C01%7C% >> 7C39742b8c6bf847ee381508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >> aaaa%7C1%7C0%7C636627596701206160&sdata=CEHEVR1HSpK0ehQ8mmOBA7fmjQsu7v >> jqKZda3NYVDWQ%3D&reserved=0> >>>>>>>> >>>>>>>> SignatureDoesNotMatchThe request >>>>>>>> signature we calculated does not match the signature you provided. >> Check >>>>>>>> your key and signing method.tx >>>>>>>> a691e7ca97a44d56bc4c2-005b06a292 >>>>>>>> >>>>>>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1 >>>>>>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 - >>>>>>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - >> 1527161490.543112040 >>>>>>>> 1527161490.563107014 - >>>>>>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - - >>>>>>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn: >>>>>>>> txa691e7ca97a44d56bc4c2-005b06a292) >>>>>>>> >>>>>>>> eightkpc at objectstore1:~$ cat .s3curl >>>>>>>> %awsSecretAccessKeys = ( >>>>>>>> tester => { >>>>>>>> id => 'test:tester', >>>>>>>> key => 'testing', >>>>>>>> }, >>>>>>>> testerks => { >>>>>>>> id => 'e6289a1b5692461388d0597a4873d054', >>>>>>>> key => '88bb706887094696b082f008ba133ad7', >>>>>>>> }, >>>>>>>> ); >>>>>>>> >>>>>>>> eightkpc at objectstore1:~$ openstack ec2 credentials show >>>>>>>> e6289a1b5692461388d0597a4873d054 >>>>>>>> +------------+---------------------------------------------- >>>>>>>> ------------------------------------------------------------ >>>>>>>> --------------------------+ >>>>>>>> | Field | Value >>>>>>>> >>>>>>>> | >>>>>>>> +------------+---------------------------------------------- >>>>>>>> ------------------------------------------------------------ >>>>>>>> --------------------------+ >>>>>>>> | access | e6289a1b5692461388d0597a4873d0 >>>>>>>> 54 >>>>>>>> | >>>>>>>> | links | {u'self': u'http://controller:5000/v3/us >>>>>>>> ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628 >>>>>>>> 9a1b5692461388d0597a4873d054'} | >>>>>>>> | project_id | dc86f7d8787b46158268bd77098b65 >>>>>>>> 78 >>>>>>>> | >>>>>>>> | secret | 88bb706887094696b082f008ba133a >>>>>>>> d7 >>>>>>>> | >>>>>>>> | trust_id | None >>>>>>>> >>>>>>>> | >>>>>>>> | user_id | d7df7b56343b4ea988869fc30efeda >>>>>>>> 09 >>>>>>>> | >>>>>>>> +------------+---------------------------------------------- >>>>>>>> ------------------------------------------------------------ >>>>>>>> --------------------------+ >>>>>>>> >>>>>>>> Can someone please let me know what is going on? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Shyam >>>>>>>> _______________________________________________ >>>>>>>> Mailing list: https://eur03.safelinks.protection.outlook.com/?url= >>>>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 >>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >>>>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI >>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 >>>>>>>> Post to : openstack at lists.openstack.org >>>>>>>> Unsubscribe : https://eur03.safelinks.protection.outlook.com/?url= >>>>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 >>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >>>>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI >>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> -Shyam >>>>>> _______________________________________________ >>>>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f >>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >>>>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% >>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 >>>>>> Post to : openstack at lists.openstack.org >>>>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f >>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >>>>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% >>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> -Shyam >>>>> >>>> >>>> >>>> >>>> -- >>>> -Shyam >>>> _______________________________________________ >>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a >> 5c90% >>>> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910462&sdata=% >>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 >>>> Post to : openstack at lists.openstack.org >>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a >> 5c90% >>>> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910462&sdata=% >>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> _______________________________________________ >>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ >> openstack >>> Post to : openstack at lists.openstack.org >>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ >> openstack >>> >> >> >> >> > > From wang.yuxin at ostorage.com.cn Fri Jun 1 10:44:53 2018 From: wang.yuxin at ostorage.com.cn (Yuxin Wang) Date: Fri, 1 Jun 2018 18:44:53 +0800 Subject: [Openstack] Struggling to get the s3 api interface to work with swift. In-Reply-To: References: <2925BD08-5166-4FCB-97D0-84FBA872FFC4@ostorage.com.cn> <5B5E845C-A3D1-436E-BDC9-846257587357@ostorage.com.cn> <5F134369-41C0-4AAA-8E49-8D921AF524FA@ostorage.com.cn> Message-ID: <4F278A60-5260-4384-AF3D-00509280F759@ostorage.com.cn> Hi Shyam, It’s like what Kota said about StringToSign. And I think the point is that the host isn't equal to one of the endpoints listed(https://github.com/scality/S3/blob/master/tests/functional/s3curl/s3curl.pl#L32 ), and it isn't the subdomain case too. So it goes to the cname case, where it’ll add an additional "/$host”. You could try adding “s3server” to the endpoint list. Like: ``` my @endpoints = ( ' 20.20.20.229', '127.0.0.1’, ‘s3server' ); ``` Yuxin -------------- next part -------------- An HTML attachment was scrubbed... URL: From nspmangalore at gmail.com Fri Jun 1 11:32:16 2018 From: nspmangalore at gmail.com (Shyam Prasad N) Date: Fri, 1 Jun 2018 17:02:16 +0530 Subject: [Openstack] Struggling to get the s3 api interface to work with swift. In-Reply-To: <5B10FD3C.7080508@lab.ntt.co.jp> References: <2925BD08-5166-4FCB-97D0-84FBA872FFC4@ostorage.com.cn> <5B5E845C-A3D1-436E-BDC9-846257587357@ostorage.com.cn> <5F134369-41C0-4AAA-8E49-8D921AF524FA@ostorage.com.cn> <5B10DA62.9010106@lab.ntt.co.jp> <5B10FD3C.7080508@lab.ntt.co.jp> Message-ID: Hi Kota, I tried with the changes you suggested. It gives me the old error again... eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks -- http://s3server:8080 s3curl: Found the url: host=s3server; port=8080; uri=; query=; s3curl: s3server s3curl: s3server s3curl: ordinary endpoint signing case s3curl: StringToSign='GET\n\n\nFri, 01 Jun 2018 11:31:50 +0000\n/' s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 11:31:50 +0000' -H 'Authorization: AWS 76498e1413284b9d961d452db608dff4:X1vdAhaZ4KyuM5LpMVc21ZQaGuA=' -L -H 'content-type: ' http://s3server:8080 * Rebuilt URL to: http://s3server:8080/ * Trying 20.20.20.229... * TCP_NODELAY set * Connected to s3server (20.20.20.229) port 8080 (#0) > GET / HTTP/1.1 > Host: s3server:8080 > User-Agent: curl/7.58.0 > Accept: */* > Date: Fri, 01 Jun 2018 11:31:50 +0000 > Authorization: AWS 76498e1413284b9d961d452db608dff4:X1vdAhaZ4KyuM5LpMVc21ZQaGuA= > < HTTP/1.1 403 Forbidden < x-amz-id-2: txbdd2940942ce49509226d-005b112ea6 < x-amz-request-id: txbdd2940942ce49509226d-005b112ea6 < Content-Type: application/xml < X-Trans-Id: txbdd2940942ce49509226d-005b112ea6 < X-Openstack-Request-Id: txbdd2940942ce49509226d-005b112ea6 < Date: Fri, 01 Jun 2018 11:31:50 GMT < Transfer-Encoding: chunked < * Connection #0 to host s3server left intact SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.txbdd2940942ce49509226d-005b112ea6 On Fri, Jun 1, 2018 at 1:31 PM, Kota TSUYUZAKI wrote: > Hi Shyam, > > > > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 > > +0000\n/s3server/testbucket' > > It looks like your StringToSign doesn't include correct info for your > request.(e.g. resource should be only "/testbucket") > See https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4- > header-based-auth.html for more info. > > Your request should be: > > > * Connected to s3server (20.20.20.229) port 8080 (#0) > >> PUT /testbucket HTTP/1.1 > >> Host: s3server:8080 > >> User-Agent: curl/7.58.0 > >> Accept: */* > >> Date: Fri, 01 Jun 2018 05:47:53 +0000 > >> Authorization: AWS > > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA= > >> Content-Length: 0 > > then, the string to sign should include the info corretly. > > Looking at s3curl code, it looks to fall into cname case? > > https://github.com/scality/S3/blob/master/tests/functional/ > s3curl/s3curl.pl#L311-L328 > > Once I played with s3curl the request with ordinary endpoint signing case > worked correctly. > Again, I'm not an expert of s3curl so no idea why your setting went to the > cname case tho. > > Best, > Kota > > (2018/06/01 14:49), Shyam Prasad N wrote: > > Hi Kota, > > > > Thanks for the response. > > When I specify the URL as http://s3server:8080/testbucket, it throws > back a > > SignatureDoesNotMatch error. > > > > eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks > > --createBucket -- http://s3server:8080/testbucket > > s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; query=; > > s3curl: cname endpoint signing case > > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 > > +0000\n/s3server/testbucket' > > s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +0000' -H > > 'Authorization: AWS > > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H > > 'content-type: ' --data-binary -X PUT http://s3server:8080/testbucket > > * Trying 20.20.20.229... > > * TCP_NODELAY set > > * Connected to s3server (20.20.20.229) port 8080 (#0) > >> PUT /testbucket HTTP/1.1 > >> Host: s3server:8080 > >> User-Agent: curl/7.58.0 > >> Accept: */* > >> Date: Fri, 01 Jun 2018 05:47:53 +0000 > >> Authorization: AWS > > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA= > >> Content-Length: 0 > >> > > < HTTP/1.1 403 Forbidden > > < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09 > > < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09 > > < Content-Type: application/xml > > < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 > > < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 > > < Date: Fri, 01 Jun 2018 05:47:53 GMT > > < Transfer-Encoding: chunked > > * HTTP error before end of send, stop sending > > < > > > > * Closing connection 0 > > SignatureDoesNotMatchThe request signature > we > > calculated does not match the signature you provided. Check your key and > > signing > > method.tx5c2ac9ea26a046ac96e4d- > 005b10de09 > > > > Regards, > > Shyam > > > > On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI < > > tsuyuzaki.kota at lab.ntt.co.jp> wrote: > > > >> Hi Shyam, > >> > >> You should specify the path starts from bucket. It will be like > >> > >> http://20.20.20.229:8080/testBucket > >> > >> assuming you didn't configure virtual-hosted style. > >> Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_ > >> dc86f7d8787b46158268bd77098b6578, > >> swift3 doesn't require the account in the path so far as well as actual > >> amazon s3. > >> > >> Best, > >> Kota > >> > >> (2018/05/31 21:33), Shyam Prasad N wrote: > >>> Hi Yuxin, > >>> > >>> Thank you for sharing your configs. > >>> So I've managed to get past the Signature not matching error. > >>> > >>> Now the error is different. InvalidbucketName: > >>> > >>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks > >>> --createBucket -- > >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 > >> 78/testBucket > >>> s3curl: Found the url: host=20.20.20.229; port=8080; > >>> uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=; > >>> s3curl: cname endpoint signing case > >>> s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +0000\n/ > >>> 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket' > >>> s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +0000' -H > >>> 'Authorization: AWS > >>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H > >>> 'content-type: ' --data-binary -X PUT > >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 > >> 78/testBucket > >>> * Trying 20.20.20.229... > >>> * TCP_NODELAY set > >>> * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0) > >>>> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1 > >>>> Host: 20.20.20.229:8080 > >>>> User-Agent: curl/7.58.0 > >>>> Accept: */* > >>>> Date: Thu, 31 May 2018 12:02:57 +0000 > >>>> Authorization: AWS > >>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0= > >>>> Content-Length: 0 > >>>> > >>> < HTTP/1.1 400 Bad Request > >>> < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471 > >>> < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471 > >>> < Content-Type: application/xml > >>> < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471 > >>> < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471 > >>> < Date: Thu, 31 May 2018 12:02:57 GMT > >>> < Transfer-Encoding: chunked > >>> * HTTP error before end of send, stop sending > >>> < > >>> > >>> * Closing connection 0 > >>> InvalidBucketNameThe specified bucket is > >> not > >>> valid.tx18266052d5044eb2a3bc7- > >> 005b0fe471v1 >> Error>eightkpc at objectstore1:~/s3curl$ > >>> > >>> > >>> My specified endpoint is > >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578 > >>> What am I doing wrong? > >>> > >>> Regards, > >>> Shyam > >>> > >>> On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang < > wang.yuxin at ostorage.com.cn> > >>> wrote: > >>> > >>>> Hi Shyam, > >>>> > >>>> No problem. The output of the commands is attached. > >>>> > >>>> And my test cluster is on Swift v2.15.1 with Swift3 v1.12 > >>>> > >>>> Also, here is the common process when I'm creating an S3 credential > and > >>>> using in s3curl. Hope it helps. > >>>> > >>>> 1. Create a user and a project, and assign a proper role. > >>>> > >>>> openstack project create testproject > >>>> openstack user create testuser --password 123 > >>>> openstack role add --project testproject --user testuser _member_ > >>>> > >>>> 2. Check accessibility to swift > >>>> > >>>> create a test-openrc file with above info > >>>> source test-openrc > >>>> swift list > >>>> > >>>> 3.Create a credential > >>>> > >>>> openstack credential create --type ec2 --project testproject testuser > >>>> '{"access": "testaccess", "secret": "testsecret"}' > >>>> > >>>> 4. Use it in s3curl > >>>> > >>>> add the endpoint url to `my @endpoints` in s3curl.pl > >>>> add the credential to .s3curl config file > >>>> > >>>> do `s3curl.pl -i cred_name --debug -- http://endpoint -X GET` > >>>> > >>>> > >>>> > >>>> > >>>> 在 2018年5月25日,18:17,Shyam Prasad N 写道: > >>>> > >>>> Hi Yuxin, > >>>> > >>>> If you don't mind, can you share the output of the following commands > in > >>>> your running swift3 setup? > >>>> > >>>> openstack credential list > >>>> openstack ec2 credentials list > >>>> cat /etc/swift/proxy-server.conf > >>>> > >>>> Also, what are the access keys and secret keys that you use? > >>>> I want to make sure that I'm not missing anything in configuration. > >>>> > >>>> Regards, > >>>> Shyam > >>>> > >>>> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N < > nspmangalore at gmail.com > >>> > >>>> wrote: > >>>> > >>>>> Tried that. Unfortunately same error. > >>>>> Is there anything I can do to troubleshoot this? > >>>>> > >>>>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang < > >> wang.yuxin at ostorage.com.cn> > >>>>> wrote: > >>>>> > >>>>>> They can be any strings. > >>>>>> > >>>>>> Replace them with whatever you want. > >>>>>> > >>>>>> - Yuxin > >>>>>> > >>>>>> 在 2018年5月25日,14:57,Shyam Prasad N 写道: > >>>>>> > >>>>>> Thanks. I'll try this. > >>>>>> But what values do I use in place of ak and sk? I want to use some > >>>>>> command to get those values, right? > >>>>>> > >>>>>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang < > >> wang.yuxin at ostorage.com.cn> > >>>>>> wrote: > >>>>>> > >>>>>>> I created ec2 credentials using command `openstack credential > >> create`. > >>>>>>> > >>>>>>> i.e. > >>>>>>> > >>>>>>> openstack credential create --type ec2 --project proj user > >> '{"access": > >>>>>>> "ak", "secret": "sk”}' > >>>>>>> > >>>>>>> > >>>>>>> It seems the two credentials are not the same thing. > >>>>>>> > >>>>>>> Ref: > >>>>>>> > >>>>>>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/ > >>>>>>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta > >>>>>>> ckEC2credentials.htm > >>>>>>> >> https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter% > >> 2Fen%2FSTXKQY_4.1.1%2Fcom.ibm.spectrum.scale.v4r11.adv.doc%2Fbl1adv_ > >> ConfigureOpenstackEC2credentials.htm&data=02%7C01%7C% > >> 7Cc6d4af73a0fd4208f9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa > >> aaaa%7C1%7C0%7C636628292198191185&sdata=cBwi02p2zc3db3%2Bp8PDvrgAZ2% > >> 2FkqjB6wnuW%2FEt0zWPA%3D&reserved=0> > >>>>>>> > >>>>>>> 在 2018年5月25日,10:32,Shyam Prasad N 写道: > >>>>>>> > >>>>>>> Yes, I did. > >>>>>>> I don't think this is s3curl related issue, because I tried with > >> python > >>>>>>> AWS SDK, and got the same error. > >>>>>>> > >>>>>>> On Fri, May 25, 2018, 07:42 Yuxin Wang > > >>>>>>> wrote: > >>>>>>> > >>>>>>>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl > >>>>>>>> >> http%3A%2F%2Fs3curl.pl%2F&data=02%7C01%7C% > 7Cc6d4af73a0fd4208f9ac08d5c20f > >> 0a30%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0% > >> 7C636628292198191185&sdata=nr9HL8HskZJ8OwCfpuU2pKg7% > >> 2FPnzWhTD1b4wEi02o5A%3D&reserved=0> > >>>>>>>> ? > >>>>>>>> > >>>>>>>> i.e. > >>>>>>>> > >>>>>>>> my @endpoints = (‘127.0.0.1’); > >>>>>>>> > >>>>>>>> 在 2018年5月24日,19:48,Shyam Prasad N 写道: > >>>>>>>> > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> I've been trying to get swift3 to work for several days now. But I > >>>>>>>> haven't managed to get it running. > >>>>>>>> Both with tempauth and keystoneauth, I'm getting the same error: > >>>>>>>> > >>>>>>>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl > >>>>>>>> >> http%3A%2F%2Fs3curl.pl&data=02%7C01%7C%7C39742b8c6bf847ee381508d5c16d > 1b21% > >> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636627596701206160&sdata= > >> lZmKF41unLVD9J1ALYUv8Vkab448NOeGmcWcR56Rgxs%3D&reserved=0> > >>>>>>>> --id=testerks -- http://127.0.0.1:8080/ > >>>>>>>> >> http%3A%2F%2F127.0.0.1%3A8080%2F&data=02%7C01%7C% > >> 7C39742b8c6bf847ee381508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa > >> aaaa%7C1%7C0%7C636627596701206160&sdata=CEHEVR1HSpK0ehQ8mmOBA7fmjQsu7v > >> jqKZda3NYVDWQ%3D&reserved=0> > >>>>>>>> > >>>>>>>> SignatureDoesNotMatchThe request > >>>>>>>> signature we calculated does not match the signature you provided. > >> Check > >>>>>>>> your key and signing method.tx > >>>>>>>> a691e7ca97a44d56bc4c2-005b06a292 > >>>>>>>> > >>>>>>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1 > >>>>>>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 - > >>>>>>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - > >> 1527161490.543112040 > >>>>>>>> 1527161490.563107014 - > >>>>>>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - - > >>>>>>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn: > >>>>>>>> txa691e7ca97a44d56bc4c2-005b06a292) > >>>>>>>> > >>>>>>>> eightkpc at objectstore1:~$ cat .s3curl > >>>>>>>> %awsSecretAccessKeys = ( > >>>>>>>> tester => { > >>>>>>>> id => 'test:tester', > >>>>>>>> key => 'testing', > >>>>>>>> }, > >>>>>>>> testerks => { > >>>>>>>> id => 'e6289a1b5692461388d0597a4873d054', > >>>>>>>> key => '88bb706887094696b082f008ba133ad7', > >>>>>>>> }, > >>>>>>>> ); > >>>>>>>> > >>>>>>>> eightkpc at objectstore1:~$ openstack ec2 credentials show > >>>>>>>> e6289a1b5692461388d0597a4873d054 > >>>>>>>> +------------+---------------------------------------------- > >>>>>>>> ------------------------------------------------------------ > >>>>>>>> --------------------------+ > >>>>>>>> | Field | Value > >>>>>>>> > >>>>>>>> | > >>>>>>>> +------------+---------------------------------------------- > >>>>>>>> ------------------------------------------------------------ > >>>>>>>> --------------------------+ > >>>>>>>> | access | e6289a1b5692461388d0597a4873d0 > >>>>>>>> 54 > >>>>>>>> | > >>>>>>>> | links | {u'self': u'http://controller:5000/v3/us > >>>>>>>> ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628 > >>>>>>>> 9a1b5692461388d0597a4873d054'} | > >>>>>>>> | project_id | dc86f7d8787b46158268bd77098b65 > >>>>>>>> 78 > >>>>>>>> | > >>>>>>>> | secret | 88bb706887094696b082f008ba133a > >>>>>>>> d7 > >>>>>>>> | > >>>>>>>> | trust_id | None > >>>>>>>> > >>>>>>>> | > >>>>>>>> | user_id | d7df7b56343b4ea988869fc30efeda > >>>>>>>> 09 > >>>>>>>> | > >>>>>>>> +------------+---------------------------------------------- > >>>>>>>> ------------------------------------------------------------ > >>>>>>>> --------------------------+ > >>>>>>>> > >>>>>>>> Can someone please let me know what is going on? > >>>>>>>> > >>>>>>>> Regards, > >>>>>>>> Shyam > >>>>>>>> _________________________________________ > ______ > >>>>>>>> Mailing list: https://eur03.safelinks. > protection.outlook.com/?url= > >>>>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 > >>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa > >>>>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI > >>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 > >>>>>>>> Post to : openstack at lists.openstack.org > >>>>>>>> Unsubscribe : https://eur03.safelinks. > protection.outlook.com/?url= > >>>>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 > >>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa > >>>>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI > >>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> -Shyam > >>>>>> _______________________________________________ > >>>>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= > >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f > >>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa > >>>>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% > >>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 > >>>>>> Post to : openstack at lists.openstack.org > >>>>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= > >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f > >>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa > >>>>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% > >>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> -Shyam > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> -Shyam > >>>> _______________________________________________ > >>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= > >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a > >> 5c90% > >>>> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0% > 7C636628409546910462&sdata=% > >>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 > >>>> Post to : openstack at lists.openstack.org > >>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= > >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% > >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3d08d5c22a > >> 5c90% > >>>> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0% > 7C636628409546910462&sdata=% > >>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > >> openstack > >>> Post to : openstack at lists.openstack.org > >>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > >> openstack > >>> > >> > >> > >> > >> > > > > > > > -- -Shyam -------------- next part -------------- An HTML attachment was scrubbed... URL: From abricus at yandex.ru Fri Jun 1 11:34:55 2018 From: abricus at yandex.ru (s serge) Date: Fri, 01 Jun 2018 14:34:55 +0300 Subject: [Openstack] designate question Message-ID: <898001527852895@web49g.yandex.ru> Hello, I've configured designate to listen neutron and nova notifications and everything works fine except one thing: I can't find a way to configure reverse lookup PTR record creation for nova fixed IP when instance launches. That's work perfectly for neutron floating but not for nova. Can you give me advice about what should be configured so PTR records will be generated for nova fixed ip ? Regards, Serge. From sombrafam at gmail.com Fri Jun 1 14:42:40 2018 From: sombrafam at gmail.com (Erlon Cruz) Date: Fri, 1 Jun 2018 11:42:40 -0300 Subject: [Openstack] cinder-volume can not live migration In-Reply-To: <1519353026.15482.2.camel@ezfly.com> References: <1519353026.15482.2.camel@ezfly.com> Message-ID: Hi Cheung, Can't figure out much from your logs. Its more likely to be an LVM thing. We haven't tested this scenario, as the tests we run only tests 1GB volumes for performace reasons. But why would someone create a volume bigger than that? :P Can you open a bug on launchpad? Describing the steps to reproduce. Erlon 2018-02-22 23:30 GMT-03:00 Cheung 楊禮銓 : > Dear: > > If the volume size is bigger than 50G, I can not live migration lvm volume. > > I am using openstack pike version. > > Do I miss something? > > [root at controller01: cinder]# cinder get-pools > +----------+--------------------------+ > | Property | Value | > +----------+--------------------------+ > | name | controller01 at lvm#LVM-SAS | > +----------+--------------------------+ > +----------+--------------------------+ > | Property | Value | > +----------+--------------------------+ > | name | controller02 at lvm#LVM-SAS | > +----------+--------------------------+ > > > [root at controller01: cinder]# openstack volume show > 1495b9e9-e56a-468b-a134-59b0a728fa00 > +--------------------------------+--------------------------------------+ > | Field | Value | > +--------------------------------+--------------------------------------+ > | attachments | [] | > | availability_zone | nova | > | bootable | false | > | consistencygroup_id | None | > | created_at | 2018-02-23T02:15:14.000000 | > | description | | > | encrypted | False | > | id | 1495b9e9-e56a-468b-a134-59b0a728fa00 | > | migration_status | error | > | multiattach | False | > | name | windows | > | os-vol-host-attr:host | controller01 at lvm#LVM-SAS | > | os-vol-mig-status-attr:migstat | error | > | os-vol-mig-status-attr:name_id | None | > | os-vol-tenant-attr:tenant_id | 963097c754bf40c5a077f2ae89be36c3 | > | properties | | > | replication_status | None | > | size | 51 | > | snapshot_id | None | > | source_volid | None | > | status | available | > | type | LVM-SAS | > | updated_at | 2018-02-23T02:18:47.000000 | > | user_id | 5bfa4f66825a40709e44a047bd251bcb | > +--------------------------------+--------------------------------------+ > > > > > > > -- > 本電子郵件及其所有附件所含之資訊均屬機密,僅供指定之收件人使用,未經寄件人同意不得揭露、複製或散布本電子郵件。若您並非指定之收件人,請勿使用、 > 保存或揭露本電子郵件之任何部分,並請立即通知寄件人並完全刪除本電子郵件。網路通訊可能含有病毒,收件人應自行確認本郵件是否安全,若因此造成損害,寄件人恕不負責。 > > > The information contained in this communication and attachment is > confidential and is intended only for the use of the recipient to which > this communication is addressed. Any disclosure, copying or distribution of > this communication without the sender's consents is strictly prohibited. If > you are not the intended recipient, please notify the sender and delete > this communication entirely without using, retaining, or disclosing any of > its contents. Internet communications cannot be guaranteed to be > virus-free. The recipient is responsible for ensuring that this > communication is virus free and the sender accepts no liability for any > damages caused by virus transmitted by this communication. > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matheus.wagner at ufba.br Fri Jun 1 15:11:05 2018 From: matheus.wagner at ufba.br (Matheus Wagner) Date: Fri, 1 Jun 2018 12:11:05 -0300 Subject: [Openstack] [Neutron] - Integration Ryu and OpenStack Message-ID: Good evening. My name is Matheus, I am a master's student at the Federal University of Bahia (UFBA) in Brazil. I am studying about OpenStack to do its integration with SDN, using the OpenFlow Ryu controller. In my experiments, I use the OpenStack version of Libert and created a VM with Ubuntu server 16.04 where I installed Ryu (https://github.com/osrg/ryu). The biggest problem is that I can not find materials to help me integrate my VM into the neutron. I would like to know if you have any practical material on how this integration is done within OpenStack (neutron), a tip from a book, video lesson, course, tutorial, step by step, anything, as it would help me a lot in the evolution of my research. Thank you. -- -- Abraço, *Matheus Wagner* -------------- next part -------------- An HTML attachment was scrubbed... URL: From explth at gmail.com Mon Jun 4 07:31:17 2018 From: explth at gmail.com (pen paul) Date: Mon, 4 Jun 2018 15:31:17 +0800 Subject: [Openstack] cerate network by rest api Message-ID: <5b14eac6.1c69fb81.340b7.331e@mx.google.com> Hi, I tried to create a network through the rest api, referenced the official documentation, tried to use the given request example, but all returned 400 errors. I use the VLAN transparency extension interface, the official document is Https://developer.openstack.org/api-ref/network/v2/#networks The request body like { "network": { "name": "sample_network", "admin_state_up": True } } Besides, the version of openstack is ocata,which build by devstack in Ubuntu. I don't know what went wrong, whether it was asking for a build or whether there was a problem with the platform itself. Thanks, -Pen 发送自 Windows 10 版邮件应用 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thiagocmartinsc at gmail.com Mon Jun 4 22:59:38 2018 From: thiagocmartinsc at gmail.com (=?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?=) Date: Mon, 4 Jun 2018 18:59:38 -0400 Subject: [Openstack] Geneve isn't working on Queens, Ubuntu 18.04 - Failed to bind port type geneve Message-ID: Hello! I have OpenStack Queens up and running on Ubuntu 18.04 with VXLAN! It is awesome! However, I want to use it with Geneve, instead of VXLAN. But, it doesn't work! With VXLAN, I have the following ml2_conf.ini: --- [ml2] type_drivers = vxlan,flat,vlan tenant_network_types = vxlan,flat,vlan mechanism_drivers = openvswitch,l2population extension_drivers = port_security overlay_ip_version = 4 --- All good! I can launch instances and ping the Internet from within an instance. So, when I try the Geneve instead, like this: --- [ml2] type_drivers = geneve,vxlan,flat,vlan tenant_network_types = geneve,vxlan,flat,vlan mechanism_drivers = openvswitch,l2population extension_drivers = port_security overlay_ip_version = 4 --- NOTE: I can easily bring up a clean Ubuntu 18.04 server image, and install OpenStack from scratch, to do the each test independently. I have my own Ansible automation to deploy OpenStack Queens on Ubuntu 18.04. As I've said, it works fine with VXLAN but, not with Geneve (2 lines change from one deployment, to another). So, while trying to create an instance with Geneve, the following error appear on Neutron logs: --- 2018-06-04 22:55:40.677 11426 ERROR neutron.plugins.ml2.managers [req-c988c769-690e-45db-b810-3b35f0e8cba8 bda3aed0ccae46008f9928885280c085 46f4131518fd4b699ac80bc867fd1832 - default default] Failed to bind port 17e4dd94-7655-40f5-9077-b6e7c583c7eb on host queens-1 for vnic_type normal using segments [{'network_id': '6f805d1f-dfb6-42f6-846a-e39fac80ca8c', 'segmentation_id': 19, 'physical_network': None, 'id': '51a89942-5a91-47c6-872b-b33d2e6d418d', 'network_type': u'geneve'}] --- Is it a bug? I appreciate any help! Cheers! Thiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From thiagocmartinsc at gmail.com Tue Jun 5 00:53:27 2018 From: thiagocmartinsc at gmail.com (=?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?=) Date: Mon, 4 Jun 2018 20:53:27 -0400 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! Message-ID: Hello, I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, the "gnocchi-api" package tries to uninstall Keystone and Horizon! So, from what I'm seeing, it is impossible to build an OpenStack Queens All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( The problem (line 29): https://pastebin.com/sns8LG18 Any workaround or bug reported on Launchpad about this? Time for Canonical to provide OpenStack Snap packages! lol Thanks! Thiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From pablobrunetti at hotmail.com Tue Jun 5 01:25:33 2018 From: pablobrunetti at hotmail.com (pablo brunetti) Date: Tue, 5 Jun 2018 01:25:33 +0000 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: References: Message-ID: Hello, This bug is confirmed in https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992 Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : Bugs : gnocchi package : Ubuntu bugs.launchpad.net Since the two wsgi modules are conflicting, installing gnocchi-api breaks other OpenStack services. Pablo. ________________________________ De: Martinx - ジェームズ Enviado: segunda-feira, 4 de junho de 2018 21:53 Para: openstack at lists.openstack.org; James Page Assunto: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! Hello, I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, the "gnocchi-api" package tries to uninstall Keystone and Horizon! So, from what I'm seeing, it is impossible to build an OpenStack Queens All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( The problem (line 29): https://pastebin.com/sns8LG18 [https://pastebin.com/i/facebook.png] administrative at queens-1:~$ sudo apt install gnocchi-api Reading package lists. - Pastebin.com pastebin.com Any workaround or bug reported on Launchpad about this? Time for Canonical to provide OpenStack Snap packages! lol Thanks! Thiago -------------- next part -------------- An HTML attachment was scrubbed... URL: From thiagocmartinsc at gmail.com Tue Jun 5 02:31:50 2018 From: thiagocmartinsc at gmail.com (=?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?=) Date: Mon, 4 Jun 2018 22:31:50 -0400 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: References: Message-ID: Thank you! On 4 June 2018 at 21:25, pablo brunetti wrote: > Hello, > > > This bug is confirmed in https://bugs.launchpad.net/ > ubuntu/+source/gnocchi/+bug/1746992 > Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : > Bugs : gnocchi package : Ubuntu > > bugs.launchpad.net > Since the two wsgi modules are conflicting, installing gnocchi-api breaks > other OpenStack services. > > > Pablo. > > > > > ------------------------------ > *De:* Martinx - ジェームズ > *Enviado:* segunda-feira, 4 de junho de 2018 21:53 > *Para:* openstack at lists.openstack.org; James Page > *Assunto:* [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install > tries to remove both "keystone" and "openstack-dashboard"! > > Hello, > > I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, > the "gnocchi-api" package tries to uninstall Keystone and Horizon! > > So, from what I'm seeing, it is impossible to build an OpenStack Queens > All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( > > The problem (line 29): > > https://pastebin.com/sns8LG18 > > administrative at queens-1:~$ sudo apt install gnocchi-api Reading package > lists. - Pastebin.com > pastebin.com > > > Any workaround or bug reported on Launchpad about this? > > Time for Canonical to provide OpenStack Snap packages! lol > > Thanks! > Thiago > -------------- next part -------------- An HTML attachment was scrubbed... URL: From agbedko at gmail.com Tue Jun 5 03:05:27 2018 From: agbedko at gmail.com (kodzo agbedanu) Date: Mon, 4 Jun 2018 22:05:27 -0500 Subject: [Openstack] To post Message-ID: agbedko at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From kysung at devstack.co.kr Tue Jun 5 06:42:50 2018 From: kysung at devstack.co.kr (KiYoun Sung) Date: Tue, 5 Jun 2018 15:42:50 +0900 Subject: [Openstack] [queens][ceilometer][gnocchi] no network resource, after installation openstack queens Message-ID: Hello. I installed Openstack Queens version using Openstack-ansible. and I set gnocchi, ceilometer for metering. After installation, I got metric from instance, image, swift, etc. but, there is no metric by network I did by gnocchi cli, like this $ gnocchi resource-type list the network resource-type is exist. but, "$ gnocchi resource list" is empty. I made a external network and created floating ip. but, there is no network resource. neutron.conf has [oslo_messaging_notifications] field below: [oslo_messaging_notifications] notification_topics = notifications driver = messagingv2 transport_url = rabbit://neutron:xxxx at 172.29.238.44:5671//neutron How can I get network resoruce(especially floating ip)? What is a problem? Thank you. Best regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregory.orange at pawsey.org.au Tue Jun 5 08:48:15 2018 From: gregory.orange at pawsey.org.au (Gregory Orange) Date: Tue, 5 Jun 2018 16:48:15 +0800 Subject: [Openstack] Upgrade Nova Ocata -> Pike placement section Message-ID: Hi everyone, I'm looking at upgrading Nova from Ocata to Pike and reading https://docs.openstack.org/releasenotes/nova/pike.html: "Ensure the [placement] section of nova.conf for the nova-conductor service is filled in." Can I get some input on what that means? That is, I assume it needs to be our nova controllers, not compute nodes, and nova.conf [placement] section... but which settings need values? All of them? Thanks, Greg. From eblock at nde.ag Tue Jun 5 09:08:00 2018 From: eblock at nde.ag (Eugen Block) Date: Tue, 05 Jun 2018 09:08:00 +0000 Subject: [Openstack] Upgrade Nova Ocata -> Pike placement section In-Reply-To: Message-ID: <20180605090800.Horde.i1uPApcXKdwffGrZWLXsRmP@webmail.nde.ag> Hi, you can check the install guide [1] for further information. Here's what it says: ---cut here--- [placement] # ... os_region_name = RegionOne project_domain_name = Default project_name = service auth_type = password user_domain_name = Default auth_url = http://controller:35357/v3 username = placement password = PLACEMENT_PASS ---cut here--- Both control and compute node need that section. Regards, Eugen [1] https://docs.openstack.org/nova/pike/install/controller-install-obs.html Zitat von Gregory Orange : > Hi everyone, > > I'm looking at upgrading Nova from Ocata to Pike and reading > https://docs.openstack.org/releasenotes/nova/pike.html: "Ensure the > [placement] section of nova.conf for the nova-conductor service is > filled in." Can I get some input on what that means? > > That is, I assume it needs to be our nova controllers, not compute > nodes, and nova.conf [placement] section... but which settings need > values? All of them? > > Thanks, > Greg. > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack From ionos3d at gmail.com Tue Jun 5 10:43:19 2018 From: ionos3d at gmail.com (Ionosphere s.r.o.) Date: Tue, 5 Jun 2018 12:43:19 +0200 Subject: [Openstack] Installing openstack Message-ID: Hello, my name is Patrik Púpala. Recently we tried to install openstack, but we went into some problems installing it so i want to ask that if we need to install it on a fresh minimal installation of linux or we can use DVD versions of linux. Also if you can point me what addational packages (like EPEL in CentOS) we need to install to install it properly. I know that there are a specific steps which i need to follow to install it but in meaning of addational packages i mean like linux addational packages not openstack because i know openstack will install automatically what he needs. Also i want to ask what linux is best and easiest for installing openstack. If i wrote this to wrong mail can you point me to some kind of technical support ? Thank you for your answer. -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Tue Jun 5 11:12:46 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Tue, 5 Jun 2018 20:12:46 +0900 Subject: [Openstack] Installing openstack In-Reply-To: References: Message-ID: <65bd2ec3-3b0f-7958-63ed-6dd86ff470f4@gmail.com> The installation tutorials mention a "base installation" of the operating system. I would start with a minimal install to avoid any problems arising from incompatible software versions, plus sshd if it's not part of that minimal install. All other requirements, like NTP, database, message queue, SELinux etc are covered in the tutorials [1]. Out of OpenSUSE, Ubuntu and Centos, use the distro you are most familiar with. This mailing list is one of the community support options. More focused mailing lists exist, see [2]. You can also try http://ask.openstack.org. If you are willing to pay, there are many companies that offer support, for example [3]. [1] https://docs.openstack.org/install-guide/environment.html [2] http://lists.openstack.org [3] https://www.openstack.org/marketplace/consulting/ On 6/5/2018 7:43 PM, Ionosphere s.r.o. wrote: > Hello, my name is Patrik Púpala. Recently we tried to install > openstack, but we went into some problems installing it so i want to > ask that if we need to install it on a fresh minimal installation of > linux or we can use DVD versions of linux. Also if you can point me > what addational packages (like EPEL in CentOS) we need to install to > install it properly. I know that there are a specific steps which i > need to follow to install it but in meaning of addational packages i > mean like linux addational packages not openstack because i know > openstack will install automatically what he needs. Also i want to ask > what linux is best and easiest for installing openstack. > > If i wrote this to wrong mail can you point me to some kind of > technical support ?  > > Thank you for your answer. > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From corey.bryant at canonical.com Tue Jun 5 14:30:41 2018 From: corey.bryant at canonical.com (Corey Bryant) Date: Tue, 5 Jun 2018 10:30:41 -0400 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: References: Message-ID: Hi Martin, Thanks for bringing this up. I replied in the bug, but pasting some of my response below: gnocchi-api only supports py3 for now in bionic/queens and above. Most OpenStack packages in Ubuntu have not yet received py3 support. That is a focus for the cosmic cycle. Where possible the plan is to install py2 by default and py3 as an alternative to prevent all-in-one issues like this. In other words, 'sudo apt install python3-keystone keystone' would install python3 packages, and (assuming python3-keystone was not already installed) 'sudo apt install keystone' would install python2 packages. That's not the case for gnocchi-api, obviously, as it only installs py3 packages which conflicts with other python packages if and only if you're installing on the same machine as other py2 services. Most modern production deployments isolate services in one way or another (e.g. containers such as LXD or docker) so there's a clear work around. With that said, we can probably add py2 alternative packages to the Depends for gnocchi-api allowing py2 installs, however I seem to remember gnocchi-api was forced to move to py3 for a reason. I'm not remembering why though atm. Thanks, Corey On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ wrote: > Thank you! > > On 4 June 2018 at 21:25, pablo brunetti wrote: > >> Hello, >> >> >> This bug is confirmed in https://bugs.launchpad.net/ubu >> ntu/+source/gnocchi/+bug/1746992 >> Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : >> Bugs : gnocchi package : Ubuntu >> >> bugs.launchpad.net >> Since the two wsgi modules are conflicting, installing gnocchi-api breaks >> other OpenStack services. >> >> >> Pablo. >> >> >> >> >> ------------------------------ >> *De:* Martinx - ジェームズ >> *Enviado:* segunda-feira, 4 de junho de 2018 21:53 >> *Para:* openstack at lists.openstack.org; James Page >> *Assunto:* [Openstack] On Ubuntu 18.04, the package "gnocchi-api" >> install tries to remove both "keystone" and "openstack-dashboard"! >> >> Hello, >> >> I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, >> the "gnocchi-api" package tries to uninstall Keystone and Horizon! >> >> So, from what I'm seeing, it is impossible to build an OpenStack Queens >> All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( >> >> The problem (line 29): >> >> https://pastebin.com/sns8LG18 >> >> administrative at queens-1:~$ sudo apt install gnocchi-api Reading package >> lists. - Pastebin.com >> pastebin.com >> >> >> Any workaround or bug reported on Launchpad about this? >> >> Time for Canonical to provide OpenStack Snap packages! lol >> >> Thanks! >> Thiago >> > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Remo at italy1.com Tue Jun 5 15:31:36 2018 From: Remo at italy1.com (Remo Mattei) Date: Tue, 5 Jun 2018 08:31:36 -0700 Subject: [Openstack] Installing openstack In-Reply-To: <65bd2ec3-3b0f-7958-63ed-6dd86ff470f4@gmail.com> References: <65bd2ec3-3b0f-7958-63ed-6dd86ff470f4@gmail.com> Message-ID: What are you using to install OpenStack? Packstack? OOO? Ansi Kolla, helm? > On Jun 5, 2018, at 4:12 AM, Bernd Bausch wrote: > > The installation tutorials mention a "base installation" of the operating system. I would start with a minimal install to avoid any problems arising from incompatible software versions, plus sshd if it's not part of that minimal install. All other requirements, like NTP, database, message queue, SELinux etc are covered in the tutorials [1]. > > Out of OpenSUSE, Ubuntu and Centos, use the distro you are most familiar with. > > This mailing list is one of the community support options. More focused mailing lists exist, see [2]. You can also try http://ask.openstack.org . If you are willing to pay, there are many companies that offer support, for example [3]. > > > [1] https://docs.openstack.org/install-guide/environment.html > [2] http://lists.openstack.org > [3] https://www.openstack.org/marketplace/consulting/ > On 6/5/2018 7:43 PM, Ionosphere s.r.o. wrote: >> Hello, my name is Patrik Púpala. Recently we tried to install openstack, but we went into some problems installing it so i want to ask that if we need to install it on a fresh minimal installation of linux or we can use DVD versions of linux. Also if you can point me what addational packages (like EPEL in CentOS) we need to install to install it properly. I know that there are a specific steps which i need to follow to install it but in meaning of addational packages i mean like linux addational packages not openstack because i know openstack will install automatically what he needs. Also i want to ask what linux is best and easiest for installing openstack. >> >> If i wrote this to wrong mail can you point me to some kind of technical support ? >> >> Thank you for your answer. >> >> >> >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack at lists.openstack.org >> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From satish.txt at gmail.com Tue Jun 5 16:19:02 2018 From: satish.txt at gmail.com (Satish Patel) Date: Tue, 5 Jun 2018 12:19:02 -0400 Subject: [Openstack] First Ceph storage planning advice Message-ID: Folks, I am building 15 node openstack private cloud for beginning, so i am planning to build Ceph storage for nova block storage so all VM will run on Central storage and provide failover for vm instances. This is what i have in my inventory and i want to build my first ceph storage, i need some suggestion form you guys how should i plan to build best storage for my openstack cloud? 5 Server (DL360 G8 - CPU core 32 / 32GB mem / 2x10GE NIC) 16 500GB SSD (samsung) 16 1TB SATA (7.5k RPMS) From thiagocmartinsc at gmail.com Tue Jun 5 23:50:13 2018 From: thiagocmartinsc at gmail.com (=?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?=) Date: Tue, 5 Jun 2018 19:50:13 -0400 Subject: [Openstack] Geneve isn't working on Queens, Ubuntu 18.04 - Failed to bind port type geneve In-Reply-To: References: Message-ID: Guys, Is there anyone running Queens on Ubuntu 18.04 with Geneve instead of VXLAN (OpenvSwitch Agent, Neutron L3 Agents...)? Thanks! Thiago On 4 June 2018 at 18:59, Martinx - ジェームズ wrote: > Hello! > > I have OpenStack Queens up and running on Ubuntu 18.04 with VXLAN! > > It is awesome! > > However, I want to use it with Geneve, instead of VXLAN. > > But, it doesn't work! > > With VXLAN, I have the following ml2_conf.ini: > > --- > [ml2] > type_drivers = vxlan,flat,vlan > tenant_network_types = vxlan,flat,vlan > mechanism_drivers = openvswitch,l2population > extension_drivers = port_security > overlay_ip_version = 4 > --- > > All good! I can launch instances and ping the Internet from within an > instance. > > So, when I try the Geneve instead, like this: > > --- > [ml2] > type_drivers = geneve,vxlan,flat,vlan > tenant_network_types = geneve,vxlan,flat,vlan > mechanism_drivers = openvswitch,l2population > extension_drivers = port_security > overlay_ip_version = 4 > --- > > NOTE: I can easily bring up a clean Ubuntu 18.04 server image, and install > OpenStack from scratch, to do the each test independently. I have my own > Ansible automation to deploy OpenStack Queens on Ubuntu 18.04. As I've > said, it works fine with VXLAN but, not with Geneve (2 lines change from > one deployment, to another). > > > So, while trying to create an instance with Geneve, the following error > appear on Neutron logs: > > --- > 2018-06-04 22:55:40.677 11426 ERROR neutron.plugins.ml2.managers > [req-c988c769-690e-45db-b810-3b35f0e8cba8 bda3aed0ccae46008f9928885280c085 > 46f4131518fd4b699ac80bc867fd1832 - default default] Failed to bind port > 17e4dd94-7655-40f5-9077-b6e7c583c7eb on host queens-1 for vnic_type > normal using segments [{'network_id': '6f805d1f-dfb6-42f6-846a-e39fac80ca8c', > 'segmentation_id': 19, 'physical_network': None, 'id': > '51a89942-5a91-47c6-872b-b33d2e6d418d', 'network_type': u'geneve'}] > --- > > Is it a bug? > > I appreciate any help! > > Cheers! > Thiago > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Wed Jun 6 00:17:41 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Wed, 6 Jun 2018 09:17:41 +0900 Subject: [Openstack] Geneve isn't working on Queens, Ubuntu 18.04 - Failed to bind port type geneve In-Reply-To: References: Message-ID: <20e18f12-cd72-588f-d1e1-e8b4b911ef12@gmail.com> Not me, but this part in the log message makes me think something went wrong with the mapping from virtual to physical network: 'physical_network': None Not sure. However, I believe this log message comes from the neutron server. If so, it would be worthwhile checking the OVS agent log on the compute node for related messages. Bernd Bausch On 6/6/2018 8:50 AM, Martinx - ジェームズ wrote: > Guys, > >  Is there anyone running Queens on Ubuntu 18.04 with Geneve instead of > VXLAN (OpenvSwitch Agent, Neutron L3 Agents...)? > > Thanks! > Thiago > > On 4 June 2018 at 18:59, Martinx - ジェームズ > wrote: > > Hello! > >  I have OpenStack Queens up and running on Ubuntu 18.04 with VXLAN! > >  It is awesome! > >  However, I want to use it with Geneve, instead of VXLAN. > >  But, it doesn't work! > >  With VXLAN, I have the following ml2_conf.ini: > > --- > [ml2] > type_drivers = vxlan,flat,vlan > tenant_network_types = vxlan,flat,vlan > mechanism_drivers = openvswitch,l2population > extension_drivers = port_security > overlay_ip_version = 4 > --- > >  All good! I can launch instances and ping the Internet from > within an instance. > >  So, when I try the Geneve instead, like this: > > --- > [ml2] > type_drivers = geneve,vxlan,flat,vlan > tenant_network_types = geneve,vxlan,flat,vlan > mechanism_drivers = openvswitch,l2population > extension_drivers = port_security > overlay_ip_version = 4 > --- > > NOTE: I can easily bring up a clean Ubuntu 18.04 server image, and > install OpenStack from scratch, to do the each test independently. > I have my own Ansible automation to deploy OpenStack Queens on > Ubuntu 18.04. As I've said, it works fine with VXLAN but, not with > Geneve (2 lines change from one deployment, to another). > > > So, while trying to create an instance with Geneve, the following > error appear on Neutron logs: > > --- > 2018-06-04 22:55:40.677 11426 ERROR neutron.plugins.ml2.managers > [req-c988c769-690e-45db-b810-3b35f0e8cba8 > bda3aed0ccae46008f9928885280c085 46f4131518fd4b699ac80bc867fd1832 > - default default] Failed to bind port > 17e4dd94-7655-40f5-9077-b6e7c583c7eb on host queens-1 for > vnic_type normal using segments [{'network_id': > '6f805d1f-dfb6-42f6-846a-e39fac80ca8c', 'segmentation_id': 19, > 'physical_network': None, 'id': > '51a89942-5a91-47c6-872b-b33d2e6d418d', 'network_type': u'geneve'}] > --- > >  Is it a bug? > >  I appreciate any help! > > Cheers! > Thiago > > > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From skaplons at redhat.com Wed Jun 6 07:58:32 2018 From: skaplons at redhat.com (Slawomir Kaplonski) Date: Wed, 6 Jun 2018 09:58:32 +0200 Subject: [Openstack] Geneve isn't working on Queens, Ubuntu 18.04 - Failed to bind port type geneve In-Reply-To: References: Message-ID: <154945DF-E835-48CA-8476-ECA66C2AE1BE@redhat.com> Hi, You probably need also change in L2 agent’s config as it needs to report that it supports Geneve tunnel types as well. It’s defined in https://github.com/openstack/neutron/blob/2820c25e3a67e1cc747abdd6d69e4a0331425904/neutron/conf/plugins/ml2/drivers/ovs_conf.py#L107 > Wiadomość napisana przez Martinx - ジェームズ w dniu 05.06.2018, o godz. 00:59: > > Hello! > > I have OpenStack Queens up and running on Ubuntu 18.04 with VXLAN! > > It is awesome! > > However, I want to use it with Geneve, instead of VXLAN. > > But, it doesn't work! > > With VXLAN, I have the following ml2_conf.ini: > > --- > [ml2] > type_drivers = vxlan,flat,vlan > tenant_network_types = vxlan,flat,vlan > mechanism_drivers = openvswitch,l2population > extension_drivers = port_security > overlay_ip_version = 4 > --- > > All good! I can launch instances and ping the Internet from within an instance. > > So, when I try the Geneve instead, like this: > > --- > [ml2] > type_drivers = geneve,vxlan,flat,vlan > tenant_network_types = geneve,vxlan,flat,vlan > mechanism_drivers = openvswitch,l2population > extension_drivers = port_security > overlay_ip_version = 4 > --- > > NOTE: I can easily bring up a clean Ubuntu 18.04 server image, and install OpenStack from scratch, to do the each test independently. I have my own Ansible automation to deploy OpenStack Queens on Ubuntu 18.04. As I've said, it works fine with VXLAN but, not with Geneve (2 lines change from one deployment, to another). > > > So, while trying to create an instance with Geneve, the following error appear on Neutron logs: > > --- > 2018-06-04 22:55:40.677 11426 ERROR neutron.plugins.ml2.managers [req-c988c769-690e-45db-b810-3b35f0e8cba8 bda3aed0ccae46008f9928885280c085 46f4131518fd4b699ac80bc867fd1832 - default default] Failed to bind port 17e4dd94-7655-40f5-9077-b6e7c583c7eb on host queens-1 for vnic_type normal using segments [{'network_id': '6f805d1f-dfb6-42f6-846a-e39fac80ca8c', 'segmentation_id': 19, 'physical_network': None, 'id': '51a89942-5a91-47c6-872b-b33d2e6d418d', 'network_type': u'geneve'}] > --- > > Is it a bug? > > I appreciate any help! > > Cheers! > Thiago > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack — Slawek Kaplonski Senior software engineer Red Hat From tobias.urdin at crystone.com Thu Jun 7 05:26:09 2018 From: tobias.urdin at crystone.com (Tobias Urdin) Date: Thu, 7 Jun 2018 05:26:09 +0000 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! References: Message-ID: I can jump in here as well and say that the Puppet OpenStack project had issue with this as well with the UCA Queens release since we run all services on the same nodes in our CI. We got help from Corey and James, they added the python-gnocchi (which is py2) package which provides the necessary Gnocchi code and WSGI entry points that we could start using that with Apache2, it just doesn't fix the Apache2 config automatically. Other gnocchi packages like the metricd daemon will still be running python3 but it won't collide with any packages since it's Apache2 combining that is the issue. You will however need the python3-redis and python3-rados (if you use Ceph) packages for the metricd daemon. The full swap to python3 should be a coordinated bump where it moves all packages to python3. Any changes to the gnocchi-api package does not affect Puppet OpenStack on Ubuntu's ability to work as long as python-gnocchi is provided. Now while we are at it, do you know if python-gnocchi is packaged for bionic? Or was it a quick fix for uca/queens only? Best regards On 06/05/2018 04:43 PM, Corey Bryant wrote: Hi Martin, Thanks for bringing this up. I replied in the bug, but pasting some of my response below: gnocchi-api only supports py3 for now in bionic/queens and above. Most OpenStack packages in Ubuntu have not yet received py3 support. That is a focus for the cosmic cycle. Where possible the plan is to install py2 by default and py3 as an alternative to prevent all-in-one issues like this. In other words, 'sudo apt install python3-keystone keystone' would install python3 packages, and (assuming python3-keystone was not already installed) 'sudo apt install keystone' would install python2 packages. That's not the case for gnocchi-api, obviously, as it only installs py3 packages which conflicts with other python packages if and only if you're installing on the same machine as other py2 services. Most modern production deployments isolate services in one way or another (e.g. containers such as LXD or docker) so there's a clear work around. With that said, we can probably add py2 alternative packages to the Depends for gnocchi-api allowing py2 installs, however I seem to remember gnocchi-api was forced to move to py3 for a reason. I'm not remembering why though atm. Thanks, Corey On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ > wrote: Thank you! On 4 June 2018 at 21:25, pablo brunetti > wrote: Hello, This bug is confirmed in https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992 Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : Bugs : gnocchi package : Ubuntu bugs.launchpad.net Since the two wsgi modules are conflicting, installing gnocchi-api breaks other OpenStack services. Pablo. ________________________________ De: Martinx - ジェームズ > Enviado: segunda-feira, 4 de junho de 2018 21:53 Para: openstack at lists.openstack.org; James Page Assunto: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! Hello, I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, the "gnocchi-api" package tries to uninstall Keystone and Horizon! So, from what I'm seeing, it is impossible to build an OpenStack Queens All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( The problem (line 29): https://pastebin.com/sns8LG18 [https://pastebin.com/i/facebook.png] administrative at queens-1:~$ sudo apt install gnocchi-api Reading package lists. - Pastebin.com pastebin.com Any workaround or bug reported on Launchpad about this? Time for Canonical to provide OpenStack Snap packages! lol Thanks! Thiago _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack at lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregory.orange at pawsey.org.au Thu Jun 7 06:49:15 2018 From: gregory.orange at pawsey.org.au (Gregory Orange) Date: Thu, 7 Jun 2018 14:49:15 +0800 Subject: [Openstack] Upgrade Nova Ocata -> Pike placement section In-Reply-To: <20180605090800.Horde.i1uPApcXKdwffGrZWLXsRmP@webmail.nde.ag> References: <20180605090800.Horde.i1uPApcXKdwffGrZWLXsRmP@webmail.nde.ag> Message-ID: Great, thank you Eugen. I cross referenced that with the configuration reference[1] and what we already have configured, and I'm satisfied that section is setup fine for the upgrade. Greg. [1] https://docs.openstack.org/nova/pike/configuration/config.html On 05/06/18 17:08, Eugen Block wrote: > Hi, > > you can check the install guide [1] for further information. > > Here's what it says: > > ---cut here--- > [placement] > # ... > os_region_name = RegionOne > project_domain_name = Default > project_name = service > auth_type = password > user_domain_name = Default > auth_url = http://controller:35357/v3 > username = placement > password = PLACEMENT_PASS > ---cut here--- > > Both control and compute node need that section. > > Regards, > Eugen > > [1] https://docs.openstack.org/nova/pike/install/controller-install-obs.html > > > Zitat von Gregory Orange : > >> Hi everyone, >> >> I'm looking at upgrading Nova from Ocata to Pike and reading https://docs.openstack.org/releasenotes/nova/pike.html: "Ensure the [placement] section of nova.conf for the nova-conductor service is filled in." Can I get some input on what that means? >> >> That is, I assume it needs to be our nova controllers, not compute nodes, and nova.conf [placement] section... but which settings need values? All of them? >> >> Thanks, >> Greg. >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to     : openstack at lists.openstack.org >> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to     : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Gregory Orange Cloud Computing System Administrator Pawsey Supercomputing Centre Australian Resources Research Centre (ARRC) From corey.bryant at canonical.com Thu Jun 7 13:19:27 2018 From: corey.bryant at canonical.com (Corey Bryant) Date: Thu, 7 Jun 2018 09:19:27 -0400 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: References: Message-ID: On Thu, Jun 7, 2018 at 1:26 AM, Tobias Urdin wrote: > I can jump in here as well and say that the Puppet OpenStack project had > issue with this as well with the UCA Queens release > since we run all services on the same nodes in our CI. > > We got help from Corey and James, they added the python-gnocchi (which is > py2) package which provides the necessary Gnocchi code and > WSGI entry points that we could start using that with Apache2, it just > doesn't fix the Apache2 config automatically. > > Other gnocchi packages like the metricd daemon will still be running > python3 but it won't collide with any packages since it's Apache2 combining > that is the issue. > You will however need the python3-redis and python3-rados (if you use > Ceph) packages for the metricd daemon. > > Note that all of the other gnocchi-* packages other than gnocchi-api (gnocchi-metricd and gnocchi-statsd) support python2. You just need to install python-gnocchi before installing them. If you don't do that they'll default to python3-gnocchi. > The full swap to python3 should be a coordinated bump where it moves all > packages to python3. > Any changes to the gnocchi-api package does not affect Puppet OpenStack on > Ubuntu's ability to work as long as python-gnocchi is provided. > I agree it should be coordinated. I'm going to test gnocchi-api support for python2 as an alternative (would behave similar to how the above packages work). It's an easy fix. Stay tuned to the bug that was linked earlier. > Now while we are at it, do you know if python-gnocchi is packaged for > bionic? Or was it a quick fix for uca/queens only? > Yes, the the same package source is used for bionic and queens. Thanks, Corey Best regards > > > On 06/05/2018 04:43 PM, Corey Bryant wrote: > > Hi Martin, > > Thanks for bringing this up. I replied in the bug, but pasting some of my > response below: > > gnocchi-api only supports py3 for now in bionic/queens and above. > > Most OpenStack packages in Ubuntu have not yet received py3 support. That > is a focus for the cosmic cycle. Where possible the plan is to install py2 > by default and py3 as an alternative to prevent all-in-one issues like this. > > In other words, 'sudo apt install python3-keystone keystone' would install > python3 packages, and (assuming python3-keystone was not already installed) > 'sudo apt install keystone' would install python2 packages. > > That's not the case for gnocchi-api, obviously, as it only installs py3 > packages which conflicts with other python packages if and only if you're > installing on the same machine as other py2 services. Most modern > production deployments isolate services in one way or another (e.g. > containers such as LXD or docker) so there's a clear work around. > > With that said, we can probably add py2 alternative packages to the > Depends for gnocchi-api allowing py2 installs, however I seem to remember > gnocchi-api was forced to move to py3 for a reason. I'm not remembering why > though atm. > > Thanks, > > Corey > > On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ < > thiagocmartinsc at gmail.com> wrote: > >> Thank you! >> >> On 4 June 2018 at 21:25, pablo brunetti >> wrote: >> >>> Hello, >>> >>> >>> This bug is confirmed in https://bugs.launchpad.net/ubu >>> ntu/+source/gnocchi/+bug/1746992 >>> Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : >>> Bugs : gnocchi package : Ubuntu >>> >>> bugs.launchpad.net >>> Since the two wsgi modules are conflicting, installing gnocchi-api >>> breaks other OpenStack services. >>> >>> >>> Pablo. >>> >>> >>> >>> >>> ------------------------------ >>> *De:* Martinx - ジェームズ >>> *Enviado:* segunda-feira, 4 de junho de 2018 21:53 >>> *Para:* openstack at lists.openstack.org; James Page >>> *Assunto:* [Openstack] On Ubuntu 18.04, the package "gnocchi-api" >>> install tries to remove both "keystone" and "openstack-dashboard"! >>> >>> Hello, >>> >>> I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, >>> the "gnocchi-api" package tries to uninstall Keystone and Horizon! >>> >>> So, from what I'm seeing, it is impossible to build an OpenStack Queens >>> All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( >>> >>> The problem (line 29): >>> >>> https://pastebin.com/sns8LG18 >>> >>> administrative at queens-1:~$ sudo apt install gnocchi-api Reading package >>> lists. - Pastebin.com >>> pastebin.com >>> >>> >>> Any workaround or bug reported on Launchpad about this? >>> >>> Time for Canonical to provide OpenStack Snap packages! lol >>> >>> Thanks! >>> Thiago >>> >> >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi >> -bin/mailman/listinfo/openstack >> Post to : openstack at lists.openstack.org >> Unsubscribe : http://lists.openstack.org/cgi >> -bin/mailman/listinfo/openstack >> >> > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From torin.woltjer at granddial.com Thu Jun 7 14:21:11 2018 From: torin.woltjer at granddial.com (Torin Woltjer) Date: Thu, 07 Jun 2018 14:21:11 GMT Subject: [Openstack] Openstack Dashboard console iframe Message-ID: <27ef553f69e94420a0afeb3dbc4d831f@granddial.com> When using haproxy for the openstack dashboard the iframe for the instance console stops working. The console does work without the iframe, if I open it in its own window. nova.conf on controller: my_ip = 192.168.116.21 [vnc] enabled = true server_listen = $my_ip server_proxyclient_address = $my_ip novncproxy_host = $my_ip nova.conf on compute: my_ip = 192.168.116.23 [vnc] enabled = True server_listen = 0.0.0.0 server_proxyclient_address = $my_ip novncproxy_base_url = http://controller:6080/vnc_auto.html controller in the host file resolves to 192.168.116.16, the VIP on HAProxy. Is there something wrong with this configuration? Does anybody else have this problem with the console iframe when using HAProxy? -------------- next part -------------- An HTML attachment was scrubbed... URL: From thiagocmartinsc at gmail.com Thu Jun 7 19:57:51 2018 From: thiagocmartinsc at gmail.com (=?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?=) Date: Thu, 7 Jun 2018 15:57:51 -0400 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: References: Message-ID: Corey, I still don't get it... The package gnocchi-api is basically empty. It have only 1 single text file: "/etc/apache2/sites-available/gnocchi-api.conf"! The problem is that it depends on "python3-gnocchi" and "libapache2-mod-wsgi-py3", which brings the problem... So, the workaround looks quite simple! Instead of running "apt install gnocchi-api", I'm doing: --- apt install python-gnocchi # which brings Gnocchi API (/usr/bin/gnocchi-api) for Python 2, then: apt download gnocchi-api # Extract the "/etc/apache2/sites-available/gnocchi-api.conf" file out from "gnocchi-api_4.2.4-0ubuntu1_all.deb" and manually copy to /etc/apache/sites-available". --- On 5 June 2018 at 10:30, Corey Bryant wrote: > Hi Martin, > > Thanks for bringing this up. I replied in the bug, but pasting some of my > response below: > > gnocchi-api only supports py3 for now in bionic/queens and above. > > Most OpenStack packages in Ubuntu have not yet received py3 support. That > is a focus for the cosmic cycle. Where possible the plan is to install py2 > by default and py3 as an alternative to prevent all-in-one issues like this. > > In other words, 'sudo apt install python3-keystone keystone' would install > python3 packages, and (assuming python3-keystone was not already installed) > 'sudo apt install keystone' would install python2 packages. > > That's not the case for gnocchi-api, obviously, as it only installs py3 > packages which conflicts with other python packages if and only if you're > installing on the same machine as other py2 services. Most modern > production deployments isolate services in one way or another (e.g. > containers such as LXD or docker) so there's a clear work around. > > With that said, we can probably add py2 alternative packages to the > Depends for gnocchi-api allowing py2 installs, however I seem to remember > gnocchi-api was forced to move to py3 for a reason. I'm not remembering why > though atm. > > Thanks, > > Corey > > On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ < > thiagocmartinsc at gmail.com> wrote: > >> Thank you! >> >> On 4 June 2018 at 21:25, pablo brunetti >> wrote: >> >>> Hello, >>> >>> >>> This bug is confirmed in >>> https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992 >>> Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : >>> Bugs : gnocchi package : Ubuntu >>> >>> bugs.launchpad.net >>> Since the two wsgi modules are conflicting, installing gnocchi-api >>> breaks other OpenStack services. >>> >>> >>> Pablo. >>> >>> >>> >>> >>> ------------------------------ >>> *De:* Martinx - ジェームズ >>> *Enviado:* segunda-feira, 4 de junho de 2018 21:53 >>> *Para:* openstack at lists.openstack.org; James Page >>> *Assunto:* [Openstack] On Ubuntu 18.04, the package "gnocchi-api" >>> install tries to remove both "keystone" and "openstack-dashboard"! >>> >>> Hello, >>> >>> I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, >>> the "gnocchi-api" package tries to uninstall Keystone and Horizon! >>> >>> So, from what I'm seeing, it is impossible to build an OpenStack Queens >>> All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( >>> >>> The problem (line 29): >>> >>> https://pastebin.com/sns8LG18 >>> >>> administrative at queens-1:~$ sudo apt install gnocchi-api Reading package >>> lists. - Pastebin.com >>> pastebin.com >>> >>> >>> Any workaround or bug reported on Launchpad about this? >>> >>> Time for Canonical to provide OpenStack Snap packages! lol >>> >>> Thanks! >>> Thiago >>> >> >> >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack at lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thiagocmartinsc at gmail.com Thu Jun 7 20:40:49 2018 From: thiagocmartinsc at gmail.com (=?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?=) Date: Thu, 7 Jun 2018 16:40:49 -0400 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: References: Message-ID: Worth to mention that I still have to test python-gnocchi, my confs are wrong but, it is installed... :-P On Thu, 7 Jun 2018 at 15:57, Martinx - ジェームズ wrote: > Corey, > > I still don't get it... The package gnocchi-api is basically empty. > > It have only 1 single text file: > "/etc/apache2/sites-available/gnocchi-api.conf"! > > The problem is that it depends on "python3-gnocchi" and > "libapache2-mod-wsgi-py3", which brings the problem... > > So, the workaround looks quite simple! > > Instead of running "apt install gnocchi-api", I'm doing: > > --- > apt install python-gnocchi # which brings Gnocchi API > (/usr/bin/gnocchi-api) for Python 2, then: > > apt download gnocchi-api > > # Extract the "/etc/apache2/sites-available/gnocchi-api.conf" file out > from "gnocchi-api_4.2.4-0ubuntu1_all.deb" and manually copy to > /etc/apache/sites-available". > --- > > > > On 5 June 2018 at 10:30, Corey Bryant wrote: > >> Hi Martin, >> >> Thanks for bringing this up. I replied in the bug, but pasting some of my >> response below: >> >> gnocchi-api only supports py3 for now in bionic/queens and above. >> >> Most OpenStack packages in Ubuntu have not yet received py3 support. That >> is a focus for the cosmic cycle. Where possible the plan is to install py2 >> by default and py3 as an alternative to prevent all-in-one issues like this. >> >> In other words, 'sudo apt install python3-keystone keystone' would >> install python3 packages, and (assuming python3-keystone was not already >> installed) 'sudo apt install keystone' would install python2 packages. >> >> That's not the case for gnocchi-api, obviously, as it only installs py3 >> packages which conflicts with other python packages if and only if you're >> installing on the same machine as other py2 services. Most modern >> production deployments isolate services in one way or another (e.g. >> containers such as LXD or docker) so there's a clear work around. >> >> With that said, we can probably add py2 alternative packages to the >> Depends for gnocchi-api allowing py2 installs, however I seem to remember >> gnocchi-api was forced to move to py3 for a reason. I'm not remembering why >> though atm. >> >> Thanks, >> >> Corey >> >> On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ < >> thiagocmartinsc at gmail.com> wrote: >> >>> Thank you! >>> >>> On 4 June 2018 at 21:25, pablo brunetti >>> wrote: >>> >>>> Hello, >>>> >>>> >>>> This bug is confirmed in >>>> https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992 >>>> Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : >>>> Bugs : gnocchi package : Ubuntu >>>> >>>> bugs.launchpad.net >>>> Since the two wsgi modules are conflicting, installing gnocchi-api >>>> breaks other OpenStack services. >>>> >>>> >>>> Pablo. >>>> >>>> >>>> >>>> >>>> ------------------------------ >>>> *De:* Martinx - ジェームズ >>>> *Enviado:* segunda-feira, 4 de junho de 2018 21:53 >>>> *Para:* openstack at lists.openstack.org; James Page >>>> *Assunto:* [Openstack] On Ubuntu 18.04, the package "gnocchi-api" >>>> install tries to remove both "keystone" and "openstack-dashboard"! >>>> >>>> Hello, >>>> >>>> I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, >>>> the "gnocchi-api" package tries to uninstall Keystone and Horizon! >>>> >>>> So, from what I'm seeing, it is impossible to build an OpenStack >>>> Queens All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( >>>> >>>> The problem (line 29): >>>> >>>> https://pastebin.com/sns8LG18 >>>> >>>> administrative at queens-1:~$ sudo apt install gnocchi-api Reading package >>>> lists. - Pastebin.com >>>> pastebin.com >>>> >>>> >>>> Any workaround or bug reported on Launchpad about this? >>>> >>>> Time for Canonical to provide OpenStack Snap packages! lol >>>> >>>> Thanks! >>>> Thiago >>>> >>> >>> >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : openstack at lists.openstack.org >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobias.urdin at crystone.com Fri Jun 8 07:44:24 2018 From: tobias.urdin at crystone.com (Tobias Urdin) Date: Fri, 8 Jun 2018 07:44:24 +0000 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! References: Message-ID: <1fec49b81bd541228550092d58f3c8c4@mb01.staff.ognet.se> Yeah, that's it :) Can post the apache2 config here, this is the one we use which is generated by puppet, you'll need the mod_wsgi module as well. ServerName hostnamehere ## Vhost docroot DocumentRoot "/usr/lib/cgi-bin/gnocchi" ## Directories, there should at least be a declaration for /usr/lib/cgi-bin/gnocchi Options Indexes FollowSymLinks MultiViews AllowOverride None Require all granted ## Logging ErrorLog "/var/log/apache2/gnocchi_wsgi_error.log" ServerSignature Off CustomLog "/var/log/apache2/gnocchi_wsgi_access.log" combined SetEnvIf X-Forwarded-Proto https HTTPS=1 WSGIApplicationGroup %{GLOBAL} WSGIDaemonProcess gnocchi display-name=gnocchi_wsgi group=gnocchi processes=2 threads=1 user=gnocchi WSGIProcessGroup gnocchi WSGIScriptAlias / "/usr/lib/cgi-bin/gnocchi/app" On 06/07/2018 10:54 PM, Martinx - ジェームズ wrote: Worth to mention that I still have to test python-gnocchi, my confs are wrong but, it is installed... :-P On Thu, 7 Jun 2018 at 15:57, Martinx - ジェームズ > wrote: Corey, I still don't get it... The package gnocchi-api is basically empty. It have only 1 single text file: "/etc/apache2/sites-available/gnocchi-api.conf"! The problem is that it depends on "python3-gnocchi" and "libapache2-mod-wsgi-py3", which brings the problem... So, the workaround looks quite simple! Instead of running "apt install gnocchi-api", I'm doing: --- apt install python-gnocchi # which brings Gnocchi API (/usr/bin/gnocchi-api) for Python 2, then: apt download gnocchi-api # Extract the "/etc/apache2/sites-available/gnocchi-api.conf" file out from "gnocchi-api_4.2.4-0ubuntu1_all.deb" and manually copy to /etc/apache/sites-available". --- On 5 June 2018 at 10:30, Corey Bryant > wrote: Hi Martin, Thanks for bringing this up. I replied in the bug, but pasting some of my response below: gnocchi-api only supports py3 for now in bionic/queens and above. Most OpenStack packages in Ubuntu have not yet received py3 support. That is a focus for the cosmic cycle. Where possible the plan is to install py2 by default and py3 as an alternative to prevent all-in-one issues like this. In other words, 'sudo apt install python3-keystone keystone' would install python3 packages, and (assuming python3-keystone was not already installed) 'sudo apt install keystone' would install python2 packages. That's not the case for gnocchi-api, obviously, as it only installs py3 packages which conflicts with other python packages if and only if you're installing on the same machine as other py2 services. Most modern production deployments isolate services in one way or another (e.g. containers such as LXD or docker) so there's a clear work around. With that said, we can probably add py2 alternative packages to the Depends for gnocchi-api allowing py2 installs, however I seem to remember gnocchi-api was forced to move to py3 for a reason. I'm not remembering why though atm. Thanks, Corey On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ > wrote: Thank you! On 4 June 2018 at 21:25, pablo brunetti > wrote: Hello, This bug is confirmed in https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992 Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : Bugs : gnocchi package : Ubuntu bugs.launchpad.net Since the two wsgi modules are conflicting, installing gnocchi-api breaks other OpenStack services. Pablo. ________________________________ De: Martinx - ジェームズ > Enviado: segunda-feira, 4 de junho de 2018 21:53 Para: openstack at lists.openstack.org; James Page Assunto: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! Hello, I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, the "gnocchi-api" package tries to uninstall Keystone and Horizon! So, from what I'm seeing, it is impossible to build an OpenStack Queens All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( The problem (line 29): https://pastebin.com/sns8LG18 [https://pastebin.com/i/facebook.png] administrative at queens-1:~$ sudo apt install gnocchi-api Reading package lists. - Pastebin.com pastebin.com Any workaround or bug reported on Launchpad about this? Time for Canonical to provide OpenStack Snap packages! lol Thanks! Thiago _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack at lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From pablobrunetti at hotmail.com Fri Jun 8 13:27:52 2018 From: pablobrunetti at hotmail.com (pablo brunetti) Date: Fri, 8 Jun 2018 13:27:52 +0000 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: <1fec49b81bd541228550092d58f3c8c4@mb01.staff.ognet.se> References: , <1fec49b81bd541228550092d58f3c8c4@mb01.staff.ognet.se> Message-ID: I installed the gnocchi-api with sudo "pip install gnocchi-api" and it worked correctly, without the dependencies of python3 and manually configured the _wsgi module. There was an error in ceilometer-agent-compute on compute node, when I activated the memory.usage metric: 2018-06-08 13:25:19.031 11424 WARNING ceilometer.compute.pollsters [-] memory.usage statistic in not available for instance 8a6954a4-d8cc-43f6-aa41-8f371bbb9fd3: NoVolumeException Could someone help me with this error? ________________________________ De: Tobias Urdin Enviado: sexta-feira, 8 de junho de 2018 04:44 Para: Martinx - ジェームズ Cc: openstack at lists.openstack.org Assunto: Re: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! Yeah, that's it :) Can post the apache2 config here, this is the one we use which is generated by puppet, you'll need the mod_wsgi module as well. ServerName hostnamehere ## Vhost docroot DocumentRoot "/usr/lib/cgi-bin/gnocchi" ## Directories, there should at least be a declaration for /usr/lib/cgi-bin/gnocchi Options Indexes FollowSymLinks MultiViews AllowOverride None Require all granted ## Logging ErrorLog "/var/log/apache2/gnocchi_wsgi_error.log" ServerSignature Off CustomLog "/var/log/apache2/gnocchi_wsgi_access.log" combined SetEnvIf X-Forwarded-Proto https HTTPS=1 WSGIApplicationGroup %{GLOBAL} WSGIDaemonProcess gnocchi display-name=gnocchi_wsgi group=gnocchi processes=2 threads=1 user=gnocchi WSGIProcessGroup gnocchi WSGIScriptAlias / "/usr/lib/cgi-bin/gnocchi/app" On 06/07/2018 10:54 PM, Martinx - ジェームズ wrote: Worth to mention that I still have to test python-gnocchi, my confs are wrong but, it is installed... :-P On Thu, 7 Jun 2018 at 15:57, Martinx - ジェームズ > wrote: Corey, I still don't get it... The package gnocchi-api is basically empty. It have only 1 single text file: "/etc/apache2/sites-available/gnocchi-api.conf"! The problem is that it depends on "python3-gnocchi" and "libapache2-mod-wsgi-py3", which brings the problem... So, the workaround looks quite simple! Instead of running "apt install gnocchi-api", I'm doing: --- apt install python-gnocchi # which brings Gnocchi API (/usr/bin/gnocchi-api) for Python 2, then: apt download gnocchi-api # Extract the "/etc/apache2/sites-available/gnocchi-api.conf" file out from "gnocchi-api_4.2.4-0ubuntu1_all.deb" and manually copy to /etc/apache/sites-available". --- On 5 June 2018 at 10:30, Corey Bryant > wrote: Hi Martin, Thanks for bringing this up. I replied in the bug, but pasting some of my response below: gnocchi-api only supports py3 for now in bionic/queens and above. Most OpenStack packages in Ubuntu have not yet received py3 support. That is a focus for the cosmic cycle. Where possible the plan is to install py2 by default and py3 as an alternative to prevent all-in-one issues like this. In other words, 'sudo apt install python3-keystone keystone' would install python3 packages, and (assuming python3-keystone was not already installed) 'sudo apt install keystone' would install python2 packages. That's not the case for gnocchi-api, obviously, as it only installs py3 packages which conflicts with other python packages if and only if you're installing on the same machine as other py2 services. Most modern production deployments isolate services in one way or another (e.g. containers such as LXD or docker) so there's a clear work around. With that said, we can probably add py2 alternative packages to the Depends for gnocchi-api allowing py2 installs, however I seem to remember gnocchi-api was forced to move to py3 for a reason. I'm not remembering why though atm. Thanks, Corey On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ > wrote: Thank you! On 4 June 2018 at 21:25, pablo brunetti > wrote: Hello, This bug is confirmed in https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992 Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : Bugs : gnocchi package : Ubuntu bugs.launchpad.net Since the two wsgi modules are conflicting, installing gnocchi-api breaks other OpenStack services. Pablo. ________________________________ De: Martinx - ジェームズ > Enviado: segunda-feira, 4 de junho de 2018 21:53 Para: openstack at lists.openstack.org; James Page Assunto: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! Hello, I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, the "gnocchi-api" package tries to uninstall Keystone and Horizon! So, from what I'm seeing, it is impossible to build an OpenStack Queens All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( The problem (line 29): https://pastebin.com/sns8LG18 [https://pastebin.com/i/facebook.png] administrative at queens-1:~$ sudo apt install gnocchi-api Reading package lists. - Pastebin.com pastebin.com Any workaround or bug reported on Launchpad about this? Time for Canonical to provide OpenStack Snap packages! lol Thanks! Thiago _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack at lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From corey.bryant at canonical.com Fri Jun 8 14:09:59 2018 From: corey.bryant at canonical.com (Corey Bryant) Date: Fri, 8 Jun 2018 10:09:59 -0400 Subject: [Openstack] On Ubuntu 18.04, the package "gnocchi-api" install tries to remove both "keystone" and "openstack-dashboard"! In-Reply-To: References: Message-ID: It's the dependencies of gnocchi-api that prevent a py2 installation. I've uploaded new package versions for cosmic and bionic via https://bugs.launchpad.net/cloud-archive/+bug/1746992. It would be great if you could help us test! Thanks, Corey On Thu, Jun 7, 2018 at 3:57 PM, Martinx - ジェームズ wrote: > Corey, > > I still don't get it... The package gnocchi-api is basically empty. > > It have only 1 single text file: "/etc/apache2/sites-available/ > gnocchi-api.conf"! > > The problem is that it depends on "python3-gnocchi" and > "libapache2-mod-wsgi-py3", which brings the problem... > > So, the workaround looks quite simple! > > Instead of running "apt install gnocchi-api", I'm doing: > > --- > apt install python-gnocchi # which brings Gnocchi API > (/usr/bin/gnocchi-api) for Python 2, then: > > apt download gnocchi-api > > # Extract the "/etc/apache2/sites-available/gnocchi-api.conf" file out > from "gnocchi-api_4.2.4-0ubuntu1_all.deb" and manually copy to > /etc/apache/sites-available". > --- > > > > On 5 June 2018 at 10:30, Corey Bryant wrote: > >> Hi Martin, >> >> Thanks for bringing this up. I replied in the bug, but pasting some of my >> response below: >> >> gnocchi-api only supports py3 for now in bionic/queens and above. >> >> Most OpenStack packages in Ubuntu have not yet received py3 support. That >> is a focus for the cosmic cycle. Where possible the plan is to install py2 >> by default and py3 as an alternative to prevent all-in-one issues like this. >> >> In other words, 'sudo apt install python3-keystone keystone' would >> install python3 packages, and (assuming python3-keystone was not already >> installed) 'sudo apt install keystone' would install python2 packages. >> >> That's not the case for gnocchi-api, obviously, as it only installs py3 >> packages which conflicts with other python packages if and only if you're >> installing on the same machine as other py2 services. Most modern >> production deployments isolate services in one way or another (e.g. >> containers such as LXD or docker) so there's a clear work around. >> >> With that said, we can probably add py2 alternative packages to the >> Depends for gnocchi-api allowing py2 installs, however I seem to remember >> gnocchi-api was forced to move to py3 for a reason. I'm not remembering why >> though atm. >> >> Thanks, >> >> Corey >> >> On Mon, Jun 4, 2018 at 10:31 PM, Martinx - ジェームズ < >> thiagocmartinsc at gmail.com> wrote: >> >>> Thank you! >>> >>> On 4 June 2018 at 21:25, pablo brunetti >>> wrote: >>> >>>> Hello, >>>> >>>> >>>> This bug is confirmed in https://bugs.launchpad.net/ >>>> ubuntu/+source/gnocchi/+bug/1746992 >>>> Bug #1746992 “gnocchi-api in Bionic uses python3, and libapache2...” : >>>> Bugs : gnocchi package : Ubuntu >>>> >>>> bugs.launchpad.net >>>> Since the two wsgi modules are conflicting, installing gnocchi-api >>>> breaks other OpenStack services. >>>> >>>> >>>> Pablo. >>>> >>>> >>>> >>>> >>>> ------------------------------ >>>> *De:* Martinx - ジェームズ >>>> *Enviado:* segunda-feira, 4 de junho de 2018 21:53 >>>> *Para:* openstack at lists.openstack.org; James Page >>>> *Assunto:* [Openstack] On Ubuntu 18.04, the package "gnocchi-api" >>>> install tries to remove both "keystone" and "openstack-dashboard"! >>>> >>>> Hello, >>>> >>>> I'm trying to install Gnocchi on Ubuntu 18.04, but there is a problem, >>>> the "gnocchi-api" package tries to uninstall Keystone and Horizon! >>>> >>>> So, from what I'm seeing, it is impossible to build an OpenStack >>>> Queens All-in-One on Ubuntu 18.04 with Gnocchi and Ceilometer... :-( >>>> >>>> The problem (line 29): >>>> >>>> https://pastebin.com/sns8LG18 >>>> >>>> administrative at queens-1:~$ sudo apt install gnocchi-api Reading package >>>> lists. - Pastebin.com >>>> pastebin.com >>>> >>>> >>>> Any workaround or bug reported on Launchpad about this? >>>> >>>> Time for Canonical to provide OpenStack Snap packages! lol >>>> >>>> Thanks! >>>> Thiago >>>> >>> >>> >>> _______________________________________________ >>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ >>> openstack >>> Post to : openstack at lists.openstack.org >>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ >>> openstack >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrhillsman at gmail.com Fri Jun 8 19:42:55 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Fri, 8 Jun 2018 14:42:55 -0500 Subject: [Openstack] Reminder: UC Meeting Monday 1400UTC Message-ID: Hey everyone, Please see https://wiki.openstack.org/wiki/Governance/ Foundation/UserCommittee for UC meeting info and add additional agenda items if needed. -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ravi.Rao at us.fujitsu.com Sat Jun 9 18:52:55 2018 From: Ravi.Rao at us.fujitsu.com (Ravi.Rao at us.fujitsu.com) Date: Sat, 9 Jun 2018 18:52:55 +0000 Subject: [Openstack] Creation of a server get stuck at Building state Message-ID: Hi All, I have installed openstack queens using packstack on a multimode setup. One controller and two compute nodes. Openstack hypervisor list shows all 3 compute nodes as up. I was able to spinup about 5 servers and all of them got hosted on the controller node which is also a compute. When I try to spin the 6th server it is getting stuck at the build state. Looks like it is not able to use the other two compute nodes. I have already verified all the cells_v2 settings and they all look ok. Can one of you please let me know what logs to check to understand what is causing this issue. None of the Nova logs on the controller has any errors.. Any help to resolve this is greatly appreciated. Regards, Ravi.. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrhillsman at gmail.com Sun Jun 10 01:11:47 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Sat, 9 Jun 2018 20:11:47 -0500 Subject: [Openstack] Creation of a server get stuck at Building state In-Reply-To: References: Message-ID: I would recommend grepping for the request ID across all logs if they are centralized. Additionally if you have not turned on debugging, more than likely doing so for at least nova-scheduler prior to trying to spin up an instance again should help. Providing error messages is generally beneficial as if you are not able to see any there is really no way for anyone to assist without some additional details so I first suggest you look a bit more at all your logs and in general your environment and provide a bit more detail for assistance. Hope this helps. On Sat, Jun 9, 2018 at 1:52 PM, Ravi.Rao at us.fujitsu.com < Ravi.Rao at us.fujitsu.com> wrote: > Hi All, > > I have installed openstack queens using packstack on a multimode setup. > One controller and two compute nodes. > > Openstack hypervisor list shows all 3 compute nodes as up. > > I was able to spinup about 5 servers and all of them got hosted on the > controller node which is also a compute. > > When I try to spin the 6th server it is getting stuck at the build state. > Looks like it is not able to use the other two compute nodes. > > I have already verified all the cells_v2 settings and they all look ok. > > Can one of you please let me know what logs to check to understand what is > causing this issue. > > None of the Nova logs on the controller has any errors.. > > Any help to resolve this is greatly appreciated. > > Regards, > > Ravi.. > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ravi.Rao at us.fujitsu.com Sun Jun 10 15:39:26 2018 From: Ravi.Rao at us.fujitsu.com (Ravi.Rao at us.fujitsu.com) Date: Sun, 10 Jun 2018 15:39:26 +0000 Subject: [Openstack] Creation of a server get stuck at Building state In-Reply-To: References: Message-ID: Hi Melvin, Thanks for the response. I have already turned on debug mode. I will keep digging into the logs further. Do u know of any document that clearly explains the sequence once we issue a openstack server create. This will help me narrow down the issue. I have another setup with ocata and it works fine in that env. Regards, Ravi.. From: Melvin Hillsman [mailto:mrhillsman at gmail.com] Sent: Saturday, June 9, 2018 8:12 PM To: Rao, Ravi Cc: openstack at lists.openstack.org Subject: Re: [Openstack] Creation of a server get stuck at Building state I would recommend grepping for the request ID across all logs if they are centralized. Additionally if you have not turned on debugging, more than likely doing so for at least nova-scheduler prior to trying to spin up an instance again should help. Providing error messages is generally beneficial as if you are not able to see any there is really no way for anyone to assist without some additional details so I first suggest you look a bit more at all your logs and in general your environment and provide a bit more detail for assistance. Hope this helps. On Sat, Jun 9, 2018 at 1:52 PM, Ravi.Rao at us.fujitsu.com > wrote: Hi All, I have installed openstack queens using packstack on a multimode setup. One controller and two compute nodes. Openstack hypervisor list shows all 3 compute nodes as up. I was able to spinup about 5 servers and all of them got hosted on the controller node which is also a compute. When I try to spin the 6th server it is getting stuck at the build state. Looks like it is not able to use the other two compute nodes. I have already verified all the cells_v2 settings and they all look ok. Can one of you please let me know what logs to check to understand what is causing this issue. None of the Nova logs on the controller has any errors.. Any help to resolve this is greatly appreciated. Regards, Ravi.. _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack at lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From remo at italy1.com Sun Jun 10 16:00:48 2018 From: remo at italy1.com (Remo Mattei) Date: Sun, 10 Jun 2018 09:00:48 -0700 Subject: [Openstack] Creation of a server get stuck at Building state In-Reply-To: References: Message-ID: <5156ADFE-2467-4D56-B699-FA8E8C90408F@italy1.com> I remember I did a project and we removed the controller since we did not want to have it to serve compute. You do have to change the dB to exclude it or you can disable is as nova-manage if you want to try and see what happen to track down the behavior Remo > Il giorno 10 giu 2018, alle ore 08:39, "Ravi.Rao at us.fujitsu.com" ha scritto: > > Hi Melvin, > Thanks for the response. I have already turned on debug mode. I will keep digging into the logs further. Do u know of any document that clearly explains the sequence once we issue a openstack server create. This will help me narrow down the issue. I have another setup with ocata and it works fine in that env. > Regards, > Ravi.. > > From: Melvin Hillsman [mailto:mrhillsman at gmail.com] > Sent: Saturday, June 9, 2018 8:12 PM > To: Rao, Ravi > Cc: openstack at lists.openstack.org > Subject: Re: [Openstack] Creation of a server get stuck at Building state > > I would recommend grepping for the request ID across all logs if they are centralized. Additionally if you have not turned on debugging, more than likely doing so for at least nova-scheduler prior to trying to spin up an instance again should help. Providing error messages is generally beneficial as if you are not able to see any there is really no way for anyone to assist without some additional details so I first suggest you look a bit more at all your logs and in general your environment and provide a bit more detail for assistance. Hope this helps. > > On Sat, Jun 9, 2018 at 1:52 PM, Ravi.Rao at us.fujitsu.com wrote: > Hi All, > I have installed openstack queens using packstack on a multimode setup. One controller and two compute nodes. > Openstack hypervisor list shows all 3 compute nodes as up. > I was able to spinup about 5 servers and all of them got hosted on the controller node which is also a compute. > When I try to spin the 6th server it is getting stuck at the build state. Looks like it is not able to use the other two compute nodes. > I have already verified all the cells_v2 settings and they all look ok. > Can one of you please let me know what logs to check to understand what is causing this issue. > None of the Nova logs on the controller has any errors.. > Any help to resolve this is greatly appreciated. > Regards, > Ravi.. > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > > > -- > Kind regards, > > Melvin Hillsman > mrhillsman at gmail.com > mobile: (832) 264-2646 > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From satish.txt at gmail.com Sun Jun 10 23:35:15 2018 From: satish.txt at gmail.com (Satish Patel) Date: Sun, 10 Jun 2018 19:35:15 -0400 Subject: [Openstack] First Ceph storage planning advice In-Reply-To: <80a31efd112e4f25ab1f6157d7245789@granddial.com> References: <80a31efd112e4f25ab1f6157d7245789@granddial.com> Message-ID: Thanks! I’m still looking for advice to see what I can build from my inventory Sent from my iPhone > On Jun 6, 2018, at 9:17 AM, Torin Woltjer wrote: > > Hello Satish Patel, > > Here are a couple of resources that should help you get started with Ceph: > > http://docs.ceph.com/docs/master/install/ > https://ceph.com/planet/deploying-ceph-with-storage-tiering/ > https://www.stratoscale.com/blog/storage/integrating-ceph-storage-openstack-step-step-guide/ > > And if you would like, you can join the ceph-users mailing list here: > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com/ > > Torin Woltjer > > Grand Dial Communications - A ZK Tech Inc. Company > > 616.776.1066 ext. 2006 > www.granddial.com > > From: Satish Patel > Sent: 6/5/18 12:35 PM > To: openstack > Subject: [Openstack] First Ceph storage planning advice > Folks, > > I am building 15 node openstack private cloud for beginning, so i am > planning to build Ceph storage for nova block storage so all VM will > run on Central storage and provide failover for vm instances. > > This is what i have in my inventory and i want to build my first ceph > storage, i need some suggestion form you guys how should i plan to > build best storage for my openstack cloud? > > 5 Server (DL360 G8 - CPU core 32 / 32GB mem / 2x10GE NIC) > 16 500GB SSD (samsung) > 16 1TB SATA (7.5k RPMS) > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrhillsman at gmail.com Mon Jun 11 12:37:34 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Mon, 11 Jun 2018 07:37:34 -0500 Subject: [Openstack] Reminder: UC Meeting Today 1400UTC / 0900CST Message-ID: Hey everyone, Please see https://wiki.openstack.org/wiki/Governance/Foundation/ UserCommittee for UC meeting info and add additional agenda items if needed. -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pablobrunetti at hotmail.com Mon Jun 11 16:54:12 2018 From: pablobrunetti at hotmail.com (pablo brunetti) Date: Mon, 11 Jun 2018 16:54:12 +0000 Subject: [Openstack] [Neutron][Ceilometer] - Integration Ryu and OpenStack Message-ID: Hello, I manually installed the Openstack Multi node Queens version with OVS, following the tutorial https://docs.openstack.org/neutron/queens/admin/deploy-ovs-selfservice.html The controller RYU is normally running as seen in the neutron-openvswitch-agent.log log 2018-06-11 14:28:13.242 13220 INFO neutron.common.config [-] Logging enabled! 2018-06-11 14:28:13.243 13220 INFO neutron.common.config [-] /usr/bin/neutron-openvswitch-agent version 12.0.1 2018-06-11 14:28:13.243 13220 INFO ryu.base.app_manager [-] loading app neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_ryuapp 2018-06-11 14:28:13.556 13220 INFO ryu.base.app_manager [-] loading app ryu.app.ofctl.service 2018-06-11 14:28:13.556 13220 INFO ryu.base.app_manager [-] loading app ryu.controller.ofp_handler 2018-06-11 14:28:13.557 13220 INFO ryu.base.app_manager [-] instantiating app neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_ryuapp of OVSNeutronAgentRyuApp 2018-06-11 14:28:13.557 13220 INFO ryu.base.app_manager [-] instantiating app ryu.controller.ofp_handler of OFPHandler 2018-06-11 14:28:13.557 13220 INFO ryu.base.app_manager [-] instantiating app ryu.app.ofctl.service of OfctlService 2018-06-11 14:28:13.558 13220 INFO neutron.agent.agent_extensions_manager [-] Loaded agent extensions: [] 2018-06-11 14:28:13.560 13220 WARNING oslo_config.cfg [-] Option "ovsdb_interface" from group "OVS" is deprecated for removal. Its value may be silently ignored in the future. 2018-06-11 14:28:13.677 13220 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [-] Bridge br-int has datapath-ID 0000ce215119c542 2018-06-11 14:28:15.856 13220 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [req-adece591-4460-406a-a183-110a2f98ba8c - - - - -] Bridge br-tun has datapath-ID 0000b65f0ce4d44f 2018-06-11 14:28:15.943 13220 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Agent has just been revived. Doing a full sync. 2018-06-11 14:28:16.098 13220 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-21a8fb32-9ebb-445b-860f-836941134bdf - - - - -] Agent initialized successfully, now running... My question is how do I get the SDN metrics(switch.port.receive.bytes, switch.port.transmit.bytes, port.receive.bytes, port.transmit.bytes) for this driver. Can anyone help me by providing details of how I can perform monitoring with the Ceilometer with the RYU driver? Or if there is any other way to get these metrics. Best regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From arnaud.morin at gmail.com Tue Jun 12 08:10:01 2018 From: arnaud.morin at gmail.com (Arnaud MORIN) Date: Tue, 12 Jun 2018 10:10:01 +0200 Subject: [Openstack] Oslo DB Message-ID: Hey all, Is there any way to configure Oslo db to perform sql write (update/delete) on a different db server than for read only? I can only see connection string. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From joe at topjian.net Tue Jun 12 17:39:05 2018 From: joe at topjian.net (Joe Topjian) Date: Tue, 12 Jun 2018 11:39:05 -0600 Subject: [Openstack] [Sahara] Anti-Affinity Broke? Message-ID: Hello, I was unable to get anti-affinity to work in Sahara. The logs were reporting a Heat error that u'' was not a valid UUID. Upon further investigation, I think I found several errors in the `sahara/service/heat/templates.py` file. I'm working with Sahara 7.0.0 but the master branch still exhibits these problems. I figured I would start with posting to the general openstack list rather than -dev or opening a bug report just to check my sanity on this. If these findings are correct, then anti-affinity is broke and has been for some time. The alternative is that I've missed some configuration somewhere -- which is entirely possible :) 1. ng.count is either invalid, always returns 0, or isn't being set somewhere else. https://github.com/openstack/sahara/blob/master/sahara/service/heat/templates.py#L276 Instead, I've used ng_count = self.node_groups_extra[ng.id]['node_count'] 2. an uninitialized Python key. https://github.com/openstack/sahara/blob/master/sahara/service/heat/templates.py#L283 3. Incorrect bounds in range(): https://github.com/openstack/sahara/blob/master/sahara/service/heat/templates.py#L255-L256 I believe this should be: for i in range(0, self.cluster.anti_affinity_ratio): resources.update(self._serialize_aa_server_group(i+1)) https://github.com/openstack/sahara/blob/master/sahara/service/heat/templates.py#L278 I believe this should be: for i in range(0, ng_count): Thanks, Joe -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel at jtcressy.net Tue Jun 12 22:16:44 2018 From: joel at jtcressy.net (Joel Cressy) Date: Tue, 12 Jun 2018 16:16:44 -0600 Subject: [Openstack] [Fuel] Fresh install of fuel-community 11.0 skips setup to login prompt with no MOTD Message-ID: Hi all, It was working previously, but on a freshly-made VM and a fuel-community 11.0 iso the installer completes and reboots the vm but at no point was I presented with the fuel setup TUI to setup my networking or set passwords, etc. It’s inaccessible because I don’t know what the root password is nor what IP it’s using. I’ve tried to reboot it and reinstall it with the iso, but it keeps doing the same thing and i’m not sure what I’m doing wrong. Is there a way for me to find out the default root password and then manually start the fuel-setup TUI? Thanks, -Joel Cressy From joel at jtcressy.net Tue Jun 12 23:01:07 2018 From: joel at jtcressy.net (Joel Cressy) Date: Tue, 12 Jun 2018 17:01:07 -0600 Subject: [Openstack] [Fuel] Fresh install of fuel-community 11.0 skips setup to login prompt with no MOTD In-Reply-To: References: Message-ID: <2602E464-6437-47AD-80BF-64030558C306@jtcressy.net> Ok, I was able to login to the fuel instance with the default r00tme password, but I still can’t configure the fuel master and enable the web service. It also has a default IP of 10.20.0.1 but even if i could access that I think it’s still useless without having ran the setup. Any ideas? -Joel Cressy > On Jun 12, 2018, at 4:16 PM, Joel Cressy wrote: > > Hi all, > > It was working previously, but on a freshly-made VM and a fuel-community 11.0 iso the installer completes and reboots the vm but at no point was I presented with the fuel setup TUI to setup my networking or set passwords, etc. It’s inaccessible because I don’t know what the root password is nor what IP it’s using. I’ve tried to reboot it and reinstall it with the iso, but it keeps doing the same thing and i’m not sure what I’m doing wrong. > > Is there a way for me to find out the default root password and then manually start the fuel-setup TUI? > > Thanks, > -Joel Cressy > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack From Remo at italy1.com Thu Jun 14 05:10:56 2018 From: Remo at italy1.com (Remo Mattei) Date: Wed, 13 Jun 2018 22:10:56 -0700 Subject: [Openstack] Tempest with OOO In-Reply-To: References: <3D0D0130-B17C-448A-9A65-98D9B4316BCA@rm.ht> Message-ID: Hello guys, I see that OOO gens a file for tempest, I could not find any data on how to use that option. Any suggestions? Thanks Remo -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengtcli at qq.com Thu Jun 14 13:00:21 2018 From: chengtcli at qq.com (=?ISO-8859-1?B?Q2hlbmc=?=) Date: Thu, 14 Jun 2018 21:00:21 +0800 Subject: [Openstack] cinder-schduler multi workers Message-ID: Hi, I am trying to understand why we don't support multi workers of cinder-scheduler. I searched on google and the archived mails. But I didn't find the details. I increased the cinder-scheduler workers in my test env to get better performance, it worked. I didn't find the configuration option for cinder-scheduler workers number. so I had to change the source code of cinder to increase workers. `cinder/cmd/scheduler.py` Seems we don't support configuring multi cinder-scheduler workers, so why do not we support it. I can think of one case for not supporting multi workers: If I have 2 workers, and 2 cinder volume backends. [backend1: {free: 1.5GB}, backend2: {free: 1GB}] Now, I send two requests to create two volumes at the same time. Worker1 gets one request, while worker2 gets the other. They will both schedule the new volume to backend1(because 1.5GB > 1GB). This is not good, because backend1 is not able to afford two volumes of 1GB. But seems this is not a big problem, as reschedule will be triggered to correct it. Is there any other reason we don't support multi cinder-scheduler workers? Thanks. Cheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From torin.woltjer at granddial.com Thu Jun 14 15:11:54 2018 From: torin.woltjer at granddial.com (Torin Woltjer) Date: Thu, 14 Jun 2018 15:11:54 GMT Subject: [Openstack] Masakari Setup Message-ID: <554b45e7512549ff8cfce6bc5ba28041@granddial.com> Currently trying to run masakari 4.0.0 on openstack queens. I have corosync + pacemaker running on compute nodes, crm status shows both running. When I run masakari-hostmonitor, I see 2 errors that are repeated while running. 2018-06-14 09:48:58.475 11062 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'vlan60' is failed.: ProcessExecutionError: Unexpected error while running command. 2018-06-14 09:48:58.476 11062 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed.: ProcessExecutionError: Unexpected error while running command. This is my /etc/masakarimonitors/masakarimonitors.conf [DEFAULT] [api] auth_uri = http://controller:5000 auth_url = http://controller:5000 memcached_servers = controller1:11211,controller2:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = masakari password = ********** [host] corosync_multicast_interfaces = vlan60 corosync_multicast_ports = 5405 -------------- next part -------------- An HTML attachment was scrubbed... URL: From eblock at nde.ag Fri Jun 15 07:34:15 2018 From: eblock at nde.ag (Eugen Block) Date: Fri, 15 Jun 2018 07:34:15 +0000 Subject: [Openstack] can't resize server In-Reply-To: <9D8A2486E35F0941A60430473E29F15B01739C7B89@MXDB1.ad.garvan.unsw.edu.au> Message-ID: <20180615073415.Horde.BJ-cHfvI4vskH-pKYRwG9Tk@webmail.nde.ag> Hi, did you find a solution yet? If not, I tried to rebuild your situation with a test instance. Although the environment and the storage backend are different, I believe it still applies to your issue, at least in a general way. I have an instance booted from volume (size 1 GB). Trying to resize the instance via Horizon dashboard works (at least you would think that), it shows a new flavor with a disk size 8 GB. But the volume has not been resized, so the instance won't notice any changes. To accomplish that, I had to shutdown the vm, set the volume state to available (you can't detach a root disk volume), then resize the volume to the size of the flavor, and then boot the vm again, now its disk has the desired size. control:~ # openstack server stop test1 control:~ # openstack volume set --state available b832f798-e0de-4338-836a-07375f3ae3a0 control:~ # openstack volume set --size 8 b832f798-e0de-4338-836a-07375f3ae3a0 control:~ # openstack volume set --state in-use b832f798-e0de-4338-836a-07375f3ae3a0 control:~ # openstack server start test1 I should mention that I use live-migration, so during resize of an instance it migrates to another compute node. Hope this helps! Regards Eugen Zitat von Manuel Sopena Ballesteros : > Dear openstack community, > > I have a packstack all-in-one environment and I would like to resize > one of the vms. It seems like the resize process fails due to an > issue with cinder > > NOTE: the vm boots from volume and not from image > > This is the vm I am trying to resize > > [root at openstack ~(keystone_admin)]# openstack server show > 7292a929-54d9-4ce6-a595-aaf93a2be320 > +--------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | Field | Value > > > | > +--------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | OS-DCF:diskConfig | MANUAL > > > | > | OS-EXT-AZ:availability_zone | nova > > > | > | OS-EXT-SRV-ATTR:host | openstack.localdomain > > > | > | OS-EXT-SRV-ATTR:hypervisor_hostname | openstack.localdomain > > > | > | OS-EXT-SRV-ATTR:instance_name | instance-0000005f > > > | > | OS-EXT-STS:power_state | Shutdown > > > | > | OS-EXT-STS:task_state | None > > > | > | OS-EXT-STS:vm_state | error > > > | > | OS-SRV-USG:launched_at | 2018-05-14T07:24:00.000000 > > > | > | OS-SRV-USG:terminated_at | None > > > | > | accessIPv4 | > > > | > | accessIPv6 | > > > | > | addresses | > privatenetwork=192.168.1.106, 129.94.14.238 > > > | > | config_drive | > > > | > | created | 2018-05-14T07:23:52Z > > > | > | fault | {u'message': u'The server > has either erred or is incapable of performing the requested > operation. (HTTP 500) (Request-ID: > req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a)', u'code': 500, > u'details': u' File | > | | > "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line > 204, in decorated_function\n return function(self, context, > *args, **kwargs)\n File "/usr/lib/python2.7/site- > | > | | > packages/nova/compute/manager.py", line 3810, in resize_instance\n > self._terminate_volume_connections(context, instance, bdms)\n File > "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line > 3843, | > | | in > _terminate_volume_connections\n connector)\n File > "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 188, > in wrapper\n res = method(self, ctx, *args, **kwargs)\n File > "/usr/lib/python2.7 | > | | > /site-packages/nova/volume/cinder.py", line 210, in wrapper\n res > = method(self, ctx, volume_id, *args, **kwargs)\n File > "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 416, > in | > | | terminate_connection\n > connector)\n File > "/usr/lib/python2.7/site-packages/cinderclient/v3/volumes.py", line > 426, in terminate_connection\n {\'connector\': connector})\n > File "/usr/lib/python2.7/site- | > | | > packages/cinderclient/v3/volumes.py", line 346, in _action\n > resp, body = self.api.client.post(url, body=body)\n File > "/usr/lib/python2.7/site-packages/cinderclient/client.py", line 146, > in post\n return | > | | self._cs_request(url, > \'POST\', **kwargs)\n File > "/usr/lib/python2.7/site-packages/cinderclient/client.py", line 134, > in _cs_request\n return self.request(url, method, **kwargs)\n > File "/usr/lib/python2.7 | > | | > /site-packages/cinderclient/client.py", line 123, in request\n > raise exceptions.from_response(resp, body)\n', u'created': > u'2018-05-28T07:54:40Z'} > | > | flavor | m1.medium (3) > > > | > | hostId | > ecef276660cd714fe626073a18c11fe1c00bec91c15516178fb6ac28 > > > | > | id | > 7292a929-54d9-4ce6-a595-aaf93a2be320 > > > | > | image | > > > | > | key_name | None > > > | > | name | danrod-server > > > | > | os-extended-volumes:volumes_attached | [{u'id': > u'f1ac2e94-b0ed-4089-898f-5b6467fb51e3'}] > > | > | project_id | > d58cf22d960e4de49b71658aee642e94 > > > | > | properties | > > > | > | security_groups | [{u'name': u'admin'}, > {u'name': u'R-Studio Server'}] > > | > | status | ERROR > > > | > | updated | 2018-05-28T07:54:40Z > > > | > | user_id | > c412f34c353244eabecd4b6dc4d36392 > > > | > +--------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > > Cinder volume logs > > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > [req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a > c412f34c353244eabecd4b6dc4d36392 d58cf22d960e4de49b71658aee642e94 - > default default] Failed to delete initiator iqn > iqn.1994-05.com.redhat:401b935e7b19 from target. > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > Traceback (most recent call last): > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File > "/usr/lib/python2.7/site-packages/cinder/volume/targets/lio.py", > line 197, in terminate_connection > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > run_as_root=True) > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File > "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", > line 271, in inner > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > return f(*args, **kwargs) > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File > "/usr/lib/python2.7/site-packages/cinder/volume/targets/lio.py", > line 52, in _execute > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > return utils.execute(*args, **kwargs) > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File > "/usr/lib/python2.7/site-packages/cinder/utils.py", line 123, in > execute > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > return processutils.execute(*cmd, **kwargs) > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File > "/usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py", > line 389, in execute > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > cmd=sanitized_cmd) > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > ProcessExecutionError: Unexpected error while running command. > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf > cinder-rtstool delete-initiator > iqn.2010-10.org.openstack:volume-f1ac2e94-b0ed-4089-898f-5b6467fb51e3 > iqn.1994-05.com.redhat:401b935e7b19 > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio Exit code: 1 > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio Stdout: u'' > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio Stderr: > u'Traceback (most recent call last):\n File "/bin/cinder-rtstool", > line 10, in \n sys.exit(main())\n File > "/usr/lib/python2.7/site-packages/cinder/cmd/rtstool.py", line 313, > in main\n delete_initiator(target_iqn, initiator_iqn)\n File > "/usr/lib/python2.7/site-packages/cinder/cmd/rtstool.py", line 143, > in delete_initiator\n target = _lookup_target(target_iqn, > initiator_iqn)\n File > "/usr/lib/python2.7/site-packages/cinder/cmd/rtstool.py", line 123, > in _lookup_target\n raise RtstoolError(_(\'Could not find target > %s\') % target_iqn)\ncinder.cmd.rtstool.RtstoolError: Could not find > target > iqn.2010-10.org.openstack:volume-f1ac2e94-b0ed-4089-898f-5b6467fb51e3\n' > 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager > [req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a > c412f34c353244eabecd4b6dc4d36392 d58cf22d960e4de49b71658aee642e94 - > default default] Terminate volume connection failed: Failed to > detach iSCSI target for volume f1ac2e94-b0ed-4089-898f-5b6467fb51e3. > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager Traceback > (most recent call last): > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager File > "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line > 1493, in terminate_connection > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager force=force) > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager File > "/usr/lib/python2.7/site-packages/cinder/volume/drivers/lvm.py", > line 848, in terminate_connection > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager **kwargs) > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager File > "/usr/lib/python2.7/site-packages/cinder/volume/targets/lio.py", > line 202, in terminate_connection > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager raise > exception.ISCSITargetDetachFailed(volume_id=volume['id']) > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager > ISCSITargetDetachFailed: Failed to detach iSCSI target for volume > f1ac2e94-b0ed-4089-898f-5b6467fb51e3. > 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server > [req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a > c412f34c353244eabecd4b6dc4d36392 d58cf22d960e4de49b71658aee642e94 - > default default] Exception during message handling > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server > Traceback (most recent call last): > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", > line 133, in _process_incoming > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server res > = self.dispatcher.dispatch(message) > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 150, in dispatch > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server > return self._do_dispatch(endpoint, method, ctxt, args) > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 121, in _do_dispatch > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server > result = func(ctxt, **new_args) > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line > 4404, in terminate_connection > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server force=force) > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line > 1498, in terminate_connection > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server > raise exception.VolumeBackendAPIException(data=err_msg) > 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server > VolumeBackendAPIException: Bad or unexpected response from the > storage volume backend API: Terminate volume connection failed: > Failed to detach iSCSI target for volume > f1ac2e94-b0ed-4089-898f-5b6467fb51e3. > > Any thoughts? > > Manuel Sopena Ballesteros | Big data Engineer > Garvan Institute of Medical Research > The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010 > T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: > manuel.sb at garvan.org.au > > NOTICE > Please consider the environment before printing this email. This > message and any attachments are intended for the addressee named and > may contain legally privileged/confidential/copyright information. > If you are not the intended recipient, you should not read, use, > disclose, copy or distribute this communication. If you have > received this message in error please notify us at once by return > email and then delete both messages. We accept no liability for the > distribution of viruses or similar in electronic communications. > This notice should not be removed. From Dave.Chen at Dell.com Fri Jun 15 10:34:48 2018 From: Dave.Chen at Dell.com (Dave.Chen at Dell.com) Date: Fri, 15 Jun 2018 10:34:48 +0000 Subject: [Openstack] [neutron][devstack][network] Question on the OVS configuration Message-ID: <8ef87a50c8b340c5aa8fb459baf16166@KULX13MDC117.APAC.DELL.COM> Hi All, Let me brief my question, I have two NIC ports, one is connect to internal (eno1) and the other (eno2) is external, my openstack cluster is based on the devstack and neutron is configured as OVS + vxlan, How can I make my VM could be able to access external with eno2 port? I tried to add the port to br-ex but it seems doesn't work, the VM still go to the default route on the physical node which is via eno1. $ ovs-vsctl add-port br-ex eno2 Thanks in the advance for any comments! Best Regards, Dave Chen From: Chen2, Dave Sent: Friday, June 15, 2018 4:17 PM To: 'openstack-dev at lists.openstack.org' Cc: Chen2, Dave Subject: [neutron] Question on the OVS configuration Dear folks, I have setup a pretty simple OpenStack cluster in our lab based on devstack, couples of guest VM are running on one controller node (this doesn't looks like a right behavior anyway), the Neutron network is configured as OVS + vxlan, the bridge "br-ex" configured as below: Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} Port br-ex Interface br-ex type: internal ovs_version: "2.8.0" As you see, there is no external physical NIC bound to "br-ex", so I guess the traffic from the VM to external will use the default route set on the controller node, since there is a NIC (eno2) that can access external so I bind it to "br-ex" like this: ovs-vsctl add-port br-ex eno2. now the "br-ex" is configured as below: Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} *Port "eno2"* Interface "eno2" Port br-ex Interface br-ex type: internal ovs_version: "2.8.0" Looks like this is how it should be configured according to lots of wiki/blog suggestion I have googled, but it doesn't work as expected, ping from the VM, the tcpdump shows the traffic still go the "eno1" which is the default route on the controller node. Inside of VM ubuntu at test-br:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=38 time=168 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=38 time=168 ms ... Dump the traffic on the "eno2", got nothing $ sudo tcpdump -nn -i eno2 icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eno2, link-type EN10MB (Ethernet), capture size 262144 bytes ... Dump the traffic on the "eno1" (internal NIC), catch it! $ sudo tcpdump -nn -i eno1 icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes 16:08:59.609888 IP 192.168.20.132 > 8.8.8.8: ICMP echo request, id 1439, seq 1, length 64 16:08:59.781042 IP 8.8.8.8 > 192.168.20.132: ICMP echo reply, id 1439, seq 1, length 64 16:09:00.611453 IP 192.168.20.132 > 8.8.8.8: ICMP echo request, id 1439, seq 2, length 64 16:09:00.779550 IP 8.8.8.8 > 192.168.20.132: ICMP echo reply, id 1439, seq 2, length 64 $ sudo ip route default via 192.168.18.1 dev eno1 proto static metric 100 default via 192.168.8.1 dev eno2 proto static metric 101 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.8.0/24 dev eno2 proto kernel scope link src 192.168.8.101 metric 100 192.168.16.0/21 dev eno1 proto kernel scope link src 192.168.20.132 metric 100 192.168.42.0/24 dev br-ex proto kernel scope link src 192.168.42.1 What's going wrong here? Do I miss something? Or some service need to be restarted? Anyone could help me out? This question made me sick for many days! Huge thanks in the advance! Best Regards, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Fri Jun 15 22:48:47 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Sat, 16 Jun 2018 07:48:47 +0900 Subject: [Openstack] [neutron][devstack][network] Question on the OVS configuration In-Reply-To: <8ef87a50c8b340c5aa8fb459baf16166@KULX13MDC117.APAC.DELL.COM> References: <8ef87a50c8b340c5aa8fb459baf16166@KULX13MDC117.APAC.DELL.COM> Message-ID: Did you follow the networking guide https://docs.openstack.org/devstack/latest/guides/neutron.html? It has instructions for single- and multiple-NIC nodes. I believe the secret is in this setting: PUBLIC_INTERFACE=eth0 Plugging your eno2 into the bridge is not enough; as far as I understand it, you also need to move the IP address to the bridge and ensure that the bridge is UP. Perhaps the routing table must be tweaked as well, but in any case, the guides should achieve your goal. Bernd Bausch On 6/15/2018 7:34 PM, Dave.Chen at Dell.com wrote: > > Hi All, > >   > > Let me brief my question, I have two NIC ports, one is connect to > internal (eno1) and the other (eno2) is external, my openstack cluster > is based on the devstack and neutron is configured as OVS + vxlan, How > can I make my VM could be able to access external with eno2 port? > >   > > I tried to add the port to br-ex but it seems doesn’t work, the VM > still  go to the default route on the physical node which is via eno1. > >   > > $ ovs-vsctl add-port br-ex eno2 > >   > >   > > Thanks in the advance for any comments! > >   > >   > > Best Regards, > > Dave Chen > >   > > *From:* Chen2, Dave > *Sent:* Friday, June 15, 2018 4:17 PM > *To:* 'openstack-dev at lists.openstack.org' > *Cc:* Chen2, Dave > *Subject:* [neutron] Question on the OVS configuration > >   > > Dear folks, > >   > > I have setup a pretty simple OpenStack cluster in our lab based on > devstack, couples of guest VM are running on one controller node (this > doesn’t looks like a right behavior anyway),  the Neutron network is > configured as OVS + vxlan, the bridge “br-ex” configured as below: > >   > >     Bridge br-ex > >         Controller "tcp:127.0.0.1:6633" > >             is_connected: true > >         fail_mode: secure > >         Port phy-br-ex > >             Interface phy-br-ex > >                 type: patch > >                 options: {peer=int-br-ex} > >         Port br-ex > >             Interface br-ex > >                 type: internal > > ovs_version: "2.8.0" > >   > >   > >   > > As you see, there is no external physical NIC bound to “br-ex”, so I > guess the traffic from the VM to external will use the default route > set on the controller node,  since there is a NIC (eno2) that can > access external so I bind it to “br-ex” like this: ovs-vsctl add-port > br-ex eno2. now the “br-ex” is configured as below:   > >   > >     Bridge br-ex > >         Controller "tcp:127.0.0.1:6633" > >             is_connected: true > >         fail_mode: secure > >         Port phy-br-ex > >             Interface phy-br-ex > >                 type: patch > >                 options: {peer=int-br-ex} > >         **Port "eno2"** > >             Interface "eno2" > >         Port br-ex > >             Interface br-ex > >                 type: internal > >     ovs_version: "2.8.0" > >   > >   > >   > > Looks like this is how it should be configured according to lots of > wiki/blog suggestion I have googled, but it doesn’t work as expected, > ping from the VM, the tcpdump shows the traffic still go the “eno1” > which is the default route on the controller node. > >   > > Inside of VM > > ubuntu at test-br:~$ ping 8.8.8.8 > > PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. > > 64 bytes from 8.8.8.8: icmp_seq=1 ttl=38 time=168 ms > > 64 bytes from 8.8.8.8: icmp_seq=2 ttl=38 time=168 ms > > … > >   > > Dump the traffic on the “eno2”, got nothing > > $ sudo tcpdump -nn -i eno2 icmp > > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > > listening on eno2, link-type EN10MB (Ethernet), capture size 262144 bytes > > … > >   > > Dump the traffic on the “eno1” (internal NIC),  catch it! > > $ sudo tcpdump -nn -i eno1 icmp > > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > > listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes > > 16:08:59.609888 IP 192.168.20.132 > 8.8.8.8: ICMP echo request, id > 1439, seq 1, length 64 > > 16:08:59.781042 IP 8.8.8.8 > 192.168.20.132: ICMP echo reply, id 1439, > seq 1, length 64 > > 16:09:00.611453 IP 192.168.20.132 > 8.8.8.8: ICMP echo request, id > 1439, seq 2, length 64 > > 16:09:00.779550 IP 8.8.8.8 > 192.168.20.132: ICMP echo reply, id 1439, > seq 2, length 64 > >   > >   > > $ sudo ip route > > default via 192.168.18.1 dev eno1  proto static  metric 100 > > default via 192.168.8.1 dev eno2  proto static  metric 101 > > 169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown > > 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 > linkdown > > 192.168.8.0/24 dev eno2  proto kernel  scope link  src 192.168.8.101  > metric 100 > > 192.168.16.0/21 dev eno1  proto kernel  scope link  src > 192.168.20.132  metric 100 > > 192.168.42.0/24 dev br-ex  proto kernel  scope link  src 192.168.42.1 > >   > >   > > What’s going wrong here? Do I miss something? Or some service need to > be restarted? > >   > > Anyone could help me out?  This question made me sick for many days!  > Huge thanks in the advance! > >   > >   > > Best Regards, > > Dave > >   > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From Dave.Chen at Dell.com Sat Jun 16 03:28:35 2018 From: Dave.Chen at Dell.com (Dave.Chen at Dell.com) Date: Sat, 16 Jun 2018 03:28:35 +0000 Subject: [Openstack] [neutron][devstack][network] Question on the OVS configuration In-Reply-To: References: <8ef87a50c8b340c5aa8fb459baf16166@KULX13MDC117.APAC.DELL.COM> Message-ID: Thanks Bernd for pointing me to the link, that is definitely much helpful! Best Regards, Dave Chen From: Bernd Bausch [mailto:berndbausch at gmail.com] Sent: Saturday, June 16, 2018 6:49 AM To: openstack at lists.openstack.org Subject: Re: [Openstack] [neutron][devstack][network] Question on the OVS configuration Did you follow the networking guide https://docs.openstack.org/devstack/latest/guides/neutron.html? It has instructions for single- and multiple-NIC nodes. I believe the secret is in this setting: PUBLIC_INTERFACE=eth0 Plugging your eno2 into the bridge is not enough; as far as I understand it, you also need to move the IP address to the bridge and ensure that the bridge is UP. Perhaps the routing table must be tweaked as well, but in any case, the guides should achieve your goal. Bernd Bausch On 6/15/2018 7:34 PM, Dave.Chen at Dell.com wrote: Hi All, Let me brief my question, I have two NIC ports, one is connect to internal (eno1) and the other (eno2) is external, my openstack cluster is based on the devstack and neutron is configured as OVS + vxlan, How can I make my VM could be able to access external with eno2 port? I tried to add the port to br-ex but it seems doesn't work, the VM still go to the default route on the physical node which is via eno1. $ ovs-vsctl add-port br-ex eno2 Thanks in the advance for any comments! Best Regards, Dave Chen From: Chen2, Dave Sent: Friday, June 15, 2018 4:17 PM To: 'openstack-dev at lists.openstack.org' Cc: Chen2, Dave Subject: [neutron] Question on the OVS configuration Dear folks, I have setup a pretty simple OpenStack cluster in our lab based on devstack, couples of guest VM are running on one controller node (this doesn't looks like a right behavior anyway), the Neutron network is configured as OVS + vxlan, the bridge "br-ex" configured as below: Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} Port br-ex Interface br-ex type: internal ovs_version: "2.8.0" As you see, there is no external physical NIC bound to "br-ex", so I guess the traffic from the VM to external will use the default route set on the controller node, since there is a NIC (eno2) that can access external so I bind it to "br-ex" like this: ovs-vsctl add-port br-ex eno2. now the "br-ex" is configured as below: Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} *Port "eno2"* Interface "eno2" Port br-ex Interface br-ex type: internal ovs_version: "2.8.0" Looks like this is how it should be configured according to lots of wiki/blog suggestion I have googled, but it doesn't work as expected, ping from the VM, the tcpdump shows the traffic still go the "eno1" which is the default route on the controller node. Inside of VM ubuntu at test-br:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=38 time=168 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=38 time=168 ms ... Dump the traffic on the "eno2", got nothing $ sudo tcpdump -nn -i eno2 icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eno2, link-type EN10MB (Ethernet), capture size 262144 bytes ... Dump the traffic on the "eno1" (internal NIC), catch it! $ sudo tcpdump -nn -i eno1 icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes 16:08:59.609888 IP 192.168.20.132 > 8.8.8.8: ICMP echo request, id 1439, seq 1, length 64 16:08:59.781042 IP 8.8.8.8 > 192.168.20.132: ICMP echo reply, id 1439, seq 1, length 64 16:09:00.611453 IP 192.168.20.132 > 8.8.8.8: ICMP echo request, id 1439, seq 2, length 64 16:09:00.779550 IP 8.8.8.8 > 192.168.20.132: ICMP echo reply, id 1439, seq 2, length 64 $ sudo ip route default via 192.168.18.1 dev eno1 proto static metric 100 default via 192.168.8.1 dev eno2 proto static metric 101 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.8.0/24 dev eno2 proto kernel scope link src 192.168.8.101 metric 100 192.168.16.0/21 dev eno1 proto kernel scope link src 192.168.20.132 metric 100 192.168.42.0/24 dev br-ex proto kernel scope link src 192.168.42.1 What's going wrong here? Do I miss something? Or some service need to be restarted? Anyone could help me out? This question made me sick for many days! Huge thanks in the advance! Best Regards, Dave _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack at lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From poby1972 at gmail.com Sat Jun 16 14:30:10 2018 From: poby1972 at gmail.com (Kevin Kwon) Date: Sat, 16 Jun 2018 23:30:10 +0900 Subject: [Openstack] OpenStack Queens Manual Installation Message-ID: Dear All! Hi.. Would you please help to install the Openstack on Ubunto 16.04.4 Server manually. I have installed the Keystone, Glance and Nova with One Controller Node and One Compute node with Installation guide on OpenStack.org. after installed the Neutron and ran the "openstack network" command, i got below errors. Would you please let me know know how can solve this problem? root at OpenStack-Controller:~# root at OpenStack-Controller:~# openstack network list HttpException: Unknown error root at OpenStack-Controller:~# 2018-06-16 23:25:23.187 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET / HTTP/1.1" status: 200 len: 262 time: 0.0008469 2018-06-16 23:25:23.192 10706 WARNING keystoneauth.identity.generic.base [-] Failed to discover available identity versions when contacting http://OpenStack-Controller:35357. Attempting to parse version from URL.: ConnectFailure: Unable to establish connection to http://OpenStack-Controller:35357: HTTPConnectionPool(host='openstack-controller', port=35357): Max retries exceeded with url: / (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] ECONNREFUSED',)) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors [-] An error occurred during processing the request: GET /v2.0/networks HTTP/1.0 Accept: application/json Accept-Encoding: gzip, deflate Connection: keep-alive Content-Type: text/plain Host: openstack-controller:9696 User-Agent: osc-lib/1.9.0 keystoneauth1/3.4.0 python-requests/2.18.4 CPython/2.7.12 X-Auth-Token: *****: DiscoveryFailure: Could not determine a suitable URL for the plugin 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors Traceback (most recent call last): 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/oslo_middleware/catch_errors.py", line 40, in __call__ 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors response = req.get_response(self.application) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1316, in send 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors application, catch_exc_info=False) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1280, in call_application 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors app_iter = application(self.environ, start_response) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 131, in __call__ 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp = self.call_func(req, *args, **self.kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 196, in call_func 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return self.func(req, *args, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 334, in __call__ 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors response = self.process_request(req) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 633, in process_request 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp = super(AuthProtocol, self).process_request(request) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 407, in process_request 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 440, in _do_fetch_token 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors data = self.fetch_token(token, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 772, in fetch_token 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 219, in verify_token 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors auth_ref = self._request_strategy.verify_token( 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 170, in _request_strategy 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors strategy_class = self._get_strategy_class() 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 192, in _get_strategy_class 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors if self._adapter.get_endpoint(version=klass.AUTH_VERSION): 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 223, in get_endpoint 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return self.session.get_endpoint(auth or self.auth, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 942, in get_endpoint 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return auth.get_endpoint(self, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 379, in get_endpoint 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_version_hack=allow_version_hack, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 270, in get_endpoint_data 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors service_catalog = self.get_access(session).service_catalog 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 134, in get_access 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors self.auth_ref = self.get_auth_ref(session) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 199, in get_auth_ref 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors self._plugin = self._do_create_plugin(session) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 194, in _do_create_plugin 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors raise exceptions.DiscoveryFailure('Could not determine a suitable URL ' 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors DiscoveryFailure: Could not determine a suitable URL for the plugin 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors 2018-06-16 23:25:23.194 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET /v2.0/networks HTTP/1.1" status: 500 len: 404 time: 0.0042169 Thank you! Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From pablobrunetti at hotmail.com Sat Jun 16 15:22:43 2018 From: pablobrunetti at hotmail.com (pablo brunetti) Date: Sat, 16 Jun 2018 15:22:43 +0000 Subject: [Openstack] OpenStack Queens Manual Installation In-Reply-To: References: Message-ID: Hello Kevin, In installation of the Keystone OpenStack Queens the port 35357 is deprecated and should be replaced by port 5000. ConnectFailure: Unable to establish connection to http://OpenStack-Controller:35357 Review the entire Neutron installation, replacing port 35357 with 5000. I suggest deleting the database and popular again. I made a notification on bugs.launchpad, but was flagged as invalid, stating that the problem has already been fixed. https://bugs.launchpad.net/neutron/+bug/1773585 Best Regards. ________________________________ De: Kevin Kwon Enviado: sábado, 16 de junho de 2018 11:30 Para: openstack at lists.openstack.org Assunto: [Openstack] OpenStack Queens Manual Installation Dear All! Hi.. Would you please help to install the Openstack on Ubunto 16.04.4 Server manually. I have installed the Keystone, Glance and Nova with One Controller Node and One Compute node with Installation guide on OpenStack.org. after installed the Neutron and ran the "openstack network" command, i got below errors. Would you please let me know know how can solve this problem? root at OpenStack-Controller:~# root at OpenStack-Controller:~# openstack network list HttpException: Unknown error root at OpenStack-Controller:~# 2018-06-16 23:25:23.187 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET / HTTP/1.1" status: 200 len: 262 time: 0.0008469 2018-06-16 23:25:23.192 10706 WARNING keystoneauth.identity.generic.base [-] Failed to discover available identity versions when contacting http://OpenStack-Controller:35357. Attempting to parse version from URL.: ConnectFailure: Unable to establish connection to http://OpenStack-Controller:35357: HTTPConnectionPool(host='openstack-controller', port=35357): Max retries exceeded with url: / (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] ECONNREFUSED',)) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors [-] An error occurred during processing the request: GET /v2.0/networks HTTP/1.0 Accept: application/json Accept-Encoding: gzip, deflate Connection: keep-alive Content-Type: text/plain Host: openstack-controller:9696 User-Agent: osc-lib/1.9.0 keystoneauth1/3.4.0 python-requests/2.18.4 CPython/2.7.12 X-Auth-Token: *****: DiscoveryFailure: Could not determine a suitable URL for the plugin 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors Traceback (most recent call last): 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/oslo_middleware/catch_errors.py", line 40, in __call__ 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors response = req.get_response(self.application) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1316, in send 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors application, catch_exc_info=False) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1280, in call_application 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors app_iter = application(self.environ, start_response) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 131, in __call__ 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp = self.call_func(req, *args, **self.kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 196, in call_func 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return self.func(req, *args, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 334, in __call__ 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors response = self.process_request(req) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 633, in process_request 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp = super(AuthProtocol, self).process_request(request) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 407, in process_request 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 440, in _do_fetch_token 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors data = self.fetch_token(token, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 772, in fetch_token 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 219, in verify_token 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors auth_ref = self._request_strategy.verify_token( 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 170, in _request_strategy 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors strategy_class = self._get_strategy_class() 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 192, in _get_strategy_class 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors if self._adapter.get_endpoint(version=klass.AUTH_VERSION): 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 223, in get_endpoint 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return self.session.get_endpoint(auth or self.auth, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 942, in get_endpoint 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return auth.get_endpoint(self, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 379, in get_endpoint 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_version_hack=allow_version_hack, **kwargs) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 270, in get_endpoint_data 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors service_catalog = self.get_access(session).service_catalog 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 134, in get_access 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors self.auth_ref = self.get_auth_ref(session) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 199, in get_auth_ref 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors self._plugin = self._do_create_plugin(session) 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 194, in _do_create_plugin 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors raise exceptions.DiscoveryFailure('Could not determine a suitable URL ' 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors DiscoveryFailure: Could not determine a suitable URL for the plugin 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors 2018-06-16 23:25:23.194 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET /v2.0/networks HTTP/1.1" status: 500 len: 404 time: 0.0042169 Thank you! Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From emccormick at cirrusseven.com Sat Jun 16 15:32:30 2018 From: emccormick at cirrusseven.com (Erik McCormick) Date: Sat, 16 Jun 2018 11:32:30 -0400 Subject: [Openstack] OpenStack Queens Manual Installation In-Reply-To: References: Message-ID: Hi Kevin, Your problem is here. ConnectFailure: Unable to establish connection to http://OpenStack-Controller:35357 : Check to see if you can curl that URL. That is Neutron attempting to talk to Keystone and failing. On Sat, Jun 16, 2018, 10:43 AM Kevin Kwon wrote: > Dear All! > > Hi.. Would you please help to install the Openstack on Ubunto 16.04.4 > Server manually. > > I have installed the Keystone, Glance and Nova with One Controller Node > and One Compute node with Installation guide on OpenStack.org. > > after installed the Neutron and ran the "openstack network" command, i got > below errors. > > Would you please let me know know how can solve this problem? > > > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# openstack network list > HttpException: Unknown error > root at OpenStack-Controller:~# > > > 2018-06-16 23:25:23.187 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET / > HTTP/1.1" status: 200 len: 262 time: 0.0008469 > 2018-06-16 23:25:23.192 10706 WARNING keystoneauth.identity.generic.base > [-] Failed to discover available identity versions when contacting > http://OpenStack-Controller:35357. Attempting to parse version from URL.: > ConnectFailure: Unable to establish connection to > http://OpenStack-Controller:35357: > HTTPConnectionPool(host='openstack-controller', port=35357): Max retries > exceeded with url: / (Caused by > NewConnectionError(' 0x7ffa93656d50>: Failed to establish a new connection: [Errno 111] > ECONNREFUSED',)) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors [-] An > error occurred during processing the request: GET /v2.0/networks HTTP/1.0 > Accept: application/json > Accept-Encoding: gzip, deflate > Connection: keep-alive > Content-Type: text/plain > Host: openstack-controller:9696 > User-Agent: osc-lib/1.9.0 keystoneauth1/3.4.0 python-requests/2.18.4 > CPython/2.7.12 > X-Auth-Token: *****: DiscoveryFailure: Could not determine a suitable URL > for the plugin > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors Traceback > (most recent call last): > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/oslo_middleware/catch_errors.py", line > 40, in __call__ > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > response = req.get_response(self.application) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/webob/request.py", line 1316, in send > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > application, catch_exc_info=False) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/webob/request.py", line 1280, in > call_application > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > app_iter = application(self.environ, start_response) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/webob/dec.py", line 131, in __call__ > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp > = self.call_func(req, *args, **self.kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/webob/dec.py", line 196, in call_func > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > return self.func(req, *args, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", > line 334, in __call__ > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > response = self.process_request(req) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", > line 633, in process_request > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp > = super(AuthProtocol, self).process_request(request) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", > line 407, in process_request > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > allow_expired=allow_expired) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", > line 440, in _do_fetch_token > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors data > = self.fetch_token(token, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", > line 772, in fetch_token > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > allow_expired=allow_expired) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", > line 219, in verify_token > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > auth_ref = self._request_strategy.verify_token( > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", > line 170, in _request_strategy > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > strategy_class = self._get_strategy_class() > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", > line 192, in _get_strategy_class > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors if > self._adapter.get_endpoint(version=klass.AUTH_VERSION): > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 223, in > get_endpoint > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > return self.session.get_endpoint(auth or self.auth, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 942, in > get_endpoint > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > return auth.get_endpoint(self, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line > 379, in get_endpoint > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > allow_version_hack=allow_version_hack, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line > 270, in get_endpoint_data > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > service_catalog = self.get_access(session).service_catalog > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line > 134, in get_access > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > self.auth_ref = self.get_auth_ref(session) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", > line 199, in get_auth_ref > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > self._plugin = self._do_create_plugin(session) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File > "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", > line 194, in _do_create_plugin > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors raise > exceptions.DiscoveryFailure('Could not determine a suitable URL ' > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > DiscoveryFailure: Could not determine a suitable URL for the plugin > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > 2018-06-16 23:25:23.194 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET > /v2.0/networks HTTP/1.1" status: 500 len: 404 time: 0.0042169 > > Thank you! > Kevin > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From skaplons at redhat.com Sat Jun 16 19:51:53 2018 From: skaplons at redhat.com (Slawomir Kaplonski) Date: Sat, 16 Jun 2018 21:51:53 +0200 Subject: [Openstack] OpenStack Queens Manual Installation In-Reply-To: References: Message-ID: <0A578F6B-4A5F-49C5-8EF5-C567EE21A6AB@redhat.com> Hi, > Wiadomość napisana przez pablo brunetti w dniu 16.06.2018, o godz. 17:22: > > Hello Kevin, > > In installation of the Keystone OpenStack Queens the port 35357 is deprecated and should be replaced by port 5000. > > ConnectFailure: Unable to establish connection to http://OpenStack-Controller:35357 > > Review the entire Neutron installation, replacing port 35357 with 5000. I suggest deleting the database and popular again. In Neutron DB there is nothing about connection to keystone, so deleting db shouldn’t be necessary. I think that fixing Neutron’s config files should be enough. > > I made a notification on bugs.launchpad, but was flagged as invalid, stating that the problem has already been fixed. > > https://bugs.launchpad.net/neutron/+bug/1773585 > > > Best Regards. > > > De: Kevin Kwon > Enviado: sábado, 16 de junho de 2018 11:30 > Para: openstack at lists.openstack.org > Assunto: [Openstack] OpenStack Queens Manual Installation > > Dear All! > > Hi.. Would you please help to install the Openstack on Ubunto 16.04.4 Server manually. > > I have installed the Keystone, Glance and Nova with One Controller Node and One Compute node with Installation guide on OpenStack.org. > > after installed the Neutron and ran the "openstack network" command, i got below errors. > > Would you please let me know know how can solve this problem? > > > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# openstack network list > HttpException: Unknown error > root at OpenStack-Controller:~# > > > 2018-06-16 23:25:23.187 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET / HTTP/1.1" status: 200 len: 262 time: 0.0008469 > 2018-06-16 23:25:23.192 10706 WARNING keystoneauth.identity.generic.base [-] Failed to discover available identity versions when contacting http://OpenStack-Controller:35357. Attempting to parse version from URL.: ConnectFailure: Unable to establish connection to http://OpenStack-Controller:35357: HTTPConnectionPool(host='openstack-controller', port=35357): Max retries exceeded with url: / (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] ECONNREFUSED',)) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors [-] An error occurred during processing the request: GET /v2.0/networks HTTP/1.0 > Accept: application/json > Accept-Encoding: gzip, deflate > Connection: keep-alive > Content-Type: text/plain > Host: openstack-controller:9696 > User-Agent: osc-lib/1.9.0 keystoneauth1/3.4.0 python-requests/2.18.4 CPython/2.7.12 > X-Auth-Token: *****: DiscoveryFailure: Could not determine a suitable URL for the plugin > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors Traceback (most recent call last): > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/oslo_middleware/catch_errors.py", line 40, in __call__ > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors response = req.get_response(self.application) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1316, in send > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors application, catch_exc_info=False) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1280, in call_application > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors app_iter = application(self.environ, start_response) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 131, in __call__ > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp = self.call_func(req, *args, **self.kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 196, in call_func > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return self.func(req, *args, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 334, in __call__ > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors response = self.process_request(req) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 633, in process_request > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors resp = super(AuthProtocol, self).process_request(request) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 407, in process_request > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 440, in _do_fetch_token > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors data = self.fetch_token(token, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 772, in fetch_token > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 219, in verify_token > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors auth_ref = self._request_strategy.verify_token( > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 170, in _request_strategy > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors strategy_class = self._get_strategy_class() > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 192, in _get_strategy_class > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors if self._adapter.get_endpoint(version=klass.AUTH_VERSION): > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 223, in get_endpoint > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return self.session.get_endpoint(auth or self.auth, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 942, in get_endpoint > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors return auth.get_endpoint(self, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 379, in get_endpoint > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors allow_version_hack=allow_version_hack, **kwargs) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 270, in get_endpoint_data > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors service_catalog = self.get_access(session).service_catalog > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/base.py", line 134, in get_access > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors self.auth_ref = self.get_auth_ref(session) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 199, in get_auth_ref > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors self._plugin = self._do_create_plugin(session) > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 194, in _do_create_plugin > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors raise exceptions.DiscoveryFailure('Could not determine a suitable URL ' > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors DiscoveryFailure: Could not determine a suitable URL for the plugin > 2018-06-16 23:25:23.192 10706 ERROR oslo_middleware.catch_errors > 2018-06-16 23:25:23.194 10706 INFO neutron.wsgi [-] 192.168.56.101 "GET /v2.0/networks HTTP/1.1" status: 500 len: 404 time: 0.0042169 > > Thank you! > Kevin > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack — Slawek Kaplonski Senior software engineer Red Hat From poby1972 at gmail.com Sat Jun 16 23:40:29 2018 From: poby1972 at gmail.com (Kevin Kwon) Date: Sun, 17 Jun 2018 08:40:29 +0900 Subject: [Openstack] Install Glance on Queens Message-ID: Dear All. In below link which is OpenStack Website. https://docs.openstack.org/glance/queens/install/install-ubuntu.html#install-and-configure-components It is showing like below. In the [keystone_authtoken] and [paste_deploy] sections, configure Identity service access: [keystone_authtoken] # ... auth_uri = http://controller:5000 auth_url = http://controller:5000 memcached_servers = controller:11211 auth_type = password project_domain_name = Default user_domain_name = Default project_name = service username = glance password = GLANCE_PASS [paste_deploy] # ... flavor = keystone Why i have to add same two blow lines in the " /etc/glance/glance-api.conf" file? auth_uri = http://controller:5000 auth_url = http://controller:5000 Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Sun Jun 17 00:00:48 2018 From: amy at demarco.com (Amy Marrich) Date: Sat, 16 Jun 2018 19:00:48 -0500 Subject: [Openstack] Install Glance on Queens In-Reply-To: References: Message-ID: Kevin, Those are 2 separate entries. The first is the auth_uri and the second is the auth_url. The lower case I and the lower case L look almost identical in some fonts. The auth_uri is what you'll see in the WWW-Authenticate: keystone-uri header so should be an unversioned public endpoint while the auth_url is what the auth plugin is using. Amy (spotz) On Sat, Jun 16, 2018 at 6:40 PM, Kevin Kwon wrote: > > Dear All. > > In below link which is OpenStack Website. > https://docs.openstack.org/glance/queens/install/install- > ubuntu.html#install-and-configure-components > > It is showing like below. > > In the [keystone_authtoken] and [paste_deploy] sections, configure > Identity service access: > > [keystone_authtoken] > # ... > auth_uri = http://controller:5000 > auth_url = http://controller:5000 > memcached_servers = controller:11211 > auth_type = password > project_domain_name = Default > user_domain_name = Default > project_name = service > username = glance > password = GLANCE_PASS > > [paste_deploy] > # ... > flavor = keystone > > Why i have to add same two blow lines in the " /etc/glance/glance-api.conf" > file? > auth_uri = http://controller:5000 > auth_url = http://controller:5000 > > Kevin > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zijian1012 at 163.com Sun Jun 17 03:44:03 2018 From: zijian1012 at 163.com (jython) Date: Sun, 17 Jun 2018 11:44:03 +0800 Subject: [Openstack] cinder-schduler multi workers Message-ID: <824D5EA0-356A-43AD-9B9D-73AD2294434F@163.com> Here is a patch about "multiple process workers support for nova-scheduler" https://review.openstack.org/#/c/159382/ Before the placement service takes over nova-scheduler, nova-scheduler will have problems with thread-safe, inconsistent, etc. therefore, the patch was not merged until the implementation of the placement-claims mechanism, It was recently merged into the master branch https://github.com/openstack/nova/blob/master/nova/cmd/scheduler.py So, I think the cinder-scheduler also has this problem. -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoquqi at gmail.com Mon Jun 18 00:34:35 2018 From: xiaoquqi at gmail.com (Ray Sun) Date: Mon, 18 Jun 2018 08:34:35 +0800 Subject: [Openstack] [OpenStack][Kolla]Choose binary or source Message-ID: OpenStackers, I have several questions for using kolla deployment in production: 1. Binary or source? Which one is mostly used in production 2. Which one is easy to operation, like updating..... 3. Is there any document to describe how to operation kolla deployment OpenStack, seems it's not the quite same with the bare metal deployment. Thanks. Best Regards -- Ray -------------- next part -------------- An HTML attachment was scrubbed... URL: From emccormick at cirrusseven.com Mon Jun 18 02:22:07 2018 From: emccormick at cirrusseven.com (Erik McCormick) Date: Sun, 17 Jun 2018 22:22:07 -0400 Subject: [Openstack] [OpenStack][Kolla]Choose binary or source In-Reply-To: References: Message-ID: On Sun, Jun 17, 2018, 8:46 PM Ray Sun wrote: > OpenStackers, > I have several questions for using kolla deployment in production: > 1. Binary or source? Which one is mostly used in production > I've heard a lot more reports from people running source, but this is anecdotal 2. Which one is easy to operation, like updating.. > IMHO source is better for updates. With binary you sit around waiting for packages to decide a patch or stable milestone is worthy of dropping new packages. With source you can get things when they hit stable branches upstream. I did exactly one binary deployment, waited forever for a patch I needed, and swore off doing it that way forever more. Operations are the same either way really. ... > 3. Is there any document to describe how to operation kolla deployment > OpenStack, seems it's not the quite same with the bare metal deployment. > The deployment docs are quite good. There isn't really a good ops guide though. This is true of bare metal as well though ( in process of being addressed presently). The IRC channel is terrific though, so if you hit a wall, pop on there and ask for help or email this list with a tag like you did here. > > Thanks. > > Best Regards > -- Ray > Cherrs, Erik _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoquqi at gmail.com Mon Jun 18 02:46:59 2018 From: xiaoquqi at gmail.com (Ray Sun) Date: Mon, 18 Jun 2018 10:46:59 +0800 Subject: [Openstack] [OpenStack][Kolla]Choose binary or source In-Reply-To: References: Message-ID: Eric, Thanks for your reply. I just consider one senario: if I deployed use source, if source is updated, do I need to rebuild the docker image and do an update? Or is there any better way? Best Regards -- Ray On Mon, Jun 18, 2018 at 10:22 AM Erik McCormick wrote: > > > On Sun, Jun 17, 2018, 8:46 PM Ray Sun wrote: > >> OpenStackers, >> I have several questions for using kolla deployment in production: >> > 1. Binary or source? Which one is mostly used in production >> > > I've heard a lot more reports from people running source, but this is > anecdotal > > 2. Which one is easy to operation, like updating.. >> > > IMHO source is better for updates. With binary you sit around waiting for > packages to decide a patch or stable milestone is worthy of dropping new > packages. With source you can get things when they hit stable branches > upstream. I did exactly one binary deployment, waited forever for a patch I > needed, and swore off doing it that way forever more. > > Operations are the same either way really. > > ... >> 3. Is there any document to describe how to operation kolla deployment >> OpenStack, seems it's not the quite same with the bare metal deployment. >> > > The deployment docs are quite good. There isn't really a good ops guide > though. This is true of bare metal as well though ( in process of being > addressed presently). The IRC channel is terrific though, so if you hit a > wall, pop on there and ask for help or email this list with a tag like you > did here. > >> >> Thanks. >> >> Best Regards >> -- Ray >> > > Cherrs, > Erik > > _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack at lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emccormick at cirrusseven.com Mon Jun 18 03:35:13 2018 From: emccormick at cirrusseven.com (Erik McCormick) Date: Sun, 17 Jun 2018 23:35:13 -0400 Subject: [Openstack] [OpenStack][Kolla]Choose binary or source In-Reply-To: References: Message-ID: On Sun, Jun 17, 2018, 10:47 PM Ray Sun wrote: > Eric, > Thanks for your reply. > > I just consider one senario: if I deployed use source, if source is > updated, do I need to rebuild the docker image and do an update? Or is > there any better way? > > Best Regards > -- Ray > If you want the updates, then build new containers with new tags and run the upgrade playbook. You can do this even just for one project. The process is the same for binary or source. If you want updates, build new containers with newer tags. You don't upgrade the already-running containers in place. -Erik > > On Mon, Jun 18, 2018 at 10:22 AM Erik McCormick < > emccormick at cirrusseven.com> wrote: > >> >> >> On Sun, Jun 17, 2018, 8:46 PM Ray Sun wrote: >> >>> OpenStackers, >>> I have several questions for using kolla deployment in production: >>> >> 1. Binary or source? Which one is mostly used in production >>> >> >> I've heard a lot more reports from people running source, but this is >> anecdotal >> >> 2. Which one is easy to operation, like updating.. >>> >> >> IMHO source is better for updates. With binary you sit around waiting for >> packages to decide a patch or stable milestone is worthy of dropping new >> packages. With source you can get things when they hit stable branches >> upstream. I did exactly one binary deployment, waited forever for a patch I >> needed, and swore off doing it that way forever more. >> >> Operations are the same either way really. >> >> ... >>> 3. Is there any document to describe how to operation kolla deployment >>> OpenStack, seems it's not the quite same with the bare metal deployment. >>> >> >> The deployment docs are quite good. There isn't really a good ops guide >> though. This is true of bare metal as well though ( in process of being >> addressed presently). The IRC channel is terrific though, so if you hit a >> wall, pop on there and ask for help or email this list with a tag like you >> did here. >> >>> >>> Thanks. >>> >>> Best Regards >>> -- Ray >>> >> >> Cherrs, >> Erik >> >> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : openstack at lists.openstack.org >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoquqi at gmail.com Mon Jun 18 04:14:28 2018 From: xiaoquqi at gmail.com (Ray Sun) Date: Mon, 18 Jun 2018 12:14:28 +0800 Subject: [Openstack] [OpenStack][Kolla]Choose binary or source In-Reply-To: References: Message-ID: Ok, thanks for the info. Best Regards -- Ray On Mon, Jun 18, 2018 at 11:35 AM Erik McCormick wrote: > > > On Sun, Jun 17, 2018, 10:47 PM Ray Sun wrote: > >> Eric, >> Thanks for your reply. >> >> I just consider one senario: if I deployed use source, if source is >> updated, do I need to rebuild the docker image and do an update? Or is >> there any better way? >> >> Best Regards >> -- Ray >> > > If you want the updates, then build new containers with new tags and run > the upgrade playbook. You can do this even just for one project. > > The process is the same for binary or source. If you want updates, build > new containers with newer tags. You don't upgrade the already-running > containers in place. > > -Erik > > >> >> On Mon, Jun 18, 2018 at 10:22 AM Erik McCormick < >> emccormick at cirrusseven.com> wrote: >> >>> >>> >>> On Sun, Jun 17, 2018, 8:46 PM Ray Sun wrote: >>> >>>> OpenStackers, >>>> I have several questions for using kolla deployment in production: >>>> >>> 1. Binary or source? Which one is mostly used in production >>>> >>> >>> I've heard a lot more reports from people running source, but this is >>> anecdotal >>> >>> 2. Which one is easy to operation, like updating.. >>>> >>> >>> IMHO source is better for updates. With binary you sit around waiting >>> for packages to decide a patch or stable milestone is worthy of dropping >>> new packages. With source you can get things when they hit stable branches >>> upstream. I did exactly one binary deployment, waited forever for a patch I >>> needed, and swore off doing it that way forever more. >>> >>> Operations are the same either way really. >>> >>> ... >>>> 3. Is there any document to describe how to operation kolla deployment >>>> OpenStack, seems it's not the quite same with the bare metal deployment. >>>> >>> >>> The deployment docs are quite good. There isn't really a good ops guide >>> though. This is true of bare metal as well though ( in process of being >>> addressed presently). The IRC channel is terrific though, so if you hit a >>> wall, pop on there and ask for help or email this list with a tag like you >>> did here. >>> >>>> >>>> Thanks. >>>> >>>> Best Regards >>>> -- Ray >>>> >>> >>> Cherrs, >>> Erik >>> >>> _______________________________________________ >>>> Mailing list: >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>>> Post to : openstack at lists.openstack.org >>>> Unsubscribe : >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From kamil.madac at gmail.com Mon Jun 18 08:34:39 2018 From: kamil.madac at gmail.com (Kamil Madac) Date: Mon, 18 Jun 2018 10:34:39 +0200 Subject: [Openstack] DietStack lightweight deployment Message-ID: Hi OpenStack community, In my spare time I'm working on deployment of OpenStack called DietStack. It started as a small POC and it turned out, but it is working for me, so I'm making it publicly available under Apache2 license. DietStack is aimed to cover small OpenStack deployments where end-user (small development shops, schools, training labs, home users) have few machines, doesn't need HA, does not want to spend hours with studying of all OpenStack config files or to hire consultants to build and manage the private cloud and still wants to profit from programmable infrastructure and other advantages of Openstack private cloud. DietStack makes OpenStack deployment easy without need of configuration management tool like Ansible/Chef/Puppet. It is just set of small docker images which are run by bash script. You could still want to use configuration management tools, to run ds.sh on multiple machines, and it is completely ok, but as it is about running just one command on multiple machines I'm leaving it on end-user. Main focus: 1. Linux, Bash and Docker are the only requirements. 2. One fixed configuration (KVM as Hypervisor, VXLANS on Linux Bridges for Neutron and NFS as Cinder backend), no need to fiddle with config files. 3. Upstream versions of openstack services are used to build docker images 4. Deployment is one simple bash script and configuration is done over environment variables. Config files for services are generated automatically within containers. Docker images are based on Debian 9. Current version is build on Pike. Currently, deployment on Debian 9 and Ubuntu 16.04 and 18.04 is tested. Github: https://github.com/dietstack/dietstack Documentation: http://dietstack.readthedocs.io It is still hobby project but if there is anyone who likes the idea and would like to try it or even contribute you are welcome and I'm ready to help :). -- Kamil Madac From e0ne at e0ne.info Mon Jun 18 10:03:04 2018 From: e0ne at e0ne.info (Ivan Kolodyazhny) Date: Mon, 18 Jun 2018 13:03:04 +0300 Subject: [Openstack] cinder-schduler multi workers In-Reply-To: <824D5EA0-356A-43AD-9B9D-73AD2294434F@163.com> References: <824D5EA0-356A-43AD-9B9D-73AD2294434F@163.com> Message-ID: Hi Jython, Thank you for pointing attention to it. cinder-scheduler keeps all data in memory, so we can't just increase workers count to scale it. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Sun, Jun 17, 2018 at 6:44 AM, jython wrote: > Here is a patch about "multiple process workers support for > nova-scheduler" https://review.openstack.org/#/c/159382/ > > Before the placement service takes over nova-scheduler, nova-scheduler > will have problems with thread-safe, inconsistent, etc. therefore, the > patch was not merged until the implementation of the placement-claims > mechanism, It was recently merged into the master branch > https://github.com/openstack/nova/blob/master/nova/cmd/scheduler.py > > So, I think the cinder-scheduler also has this problem. > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfernandes at toulouse.viveris.com Mon Jun 18 10:26:00 2018 From: dfernandes at toulouse.viveris.com (David Fernandes) Date: Mon, 18 Jun 2018 12:26:00 +0200 Subject: [Openstack] Is it possible to use OVS inside an Openstack VM ? Message-ID: Hi guys, I have just 1 question. Is it possible to use OVS inside an Openstack VM ? Let me explain my issue. I have created 2 Ubuntu 16.04 VMs and installed last version of OVS in both. Both VMs are connected to the same network and they can ping each other. Then, I have created an OVS bridge (namely "br-test") in the first VM and I have added the port of the VM (ens1) to the ovs bridge as usual. At this point I cant't ping from one VM to the other. If I perform tcpdump on the bridge (tcpdump br-test), I see that ARP requests are sent but they are not sent by the interface of the VM (ens1). I tried to add the MAC addreses manually to the ARP table of each VM. When I ping, I see the same case :  icmp packets outgoing the bridge br-test but never sent by the interface ens1 of the VM. I have tried the same scenario using a linux bridge instead of OVS swithch and it works. Do you have any idea of why there are issues binding VM interface to OVS bridges ? Any information will be really apreciated !! Thanks in advance !!! David -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayachander.it at gmail.com Mon Jun 18 10:48:39 2018 From: jayachander.it at gmail.com (Jay See) Date: Mon, 18 Jun 2018 12:48:39 +0200 Subject: [Openstack] network is unreachable in instance Message-ID: I have created question on ask.opestack, but profile is still not approved by moderators. (https://ask.openstack.org/en/question/114803/network-is- unreachable-in-instance/) Someone in IRC suggested to send the mail here. Problem seems to be similar to, but I am not able to follow the bug to fix the issue - https://ask.openstack.org/en/question/80462/network-is- unreachable-in-instance/ We have 3 controller nodes connected to 12 compute nodes. Eth3 port on all the compute node is down. [Thu Jun 14 14:38:57] root@:~# node-ping-check Ping check of all service-ip, vm-ip, data-ip and floating-ip, ping status result after ip, 1/0 = alive/dead command start time 2018-06-14 14:39:00 node service-ip vm-ip data-ip floating-ip --------------------------------------------------------------------- h002 10.1.12.102 1 10.2.12.102 1 10.3.13.102 1 10.4.13.102 1 (controller 1) h003 10.1.12.103 1 10.2.12.103 1 10.3.13.103 1 10.4.13.103 1 (controller 2) h004 10.1.12.104 1 10.2.12.104 1 10.3.13.104 1 10.4.13.104 1 (controller 3 + Network node) h005 10.1.12.105 1 10.2.12.105 1 10.3.13.105 1 10.4.13.105 0 h006 10.1.12.106 1 10.2.12.106 1 10.3.13.106 1 10.4.13.106 0 h007 10.1.12.107 1 10.2.12.107 1 10.3.13.107 1 10.4.13.107 0 h008 10.1.12.108 1 10.2.12.108 1 10.3.13.108 1 10.4.13.108 0 h009 10.1.12.109 1 10.2.12.109 1 10.3.13.109 1 10.4.13.109 0 h010 10.1.12.110 1 10.2.12.110 1 10.3.13.110 1 10.4.13.110 0 h011 10.1.14.111 1 10.2.14.111 1 10.3.15.111 1 10.4.15.111 0 h012 10.1.14.112 1 10.2.14.112 1 10.3.15.112 1 10.4.15.112 0 h013 10.1.14.113 1 10.2.14.113 1 10.3.15.113 1 10.4.15.113 0 h014 10.1.14.114 1 10.2.14.114 1 10.3.15.114 1 10.4.15.114 0 h015 10.1.14.115 1 10.2.14.115 1 10.3.15.115 1 10.4.15.115 0 h016 10.1.14.116 0 10.2.14.116 0 10.3.15.116 0 10.4.15.116 0 ( Down because of hardware issue) h017 10.1.14.117 1 10.2.14.117 1 10.3.15.117 1 10.4.15.117 0 [Thu Jun 14 14:39:39] root@:~# To bring eth3 on Network node followed following steps: ifconfig eth3 down ifconfig eth3 0.0.0.0 up ovs-vsctl del-br br-ex ovs-vsctl add-br br-ex ovs-vsctl add-port br-ex eth3 ifconfig br-ex 10.4.13.104 netmask 255.255.255.0 route add -net 10.4.0.0 netmask 255.255.0.0 gateway 10.4.13.1 dev br-ex On Network node: [2018-06-18 11:38:24] root at h004:~$ ip netns exec qdhcp-eb7573a0-9d91-491c-b150-90f0135778ad ping 12.12.0.4 PING 12.12.0.4 (12.12.0.4) 56(84) bytes of data. 64 bytes from 12.12.0.4: icmp_seq=1 ttl=64 time=1.98 ms 64 bytes from 12.12.0.4: icmp_seq=2 ttl=64 time=0.529 ms ^C --- 12.12.0.4 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.529/1.254/1.980/0.726 ms [2018-06-18 11:38:33] root at h004:~$ ip netns exec qdhcp-eb7573a0-9d91-491c-b150-90f0135778ad ssh cirros at 12.12.0.4 ^C [SSH Not working] [2018-06-18 11:45:51] root at h004:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets connect: Network is unreachable [2018-06-18 11:58:01] root at h004:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 12.12.0.4 traceroute to 12.12.0.4 (12.12.0.4), 30 hops max, 60 byte packets On Compute node: [2018-06-18 11:56:12] root at h011:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets connect: Network is unreachable [2018-06-18 11:59:20] root at h011:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc ping 12.12.0.4 PING 12.12.0.4 (12.12.0.4) 56(84) bytes of data. 64 bytes from 12.12.0.4: icmp_seq=1 ttl=64 time=1.61 ms 64 bytes from 12.12.0.4: icmp_seq=2 ttl=64 time=0.273 ms ^C --- 12.12.0.4 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.273/0.943/1.614/0.671 ms [2018-06-18 12:02:21] root at h011:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc ping x.x.170.61 (floating ip) connect: Network is unreachable -- ​ P *SAVE PAPER – Please do not print this e-mail unless absolutely necessary.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From skaplons at redhat.com Mon Jun 18 11:28:54 2018 From: skaplons at redhat.com (Slawomir Kaplonski) Date: Mon, 18 Jun 2018 13:28:54 +0200 Subject: [Openstack] network is unreachable in instance In-Reply-To: References: Message-ID: Hi, > Wiadomość napisana przez Jay See w dniu 18.06.2018, o godz. 12:48: > > > I have created question on ask.opestack, but profile is still not approved by moderators. (https://ask.openstack.org/en/question/114803/network-is-unreachable-in-instance/) Someone in IRC suggested to send the mail here. > > > Problem seems to be similar to, but I am not able to follow the bug to fix the issue - https://ask.openstack.org/en/question/80462/network-is-unreachable-in-instance/ > > We have 3 controller nodes connected to 12 compute nodes. Eth3 port on all the compute node is down. > > [Thu Jun 14 14:38:57] root@:~# node-ping-check > > Ping check of all service-ip, vm-ip, data-ip and floating-ip, ping > status result after ip, 1/0 = alive/dead > > command start time 2018-06-14 14:39:00 > > node service-ip vm-ip data-ip floating-ip > --------------------------------------------------------------------- > h002 10.1.12.102 1 10.2.12.102 1 10.3.13.102 1 10.4.13.102 1 (controller 1) > h003 10.1.12.103 1 10.2.12.103 1 10.3.13.103 1 10.4.13.103 1 (controller 2) > h004 10.1.12.104 1 10.2.12.104 1 10.3.13.104 1 10.4.13.104 1 (controller 3 + Network node) > h005 10.1.12.105 1 10.2.12.105 1 10.3.13.105 1 10.4.13.105 0 > h006 10.1.12.106 1 10.2.12.106 1 10.3.13.106 1 10.4.13.106 0 > h007 10.1.12.107 1 10.2.12.107 1 10.3.13.107 1 10.4.13.107 0 > h008 10.1.12.108 1 10.2.12.108 1 10.3.13.108 1 10.4.13.108 0 > h009 10.1.12.109 1 10.2.12.109 1 10.3.13.109 1 10.4.13.109 0 > h010 10.1.12.110 1 10.2.12.110 1 10.3.13.110 1 10.4.13.110 0 > h011 10.1.14.111 1 10.2.14.111 1 10.3.15.111 1 10.4.15.111 0 > h012 10.1.14.112 1 10.2.14.112 1 10.3.15.112 1 10.4.15.112 0 > h013 10.1.14.113 1 10.2.14.113 1 10.3.15.113 1 10.4.15.113 0 > h014 10.1.14.114 1 10.2.14.114 1 10.3.15.114 1 10.4.15.114 0 > h015 10.1.14.115 1 10.2.14.115 1 10.3.15.115 1 10.4.15.115 0 > h016 10.1.14.116 0 10.2.14.116 0 10.3.15.116 0 10.4.15.116 0 ( Down because of hardware issue) > h017 10.1.14.117 1 10.2.14.117 1 10.3.15.117 1 10.4.15.117 0 > > [Thu Jun 14 14:39:39] root@:~# > > > To bring eth3 on Network node followed following steps: > > ifconfig eth3 down > ifconfig eth3 0.0.0.0 up > > ovs-vsctl del-br br-ex > ovs-vsctl add-br br-ex When You removed and added again br-ex it has no any openflow rules configured. So there will be no traffic passed via this bridge at all please try to restart neutron-openvswitch-agent and check if rules are recreated. If that will help, You can apply patch https://review.openstack.org/#/c/573696/ and check if that will help :) > ovs-vsctl add-port br-ex eth3 > ifconfig br-ex 10.4.13.104 netmask 255.255.255.0 > route add -net 10.4.0.0 netmask 255.255.0.0 gateway 10.4.13.1 dev br-ex > > > On Network node: > > [2018-06-18 11:38:24] root at h004:~$ ip netns exec qdhcp-eb7573a0-9d91-491c-b150-90f0135778ad ping 12.12.0.4 > PING 12.12.0.4 (12.12.0.4) 56(84) bytes of data. > 64 bytes from 12.12.0.4: icmp_seq=1 ttl=64 time=1.98 ms > 64 bytes from 12.12.0.4: icmp_seq=2 ttl=64 time=0.529 ms > ^C > --- 12.12.0.4 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > rtt min/avg/max/mdev = 0.529/1.254/1.980/0.726 ms > [2018-06-18 11:38:33] root at h004:~$ ip netns exec qdhcp-eb7573a0-9d91-491c-b150-90f0135778ad ssh cirros at 12.12.0.4 > ^C > [SSH Not working] > > [2018-06-18 11:45:51] root at h004:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 8.8.8.8 > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets > connect: Network is unreachable > [2018-06-18 11:58:01] root at h004:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 12.12.0.4 > traceroute to 12.12.0.4 (12.12.0.4), 30 hops max, 60 byte packets > > > On Compute node: > [2018-06-18 11:56:12] root at h011:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 8.8.8.8 > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets > connect: Network is unreachable > > [2018-06-18 11:59:20] root at h011:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc ping 12.12.0.4 > PING 12.12.0.4 (12.12.0.4) 56(84) bytes of data. > 64 bytes from 12.12.0.4: icmp_seq=1 ttl=64 time=1.61 ms > 64 bytes from 12.12.0.4: icmp_seq=2 ttl=64 time=0.273 ms > ^C > --- 12.12.0.4 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > rtt min/avg/max/mdev = 0.273/0.943/1.614/0.671 ms > [2018-06-18 12:02:21] root at h011:~$ ip netns exec qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc ping x.x.170.61 (floating ip) > connect: Network is unreachable > > > > -- > ​P SAVE PAPER – Please do not print this e-mail unless absolutely necessary. > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack — Slawek Kaplonski Senior software engineer Red Hat From mrhillsman at gmail.com Mon Jun 18 14:30:02 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Mon, 18 Jun 2018 09:30:02 -0500 Subject: [Openstack] Reminder: UC Meeting Today 1800UTC Message-ID: Hey everyone, Please see https://wiki.openstack.org/wiki/Governance/Foundation/ UserCommittee for UC meeting info and add additional agenda items if needed. -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayachander.it at gmail.com Mon Jun 18 16:14:17 2018 From: jayachander.it at gmail.com (Jay See) Date: Mon, 18 Jun 2018 18:14:17 +0200 Subject: [Openstack] network is unreachable in instance In-Reply-To: References: Message-ID: Hai, I think , I am not effected by this bug. As we have around 220 vm max. But as suggested in bug, do I need to set this on all nodes. (1. controller 2. Network and 3. Compute) or just network node? As br-ex bridge is been used , I am supposed to use only br-ex while setting. ovs-vsctl set bridge other-config:mac-table-size=50000 Regarding the MTU link suggested by Slawomir Kaplonski in IRC discussion, we are using 1500 MTU consistently in all those locations. PS: I am not expert in openstack system, just started working on existing system ~ Jayachander. On Mon, Jun 18, 2018 at 1:28 PM, Slawomir Kaplonski wrote: > Hi, > > > Wiadomość napisana przez Jay See w dniu > 18.06.2018, o godz. 12:48: > > > > > > I have created question on ask.opestack, but profile is still not > approved by moderators. (https://ask.openstack.org/en/ > question/114803/network-is-unreachable-in-instance/) Someone in IRC > suggested to send the mail here. > > > > > > Problem seems to be similar to, but I am not able to follow the bug to > fix the issue - https://ask.openstack.org/en/question/80462/network-is- > unreachable-in-instance/ > > > > We have 3 controller nodes connected to 12 compute nodes. Eth3 port on > all the compute node is down. > > > > [Thu Jun 14 14:38:57] root@:~# node-ping-check > > > > Ping check of all service-ip, vm-ip, data-ip and floating-ip, ping > > status result after ip, 1/0 = alive/dead > > > > command start time 2018-06-14 14:39:00 > > > > node service-ip vm-ip data-ip floating-ip > > --------------------------------------------------------------------- > > h002 10.1.12.102 1 10.2.12.102 1 10.3.13.102 1 10.4.13.102 1 > (controller 1) > > h003 10.1.12.103 1 10.2.12.103 1 10.3.13.103 1 10.4.13.103 1 > (controller 2) > > h004 10.1.12.104 1 10.2.12.104 1 10.3.13.104 1 10.4.13.104 1 > (controller 3 + Network node) > > h005 10.1.12.105 1 10.2.12.105 1 10.3.13.105 1 10.4.13.105 0 > > h006 10.1.12.106 1 10.2.12.106 1 10.3.13.106 1 10.4.13.106 0 > > h007 10.1.12.107 1 10.2.12.107 1 10.3.13.107 1 10.4.13.107 0 > > h008 10.1.12.108 1 10.2.12.108 1 10.3.13.108 1 10.4.13.108 0 > > h009 10.1.12.109 1 10.2.12.109 1 10.3.13.109 1 10.4.13.109 0 > > h010 10.1.12.110 1 10.2.12.110 1 10.3.13.110 1 10.4.13.110 0 > > h011 10.1.14.111 1 10.2.14.111 1 10.3.15.111 1 10.4.15.111 0 > > h012 10.1.14.112 1 10.2.14.112 1 10.3.15.112 1 10.4.15.112 0 > > h013 10.1.14.113 1 10.2.14.113 1 10.3.15.113 1 10.4.15.113 0 > > h014 10.1.14.114 1 10.2.14.114 1 10.3.15.114 1 10.4.15.114 0 > > h015 10.1.14.115 1 10.2.14.115 1 10.3.15.115 1 10.4.15.115 0 > > h016 10.1.14.116 0 10.2.14.116 0 10.3.15.116 0 10.4.15.116 0 ( > Down because of hardware issue) > > h017 10.1.14.117 1 10.2.14.117 1 10.3.15.117 1 10.4.15.117 0 > > > > [Thu Jun 14 14:39:39] root@:~# > > > > > > To bring eth3 on Network node followed following steps: > > > > ifconfig eth3 down > > ifconfig eth3 0.0.0.0 up > > > > ovs-vsctl del-br br-ex > > ovs-vsctl add-br br-ex > > When You removed and added again br-ex it has no any openflow rules > configured. So there will be no traffic passed via this bridge at all > please try to restart neutron-openvswitch-agent and check if rules are > recreated. > If that will help, You can apply patch https://review.openstack.org/# > /c/573696/ and check if that will help :) > > > ovs-vsctl add-port br-ex eth3 > > ifconfig br-ex 10.4.13.104 netmask 255.255.255.0 > > route add -net 10.4.0.0 netmask 255.255.0.0 gateway 10.4.13.1 dev br-ex > > > > > > On Network node: > > > > [2018-06-18 11:38:24] root at h004:~$ ip netns exec > qdhcp-eb7573a0-9d91-491c-b150-90f0135778ad ping 12.12.0.4 > > PING 12.12.0.4 (12.12.0.4) 56(84) bytes of data. > > 64 bytes from 12.12.0.4: icmp_seq=1 ttl=64 time=1.98 ms > > 64 bytes from 12.12.0.4: icmp_seq=2 ttl=64 time=0.529 ms > > ^C > > --- 12.12.0.4 ping statistics --- > > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > > rtt min/avg/max/mdev = 0.529/1.254/1.980/0.726 ms > > [2018-06-18 11:38:33] root at h004:~$ ip netns exec > qdhcp-eb7573a0-9d91-491c-b150-90f0135778ad ssh cirros at 12.12.0.4 > > ^C > > [SSH Not working] > > > > [2018-06-18 11:45:51] root at h004:~$ ip netns exec > qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 8.8.8.8 > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets > > connect: Network is unreachable > > [2018-06-18 11:58:01] root at h004:~$ ip netns exec > qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 12.12.0.4 > > traceroute to 12.12.0.4 (12.12.0.4), 30 hops max, 60 byte packets > > > > > > On Compute node: > > [2018-06-18 11:56:12] root at h011:~$ ip netns exec > qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc traceroute 8.8.8.8 > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets > > connect: Network is unreachable > > > > [2018-06-18 11:59:20] root at h011:~$ ip netns exec > qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc ping 12.12.0.4 > > PING 12.12.0.4 (12.12.0.4) 56(84) bytes of data. > > 64 bytes from 12.12.0.4: icmp_seq=1 ttl=64 time=1.61 ms > > 64 bytes from 12.12.0.4: icmp_seq=2 ttl=64 time=0.273 ms > > ^C > > --- 12.12.0.4 ping statistics --- > > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > > rtt min/avg/max/mdev = 0.273/0.943/1.614/0.671 ms > > [2018-06-18 12:02:21] root at h011:~$ ip netns exec > qrouter-d770b552-1979-4063-ae79-c6ff402c8cbc ping x.x.170.61 (floating > ip) > > connect: Network is unreachable > > > > > > > > -- > > ​P SAVE PAPER – Please do not print this e-mail unless absolutely > necessary. > > _______________________________________________ > > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > Post to : openstack at lists.openstack.org > > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > — > Slawek Kaplonski > Senior software engineer > Red Hat > > -- ​ P *SAVE PAPER – Please do not print this e-mail unless absolutely necessary.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From haleyb.dev at gmail.com Mon Jun 18 18:21:01 2018 From: haleyb.dev at gmail.com (Brian Haley) Date: Mon, 18 Jun 2018 14:21:01 -0400 Subject: [Openstack] Is it possible to use OVS inside an Openstack VM ? In-Reply-To: References: Message-ID: <9b1101e4-8e3f-eefc-045f-59b1f454a6db@gmail.com> On 06/18/2018 06:26 AM, David Fernandes wrote: > Hi guys, > > I have just 1 question. Is it possible to use OVS inside an Openstack VM > ? Let me explain my issue. > > I have created 2 Ubuntu 16.04 VMs and installed last version of OVS in > both. Both VMs are connected to the same network and they can ping each > other. > Then, I have created an OVS bridge (namely "br-test") in the first VM > and I have added the port of the VM (ens1) to the ovs bridge as usual. > At this point I cant't ping from one VM to the other. > If I perform tcpdump on the bridge (tcpdump br-test), I see that ARP > requests are sent but they are not sent by the interface of the VM (ens1). > I tried to add the MAC addreses manually to the ARP table of each VM. > When I ping, I see the same case :  icmp packets outgoing the bridge > br-test but never sent by the interface ens1 of the VM. I can only guess things are being blocked by the MAC anti-spoofing rules neutron adds - perhaps the source MAC of the bridge is being used which is different from the NIC? -Brian > I have tried the same scenario using a linux bridge instead of OVS > swithch and it works. > > Do you have any idea of why there are issues binding VM interface to OVS > bridges ? Any information will be really apreciated !! Thanks in advance > !!! > > David > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > From torin.woltjer at granddial.com Mon Jun 18 19:01:29 2018 From: torin.woltjer at granddial.com (Torin Woltjer) Date: Mon, 18 Jun 2018 19:01:29 GMT Subject: [Openstack] Masakari on queens Message-ID: <3a1185a9af7b4be2a045566c73e298ca@granddial.com> Hello Tushar Patil, I have upgraded to Openstack Queens and am trying to run Masakari version 4.0.0 . I'm curious what additional configuration is required to get this set up correctly. /etc/masakarimonitors/masakarimonitors.conf http://paste.openstack.org/show/723726/ masakari-hostmonitor is giving me errors like: 2018-06-18 12:44:44.812 18236 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed.: ProcessExecutionError: Unexpected error while running command. 2018-06-18 12:45:14.895 18236 INFO masakarimonitors.hostmonitor.host_handler.handle_host [-] 'UBNTU-OSTACK-COMPUTE2' is 'online'. 2018-06-18 12:46:20.047 18236 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'vlan60' is failed.: ProcessExecutionError: Unexpected error while running command. Do you have any knowledge on this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tushar.Patil at nttdata.com Tue Jun 19 01:09:59 2018 From: Tushar.Patil at nttdata.com (Patil, Tushar) Date: Tue, 19 Jun 2018 01:09:59 +0000 Subject: [Openstack] Masakari on queens In-Reply-To: <3a1185a9af7b4be2a045566c73e298ca@granddial.com> References: <3a1185a9af7b4be2a045566c73e298ca@granddial.com> Message-ID: Hi Torin, Looking at the code, it seems it is trying to run below command as root user. timeout tcpdump -n -c 1 -p -I port where, tcpdump_timeout -> CONF.host.tcpdump_timeout -> default value is 5 seconds multicast_interface -> corosync_multicast_interface -> vlan60 multicast_ports-> corosync_multicast_ports -> 5405 Unfortunately, the error message is suppressed [1] hence it's difficult to know the exact reason. Can you please run below command on the host where you are running masakari-hostmonitor service? The error you would get after running this command would give you some hint to troubleshoot this issue further. $timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405 [1] : https://github.com/openstack/masakari-monitors/blob/cde057bc685b7bbc35f5c425f9690b01766654b2/masakarimonitors/hostmonitor/host_handler/handle_host.py#L121 Regards, Tushar Patil ________________________________________ From: Torin Woltjer Sent: Tuesday, June 19, 2018 4:01:29 AM To: Patil, Tushar; openstack at lists.openstack.org Subject: Masakari on queens Hello Tushar Patil, I have upgraded to Openstack Queens and am trying to run Masakari version 4.0.0 . I'm curious what additional configuration is required to get this set up correctly. /etc/masakarimonitors/masakarimonitors.conf http://paste.openstack.org/show/723726/ masakari-hostmonitor is giving me errors like: 2018-06-18 12:44:44.812 18236 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed.: ProcessExecutionError: Unexpected error while running command. 2018-06-18 12:45:14.895 18236 INFO masakarimonitors.hostmonitor.host_handler.handle_host [-] 'UBNTU-OSTACK-COMPUTE2' is 'online'. 2018-06-18 12:46:20.047 18236 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'vlan60' is failed.: ProcessExecutionError: Unexpected error while running command. Do you have any knowledge on this? Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. From xiaoquqi at gmail.com Tue Jun 19 14:43:55 2018 From: xiaoquqi at gmail.com (Ray Sun) Date: Tue, 19 Jun 2018 22:43:55 +0800 Subject: [Openstack] [OpenStack][Kolla]Choose binary or source In-Reply-To: References: Message-ID: Eric, I discussed upgrade action today with my colleagues, our purpose is a little difference. We want to create an ISO with kolla images and help our customer install OpenStack in an offline way. But for upgrade each time, user's environment always can't access to the internet, and each time I need to copy the docker exported file, it's very large and it seems it's not worth to update one file but copy a 1G file. I am not quite sure there is other way to handle this scenarios. Thanks. Best Regards -- Ray On Mon, Jun 18, 2018 at 12:14 PM Ray Sun wrote: > Ok, thanks for the info. > Best Regards > -- Ray > > > On Mon, Jun 18, 2018 at 11:35 AM Erik McCormick < > emccormick at cirrusseven.com> wrote: > >> >> >> On Sun, Jun 17, 2018, 10:47 PM Ray Sun wrote: >> >>> Eric, >>> Thanks for your reply. >>> >>> I just consider one senario: if I deployed use source, if source is >>> updated, do I need to rebuild the docker image and do an update? Or is >>> there any better way? >>> >>> Best Regards >>> -- Ray >>> >> >> If you want the updates, then build new containers with new tags and run >> the upgrade playbook. You can do this even just for one project. >> >> The process is the same for binary or source. If you want updates, build >> new containers with newer tags. You don't upgrade the already-running >> containers in place. >> >> -Erik >> >> >>> >>> On Mon, Jun 18, 2018 at 10:22 AM Erik McCormick < >>> emccormick at cirrusseven.com> wrote: >>> >>>> >>>> >>>> On Sun, Jun 17, 2018, 8:46 PM Ray Sun wrote: >>>> >>>>> OpenStackers, >>>>> I have several questions for using kolla deployment in production: >>>>> >>>> 1. Binary or source? Which one is mostly used in production >>>>> >>>> >>>> I've heard a lot more reports from people running source, but this is >>>> anecdotal >>>> >>>> 2. Which one is easy to operation, like updating.. >>>>> >>>> >>>> IMHO source is better for updates. With binary you sit around waiting >>>> for packages to decide a patch or stable milestone is worthy of dropping >>>> new packages. With source you can get things when they hit stable branches >>>> upstream. I did exactly one binary deployment, waited forever for a patch I >>>> needed, and swore off doing it that way forever more. >>>> >>>> Operations are the same either way really. >>>> >>>> ... >>>>> 3. Is there any document to describe how to operation kolla deployment >>>>> OpenStack, seems it's not the quite same with the bare metal deployment. >>>>> >>>> >>>> The deployment docs are quite good. There isn't really a good ops guide >>>> though. This is true of bare metal as well though ( in process of being >>>> addressed presently). The IRC channel is terrific though, so if you hit a >>>> wall, pop on there and ask for help or email this list with a tag like you >>>> did here. >>>> >>>>> >>>>> Thanks. >>>>> >>>>> Best Regards >>>>> -- Ray >>>>> >>>> >>>> Cherrs, >>>> Erik >>>> >>>> _______________________________________________ >>>>> Mailing list: >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>>>> Post to : openstack at lists.openstack.org >>>>> Unsubscribe : >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>>>> >>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From torin.woltjer at granddial.com Tue Jun 19 19:04:32 2018 From: torin.woltjer at granddial.com (Torin Woltjer) Date: Tue, 19 Jun 2018 19:04:32 GMT Subject: [Openstack] Masakari on queens Message-ID: Thank for the reply. Tushar Patil. The command: $timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405 returns: "tcpdump: enp2s0f0: That device doesn't support monitor mode" The command: (lowercase i) $timeout 5 tcpdump -n -c 1 -p -i vlan60 port 5405 Runs fine with no errors: "tcpdump: listening on vlan60, link-type EN10MB (Ethernet), capture size 262144 bytes" The in use interfaces on all of my nodes are as follows: enp2s0f0=192.168.114.x enp3s0f0=bond0=vlan60,vlan101 enp3s0f1=bond0=vlan60,vlan101 vlan60=management vlan101=provider >From this part of handle_host.py I can't tell what is causing the command to raise exception. ---------------------------------------- From: "Patil, Tushar" Sent: 6/18/18 9:10 PM To: "openstack at lists.openstack.org" , "torin.woltjer at granddial.com" Subject: Re: Masakari on queens Hi Torin, Looking at the code, it seems it is trying to run below command as root user. timeout tcpdump -n -c 1 -p -I port where, tcpdump_timeout -> CONF.host.tcpdump_timeout -> default value is 5 seconds multicast_interface -> corosync_multicast_interface -> vlan60 multicast_ports-> corosync_multicast_ports -> 5405 Unfortunately, the error message is suppressed [1] hence it's difficult to know the exact reason. Can you please run below command on the host where you are running masakari-hostmonitor service? The error you would get after running this command would give you some hint to troubleshoot this issue further. $timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405 [1] : https://github.com/openstack/masakari-monitors/blob/cde057bc685b7bbc35f5c425f9690b01766654b2/masakarimonitors/hostmonitor/host_handler/handle_host.py#L121 Regards, Tushar Patil ________________________________________ From: Torin Woltjer Sent: Tuesday, June 19, 2018 4:01:29 AM To: Patil, Tushar; openstack at lists.openstack.org Subject: Masakari on queens Hello Tushar Patil, I have upgraded to Openstack Queens and am trying to run Masakari version 4.0.0 . I'm curious what additional configuration is required to get this set up correctly. /etc/masakarimonitors/masakarimonitors.conf http://paste.openstack.org/show/723726/ masakari-hostmonitor is giving me errors like: 2018-06-18 12:44:44.812 18236 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed.: ProcessExecutionError: Unexpected error while running command. 2018-06-18 12:45:14.895 18236 INFO masakarimonitors.hostmonitor.host_handler.handle_host [-] 'UBNTU-OSTACK-COMPUTE2' is 'online'. 2018-06-18 12:46:20.047 18236 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'vlan60' is failed.: ProcessExecutionError: Unexpected error while running command. Do you have any knowledge on this? Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfernandes at toulouse.viveris.com Wed Jun 20 08:15:03 2018 From: dfernandes at toulouse.viveris.com (David Fernandes) Date: Wed, 20 Jun 2018 10:15:03 +0200 Subject: [Openstack] Is it possible to use OVS inside an Openstack VM ? In-Reply-To: <9b1101e4-8e3f-eefc-045f-59b1f454a6db@gmail.com> References: <9b1101e4-8e3f-eefc-045f-59b1f454a6db@gmail.com> Message-ID: <77bb736a-8e85-ee98-ccab-cd1c42833564@toulouse.viveris.com> Yo are totally Right Brian ! I tried to allow the bridge address pair to the VM port using the following command and it works !!! neutron port-update --allowed-address-pairs type=dict list=true mac_address=,ip_address= Thank you so much !! David Le 18/06/2018 à 20:21, Brian Haley a écrit : > On 06/18/2018 06:26 AM, David Fernandes wrote: >> Hi guys, >> >> I have just 1 question. Is it possible to use OVS inside an Openstack >> VM ? Let me explain my issue. >> >> I have created 2 Ubuntu 16.04 VMs and installed last version of OVS >> in both. Both VMs are connected to the same network and they can ping >> each other. >> Then, I have created an OVS bridge (namely "br-test") in the first VM >> and I have added the port of the VM (ens1) to the ovs bridge as >> usual. At this point I cant't ping from one VM to the other. >> If I perform tcpdump on the bridge (tcpdump br-test), I see that ARP >> requests are sent but they are not sent by the interface of the VM >> (ens1). >> I tried to add the MAC addreses manually to the ARP table of each VM. >> When I ping, I see the same case :  icmp packets outgoing the bridge >> br-test but never sent by the interface ens1 of the VM. > > I can only guess things are being blocked by the MAC anti-spoofing > rules neutron adds - perhaps the source MAC of the bridge is being > used which is different from the NIC? > > -Brian > > >> I have tried the same scenario using a linux bridge instead of OVS >> swithch and it works. >> >> Do you have any idea of why there are issues binding VM interface to >> OVS bridges ? Any information will be really apreciated !! Thanks in >> advance !!! >> >> David >> >> >> >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to     : openstack at lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> From torin.woltjer at granddial.com Wed Jun 20 14:23:34 2018 From: torin.woltjer at granddial.com (Torin Woltjer) Date: Wed, 20 Jun 2018 14:23:34 GMT Subject: [Openstack] Masakari on queens Message-ID: Oddly enough, I never made changes to the original code to get that output. It is just masakari-monitor 4.0.0 as installed by pip. Here are the changes and output to that code snippit you sent: http://paste.openstack.org/show/723924/ I'd like to increase the logging, but I'm not familiar with the codebase and lack more than a rudimentary knowledge of python. I've found where it seems pip installed the files for masakari-hostmonitor, but I don't know which one contains the corosync bit. ---------------------------------------- From: "Patil, Tushar" Sent: 6/20/18 12:51 AM To: "torin.woltjer at granddial.com" Subject: Re: Masakari on queens Hi Torin, Option -i is correct. It seems that you have modified code to log error message: "ProcessExecutionError: Unexpected error while running command." Could you please log 'stderr' and 'exit_code' as well in order to know the exact error you are getting? I suspect you must be getting 124 exit code. This is a small program which I have created to simulate the error you are getting. http://paste.openstack.org/show/723882/ Please specify interface and port as per your configuration and run the program. Regards, Tushar Patil ________________________________________ From: Torin Woltjer Sent: Tuesday, June 19, 2018 9:58:32 PM To: Patil, Tushar Subject: Re: Masakari on queens Thank for the reply. Tushar Patil. The command: $timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405 returns: "tcpdump: enp2s0f0: That device doesn't support monitor mode" The command: (lowercase i) $timeout 5 tcpdump -n -c 1 -p -i vlan60 port 5405 Runs fine with no errors: "tcpdump: listening on vlan60, link-type EN10MB (Ethernet), capture size 262144 bytes" The in use interfaces on all of my nodes are as follows: enp2s0f0=192.168.114.x enp3s0f0=bond0=vlan60,vlan101 enp3s0f1=bond0=vlan60,vlan101 vlan60=management vlan101=provider >From this part of handle_host.py I can't tell what is causing the command to raise exception. ________________________________ From: "Patil, Tushar" Sent: 6/18/18 9:10 PM To: "openstack at lists.openstack.org" , "torin.woltjer at granddial.com" Subject: Re: Masakari on queens Hi Torin, Looking at the code, it seems it is trying to run below command as root user. timeout tcpdump -n -c 1 -p -I port where, tcpdump_timeout -> CONF.host.tcpdump_timeout -> default value is 5 seconds multicast_interface -> corosync_multicast_interface -> vlan60 multicast_ports-> corosync_multicast_ports -> 5405 Unfortunately, the error message is suppressed [1] hence it's difficult to know the exact reason. Can you please run below command on the host where you are running masakari-hostmonitor service? The error you would get after running this command would give you some hint to troubleshoot this issue further. $timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405 [1] : https://github.com/openstack/masakari-monitors/blob/cde057bc685b7bbc35f5c425f9690b01766654b2/masakarimonitors/hostmonitor/host_handler/handle_host.py#L121 Regards, Tushar Patil ________________________________________ From: Torin Woltjer Sent: Tuesday, June 19, 2018 4:01:29 AM To: Patil, Tushar; openstack at lists.openstack.org Subject: Masakari on queens Hello Tushar Patil, I have upgraded to Openstack Queens and am trying to run Masakari version 4.0.0 . I'm curious what additional configuration is required to get this set up correctly. /etc/masakarimonitors/masakarimonitors.conf http://paste.openstack.org/show/723726/ masakari-hostmonitor is giving me errors like: 2018-06-18 12:44:44.812 18236 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed.: ProcessExecutionError: Unexpected error while running command. 2018-06-18 12:45:14.895 18236 INFO masakarimonitors.hostmonitor.host_handler.handle_host [-] 'UBNTU-OSTACK-COMPUTE2' is 'online'. 2018-06-18 12:46:20.047 18236 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'vlan60' is failed.: ProcessExecutionError: Unexpected error while running command. Do you have any knowledge on this? Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel at jtcressy.net Wed Jun 20 20:33:34 2018 From: joel at jtcressy.net (Joel Cressy) Date: Wed, 20 Jun 2018 14:33:34 -0600 Subject: [Openstack] [TripleO] Containerized Undercloud Install Fails On Queens Release Message-ID: Hi All, I’m following the instructions at https://docs.openstack.org/tripleo-docs/latest/install/installation/installation.html and at the step to deploy a containerized undercloud, it fails immediately. The command I ran was “openstack undercloud install --use-heat” It fails with this traceback: ``` [stack at undercloud1 ~]$ openstack undercloud install --use-heat Running: sudo openstack undercloud deploy --local-ip=192.168.24.1 --templates=/usr/share/openstack-tripleo-heat-templates/ --heat-native -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/ironic.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/ironic-inspector.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/mistral.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/zaqar.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/docker.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/config-download-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/undercloud.yaml -e /tmp/undercloud_parameters.yaml --output-dir=/home/stack Undercloud deploy is an experimental developer focused feature that does not yet replace 'openstack undercloud install'. Configuring puppet modules symlinks ... Exception: list index out of range ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.7/site-packages/tripleoclient/v1/undercloud_deploy.py", line 502, in take_action\n orchestration_client = self._launch_heat(parsed_args)\n', ' File "/usr/lib/python2.7/site-packages/tripleoclient/v1/undercloud_deploy.py", line 187, in _launch_heat\n parsed_args.heat_user)\n', ' File "/usr/lib/python2.7/site-packages/tripleoclient/heat_launcher.py", line 306, in __init__\n user)\n', ' File "/usr/lib/python2.7/site-packages/tripleoclient/heat_launcher.py", line 170, in __init__\n uid = int(self.get_heat_uid())\n', ' File "/usr/lib/python2.7/site-packages/tripleoclient/heat_launcher.py", line 318, in get_heat_uid\n return p.communicate()[0].rstrip().split(\':\')[2]\n', 'IndexError: list index out of range\n'] 'DeployUndercloud' object has no attribute 'heat_launch' Command '['sudo', 'openstack', 'undercloud', 'deploy', '--local-ip=192.168.24.1', '--templates=/usr/share/openstack-tripleo-heat-templates/', '--heat-native', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services-docker/ironic.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services-docker/ironic-inspector.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services-docker/mistral.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services-docker/zaqar.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/docker.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/config-download-environment.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/undercloud.yaml', '-e', '/tmp/undercloud_parameters.yaml', '--output-dir=/home/stack']' returned non-zero exit status 1 [stack at undercloud1 ~]$ ``` This is a fresh install of CentOS 7. Prior commands ran were “sudo -E tripleo-repos -b queens current ceph” and “sudo yum install python-tripleorepos”. Is a containerized install recommended as the documentation claims? Why does the command line say "Undercloud deploy is an experimental developer focused feature that does not yet replace 'openstack undercloud install’.”? This makes me think that the command line tool is not on par with the documentation. What can I do to fix this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Thu Jun 21 00:32:34 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Thu, 21 Jun 2018 09:32:34 +0900 Subject: [Openstack] [tripleo] [tripleo-quickstart] quickstart.sh failing Message-ID: <72d3fd45-d6a3-e16f-a447-863884422d5a@gmail.com> I hoped that I could use quickstart.sh to set up Tripleo without much thinking. The Ansible playbook generates undercloud, compute and control images and much more on the VIRTHOST but ultimately fails with: TASK [undercloud-deploy : Write containers-prepare-parameter.yaml] ************************************************************************** task path: /home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96 Wednesday 20 June 2018  18:31:07 +0900 (0:00:07.221)       1:14:05.859 ******** fatal: [undercloud]: FAILED! => {"changed": false, "failed": true, "msg": "AnsibleUndefinedVariable: 'container_build_id' is undefined"} What puzzles me (I am far from being an Ansible expert): If I interpret /_quickstart.log/ correctly, this variable is set about half-way through the process: TASK [extras-common : set container_build_id from docker_image_tag] ************************************************************************* task path: /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 Wednesday 20 June 2018  17:23:13 +0900 (0:00:00.212)       0:06:12.229 ******** ok: [jupiter] => {*"ansible_facts": {"container_build_id": "current-tripleo-rdo"},* "changed": false, "failed": false} Later plays also set it conditionally, but the conditions are never met. Some derive it from a variable named /get_build_command/, which I can't find anywhere (I did do a http://codesearch.openstack.org): TASK [extras-common : set container_build_id from get_build_command] ************************************************************************ task path: /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6 Wednesday 20 June 2018  18:16:45 +0900 (0:00:00.323)       0:59:44.741 ******** skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true} others base it on a Docker container tag: TASK [extras-common : set container_build_id from docker_image_tag] ************************************************************************* task path: /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 Wednesday 20 June 2018  18:16:46 +0900 (0:00:00.128)       0:59:44.996 ******** skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true} Any pointers how to fix this? My VIRTHOST is a HP Z420 workstation named /jupiter/, 4 core Xeon, 32G memory, 150G disk space running freshly installed Centos 7.5. I run the quickstart script on a VM, equally with Centos 7.5. I followed the instructions at https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart: $ ssh-keygen; ssh-copy-id root at jupiter; ssh-copy-id stack at jupiter $ curl-Ohttps://raw.githubusercontent.com/openstack/tripleo-quickstart/master/quickstart.sh $ bashquickstart.sh--install-deps $ bash quickstart.sh jupiter Bernd Bausch -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From majopela at redhat.com Thu Jun 21 07:43:33 2018 From: majopela at redhat.com (Miguel Angel Ajo Pelayo) Date: Thu, 21 Jun 2018 09:43:33 +0200 Subject: [Openstack] [tripleo] [tripleo-quickstart] quickstart.sh failing In-Reply-To: <72d3fd45-d6a3-e16f-a447-863884422d5a@gmail.com> References: <72d3fd45-d6a3-e16f-a447-863884422d5a@gmail.com> Message-ID: I'm also hitting that issue currently too you can workaround with -e docker_registry_namespace_used=tripleomaster -e container_build_id=current-tripleo on the quickstart command line while this is fixed (please note that's only for tripleo master). I see in the quickstart logs that those variables are detected as facts, but then ansible does not find them on those tasks. Note: I'm just providing a workaround that I used to keep moving, but I'm not actively working on fixing the quickstart issue because I don't know how to fix it at this moment. On Thu, Jun 21, 2018 at 2:44 AM Bernd Bausch wrote: > I hoped that I could use quickstart.sh to set up Tripleo without much > thinking. The Ansible playbook generates undercloud, compute and control > images and much more on the VIRTHOST but ultimately fails with: > > TASK [undercloud-deploy : Write containers-prepare-parameter.yaml] > ************************************************************************** > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96 > Wednesday 20 June 2018 18:31:07 +0900 (0:00:07.221) 1:14:05.859 > ******** > fatal: [undercloud]: FAILED! => {"changed": false, "failed": true, "msg": > "AnsibleUndefinedVariable: 'container_build_id' is undefined"} > What puzzles me (I am far from being an Ansible expert): If I interpret > *_quickstart.log* correctly, this variable is set about half-way through > the process: > > TASK [extras-common : set container_build_id from docker_image_tag] > ************************************************************************* > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 > Wednesday 20 June 2018 17:23:13 +0900 (0:00:00.212) 0:06:12.229 > ******** > ok: [jupiter] => {*"ansible_facts": {"container_build_id": > "current-tripleo-rdo"},* "changed": false, "failed": false} > > Later plays also set it conditionally, but the conditions are never met. > Some derive it from a variable named *get_build_command*, which I can't > find anywhere (I did do a http://codesearch.openstack.org): > > TASK [extras-common : set container_build_id from get_build_command] > ************************************************************************ > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6 > Wednesday 20 June 2018 18:16:45 +0900 (0:00:00.323) 0:59:44.741 > ******** > skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional > result was False", "skipped": true} > > others base it on a Docker container tag: > > TASK [extras-common : set container_build_id from docker_image_tag] > ************************************************************************* > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 > Wednesday 20 June 2018 18:16:46 +0900 (0:00:00.128) 0:59:44.996 > ******** > skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional > result was False", "skipped": true} > > Any pointers how to fix this? > > My VIRTHOST is a HP Z420 workstation named *jupiter*, 4 core Xeon, 32G > memory, 150G disk space running freshly installed Centos 7.5. I run the > quickstart script on a VM, equally with Centos 7.5. I followed the > instructions at > https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart > : > > $ ssh-keygen; ssh-copy-id root at jupiter; ssh-copy-id stack at jupiter > $ curl -O https://raw.githubusercontent.com/openstack/tripleo-quickstart/ > master/quickstart.sh > $ bash quickstart.sh --install-deps > $ bash quickstart.sh jupiter > > Bernd Bausch > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nspmangalore at gmail.com Thu Jun 21 10:24:44 2018 From: nspmangalore at gmail.com (Shyam Prasad N) Date: Thu, 21 Jun 2018 15:54:44 +0530 Subject: [Openstack] Struggling to get the s3 api interface to work with swift. In-Reply-To: References: <2925BD08-5166-4FCB-97D0-84FBA872FFC4@ostorage.com.cn> <5B5E845C-A3D1-436E-BDC9-846257587357@ostorage.com.cn> <5F134369-41C0-4AAA-8E49-8D921AF524FA@ostorage.com.cn> <5B10DA62.9010106@lab.ntt.co.jp> <5B10FD3C.7080508@lab.ntt.co.jp> Message-ID: I forgot to close loop on this. I managed to solve this problem with a config change in /etc/swift/proxy-server.conf: I needed to include the line: auth_version = 3 under [filter:s3token] On Fri, Jun 1, 2018 at 5:02 PM, Shyam Prasad N wrote: > Hi Kota, > > I tried with the changes you suggested. It gives me the old error again... > eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks -- > http://s3server:8080 > s3curl: Found the url: host=s3server; port=8080; uri=; query=; > s3curl: s3server > s3curl: s3server > s3curl: ordinary endpoint signing case > s3curl: StringToSign='GET\n\n\nFri, 01 Jun 2018 11:31:50 +0000\n/' > s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 11:31:50 +0000' -H > 'Authorization: AWS 76498e1413284b9d961d452db608dff4:X1vdAhaZ4KyuM5LpMVc21ZQaGuA=' > -L -H 'content-type: ' http://s3server:8080 > * Rebuilt URL to: http://s3server:8080/ > * Trying 20.20.20.229... > * TCP_NODELAY set > * Connected to s3server (20.20.20.229) port 8080 (#0) > > GET / HTTP/1.1 > > Host: s3server:8080 > > User-Agent: curl/7.58.0 > > Accept: */* > > Date: Fri, 01 Jun 2018 11:31:50 +0000 > > Authorization: AWS 76498e1413284b9d961d452db608dff4: > X1vdAhaZ4KyuM5LpMVc21ZQaGuA= > > > < HTTP/1.1 403 Forbidden > < x-amz-id-2: txbdd2940942ce49509226d-005b112ea6 > < x-amz-request-id: txbdd2940942ce49509226d-005b112ea6 > < Content-Type: application/xml > < X-Trans-Id: txbdd2940942ce49509226d-005b112ea6 > < X-Openstack-Request-Id: txbdd2940942ce49509226d-005b112ea6 > < Date: Fri, 01 Jun 2018 11:31:50 GMT > < Transfer-Encoding: chunked > < > > * Connection #0 to host s3server left intact > SignatureDoesNotMatchThe request signature > we calculated does not match the signature you provided. Check your key and > signing method.txbdd2940942ce49509226d- > 005b112ea6 > > On Fri, Jun 1, 2018 at 1:31 PM, Kota TSUYUZAKI < > tsuyuzaki.kota at lab.ntt.co.jp> wrote: > >> Hi Shyam, >> >> >> > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 >> > +0000\n/s3server/testbucket' >> >> It looks like your StringToSign doesn't include correct info for your >> request.(e.g. resource should be only "/testbucket") >> See https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-heade >> r-based-auth.html for more info. >> >> Your request should be: >> >> > * Connected to s3server (20.20.20.229) port 8080 (#0) >> >> PUT /testbucket HTTP/1.1 >> >> Host: s3server:8080 >> >> User-Agent: curl/7.58.0 >> >> Accept: */* >> >> Date: Fri, 01 Jun 2018 05:47:53 +0000 >> >> Authorization: AWS >> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA= >> >> Content-Length: 0 >> >> then, the string to sign should include the info corretly. >> >> Looking at s3curl code, it looks to fall into cname case? >> >> https://github.com/scality/S3/blob/master/tests/functional/s >> 3curl/s3curl.pl#L311-L328 >> >> Once I played with s3curl the request with ordinary endpoint signing case >> worked correctly. >> Again, I'm not an expert of s3curl so no idea why your setting went to >> the cname case tho. >> >> Best, >> Kota >> >> (2018/06/01 14:49), Shyam Prasad N wrote: >> > Hi Kota, >> > >> > Thanks for the response. >> > When I specify the URL as http://s3server:8080/testbucket, it throws >> back a >> > SignatureDoesNotMatch error. >> > >> > eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks >> > --createBucket -- http://s3server:8080/testbucket >> > s3curl: Found the url: host=s3server; port=8080; uri=/testbucket; >> query=; >> > s3curl: cname endpoint signing case >> > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 >> > +0000\n/s3server/testbucket' >> > s3curl: exec curl -v -H 'Date: Fri, 01 Jun 2018 05:47:53 +0000' -H >> > 'Authorization: AWS >> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA=' -L -H >> > 'content-type: ' --data-binary -X PUT http://s3server:8080/testbucket >> > * Trying 20.20.20.229... >> > * TCP_NODELAY set >> > * Connected to s3server (20.20.20.229) port 8080 (#0) >> >> PUT /testbucket HTTP/1.1 >> >> Host: s3server:8080 >> >> User-Agent: curl/7.58.0 >> >> Accept: */* >> >> Date: Fri, 01 Jun 2018 05:47:53 +0000 >> >> Authorization: AWS >> > 76498e1413284b9d961d452db608dff4:uzQs5hJOnwY4dyFk0PIxHHwmVcA= >> >> Content-Length: 0 >> >> >> > < HTTP/1.1 403 Forbidden >> > < x-amz-id-2: tx5c2ac9ea26a046ac96e4d-005b10de09 >> > < x-amz-request-id: tx5c2ac9ea26a046ac96e4d-005b10de09 >> > < Content-Type: application/xml >> > < X-Trans-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 >> > < X-Openstack-Request-Id: tx5c2ac9ea26a046ac96e4d-005b10de09 >> > < Date: Fri, 01 Jun 2018 05:47:53 GMT >> > < Transfer-Encoding: chunked >> > * HTTP error before end of send, stop sending >> > < >> > >> > * Closing connection 0 >> > SignatureDoesNotMatchThe request >> signature we >> > calculated does not match the signature you provided. Check your key and >> > signing >> > method.tx5c2ac9ea26a046ac96e4d-005b10de >> 09 >> > >> > Regards, >> > Shyam >> > >> > On Fri, Jun 1, 2018 at 11:02 AM, Kota TSUYUZAKI < >> > tsuyuzaki.kota at lab.ntt.co.jp> wrote: >> > >> >> Hi Shyam, >> >> >> >> You should specify the path starts from bucket. It will be like >> >> >> >> http://20.20.20.229:8080/testBucket >> >> >> >> assuming you didn't configure virtual-hosted style. >> >> Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_ >> >> dc86f7d8787b46158268bd77098b6578, >> >> swift3 doesn't require the account in the path so far as well as actual >> >> amazon s3. >> >> >> >> Best, >> >> Kota >> >> >> >> (2018/05/31 21:33), Shyam Prasad N wrote: >> >>> Hi Yuxin, >> >>> >> >>> Thank you for sharing your configs. >> >>> So I've managed to get past the Signature not matching error. >> >>> >> >>> Now the error is different. InvalidbucketName: >> >>> >> >>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks >> >>> --createBucket -- >> >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 >> >> 78/testBucket >> >>> s3curl: Found the url: host=20.20.20.229; port=8080; >> >>> uri=/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket; query=; >> >>> s3curl: cname endpoint signing case >> >>> s3curl: StringToSign='PUT\n\n\nThu, 31 May 2018 12:02:57 +0000\n/ >> >>> 20.20.20.229/v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket' >> >>> s3curl: exec curl -v -H 'Date: Thu, 31 May 2018 12:02:57 +0000' -H >> >>> 'Authorization: AWS >> >>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0=' -L -H >> >>> 'content-type: ' --data-binary -X PUT >> >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b65 >> >> 78/testBucket >> >>> * Trying 20.20.20.229... >> >>> * TCP_NODELAY set >> >>> * Connected to 20.20.20.229 (20.20.20.229) port 8080 (#0) >> >>>> PUT /v1/AUTH_dc86f7d8787b46158268bd77098b6578/testBucket HTTP/1.1 >> >>>> Host: 20.20.20.229:8080 >> >>>> User-Agent: curl/7.58.0 >> >>>> Accept: */* >> >>>> Date: Thu, 31 May 2018 12:02:57 +0000 >> >>>> Authorization: AWS >> >>> 76498e1413284b9d961d452db608dff4:jj/kaAEuX/vK+WUTvZyDQUUEGV0= >> >>>> Content-Length: 0 >> >>>> >> >>> < HTTP/1.1 400 Bad Request >> >>> < x-amz-id-2: tx18266052d5044eb2a3bc7-005b0fe471 >> >>> < x-amz-request-id: tx18266052d5044eb2a3bc7-005b0fe471 >> >>> < Content-Type: application/xml >> >>> < X-Trans-Id: tx18266052d5044eb2a3bc7-005b0fe471 >> >>> < X-Openstack-Request-Id: tx18266052d5044eb2a3bc7-005b0fe471 >> >>> < Date: Thu, 31 May 2018 12:02:57 GMT >> >>> < Transfer-Encoding: chunked >> >>> * HTTP error before end of send, stop sending >> >>> < >> >>> >> >>> * Closing connection 0 >> >>> InvalidBucketNameThe specified bucket is >> >> not >> >>> valid.tx18266052d5044eb2a3bc7- >> >> 005b0fe471v1> >> Error>eightkpc at objectstore1:~/s3curl$ >> >>> >> >>> >> >>> My specified endpoint is >> >>> http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578 >> >>> What am I doing wrong? >> >>> >> >>> Regards, >> >>> Shyam >> >>> >> >>> On Wed, May 30, 2018 at 7:32 PM, Yuxin Wang < >> wang.yuxin at ostorage.com.cn> >> >>> wrote: >> >>> >> >>>> Hi Shyam, >> >>>> >> >>>> No problem. The output of the commands is attached. >> >>>> >> >>>> And my test cluster is on Swift v2.15.1 with Swift3 v1.12 >> >>>> >> >>>> Also, here is the common process when I'm creating an S3 credential >> and >> >>>> using in s3curl. Hope it helps. >> >>>> >> >>>> 1. Create a user and a project, and assign a proper role. >> >>>> >> >>>> openstack project create testproject >> >>>> openstack user create testuser --password 123 >> >>>> openstack role add --project testproject --user testuser _member_ >> >>>> >> >>>> 2. Check accessibility to swift >> >>>> >> >>>> create a test-openrc file with above info >> >>>> source test-openrc >> >>>> swift list >> >>>> >> >>>> 3.Create a credential >> >>>> >> >>>> openstack credential create --type ec2 --project testproject testuser >> >>>> '{"access": "testaccess", "secret": "testsecret"}' >> >>>> >> >>>> 4. Use it in s3curl >> >>>> >> >>>> add the endpoint url to `my @endpoints` in s3curl.pl >> >>>> add the credential to .s3curl config file >> >>>> >> >>>> do `s3curl.pl -i cred_name --debug -- http://endpoint -X GET` >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> 在 2018年5月25日,18:17,Shyam Prasad N 写道: >> >>>> >> >>>> Hi Yuxin, >> >>>> >> >>>> If you don't mind, can you share the output of the following >> commands in >> >>>> your running swift3 setup? >> >>>> >> >>>> openstack credential list >> >>>> openstack ec2 credentials list >> >>>> cat /etc/swift/proxy-server.conf >> >>>> >> >>>> Also, what are the access keys and secret keys that you use? >> >>>> I want to make sure that I'm not missing anything in configuration. >> >>>> >> >>>> Regards, >> >>>> Shyam >> >>>> >> >>>> On Fri, May 25, 2018 at 3:05 PM, Shyam Prasad N < >> nspmangalore at gmail.com >> >>> >> >>>> wrote: >> >>>> >> >>>>> Tried that. Unfortunately same error. >> >>>>> Is there anything I can do to troubleshoot this? >> >>>>> >> >>>>> On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang < >> >> wang.yuxin at ostorage.com.cn> >> >>>>> wrote: >> >>>>> >> >>>>>> They can be any strings. >> >>>>>> >> >>>>>> Replace them with whatever you want. >> >>>>>> >> >>>>>> - Yuxin >> >>>>>> >> >>>>>> 在 2018年5月25日,14:57,Shyam Prasad N 写道: >> >>>>>> >> >>>>>> Thanks. I'll try this. >> >>>>>> But what values do I use in place of ak and sk? I want to use some >> >>>>>> command to get those values, right? >> >>>>>> >> >>>>>> On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang < >> >> wang.yuxin at ostorage.com.cn> >> >>>>>> wrote: >> >>>>>> >> >>>>>>> I created ec2 credentials using command `openstack credential >> >> create`. >> >>>>>>> >> >>>>>>> i.e. >> >>>>>>> >> >>>>>>> openstack credential create --type ec2 --project proj user >> >> '{"access": >> >>>>>>> "ak", "secret": "sk”}' >> >>>>>>> >> >>>>>>> >> >>>>>>> It seems the two credentials are not the same thing. >> >>>>>>> >> >>>>>>> Ref: >> >>>>>>> >> >>>>>>> https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/ >> >>>>>>> com.ibm.spectrum.scale.v4r11.adv.doc/bl1adv_ConfigureOpensta >> >>>>>>> ckEC2credentials.htm >> >>>>>>> > >> https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter% >> >> 2Fen%2FSTXKQY_4.1.1%2Fcom.ibm.spectrum.scale.v4r11.adv.doc%2Fbl1adv_ >> >> ConfigureOpenstackEC2credentials.htm&data=02%7C01%7C% >> >> 7Cc6d4af73a0fd4208f9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >> >> aaaa%7C1%7C0%7C636628292198191185&sdata=cBwi02p2zc3db3%2Bp8PDvrgAZ2% >> >> 2FkqjB6wnuW%2FEt0zWPA%3D&reserved=0> >> >>>>>>> >> >>>>>>> 在 2018年5月25日,10:32,Shyam Prasad N 写道: >> >>>>>>> >> >>>>>>> Yes, I did. >> >>>>>>> I don't think this is s3curl related issue, because I tried with >> >> python >> >>>>>>> AWS SDK, and got the same error. >> >>>>>>> >> >>>>>>> On Fri, May 25, 2018, 07:42 Yuxin Wang < >> wang.yuxin at ostorage.com.cn> >> >>>>>>> wrote: >> >>>>>>> >> >>>>>>>> Did you add 127.0.0.1 to the endpoint list in s3curl.pl >> >>>>>>>> > >> http%3A%2F%2Fs3curl.pl%2F&data=02%7C01%7C%7Cc6d4af73a0fd4208 >> f9ac08d5c20f >> >> 0a30%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0% >> >> 7C636628292198191185&sdata=nr9HL8HskZJ8OwCfpuU2pKg7% >> >> 2FPnzWhTD1b4wEi02o5A%3D&reserved=0> >> >>>>>>>> ? >> >>>>>>>> >> >>>>>>>> i.e. >> >>>>>>>> >> >>>>>>>> my @endpoints = (‘127.0.0.1’); >> >>>>>>>> >> >>>>>>>> 在 2018年5月24日,19:48,Shyam Prasad N 写道: >> >>>>>>>> >> >>>>>>>> Hi, >> >>>>>>>> >> >>>>>>>> I've been trying to get swift3 to work for several days now. But >> I >> >>>>>>>> haven't managed to get it running. >> >>>>>>>> Both with tempauth and keystoneauth, I'm getting the same error: >> >>>>>>>> >> >>>>>>>> eightkpc at objectstore1:~/s3curl$ ./s3curl.pl >> >>>>>>>> > >> http%3A%2F%2Fs3curl.pl&data=02%7C01%7C%7C39742b8c6bf847ee381 >> 508d5c16d1b21% >> >> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636627596701206160&sdata= >> >> lZmKF41unLVD9J1ALYUv8Vkab448NOeGmcWcR56Rgxs%3D&reserved=0> >> >>>>>>>> --id=testerks -- http://127.0.0.1:8080/ >> >>>>>>>> > >> http%3A%2F%2F127.0.0.1%3A8080%2F&data=02%7C01%7C% >> >> 7C39742b8c6bf847ee381508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >> >> aaaa%7C1%7C0%7C636627596701206160&sdata=CEHEVR1HSpK0ehQ8mmOBA7fmjQsu7v >> >> jqKZda3NYVDWQ%3D&reserved=0> >> >>>>>>>> >> >>>>>>>> SignatureDoesNotMatchThe request >> >>>>>>>> signature we calculated does not match the signature you >> provided. >> >> Check >> >>>>>>>> your key and signing method.tx >> >>>>>>>> a691e7ca97a44d56bc4c2-005b06a292 >> >>>>>>>> >> >>>>>>>> May 24 11:31:30 localhost proxy-server: 127.0.0.1 127.0.0.1 >> >>>>>>>> 24/May/2018/11/31/30 GET / HTTP/1.0 403 - curl/7.58.0 - - 277 - >> >>>>>>>> txa691e7ca97a44d56bc4c2-005b06a292 - 0.0200 - - >> >> 1527161490.543112040 >> >>>>>>>> 1527161490.563107014 - >> >>>>>>>> May 24 11:31:30 localhost proxy-server: STDERR: 127.0.0.1 - - >> >>>>>>>> [24/May/2018 11:31:30] "GET / HTTP/1.1" 403 621 0.021979 (txn: >> >>>>>>>> txa691e7ca97a44d56bc4c2-005b06a292) >> >>>>>>>> >> >>>>>>>> eightkpc at objectstore1:~$ cat .s3curl >> >>>>>>>> %awsSecretAccessKeys = ( >> >>>>>>>> tester => { >> >>>>>>>> id => 'test:tester', >> >>>>>>>> key => 'testing', >> >>>>>>>> }, >> >>>>>>>> testerks => { >> >>>>>>>> id => 'e6289a1b5692461388d0597a4873d054', >> >>>>>>>> key => '88bb706887094696b082f008ba133ad7', >> >>>>>>>> }, >> >>>>>>>> ); >> >>>>>>>> >> >>>>>>>> eightkpc at objectstore1:~$ openstack ec2 credentials show >> >>>>>>>> e6289a1b5692461388d0597a4873d054 >> >>>>>>>> +------------+---------------------------------------------- >> >>>>>>>> ------------------------------------------------------------ >> >>>>>>>> --------------------------+ >> >>>>>>>> | Field | Value >> >>>>>>>> >> >>>>>>>> | >> >>>>>>>> +------------+---------------------------------------------- >> >>>>>>>> ------------------------------------------------------------ >> >>>>>>>> --------------------------+ >> >>>>>>>> | access | e6289a1b5692461388d0597a4873d0 >> >>>>>>>> 54 >> >>>>>>>> | >> >>>>>>>> | links | {u'self': u'http://controller:5000/v3/us >> >>>>>>>> ers/d7df7b56343b4ea988869fc30efeda09/credentials/OS-EC2/e628 >> >>>>>>>> 9a1b5692461388d0597a4873d054'} | >> >>>>>>>> | project_id | dc86f7d8787b46158268bd77098b65 >> >>>>>>>> 78 >> >>>>>>>> | >> >>>>>>>> | secret | 88bb706887094696b082f008ba133a >> >>>>>>>> d7 >> >>>>>>>> | >> >>>>>>>> | trust_id | None >> >>>>>>>> >> >>>>>>>> | >> >>>>>>>> | user_id | d7df7b56343b4ea988869fc30efeda >> >>>>>>>> 09 >> >>>>>>>> | >> >>>>>>>> +------------+---------------------------------------------- >> >>>>>>>> ------------------------------------------------------------ >> >>>>>>>> --------------------------+ >> >>>>>>>> >> >>>>>>>> Can someone please let me know what is going on? >> >>>>>>>> >> >>>>>>>> Regards, >> >>>>>>>> Shyam >> >>>>>>>> _________________________________________ >> ______ >> >>>>>>>> Mailing list: https://eur03.safelinks.protec >> tion.outlook.com/?url= >> >>>>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> >>>>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 >> >>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >> >>>>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI >> >>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 >> >>>>>>>> Post to : openstack at lists.openstack.org >> >>>>>>>> Unsubscribe : https://eur03.safelinks.protec >> tion.outlook.com/?url= >> >>>>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> >>>>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C39742b8c6bf847ee3 >> >>>>>>>> 81508d5c16d1b21%7C84df9e7fe9f640afb435aaaaaaaa >> >>>>>>>> aaaa%7C1%7C0%7C636627596701206160&sdata=KI%2F2T2FhVQJTeX1KbI >> >>>>>>>> ObDZVDiUA3SbTq6Pplo1bc7ak%3D&reserved=0 >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>> >> >>>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> -Shyam >> >>>>>> _______________________________________________ >> >>>>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= >> >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f >> >>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >> >>>>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% >> >>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 >> >>>>>> Post to : openstack at lists.openstack.org >> >>>>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= >> >>>>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> >>>>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7Cc6d4af73a0fd4208f >> >>>>>> 9ac08d5c20f0a30%7C84df9e7fe9f640afb435aaaaaaaa >> >>>>>> aaaa%7C1%7C0%7C636628292198347486&sdata=tGhHmhX%2By9RVFjl% >> >>>>>> 2B31%2BVgRiN1mD%2Fc%2B7QLiImlGnCv98%3D&reserved=0 >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> -Shyam >> >>>>> >> >>>> >> >>>> >> >>>> >> >>>> -- >> >>>> -Shyam >> >>>> _______________________________________________ >> >>>> Mailing list: https://nam05.safelinks.protection.outlook.com/?url= >> >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3 >> d08d5c22a >> >> 5c90% >> >>>> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910 >> 462&sdata=% >> >>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 >> >>>> Post to : openstack at lists.openstack.org >> >>>> Unsubscribe : https://nam05.safelinks.protection.outlook.com/?url= >> >>>> http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman% >> >>>> 2Flistinfo%2Fopenstack&data=02%7C01%7C%7C7bf3d25a540b4d402d3 >> d08d5c22a >> >> 5c90% >> >>>> 7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636628409546910 >> 462&sdata=% >> >>>> 2FhXb5bRIU0kCZSDj4pJXfEkVYEtBApcA6OjhKHw1fMQ%3D&reserved=0 >> >>>> >> >>>> >> >>>> >> >>>> >> >>> >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ >> >> openstack >> >>> Post to : openstack at lists.openstack.org >> >>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ >> >> openstack >> >>> >> >> >> >> >> >> >> >> >> > >> > >> >> >> > > > -- > -Shyam > -- -Shyam -------------- next part -------------- An HTML attachment was scrubbed... URL: From nspmangalore at gmail.com Thu Jun 21 10:27:32 2018 From: nspmangalore at gmail.com (Shyam Prasad N) Date: Thu, 21 Jun 2018 15:57:32 +0530 Subject: [Openstack] Swift3 bucket naming conventions Message-ID: Hi, On my openstack swift s3 interface, I tried to create bucket names similar to what I have in my AWS S3. But swift3 doesn't seem to allow bucket names containing underscore. Once I remove the underscore and try to create the bucket, it works. Is there a way to overcome this? -- -Shyam -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Fri Jun 22 08:47:53 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Fri, 22 Jun 2018 17:47:53 +0900 Subject: [Openstack] [tripleo] [tripleo-quickstart] quickstart.sh failing In-Reply-To: References: <72d3fd45-d6a3-e16f-a447-863884422d5a@gmail.com> Message-ID: <390737e0-ca67-4deb-4c21-71f57548834e@gmail.com> Thanks Miguel! When I set these variables, the quickstart script completes successfully. Bernd Bausch On 6/21/2018 4:43 PM, Miguel Angel Ajo Pelayo wrote: > I'm also hitting that issue currently too > > you can workaround with  > >       -e docker_registry_namespace_used=tripleomaster -e > container_build_id=current-tripleo > > on the quickstart command line while this is fixed (please note that's > only for tripleo master). > > > I see in the quickstart logs that those variables are detected as > facts, but then ansible does > not find them on those tasks.  > > Note: I'm just providing a workaround that I used to keep moving, but > I'm not actively working > on fixing the quickstart issue because I don't know how to fix it at > this moment. > > > > > On Thu, Jun 21, 2018 at 2:44 AM Bernd Bausch > wrote: > > I hoped that I could use quickstart.sh to set up Tripleo without > much thinking. The Ansible playbook generates undercloud, compute > and control images and much more on the VIRTHOST but ultimately > fails with: > > TASK [undercloud-deploy : Write containers-prepare-parameter.yaml] > ************************************************************************** > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96 > Wednesday 20 June 2018  18:31:07 +0900 (0:00:07.221)       > 1:14:05.859 ******** > fatal: [undercloud]: FAILED! => {"changed": false, "failed": true, > "msg": "AnsibleUndefinedVariable: 'container_build_id' is undefined"} > > What puzzles me (I am far from being an Ansible expert): If I > interpret /_quickstart.log/ correctly, this variable is set about > half-way through the process: > > TASK [extras-common : set container_build_id from > docker_image_tag] > ************************************************************************* > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 > Wednesday 20 June 2018  17:23:13 +0900 (0:00:00.212)       > 0:06:12.229 ******** > ok: [jupiter] => {*"ansible_facts": {"container_build_id": > "current-tripleo-rdo"},* "changed": false, "failed": false} > > Later plays also set it conditionally, but the conditions are > never met. Some derive it from a variable named > /get_build_command/, which I can't find anywhere (I did do a > http://codesearch.openstack.org): > > TASK [extras-common : set container_build_id from > get_build_command] > ************************************************************************ > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6 > Wednesday 20 June 2018  18:16:45 +0900 (0:00:00.323)       > 0:59:44.741 ******** > skipping: [jupiter] => {"changed": false, "skip_reason": > "Conditional result was False", "skipped": true} > > others base it on a Docker container tag: > > TASK [extras-common : set container_build_id from > docker_image_tag] > ************************************************************************* > task path: > /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 > Wednesday 20 June 2018  18:16:46 +0900 (0:00:00.128)       > 0:59:44.996 ******** > skipping: [jupiter] => {"changed": false, "skip_reason": > "Conditional result was False", "skipped": true} > > Any pointers how to fix this? > > My VIRTHOST is a HP Z420 workstation named /jupiter/, 4 core Xeon, > 32G memory, 150G disk space running freshly installed Centos 7.5. > I run the quickstart script on a VM, equally with Centos 7.5. I > followed the instructions at > https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart: > > $ ssh-keygen; ssh-copy-id root at jupiter; ssh-copy-id stack at jupiter > $ > curl-Ohttps://raw.githubusercontent.com/openstack/tripleo-quickstart/master/quickstart.sh > $ bashquickstart.sh--install-deps > $ bash quickstart.sh jupiter > > Bernd Bausch > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to     : openstack at lists.openstack.org > > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From nick.bmth at gmail.com Fri Jun 22 15:36:31 2018 From: nick.bmth at gmail.com (Nick A) Date: Fri, 22 Jun 2018 16:36:31 +0100 Subject: [Openstack] Network Planning Message-ID: Hello everyone! I'm planning a small test Openstack deployment, 3 compute nodes and 5 ceph nodes. The part I'm struggling with is public/private networking. Whilst I wait for the hardware to arrive, what I'm trying to work out is exactly what I need to make this a reality, I've read everything I can find but still not 100% sure: 1. Each customer/account has a private network (10.0.0.0/8 for example) available 2. By default, VM's are provisioned with a public (internet routed IP) NIC and a private NIC (connected to their private network). 3. No dedicated network node Each compute node will have: 1G management connection 1G public internet connection, L3 for this will be done elsewhere. 40G private networking connection Am I right in assuming the public network is essentially a flat network, then I can use OVS for the private networks? Can that be done at the same time? Is that possible without a dedicated network node? If someone could point me in the right direction it'd be greatly appreciated. Regards, Nick From clay.gerrard at gmail.com Fri Jun 22 16:22:15 2018 From: clay.gerrard at gmail.com (Clay Gerrard) Date: Fri, 22 Jun 2018 09:22:15 -0700 Subject: [Openstack] Swift3 bucket naming conventions In-Reply-To: References: Message-ID: Swift containers can certainly have underscores in them... almost any character is valid. But I guess s3api thinks that's maybe not a valid bucket name? https://github.com/openstack/swift/blob/master/test/unit/common/middleware/s3api/test_utils.py#L38 -Clay On Thu, Jun 21, 2018 at 3:27 AM, Shyam Prasad N wrote: > Hi, > > On my openstack swift s3 interface, I tried to create bucket names similar > to what I have in my AWS S3. But swift3 doesn't seem to allow bucket names > containing underscore. Once I remove the underscore and try to create the > bucket, it works. Is there a way to overcome this? > > -- > -Shyam > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Fri Jun 22 23:14:19 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Sat, 23 Jun 2018 08:14:19 +0900 Subject: [Openstack] Network Planning In-Reply-To: References: Message-ID: <54C5A93F-EA81-4C3B-A806-B4DBEA8FA85D@gmail.com> A typical deployment has one or more external networks and as many private networks as users want. An external network represents (part or all of) the network outside of the cloud. It’s either flat or VLAN. You can allow users to create their own network structure and routing, connected to the external network with the help of OVS bridges, Linuxbridges and other mechanisms. “Each customer/account has a private network” is a bit misleading. Customers can set up complex multi-tier network structures, not just one network, and they can use whatever IP address ranges they want. “By default, VM's are provisioned with a public (internet routed IP) NIC and a private NIC” is also not quite right. VMs get an IP on the customer’s network (the usual term is tenant network). The customer can add external IP addresses, named floating IP. In a typical application, not all VMs need them. You are correct, no separate network node is required. I believe the recommendation to set up a separate network node was made at the time when all routed traffic used to flow through this one node. That’s not the case anymore if you deploy the distributed router. In addition to your compute and Ceph nodes, you do need a controller though. The same server can have both the controller and the compute role, but they are normally kept separate for better performance and ease of management. See the Networking guide and the Installation tutorials for more detail. In particular, look for the terms “provider network” and “tenant network”, and the deployment examples in both guides. https://docs.openstack.org/neutron/latest/admin/index.html https://docs.openstack.org/queens/install/ Regarding terminology: Strictly speaking, “public” and “private” are not OpenStack terms. They are the names given to the external and tenant networks provisioned by some deployment tools like Devstack or Packstack. Bernd > On Jun 23, 2018, at 0:36, Nick A wrote: > > Hello everyone! > > I'm planning a small test Openstack deployment, 3 compute nodes and 5 > ceph nodes. The part I'm struggling with is public/private networking. > > Whilst I wait for the hardware to arrive, what I'm trying to work out > is exactly what I need to make this a reality, I've read everything I > can find but still not 100% sure: > > 1. Each customer/account has a private network (10.0.0.0/8 for > example) available > 2. By default, VM's are provisioned with a public (internet routed IP) > NIC and a private NIC (connected to their private network). > 3. No dedicated network node > > Each compute node will have: > 1G management connection > 1G public internet connection, L3 for this will be done elsewhere. > 40G private networking connection > > Am I right in assuming the public network is essentially a flat > network, then I can use OVS for the private networks? Can that be done > at the same time? Is that possible without a dedicated network node? > If someone could point me in the right direction it'd be greatly > appreciated. > > Regards, > Nick > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From remo at italy1.com Sat Jun 23 02:38:13 2018 From: remo at italy1.com (Remo Mattei) Date: Fri, 22 Jun 2018 19:38:13 -0700 Subject: [Openstack] Network Planning In-Reply-To: <54C5A93F-EA81-4C3B-A806-B4DBEA8FA85D@gmail.com> References: <54C5A93F-EA81-4C3B-A806-B4DBEA8FA85D@gmail.com> Message-ID: First how do you deploy it? Normally now vxlan is used between tenants now called projects. They do pock into the provider network but they cannot talk to each other since we are using namespaces. Are you going to have separation between other services? Feel free to ping me Remo > Il giorno 22 giu 2018, alle ore 16:14, Bernd Bausch ha scritto: > > A typical deployment has one or more external networks and as many private networks as users want. > > An external network represents (part or all of) the network outside of the cloud. It’s either flat or VLAN. You can allow users to create their own network structure and routing, connected to the external network with the help of OVS bridges, Linuxbridges and other mechanisms. > > “Each customer/account has a private network” is a bit misleading. Customers can set up complex multi-tier network structures, not just one network, and they can use whatever IP address ranges they want. > > “By default, VM's are provisioned with a public (internet routed IP) NIC and a private NIC” is also not quite right. VMs get an IP on the customer’s network (the usual term is tenant network). The customer can add external IP addresses, named floating IP. In a typical application, not all VMs need them. > > You are correct, no separate network node is required. I believe the recommendation to set up a separate network node was made at the time when all routed traffic used to flow through this one node. That’s not the case anymore if you deploy the distributed router. > > In addition to your compute and Ceph nodes, you do need a controller though. The same server can have both the controller and the compute role, but they are normally kept separate for better performance and ease of management. > > See the Networking guide and the Installation tutorials for more detail. In particular, look for the terms “provider network” and “tenant network”, and the deployment examples in both guides. > https://docs.openstack.org/neutron/latest/admin/index.html > https://docs.openstack.org/queens/install/ > > Regarding terminology: Strictly speaking, “public” and “private” are not OpenStack terms. They are the names given to the external and tenant networks provisioned by some deployment tools like Devstack or Packstack. > > Bernd > >> On Jun 23, 2018, at 0:36, Nick A wrote: >> >> Hello everyone! >> >> I'm planning a small test Openstack deployment, 3 compute nodes and 5 >> ceph nodes. The part I'm struggling with is public/private networking. >> >> Whilst I wait for the hardware to arrive, what I'm trying to work out >> is exactly what I need to make this a reality, I've read everything I >> can find but still not 100% sure: >> >> 1. Each customer/account has a private network (10.0.0.0/8 for >> example) available >> 2. By default, VM's are provisioned with a public (internet routed IP) >> NIC and a private NIC (connected to their private network). >> 3. No dedicated network node >> >> Each compute node will have: >> 1G management connection >> 1G public internet connection, L3 for this will be done elsewhere. >> 40G private networking connection >> >> Am I right in assuming the public network is essentially a flat >> network, then I can use OVS for the private networks? Can that be done >> at the same time? Is that possible without a dedicated network node? >> If someone could point me in the right direction it'd be greatly >> appreciated. >> >> Regards, >> Nick >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack at lists.openstack.org >> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From doka.ua at gmx.com Sat Jun 23 13:40:50 2018 From: doka.ua at gmx.com (Volodymyr Litovka) Date: Sat, 23 Jun 2018 16:40:50 +0300 Subject: [Openstack] can't resize server In-Reply-To: <20180615073415.Horde.BJ-cHfvI4vskH-pKYRwG9Tk@webmail.nde.ag> References: <20180615073415.Horde.BJ-cHfvI4vskH-pKYRwG9Tk@webmail.nde.ag> Message-ID: Hi Eugen, actually, I did some tests with making volume available without stopping it. I'm using CEPH and these steps produce the following results: 1) openstack volume set --state available [UUID] - nothing changed inside both VM (volume is still connected) and CEPH 2) openstack volume set --size [new size] --state in-use [UUID] - nothing changed inside VM (volume is still connected and has an old size) - size of CEPH volume changed to the new value 3) during these operations I was copying a lot of data from external source and all md5 sums are the same on both VM and source 4) changes on VM happens upon any kind of power-cycle (e.g. reboot (either soft or hard): openstack server reboot [--hard] [VM uuid] ) - note: NOT after 'reboot' from inside VM I think, all these manipilations with cinder/ceph just update internal parameters of these subsystems, without immediate effect for VMs. In order to apply for the changes, you need to power-cycle it. From practical point of view, it's useful when you, for example, update project in batch mode, and will then manually reboot every VM, affected by the update, with minimized downtime (it's just reboot, not manual stop/update/start). On 6/15/18 10:34 AM, Eugen Block wrote: > Hi, > > did you find a solution yet? > > If not, I tried to rebuild your situation with a test instance. > Although the environment and the storage backend are different, I > believe it still applies to your issue, at least in a general way. > > I have an instance booted from volume (size 1 GB). Trying to resize > the instance via Horizon dashboard works (at least you would think > that), it shows a new flavor with a disk size 8 GB. But the volume has > not been resized, so the instance won't notice any changes. > To accomplish that, I had to shutdown the vm, set the volume state to > available (you can't detach a root disk volume), then resize the > volume to the size of the flavor, and then boot the vm again, now its > disk has the desired size. > > control:~ # openstack server stop test1 > control:~ # openstack volume set --state available > b832f798-e0de-4338-836a-07375f3ae3a0 > control:~ # openstack volume set --size 8 > b832f798-e0de-4338-836a-07375f3ae3a0 > control:~ # openstack volume set --state in-use > b832f798-e0de-4338-836a-07375f3ae3a0 > control:~ # openstack server start test1 > > I should mention that I use live-migration, so during resize of an > instance it migrates to another compute node. > Hope this helps! > > Regards > Eugen > > > Zitat von Manuel Sopena Ballesteros : > >> Dear openstack community, >> >> I have a packstack all-in-one environment and I would like to resize >> one of the vms. It seems like the resize process fails due to an >> issue with cinder >> >> NOTE: the vm boots from volume and not from image >> >> This is the vm I am trying to resize >> >> [root at openstack ~(keystone_admin)]# openstack server show >> 7292a929-54d9-4ce6-a595-aaf93a2be320 >> +--------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ >> >> | Field                                | Value >>                                              | >> +--------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ >> >> | OS-DCF:diskConfig                    | MANUAL >>                                              | >> | OS-EXT-AZ:availability_zone          | nova >>                                              | >> | OS-EXT-SRV-ATTR:host                 | openstack.localdomain >>                                              | >> | OS-EXT-SRV-ATTR:hypervisor_hostname  | openstack.localdomain >>                                              | >> | OS-EXT-SRV-ATTR:instance_name        | instance-0000005f >>                                              | >> | OS-EXT-STS:power_state               | Shutdown >>                                              | >> | OS-EXT-STS:task_state                | None >>                                              | >> | OS-EXT-STS:vm_state                  | error >>                                              | >> | OS-SRV-USG:launched_at               | 2018-05-14T07:24:00.000000 >>                                              | >> | OS-SRV-USG:terminated_at             | None >>                                              | >> | accessIPv4 |                                              | >> | accessIPv6 |                                              | >> | addresses                            | >> privatenetwork=192.168.1.106, 129.94.14.238 | >> | config_drive |                                              | >> | created                              | 2018-05-14T07:23:52Z >>                                              | >> | fault                                | {u'message': u'The server >> has either erred or is incapable of performing the requested >> operation. (HTTP 500) (Request-ID: >> req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a)', u'code': 500, u'details': >> u'  File           | >> |                                      | >> "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 204, >> in decorated_function\n    return function(self, context, *args, >> **kwargs)\n  File "/usr/lib/python2.7/site-                   >>               | >> |                                      | >> packages/nova/compute/manager.py", line 3810, in resize_instance\n   >>  self._terminate_volume_connections(context, instance, bdms)\n  File >> "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line >> 3843,   | >> |                                      | in >> _terminate_volume_connections\n    connector)\n  File >> "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 188, >> in wrapper\n    res = method(self, ctx, *args, **kwargs)\n File >> "/usr/lib/python2.7  | >> |                                      | >> /site-packages/nova/volume/cinder.py", line 210, in wrapper\n res = >> method(self, ctx, volume_id, *args, **kwargs)\n  File >> "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 416, >> in                | >> |                                      | terminate_connection\n    >> connector)\n  File >> "/usr/lib/python2.7/site-packages/cinderclient/v3/volumes.py", line >> 426, in terminate_connection\n    {\'connector\': connector})\n  File >> "/usr/lib/python2.7/site-   | >> |                                      | >> packages/cinderclient/v3/volumes.py", line 346, in _action\n resp, >> body = self.api.client.post(url, body=body)\n  File >> "/usr/lib/python2.7/site-packages/cinderclient/client.py", line 146, >> in post\n    return | >> |                                      | self._cs_request(url, >> \'POST\', **kwargs)\n  File >> "/usr/lib/python2.7/site-packages/cinderclient/client.py", line 134, >> in _cs_request\n    return self.request(url, method, **kwargs)\n  >> File "/usr/lib/python2.7  | >> |                                      | >> /site-packages/cinderclient/client.py", line 123, in request\n    >> raise exceptions.from_response(resp, body)\n', u'created': >> u'2018-05-28T07:54:40Z'}                  | >> | flavor                               | m1.medium (3) >>                                              | >> | hostId                               | >> ecef276660cd714fe626073a18c11fe1c00bec91c15516178fb6ac28     | >> | id                                   | >> 7292a929-54d9-4ce6-a595-aaf93a2be320     | >> | image |                                              | >> | key_name                             | None >>                                              | >> | name                                 | danrod-server >>                                              | >> | os-extended-volumes:volumes_attached | [{u'id': >> u'f1ac2e94-b0ed-4089-898f-5b6467fb51e3'}] | >> | project_id                           | >> d58cf22d960e4de49b71658aee642e94     | >> | properties |                                              | >> | security_groups                      | [{u'name': u'admin'}, >> {u'name': u'R-Studio Server'}] >>                                                    | >> | status                               | ERROR >>                                              | >> | updated                              | 2018-05-28T07:54:40Z >>                                              | >> | user_id                              | >> c412f34c353244eabecd4b6dc4d36392     | >> +--------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ >> >> >> Cinder volume logs >> >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio >> [req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a >> c412f34c353244eabecd4b6dc4d36392 d58cf22d960e4de49b71658aee642e94 - >> default default] Failed to delete initiator iqn >> iqn.1994-05.com.redhat:401b935e7b19 from target. >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio >> Traceback (most recent call last): >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File >> "/usr/lib/python2.7/site-packages/cinder/volume/targets/lio.py", line >> 197, in terminate_connection >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio >> run_as_root=True) >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File >> "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", >> line 271, in inner >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio return >> f(*args, **kwargs) >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File >> "/usr/lib/python2.7/site-packages/cinder/volume/targets/lio.py", line >> 52, in _execute >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio return >> utils.execute(*args, **kwargs) >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File >> "/usr/lib/python2.7/site-packages/cinder/utils.py", line 123, in execute >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio return >> processutils.execute(*cmd, **kwargs) >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio File >> "/usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py", >> line 389, in execute >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio >> cmd=sanitized_cmd) >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio >> ProcessExecutionError: Unexpected error while running command. >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio Command: >> sudo cinder-rootwrap /etc/cinder/rootwrap.conf cinder-rtstool >> delete-initiator >> iqn.2010-10.org.openstack:volume-f1ac2e94-b0ed-4089-898f-5b6467fb51e3 >> iqn.1994-05.com.redhat:401b935e7b19 >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio Exit >> code: 1 >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio Stdout: u'' >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio Stderr: >> u'Traceback (most recent call last):\n  File "/bin/cinder-rtstool", >> line 10, in \n sys.exit(main())\n  File >> "/usr/lib/python2.7/site-packages/cinder/cmd/rtstool.py", line 313, >> in main\n    delete_initiator(target_iqn, initiator_iqn)\n File >> "/usr/lib/python2.7/site-packages/cinder/cmd/rtstool.py", line 143, >> in delete_initiator\n    target = _lookup_target(target_iqn, >> initiator_iqn)\n  File >> "/usr/lib/python2.7/site-packages/cinder/cmd/rtstool.py", line 123, >> in _lookup_target\n    raise RtstoolError(_(\'Could not find target >> %s\') % target_iqn)\ncinder.cmd.rtstool.RtstoolError: Could not find >> target >> iqn.2010-10.org.openstack:volume-f1ac2e94-b0ed-4089-898f-5b6467fb51e3\n' >> 2018-05-28 17:54:39.809 6804 ERROR cinder.volume.targets.lio >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager >> [req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a >> c412f34c353244eabecd4b6dc4d36392 d58cf22d960e4de49b71658aee642e94 - >> default default] Terminate volume connection failed: Failed to detach >> iSCSI target for volume f1ac2e94-b0ed-4089-898f-5b6467fb51e3. >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager Traceback >> (most recent call last): >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager   File >> "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line >> 1493, in terminate_connection >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager force=force) >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager   File >> "/usr/lib/python2.7/site-packages/cinder/volume/drivers/lvm.py", line >> 848, in terminate_connection >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager **kwargs) >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager   File >> "/usr/lib/python2.7/site-packages/cinder/volume/targets/lio.py", line >> 202, in terminate_connection >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager raise >> exception.ISCSITargetDetachFailed(volume_id=volume['id']) >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager >> ISCSITargetDetachFailed: Failed to detach iSCSI target for volume >> f1ac2e94-b0ed-4089-898f-5b6467fb51e3. >> 2018-05-28 17:54:39.813 6804 ERROR cinder.volume.manager >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server >> [req-bf6a33bd-affc-48a3-80f3-e6e1be459e7a >> c412f34c353244eabecd4b6dc4d36392 d58cf22d960e4de49b71658aee642e94 - >> default default] Exception during message handling >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server >> Traceback (most recent call last): >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File >> "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line >> 133, in _process_incoming >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server res = >> self.dispatcher.dispatch(message) >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File >> "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", >> line 150, in dispatch >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server return >> self._do_dispatch(endpoint, method, ctxt, args) >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File >> "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", >> line 121, in _do_dispatch >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server result = >> func(ctxt, **new_args) >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File >> "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line >> 4404, in terminate_connection >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server >> force=force) >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server File >> "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line >> 1498, in terminate_connection >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server raise >> exception.VolumeBackendAPIException(data=err_msg) >> 2018-05-28 17:54:39.814 6804 ERROR oslo_messaging.rpc.server >> VolumeBackendAPIException: Bad or unexpected response from the >> storage volume backend API: Terminate volume connection failed: >> Failed to detach iSCSI target for volume >> f1ac2e94-b0ed-4089-898f-5b6467fb51e3. >> >> Any thoughts? >> >> Manuel Sopena Ballesteros | Big data Engineer >> Garvan Institute of Medical Research >> The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010 >> T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: >> manuel.sb at garvan.org.au >> >> NOTICE >> Please consider the environment before printing this email. This >> message and any attachments are intended for the addressee named and >> may contain legally privileged/confidential/copyright information. If >> you are not the intended recipient, you should not read, use, >> disclose, copy or distribute this communication. If you have received >> this message in error please notify us at once by return email and >> then delete both messages. We accept no liability for the >> distribution of viruses or similar in electronic communications. This >> notice should not be removed. > > > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to     : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison From poby1972 at gmail.com Sat Jun 23 19:09:22 2018 From: poby1972 at gmail.com (Kevin Kwon) Date: Sun, 24 Jun 2018 04:09:22 +0900 Subject: [Openstack] Swift Error in the Openstack queens Message-ID: Dear All! Hi.. I have configured the one Controller node and one Compute(included Storage) node. after installed the swift in the Compute Node, I have checked the status and tried to create a container in Controller Node like below. but, it occurred below errors. Would you please let me know how can i fixed it. ====================================== Controller Node ====================================== root at OpenStack-Controller:~# root at OpenStack-Controller:~# . demo-openrc root at OpenStack-Controller:~# root at OpenStack-Controller:~# swift stat Account: AUTH_1d375b70db694866914c25140278c35b Containers: 0 Objects: 0 Bytes: 0 X-Account-Project-Domain-Id: default X-Openstack-Request-Id: txeaaa635cf1994d8aae148-005b2e9851 X-Timestamp: 1529779320.82412 X-Trans-Id: txeaaa635cf1994d8aae148-005b2e9851 Content-Type: application/json; charset=utf-8 Accept-Ranges: bytes root at OpenStack-Controller:~# root at OpenStack-Controller:~# root at OpenStack-Controller:~# root at OpenStack-Controller:~# root at OpenStack-Controller:~# openstack container list root at OpenStack-Controller:~# root at OpenStack-Controller:~# openstack container create container1 Service Unavailable (HTTP 503) (Request-ID: tx0841624d3b47476398113-005b2e98a6) root at OpenStack-Controller:~# ======================================= Storage Node ======================================== Jun 24 03:48:04 OpenStack-Controller proxy-server: - - 23/Jun/2018/18/48/04 HEAD /v1/AUTH_1d375b70db694866914c25140278c35b%3Fformat%3Djson HTTP/1.0 204 - Swift - - - - tx3fb4ae2d2c1948b3846e7-005b2e95e4 - 0.0081 RL - 1529779684.666325092 1529779684.674436092 - Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with Container server 10.0.0.51:6201/sdc re: Trying to PUT /AUTH_1d375b70db694866914c25140278c35b/container1: ConnectionTimeout (0.5s) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with Container server 10.0.0.51:6201/sdd re: Trying to PUT /AUTH_1d375b70db694866914c25140278c35b/container1: ConnectionTimeout (0.5s) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with Container server 10.0.0.51:6201/sde re: Trying to PUT /AUTH_1d375b70db694866914c25140278c35b/container1: ConnectionTimeout (0.5s) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) Jun 24 03:48:05 OpenStack-Controller proxy-server: Container PUT returning 503 for (503, 503, 503) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) Jun 24 03:48:05 OpenStack-Controller proxy-server: 192.168.100.101 192.168.100.101 23/Jun/2018/18/48/05 PUT /v1/AUTH_1d375b70db694866914c25140278c35b/container1 HTTP/1.0 503 - osc-lib/1.9.0%20keystoneauth1/3.4.0%20python-requests/2.18.4%20CPython/2.7.12 gAAAAABbLpXkaKj1... - 118 - tx3fb4ae2d2c1948b3846e7-005b2e95e4 - 0.8265 - - 1529779684.665580988 1529779685.492069960 - Thank you! Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From poby1972 at gmail.com Sat Jun 23 21:01:02 2018 From: poby1972 at gmail.com (Kevin Kwon) Date: Sun, 24 Jun 2018 06:01:02 +0900 Subject: [Openstack] To create Network after install manually Message-ID: Dear All! HI.. I have installed the Openstack with Controller-Compute Node by manually with Provider Network. when i tried to create the network on Openstack GUI, I couldn't create it because below error messages. would you please let me know how can i create network and check status? 2018-06-24 05:55:43.627 2763 INFO neutron.wsgi [req-ebd9f116-16c8-4c6e-9b7e-1c30cda4c240 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/availability_zones HTTP/1.1" status: 200 len: 285 time: 0.0281010 2018-06-24 05:55:43.657 2761 INFO neutron.wsgi [req-30b4b825-1e4f-48b9-a720-e31e0da62688 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/availability_zones HTTP/1.1" status: 200 len: 285 time: 0.0219860 2018-06-24 05:55:43.697 2761 INFO neutron.wsgi [req-20a1c897-a416-446e-9138-d1381e416e9f ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/subnetpools HTTP/1.1" status: 200 len: 216 time: 0.0319090 2018-06-24 05:55:43.836 2761 INFO neutron.pecan_wsgi.hooks.translation [req-93c05a57-c5da-45c2-9fbc-aa586c6317c3 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] POST failed (client error): The server could not comply with the request since it is either malformed or otherwise incorrect. 2018-06-24 05:55:44.081 2761 INFO neutron.wsgi [req-93c05a57-c5da-45c2-9fbc-aa586c6317c3 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "POST /v2.0/networks HTTP/1.1" status: 400 len: 349 time: 0.3781040 *2018-06-24 05:55:44.126 2762 INFO neutron.wsgi [req-23595cd9-5746-43b5-94f9-506fcc4fcb47 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/extensions HTTP/1.1" status: 200 len: 6914 time: 0.0106690* *2018-06-24 05:55:44.215 2761 INFO neutron.wsgi [req-7b9896d5-694f-4e7e-b4e4-5b7cbdd7b665 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/networks HTTP/1.1" status: 200 len: 213 time: 0.0829711* 2018-06-24 05:55:44.267 2763 INFO neutron.wsgi [req-e56f827c-8e14-4573-91e4-6d1b7c7abb69 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/subnets HTTP/1.1" status: 200 len: 212 time: 0.0480430 Have a nice day! Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Sat Jun 23 23:55:32 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Sun, 24 Jun 2018 08:55:32 +0900 Subject: [Openstack] Swift Error in the Openstack queens In-Reply-To: References: Message-ID: <9403a48e-d6ee-2cc7-22d0-ba084271cf78@gmail.com> The message "ERROR with Container server 10.0.0.51:6201/sdc re: Trying to PUT /AUTH_1d375b70db694866914c25140278c35b/container1: ConnectionTimeout (0.5s" indicates that either 10.0.0.51 is not listening on port 6201, or it is so busy that it doesn't respond in time. On 6/24/2018 4:09 AM, Kevin Kwon wrote: > Dear All! > > Hi.. > I have configured the one Controller node and one Compute(included > Storage) node. > > after installed the swift in the Compute Node, I have checked the > status and tried to create a container in Controller Node like below. > but, it occurred below errors. > Would you please let me know how can i fixed it. > > > ====================================== > Controller Node > ====================================== > > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# . demo-openrc > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# swift stat >                     Account: AUTH_1d375b70db694866914c25140278c35b >                  Containers: 0 >                     Objects: 0 >                       Bytes: 0 > X-Account-Project-Domain-Id: default >      X-Openstack-Request-Id: txeaaa635cf1994d8aae148-005b2e9851 >                 X-Timestamp: 1529779320.82412 >                  X-Trans-Id: txeaaa635cf1994d8aae148-005b2e9851 >                Content-Type: application/json; charset=utf-8 >               Accept-Ranges: bytes > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# openstack container list > > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# openstack container create container1 > Service Unavailable (HTTP 503) (Request-ID: > tx0841624d3b47476398113-005b2e98a6) > root at OpenStack-Controller:~# > > > ======================================= > Storage Node > ======================================== > > Jun 24 03:48:04 OpenStack-Controller proxy-server: - - > 23/Jun/2018/18/48/04 HEAD > /v1/AUTH_1d375b70db694866914c25140278c35b%3Fformat%3Djson HTTP/1.0 204 > - Swift - - - - tx3fb4ae2d2c1948b3846e7-005b2e95e4 - 0.0081 RL - > 1529779684.666325092 1529779684.674436092 - > Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with > Container server 10.0.0.51:6201/sdc re: > Trying to PUT /AUTH_1d375b70db694866914c25140278c35b/container1: > ConnectionTimeout (0.5s) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) > (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with > Container server 10.0.0.51:6201/sdd re: > Trying to PUT /AUTH_1d375b70db694866914c25140278c35b/container1: > ConnectionTimeout (0.5s) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) > (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with > Container server 10.0.0.51:6201/sde re: > Trying to PUT /AUTH_1d375b70db694866914c25140278c35b/container1: > ConnectionTimeout (0.5s) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) > (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: Container PUT > returning 503 for (503, 503, 503) (txn: > tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: 192.168.100.101 > 192.168.100.101 23/Jun/2018/18/48/05 PUT > /v1/AUTH_1d375b70db694866914c25140278c35b/container1 HTTP/1.0 503 - > osc-lib/1.9.0%20keystoneauth1/3.4.0%20python-requests/2.18.4%20CPython/2.7.12 > gAAAAABbLpXkaKj1... - 118 - tx3fb4ae2d2c1948b3846e7-005b2e95e4 - > 0.8265 - - 1529779684.665580988 1529779685.492069960 - > > > > Thank you! > Kevin > > > > > > > > > > > > > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From berndbausch at gmail.com Sun Jun 24 00:02:31 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Sun, 24 Jun 2018 09:02:31 +0900 Subject: [Openstack] To create Network after install manually In-Reply-To: References: Message-ID: <7325fc82-550e-6617-f67a-9ae93a032fd9@gmail.com> If you built your cloud with a provider network only, you can't create tenant networks. You need to configure "network option 2, self-service networks", for example at https://docs.openstack.org/neutron/latest/install/controller-install-option2-ubuntu.html. On 6/24/2018 6:01 AM, Kevin Kwon wrote: > > Dear All! > > HI.. > I have installed the Openstack  with Controller-Compute Node by > manually with Provider Network. > > when i tried to create the network on Openstack GUI, I couldn't create > it because below error messages. > > would you please let me know how can i create network and check status? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From poby1972 at gmail.com Sun Jun 24 02:35:57 2018 From: poby1972 at gmail.com (Kevin Kwon) Date: Sun, 24 Jun 2018 11:35:57 +0900 Subject: [Openstack] Swift Error in the Openstack queens In-Reply-To: <9403a48e-d6ee-2cc7-22d0-ba084271cf78@gmail.com> References: <9403a48e-d6ee-2cc7-22d0-ba084271cf78@gmail.com> Message-ID: Dear Bernd! I found that i was wrong when i create the container ring . Thank you so much! Kevin 2018-06-24 8:55 GMT+09:00 Bernd Bausch : > The message "ERROR with Container server 10.0.0.51:6201/sdc re: Trying to > PUT /AUTH_1d375b70db694866914c25140278c35b/container1: ConnectionTimeout > (0.5s" indicates that either 10.0.0.51 is not listening on port 6201, or it > is so busy that it doesn't respond in time. > On 6/24/2018 4:09 AM, Kevin Kwon wrote: > > Dear All! > > Hi.. > I have configured the one Controller node and one Compute(included > Storage) node. > > after installed the swift in the Compute Node, I have checked the status > and tried to create a container in Controller Node like below. > but, it occurred below errors. > Would you please let me know how can i fixed it. > > > ====================================== > Controller Node > ====================================== > > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# . demo-openrc > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# swift stat > Account: AUTH_1d375b70db694866914c25140278c35b > Containers: 0 > Objects: 0 > Bytes: 0 > X-Account-Project-Domain-Id: default > X-Openstack-Request-Id: txeaaa635cf1994d8aae148-005b2e9851 > X-Timestamp: 1529779320.82412 > X-Trans-Id: txeaaa635cf1994d8aae148-005b2e9851 > Content-Type: application/json; charset=utf-8 > Accept-Ranges: bytes > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# openstack container list > > root at OpenStack-Controller:~# > root at OpenStack-Controller:~# openstack container create container1 > Service Unavailable (HTTP 503) (Request-ID: tx0841624d3b47476398113- > 005b2e98a6) > root at OpenStack-Controller:~# > > > ======================================= > Storage Node > ======================================== > > Jun 24 03:48:04 OpenStack-Controller proxy-server: - - > 23/Jun/2018/18/48/04 HEAD /v1/AUTH_1d375b70db694866914c25140278c35b%3Fformat%3Djson > HTTP/1.0 204 - Swift - - - - tx3fb4ae2d2c1948b3846e7-005b2e95e4 - 0.0081 > RL - 1529779684.666325092 1529779684.674436092 - > Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with Container > server 10.0.0.51:6201/sdc re: Trying to PUT /AUTH_ > 1d375b70db694866914c25140278c35b/container1: ConnectionTimeout (0.5s) > (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with Container > server 10.0.0.51:6201/sdd re: Trying to PUT /AUTH_ > 1d375b70db694866914c25140278c35b/container1: ConnectionTimeout (0.5s) > (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: ERROR with Container > server 10.0.0.51:6201/sde re: Trying to PUT /AUTH_ > 1d375b70db694866914c25140278c35b/container1: ConnectionTimeout (0.5s) > (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: Container PUT returning > 503 for (503, 503, 503) (txn: tx3fb4ae2d2c1948b3846e7-005b2e95e4) > (client_ip: 192.168.100.101) > Jun 24 03:48:05 OpenStack-Controller proxy-server: 192.168.100.101 > 192.168.100.101 23/Jun/2018/18/48/05 PUT /v1/AUTH_ > 1d375b70db694866914c25140278c35b/container1 HTTP/1.0 503 - > osc-lib/1.9.0%20keystoneauth1/3.4.0%20python-requests/2.18.4%20CPython/2.7.12 > gAAAAABbLpXkaKj1... - 118 - tx3fb4ae2d2c1948b3846e7-005b2e95e4 - 0.8265 - > - 1529779684.665580988 1529779685.492069960 - > > > > Thank you! > Kevin > > > > > > > > > > > > > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From majopela at redhat.com Mon Jun 25 09:21:29 2018 From: majopela at redhat.com (Miguel Angel Ajo Pelayo) Date: Mon, 25 Jun 2018 11:21:29 +0200 Subject: [Openstack] [tripleo] [tripleo-quickstart] quickstart.sh failing In-Reply-To: <390737e0-ca67-4deb-4c21-71f57548834e@gmail.com> References: <72d3fd45-d6a3-e16f-a447-863884422d5a@gmail.com> <390737e0-ca67-4deb-4c21-71f57548834e@gmail.com> Message-ID: I got that working too, but then: 1) my undercloud didn't have any hosts when I did openstack server list over stackrc 2) I had no overcloud-deploy.sh of any kind Folks I need help with this, I'm blocked. On Fri, Jun 22, 2018 at 10:48 AM Bernd Bausch wrote: > Thanks Miguel! When I set these variables, the quickstart script completes > successfully. > > Bernd Bausch > On 6/21/2018 4:43 PM, Miguel Angel Ajo Pelayo wrote: > > I'm also hitting that issue currently too > > you can workaround with > > -e docker_registry_namespace_used=tripleomaster -e > container_build_id=current-tripleo > > on the quickstart command line while this is fixed (please note that's > only for tripleo master). > > > I see in the quickstart logs that those variables are detected as facts, > but then ansible does > not find them on those tasks. > > Note: I'm just providing a workaround that I used to keep moving, but I'm > not actively working > on fixing the quickstart issue because I don't know how to fix it at this > moment. > > > > > On Thu, Jun 21, 2018 at 2:44 AM Bernd Bausch > wrote: > >> I hoped that I could use quickstart.sh to set up Tripleo without much >> thinking. The Ansible playbook generates undercloud, compute and control >> images and much more on the VIRTHOST but ultimately fails with: >> >> TASK [undercloud-deploy : Write containers-prepare-parameter.yaml] >> ************************************************************************** >> task path: >> /home/stack/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/create-scripts.yml:96 >> Wednesday 20 June 2018 18:31:07 +0900 (0:00:07.221) 1:14:05.859 >> ******** >> fatal: [undercloud]: FAILED! => {"changed": false, "failed": true, "msg": >> "AnsibleUndefinedVariable: 'container_build_id' is undefined"} >> What puzzles me (I am far from being an Ansible expert): If I interpret >> *_quickstart.log* correctly, this variable is set about half-way through >> the process: >> >> TASK [extras-common : set container_build_id from docker_image_tag] >> ************************************************************************* >> task path: >> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 >> Wednesday 20 June 2018 17:23:13 +0900 (0:00:00.212) 0:06:12.229 >> ******** >> ok: [jupiter] => {*"ansible_facts": {"container_build_id": >> "current-tripleo-rdo"},* "changed": false, "failed": false} >> >> Later plays also set it conditionally, but the conditions are never met. >> Some derive it from a variable named *get_build_command*, which I can't >> find anywhere (I did do a http://codesearch.openstack.org): >> >> TASK [extras-common : set container_build_id from get_build_command] >> ************************************************************************ >> task path: >> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:6 >> Wednesday 20 June 2018 18:16:45 +0900 (0:00:00.323) 0:59:44.741 >> ******** >> skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional >> result was False", "skipped": true} >> >> others base it on a Docker container tag: >> >> TASK [extras-common : set container_build_id from docker_image_tag] >> ************************************************************************* >> task path: >> /home/stack/.quickstart/usr/local/share/ansible/roles/extras-common/tasks/main.yml:19 >> Wednesday 20 June 2018 18:16:46 +0900 (0:00:00.128) 0:59:44.996 >> ******** >> skipping: [jupiter] => {"changed": false, "skip_reason": "Conditional >> result was False", "skipped": true} >> >> Any pointers how to fix this? >> >> My VIRTHOST is a HP Z420 workstation named *jupiter*, 4 core Xeon, 32G >> memory, 150G disk space running freshly installed Centos 7.5. I run the >> quickstart script on a VM, equally with Centos 7.5. I followed the >> instructions at >> https://docs.openstack.org/tripleo-quickstart/latest/readme.html#tripleo-quickstart >> : >> >> $ ssh-keygen; ssh-copy-id root at jupiter; ssh-copy-id stack at jupiter >> $ curl -O https://raw.githubusercontent.com/openstack/tripleo-quickstart/ >> master/quickstart.sh >> $ bash quickstart.sh --install-deps >> $ bash quickstart.sh jupiter >> >> Bernd Bausch >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack at lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ellstripes at gmail.com Mon Jun 25 18:23:52 2018 From: ellstripes at gmail.com (Ell Marquez) Date: Mon, 25 Jun 2018 13:23:52 -0500 Subject: [Openstack] OpenStack Mentorship Program Relaunch Message-ID: Hello all, We are happy to announce the relaunch of the OpenStack Mentoring program, and we are kicking off with some changes to the program that we hope will better serve the community. Previously mentoring occurred through one on one partnering of mentor and mentee; this new program will focus on providing mentorship through goal-focused cohorts of mentors. This change will allow mentoring responsibilities to be shared among each group's mentors. The initial cohorts will be: - Get your first patch merged - First CFP submission / Give your first talk - Become COA certified / study for COA - Deploy your first Cloud If you are interested in joining as a mentor or mentee, please sign up at : Mentor Signup: https://openstackfoundation.formstack.com/forms/mentoring_ cohorts_mentors Mentee Signup: https://openstackfoundation.formstack.com/forms/mentoring_ cohorts_mentees freenode irc room: #openstack-mentoring Cheers, Ell Marquez and Jill Rouleau -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrhillsman at gmail.com Mon Jun 25 19:10:46 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Mon, 25 Jun 2018 14:10:46 -0500 Subject: [Openstack] Get Your Survey On! Message-ID: Hi everyone, Running, operating, supporting an OpenStack cloud? Participate in the User Survey to share more about your technology implementations and provide feedback for the community. The deadline to complete the survey and be part of the next report is *Friday, August 3 at 23:59 UTC.* - Login and complete the OpenStack User Survey here: http://www.openstack.org/user-survey - Help with the survey analysis by jointing the OpenStack User Survey Working Group: https://openstackfoundation.formstack.com/forms/user_ survey_working_group - And promote the User Survey!: https://twitter.com/Op enStack/status/993589356312088577 -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From porgfa at gmail.com Tue Jun 26 11:25:06 2018 From: porgfa at gmail.com (Max) Date: Tue, 26 Jun 2018 13:25:06 +0200 Subject: [Openstack] RDO Queens and Murano Message-ID: Hi All! I'm looking for help with Murano! I setup a AIO RDO Openstack solution for Lab use, an now I'm trying to integrate Murano using RDO rpms and this doc: https://docs.openstack.org/murano/queens/admin/deploy_murano/install_ manually.html It seems everything is ok, but both on horizon and cli i receive this error message and i'm not able to configure/create anything: 2018-06-26 13:19:56.452 2330 WARNING keystonemiddleware.auth_token [-] Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use memcache for the auth_token token cache by setting the memcached_servers option. 2018-06-26 13:19:56.468 2330 WARNING keystonemiddleware.auth_token [-] Authorization failed for token: InvalidToken: Token authorization failed Any idea? Thanks in advance P -------------- next part -------------- An HTML attachment was scrubbed... URL: From skaplons at redhat.com Tue Jun 26 14:44:51 2018 From: skaplons at redhat.com (Slawomir Kaplonski) Date: Tue, 26 Jun 2018 16:44:51 +0200 Subject: [Openstack] To create Network after install manually In-Reply-To: References: Message-ID: Hi, What is this „OpenStack GUI” which You are using? Is it Horizon? From log which You sent it only looks that Your request wasn’t done in proper format. Maybe Your client is doing something wrong or maybe You are sending encrypted request to Neutron endpoint configured as not encrypted one? > Wiadomość napisana przez Kevin Kwon w dniu 23.06.2018, o godz. 23:01: > > > Dear All! > > HI.. > I have installed the Openstack with Controller-Compute Node by manually with Provider Network. > > when i tried to create the network on Openstack GUI, I couldn't create it because below error messages. > > would you please let me know how can i create network and check status? > > > > > 2018-06-24 05:55:43.627 2763 INFO neutron.wsgi [req-ebd9f116-16c8-4c6e-9b7e-1c30cda4c240 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/availability_zones HTTP/1.1" status: 200 len: 285 time: 0.0281010 > 2018-06-24 05:55:43.657 2761 INFO neutron.wsgi [req-30b4b825-1e4f-48b9-a720-e31e0da62688 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/availability_zones HTTP/1.1" status: 200 len: 285 time: 0.0219860 > 2018-06-24 05:55:43.697 2761 INFO neutron.wsgi [req-20a1c897-a416-446e-9138-d1381e416e9f ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/subnetpools HTTP/1.1" status: 200 len: 216 time: 0.0319090 > 2018-06-24 05:55:43.836 2761 INFO neutron.pecan_wsgi.hooks.translation [req-93c05a57-c5da-45c2-9fbc-aa586c6317c3 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] POST failed (client error): The server could not comply with the request since it is either malformed or otherwise incorrect. > 2018-06-24 05:55:44.081 2761 INFO neutron.wsgi [req-93c05a57-c5da-45c2-9fbc-aa586c6317c3 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "POST /v2.0/networks HTTP/1.1" status: 400 len: 349 time: 0.3781040 > 2018-06-24 05:55:44.126 2762 INFO neutron.wsgi [req-23595cd9-5746-43b5-94f9-506fcc4fcb47 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/extensions HTTP/1.1" status: 200 len: 6914 time: 0.0106690 > 2018-06-24 05:55:44.215 2761 INFO neutron.wsgi [req-7b9896d5-694f-4e7e-b4e4-5b7cbdd7b665 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/networks HTTP/1.1" status: 200 len: 213 time: 0.0829711 > 2018-06-24 05:55:44.267 2763 INFO neutron.wsgi [req-e56f827c-8e14-4573-91e4-6d1b7c7abb69 ea238a134257452b95e3f096d21034e1 53a4a1dd44334dd29fcdbf1d514928f1 - default default] 192.168.100.101 "GET /v2.0/subnets HTTP/1.1" status: 200 len: 212 time: 0.0480430 > > Have a nice day! > Kevin > > > > > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack — Slawek Kaplonski Senior software engineer Red Hat From toni.mueller at oeko.net Tue Jun 26 18:05:34 2018 From: toni.mueller at oeko.net (Toni Mueller) Date: Tue, 26 Jun 2018 19:05:34 +0100 Subject: [Openstack] CPU Affinity And Dynamic Load Balancing Message-ID: <20180626180534.42rzcpanaasdcwv3@bla.tonimueller.org> Hi, as part of building a small but completely new OpenStack cloud on top of Queens, I am investigating the possibilities of providing SLAs for VMs. Unfortunately, I'm still rather new to OpenStack. I have a four compute nodes with a few dozen threads each, and a few VMs on top of them. Some of my VMs occasionally need to be able to nail entire cores for optimal single-threaded performance, but are usually nearly idle. For performance and reliability reasons, I would not want all high-priority VMs be scheduled on one node only, while having the less performance-critical ones share the other nodes. So the question is how to (eg) partition nodes to have at least two compartments, and/or dynamically (re-) allocate VMs to lesser used nodes/compartments. When the load goes down again, I would like to undo squeezing the other VMs into the remaining capacity and have them spread out evenly again. For me, the critical factor is having some cores exclusively used by certain VMs, if and only as long as they require it (yes, more hardware might be on the horizon later, but there's no desire to squander the money). I've read about the FilterScheduler, which looks almost good, but I would like to apply this placement mechanism to running VMs. I am also interested in just pausing VMs for seconds in turn, if I can detect that a high-priority VM needs more capacity. But I don't see off the top of my head how to partition compute nodes. Can it be done with the NUMA configuration, and then schedule based on the individual "pieces", ie. effectively not scheduling across four nodes, but, say, 16 NUMA slices in a hierarchical setting (I haven't seen the machines yet, so I don't really know what they are)? If I could sort of put a VM through the placement algorithm so that I get the placement decision, then that's sort of fine: In that case, I'd put my other VMs through the placement algoritm and "manually" (scripted) migrate them. What is the common wisdom on these problems, please? Thanks, Toni From martialmichel at datamachines.io Tue Jun 26 19:13:58 2018 From: martialmichel at datamachines.io (Martial Michel) Date: Tue, 26 Jun 2018 15:13:58 -0400 Subject: [Openstack] [Scientific] Scientific SIG meeting today at 2100 UTC Message-ID: IRC Meeting June 27th 2018 2018-06-27 2100 UTC in channel #openstack-meeting 1. Presentation: Utilizing Distributed Clouds for Compute and Storage - Marcus Ebert to present, discuss and answer questions - Video link https://youtu.be/QAda-ee-9Ko - Slides link https://goo.gl/g9EmWg 2. AOB Everybody welcome as usual :) -- Martial Michel, PhD Director of Scientific Computing Data Machines Corp. [ datamachines.io ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From torin.woltjer at granddial.com Fri Jun 29 21:04:42 2018 From: torin.woltjer at granddial.com (Torin Woltjer) Date: Fri, 29 Jun 2018 21:04:42 GMT Subject: [Openstack] Masakari on queens Message-ID: The wrong address was specified in the corosync configuration. Corrected that and now it runs without error. The important part here was the -c 1 switch of tcpdump. Timeout was being reached before a single packet was captured on tcpdump ( because the configuration of corosync was incorrect ). Once timeout was reached it was producing an exit code 124, which triggered the exception in the host_handler. Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com ---------------------------------------- From: "Torin Woltjer" Sent: 6/22/18 2:17 PM To: "Tushar.Patil at nttdata.com" Subject: Re: Masakari on queens Oddly enough, I never made changes to the original code to get that output. It is just masakari-monitor 4.0.0 as installed by pip. Here are the changes and output to that code snippit you sent: http://paste.openstack.org/show/723924/ I'd like to increase the logging, but I'm not familiar with the codebase and lack more than a rudimentary knowledge of python. I've found where it seems pip installed the files for masakari-hostmonitor, but I don't know which one contains the corosync bit. ---------------------------------------- From: "Patil, Tushar" Sent: 6/20/18 12:51 AM To: "torin.woltjer at granddial.com" Subject: Re: Masakari on queens Hi Torin, Option -i is correct. It seems that you have modified code to log error message: "ProcessExecutionError: Unexpected error while running command." Could you please log 'stderr' and 'exit_code' as well in order to know the exact error you are getting? I suspect you must be getting 124 exit code. This is a small program which I have created to simulate the error you are getting. http://paste.openstack.org/show/723882/ Please specify interface and port as per your configuration and run the program. Regards, Tushar Patil ________________________________________ From: Torin Woltjer Sent: Tuesday, June 19, 2018 9:58:32 PM To: Patil, Tushar Subject: Re: Masakari on queens Thank for the reply. Tushar Patil. The command: $timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405 returns: "tcpdump: enp2s0f0: That device doesn't support monitor mode" The command: (lowercase i) $timeout 5 tcpdump -n -c 1 -p -i vlan60 port 5405 Runs fine with no errors: "tcpdump: listening on vlan60, link-type EN10MB (Ethernet), capture size 262144 bytes" The in use interfaces on all of my nodes are as follows: enp2s0f0=192.168.114.x enp3s0f0=bond0=vlan60,vlan101 enp3s0f1=bond0=vlan60,vlan101 vlan60=management vlan101=provider >From this part of handle_host.py I can't tell what is causing the command to raise exception. ________________________________ From: "Patil, Tushar" Sent: 6/18/18 9:10 PM To: "openstack at lists.openstack.org" , "torin.woltjer at granddial.com" Subject: Re: Masakari on queens Hi Torin, Looking at the code, it seems it is trying to run below command as root user. timeout tcpdump -n -c 1 -p -I port where, tcpdump_timeout -> CONF.host.tcpdump_timeout -> default value is 5 seconds multicast_interface -> corosync_multicast_interface -> vlan60 multicast_ports-> corosync_multicast_ports -> 5405 Unfortunately, the error message is suppressed [1] hence it's difficult to know the exact reason. Can you please run below command on the host where you are running masakari-hostmonitor service? The error you would get after running this command would give you some hint to troubleshoot this issue further. $timeout 5 tcpdump -n -c 1 -p -I vlan60 port 5405 [1] : https://github.com/openstack/masakari-monitors/blob/cde057bc685b7bbc35f5c425f9690b01766654b2/masakarimonitors/hostmonitor/host_handler/handle_host.py#L121 Regards, Tushar Patil ________________________________________ From: Torin Woltjer Sent: Tuesday, June 19, 2018 4:01:29 AM To: Patil, Tushar; openstack at lists.openstack.org Subject: Masakari on queens Hello Tushar Patil, I have upgraded to Openstack Queens and am trying to run Masakari version 4.0.0 . I'm curious what additional configuration is required to get this set up correctly. /etc/masakarimonitors/masakarimonitors.conf http://paste.openstack.org/show/723726/ masakari-hostmonitor is giving me errors like: 2018-06-18 12:44:44.812 18236 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed.: ProcessExecutionError: Unexpected error while running command. 2018-06-18 12:45:14.895 18236 INFO masakarimonitors.hostmonitor.host_handler.handle_host [-] 'UBNTU-OSTACK-COMPUTE2' is 'online'. 2018-06-18 12:46:20.047 18236 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'vlan60' is failed.: ProcessExecutionError: Unexpected error while running command. Do you have any knowledge on this? Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. -------------- next part -------------- An HTML attachment was scrubbed... URL: From torin.woltjer at granddial.com Fri Jun 29 21:19:58 2018 From: torin.woltjer at granddial.com (Torin Woltjer) Date: Fri, 29 Jun 2018 21:19:58 GMT Subject: [Openstack] =?utf-8?q?=28no_subject=29?= Message-ID: <704b3de287b4426db04f9f6a303c79cf@granddial.com> Installed masakari 4.0.0 on queens. Hostmonitor, instancemonitor, and processmonitor all running on compute nodes. API and engine running on controller nodes. I've tried using the masakari client to list/add segments, any of those commands does nothing and returns: ("'NoneType' object has no attribute 'auth_url'", ', mode 'w' at 0x7f26bb4b71e0>) Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From poby1972 at gmail.com Sat Jun 30 08:15:59 2018 From: poby1972 at gmail.com (Kevin Kwon) Date: Sat, 30 Jun 2018 17:15:59 +0900 Subject: [Openstack] Keystone Error Message-ID: Dear All! Would you please help to find out why below error messages is happened when i installed keystone? when i ran the "su -s /bin/sh -c "keystone-manage db_sync" keystone" command, it can't connected to DATABASE correctly. Kevin root at OpenStack-Controller:~# hostname OpenStack-Controller root at OpenStack-Controller:~# root at OpenStack-Controller:~# cat /etc/hosts 127.0.0.1 localhost 192.168.56.101 OpenStack-Controller 192.168.56.102 OpenStack-Compute01 192.168.56.103 OpenStack-Compute02 192.168.56.104 OpenStack-Storage # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters root at OpenStack-Controller:~# root at OpenStack-Controller:~# root at OpenStack-Controller:~# ping OpenStack-Controller PING OpenStack-Controller (192.168.56.101) 56(84) bytes of data. 64 bytes from OpenStack-Controller (192.168.56.101): icmp_seq=1 ttl=64 time=0.052 ms 64 bytes from OpenStack-Controller (192.168.56.101): icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from OpenStack-Controller (192.168.56.101): icmp_seq=3 ttl=64 time=0.052 ms ^C --- OpenStack-Controller ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2006ms rtt min/avg/max/mdev = 0.050/0.051/0.052/0.006 ms root at OpenStack-Controller:~# root at OpenStack-Controller:~# cat /etc/keystone/keystone.conf [DEFAULT] log_dir = /var/log/keystone [application_credential] [assignment] [auth] [cache] [catalog] [cors] [credential] [database] connection = mysql+pymysql://keystone:password at OpenStack-Controller/keystone [domain_config] [endpoint_filter] [endpoint_policy] [eventlet_server] [extra_headers] [federation] [fernet_tokens] [healthcheck] [identity] [identity_mapping] [ldap] [matchmaker_redis] [memcache] [oauth1] [oslo_messaging_amqp] [oslo_messaging_kafka] [oslo_messaging_notifications] [oslo_messaging_rabbit] [oslo_messaging_zmq] [oslo_middleware] [oslo_policy] [paste_deploy] [policy] [profiler] [resource] [revoke] [role] [saml] [security_compliance] [shadow_users] [signing] [token] provider = fernet [tokenless_auth] [trust] [unified_limit] root at OpenStack-Controller:~# root at OpenStack-Controller:~# cat /var/log/keystone/keystone-manage.log 2018-06-30 16:44:24.543 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 10 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:44:34.555 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 9 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:44:44.558 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 8 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:44:54.571 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 7 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:45:04.577 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 6 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:45:14.584 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 5 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:45:24.596 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 4 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:45:34.609 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 3 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:45:44.621 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 2 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:45:54.634 5917 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 1 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:46:04.642 5917 CRITICAL keystone [-] Unhandled error: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] Connection refused)") 2018-06-30 16:46:04.642 5917 ERROR keystone Traceback (most recent call last): 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/bin/keystone-manage", line 10, in 2018-06-30 16:46:04.642 5917 ERROR keystone sys.exit(main()) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/cmd/manage.py", line 45, in main 2018-06-30 16:46:04.642 5917 ERROR keystone cli.main(argv=sys.argv, config_files=config_files) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py", line 1349, in main 2018-06-30 16:46:04.642 5917 ERROR keystone CONF.command.cmd_class.main() 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py", line 548, in main 2018-06-30 16:46:04.642 5917 ERROR keystone CONF.command.version) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/common/sql/upgrades.py", line 250, in offline_sync_database_to_version 2018-06-30 16:46:04.642 5917 ERROR keystone expand_schema() 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/common/sql/upgrades.py", line 323, in expand_schema 2018-06-30 16:46:04.642 5917 ERROR keystone _sync_common_repo(version=None) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/keystone/common/sql/upgrades.py", line 166, in _sync_common_repo 2018-06-30 16:46:04.642 5917 ERROR keystone with sql.session_for_write() as session: 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__ 2018-06-30 16:46:04.642 5917 ERROR keystone return self.gen.next() 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 1035, in _transaction_scope 2018-06-30 16:46:04.642 5917 ERROR keystone context=context) as resource: 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__ 2018-06-30 16:46:04.642 5917 ERROR keystone return self.gen.next() 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 638, in _session 2018-06-30 16:46:04.642 5917 ERROR keystone bind=self.connection, mode=self.mode) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 403, in _create_session 2018-06-30 16:46:04.642 5917 ERROR keystone self._start() 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 489, in _start 2018-06-30 16:46:04.642 5917 ERROR keystone engine_args, maker_args) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 513, in _setup_for_connection 2018-06-30 16:46:04.642 5917 ERROR keystone sql_connection=sql_connection, **engine_kwargs) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/debtcollector/renames.py", line 45, in wrapper 2018-06-30 16:46:04.642 5917 ERROR keystone return f(*args, **kwargs) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py", line 184, in create_engine 2018-06-30 16:46:04.642 5917 ERROR keystone test_conn = _test_connection(engine, max_retries, retry_interval) 2018-06-30 16:46:04.642 5917 ERROR keystone File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py", line 370, in _test_connection 2018-06-30 16:46:04.642 5917 ERROR keystone six.reraise(type(de_ref), de_ref) 2018-06-30 16:46:04.642 5917 ERROR keystone File "", line 3, in reraise -------------- next part -------------- An HTML attachment was scrubbed... URL: From berndbausch at gmail.com Sat Jun 30 10:59:00 2018 From: berndbausch at gmail.com (Bernd Bausch) Date: Sat, 30 Jun 2018 19:59:00 +0900 Subject: [Openstack] Keystone Error In-Reply-To: References: Message-ID: <8dce5603-a80f-296f-ca08-fdc39f4a9479@gmail.com> On 6/30/2018 5:15 PM, Kevin Kwon wrote: > "Can't connect to MySQL server on 'OpenStack-Controller' ([Errno 111] > Connection refused)") This error message means that no process is listening at the MySQL port on OpenStack-Controller. Initial thoughts: Either OpenStack-Controller is the wrong server, or MySQL is not running. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: