So glad to see there are 11 more developers join us, and now there are 146 members in the China StarlingX WeChat.

Welcome!

 

These topics were discussed in last two weeks:

Knowledge share:

  1.  Workshop: How-To upgrade OpenStack in StarlingX (shared by @Liu, ZhipengS)

  2.  Hands-on: another starlingx docker images registry for Chinese contributor (share by 张鲲鹏 <zhang.kunpeng@99cloud.net>)

 

Deploy problems (all solved in the WeChat group):

None

 

Questions:

  1. what’s the password of official ubuntu vm image?  (answered,  could use libguestfs-tools to edit passwords.)

 

 

Thanks for your attention

Ran

 

 

 

From: An, Ran1
Sent: Friday, November 8, 2019 8:50 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss]summary of discussions in China StarlingX WeChat Group

 

Hi all:

   The China StarlingX WeChat group was created during the StarlingX 2.0 Meetup (Beijing) on 24th Sept. Currently there are 135 members from Intel, 99cloud, WindRiver, China Unicom, China Telecom, Fiberhome, ZTE  and other companies. (Maybe someone from China Mobile)

   The hottest topic in the WeChat group is about deployment. The discussions covered all versions of starlingX (stx1.0, stx 2.0 and master branch). Customer configuration is also frequently discussed/asked there. Other topics such as openstack domain name (service name), bluestore of ceph, raid card supported were mentioned.

   In addition, we are glad to see some contributors share their experiences in the group, like:

   1. an offline deployment tutorial of stx 2.0[1] from KunpengZhang@99cloud.

   2. an docker registry for Chinese users is built by bin.yang@intel and contributors from Neusoft. The tutorial can be got from [2]

 

Specifically, these topics were discussed in the past week:

Deploy problems (all solved in the WeChat group):

  1. some pods kept on pending status (from ZTE, version 2.0)

       Solution: the Kubernetes worker node on compute nodes were not ready, solved by adding network for compute node manually.  

  2. ansible processing was blocked at docker images download stage. (master branch)

     Solution:  local registry did not take effect. Format of ansible file was incorrect (there are codes changes recently).

 3. some pods of openstack failed to start for the request resource was larger than default limitation. (version 2.0)

     Solution:  use cmd "system helm-override-update modify pod.resources. XXX" 

 

Questions:

  1. does starlingX support real time kernel?  (answered, yes)

  2. how to transfer instances from old system to new one. (answered, use snapshot)

  3. is there an efficient way to check the system status and find the key point during deployment processing. (request a proper answer)

 

[1] https://github.com/zhangkunpeng/starlingx/blob/master/host-unlock/stx-2.0/deployment.md

[2] https://pan.baidu.com/s/1EEk6j17NC8uc5zhKzW-hlw fetch code: t2ix

 

Thanks for your attention

Ran