[openstack-dev] [cyborg] [weekly-meeting]

[Li Liu]

There is no weekly IRC meeting for the week of Nov 21st as most of the
people are still recovering from the jetlag after the summit.

I will follow up with individuals offline.

-- 
Thank you

Regards

Li
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] Feedback about our project at Summit

[Emilien Macchi]

Hi folks,

I wasn't at the Summit but I was interested by the feedback people gave
about TripleO so I've discussed with a few people who made the trip. I
would like to see what actions we can take on short and long term to
address it.
I collected some thoughts here:
https://etherpad.openstack.org/p/BER-tripleo-feedback
Which is based on
https://etherpad.openstack.org/p/BER-deployment-tools-feedback initially.

Feel fee to add more feedback if missing, and also comment what was
written. If you're aware of some WIP that address the feedback, adjust some
wording if needed or just put some links if something exists and is
documented already.
I believe it is critical to us to listen this feedback and include some of
it into our short term roadmap, so we can reduce some frustration that we
can hear sometimes.

Thanks for your help,
-- 
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [zun] Failed to create Container

[Rania Adouni]

Hi Hongbin ,
thanks for your advice I did fix it with changing the kuryr-lib to 0.6.0
and my service just work fine and also  with lsof -iTCP -sTCP:LISTEN -P

I can see it in the list  :
*kuryr-ser 16581 root5u  IPv4  91929  0t0  TCP
localhost:23750 (LISTEN)*  > that is great.

 + but I have two questions :
  1- How I can change the localhost to my compute address (
192.168.1.10:23750) because it is still the same error when trying to
create container " Docker internal error: 500 Server Error: Internal Server
Error ("legacy plugin: Post http://192.168.1.10:23750/Plugin.Activate: dial
tcp 192.168.1.10:23750: connect: connection refused"). ?

  2- my other question is about the log of zun why I can find it under
my directory /var/log  ?

Best Regards,
Rania Adouni


Le mer. 21 nov. 2018 à 02:34, Rania Adouni  a écrit :

> Hi Hongbin,
> Yes the version of kuryr-lib is :0.8.0 , So I think I should remove it !
> I should remove only the kuryr-lib ! if you have some command they can
> help me to unisntall it  , it will be nice to provide it .
>
> Best Regards,
> Rania
>
>
> Le mer. 21 nov. 2018 à 02:27, Hongbin Lu  a écrit :
>
>> Hi Rania,
>>
>> The config option 'driver' was recently renamed, so I guess the problem
>> is the version of kuryr-lib is not right. The Pike release of Zun is
>> matched to kuryr-lib 0.6.0 so you might want to confirm the version of
>> kuryr-lib.
>>
>> $ sudo pip freeze | grep kuryr
>>
>> If the version is not right, uninstall and re-install the kuryr-lib, then
>> restart kuryr-libnetwork. Let me know if it still doesn't work.
>>
>> Best regards,
>> Hongbin
>>
>> On Tue, Nov 20, 2018 at 8:01 PM Rania Adouni 
>> wrote:
>>
>>> hi ,
>>> Thanks for your reply and yes the problem that kuryr-libnetwork  is
>>> failed to start with the error :
>>> ● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin
>>> for Neutron
>>>Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service;
>>> enabled; vendor preset: enabled)
>>>Active: failed (Result: exit-code) since mer. 2018-11-21 01:48:48
>>> CET; 287ms ago
>>>   Process: 13974 ExecStart=/usr/local/bin/kuryr-server --config-file
>>> /etc/kuryr/kuryr.conf (code=exited, status=1/FAILURE)
>>>  Main PID: 13974 (code=exited, status=1/FAILURE)
>>>
>>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>>> 13974 ERROR kuryr value = self._do_get(name, group, namespace)
>>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>>> 13974 ERROR kuryr   File
>>> "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2942, in _
>>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>>> 13974 ERROR kuryr info = self._get_opt_info(name, group)
>>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>>> 13974 ERROR kuryr   File
>>> "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 3099, in _
>>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>>> 13974 ERROR kuryr raise NoSuchOptError(opt_name, group)
>>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>>> 13974 ERROR kuryr NoSuchOptError: no such option driver in group [binding]
>>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>>> 13974 ERROR kuryr
>>> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Main
>>> process exited, code=exited, status=1/FAILURE
>>> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Unit
>>> entered failed state.
>>> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Failed
>>> with result 'exit-code'.
>>>
>>>
>>> and also the command lsof -iTCP -sTCP:LISTEN -P doesn't show the kuryr
>>> service :
>>> COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>>> dockerd   1144 root5u  IPv4  20120  0t0  TCP
>>> compute:2375 (LISTEN)
>>> sshd  1288 root3u  IPv4  19532  0t0  TCP *:22
>>> (LISTEN)
>>> sshd  1288 root4u  IPv6  19534  0t0  TCP *:22
>>> (LISTEN)
>>> dnsmasq   1961   nobody6u  IPv4  23450  0t0  TCP
>>> 192.168.122.1:53 (LISTEN)
>>> sshd  4163   adouni9u  IPv6  34950  0t0  TCP
>>> localhost:6010 (LISTEN)
>>> sshd  4163   adouni   10u  IPv4  34951  0t0  TCP
>>> localhost:6010 (LISTEN)
>>> qemu-syst 4621 libvirt-qemu   18u  IPv4  37121  0t0  TCP *:5900
>>> (LISTEN)
>>>
>>> !!!
>>>
>>>
>>> Le mer. 21 nov. 2018 à 01:45, Jacob Burckhardt <
>>> jburckha...@pdvwireless.com> a écrit :
>>>
 Your error message says it cannot connect to port 23750.  That's the
 kuryr-libnetwork default listen port.  On 192.168.1.10, run:



 lsof -iTCP -sTCP:LISTEN -P



 On my compute node, it outputs:



 COMMANDPIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME

 …

 kuryr-ser 1976root6u  IPv4  30896  0t0  TCP
 localhost:23750 (LISTEN)
