Base_OS Role - lack of network configuration

[Tony Tarasov]

Hello Team,

I have a request from a customer to move zabbix out of production env.
We want to use base_os for it.
But after deployment fails because zabbix can't use mgmt network - because base_os don't have it.

Since the configuration of this option is included in the Fuel UI(but inactive but should be) , we expect this option configured after deployment.

By the way - this role is useless if you can't just configure it as you wish.

[Denis Meltsaykin (dmeltsaykin)]

Tony, please add more details. What option is inactive but expected to be activated? Base_os has no network configuration because it's just OS without a role.

[Tony Tarasov (atarasov)]

Hello my dear Denis,

let me clarify this question for you.

You can explore the "ADD NODE" tab and there you can find a "Base_OS"/"Operating System" role which you can assign to any "free" node - That means that we have this particular "ROLE".

Using this "ROLE" pattern on the node, you can describe interfaces and HDD configuration(Touch them, move them) as for other nodes with other "ROLES" from UI such as Controller, Compute, Storage, MongoDB - but the interface configuration is colored grey - which tell us that this option is not activated - which is not so good point.

Using this "ROLE" you can't configure interfaces at the node with "Base_os" as you wish and use it after deployment by your needs.

Let's say more - this unexpected behaviour of our product put other teams under pressure. They are preparing workarounds to avoid the bringing cloud into the "Error" state.
For example - Zabbix agent on Base_OS node can't connect to the Zabbix server on the controller node because of lack of mgmt network on it and the cluster is going in "Error" state - customers see it and arguing that their cluster is down.

Also from your last words I can say that we have a misunderstanding between customers expectations and your expectations. Customers want to be able to configure and use this "ROLE" comfortable near by the OpenStack, but you say this is not a "ROLE" at all and we have uncommited expectations from their side.

So we asking you to discuss this issue with your collegues and managers, you can also contact myself via Slack if needed to get more understanding in this question.

We need the node with "ROLE" Base_OS configurable as any other nodes.

[Sergii Rizvan (srizvan)]

Base OS doesn't have network configuration by design. This is expected behavior not only in 7.0, but in the latest releases also. If you disagree with this behavior, you should escalate this issue to Fuel architects in order to make a review if Base OS need network configuration in future releases.
That's why I'm about to set status of this bug to Invalid for 7.0.