Hi Shuicheng

 

Thanks for your response.

 

I am able to assign oam and data networks to my interfaces.

 

I have successfully unlocked my Controller

 

In the section, Generate the stx-openstack application tarball, I am unable to find the tar ball “helm-charts-manifest.tgz”

 

In order to generate the tarball, there is no file “$MY_REPO_ROOT_DIR/cgcs-root/build-tools/build-helm-charts.sh” on my machine

 

Also the command “build-pkgs” to build the packages is not running on my controller.

 

And on the repository mentioned below, there are multiple .tgz files, but none is named “helm-charts-manifest.tgz”

 

http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/helm-charts/

 

 

Can you please help in resolving this?

 

Regards

Anirudh Gupta

 

From: Lin, Shuicheng <shuicheng.lin@intel.com>
Sent: 08 July 2019 06:08
To: Anirudh Gupta <Anirudh.Gupta@hsc.com>; starlingx-discuss@lists.starlingx.io; starlingx-announce@lists.starlingx.io
Subject: RE: [Starlingx-discuss] Unable to set OAM interface in R2.0 28th June 2019 Green Build

 

Hi,

Please check the new cmd in below mail:

http://lists.starlingx.io/pipermail/starlingx-discuss/2019-June/004941.html

 

Best Regards

Shuicheng

 

From: Anirudh Gupta [mailto:Anirudh.Gupta@hsc.com]
Sent: Thursday, July 4, 2019 5:16 PM
To: starlingx-discuss@lists.starlingx.io; starlingx-announce@lists.starlingx.io
Subject: [Starlingx-discuss] Unable to set OAM interface in R2.0 28th June 2019 Green Build

 

Hi Team,

 

I have picked StarlingX R2.0 latest Gren Build dated 28th June 2019 from the link below:

 

http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/

 

I am following the below document in order to build AIO Simplex R2.0

 

https://docs.starlingx.io/deploy_install_guides/latest/aio_simplex/index.html#using-the-system-cli-to-bring-up-and-take-down-the-containerized-services

 

After successfully bootstrapping, I am facing the error in the below command while provisioning the controller

 

[sysadmin@controller-0 ~(keystone_admin)]$ system host-if-modify controller-0 ens3 -c platform --networks oam

usage: system [--version] [--debug] [-v] [-k] [--cert-file CERT_FILE]

              [--key-file KEY_FILE] [--ca-file CA_FILE] [--timeout TIMEOUT]

              [--os-username OS_USERNAME] [--os-password OS_PASSWORD]

              [--os-tenant-id OS_TENANT_ID] [--os-tenant-name OS_TENANT_NAME]

              [--os-auth-url OS_AUTH_URL] [--os-region-name OS_REGION_NAME]

              [--os-auth-token OS_AUTH_TOKEN] [--system-url SYSTEM_URL]

              [--system-api-version SYSTEM_API_VERSION]

              [--os-service-type OS_SERVICE_TYPE]

              [--os-endpoint-type OS_ENDPOINT_TYPE]

              [--os-user-domain-id OS_USER_DOMAIN_ID]

              [--os-user-domain-name OS_USER_DOMAIN_NAME]

              [--os-project-id OS_PROJECT_ID]

              [--os-project-name OS_PROJECT_NAME]

              [--os-project-domain-id OS_PROJECT_DOMAIN_ID]

              [--os-project-domain-name OS_PROJECT_DOMAIN_NAME]

              <subcommand> ...

system: error: unrecognized arguments: --networks oam

 

On checking the help command, I found out that there is no “networks” and “datanetworks” flag in the latest green Build

 

No option mentioned in the document is available

 

[root@controller-0 sysadmin(keystone_admin)]# system host-if-modify help

usage: system host-if-modify [-n <new interface name>] [-m <mtu>]

                             [-a <ae mode>] [-x <txhashpolicy>] [-c <class>]

                             [--ipv4-mode <ipv4_mode>]

                             [--ipv6-mode <ipv6_mode>]

                             [--ipv4-pool <ipv4 pool uuid or name>]

                             [--ipv6-pool <ipv6 pool uuid or name>]

                             [-N <sriov numvfs>]

                             [--vf-driver <sriov vf driver>]

                             <hostname or id> <interface name or uuid>

 

 

However, in the previous green build dated 13th June, both the flags were available in the iso.

 

 

Both options i.e. networks and -d(datanetworks) mentioned in the document are available

 

[root@localhost wrsroot(keystone_admin)]# system host-if-modify help

usage: system host-if-modify [-n <new interface name>] [-m <mtu>]

                             [-p <providernetworks>] [-d <datanetworks>]

                             [-a <ae mode>] [-x <txhashpolicy>] [-c <class>]

                             [--networks <network name or id>]

                             [--ipv4-mode <ipv4_mode>]

                             [--ipv6-mode <ipv6_mode>]

                             [--ipv4-pool <ipv4 pool uuid or name>]

                             [--ipv6-pool <ipv6 pool uuid or name>]

                             [-N <sriov numvfs>]

                             [--vf-driver <sriov vf driver>]

                             <hostname or id> <interface name or uuid>

 

 

 

Can you please suggest what are the new parameters that needs to be configured.

 

 

 

Regards

Anirudh Gupta

(Senior Engineer)

 

 

 

 

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.