>>>

Re: [openstack-dev] [zun] Failed to create Container

[Rania Adouni]

Hi Hongbin,
Yes the version of kuryr-lib is :0.8.0 , So I think I should remove it !
I should remove only the kuryr-lib ! if you have some command they can help
me to unisntall it  , it will be nice to provide it .

Best Regards,
Rania


Le mer. 21 nov. 2018 à 02:27, Hongbin Lu  a écrit :

> Hi Rania,
>
> The config option 'driver' was recently renamed, so I guess the problem is
> the version of kuryr-lib is not right. The Pike release of Zun is matched
> to kuryr-lib 0.6.0 so you might want to confirm the version of kuryr-lib.
>
> $ sudo pip freeze | grep kuryr
>
> If the version is not right, uninstall and re-install the kuryr-lib, then
> restart kuryr-libnetwork. Let me know if it still doesn't work.
>
> Best regards,
> Hongbin
>
> On Tue, Nov 20, 2018 at 8:01 PM Rania Adouni 
> wrote:
>
>> hi ,
>> Thanks for your reply and yes the problem that kuryr-libnetwork  is
>> failed to start with the error :
>> ● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for
>> Neutron
>>Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled;
>> vendor preset: enabled)
>>Active: failed (Result: exit-code) since mer. 2018-11-21 01:48:48 CET;
>> 287ms ago
>>   Process: 13974 ExecStart=/usr/local/bin/kuryr-server --config-file
>> /etc/kuryr/kuryr.conf (code=exited, status=1/FAILURE)
>>  Main PID: 13974 (code=exited, status=1/FAILURE)
>>
>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>> 13974 ERROR kuryr value = self._do_get(name, group, namespace)
>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>> 13974 ERROR kuryr   File
>> "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2942, in _
>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>> 13974 ERROR kuryr info = self._get_opt_info(name, group)
>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>> 13974 ERROR kuryr   File
>> "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 3099, in _
>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>> 13974 ERROR kuryr raise NoSuchOptError(opt_name, group)
>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>> 13974 ERROR kuryr NoSuchOptError: no such option driver in group [binding]
>> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
>> 13974 ERROR kuryr
>> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Main
>> process exited, code=exited, status=1/FAILURE
>> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Unit
>> entered failed state.
>> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Failed
>> with result 'exit-code'.
>>
>>
>> and also the command lsof -iTCP -sTCP:LISTEN -P doesn't show the kuryr
>> service :
>> COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>> dockerd   1144 root5u  IPv4  20120  0t0  TCP compute:2375
>> (LISTEN)
>> sshd  1288 root3u  IPv4  19532  0t0  TCP *:22 (LISTEN)
>> sshd  1288 root4u  IPv6  19534  0t0  TCP *:22 (LISTEN)
>> dnsmasq   1961   nobody6u  IPv4  23450  0t0  TCP
>> 192.168.122.1:53 (LISTEN)
>> sshd  4163   adouni9u  IPv6  34950  0t0  TCP
>> localhost:6010 (LISTEN)
>> sshd  4163   adouni   10u  IPv4  34951  0t0  TCP
>> localhost:6010 (LISTEN)
>> qemu-syst 4621 libvirt-qemu   18u  IPv4  37121  0t0  TCP *:5900
>> (LISTEN)
>>
>> !!!
>>
>>
>> Le mer. 21 nov. 2018 à 01:45, Jacob Burckhardt <
>> jburckha...@pdvwireless.com> a écrit :
>>
>>> Your error message says it cannot connect to port 23750.  That's the
>>> kuryr-libnetwork default listen port.  On 192.168.1.10, run:
>>>
>>>
>>>
>>> lsof -iTCP -sTCP:LISTEN -P
>>>
>>>
>>>
>>> On my compute node, it outputs:
>>>
>>>
>>>
>>> COMMANDPIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>>>
>>> …
>>>
>>> kuryr-ser 1976root6u  IPv4  30896  0t0  TCP
>>> localhost:23750 (LISTEN)
>>>
>>>
>>>
>>> So, you can see that kuryr is listening on 23750.  If lsof does not list
>>> a process listening on 23750, then check if kuryr is up by running:
>>>
>>>
>>>
>>> systemctl status kuryr-libnetwork
>>>
>>>
>>>
>>> You can also try restarting it by running:
>>>
>>>
>>>
>>> systemctl restart kuryr-libnetwork
>>>
>>>
>>>
>>> I installed that service by following:
>>>
>>>
>>>
>>>
>>> https://docs.openstack.org/kuryr-libnetwork/queens/install/compute-install-ubuntu.html
>>>
>>>
>>>
>>> That is the queens install guide which might help you since zun has no
>>> install guide in pike.
>>>
>>>
>>>
>>> If you see it listening, you can try this command:
>>>
>>>
>>>
>>> telnet 192.168.1.10 23750
>>>
>>>
>>>
>>> If it fails to connect, then try:
>>>
>>>
>>>
>>> telnet localhost 23750
>>>
>>>
>>>
>>> If it works with localhost but not 192.168.1.10, then I think that means
>>> you need to tell docker to connect to localhost instead of 192.168.1.10.
>>>
>>>
>>>
>>> Can you get the 

