On Fri, 2019-11-08 at 13:13 +0000, Chen, Haochuan Z wrote:
Hi Kris
Before you run this command, are you sure "system mode: simplex" in localhost.yml $ ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml
The localhost.yaml indeed does contain system_mode: simplex The platform.conf however not , so I updated that .. After the chnage it seemed to ingnore that change .. the command still has the same error There also is an empty file in /etc/platform called simplex I regtriggered the ansible run to be sure .. and even during that run with the config i noticed TASK [bringup-essential-services : Save the current system and network config for reference in subsequent replays] *** changed: [localhost] => (item=prev_system_mode: duplex) changed: [localhost] => (item=prev_timezone: UTC) So somewhere it looks like it is taking in the wrong parameter .. I`ll dig deeper .. but if you have any hints on where to search ? greetings Kris
You can check this in your system $ cat /etc/platform/platform.conf
BR!
Martin, Chen SSP, Software Engineer 021-61164330
-----Original Message----- From: starlingx-discuss-request@lists.starlingx.io <starlingx-discuss-request@lists.starlingx.io> Sent: Friday, November 8, 2019 8:30 PM To: starlingx-discuss@lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 70
Send Starlingx-discuss mailing list submissions to starlingx-discuss@lists.starlingx.io
To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request@lists.starlingx.io
You can reach the person managing the list at starlingx-discuss-owner@lists.starlingx.io
When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..."
Today's Topics:
1. Re: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. (Liu, ZhipengS) 2. [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. (张鲲鹏) 3. StarlingX platform-integ-apps docker images (cristopher.j.lemus.contreras@intel.com) 4. Calsoft's Contribution StarlingX all-in-one Simplex EdgeX with Openstack (Saichandu Behara) 5. Failing to add an OSD on controller-0 for ceph (Kris Buytaert)
----------------------------------------------------------------------
Message: 1 Date: Fri, 8 Nov 2019 01:55:15 +0000 From: "Liu, ZhipengS" <zhipengs.liu@intel.com> To: "Hu, Yong" <yong.hu@intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>, "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com>, "Lemus Contreras, Cristopher J" <cristopher.j.lemus.contreras@intel.com> Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Message-ID: <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass!
Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root
Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J < cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches.
Hi Core reviewers in Stx.distro.openstack:
The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher).
So to unblock stx.3.0 MS-3, please review the following patches in time:
https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/
In addition, some background info related to this upgrade:
1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header.
2). these patches have to be merged *in one batch* due to the inter-dependencies.
3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*.
------------------------------
Message: 2 Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) From: 张鲲鹏 <zhang.kunpeng@99cloud.net> To: tao.liu@windriver.com Cc: starlingx-discuss <starlingx-discuss@lists.starlingx.io>, "greg.waines" <greg.waines@windriver.com> Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Message-ID: <ALMAzQDsCJQdsOiV*wPHQapB.1.1573187689506.Hmail.zhang.kunpeng@99cloud.net>
Content-Type: text/plain; charset="utf-8"
Hi Tao, Distributed Cloud team,
The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1].
As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography.
Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it?
1. https://bugs.launchpad.net/starlingx/+bug/1846799
Thanks Kunpeng