Open Stack

Hello Sean, if you do not want to spend you time for configuring a test
openstack environment I am available for schedule a call where I can share
my desktop and we could test on rocky and stein .
Let me know if you can.
Best Regards
Ignazio

Il giorno sab 2 mag 2020 alle ore 17:40 Ignazio Cassano <
ignaziocassano at gmail.com> ha scritto:

> Hello Sean, I am continuing my test (so you we'll have to read a lot :-) )
> If I understood well file neutron.py contains a patch for
> /usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py for reading
> the configuration force_legacy_port_binding.
> If it is true it returns false.
> I patched the api.py and inserting a LOG.info call I saw  it reads the
> variable but it seems do nothing and the migrate instance stop to respond.
> Best Regards
> Ignazio
>
>
>
> Il giorno sab 2 mag 2020 alle ore 10:43 Ignazio Cassano <
> ignaziocassano at gmail.com> ha scritto:
>
>> Hello Sean,
>> I modified the no workloads.py to add the consoleauth code, so now it
>> does note returns errors during live migration phase, as I wrote in my last
>> email.
>> Keep in mind my stein is from an upgrade.
>> Sorry if I am not sending all email history here, but if message body is
>> too big the email needs the moderator approval.
>> Anycase, I added the following code:
>>
>>     cfg.BoolOpt(
>>         'enable_consoleauth',
>>         default=False,
>>         deprecated_for_removal=True,
>>         deprecated_since="18.0.0",
>>         deprecated_reason="""
>> This option has been added as deprecated originally because it is used
>> for avoiding a upgrade issue and it will not be used in the future.
>> See the help text for more details.
>> """,
>>         help="""
>> Enable the consoleauth service to avoid resetting unexpired consoles.
>>
>> Console token authorizations have moved from the ``nova-consoleauth``
>> service
>> to the database, so all new consoles will be supported by the database
>> backend.
>> With this, consoles that existed before database backend support will be
>> reset.
>> For most operators, this should be a minimal disruption as the default
>> TTL of a
>> console token is 10 minutes.
>>
>> Operators that have much longer token TTL configured or otherwise wish to
>> avoid
>> immediately resetting all existing consoles can enable this flag to
>> continue
>> using the ``nova-consoleauth`` service in addition to the database
>> backend.
>> Once all of the old ``nova-consoleauth`` supported console tokens have
>> expired,
>> this flag should be disabled. For example, if a deployment has configured
>> a
>> token TTL of one hour, the operator may disable the flag, one hour after
>> deploying the new code during an upgrade.
>>
>> .. note:: Cells v1 was not converted to use the database backend for
>>   console token authorizations. Cells v1 console token authorizations will
>>   continue to be supported by the ``nova-consoleauth`` service and use of
>>   the ``[workarounds]/enable_consoleauth`` option does not apply to
>>   Cells v1 users.
>>
>> Related options:
>>
>> * ``[consoleauth]/token_ttl``
>> """),
>>
>> Now the live migration starts e the instance is moved  but the it
>> continues to be unreachable after live migration.
>> It starts to respond only when it starts a connection (for example a
>> polling to ntp server).
>> If I disable chrony in the instance, it stop to respond for ever.
>> Best Regards
>> Ignazio
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200505/c41ce3cd/attachment.html>