Re: [openstack-dev] [zun] Failed to create Container

[Hongbin Lu]

Hi Rania,

The config option 'driver' was recently renamed, so I guess the problem is
the version of kuryr-lib is not right. The Pike release of Zun is matched
to kuryr-lib 0.6.0 so you might want to confirm the version of kuryr-lib.

$ sudo pip freeze | grep kuryr

If the version is not right, uninstall and re-install the kuryr-lib, then
restart kuryr-libnetwork. Let me know if it still doesn't work.

Best regards,
Hongbin

On Tue, Nov 20, 2018 at 8:01 PM Rania Adouni  wrote:

> hi ,
> Thanks for your reply and yes the problem that kuryr-libnetwork  is failed
> to start with the error :
> ● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for
> Neutron
>Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled;
> vendor preset: enabled)
>Active: failed (Result: exit-code) since mer. 2018-11-21 01:48:48 CET;
> 287ms ago
>   Process: 13974 ExecStart=/usr/local/bin/kuryr-server --config-file
> /etc/kuryr/kuryr.conf (code=exited, status=1/FAILURE)
>  Main PID: 13974 (code=exited, status=1/FAILURE)
>
> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
> 13974 ERROR kuryr value = self._do_get(name, group, namespace)
> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
> 13974 ERROR kuryr   File
> "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2942, in _
> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
> 13974 ERROR kuryr info = self._get_opt_info(name, group)
> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
> 13974 ERROR kuryr   File
> "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 3099, in _
> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
> 13974 ERROR kuryr raise NoSuchOptError(opt_name, group)
> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
> 13974 ERROR kuryr NoSuchOptError: no such option driver in group [binding]
> nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542
> 13974 ERROR kuryr
> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Main
> process exited, code=exited, status=1/FAILURE
> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Unit
> entered failed state.
> nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Failed with
> result 'exit-code'.
>
>
> and also the command lsof -iTCP -sTCP:LISTEN -P doesn't show the kuryr
> service :
> COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
> dockerd   1144 root5u  IPv4  20120  0t0  TCP compute:2375
> (LISTEN)
> sshd  1288 root3u  IPv4  19532  0t0  TCP *:22 (LISTEN)
> sshd  1288 root4u  IPv6  19534  0t0  TCP *:22 (LISTEN)
> dnsmasq   1961   nobody6u  IPv4  23450  0t0  TCP
> 192.168.122.1:53 (LISTEN)
> sshd  4163   adouni9u  IPv6  34950  0t0  TCP
> localhost:6010 (LISTEN)
> sshd  4163   adouni   10u  IPv4  34951  0t0  TCP
> localhost:6010 (LISTEN)
> qemu-syst 4621 libvirt-qemu   18u  IPv4  37121  0t0  TCP *:5900
> (LISTEN)
>
> !!!
>
>
> Le mer. 21 nov. 2018 à 01:45, Jacob Burckhardt <
> jburckha...@pdvwireless.com> a écrit :
>
>> Your error message says it cannot connect to port 23750.  That's the
>> kuryr-libnetwork default listen port.  On 192.168.1.10, run:
>>
>>
>>
>> lsof -iTCP -sTCP:LISTEN -P
>>
>>
>>
>> On my compute node, it outputs:
>>
>>
>>
>> COMMANDPIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>>
>> …
>>
>> kuryr-ser 1976root6u  IPv4  30896  0t0  TCP
>> localhost:23750 (LISTEN)
>>
>>
>>
>> So, you can see that kuryr is listening on 23750.  If lsof does not list
>> a process listening on 23750, then check if kuryr is up by running:
>>
>>
>>
>> systemctl status kuryr-libnetwork
>>
>>
>>
>> You can also try restarting it by running:
>>
>>
>>
>> systemctl restart kuryr-libnetwork
>>
>>
>>
>> I installed that service by following:
>>
>>
>>
>>
>> https://docs.openstack.org/kuryr-libnetwork/queens/install/compute-install-ubuntu.html
>>
>>
>>
>> That is the queens install guide which might help you since zun has no
>> install guide in pike.
>>
>>
>>
>> If you see it listening, you can try this command:
>>
>>
>>
>> telnet 192.168.1.10 23750
>>
>>
>>
>> If it fails to connect, then try:
>>
>>
>>
>> telnet localhost 23750
>>
>>
>>
>> If it works with localhost but not 192.168.1.10, then I think that means
>> you need to tell docker to connect to localhost instead of 192.168.1.10.
>>
>>
>>
>> Can you get the commands at the following web page to succeed?
>>
>>
>>
>> https://docs.openstack.org/kuryr-libnetwork/queens/install/verify.html
>>
>>
>>
>> *Jacob Burckhardt*
>>
>> Senior Software Engineer
>>
>> [image: pdvWireless]
>>
>>
>>
>> *From:* Rania Adouni 
>> *Sent:* Tuesday, November 20, 2018 2:02 PM
>> *To:* openstack-dev@lists.openstack.org
>> *Subject:* [openstack-dev] [zun] Failed to create Container
>>
>>
>>
>>
>>
>> Hi ,
>>
>>
>>
>> I am starting

