Python3 proposal: stabilized Fedora repositories for OpenStack
by Haïkel
Hi,
Following our discussions during today's RDO meeting about a draft to
start working on
python3 support in RDO, I expand the discussion to the wider group.
Please keep the discussion on the dev list, users list is only there
to raise awareness.
Since it's a huge topic, I started an etherpad to collect our
thoughts. It is on upstream etherpad
in order to collaborate with upstream as we hope this would be useful
for upstream gating.
Please read the etherpad for details and provide your feedback.
https://etherpad.openstack.org/p/stabilized-fedora-repositories-for-opens...
The main idea is to use stabilized Fedora repositories, it is a lot of
work and we intend to start
working that during the Rocky cycle. This will allow us to work on
migrating our packaging on python3
and support modularity which will ship with EL8 (currently a Fedora
only feature).
There's a lot of work but we aim to be ready on time to migrate to
Python3 when EL8 will be released.
This is not about supporting python3 for end-users, until EL8 gets
released, this is only intended
for our downstream and upstream CI pipelines.
Regards,
H.
6 years, 9 months
Re: [rdo-dev] Long queue in RDO SF
by David Manchado Cuesta
FWIW no alerts during the weekend and I have been able to spawn 10+
instances without issue.
Cheers
David Manchado
Senior Software Engineer - SysOps Team
Red Hat
dmanchad(a)redhat.com
On 11 February 2018 at 16:39, Paul Belanger <pabelanger(a)redhat.com> wrote:
> On Sun, Feb 11, 2018 at 12:44:52PM +0100, Haïkel Guémar wrote:
>> On 02/11/2018 12:17 AM, Sagi Shnaidman wrote:
>> > Hi,
>> >
>> > I see openstack-check has 53 hours queue when 1 job only is queued:
>> > https://review.rdoproject.org/zuul/
>> >
>> > Seems like problem with nodepool?
>> >
>> > Thanks
>> >
>> > --
>> > Best regards
>> > Sagi Shnaidman
>> >
>> >
>> > _______________________________________________
>> > dev mailing list
>> > dev(a)lists.rdoproject.org
>> > http://lists.rdoproject.org/mailman/listinfo/dev
>> >
>> > To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
>> >
>>
>> Ok, it looks bad enough that a simple nodepool list fails with that error:
>> os_client_config.exceptions.OpenStackConfigException: Cloud rdo-cloud was
>> not found.
>>
>> Despite RDO Cloud looks up, there might be an outage or incident hence
>> copying David Manchado.
>>
>> Regards,
>> H.
>>
> Okay, I have to run, but this looks like a configuration issue. It is hard to
> tell without debug logs for nodepool or zuul, but please double check your node
> is setup properly.
>
> I have to run now.
>
6 years, 9 months
Test day readiness
by Rich Bowen
We've moved the test day to this Thursday and Friday -
http://rdoproject.org/testday/queens/milestone3/ - but we're still
waiting for a promotion - https://dashboards.rdoproject.org/rdo-dev
Do we want to cancel this one, and wait for the GA, or is there a decent
chance that we'll have a promotion in time to set up the test cloud?
Mostly, I'm wondering if I should go ahead with the planned promotion of
the test day, or just remain quiet.
--Rich
--
Rich Bowen - rbowen(a)redhat.com
@RDOcommunity // @CentOSProject // @rbowen
6 years, 9 months
Re: [rdo-dev] [rdo-users] Quickstart and containers (2)
by Boris Derzhavets
Attempting via F27 connection to VIRTHOST (32 GB) with 770 MB is Swap
4 Node HA case. Sitill fails with control_memory=7700
ep4.0]: SIGNAL_IN_PROGRESS Signal: deployment f7493897-9e88-464c-bb78-71c2c5fa164f succeeded
2018-02-12 07:47:10 | 2018-02-12 07:46:45Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED Resource CREATE failed: Error: resources.ControllerDeployment_Step4.resources[2]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
2018-02-12 07:47:10 | 2018-02-12 07:46:46Z [overcloud.AllNodesDeploySteps.ControllerDeployment_Step4.0]: CREATE_COMPLETE state changed
2018-02-12 07:47:10 | 2018-02-12 07:46:46Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED Error: resources.AllNodesDeploySteps.resources.ControllerDeployment_Step4.resources[2]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
2018-02-12 07:47:10 | 2018-02-12 07:46:47Z [overcloud]: CREATE_FAILED Resource CREATE failed: Error: resources.AllNodesDeploySteps.resources.ControllerDeployment_Step4.resources[2]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
2018-02-12 07:47:10 | 2018-02-12 07:46:51Z [overcloud.AllNodesDeploySteps.ControllerDeployment_Step4.1]: SIGNAL_IN_PROGRESS Signal: deployment 51c7e7c9-ae7b-41e8-ba62-6767c9730986 failed (2)
2018-02-12 07:47:10 |
2018-02-12 07:47:10 | Stack overcloud CREATE_FAILED
2018-02-12 07:47:10 |
2018-02-12 07:47:10 | overcloud.AllNodesDeploySteps.ControllerDeployment_Step4.1:
2018-02-12 07:47:10 | resource_type: OS::Heat::StructuredDeployment
2018-02-12 07:47:10 | physical_resource_id: 51c7e7c9-ae7b-41e8-ba62-6767c9730986
2018-02-12 07:47:10 | status: CREATE_FAILED
2018-02-12 07:47:10 | status_reason: |
2018-02-12 07:47:10 | Error: resources[1]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
2018-02-12 07:47:10 | deploy_stdout: |
2018-02-12 07:47:10 | ...
2018-02-12 07:47:10 | "a2b168fb9a3d: Pull complete",
2018-02-12 07:47:10 | "5e1193f920e0: Pull complete",
2018-02-12 07:47:10 | "Digest: sha256:36ca9874c8359103a574ee7311688cdbefa61bec6a8fa5b728add93dc614d7c8"
2018-02-12 07:47:10 | ]
2018-02-12 07:47:10 | }
2018-02-12 07:47:10 | to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/fa4dfb68-f59a-420d-88f9-1d12528284a3_playbook.retry
2018-02-12 07:47:10 |
2018-02-12 07:47:10 | PLAY RECAP *********************************************************************
2018-02-12 07:47:11 | Heat Stack create failed.
2018-02-12 07:47:11 | Heat Stack create failed.
2018-02-12 07:47:11 | localhost : ok=6 changed=2 unreachable=0 failed=1
2018-02-12 07:47:11 |
2018-02-12 07:47:11 | (truncated, view all with --long)
2018-02-12 07:47:11 | deploy_stderr: |
2018-02-12 07:47:11 |
2018-02-12 07:47:11 | overcloud.AllNodesDeploySteps.ControllerDeployment_Step4.2:
2018-02-12 07:47:11 | resource_type: OS::Heat::StructuredDeployment
2018-02-12 07:47:11 | physical_resource_id: 16874306-3619-46ab-be0d-c0b91ee790fe
2018-02-12 07:47:11 | status: CREATE_FAILED
2018-02-12 07:47:11 | status_reason: |
2018-02-12 07:47:11 | Error: resources[2]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
2018-02-12 07:47:11 | deploy_stdout: |
2018-02-12 07:47:11 | ...
2018-02-12 07:47:11 | "a2b168fb9a3d: Pull complete",
2018-02-12 07:47:11 | "5e1193f920e0: Pull complete",
2018-02-12 07:47:11 | "Digest: sha256:36ca9874c8359103a574ee7311688cdbefa61bec6a8fa5b728add93dc614d7c8"
2018-02-12 07:47:11 | ]
2018-02-12 07:47:11 | }
2018-02-12 07:47:11 | to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/7be0326a-ff52-4745-918c-f1279eb546f9_playbook.retry
2018-02-12 07:47:11 |
2018-02-12 07:47:11 | PLAY RECAP *********************************************************************
2018-02-12 07:47:11 | localhost : ok=6 changed=2 unreachable=0 failed=1
2018-02-12 07:47:11 |
2018-02-12 07:47:11 | (truncated, view all with --long)
2018-02-12 07:47:11 | deploy_stderr: |
2018-02-12 07:47:11 |
2018-02-12 07:47:11 | + status_code=1
2018-02-12 07:47:11 | + openstack stack list
2018-02-12 07:47:11 | + grep -q overcloud
2018-02-12 07:47:21 | + grep -Eq '(CREATE|UPDATE)_COMPLETE'
2018-02-12 07:47:21 | + openstack stack list
2018-02-12 07:47:24 | + openstack stack failures list overcloud --long
2018-02-12 07:47:30 | ++ grep FAILED
2018-02-12 07:47:30 | ++ grep 'StructuredDeployment '
2018-02-12 07:47:30 | ++ cut -d '|' -f3
2018-02-12 07:47:30 | ++ openstack stack resource list --nested-depth 5 overcloud
2018-02-12 07:47:58 | + for failed in '$(openstack stack resource list --nested-depth 5 overcloud | grep FAILED |
2018-02-12 07:47:58 | grep '\''StructuredDeployment '\'' | cut -d '\''|'\'' -f3)'
2018-02-12 07:47:58 | + echo 'heat deployment-show output for deployment: 51c7e7c9-ae7b-41e8-ba62-6767c9730986'
2018-02-12 07:47:58 | + echo '######################################################'
2018-02-12 07:47:58 | + heat deployment-show 51c7e7c9-ae7b-41e8-ba62-6767c9730986
2018-02-12 07:47:59 | WARNING (shell) "heat deployment-show" is deprecated, please use "openstack software deployment show" instead
2018-02-12 07:48:00 | + echo '######################################################'
2018-02-12 07:48:00 | + echo 'puppet standard error for deployment: 51c7e7c9-ae7b-41e8-ba62-6767c9730986'
2018-02-12 07:48:00 | + echo '######################################################'
2018-02-12 07:48:00 | + heat deployment-show 51c7e7c9-ae7b-41e8-ba62-6767c9730986
2018-02-12 07:48:00 | + jq -r .output_values.deploy_stderr
2018-02-12 07:48:00 | + sed -r 's:\x1B\[[0-9;]*[mK]::g'
2018-02-12 07:48:01 | WARNING (shell) "heat deployment-show" is deprecated, please use "openstack software deployment show" instead
2018-02-12 07:48:01 | + echo '######################################################'
2018-02-12 07:48:01 | + for failed in '$(openstack stack resource list --nested-depth 5 overcloud | grep FAILED |
2018-02-12 07:48:01 | grep '\''StructuredDeployment '\'' | cut -d '\''|'\'' -f3)'
2018-02-12 07:48:01 | + echo 'heat deployment-show output for deployment: 16874306-3619-46ab-be0d-c0b91ee790fe'
2018-02-12 07:48:01 | + echo '######################################################'
2018-02-12 07:48:01 | + heat deployment-show 16874306-3619-46ab-be0d-c0b91ee790fe
2018-02-12 07:48:02 | WARNING (shell) "heat deployment-show" is deprecated, please use "openstack software deployment show" instead
2018-02-12 07:48:03 | + echo '######################################################'
2018-02-12 07:48:03 | + echo 'puppet standard error for deployment: 16874306-3619-46ab-be0d-c0b91ee790fe'
2018-02-12 07:48:03 | + echo '######################################################'
2018-02-12 07:48:03 | + jq -r .output_values.deploy_stderr
2018-02-12 07:48:03 | + sed -r 's:\x1B\[[0-9;]*[mK]::g'
2018-02-12 07:48:03 | + heat deployment-show 16874306-3619-46ab-be0d-c0b91ee790fe
2018-02-12 07:48:03 | WARNING (shell) "heat deployment-show" is deprecated, please use "openstack software deployment show" instead
2018-02-12 07:48:04 | + echo '######################################################'
2018-02-12 07:48:04 | + exit 1
________________________________
From: users <users-bounces(a)lists.rdoproject.org> on behalf of Boris <dba477(a)list.ru>
Sent: Friday, February 9, 2018 9:03 PM
To: James LaBarre
Cc: users(a)lists.rdoproject.org
Subject: Re: [rdo-users] Quickstart and containers
Пятница, 9 февраля 2018, 19:17 +03:00 от James LaBarre <jlabarre(a)redhat.com>:
If I am trying to familiarize myself with the newer containerized
overcloud (Queens & upwards), is there a way to build a TripleO
Quickstart on a single node?
Due to I cannot any longer respond from hotmail.com ( backup address is used )
1. https://www.anstack.com/blog/2018/01/05/tripleo-quickstart-cheatsheet.html
2. this one was done via F27 connection to VIRTHOST
http://lxer.com/module/newswire/view/252059/index.html
I believe it might work in the way suggested by Carlos Camacho (1)
Boris.
As I say, it's mainly to get some
experience in the newer configurations, after which I could probably
grab some more baremetal and do proper setups.
I do find myself wondering, though, with the way Quickstart worked with
images, if it's been doing containers all along...
_______________________________________________
users mailing list
users(a)lists.rdoproject.org<mailto:users@lists.rdoproject.org>
http://lists.rdoproject.org/mailman/listinfo/users
To unsubscribe: users-unsubscribe(a)lists.rdoproject.org<mailto:users-unsubscribe@lists.rdoproject.org>
С уважением,
Boris Derzhavets
dba477(a)list.ru
6 years, 9 months
Re: [rdo-dev] [rdo-users] Quickstart and containers
by Boris Derzhavets
Mentioned bellow my deployment (4 Node HA) via F27 WKS, which worked fine twice on 02/06 and 02/09 now fails with message in log :
2018-02-11 10:19:50 | 2018-02-11 10:19:27Z [overcloud]: CREATE_FAILED Resource CREATE failed: Error: resources.AllNodesDeploySteps.resources.ControllerDeployment_Step1.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
2018-02-11 10:19:50 |
2018-02-11 10:19:50 | Stack overcloud CREATE_FAILED
2018-02-11 10:19:50 |
2018-02-11 10:19:50 | overcloud.AllNodesDeploySteps.ControllerDeployment_Step1.0:
2018-02-11 10:19:50 | resource_type: OS::Heat::StructuredDeployment
2018-02-11 10:19:50 | physical_resource_id: a9db44c8-39f7-4bc6-80b8-534b2c402b48
2018-02-11 10:19:50 | status: CREATE_FAILED
2018-02-11 10:19:50 | status_reason: |
2018-02-11 10:19:50 | Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
2018-02-11 10:19:50 | deploy_stdout: |
2018-02-11 10:19:50 | ...
2018-02-11 10:19:50 | "2018-02-11 10:19:11,526 INFO: 22569 -- Removing container: docker-puppet-heat_api_cfn",
2018-02-11 10:19:50 | "2018-02-11 10:19:11,558 INFO: 22569 -- Finished processing puppet configs for heat_api_cfn",
2018-02-11 10:19:50 | "2018-02-11 10:19:11,559 ERROR: 22567 -- ERROR configuring swift_ringbuilder"
2018-02-11 10:19:50 | ]
2018-02-11 10:19:50 | }
2018-02-11 10:19:50 | to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/a25a263b-579b-4954-bf09-25bda1c4f1c3_playbook.retry
2018-02-11 10:19:50 |
2018-02-11 10:19:50 | PLAY RECAP *********************************************************************
2018-02-11 10:19:50 | localhost : ok=6 changed=2 unreachable=0 failed=1
2018-02-11 10:19:50 |
2018-02-11 10:19:50 | (truncated, view all with --long)
2018-02-11 10:19:50 | deploy_stderr: |
2018-02-11 10:19:50 |
2018-02-11 10:19:51 | + status_code=1
2018-02-11 10:19:51 | + openstack stack list
2018-02-11 10:19:51 | + grep -q overcloud
2018-02-11 10:20:20 | + openstack stack list
2018-02-11 10:20:20 | + grep -Eq '(CREATE|UPDATE)_COMPLETE'
Thanks
Boris
________________________________
From: users <users-bounces(a)lists.rdoproject.org> on behalf of Boris <dba477(a)list.ru>
Sent: Friday, February 9, 2018 9:03 PM
To: James LaBarre
Cc: users(a)lists.rdoproject.org
Subject: Re: [rdo-users] Quickstart and containers
Пятница, 9 февраля 2018, 19:17 +03:00 от James LaBarre <jlabarre(a)redhat.com>:
If I am trying to familiarize myself with the newer containerized
overcloud (Queens & upwards), is there a way to build a TripleO
Quickstart on a single node?
Due to I cannot any longer respond from hotmail.com ( backup address is used )
1. https://www.anstack.com/blog/2018/01/05/tripleo-quickstart-cheatsheet.html
2. this one was done via F27 connection to VIRTHOST
http://lxer.com/module/newswire/view/252059/index.html
I believe it might work in the way suggested by Carlos Camacho (1)
Boris.
As I say, it's mainly to get some
experience in the newer configurations, after which I could probably
grab some more baremetal and do proper setups.
I do find myself wondering, though, with the way Quickstart worked with
images, if it's been doing containers all along...
_______________________________________________
users mailing list
users(a)lists.rdoproject.org<mailto:users@lists.rdoproject.org>
http://lists.rdoproject.org/mailman/listinfo/users
To unsubscribe: users-unsubscribe(a)lists.rdoproject.org<mailto:users-unsubscribe@lists.rdoproject.org>
С уважением,
Boris Derzhavets
dba477(a)list.ru
6 years, 9 months
