[Starlingx-discuss] Failing to add an OSD on controller-0 for ceph

Fri Nov 8 13:13:00 UTC 2019

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

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 at lists.starlingx.io <starlingx-discuss-request at lists.starlingx.io> 
Sent: Friday, November 8, 2019 8:30 PM
To: starlingx-discuss at lists.starlingx.io
Subject: Starlingx-discuss Digest, Vol 18, Issue 70

Send Starlingx-discuss mailing list submissions to
	starlingx-discuss at 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 at lists.starlingx.io

You can reach the person managing the list at
	starlingx-discuss-owner at 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 at 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 at intel.com>
To: "Hu, Yong" <yong.hu at intel.com>,
	"starlingx-discuss at lists.starlingx.io"
	<starlingx-discuss at lists.starlingx.io>, "Alonso, Juan Carlos"
	<juan.carlos.alonso at intel.com>, "Lemus Contreras, Cristopher J"
	<cristopher.j.lemus.contreras at intel.com>
Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for
	review on OpenStack Train Upgrade Patches.
Message-ID:
	<93814834B4855241994F290E959305C7530F61C3 at 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 at intel.com>
Sent: 2019年11月5日 22:47
To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso at intel.com>; Liu, ZhipengS <zhipengs.liu at intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at 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 at 99cloud.net>
To: tao.liu at windriver.com
Cc: starlingx-discuss <starlingx-discuss at lists.starlingx.io>,
	"greg.waines" <greg.waines at 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 at 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191108/ae122f8c/attachment-0001.html>

------------------------------

Message: 3
Date: Fri, 08 Nov 2019 03:01:31 -0600
From: cristopher.j.lemus.contreras at intel.com
To: <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker
	images
Message-ID: <3cea8d$6uns3q at fmsmga002.fm.intel.com>

List of docker images required for "platform-integ-apps":

BUILD_ID="20191108T023000Z"

rabbitmq:3.7-management
k8s.gcr.io/kube-proxy:v1.16.2
k8s.gcr.io/kube-apiserver:v1.16.2
k8s.gcr.io/kube-controller-manager:v1.16.2
k8s.gcr.io/kube-scheduler:v1.16.2
k8s.gcr.io/etcd:3.3.15-0
k8s.gcr.io/coredns:1.6.2
quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic
quay.io/calico/node:v3.6.2
quay.io/calico/cni:v3.6.2
quay.io/calico/kube-controllers:v3.6.2
rabbitmq:3.7.13-management
rabbitmq:3.7.13
gcr.io/kubernetes-helm/tiller:v2.13.1
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0
openstackhelm/mariadb:10.2.18
quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11
quay.io/stackanetes/kubernetes-entrypoint:v0.3.1
mariadb:10.2.13
memcached:1.5.5
k8s.gcr.io/pause:3.1
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0
nginx:1.13.3
gcr.io/google_containers/defaultbackend:1.0

------------------------------

Message: 4
Date: Fri, 8 Nov 2019 17:38:25 +0530
From: Saichandu Behara <saichandu.behara at calsoftinc.com>
To: "Bill.Zvonar at windriver.com" <Bill.Zvonar at windrive.calsofthq.com>,
	"starlingx-discuss at lists.starlingx.io"
	<starlingx-discuss at lists.starlingx.io>,  bruce.e.jones at intel.com,
	cindy.xie at intel.com, sgw at linux.intel.com
Cc: Pavan Gupta <pavan.gupta at calsoftinc.com>
Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX
	all-in-one Simplex EdgeX with Openstack
Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6 at calsoftinc.com>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello all,

We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack.

We have two images. StarlingX without Openstack and StarlingX with Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in-one EdgeX simplex.

We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack.

--
Thanks & Regards
Sai Chandu Behara

------------------------------

Message: 5
Date: Fri, 08 Nov 2019 13:15:44 +0100
From: Kris Buytaert <kris at inuits.eu>
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for
	ceph
Message-ID: <c8cc91a6cfb9b812b09399a14d0f3a698a11091d.camel at inuits.eu>
Content-Type: text/plain; charset="UTF-8"

I`m working my way trough https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html

but on step 5. Add an OSD on controller-0 for ceph:

the host-stor-add controllor0 command returns with the following error.

[root at controller-0 etc(keystone_admin)]# system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {}
Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices.

Any ideas how to fix this ?

greetings

Kris

------------------------------

Subject: Digest Footer

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

------------------------------

End of Starlingx-discuss Digest, Vol 18, Issue 70
*************************************************