Re: [openstack-dev] [zun] Failed to create Container

[Jacob Burckhardt]

The important part of the error message seems to be:

NoSuchOptError: no such option driver in group [binding]

In my /etc/kuryr/kuryr.conf file, all the text is commented out in the 
[binding] section.  Some of the commented options have "driver" in the name.  
Since they are commented, I guess they have defaults.  I suggest commenting any 
option that mentions "driver" and then restart kuryr-libnetwork.

-Jacob Burckhardt

From: Rania Adouni  
Sent: Tuesday, November 20, 2018 4:58 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [zun] Failed to create Container


hi , 
Thanks for your reply and yes the problem that kuryr-libnetwork  is failed to 
start with the error :
● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for 
Neutron
   Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since mer. 2018-11-21 01:48:48 CET; 287ms 
ago
  Process: 13974 ExecStart=/usr/local/bin/kuryr-server --config-file 
/etc/kuryr/kuryr.conf (code=exited, status=1/FAILURE)
 Main PID: 13974 (code=exited, status=1/FAILURE)

nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974 
ERROR kuryr     value = self._do_get(name, group, namespace)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974 
ERROR kuryr   File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 
2942, in _
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974 
ERROR kuryr     info = self._get_opt_info(name, group)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974 
ERROR kuryr   File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 
3099, in _
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974 
ERROR kuryr     raise NoSuchOptError(opt_name, group)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974 
ERROR kuryr NoSuchOptError: no such option driver in group [binding]
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974 
ERROR kuryr
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Main process 
exited, code=exited, status=1/FAILURE
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Unit entered 
failed state.
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Failed with 
result 'exit-code'.


