Hi Greg,

Thanks for your reply.

I was following Standard with Dedicated Storage and can't remember exact URL.
I even did search for "system host-label-assign" but may I made a mistake while searching for labels, apologies for the inconvenience.

I found stx-monitor when I was looking for performance and usage monitoring and ended up with StarlingX training slide set.


Regards,
Danishka


On Sat, Jun 26, 2021 at 6:47 PM Waines, Greg <Greg.Waines@windriver.com> wrote:

Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size.  We have plans to fix this.

 

Greg.

 

From: open infra <openinfradn@gmail.com>
Sent: Friday, June 25, 2021 10:30 AM
To: Zvonar, Bill <Bill.Zvonar@windriver.com>
Cc: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] stx-openstack application applying failed

 

[Please note: This e-mail is from an EXTERNAL e-mail address]

Finally managed to deploy OpenStack but not sure what caused the issue.

Increased disk capacity for docker in worker and reviewed network.

 

On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com> wrote:

I managed to deploy stx-monitoring that require labelling only in controller nodes.

Definitely something wrong with worker-0 labelling

 

 

On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com> wrote:

Here is more information about the issue.

 

Then I set the  openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test).

Then stx-openstack applying progress continued up to 55%.

 

I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network.

 

 

On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote:

thank you Bill and Thiago.

Now I have switched to Release 5.

Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack?

 

for controllers:

 

system host-label-assign $NODE openstack-control-plane=enabled

 

For worker nodes:

 

system host-label-assign $NODE openstack-compute-node=enabled

system host-label-assign $NODE openvswitch=enabled

 

Because these labels are not visible in the release 5 installation guide.

 

On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote:

Hi again Danishka, we discussed this too.

 

It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on.

 

Thanks, Bill...  

 

From: open infra <openinfradn@gmail.com>
Sent: Saturday, May 22, 2021 2:28 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] stx-openstack application applying failed

 

[Please note: This e-mail is from an EXTERNAL e-mail address]

Hi,

 

I have deployed StarlingX R4 (bare metal dedicated storage installation).

stx-openstack application applying was failed.

 

When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending.

I have re-uploaded stx-openstack but the same results.

 

I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week.

 

More details available here.

describe pod osh-openstack-garbd-garbd

 

Regards,

Danishka