and also the command lsof -iTCP -sTCP:LISTEN -P doesn't show the kuryr service :
COMMAND    PID         USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dockerd   1144         root    5u  IPv4  20120      0t0  TCP compute:2375 
(LISTEN)
sshd      1288         root    3u  IPv4  19532      0t0  TCP *:22 (LISTEN)
sshd      1288         root    4u  IPv6  19534      0t0  TCP *:22 (LISTEN)
dnsmasq   1961       nobody    6u  IPv4  23450      0t0  TCP 
http://192.168.122.1:53 (LISTEN)
sshd      4163       adouni    9u  IPv6  34950      0t0  TCP localhost:6010 
(LISTEN)
sshd      4163       adouni   10u  IPv4  34951      0t0  TCP localhost:6010 
(LISTEN)
qemu-syst 4621 libvirt-qemu   18u  IPv4  37121      0t0  TCP *:5900 (LISTEN)
 
!!!


Le mer. 21 nov. 2018 à 01:45, Jacob Burckhardt 
 a écrit :
Your error message says it cannot connect to port 23750.  That's the 
kuryr-libnetwork default listen port.  On 192.168.1.10, run:
 
lsof -iTCP -sTCP:LISTEN -P
 
On my compute node, it outputs:
 
COMMAND    PID    USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
…
kuryr-ser 1976    root    6u  IPv4  30896  0t0  TCP localhost:23750 
(LISTEN)
 
So, you can see that kuryr is listening on 23750.  If lsof does not list a 
process listening on 23750, then check if kuryr is up by running:
 
systemctl status kuryr-libnetwork
 
You can also try restarting it by running:
 
systemctl restart kuryr-libnetwork
 
I installed that service by following:
 
https://docs.openstack.org/kuryr-libnetwork/queens/install/compute-install-ubuntu.html
 
That is the queens install guide which might help you since zun has no install 
guide in pike.
 
If you see it listening, you can try this command:
 
telnet 192.168.1.10 23750
 
If it fails to connect, then try:
 
telnet localhost 23750
 
If it works with localhost but not 192.168.1.10, then I think that means you 
need to tell docker to connect to localhost instead of 192.168.1.10.
 
Can you get the commands at the following web page to succeed?
 
https://docs.openstack.org/kuryr-libnetwork/queens/install/verify.html
 
Jacob Burckhardt
Senior Software Engineer

 
From: Rania Adouni  
Sent: Tuesday, November 20, 2018 2:02 PM
To: mailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [zun] Failed to create Container
 

 
Hi ,
 
I am starting to use zun on openstack pike , and when I try to lunch container 
with cirros image , I get this reason : Docker internal error: 500 Server 
Error: Internal Server Error ("legacy plugin: Post 
http://192.168.1.10:23750

Re: [openstack-dev] [zun] Failed to create Container

[Rania Adouni]

hi ,
Thanks for your reply and yes the problem that kuryr-libnetwork  is failed
to start with the error :
● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for
Neutron
   Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled;
vendor preset: enabled)
   Active: failed (Result: exit-code) since mer. 2018-11-21 01:48:48 CET;
287ms ago
  Process: 13974 ExecStart=/usr/local/bin/kuryr-server --config-file
/etc/kuryr/kuryr.conf (code=exited, status=1/FAILURE)
 Main PID: 13974 (code=exited, status=1/FAILURE)

nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr value = self._do_get(name, group, namespace)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr   File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 2942, in _
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr info = self._get_opt_info(name, group)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr   File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 3099, in _
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr raise NoSuchOptError(opt_name, group)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr NoSuchOptError: no such option driver in group [binding]
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Main process
exited, code=exited, status=1/FAILURE
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Unit entered
failed state.
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Failed with
result 'exit-code'.


and also the command lsof -iTCP -sTCP:LISTEN -P doesn't show the kuryr
service :
COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dockerd   1144 root5u  IPv4  20120  0t0  TCP compute:2375
(LISTEN)
sshd  1288 root3u  IPv4  19532  0t0  TCP *:22 (LISTEN)
sshd  1288 root4u  IPv6  19534  0t0  TCP *:22 (LISTEN)
dnsmasq   1961   nobody6u  IPv4  23450  0t0  TCP
192.168.122.1:53 (LISTEN)
sshd  4163   adouni9u  IPv6  34950  0t0  TCP localhost:6010
(LISTEN)
sshd  4163   adouni   10u  IPv4  34951  0t0  TCP localhost:6010
(LISTEN)
qemu-syst 4621 libvirt-qemu   18u  IPv4  37121  0t0  TCP *:5900 (LISTEN)

!!!


Le mer. 21 nov. 2018 à 01:45, Jacob Burckhardt 
a écrit :

> Your error message says it cannot connect to port 23750.  That's the
> kuryr-libnetwork default listen port.  On 192.168.1.10, run:
>
>
>
> lsof -iTCP -sTCP:LISTEN -P
>
>
>
> On my compute node, it outputs:
>
>
>
> COMMANDPIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>
> …
>
> kuryr-ser 1976root6u  IPv4  30896  0t0  TCP
> localhost:23750 (LISTEN)
>
>
>
> So, you can see that kuryr is listening on 23750.  If lsof does not list a
> process listening on 23750, then check if kuryr is up by running:
>
>
>
> systemctl status kuryr-libnetwork
>
>
>
> You can also try restarting it by running:
>
>
>
> systemctl restart kuryr-libnetwork
>
>
>
> I installed that service by following:
>
>
>
>
> https://docs.openstack.org/kuryr-libnetwork/queens/install/compute-install-ubuntu.html
>
>
>
> That is the queens install guide which might help you since zun has no
> install guide in pike.
>
>
>
> If you see it listening, you can try this command:
>
>
>
> telnet 192.168.1.10 23750
>
>
>
> If it fails to connect, then try:
>
>
>
> telnet localhost 23750
>
>
>
> If it works with localhost but not 192.168.1.10, then I think that means
> you need to tell docker to connect to localhost instead of 192.168.1.10.
>
>
>
> Can you get the commands at the following web page to succeed?
>
>
>
> https://docs.openstack.org/kuryr-libnetwork/queens/install/verify.html
>
>
>
> *Jacob Burckhardt*
>
> Senior Software Engineer
>
> [image: pdvWireless]
>
>
>
> *From:* Rania Adouni 
> *Sent:* Tuesday, November 20, 2018 2:02 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [zun] Failed to create Container
>
>
>
>
>
> Hi ,
>
>
>
> I am starting to use zun on openstack pike , and when I try to lunch
> container with cirros image , I get this reason : Docker internal error:
> 500 Server Error: Internal Server Error ("legacy plugin: Post
> http://192.168.1.10:23750/Plugin.Activate: dial tcp 192.168.1.10:23750:
> connect: connection refused").
>
> you can find here the log on my compute node :
> https://pastebin.com/nZTiTZiV.
>
> some help with this will be great .
>
> Best Regards,
>
> Rania Adouni
>
>
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-b

Re: [openstack-dev] [zun] Failed to create Container

[Jacob Burckhardt]

Your error message says it cannot connect to port 23750.  That's the 
kuryr-libnetwork default listen port.  On 192.168.1.10, run:

lsof -iTCP -sTCP:LISTEN -P

On my compute node, it outputs:

COMMANDPIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME
…
kuryr-ser 1976root6u  IPv4  30896  0t0  TCP localhost:23750 
(LISTEN)

So, you can see that kuryr is listening on 23750.  If lsof does not list a 
process listening on 23750, then check if kuryr is up by running:

systemctl status kuryr-libnetwork

You can also try restarting it by running:

systemctl restart kuryr-libnetwork

I installed that service by following:

https://docs.openstack.org/kuryr-libnetwork/queens/install/compute-install-ubuntu.html

That is the queens install guide which might help you since zun has no install 
guide in pike.

If you see it listening, you can try this command:

telnet 192.168.1.10 23750

If it fails to connect, then try:

telnet localhost 23750

If it works with localhost but not 192.168.1.10, then I think that means you 
need to tell docker to connect to localhost instead of 192.168.1.10.

Can you get the commands at the following web page to succeed?

https://docs.openstack.org/kuryr-libnetwork/queens/install/verify.html

Jacob Burckhardt
Senior Software Engineer
[pdvWireless]

From: Rania Adouni 
Sent: Tuesday, November 20, 2018 2:02 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [zun] Failed to create Container

[https://mailtrack.io/trace/mail/17bd40a2e38fcf449f8e80fdc1e7d9474dfbed19.png?u=2497697]

Hi ,

I am starting to use zun on openstack pike , and when I try to lunch container 
with cirros image , I get this reason : Docker internal error: 500 Server 
Error: Internal Server Error ("legacy plugin: Post 
http://192.168.1.10:23750/Plugin.Activate: dial tcp 
192.168.1.10:23750: connect: connection refused").
you can find here the log on my compute node :https://pastebin.com/nZTiTZiV.
some help with this will be great .
Best Regards,
Rania Adouni




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] about filter the flavor

[Matt Riedemann]

On 11/19/2018 9:32 PM, Rambo wrote:
       I have an idea.Now we can't filter the special flavor according 
to the property.Can we achieve it?If we achieved this,we can filter the 
flavor according the property's key and value to filter the flavor. What 
do you think of the idea?Can you tell me more about this ?Thank you very 
much.


To be clear, you want to filter flavors by extra spec key and/or value? 
So something like:


GET /flavors?key=hw%3Acpu_policy

would return all flavors with an extra spec with key "hw:cpu_policy".

And:

GET /flavors?key=hw%3Acpu_policy&value=dedicated

would return all flavors with extra spec "hw:cpu_policy" with value 
"dedicated".


The query parameter semantics are probably what gets messiest about 
this. Because I could see wanting to couple the key and value together, 
but I'm not sure how you do that, because I don't think you can do this:


GET /flavors?spec=hw%3Acpu_policy=dedicated

Maybe you'd do:

GET /flavors?hw%3Acpu_policy=dedicated

The problem with that is we wouldn't be able to perform any kind of 
request schema validation of it, especially since flavor extra specs are 
not standardized.


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [zun] Failed to create Container

[Rania Adouni]

Hi ,

I am starting to use zun on openstack pike , and when I try to lunch
container with cirros image , I get this reason : Docker internal error:
500 Server Error: Internal Server Error ("legacy plugin: Post
http://192.168.1.10:23750/Plugin.Activate: dial tcp 192.168.1.10:23750:
connect: connection refused").
you can find here the log on my compute node :https://pastebin.com/nZTiTZiV.
some help with this will be great .
Best Regards,
Rania Adouni
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Senlin] Does Senlin support Prometheus？

[Duc Truong]

Senlin integrates with Aodh using webhooks.  As shown in [1], you
create a receiver of type webhook and then create a Aodh alarm to call
this webhook [2] on the desired condition.
Prometheus AlertManager supports notifications to webhooks [3].  While
I have not tried this myself, I believe that it should be as simple as
setting up Prometheus AlertManager to notify the webhook created in
Senlin (see [1]).

Regards,

Duc (dtruong)

[1] 
https://docs.openstack.org/senlin/latest/scenarios/autoscaling_ceilometer.html#step-2-create-receivers
[2] 
https://docs.openstack.org/senlin/latest/scenarios/autoscaling_ceilometer.html#step-3-creating-aodh-alarms
[3] https://prometheus.io/docs/alerting/configuration/#webhook_config
On Mon, Nov 19, 2018 at 6:33 PM xuc...@chinacloud.com.cn
 wrote:
>
> Hi，
>
> Senlin, Ceilometer/Aodh is currently integrated, does it support Prometheus ？
>
>
> thanks
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Stein forum session notes

[melanie witt]

On Mon, 19 Nov 2018 17:19:22 +0100, Surya Seetharaman wrote:



On Mon, Nov 19, 2018 at 2:39 PM Matt Riedemann > wrote:


On 11/19/2018 3:17 AM, melanie witt wrote:
 > - Not directly related to the session, but CERN (hallway track) and
 > NeCTAR (dev ML) have both given feedback and asked that the
 > policy-driven idea for handling quota for down cells be avoided.
Revived
 > the "propose counting quota in placement" spec to see if there's
any way
 > forward here

Should this be abandoned then?

https://review.openstack.org/#/c/614783/

Since there is no microversion impact to that change, it could be added
separately as a bug fix for the down cell case if other operators want
that functionality. But maybe we don't know what other operators want
since no one else is at multi-cell cells v2 yet.


I thought the policy check was needed until the "propose counting quota 
in placement"
has been implemented as a workaround and that is what the "handling down 
cell" spec also proposed,
unless the former spec would be implemented within this cycle in which 
case we do not need the

policy check.


Right, I don't think that anyone _wants_ the policy check approach. That 
was just the workaround, last resort idea we had for dealing with down 
cells in the absence of being able to count quota usage from placement.


The operators we've discussed with (CERN, NeCTAR, Oath) would like quota 
counting not to depend on cell databases, if possible. But they are 
understanding and will accept the policy-driven workaround if we can't 
move forward with counting quota usage from placement.


If we can get agreement on the count quota usage from placement spec (I 
have updated it with new proposed details), then we should abandon the 
policy-driven behavior patch. I am eager to find out what everyone 
thinks of the latest proposal.


Cheers,
-melanie

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [omni] Has the Platform9's hybrid multicloud project been abandoned?

[Steven Hardy]

On Tue, Nov 20, 2018 at 6:13 AM Blake Covarrubias  wrote:
>
> Hi Andrea,
>
> Omni has not been abandoned by Platform9. We're still developing Omni 
> internally, and are working to open source additional code as well as improve 
> docs so that others may more easily test & contribute.

It sounds like you're approaching this using an internal design
process, so you may like to check:

https://governance.openstack.org/tc/reference/opens.html

The most recent commit was over a year ago, so it's understandably
confusing to have an apparently unmaintained project, hosted under the
openstack github org, which doesn't actually follow our comunity
design/development process?

> With that said, I too would be interested in hearing how others are enabling, 
> or looking to enable, hybrid cloud use cases with OpenStack. I'm not aware of 
> any other projects with similar goals as Omni, however its possible I just 
> haven't been looking in the right places.

Having design discussions in the open, and some way for others in the
community to understand the goals and roadmap of the project is really
the first step in engaging folks for this sort of discussion IME.

Steve

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev